Requirements for the documentation and checking of routings vary widely depending on the branch of industry and the product. They range from a fairly unrestricted maintenance of routing to detailed planning, documentation, and even strict approval procedures. To meet these requirements, the R/3 System offers various types of routing maintenance described below.
Change master recordsand engineering change hierarchies are part of Engineering Change Management, which is a function in the component of the same name.
If you maintain a routing using history, you always refer to a change master record. You can include change master records in a engineering change hierarchy.
Before you can work with history, you must have created change master records and if necessary engineering change hierarchies.
For more information, see the R/3 Library LO - Engineering Change Management.
Changes that you make to particular fields can be recorded in change documents.
Evaluating Change Documents
A function is available for evaluation, with which you can find change documents for selected groups, routing objects and the person who made the change. You can choose between the following ways of presenting the results.
The system displays the change documents in the order they were created. The administrative data are displayed for each change document (for example, changed by, change on date and validity).
You can also display the changes recorded in each change document. Information is displayed about the edited routing object, the activity carried out (created, changed or deleted) as well as the changed field contents.
The system displays all routing objects that have change documents within the evaluation period. Information is displayed about the object, the activity carried out (created, changed or deleted) as well as the changed field contents. The objects are sorted according to category, that means first all headers are displayed, then material assignments etc.
Working with History
If necessary you can maintain your routings with history. This is particularly useful, if you want to make very complex changes. If you
Every routing object (header, operation etc.) has one and the same change status throughout its whole validity period.
Changes that you make in one routing object are valid for its whole validity period
Evaluating Change Statuses
You can compare the change statuses of selected routings or routings objects. You receive.