As part of configuring the SAP system, you should complete the following steps in this order:
NOTE: The following instructions are for SAP version 4.6C. If you are using a previous version of SAP, the configuration process is the same; however, the SAP interface will be different.
The sending and receiving systems must be defined for messaging. In order to distribute data between systems you must first define both the sending and receiving systems as unique logical systems.
For this particular solution, we recommend defining two logical systems. One logical system represents the driver and acts as the receiver system. The other logical system represents the SAP system and acts as the sender system. Because only one of these clients is used as a data source (that is, the client/logical system where SAP User data is stored and "actions" occur), there is no need to assign a client to the receiving logical system.
NOTE: Depending on your current SAP environment, you might not need to create a logical system. You might only need to modify an existing Distribution Model by adding the USERCLONE message type to a previously configured Model View. For more information, see Creating a Distribution Model.
It is important, however, that you follow SAP's recommendations for logical systems and configuring your ALE network. The following instructions assume that you are creating new logical systems and a new model view.
In SAP, type transaction code BD54.
Click New Entries.
Type an easily identifiable name to represent the SAP sender system. SAP recommends the following format for logical systems representing R/3 clients: systemIDCLNTclient number (such as ADMCLNT100).
Type a description for the logical system (such as Central System for SAP User Distribution).
Add a second logical system name to represent the DirXML external receiver system (such as DIRXMLDRV).
Type a description for the logical system (such as DirXML User Management Integration).
Save your entries.
In SAP, type transaction code SCC4.
Click Table View > Display > Change to switch from display to change mode.
Select the client from which you want User information distributed (such as 100).
Click Goto > Details > Client Details.
In the Logical System field, browse to the sender logical system you want to assign to this client (such as ADMCLNT100).
Save your entry.
The distribution model contains essential information about message flow. The model view defines the systems that will communicate with each other and the messages that will flow between them. The distribution model forms the basis of distribution and controls it directly.
To create a distribution model:
Verify that you are logged on to the sending system/client.
In SAP, type transaction code BD64. Ensure that you are in Change mode (click Table View > Display > Change.)
Click Edit > Model View > Create.
Type the short text to describe the distribution model (such as Client 100 Distribution to DirXML).
Type the technical name for the model (such as SAP2DIRXML).
Accept the default Start and End dates or specify valid values. Click the check mark icon to save your entry.
Select the view you created, then click Add BAPI.
In the Sender/Client field, type the name of the sender logical system (such as ADMCLNT100).
In the Receiver/Client field, add the name of the receiver logical system (such as DIRXMLDRV).
In the Obj. Name/Interface field, add the USER object name.
NOTE: Ensure that you add the USER object name with all capital letters.
In the Method field, add Clone.
Click the check mark icon to save the BAPI.
Select the SAP2DIRXML model view.
Click Add BAPI.
Define the sender (logical system ADMCLNT100).
Define the receiver (logical system DIRXMLDRV).
In the Obj. Name/Interface field, add the UserCompany object name.
In the Method field, add Clone.
Click the check mark icon to save your BAPI entries.
Save the Distribution Model entries.
The port is the communication channel to which IDocs are sent. The port describes the technical link between the sending and receiving systems.
The driver can be configured to support a connection via a TRFC port or to consume IDocs distributed via a File port. The default driver configuration assumes that you use the TRFC port configuration.
Prior to creating a TRFC port definition, you must create an RFC destination. To create an RFC destination:
In SAP, type transaction code SM59.
Click the Create icon.
Name the RFC destinations (such as DIRXML USER DRIVER).
Select T as the connection type (for a TCP/IP connection.)
Add a description for the destination (such as JCO Server in DirXML User Driver.)
Save your entry.
Select the option for Registration or Registered Server Program. Type the program ID that will be used for the driver. In the default driver configuration, this value is set to DirXMLUser.
Save your entry.
The TRFC port is used to determine the RFC program to which IDocs are sent.
In SAP, type transaction code WE21.
Select Transactional RFC, then click the Create icon.
Select Own Port Option Name.
Type a port name (such as DIRXMLPORT).
Type a description for the port definition (such as Port to DirXML User Driver).
Select a version (such as IDoc record types SAP release 4.X)
Enter the RFC destination. This is the name of the RFC destination representing the driver (such as DIRXML USER DRIVER.)
Save your entries.
In SAP, type transaction code WE21.
Select File, then click the Create icon.
Define the outbound file:
Select the physical directory. This is the directory where you want IDocs placed. You might need to create this directory.
Type the directory where the outbound files are written, for example: \\sapdev\nov\sys\global\sapndsconnector.
Type the function module. This names the IDoc file in a specific format. For example: edi_path_create_client_docnum.
Save your changes.
NOTE: You do not need to configure the other three tabs for the port properties (outbound:trigger, inbound file, and status file).
The system automatically generates a partner profile or you can manually maintain the profile.
NOTE: If you are using an existing distribution model and partner profile, you do not need to automatically generate a partner profile. Instead, you can modify it to include the USERCLONE BAPI.
In SAP, type transaction code BD82.
Select the Model View. This should be the Model View previously created in Creating a Distribution Model.
Ensure that the Transfer IDoc Immediately and Trigger Immediately option buttons are selected.
Click the Execute icon.
NOTE: Ignore any red error or warning messages when the status screen appears. These issues will be resolved when you modify the port definition in the next section.
When you generated a partner profile, the port definition might have been entered incorrectly. For your system to work properly, you need to modify the port definition.
In SAP, type transaction code WE20.
Select Partner Type LS.
Select your receiver partner profile (such as DIRXMLDRV).
Click the Create Outbound Parameter icon, then select message type USERCLONE.
Modify the receiver port so it is the file or TRFC port name you created earlier (such as DIRXMLPORT or DIRXMLFILE).
Under Output Mode, select Transfer IDoc Immediately to send IDocs immediately after they are created.
In the IDoc Type section, select the Basic type and the appropriate USERCLONE:
Save your entries.
Click the Create Outbound Parameter icon, then select message type CCLONE.
Modify the receiver port so it is the file or TRFC port name you created earlier (such as DIRXMLPORT or DIRXMLFILE.)
Under Output Mode, select Transfer IDoc Immediately to send IDocs immediately after they are created.
In the IDoc type section, select Basic type and the appropriate CCLONE. (For all SAP versions, select CCLONE01.)
Save your entries.
Central User Administration (CUA) is the process that activates the distribution model.
In SAP, type transaction code SCUA.
In the Maintain System Landscape dialog box, select the distribution Model View previously created (such as SAP2DIRXML).
Save your entry.
You will see a message stating "Unable to distribute the system landscape to system DIRXMLDRV." This is an informative message and is not an error or issue of concern.
By default, all data fields of the User object will be configured for global control. This means that changes can only be made on the central system (the sender client) and distributed to child systems. This is acceptable unless you want to distribute Roles and Profiles information to the driver. If you want this distribution, you must modify the field distribution parameters.
In SAP, type transaction code SCUM.
Click the Roles tab.
Select the Local option for the Role Assignment and Reference User fields.
Click the Profiles tab.
Select the Local option for the Auth Profiles file.
Save your entries.
Once again, you will receive the "Unable to distribute . . ." message. This is not an error or issue of concern.
Users are client-independent. For each client that will be using the driver, a system user with CPIC access must be created.
In SAP, type transaction code SU01.
From User Maintenance, enter a username in the User dialog box (such as DIRXML_CPIC), then click the Create icon.
Click the Address tab, then type data in the last name fields (Last_DirXML).
Click the Logon Data tab, then define the initial password and set the user type to CPIC (Communication).
Click the Profiles tab, then add the sample values of SAP_ALL, SAP_NEW and S_A.CPIC profiles. You can use other profiles.
Click the Systems tab. Add the logical name of the sender system (such as ADMCLNT100). This enables the CPIC user to authenticate to the client system.
Click Save.
NOTE: Initially, you can create a dialog user to test your SAP system configuration. If there are processing problems, you can analyze the dialog user in the debugger. You should also log into the SAP system once to set this user's password. After the system is tested and works properly, you should switch to a CPIC user for security measures.