How To Fix MD658 - Enter order type


SAP Error Message - Details

  • Message type: E = Error

  • Message class: MD - Material Requirements Planning (MRP)

  • Message number: 658

  • Message text: Enter order type

  • Show details Hide details
  • What causes this issue?

    You have not specified the planned order profile. The system is not
    able to determine the order type if a planned order profile is not
    specified.

    System Response

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    How to fix this error?

    Please specify an appropriate planned order profile.

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message MD658 - Enter order type ?

    The SAP error message MD658 "Enter order type" typically occurs in the context of production planning and control, particularly when working with production orders or related transactions. This error indicates that the system requires an order type to be specified, but it has not been provided in the relevant field.

    Cause:

    1. Missing Order Type: The most common cause of this error is that the user has not entered an order type in the relevant field when trying to create or process a production order.
    2. Configuration Issues: There may be configuration issues in the system that prevent the order type from being recognized or displayed.
    3. User Input Error: The user may have overlooked the order type field or entered it incorrectly.

    Solution:

    1. Enter Order Type: The immediate solution is to ensure that you enter a valid order type in the specified field. This can usually be done in the transaction where the error occurs (e.g., creating a production order).
    2. Check Configuration: If the order type is not available or you are unsure which order type to use, check the configuration settings in the SAP system. This can be done by:
      • Navigating to the configuration settings for order types in the SAP IMG (Implementation Guide).
      • Ensuring that the necessary order types are defined and active for the relevant plant and production processes.
    3. User Training: If users frequently encounter this error, consider providing additional training on the relevant transactions and the importance of entering the order type.
    4. Consult Documentation: Review SAP documentation or help files related to production orders to understand the required fields and their significance.

    Related Information:

    • Transaction Codes: The error may occur in various transaction codes related to production orders, such as CO01 (Create Production Order), CO02 (Change Production Order), or CO03 (Display Production Order).
    • Order Types: Different order types (e.g., standard, repetitive, or special orders) have specific configurations and implications for production planning. Familiarize yourself with the order types relevant to your organization.
    • SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address underlying issues.

    If the problem persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in production planning.

    • 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:
  • MD657 Planned order & exists
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

  • MD656 Planning scenario & does not exist
    What causes this issue? Specified planning scenario does not exist.System Response The system issues an error message and will not allow you to cont...

  • MD659 Enter a planning plant
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

  • MD660 There is a conflict in the import parameters.
    What causes this issue? Import parameters contain a conflict. Planned order specified in the header data (EPLAF) is different from the target planned...

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant