How To Fix NJIT_MSG070 - &1 is pending for External JIT Call &2

SAP Error Message - Details

• Message type: E = Error

• Message class: NJIT_MSG - NJIT Inbound message class

• Message number: 070

• Message text: &1 is pending for External JIT Call &2

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 NJIT_MSG070 - &1 is pending for External JIT Call &2 ?

  The SAP error message NJIT_MSG070 typically indicates that there is a pending external Just-In-Time (JIT) call for a specific process or transaction. This error can occur in various contexts, often related to logistics or production processes where JIT principles are applied.
  Cause:
  
  Pending External JIT Call: The error suggests that there is an external JIT call that has not been completed or processed. This could be due to various reasons such as:
  
  The external system has not responded.
  There is a communication issue between SAP and the external system.
  The JIT call was not properly configured or initiated.
  There may be missing or incorrect data that is preventing the JIT call from being processed.
  
  
  
  Solution:
  
  Check External System: Verify the status of the external system that is supposed to handle the JIT call. Ensure that it is operational and can communicate with SAP.
  Review JIT Configuration: Check the configuration settings for JIT in SAP. Ensure that all necessary parameters are correctly set up.
  Monitor JIT Calls: Use transaction codes like JIT1 or JIT2 to monitor the status of JIT calls and identify any that are pending or have failed.
  Check Logs: Review application logs (transaction SLG1) for any additional error messages or warnings that could provide more context about the issue.
  Data Validation: Ensure that all required data for the JIT call is complete and accurate. Missing or incorrect data can lead to pending calls.
  Retry the Call: If the issue was temporary, you may be able to retry the JIT call manually or through a batch job.
  Consult Documentation: Refer to SAP documentation or notes related to JIT processing for any specific troubleshooting steps or known issues.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to JIT processing. You can search for relevant notes using the SAP Support Portal.
  Transaction Codes: Familiarize yourself with relevant transaction codes for monitoring and managing JIT calls, such as:
  
  JIT1 - JIT Call Overview
  JIT2 - JIT Call Processing
  
  
  Integration with External Systems: If your JIT process involves integration with external systems (like EDI), ensure that the integration settings are correctly configured and that there are no connectivity issues.
  
  If the problem persists after following these steps, it may be necessary to involve your SAP Basis or technical team for further investigation.