Cross-client transports in ChRM.

Dear SolMan Gurus!
How to handle cross-clients transport request in change request management. Is it in the way that no matter how do I set may landscapen = transport routes, than all cross-client transports go to the cliet 000? Do I need any additional setting in SolMan Change Req. Man.?
Thank you for you reply.
Best regards,
Petr Syka

Hi Suker,
There are two ways to transport your Workbench/ Customizing request from one client to the other, The detail are as below:
1. SCC1: Create a transport request for the task done. Move to the target client and enter the tcode: scc1. Specify the transport request and upload it. The data will be transfered.
2. BC Sets: Create BC Set for the Cutomization done and upload it to the target system.
Award points if useful.
Regards,
Madhu Sudhanan

Similar Messages

How do u segrigate cross client req. and client specific req.?

How can I find out which one is Cross client transport and client specific transport req.?

Hi tjk
In SPRO, do the following:
Menu: Additional Information->Technical Data->Client Dependence
Then all IMG nodes will have the client specific/client independent information visible.
Also:
Normally, when you try to open an IMG node of cross-client, then system gives a warning message.
Best regards
Ramki

Client export for ABAP programs, repository objects cross client objects

Hello,
Let me first explain the scenario here. Our Development system crashed we are rebuilding the development system from a client export of the production. Client does not want migration etc so the only way we want to do it is through client export.
Now the question is whether cross client objects can really be imported through client export KT, KO, KX requests?
I thought it was possible but after successfully importinng the client export (which was taken using profile SAP_EXPC) of the Production client all the customizing has been imported but non of the ABAP programs have been imported.
Can anyone explain how this is done and if it is possible?
Steps I performed:
1] Exported Production client with profile SAP_EXPC
2] Imported the 3 requests KT, KO, KX using command line
tp import <KT req> <SID> U2 client=<my client> pf=<profile path>
tp import <KX req> <SID> U2 client=<my client> pf=<profile path>
tp import <KO req> <SID> U2 client=<my client> pf=<profile path>
3] After successful import ran scc7 which finished successfully
Thank you

You can transport client independent customizing, read sap note [24853 - CC-INFO: Client copy, functionality|https://service.sap.com/sap/support/notes/24853].
But you cannot transport abap repository objects (abap programs) with a client copy.
Can you explain what you mean by "Our Development system crashed". If you still can happily do client copies to that system, then i really wonder what you mean by crashed...
Cheers Michael

Cross-client customizing are not permitted

Hi,
I am trying to remove "Transformation Object" in BI 7.0, QA server, and it not allowe to me access, I have SAP_ALL access
I am getting this error messages:
"changes to repository or cross-client customizing are not permitted"
I know we can't change anyitng in QA its goes through Transport, but the problem is DEV system this objects didn't show and QA this objects shows, so I want to remove this bi object from QA system
I know while installation NW 2004s its post installation steps to not change objects
in SE06 I am trying to change these objects to modifible but still not allow to changeable
please help me out

Hi Angeline,
In transaction SCC4 double click the client on which you are working. There will be a setting "Changes to repository or cross-client customizing are not permitted." Modify this option to "Automatic recording of changes."
Making that will allow you to delete the object.
Make sure after you achieve your desired objective, you revert back the client settings to "Changes to repository or cross-client customizing are not permitted." Also revert back the settings in SE06 in QA to the original what you had in post installation.
Regards
Sourabh Majumdar

Error Changes to Repository or cross-client Customizing are not permitted

Hi
While creating infoset in SQ02 it is giving an error as "Changes to Repository or cross-client Customizing are not permitted"
I did change the SE06 system change options , software components modifiable.
And I also changed the objects changebility in transport connections in RSA1. But still it is giving the same error.....
Can you please let me know the solution?
Thanks

I'm assuming that you're creating a custom InfoCube query, so does it give you the option of creating as a Local Object (package $TMP) or one of your custom, transportable packages? Basically it's determining whether you want this InfoSet Query to be a Local Object or if you plan on transporting it throughout the landscape.
One other thing that I wanted to point out about security. SAP_ALL doesn't necessarily mean access to anything and everything. There are cases where the Authorizations assigned to an SAP_ALL Authorization Object don't necessarily have all of the correct assigned Activity for every transaction. Security, in your case, doesn't seem to be the problem because you're getting this request to assign a package.
Edited by: Dennis Scoville on Nov 4, 2009 2:39 PM

Cross-Client (HR Related)

Hi
we are using the ECC 6 with teh following patch level
ABAP / BASIS        11
PI_BASIS            11
SAP_HR              14
SAP_APPL            09
This is Quality system where users are testing the scenario, i have protected the client.
I have complained from the HR users which are listed down:-
1) whenever he executing the SQ03 to create the group, the dialoge box appear that "Changes to repository or cross-client customizng are not permitted"
2) PA30,to change anything in the master - data are requring to make customizing request.
Please provide the solution ASAP.
Regards

