Automatic posting to G/L Codes for different movement type

[former_member190312]

Hi All,

i am really confused how the goods movements ( 101,201,561,122 etc ) are taking the different G/L codes from OBYC ?

After GR (101 movement type), it takes 3 G/L code for financial postings.

one G/L is for stock posting & is taken from "BSX" .

2nd G/L is GR/IR account & it is taken from "GBB". here, what is the transaction like "AKO" for 101 movement type & how they decide ?

& 3rd G/L is Price difference G/L account & it is taken from "PRD" (in OBYC).

Like above, can anybody explain all the  detailed postings for all other movement type ( 201,561,122 etc ) ?

what are the movement types( like 101) where there is financial postings ?

Thanks

  Pabi

[BijayKumarBarik · Accepted solution]

Hi,

The concept of goods movment and auotmatic account determination:

In SAP every movement of goods is followed by one movement type, without movement types no goods movement possible and movement type trigged transaction event keys (OMWN). G/L account assignment and G/L account assigned to transaction event key (OBYC).If all assignment correct/perfact, the GR & IR or any transactions will updated by movement of goods only

In Automatic account assignment: The vital components involved are movement type, Value string , valuation class, chart of account, Valuation area, business key (transaction key), and valuation grouping code, account grouping code & nature of G/L account and Posting keys

Chart of account: Collection of all G/L account

Valuation class: Enable the assignment of account on specific based on material & material type.

Valuation Grouping Code( is known as Valuation Modifier) is used for grouping of all  Valuation Area( for example: plant/plants)

Account Grouping Code (is known as Account Modifier & also known as General Modification) is three character code which is use to break account determination down by movement type

Value string: Value String Indicates the posting rule that always contains the same account assignment for a certain transaction or event (for example a goods movement or an invoice receipt).

Accountinmg document for with movement types are:

For movemnet type 561:

(BSX) Stock A/c - Dr

(GBB-BSV) Initial Stock Entry - Cr

For movemnet type 101(if no excise involved):

(BSX) Stock A/c - Dr

(WRX)GR/IR Clearing- material - Cr

For movemnet type 201:

(GBB-VBR) Consumption A/C:Dr

(BSX) Stock A/c - Cr

For movemnet type 122:

All stock and G/L account updates that occurred during the goods receipt posting(101 movement type ) are reversed.The open purchase order quantity is increased by the returned quantity

PRD key triggers as in the case of price control in material master S and if any price differs in the transaction WRT material master price and in the case of price control in material master V, it also triggers, if no sufficient stock available during posting.

Regards,

Biju K

[ricardo_jimenez4 · Accepted solution]

This message was moderated.

[mathewgeorge]

Pabi,

OBYC is t-code which is relevent to  automatic account determination linking Chart of accounts, Valuation grouping code, valuation class, transaction event key and the GL account.

For movement types, the transaction event keys are fixed except in the case of account grouping code which are further divisions for the transaction event key.

For all movement types the transaction event keys can be easily understood. For example in the case of 101 movement type, stock account (BSX), GR/IR account(WRX) and , PRD(price difference account-in the case where price difference matters) are affected.

In the case of 201, BSX, GBB(consumption account) are generally affected

Like that for all movement types we can easily identify the Keys that is relevant.

AKO is the key used in inventory management that deals with the price difference involved when consignment material is  withdrawn.

Mathew

[Former Member]

Assignment of valuation calss in MMR is also plays an important role in Acct, determination, since in OBYC we do assignment of GL accounts for a valuation class...

[Former Member]

hi,

In the SAP system, the corresponding posting transactions for each

accounting-relevant transaction in Materials Management are predefined. Since

the many individual companies using SAP employ different charts of accounts,

generalized posting records are assigned to each transaction in a so-called value

string.

Instead of specific G/L account numbers, the value string contains the

transaction/event key for the relevant posting transaction. The first

transaction/event key of a posting rule generally stands for the debit posting.

