Q1. For Transactions ME2L, ME2M, ME2B, ME2N, ME2W, ME2K, ME2J, the stockkeeping unit is output for each individual unit of measure even though the price was maintained, for example, for 1000 units of measure in the purchasing document or in the info record.
In addition, in this line, the price is displayed in local currency and not in document currency.
For example, the display may look as follows:
4500032918 NB 1024758 Müller KG 001 08.08.2001
00010 HOLZ Timber, high-quality 002
0001 100,000 KG 15.00 FRF 15 KG
In stockkeeping unit 100,000 KG 0.30 DEM 1 KG
T 13.08.2001 100,000 KG
Still to be delivered 100,000 KG 100.00 FRF 100.00
Still to be invoiced 100,000 KG 100.00 FRF 100.00
How can I deactivate this?
You can deactivate the special line 'Stockkeeping unit' in Transaction OMEM. Select the corresponding scope of list and deactivate the 'Qty./val in BME/HW' indicator.
Q2. Why is the price for the stockkeeping unit not always correct (see the above question)?
If the prices for a material have been maintained, for example, for 1000 units of measure (5 EUR per 100 pieces) and not for individual units of measure (5 EUR per piece), this can result in inaccuracies caused by rounding. This is due to the fact that the stockkeeping unit is always displayed for each individual unit of measure, and therefore the price has to be converted so it can be displayed in the list.
However, since the line for the stockkeeping unit is for information purposes only and is not involved when calculating prices in documents, this inaccuracy should be acceptable.
Q3. In Transactions ME80FN, ME80AN, ME80RN, certain views do not contain any data in the result screen (ALV grid).
Refer to 451033.
Q4. If the indicator for the 'Only relevant' field is set in Transactions ME1L, ME1M and ME1W, the system behaves in exactly the opposite way to the description in the F1 help for this field.
The help text for this field is incorrect and was corrected for the R/3 Enterprise . The correct help text should be:
'Select the field if you do NOT want the system to display prices at plant level which were once created for a plant for which now prices are no longer permitted at plant level.'
Q5. If you double-clicked an info record in the list display for info records (Transactions ME1L, ME1M, ME1W), the system always displayed the last document for this info record. Now, you only get to the info record itself and no longer to the last document. Why?
386059 is responsible for this behavior.
The reason why this was possible before you implemented the was an inconsistency in the programming because a double-click was not explicitly read. As is usual in R/3 system, a double-click is used to access the detail display or for navigation purposes. Since the above transactions are list displays of info records, it makes sense to display these when you double-click. You can still navigate to the last purchasing document and you can display it by following the menu path 'Environment -> Purchase order'.
If you want to restore the old system response, you can only do this by removing 386059 again.
Q6. In the list displays for purchase requisitions (Transactions ME5A, ME5K, ME5R) you want to select only purchase requisitions that are blocked. To do this, you have set the flag 'Requisns.f.item-wise '.
However, in the list display.
The purpose of the 'Requisns.f.item-wise ' flag is not to exclude purchase requisitions that have already been from the selection.
To select only blocked purchase requisitions, use the dynamic selections for 'Purchase requisition' and select the 'Subject to ' field.
Q7.Why do some transactions for the list display terminate with error message VD 346 'Period indicator & is not defined'?
Refer to 456261.
Q8. Why does the quantity in the line 'Total of goods received' in the list display of reporting transactions sometimes differ from the total of goods received in the purchase order history?
In reporting transactions (for example, Transactions ME2L, ME2M, and so on) the total of the goods receipts is calculated by the quantity of goods received and the blocked stock quantity.
However, the total of the goods receipts that is displayed in the purchase order history (for example, Transaction ME22, ME23) does not take the blocked stock quantity into account.
Q9. After you have imported Support Packages, the layout variants in Transactions ME80FN, ME80RN and ME80AN no longer work.
What is the cause of this?
Refer to 495631.
Q10. Why is it not possible to select purchase orders in Transaction ME3L if you use the scope of list 'BEST'?
In Transaction ME3L, you can only select scheduling agreements and contracts.
Use Transaction ME2L to select purchase orders.
Q11.For which transactions for the list display is the ALV grid available?
You can find the list of the available transactions
- for R/3 Enterprise, in the :
- Menu path: Help -> Information
- Pushbutton: MySAP Complete List
- Select the entry "470" and choose Display.
- Under 'MM-PUR' you can find the document: "Accessible: Lists converted to ALV grid in the purchasing (changed)"
- as of ECC 5.0 (ERP2004), there are additional enhancements.
Q12. Why does the sort indicator in Transaction ME55 not work for overall strategies?
For technical reasons, the sort indicator only works with strategies for item-wise .
Read Here at SAP PP Forum to Get Answers to More Questions Like Aforementioned.