Fi MM
Fi MM
Fi MM
Stock of a material owned by a company is an asset to the company. Valuation area defines the
organization level at which materials are valuated.
SAP has provided two options for valuation.
1. Valuation at plant level: All materials are valuated at plant level.
2. Valuation at company code level: All materials in all plants of a company are valuated at
company code level.
Material type:
This defines the type of material.
EG: Raw material, Finished goods etc.
Material type is defined during material master data creation.
Movement type:
This defines the type of material movement from one place to other. Movement type enables the
system to find predefined posting rules determining how the stock and consumption accounts are to be
posted. All possible goods movements are already defined by standard SAP
EG: Movement type 101 refers goods receipt
Movement type is entered while posting stock movement related transactions. Most of the time,
standard SAP automatically derives the movement type based on transaction code.
EG: If we go to MIGO, default movement type 101 is displayed by system.
Valuation class:
Valuation class is defined for the combination of plant and material (In Accounting 1 view of material
master).
Valuation class allows posting of stock values of
1. Materials of same material type to different G/L account (Different valuation class is
assigned in different plants for the same material)
2. Materials of different material type to same G/L account (Same valuation class is assigned to
materials of different material type)
Note: G/L accounts can be defined at valuation class level along with other parameters.
Valuation grouping code:
Valuation grouping code combines the valuation areas having same business properties for the
account determination. This reduces number of entries to be created for automatic account
determination for the stock postings.
EG: Valuation area 1 and 2 are required to be posted to same G/L account, these are grouped to
valuation grouping code ABC and G/L is determined based on valuation grouping code and valuation
class.
Before using valuation grouping code, it needs to be activated in OMWM.
Valuation grouping code is assigned to valuation area in t-code OMWD.
In below example, five valuation areas are assigned to same valuation grouping code.
Account modification/General modification:
This key is used to determine different G/L account for the same kind of goods movement based on
origin and target.
EG: During Goods issue, offsetting G/L is determined from transaction key GBB. If business wants to
post to different G/Ls for goods issue for cost centers (Movement type 201) and good issues to orders
(Movement type 261) for the same material and plant, Account modifier can help here. To understand
this better, let us go to t-code OMWN where we define the transaction key and account modification
for the movement type.
Transaction key which we see in OBYC is determined based on the movement type. When material
document is posted with these movement types, offsetting account is determined from transaction key
GBB based on account modifier and valuation class.
Transaction keys are used to determine general ledger accounts used by the system. Transaction keys
are predefined in the SAP system and cannot be changed.
At the time of the purchase of raw material as a debit to inventory and credit GR/IR. The
configuration setup of transaction BSX (inventory posting) is responsible for the inventory posting
and WRX (GR/IR clearing account) is responsible for GR/IR posting.
By Default, Standard SAP defines account modification keys for below transaction keys. User defined
keys can also be defined and respective account determination settings can be maintained.
For the transaction/event GBB (offsetting entry for inventory posting), the following account
groupings have already been assigned to the relevant movement types:
AUF: for goods receipts for production orders with account assignment
BSA: for initial entries of stock balances
INV: for expense/revenue from inventory differences
VAX: for goods issues for sales orders without account assignment object
VAY: for goods issues for sales orders with account assignment object
VBO: for consumption from stock of material provided to vendor
VBR: for internal goods issues (e.g., for cost center)
VKA: for consumption for sales order without SD
VNG: for scrapping/destruction
VQP: for sampling
ZOB: for goods receipts without purchase orders
ZOF: for goods receipts without production orders
If you also activate account grouping for transaction/event PRD (price differences) when you make
the settings for automatic postings, the following account groupings are already assigned to the
relevant movement types in the standard:
none for goods receipts and invoice receipts for purchase orders
PRF: for goods receipts for production orders
PRA: for goods issues and other goods movements
If you also activate account grouping for transaction/event KON (consignment liabilities) when you
make the settings for automatic postings, the following account groupings are already assigned to the
relevant movement types in the standard:
Dr. COGS (here, COGS entry comes because, delivery may include selling and other expenses)
BSX :
E001 Inventory – RM
E002 Inventory –SFG
E003 Inventory - FG
FR1:
PRD:
Price Differences (Expenses)
WRX:
GBB