Release Strategy - interview FAQs

1. Why can I modify a purchase requisition although I set the changeability of the release
indicator to '1' ('Cannot be changed')?
The purchase requisition is not modifiable via a purchasing transaction like ME52 or ME52N. But it is
possible to change the purchase requisition from any other external application like sales order,
planned order, maintenance order or network. The Changeability functionality only concerns the
purchasing transactions. This is intended and a new release strategy determination takes place if
there is a modification of the data in the external application.
2. Is it possible to modify the overall release status (V_T161-GSFRG) of the document type for
a purchase requisition ? Why is the database table field Overall release of purchase
requisitions (EBAN-GSFRG) set as overall whereas the item is subject to an item-wise release
strategy ?
SAP does not recommend to modify the overall release status (V_T161-GSFRG) of the document
type for a purchase requisition (customizing - transaction OMEB). The risk is to create
inconsistencies in database table EBAN. If a purchase requisition is subject to an overall release
strategy and you change the document type from overall to item-wise release, the system can
determine an item-wise release strategy when you modify one item with ME52. This item is now
subject to a single release strategy when all other items are still subject to the former overall release
strategy. And the overall release field (EBAN-GSFRG) is still set as overall for all items. If you do the
same change with ME52N, the items not modified are no longer subject to the former overall release
strategy and EBAN-GSFRG is set as item-wise for all items. But the requisition processing state
(EBAN-BANPR) remains in status release completed (05) for the items not modified.
3. Why is the release strategy not reset ?
A reset of the release strategy only takes place if
 the changeability of the release indicator is set to '4' in case of a purchase requisition and '4' or '6' in
case of another purchasing document (purchase order, request for quotation, contract, scheduling
agreement),
 the document is still subject to the previous release strategy,
 the new TOTAL NET ORDER VALUE is higher than the old one.
The total net order value is linked to CEKKO-GNETW for a purchase order, CEBAN-GSWRT for a
purchase requisition item-wise release and CEBAN-GFWRT for a purchase requisition overall
release. If you have maintained a Tolerance for value changes during release (V_161S-TLFAE), the
release strategy is reset when the value of the document is higher than the percentage you have
specified and if the document is still subject to the previous release strategy.
Read Here for more SAP MM Transaction Codes.
4. Why is the release strategy not determined ?
Please check the following points:
 You can not use Release without classification and Release with classification. If there is an entry
present in Release Group table (T16FG-FRGOT) only release with classification can be used.
 If you use version management, the determination of the release strategy starts when the version is
completed.
You complete a version by setting the "version completed" indicator in the version tab.
 Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy
characteristics should be entered with leading zeros. This is true for the other structures as well
(CEKKO and CESSR). See 52225.
 For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant
and Material Group will be aggregated to header level. For example you use Plant as one of your
characteristics. If all items do not belong to the same plant then the relase strategy will not be found
unless you have maintained a blank value as one of your allowed values for the characteristic Plant.
If all items belong to the same plant then that plant is aggregated to the header; if one or more is
different then a blank is aggregated to the header. See 47089.
 If you use a release user exit to derive the communication structure the following statements must
be in the code (see 371667):
 E_CEBAN = I_CEBAN (EXIT_SAPLEBND_001 and EXIT_SAPBELND_004)
 E_CEKKO = I_CEKKO (EXIT_SAPLEBND_002)
5. Why is there no release strategy for the quotations (ME47)?
The release strategy determination takes only place when you modify the request of quotation via
ME42.
6. Why does the system not display the purchase requisition I double click on with ME55
(scope of list F) ?
If you have previously selected one or several documents the program determines the first
document selected and not necessary the one you double click on. The purchase requisitions will be
displayed one after the other and to do so each purchase requisition displayed is deselected. On the
other hand, if no document is marked, the system displays the document you double click on
because the program selects the document according to the position of the cursor and not the mark.
Read Here for SAP MM Forums.
7. Why can I not select several purchase requisitions with ME55 and scope of list ALV grid?
As from release 470, you can use scope of list ALV grid with ME55. This constitutes a new design
and was developed in order to achieve accessibility requirements. It was not the aim to guarantee
absolute identical functioning as with the other scopes. The behaviour is more user-friendly than with
the old scope of list. With scope of list ALV grid it is no longer possible to select several purchase
requisitions and release them all together. This was done on purpose and the user should release
the documents without the checkbox selection.
8. Why is the database table ekko not updated when I use transaction ME28 to release
purchase orders ?
First check that the transaction/event key (vorga) for ME28 in pooled table T160 (SAP Transaction
Control, Purchasing) is EF. Then check if a committed work in a user-exit does not interfere with
logic of transaction ME28.
9. What authority check is performed with release transactions ME29N and ME54N ?
With the Release Purchase Order (ME29N) and Release Purchase Requisition (ME54N)
transactions, an AUTHORIZED person can display/change the current version of the document and
effect release with his release codes. An authority check is performed on object M_EINK_FRG for
transaction ME29N and object M_BANF_FRG for transaction ME54N. With the authorization object
M_EINK_FRG, you can determine which purchasing documents the user may release via the
release group (FRGGR) and which release codes (FRGCO) he may use when doing so. The
authorization object M_BANF_FRG enables you to restrict the release of purchase requisitions via
the release code (FRGCD).
10. Why do I have to switch to change mode in order to release with transaction ME54N ?
When you select with ME54N a purchase requisition that cannot be released the system switches to
display mode and if then you select a releasable purchase requisition the system keeps the display
mode due to technical reasons. Consequently, you have to switch to Change mode by clicking on
the Change/Display button (F7).
11. Is it possible to create a purchase order with reference to a purchase requisition not yet
released? Is it possible to create a purchase order with reference to a request of quotation
not yet released ?
It is not possible to create a purchase order if the referenced purchase requisition is not released.
But the system allows you to put the purchase order on hold and then release the purchase
requisition. On the other hand, you can create a purchase order with reference to an unreleased
request of quotation.
Read Next What is SAP MM
12. Is it possible to cancel a release strategy when the purchase order has been printed out?
With ME29N you cannot cancel a release strategy once the document has been printed out. This
behaviour constitutes a new design. Regarding ME28 it has been decided to keep the old behaviour
and you can cancel the release if there is at least one message type which has not been printed out.
13. How is the currency converted?
The header currency is converted to local currency (company code currency) and then the local
currency is converted to the characteristic currency.
14. Can I use a blank characteristic so that this characteristic will not be considered during
the release strategy determination?
Unfortunately, there is no mechanism like entering a blank or * in order to make classification
understand this characteristic is not relevant. The characteristic and its values will always been
taken into consideration. In case you use a 'non-aggregated' field in your release strategy you need
to enter all possible values for the corresponding characteristic (as a range - just in case of numeric
characteristics). Example: You use item-wise release strategy for purchase requisitions and the
plant is used in the release strategy (characteristic CEBAN-WERKS). Release strategy
determination will be processed item by item. There will always be just one value for the plant (from
the current item), multiple values and thus aggregation is not possible. In this case you have to
enter all possible values for the characteristic CEBAN-WERKS.
In case you use an 'aggregated' field in your release strategy (which is possible for overall release
strategy for PRs and release strategy for POs) and multiple values are used for that field on a
purchasing document, you can use a blank value for the corresponding characteristic if you'd like the
release strategy be applied. Example: You use release strategy for a PO and the plant is one of the
relevant fields (characteristic CEKKO-WERKS). You enter a first PO item with plant 0001 and a
second item with plant 0002. Since there are multiple values for the plant the system will
'aggregate' to blank value and use blank value for searching for a release strategy. Since you have
maintained a blank value for characteristic CEKKO-WERKS the system will find the corresponding
release strategy. In this case please pay attention to 732566. It causes an error in case blank values
are used for release strategies. Even when the long text just talks about process orders the impact
of the side effect is more general. Please take care 754178 is implemented, it corrects 732566.
15. Why can I not input more that 999 entries for a characteristic like costcenter (KOSTL) ?
The cost center field ( CEBAN-KOSTL) is defined as a CHAR field and also the reference
characteristic for this field has a CHAR format. Therefore you can only assign less than 999 values
(see 534226).
16. Why is there no release strategy determination when a program changes in the
background a purchasing document which corresponds to the classification of a release
strategy?
This is the system design that a release strategy determination can only be triggered by a user
action and not by changes made in the background process. If you create a document (e.g. PO,
Contract, etc), the determination of the release strategy takes place only in case of a user event like
checking or saving the document.
Top 26 Material Master Interview Questions and Answers for
Experienced

