Do you have any question about this error?
Message type: E = Error
Message class: MIGO - Inventory Management: Interface
Message number: 045
Message text: Entry quantity changed in line &. Enter the PO price quantity
You want to post a goods movement for a purchase order with varying
order units and purchase order price units. You have changed the entry
quantity but not the purchase order price quantity.
The purchase order price quantity is deleted.
Enter the correct purchase order price quantity or leave the field
empty .
If you do not enter a purchase order price quantity, the purchase order
price quantity is calculated as follows:
At goods receipt, the conversion stated in the purchase order is used.
In the case of a return delivery, the conversion factor is calculated
using the total quantity of goods received.
Note: If you have changed the entry quantity in more than one line at
the same time, and this message is displayed in the status bar, a
message is generated for the last line only.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
MIGO045
- Entry quantity changed in line &. Enter the PO price quantity ?The SAP error message MIGO045 ("Entry quantity changed in line &. Enter the PO price quantity") typically occurs during the goods movement process, particularly when you are trying to post a goods receipt (GR) or a goods issue (GI) using the MIGO transaction. This error indicates that there is a discrepancy between the quantity you are trying to enter and the quantity that is expected based on the purchase order (PO) or the stock transfer.
Cause:
- Quantity Mismatch: The quantity you are trying to enter in the MIGO transaction does not match the quantity specified in the associated purchase order or stock transfer document.
- PO Price Quantity: The system expects you to enter a quantity that corresponds to the price conditions defined in the purchase order. If the quantity is changed, the system requires you to also adjust the price or confirm the price quantity.
- Incomplete Data: There may be missing or incorrect data in the purchase order or the goods movement document.
Solution:
- Check the Purchase Order: Verify the purchase order associated with the goods movement. Ensure that the quantity you are trying to enter matches the quantity specified in the PO.
- Adjust the Quantity: If you need to change the quantity, make sure to adjust it to match the PO or stock transfer document. If the quantity is correct but the error persists, check if the PO allows for partial deliveries.
- Enter PO Price Quantity: If you have changed the quantity, you may need to enter the corresponding price quantity. This can usually be done in the MIGO screen where you enter the goods movement.
- Review Document Flow: Check the document flow for the purchase order to ensure that there are no inconsistencies or issues with previous postings.
- Consult with Procurement: If you are unsure about the correct quantities or pricing, consult with your procurement or purchasing department to clarify the details of the purchase order.
Related Information:
If the issue persists after following these steps, it may be beneficial to involve your SAP support team or consult with an SAP expert for further troubleshooting.
Get instant SAP help. Start your 7-day free trial now.
MIGO044
Change of movement type &1 to &2 not possible
What causes this issue? The change &V3& is not allowed.System Response The system issues an error message and will not allow you to continue...
MIGO043
Check combination of movement type and stock type
What causes this issue? The stock type you have entered for a movement type is not allowed for that movement type. System Response This message is a...
MIGO046
Use button for stock or batch determination
What causes this issue? You entered an asterisk (*) in the field "storage lcoation" or "batch".System Response Entering "*&...
MIGO047
Maximum number of BADI implementations in MIGO has been exceeded
What causes this issue? The maximum number of implementations of BAdI <LS>MB_MIGO_BADI</> is five. This number has been exceeded. In tran...
Click on this link to search all SAP messages.