Kontakt

Ansicht
Dokumentation

New functions for release procedure ( RELNPP_BD_40C_AENRK )

New functions for release procedure ( RELNPP_BD_40C_AENRK )

PERFORM Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

New functions for release procedure

Description

Change objects

Up until now you could only process BOMs with reference to a change number if the release procedure was controlled by a release key.
As of this release, you can also process the following objects:

  • Task list types:
  • Routings

  • Reference operation sets

  • Characteristics
  • Characteristics of class
  • Classification

Defining the release key

In Customizing, you can define the release key that controls the release procedure more precisely.

  • Release for enterprise areas
Up until now, you could use the release key to release the object changes either globally or not at all
As of this release, you can define release keys that allow you to release object changes for the following areas:
  • Costing

  • Planning

  • Production

  • Simulation for production

You can use this indicator to ensure that the changes are also taken into account in the production simulation.
This simulation allows you to check new developments or changes in simulation orders for production. For example, you receive early information about whether all the changed data (for example, BOM, task list, document) fits together.
  • Late transferral of changes
If you have to adapt production orders to changed basic data, you can check the effects of the basic data changes by using order change management (Order Change Management) and transfer the changes to production orders.
You use the following indicators to ensure that a change flag is automatically created for order change management:
  • Release key creates flag for order change management (OCM)

  • Date shift creates flag for order change management(OCM)

Processing a change master record after release

Under the control data in Customizing, you can define whether change numbers that have already been released for one or more areas should be locked. After the lock, you can only process the release key and the deletion flag.

Releasing a change hierarchy

Changes in a change hierarchy are released after additional checks.

  • Technical release of packages
The superior change master (leading change master record) can only be released globally or for production if all the change master records assigned to it (change packages) have been technically released.
You can release a package technically as follows: Edit -> Technical release. The system sets the Technical release indicator on the Change header screen.
  • Late assignment of a package after release
In the standard system you cannot add any more packages after you have released the change leader for production.
If you want to assign a package at a later stage, you can set the Late packages allowed indicator in the control data of Customizing.
The following activities are supported:
  • When you assign a package to a change leader that has already been released, you receive a warning message since the changes in this change hierarchy may have already been taken into account in production.

  • You can release the change leader for production even if not all the assigned packages have been technically released.

  • Defining a change as a basic change
You can define changes in a change hierarchy where the change leader determines effectivity by the valid-from date as basic changes that are always valid. All changes in this change hierarchy are always taken to be valid irrespective of the valid-from date.
This function is only active if the following conditions are met:
  • The Function for basic change is active indicator is set in the control data in Customizing.

  • The change leader has been released for production with the release key.

You can define a basic change by choosing Edit -> Define basic change in the change leader.
The system replaces the valid-from date on the Change header screen with the term Basic change.
You can then no longer have any late packages for these change leaders.

Effects on ECR/ECOs

There are additional checks for change master rceords with this function:

  • Change order with release key
When you maintain a change order with a release key, you can only release the changes globally or for production if the Release ECO system status is set.
  • ECO in change hierarchy
You can link an ECO into a change hierarchy as a change package. The system technically releases these orders automatically as soon as you set the Release ECO system status for the package. The system sets the Technical release indicator on the Change header screen.
  • ECOs as late packages
You can assign further change packages that have been created as ECOs even after the change leader has been released. To be able to do this, you must have set the Late packages allowed indicator in the control data in Customizing.

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

You can make the required settings in the following work steps:

Set up control data

Define release key

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

You can find further information on order change management (OCM) in the release information Engineering Change Management for Production Orders.






General Material Data   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 8209 Date: 20240523 Time: 043111     sap01-206 ( 98 ms )