5. Manually creating partner profiles (WE20)

The Distribution Model is only applicable to ALE interfaces. When using the Distribution Model, the BD82 transaction will automatically update/create partner profile definitions and create RFC port definitions as needed. However, these definitions must be created or modified manually in situations such as the following:

  • When you are not able to use the Distribution Model, you must manually create your partner profile definitions (WE20) and port definitions (WE21). Reference the SAP Online Library for additional information.
  • When using the EDI file-based method of IDoc creation, you will need to manually create partner profiles.
  • When modifying the Partner Profile parameters prior to production or to create partner profiles manually.

There are situations where partner profiles must be created or modified manually.

To manually create partner profiles

  1. Enter /nWE20 transaction in the command field.

    The Partner Profiles window opens.

  2. From the Partners menu, select Create or Display Change to create a new profile or to modify an existing profile.
  3. Enter Outbound parameters or Inbound parameters as appropriate.

In the Outbound Parameters window, you can add or change the information as required.

From transaction codes the various reports can be run.

  • RSEOUT00: Dispatch collected IDocs in a batch job.
  • RSEOIND: Check the successful completion of the transmission of a tRFC to the communication layer. If successfully completed, the status of the IDoc is changed.

Schedule report RSEOUT00

As SAP recommends, the program RSEOUT00 should be scheduled to send IDocs by using transactional RFCs. This sends IDoc packages in one transmission, using one logon, and may provide better performance than sending IDocs individually. Avoid sending individual IDocs because each transmission involves significant overhead such as the loading of programs, establishing the connection, and logging on.

When using RSEOUT00, note the size of the IDoc packages, which can be defined in the outbound parameters of the corresponding partner agreement. For optimization, the size of the data objects involved and the number of available processes at the transmitting and receiving ends must be considered. SAP R/3 generally recommends packing 2 to 20 IDocs per package for IDocs that have numerous segments (such as ALEUD and GLDCMT) and 20 to 2,000 IDocs per package for IDocs with a small number of segments.

The use of RSEOUT00 requires one or more dialog work processes to enable parallel transmissions of IDoc packages. For SAP R/3 versions 3.1i and higher, tRFC resource management support is available. SAP R/3 advises that to avoid timeouts, the number of sender-side dialog work processes should be less than or equal to the number of available processes on the receiver. See OSS note 74141 in the SAP R/3 Documentation for details.

When sending IDoc packages in parallel using this method, the packages cannot be received in serial order. If serialization of IDoc package transmission is required, use a periodic process on the received packages. To do this, configure your partner profiles for background processing and select a processing interval sufficiently large enough to ensure all interdependent packages can be received. Based on their time stamp, the packages are then reordered before processing.

Schedule Report RBDMOIND

When outbound IDocs are passed to the communication layer successfully, they are assigned the status data passed to port OK. This does not mean that it was a successful tRFC transmission. The RBDMOIND report from SE38 should be regularly started to check whether the communication was successfully completed. If successfully completed, the status of the IDoc is changed.

The RBDMOIND report indicates whether the outbound IDocs were transmitted to the communication layer successfully and should be scheduled to run regularly.

To schedule the RBDMOIND report

  1. Define variants for the job.
  2. Schedule the job with the report and one variant in one step.