Hi
Generally to customizing in carried in Quality server, it is used for testing.
As per my knowledge all the customizings are done in develpement and ask the transport no from basis once we get that save that and send it to Quality. there we test the configured steps wth values and then again get the transport no save that and ask basis to transport to Production.
Yup Any data changes has to be first customised in development and follow the same proses as above and move to production. Any editing everything follows the same stps....
Hope this help u,
reward if helpful,
Asha

Cross Client Logical File Name

Hi Gurus, I have got 3 cross-client LFN's transported into PROD. Couple of couple ago, I had them imported into PROD. When I go to FILE, I do not see the new LFN's at all. There's no refresh button to refresh the screen. I have been like watching it since last 2 hours now. Am I wrong somewhere? Please guide
Thnx.
null

Is re-transporting the only solution?
I did re-transport it one more time. But still I do not see the LFN's. Please guide.

Cross-client activation issue with LBWE

Hi,
I am running into the same problem as the following links:
Problem with setup table fillup
Cross-client problem
We have the configuration client 300 and the loading client 310. The structures in client 100 are active but are inactive in client 310. The first link says that I have to go into LBWE in the loading client to activate the structures, but I have the same issue relating to the second link. This is happening in the DEV system.
Is the fix for the second issue relating to Basis who would allow me to do the activation on the loading client - opening the system for me to activate? Or is it the Developer's issue to find the workaround?
I don't see why the restriction on the configuration for DEV client systems. This is for BW related Configuration issues and nothing is relating to SAP Business Configuration that had to be so restricted.
Please advise how to get the inactive structures to be active in the loading client.
Thanks

Hi,
It is a very common issue. You can solve it by logging in to 310 client, going to SCC1 transaction and replicating changes from the transport orders that you created in the other DEV client.
It's like transporting from one DEV client to the other, but please note that the request does not need to be released.
I hope this helps.
Best regards,
Maximiliano Ariel López

'Changes to reposotory or cross client custimizing is not permitted'.

Hi,
I am trying to activate datasources at r/3 side.
I am getting message that 'Changes to reposotory or cross client custimizing is not permitted'.
I cant understand that why this is happening.
I feel that it is because of cleint is lock or not changeable.
So how to check that client is locked. OR how to resolve this problem.

Hi,
If you are trying to do this in R/3 production system, obviously you will get this messaage because most production systems are locked and no customization or chagnes are allowed. If you are getting this message in R/3 development system then you need to change the settings to allow customization. Use Transaction code SCC4, click on the pencil, click on continue, double click on the appropriate client, choose second option in changes and transports for client-specific objects. Now choose "Changes to reporsitory andd cross-client customizing allowed" from the first drop down list and save it.
Hope it will help.
Regards,
Rao.

Advantages and Dsadvantages of Remote Client Copy over Client Transport...

Can anybody explain the Advantages and Dsadvantages of Remote Client Copy over Client Transport...
Thanks in Advance

Advantages of Remote client copy over client transport
1. Client-specific data as well as cross-client customizing can be copied to the target client, this is not the same in client transport.
2. The prerequisites for performing a remote client copy are that an RFC connection has to exist whereas client transport do not need RFC connection
3. The copy can be performed in parallel with several processes.
4. Remote client copy automatically performs a consistency check on the tables being copied,for client transport performance check need to be done.
5. A remote client copy is easy to use and does not require file system space on
operating system level whereas Client transport require lot of space as files are created at OS level.
Disadv
1. A remote client copy does not create a file at the operating system level,
so there is no hard copy of the client to be copied. Therefore, the same,
identical client copy cannot be duplicated at a later time.Client transport creates import and export files at Os levels
2. To be able to copy all data during the client copy, the structures of all copied
tables in both systems must be identical.
3. An automatic repository consistency check is performed in Remote client copy and if inconsistencies are detected, the client copy is terminated and an error message is displayed.
4. You cannot copy the remote client data and use it whereas in client transport you can copy the files in a cd (like import files, export files)
Also see notes
47502
557132
Rakesh

