How To Fix CONVERT_OTC058 - Condition type Customizing missing for company code &1, transaction &2


SAP Error Message - Details

  • Message type: E = Error

  • Message class: CONVERT_OTC - Conversion of OTC Interest Rate Instruments

  • Message number: 058

  • Message text: Condition type Customizing missing for company code &1, transaction &2

  • Show details Hide details


  • 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 CONVERT_OTC058 - Condition type Customizing missing for company code &1, transaction &2 ?

    The SAP error message CONVERT_OTC058 indicates that there is a missing condition type configuration for a specific company code and transaction. This error typically arises during the processing of pricing or condition records in the SAP system, particularly in the context of sales and distribution (SD) or materials management (MM).

    Cause:

    1. Missing Customizing Entries: The condition type that is being referenced in the transaction is not defined or configured in the system for the specified company code.
    2. Incorrect Configuration: The condition type may exist, but it might not be properly assigned to the relevant pricing procedure or may not be active for the specified company code.
    3. Transport Issues: If the configuration was recently transported from another system (e.g., development to production), it may not have been transported correctly or completely.

    Solution:

    1. Check Condition Type Configuration:

      • Go to the SAP Customizing Implementation Guide (SPRO).
      • Navigate to Sales and Distribution or Materials Management (depending on the context).
      • Check the configuration for Pricing and ensure that the condition type in question is defined for the relevant company code.
      • Ensure that the condition type is assigned to the appropriate pricing procedure.
    2. Assign Condition Type to Pricing Procedure:

      • If the condition type exists but is not assigned, you can assign it to the relevant pricing procedure.
      • Ensure that the condition type is active and has the correct settings (e.g., calculation type, access sequence).
    3. Check for Transport Issues:

      • If the configuration was recently transported, verify that all necessary transport requests were successfully imported.
      • Check for any missing entries in the target system that may have been overlooked during the transport process.
    4. Consult Documentation:

      • Review any documentation or notes related to the specific condition type and its configuration to ensure compliance with business requirements.
    5. Testing:

      • After making the necessary changes, perform tests to ensure that the error no longer occurs and that the pricing is calculated correctly.

    Related Information:

    • Transaction Codes: You may need to use transaction codes like VK11 (Create Condition), VK12 (Change Condition), or VK13 (Display Condition) to manage condition records.
    • Debugging: If the issue persists, consider using the debugger to trace the pricing procedure and identify where the error is occurring.
    • SAP Notes: Check SAP Notes for any known issues or patches related to the specific condition type or error message.

    By following these steps, you should be able to resolve the CONVERT_OTC058 error and ensure that the necessary condition types are properly configured in your SAP system.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker