How To Fix OC735 - Default consignment plant & does not exist


SAP Error Message - Details

  • Message type: E = Error

  • Message class: OC - IS-Oil: BDRP Bulk Distribution Requirement Planning messages

  • Message number: 735

  • Message text: Default consignment plant & does not exist

  • 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 OC735 - Default consignment plant & does not exist ?

    The SAP error message OC735, which states "Default consignment plant & does not exist," typically occurs in the context of materials management and inventory management when dealing with consignment stock. This error indicates that the system is unable to find a default consignment plant that has been configured for the material in question.

    Cause:

    1. Missing Configuration: The default consignment plant has not been defined in the system for the material or vendor combination.
    2. Incorrect Master Data: The material master or vendor master data may not be set up correctly, leading to the system not being able to identify the consignment plant.
    3. Plant Deactivation: The plant that was previously set as the default consignment plant may have been deactivated or deleted.
    4. User Authorization: The user may not have the necessary authorizations to access the consignment plant data.

    Solution:

    1. Check Material Master Data:

      • Go to the material master record (transaction code MM03) and check if the consignment plant is correctly assigned.
      • Ensure that the relevant views (like Purchasing and Plant Data) are properly maintained.
    2. Check Vendor Master Data:

      • Use transaction code XK03 to check the vendor master data and ensure that the consignment plant is correctly assigned to the vendor.
    3. Define Default Consignment Plant:

      • If the default consignment plant is not defined, you can set it up in the configuration:
        • Navigate to the following path in SPRO:
          Logistics - General > Material Master > Settings for Key Fields > Define Default Consignment Plant
        • Here, you can define the default consignment plant for the relevant materials.
    4. Check Plant Status:

      • Ensure that the plant is active and has not been marked for deletion or deactivated in the system.
    5. User Authorization:

      • Verify that the user has the necessary authorizations to access the consignment plant data.
    6. Consult Documentation:

      • If the issue persists, consult SAP documentation or reach out to your SAP support team for further assistance.

    Related Information:

    • Transaction Codes: MM03 (Display Material), XK03 (Display Vendor), SPRO (Customizing).
    • Consignment Stock: Understand the concept of consignment stock in SAP, which involves stock that is owned by the vendor but stored at the customer’s location.
    • SAP Notes: Check for any relevant SAP Notes that might address specific issues related to this error message.

    By following these steps, you should be able to identify and resolve the issue related to the OC735 error message in SAP.

    • 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