Introduction to Oracle B2B Document Editor

Creating Guideline Files 3-3 Figure 3–3 Importing XSD and ECS File Created in Oracle B2B Document Editor The image shows the Oracle B2B Document Editor displaying the following tabs: Document, Deploy, Management Deployments, Types, ImportExport, Schedule Batch, Manage Batch, and Callout. The Document tab is selected. The left pane of the editor shows an expanded hierarchy of Document Protocols with ORDERS_def selected. The right pane of the editor show the ORDERS_def details including the Document Definition Name, Document Definition Description, and Definition fields. Below the fields is the Update button. In Figure 3–3 , EDIFACT_D98A_ORDERS.xsd and EDIFACT_D98A_ORDERS.ecs are imported to create the document definition. The ECS file is required in B2B for translating and validating documents. The XSD is optional in B2B; however, it provides an easy reference to the document schema when modeling a SOA composite for sending and receiving the document.

3.2 Installing Oracle B2B Document Editor

Oracle B2B Document Editor can be obtained by product CD or downloaded from the Oracle Technology Network Software Downloads page: http:www.oracle.comtechnetworkmiddlewaresoasuitedownloads downloads-085394.html11g To install the Oracle B2B Document Editor, extract the downloaded files onto your disk drive, and run Install.exe. Several installation scripts guide you through the process of installing each of the Oracle B2B Document Editor components. Oracle B2B Document Editor runs on Microsoft Windows only Win 2000, WinXP, Vista 1 32-bit and 64-bit, and Windows Server 2003, and requires the Microsoft .NET Note: The MapBuilder component of Oracle B2B Document Editor is not certified or supported. 1 When using Microsoft Vista, do not install Oracle B2B Document Editor in the program folder, for which admin privilege is needed. 3-4 Oracle Fusion Middleware Users Guide for Oracle B2B framework installed automatically from the CD for full support of W3C XML Schema guidelines. Complete usage instructions are available from the Oracle B2B Document Editor Help menu by searching on installation and displaying the Preparation topic. A list of new features in this release of the document editor is also provided.

3.3 Creating Guideline Files: EDIFACT D98 Example

The following example describes how to create the guideline files—the ECS and XSD files— required to send an EDIFACT D98A purchase order, and how to generate and validate test data files based on the D98A–ORDERS guideline. To create the EDIFACT transaction documents for this scenario, do the following: ■ Task 1, Create the ECS File ■ Task 2, Create the XSD File ■ Task 3, Generate Data Using the ECS File ■ Task 4, Analyze the Data Task 1 Create the ECS File Using an existing EDIFACT guideline standard as a template, create a purchase order guideline file called orders.ecs. 1. Open Oracle B2B Document Editor.

2. Click New Document and then EDI, as shown in

Figure 3–4 . Figure 3–4 Creating a New Document in Oracle B2B Document Editor The image shows the New Document Wizard. The left pane of the wizard shows a series of folders with EDI selected. The right pane of the wizard shows a hierarchy of guidelines with EDIFACT selected.

3. Expand EDIFACT and D98A.

Creating Guideline Files 3-5

4. Select ORDERS - Purchase order message, as shown in

Figure 3–5 , and click Next. Figure 3–5 Creating a New Document: Selecting a Guideline The image shows the New Document Wizard. The left pane of the wizard shows a series of folders with EDI selected. The right pane of the wizard shows a hierarchy of guidelines with ORDERS - Purchase order message selected.

5. Ensure that Insert Envelope Segments is not selected, as shown in

Figure 3–6 , and click Finish.