Q1: How can I extend all material to a new plant?

Ans: The SAP program - RMDATIND is used to create /update material master record.
Q2: How can we delete materials permanently from Material master?
Ans: Use transaction MM70 - Material Master->Other->Reorganization->Material->Choose.
Build variant with selection range of material master records to be selected for deletion and maintain
run parameters. Execute.
Use transaction MM71 - Material Master-> other-> Reorganization->Material->Reorganization
Build a second variant
Maintain run parameters and execute.
It is also important to remove the records manually from info record, POs, PRs, reservation etc for
successful deletion of the material.
Q3: SAP only provides moving average value for current, previous period, and previous year.
SAP does not provide transactions/reports that will provide moving average value for a given
date. How can I report moving average price for material number 10000000 at plant 0001 on
July 4, 1998?
Ans: Try any of these solutions:
1. Change the updating level of the structure (S031) to "daily". In LIS the total value and the total
stock are available. Divide value by the stock. It is possible to calculate this dynamically when the
analysis is run and to display the result.
2. Create your own structure in LIS and populate it by copying the Moving Average Price from the
material master every time there is a transaction. You will have data on those days when there was
a transaction.
Q4: We have defined all the variables for the materials. However, when I attempt to use
Material Matchcode object MAT1, I get the response "No possible entries found". Why?
Ans: Matchcode i.d. "B", "Material by bill of material" has a selection condition for field STLNR NE '
'. STLNR is the BOM number associated with a material in table MAST. Hence the message - "no
possible entries..." pops up if there are no bills of materials associated with your material numbers.
You get the matchcodes as long as the material referred by you has BOM number associated with it.
Q5: The matchcode object selection defaults to matchcode ID "B". I would like to change to M
"Material by Description" What is the solution?
Ans: Press the pull down arrow on the material number field and matchcode "B" is displayed, press
F5 double-click matchcode i.d. "M", then press F6. This will set matchcode "M" as the default.
Read Here for SAP MM Tutorials.
Q6: We have one material master: X and the unit of measure is 'pcs' and two serial number:
A,B
For this material we make two Pos
First PO calls material X, 1 pcs price 100 (will use serial number A)
Second PO calls material X, 1 pcs price 250 (will use serial number B)
Goods Receipt is done and by filling serial number for the fist PO with A and the second PO
with B.
We want to transfer material X serial number A to another plant and want the valuation of this
material as 100. How can we do it ?
Ans: Use "split valuation". Stocks may be received into separate storage locations. Transfer stocks
may be done from a storage location/plant to another storage location/plant.
Q7: We want to change the calculation of Moving Average Price. We know that the same is in
MBEW-VERPR and two transactions to consider - MRHR, MB01. Is there a transaction to
change MAV or all the places it is needed?
Ans: Any Goods receipt or issue (in case of split valuated material) changes Moving Average price
depending upon the valuation type which is used when posting the goods issue. You have to go
through all the transactions involving those!
For Example:
Material X is using split valuation by origin:
Malaysia: MAV 60 USD - total stock 100 units
India: MAV 50 USD - total stock 200 units
Total stock 300 units MAV 53.33
Here, goods issues will also affect the global MAV, despite not changing MAV from origin country.
Q8: What is the use of configurable material?
Ans: Configurable material is useful if you have a large number of combination of parts that go into a
product. It means different permutations and combinations of the parts for the same material. If you
maintain a unique material code for each combination, you require a large number of material
numbers. KMAT may be used in such a case where you maintain just one generic product code. A
super Bill of material (BOM) is maintained for such a material consisting of all possible alternatives.
A routing is also maintained consisting of all possible operations that could be used. Typically
configurable material is used in Made To Order (MTO) environment. However frequently ordered
configurations may be planned with a material variant which needs to have a material master record.
Thus Material variants may have stock and value. Depending upon characteristic values chosen at
sales order entry Sales Order BOM is created. Routing operations are also chosen depending upon
which BOM components are assigned to them.
Q9: Will Source List automatically appear in Material Master as default if maintained at plant
level using OME5?
Ans1: If you have maintained source list requirement in OME5 and have not maintained the source
list for the material, Po can not be released. You are required to maintain source list for all materials
in the plant where the indicator is set if you maintain source list at the plant level. Else you can make
use of info record to do so automatically.
Q10: We have One company with a plant and another company with a sales organization.
Which is the better option between these - PO or Stock Transfer Order?
Ans: Cross company Stock Transport Orders can be done.
1. Configure using transaction OMGN.
2. Depending upon the sending and receiving plants, maintain sales organization and customer data
in customizing.
3. Maintain the supplying plant as a vendor and attach the plant to the vendor in the Vendor Master.
4. The material type has to be HALB or HAWA.
5. Ensure that the company with sales Organization has a plant to take care of stocking.
6. The PO used is NB and not Stock Transfer PO.
7. Configure SD for inter-company billing to enable picking up the pricing procedure for billing.
8. Carry Out delivery through the process delivery due list and billing through the process billing due
list.
Q11: We can make a field mandatory. We want to make a default value to a Particular field in
the Material Master. Say, We want that the period indicator in the MRP2 view as "P". What is
the best way?
A: Use transaction variant. Transaction SHD0 and then Transaction SE93.
Read Here for more SAP MM Transaction Codes.
Q12: We could create two Purchase Orders for full amount & quantity out of one Purchase
Requisition. two goods receipts and invoice receipts on their respective POs. How can We
avoid this kind of double transactions?
Ans: For PO's:
Define buyers' functional authorizations in the customizing for purchasing, there you can unmark PO
w/o reference allowed. Buyer's functional authorization, say 'ABC' can be created using transaction
code OMET. Assign this 'abc' to a particular user by using parameter ID "EFB" (trans su52).
For GR and IR:
Make the warning message as an error in customising of messages under Inventory Management or
Invoice Verification, respectively.
For IR:
Mark the indicator in the vendor master for checking of double invoices.
Q13: Is there a transaction or Report available to see the scrapped quantity of a particular
material where goods issue is done using movement type 551?
Ans: If you want to manage the inventory of Scrap, create another material ID for scrap and receive
as the by-product. When you issue goods against Movement type 551, the material is removed from
inventory by writing it off the books.
Q14: We want to run multi-plant planning for 3 plants A, B and C, where the requirements of
plant A and B are transferred to Plant C. Plant C is expected to consolidate the requirement
and convert these requirements into requisitions and then into POs. When we do a planning
at Plant C, we are unable to see the requirements for plant A and plant B. We are using the
special procurement key 40 for all the materials being planned. Can we do multi-plant
planning at plant level as well as a Material level?
Ans: The special procurement key is defined for the Planning plant and does not contain supplying
plant. This key may be copied to create a new key. Then enter the supplying plant in it. Use this key
in material master. Now all the requirements of plant A and B will be called in planning plant C.
Q15: We are doing goods receipt with PO. How can we find whether there is any USER EXIT
available which is triggered before the document is saved?
Ans: The User exit in your case could be MB_CF001 and use transaction SMOD to look for user
exits
Q16: In MM pricing schema, there are a list of selection from A to M and 1 to 8. How can we
make use of the condition sub-total field?
Ans: Subtotal field on Pricing schema are useful in a number of cases.
For Ex: 1 is Carry over value to KOMP-KZWI1.
7 is used for deciding on the basis for which to calculate Rebate subsequent settlement.
S is used for the final net inclusive, cash discount, rebates and any other conditions including
statistical
For reporting in LIS
Used in the layout for printing.
Get More Questions and Answers with Explanation atSAP Material Management Forums.
Q17: There are some complaints that though the data is correct in User Info (USR03),
Purchase order is being printed with wrong information. For Example: telephone Number.
Where can I find correct Purchase group Information?
Ans: Purchase group information is in table T024.
Q18: What are the tables generally used for MM Queries?
Ans: Some tables are listed below. However, a host of others can be seen using Technical help
after activating the query
Purchasing Tables
Purchase Requisitions
Purchase Order
CEBAN
EKPO
Material Master Description
Material master
Material master - segment C
Material to BOM Link
Material Valuation MAKT
MARA
MARC
MAST
MBEW
BOM Tables
BOM Header
BOM item
BOM Sub-item
STKO
STPO
STPU
Purchase Group information
T024
MRP Tables
MRP Header
MRP Table
MDKP
MDTB
Q19: What are the typical transaction codes for IM & PO?
Ans: Transaction codes can be checked using menu path System->Service->Status.
IM transaction codes start with MBxx.
PO transaction codes start with Mexx.
Q20: During a good issue for an inventory product (HIBE), we assign by the automatic
account assignment a GL account in relation to the valuation class of the product. However,
we would like to change this GL account automatically depending on the cost center
requested the product for consumption. How can we do it?
Ans: Try OKB9 where you can find the cost center account assignment table. However, this GL
account becomes defaulted for all the products used by the cost center.
Note that GBB/VBR process key governs the credit posting for cost center issues in Automatic
Account Assignment (AAA).
If you want change Account assignment for exception materials, try the following options:
1.For all exception, materials define a new valuation class and setup all inventory posting accounts
for this exception valuation class. Here the AAA automatically picks up the G/L a/c.
2.In the inventory screen allow the user to enter G/L a/c manually. Configure the IMG in inventory so
that user account overrides the AAA determined account
3. Define a new movement type by copying 201 to say 901. Then in Valuation IMG define a
transaction key for 901 under account grouping for movement. types. Define G/L accounts for this
new transaction key. For exception issues, users have to use this new movement type.
Q21: We have specified in MRP for requisitions to be created. The document type of the
requisitions created is always the type NB. How can we change the document type created?
Ans: Refer transaction 'OMH5'. Define the document type required that you want in ME51.
Q22: We have created a workflow for the purchase requisition approval process. When the
event (BUS2009, RELEASESTEPCREATED) is triggered to kick off WF, the following error
message is appearing:
Work item XXXXXX: Linkage to object BUS2009 event REJECTED cannot be written.
Diagnosis: The instance linkage between the required event and the specified work item
cannot be entered in the type linkage table of the event manager.
The reason is either a database error or an error when generating internal linkage numbers.
What to do: Check the number range object 'SWE_EVTID' How can this be fixed?
Ans: 1. Must update the number range for events object SWE_EVTID with transaction SNRO.
Ex: SWE_EVTID: 01 000000000001 999999999999.
2. SWE2, double click on BUS2009 entries, check GLOBAL field, ENABLE field will be updated
3. Error when executing the Workflow. Transaction code SWLE not defined. Apply OSS note 43986
to fix.
Q23: How can we make a Taxcode as default on purchase order item detail screen?
Ans: 1. Use condition type NAVS with access sequence 0003 to default the taxcode in the purchase
order item using conditions.
2: Go to IMG.
Materials Management -> Purchasing -> Purchasing order processing ->define screen layout at document
level.
Search for the transaction ME21.Double click on ME21. Then search for TaxCode. It is advisable to
configure also the info record. The tax code should be a required entry, and whatever you specify
here will be the default value in the Purchase order.
Materials Management -> Purchasing -> Purchasing info record -> define screen layout.
When you get here you search for the transaction ME12, double click here; search for Input VAT
indicator.
Q24: We have defined EA (each) as 0 decimal place in configuration. But transaction ME2L
shows this field with three decimal places. How can I change to an actual number of decimal
places?
Ans: The quantity (MENGE) in that report must have been set for 3 decimal places.
Table EKPO may have to be corrected accordingly.
Q25: We have created a new movement type and assigned to a schedule line. When goods
issue is posted, message - movement type zzz is not allowed for customer goods movement?
Why?
Ans: Use transaction code OMJJ and check the "Allowed Transactions" for customizing movement
types.
Q26: Is it possible to generate packing list for goods issued in MM?
Ans: SD & Ware House management have the functionality of picking/Packing lists.
Top 37 Price Determination in Purchasing Interview Questions and
Answers
Q1:Problems occur during price determination in transaction ME21N or ME22N.
Implement 381391 and the related s that it contains, unless - depending on your Support Package
level - they have already been implemented.
Q2: What is the difference between master conditions (time-dependent conditions) and
document conditions?
The conditions in the info record and in the contract are master conditions. The differentiation for
quotations and scheduling agreements is made through the document type (indicator "Time-dep.
conditions"). The master conditions are restricted to a specific validity period, they have the
characteristics of master data, and they are usually valid over a long period of time. Master
conditions that refer to more general price agreements, such as the vendor or the material type, can
also be mapped (general conditions, transactions MEK*). Generally, the conditions in the POs are
document conditions. They are only valid for this document. The document conditions may also be
available for quotations and scheduling agreements if you have configured this in Customizing.
Q3: How does the price determination determine the conditions using a last purchase order?
If the info record does not contain any valid conditions, but a "last document" exists for the info
record, the system copies all of the conditions from this document if the following prerequisites are
met:
The net price must be zero (EKPO-NETPR = 0.00) after the system has carried out price
determination.
However, the net price is not zero after price determination has taken place and the system does not
copy the conditions from the last PO if master conditions that are included in the net price calculation
are maintained at, for example, vendor level or material group level.
The last document is not a request for quotation. The info record has not been deleted. The vendor
and the material in the info record are identical to the vendor and the material in the last document.
The calculation schema of the last document is the same as the current schema that has been
determined.
The system simply executes a copy function to transfer the conditions from the last document. The
system does not check for requirements for the calculation schema. The system does not copy the
condition records of the subsequent settlement (the condition type has the condition class "C");
instead, they are always determined again to ensure that the condition records are consistent with
the field contents. If you generally do not want the system to transfer the conditions from the last PO,
you can use the user parameter EVO to deactivate this .
Q4. Why does the system not carry out price determination when a scheduling agreement is
created?
Check Customizing for the document type of the scheduling agreement (transaction OMED). When
a scheduling agreement is created, the system carries out price determination only if the "Time-
dependent conditions" indicator is deactivated.
Q5. Rounding errors occur during a price determination process that takes into account the
conditions in the info record.
Check the standard quantity and the price unit in the info record. When you do this, take into
accounts 30658 and 39963). To avoid rounding errors, choose a standard quantity that is at least as
high as the price unit.
Q6.Why does the system not use a condition type when a purchasing document is created?
On the condition screen, go to the condition analysis (choose the "Analysis" pushbutton). The
condition screen displays all conditions for the calculation schema. Double-click the condition type
(or the access) to open the detail screen on the right-hand side. Navigate to the technical view
("View" pushbutton) for information about the field contents that were used for accessing the
condition table, and which fields have not been filled for accessing the table.
Q7. Why does the system not transfer the conditions from the contract to the scheduling
agreement when a scheduling agreement with reference to a contract is created?
Answer:
See 160630.
Q8. Why does the system not find any prices when I post a goods receipt (GR) for a
scheduling agreement or during the price simulation for a scheduling agreement (the
scheduling agreement has been created with reference to a contract)?
See 431460.
Q9. How can I maintain conditions for a material group item in the contract?
Conditions for material group items in the contract are not permitted. (see 62729 and 105899).
Q10.A plant-dependent info record and a plant-independent info record exist. The deletion
indicator (EINE-LOEKZ) is set for both info records. However, the system uses the price of
the plant-independent info record when I create a purchase order (PO). Why is this the case?
The relevant condition tables are read by an external SD module. The information about the deletion
indicator for the info record is therefore not available in this place. You can only configure that the
conditions of the plant-independent info record are read if the plant-dependent info record has been
deleted. To control this, use a relevant transfer parameter (komp-no017, set in the function module
ME_FILL_KOMP_PO). If both info records have been deleted, you can change the validity period of
the conditions to a date in the past, or you can archive the info record.
Q11. Why is the "Refresh" (Refresh prices) pushbutton inactive on the header conditions
screen in a PO?
At header level, this pushbutton does not have a function. The pushbutton does not trigger a new
price determination process for all items in a document. This can be executed only for one item at a
time. The pushbutton is therefore not active at header level. (This is the standard system design.)
You can use transaction MEI2 for the mass adjustment of documents due to changes in conditions.
Take into account the functional restrictions as described in the online documentation or in 457511
"FAQ: Purchase order change and goods receipt in purchasing".
Q12.Why does the system not determine the conditions automatically when I maintain a
quotation (transaction ME47)?
The price determination is not carried out when quotations are maintained. You must maintain the
conditions manually.
Q13.Why does the system not transfer the price from the purchase requisition to the PO?
See 393367.
Q14.Transaction ME22N: Why does the system not convert the price of the PO into the new
currency when the vendor is changed (different currency)?
See 445509.
Q14.When I change data, such as the material group or the account assignment category, in a
PO item, the new EnjoySAP transaction (ME21N/ME22N) automatically carries out a new price
determination process. This is not the case in the old transaction ME21/ME22.
This is not an error. The new EnjoySAP transaction has been designed to include this function as
well as several other additional functions regarding price determination.
Read Here for more SAP MM Transaction Codes.
Q15.Why does the system adjust the absolute conditions of a purchasing document to the
goods receipt (GR) quantity, or proportionally calculates them, when I post a GR? See
304178.
Q16. How does a new price determination process affect the values that were posted during
the GR when a GR is canceled?
See 508009.
Q17.In what circumstances does the system update the header conditions when a PO item is
deleted?
When a PO item is deleted, the system marks this item as "statistical" (field EKPO-STAPO = X) and
the header conditions reflect these changes. However, if the final invoice indicator (EKPO-EREKZ)
or the "Delivery Completed" indicator (EKPO-ELIKZ) is set for this item, the system does not mark
the item as "statistical" (EKPO-STAPO is not set) and the system therefore does not update the
header conditions.
Q18.When I display or change a purchasing document (scheduling agreement/contract), a
runtime error occurs because the price (net price or effective price) is negative. How can I
correct this problem?
To determine the condition that causes the negative price, proceed as follows: Scheduling
agreement: Use transaction ME3N to display the document. Choose the item and follow the menu
path "Edit -> Price Simulation" to navigate to the price simulation. Contract: Use transaction MEKA
to display the conditions for the contract. You can change these conditions directly in this
transaction.
Q19.When I change or display a PO, why does the system display other or additional
conditions that were not displayed when I created the document?Why does the system
suddenly display the gross price (PB00) in addition to the manual gross price (PBXX), or vice
versa?
These problems indicate that the calculation schema was changed after you had created the PO.
You must avoid this.
Q20.Why does the price determination not determine a price even though the master
conditions (info record, contract, scheduling agreement) contain valid prices (with scales)?
Check whether a scale exists for the quantity the price determination is based on. We recommend
that you set the quantity of the first scale to zero to avoid these problems.
Get More Questions and Answers with Explanation related to Price Determination in
Purchasing atSAP MM Forum.
Q21. Conditions that are valid at the time are maintained in a contract or in a scheduling
agreement (that has time-dependent conditions). Why does the item overview display an
obsolete price?
When you maintain condition validity periods, the system uses the price of the period that is currently
valid for the item (field EKPO-NETPR) However, when a validity period expires, the system does not
automatically update the net price of the item. You can use the report RM06ENP0 (for contracts) or
RM06ENP1 (for scheduling agreements) to update it afterwards. When you create a PO with
reference to such a document, the obsolete price does not affect this process because the system
always uses the current price from the conditions without taking into account the price of the item
(EKPO-NETPR).
Q22.A PO item contains a manual gross price (PBXX in the standard system). I use
transaction ME21N or ME22N to change fundamental data, such as the plant. Under what
circumstances does the system retain the price (the conditions), and when does it delete
them (the system issues message 06 218 "Net price must be greater than 0")?
When you change fundamental data, the system triggers a new price determination process. If the
price determination does not find a price, the system checks whether the price that previously
existed was a "manual price". (A price is a manual price if the net price equals the gross price
(PBXX); that is, if no further conditions were included in the net price. In this case, the "Net price"
field on the item overview is ready for input.) If this is the case, the system uses the price that
previously existed. You therefore get the impression that the system did not change the price when
you made changes to the item. In the alternative scenario (the net price does not equal the gross
price; the "Net price" field on the item overview is not ready for input), the system cannot transfer the
price that existed previously (the conditions). You must maintain the price again; the system issues
error 06 218 "Net price must be greater than 0".
Q23.Why does the system not use the better price, which results from the scales, for a PO
(several items for the same material, scales are maintained in the master conditions)?
The system does not group together the PO quantities of the items so that the scales are taken into
account until the document is saved or checked.
Q24.I create a PO with reference to a quotation with document conditions. The quotation
contains further conditions, such as discounts or surcharges, in addition to the gross price
(PBXX in the standard system). When a price determination of the type "C" ("Copy manual
pricing elements and redetermine the others") is carried out for the PO item (either manually,
or triggered by the system when, for example, the account assignment category is changed),
the system doubles several conditions. Why is this the case?
When you use a reference to a quotation, the system copies the conditions from the quotation. If the
price determination of the type "C" is carried out afterwards, the conditions that were maintained
manually (from the quotation, as PBXX) are retained, and the gross price from the master conditions
(for example, info record) is included. However, this gross price is set to "inactive". This is displayed
on the detail screen for the condition.
Q25.I post a GR for a PO item with pricing date category "5" (new price determination at GR).
Why does this price determination determine a condition twice?
You have manually changed or manually maintained this condition in the PO. In addition, this
condition is maintained in the master conditions (for example, info record). The price determination
of the type "C" is carried out during the GR. As a result, the system retains the condition, which you
manually changed or maintained, from the document, and also determines it from the master
conditions. To correct this problem, make the following setting for the condition in Customizing
(transaction M/06): Manual entries: "C Manual entry has priority"
If the price determination of the type "C" during the GR now determines an existing condition from
the master conditions, the system sets this condition to "inactive" because the manual condition from
the document has priority (this is displayed on the detail screen for the condition).
Q26. I post a GR for a PO item with pricing date category "5" (new price determination at GR).
The system issues error message ME 573 "Transaction cannot be posted due to errors in
price determination".
The price determination may use condition records that did not yet exist when the document item
was created; for example, an additional discount at vendor level. The net price may have a negative
value or a value of "0" due to these conditions, which are determined additionally. To establish which
conditions cause the incorrect price, it may be helpful to create an identical PO item that has
identical data. On the condition screen, navigate to the analysis. In the analysis, you can establish
which condition record causes the incorrect result.
Q27. When is the net price in the item overview for a PO ready for input, and when is the net
price not ready for input?
The net price is not ready for input (you can change the price on the condition screen only) in the
following scenarios:
The document currency differs from the condition currency of the price. The system includes further
conditions in addition to the basic price PB00 when the gross value is calculated (for example,
variants). The net value differs from gross value.
Q28. When is the condition value for the condition of a returns item negative, and when is it
not negative?
A negative plus/minus sign is assigned to the condition value for the condition of a returns item if the
following settings are made in Customizing for the condition type: - The condition category is not set
to "B" (Delivery costs). - The "Accruals" indicator is not set. - The "Statistical" indicator is not set in
the calculation schema for the condition.
You can also get information regarding SAP MM
A negative plus/minus sign is assigned to the condition value for a condition that has the category
"B" ("Delivery costs") only if the calculation type for the condition is set to "A" ("Percentage"). (See
LV61AA43, FORM xkomv_kwert_ermitteln.)
Q29.How are the prices determined in the info record or in the contract if fixed conditions
(calculation rule "B", fixed amount) are included in the net price?
See 586856.
Q30.If I use the user exit EXIT_SAPLMEKO_002, price determination in transaction ME21N
differs from price determination in transactions ME21 and ME59.
A frequent cause for the different behavior of the price determination in transaction ME21/ME59
when you use the user exit EXIT_SAPLMEKO_002 is that the user exit uses the fields EKPO-
BANFN/EKPO-BNFPO. The system fills these two fields only if transaction ME21N is used. In
transactions ME21 and ME59, these fields are initial; however, the document number and the item
number for the purchase requisition are contained in the table EKET. The system behavior differs
because the features of the EnjoySAP purchase order transaction have been enhanced. This is not
an error in the R/3 standard system. If you want these transactions to behave in the same way,
extend the interface of the user exit EXIT_SAPLMEKO_002 and the interface of the function module
ME_FILL_KOMP_PO accordingly.
Q31.I copy a PO item ((ME21/ME22 or ME21N/ME22N). The reference item contains taxes. Why
does the system copy the corresponding condition, but it does not copy the condition
amount and the condition value?
The system does not copy the amount and the value to the new PO item. The system determines
the amount and the value when a PRICING_COMPLETE is executed. This is executed when the
document is checked or posted, and when you navigate to the header conditions.
Q31. When I post a GR for a scheduling agreement with pricing date category "5" (new price
determination at GR), the system may determine a price that has a value of zero; this price is
also displayed in the PO history (and in the goods receipt/invoice receipt (GR/IR) clearing
account). Why does this happen?
See 683646.
Q32.Can I change conditions after the GR/IR has taken place? Is it still possible to carry out a
new price determination process at this stage?
You can no longer change the delivery costs after the GR has been posted. If you have implemented
549408, you cannot change conditions that have the category "B" ("Delivery costs") after an invoice
has been posted or parked either. If you change data in the PO and this data usually triggers a new
price determination process of the type "B" or "C", the system does not execute this automatic price
determination if a GR or an IR has already been posted.
Q33.I want to use the report RM06ENP0 to update the net price in the contract. The document
contains valid conditions. Why does the report not determine the net price?
The system uses the release quantity to determine the net price. If the release quantity is smaller
than the price unit, the net price may be rounded to zero if the gross price is low. The release
quantity should always be the same as the price unit or higher than the price unit.
Q34.In a scheduling agreement that has time-dependent conditions, I maintain a condition
that has scales. The system always uses the first scale level to calculate the net price. Is this
the intended system behavior?
You cannot compare the price determination in the scheduling agreement to the price determination
for the PO if the scheduling agreement is a document that has time-dependent conditions (master
conditions). The system always uses the first scale level when the price is displayed in the
scheduling agreement. For further information about the GR for scheduling agreements with scales,
read 401941.
Q35.I maintain supplementary conditions in a quotation; for example, discounts (condition
type RA01). Why does the system ignore these conditions when I compare quotations
(transaction ME49)?
This problem occurs if you use a supplementary calculation schema (RM0002 in the standard
system), which contains conditions that are not included in the calculation schema for the document
(RM0000 in the standard system). All of the condition types that are used in a supplementary
calculation schema must be specified in the calculation schema for the document.
Q36.Can I use net prices that have more than 11 digits (including decimal places)?
The field for the net price can be filled only with 11 characters (including 2 decimal places). A larger
value usually leads to an overflow error ('price overflow error'). You can avoid this error by i)
reducing the related quantity, ii) splitting the material item into several items, or iii) changing the price
unit of measure accordingly.
The same applies for effective prices, which cannot exceed 13 digits (including 2 decimal places).
If you have further questions about this, we recommend that you open a customer message and
forward it to SAP Development Support.
 Q37.How can I prohibit changing the amounts on the condition screen in the conditions PB00
