How to Identify the B2B Document Protocol

17-2 Developers Guide for Oracle Application Integration Architecture Foundation Pack

17.2 Step 1: Identifying the B2B Document and Analyzing Requirements

This section includes the following topics: ■ Section 17.2.1, How to Identify the B2B Document Protocol ■ Section 17.2.2, How to Identify the B2B Document Type and Definition ■ Section 17.2.3, How to Define the Document in Oracle B2B ■ Section 17.2.4, How to Define the Document in AIA ■ Section 17.2.5, How to Identify the EBO, EBS, and EBM to Be Used ■ Section 17.2.6, How to Design Mappings for the B2B Document ■ Section 17.2.7, How to Publish Mapping to Trading Partners The first step in building an outbound B2B flow is to identify the B2B document that needs to be generated by the flow. As a part of this step, as shown in Figure 17–2 , you must also analyze the requirements for the AIA services that need to be built or extended to support the flow. Figure 17–2 Step 1: Identifying B2B Document and Analyzing Service Requirements As a part of this step, the integration development team performs the following tasks: ■ Identify the B2B document protocol to be used. ■ Identify the B2B document type to be used. ■ Define the B2B document in Oracle B2B. ■ Define the B2B document in AIA. ■ Identify the AIA Enterprise Business Object EBO, Enterprise Business Message EBM, and Enterprise Business Service EBS to be used. ■ Identify the message exchange pattern. ■ Map the EBM, B2B document, and Application Business Message ABM. ■ Document and publish the mapping.

17.2.1 How to Identify the B2B Document Protocol

To develop a B2B flow, you first identify the B2B document to be used. Often, the choice of B2B document is influenced by the capabilities of the trading partners or e-commerce hub that needs to be integrated with your applications. However, if you have the choice to choose a B2B document definition to be used for a particular integration use case, several industry-standard e-commerce standards exist today that vary in popularity in different geographies and industries. Developing and Implementing Outbound B2B Integration Flows 17-3 Examples of B2B document protocols are Open Applications Group Integration Specification OAGIS, Electronic Data Interchange EDI X12, Electronic Data Interchange For Administration, Commerce and Transport EDIFACT, Health Insurance Portability and Accountability Act HIPAA, EANCOM, RosettaNet, Universal Business Language UBL, Health Level 7 HL7, and 1SYNC. Consider the following questions when choosing a B2B document protocol to integrate with your trading partners: ■ Does the document protocol have the list of documents to support your integration needs? ■ Does the document protocol have adequate support for your industry? ■ Is the document protocol supported by your key trading partners? ■ Is the document protocol popular in your geography? ■ Is the document protocol based on open standards such as XML and XML Schema? ■ Is the protocol support by your vendor, for example, Oracle? Along with the B2B document protocol, the version of the B2B document must also be determined. Similar considerations as listed previously can be used to determine the B2B document protocol version.

17.2.2 How to Identify the B2B Document Type and Definition