Go Coding

Category: SAP Modules

  • Action Control in SAP

    Introduction

    In the vast world of SAP, Action Control serves as a mechanism to automate specific actions based on certain conditions or events. Whether it’s sending out notifications, changing the status of an order, or triggering workflows, Action Control plays a pivotal role in enhancing SAP’s efficiency and minimizing manual interventions. Let’s delve deeper into the concept and understand its significance.

    What is Action Control

    Action Control, often referred to within SAP as “Actions,” provides a way to automate certain tasks or activities based on predefined conditions. For instance, once a sales order is approved, Action Control can be configured to automatically send a notification to the warehouse to prepare for shipment.

    Actions are typically defined by:

    1. Conditions: These are the criteria that determine when a particular action should be triggered.
    2. Methods: These dictate what happens once the action is triggered.

    Benefits of Action Control

    1. Automation: Reduces the need for manual intervention in various business processes.
    2. Consistency: Ensures standard procedures are followed across the organization.
    3. Efficiency: Speeds up processes by automating routine tasks, ensuring faster response times.
    4. Flexibility: Allows for customization to cater to specific business needs.

    Where is Action Control used?

    Action Control can be employed across various modules in SAP, such as:

    1. SAP Customer Relationship Management (CRM): For example, upon creating a service request, an automatic email can be sent to the customer confirming the receipt of their request.
    2. SAP Sales and Distribution (SD): Actions can be used to notify the logistics department once an order is approved.
    3. SAP Supplier Relationship Management (SRM): For instance, after a purchase order is accepted by a vendor, a notification can be sent to the relevant department.
    4. SAP Human Capital Management (HCM): Like sending reminders for training or performance reviews.
    5. SAP EWM: In SAP Supply To Production and Supply To Customer, it is used to define actions that would happen in case the creation of JIT is executed. The JIT triggers other functionalities like EWM update and Proxy calls to Supply To Customer.

    Configuring Action Control

    To leverage the benefits of Action Control, one needs to configure it in the SAP system:

    1. Define Action Profiles and Actions: This involves creating a profile and defining the individual actions within it.
    2. Condition Maintenance: Here, you set the specific conditions under which the action will be triggered.
    3. Determine Processing Time: Decide whether the action should be immediate or scheduled for a specific time.
    4. Link Actions with Business Processes: Integrate the defined actions with the relevant business processes or documents.

    How to implement Action Control in SAP using T Code SAP IMG

    Action Control, a key automation feature in SAP, can be implemented using the SAP Implementation Guide (IMG) through specific T-Codes. The step-by-step guide below will help you set up Action Control in your SAP system using the IMG [This is just a use case, and can vary for different modules]

    Implementing Action Control in SAP through SAP IMG:

    1. Accessing SAP IMG:
      • Log in to your SAP system.
      • Enter T-Code SPRO in the command field. This will open up the SAP IMG screen.
    2. Navigate to Action Control Configuration: Depending on the SAP module you are working in, you will navigate to the relevant path. For instance, in SAP Customer Relationship Management (CRM), you might navigate as:
      • SAP IMG → Customer Relationship Management → Basic Functions → Actions.
    3. Define Action Profiles & Actions:
      • Under the “Actions” section, choose “Define Action Profiles and Actions.”
      • Here, you can create a new action profile or modify an existing one.
      • Within an action profile, define individual actions by providing an action definition, description, and relevant processing class.
    4. Condition Maintenance:
      • Back in the “Actions” section, select “Define Conditions” or “Change Conditions.”
      • For each action, define the criteria or conditions under which the action will be triggered. This can involve setting up conditions based on field values, document statuses, or other relevant criteria.
    5. Determine Processing Time:
      • Still in the “Actions” section, opt for “Determine Processing Time.”
      • Decide whether each action should be triggered immediately, scheduled for a later time, or manually by the user.
    6. Set Up Partner-Dependent Actions (if necessary):
      • If your actions depend on specific partners (like customers or suppliers), navigate to “Define Partner-Dependent Actions.”
      • Here, specify which actions should be linked with which partners.
    7. Integrate Actions with Transactions:
      • Finally, ensure that your actions are integrated with the specific transactions or business processes they relate to.
      • This is crucial to ensure that the action is triggered at the right moment in the process flow.
    8. Testing & Verification:
      • After configuration, it’s a good practice to test the actions in a sandbox or development environment.
      • Create or use an existing transaction that meets the conditions for the action. Ensure that the action gets triggered as expected.
    9. Documentation:
      • Keep detailed documentation of the action profiles, actions, conditions, and any other relevant settings. This will aid future modifications or troubleshooting.
    10. Transport to Production:
    • Once thoroughly tested, transport the configuration to your production system.

    Conclusion

    Action Control in SAP provides an efficient way to automate repetitive tasks, ensure consistency across processes, and enhance overall productivity. By understanding and properly configuring this feature, businesses can significantly improve their operational efficiency and responsiveness. Whether you’re just starting with SAP or looking to refine existing processes, taking a closer look at Action Control can be a game-changer.

  • SAP Next-generation Just-In-Time Supply to Production

    SAP Next-generation Just-In-Time Supply to Production

    Introduction

    In the modern, fast-paced manufacturing world, companies strive to optimize their processes for efficiency, cost-saving, and customer satisfaction. SAP’s next-generation Just-In-Time (JIT) Supply to Production provides an integrated solution that allows manufacturing entities to streamline their production processes, reduce inventory costs, and ensure that the right components arrive just when needed. Let’s dive into this state-of-the-art solution.

    SAP Next-generation Just-In-Time Supply to Production

    What is SAP Just-In-Time Supply to Production

    SAP Just-In-Time Supply to Production is an innovative approach designed for manufacturing setups that thrive on JIT principles. With the challenges posed by varied customer demands and limited storage space, manufacturers need a sophisticated solution. The SAP JIT ensures that components, whether sourced externally or from internal warehouses, are delivered in the right quantity and at the precise moment they’re needed for production, ensuring optimal workflow and reducing unnecessary inventory overhead.

    JIT-Process Architecture

    JIT-Process Architecture

    This architecture represents a flowchart detailing the Just-In-Time (JIT) Supply to Production process in an SAP environment. The diagram shows how various components and functionalities of SAP interrelate, especially in the context of materials management, production planning, logistics execution, and transportation. Let’s break it down:

    1. Production Planning:
      • The process begins with “Production Order (PP)”, which may derive from a “Planned Order” either from PP-REM or PPDS.
      • These planned orders create demands for either JIT (Just-In-Time) or JIS (Just-In-Sequence) processes.
    2. JIT Supply to Production:
      • Master data and communication group management are fundamental components.
      • The control cycles of JIT are managed and modified, leading to various processes like JIT call management, planning of supply to production, scheduling of JIT replenishments, and more.
      • The JIT calls, whether summarized or sequenced, influence the internal replenishment processes and stock transfers.
    3. OEM/Customer (Original Equipment Manufacturer):
      • This section provides an overview and analytics of the JIT supply to production, highlighting potential changes in the plan and monitoring of JIT calls and their components.
    4. Materials Management:
      • This is where scheduling agreements and schedule lines come into play. As materials are planned and ordered, updates to quantities (Qty Updates) are made, which then lead to the creation of various logistics and transportation processes.
    5. Logistics Execution:
      • Before the goods are received, there’s a series of actions such as updating status, delivery creation, setting transfers, and eventually posting the goods receipt.
      • This interacts closely with the Transportation Management and Warehouse Management processes.
    6. Transportation Management:
      • The system manages the transportation of goods via various stages like creating consignment orders, assigning freight units, managing freight orders, and handling advanced shipping & receiving protocols. External replenishments might also be noted via SOAP messages.
    7. Extended Warehouse Management:
      • Once goods are in the warehouse, processes like pick/prepare management, route train loading, and pick execution are carried out. Internal replenishments are managed, and unloading points for goods are defined.
      • The production supply areas and storage bins for different production lines are clearly depicted.
    8. Integration Points:
      • Red dotted lines typically signify integration or informational flow between processes.
      • Green solid lines might indicate a direct flow or process sequence.
    9. Storage and Stock Management:
      • The architecture demonstrates the flow of stock and its management, transitioning between IM-managed source storage locations, destination areas, and EWM-managed areas.

    In essence, this architecture provides a holistic view of how JIT supply to production processes are executed within the SAP environment, integrating production planning, materials management, logistics, transportation, and warehouse management for efficient and streamlined operations.

    Fiori Apps in Just-In-Time Supply to Production

    The SAP Fiori design language brings user experience to the fore, ensuring that processes are not only efficient but also user-friendly. Here are some core apps within the SAP JIT Supply to Production ecosystem:

    a) Manage JIT Calls: This app offers a centralized platform to oversee all JIT calls. You can create, modify, or track JIT calls, ensuring you’re always in sync with your supply needs.

    b) Manage JIT Control Cycles: A control cycle determines the supply frequency and quantity. This app aids in setting up, modifying, or monitoring these cycles, which act as the backbone for your JIT system.

    c) Request Replenishments for Control Cycles: Occasionally, manual intervention may be required to request specific replenishments. This app allows users to make such bespoke requests aligned with established control cycles.

    d) Plan Supply to Production: An intuitive planning tool that integrates with your JIT control cycles, ensuring that your production lines are never starved of the components they need.

    e) Manage JIS calls and Reorder: Just-In-Sequence (JIS) is an extension of JIT, ensuring components arrive not just in time, but also in the sequence they’re needed. This app also provides reordering functionalities in case of unforeseen supply issues.

    f) Monitor Customer JIT Calls: Keeping an eye on the end customer is crucial. This app provides insights into customer JIT calls, enabling manufacturers to foresee and plan for demand spikes or changes.

    g) Manage JIT Delivery Confirmations: Once the components are delivered, confirming their receipt is crucial for inventory tracking and supplier relations. This app streamlines this confirmation process.

    h) Stock Availability Analysis: Real-time visibility into stock levels is critical in a JIT setup. This app provides analytics, trends, and insights into stock availability, ensuring decision-makers are always informed.

    i) Manage Production Supply Areas: Different production lines or units might have distinct supply needs. This app allows for the efficient management of these individualized production supply zones.

    In conclusion, SAP’s next-generation Just-In-Time Supply to Production system is revolutionizing how manufacturers operate. With integrated Fiori apps ensuring a seamless user experience, manufacturers can now optimize their processes, cut down on wastage, and cater to their customers more effectively than ever before. Embracing this solution ensures a competitive edge in the challenging landscape of modern manufacturing.

     

  • Inbound Vs Outbound JIT

    Inbound Vs Outbound JIT

    Introduction

    Have you ever wondered about the intricate dance of products and materials moving in and out of a manufacturing facility? It’s not just a matter of stocking up and shipping out. In the world of Just-In-Time (JIT) manufacturing, the flow is finely tuned to perfection. Let’s delve deeper into the realm of Inbound and Outbound JIT, and see how they differ from each other.

    Inbound Vs Outbound JIT Banner

    Inbound JIT

    Imagine a bustling car manufacturing plant. Now, instead of having months’ worth of parts stocked up in a warehouse, the facility gets its components delivered just when they’re about to be used in production. That’s Inbound JIT for you.

    Inbound JIT focuses on the timely delivery of materials and parts from suppliers to the manufacturing facility. It’s all about reducing storage costs, minimizing the space required for inventory, and ensuring that parts are fresh off the delivery truck and straight into production. This methodology requires a strong and reliable relationship with suppliers. The idea is to have components arrive not a moment too early or a second too late.

    Outbound JIT

    Now, let’s flip the script. Once our cars are assembled, they don’t just pile up waiting for someone to buy them. Outbound JIT is all about ensuring that the finished products are delivered to dealerships or end customers precisely when they’re needed.

    Instead of producing large quantities of products and then finding customers for them, manufacturers relying on Outbound JIT produce based on actual demand or close forecasts. This means lower storage costs for finished products and faster delivery times. It’s about ensuring that the time from the end of the production line to the customer’s driveway is as short as possible.

    Inbound Vs Outbound JIT

    At first glance, Inbound and Outbound JIT might seem like two sides of the same coin. And in a way, they are. Both revolve around the concept of ‘just in time’ – minimizing storage and maximizing efficiency. But here’s the difference:

    • Focus: While Inbound JIT is concerned with materials coming into the production line, Outbound JIT focuses on getting the finished product out to the customers efficiently.
    • Relationships: For Inbound JIT, the manufacturer’s relationship with its suppliers is crucial. Reliable and timely deliveries are the name of the game. On the other hand, Outbound JIT is more about understanding customer demand and ensuring that production schedules align with it.
    • Benefits: Both methods aim to reduce storage costs. Inbound JIT ensures fresher components and minimizes the risk of inventory obsolescence. Outbound JIT, meanwhile, ensures that finished products don’t languish in storage, which can be particularly vital for products that are time-sensitive or have short shelf lives.

    Inbound Vs Outbound JIT

    When the influx of raw materials and parts are made within supplier and manufacturing plants then it involves Inbound JIT. When the movement of final goods is made from supplier to end users, then it involves Outbound JIT. Read more about Inbound Delivery and Outbound Delivery.

    In conclusion, while both Inbound and Outbound JIT share a common philosophy, their applications are distinct yet complementary. In the finely-tuned ballet of modern manufacturing, both play essential roles in ensuring that companies remain efficient, responsive, and cost-effective. And that, my friend, is the magic of JIT in action!

  • Just-In-Time (JIT) and Just-In-Sequence (JIS) Processing in SAP S/4HANA

    Just-In-Time (JIT) and Just-In-Sequence (JIS) Processing in SAP S/4HANA

    Introduction

    The automotive industry is all about speed, precision, and meeting customer needs. A significant part of this involves ensuring that components are available exactly when they’re needed, and in the correct order. This is where Just-in-time (JIT) and Just-in-sequence (JIS) processing come into play. Today, we’re diving into how SAP S/4HANA, a leading enterprise resource planning software, is revolutionizing this process.

    SAP JIT

    What is Just-In-Time (JIT)?

    JIT, or Just-In-Time, is a production method rooted in the principle of reducing in-process inventory. Given the sheer variety of configurations automotive manufacturers offer, there’s a need to have a multitude of components on hand. However, with space at a premium on production lines, it’s crucial to keep inventory lean. This means having suppliers or internal warehouses deliver small quantities of components multiple times a day. In a JIT environment, the sequence in which these parts are delivered doesn’t matter.

    Just-in-Time inventory, commonly referred to as JIT, is an inventory management strategy in which raw materials arrive as soon as production is scheduled to begin but no sooner. The goal is high-volume production with minimal inventory on hand to meet demand and eliminate waste.

    What is JIT in SAP?

    JIT calls in SAP are created for a supplier based upon demands that can be either planned or production orders and even based upon the safety stocks in case of consumption-driven scenarios.

    SAP provides multiple T-Codes to manage the JIT scenarios. SAP has also introduced Fiori Apps to manage JIT for S/4 HANA customers.

    It is important to note that JIT is a very complex process as it highly depends upon the efficacy of the ordering system so that items are delivered with the right amount at the right time.

    SAP JIT Types

    Based on scenarios JIT can be divided into two structures

    • JIT Supply to Customer: Also, known as JIT S2C covers the JIT processes from the perspective of a supplier.
    • JIT Supply to Production: Also, known as JIT S2P covers the JIT processes from the perspective of Manufacturers.

    JIT in R/3 ABAP

    SAP on-premise system provides all the methods that can be used to maintain a plan, create scheduling agreements, create a JIT order, plan a JIT forecast order, and many other relevant operations. Various Reports and T-codes are available to create and manage the same such as:

    JIT in S/4 HANA

    SAP S/4 HANA provides various Fiori Apps that can be used to create, manage and plan a JIT. Different Apps provide different functionality. The technologies involved for the same include ABAP CDS, BOPF, ABAP RAP, and Fiori.

    What is Just-In-Sequence (JIS)

    Unlike JIT, Just-In-Sequence (JIS) focuses on delivering the right components to the production line in the exact sequence they are needed. This becomes especially crucial when suppliers are building complex modules or sets that are directly delivered to the line.

    Just-In-Time (JIT) and Just-In-Sequence (JIS) Processing in SAP S/4HANA

    SAP S/4HANA has risen to the occasion, offering next-gen JIT and JIS processing, catering to both automotive manufacturers and their wider ecosystems. It provides support for both summarized JIT calls and sequenced JIT calls from both outbound and inbound perspectives.

    JIT Supply to Production

    Delving deeper into the JIT Supply to Production, we see a demand-triggered pull signal to either internal or external supply sources. The highlights of this process include:

    • Flexibility: You can cater to both summarized and sequenced JIT calls.
    • Integration: Seamless linkage with SAP S/4HANA inventory management and SAP Extended Warehouse Management (SAP EWM) means tasks can be directly created in embedded EWM.
    • Adaptability: Reordering of sequenced JIT calls in case of damage or quality issues is possible, ensuring production isn’t halted.
    • Real-time Transparency: With embedded analytics, companies can have an instant overview of their operational system, facilitating better decision-making.

    What’s more, the use of communication groups for multiple JIS call recipients and lifecycle management for control cycles ensures that this system can be tailored to fit specific customer needs.

    JIT Supply to Customer

    Switching gears to JIT Supply to Customer, we find a similarly robust system. Key takeaways here include:

    • End-to-End Process Support: With both summarized and sequenced JIT calls being supported, companies have a comprehensive toolkit at their disposal.
    • Flexibility: Rules-based component group determination, combined with simplified grouping of sequenced JIT calls, allows for precise and efficient packing and delivery.
    • Usability: The new SAP Fiori user interface, combined with a monitoring app for JIT calls, ensures that the system is both powerful and user-friendly.
    • Transparency: Thanks to SAP S/4HANA’s embedded analytics, companies can get a clearer view of their stock availability and demand analysis.

    In essence, SAP S/4HANA’s next-gen JIT solutions elevate the JIT processing, offering automotive companies the tools they need to streamline processes, enhance reliability, and ultimately, boost customer satisfaction.

    In conclusion, as the automotive world becomes more complex and customer-centric, systems like SAP S/4HANA’s JIT and JIS processes will be the linchpin holding production lines together, ensuring that the right part is always at the right place, at the right time.

  • Journal Entry Posting in SAP

    Preface – This post is part of the SAP FI series.

    Introduction

    Journal Entry posting in SAP FI is the process that takes a batch, validates it for consistency, then generates appropriate FI documents and posts entries in line-item accounts required for subsequent business processing.

    In this article, we will learn about G/L posting.

    How to perform G/L posting

    T-code: FB50

    Path:

    SPRO -> SAP Reference IMG -> Display IMG -> Financial Accounting -> General Ledger -> Posting -> FB50 – Enter G/L Account Document -> Double click

    Steps:

    1. Enter t-code FB50

    Or go to the path described above

    2. Enter Company code

    3. Provide header data

    Enter required details: Document date, Posting date, Header text.

    4. Provide item data. Enter required details:

    • Enter debit account (G/L account)
    • Select Debit
    • Enter debit amount
    • Enter credit account (G/L account)
    • Select Credit
    • Enter credit amount

    5. Check status in the Amount Information Section (for success, the status indicator will be green)

    6. Click on Save

    7. The status bar shows the generated document number and confirms the posting.

  • How to Open and Close Periods in Posting Period Variant in SAP

    Preface – This post is part of the SAP FI series.

    Introduction

    The Posting Period Variant is used to maintain the opening and closing period in the fiscal year for posting purposes. To learn how to a create Posting Period Variant, click < link to Create Posting Period Variant>

    In this article, we will learn how to open and close periods in Posting Period Variant.

    How to open and close periods in Posting Period Variant?

    T-code: S_ALR_87003642

    Path:

    SPRO → SAP Reference IMG → Financial Accounting → Financial Accounting Global Setting → Posting Periods → Open and Close Posting Periods → Execute.

    Steps:

    1. Go to the t-code or follow the path.

    2. Click on New Entries.

    3. Provide details:

      1. Var: Posting period variant
      2. Account type
        1. ++=Valid for all account types (masking)
        2. A = Asset
        3. D = Customers
        4. K = Vendors
        5. M = Materials
        6. S = General Ledger Account
      3. From Account/To Account: Account range
      4. From per.1: Starting Period
      5. Year: Year
      6. To Period: Ending period
      7. From Period2: First special period
      8. To period: Period
      9. Authorization Group: To open a period for a particular user.

    Note: All the other periods will remain close for posting for the defined account number range.

    4. Click on Save

     

  • How to Define Posting Period Variant in SAP

    Preface – This post is part of the SAP FI series.

    Introduction

    SAP Financial Accounting (FI) posting period variants are used to maintain the accounting periods. These accounting periods are open for posting and thus balance all the closed periods. Also, one or more company codes can be assigned to these posting periods.

    How to create posting period variants in SAP FI?

    T-code: OBBO

    Path:

    SPRO → SAP Reference IMG → Financial Accounting → Financial Accounting Global Setting → Document → Posting Periods → Define Variant for open Posting Periods → Execute.

    Steps:

    1. Go to t-code or follow the path mentioned above.

    2. Click on New Entries

    3. Enter the details: Posting period variant key and description.

    4. Click on save.

     

  • Field Status Variant and Field Status Group in SAP

    Preface – This post is part of the SAP FI series.

    Introduction

    SAP has provided a tool to assign the same properties to multiple objects, often termed a field status variant tool. The field status variant defines the input fields such as cost centre, plant etc.

    The field status group defines field type as a mandatory, option or suppressed. The field status variant groups the field status group and are assigned to the company code.

    In this article, we will learn:

    • How to define Field Status Variant and Field Status Group
    • How to assign Field Status Variant to Company Code

    Difference between Field Status Variant and Field Status Group

    • Field status groups are maintained in G/L accounts and define the fields when posting to G/L.
    • The field status group is assigned to a field status variant.

    How to define Field Status Variant and Field Status Group?

    Path:

    SPRO → SAP Reference IMG → Financial Accounting (New) → Financial Accounting Global Settings (New) → Define Field Status Variant

    Steps:

    1. Go to the path.

    2. Click on execute icon provided on the left side of Define Field Status Variants.

    3. Click on the new icon. Paper

    4. Provide the details- Field Status Variant key, description

    5. Select the new field status variant and click on Field Status Group Folder.

    6. Enter Field Status Group to be assigned and click on Field Status.

    7. Select Field Group.

    8. Maintain the field status for group fields.

    9. Press back and click on save.

    How to assign Field Status Variant to Company Code?

    Path:

    SPRO → SAP Reference IMG → Financial Accounting (New) → Financial Accounting Global Settings (New) → Assign Company Code to Field Status Variant

    Steps:

    1. Go to the path.

    2. Maintain the Field status variant to the Company code list

    3. Click on Save

  • How to Define Document Type and Number Range in SAP FICO

    Preface – This post is part of the SAP FI series.

    Introduction

    In this article, we will learn:

    • List of Account Types in SAP
    • List of Standard Document Types in SAP
    • How to define Document Type
    • How to describe a Number Range

    List of Account Types in SAP

    Account Type Description
    A Asset
    D Customer
    K Vendors
    M Material
    S General Ledger Accounts

    List of Standard Document Types in SAP

    Document Type Description
    AA Asset Posting
    AB Accounting Document
    AE Accounting Document
    AF Dep. Posting
    AN Net Asset Posting
    C1 Closing GR/IR accts
    CI Customer Invoice
    CP Customer Payment
    DA Customer
    DB Cust. Recurring entry
    DE Customer Invoice
    DG Customer Credit Memo
    DR Customer Invoice
    DZ Customer Payment
    KA Vendor Document
    KG Vendor Credit Memo

    How to define Document Type?

    Path:

    SPRO -> IMG -> Financial Accounting -> Financial Accounting Global Setting -> Document -> Document Types -> Define Document Types -> Execute

    1. Go to the path mentioned above

    2. Click on New Entries

    3. Provide the details.

      1. Document Type Key
      2. A number range for the Document Type
      3. An Account type which you would like to do posting
      4. Also enter an Appropriate Selection in the Control Data Section

    4. Click on Save

    How to describe a Number Range?

    1. Press the ‘Number range Information’ Button in the properties section.

    2. Provide details.

      1. Company Code
      2. Intervals

    3. Click on insert interval

    4. Provide details.

      1. Unique number range key
      2. Fiscal year
      3. Start and End Number of range without overlapping other Number Ranges
      4. Mark checkbox External if you want to insert the Document number manually during document creation
      5. Click Insert button

    5. The new number range is listed.

    NOTE: You can assign a number range to one or more document types.

  • Financial Statement Versions in SAP

    Preface – This post is part of the SAP FI series.

    Introduction

    Financial statement versions (FSV) help to group related accounts prepare the balance sheet and income statements for reporting purposes. SAP has provided a standard financial statement version for all the countries. As per the requirement, you can use the SAP standard FSV or you can create your financial statement version.

    How to create Financial Statement Versions in SAP?

    T-code : OB58

    Path to FSV:

    SPRO -> SAP Reference IMG -> Display IMG -> Financial Accounting -> General Ledger Accounting -> Business Transactions -> Closing -> Document -> Define Financial Statement Versions

    Steps to create Financial Statement Versions in SAP:

    1. Go to T-code OB58

    2. Select New Entries

    Financial Statement Versions in SAP

    3. Provide the details.

      1. Fin. Stmt.Version: It identifies the financial statement versions in SAP. Enter the new four digits key.
      2. Name: Enter the descriptive name of the FSV.
      3. Maint. language: It describes the language in which your financial statement is to be maintained. Enter the language key.
      4. Item Keys Auto: It determines whether the item keys be assigned automatically or manually. Item keys are linked to financial statement items in the FSV. For the automatic assignment, it is recommended to mark this option.
      5. Chart of Accounts: Enter the COA to tag to FSV.
      6. Group Account number: Use this indicator to account number from the group chart of accounts to account number. This option is only valid if we are using consolidation.
      7. Fun.area.perm.: Use this indicator to use organizational elements for the functional area. It helps maintain alternative group costs.

    4. Click on Save.

    5. Click on “Fin. Statement items” to configure financial statement items.

    There are seven nodes we need to maintain here. By clicking Create item, we can add a new item or delete it by clicking Delete item.

    Basic nodes:

    1. Financial Statement Notes
    2. Not Assigned
    3. P+L result
    4. Net result : loss
    5. Net result : profit
    6. Liabilities+Equity
    7. Assets

    • We can maintain node texts by clicking on the nodes.
    • We can create sub-nodes for the given nodes by clicking on nodes and clicking on the “Create Items” button.
    • We can assign Accounts or groups of accounts to given nodes by selecting a node and clicking on the “Assign Accounts” button.

    Example

    Let us take the Assets node. We will maintain the Assets text, create sub-nodes, and assign Accounts.

    1. Double click on “No text exists” and maintain texts.

    2. Select Asset and click in Create Item button to create sub-nodes. Add all the Asset items.

    After successful maintenance, the configuration screen will look like this.

    We can also create sub-nodes for Asset sub-nodes.

    1. To assign Accounts, select node and double click on Assign Items.

    Enter the details and select both Debit/Credit indicator

    2. After maintaining, click on save.

    We have successfully assigned the Account to the node.