or PBXX using transaction ME22N? Use the user exit USEREXIT_FIELD_MODIFICATION, and
use transaction SE38 to insert the source code in the include LV69AFZZ to prevent the changes.

Top 20 Purchase Requisition (PR) FAQ's for Freshers

Q1: How can we track requisitions that have the deletion indicator set? Can we track the date in which
the deletion indicator was set?
Ans: You can refer the change document tables cdpos and cdhdr. You can also refer Transaction
ME53 under menu path goto-statistics-changes, where the complete audit trails of changes,
including deletion are stored.
Q2: Is it possible to generate Purchase requisition (PR) with reference to Scheduling Agreement?
Ans: PR can be created with reference to another PR and can not be created referencing a PO or
Scheduling agreements. PO & Scheduling are created and controlled by purchasing organizations.
PR can be created by even end users. For creating PR with reference to another PR, follow the
menu path:
 Purchasing->Requisition->Create.
 Requisition->Copy reference and enter.
However, requirement can be generated with reference to Scheduling agreement when MRP is run.
For this to happen, source list has to be maintained for that item-vendor combination and the MRP
shall be properly set.
Q3: Where can I locate the latest Purchase Order price and the latest purchase order number for a
material?
Ans: Logistics-Material Management-Purchasing-Master data-Info record-List display-Order Price
History
Q4: Automatic generation of PO is by using 'Automatic Via Purchase Requisition' option in purchasing-
Requisition-Follow on Functions- Create PO. However PO can not be created automatically after MRP
run. Is there a provision in SAP to release Purchase Orders automatically after MRP run?
Ans: Tick the automatic PO and Source List fields in purchase view of the material master for the
vendors on whom you would like to release PO automatically. Create a purchase info record. Create
source list. In the last column in the details screen of the source list check the field relevant for MRP
set the correct parameters for running MRP. But PO can not be created automatically after MRP run.
The automatic PO creation flag enables you to run a batch job that will convert all selected Purchase
Requisitions to be converted Purchase Orders in the background.
You may consider scheduling agreements if you want MRP to kick out Purchase Orders. Set the flag
in the source list for the scheduling agreement to "2" enabling MRP to kick out delivery schedules for
future requirements. If you want to fix the schedule within a certain period you have two options.
 Using firm zone - firms all orders within this period. Refer additional data screen of the scheduling
