1.PR is the request created by user dept. for a consumable matl.

it can also be created automatically

Where PO is the legal doc which binds company and supplier, based on PO only he will supply matl and
get payment.Po can be created wrto pr

2.Bill of matl ( BOM ) is the structure will tell us the details of child items reqd to create a final product, it
is mainly used by purchasing , and shop floor and controlled by Engg. dept Toced is CS01/CS02?CS03

3.ME23 is used old tcode to display a PO where as ME23N is enjoy tcode started from SAPR/3 4.6 C
onwards

ME23n is combination of all screens u of me23 u need to go one by one screen like ME23

4.MIGo is the evidance for the goods supplied by the supplier, and it will create matl. doc no and
account docc. o based on configuration

MiRo is the TCode used to check and post the invoice supplied by the supplier,

Base for MIRo is PO/migo doc no

After miro FI people will run for payment based on payment term with supplier

Transaction Keys in Materials Management

Materials Management
Also known as process keys, the Transaction Keys are pre-defined in the system to enable transaction
postings in Inventory Management and Accounting (Invoice Verification). For each of the movement types
in MM, there is a value string that stores these possible transactions.
The pre-defined transaction keys are:
BSX (used in Inventory Postings)
WRX (used in GR/IR Clearing Postings)
PRD (used to post Cost/Price differences)
UMB (used to post Revenue/Expenses from revaluation)
GBB (used in offsetting entries in Stock postings)
BSX, WRX, and PRD are examples of transaction keys that are relevant for a GR with reference to a
purchase order for a material with standard price control. The transaction key UMB is used when the
standard price has changed and the movement is posted to a previous period. Likewise,
GBB is used to identify the GL account to post to as the offsetting entry to the stock account (when not
referencing a purchase order) such as miscellaneous goods receipts, goods issues for sales orders with
no account assignment, and scrapping.

Posting Keys
What are posting Keys and How are they used while making postings?

Posting Keys are defined at Client Level.

Posting keys determine whether a line item is a debit or credit as well as the possible field status for the
transaction. In this context, it is essential to understand the factors that determine the field status of a
transaction. The field status within a FI document is controlled by Accout Type, field status of Posting Key
and the field status of the G/L account.

Modifying the SAP delivered Posting keys are not recommended. if a posting key is to be modified the
best possible action is to copy the posting key that needs to be modified and then modify the copy. we
can define the posting keys using the transaction OB41.

It also determines the account type to which the debit or credit is to be made and whether it is Spl G/L
transaction. If it is a Spl G/L transaction, then the field for Spl G/L indicator becomes required entry.

Difference Between Posting Key and Field Status Group

What is the difference among Account group, Posting key and Field status group in terms field
status?
Account group (in GL accounting)defines:
a. no. ranges of the gl account numbers
b. field status of the GL account master data in the company code segment.(which fields to appear when
you create a gl account) (to controldouble click on your GL account group in Screen transaction code
OBD4)
Posting key defines:
a. whether the line item is a debit or credit
b. to which type of account the amount should be posted to(ex: when you use posting key 40, you will be
able to post to gl accounts. When you use Posting key 01, you will be only able to post to customer
account.
c. document screen layout during posting of a document. (which feilds to appear in a documentdouble
click on the posting key and select field status and make the entries as required /optional etc)
Field status group defines:
Document screen layout during posting of a document. (which feilds to appear in a documentdouble
click on the field status group and select fields and make the entries as required /optional etc)
LOGIC: you assign field status variant to the company code, FSV is a bundle of field status groups.
ex: in FSG G001 you have made the text as required entryyou assigned the field status group g001 to
cash account..so when you use cash account and try to post a document it will definitely prompt you to
enter the text (text made as required.)
Both FSG and PK control the same feilds in a document.There is no dominance between FSG and
Posting keys..but we should know the allowed combinations.
If text is made required in PK and suppressed in FSG..the system will issue a error msg..Rules for PK
and FSG.is set incorrectli for SGTXT field.
Permissable combinations:
Pk R/S O/S R/o R S O
FSG S/R S/O o/r R S O
Result e SD RD NP NP NP

R= required
s= suppressed
e=error
SD= Suppressed dominates
Rd= required dominates
np=no problem.

Regards

Aravind

The system always follows the priority rule Hide (Suppressed)

Display
Required
Optional

Only Hide and Required combination gives error. In all other cases the dominace is always in the above
sequence. If you want to take the FSG dominace, set all fields in posting key as optional.

Difference Between Parking and Holding of Documents

Hold Document, Park Document
The Parking of a Document in SAP is one of the two preliminary postings (the other being the
Holding of documents) in the system and refers to the storing of incomplete documents in the system.
These documents can later be called on for completion and posting. While parking a document, the
system does not carry out the mandatory validity checking. The system does not also carry out any
automatic postings (such as creating tax line items) or balance checks. As a result, the transaction
figures (account balances) are not updated. This is true in the case of all financial transactions except in
the area of TR-CM (Cash management) where parked documents will update the transactions.

The parking of documents can be used to park data relating to customers, vendors, or assets
(acquisition only). When a cross-Company Code document is parked, only one document is created in
the initial Company Code; when this parked document is posted all other documents relevant for all other
Company Codes will also be created. However, it is to be noted that substitution functionality cannot be
used with document parking, as substitution is activated only on transaction processing.

The added advantage is that a document parked by an accounting clerk can be called on for completion
by someone else. The parked documents can be displayed individually or as a list from where the
required document can be selected for completion and posting. The number of the parked document is
transferred to the posted document. The original parked document, if necessary, can be displayed even
after it has been posted to.

During a transaction when you do not have a piece of required information, you can Hold the Document
and complete it later. As in the case of parked documents, here also the document does not update the
transaction figures.

Materials Management (MM) Integration in Other Modules

Materials Management
Integration in Financial Accounting

Purchasing maintains data on the vendors that are defined in the system jointly with Finance. Information
on each vendor is stored in a vendor master record that contains both accounting and procurement
information. The vendor master record represents the creditor account in Finance.

Integration in Sales and Distribution

Within the framework of materials planning and control, a requirement that has arisen in the Sales area
can be passed on to purchasing. In addition, when a requisition is created, it can be directly assigned to a
sales order. As soon as you enter a sales order, you can initiate a dynamic availability check of on hand
stock.
Integration in Production Planning

Materials Management is closely linked to Production Planning through inventory needs. Inventory
management is responsible for staging of components required for production.
 Integration in Plant Maintenance

Materials Management and Plant Maintenance are linked by Bills of Materials. It is possible to post a
good receipt with reference to an equipment BOM. It is also possible to withdraw part for maintenance
orders. Serial numbers are activated in Materials Management but used within the Plant Maintenance
system.

Integration in Logistics

The inventory management system can be extended by the Warehouse Management System (WMS),
which manages storage bins in complex warehouse structures. While Inventory Management manages
the stock quantity and value, WMS handles and monitors storage.