If you encounter this issue of the below error during PO Creation, you need to input PBXX and then fill the Price which is a work around.
But, you can find the root cause of the issue to fix the issue completely.
Go to M/06 or SPRO-IMG Reference-Material Management-Purchasing-Conditions-Define Price Determination Process-Define Condition Types and verify whether any one assigned Access sequence wrongly. If yes, you can remove and save.
Once you move the configuration TR to your testing client or quality client, you can test which will work fine
I hope this document is helpful for you. If you like, you can click on LIKE button and share with your circle.
I came with a concept which will be helpful for all SAP Functional consultants. I hope you will like the video. I am also providing the the document link with this video. Watch and share with your friends.
You can download the document which is used in Video with below link.
In this video, I have explained the process of fetching delivery texts with Function Module READ_TEXT. As we know that the text details can’t be fetched from Table so we need to use Function Module to get the data. This logic will be helpful when you work on any custom reports or Forms or any other developments where you supposed to get this information and display on screen.
I hope it will be helpful for you. Please watch and provide your valuable feedback.
I made video to check the roles details and basic usage of SUIM during authorization related queries. I hope it will be helpful for a functional consultant to get basic knowledge to use SUIM Transaction Code.
Watch and learn. Share the video if you like
If you need my whole SAP MM Videos, you can register in below link
Above error is occurred when the service entry sheet is released for a Service Purchase Order. The reason is the Service Purchase Order contains Planned Delivery Costs. Below are the reasons from SAP Standard to stop Service Entry Sheet.
planned delivery costs are generally not supported in
External Services Management and for blanket purchase orders, item category D
In the business function “LOG_MM_MAA_1”, it is possible to process service purchase order items with multiple account assignment and valuated goods receipts only without planned delivery costs. The design of this business function does not allow planned delivery costs for MAA service purchase order items. When posting the goods receipt for MAA purchase order items, the system checks the data to be posted for consistency. If this data is not consistent, the posting of the goods receipt terminates with error message M7 599. This message should prevent data inconsistencies.