How To Fix ME663 - Planning and SA release in APO requires different confirm. control key

SAP Error Message - Details

• Message type: E = Error

• Message class: ME - Purchasing: General Messages

• Message number: 663

• Message text: Planning and SA release in APO requires different confirm. control key

What causes this issue?

The confirmation control key used in the scheduling agreement and the
setting of the <LS>External Planning</> indicator are mutually
exclusive.,,,,,,,,

System Response

If you have stipulated planning and release creation in APO, you must
use a confirmation control key that satisfies the following criteria if
it is to be taken into account in MRP:
You may only use a confirmation category (internal confirmation
category <LS>2</> - <LS>inbound delivery</>) that is MRP-relevant
All other confirmation categories (e.g. AB, LA) of this confirmation
control key must not be MRP-relevant (i.e. they are for information
only)

How to fix this error?

Check your input and, if necessary, use a different confirmation
control key.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ME663 - Planning and SA release in APO requires different confirm. control key ?

  The SAP error message ME663 indicates that there is a mismatch in the confirmation control keys between the planning and the release in the Advanced Planning and Optimization (APO) module. This typically occurs when the system is trying to process a planned order or a production order, and the confirmation control key defined in the planning data does not match the one defined in the release data.
  Cause:
  
  Mismatch in Confirmation Control Keys: The confirmation control key used in the planning phase is different from the one used in the release phase. This can happen if the order was created with one control key and then modified or released with another.
  Configuration Issues: There may be configuration settings in the APO or the ERP system that are not aligned, leading to this inconsistency.
  Master Data Issues: The material master or the production version may have different confirmation control keys set up, causing the error when trying to process the order.
  
  Solution:
  
  
  Check Confirmation Control Keys:
  
  Go to the relevant order (planned or production) and check the confirmation control key settings.
  Ensure that the confirmation control key in the planning data matches the one in the release data.
  
  
  
  Adjust Configuration:
  
  If the keys are supposed to be different, review the configuration settings in the APO and ERP systems to ensure they are set up correctly.
  You may need to consult with your SAP Basis or configuration team to align the settings.
  
  
  
  Review Master Data:
  
  Check the material master data and production version settings to ensure that the confirmation control keys are consistent across all relevant data.
  Make any necessary adjustments to the master data to ensure consistency.
  
  
  
  Recreate Orders:
  
  If the orders are significantly misconfigured, it may be easier to delete the problematic orders and recreate them with the correct settings.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to ME663 for any specific guidance or updates that may apply to your version of SAP.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like MD04 (Stock/Requirements List) or CO02 (Change Production Order) to check the details of the orders.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  User Exits and BAdIs: If custom logic is involved, review any user exits or BAdIs that might affect the confirmation control key settings.
  
  By following these steps, you should be able to identify the cause of the ME663 error and implement a solution to resolve it.