How To Fix 6E123 - Planned record not reset

6E123 - Overview

• Message type: E = Error

• Message class: 6E - Messages for EMU currency conversion in Treasury

• Message number: 123

• Message text: Planned record not reset

What causes this issue?

INCLUDE TRLO_EMU_BEPP_KEY OBJECT DOKU ID TX
The planned record cannot be reset, since the original data is not
available.

System Response

Processing is terminated.

How to fix this error?

Delete the planned record. Repeat the reset of the changeover and then
enter the planned record again.

Error message extract from SAP system. Copyright SAP SE.

6E123 - Details

• The SAP error message 6E123: Planned record not reset typically occurs in the context of production planning and control, particularly when dealing with planned orders or production orders. This error indicates that there is an issue with resetting a planned record, which can be due to various reasons.
  Causes:
  
  Existing Dependent Requirements: If there are dependent requirements (like reservations or dependent demand) linked to the planned order, the system may prevent the reset.
  Status of the Planned Order: The planned order may be in a status that does not allow it to be reset (e.g., if it has already been converted to a production order).
  Locking Issues: The planned order might be locked by another user or process, preventing changes.
  
  Configuration Issues: There may be configuration settings in the system that restrict the resetting of planned orders under certain conditions.
  
  Solutions:
  
  Check Dependencies: Review any dependent requirements associated with the planned order. If there are reservations or