SAP MM INTERVIEW QUESTION & ANWSER

Q1. A goods receipt was posted for a purchase order. You then want to make other changes
in the purchase order. What may be changed?

If follow-on documents already exist for a purchase order, changing the purchase order is generally
a problem. Therefore, you should consider the changes and the possible consequences carefully. If
possible, it is better for you to create a new purchase order.

Q2. A goods receipt has already been completed for a purchase order item. Can a deletion
indicator be assigned to this purchase order item? What happens if delivery costs are
provided for the purchase order items in question?

In this case, the purchase order item can be provided with the deletion indicator, if either all
subsequent documents created for the purchase order item (goods receipts, invoice receipts) were
cancelled again, or if the item has already been settled completely, that is, if the invoices for the
goods reciepts have been posted and if there are no remaining open items or differences.

This also applies if delivery costs are planned for the purchase order item. In this case, completely
settled means that the corresponding settlements are made for the delivery costs. If you can also
delete purchase order items in other cases, this is an error and it can be corrected using 157602.
(affected releases 3.1I, 40B and 45B, more detailed information is contained in the ). : If the delivery
costs are not to be settled, but are only taken into account when goods are received, the conditions
you select for the purchase order items should not be of type 'B' and should not be provisions.

The deletion indicator is particularly important for archiving. In the above case, it initially only means
that the purchase order item is flagged for deletion. Only the whole order can actually be deleted,
and only if all items in the purchase order are flagged for deletion .

Q4.Is it still possible to change the net price of a purchase order item after a goods receipt
has been executed?

Yes, the net price can still be changed in the purchase order after the execution of a goods receipt or
invoice receipt so that price changes for a material that occurred in the meantime can be included.
However, when you execute the change you must be careful. In any case you should check whether
this change possibly requires that you cancel follow-on documents. In particular, bear in mind that if
you run a new price determination during goods receipt (meprf=5), any changes made to the
cancellation after the goods receipt causes the system to run a new price determination. For more
information on this, see 508009 and 456691, question 17.
A new price determination is no longer possible after the goods receipt has occurred. That is, if for
example, you work with new price determination for the goods receipt and WE-related invoice
verification and you change the purchase order price after the goods receipt, the 'old' price in the
goods receipt is used in the bill. If you do not want this to happen, you can cancel the goods receipt,
post with the new price and then this is considered in the invoice. Also consider FAQ 456691 for
questions regarding the price determination. If you have questions concerning a price change in
connection with a change of the IR indicator, see also 363173. If there are conditions (for example
discounts) that are included in the net price, you cannot change the net value on the overview
screen in the purchase order (this is no longer possible after you create the purchase order). It is
only possible to change the individual conditions, including PB00, on the condition detail screen.
Q5. Is it possible to still change the gross price for purchase order items with pricing date
category '5' (new price determination for goods receipt) manually after a goods receipt has
been executed in the purchase order?

Yes. However, you have to refer to 444708 and 509332, if the system then no longer determines the
price from the info record for the next goods receipt or the system does not post a shipment cost
document.

Q6. Is it possible to change the account assignment category or the data for the account
assignment (for example, account, cost center) of a purchase order item after a goods
receipt?

The account assignment category itself can no longer be changed after follow-on documents have
been posted. The system displays error message ME 458 (ME458). If this does not happen, then
there is a program error that can be corrected with 163428 or 382916 (if parked invoices are the only
follow-on documents, implement 489342 if the error message is not issued correctly). Implement
these s - if they have not yet been implemented in R/3 Support Packages - as otherwise errors may
occur during internal processing of data when follow-on documents are posted (in particular if
documents are canceled). Whether the data for the account assignment (such as account, cost
center) can still be changed after follow-on documents have been posted, depends on the account
assignment category used and can be specified in Customizing (Transaction OME9). If the
'Acct.asst.changeable' (depending on Release) flag is set there for the corresponding account
assignment category, the data for the account assignment can also be changed again in the
purchase order after goods receipt or invoice receipt. This also applies, of course, to the data in
individual lines of the multiple account assignment. However, bear in mind that you should carefully
consider every subsequent change in the purchase order. If there are differences between
Transaction ME22 and ME22N regarding the changeability of the account assignment category, refer
to 374554. For problems with the 'Acct.asst.changeable' flag with reference to a service order, refer
to 306528.

