Feb 15, 2022 · SCC1N combines and enhances the old transaction SCC1 and the previous batch report RSCC_SCC1_BATCH. This allows you to copy several transports to the target clients in one run. SCC1N can be scheduled and executed once in client 000 (or another client).

Sep 28, 2006 · To move a transport from one client to the other please follow the below steps. 1. Go to SCC1 T-code. 2. Provide the source client. 3. Provide the Transport number. 4. Select including request sub-tasks if the child Transports also need to be moved. 5.

Feb 24, 2023 · SCC1 is an SAP transaction code that is used to create and maintain customer master records. It is a part of the customer relationship management (CRM) module. SCC1N is an SAP transaction code that is used to display customer master records.

May 19, 2018 · Now login into other client ex.810 with a user who has full authorizations. execute scc1, enter the source client i.e 800 and in the next field i.e transport request click on pop box.

Transaction code SCC1 is a supplement to the client copy. It can be used to transfer individual transport requests directly out for the source client into the the current client. The activities are listed in a clearly structured copy log.

You want to perform a Local Client copy, a Remote Client copy, Delete a Client or Client transport: Client Export and Import. This KBA describes the usage of old client copy tools which were available prior to SAP_BASIS 7.54 (SAP S/4HANA 1909).

You use RSCC_SCC1_BATCH to copy workbench transports (that contain client specific customizing) from one client to another. Read more...

SCC1 tcode in SAP BC (Change & Transport System in Basis) module. This transaction code is used for Client Copy - Special Selections. Here is it details, technical data, menu path etc.

Oct 27, 2023 · In tcode SCC1N users normally face error message of "No transport requests to import found." Even if user have entered all the correct information. Request No., Type of request, Source Client, Target Client, Export/Import Date are few required fields. In this blog I will share two simple solutions that can help to resolve this issue.

Not able to transport a migration project between clients (eg: DS4/200 to DS4/220) using SCC1 or SCC1N transaction. Read more...