Table definitions missing locally while performing remote client copy in sap

[former_member605935]

Hi Experts,

We have done installation some set of tables created in both Quality and Production which contains the same data but the table definitions were not matching.

In Qulaity the table definitions as shown below

K9RHEQ2200006

K9RHEQ2200007

K9RHEQ2200008

K9RHEQ2200009

K9RHEQ2200010

Where as in Produciton the same tables created with the table definition as below

K9RHEP3000001

K9RHEP3000002

K9RHEP3000003

K9RHEP3000004

K9RHEP3000005

While doing client copy remotely in Quality system we are getting the message saying that the "table defiinition missing locally" as the above mentioned table definitions were different in SID's in quality it is "HEQ" where as in Production it is "HEP".

So Kindly suggest how to overcome from this missing table definitions.

Please find the attached screenshots for your reference.

Thanks,

Shiva.

[ACE-SAP]

Hello,

Some CO customizing steps have been performed directly into production & QA systems...

=> thus derivation tables are created in each system with the SID included in table name...

You'll need to create the K9R* tables into your QA system:

Create a transport order in production with the definition of these missing tables (R3TR TABL ...)

1915494  - How to include objects manually into a transport request

Release the order & Import in QA

Restart the copy process

Best regards

116787 - CC-TOPIC: Remote client copy

A remote copy terminates with status "Termination, Dictionary diffs". One or several of the following messages are displayed:
TA 308 Table definition & missing in the target system

              Affected are the tables that were generated in the frame of the Customizing for CO-PA or EC-EIS. That are, for example:
T25xx ; K9R<SId>mmmxxx ; CExxxx ; CExxxx_ACCT ; CExxxx_FLAG
CExxxx_KENC ; T27xx ; T28xx ; CFxxxx

<SId> stands for a system name, mmm for a client, and x is a general placeholder. Examples:
Table definition K9RDEV100001 missing in the target system
Table definition T25B4 missing in the target system

a) Release 4.6: The corresponding Tables T25xx or K9R<SId>mmmxxx exist in the target system (check using Transaction SE11).

b) The tables do not exist in the target system.

20. Generated CO-PA or EC-EIS tables.

a) The appended Preliminary correction no. 364789 solves the problem.

b) Transport the missing Customizing into the systems concerned.

c) Use version management (Transaction SE11) to determine the transport request used to create the tables, and then transport the transport request accordingly.

144015 - CC-INFO: client copy and CO-PA/EC-EIS

The client copy was started without objects for all clients.

The generated data structures for CO-PA/EC-EIS are missing in the target system ( DDIC comparison for remote copy fails).

If you do not wish to do this (for example because the target system is not empty), then proceed as follows:

Transport the missing data structures with the transport options of the application:

    CO-PA: Trans KE3I - Select the operating concerns of the respective client and select all dependent object classes.

    EC-EIS: Trans OKXB - Select the respective aspects for your client and select the dependent objects 'Aspect' and 'Field'.

a) First of all transport the transport requests created into the target system. The orders contain the generated DDIC objects of the respective application.

b) Start the client copy again.

c) If a client transport has already been carried out, the data structures can also be imported into the target system afterwards.

d) CO-PA only: generate the environment for the transported operating concerns using Transaction KEA0.

446279 - Syntax errors or terminations after client copy

[sunny_pahuja2]

Hello,

Remote client copy cannot copy cross client data. So, if there are any changes in the table structure in source and target system then same should be copied to target system manually using transport.

Please also make sure that Support package level of source and target system should be same. Please refer to SAP KBA 1692763 for more information.

Thanks,

Sunny

[former_member605935]

Hi,

How to avoid the below tables from client copy.

K9RHEP3000001

K9RHEP3000002

K9RHEP3000003

K9RHEP3000004

K9RHEP3000005

Thanks

Shiva

[former_member188883]

Hi Shiva,

Please add these tables into the exclusion list using the expert settings under SCC9 in PRD.

Hope this helps.

Regards,

Deepak Kori

[former_member605935]

Dear Deepak,

Thanks, We are doing client copy from PRD to QUA in this situation how this will work.

Thanks,

Siva.

[former_member188883]

Hi Shiva,

In PRD go to SCC9 tcode

Edit -> Expert Settings

Click on Tab "Tables"

Maintain all the tables in this section. Save it.

Now when you start remote client copy the table entries maintained in above section will be excluded from copy.

Hope this helps.

Regards,

Deepak Kori