Q7. Is it possible to change or add delivery costs in the purchase order after a goods receipt
has been executed?

No, this should not be possible. The system generates error message V1631 'You cannot enter new
delivery costs' (V1631). Important: If your system does not behave in the manner described, this is
an error that can be corrected using s 187694 and 196884. This affects the earlier Support
Packages of Release 31I, 40B, 45B and 46B (you will find more detailed information in the two s
mentioned).

For the changeability of delivery costs after an invoice receipt, see 651798 and 720191,
or 549408. The existence of held delivery cost invoice documents must be checked
manually and has to be considered. Delivery costs must not be entered again or
changed if all follow-on documents were cancelled for the purchase order item, unless
there were no delivery costs for the posted documents. Otherwise there is no guarantee
that continued processing will run without errors. If you change the Customizing for
existing delivery costs, the system does not read this either in a purchase order with an
existing goods receipt. The new Customizing settings only take effect when you create a
new purchase order. Of course, the condition values of time-dependent conditions can
still be changed even after a goods receipt has occurred. See question four for
information on how to change the master condition values.

Get More Questions and Answers with Explanation at SAP MM Forum.

Please :
The restrictions on changing delivery costs as described above have only been developed over time.
This is not due to changed functions, rather previously we did not know that making changes could
sometimes lead to subsequent irreparable errors. In particular, when you post invoices for delivery
costs, the logic considers delivery costs that have already been posted (even if they have since been
cancelled) AND the data for delivery costs from the database (as displayed in the purchase order).
During processing, you have no way of knowing if this information is no longer compatible, nor any
way to discover the cause, and this leads to incorrect processing. You should therefore proceed as
follows: If delivery costs were entered incorrectly, you must cancel all related purchase order items
(reverse all documents) and enter a new purchase order item with the correct delivery costs.
Otherwise, there is no guarantee that further processing will be correct. If your delivery costs are
changed regularly, you should use master conditions.

Additional : If you have manually changed or maintained conditions in the purchase order, under
certain Customizing settings when you run a new price determination after a goods receipt, a
condition may be determined twice. For more information, see 456691, question 26.

Q8. Is it possible to change the currency in the purchase order after a goods receipt has been
executed?

No, this should not be possible. The system generates Message 06 489: 'Currency cannot be
changed after goods receipt' (Release 4.0) or 'Currency can no longer be changed' (Release 4.5). If
your system behaves differently, check whether 311129 was implemented to correct the system
response. If no currency update is executed (which may occasionally be the case) , you can change
the currency later (the system does not display an error message). However, you should consider
carefully if such a change is useful or required here.

Q9. What does the inward delivery completed indicator mean and where can I set it
manually?

You can set the inward delivery completed indicator if you do not expect any additional goods
receipts - even if the quantity ordered was not delivered completely. Since it is still possible that
another delivery may arrive for the purchase order in question, when you try to post another goods
receipt for the purchase order, the system may propose the remaining quantity instead of the
ordered quantity. However, the system does not propose the goods receipt indicator in this case,
rather you must set it manually.

If the purchase order has been completely delivered, you cannot post any further goods receipts.

In general, the "delivery completed" indicator is set directly in the purchase order. This is, of course,
only possible if at least one goods receipt has been posted. Otherwise the indicator is automatically
removed during the next goods receipt. If you want the goods receipt processor to set the "delivery
completed" indicator, but you do not want the processor to have authorization to change the
purchase order, the indicator can also be set in the goods receipt.
Q10.Is it possible to post a valuated goods receipt for a purchase order with multiple account
assignment?

No, this is not supported. The system generates error message 06 417 'With multiple acct.
assignment, enter GR non-val. or cancel GR'. Individual values can only be distributed to the
different account assignment objects when you post the invoice. For further information about this,
refer to 204252.

Q11.I want to use a report to set the 'Goods-receipt-based invoice verification' indicator
subsequently in purchase orders that have already been created. Do you recommend this
procedure?

NO. Even before you post the follow-on documents, you should not use this procedure. It inevitably
leads to follow-on errors because of mutual field relationships. In our experience, we know that some
other customers have had to invest a lot of time and energy into correcting follow-on errors.

Q12.Is it still possible to change the 'Goods-receipt-based invoice verification' indicator

manually after you have posted follow-on documents? No, this should not be possible. If this
was possible in your system, especially if such a change was d in the change documents with
Transactions ME22N or ME21N, the change was probably carried out indirectly by changing the
reference documents. To prevent this from happening, implement s 431213 and 441759 as well as
570321.
Refer also to s 494376 and 587759 with respect to this when working with the invoice parking
(Transaction MIR7).

The only case in which the indicator can still be changed after posting follow-on documents is if all
follow-on documents were cancelled again and no delivery costs were involved in the follow-on
documents.

To find purchase orders in your system for which the indicator can still be changed subsequently
(that is, after you have posted follow-on documents), you can implement the check report contained
in 550163. You MUST first consult with Development Support.

Q13. Can the indicators for expected goods receipt or expected invoice receipt, and the
indicator for non-valuated goods receipt, subsequently be changed?

In principle, the logic is the same as for the indicator for goods receipt-based invoice verification (see
questions 10 and 11). In addition to the s mentioned there, check whether 587759 has been
implemented in your system to avoid this error in the future ( 587759 fills the gap for parked
invoices). See 584232 for information about updating change documents for the 'Goods Receipt,
Non-Valuated' indicator.

Q14. Is it still possible to change the freight vendor after a goods receipt or invoice receipt
has been executed?

Yes, the freight vendor can be changed subsequently to accomodate corresponding changes in the
process handling (new vendor). However, you cannot check here whether invoices or goods receipts
are still open for this vendor. Therefore, you must check whether the goods receipts and the
corresponding invoice receipts for delivery costs for the vendor are cleared before you make the
change. Otherwise you can no longer delete the corresponding purchase order item or problems can
occur, in particular when you post invoices for delivery costs (the system does not propose a vendor,
or a held delivery costs document can no longer be processed).
Release Strategy 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.
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?
Top 10 Taxes in Purchasing FAQs

Q1. How is the tax code determined in purchase orders?

In the standard system, the system considers the following sources for the tax code (in this
sequence): Reference item, contract, request for quotation, info record. It can also be entered
manually.

Furthermore, the tax code can be automatically determined via the condition technique.

For the determination of the tax code via the condition technique, condition type NAVS with assigned
access sequence 003 is available in the standard system. With Transactions MEK1/MEK2,
depending on tax indicators (material, plant, account assignment, origin) you can define different tax
codes in the condition tables.

In principle, you can assign this access sequence also to other condition types. The tax code is only
transferred to the purchase order if class 'D' (taxes) is the condition type. If there are several
condition types of this class in the condition schema, then the first condition schema which contains
a tax code has priority.

Q2.How is the tax jurisdiction code (tax jurisdiction code) determined in purchase orders?

You activate the tax handling with tax jurisdiction codes in FI Customizing (transaction OBCO). In the
standard system during the creation of a purchase order, the system considers the following sources
for the tax jurisdiction code: Reference item, request for quotation, contract, plant, the account
assignment object. During this process, the system overwrites the respective preceding value in this
list. If for example, you have maintained a tax jurisdiction code with the account assignment object
for a purchase order item, this entry "wins" as opposed to the entry in the plant table. Besides this,
the tax jurisdiction code can be entered manually.

If you use the function from 493515, also the tax jurisdiction code from the delivery address can be
taken into account (see below.).

Q3.How is the tax amount calculated?

Only the non-deductible part of the tax is calculated. This amount should be regarded as an
additional cost item of the procurement because the tax authorities do not refund this amount unlike
the deductible part of the tax. Therefore, the non-deductible part of the tax is added to the stock
value during the inventory posting. In the purchase order item, the non-deductible tax amount is
saved in field EKPO-NAVNW and, if existing, it is saved in the first condition type of category 'N'
(non-deductible tax). In the standard system, these are condition types NAVS and NAVM. For this
reason, calculation rule 'B' (fixed amount) must be set for the condition type (also refer to 138434).
Moreover, you have to take into account that the non-deductible tax amount is calculated with
function module 'CALCULATE_TAX_ITEM' program-internally. The calculation does not occur within
the price determination. As a result of this, the tax amount is only calculated after you have returned
from the condition screen and is not calculated on the condition screen when you change the price.

