Publication Modes

A publication mode defines the format of IDocs to be published and recieved.

The adapter supports the following three types of publication mode:
  • Explode Mode

    IDocs are initially received in compressed form as RFC tables. The received IDoc is expanded and serialized into a hierarchical ActiveEnterprise message structure, namely the ActiveEnterprise Message format, using IDoc metadata. Metadata specifies the hierarchical structure, including contained records and fields, associations between different segments, and repetition information. The ActiveEnterprise Message format is described in the TIBCO Adapter SDK Concepts.

    If multiple IDocs are received in a batch, then each IDoc in the batch is split from the other IDocs and sent individually.

    The SAP system sends out data to the adapter with padded blanks wherever a field in the IDoc segment does not occupy the complete field length or a field is not populated at all.

    By default, the adapter trims off the trailing spaces from blank padded fields, and cuts out blanks-only fields.

    Note: The data published for a particular IDoc segment field is based on the actual data sent by the SAP system. The adapter does not pad the value provided by the SAP system with trailing whitespace.
  • Exploded Batch Mode

    Using Exploded Batch mode, the adapter sends a batch of IDocs in Explode mode. Similarly on the subscriber side, the adapter receives the IDocs in a batch and processes them in the SAP system.

    If the ALE outbound profile for an IDoc type is set up to Collect IDocs, IDocs are collected within the SAP system until the packet size value is reached, and then sent to the adapter at one time.

    Exploded Batch mode ensures that individual IDocs are “exploded” to a self-describing format and also maintained as a batch. The batch of exploded IDocs is then published as one single message by the adapter.

  • IDocFormat

    In IDocFormat mode, no transformation is performed in the IDoc content. The IDoc is presented in a original string format.

    Similar to Expode mode, only one IDoc is exchanged per message. When you send multiple IDocs from SAP system or TIBCO environment in one call, each IDoc is sent individually.

    If the Transport Type is JMS, the control fields are also passed as JMS properties. The property name consists of the prefix, SAPIDOC_ and the IDoc control record field. For example, if the field is DOCNUM, the corresponding JMS property is SAPIDOC_DOCNUM.

    If the Transport Type is Rendezvous, the Rendezvous Message wire format is not supported.

Contents
Search Results