agreement at the vendor material level.
 Planning time - all new orders outside of the planning time fence - refer MRP 1 view of the material
master
Read Here for SAP MM Tutorials
Q5: I would like Convert MRP generated 100 PRs into 100 POs automatically. Not one by one manually.
Is it possible?
Ans: Use transaction ME59
Q6: How can I print an Un-invoiced Receipts Report which shows Purchase Orders for which goods are
received, but not yet invoiced? We require this report with sub-totals and tied to Un-invoiced Receipts
G/L Account
Ans: Report RM07MSAL analyses GR/IR balances according to goods received but not invoiced
and invoices received where good have not been fully delivered.
Q7: How can I calculate the net price of an inforecord for a given date?
Ans: Run price simulation in the LIS-Purchasing on the Vendor-info record and Specify the required
date. (Transaction code is: MEIL)
 Q8: Can we release a Purchase Order with price equals zero? ( like in SD- free of charge sales Order)
Ans: Create the PO with IR field un-ticked in Item Detail screen and change the line item price to 0.
Q9: The net price is calculated by summing up the gross price condition type and subtracting /adding all
discount/surcharge type condition types respectively. Any condition type which is not marked as
statistical will be considered for net price calculation. We have a surcharge that is not marked as
statistical and should be included in the net price but excluded in the taxation base value. Can I have a
procedure where the taxes are calculated on the net price calculated till the condition type NAVS and
then have this additional surcharge type?
Ans: Create Pricing Schema with all condition not marked in the Statistical column if you need all
condition Record to be calculated.
For Example:
Level CondTy Description From To
100 PB00 Gross Price
200 RA01 Discount % on Gross
300 ZMUP Mark Up (value)
400 Base Value for Tax 100 300
500 ZDIS Disc. Excluded Tax
600 Net Amount
700 MST Tax 400 400
800 Net Amount
Read Here for more SAP MM Transaction Codes.
With this Schema:
 Net Amount will be calculated from PB00, RA01, ZMUP, ZDIS.
 Tax will be calculated from PB00, RA01, ZMUP.
The total amount will be calculated from net amount and Tax. So, ZDIS will included in Net Amount
and excluded for Tax.
Q10: Can we change the name of the Vendor in a PO released on another Vendor?
Ans: NO. You may create another PO on the vendor required by referencing any PO.
Q11: We want to return unused material procured from a vendor and update stock or expense Account.
How to do this effectively?
Ans:
1. Use movement type - 122 to reverse receipt and reopen purchase order. This can be done if you
can identify the PO against which the material was received. And also credit shall be same as PO
Price
2. Special movement type has to be setup if the PO is not known. The price may have to be
negotiated with vendor.

Q12: How do I define a new currency? How can I set the number of decimal places more than two?
Ans: Define a new currency in Customizing with transaction OY03
If you change the current currency all of your accounting documents will be re-evaluated by R3 and
this could cause adverse affects to your financials.
Use transactions:
OY04 to assign number of digits to new currency
OBBS to define conversion factors for currency conversion
OB08 to enter exchange rates
XK02 to assign new currency to Vendor Master
ME11 to create a Purchase Info record
Create MM documents with the new extended price.
However, you notice that accounting documents will still reflect the 2 digit price and rounded to the
nearest 1/100th.
Q13: Our supplier delivers his product for an Auction. We sell it in an auction and pay the supplier.
What is the best way to handle this?
 Ans: You can try consignment process. In this process, Vendor holds the goods until they are sold.
