Reasons for Documenting Changes (SAP Library

Reasons for Documenting Changes

The following table helps you to decide when you should make changes to maintenance task lists with a history and when without.

Reason	y/n	Change type
Do the changes need to be documented?	yes no	With change history, this means with reference to a change master record Without history
Are there legal requirements for a change history?	yes no	With change history, this means with reference to a change master record Without history

Answer the following questions to decide whether an existing change number is suitable for your requirements and can be assigned to a maintenance task list:

What object types or objects are changed owing to this change number?
What validity period has been set?
Why do the changes have to be made?

If no existing change number is suitable, you create a new change master record.