1. 1
(1) How to configure the system for automatic conversion of Purchase Requisition to
Purchase Order?
Ensure automatic purchase order field in Material Master (purchasing view) and Vendor
Master is ticked, maintain the source list for respective materials and vendor. Also maintain
correct data at the MRP views. On the MRP run system will generate purchase requisitions for
the following materials.
Using T-code ME59 conversion of purchase requisition to Purchase orders is possible.
(2) What are the configuration for automatic creation and selection of storage locations in
Inventory Management?
Auto creation of storage location in inventory management can be created with respect to the
movement type and plant. Using t-code OBM2/OBM3.
For automatic storage location selection, storage location data can be specified in
procurement storage location field of MRP view in Material master and Issue storage location
field in Bill Of Material.
(3) How to maintain automatic determination of G/L accounts during GR/GI/Transfer
posting?
Automatic account determination of GL account can be maintained using T-code OBYC by
specifying GL code for specific valuation class within the posting key(TE-KEY) maintained for
respective movement types.
(4) What is the difference between selection parameter WE101 and WE103?
To optimize internal processes, you regularly create list displays to inform yourself about
the status of your purchase orders, info records, and other documents in the system.
You are checking the purchase orders issued over the past 24 months. you are primarily
interested in POs against which no goods receipts have been entered.
Choose the scope of list BEST_ALV, so that the list of selected purchase orders is
displayed with ALV Grid Control.
Choose Logistics --> Materials Management --> Purchasing --> Purchase Order --> List
Displays --> For Vendor (ME2L).
Selection parameter : WE101 (open goods receipt)
WE103 means then that SAP considers the GR blocked stock as well as already received
quantity while with WE101 the GR blocked stock is not considered as received.
(5) What is the difference between XD01, XK01 & MK01? Knowing that all the above tx
codes are used to create vendor.
2. 2
There are 3 t-codes by which you can create vendor:
XK01 is for centrally creating vendor where all data are included.
MK01 is for purchasing vendor.
FK01 is for accounting vendor or vendor with accounting details.
(6) Can any one tell me what is MM closing and what is FI closing? How can I know if
period is closed?
MM closing means that you can not post materials document. In MM area you have two
open periods current and previous.
If you do not set other in MMRV - here you can check which are the open MM periods for
company code. If you check Allow posting to previous period - it will forbid MM posting in
previous period.
FI open period (ob52) allow to post FI documents. As I know you can allow postings for
some accounts - for example forbid material accounts for previous period in order to prevent
MM posting until you finish all FI documents.
(7) How to add an attachment to a Purchase Order in SAP?
You can attach manually any document to PO without using Document Management
System ( DMS )
But you cannot attach document while you create PO in T/Code ME21N
Save you PO ( ME21N ) and again open with change ( ME22N ) then you can attach document
through Service for Object button. Service for Object button available down side of Command
screen ( in your PO screen ME22N )
Click your Service Object button -> Create -> Create attachment
then select your window directory ( which file you need to attach) select your file Now your
system shows message Service "Create attachment" is started.
Save again your PO. You can see (open) your attachment in same field ( Service for Object )
select and Create and check attachment list. You can attach as many document in your PO.
Note: This is only information for internal or you can print separately this document for sending
to vendor ( fax ) System will not print automatically along PO print out.
(8) What is the difference between Blanket Purchase Order and the Framework Order?
In general the Blanket POs are used for consumable materials such as Xerorx papers with a short
text (does not need to have Master Record) with Item Category ' B' i.e.limit, where in the PO
validity period as well as the limits are to be mentioned for the simplicity of procurement.The
doc type is 'FO' (Framework Order).
The GR or Service Entry for the PO are not necessary in case of Blanket POs as well as one need
not to mention the account assignment category during creation of PO it can be 'U'-unknown &
can be changed at the time of IR.
3. 3
(9) Auto P.O.: In MMR & Vendor Master Record (Control data) I have checked 'Auto PO'....I have
created the Purchase Req for the Material.....Now I want to know how the automatic PO will
come into force...I mean what steps to do after creating PReq.
For Auto PO , yo should proceed as follows:
Auto P.O.: In MMR & Vendor Master Record - checked(MM02/XK02)
maintain Source List & select the indicator for source list record as MRP relevent.(ME01)
If more than one source list records are generated, make one of them as fixed.
Run MRP , the PR's generated will be preassigned with the source of supply.(MD01)
Enter T Code ME59 for automatically creating PO's from PR's.
(10) Source List: I have checked 'Source List' In Purchasing view of MMR...Have two vendors for
this material for which source list is also maintained(ME01)....While creating PO..the system takes by
default the first vendor....I tried to assign the second vendor (made sure that validity period are in
range)..but couldn't do so...Can you suggest how the system will tell me to select one of the vendor I
want to assign to the PO.
Check if the assigned Source in PR is not fixed in Source List.
Check if the info record for source not assigned, is having valid conditions.
(11) Why system giving me only warning message instead of error message when I am
trying to make GR with a material which already tick for deletion flag. Is there any
configuration mistake?
Through OMCQ , set message no M7 430 for error.
(12) Is it possible to maintain the same material master with same code in all plants in a
company. Our client is using same materials in all their four plants?
Material numbers are always maintained at Company code level. If you look at the
Material master data, some data is maintained at Company code level, some at Plant level and
some at Storage location level. If you have all the 4 plants attached to one company code, they
should have the same material number. What you need to do is to extend the material to all the 4
plants if thats your requirement. Also, if you have your valuation area as your Plant, then you
have the flexibility to maintain Plant specific pricing for the same material.
You can use MM01 T code to copy material from old plant to new plant. But check for the
required details in your new plant and make changes accordingly.
(13) Where we do the configuration for the cost centre allocation, because whenever we
GR a material, accounting document is created for that particular material. How that
particular material go in to the particular accounting (G/L account)
4. 4
In T.code : OBYC -- Automatic Postings.
for Inventory Posting Transaction Key is : BSX
for Off Setting entries like Goods issue, initial stock......Trans Key is : GBB
Based on the Movement types, Valuation class it will be assigned to a G/L account.
You can refer the configuration in T.code : OBYC
(14) Could anyone can explain complete configuration of pricing procedure &
application.
The Basic thing is Condition Technique. In which there are 1.Access Sequence 2. Condition
Record 3. Condition Type 4. Condition Table.
Access Sequence access a Condition Record of a Condition Type in a Condition Table is a
Condition Technique. This is a simple logic
Here the Condition Type is very important like PB00, PBXX,RA01 etc.
In the background every Condition Type has its own definition means the purpose of the
Condition Type like, is it for Pricing or Percentage, Quantity base, Accrual Fields etc is to be
defined to work this functions. Normally we use the existing ones without any risk. But some
cases, we have to Create a New Condition Types as per the organization requirement.
The Pricing Schema is useful to minimize condition types while mention prices for Vendor on
the basis of Pricing Schema which we defined according to organization requirement.
The Pricing Schema means the calculations procedure of Condition Type.
Ex. RA01 - Discount % is calculated on PB00 - Gross Price means
RA01 is based on PB00 like that we have to define in the Pricing Schema
which makes easy to use in real time.
Here PB00 has the Access Sequence - 0002.
But RA01 does not have the Access Sequence. Why because it is a dependent on PB00. But both
are Condition Types.
(15) In the system, by default some standard Scheme will be there at Vendor Schema Group
in the Vendor Master Screen means the standard one is assigned which is very lengthy
which may fulfill our requirement. But some cases which may not fulfill our requirement, in
such we have to define.
For the configuration, I may not able to explain properly through here but will give some idea.
Configuration: SPRO - IMG - Material Management - Purchasing - Conditions - Define Price
Determination Process:
1. Define Access Sequence
2. Define Condition Type
3. Define Calculation Schema:- Here you have to define the Schema - Define Schema group
5. 5
1. Define Schema Group vendor
2. Define Pricing Schema group
3. Schema group for Purchase Organization
4. Assign Schema group to Purchase Organization - Define Schema determination
1.define calculation schema for Standard purchase organization
After completion of the Schema Group, we have to assign it to Vendors.
Then whenever we use any transaction with this Vendor, the concerned Schema will work as
configured by us.
The Pricing in MM is vast because each Condition have its own importance and each Access
Sequence have its own importance. So you need not bother about this. First you learn how to
define the Calculation Schema through the above.