Skip to Content

Note: Assuming that reader is aware of MM-FI integration concepts. You can go through below blog  as well to understand the MM-FI integration concepts.


MM-FI integration: A conceptual understanding

Now we know how MM and FI are integrated and how the account determination happens. If we want to test inventory account determination, neither you need to do actual material posting in the system nor go through master data and customization to identify the accounts. SAP has delivered account determination simulation tool.

This helps to find how an account is determined while posting stock related transactions. We just need to input plant, material, movement type and select the transaction we would like to check say GR for purchase order, GR for process order etc. Based on above inputs, system would read customization, master data and simulate the account determination process. Apart from above, system would also identify missing account assignments for a given transaction. This would further help to analyze issues in an easy manner.

Go to T-code OMWB and close the initial popup. Click on Simulation button.

/wp-content/uploads/2014/05/q_456405.png

Fill in plant, material , movement type and enter. Transaction list would be automatically refreshed based on the movement type. Double click on required type of transaction to be checked say GR and click on Account assignments.

/wp-content/uploads/2014/05/q_456405.png

In next screen, we can see the list of all available transactions possible for this movement type, plant and material combination. Some fields like material type, valuation class etc. are derived from material master data. Some fields like valuation area, valuation grouping code etc. are derived from customization of the plant.

/wp-content/uploads/2014/05/q_456405.png

In this screen, we can see what all accounts are determined for different kind of transactions.

EG: For Inventory posting, you can see Debit/Credit posting keys and respective G/L accounts. If there are any missing account assignment for a given transaction, this is also highlighted with text as “Missing”.

In above example, you can see this happened for Purchase account and purchase offsetting account. We don’t have any account assignments here as we are not using this scenario. By this way, we can clearly identify the gaps in account assignment without even doing the actual posting.

We can change to different movement types and transaction combinations and see how account determination happens and based on what fields it happens. You can try this in your system for various permutations and combinations.

Second feature available with this tool is, to check the screen layout. This would help to identify any conflicts in screen layout rules for the inventory G/L account item during material document posting.

Screen layout for the inventory account item is determined at two levels.

  1. From field status group of movement type
  2. From field status group of inventory G/L account.

Click on “Check screen layout” button. In Next screen, we can see what is the field status set at movement type level and G/L account level. We should ensure that, there is no conflict between these two field status exist.

EG: We can’t have a field mandatory in one FSG and suppressed in other FSG. Posting would fail in such cases.

Sample output:

/wp-content/uploads/2014/05/q_456405.png


Just hover on the small ICON to see if a field is Mandatory/Optional/Suppressed/Display only. Any conflicts found should get reported in the error log in tool bar.

In case of conflicts, priority would be given in the sequence below with the exception of Required and suppressed combination which is not allowed.

  1. Suppressed
  2. Display
  3. Required
  4. Optional

Third option provided by this tool is, “where used list of G/Ls”. This would help to Identify in what all scenarios a G/L has been configured in the system.

From the main screen of OMWB, click on where used list of G/L.

/wp-content/uploads/2014/05/q_456405.png

Enter company code and valuation area in next screen and execute.

Sample output:

This output shows the list of valuation classes and transaction keys a G/L has been assigned to.

/wp-content/uploads/2014/05/q_456405.png

Hierarchy is as below.

Chart of accounts

                |-G/L account

                                |-Valuation class

                                                |-Transaction event key

                                                                |-Account grouping code

Hope this information would be helpful in your projects 🙂

Your valuable feed back/comments are much appreciated.

Regards,

V V

To report this post you need to login first.

72 Comments

You must be Logged on to comment or reply to a post.

  1. Sridhar Bolisetti

    Hi VV,

    Simply superb.  You are a very good excavator of treasure mine of knowledge.

    Excellent way of presentation with beautiful flow of logic for easy understanding of system capabilities.  Thanks for sharing.

    Regards,

    Sridhar

    (0) 
  2. Chandra Mohan

    hi venod simply supppppppppppper

    thank for its.

    I  want some help from you like what is job and  jobs in sap fico ?day and monthly jobs?

    when we are using sessions ?wt are the main sessions in sap fico ?days and monthly sessions are using in sap fico?

    Thanks and regards,

    Chandu,

    Chandufico87@gmail.com

    (0) 
    1. Vinod Vemuru Post author

      Thanks Chandra 🙂

      All your questions were already discussed many times in forum. Just do a search on “Batch jobs in SAP”

      (0) 
  3. Sheryl Perry

    Thanks so much for sharing your knowledge in a great document, Vinod.  I can share this with my Cost Accountant and her staff.  It will make things much easier for them, and for me.

    Regards,

    Sheryl P

    (0) 
  4. RANSINGH SATYAJIT RAY

    I Read a lot of blogs on account determination but didn’t find them useful, But your was simply great and my concept is clear after reading it. Great stuff great work.

    Regards

    Ransingh

    (0) 
  5. Oghenetega Oruade

    thank Venod. You made this complex and confusing topic  as easy as abc …. for me .  i I have better understanding on FI-MM integration ….Thanks. God Bless You for sharing ….

    (0) 
      1. Oghenetega Oruade

        please venod , i have a problem which i want you to give me clarification, i did  a good receipt and no accounting document was generated . could you explain possible reason for this….

        (0) 
            1. Oghenetega Oruade

              thanks Mohammed i just checked the material master, and the the moving average price was zero…. i extended the material to a another plant and maintain the the price there, i ran a demonstration of good receipt on sand box , and i got the FI document… thanks you were absolutely right about it thanks again…………….

              (0) 
  6. Michal Szymanski

    Hi Vinod,

    I have a question please: How does it come, that some of the movement combinations are not appearing in the simulation screen? I have ensured that a certain movement combination is foreseen in OMJJ =>Account Grouping (movement 601 with special stock indicator and consumption posting); I see it is being executed/processed well (but obviously without any accounting document)?… In the simulation screen there is no such combination either…

    I hope anyone knows the reason…

    (0) 
      1. Michal Szymanski

        Hi Vinod,

        in OMJJ I’ve renamed the short text of each 601 type (differentiated by special stock and/or movement indicator and by consumption posting). So in the OMWB I see that the “E” for order on hand is not being taken into account for simulation, while the “K” for consignment is. Consumption posting E is being taken into account. L stands for goods movements for delivery note. In OMJJ =>  Account grouping the entries are there, so why they don’t appear in OMWB? The material has a standard price and strategy group 20, and it supposed to be purchased (source of supply F). Logistically the process is going fine. 101 E goes well too. 601 E does not…OMWB_601_Simulation.JPG

        OMJJ_601_Account_grouping.jpg

        Rgds,

        Michal

        (0) 

Leave a Reply