The price to the supplier can be reset when the goods are sold in settle consignment liabilities.
Q14: How can I open a previous MM period?
Ans: Transaction - MMPV
Menu path - Logistics->Materials Management->MaterialMaster->Other-> Close Period
Q15: We can make a particular indicator mandatory. Can I have a defaulted value for the indicator
while creating a Material master that can be changed later in MM02?
Ans: Try using transaction variant, transaction code SHDO. And then SE93. In SE93 choose the
option of variant transaction
Get More Questions and Answers with Explanation atSAP MM Forum.

Q16: How can I generate a report of cancelled PO?

Ans1: Use a Query with table EKKO whose field LOEKZ is the deletion indicator.

Ans2: Go to the initial screen of purchasing. Then go to PURCHASING -> LIST DISPLAYS -> BY
PO NUMBER -> EDIT -> DYNAMIC SELECTION. This allows you to select certain fields from the
EKKO table and EKPO table. Deletion indicator can also be seen here. Use 'dynamic selections' to
determine your selection criteria and run the report.

Ans3: You can also do this via the IMG

 Go to Transaction OMEM or Menu path - MM -> Purchasing -> Reporting -> Maintain Purchasing
Lists
 Click on Scope of List Create New entry.
 Check on Change Documents field. Name the new Scope with a relevant name. This will now
