Generated by Jive on 2014-05-29+02:001

SAP ERP - Logistics Materials Management(SAP MM): Account Determination - Why wasthis account determined?

Joao Sousa 2014/4/28A lot of times you see people in forums asking questions about OBYC, on why account X was determinedwhen the system should be determining account Y. Instead of trying the forums, where it is extremely hard toget help because people don't have access to your system, you can debug the call and see for yourself.

"Debug? But I'm a functional consultant!" - You're a "consultant" and a consultant should understand alanguage as basic as ABAP. You don't have to write it, you have to read parts of it, so don't whine. Trust me, itwill make your life much easier.

There are two transactions you should know about: ST05 and SE37, but first lets use MIGO to provide anexample. Go to MIGO and create a document with a 201 movement (consumption to cost center) and stopbefore saving the document.

Go to ST05. Select "Buffer Trace" (SQL Trace should already be pre selected). Press "Activate Trace". Go toMIGO, save the document, and then back in ST05 press "Deactivate Trace" and "Display Trace". Execute.

In the object name column set a filter for T030. It depends if your hit is in the buffer or SQL, but you should seesomething like this (in this case it's blue because it hit the buffer):

So my 201 movement is hitting BSX with valuation class 1100 and GBB with VBR 1100. That provides somevaluable information about how SAP is reading OBYC, namely you see it is using VBR and 1100.

If you want more detail you have to go SE37 and debug (and I seriously recommend you at least learn todebug). Select function module MR_ACCOUNT_ASSIGNMENT and look for the following code (I knew I had todebug this FM because if you double click SAPLKONT on the previous picture, you navigate to the code wherethe SELECT is made):

SAP ERP - Logistics Materials Management (SAP MM): Account Determination - Why was this accountdetermined?

Generated by Jive on 2014-05-29+02:002

The important one is the SELECT to T030. If you set a break point you will be able to see (when you post anew document) the various selections to your OBYC configuration, and can see in T030-KONTS and T030-KONTH which accounts were determined (this way you can see if your account determination is standard or ifthe account is being changed in a substitution further down the line).

Above the SELECT you can see the various configurations: XKOMO - Relevant for account modification XBWMO - Valuation modification relevant XBKLA - Relevant for evaluation class

I hope this helps you understand what is wrong with your account determination, and helps you understandhow SAP works.466 account_determination, obyc, account_assignment;

animesh sundriyal2014/4/30 1:19Hello Joao, thankyou very much for this information and yes this is sometimes a challenge for the developer to findout the account determination.

SAP ERP - Logistics Materials Management (SAP MM): Account Determination - Why was this accountdetermined?

Generated by Jive on 2014-05-29+02:003

RegardsAnimesh Sundriyal

Manosij Basu2014/4/29 10:45Good document!

However, most of my OBYC problems get sorted through the 'Simulation' option in AAD using the movementtype.