Hierarchy
⤷ CRM-CIC (Application Component) Interaction Center WinClient
⤷ CPC (Package) R/3 Application Development: PP Task Lists Master Recipes
Basic Data
Data Element | R_CHRULE |
Short Description | Change rule |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | R_CHRULE | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | CHANGE_RULE | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | ChngeRule |
Medium | 15 | Change rule |
Long | 20 | Change rule |
Heading | 2 | CR |
Documentation
Definition
Key that specifies which change procedure must be used for recipe or inspection plan editing.
Use
Using the change rule, you can define the following restrictions for editing:
- Change master record required
Here, you create a new change status on the valid-from date of the change master record. The changes are logged and can be documented in the change master record.
Exception:
There is only one change status for production versions. You specify this status when you edit production versions.
- Engineering change order required
If you choose this option, you specify that all changes must follow a detailed approval procedure. The functionality of the change master record also applies to the engineering change order.
- Engineering change order with specific change type required
You assign the change type to the object management record of the corresponding recipe or inspection plan in the change order. In this way, you specify a user-defined approval procedure as well as a specfic workflow.
Note
- You cannot use change master records or change orders with parameter effectivity in the master recipe.
- The change rule does not apply to bills of material of phantom assemblies. For this reason, do not use phantom assemblies in recipes requiring approval.
Dependencies
- If a change rule has been assigned in the recipe profile, you must follow this rule when your create the master recipe or inspection plan. This means that you must use a change number that complies with the change rule or restricts changes even more.
- You can replace the change rule assigned in the profile with a more restrictive change rule in the recipe header or inspection plan header but never with a less restrictive one.
You cannot change the change rule in the recipe profile from within recipe or task list maintenance.
History
Last changed by/on | SAP | 19991209 |
SAP Release Created in |