appear in Scope of List field in all Purchasing List Display screens. The output will show the details
of the changes like date and time of change, old value, new value etc.
Q17: How can we detect a change in a Purchase Order?
Ans: For Header level changes: Go to Header -> Statistics -> Changes
For Item level changes: Go To Item-> Statistics -> Changes
Q18: We want to pop-up a screen to show the total value of PO before saving the PO so that user can
decide whether to save the PO or discard it. What is the best way?
Ans: Try using EXIT_SAPLEINS_001. It is entered during the saving operation of a PO. You can
review the PO, present a popup dialog using one of the POPUP_* functions enabling the user to
decide either to save or abort the PO.
Q19: PO item text is being adopted from the Material master. The text has got adopted status and is not
stored in the text ID tables STXH and STXL. Hence print program is not able to print these texts. How
can we solve this?
Ans: Purchase order texts can be adopted from Info record or material master. All the texts finally
gets stored in table STXH with different text application objects. Incase of PO header text it is EKKO
and PO Item text it is EKPO. Even if the texts are adopted from either of these, there is a possibility
that it can be altered at PO level. Here it will get stored with object EKKO or EKPO.
There is no need to store this at PO level if there is no change made to the text at PO level,
Try these: Check for texts in EKKO or EKPO ( depending on header or item level)
If no text gets returned back check in object EINA for info record or MATERIAL for material master
long text.( table is same i.e. STXH)
Q20: While creating a purchase order we can see that there is the "Info rec. update" in the box item
detail screen. How can we change the default setting for this box?
Ans: In MM Purchasing configuration (use Transaction code: OMFI), you can assign the default
value of info records update for buyers then assign it through parameter ID EVO (check the
configuration documentation)
Best 20 Purchasing Related Interview Questions for 2 Years Experienced

Q1: How can we track requisitions that have the deletion indicator set? Can we track the date
in which the deletion indicator was set?
Ans: You can refer the change document tables cdpos and cdhdr. You can also refer Transaction
ME53 under menu path goto-statistics-changes, where the complete audit trails of changes,
including deletion are stored.

Q2: Is it possible to generate Purchase requisition (PR) with reference to Scheduling

Agreement?
Ans: PR can be created with reference to another PR and can not be created referencing a PO or
Scheduling agreements. PO & Scheduling are created and controlled by purchasing organizations.
PR can be created by even end users. For creating PR with reference to another PR, follow the
menu path:
Purchasing->Requisition->Create.
Requisition->Copy reference and enter.
However requirement can be generated with reference to Scheduling agreement when MRP is run.
For this to happen, source list has to be maintained for that item-vendor combination and the MRP
shall be properly set.

Q3: Where can I locate the latest Purchase Order price and the latest purchase order number
for a material?
Ans: Logistics-Material Management-Purchasing-Master data-Info record-List display-Order Price
History

Q4: Automatic generation of PO is by using 'Automatic Via Purchase Requisition' option in

purchasing- Requisition-Follow on Functions- Create PO. However PO can not be created
automatically after MRP run. Is there a provision in SAP to release Purchase Orders
automatically after MRP run?
Ans: Tick the automatic PO and Source List fields in purchase view of the material master for the
vendors on whom you would like to release PO automatically. Create a purchase info record. Create
source list. In the last column in the details screen of the source list check the field relevant for MRP
set the correct parameters for running MRP. But PO can not be created automatically after MRP run.
The automatic PO creation flag enables you to run a batch job that will convert all selected Purchase
Requisitions to be converted Purchase Orders in the background.
You may consider scheduling agreements if you want MRP to kick out Purchase Orders. Set the flag
in the source list for the scheduling agreement to "2" enabling MRP to kick out delivery schedules for
future requirements. If you want to fix the schedule within a certain period you have two options.
1. Using firm zone - firms all orders within this period . Refer additional data screen of the scheduling
agreement at the vendor material level.
2. Planning time - all new orders outside of the planning time fence - refer MRP 1 view of the
material master
Read Here for SAP MM Tutorials

Q5: I would like Convert MRP generated 100 PRs into 100 POs automatically. Not one by one
manually. Is it possible?
Ans: Use transaction ME59

Q6: How can I print an Un-invoiced Receipts Report which shows Purchase Orders for which
goods are received , but not yet invoiced ? We require this report with sub-totals and tied to
Un-invoiced Receipts G/L(General Ledger) Account.
Ans: Report RM07MSAL analyses GR/IR balances according to goods received but not invoiced
and invoices received where good have not been fully delivered.

Q7: How can I calculate the net price of an inforecord for a given date?
Ans: Run price simulation in the LIS-Purchasing on the Vendor-info record and Specify the required
date. (Transaction code is : MEIL)

Q8: Can we release a Purchase Order with price equals zero? ( like in SD- free of charge sales
Order)
Ans: Create the PO with IR field un-ticked in Item Detail screen and change the line item price to 0.

Q9: The net price is calculated by summing up the gross price condition type and subtracting
/adding all discount/surcharge type condition types respectively. Any condition type which is
not marked as statistical will be considered for net price calculation. We have a surcharge
that is not marked as statistical and should be included in the net price but excluded in the
taxation base value. Can I have a procedure where the taxes are calculated on the net price
calculated till the condition type NAVS and then have this additional surcharge type?
Ans: Create Pricing Schema with all condition not marked in Statistical column if you need all
condition Record to be calculated.
For Example :

Level CondTy Description From To

100 PB00 Gross Price

200 RA01 Discount % on Gross
300 ZMUP Mark Up (value)
400 Base Value for Tax 100 300
500 ZDIS Disc. Excluded Tax
600 Net Amount
700 MST Tax 400 400
800 Net Amount
With this Schema:
- Net Amount will be calculated from PB00, RA01, ZMUP, ZDIS.
- Tax will be calculated from PB00, RA01, ZMUP.
Total amount will be calculated from net amount and Tax. So, ZDIS will included in Net Amount and
excluded for Tax.

Q10: Can we change the name of the Vendor in a PO released on another Vendor?
Ans: NO. You may create another PO on the vendor required by referencing any PO.

Q11: We want to return unused material procured from a vendor and update stock or expense
Account. How to do this effectively?
Ans: 1. Use movement type - 122 to reverse receipt and reopen purchase order. This can be done if
you can identify the PO against which the material was received. And also credit shall be same as
PO Price
2. Special movement type has to be setup if the PO is not known. The price may have to be
negotiated with vendor.

Q12: How do I define a new currency ? How can i set number of decimal places more than
two?
Ans: Define a new currency in Customizing with transaction OY03
If you change the current currency all of your accounting documents will be re-evaluated by R3 and
this could cause adverse affects to your financials.
Use transaction
OY04 to assign number of digits to new currency
OBBS to define conversion factors for currency conversion
OB08 to enter exchange rates
XK02 to assign new currency to Vendor Master
ME11 to create a Purchase Info record
Create MM documents with the new extended price.
However you notice that accounting documents will still reflect the 2 digit price and rounded to the
nearest 1/100th.

