Importing Client-Dependent Objects
The import postprocessing takes place in client 000. So that the objects can be correctly created or activated (and scheduled, if necessary) in the target client, an RFC logon with a change of user must be carried out in the target client. An RFC destination that is intended for this is required in the target system. This destination is used during the import postprocessing for the logon from client 000 into the target client.
In BI there are objects whose processing is client-dependent.
● During the creation of Web service DataSources, client-dependent objects (ICF nodes) occur in the BI standard client.
For Web service DataSources, a destination in the BI standard client is necessary.
● Process chains schedule background jobs that are client-dependent. You can also use the Editing Client attribute to mark individual process chains as client-dependent.
As soon as the attribute is maintained, the chain can only be displayed, edited, activated, executed, and scheduled in the specified client. The attribute is transported with the process chain. During an import into a target system, you can modify the attribute by specifying another client as the target client into which the import should take place. If you do not specify a target client or import client here, in the target system the import is carried out into the client that has the same number as the client in the export system.
Process chains for which no processing client was defined must be imported into the BI standard client in order to schedule the background jobs in the BI standard client.
For process chains, an appropriate destination must be available in the relevant clients. This can be the BI standard client if no editing client has been specified for the process chain. It can also be the specified editing client for the process chain or the client that was specified during the import.
The destinations are also required during the transport of the deletion of the objects.
A user for background processes (BI background user) was created in the Implementation Guide (IMG) under SAP NetWeaver → Business Intelligence → Automated Processes.
For Web service DataSources: the background user has sufficient authorizations to be able to edit Web service DataSources (role template S_RS_WDS).
1. In the Implementation Guide (IMG), choose SAP NetWeaver → Business Intelligence → Transport Settings → Create Destination for Import Postprocessing (transaction RSTPRFC).
2. Select a target client.
○ Select the BI standard client to transport of Web service DataSources and process chains without specifying a client.
○ For the transport of a client-dependent process chain, select the client that is specified in the attribute of the process chain or was specified in the import.
3. Enter a description for the destination.
4. Enter the background user and password.
The RFC call is executed with this user name when you perform postprocessing steps for the import. For the standard client, the BI background user is displayed.
The user entered there must have authorization profile S_BI-WHM_RFC.
5. Save your entries.
The destination is created when you save your entries. It contains the name of the target client, a host of the same system, and a background user with authorization profile S_BI-WHM_RFC.
The destination of the BI standard client is entered in the RSADMINA table in the TPBWMANDTRFC field. The destinations of additional target clients are entered in the RSTPRFC table.
In the after-import or during the execution of the method, the specified RFC destination is called in the target system of the transport so that the objects are correctly created and activated in the respective target client.