History Requirement and Object Type
There is a history requirement for most change objects.
When you have edited a change object with reference to a change number, you can only edit these objects subsequently with reference to a change number.
When you have edited a change object with reference to a change number, you can edit these objects susequently even without reference to a change number. However, this may lead to gaps in the documentation of your change objects.
Object Type and History Requirement
Object Type With History Requirement |
Object Type Without History Requirement |
BOM Characteristics Characteristics of Class Classification Object dependencies Configuration profiles Contents of a variant table Substances Phases Dangerous goods |
Task lists Materials
|
Note for BOMs
With authorization object C_STUE_NOH you can change BOMs that have already been edited with reference to a change number without a change number.
For the authorization object C_STUE_NOH you should maintain the field NOHIS (authorization to edit BOMs without change number). To assign this authorization, enter the value X.
We advise you to only assign this authorization to change BOMs without a change number in exceptional cases. Otherwise, there may be gaps in the documentation of your changes to BOMs.
Note for Documents
The change number for documents is maintained in the document info record. No data records for effectivity periods are created dependently of the change number.