Q13: Our supplier delivers his product for an Auction. We sell it in auction and pay the
supplier. What is the best way to handle this?
Ans: You can try consignment process. In this process, Vendor holds the goods until they are sold.
The price to the supplier can be reset when the goods are sold in settle consignment liabilities.

Q14: How can I open a previous MM period?

Ans: Transaction - MMPV
Menu path - Logistics->Materials Management->MaterialMaster->Other-> Close Period
Get More Questions and Answers with Explanation related to Purchasing at SAP Material
Management Forums.

Q15: We can make a particular indicator mandatory. Can I have a defaulted value for the
indicator while creating Material master that can be changed later in MM02?
Ans: Try using transaction variant, transaction code SHDO. And then SE93. In SE93 choose the
option of variant transaction

Q16: How can I generate a report of cancelled PO?

Ans1: Use a Query with table EKKO whose field LOEKZ is the deletion indicator.

Ans2: Go to the initial screen of purchasing. Then go to PURCHASING -> LIST DISPLAYS -> BY
PO NUMBER -> EDIT -> DYNAMIC SELECTION. This allows you to select certain fields from the
EKKO table and EKPO table. Deletion indicator can also be seen here. Use 'dynamic selections' to
determine your selection criteria and run the report.

Ans3: You can also do this via the IMG

Go to Transaction OMEM or Menu path - MM -> Purchasing -> Reporting -> Maintain Purchasing
Lists
Click on Scope of List Create New entry.
Check on Change Documents field. Name the new Scope with relevant name. This will now appear
in Scope of List field in all Purchasing List Display screens. The output will show the details of the
changes like date and time of change, old value, new value etc.

Q17: How can we detect a change in a Purchase Order?

Ans: For Header level changes: Go to Header -> Statistics -> Changes
For Item level changes: Go To Item-> Statistics -> Changes

Q18: We want to pop-up a screen to show the total value of PO before saving the PO so that
user can decide whether to save the PO or discard it. What is the best way ?
Ans: Try using EXIT_SAPLEINS_001. It is entered during the saving operation of a PO. You can
review the PO, present a popup dialog using one of the POPUP_* functions enabling the user to
decide either to save or abort the PO.

Q19: PO item text is being adopted from the Material master. The text has got adopted status
and is not stored in the text ID tables STXH and STXL. Hence print program is not able to
print these texts. How can we solve this?
Ans: Purchase order texts can be adopted from Info record or material master. All the texts finally
gets stored in table STXH with different text application objects. Incase of PO header text it is EKKO
and PO Item text it is EKPO. Even if the texts are adopted from either of these, there is a possibility
that it can be altered at PO level. Here it will get stored with object EKKO or EKPO.
There is no need to store this at PO level if there is no change made to the text at PO level,.
Try these: Check for texts in EKKO or EKPO ( depending on header or item level)
If no text gets returned back check in object EINA for info record or MATERIAL for material master
long text.( table is same i.e. STXH)

Q20: While creating a purchase order we can see that there is the "Info rec. update" in the
box item detail screen. How can we change the default setting for this box?
Ans: In MM Purchasing configuration (use Transaction code: OMFI), you can assign the default
value of info records update for buyers then assign it through parameter ID EVO (check the
configuration documentation).

SAP Procurement (MM) GST FAQ

Do we need to maintain service master for the procurement of any text based service?
That shall not be necessary. You can make use of the FI invoice or External Service Management
that was provided with the GST patch.
Is there a restriction of any kind on the name of the pricing procedure that is used in the
global landscape?
No restrictions have been put here.
Is it necessary to split the business places at line item in PO?
There is no need to do so.
When it comes to MIRO, are we required to split PO and Invoice if there is more than one
plant in a single PO that links to a different business place?
Each business place requires the creation of a separate MIRO. The Vendor is required to send a
separate invoice for each business place or GSTIN.
If the goods supplier partner is not maintained in the header of the PO, what is to be
defaulted in the MIRO under GST Partner field?
Under GST Partner field in MIRO, the main vendor of the PO shall be defaulted.
Why is there a field for the actual place of supply provided in the MIRO header?
Legally, there should be a separate invoice created for each business place/GSTIN. According to
rules regarding the place of supply, the place of supply need not be the same as the recipient
location specifically when it comes to services.
Will capturing of GST tax take place at the GRN Level?
No.
Shall all of the registers, such as RG1 and RG23 carry on in GST regime?
No.
Shall all of the registers such as RG1 and RG23 continue with regard to excise materials?
Yes.
Is it compulsory to create goods supplier partner function or is it sufficient to use main
vendor?
Goods supplier is not mandatory and the use of main vendor is fine.
During GR creation, will SAP provide the functionality for capturing the GST tax ?
No. this is not a mandatory functionality ,as per the law.
Will accounting document and tax component be different in case of vendor partner is getting
changed in MIRO?
For maintaining consistency, the customers will be required to modify the values in PO manual.
During import transactions, how will the Business place be updated or determined ?
SAP – Imports will be a part of the phase 2 deliveries in March 2017. For more details please refer to
the proposed development roadmap.
Which one is the best from IT point of view, the credit taken at the time of GR or IR?
SAP – In the GST regime credit is made available only when the vendor uploads the invoice in the
GSTN system. Therefore, it is only be at the time of IR.
Incase there are changes in Purchase order inputs, for example if the vendor has supplied
material from different location than that of listed in PO?
SAP – SAP will suggest to make the required changes in the PO, for ensuring consistency.
However, there will be an option available for editing this information at the time of MIRO. but this
change will not make a change in the PO.
During the time of Goods Receipt (GR), will the input tax credit be available?
No, input tax credit will not be available at the time of GR. It will only be available at the time of
IR. The reasons have been stated below:-
- GST invoice is a ‘Commercial cum tax invoice’ which is quite like VAT where taxes are
mentioned along with price (transaction value). Quite Unlike Excise, there is no TAX only invoice in
GST, therefore there is no separate invoice apart from the Logistics Invoice is required.
- Section 16(2) of the model GST law states that if a buyer has a valid GST invoice and has
received the goods, then he becomes eligible for claiming ITC on a provisional basis. GR is an
internal document for enabling the movement of Inventory, Inventory accounting. This is in no way
related to the recording of invoice from the supplier. ‘Possession of Invoice or Debit note’ is only
understood by the system when the invoice is recorded in the system. This step in the system is
MIRO. Please note that MIRO is Invoice capture and post transaction solely for the purpose of
verifying the logistics Invoice (proof that an invoice is received and has values which match to those
calculated by system). Please note, this is not considered as a payment transaction. This is quite
similar to all other countries which have VAT/GST.
- Last and most important, the source of truth for ITC of GST are the INVOICES uploaded in
GSTN by supplier. Incase this data has to be reconciled and credit accordingly confirmed w.r.t. ERP,
the comparison will be that of the INVOICE number/Date and Fiscal Period. GRNs cannot be
uploaded/compared with records in GSTN.