RSA6 is cross client?

Hello,
just a question, for the first time we use the same source system (with different client) as a sandbox and development box.
When activating a datasource in RSA6 in client 120 and then go to RSA6 client 190, it is written that
Only editing of DataSources (hierarchy locked by user).
I understand that RSA6 is cross client and so, modifications to datasources also, so it makes no sens to have a sandbox and development on the same instance, because all tests from sandbox (client 190) will affect extract structure in the development client.
Can you confirm, or do you think this is a strange behavior or some customizing is missing?
ECC 6.0 Ehp4 connected to BI 7.0 Ehp1
Thanks a lot
Thibaud.

You are correct that DataSources are cross-client and therefore when you activate a DataSource in your Client 120, the DataSource is immediately available in Client 190 and every other client on that same instance. Therefore, any changes made to the DataSource, including enhancement of the extraction structure and CMOD code, will affect all clients in that instance.
I can see your point that it does not make much sense that a sandbox client and development client exist on the same instance. In fact, I could say that it does not make sense for many more reasons than just BW-related areas. For example, if a user exit for a transaction process is developed in the sandbox client, it would be in the development client as well. Then, if true development is being done and unit testing is performed with the user exit developed in the sandbox, the results of that testing would be flawed because that user exit would not be transported to the next target instance (e.g. QA) along with the actual development objects, causing potential issues whilst testing in QA.
In the many years that I've been working on SAP (R3/ECC, BW/BI, GTS, etc), the organizations that I have worked for have always had the sandbox as a separate, significantly smaller, instance from the development instance. Sanbox environments are supposed to be just that, a playground where there are no rules. Once you introduce that type of open availability to the development environment of a productive system, you are introducing a boat load of potential issues.

How to disable Cross client Table Access

Hi All,
i have created a Sand box client and i have set its cross client object value to
"No Changes to repository and cross client customizing objs"
but still users are able to run transactions like SR13 which are cross client tables
please help

HI Zeeshan,
Once u run the Tcode like SR13, the users would be able to enter the Tcode and have a new entry varinat created..but during SAVE the system would sure prompt the message... " Changes to Repository or cross-client Customizing are not allowed. Please press DISPLAY or CANCEL" ..
so the changes would not be saved hence forth and have to be cancelled out..
hope this is what u have been looking for..
Br,
Sri
Award points for helpful answers

How to create cross-client variant?

Hi Experters:
Can someone tell me how create cross-client variant in ECC6.0?
in 4.6, we can define the client or define cross-client transaction variant,
how to create cross-client variant in ECC6.0?
Regareds,

Hi,
In se93 there is a check box cross-client .
The Cross-client switch identifies which transaction variants are cross-client and which are client-specific. If the switch is set, the transaction variant is cross-client. If the switch is not set, the transaction variant is client-specific.
A client-specific transaction variant can only exist in the client where it was created. The field contents of the transaction variant only have to be available in the particular client. A cross-client transaction variant is available in the system regardless of which client is currently active. The field contents of the transaction variant have to be available in all clients.
http://****************/Tutorials/ABAP/TransactionVariant/Create.htm

How to create a cross-client table maintenance dialog?

Hello everybody,
I have a client specific table (mandt is the first key field) that should be maintained cross-client: In the table maintenance dialog, I want to change/create/insert values belonging to clients other than the current logon client. Can I do this with a generated maintenace dialog? If yes, how?
Thank you for your help, regards, Kathrin!

Hi Kathrin,
I think you can't, you must create your own dialog maintenance program.
They are some program to copy data from client to others .. but never seen any dialog cross client. (or remove the mandt in your key).
Regards
Frédéric

Steps to create Cross-Platform Transportable Tablespaces

hi
what is the steps to do Cross-Platform Transportable Tablespaces.
i want to perform this in my pc, i have linux and windows in same PC, i want to migrate from linux to windows and vice versa.
so can i know complete steps and commands to perform Cross-Platform Transportable Tablespaces. to get complete knowledge i am doing this so i can implement this in my office when any migrate issues comes. so once i do this i will get confidence so that i can do the same in my office which saves my time.
veeresh s
oracle-dba
[email protected]

Hi, also you can review the Note:413586.1 into metalink site.
Good luck.
Regards.

Cross-client transports in ChRM.

Similar Messages

Maybe you are looking for