Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Santosh.Vukkalkar on Jan 6 at 3:16 AM Hi,
AUTHORIZATIONS
To perform client copy or transport, you need the appropriate
authorizations. There are two types of authorizations: general
authorizations for client copy, and special authorizations that depend on
what you want to copy.
The initial user SAP* has all authorizations required, except authorization
to create a transport request. It can be used for all client copy tools
except the client export (SCC8).
General authorizations for Client Copy
Authorization Action
S_TABU_CLI Maintain cross-client tables
S_TABU_DIS Maintain system tables
S_CLIENT_IMP Import data in client copy
S_DATASET_AL Access the file system
Copy User Profiles and User Master Records
Authorization Action
S_USER_PRO Copy authorization profiles
S_USER_GRP Copy user master records
Transport Clients
You also need the following authorizations to transport clients:
Authorization Action
S_CTMS_ADMI with TTYPE 'CLCP' ACTVT '01'
Create object lists for client transport and copy into another client
Remote Copy (authorization required for RFC user in source client)
Authorization Action
S_TABU_RFC Remote access to tables in target system
Regards,
Santosh.
| | | ---------------Original Message---------------
From: ash61892
Sent: Monday, January 05, 2015 4:28 PM
Subject: Client Copy from Prd to Dev
For Audit reason SAP_ALL is not allowed in production.I can assign assign SAP_all to id in QA when start the kick off job but in post processing step "userid in QA has now production porfile which donot have SAP_ALL" . What need to be done in such case |
| Reply to this email to post your response. __.____._ |   _.____.__ |
