New value field not updated in production even after using KE3I

[Former Member]

Dear Experts,

We have an issue with new value field creation in DEV server and transport to PRD server. Earlier, some one has created new value field in DEV server and moved it to QA and tested successfully. It was pending for long time and now we would like to bring the same value field to PRD server. I have checked the same value field in DEV server and regenerated the Operating concern. Later, in KE3I - selected "Operating Concern" and executed with workbench and customized requests.

Later, in SE10, released the TRs and basis team moved the same to QA and PRD server. But when I check the same PRD server, the new value field is not updated.

We are with ECC6.0 and not regenerated Operating concern in PRD server.

Is it required to regenerate the "Operating concer" in PRD server once we move the TR from DEV server.

Pls help us why the new value field is not updated in PRD server?

Best Regards

[Former Member · Accepted solution]

Hi,

Manually create value field in production system and bring the KE4I settings to production system through TP and re generate the operating concern in production system.

So that it will update and appear in all the copa reports and transactions,  or other wise your dev, qas and prd operating concern should be sync to bring the value fields through TP.

Regards,

Ravi.

[Former Member · Accepted solution]

Hi Ravi,

Thanks for your immediate response. But in my case I dont want to create the value field in production system. Its already created in DEV server and transported to QA successfully. Now, I want to transport it to PRD server through KE3I.

After moving TR from DEV to QA and PRD, its not updated in live system. My question is Do I need to regenerate KEA0 to update the new value field in the live system. Is it feasible and will not create any problem if I regnerate Operating Concern in PRD server? Will it not update new value fields creation in ECC6.0 directly without regenerating "Operating Concern"?

Pls advice....

Best Regards

[former_member207505]

Please see the SAP Note 131664 regarding the use
transaction KE3I to transport operating concern structures.

  In principle you can transport a new value field with a transport of
an operating concern - part 'Structures: ABAP Repository objects'
in transaction KE3I.

  You need to perform the following steps:
1. Value field added in source system thro tcode KEA6
2. Regenerate the environment of operating concern in source system
(tcode KEA0)
3. Transport using KE3I (select: ABAP repository objects)
4. Regenerate the environment of operating concern in target system.

In this issue, it seems that you have not regenerated your Operating concern. please

try to regenerate your operating concern after the transport in T-cd:KEA0.

By the way, please also refer to the following information:

Via transaction code KE3I you have the option to transport
specific object classes.  If you select 'Structures: ABAP Repository
objects' the following settings are transported:
Cross-client objects in the SAP Repositiory
- Tables and structures of the operating concern (CE1xxxx - CE8xxxx)
- Domains and data elements for CO-PA characteristics
- Master data tables for CO-PA characteristics (without data)
Cross-client control tables
- CO-PA field catalog
- View directory

Normally we advise customer to add a new value field/characteristic to
DEV then transport to QAS and then transport to PRD. This ensures that
the operating concerns in the 3 systems are in sync.

Thanks and best regards,

Ronghua

[Former Member]

Hi Ronghua,

Thanks for your inputs. I will try to regenerate operating concern in PRD server.

Best Regards

[Former Member]

You can regenerate the operating concern in production server, for this the client should be open.

Talk to your basis guy to open the client and then re generate the same, it is better to re generate in off business hours.

Regards,

Ravi.

[Former Member]

Hi Ravi,

Thanks for your reply. I will check it and come back.

Best Regards

[Former Member]

Hi Ravi,

The issue has been resolved.

thanks for your help.

Regards