E - 20200703 - FAQ About ECM

Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

2020-07-03 1252123

1252123 - FAQ: Frequently asked questions about


Engineering Change Mng
Version 1 Type SAP Note
Language English Master Language English
Priority Recommendations / Additional Info Category FAQ
Release Status Released for Customer Released On 16.09.2009
Component LO-ECH ( Engineering Change Management )

Please find the original document at https://launchpad.support.sap.com/#/notes/ 1252123

Symptom

1. Why can't I create a change number with release key for certain objects?

2. What User exits or BAdi's are released and available in Engineering


Change management to use?

3. Is there an undo-transaction for master data changes?

4. Does CCUNDO support undo functionality for routings?

5. How do I identify performance problems related to the change master?

6. Why do I get an update termination when creating or changing a change


number?

7. I changed a BOM with a change number and afterwards I take the change
back with the same. I cannot delete the change number afterwards, as it is
still in use in the BOM. What do I have to do to delete the change number?

8. In CC03 - reporting - all changes - BOM TAB the layout has changed - how
do I change back to the old layout?

9. How to increase the revision level size?

Other Terms

change number , ECO , ECR ,ECH , ECM

Reason and Prerequisites

Solution

1. Why can't I create a change number with release key for certain object
type?

The note 159414 states that the function ' release key' in general is not used
for all of the objects types implemented in the system.

Only the following objects types support release key :

• Bill of material

• Routing

• Reference operation set

© 2020 SAP SE or an SAP affiliate company. All rights reserved 1 of 3


2020-07-03 1252123

• Characteristic

• Characts of class

• Classification

• Validity of Material Version

• PVS Variant

• PVS Mode

• PVS Dependency

Note 159414 identifies a MODIFICATION that you can implement to allow the
selection of all other object types for a change number with a release key.

Keep in mind, this allows you to add objects of these type to the ECM. It does
NOT provide the release key functionality for those other object types. They
will become effective on the validity date of the ECM, regardless of the release
key status.

2. What User exits or BAdIs are released and available in Engineering Change
management to use?

The following user exits are available:

• PCCD0001 Customer field in the change master

• PCCD0002 Check of the values of parameter effectivity

• PCCD0003 Check when setting a system status

• PCCD0004 Check before setting the change number

• PCCD0005 Check at initial screen

• PCCD0006 Parameter effectivity: Format effectivity output control

BAdIs :

• ECM_EXIT Engineering Change Management customers exits

• REV_SELECT Revision Selection

• ECM_UPDATE Maintain Engineering Change Management master data

• ECM_UNDO Undo Changes

• ECM_AEOI_CI Change Mgmt: Customer Fields for Object Management Record

For more information about their use please refer to the documentation in SMOD
and SE18.

3. Is there an UNDO-transaction for master data changes?

Yes there is. Starting with software release SAP_APPL 600 you can use CCUNDO.

4. Does CCUNDO support undo functionality for routings?

CUNDO does not support undo functionality for routings.

5. How do I solve performance problems related to change numbers ?

© 2020 SAP SE or an SAP affiliate company. All rights reserved 2 of 3


2020-07-03 1252123

Performance problems relating to changes numbers are usually caused by the


object they are assigned to. They usually occur when performing a date shift.

You should check the applications, where the change number is assigned to. Go to
CC03, menu "Environment", "All Changes". Here you get an overview about all
assigned objects which have been changed. This can give you an idea about which
applications have to be checked for performance improvements.

Please check the notes 429146 ,579851 , 387365 , 534542, 1224528, 514788,
1012624, 540360, 413565, 621338, 621338 , 691526

6. Why do I get an update termination when creating or changing a change


number?

There are 2 known reasons why this termination can occur:

• Inconsistency in table AENR/AENV/AEOI with a blank key value for AENNR.

Applying the note 964638 should avoid future inconsistencies. The note 964638
also provides 2 report to delete entries from AENR and AENV where there is an
initial value for AENNR.

• No logical system is maintained.

You can set the logical system in transaction SCC5. There you can check to see
if the logical system has been maintained If no logical system is defined then
this could be the reason why you are receiving the Express document termination.

7. I changed a BOM with a change number and afterwards I take the change
back with the same. I cannot delete the change number afterwards, as it is
still in use in the BOM. What do I have to do to delete the change number?

You have created so called dead items. To remove them please refer to the note
215970. Afterwards the change number can be deleted.

8. In the reporting option - "All Changes" - BOM TAB the layout has changed.
How do I change back to the old layout?

For accessibility reasons in Release 500 and onwards the classical report view
that you seen on your system has been replaced by an ALV display. The setting
cannot be changed back.

9. How do I increase the size of the revision level field?

The original revison level, reporting master data changes for material masters
and document information records comes from the engineering change management
(AEOI-REVLV). The deep integration of the revison level in master data mangement
and follow up processes does not allow to change the field lenght, as there are
too much dependencies over all the applications which work with it.

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2020 SAP SE or an SAP affiliate company. All rights reserved 3 of 3

You might also like