Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification.
#Sap movement type 561 transaction key verification
Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting. Transaction/event key (internal processing key)
#Sap movement type 561 transaction key code
If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code. It applies to all valuation areas which are assigned to this valuation grouping code. You must define the automatic account determination individually for every valuation grouping code within a chart of accounts.
If the automatic account determination within a chart of accounts is to run differently for certain company codes or plants (valuation areas), assign different valuation grouping codes to these valuation areas. Valuation grouping code for the valuation area You must define the automatic account determination individually for each chart of accounts. If the user enters a company code or a plant when entering a transaction, the R/3 System determines the chart of accounts which is valid for the company code. When entering the goods movement, the user does not have to enter a G/L account, since the R/3 System automatically finds the accounts to which postings are to be made using the following data: How does the system find the relevant accounts? Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost lines are created in the following accounts in the case of a goods issue for a cost center:
0 kommentar(er)
