How To Fix BORGR042 - Inbound deliveries found are not relevant for transport


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 042

  • Message text: Inbound deliveries found are not relevant for transport

  • Show details Hide details
  • What causes this issue?

    The inbound deliveries that match you entries are not relevant for
    transport.

    System Response

    No inbound deliveries are transferred.

    How to fix this error?

    You cannot change the indicator in the inbound delivery. The system
    automatically determines the transport-relevance from the Customizing
    settings for the delivery type, item category, and route.

    Procedure for System Administrators

    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.


Smart SAP Assistant

  • What is the cause and solution for SAP error message BORGR042 - Inbound deliveries found are not relevant for transport ?

    The SAP error message BORGR042 indicates that the inbound deliveries found are not relevant for transport. This error typically occurs in the context of logistics and transportation management within SAP, particularly when dealing with inbound deliveries that are expected to be processed for transport but do not meet the necessary criteria.

    Causes of BORGR042

    1. Delivery Status: The inbound delivery may not be in a status that allows it to be processed for transport. For example, it might be marked as "not yet started" or "completed."

    2. Delivery Type: The type of inbound delivery may not be configured to be relevant for transport. Certain delivery types may be excluded from transport processing.

    3. Transport Planning: There may be issues with the transport planning setup, such as missing or incorrect transport routes, or the transport planning run may not have been executed properly.

    4. Master Data Issues: There could be issues with master data, such as incorrect vendor information, material master data, or transport lane configurations.

    5. Selection Criteria: The selection criteria used to find inbound deliveries may be too restrictive, leading to no relevant deliveries being found.

    Solutions to BORGR042

    1. Check Delivery Status: Verify the status of the inbound deliveries in question. Ensure that they are in a status that allows them to be processed for transport.

    2. Review Delivery Type Configuration: Check the configuration of the delivery types in your SAP system to ensure that they are set up to be relevant for transport.

    3. Transport Planning Configuration: Review the transport planning settings and ensure that all necessary configurations, such as transport routes and planning parameters, are correctly set up.

    4. Master Data Verification: Ensure that all relevant master data (vendors, materials, transport lanes) is correctly maintained and up to date.

    5. Adjust Selection Criteria: If applicable, modify the selection criteria used to find inbound deliveries to ensure that it is not too restrictive.

    6. Consult Documentation: Refer to SAP documentation or help resources for additional guidance on the specific context in which the error occurs.

    7. SAP Notes and Support: Check for any relevant SAP Notes that may address this specific error message or related issues. If necessary, contact SAP support for further assistance.

    Related Information

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as VL31N (Create Inbound Delivery) and VL32N (Change Inbound Delivery) to manage inbound deliveries effectively.
    • Logistics Execution: Understanding the logistics execution processes in SAP can help in troubleshooting issues related to inbound deliveries and transport.
    • SAP Community: Engage with the SAP Community forums for insights and solutions shared by other users who may have encountered similar issues.

    By following these steps, you should be able to identify the cause of the BORGR042 error and implement a solution to resolve it.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker