How To Fix J-139 - Determination of strike was not possible

J-139 - Overview

• Message type: E = Error

• Message class: J- -

• Message number: 139

• Message text: Determination of strike was not possible

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 J-139 - Determination of strike was not possible ?

  The SAP error message J-139, "Determination of strike was not possible," typically occurs in the context of the SAP system's handling of pricing and conditions, particularly in the area of sales and distribution (SD) or materials management (MM). This error indicates that the system was unable to determine the appropriate pricing conditions or strike prices for a transaction.
  Causes:
  
  
  Missing Condition Records: The most common cause is that there are no condition records available for the pricing procedure being used. This could be due to missing entries in the condition tables.
  
  
  Incorrect Configuration: The pricing procedure may not be correctly configured in the system. This includes issues with the access sequence or the condition types.
  
  
  Master Data Issues: There may be issues with the master data, such as customer master records or material master records, which could affect pricing determination.
  
  
  Inconsistent Data: Inconsistencies in the data, such as invalid or incomplete entries in the pricing