- SAP MOVEMENT TYPE TO TRANSACTION KEY DETERMINATION HOW TO
- SAP MOVEMENT TYPE TO TRANSACTION KEY DETERMINATION CODE
In case, you enter a G/L account for the data set without a valuation class the program will uses this account as default value when you create a purchase order for a material without valuation class.As per standard SAP, system determines G/L account as per defined rule for the account determination. purchasing uses the same function module for the account determination. The reason why you should leave the G/L account for debit and credit blank is that other components e.g. So even if you would like the program to use the G/L account determined in step 1 (as explained in note 441991) it is necessary to maintain a rudimentary data set in order to prevent the error message 'M8 147'. In this case the G/L account from step 2 is used. But the customer has the possibilty to change the program behaviour by setting XPKON to ' '. In SAP standard the indicator is set to 'X' hence the G/L account from step 1 is used. (Transaction OMJJ Movement Type -> Account Grouping) Based on the indicator 'Check account assignment' (T156X-XPKON) the program uses the G/L account determined in step 1 or 2. Hence, at least an entry for the above mentioned data set has to be maintained.ģ) Afterwards the program reads the customizing for the movement type. At this time, the program does not know whether the G/L account from step 1 or 2 is used. In case no entry for the data set charts of accounts, transaction, valuation modif, valuation class and general modification is maintained in the account determination customizing the error message 'M8 147' is issued. The determined account is saved internally (dm07m-konto).Ģ) When the accounting interface tables are setup the program reads the account for the receveing plant/material. valuation class) of the sending plant/material. D) If you are using a non-valuated material, please check note 441991:ġ) As explained in note 441991 the account for the for the receveing plant/material is determined based on the data (e.g. KONTENPLAN VORGANGSSCHLUESSEL BEWERTUNG_MODIF SELECT SINGLE * FROM T030 WHERE KTOPL = KONTENPLAN AND KTOSL = VORGANGSSCHLUESSEL AND BWMOD = BEWERTUNG_MODIF AND KOMOK = KONTO_MODIF AND BKLAS = BEWERTUNGSKLASSE. Make sure that there is not any missing customizing setting.Ĭ) Set a breakpoint in the function module MR_ACCOUNT_ASSIGNMENT and check the missing entry into the table T030 and then compare with OBYC configuration:
In transaction OBYC check if transaction key is correctly assigned to the account numbers. In transaction OMSK check if valuation class is correctly assigned. In transaction OMWN check if material type is linked to account modifiers. In transaction OMWD check if valuation area is linked to the chart of account and valuation grouping code.
SAP MOVEMENT TYPE TO TRANSACTION KEY DETERMINATION CODE
In transaction OMWM check if valuation grouping code is active. In transaction OX14 check if valuation area is the plant. Make sure that there is not any missing account number.ī) Check all account determination customizing settings Then, you will see the account numbers and the possible account assignment.
double click on the option which defines the goods movement you are trying to post. insert the affected plant, material and movement type you are trying to post. click on 'cancel' button, if a pop up window is presented you. A) Execute an account assignment simulation
SAP MOVEMENT TYPE TO TRANSACTION KEY DETERMINATION HOW TO
The purpose of this page is explain how to analyze error 'M8147 - Account Determination for entry & not possible'.