The posting transactions for accounting-relevant transactions in inventory

management and invoice verification are predefined and cannot be changed.

Posting records generalized in a value string (posting rule) are assigned to each

relevant movement type in inventory management and each transaction in invoice

verification. Instead of specific G/L account numbers, this value string contains

keys for the relevant posting transactions (for example, BSX for a stock posting

and PRD for a price difference posting).

You do not have to define these transaction/event keys. They are determined

automatically in the SAP system from the specific transaction in invoice

verification or from the transaction and movement type in inventory management.

You need only assign the G/L account to which postings are to be made to each

posting transaction (taking into account the other influencing factors).

The assignments of the value strings to the goods movements and the breakdowns

of the value strings into transaction/event keys can be found in Customizing for

inventory management and physical inventory. However, you can change neither

the value strings nor their assignments in Customizing.

You assign the relevant G/L accounts to the corresponding posting transactions in

Customizing for valuation and account assignment.

The value string assigned to a specific transaction is determined automatically. It

depends partly on manually entered parameters and partly on parameters derived

internally by the system.

The value string contains the maximum possible posting transactions for a certain

transaction. Which of these posting transactions lead to G/L postings in individual

cases is decided by the program and cannot be defined in Customizing.

The goods receipt posting in the example shown in this figure represents a goods

receipt against an NB purchase order into the warehouse or stores. The relevant

PO item has no account assignment and is of the category standard. The value

string WE01 has been assigned to this business transaction for materials subject to

value-based (and quantity-based) inventory management. The next figure contains

the transaction/event keys assigned to this value string.

These include:

• BSX for (all) postings to stock accounts

• WRX for postings to the GR/IR clearing account following goods and

invoice receipts relating to NB purchase orders

• UMB for the offsetting entry in the case of a price change (accounts for

loss or gain from revaluation)

The documentation for the Customizing activity Configure Automatic Postings

contains more detailed information on all SAP transaction/event keys.

In the standard system, the value string WE01 is assigned to goods receipts for

standard purchase orders (and corresponding reversals and return deliveries) with

items that have no account assignment and are of the categories standard or

subcontracting for valuated material into the warehouse/stores.

For a (valuated) goods receipt against a PO item without account assignment,

a posting is always made to a stock account with the transaction/event code

BSX. The offsetting entry is made to the GR/IR clearing account with the

transaction/event key WRX.

A price difference posting (transaction/event key PRD) is only made if the

valuated material is valuated at a standard price and if the PO price (or the invoice

price) varies from the standard price.

The transaction/event key KDM is needed in Materials Management for exchange

rate differences involving POs in foreign currencies due to differences in exchange

rates at the times of goods receipt and invoice receipt if the material cannot be

debited or credited due to standard price control or lack of stock.

The transaction/event keys EIN and EKG (as well as, perhaps, FRE - see account

determination for delivery costs) are only considered in company codes in which

purchase account management is active (as is legally required in France or

Belgium, for example).

The transaction/event keys BSV, FRL, and FRN are used only in connection with

the item category subcontracting.

For an explanation of why the transaction/event key BSX is included twice, and

the meaning of the key UMB, please refer to the following figure.

The value stringWA14 is provided for the goods movement free-of-charge delivery

(movement type 511) for materials with value-based inventory management.

Regards.

[Former Member]

Hi Pabi,

Each movement type has a posting string or a value string attached to it. This can be checked in OMJJ for a specific movement type under "Account Grouping" subsection or in table T156X for that movement type.

Each value string has different transaction event keys assigned to them and this can be checked in table T156W.

In OBYC, you have to assign for each tranaction event key and the combination reqd for that key to a G/L account. This account is hit when the movement type is called with these combinations.

In your case above, the keys that were triggered are BSX (Inventory Posting), WRX (GR/IR) and PRD (Price Difference) and GBB  is an offsetting for inventory postings.

[Former Member]

CHECK THE t-CODE: OMJJ