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 is 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.
You must assign a client to the sending logical system. Because the receiving logical system is an external system, there is no need to assign it to a client. You should never assign the same client to more than one logical system.
For this particular solution, we recommend defining two logical systems. One logical system acts as the receiver and the other logical system acts as the sender. Although only one of these logical systems is used as a data source process (that is, the client/logical system where employee data is stored and “actions” occur), the second logical system is needed to represent the receiving process (in this case, the driver.)
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 HRMD_A 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 .
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 HR Distribution).
Add a second logical system name to represent the Identity Manager external receiver system (such as DRVCLNT100).
Type a description for the logical system (such as IDM HR Integration).
Save your entry.
In SAP, type transaction code SCC4.
Click > > to switch from display to change mode.
Select the client from which you want User information distributed (such as 100).
Click > > .
In the 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 communicate with each other and the messages that 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 > > .)
Click > > .
Type the short text to describe the distribution model (such as Client 100 Distribution to IDM).
Type the technical name for the model (such as SAP2IDM).
Accept the default and dates or specify valid values. Click the check mark icon to save your entry.
Select the view you created, then click
Define the sender/logical system name.
Define the receiver/server name.
Define the Message Type you want to use (), then click .
Click .
The port is the communication channel to which IDocs are sent. The port describes the technical link between the sending and receiving systems. You should configure a file port for this solution. The file port is used to determine the directory and the file location to which IDocs are sent.
To create a file port definition:
Type transaction code WE21.
Select , then click the icon. Specify information for the following fields:
: Select SAP release 4.X
On newer SAP servers, the database might be Unicode*. If this is true, select the check box on the tab.
Define the outbound file:
Select the physical directory. This is the directory where you want IDocs placed. You might need to create this directory.
Specify the directory where the outbound files are written, for example: \\SAPDEV\NOV\SYS\GLOBAL\SAPNDSCONNECTOR.
Specify the function module. This names the IDoc file in a specific format. Always use the following format: EDI_PATH_CREATE_CLIENT_DOCNUM.
Save your changes.
You do not need to configure the other three tabs for the port properties (, , and).
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 generate a partner profile. Instead, you can modify it to include the HRMD_A message type.
Type transaction code BD82.
Select the model view. This should be the model view previously created in Creating a Distribution Model.
Ensure that the and option buttons are selected.
Select a reasonable packet size value to ensure that IDoc files are not too large to process. We recommend a value of 100.
Click .
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.
Type transaction code WE20.
Select .
Select your receiving partner profile.
Select , then click .
Select message type .
Click , then modify the receiver port so it is the file port name you created in Creating a Port Definition.
From the Output Mode section, select to send IDocs immediately after they are created.
From the IDoc Type section, select the latest version available for your system.
Click .
Type transaction code PFAL.
Insert the for person objects.
Enter an employee’s ID for the or select a range of employees.
Under the tab, set to if you select a range of employees.
Click .
Ensure that the status is set to P
The IDoc has been created. Go to the directory where IDocs are stored (it was defined in the file port setup) and verify that the IDoc text file was created.
To activate change pointers globally:
Type transaction code BD61.
Enable the tab.
To activate change pointers for a message type:
Type transaction code BD50.
Scroll to the .
Select the check box, then click .
Type transaction code SE38 to begin defining the variant.
Select the select , then click the icon.
Name the variant and give it a description.
Make note of the variant name so you can use it when scheduling the job.
Select the message type, then click .
You are prompted to select variant attributes. Select the background processing attribute.
Click .
Type transaction code SM36.
Name the job.
Assign a Job Class.
Job Class is the priority in which jobs are processed. Class is the highest priority and will be processed first. For a production environment, we recommend assigning the class to or .
Schedule a start time. Click the tab, then click . Specify a scheduled start time, which must be a future event.
Mark the job as a periodic job, click the tab, schedule how frequently you want the job to run, then press . For testing purposes, we recommend setting this period to 5 minutes.
Click .
Define the job steps:
Type the ABAP program name: RBDMIDOC.
Select the variant you created in the previous step.
Click .
IMPORTANT:Click once; otherwise, the job will be scheduled to run multiple times.
From the SAP client, hire an employee.
Ensure that an IDoc was created.
You can verify IDoc creation in two locations:
Type transaction code WE02
Go to the IDoc file locations
Users are client-dependent. For each client that will be using the driver, a system user with CPIC access must be created.
From specify a username in the user dialog box, then click the icon.
Click the tab, then specify data in the and fields.
Click the tab, then define the initial password and set the user type to .
Click the tab, then add the , and profiles.
Click .
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.
IMPORTANT:If restricted rights are assigned to the CPIC User, the Identity Manager and SAP administrators are responsible to ensure that sufficient rights are assigned to enable the configured level of integration. Section D.0, Business Application Programming Interfaces (BAPIs) contains a table describing which BAPIs the driver uses.