Professional Documents
Culture Documents
There are many transactions in Material Management (MM) that relevant for Accounting. These
transactions must be recorded in accounting documents that contain the postings made to the G/L
accounts in Financial Accounting (FI). The mostly used MM transactions that relevant for FI can be
seen at Accounting Journals of SAP Material Management (MM) Transactions.
For those transactions, as far as possible, the SAP R/3 System should determine automatically the
G/L account numbers that are involved in the accounting journal. By doing so, we can minimize the
inputs and error possibilities made by MM end-users who perform the transactions as they don’t
determine the G/L account numbers.
We can do this by Automatic Account Determination process in MM configuration (T-code: SPRO).
The automatic account determination process must be done together with Accounting Department.
The influencing factors that determine how SAP choose the G/L account numbers that are involved
in the accounting journal for MM transactions are:
A valuation grouping code consists of a group of valuation areas that can have same
account determination in a specific chart of account. It is a tool that enables us to
configure the automatic account determination with a minimum of effort.
If we activate the valuation grouping code in configuration process, we have to assign a
valuation grouping code to each valuation area.
SAP Screenshots of How to define valuation grouping code (T-code: SPRO/OMWD):
SPRO menu: IMG - Materials Management-Valuation and Account Assignment -
Account Determination - Account Determination Without Wizard - Group Together
Valuation Areas.
reserved
By activating and using the valuation grouping code, we don’t have to configure account
determination for each valuation area (that is a plant or company code) if we don’t want
to differentiate it for each valuation area. If we want the automatic account determination
within a chart of accounts runs differently for valuation areas, we can assign different
valuation grouping codes to these valuation areas.
We must define the automatic account determination individually for every valuation
grouping code within a chart of accounts. It applies to all valuation areas which are
assigned to this valuation grouping code.
For example, if we want to differentiate the account determination for a group of two
plants with another group of other three plants in a company code (where the valuation
level is plant), we can assign a valuation grouping code for the group of two plants and
another valuation grouping code for the group of other three plants. By doing so, we just
have to configure the account determination for the two valuation grouping codes, no
need for five valuation areas (plants).
SAP R/3 determines the valuation area and the valuation grouping code affected by MM
transaction from the company code or plant entered by user when performs a
transaction.
reserved
The above image is © SAP AG 2010. All
rights reserved
When entering the goods movement, the user does not have to enter a G/L account, since the SAP
R/3 System automatically finds the accounts to which postings are to be made using the influence
factors as explain above.
SAP Screenshots of how to configure automatic posting (T-code: SPRO/OBYC):
• Posting made in the case of goods receipt (GR) to purchase order (PO):
GR/IR Clearing
Inventory account Account
500 500
We need to update the BSX transaction key (Inventory posting) with the GL code Inventory account.
SPRO menu:
IMG - Materials Management-Valuation and Account Assignment - Account Determination - Account
Determination Without Wizard - Configure Automatic Posting.
Enter Chart of Account which we want to configure its account determination, then enter the G/L
account affected by the transaction as below:
The above image is © SAP AG 2010. All rights reserved
We also need to update the WRX transaction key with the GL code GR/IR Clearing account.
Enter Chart of Account which we want to configure its account determination, then enter the G/L
account affected by the transaction as below:
Material consumption
Inventory account expense account
500 500
We have configured the inventory posting transaction in the previous section (GR to PO).
Now, we have to configure transaction key GBB. GBB key is used for various offsetting posting
entries. Within GBB transaction there are various account grouping (general modification). In this
case we need to update general modification VBR with the material consumption expense account.
What's Next?
See all articles list at TABLE OF CONTENTS
Can't find what you're looking for? Try search here:
Top of Form
Bottom of Form
Posted by Rizki
Share your opinions or suggestions by posting a comment below.
13 comments:
Yuvi said...
This is Gr8 Document who ever created it!! Thanks a Lot
September 18, 2008 10:56 PM
mk said...
I have one question though (at the end of the following restatements)
In all screen shots shown connecting the three/four attributes above with a
GL account do not include the Account Category Reference. quote "The
relationship between valuation classes and material types is established by
the account category reference."
Anonymous said...
Thanks for sharing this, Great blog.
a Blogger said...
Yes, you can post a goods receipt to expense account by choosing "K" in
"account assignment" field of the Purchase Order (PO). You can read this
post to know more about it.
March 11, 2009 7:41 AM
Anonymous said...
I think the A/c Cat.Ref. is only used to establish many to many relationship
between Material Types and Valuation Classes.Consider the following
example:
Mat.typeVal.Class
ax
ay
az
bx
by
bz
cx
cy
cz
this way we are is using 3-as, 3-bs, 3-cs as also 3-xs, 3-ys and 3-zs. Not
only that we are using more number of lines but also it is difficult to
understand. Moreover, if we assign mat.types to val. classes as above, it is
against normalization rules of DataBase management bcoz they
creatredundent data.
I feel I should be right.
regards
Anoopjeet.
March 25, 2009 1:58 AM
Anonymous said...
Anonymous said...
Anonymous said...
Regards
sidhartha
September 8, 2010 1:51 AM
Anonymous said...
Anonymous said...
Really nice and well documented...Very good and quick reference for a
quick interview review...Nicely explained.
Nureya
November 21, 2010 2:39 AM
Anonymous said...
Created a new plant and want to assign ValGrpgCode nut my new plant
does not appear in the view list for me to assign ValGrpgCode. it is created
at CoCo level.
Anonymous said...
very nice explained. i did not understand offsetting entries. would you
please give a real time example for this.
February 26, 2011 6:34 AM