Problems with client dependet transports

[Former Member]

Hello!

My transport system landscape looks as follows:

SRM:000 (DEV)

SRM:001 (QAS)

SRM:100 (PRD)

Transport routes:

SAP: 000 --> 001

ZSRM: 000 --> 001

Delivery: 001 --> 100

I would like to copy or create some role from PFCG, let's say Z_test and tranport these role firstly to QAS client and then to PRD client.

When I tranport this role I get the error:

AGR_1016 table class is 'C'. Entries are only imported to client '000'.

AGR_1016B table class is 'C'. Entries are only imported to client '000'.

AGR_PROF table class is 'C'. Entries are only imported to client '000'.

AGR_USERT table class is 'C'. Entries are only imported to client '000'.

AGR_TIMEB table class is 'C'. Entries are only imported to client '000'.

Main import

End date and time : 20071115141115

Ended with return code: ===> 8 <===

<b>What is here the problem?

which request typ is that? (WB or Customizing)?</b>

Thank you very much!

regards

Thom

[Former Member]

Hello!

My transport system landscape looks as follows:

SRM:000 (DEV)

SRM:001 (QAS)

SRM:100 (PRD)

Transport routes:

SAP: 000 --> 001

ZSRM: 000 --> 001

Delivery: 001 --> 100

I would like to copy or create some role from PFCG, let's say Z_test and tranport these role firstly to QAS client and then to PRD client.

When I tranport this role I get the error:

AGR_1016 table class is 'C'. Entries are only imported to client '000'.

AGR_1016B table class is 'C'. Entries are only imported to client '000'.

AGR_PROF table class is 'C'. Entries are only imported to client '000'.

AGR_USERT table class is 'C'. Entries are only imported to client '000'.

AGR_TIMEB table class is 'C'. Entries are only imported to client '000'.

Main import

End date and time : 20071115141115

Ended with return code: ===> 8 <===

<b>What is here the problem?

which request typ is that? (WB or Customizing)?</b>

Thank you very much!

regards

Thom

[uwe_schieferstein]

Hello Thom

I cannot tell you the exact cause of the problem yet I can give you some advice how to overcome it.

Roles are client-dependent, thus they are transported using customizing transport requests. When you import the customizing request into your QAS using the TMS (transaction <b>STMS</b>) you have several (importing) <i>options </i>available. Most likely you have to choose <b>"Ignore Non-Permitted Table Class"</b>.

This point to the possible cause of the problem. I have never seen, worked for or heard of any customer using clients <b>000 & 001</b> for productive purposes (development, customizing, QA, or production).

Clients 000 & 001 are special client which should not used at all except, for example, as source for a client copy.

Regards

Uwe

[Former Member]

Hello Uwe,

thank you very much for your response.

The error could really arise due to standard client 000 and 001.

You talk about several options for TMS procedure.

-<b> How can I check which TMS option is currently active and change these?

- Is that possible to change the TMS settings in order to use clients 000 and 001 for transport?

- Do you how much space do I need to copy client 000?</b>

Thank you very much!

regards

[uwe_schieferstein]

Hello Thom

The import options I have described are not general settings of the TMS but if you import individual transports using transaction <b>STMS </b>a <b>popup </b>appears where you can set these options (tabstrip <i>Options</i>) .

The size of a client copy depends on the profile you are using for the copy (transaction SCCL or SCC9):

SAP_ALL    All Client-Specific Data w/o Change Documents     
SAP_APPL   Customizing and Application Data w/o Change Docs  
SAP_APPX   SAP_APPL w/o Authorization Profiles and Roles     
SAP_CUST   Customizing                                       
SAP_CUSV   Customizing and User Variants                     
SAP_CUSX   Customizing w/o Authorization Profiles and Roles  
SAP_PROF   Only Authorization Profiles and Roles             
SAP_UCSV   Customizing, User Master Records and User Variants
SAP_UCUS   Customizing and User Master Records               
SAP_UONL   User Without Authorization Profiles and Roles     
SAP_USER   User Master Records and Authorization Profiles   

I would guess the size will vary between 1 and 10 GB.

If you are only interested in maintaining roles on this client then you could use profile <b>SAP_PROF</b> and/or <b>SAP_USER</b>.

Regards

Uwe

[Former Member]

Hello!

Thank you very much for your response.

Currently I have one productive client 100 so I need one DEV and one QAS client in order to demonstrate the Change Request Management in SAP Solution Manager.

Which profiles can be taken for this issue?

The last vital question:

<b>Must I copy client via SCCL or is there some settings allowing to use clients 000 and 001 for TMS?

</b>

Thank you very much!

regards

Thom

[uwe_schieferstein]

Hello Thom

The question is how "productive" are these clients?

Do you only need them for creating and maintaining roles OR do you want to simultaneously test these roles in a productive environment (= customizing & businees data)? The answer to this question will lead you to the appropriate copy profile.

If I remember correctly you can do the client-copy in a<i> test mode</i> where you see (as a long list) which tables would be copied.

With respect to your last question I am a bit puzzled. SCCL or SCC9 allow you to choose the client for the copy procedure.

In order to import transport requests you always have to tell the TMS explicitly which import client should be used. The only thing the TMS does automatically is to add a release request to the import queue of the next system (e.g.: DEV -> QA system). This depends on the settings of the TMS.

I hope I could give you some useful input.

Regards

Uwe

[Former Member]

Hello Uwe,

thank you very much. I solved my problem by my own.

The following TMS configuration works now, it means I can transport requests without errors:

100 (as DEV client)

001 (as QAS ciient)

000 (as PRD client)

I know to use 000 client as PRD system is not advisable, but for demo issues it works.

Thank you

regards

Thom