#CoE#BUMA - Item price has not changed in the catalog Error upon creation of Purchase Requisition

[_JohnL_]

Hi,

We attempted to populate the material number using the BAdI (MMPUR_OCI_ITEM_TRANSFER_DATA - Change of OCI 4.0 Data When Mapping to a Purchase Requisition Item), but when trying to place an order through the external catalog and completed the details in Purchase requisition app then clicked "Create" PR, we received an error message stating, "The price for item 00010 has changed in the catalog. Update item price." Please note that this material number has an associated Purchasing Info Record.

Is there a way not to encounter this error and proceed with the creation of PR?

Regards!

John

[Dave_He · Accepted solution]

Hello @_JohnL_ 

Thanks for the questiona, The error message you are encountering, "The price for item 00010 has changed in the catalog. Update item price," typically occurs when there is a discrepancy between the price of the item in the external catalog and the price recorded in the SAP S/4HANA Cloud system (either in the Purchasing Info Record or the material master).

Here are some steps and considerations to resolve this issue:

1. Verify Price Consistency: Ensure that the price of the material in the external catalog matches the price in the Purchasing Info Record (PIR) or the material master. If they differ, you need to decide which price should be considered correct and update the other accordingly.

2.Synchronize Catalog and SAP System: Regularly synchronize the prices in the external catalog with those in the SAP system to prevent such discrepancies. This can be part of a routine check or automated if your system and the catalog provider support such functionality.

3.BAdI Customization: Since you are using the BAdI MMPUR_OCI_ITEM_TRANSFER_DATA, you can implement additional logic to handle price discrepancies. For example, you could add a check that compares the catalog price and the SAP price. If they differ, the BAdI could automatically update the price in the purchase requisition to match the catalog price, or it could trigger a notification for manual review.

4.User Training and Communication: Ensure that users are aware of the importance of maintaining consistent pricing information between the catalog and the SAP S/4HANA Cloud system. Training sessions or memos can help emphasize the impact of price discrepancies on the procurement process.

5.Error Handling in BAdI: Enhance the error handling within the BAdI to provide more descriptive and actionable messages. Instead of a generic error, provide guidance on what needs to be done to resolve the issue (e.g., "Please update the price in the Purchasing Info Record to match the external catalog").

6.Testing: After making adjustments, thoroughly test the process to ensure that the error does not recur. Test with different scenarios to cover various price mismatch situations.

By following these steps, you should be able to resolve the price discrepancy issue and prevent similar errors in the future when creating purchase requisitions from external catalogs.

Best Regards

Dave

[_JohnL_ · Accepted solution]

Hi Dave,

Thank you for your prompt response.

We noticed that whenever we purchase items through external catalogue then whenever there is an assigned Source of supply, we encountered this kind of error.

Does this mean that user must not add a Source of supply whenever they purchase items from catalog?

Regards!

John

[Eric_Yu · Accepted solution]

Hi Dave, would you please advise further?

[Dave_He · Accepted solution]

Hello @_JohnL_ Explorer. The error message you're encountering is likely due to a discrepancy between the price of the item in the external catalog and the price recorded in the Purchasing Info Record (PIR) in SAP S/4HANA Cloud. When a source of supply is assigned, the system checks the PIR for the price, and if it doesn't match the catalog price, it throws an error.

[Dave_He · Accepted solution]

Hello @_JohnL_ 

The error message you're encountering is likely due to a discrepancy between the price of the item in the external catalog and the price recorded in the Purchasing Info Record (PIR) in SAP S/4HANA Cloud. When a source of supply is assigned, the system checks the PIR for the price, and if it doesn't match the catalog price, it throws an error.

To avoid this error, you have a few options:

1. Update the PIR to match the catalog price: This would ensure that the prices are consistent and prevent the error from occurring. However, this may not be feasible if the catalog prices change frequently or if there are many items to update.

2. Remove the source of supply: As you suggested, not assigning a source of supply would prevent the system from checking the PIR and thus avoid the error. However, this may not be ideal if the source of supply information is important for your procurement process.

3. Customize the BAdI: You could potentially customize the BAdI to ignore the price check when the item is being ordered from the external catalog. This would require some technical expertise and a good understanding of your business requirements to ensure that it doesn't cause other issues.

BR

Dave