Do you have any question about this error?
Message type: E = Error
Message class: J- -
Message number: 139
Message text: Determination of strike was not possible
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.
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.
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 conditions, can lead to this error.
Authorization Issues: Sometimes, the user may not have the necessary authorizations to access certain pricing conditions.
Solutions:
Check Condition Records: Verify that the necessary condition records exist for the pricing procedure. You can do this by using transaction codes like
VK11
(Create Condition) orVK12
(Change Condition) to check the relevant condition types.Review Pricing Procedure Configuration: Ensure that the pricing procedure is correctly configured in the system. Check the access sequence and ensure that the condition types are properly assigned.
Validate Master Data: Check the customer and material master data for completeness and correctness. Ensure that the relevant fields for pricing are filled out correctly.
Analyze Access Sequences: Review the access sequences associated with the condition types to ensure they are set up correctly and that they can access the necessary data.
Check User Authorizations: Ensure that the user has the necessary authorizations to access the pricing conditions. This can be checked with the help of your SAP security team.
Debugging: If the issue persists, consider debugging the pricing determination process to identify where it fails. This may require technical expertise.
Related Information:
VK11
, VK12
, VK13
(Display Condition), and V/06
(Pricing Procedure).If the problem continues after trying these solutions, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP SD/MM modules for further assistance.
Get instant SAP help. Start your 7-day free trial now.
J-138
Enter a strike currency
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
J-137
Valuation of option with underlying (T.form of underly:&) is 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...
J-140
Enter a quotation category
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
J-141
Enter the number of units for the unit-quoted underlying
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.