Read Here for SAP MM Tutorials.

Q4.What must I take into account for Customizing of a tax condition type for purchasing?

In order to ensure that the tax code is transferred to the purchase order and that the tax amount is
calculated correctly, you should make the following settings:

 Condition class: 'D' (Taxes)

 Calculation rule: 'B' (Fixed amount)
 Condition category: 'D' (Tax) or 'N' (Non-deductible input tax)
 Scale type: ' ' (must remain empty, this means 'can be maintained in condition record')

Read Here for more SAP MM Transaction Codes.

In addition, take into account that you have to set the tax record which is assigned to a tax code in
purchasing in FI Customizing (transaction FTXP).

Q5.The deductible tax amount is not to be considered as a cost item of the procurement. Is it
nevertheless possible to display it when printing a purchase order, for example?

This is possible. For this, proceed as described in 214151.

Q6: How is the tax determination in purchasing linked with the tax determination in the
service (MM-SRV)?

For detailed information on this, refer to 495316.

Q7: For the automatic specification of the tax code in purchase orders, I defined an access
sequence with own condition tables in Customizing. Why does the system not determine the
tax code again when changes are made to a purchase order which affect fields of these
condition tables?

In order to determine the tax code again, the price determination must be triggered again. Due to
performance reasons, in the standard system not all changes are taken into account in the header
and item fields. As of Release 4.6B using Business Add-Ins (BAdIs) you can, however, define
additional fields the change of which triggers a new price determination (see 495264).

Q8: I use a tax handling that works with tax jurisdiction codes. Is it possible to determine the
tax jurisdiction code depending on the actual delivery address and to use it for the tax
calculation?

This is possible. As of Release 46B, by means of a Business Add-In (BAdIs) you can define that and
how the tax jurisdiction code defined in the delivery address is to be considered at the tax calculation
in the purchasing (cf. 493515). This, however, only applies to the 'new' SAP ordering transaction
ME21N.

Get More Questions and Answers with Explanation at SAP MM Forum.

Q9: I use a tax handling that works with tax jurisdiction codes. At the same time, I defined
plants with a foreign location for company code in the system. However, the tax handling for
purchase orders for these plants does not work or does not work correctly.

The purchasing uses the FI function for the calculation of taxes. In order to ensure that the tax
handling for foreign plants works, you must activate and set the option "Plants abroad" in the FI
Customizing. However, this option is not compatible with a tax handling with tax jurisdiction codes.

Q10: You create a purchase order for a plant abroad or change such a purchase order. The
system generates an error message and/or the tax code is not determined correctly.

For this application area, the following exist:

492935: ME21N ME22N FICORE704 upon company code change

423019: ME21N Incorrect tax code after change of plant
494420: ME21N Incorrect price determination when plant is abroad
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 21 SAP MM Interview Questions &
Answers
1) Explain what is SAP MM?

SAP MM (Material Management) is a functional module in SAP that deals with

procurement handling and material management. The MM module contains
master data, system configuration and transactions to complete the procure to
pay process.

2) What are the essential components in SAP MM?

 Determine requirements
 Source determination
 Vendor Selection
 Order Processing
 Order follow up
 Goods receipts and Inventory management
 Invoice Verification

3) Mention what are the types of special stock available?

The types of special stock available are subcontracting, consignment, project,

pipeline, sales order, stock transfer, returnable packaging with customer, etc.

4) List out important field in purchasing view?

The critical fields in purchasing view are

 Base unit of measure

 Order unit
 Purchasing group
 Material group
 Valid from
 Tax indicator for material
 Manufacturer part number
 Manufacturer, etc.
5) Explain the importance of the batch record?

A batch tells about a quantity of a particular product, which is processed or

produced at the same time with the same parameters. The materials produced
in such batch have the same values and characteristics. While, the batch record
gives the information about a particular batch product and helpful in knowing
whether the product has gone through GMP (Good Manufacturing Process).

