Delimited Payload Support

B2B for Oracle Integration supports delimited payloads in inbound and outbound transactions. You create a schema and document from a delimited payload to use in integrations. During runtime, the delimited payload is translated to XML (and vice versa) based on the schema you created. Delimited payload support is provided in both standalone and trading partner modes.

How B2B for Oracle Integration handles delimited payload

When processing a delimited payload in B2B for Oracle Integration, you must specify segment, segment name, element, and composite element delimiters in the payload. These delimiters are required during schema creation on the Schemas page.

Example delimited payload
STX=ANAA:1+5000116000123:RETAIL STORES LTD+5013546110456:RETAIL SERVICES+141123:134748+358767+ +ORDHDR'MHD=1+ORDHDR:9'TYP=0430+NEW-ORDERS'SDT=5021839054321+RETAIL SERVICES'CDT=5000119012345+RETAIL STORES LTD++220430231'FIL=513+1+141123'MTR=6'CLO=5000116001234:0100821'ORD=LM82191329029::141123'DIN=141130+++ANY PROBS CALL LISA 01234 123783:EMAIL?: LISA.JONES@UK.RETAIL.COM'OLD=1+::05050747002152++:4294588+5+400++++128MB USB FLASH MEMORY'OTR=3'OFT=3'RSG=358767+5013546110456'END=5'

In the example payload:

  • Segment name delimiters are indicated by an equal to sign (=)

    This delimiter separates the segment name from the rest of the segment data. For example in STX=, STX is the segment name and = is the delimiter.

  • Segment delimiters are indicated by an apostrophe (')

    This delimiter marks the end of each segment. For example, the apostrophe at the end of STX=ANAA:1+5000116000123:RETAIL STORES LTD+5013546110456:RETAIL SERVICES+141123:134748+358767+ +ORDHDR' indicates the end of segment STX and separates the STX segment from the next segment MHD.

  • Element delimiters are indicated by a plus sign (+)

    This delimiter separates individual data elements within a segment. For example, in the segment STX, the plus sign (+) separates element 1 from 5000116000123, element RETAIL STORES LTD from 5013546110456 and so on.

  • Composite element delimiters are indicated by a colon (:)

    This delimiter separates sub elements within a composite element. For example in composite element ANAA:1+5000116000123:RETAIL STORES LTD, the colon (:) separates ANAA from 1, and 5000116000123 from RETAIL STORES LTD.

The corresponding translated XML in B2B for Oracle Integration at runtime looks as follows. Segments such as STX, MHD and TYP are created, each with their individual elements and composite elements.


Description of delimited-sample-xml.png follows
Description of the illustration delimited-sample-xml.png

When you create the schema on the Schemas page, you specify the following key details:
  • Select Delimited as the document standard.
  • Drag and drop the delimited payload.
  • Select the segment, segment name, element and composite element delimiters that you specified in the delimited payload.
  • Manually specify values for the document version and type or select existing values.


Description of delimited-create-schema.png follows
Description of the illustration delimited-create-schema.png

This creates a schema consisting of the segments, segment names, elements, and composite elements from the delimited payload. You can further customize the schema from the Actions menu at the segment and element levels by adding new child elements, new child composites, new segments, new loops and more. You can also view the defined delimiters for the schema by selecting Edit info at the top of the page.


Description of delimited-schema.png follows
Description of the illustration delimited-schema.png

After schema definition is complete, you define a document from that schema to use in integrations on the Documents page, including:
  • Defining identifiers for document identifications at runtime.
  • Defining XPath expressions for business identifiers in the document.