Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-ECM (Application Component) Engineering Change Management⤷
CC (Package) Engineering Change Management
Basic Data
| Data Element | AENNR |
| Short Description | Change Number |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AENNR | |
| Data Type | CHAR | Character String |
| Length | 12 | |
| Decimal Places | 0 | |
| Output Length | 12 | |
| Value Table | AENR |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | AEN | |
| Default Component name | CHANGE_NO | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Change No. |
| Medium | 15 | Change Number |
| Long | 20 | Change Number |
| Heading | 12 | Change No. |
Documentation
Definition
Number used to uniquely identify a change master record.
Use
If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal:
- The system determines the validity conditions
The conditions that the change is effective under can be defined in the change master record as follows:
- Changes with a date validity (valid-from date)
- Changes with parameter effectivity (for example: serial no. effectivity)
- Log of the changes made
- Documentation of the changes
- Assignment of a revision level to a change state of a material or document
- Release of changes for the different areas in the company
Supplementary Documentation - AENNR 0000
Use
You can simulate the changes that are made with reference to the change number as follows:
- Ineffective change numbers are declared as effective:
- Release key
- The release key of the change master record is simulated as released.
- Effectivity data
- The valid-from date and the effectivity type paramters are not checked. The change number is effective irrespective of the effectivity data.
- Effective change numbers are declared as ineffective.
Procedure
How you proceed depends on what you want to simulate:
- Simulate as effective
Enter both the change number and the Effective indicator.
- Simulate as ineffective
Just enter the change number.
Dependencies
The change number is declared as effective or ineffective depending on the Effective indicator.
Supplementary Documentation - AENNR 0001
Procedure
There are two ways of assigning this number:
- external
You choose a number.
If you want a number in numeric format, it must fall within the number range defined. - internal
The system assigns a number.
You do not make an entry here. If you save the change master, you see a message which tells you which number the system assigned.
Supplementary Documentation - AENNR 0002
Procedure
- Enter the change number which you want to use for editing the BOM.
- If you want to choose a change number via matchcode ID, press function key F4. Choose the ID according to a field you know.
- The system requires an entry in the first field. To search generically, enter "*".
Entry in the other fields is optional. Press ENTER. - You see a list of all the change numbers which fulfil your selection criteria.
- Choose the change number you require by placing the cursor on the line and pressing function key F2.
Supplementary Documentation - AENNR 0007
Procedure
The system determines the number of the change master used to change the BOM.
Supplementary Documentation - AENNR 0008
Procedure
The system determines the change number on the basis of your entries on the initial screen.
Supplementary Documentation - AENNR 4000
Definition
Key that uniquely identifies a change master record or an engineering change order.
Use
When you edit or display a master recipe with reference to a change number, this has the following effects:
- The valid-from date of the change number becomes the key date. This implies the following:
- When you create a recipe, the new recipe is valid from this date.
- When you change a recipe, the system creates a new change status for all affected recipe objects for this date.
- When you display a recipe, the system selects the change status of the recipe that was edited with the change number you have entered.
- All changes that are carried out with a change number are logged in the system.
- You can enter detailed documentation for the changes in the change master record.
- In engineering change orders, you also specify that the recipe is subject to an approval procedure.
Dependencies
- The master recipe does not support change numbers with parameter effectivity.
- Depending on the change rule assigned in the recipe profile, you may only be allowed to edit a master recipe with a change master record or an engineering change order. In addition, a specific change type and thus a specific approval procedure may even be required for engineering change orders.
- To be able to edit a recipe with a change number, the following requirements must be met:
- Certain object types must be defined in the change master record
- Object management records must be defined for certain objects in the engineering change order
The following table shows you which object types/management records you need depending on the data you want to change:
Recipe Data to be Edited Object Types/Management Records Required
All recipe data Task list/master recipe
Production version, Task list/master recipe, BOM
Material list,
Material quantity calculation
and BOM
Exception
When you create a recipe and use internal number assignment, the engineering change record need not contain an object management record for the recipe.
Supplementary Documentation - AENNR 4450
Definition
Key for the change master record or engineering change order that the chosen change status of the recipe object was created with.
Use
Wenn Sie ein Planungsrezept mit Bezug auf eine Änderungsnummer bearbeiten oder anzeigen, hat dies folgende Auswirkungen:
- Das Gültig-ab-Datum der Änderungsnummer übernimmt die Funktion des Stichtags. Das bedeutet:
- Beim Anlegen wird das neue Rezept zu diesem Datum gültig.
- Beim Ändern erzeugt das System zu diesem Datum einen neuen Änderungsstand für die betroffenen Rezeptobjekte.
- Beim Anzeigen selektiert das System den mit dieser Änderungsnummer bearbeiteten Änderungsstand des Rezepts.
- Alle mit Änderungsnummer durchgeführten Änderungen werden protokolliert.
- Sie können die Änderungen im Änderungsstammsatz umfassend dokumentieren.
- Bei Änderungsaufträgen unterwerfen Sie das Rezept zusätzlich einem Genehmigungsverfahren.
History
| Last changed by/on | SAP | 20020827 |
| SAP Release Created in |
