Release Configuration Change Request
Explanation
Release a configuration change request means that the configuration changes made on the sales order are now
decided to be investigated to see the impact of these configuration changes on the affected supplies in
production.
This investigation step is important in this business flow when the configuration change request status is set
to Released. So the user can investigate if the requested production changes can be done or
not.
Prerequisites
- Configuration change request header must have the status Planned.
System Effects
As a result of this activity,
- The system changes the status of the configuration change request to Released.
- A comparison is performed between the old and new configurations, resulting in a list of affected orders that
the user must review to determine whether the requested production changes can be done,
- Standard Configuration Change Requests: Affected orders are supplies that have already been started and
are affected by the configuration change.
- Simulation Configuration Change Requests: Affected orders include supplies that are started, released, or
unreleased and affected by the configuration change.
- All created affected orders are in the status Pending.
- For Standard Configuration Change Requests,
- it is not possible to edit the configuration on the sales order.
- it is not possible to solve any connected DOP configuration alarm.
- it is not possible to receive a shop order if the sales order used a supply code shop order.
- For Simulation Configuration Change Requests,
- it is not possible to create a new simulation on the sales order.