How To Fix CRM_MKTPF_PFMERK059 - Number of decimal places will be corrected

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_MKTPF_PFMERK - Messages for Online Attribute Maintenance

• Message number: 059

• Message text: Number of decimal places will be corrected

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 CRM_MKTPF_PFMERK059 - Number of decimal places will be corrected ?

  The SAP error message CRM_MKTPF_PFMERK059 indicates that there is an issue with the number of decimal places in a pricing or financial context within the SAP CRM system. This error typically arises when the number of decimal places defined for a particular field does not match the expected or required format for processing.
  Cause:
  
  Mismatch in Decimal Places: The error usually occurs when the number of decimal places for a currency or quantity field does not align with the settings defined in the system or the configuration of the relevant pricing procedure.
  Configuration Issues: There may be inconsistencies in the configuration of the pricing procedure, condition types, or master data (like material or customer master records) that lead to this error.
  Data Entry Errors: Manual data entry errors where the user inputs a value with an incorrect number of decimal places can also trigger this message.
  
  Solution:
  
  
  Check Configuration:
  
  Review the configuration of the pricing procedure in the SAP system. Ensure that the number of decimal places for the relevant condition types is set correctly.
  Check the settings in the transaction code SPRO under Sales and Distribution > Basic Functions > Pricing > Pricing Control.
  
  
  
  Review Master Data:
  
  Inspect the master data for the materials or customers involved in the transaction. Ensure that the decimal places for the relevant fields are correctly defined.
  Use transaction codes like MM03 (Material Master) or XD03 (Customer Master) to check the details.
  
  
  
  Data Validation:
  
  Validate the data being entered in the transaction. Ensure that the values conform to the expected number of decimal places as defined in the system.
  If the error occurs during a specific transaction, review the input values for any discrepancies.
  
  
  
  Adjust User Input:
  
  If the error is due to user input, instruct users to enter values with the correct number of decimal places as per the system's requirements.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific details on the error message and any additional troubleshooting steps.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) for managing pricing conditions.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for relevant notes in the SAP Support Portal.
  Testing: After making changes, conduct thorough testing to ensure that the issue is resolved and that no new issues arise from the adjustments.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.