cancel
Showing results for 
Search instead for 
Did you mean: 

Client export and import

Former Member
0 Kudos

1.Can we import a client which is exported into another system which is not in the same transport group?

2. If yes ,how it is imported?

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Thanks

Former Member
0 Kudos

Hey,

The technical procedure describe, is the right one,

however, this might fails, if the system workbench are different.

There are several reasons for this,

for example:

CUSTOMIZATION problems:

1. If you are exporting a CR with customization of ECC process,

you will not be able to import the CR into an CRM system, due to the

fact that the customization table does not exist in the CRM.

2. If you are exporting a CR with customization of ECC 6 process,

sometimes, you will not be able to import the CR into an R3 4.6 system, due to the fact that the customization table might changed from version 4.6 to ECC 6.

Developing problems:

3. If you are exporting a CR with function module (FM),

the CR will fail in the target system, if the FUGR of this FM does not exist in the target (same result in REPORT and PACKAGE instead of FM and FUGR).

4. If you are exporting a CR with function module 1 (FM) that call FM 2, but the CR contains only FM 1, than of the import in the target system will work, but when you use FM1 in the target system, you would be a dump, FM2 does not exist.

5. If you are exporting a CR with report which reads from table Z1,

the CR will fail at activation phase in the target system, if the table Z1 does not exist.

To summarize all this information:

1. CR with customization data, the tables of the customization must exist in the target system, and with the same structure,

in this case, avoid transporting from different system (for example ECC to CRM) and different version (for example 4.7 and ECC 5).

2. CR with develop object, should include all the object that needs to be transfered, FUGR, PACKAGE, TABLE and etc.

in case of missing objects, the import would fail (or you will get runtime errors, such as function module does not exist)

I hope I was clear,

in case you need clarification,

feel free to ask...

Good luck.

p.s

points would be appreciated... 😄

Former Member
0 Kudos

Thank you Shani

Former Member
0 Kudos

Hi sanjeeva,

take the data and cofile of the exportet transport (/usr/sap/trans) and move it on the transport directory of the system you wanted to import the client in.

Create the new client in transaction scc4.

After that go to STMS and open the queue of your system. Add the copied transport to the importqueue. (somewhere under utilities, don't have a system right here to have a look).

Than import the transport.

(Another way would be to use the remote client copy.)

Bye

Frank

Former Member
0 Kudos

Thank you Frank