Business Function LOG_MM_SIT Activation for MTO Scenario

[former_member220526]

Hi,

I have activated Business Function LOG_MM_SIT in EHP 7. I have maintained all settings as defined for this business function. In case of MTS process it executed smoothly but when we go for MTO scenario system behave differently.

While goods movement from production to inventory against in MTO scenario system is debited Stock In Transit (SIT) GL rather than Inventory GL and using same (SIT) GL for credit posting while processing PGI, and after doing PoD system uses COGS GL for debit and Stock in Transit GL for credit posting. 

As per my understanding at time of goods received from production to inventory accounting entry should be:

Dr Inventory

      Cr Inventory Change

At time of doing PGI accounting entry should be:

Dr Stock In Transit (SIT)

          Cr Inventory

And entry at time of Proof of Delivery (PoD) entry should be:

Dr COGS

         Cr Stock In Transit (SIT)

The issue is that why system is not debited Inventory GL in case of MTO scenario after activating business function.

[former_member220526 · Accepted solution]

When you post the Goods Receipt for the Order you post your reception

into the sales order stock of the sales order 70000005 item 10.

This sales order is valuated: In the table VBAP for this sales order

and item you can see the valuation indicator VBAP-KZBWS = M.

Also, we can see in the MSEG table for material document you were

posting a goods receipts for the sales order stock 'E'.

Table: MSEG

MBLNR MJAHR ZEILE BWART MATNR WERKS LGORT CHARG INSMK SOBKZ

4900000185 2014 0001 101 000000000100000010 1000 0001 D140612379 X E

<<<<<<

When we manage valuated sales order stock, all the valuation data is

stored in a different table:

We have the valuation table MBEW for the normal, anonymus warehouse

stock which is not assigned to any special valuated stock.

When the stock is assigned to a valuated project, the valuation data

is no longer contained in MBEW, but in the special valuation table EBEW.The data in EBEW is created with the first goods movement made against

this valuated project. This valuation table EBEW contains a price

control, a price, a valuation class, etc. that may be different from

the data in MBEW.

For example, the normal stock in MBEW may have standard price control

but the same material in the same plant assigned to a specific

valuated sales order may have moving average price control in EBEW.

The data in the valuation table EBEW is totally independent from the

data in MBEW, so, if we change the data in MBEW, it will not have any

effect on the data in EBEW.

This is the case here: we are different Valuation Class for the Sales

order stock 'EBEW-BKLAS' and for the normal stock 'MBEW-BKLAS'.

So, this is not a bug or an error in the account determination.

When you post the goods receipt, the function module

MR_ACCOUNT_ASSIGNMENT carries out the selection of the accounts from

the table T030 with this Valuation class 7999:

SELECT SINGLE * FROM T030 WHERE KTOPL = KONTENPLAN

                           AND   KTOSL = VORGANGSSCHLUESSEL

                           AND   BWMOD = BEWERTUNG_MODIF

                           AND   KOMOK = KONTO_MODIF

                           AND   BKLAS = BEWERTUNGSKLASSE.

KONTENPLAN         =  1000

VORGANGSSCHLUESSEL =  BSX

BEWERTUNG_MODIF    =  0001

KONTO_MODIF        =

BEWERTUNGSKLASSE   =  7999

-> Account Determined 0000116150

I hope this information can clarify the system behavior.

[moazzam_ali · Accepted solution]

Hi Faizan

Good to see that you've posted the solution. It seems like it is SAP response.

Thank$

[former_member220526]

G G Mozam bhai... Ref: Yasir Dogar