How To Fix BORGR088 - PO determination did not run; dely type & not intended for inb. dely &4

SAP Error Message - Details

• Message type: E = Error

• Message class: BORGR - Messages Multi-Level Goods Receipt

• Message number: 088

• Message text: PO determination did not run; dely type & not intended for inb. dely &4

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message BORGR088 - PO determination did not run; dely type & not intended for inb. dely &4 ?

  The SAP error message BORGR088 indicates that the Purchase Order (PO) determination process did not run for a specific delivery type, which is not intended for inbound delivery. This error typically arises in the context of logistics and inventory management when the system is unable to determine a valid purchase order for a given delivery.
  Cause:
  
  Delivery Type Configuration: The delivery type specified in the error message may not be configured to allow for PO determination. This can happen if the delivery type is not set up correctly in the system.
  Missing or Incorrect Master Data: The relevant master data (such as vendor, material, or purchasing info records) may be missing or incorrectly maintained, preventing the system from finding a valid PO.
  Incompatible Document Types: The document types involved may not be compatible with each other, leading to the inability to determine a PO.
  Custom Logic or Enhancements: If there are custom developments or enhancements in the system, they may interfere with the standard PO determination process.
  
  Solution:
  
  
  Check Delivery Type Configuration:
  
  Go to the configuration settings for delivery types in SPRO (Transaction Code: SPRO).
  Navigate to Logistics Execution > Shipping > Delivery > Define Delivery Types.
  Ensure that the delivery type in question is correctly configured to allow for PO determination.
  
  
  
  Review Master Data:
  
  Verify that the vendor, material, and purchasing info records are correctly maintained.
  Ensure that the relevant data is active and valid for the transaction you are trying to execute.
  
  
  
  Check Document Type Compatibility:
  
  Review the document types involved in the process to ensure they are compatible with each other.
  Check if any specific settings or configurations are required for the document types being used.
  
  
  
  Debug Custom Logic:
  
  If there are any custom enhancements or user exits that might affect PO determination, review the code to ensure it is functioning as intended.
  Consider temporarily disabling custom logic to see if the standard process works without it.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide additional guidance.
  
  
  
  Testing:
  
  After making any changes, perform tests to ensure that the PO determination process works as expected.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like ME21N (Create Purchase Order), ME22N (Change Purchase Order), and VL01N (Create Outbound Delivery) to check related documents.
  SAP Documentation: Refer to SAP Help documentation for detailed information on delivery types and PO determination processes.
  Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.