How To Fix BOR01214 - Shipment &1 was not planned by an external system

SAP Error Message - Details

• Message type: E = Error

• Message class: BOR01 - Message class for ETA calculation and route simulation

• Message number: 214

• Message text: Shipment &1 was not planned by an external system

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 BOR01214 - Shipment &1 was not planned by an external system ?

  The SAP error message BOR01214 indicates that a shipment (identified by &1) was not planned by an external system. This error typically arises in the context of logistics and transportation management within SAP, particularly when integrating with external systems for shipment planning.
  Cause:
  
  Integration Issues: The shipment may not have been created or planned in the external system that is supposed to communicate with SAP.
  Data Transfer Problems: There could be issues with the data transfer between the external system and SAP, such as network problems or incorrect configurations.
  Configuration Errors: The integration settings in SAP may not be correctly configured to recognize or accept shipments from the external system.
  Missing Master Data: Required master data (like transportation lanes, shipping points, etc.) may be missing or incorrectly set up in either the external system or SAP.
  
  Solution:
  
  Check External System: Verify that the shipment was indeed planned in the external system. If not, you may need to create or plan the shipment there first.
  Review Integration Settings: Ensure that the integration settings between the external system and SAP are correctly configured. This includes checking middleware settings if applicable.
  Data Transfer Logs: Look at the logs for data transfer between the systems to identify any errors or issues that occurred during the transfer.
  Master Data Verification: Ensure that all necessary master data is available and correctly configured in both systems. This includes checking for valid transportation lanes, shipping points, and other relevant data.
  Consult Documentation: Refer to the SAP documentation or the documentation of the external system for specific integration guidelines and troubleshooting steps.
  Contact Support: If the issue persists, consider reaching out to SAP support or the support team for the external system for further assistance.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like VL03N (Display Outbound Delivery) or VT03N (Display Shipment) to check the details of the shipment in SAP.
  Integration Tools: If you are using middleware (like SAP PI/PO or other integration tools), check the configuration and logs there as well.
  SAP Notes: Look for relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution.