For a complete system that consists of several SAP systems, there are the following possible methods you can use to transport the Customizing configuration from a delivery system to a target system:
· Manual entry
· Special functions (for example, transactions, RFC-enabled function modules, Application Link Enabling)
· Compare tables
· Customizing transport
· Copy client
This topic describes which methods can be used for transporting the SNC configuration information. Pay close attention to any notes that are provided.
After upgrading your system from 3.0/3.1, and after you have completed the Customizing activities mentioned in Upgrade from 3.0/3.1 the USR15 table is empty. You need to transport this empty table to the target system. To transport the table, you must manually initiate the transport request. The entry in the transport request is as follows:
● Transport objects: R3TR TABU USR15
● Key: <Client>* or *
● User information
To transport user information, use the standard method of copying the client.
● User ACL
To transport the user ACL (table USRACL), use transaction SM30, view USRACL.
Currently, this table is considered application data, and not user information. For each client where you transport user information by means of copying, you must also initiate a transport request for table USRACL.
● Extended user ACL
To transport the extended user ACL (table USRACLEXT), use transaction SM30, view USRACLEXT.
Currently, this table is also considered application data, and not user information. For each client where you transport user information by means of copying, you must also initiate a transport request table USRACLEXT.
● Authorization for RFC User
To transport the user information, use the standard method of copying the client.
To transport the system access control list (table SNCSYSACL), use transaction SNC0 or transaction SM30, view VSNCSYSACL, type = E. You do not need to transport internal entries.
After copying a client, you can delete any superfluous entries in table SNCSYSACL. Use transaction SM30, view VSNCSYSACL, type = I. Also delete any superfluous external entries (type = E).
The following sections apply to transporting the various communication settings when using SNC. They include printing using SAPlpd, RFC and CPIC.
For information about transporting printer definitions, see Transporting Output Devices (Device Definitions).
You need to manually maintain the RFC destinations in the target system.
You also need to manually maintain the CPIC destinations in the target system.