O file not created during client export

[Syamkriz]

Hi,

We are doing client copy via client export import.We used SAP_ALL client copy profile. We were expecting 3 files O,T and X . But we got only 2 files T and X. We checked at the OS level , and client copy logs SCC3. SCC3 shows only two transport request created and OS level has only 2 set of files.

Where is transport request O and its files?

Then we proceed and did the import in target client. But import error happened, it showed import stopped because of ztable were missing from nametab. how to proceed the import? Without solving the O file problem we cannot do the import ?

Thanks and Regards

Syam

Edited by: Syam on May 31, 2010 2:59 PM

[Former Member · Accepted solution]

Hi Syam,

Have you performed a test run with a remote comparison before the export? Both ABAP dictionaries should be the same, otherwise you cannot import... For example: if you have a Z_TEST table on your source, but not on your target system, your import will fail.

In case you want to exclude tables from your CC, you can do this via report RSCCEXPT.

That you have 2 transports instead of 3 doesn't have to be any problem.

Kind regards,

Mark

[Syamkriz · Accepted solution]

Mark,

Thanks for the reply. Points added.

Hi All,

By this time we had found that there are some missing zobjects in source.

But we need to import them. We tried creating a transport request and include the ztable in the transport request.

But we have to know the package in which ztable belongs to . Do you have any idea how to find out the package in which ztable belongs to ?

Thanks and Regards

Syam

[Syamkriz · Accepted solution]

Hi All,

We are trying another solution, but it takes time. .

We are doing the export once again using SAP_EXPA profile. We expect this will bring O also. And we expect all the cross client datas will also get exported.

Could you please let me know your opinion on what we are doing

Thanks

Syam

[Former Member · Accepted solution]

The package to which a table belongs is shown in transaction se11 -> table name -> attributes.

Kind regards,

Mark

[Syamkriz · Accepted solution]

Mark,

Thank you. Points provided.

Hi All,

Client copy completed.

The SAP_EXPA worked fine, and we got O files also as a result. But we did not follow that method because we did not want to affect the system availability and data consistency of the other clients in the same SAP instance. Hence O file import is not done. We transported the missing ztables to target system. We manually created the transport request using se03. Still we had problem while running scc7 after import. For this we used Note 1235955 after post processing

Thanks and Regards

Syam