How to Identify the EBO, EBS, and EBM to Be Used How to Design Mappings for the B2B Document

17-6 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 17–5 UpdateMetaDataDeploymentPlan.xml Edited to Update the B2BObjectLibrary in Oracle Metadata Services b. Source the file aiaenv.sh located under AIA_HOMEbin. For example: source slotems5813oracleAIA3_HOMEbinaiaenv.sh c. Change the directory to AIA_HOMEInfrastructureInstallconfig. For example: cd AIA_HOMEInfrastructureInstallconfig. d. Issue the AIA command to deploy the metadata. For example: ant -f UpdateMetadata.xml. e. Verify that the command was successful and that no errors occurred.

17.2.5 How to Identify the EBO, EBS, and EBM to Be Used

To be able to integrate the B2B documents using AIA, the next step is to identify the AIA EBO, EBM, and EBS to be used. Select the AIA EBO and EBM for which the description most closely matches the B2B document to which you need to integrate. For example, to develop an outbound B2B integration flow in which EDI 850 Order documents need to be communicated to a supplier by a procurement application, you can use the following EBO, EBM, and EBS: ■ EBO: PurchaseOrderEBO ■ EBM: CreatePurchaseOrderEBM ■ EBS operation: CreatePurchaseOrder

17.2.6 How to Design Mappings for the B2B Document

The next step is to analyze your business requirements and map the ABM to the EBM and the EBM to the B2B document. Consider the following guidelines while developing mappings for B2B documents: ■ Identify and clearly list the subset of target B2B document elements to which you need to map based on your integration needs. ■ Document and publish the list of B2B elements being mapped. For each element being mapped, document the following information: – Data type – Cardinality – Example value – Description – DVM name and columns used – Mandatory indicator Developing and Implementing Outbound B2B Integration Flows 17-7 Consider the following guidelines while mapping identification and reference components in the B2B documents: ■ Map universal identifiers if available and supported by your application. For example, map UPC codes for identifying Items and UDEX codes for identifying Item Categories. ■ Map all available external identifiers used by your trading partners. For example, map the Vendor Part Number in outbound B2B documents that need to be sent to your vendors. ■ Map free-form attributes such as Description, Notes, Attachments, and so forth to enable users to communicate and provide more information to trading partners. ■ While mapping reference components, map content from the referenced entity and not just the identification. For example, if a Ship To Location has to be mapped in an outbound Purchase Order document being sent to a supplier, in addition to the location identifiers, map the actual postal address and contact details of the Ship To Location. ■ While mapping Identification type components, you can directly map the actual application IDs to the B2B document. This is unlike the application-to-application A2A use case in which an XREF is used to store the mapping between the participating application identifiers and the AIA identifiers. For example, assume that you are working with a SyncItem from an Inventory system to a trading partner. Assume that ITEM_001 is the item identifier in the source ABM. This value can be directly mapped as-is to the Identification element. Using an XREF has little additional value because the ID generated in the trading partner application as a result of the sync flow will not be captured in the XREF. A direct mapping is preferable instead. ■ Map ahead of current requirements. Even if your current integration use case may require that only a few elements be mapped, a best-practice recommendation is to map all the available fields that can be processed by your application. This allows the connectors to be reused for multiple use cases. ■ Extend EBOs, if required. If the target B2B document contains attributes that need to be mapped, but that are not available in the EBO, extend the EBO to include the target elements and map them. ■ Capture the mapping in an easy-to-understand spreadsheet and keep it current when any changes need to be made.

17.2.7 How to Publish Mapping to Trading Partners