Skip to Content
avatar image
Former Member

Two Same AET Fields Appear in CRM Production

Hi All,

Currently we have two projects on the client now. We have implementation and support projects.

The implementation is using SAP CRM that has been upgraded.

The project support is still using the older version of CRM SAP as well as the Production system.

The production will be upgraded before the implementation is going live.

Our approach are:

  1. Implementation Development Team use Client CD1 for developing the requirement.
  2. Support Development Team use Client CD2 for developing the requirement and then transport to CRP (production) then Support Team develop again in CD1.
  3. By the time the Implementation is going live all the development object in CD1 will be transported to Prod (including the support object).

These two problems appear when we create AET which the enhancement ID and the field id are generated automatically.

Following the above approaches:

  1. If the support team create field AET 'Deletion Flag' with ID ‘ZZAFLDXXX1’ in CD2 appended in table CRMD_ORDERADM_H and then transported to Production. And they create the same AET in CD1 but with different ID ‘ZZAFLDXX67’ (this is generated automatically) and then when go live, this will be transported as well to the Production.
    So it will be two Deletion flag in CRMD_ORDERADM_H in Production by the time the implementation is going live.

    It will cause inconsistency. The Web UI production will display the new field Deletion Flag (‘ZZAFLDXX67’) to the user.

    Therefore for the transaction made before go live the deletion flag will appear empty though it has been filled before. Because user filled the value on ZZAFLDXXX1.
    Can we avoid this problem without changing the approach? How do we mitigate this problem?
  2. If the implementation team creates the AET where the ID is ‘unfortunately’ the same with AET ID that support team that already transported to Prod, but for different purpose. Example AET created by Implementation team for Payer Code, and AET created by Support Team for Rating Type. Can we avoid this problem? Or how do we mitigate this problem?

Thank You

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers