The logical process of account assignment Determination

The logical process of account assignment Determination
It's very easy if you are strong in IMG. I can guide you go to omjj create a movement type by copying 601 to say 901 (or z01) now:

1) Table t156 will have something called posting reference.

2) taking the posting reference to the table t156sy, for the posting reference determined in the step #1, SAP finds two things called: value reference key and quantity reference key

3) value reference key is verified in Table t156w and qty ref in t156m earlier t156s used to be there before 4.6 B. it is divided into t156sy (client independent system table) and t156sm (client dependent-customized ). for our context, t156sy is important.

With the above knowledge, let's now see how movement type determines quantity and value reference keys in any transaction:

1) Your movement type says 601: From this, (t156), it finds posting reference: 601

2) transaction that you are using: Say vl02n, using this value, it goes to t158, it finds movement indicator, kzbew (L goods movement for delivery note)

If the transaction involves any special stock, (say consignment W). For simple

Case, say no special stock so... blank for sobkz

3) plant is supplied by the transaction that you do material # You will supply. for plant and material # You supplied, it goes to t134m (material type config) to see if value Update (wertu) and quantity Update (mengu) are active or not. it selects this combination and passes back to code in its search receipt indicator (if it is stock transfer, say t etc )... in your case, it is blank consumption indicator (blank for you) (consumption posting specifies that the consumption is to be posted to a consumption account (v) or an asset account (). the indicator is used in the case of goods receipts for purchase orders and is derived from the account assignment category of the purchase order .... used by SD and QM to determine if an assignment to CO object is necessary ). just don't worry about this very much

4) Now sap found all the values it requires (above listed), to go to t156sy to find what are the values of value string and quantity string. so, while narrating this, I ran the entries suitable for the above scenario in t156sy and go the below values:

Pstng strng ref 601

Value updating x

Qty updating x

Special stock

Movement Ind. L

Receipind.

Consumption

Value string wa01

Quantity string ma01

Sloc. Necessary x

W/O value strg.

Insplotorigin D 05

Insplotorigin C 02

Bus. Trans D pms1

Bus. Trans. c pms5

For you, just important ones are:

Value string wa01

Quantity string ma01

5) Now, it turns out to be more interesting:

Let's talk about value string first: wa01

Go to t156w with wa01 you will have the value of 'trans./ev. key' as below:

BSX

GBB

PRD

BSX

Umb

GBB

GBB

BSX

This content derived from t156w and earlier determined content of t156sy together gets into a valuation program saplmbgb (Form wa01 ).

In this program, it loops an internal table x156w and extracts values: Transaction/event key and its corresponding value simultaneously.

From t030 (obyc configuration for account determination) will be looped to pass the determined g/ls back to code (for the above transaction/event keys)

From t156w, counter (say 02) for corresponding processing key (ex: GBB) is used to determine matching keys (02) in t156x

Of course, passes the account modifier to t030:

Movement type 601

Value updating x

Qty updating x

Special stock

Movement Ind. L

Consumption

Value string wa01

Consec. Counter 2

Acct modif VAX

Check Acct. ass. X (again VAX and vay are determined based on cost object requirement, ignore it for your basic understand now) depends upon consumption posting. the result goes to an internal table xaccit to provide us the final accounting document results.

T156b can be used for copying Co object (say project or wbse) to PRD account if customer wants. Second episode continues tomorrow

Note 34913-the handling of tables t156s, t156x, t156w, t163k
Summary

Symptom

Entries are missing or available entries are to be modified in Table t156s. error message m7001 'entry & not in Table t156s (system error) 'is displayed when posting a goods movement.

Additional key words

T156s, t156x, t156w, t163k, ome9, m7001

Cause and prerequisites

Solution

The above tables are read as follows during a goods movement:

T163k
The 'consumption posting' indicator and the account grouping code for the automatic account determination are read from Table t163k for the Account assignment category from the purchase order.
The consumption posting is empty for goods receipts that are not assigned.
The value from t163k is not always used for goods issues.
During goods issues with movement type 601, the 'consumption posting' indicator originates from the delivery.
You can maintain the table with transaction ome9.

T156s
This table must contain an entry for the following key fields, because otherwise error message m7001 'entry & not in Table t156s (system error) 'is displayed.
The movement type is entered in the goods receept transactions.
The value update is stored in the detail screen for the material type, transaction oms2.
The quantity update is stored in the detail screen for the material type, transaction oms2.
The special stock indicator is entered in the goods receept transaction.
The Movement indicator is derived from the transaction-Table t158.
Consumption posting indicator for stock transfer.
The consumption posting is selected from t163k.
For this key, important economical mical data such as value string and quantity string is read from t156s during a goods movement. if a value string is maintained for an entry for a material with value update, this must not be deleted because otherwise inconsistencies may occur.

T156x
If you add an entry in t156s, you must also maintain t156x. t156x has the same key fields as t156s plus value string plus Numerator. the account grouping code for every entry is stored here. it is used in the Automatic account determination.

T156w
The respective transaction/event keys (GBB, WRX) for the value string are maintained here. for these transaction/event keys, you must store a g/L account for the automatic account determination considering the valuation grouping code and the account grouping code (from t163k and t156x ).

This article from csdn blog: http://blog.csdn.net/LOVESAP/archive/2009/07/27/4385230.aspx