6) Explain how you can link a document to a vendor master record?

To link the document with the vendor master record by using the XK01
transaction code or by using the following menu path

 SAP Menu > Logistics > Material Management > Purchasing > Master Data
> Vendor > Central > XK01- Create.

7) Mention what are the major purchasing tables? List the transaction
codes for them?

 Purchase requisition > EKBN

 Purchase requisition account assignment > EBKN
 Release documentation > EKAB
 History of purchase documents > EKBE

8) Mention what are the data contained in the information record?

The information record contains data related to the units of measurement, such
as the products, vendor price, materials used by specific vendors, etc. It also
contains information on the tolerance limit of the under delivery of data,
vendor evaluation data, planned delivery time, availability status for goods.

9) Mention what is the transaction code to delete a batch?

The transaction code MSC2N is used to delete a batch. By flagging the batch
master record, you can delete a batch record alternatively.

10) Mention what is the transaction code used to extend the material
view?

To extend the material view transaction, code MM50 is used.

11) Explain how you can change the standard price in the master material?

The standard price for the material data cannot be updated or changed directly.
However, to change the standard price you can perform the following steps

 Fill in the future fields price ( MBEW-ZKPRS ) and the effective data
( MBEW-ZKDAT) for the materials
 Select Logistics > Material Management > Valuation > Valuation Price
Determination > Future Price

12) What is Source List and what is the transaction code for creating
Source List?

To identify sources of supply for materials a source list is used. To create a

source list the transaction code used is ME01.

13) For creating a purchasing info record what are the pre-requisites?

The pre-requisites for creating a purchase info record are

 Material Number
 MPN ( Manufacturer Part Number )
 Vendor Number
 Organizational level code

14) Explain the terms Planned delivery and GR processing time?

Planned delivery means number of calendar days required to obtain the

material, and GR processing means number of workdays required after
receiving the material for inspection and placement into storage.

15) What is purchase requisition as related to SAP? Mention the document

types that are used in purchase requisition?

Purchase requisition in SAP determines both stock and non-stock items to the
purchasing department. It can be done either manually or automatically, the
document types used in purchase requisition are

 RFO ( Request For Quotation )

 Outline Agreement
 PO ( Purchasing Order )

16) Explain how consignment stocks are created?

In the normal purchase order or requisition, consignment stocks are created.

While creating consignment stocks things to be considered is that you must
enter K category for the consignment item. As a result, the goods issued are
posted to consignment stores and invoice receipt is not generated.

17) Explain how is the vendor return processed without a purchase order
reference?

First you have to observe the return column and then select -- Item Detail >
MIGO_GR > Goods Receipt for Purchase Order. Use movement type 161 if the
intention is to deduct the stock otherwise, 162 is used to undo the changes. In
the end, you have to ensure that the document is a return purchase order, and
then the document is saved.

You can also use transaction code M21N for this purpose

18) Explain how you can create a vendor account group in SAP?

To create vendor account group in SAP

 Select display IMG > Financial Accounting > Accounts Payable/Receivable

>Vendor Accounts > Master Records > Preparation of creating vendor master
records > Define Accounts groups with Screen Layout

19) Explain what are the accounts created in SAP MM?

Assignment of account is necessary for the purchase order item, it is important

in SAP MM as it determines following things

 Account assignment type

 Account that will be charged when you post the invoice or goods receipt
 Account assignment data that you should provide

20) Explain what MRP (Material Requirement Planning) list is and what is
the transaction code to access MRP list?
MRP list is the initial working document from which the MRP controller starts
working, and it consists of planning results information for the material. For an
individual item, you can access the MRP list by using the transaction code
MD05. You can also access the MRP list by navigation path

SAP Menu > Logistics > Materials Management > MRP > Evaluations > MRP List-
Material

21) Explain what is CBP? What is the difference between CBP and MRP?

CBP is the past consumption values of stock; it is used to forecast future

requirements. On the basis of past consumption values, the net requirement of
goods is calculated.

The difference between CBP and MRP is that when you plan materials using
MRP, you have to predict the materials requirement based on sales and
operations planning (SOP). While in CBP you have to predict the material
requirement based on historical demand for materials.