SAP Client Copy and Transport Issue

[Former Member]

Hi All,

Brief information about our PRD and QAS system:

- SAP: SAP ECC 6.0 EHP5.

- DB: MS SQL 2008 R2 (Ver 10.50).

- OS: Windows Server 2008 R2.Standard (64 bits).

- SAPGUI 7.20

We had performed a client copy from PRD to QAS recently via method of export/import with SAP_ALL profile. The process was completed OK, no problem.

We've several clients in QAS system. When we logon to QAS client which had been refreshed with PRD, we found some of the configs/objects which had been transported to QAS prior client copy had went missing.

How can we rectify this issue?

Any better method to perform client copy and preserve the transport data?

Appreciate for you help and advise.

Thank you.

- Peter

[Former Member · Accepted solution]

Hi Peter

You need to apply all the transports into the QAS system which were moved to QAS system prior to the client copy , but which were not moved into PROD system ..

Simple way to find the list :

Login to PROD system and check the Import Queue

( All the transports which are in INIT Status there are the TR's that have moved into QAS but not into PROD )

You need to re-import them back into the QAS system

hope it helps

Thanks

Rishi

[Former Member · Accepted solution]

This message was moderated.

[Former Member · Accepted solution]

Hi Sudhir,

You need to check the import queue to get the list.

Generally the process followed is before doing the client referesh from PRD to QAS we need to get the transport list which is imported until QAS so that after PRD client refresh we can import the transport request.

It will be easier when compared to checking the request from PRD systems.

REgards,

Raja. G

[Former Member · Accepted solution]

Hi Peter

in the PROD system , go to STMS_IMPORT  Transaction , there you can see the transports which are in the queue.

Filter the queue based on the INIT status .

Thanks

Rishi

[Former Member · Accepted solution]

This message was moderated.

[Former Member]

Hi All,

Thanks for your responses.

I'm aware we can extract the transport information from E070 table or STMS transport history.

However, sometimes, there are a few transports which have dependencies and need to be released in certain sequence.

What is the best way to handle it in order to have an accurate information on the transports released to QAS only?

Thanks.

- Peter

[Former Member]

Hi Peter

To cater to the dependencies , the best way is to get the transports from the Import history of the QAS system.

The reason being - the TR's must have been originally moved to the QAS system in the required sequence.

hence the re-importing of the TR ( post client copy ) should happen in the same way it was originally imported.

Thanks

RD

[former_member45419]

Hi peter,

check below thread,

http://scn.sap.com/thread/1887972

Regards

Nayeem

[Former Member]

Hi Nayeem,

Thanks for your reply, but the article you've provided is more related to BW and Infotypes issue. It's not related to my issue.

Thanks.

- Peter

[Former Member]

Hi Rishi,

Thanks for your response.

"You need to apply all the transports into the QAS system which were moved to QAS system prior to the client copy , but which were not moved into PROD system"

I agree with you on this point and I do know how to perfom it, however, it'll be very troublesome to re-apply all the transports which were released to QAS system prior client copy considering our frequent development, testing and customizing.

Is there a better way?

Thanks.

- Peter

[Former Member]

Hi Peter

You can simply take out the list from the PROD System STMS queue.. I have replied above on how to take out the TR list ..

Once you have the transport list , then you can mass import them using tp import script at the OS level ..

Let me know if you are able to get the list of TR's.

Thanks

Rishi

[Former Member]

Hi Peter,

I dont think any better way. Maybe you can carefully select your client copy profiles so that only Application data will be transferred from PRD to QAS instead of SAP_ALL profile.

Regards,

Raja. G

[Former Member]

Hi Rishi,

Thanks for your response.

Yes, I know we can mass re-import those affected transports using a batch script on OS level.

However, I'm looking for more efficient way of performing a client copy without the need to re-import.

Is there any other option?

Thanks.

- Peter

[Former Member]

Hi Peter

Not sure if there is a process in which transport import can be avoided after a client copy..

Even if you use other profiles like SAP_APPX ( which I have been using in my projects ) - then also transport imports would be needed..

Maybe you can raise a SAP OSS Message ..

Thanks

Rishi

[Former Member]

Hi Rishi,

Thanks for your reply.

I'm not sure if I can raise OSS as it's more related to consulting rather than bug.

Thanks.

- Peter

[Former Member]

Hi Raja,

Thanks for your reply.

Which other profile that could used without affecting the transport?

Thanks.

- Peter

[Former Member]

Hi Peter

Understand your point . But I think at times you need to do what you have go to do ! ! ..

I have not come across any options which could avoid the situation of transport re-import post remote client copy from PRD to QAS , so this I think can be raised as a query to SAP..

Thanks

Rishi