IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > SAP Software > Configure the module for deployment > Configure the module for inbound processing > Configure a module for ALE pass-through IDoc inbound processing

Selecting business objects and services for ALE pass-through IDoc inbound processing

To specify the IDoc you want to process, you provide information in the external service wizard.

For the ALE pass-through IDoc interface, you can specify IDocs from a system or from a file, but the most likely reason for using the pass-through IDoc interface is to use a generic IDoc.

When you select a generic IDoc, you create one business-object definition that can apply to any IDoc at run time. This selection is helpful if you are processing many IDocs and do not want to create a separate business-object definition for each one.

You see the Generic IDoc choice only if you selected ALE pass-through IDoc as the interface on the Discovery Connection window.

The adapter now provides an out-of-the-box functionality to parse out the stream data provided in Passthrough IDoc Business Objects.

To use this new feature, you need to configure the DataBinding (after the EMD run) to use the com.ibm.j2ca.sap.ale.idoc.datahandler.SAPIDocDataHandler DataHandler Java class that is now bundled with the SAP adapter RAR file.

When invoking the Data Handler, you must provide the following details:

  1. Name of the specific IDoc

    For example, SapAlereq01. The corresponding schema must be available for the Artifact Loader at runtime.

  2. Business Object namespace for that specific schema.

  3. Data Encoding.

With this setting, your end point will get the specific parsed IDoc without any change to the existing modules.

To learn more about how to work with Java Beans and Data Handlers, refer to the IBM BPM or WebSphere Enterprise Service Bus documentation.


Procedure

  1. In the Find Objects in the Enterprise System window, indicate that you want to select a generic IDoc.

    1. Expand ALE.

    2. Click Generic IDoc .

  2. Click the arrow button to add the generic IDoc to the Selected objects list.

  3. When the Configuration Properties window is displayed, you can set the following configurable options for the selected IDoc:

    Figure 1. Configuration parameters for a generic IDoc

    1. Enable the checkbox Parse the IDoc Control Record, to generate a child business object to hold the parsed Control Record. When enabled, the property to send IDocs in the Flat File format are disabled. This feature enables you to route IDocs based on individual Control Record settings.

    2. Indicate whether you want to have multiple IDocs sent as one packet instead of sending them as individual business objects:

      • If you want to send multiple IDocs as a packet, select the Send an IDoc packet as one business object option.

    3. Indicate whether you want to send the IDoc in the Flat File format to the configured end point(s):

      • If you do not want to send the IDoc in the Flat File format, leave the Send IDoc in flat-file format option unchecked

      • If you want to send IDoc in the Flat File format, select the Send IDoc in flat-file format option:

        1. When sending the IDoc in the Flat File format, the Control Record length will remain 524. The Data Record length can vary depending on the segment length which is based on the IDoc version selected. Choose the correct value in the IDoc release version field.

          If the IDoc contains unreleased segments, leave the version field blank.

        2. When sending the IDoc in the Flat File format, set a delimiter, which will be added after the Control Record as well as after each Data Record, in the Specify a delimiter for IDocs field.

          You can choose standard delimiters provided in the drop down or specify a custom one.

  4. Click OK.


Results

You have selected a generic IDoc.


What to do next

Set deployment properties and generate a module.

Configure a module for ALE pass-through IDoc inbound processing