PaaS Partner Community

  • July 22, 2015

Document Editor – Defining a custom message (Part 1 of 3) b2b SOA Suite by Bernardo Cabaços

Juergen Kress
PaaS Partner Adoption

clip_image002Oracle Document Editor is an application used for creating and testing document definitions for Oracle B2B.

The document definition (ECS) file is required in B2B for translating and validating documents.

With Document Editor you are able to create new guideline documents or use a template from the comprehensive library of standards available for download. You can download Document Editor and the standard definitions available here.

The available document guideline templates include EDI, HL7, positional flat file (which includes some SAP iDocs), XMLSchema and so on, as seen below.

Thanks to the countless templates available you can easily and quickly create a message definition (ECS) and respective XSD to import to B2B. Making the necessary changes if needed.

Below is an example of a message definition from the template library.

However, specially with Positional Flat File (PFF) messages, you might have to create a custom definition.

In this post I will go through the steps needed to create a custom PFF document definition in Document Editor. This post will be divided in 3 parts, in the first part I will focus on Message Segments', afterwards I'll cover the Field's types and properties, finalizing with testing and XSD generation.

Let's start by creating an empty definition. Read part I here and read part II here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.