oracle® iprocurement connectordocs.oracle.com/cd/b40089_10/current/acrobat/120itgoipcig.pdfthis...

Oracle® iProcurement ConnectorImplementation GuideRelease 12Part No. B40057-01

January 2007

Oracle iProcurement Connector Implementation Guide, Release 12

Part No. B40057-01

Copyright © 2007, Oracle. All rights reserved.

Primary Author: Harry Anthony

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, ordecompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTSPrograms, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear allrisks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the qualityof third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services.Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

iii

Contents

Send Us Your Comments

Preface

1 Understanding Oracle iProcurement Connector About This Guide...................................................................................................................... 1-1About Oracle iProcurement Connector ....................................................................................1-2Oracle iProcurement Connector Components ......................................................................... 1-4Oracle iProcurement Connector Flow....................................................................................... 1-6Oracle iProcurement Connector Business Models................................................................... 1-7

Application-to-Application Integration............................................................................... 1-7Business to Business Integration.......................................................................................... 1-8Oracle iProcurement Connector Business Model Summary................................................ 1-9

2 Setting Up the Oracle iProcurement ConnectorOracle iProcurement Connector Implementation Steps.......................................................... 2-1Using the Oracle iProcurement Connector............................................................................... 2-5

3 MessagesTransaction Flow from Oracle E-Business Suite...................................................................... 3-1

Purchase Order.................................................................................................................... 3-1Change Purchase Order....................................................................................................... 3-3Process Purchase Order....................................................................................................... 3-5Requisitions......................................................................................................................... 3-7Cancel Purchase Order........................................................................................................ 3-8Cancel Requisition............................................................................................................... 3-9

iv

Receipts.............................................................................................................................. 3-10Transaction Flow into Oracle E-Business Suite......................................................................3-11

Supplier..............................................................................................................................3-11Unit of Measure (UOM)..................................................................................................... 3-12Item.................................................................................................................................... 3-13Exchange Rates.................................................................................................................. 3-14Chart of Accounts (COA)................................................................................................... 3-14Purchase Order Status........................................................................................................3-15Purchase Order Number.................................................................................................... 3-17

A Sample XMLADD REQUISITION................................................................................................................ A-1CHANGE REQUISITION...................................................................................................... A-13CANCEL REQUISITION........................................................................................................A-22SYNC PO................................................................................................................................. A-23SYNC PO (Release)................................................................................................................. A-36CHANGE PO...........................................................................................................................A-48CANCEL PO............................................................................................................................ A-65UPDATE DELIVERY.............................................................................................................. A-66SYNC SUPPLIER.................................................................................................................... A-70SYNC ITEM.............................................................................................................................A-72SYNC UOMGROUP............................................................................................................... A-74SYNC FIELD (PO Number).................................................................................................... A-76SYNC PO (Inbound Invoice and Receipt Totals)...................................................................A-77SYNC EXCHANGE RATE...................................................................................................... A-79SYNC COA.............................................................................................................................. A-80CONFIRM BOD...................................................................................................................... A-82PROCESS PO.......................................................................................................................... A-84

B TroubleshootingTroubleshooting Common Errors.............................................................................................B-1

Glossary

Index

v

Send Us Your Comments

Oracle iProcurement Connector Implementation Guide, Release 12Part No. B40057-01

Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document. Your feedback is important, and helps us to best meet your needs as a user of our products. For example:

• Are the implementation steps correct and complete? • Did you understand the context of the procedures? • Did you find any errors in the information? • Does the structure of the information help you with your tasks? • Do you need different information or graphics? If so, where, and in what format? • Are the examples correct? Do you need more examples?

If you find any errors or have any other suggestions for improvement, then please tell us your name, the name of the company who has licensed our products, the title and part number of the documentation andthe chapter, section, and page number (if available).

Note: Before sending us your comments, you might like to check that you have the latest version of the document and if any concerns are already addressed. To do this, access the new Applications Release Online Documentation CD available on Oracle MetaLink and www.oracle.com. It contains the most current Documentation Library plus all documents revised or released recently.

Send your comments to us using the electronic mail address: [email protected]

Please give your name, address, electronic mail address, and telephone number (optional).

If you need assistance with Oracle software, then please contact your support representative or Oracle Support Services.

If you require training or instruction in using Oracle software, then please contact your Oracle local officeand inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at www.oracle.com.

vii

Preface

Intended AudienceWelcome to Release 12 of the Oracle iProcurement Connector Implementation Guide.

This guide assumes that you have working knowledge of your business area's processes, tools, principles, and customary practices. It also assumes that you are familiar with Oracle iProcurement. If you have never used Oracle iProcurement, we suggest you attend one or more of the Oracle iProcurement training classes available through Oracle University.

See Related Information Sources on page viii for more Oracle Applications product information.

TTY Access to Oracle Support ServicesOracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.

Documentation AccessibilityOur goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to allof our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/ .

viii

Accessibility of Code Examples in DocumentationScreen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in DocumentationThis documentation may contain links to Web sites of other companies or organizationsthat Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Structure1 Understanding Oracle iProcurement Connector This topic introduces the Oracle iProcurement Connector and describes its features and functions.

2 Setting Up the Oracle iProcurement ConnectorThis topic provides the implementation steps to configure the Oracle iProcurement Connector. It also provides the steps to use the windows and reports specific to Oracle iProcurement Connector.

3 MessagesThis topic discusses the function and technical details of each of the messages or OAG BODs currently supported by the Oracle iProcurement Connector. The messages are grouped by the direction of flow of information.

A Sample XMLThis topic lists the sample XML Code Structure.

B TroubleshootingGlossary

Related Information SourcesRelated Guides

Oracle iProcurement shares business and setup information with other Oracle Applications products. Therefore, you may want to refer to other guides when you set up and use Oracle iProcurement. You can read the guides online from the Oracle Applications Document Library CD included in your media pack, or by using a Web browser with a URL that your system administrator provides. If you require printed guides, then you can purchase them from the Oracle Store at http://oraclestore.oracle.com

Guides Related to All Products

ix

Oracle Alert User's Guide

This guide explains how to define periodic and event alerts to monitor the status of your Oracle Applications data.

Oracle Applications Concepts

This book is intended for all those planning to deploy Oracle E-Business Suite Release 12, or contemplating significant changes to a configuration. After describing the Oracle Applications architecture and technology stack, it focuses on strategic topics, giving a broad outline of the actions needed to achieve a particular goal, plus the installation andconfiguration choices that may be available.

Oracle Applications Flexfields Guide

This guide provides flexfields planning, setup, and reference information for the Oracle Applications implementation team, as well as for users responsible for the ongoing maintenance of Oracle Applications product data. This guide also provides information on creating custom reports on flexfields data.

Oracle Application Framework Personalization Guide

This guide covers the design-time and run-time aspects of personalizing applications built with Oracle Application Framework.

Oracle Applications Installation Guide: Using Rapid Install

This book is intended for use by anyone who is responsible for installing or upgrading Oracle Applications. It provides instructions for running Rapid Install either to carry out a fresh installation of Oracle Applications Release 12, or as part of an upgrade from Release 11i to Release 12. The book also describes the steps needed to install the technology stack components only, for the special situations where this is applicable.

Oracle Application Server Adapter for Oracle Applications User's Guide

This guide covers the use of OracleAS Adapter in developing integrations between Oracle applications and trading partners.

Please note that this guide is in the Oracle Application Server 10g (10.1.3.1) Documentation Library.

Oracle Applications System Administrator's Guide Documentation Set

This documentation set provides planning and reference information for the Oracle Applications System Administrator. Oracle Applications System Administrator's Guide - Configuration contains information on system configuration steps, including defining concurrent programs and managers, enabling Oracle Applications Manager features, and setting up printers and online help. Oracle Applications System Administrator's Guide - Maintenance provides information for frequent tasks such as monitoring your system with Oracle Applications Manager, managing concurrent managers and reports, using diagnostic utilities, managing profile options, and using alerts. Oracle Applications System Administrator's Guide - Security describes User Management, data security, function security, auditing, and security configurations.

Oracle Applications User's Guide

x

This guide explains how to navigate, enter data, query, and run reports using the user interface (UI) of Oracle Applications. This guide also includes information on setting user profiles, as well as running and reviewing concurrent requests.

Oracle e-Commerce Gateway User's Guide

This guide describes the functionality of Oracle e-Commerce Gateway and the necessary setup steps in order for Oracle Applications to conduct business with trading partners through Electronic Data Interchange (EDI). It also contains how to run extract programs for outbound transactions, import programs for inbound transactions, and the relevant reports.

Oracle e-Commerce Gateway Implementation Guide

This guide describes implementation details, highlights additional setups for trading partner, code conversion, and Oracle Applications as well as provides the architecture guidelines for transaction interface files. This guide also contains troubleshooting information and how to customize EDI transactions.

Oracle Report Manager User's Guide

Oracle Report Manager is an online report distribution system that provides a secure and centralized location to produce and manage point-in-time reports. Oracle Report Manager users can be either report producers or report consumers. Use this guide for information on setting up and using Oracle Report Manager.

Oracle iSetup User Guide

This guide describes how to use Oracle iSetup to migrate data between different instances of the Oracle E-Business Suite and generate reports. It also includes configuration information, instance mapping, and seeded templates used for data migration.

Oracle Workflow Administrator's Guide

This guide explains how to complete the setup steps necessary for any product that includes workflow-enabled processes. It also describes how to manage workflow processes and business events using Oracle Applications Manager, how to monitor the progress of runtime workflow processes, and how to administer notifications sent to workflow users.

Oracle Workflow Developer's Guide

This guide explains how to define new workflow business processes and customize existing Oracle Applications-embedded workflow processes. It also describes how to define and customize business events and event subscriptions.

Oracle Workflow User's Guide

This guide describes how users can view and respond to workflow notifications and monitor the progress of their workflow processes.

Oracle Workflow API Reference

This guide describes the APIs provided for developers and administrators to access

xi

Oracle Workflow.

Oracle XML Gateway User's Guide

This guide describes Oracle XML Gateway functionality and each component of the Oracle XML Gateway architecture, including Message Designer, Oracle XML Gateway Setup, Execution Engine, Message Queues, and Oracle Transport Agent. The integrations with Oracle Workflow Business Event System and the Business-to-Businesstransactions are also addressed in this guide.

Oracle XML Publisher Report Designer's Guide

Oracle XML Publisher is a template-based reporting solution that merges XML data with templates in RTF or PDF format to produce a variety of outputs to meet a variety of business needs. Using Microsoft Word or Adobe Acrobat as the design tool, you can create pixel-perfect reports from the Oracle E-Business Suite. Use this guide to design your report layouts.

Oracle XML Publisher Administration and Developer's Guide

Oracle XML Publisher is a template-based reporting solution that merges XML data with templates in RTF or PDF format to produce a variety of outputs to meet a variety of business needs. Outputs include: PDF, HTML, Excel, RTF, and eText (for EDI and EFT transactions). Oracle XML Publisher can be used to generate reports based on existing E-Business Suite report data, or you can use Oracle XML Publisher's data extraction engine to build your own queries. Oracle XML Publisher also provides a robust set of APIs to manage delivery of your reports via e-mail, fax, secure FTP, printer, WebDav, and more. This guide describes how to set up and administer Oracle XML Publisher as well as how to use the Application Programming Interface to build custom solutions.

Guides Related to This Product

Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to Release 12

This guides provides detailed information about the functional impacts of upgrading Oracle Financials and Oracle Procurement products from Release 11i to Release 12. This guide supplements the Oracle Applications Upgrade Guide: Release 11i to Release 12.

Oracle Financials Concepts Guide

This guide describes the fundamental concepts of Oracle Financials. The guide is intended to introduce readers to the concepts used in the applications, and help them compare their real world business, organization, and processes to those used in the applications.

Oracle Financials Implementation Guide

This guide provides information on how to implement the Oracle Financials E-Business Suite. It guides you through setting up your organizations, including legal entities, and their accounting, using the Accounting Setup Manager. It covers intercompany accounting and sequencing of accounting entries, and it provides examples.

Oracle General Ledger Implementation Guide

xii

This guide provides information on how to implement Oracle General Ledger. Use this guide to understand the implementation steps required for application use, including how to set up Accounting Flexfields, Accounts, and Calendars.

Oracle General Ledger User's Guide

This guide provides information on how to use Oracle General Ledger. Use this guide to learn how to create and maintain ledgers, ledger currencies, budgets, and journal entries. This guide also includes information about running financial reports.

Oracle iSupplier Portal User Guide

This guide contains information on how to use Oracle iSupplier Portal to enable secure transactions between buyers and suppliers using the Internet. Using Oracle iSupplier Portal, suppliers can monitor and respond to events in the procure-to-pay cycle.

Oracle iSupplier Portal Implementation Guide

This guide contains information on how to implement Oracle iSupplier Portal and enable secure transactions between buyers and suppliers using the Internet.

Oracle Purchasing User's Guide

This guide describes how to create and approve purchasing documents, including requisitions, different types of purchase orders, quotations, RFQs, and receipts. This guide also describes how to manage your supply base through agreements, sourcing rules, and approved supplier lists. In addition, this guide explains how you can automatically create purchasing documents based on business rules through integrationwith Oracle Workflow technology, which automates many of the key procurement processes.

Oracle iProcurement Implementation and Administration Guide

This manual describes how to set up and administer Oracle iProcurement. Oracle iProcurement enables employees to requisition items through a self–service, Web interface.

Installation and System Administration

Oracle Applications Concepts

This guide provides an introduction to the concepts, features, technology stack, architecture, and terminology for Oracle Applications Release 12. It provides a useful first book to read before an installation of Oracle Applications. This guide also introduces the concepts behind Applications-wide features such as Business Intelligence(BIS), languages and character sets, and Self-Service Web Applications.

Installing Oracle Applications

This guide provides instructions for managing the installation of Oracle Applications products. In Release 12, much of the installation process is handled using Oracle Rapid Install, which minimizes the time to install Oracle Applications and the Oracle technology stack by automating many of the required steps. This guide contains instructions for using Oracle Rapid Install and lists the tasks you need to perform to finish your installation. You should use this guide in conjunction with individual

xiii

product user guides and implementation guides.

Upgrading Oracle Applications

Refer to this guide if you are upgrading your Oracle Applications Release 10.7 or Release 11.0 products to Release 12. This guide describes the upgrade process and lists database and product-specific upgrade tasks. You must be either at Release 10.7 (NCA, SmartClient, or character mode) or Release 11.0, to upgrade to Release 12. You cannot upgrade to Release 11i directly from releases prior to 10.7.

"About" Document

For information about implementation and user documentation, instructions for applying patches, new and changed setup steps, and descriptions of software updates, refer to the "About" document for your product. "About" documents are available on OracleMetaLink for most products beginning with Release 11.5.8.

Maintaining Oracle Applications

Use this guide to help you run the various AD utilities, such as AutoUpgrade, AutoPatch, AD Administration, AD Controller, AD Relink, License Manager, and others. It contains how-to steps, screenshots, and other information that you need to runthe AD utilities. This guide also provides information on maintaining the Oracle applications file system and database.

Oracle Applications System Administrator's Guide

This guide provides planning and reference information for the Oracle Applications System Administrator. It contains information on how to define security, customize menus and online help, and manage concurrent processing.

Oracle Alert User's Guide

This guide explains how to define periodic and event alerts to monitor the status of your Oracle Applications data.

Oracle Applications Developer's Guide

This guide contains the coding standards followed by the Oracle Applications development staff and describes the Oracle Application Object Library components thatare needed to implement the Oracle Applications user interface described in the Oracle Applications User Interface Standards for Forms-Based Products. This manual also provides information to help you build your custom Oracle Forms Developer forms so that the forms integrate with Oracle Applications.

Oracle Applications User Interface Standards for Forms-Based Products

This guide contains the user interface (UI) standards followed by the Oracle Applications development staff. It describes the UI for the Oracle Applications productsand how to apply this UI to the design of an application built by using Oracle Forms.

Other Implementation Documentation

Oracle Applications Product Update Notes

Use this guide as a reference for upgrading an installation of Oracle Applications. It

xiv

provides a history of the changes to individual Oracle Applications products between Release 11.0 and Release 12. It includes new features, enhancements, and changes made to database objects, profile options, and seed data for this interval.

Oracle Workflow Administrator's Guide

This guide explains how to complete the setup steps necessary for any Oracle Applications product that includes workflow-enabled processes, as well as how to monitor the progress of runtime workflow processes.

Oracle Workflow Developer's Guide

This guide explains how to define new workflow business processes and customize existing Oracle Applications-embedded workflow processes. It also describes how to define and customize business events and event subscriptions.

Oracle Workflow User's Guide

This guide describes how Oracle Applications users can view and respond to workflow notifications and monitor the progress of their workflow processes. Oracle Workflow API Reference This guide describes the APIs provided for developers and administrators to access Oracle Workflow.

Oracle Applications Flexfields Guide

This guide provides flexfields planning, setup and reference information for the Oracle E-Records implementation team, as well as for users responsible for the ongoing maintenance of Oracle Applications product data. This guide also provides information on creating custom reports on flexfields data.

Oracle eTechnical Reference Manuals

Each eTechnical Reference Manual (eTRM) contains database diagrams and a detailed description of database tables, forms, reports, and programs for a specific Oracle Applications product. This information helps you convert data from your existing applications, integrate Oracle Applications data with non-Oracle applications, and writecustom reports for Oracle Applications products. Oracle eTRM is available on OracleMetalink.

Oracle Applications Message Manual

This manual describes all Oracle Applications messages. This manual is available in HTML format on the documentation CD-ROM for Release 12.

Integration RepositoryThe Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner.

The Oracle Integration Repository is shipped as part of the E-Business Suite. As your

xv

instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.

Do Not Use Database Tools to Modify Oracle Applications DataOracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle Applications data unless otherwise instructed.

Oracle provides powerful tools you can use to create, store, change, retrieve, and maintain information in an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle Applications data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data.

Because Oracle Applications tables are interrelated, any change you make using an Oracle Applications form can update many tables at once. But when you modify Oracle Applications data using anything other than Oracle Applications, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle Applications.

When you use Oracle Applications to modify your data, Oracle Applications automatically checks that your changes are valid. Oracle Applications also keeps track of who changes information. If you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track whohas changed your information because SQL*Plus and other database tools do not keep arecord of changes.

Understanding Oracle iProcurement Connector 1-1

1Understanding Oracle iProcurement

Connector

This topic introduces the Oracle iProcurement Connector and describes its features and functions.

This chapter covers the following topics:

• About This Guide

• About Oracle iProcurement Connector

• Oracle iProcurement Connector Components

• Oracle iProcurement Connector Flow

• Oracle iProcurement Connector Business Models

About This GuideThe purpose of this guide is to provide information for users of Oracle iProcurement Connector. It presents the following:

• Overview of the Oracle iProcurement Connector

• Steps to implement the Oracle iProcurement Connector

• Transaction contents of the Oracle iProcurement Connector

• Sample XML Code Structures

• Troubleshooting steps to ensure complete and proper implementation of the Oracle iProcurement Connector

1-2 Oracle iProcurement Connector Implementation Guide

About Oracle iProcurement Connector The Oracle iProcurement Connector is key to conducting the integration between the Oracle iProcurement and other applications within or outside of the organization. The Oracle iProcurement Connector is used as an application-to-application integration tool and as a business-to-business integration tool when used with supported middleware such as Oracle Application Server 10g Integration for package, transport, and other technical messaging requirements.

The Oracle iProcurement Connector lets an enterprise take advantage of the world-classfeatures and functionalities of iProcurement while continuing to leverage the enterprise's investment in other Enterprise Resource Planning (ERP) and middleware applications.

The Oracle iProcurement Connector adheres to the Open Application Group IntegrationSpecification (OAGIS) version 7.2. OAG specifies standardized XML document type definitions (DTD) for many Business Service Requests (BSRs). Refer to the Open Application Group Web site at http://www.openapplications.org for more details.

The Oracle iProcurement Connector sends and receives Business Object Documents (BODs) in the XML format to comply with the OAG standard. This standards-based communication allows the Oracle iProcurement Connector to interact with third party systems that adhere to the OAGIS standard, including third party middleware directly with third party applications and legacy systems.

Functioning of the Oracle iProcurement Connector The Oracle iProcurement Connector supports messages inbound to the E-Business Suiteand outbound from the E-Business Suite. For outbound messages, the Oracle iProcurement Connector detects transaction events in Oracle iProcurement, transforms them into standardized XML formatted messages, and then publishes them onto an Oracle Advanced Queue (AQ). The messages are transformed using OAGIS transaction definition for ease of integration with the target system. Once the messages are in the AQ, they are easily routed to other applications directly, through third party middleware such as the Oracle Application Server 10g Integration (AS10g), or through Java Messaging Services (JMS).

FeaturesThe Oracle iProcurement Connector supports the following outbound messages from the E-Business Suite:

• Add Requisition

• Change Requisition

• Cancel Requisition


• Synchronize Purchase Order (PO)

• Change PO

• Cancel PO

• Update Delivery (receipt, return, and correction)

• Process PO

The Oracle iProcurement Connector supports the following inbound messages to the E-Business Suite:

• Synchronize Supplier

• Synchronize Item

• Synchronize Unit Of Measurement (UOM)

• Synchronize Chart of Accounts (COA)

• Synchronize Currency Exchange Rate

• Synchronize Field (PO Status)

• Synchronize PO (Receiving, Inspection, and Invoicing quantities)

These messages are used in conjunction with the business process models described in the "Oracle iProcurement Connector Business Models" topic. Any combination of the messages listed can be implemented. The models represent common patterns and are intended to guide, rather than to restrict the implementor.

The Oracle iProcurement Connector adheres to the Open Application Group Internet Standard (OAGIS) version 7.2. Any product, typically referred to as middleware, that can read from and write to the Oracle Advanced Queue can process the OAG XML messages.

The flexible design lets an implementor make extensions to the Oracle iProcurement Connector by adding support for additional transactions or modifying existing transactions.

The Oracle iProcurement Connector offers several configurational options for additional flexibility. These include options to:

• Enable or disable specific transactions.

• Tune the level of message logging and message confirmations.

• Purge the message logs at a flexible frequency.


Oracle iProcurement Connector Components The Oracle iProcurement Connector uses the Oracle XML Gateway and Oracle Workflow Business Event System (BES) to support the payload flow into and out of Oracle iProcurement. Preconfigured XML Gateway mappings, workflows and BES events are delivered with several APIs and triggers required to initiate the BES events.

The Oracle iProcurement Connector uses Collaboration History and Notification Processing. These features are a part of the Oracle XML Gateway. Refer to the Oracle XML Gateway User's Guide for details.

Workflow Business Event SystemThe Oracle iProcurement Connector and Oracle XML Gateway leverage the Oracle Workflow BES to publish and subscribe to application business events, which automatically trigger message creation and consumption.

The core of the BES is the Event Manager. The BES contains a registry of business eventsthat are generated or received. The subscriptions are made to these events. When the events are generated or received, the subscribing code is executed in the same transaction as the code that raised the event. The subscriptions send event data to functions, workflows, or to other queues or systems.

To make use of events, the workflow process definition is extended to model the generation or receipt of business events directly. The events integration is represented as a new event type activity. The workflow engine is extended with an API to send events to workflow processes. When an event is sent to a workflow process, it triggers anew thread of execution in the process.

All events required for the product are included in the Oracle iProcurement Connector, so no coding is required as a part of the standard implementation process.

XML GatewayThe primary purpose of the Oracle XML Gateway is to provide the integration mechanism for A2A and B2B with a common XML standards-based interface to the Oracle Applications in the following manner:

• For outbound XML messages, XML Gateway transforms the given data from OracleE-Business Suite Applications into XML messages.

• For inbound XML messages, XML Gateway maps the data from the XML message to a business API or an open interface table.

The Outbound XML messages are processed starting with the Oracle Workflow BES. The base application raises an event to initiate the creation of the XML message. The BES passes the basic transaction data to the XML Gateway for further processing.

The Inbound XML messages are processed by the BES, which controls the movement of


the data. A listener detects the presence of a message in the inbound queue and passes it to the BES.

The Oracle iProcurement Connector contains all XML Gateway maps, Collaborations and default Notification Processing for supported messages.

Collaboration HistoryA Collaboration is a collection of events and messages related to one business process instance. The XML Gateway's Collaboration History feature captures the message and receipt events, such as linking an outbound OAG SYNC_PO message with its OAG confirmation BOD (Business Object Document) returned from middleware or any other application. The Simple Search and Advanced Search application windows help in querying the status of any collaboration based on context-specific search criteria. A Summary window displays the results.

The Summary window provides a number of features, including the ability to reinitiate a Collaboration or to resend an individual message when indicated by business need or technical message failure. In either case, the original payload stored in the XML Gateway tables is resent. The complete life cycle of a Collaboration is tracked using these interactive windows.

The Collaboration History framework is leveraged to implement new collaborations, or currently unsupported transactions.

Refer to the Oracle XML Gateway User's Guide for details.

Repository Based Message DesignerThe XML Gateway Message Designer is a convenient tool used to implement and manage change of messaging requirements using the definition and remapping of XML messages.

The data source and target definitions are used by the Message Designer to create a message map. Using the repository-based Message Designer, the source and target definitions are based either on an application table, view definition, or on XML Document Type Definition (DTD). Sample XML files are created to facilitate the design process.

All message maps required by the Oracle iProcurement Connector are included. View the maps using the XML Gateway Message Designer.

Message ValidationThe XML Gateway services support the following levels of message validation:

• To ensure that each message is well-formed and valid. The XML Gateway uses the XML Parser embedded in Oracle Database to validate all inbound XML messages against DTDs. Poorly formed or invalid messages are flagged for review.


• After the DTD validation determines a message is well-formed and valid a second validation pass is performed based on predefined validation rules entered using theMessage Designer.

Advanced Queue (AQ) Used by Oracle iProcurement ConnectorThe Oracle iProcurement Connector uses Advanced Queues on the application databasefor both outbound and inbound messages to provide persistent storage of messages. The messages are saved until the listener on the queue detects them and passes them onto the next step in the process.

Oracle iProcurement Connector FlowThe following steps illustrate the general flow in Oracle iProcurement outbound and inbound business events:

Outbound

1. An event occurs in Oracle iProcurement.

2. The trigger raises a business event.

3. The BES executes an attached subscription workflow.

4. Following tasks are performed within the workflow:

• The Organization Effectivity check is performed.

• The Trading Partner validation is performed.

• The Transaction is logged in the Collaboration History.

• The matching XML Gateway map is executed to generate the XML.

• The result of the XML generation is logged in the Collaboration History.

• The XML payload is placed on the outbound AQ.

Inbound

1. The Collaboration History is updated when the confirmation BOD arrives from the source system using the Messaging Middleware or Transport Agent.

2. The source system places a record on the inbound queue, using the Messaging Middleware or Transport Agent, for processing by the XML Gateway.

3. The XML Gateway AQ listener identifies the payload BOD type and executes the appropriate XMLG map.


4. Following transactions occur within XMLG:

• The Transaction is recorded in the Collaboration History.

• The XML Message is used.

• The Oracle iProcurement Connector Business API is executed.

• The Business API execution is recorded in the Collaboration History.

• A Confirmation BOD is sent back (if required).

Oracle iProcurement Connector Business ModelsThe Oracle iProcurement Connector supports the following business process models forimplementing Oracle iProcurement. The process models are classified as:

• Application-to-Application Integration (A2A)

• Business-to-Business Integration (B2B)

Application-to-Application IntegrationThe Business process models supported in this category are:

• Requisitioning Model

• Purchase Order Model

• Purchase Order and Receipt Model

The Oracle iProcurement Connector can be used with the systems, such as:

• An Oracle non-eBusiness Suite application

• A non-Oracle packaged or legacy application

• A procurement or procurement related service that can be either internally or externally provisioned

Requisitioning Model This model supports the creation, change, and cancellation of requisition transactions inOracle iProcurement and Oracle Core Purchasing.

An approved requisition created in either Oracle iProcurement or Oracle Purchasing is sent to the third party application's purchasing system for the creation of a PO and for the completion of the procurement process.


When an approved requisition is changed or cancelled in Oracle iProcurement or OraclePurchasing, the change or cancellation information is processed and sent to the third party application system. When a PO is created in the third party system for a requisition that originated from Oracle iProcurement or Oracle Purchasing application information is sent back to Oracle Purchasing so that the Collaboration History is updated.

Purchase Order ModelThis model supports creation, change, and cancellation of a PO transaction in Oracle iProcurement and Oracle Core Purchasing. After a PO is generated from an approved requisition, it is sent for approval. Once approved, the PO transaction is sent to the thirdparty system to complete the procurement process. The requisition, remains in the Oracle Purchasing application. Only the approved PO transaction is sent to the third party system. This integration does not support blanket order purchasing.

The changes to an integrated PO are supported. When a change is made to the PO and saved in Oracle Purchasing, the status changes from Approved to Requires Reapproval.The status change causes the system to send a message to the third party system to block the purchase order against any further transactions. When the PO changes are approved and the status goes back to Approved, the updated PO is sent to the third party system.

Receiving and invoicing transaction details performed in a third party application against Oracle Purchasing-originated POs are sent back to Oracle Purchasing to update historical information. The quantities received and amounts invoiced are updated in Oracle Purchasing for inquiry and reconciliation purposes.

Purchase Order and Receipt ModelIn the purchase order model, an approved PO created in Oracle Purchasing is sent to the third party system. In this, the receiving transaction is also sent to the third party system after it is saved. A receiving transaction, whether from the Oracle iProcurement desktop receiving function or from Oracle Purchasing application, posts a single transaction to the third party system. The third party system is used to complete the procurement process. Any corrections or return-to-vendor receiving transactions followthe single transaction recording process. The invoiced amounts are updated to enable users view the transaction history and perform reconciliation tasks.

Business to Business IntegrationThis category supports the purchase order and change order business process model.

Purchase Order and Change Order ModelThe creation and change of POs in Oracle Purchasing are supported in this model. This model uses the XML messages generated in Oracle Purchasing for transmitting PO information to a supplier. The Process PO and Change PO transactions are recorded


and a corresponding XML document is generated and transmitted to a supplier's system. The supplier receives the XML Purchase Order or Change Order documents from the buyer and records them.

Oracle iProcurement Connector Business Model SummaryThese business process models are defined for use as a guide when designing your integration. They focus on implementing Oracle iProcurement with a third party systemand the different interactions that can occur. Transactional messages are operating unit controlled and let you enable different message sets and business models on an operating unit basis.

The following tables provide details of the messages that are supported in the models:

Oracle iProcurement to Third Party Application

From Oracle iProcurement to Third Party application

Model A Model B Model C Model D

Add Requisition Available n/a n/a n/a

Change Requisition Available n/a n/a n/a

Cancel Requisition Available n/a n/a n/a

Synchronize PO (Add, Change, Cancel)

n/a Available Available n/a

Change PO n/a n/a n/a Available

Cancel PO n/a Available Available n/a

Update Delivery n/a n/a Available n/a

Process PO n/a n/a n/a Available

Third Party to Oracle iProcurement

From Third Party application to Oracle iProcurement

Model A Model B Model C Model D

Synchronize Supplier Available Available Available Available


Synchronize Item Available Available Available Available

Synchronize UOM Available Available Available Available

Synchronize COA Available Available Available Available

Synchronize PO (Invoice, Inspection, and Receipt Totals)

n/a Available n/a n/a

Synchronize Currency Exchange Rate

Available Available Available Available

Synchronize Field (PO Status) Available Available Available Available

Setting Up the Oracle iProcurement Connector 2-1

2Setting Up the Oracle iProcurement

Connector

This topic provides the implementation steps to configure the Oracle iProcurement Connector. It also provides the steps to use the windows and reports specific to Oracle iProcurement Connector.


• Oracle iProcurement Connector Implementation Steps

• Using the Oracle iProcurement Connector

Oracle iProcurement Connector Implementation StepsThis topic contains the installation, configuration, and functional implementation steps required to install the Oracle iProcurement Connector.

Refer to the appropriate implementation guides for details regarding any other Oracle E-Business Suite Products referenced.

Refer to the updates to the installation guide, this guide and notices of required patches on Oracle Metalink before beginning this installation.

To set up for business object document (BOD) transmission:

1. Determine required messages.

2. Install and set up Oracle Applications.

3. Install Oracle iProcurement Connector.

4. Enable Messages (Business Objects Documents).

5. Change Oracle iProcurement Connector Message Confirmation Level.

6. Synchronize Oracle iProcurement with that of the Third Party System.


Determine Required MessagesDepending upon the needs of your enterprise, select the OAG BODs and their corresponding messages. The Oracle iProcurement Connector is used as both an A2A integration tool and a B2B integration tool. Refer to "Oracle iProcurement Connector Business Models" topic for details.

Install and Set Up Oracle Applications• Install Oracle Applications with the help of your database administrator.

• Perform a detailed analysis of your third party system configuration. With this analysis the appropriate setup choices are made for your Oracle Applications.

• Configure Oracle Applications according to the choices you made in your third party system.

Install Oracle iProcurement ConnectorRefer to Oracle iProcurement Connector Installation Guide for details.

Enable Messages (Business Objects Documents)The majority of messages or Business Object Documents (BODs) are enabled using the Business Object Effectivities (BOE) application window. The exceptions are the Cancel PO and Process PO messages, which are not affected by effectivities and must be explicitly set up for a given trading partner.

Refer to the Oracle XML Gateway User's Guide for further details.

Some BODs are operating unit controlled.

The outbound non-master-file oriented messages that are operating unit controlled are:

• Add Requisition

• Change Requisition


• Synchronize Purchase Order (PO)

• Change PO

• Cancel PO

• Process PO


• Update Delivery (receipt, return, and correction)

The Inbound non-master-file oriented message that are operating unit controlled are:

• Synchronize PO (Receiving and Invoicing Quantities)

• Synchronize Field (PO Status)

The inbound master file oriented messages are not operating unit controlled. They are:

• Synchronize Supplier

• Synchronize Item

• Synchronize UOM

• Synchronize COA

• Synchronize Currency Exchange Rate

• Process PO

• Change PO

Change Oracle iProcurement Connector Message Confirmation LevelThe messages or Business Object Documents (BODs) are delivered with a confirmation level. The target system returns an OAG confirmation BOD to confirm receipt. The following are the confirmation levels:

• Always: This level indicates that the target system always return an OAG Confirmation BOD. This is used in case of non-master files or transaction oriented messages where the receipt of these transactions has to be assured.

• Never: This level indicates that the target system never send an OAG Confirmation BOD. This is used in case of transactions with low business value and in cases where confirmation is not required.

• Error: This level indicates that the target system return an OAG Confirmation BOD only on error.

The settings for the confirmation levels are changed in the Trading Partner Setup of the XML Gateway model as follows:

• Search for the trading partner- OIPC Default TP in the XML Gateway Define Trading Partners window. This trading partner is seeded when the Oracle iProcurement Connector is installed. All the messages supported in the Oracle iProcurement Connector are seeded for this trading partner.


• Find the message to be changed and set the confirmation levels to:

• 0: To never confirm.

• 1: To confirm only on an error.

• 2: To always confirm.

Refer to the Oracle XML Gateway User's Guide for more information.

Synchronize Oracle iProcurement with a Third Party SystemOracle iProcurement is synchronized to a third party system as part of the setup process.

Oracle iProcurement Connector messages do not provide master file synchronization support. The files are not intended to be used for conversion or bootstrapping. Any conversions involving large data volumes must be performed by other means such as SQL Loader.

The master files and setups must be consistent in Oracle iProcurement and the third party system for the successful transfer of transactional messages.

The master files and setup information are maintained manually, or by the generation of an XML message. The following table provides a list of the files and setups to evaluate.

Serial Number

Reference Data iProcurement Connector Maintenance

Third Party SystemMaintenance

iProcurement Updated By

1 Accounting Calender

Manual Manual

2 Inventory and Purchasing Accounting Periods

Manual Manual

3 Approval Hierarchies

Manual Manual

4 Bank Accounts Manual Manual

5 Buyers Manual Define Buyers

Manual


6 Categories Manual Manual

7 Chart of Accounts (COA)

Manual SYNC COA BOD

8 Currencies Manual Manual

9 Employees Manual Manual

10 Exchange Rates Manual SYNC EXCHANGE RATE BOD

11 Items Manual SYNC ITEM BOD

12 Locations Manual Manual

13 Payment Terms Manual Manual

14 Sub-inventories Manual Manual

15 Suppliers and Supplier Sites

Manual SYNC SUPPLIER BOD

16 Tax Codes Manual Manual

17 Units of Measure(UOM)

Manual SYNC UOMGROUP BOD

Note: Refer to the " Messages" chapter for detailed BOD definitions.

Using the Oracle iProcurement ConnectorThe Oracle iProcurement Connector uses the XML Gateway Collaboration History feature to allow you to inspect the status of every transaction initiated within or received by the E-Business Suite. All messages are recorded and queried based on the document number, date, status, or document owner. Associated XML payloads can alsobe viewed.

Refer to Oracle XML Gateway User's Guide for more details on the Collaboration History and customization options.

Messages 3-1

3Messages

This topic discusses the function and technical details of each of the messages or OAG BODs currently supported by the Oracle iProcurement Connector. The messages are grouped by the direction of flow of information.


• Transaction Flow from Oracle E-Business Suite

• Transaction Flow into Oracle E-Business Suite

Transaction Flow from Oracle E-Business SuiteThis topic describes transactions outbound from the relevant E-Business Suite module as they are transformed to OAG objects.

The following supported transactions are discussed:

• Purchase Order

• Change Purchase Order

• Process Purchase Order

• Requisitions

• Cancel Purchase Order


• Receipts

Purchase OrderThe Oracle iProcurement Connector generates a SYNC PO BOD and places it on the outbound Advanced Queue on the occurrence of the following business events:


• Standard PO when the authorization status is set to Approved.

• Standard PO when the authorization status is set to Requires Reapproval.

• Standard PO when the closed status is set to Finally Closed.

• Planned PO when the authorization status is set to Approved.

• Planned PO when the authorization status is set to Requires Reapproval.

• Release when the authorization status is set to Approved.

• Release when the authorization status is set to Requires Reapproval.

SYNC PO Business Object DocumentThe SYNC PO BOD is used to synchronize POs between two Enterprise Resource Planning (ERP) systems. The triggering events for this BOD are CREATE PO and CHANGE PO.

Refer to "Sample XML" appendix for the sample OAG XML generated or consumed by the Oracle iProcurement Connector.

The following table contains details of SYNC PO BOD:

Serial Number Data Type Description

1 POHEADER Provides information that applies to the entire PO. Only one occurrence of POHEADER is allowed per SYNC PO BOD.

2 PARTNER Provides information definingName, Currency, and Payment method. Two occurrences of this data type are required.

3 ADDRESS Provides the PARTNER information. There is only oneaddress defined per PARTNER.

Messages 3-3


4 CONTACT Provides the contact person information for a PARTNER. There is only one CONTACT per PARTNER.

5 DISTRIBUTION Provides information about the accounting distributions associated with a POLINE.

6 POLINE Provides information about the Item, Item Description, Quantity, Unit Price, and Currency. One occurrence of the POLINE is required for each SYNC PO BOD.

7 SCHEDULE Provides information on the quantities and delivery or shipment dates associated with a POLINE.

8 POTERM Provides information about the payment due dates and discounts.

Change Purchase Order

CHANGE PO Business Object DocumentThe CHANGE PO BOD is used for transmitting changes to PO in the buyer's Oracle Application System.


The following table contains details of CHANGE PO BOD:


1 CNTROL AREA Provides information about the XML document.



2 SENDER Provides information about the system that sends the document.

3 DATETIME Provides the creation date and time of the XML document.

4 DATAAREA

CHANGE_PO

Provides information about the data included in the document.

5 POHEADER Provides information about the header level PO. One PO header is required per document.

6 POID Provides the ID for the PO.

7 POTYPE Provides information about the type of the PO.

8 PARTNER-

SUPPLIER

Provides information about the trading partner. Two occurrences of this data type are required.

9 PARTNER-

SOLD TO

Provides information about the buyer.

10 POTERM Provides information about the payment due dates and discounts.

11 POLINE Provides information about the PO line. This data type will occur one or more times. Atleast one PO line data type is required.

Messages 3-5


12 QUANTITY - ORDERED Provides information about the quantity of the item that isordered.

13 POLINENUM Provides information about the line number of the PO.

14 ITEM Provides the information about the identification of the product.

15 DATETIME-NEEDDELV Provides information about the need-by delivery date.

16 SCHEDULE Contains shipping information associated with the purchase order lines.

17 DROPSHIPDETAILS Contains information about DROPSHIP type order.

18 DISTPROJECT Contains information on distributions related to the purchase order lines.

Process Purchase Order

Process PO Business Object DocumentThe PROCESS PO BOD is used for transmitting a new PO created in the buyer's Oracle Application System.


The following table contains the details of PROCESS PO BOD:


S.No. Data Type Description

1 CNTROL

AREA

Provides information about the XML document.

2 BSR Provides the business service request name per OAGIS.

3 SENDER Provides information about the system that sends the document.

4 PO ORDERHDR Provides header level PO information. One PO header data type is required per document.

5 POID Provides the information about the unique ID for the PO.

6 POTYPE Provides information about the type of the PO.

7 PARTNER -SUPPLIER Provides information about the trading partner. Two occurrences of this data type are required.

8 PARTNER-

SOLD TO

Provides information about the buyer.

9 PO ORDERLIN Provides information about the PO line. Atleast one PO line data type is required.

10 QUANTITY

- ORDERED

Provides information about the quantity of the item required.

11 POLINENUM Provides information about the line number.

Messages 3-7

S.No. Data Type Description

12 ITEM Provides information about the identification of the product.

13 DATETIME-NEEDDELV Provides information about the need by delivery date.

14 DROPSHIPDETAILS Contains information about DROPSHIP type order.

15 DISTPROJECT Contains information on distributions related to the purchase order lines.

RequisitionsThe ADD REQUISITN BOD is used to synchronize requisitions between two ERP systems. This BOD is generated when a requisition is created in Oracle iProcurement or Oracle Purchasing application. ADD REQUISITN BOD is not generated for internal requisitions or requisitions generated from Oracle Inventory, Materials Requirement Planning (MRP) or Work in Process (WIP).

ADD REQUISITN Business Object DocumentThe ADD REQUISTN Business Service Request (BSR) is used for Requisitions from Oracle. The ADD REQUISITN BSR sends demand for goods or services to another business application for consideration of buying or obtaining the requested items. It is used to process updates, as part of a larger integration, or as a single tool for communicating demand to third party system.


The following table contains details of ADD REQUISITN BOD:


1 REHEADER Provides information that applies to the requisition. At least one occurrence of this data type is required.



2 PARTNER Provides PARTNER information such as Name, Currency, and payment method. This data type is optional.

3 ADDRESS Provides PARTNER location information. This data type is optional.

4 CONTACT Provides Name, Telephone, and other information to contact people associated with the PARTNER. This datatype is optional.

5 REQLINE Provides information that describes the requested item and its attributes. At least one occurrence of this data type is required for each REQHEADER data type.

6 REQSUBLINE Used if the item on the REQLINE needs to be dividedinto smaller units such as subcomponents or subassemblies. This is an optional data type.

Cancel Purchase OrderThe OIP Connector generates a CANCEL PO BOD and places it on the Outbound Advanced Queue (AQ) on the occurrence of the following business events:

• Standard PO canceled at the header level.

• Standard PO canceled at the line level.

• Release canceled at the header level.

• Release canceled at the line level.

Messages 3-9

CANCEL PO Business Object DocumentThe CANCEL PO BOD is used to communicate from one ERP system to another that a PO or a PO Line is canceled. The triggering event for this BOD is CANCEL PO.


The following table contains details of CANCEL PO BOD:


1 POHEADER Provides information that applies to the entire purchase order. Only one occurrence of POHEADER is allowed per CANCEL PO BOD.

2 POLINE Provides information about the Line Number, Item, Item Description, Quantity, Unit Price, and Currency. One occurrence of the POLINE is required for each CANCEL PO BOD.

3 SCHEDULE Provides information about the quantities and delivery or shipment dates associated with a POLINE.

The Oracle iProcurement Connector generates a CANCEL REQUISITN BOD and placesit on the Outbound AQ for a requisition canceled at the header level.

Cancel Requisition

CANCEL REQUISITN Business Object Document The CANCEL REQUISITN BOD is used to communicate from one ERP system to another that a requisition is no longer required. The triggering event for this BOD is CANCEL REQUISITN.


The following table has details of CANCEL REQUISITN BOD:



1 REQHEADER Provides information that applies to the entire requisition. Only one occurrence of REQHEADER is allowed per CANCEL REQUISITN BOD.

2 REQLINE Provides information on the Line Number of the requisition line.

ReceiptsThe UPDATE DELIVERY BOD is generated and placed on the outbound AQ on the occurrence of the following business events:

• Direct Receipt of goods.

• Standard Receipt that is delivered to Inventory or Expense.

• Correction to a Direct Receipt transaction.

• Correction to a Receipt delivered to Inventory or Expense transaction.

• Return goods transaction.

UPDATE DELIVERY Business Object DocumentThe UPDATE DELIVERY BOD is used to communicate from one ERP system to anotherthat a receipt transaction is processed. The triggering event for this BOD is CREATE RECEIPT.


The following table contains details of UPDATE DELIVERY BOD:


1 RECEITHDR Provides information that applies to the entire receipt. This data type is required.

Messages 3-11


2 RECEIPTLN Provides descriptive information of an item or product along with Quantity, and Price. Atleast one occurrence of this data type is required for each occurrence of the RECEIPTHDR data type.

Transaction Flow into Oracle E-Business SuiteFollowing are inbound transactions from the OAG object to the Oracle E-Business Suite.The following supported transactions are discussed:

• Supplier

• Unit of Measure (UOM)

• Item

• Exchange Rates

• Chart of Accounts (COA)

• Purchase Order Status

• Purchase Order Number

SupplierThe SYNC SUPPLIER BOD is generated when a new supplier is added or an existing supplier is changed in the third party system.

SYNC SUPPLIER Business Object DocumentThe triggering events for this BOD are CREATE SUPPLIER and CHANGE SUPPLIER.


The following table contains data type details of SYNC SUPPLIER BOD:



1 PARTNER Provides PARTNER information such as Supplier Name, and Address. This data type is required.

2 ADDRESS Provides address information of the PARTNER's location. This data type is optional.

3 CONTACT Provides Name, Telephone, and other contact informationof people associated with a PARTNER. This data type is optional.

Unit of Measure (UOM)The SYNC_UOMGROUP BOD is used when a UOM, UOM Class, or UOM Conversion is added in the third party system.

SYNC UOMGROUP Business Object DocumentThe triggering events for this BOD are create UOM, create UOM CLASS and create UOM conversion.


The following table contains data type details of SYNC UOMGROUP BOD:


1 UOMGRPHDR Provides the required data tags for defining the UOM and also the group it belongs to. UOM Group is synonymous with UOM Class.

Messages 3-13


2 UOMGRPDTL Represents the UOM relationships within a UOM Group.It provides the conversion quantity between one unit and another, and also the dimensions of the unit.

ItemThe SYNC ITEM is generated when an item is added or updated in the third party system.

SYNC ITEM Business Object DocumentThe SYNC ITEM BOD is used to manage items inbound into the Oracle E-Business Suite. The SYNC ITEM BOD supplies item information of goods or services to another business application. It is used to synchronize items used in finished goods, raw materials, Work-in-Process (WIP) or components in a Bill of Materials (BOM). It is not to be used for synchronizing Item quantities at inventory locations.

This BOD is also used individually or as part of a larger interface. The triggering events for this BOD are CREATE ITEM and CHANGE ITEM.


The following table contains data type details of SYNC ITEM BOD:


1 ITEMHEADER Provides information that describes an item and its attributes. This data type is required.

2 ITEMLOCATION Provides information on the location of an item and the attributes of that location in relation to the item. This data type is optional.



3 ITEMVALUE Provides attributes of cost or value for the item. This data type is optional.

Exchange RatesThe SYNC EXCHNGRATE BOD is generated when a daily exchange rate is added in the third party system.

SYNC EXCHNGRATE Business Object DocumentThe SYNC EXCHNGRATE Business Service Request is used to manage exchange rates inbound into Oracle E-Business Suite. SYNC EXCHNGRATE BOD enables update of currency exchange rates to be passed to other applications that have exchange rate tables.


The following table contains data type details of SYNC EXCHNGRATE BSR:


1. EXCHNGRATE Provides information that applies to the exchange rate. This data type is required.

Chart of Accounts (COA)The SYNC COA BOD is used when an accounting code value or a COA code is added or updated in the third party system.

SYNC COA Business Object DocumentThe SYNC COA BOD is used for Inbound COA messages inbound into Oracle E-Business Suite. The SYNC COA BSR facilitates distribution of General Ledger COA code values to other applications to be stored for validation purposes.


The following table contains data type details of SYNC COA:

Messages 3-15


1 COA Provides information that applies to the COA data. This data type is required.

Purchase Order StatusThe SYNC PO BOD is used when invoice and receipt information is processed in the third party system. PO status information that is be updated includes quantity received,quantity inspected, quantity billed, and amount billed.

SYNC PO Business Object DocumentRefer to "Sample XML" appendix for the sample OAG XML generated or consumed by the Oracle iProcurement Connector.

The following table contains data type details of SYNC PO BOD:


1 POHEADER Provides information that applies to the entire PO. This data type is required.

2 PARTNER Provides PARTNER information, for example, Name, Currency, payment method, etc. Two occurrences of this data type are required for the SYNC PO.

3 ADDRESS Provides PARTNER location information. This data type is optional.

4 CONTACT Provides Name, Telephone, and other information to contact people associated with the PARTNER. This datatype is optional.



5 POTERM Provides information about the payment terms for the PO or individual items on the PO.This data type is optional.

6 CHARGE Provides information about any miscellaneous charges such as freight, taxes or handling charges. This data type is optional.

7 DISTRIBUN Provides accounting distribution information associated with a BOD. This information exists for a header, a line, or a charge. This data type is optional.

8 POLINE Provides descriptive information of an item or a product, like Quantity, and Price.

9 POSUBLINE Used if the item on the POLINE needs to be divided into smaller items such as subcomponents or subassemblies. This data type is optional.

10 SCHEDULE Provides information about the dates and quantities for delivery or shipment of ordered products. This data type is used only as a part of the POLINE and cannot exist without it. This data type is optional.

Messages 3-17


11 POHISTORY Provides historical information usually updated by the system only. This includes a history of receipts, inspection activity, or invoice activity. This data type is optional.

Purchase Order NumberThe SYNC FIELD BOD is used when Requisitions are created in Oracle Purchasing and sent to a third party system.

SYNC FIELD Business Object DocumentThe SYNC FIELD BOD facilitates validation of data in multiple databases. It is used for online validation or as a single tool for synchronizing data.


Sample XML A-1

ASample XML

This topic lists the sample XML Code Structure.

This appendix covers the following topics:

• ADD REQUISITION

• CHANGE REQUISITION

• CANCEL REQUISITION

• SYNC PO

• SYNC PO (Release)

• CHANGE PO

• CANCEL PO

• UPDATE DELIVERY

• SYNC SUPPLIER

• SYNC ITEM

• SYNC UOMGROUP

• SYNC FIELD (PO Number)

• SYNC PO (Inbound Invoice and Receipt Totals)

• SYNC EXCHANGE RATE

• SYNC COA

• CONFIRM BOD

• PROCESS PO

ADD REQUISITIONThe following is a sample XML Document for the Add Requisition message:<ADD_REQUISITN_005>

A-2 Oracle iProcurement Connector Implementation Guide

<CNTROLAREA>

<BSR>

<VERB value="ADD"/>

<NOUN value="REQUISITN"/>

<REVISION value="005"/>

</BSR>

<SENDER>

<LOGICALID/>

<COMPONENT>ITG</COMPONENT>

<TASK>ADD_REQUISITN</TASK>

<REFERENCEID>ITG:00000825</REFERENCEID>

<CONFIRMATION>0</CONFIRMATION>

<LANGUAGE>US</LANGUAGE>

<CODEPAGE>US7ASCII</CODEPAGE>

<AUTHID>APPS</AUTHID>

</SENDER>

<DATETIME qualifier="CREATION">

<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>03</DAY>

<HOUR>10</HOUR>

<MINUTE>39</MINUTE>

<SECOND>26</SECOND>

<SUBSECOND>0000</SUBSECOND>

<TIMEZONE>+0000</TIMEZONE>

</DATETIME>

</CNTROLAREA>

<DATAAREA>

<ADD_REQUISITN>

<REQHEADER>

<DATETIME qualifier="DOCUMENT">

<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>03</DAY>

<HOUR>10</HOUR>

<MINUTE>30</MINUTE>

<SECOND>16</SECOND>



Sample XML A-3

</DATETIME>

<OPERAMT qualifier="EXTENDED" type="T">

<VALUE>240</VALUE>

<NUMOFDEC>0</NUMOFDEC>

<SIGN>+</SIGN>

<CURRENCY/>

<UOMVALUE>D</UOMVALUE>

<UOMNUMDEC/>

<UOM/>

</OPERAMT>

<REQUISTNID>168</REQUISTNID>

<APPROVED>1</APPROVED>

<CONTRACTB/>

<CONTRACTS/>

<COSTCENTER/>

<DELIVERTO/>

<DESCRIPTN>Expense item with multiple account distributions and supplier.</DESCRIPTN>

<DOCKID/>

<FUND/>

<GLENTITYS/>

<GLNOMACCT/>

<HDRSTATUS/>

<NOTES index="1"/>

<OPRAMTAUTH/>

<POENTITY>1653</POENTITY>

<SALESORDID/>

<BUYERID/>

<PLANNERID/>

<REQUESTER>224</REQUESTER>

<USERAREA>

<ORACLEITG.ADD_REQUISITN_005.REQHEADER.USERAREA>

<ORACLEITG.ATTRIBUTE index="1"/>
















<ORACLEITG.TO_PO_INTERNAL/>

<ORACLEITG.TO_MISC/>

<ORACLEITG.TO_APPROVER/>

<ORACLEITG.TO_BUYER/>

<ORACLEITG.TO_PAYABLES/>

<ORACLEITG.TO_RECEIVER/>

<ORACLEITG.TO_SUPPLIER/>

</ORACLEITG.ADD_REQUISITN_005.REQHEADER.USERAREA>

</USERAREA>

</REQHEADER>

<REQLINE>

<DATETIME qualifier="REQUIRED">

<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>05</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>

<QUANTITY qualifier="ORDERED">

<VALUE>2</VALUE>


<SIGN>+</SIGN>

<UOM>ST</UOM>

</QUANTITY>

<OPERAMT qualifier="UNIT" type="T">

<VALUE>120</VALUE>


<SIGN>+</SIGN>

Sample XML A-5

<CURRENCY/>


<UOMNUMDEC/>

<UOM/>

</OPERAMT>

<REQLINENUM>1</REQLINENUM>

<APPROVED/>

<BUYERID/>

<COMMODITY index="1">MISC.MISC</COMMODITY>

<CONTRACTB/>

<CONTRACTS/>

<COSTCENTER/>

<DELIVERTO>224</DELIVERTO>

<DOCKID/>

<DRAWING/>

<FREIGHTCLS/>

<FUND/>

<GLENTITYS/>

<GLNOMACCT/>

<HAZRDMATL/>

<ITEMRV/>

<ITEMTYPE/>

<ITEMX/>

<NOTES index="1">note</NOTES>

<PLANNERID/>


<PROPERTY index="1"/>


<REQLNSTAT/>

<REQUESTER/>

<SALESORDID/>

<SERIALNUM/>

<SITELEVEL index="1">Acme NY Storage 1</SITELEVEL>

<SITELEVEL index="2"/>

<UPC/>

<DESCRIPTN>D1- ITG Test D1</DESCRIPTN>

<ITEM/>

<USERAREA>

<ORACLEITG.ADD_REQUISITN_005.REQLINE.USERAREA>


<ORACLEITG.EXPENSE>Y</ORACLEITG.EXPENSE>

<ORACLEITG.REFATTRIBUTE>K</ORACLEITG.REFATTRIBUTE>






<ORACLEITG.ATTRIBUTE index="6">K</ORACLEITG.ATTRIBUTE>

















</ORACLEITG.ADD_REQUISITN_005.REQLINE.USERAREA>

</USERAREA>

<PARTNER>

<NAME index="1">Acme NA HQ</NAME>

<PARTNRID>224</PARTNRID>

<PARTNRTYPE>Employee</PARTNRTYPE>

<PARTNRIDX>1961</PARTNRIDX>

<TAXEXEMPT/>

<TAXID/>

<USERAREA>

<ORACLEITG.ADD_REQUISITN_005.REQLINE.PARTNER.USERAREA>

<ORACLEITG.BILLFLG>Y</ORACLEITG.BILLFLG>

<ORACLEITG.SHIPFLG>N</ORACLEITG.SHIPFLG>

<ORACLEITG.RECFLG>Y</ORACLEITG.RECFLG>

</ORACLEITG.ADD_REQUISITN_005.REQLINE.PARTNER.USERAREA>

Sample XML A-7

</USERAREA>

<ADDRESS>

<ADDRLINE index="1">4777 86TH Street</ADDRLINE>

<ADDRLINE index="2"/>


<ADDRTYPE>Delivery</ADDRTYPE>

<CITY>New York</CITY>

<COUNTRY>US</COUNTRY>

<COUNTY>New York</COUNTY>

<DESCRIPTN>Acme North American Headquarters</DESCRIPTN>

<FAX index="1"/>

<POSTALCODE>10299</POSTALCODE>

<STATEPROVN>NY</STATEPROVN>

<TELEPHONE index="1"/>



</ADDRESS>

<CONTACT>

<NAME index="1">Acme NY, Mr. Test</NAME>

<DESCRIPTN/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<PARTNER>

<NAME index="1">Acme NY Storage 1</NAME>

<PARTNRID>NY1</PARTNRID>

<PARTNRTYPE>ShipTo</PARTNRTYPE>


<TAXEXEMPT>0</TAXEXEMPT>

<TAXID/>

<USERAREA>


<ORACLEITG.BILLFLG>N</ORACLEITG.BILLFLG>

<ORACLEITG.SHIPFLG>Y</ORACLEITG.SHIPFLG>



</USERAREA>


<ADDRESS>

<ADDRLINE index="1">34555 Bellcrest</ADDRLINE>



<ADDRTYPE>Receiving</ADDRTYPE>

<CITY>Lansing</CITY>


<COUNTY>Eaton</COUNTY>

<DESCRIPTN>Acme NY Storage 1</DESCRIPTN>

<FAX index="1"/>


<STATEPROVN>MI</STATEPROVN>




</ADDRESS>

<CONTACT>

<NAME index="1"/>

<DESCRIPTN/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<PARTNER>

<NAME index="1">Donald-DISNEY</NAME>

<ONETIME>0</ONETIME>

<PARTNRID>DISNEY</PARTNRID>

<PARTNRTYPE>Supplier</PARTNRTYPE>

<CURRENCY>USD</CURRENCY>

<DESCRIPTN/>


<TAXEXEMPT/>

<TAXID/>

<USERAREA>


<ORACLEITG.BANKNAM/>

<ORACLEITG.BANKACT/>

<ORACLEITG.USFLAG/>

Sample XML A-9


</USERAREA>

<ADDRESS>




<ADDRTYPE/>

<CITY/>


<COUNTY/>

<DESCRIPTN>-ANP1</DESCRIPTN>

<FAX index="1"/>

<POSTALCODE/>

<STATEPROVN/>




<USERAREA>

<ORACLEITG.ADD_REQUISITN_005.REQLINE.PARTNER.ADDRESS.USERAREA>

<ORACLEITG.VATCODE/>

<ORACLEITG.PURSITE>Y</ORACLEITG.PURSITE>

<ORACLEITG.PAYSITE>N</ORACLEITG.PAYSITE>

<ORACLEITG.RFQSITE>N</ORACLEITG.RFQSITE>

<ORACLEITG.PCSITE>Y</ORACLEITG.PCSITE>

</ORACLEITG.ADD_REQUISITN_005.REQLINE.PARTNER.ADDRESS.USERAREA>

</USERAREA>

</ADDRESS>

</PARTNER>

<REQSUBLINE>

<QUANTITY qualifier="ITEM">

<VALUE>1</VALUE>


<SIGN>+</SIGN>

<UOM>ST</UOM>

</QUANTITY>

<DRAWING/>

<ITEMRV/>

<ITEMRVX/>

<NOTES index="1"/>

Sample XML A-11












</ORACLEITG.ADD_REQUISITN_005.REQLINE.REQSUBLINE.USERAREA>

</USERAREA>

</REQSUBLINE>

<REQSUBLINE>


<VALUE>1</VALUE>


<SIGN>+</SIGN>

<UOM>ST</UOM>

</QUANTITY>

<DRAWING/>

<ITEMRV/>

<ITEMRVX/>

<NOTES index="1"/>















Sample XML A-13

</REQLINE>

</ADD_REQUISITN>

</DATAAREA>

</ADD_REQUISITN_005>

CHANGE REQUISITIONThe following is a sample XML Document for the Change Requisition message:<CHANGE_REQUISITN_005>

<CNTROLAREA>

<BSR>

<VERB value="CHANGE"/>



</BSR>

<SENDER>

<LOGICALID>1111</LOGICALID>


<TASK>CHANGE_REQUISITN</TASK>






</SENDER>


<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>28</DAY>

<HOUR>14</HOUR>

<MINUTE>15</MINUTE>

<SECOND>58</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<CHANGE_REQUISITN>

<REQHEADER>

Sample XML A-15

<ORACLEITG.CHANGE_REQUISITN_005.REQHEADER.USERAREA>
















</ORACLEITG.CHANGE_REQUISITN_005.REQHEADER.USERAREA>

</USERAREA>

</REQHEADER>

<REQLINE>

<DATETIME qualifier="REQUIRED">

<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>30</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>


<VALUE>10</VALUE>


<SIGN>+</SIGN>

<CURRENCY/>


<UOMNUMDEC/>

<UOM/>

</OPERAMT>



<VALUE>222</VALUE>


<SIGN>+</SIGN>

<UOM>ST</UOM>

</QUANTITY>


<APPROVED/>

<BUYERID/>


<CONTRACTB/>

<CONTRACTS/>

<COSTCENTER/>

<DELIVERTO>224</DELIVERTO>

<DESCRIPTN>test shri</DESCRIPTN>

<DOCKID/>

<DRAWING/>

<FREIGHTCLS/>

<FUND/>

<GLENTITYS/>

<GLNOMACCT/>

<HAZRDMATL/>

<ITEM/>

<ITEMRV/>

<ITEMTYPE/>

<ITEMX/>

<NOTES index="1">test</NOTES>

<PLANNERID/>




<REQLNSTAT/>

<REQUESTER/>

<SALESORDID/>

<SERIALNUM/>

<SITELEVEL index="1">Acme NY Storage 1</SITELEVEL>

<SITELEVEL index="2"/>

<UPC/>

<USERAREA>

Sample XML A-17

<ORACLEITG.CHANGE_REQUISITN_005.REQLINE.USERAREA>














<ORACLEITG.ATTRIBUTE index="13">0</ORACLEITG.ATTRIBUTE>



</ORACLEITG.CHANGE_REQUISITN_005.REQLINE.USERAREA>

</USERAREA>

<PARTNER>

<NAME index="1">Acme US</NAME>




<TAXEXEMPT/>

<TAXID/>

<USERAREA>

<ORACLEITG.CHANGE_REQUISITN_005.REQLINE.PARTNER.USERAREA>




</ORACLEITG.CHANGE_REQUISITN_005.REQLINE.PARTNER.USERAREA>

</USERAREA>

<ADDRESS>

<ADDRLINE index="1">1190 Madison Avenue</ADDRLINE>

<ADDRLINE index="2">Suite 2300</ADDRLINE>


<ADDRTYPE>Delivery</ADDRTYPE>





<DESCRIPTN>Acme United States Address</DESCRIPTN>

<FAX index="1"/>






</ADDRESS>

<CONTACT>


<DESCRIPTN/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<PARTNER>






<TAXID/>

<USERAREA>






</USERAREA>

<ADDRESS>

<ADDRLINE index="1">34555 Bellcrest</ADDRLINE>



<ADDRTYPE>Receiving</ADDRTYPE>

<CITY>Lansing</CITY>


Sample XML A-19

<COUNTY>Eaton</COUNTY>

<DESCRIPTN>Acme NY Storage 1</DESCRIPTN>

<FAX index="1"/>


<STATEPROVN>MI</STATEPROVN>




</ADDRESS>

<CONTACT>

<NAME index="1"/>

<DESCRIPTN/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<PARTNER>

<NAME index="1">shriram-SHRI508</NAME>


<PARTNRID>SHRI508</PARTNRID>



<DESCRIPTN/>


<TAXEXEMPT/>

<TAXID/>

<USERAREA>


<ORACLEITG.BANKNAM/>

<ORACLEITG.BANKACT/>

<ORACLEITG.USFLAG/>


</USERAREA>

<ADDRESS>

<ADDRLINE index="1">34077 Paseo Padre Pkwy</ADDRLINE>



<ADDRTYPE/>


<CITY>Fremont</CITY>


<COUNTY/>

<DESCRIPTN>FREMONT-ANP1</DESCRIPTN>

<FAX index="1"/>


<STATEPROVN>CA</STATEPROVN>




<USERAREA>

<ORACLEITG.CHANGE_REQUISITN_005.REQLINE.PARTNER.ADDRESS.USERAREA>






</ORACLEITG.CHANGE_REQUISITN_005.REQLINE.PARTNER.ADDRESS.USERAREA>

</USERAREA>

</ADDRESS>

<CONTACT>

<NAME index="1"/>

<DESCRIPTN/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<REQSUBLINE>


<VALUE>222</VALUE>


<SIGN>+</SIGN>

<UOM>ST</UOM>

</QUANTITY>

<DRAWING/>

<ITEMRV/>

<ITEMRVX/>

<NOTES index="1"/>

Sample XML A-21






<PROPERTY index="6">000000010006-0000</PROPERTY>


<PROPERTY index="8">MURTHY - 10</PROPERTY>

<PROPERTY index="9">M02</PROPERTY>

<PROPERTY index="10">M04</PROPERTY>






















<ITEM/>

<DESCRIPTN>test shri</DESCRIPTN>

<USERAREA>

<ORACLEITG.CHANGE_REQUISITN_005.REQLINE.REQSUBLINE.USERAREA>

















</ORACLEITG.CHANGE_REQUISITN_005.REQLINE.REQSUBLINE.USERAREA>

</USERAREA>

</REQSUBLINE>

</REQLINE>

</CHANGE_REQUISITN>

</DATAAREA>

</CHANGE_REQUISITN_005>

CANCEL REQUISITIONThe following is a sample XML Document for the Cancel Requisition message:<CANCEL_REQUISITN_005>

<CNTROLAREA>

<BSR>

<VERB value="CANCEL"/>



</BSR>

<SENDER>

<LOGICALID/>


<TASK>CANCEL_REQUISITN</TASK>






</SENDER>

Sample XML A-23


<YEAR>2002</YEAR>

<MONTH>11</MONTH>

<DAY>25</DAY>

<HOUR>15</HOUR>

<MINUTE>01</MINUTE>

<SECOND>42</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<CANCEL_REQUISITN>

<REQHEADER>


<SITELEVEL index="1">1653</SITELEVEL>

</REQHEADER>

<REQLINE>


</REQLINE>

</CANCEL_REQUISITN>

</DATAAREA>

</CANCEL_REQUISITN_005>

SYNC POThe following is a sample XML Document for the Synchronize PO message:<SYNC_PO_007>

<CNTROLAREA>

<BSR>

<VERB value="SYNC">SYNC</VERB>

<NOUN value="PO">PO</NOUN>

<REVISION value="007">007</REVISION>

</BSR>

<SENDER>



<TASK>SYNC_PO</TASK>







</SENDER>


<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>20</DAY>

<HOUR>15</HOUR>

<MINUTE>44</MINUTE>

<SECOND>46</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<SYNC_PO>

<POHEADER>


<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>20</DAY>

<HOUR>15</HOUR>

<MINUTE>43</MINUTE>

<SECOND>28</SECOND>



</DATETIME>


<VALUE>100</VALUE>


<SIGN>+</SIGN>


<UOMVALUE>1</UOMVALUE>

<UOMNUMDEC>0</UOMNUMDEC>

<UOM/>

</OPERAMT>

<POID>160</POID>

Sample XML A-25

<SYNCIND>A</SYNCIND>

<BUYERID>Acme NY, Mr. Test</BUYERID>

<DELIVERTO>Acme US</DELIVERTO>

<NOTES index="1">test</NOTES>


<PORELEASE/>

<POSTATUS>APPROVED</POSTATUS>

<POTYPE>STANDARD</POTYPE>

<TAXWHEXMPT/>

<USERAREA>

<ORACLEITG.SYNC_PO_007.POHEADER.USERAREA>


<ORACLEITG.MISCELLANEOUS/>






</ORACLEITG.SYNC_PO_007.POHEADER.USERAREA>

</USERAREA>

<PARTNER>

<NAME index="1">Shriram-SHRI505</NAME>


<PARTNRID>SHRI505</PARTNRID>



<DESCRIPTN>FREMONT-ANP1</DESCRIPTN>



<TAXID/>

<USERAREA>

<ORACLEITG.SYNC_PO_007.POHEADER.PARTNER.USERAREA>

<ORACLEITG.BILLFLG/>

<ORACLEITG.SHIPFLG/>

<ORACLEITG.RECFLG/>

</ORACLEITG.SYNC_PO_007.POHEADER.PARTNER.USERAREA>

</USERAREA>

<ADDRESS>

<ADDRLINE index="1">34770 Campu dr.</ADDRLINE>




<ADDRTYPE/>

<CITY>Fremont</CITY>


<COUNTY/>

<DESCRIPTN/>

<FAX index="1"/>




<USERAREA>

<ORACLEITG.SYNC_PO_007.POHEADER.PARTNER.ADDRESS.USERAREA>





</ORACLEITG.SYNC_PO_007.POHEADER.PARTNER.ADDRESS.USERAREA>

</USERAREA>

</ADDRESS>

<CONTACT>

<NAME index="1">Shriram </NAME>

<DESCRIPTN/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<PARTNER>

<NAME index="1">Vision Operations</NAME>

<ONETIME/>

<PARTNRID>V1</PARTNRID>

<PARTNRTYPE>SoldTo</PARTNRTYPE>


<DESCRIPTN/>


<TAXEXEMPT/>

<TAXID/>

<USERAREA>

Sample XML A-27






</USERAREA>

<ADDRESS>

<ADDRLINE index="1">90 Fifth Avenue</ADDRLINE>



<ADDRTYPE/>




<DESCRIPTN>NYC, Vision Operations HQ</DESCRIPTN>

<FAX index="1"/>

<POSTALCODE>10022-3422</POSTALCODE>



<USERAREA/>

</ADDRESS>

<CONTACT>


<DESCRIPTN/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<PARTNER>


<ONETIME/>



<CURRENCY/>




<TAXID/>

Sample XML A-29

<POTERM>

<DESCRIPTN>Scheduled for payment 30 days from the invoice date (invoice terms date = system date, goods received date, invoice date or invoice received date). Invoice terms date can default from supplier header, site, PO, system default, etc.</DESCRIPTN>

<TERMID>30 Net (terms date + 30)</TERMID>

<DAYOFMONTH/>

<PROXMONTH/>


<VALUE/>

<NUMOFDEC/>

<SIGN/>


<UOMVALUE/>

<UOMNUMDEC/>

<UOM/>

</OPERAMT>

</POTERM>

</POHEADER>

<POLINE>

<DATETIME qualifier="NEEDDELV">

<YEAR>2002</YEAR>

<MONTH>07</MONTH>

<DAY>03</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>


<TIMEZONE>-8.00</TIMEZONE>

</DATETIME>


<VALUE>10</VALUE>


<SIGN>+</SIGN>




<UOM>Ea</UOM>

</OPERAMT>


Sample XML A-31





<ORACLEITG.DISTRIBUTN/>

<ORACLEITG.PARTNER/>

</ORACLEITG.SYNC_PO_007.POLINE.USERAREA>

</USERAREA>

<DISTRIBUTN>


<VALUE>100</VALUE>


<SIGN>+</SIGN>




<UOM>Ea</UOM>

</OPERAMT>

<COSTCENTER>510</COSTCENTER>

<ELEMENT index="1">ACUS</ELEMENT>

<ELEMENT index="2">510</ELEMENT>




<ELEMENT index="6">000000010006-0000</ELEMENT>


<ELEMENT index="8">MURTHY - 10</ELEMENT>

<ELEMENT index="9">M02</ELEMENT>

<ELEMENT index="10">M04</ELEMENT>

<ELEMENT index="11"/>





















<GLENTITYS>630</GLENTITYS>

<GLNOMACCT>7530</GLNOMACCT>

<PROJECT/>

<UNIT>Acme NY Storage 1</UNIT>

<USERAREA>

<ORACLEITG.SYNC_PO_007.POLINE.DISTRIBUTN.USERAREA>

<ORACLEITG.DISTRID>7507</ORACLEITG.DISTRID>

<ORACLEITG.SCHEDLID>7704</ORACLEITG.SCHEDLID>

<ORACLEITG.LINENUM>1</ORACLEITG.LINENUM>
















<ORACLEITG.REQUISTNID/>

<ORACLEITG.REQLINENUM/>

</ORACLEITG.SYNC_PO_007.POLINE.DISTRIBUTN.USERAREA>

</USERAREA>

</DISTRIBUTN>

Sample XML A-33

<PARTNER>

<NAME index="1">SHRIRAM</NAME>

<ONETIME/>



<CURRENCY/>

<DESCRIPTN/>

<PARTNRIDX/>


<TAXID/>

<USERAREA>

<ORACLEITG.SYNC_PO_007.POLINE.PARTNER.USERAREA>




</ORACLEITG.SYNC_PO_007.POLINE.PARTNER.USERAREA>

</USERAREA>

<ADDRESS>




<ADDRTYPE/>

<CITY/>

<COUNTRY/>

<COUNTY/>

<DESCRIPTN/>

<FAX index="1"/>

<POSTALCODE/>

<STATEPROVN/>


<USERAREA/>

</ADDRESS>

<CONTACT>

<NAME index="1"/>

<DESCRIPTN/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>


</PARTNER>

<PARTNER>


<ONETIME/>



<CURRENCY/>

<DESCRIPTN>Acme US</DESCRIPTN>



<TAXID/>

<USERAREA>




</USERAREA>

<ADDRESS>




<ADDRTYPE/>





<FAX index="1"/>




<USERAREA/>

</ADDRESS>

</PARTNER>

<SCHEDULE>


<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>20</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

Sample XML A-35

<SECOND>00</SECOND>



</DATETIME>


<VALUE>10</VALUE>


<SIGN>+</SIGN>

<UOM>Ea</UOM>

</QUANTITY>

<PSCLINENUM>1</PSCLINENUM>

<USERAREA>

<ORACLEITG.SYNC_PO_007.POLINE.SCHEDULE.USERAREA>
























</ORACLEITG.SYNC_PO_007.POLINE.SCHEDULE.USERAREA>

</USERAREA>

</SCHEDULE>


</POLINE>

</SYNC_PO>

</DATAAREA>

</SYNC_PO_007>

SYNC PO (Release)The following is a sample XML Document for the Synchronize PO (Release) message:<SYNC_PO_007>

<CNTROLAREA>

<BSR>




</BSR>

<SENDER>

<LOGICALID/>


<TASK>SYNC_PO_RELEASE</TASK>






</SENDER>


<YEAR>2002</YEAR>

<MONTH>12</MONTH>

<DAY>13</DAY>

<HOUR>10</HOUR>

<MINUTE>44</MINUTE>

<SECOND>48</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<SYNC_PO>

<POHEADER>

Sample XML A-37


<YEAR>2002</YEAR>

<MONTH>12</MONTH>

<DAY>13</DAY>

<HOUR>10</HOUR>

<MINUTE>41</MINUTE>

<SECOND>44</SECOND>



</DATETIME>


<VALUE>4700</VALUE>


<SIGN>+</SIGN>




<UOM/>

</OPERAMT>

<POID>130</POID>


<BUYERID>Acme NY, Mr. Test</BUYERID>

<DELIVERTO>Acme US</DELIVERTO>

<NOTES index="1"/>


<PORELEASE>4</PORELEASE>

<POSTATUS>APPROVED</POSTATUS>

<POTYPE>BLANKET</POTYPE>

<TAXWHEXMPT/>

<USERAREA>

<ORACLEITG.SYNC_PO_007.POHEADER.USERAREA>








</ORACLEITG.SYNC_PO_007.POHEADER.USERAREA>


</USERAREA>

<PARTNER>

<NAME index="1">Donald-DISNEY</NAME>


<PARTNRID>DISNEY</PARTNRID>



<DESCRIPTN/>



<TAXID/>

<USERAREA>


<ORACLEITG.BILLFLG/>

<ORACLEITG.SHIPFLG/>

<ORACLEITG.RECFLG/>


</USERAREA>

<ADDRESS>




<ADDRTYPE/>

<CITY/>


<COUNTY/>

<DESCRIPTN>-ANP1</DESCRIPTN>

<FAX index="1"/>

<POSTALCODE/>

<STATEPROVN/>


<USERAREA>







</USERAREA>

Sample XML A-39

</ADDRESS>

<CONTACT>

<NAME index="1">Donald Duck </NAME>

<DESCRIPTN/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<PARTNER>


<ONETIME/>

<PARTNRID>V1</PARTNRID>



<DESCRIPTN>NYC, Vision Operations HQ</DESCRIPTN>


<TAXEXEMPT/>

<TAXID/>

<USERAREA>






</USERAREA>

<ADDRESS>




<ADDRTYPE/>




<DESCRIPTN/>

<FAX index="1"/>




Sample XML A-41



<USERAREA>



<ORACLEITG.PURSITE/>

<ORACLEITG.PAYSITE/>

<ORACLEITG.RFQSITE/>

<ORACLEITG.PCSITE/>


</USERAREA>

</ADDRESS>

<CONTACT>


<DESCRIPTN/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<POTERM>



<DAYOFMONTH/>

<PROXMONTH/>


<VALUE/>

<NUMOFDEC/>

<SIGN/>

<CURRENCY/>

<UOMVALUE/>

<UOMNUMDEC/>

<UOM/>

</OPERAMT>

</POTERM>

</POHEADER>

<POLINE>



<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>


<VALUE>25</VALUE>


<SIGN>+</SIGN>




<UOM>ST</UOM>

</OPERAMT>


<VALUE>354</VALUE>


<SIGN>+</SIGN>

<UOM>ST</UOM>

</QUANTITY>



<CONTRACTS/>

<FRGHTCLS>Due</FRGHTCLS>

<HAZRDMATL/>

<ITEMRV/>

<ITEMTYPE>Inv. Blanket</ITEMTYPE>

<NOTES index="1"/>


<ITEM>KLMAT157</ITEM>

<ITEMX/>

<USERAREA>

<ORACLEITG.SYNC_PO_007.POLINE.USERAREA>

<ORACLEITG.STATUS>OPEN</ORACLEITG.STATUS>

Sample XML A-43

<ORACLEITG.EXPENSE>N</ORACLEITG.EXPENSE>

<ORACLEITG.REFATTRIBUTE>I</ORACLEITG.REFATTRIBUTE>

<ORACLEITG.ATTRIBUTE index="1">I</ORACLEITG.ATTRIBUTE>






















<ORACLEITG.DISTRIBUTN/>

<ORACLEITG.PARTNER/>

</ORACLEITG.SYNC_PO_007.POLINE.USERAREA>

</USERAREA>

<DISTRIBUTN>


<VALUE>4700</VALUE>


<SIGN>+</SIGN>




<UOM/>

</OPERAMT>

<COSTCENTER>510</COSTCENTER>
































<GLENTITYS>630</GLENTITYS>

<GLNOMACCT>5110</GLNOMACCT>

<PROJECT/>

<UNIT>Acme NY Storage 1</UNIT>

<USERAREA>

<ORACLEITG.SYNC_PO_007.POLINE.DISTRIBUTN.USERAREA>



<ORACLEITG.LINENUM>1</ORACLEITG.LINENUM>

Sample XML A-45

















<ORACLEITG.REQLINENUM/>

</ORACLEITG.SYNC_PO_007.POLINE.DISTRIBUTN.USERAREA>

</USERAREA>

</DISTRIBUTN>

<PARTNER>

<NAME index="1"/>

<ONETIME/>

<PARTNRID/>


<CURRENCY/>

<DESCRIPTN/>

<PARTNRIDX/>


<TAXID/>

<USERAREA>






</USERAREA>

<ADDRESS>


Sample XML A-47


<ADDRTYPE/>





<FAX index="1"/>




<USERAREA/>

</ADDRESS>

</PARTNER>

<SCHEDULE>


<YEAR>2002</YEAR>

<MONTH>12</MONTH>

<DAY>16</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>


<VALUE>188</VALUE>


<SIGN>+</SIGN>

<UOM>ST</UOM>

</QUANTITY>


<USERAREA>

<ORACLEITG.SYNC_PO_007.POLINE.SCHEDULE.USERAREA>


















</ORACLEITG.SYNC_PO_007.POLINE.SCHEDULE.USERAREA>

</USERAREA>

</SCHEDULE>

</POLINE>

</SYNC_PO>

</DATAAREA>

</SYNC_PO_007>

CHANGE POThe following is a sample XML Document for the Change PO message:<CHANGE_PO_006>

<CNTROLAREA>

<BSR>

<VERB value="SYNC">CHANGE</VERB>



</BSR>

<SENDER>

<LOGICALID>ORACLE</LOGICALID>

<COMPONENT>PURCHASING</COMPONENT>

<TASK>POISSUE</TASK>

<REFERENCEID>SCMX7RW3.US.ORACLE.COM:oracle.apps.po.event.xmlpo:76855-307924</REFERENCEID>



<CODEPAGE>UTF8</CODEPAGE>


</SENDER>

Sample XML A-49

<DATETIME qualifier="CREATION" type="T" index="1">>

<YEAR>2006</YEAR>

<MONTH>10</MONTH>

<DAY>03</DAY>

<HOUR>23</HOUR>

<MINUTE>37</MINUTE>

<SECOND>16</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<CHANGE_PO>

<POHEADER>

<DATETIME qualifier="DOCUMENT" type="T" index="1">

<YEAR>2006</YEAR>

<MONTH>10</MONTH>

<DAY>03</DAY>

<HOUR>22</HOUR>

<MINUTE>36</MINUTE>

<SECOND>36</SECOND>



</DATETIME>


<VALUE>166179</VALUE>


<SIGN>+</SIGN>




<UOM/>

</OPERAMT>

<POID>7954</POID>

<BUYERID>PRABHU, Mrs. SRIDEVI</BUYERID>

<CONTRACTB/>

<CONTRACTS/>

<DESCRIPTN/>

<NOTES index="1"/>


<POSTATUS>OPEN</POSTATUS>


<REQUESTER/>

<SITELEVEL index ="1">

<USERAREA>

<FOB>

<DESCRIPTN>Vendor's responsibility ceases upon transfer to carrier</DESCRIPTN>

<TERMID>Origin</TERMID>

</FOB>

<FTTERM>

<DESCRIPTN>Buyer pays freight</DESCRIPTN>

<TERMID>Due</TERMID>

</FTTERM>

<TANDC/>

<REVISIONNUM>1</REVISIONNUM>

<ACKREQUEST>N</ACKREQUEST>

<EXCHRATE/>

<DATETIME qualifier="EXCHRATEDATE">

<YEAR>2006</YEAR>

<MONTH>10</MONTH>

<DAY>03</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>

<CONFIRM>N</CONFIRM>

<SHIPPINGCONTROL/>

<DATETIME qualifier="APPREQ" type="T" index="1">

<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

Sample XML A-51

</DATETIME>

<DATETIME qualifier="ACTSTART" type="T" index="1">

<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>

<DATETIME qualifier="ACTEND" type="T" index="1">

<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>

<DFFPOHEADER>

<ATTRIBUTE1/>

<ATTRIBUTE2/>

<ATTRIBUTE3/>

<ATTRIBUTE4/>

<ATTRIBUTE5/>

<ATTRIBUTE6/>

<ATTRIBUTE7/>

<ATTRIBUTE8/>

<ATTRIBUTE9/>

<ATTRIBUTE10/>

<ATTRIBUTE11/>

<ATTRIBUTE12/>

<ATTRIBUTE13/>

<ATTRIBUTE14/>

<ATTRIBUTE15/>

<ATTRIBUTE16/>

</DFFPOHEADER>

Sample XML A-53

<ATTRIBUTE11/>

<ATTRIBUTE12/>

<ATTRIBUTE13/>

<ATTRIBUTE14/>

<ATTRIBUTE15/>

<ATTRIBUTE16/>

</DFFVENDOR>

<CUSTOMERNUM/>

</USERAREA>

<ADDRESS>

<ADDRLINE index="1">Test Site for SCTC transactions</ADDRLINE>

<ADDRLINE index="2">QA Zone</ADDRLINE>

<ADDRLINE index="3">Certification Quadrant</ADDRLINE>

<ADDRTYPE/>

<CITY>San Francisco</CITY>


<COUNTY/>

<DESCRIPTN>SUPPLIER SITE</DESCRIPTN>

<FAX index="1"/>

<POSTALCODE/>

<STATEPROVN>California</STATEPROVN>

<TAXJRSDCTN/>

<TELEPHONE index="1"></TELEPHONE>

<URL/>

<USERAREA>

<DFFVENDORSITE>

<ATTRIBUTE1/>

<ATTRIBUTE2/>

<ATTRIBUTE3/>

<ATTRIBUTE4/>

<ATTRIBUTE5/>

<ATTRIBUTE6/>

<ATTRIBUTE7/>

<ATTRIBUTE8/>

<ATTRIBUTE9/>

<ATTRIBUTE10/>

<ATTRIBUTE11/>

<ATTRIBUTE12/>

<ATTRIBUTE13/>

Sample XML A-55



<URL/>

<USERAREA>

</ADDRESS>

<CONTACT>

<NAME index="1">PRABHU, Mrs. SRIDEVI</NAME>

<CONTCTTYPE/>

<DESCRIPTN/>

<EMAIL>SPRABHU</EMAIL>

<FAX index="1"/>


<USERAREA/>

</CONTACT>

</PARTNER>

<PARTNER>




<PARTNRTYPE>BillTo</PARTNRTYPE>

<CURRENCY/>

<DESCRIPTN/>

<DUNSNUMBER/>


<PAYMETHOD/>

<TAXID/>

<TERMID/>

<USERAREA>

<ADDRESS>

<ADDRLINE index="1">475 Park Avneue</ADDRLINE>



<ADDRTYPE/>




<DESCRIPTN/>

<FAX index="1"/>




<TAXJRSDCTN/>




<URL/>

<USERAREA>

</ADDRESS>

</PARTNER>

<PARTNER>

<NAME index="1"/>

<ONETIME/>


<PARTNRTYPE>Carrier</PARTNRTYPE>

<PARTNRIDX/>

</PARTNER>

<POTERM>



<DAYSNUM/>


<VALUE/>

<NUMOFDEC/>

<SIGN/>

<CURRENCY/>

<UOMVALUE/>

<UOMNUMDEC/>

<UOM/>

</OPERAMT>

<USERAREA/>

</POTERM>

</POHEADER>

<POLINE>

<OPERAMT qualifier="UNIT" type="T">>



<SIGN>+</SIGN>

Sample XML A-57




<UOM>Ea</UOM>

</OPERAMT>


<VALUE>15</VALUE>

<NUMOFDEC/>

<SIGN>+</SIGN>

<UOM>Ea</UOM>

</QUANTITY>


<DESCRIPTN>Chemical</DESCRIPTN>

<HAZRDMAT/>

<ITEM>CLN-STD1</ITEM>

<ITEMRV/>

<ITEMRVX/>

<ITEMTYPE/>

<ITEMX/>

<POLNSTATUS>OPEN</POLNSTATUS>

<USERAREA>

<REQUESTOR/>

<CATEGORYID>MISC.MISC</CATEGORYID>

<CONTRACTNUM/>

<CONTRACTPONUM/>

<CONTRACTPOLINENUM/>

<VENDORQUOTENUM/>

<CONFIGID/>

<LISTPRICE>1107.86</LISTPRICE>

<MARKETPRICE>0</MARKETPRICE>

<PRICENOTTOEXCEED/>

<NEGPRICE>N</NEGPRICE>

<TAXABLE/>

<TXNREASONCODE/>

<TYPE1099/>

<LINEORDERTYPE>Goods</LINEORDERTYPE>

<HAZRDUNNUM/>

<HAZRDUNDESC/>

<DFFLINE>

Sample XML A-59

<ATTRIBUTE4/>

<ATTRIBUTE5/>

<ATTRIBUTE6/>

<ATTRIBUTE7/>

<ATTRIBUTE8/>

<ATTRIBUTE9/>

<ATTRIBUTE10>

<ATTRIBUTE11/>

<ATTRIBUTE12/>

<ATTRIBUTE13/>

<ATTRIBUTE14/>

<ATTRIBUTE15/>

<ATTRIBUTE16/>

<ATTRIBUTE17/>

<ATTRIBUTE18/>

<ATTRIBUTE19/>

<ATTRIBUTE20/>

</KFFITEM>

<GLOBALCONTRACT/>

<GLOBALCONTRACTLIN/>

<JOBTITLE/>

<AMOUNT qualifier="TOTAL" type="T">

<VALUE/>

<NUMOFDEC/>

<SIGN/>

<CURRENCY/>

<DRCR/>

</AMOUNT>

<CONTRACTORFIRSTNAME/>

<CONTRACTORLASTNAME/>


<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>


</DATETIME>


<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>

<DATETIME qualifier="NEEDDELV" type="T" index="1">

<YEAR>2006</YEAR>

<MONTH>10</MONTH>

<DAY>03</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>


<VALUE>15</VALUE>

<NUMOFDEC/>

<SIGN>+</SIGN>

<UOM>Ea</UOM>

</QUANTITY>


<USERAREA>

<DATETIME qualifier="PROMSHIP">

<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>

Sample XML A-61

<DATETIME qualifier="APPROVAL">

<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>




<SIGN>+</SIGN>




<UOM>Ea</UOM>

</OPERAMT>

<PRICEOVRRD/>

<TAXABLE>N</TAXABLE>

<TAXCODE/>

<PARTNER>






<DUNSNUMBER/>


<PAYMETHOD/>

<TAXID/>

<TERMID/>

<USERAREA>

<ADDRESS>

<ADDRLINE index="1">475 Park Avneue</ADDRLINE>



<ADDRTYPE/>





<DESCRIPTN/>

<FAX index="1"/>



<TAXJRSDCTN/>




<URL/>

<USERAREA/>

</ADDRESS>

<CONTACT>

<NAME index="1"/>

<CONTCTTYPE/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<PARTNER>

<NAME index="1"/>

<ONETIME/>

<PARTNRID/>

<PARTNRTYPE>DeliveryTo</PARTNRTYPE>

<PARTNRIDX/>

<USERAREA>

<ADDRESS>



<ADDRTYPE/>

</ADDRESS>

<CONTACT>

<NAME index="1"/>

<CONTCTTYPE/>

<EMAIL/>

<FAX index="1"/>

Sample XML A-63


</CONTACT>

</PARTNER>

<DROPSHIPDETAILS>

<DROPSHIPMENT/>

<DROPSHIPCUSTNAME/>

<SHIPINSTR/>

<PACKINSTR/>

<SHIPMETHOD/>

<CUSTOMERPONUM/>

<CUSTOMERLINENUM/>

<CUSTOMERSHIPNUM/>

<CUSTOMERDESC/>

</DROPSHIPDETAILS>

<CONSIGNEDINV>N</CONSIGNEDINV>

<DISTPROJECT>

<REQUESTOR/>

<EMAIL/>


<DISTNUM>1</DISTNUM>

<DISTPROJECT>

<PROJECTNUM/>

<PROJECTTYPE/>

<TASKNUM/>


<VALUE>15</VALUE>

<NUMOFDEC/>

<SIGN>+</SIGN>

<UOM>Ea</UOM>

</QUANTITY>

<CONVRATE/>


<YEAR>2006</YEAR>

<MONTH>10</MONTH>

<DAY>03</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>




</DATETIME>

<DESTTYPE>INVENTORY</DESTTYPE>

<DFFDISTRIBUTN>

<ATTRIBUTE1/>

<ATTRIBUTE2/>

<ATTRIBUTE3/>

<ATTRIBUTE4/>

<ATTRIBUTE5/>

<ATTRIBUTE6/>

<ATTRIBUTE7/>

<ATTRIBUTE8/>

<ATTRIBUTE9/>

<ATTRIBUTE10/>

<ATTRIBUTE11/>

<ATTRIBUTE12/>

<ATTRIBUTE13/>

<ATTRIBUTE14/>

<ATTRIBUTE15/>

<ATTRIBUTE16/>

</DFFDISTRIBUTN>

</DISTPROJECT>

<PSCLNSTATUS>OPEN</PSCLNSTATUS>


<VALUE>/>

<NUMOFDEC/>

<SIGN/>

<CURRENCY/>

<DRCR/>

</AMOUNT>

</USERAREA>

</SCHEDULE>

</POLINE>

</CHANGE_PO>

</DATAAREA>

</CHANGE_PO_006>

Sample XML A-65

CANCEL POThe following is a sample XML Document for the Cancel PO message:<CANCEL_PO_006>

<CNTROLAREA>

<BSR>

<VERB value="CANCEL">CANCEL</VERB>



</BSR>

<SENDER>

<LOGICALID/>


<TASK>CANCEL_PO</TASK>






</SENDER>


<YEAR>2002</YEAR>

<MONTH>12</MONTH>

<DAY>10</DAY>

<HOUR>17</HOUR>

<MINUTE>12</MINUTE>

<SECOND>32</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<CANCEL_PO>

<POHEADER>

<POID>27</POID>


</POHEADER>

<POLINE>



<SCHEDULE>


</SCHEDULE>

</POLINE>

</CANCEL_PO>

</DATAAREA>

</CANCEL_PO_006>

UPDATE DELIVERYThe following is a sample XML Document for the Update Delivery message:<UPDATE_DELIVERY_005>

<CNTROLAREA>

<BSR>

<VERB value="UPDATE"/>

<NOUN value="DELIVERY"/>


</BSR>

<SENDER>

<LOGICALID/>


<TASK>UPDATE_DELIVERY</TASK>






</SENDER>


<YEAR>2002</YEAR>

<MONTH>12</MONTH>

<DAY>13</DAY>

<HOUR>12</HOUR>

<MINUTE>34</MINUTE>

<SECOND>28</SECOND>



</DATETIME>

Sample XML A-67

</CNTROLAREA>

<DATAAREA>

<UPDATE_DELIVERY>

<RECEIPTHDR>

<DATETIME qualifier="DELIVACT">

<YEAR>2002</YEAR>

<MONTH>12</MONTH>

<DAY>13</DAY>

<HOUR>12</HOUR>

<MINUTE>30</MINUTE>

<SECOND>51</SECOND>



</DATETIME>

<DATETIME qualifier="SHIP">

<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>

<RECEIPTID>2096</RECEIPTID>


<BILLOLADNG/>

<EMPLOYEEID>Acme NY, Mr. Test</EMPLOYEEID>

<NOTES index="1"/>


<USERAREA>

<ORACLEITG.UPDATE_DELIVERY_005.RECEIPTHDR.USERAREA>

<ORACLEITG.RCPTSOURCE>VENDOR</ORACLEITG.RCPTSOURCE>

<ORACLEITG.SHIPMENTNO/>

<ORACLEITG.PACKINGSLIP/>

<ORACLEITG.UPS/>

<ORACLEITG.SUPPLIER>DISNEY</ORACLEITG.SUPPLIER>

<ORACLEITG.WAYBILL/>

















</ORACLEITG.UPDATE_DELIVERY_005.RECEIPTHDR.USERAREA>

</USERAREA>

</RECEIPTHDR>

<RECEIPTLN>

<QUANTITY qualifier="RECEIVED">

<VALUE>64</VALUE>


<SIGN>+</SIGN>

<UOM>ST</UOM>

</QUANTITY>

<AMOUNT qualifier="DOCUMENT" type="T">

<VALUE/>

<NUMOFDEC/>

<SIGN/>

<CURRENCY/>

<DRCR/>

</AMOUNT>

<DATETIME qualifier="DELIVACT">

<YEAR>2002</YEAR>

<MONTH>12</MONTH>

<DAY>13</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>


Sample XML A-69


</DATETIME>

<ITEM>KLMAT135</ITEM>

<RECLINENUM>1</RECLINENUM>

<DESCRIPTN>KLMAT 135</DESCRIPTN>

<ITEMRV/>

<ITEMX/>

<NOTES index="1"/>

<PACKING/>

<POID>139</POID>


<PORELEASE/>


<RECEPTDISP>DELIVER</RECEPTDISP>

<USERAREA>

<ORACLEITG.UPDATE_DELIVERY_005.RECEIPTLN.USERAREA>

<ORACLEITG.ORG>Acme NY Storage 1</ORACLEITG.ORG>

<ORACLEITG.SUBINV>Stores NY1</ORACLEITG.SUBINV>

<ORACLEITG.LOCATOR/>

<ORACLEITG.DELIVERTO/>

<ORACLEITG.DELVLOC>Acme US</ORACLEITG.DELVLOC>

<ORACLEITG.RCVTRANID>1684</ORACLEITG.RCVTRANID>

<ORACLEITG.DESTTYPE>INVENTORY</ORACLEITG.DESTTYPE>

<ORACLEITG.INSPSTS/>

<ORACLEITG.PACKINGSLIP/>

<ORACLEITG.RMA/>

<ORACLEITG.XREF>+YYYDELIVERINVENTORY</ORACLEITG.XREF>

<ORACLEITG.SHIPTOLOC>Acme US</ORACLEITG.SHIPTOLOC>

<ORACLEITG.REASONCODE/>

















</ORACLEITG.UPDATE_DELIVERY_005.RECEIPTLN.USERAREA>

</USERAREA>

</RECEIPTLN>

</UPDATE_DELIVERY>

</DATAAREA>

</UPDATE_DELIVERY_005>

SYNC SUPPLIERThe following is a sample SYNC SUPPLIER XML Document:<SYNC_SUPPLIER_005>

<CNTROLAREA>

<BSR>


<NOUN value="SUPPLIER">SUPPLIER</NOUN>


</BSR>

<SENDER>

<LOGICALID>XX1914409</LOGICALID>

<COMPONENT>SUP</COMPONENT>

<TASK>ADD</TASK>

<REFERENCEID>0000000000204213</REFERENCEID>


<LANGUAGE>JA</LANGUAGE>

<CODEPAGE>0</CODEPAGE>

<AUTHID>SHSUNDAR</AUTHID>

</SENDER>


<YEAR>2004</YEAR>

<MONTH>09</MONTH>

<DAY>20</DAY>

<HOUR>11</HOUR>

<MINUTE>34</MINUTE>

<SECOND>10</SECOND>

Sample XML A-71



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<SYNC_SUPPLIER>

<PARTNER>

<NAME index="1">saratr12001</NAME>


<PARTNRID></PARTNRID>


<ACTIVE>1</ACTIVE>


<DESCRIPTN>Some description</DESCRIPTN>

<DUNSNUMBER>989898</DUNSNUMBER>

<NAME index="1>sarat0001r12</NAME>

<NAME index="2">sarat0001r12</NAME>

<NAME index="3">sarat0001r12</NAME>

<PARENTID>1</PARENTID>

<PAYMETHOD>CHECK</PAYMETHOD>

<TAXID>789</TAXID>


<USERAREA>

<ORACLEITG.SYNC_SUPPLIER_005.PARTNER.USERAREA>

<ORACLEITG.USFLAG>Y</ORACLEITG.USFLAG>

<ORACLEITG.ORG>204</ORACLEITG.ORG>

</ORACLEITG.SYNC_SUPPLIER_005.PARTNER.USERAREA>

</USERAREA>

<ADDRESS>

<ADDRLINE index="1">los altos</ADDRLINE>

<ADDRLINE index="2">addressline2</ADDRLINE>



<ADDRTYPE>X</ADDRTYPE>

<CITY>los altos</CITY>


<COUNTY>Washington</COUNTY>

<DESCRIPTN>site0001</DESCRIPTN>

<FAX index="1">27801050</FAX>



<STATEPROVN>LA</STATEPROVN>

<TELEPHONE index="1">98499999</TELEPHONE>

<USERAREA>

<ORACLEITG.SYNC_SUPPLIER_005.PARTNER.ADDRESS.USERAREA>





<ORACLEITG.ORG>204</ORACLEITG.ORG>

</ORACLEITG.SYNC_SUPPLIER_005.PARTNER.ADDRESS.USERAREA>

</USERAREA>

</ADDRESS>

<CONTACT>

<NAME index="1">Name1</NAME>



<TELEPHONE index="3">999995</TELEPHONE >

<USERAREA>

<ORACLEITG.SYNC_SUPPLIER_005.PARTNER.CONTACT.USERAREA>

<ORACLEITG.SITECODE>los altos-ANP1</ORACLEITG.SITECODE>

</ORACLEITG.SYNC_SUPPLIER_005.PARTNER.CONTACT.USERAREA>

</USERAREA>

</CONTACT>

</PARTNER>

</SYNC_SUPPLIER>

</DATAAREA>

</SYNC_SUPPLIER_005>

SYNC ITEMThe following is a sample SYNC ITEM XML Document:<SYNC_ITEM_006>

<CNTROLAREA>

<BSR>


<NOUN value="ITEM">ITEM</NOUN>


</BSR>

Sample XML A-73

<SENDER>



<TASK>SYNC_ITEM</TASK>



<LANGUAGE>EN</LANGUAGE>



</SENDER>


<YEAR>2002</YEAR>

<MONTH>11</MONTH>

<DAY>25</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<SYNC_ITEM>

<ITEMHEADER>


<YEAR>2002</YEAR>

<MONTH>11</MONTH>

<DAY>20</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>

<ITEM>MURMAT31</ITEM>

<ITEMTYPE>104</ITEMTYPE>


<UOM>ST</UOM>



<COMMODITY index="2">Inventory</COMMODITY>

<ITEMDESC>Material to test PO Price Murthy teat</ITEMDESC>

<ITEMSTATUS>Active</ITEMSTATUS>

<USERAREA>

<ORACLEITG.SYNC_ITEM_006.ITEMHEADER.USERAREA>

<ORACLEITG.POENTITY>1392</ORACLEITG.POENTITY>

<ORACLEITG.RCTROUT>3</ORACLEITG.RCTROUT>

</ORACLEITG.SYNC_ITEM_006.ITEMHEADER.USERAREA>

</USERAREA>

<ITEMLOCATN>

<ITEM></ITEM>

<SITELEVEL index=""/>

</ITEMLOCATN>

</ITEMHEADER>

</SYNC_ITEM>

</DATAAREA>

</SYNC_ITEM_006>

SYNC UOMGROUPThe following is a sample SYNC UOMGROUP XML Document: <SYNC_UOMGROUP_003>

<CNTROLAREA>

<BSR>


<NOUN value="UOMGROUP">UOMGROUP</NOUN>


</BSR>

<SENDER>



<TASK>UOMCLASS</TASK>





<AUTHID>MURTHY</AUTHID>

</SENDER>


Sample XML A-75

<YEAR>2002</YEAR>

<MONTH>11</MONTH>

<DAY>11</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<SYNC_UOMGROUP>

<UOMGRPHDR>


<UOM>MDX</UOM>

<UOMGROUPID>DMX</UOMGROUPID>

<DESCRIPTN>Dimension X</DESCRIPTN>

<NOTES index="">MDX</NOTES>

<USERAREA>

<ORACLEITG.SYNC_UOMGROUP_003.UOMGRPHDR.USERAREA>

<ORACLEITG.BASEUOMFLAG>Y</ORACLEITG.BASEUOMFLAG>

<ORACLEITG.DEFCONFLAG>N</ORACLEITG.DEFCONFLAG>

</ORACLEITG.SYNC_UOMGROUP_003.UOMGRPHDR.USERAREA>

</USERAREA>

<UOMGRPDTL>

<QUANTITY qualifier="MULTIPLIER">

<VALUE>1</VALUE>


<SIGN>+</SIGN>

<UOM>dummy</UOM>

</QUANTITY>

<UOM></UOM>

</UOMGRPDTL>

</UOMGRPHDR>

</SYNC_UOMGROUP>

</DATAAREA>

</SYNC_UOMGROUP_003>


SYNC FIELD (PO Number)The following is a sample SYNC FIELD XML Document:<SYNC_FIELD_004>

<CNTROLAREA>

<BSR>


<NOUN value="FIELD">FIELD</NOUN>


</BSR>

<SENDER>



<TASK>PONUM</TASK>






</SENDER>


<YEAR>2002</YEAR>

<MONTH>11</MONTH>

<DAY>25</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<SYNC_FIELD>

<FIELD>

<FIELDID>REQUISTNID</FIELDID>

<FIELDVALUE>135</FIELDVALUE>


<USERAREA>

Sample XML A-77

<ORACLEITG.SYNC_FIELD_004.FIELD.USERAREA>

<ORACLEITG.REQLINENUM>1</ORACLEITG.REQLINENUM>

<ORACLEITG.POID>4500000032</ORACLEITG.POID>

<ORACLEITG.POENTITY>1653</ORACLEITG.POENTITY>

</ORACLEITG.SYNC_FIELD_004.FIELD.USERAREA>

</USERAREA>

</FIELD>

</SYNC_FIELD>

</DATAAREA>

</SYNC_FIELD_004>

SYNC PO (Inbound Invoice and Receipt Totals)The following is a sample SYNC PO XML Document:<SYNC_PO_007>

<CNTROLAREA>

<BSR>




</BSR>

<SENDER>



<TASK>SYNC_PO</TASK>






</SENDER>


<YEAR>2002</YEAR>

<MONTH>11</MONTH>

<DAY>20</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



<TIMEZONE>-0600</TIMEZONE>

</DATETIME>

</CNTROLAREA>

<DATAAREA>

<SYNC_PO>

<POHEADER>

<POID>65</POID>



<PORELEASE>0</PORELEASE>


<CHARGE/>

<PARTNER/>

</POHEADER>

<POLINE>


<ITEM>dummy</ITEM>

<CHARGE/>

<PARTNER/>

<POHISTORY>


<YEAR>2002</YEAR>

<MONTH>11</MONTH>

<DAY>20</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>




<SIGN>+</SIGN>

<UOM>Each</UOM>

</QUANTITY>

<AMOUNT qualifier="DOCUMENT" type="T">



Sample XML A-79

<SIGN>+</SIGN>

<CURRENCY></CURRENCY>

<DRCR></DRCR>

</AMOUNT>

<DOCTYPE>INVOICE</DOCTYPE>

<INSLINENUM>0</INSLINENUM>

<INVLINENUM>0</INVLINENUM>

<ORIGREF>0</ORIGREF>

<RECLINENUM>0</RECLINENUM>

</POHISTORY>

</POLINE>

</SYNC_PO>

</DATAAREA>

</SYNC_PO_007>

SYNC EXCHANGE RATEThe following is a sample SYNC EXCHANGE RATE XML Document:<SYNC_EXCHNGRATE_003>

<CNTROLAREA>

<BSR>


<NOUN value="EXCHNGRATE">EXCHNGRATE</NOUN>


</BSR>

<SENDER>

<LOGICALID>XX141HG09</LOGICALID>

<COMPONENT>FIN</COMPONENT>

<TASK>EXCHRATE</TASK>




<CODEPAGE>DEV</CODEPAGE>


</SENDER>


<YEAR>2002</YEAR>

<MONTH>11</MONTH>

<DAY>13</DAY>


<HOUR>12</HOUR>

<MINUTE>22</MINUTE>

<SECOND>00</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<SYNC_EXCHNGRATE>

<EXCHNGRATE>

<DATETIME qualifier="EFFECTIVE">

<YEAR>2002</YEAR>

<MONTH>11</MONTH>

<DAY>12</DAY>

<HOUR>12</HOUR>

<MINUTE>22</MINUTE>

<SECOND>00</SECOND>



</DATETIME>

<QUANTITY qualifier="RATE">



<SIGN>+</SIGN>

<UOM></UOM>

</QUANTITY>

<CURRFROM>LUF</CURRFROM>

<CURRTO>TRL</CURRTO>

<FACTOR> 0</FACTOR>


<RATETYPE>Corporate</RATETYPE>

</EXCHNGRATE>

</SYNC_EXCHNGRATE>

</DATAAREA>

</SYNC_EXCHNGRATE_003>

SYNC COAThe following is a sample SYNC COA XML Document:

Sample XML A-81

<SYNC_COA_003>

<CNTROLAREA>

<BSR>


<NOUN value="COA">COA</NOUN>


</BSR>

<SENDER>



<TASK>SYNC_COA</TASK>






</SENDER>


<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>28</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<SYNC_COA>

<COA>

<DATETIME qualifier="EFFECTIVE">

<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>28</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>




</DATETIME>


<YEAR>9999</YEAR>

<MONTH>12</MONTH>

<DAY>31</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>

<GLENTITYS></GLENTITYS>

<GLNOMACCT></GLNOMACCT>


<DESCRIPTN>MM CC</DESCRIPTN>

<USERAREA>

<ORACLEITG.SYNC_COA_003.COA.USERAREA>

<ORACLEITG.FIELDID>1009007</ORACLEITG.FIELDID>

<ORACLEITG.FIELDVALUE>789997</ORACLEITG.FIELDVALUE>

<ORACLEITG.ACTIVE>Y</ORACLEITG.ACTIVE>

</ORACLEITG.SYNC_COA_003.COA.USERAREA>

</USERAREA>

</COA>

</SYNC_COA>

</DATAAREA>

</SYNC_COA_003>

CONFIRM BODThe following is a sample CONFIRM BOD XML Document:<CONFIRM_BOD_004>

<CNTROLAREA>

<BSR>

<VERB>CONFIRM</VERB>

<NOUN>BOD</NOUN>

<REVISION/>

</BSR>

<SENDER>

Sample XML A-83

<LOGICALID/>

<COMPONENT>ECX</COMPONENT>

<TASK>CBODO</TASK>

<REFERENCEID>:oracle.apps.itg.xmlg.inbound:27553</REFERENCEID>





</SENDER>


<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>28</DAY>

<HOUR>17</HOUR>

<MINUTE>24</MINUTE>

<SECOND>22</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<CONFIRM_BOD>

<CONFIRM>

<CNTROLAREA>

<BSR>

<VERB>SYNC</VERB>

<NOUN>SUPPLIER</NOUN>

<REVISION>005</REVISION>

</BSR>

<SENDER>

<LOGICALID>XX1914409</LOGICALID>

<COMPONENT>SUP</COMPONENT>

<TASK>ADD</TASK>






</SENDER>



<YEAR>2003</YEAR>

<MONTH>01</MONTH>

<DAY>28</DAY>

<HOUR>11</HOUR>

<MINUTE>34</MINUTE>

<SECOND>10</SECOND>



</DATETIME>

</CNTROLAREA>

<STATUSLVL>00</STATUSLVL>

<DESCRIPTN>Document sucessfully processed.</DESCRIPTN>

<ORIGREF>0000000000207018</ORIGREF>

<USERAREA/>

<CONFIRMMSG>

<DESCRIPTN/>

<REASONCODE/>

<USERAREA/>

</CONFIRMMSG>

</CONFIRM>

</CONFIRM_BOD>

</DATAAREA>

</CONFIRM_BOD_004>

PROCESS POThe following is a sample PROCESS PO XML Document:<PROCESS_PO_007>

<CNTROLAREA>

<BSR>

<VERB value="PROCESS">PROCESS</VERB>



</BSR>

<SENDER>

<LOGICALID>ORACLE</LOGICALID>

<COMPONENT>PURCHASING</COMPONENT>

<TASK>POISSUE</TASK>

Sample XML A-85

<REFERENCEID>SCMX7RW3.US.ORACLE.COM:oracle.apps.po.event.xmlpo:76855-307915</REFERENCEID>



<CODEPAGE>UTF8</CODEPAGE>


</SENDER>

<DATETIME qualifier="CREATION" type="T" index="1">

<YEAR>2006</YEAR>

<MONTH>10</MONTH>

<DAY>03</DAY>

<HOUR>22</HOUR>

<MINUTE>39</MINUTE>

<SECOND>18</SECOND>



</DATETIME>

</CNTROLAREA>

<DATAAREA>

<PROCESS_PO>

<POORDERHDR>

<DATETIME qualifier="DOCUMENT" type="T" index="1">

<YEAR>2006</YEAR>

<MONTH>10</MONTH>

<DAY>03</DAY>

<HOUR>22</HOUR>

<MINUTE>36</MINUTE>

<SECOND>36</SECOND>



</DATETIME>




<SIGN>+</SIGN>




<UOM/>


</OPERAMT>

<POID>7954</POID>


<ACKREQUEST>N</ACKREQUEST>

<CONTRACTB/>

<CONTRACTS/>

<DESCRIPTN/>

<NOTES index="1"/>

><PORELEASE/>

<USERAREA>


<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>


<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>

<FOB>

<DESCRIPTN>Vendor's responsibility ceases upon transfer to carrier</DESCRIPTN>

<TERMID>Origin</TERMID>

</FOB>

<TANDC/>

<FTTERM>

<DESCRIPTN>Buyer pays freight</DESCRIPTN>

<TERMID>Due</TERMID>

Sample XML A-87

</FTTERM>

<EXCHRATE/>


<YEAR>2006</YEAR>

<MONTH>10</MONTH>

<DAY>03</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>

<SECOND>00</SECOND>



</DATETIME>

<DATETIME qualifier="APPREQ" type="T" index="1">

<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>

<CONFIRM>N</CONFIRM>

<SHIPPINGCONTROL>

<DFFPOHEADER>

<ATTRIBUTE1/>

<ATTRIBUTE2/>

<ATTRIBUTE3/>

<ATTRIBUTE4/>

<ATTRIBUTE5/>

<ATTRIBUTE6/>

<ATTRIBUTE7/>

<ATTRIBUTE8/>

<ATTRIBUTE9/>

<ATTRIBUTE10/>

<ATTRIBUTE11/>

<ATTRIBUTE12/>

<ATTRIBUTE13/>

<ATTRIBUTE14/>

Sample XML A-89

<ATTRIBUTE9/>

<ATTRIBUTE10/>

<ATTRIBUTE11/>

<ATTRIBUTE12/>

<ATTRIBUTE13/>

<ATTRIBUTE14/>

<ATTRIBUTE15/>

<ATTRIBUTE16/>

</DFFVENDOR>

<CUSTOMERNUM/>

</USERAREA>

<ADDRESS>

<ADDRLINE index="1">Test Site for SCTC transactions</ADDRLINE>

<ADDRLINE index="2">QA Zone</ADDRLINE>

<ADDRLINE index="3">Certification Quadrant</ADDRLINE>

<ADDRTYPE/>

<CITY>Sanfrancisco</CITY>


<COUNTY/>

<DESCRIPTN>SUPPLIER SITE</DESCRIPTN>

<FAX index="1"/>

<POSTALCODE/>

<REGION/>


<TAXJRSDCTN/>

<TELEPHONE index="1"></TELEPHONE>



<URL/>

<USERAREA>

<DFFVENDORSITE>

<ATTRIBUTE1/>

<ATTRIBUTE2/>

<ATTRIBUTE3/>

<ATTRIBUTE4/>

<ATTRIBUTE5/>

<ATTRIBUTE6/>

<ATTRIBUTE7/>

<ATTRIBUTE8/>

Sample XML A-91

<FAX index="1"/>


<REGION/>


<TAXJRSDCTN/>




<URL/>

<USERAREA/>

</ADDRESS>

<CONTACT>

<NAME index="1">PRABHU, Mrs. SRIDEVI</NAME>

<CONTCTTYPE/>

<DESCRIPTN/>

<EMAIL>SPRABHU</EMAIL>

<FAX index="1"/>


<USERAREA/>

</CONTACT>

</PARTNER>

<PARTNER>




<PARTNRTYPE>BillTo</PARTNRTYPE>

<CURRENCY/>

<DUNSNUMBER/>


<PAYMETHOD/>

<TERMID/>

<USERAREA/>

<ADDRESS>

<ADDRLINE index="1">475 Park Avenue</ADDRLINE>



<ADDRTYPE/>





<DESCRIPTN/>

<FAX index="1"/>


<REGION/>


<TAXJRSDCTN/>




<URL/>

<USERAREA/>

</ADDRESS>

</PARTNER>

<PARTNER>

<NAME index="1"/>

<ONETIME/>


<PARTNRTYPE>Carrier</PARTNRTYPE>

<PARTNRIDX/>

</PARTNER>

<POTERM>



<DAYSNUM/>

<QUANTITY qualifier="PERCENT">

<VALUE/>

<NUMOFDEC/>

<SIGN/>

<UOM/>

</QUANTITY>

<USERAREA/>

</POTERM>

</POORDERHDR>

<POORDERLIN>


<VALUE>10</VALUE>

Sample XML A-93

<NUMOFDEC/>

<SIGN>+</SIGN>

<UOM>Ea</UOM>

</QUANTITY>




<SIGN>+</SIGN>




<UOM>Ea</UOM>

</OPERAMT>


<HAZRDMATL/>

<ITEMRV/>

<ITEMRVX/>

<POLNSTATUS/>

<DESCRIPTN>Chemical</DESCRIPTN>

<ITEM>CLN-STD1</ITEM>

<ITEMX/>

<USERAREA>

<REQUESTOR/>

<CATEGORYID>MISC.MISC</CATEGORYID>

<CONTRACTNUM/>

<CONTRACTPONUM/>

<CONTRACTPOLINENUM/>

<VENDORQUOTENUM/>

<CONFIGID/>

<LISTPRICE>1107.86</LISTPRICE>

<MARKETPRICE>0</MARKETPRICE>

<PRICENOTTOEXCEED/>

<NEGPRICE>N</NEGPRICE>

<TAXABLE/>

<TXNREASONCODE/>

<TYPE1099/>

<LINEORDERTYPE>Goods</LINEORDERTYPE>

<HAZRDUNNUM/>

<HAZRDUNDESC/>

Sample XML A-95

<ATTRIBUTE3/>

<ATTRIBUTE4/>

<ATTRIBUTE5/>

<ATTRIBUTE6/>

<ATTRIBUTE7/>

<ATTRIBUTE8/>

<ATTRIBUTE9/>

<ATTRIBUTE10/>

<ATTRIBUTE11/>

<ATTRIBUTE12/>

<ATTRIBUTE13/>

<ATTRIBUTE14/>

<ATTRIBUTE15/>

<ATTRIBUTE16/>

<ATTRIBUTE17/>

<ATTRIBUTE18/>

<ATTRIBUTE19/>

<ATTRIBUTE20/>

</KFFITEM>

<GLOBALCONTRACT/>

<GLOBALCONTRACTLIN/>

<JOBTITLE/>


<VALUE/>

<NUMOFDEC/>

<SIGN/>

<CURRENCY/>

<DRCR>C</DRCR>

</AMOUNT>

<DRCR>C</DRCR>

<CONTRACTORFIRSTNAME/>

<CONTRACTORLASTNAME/>


<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

Sample XML A-97

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>

<DATETIME qualifier="APPROVAL">

<YEAR/>

<MONTH/>

<DAY/>

<HOUR/>

<MINUTE/>

<SECOND/>

<SUBSECOND/>

<TIMEZONE/>

</DATETIME>




<SIGN>+</SIGN>




<UOM>Ea</UOM>

</OPERAMT>

<PRICEOVRRD/>

<TAXABLE>N</TAXABLE>

<TAXCODE/>

<PARTNER>






<DUNSNUMBER/>


<PAYMETHOD/>

<TERMID/>

<USERAREA/>

<ADDRESS>

<ADDRLINE index="1">475 Park Avenue</ADDRLINE>




<ADDRTYPE/>




<DESCRIPTN/>

<FAX index="1"/>


<REGION/>


<TAXJRSDCTN/>




<URL/>

<USERAREA/>

</ADDRESS>

<CONTACT>

<NAME index="1"/>

<CONTCTTYPE/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<PARTNER>

<NAME index="1"/>

<ONETIME/>

<PARTNRID/>

<PARTNRTYPE>DeliveryTo</PARTNRTYPE>

<PARTNRIDX/>

<USERAREA/>

<ADDRESS>



<ADDRTYPE/>

</ADDRESS>

<CONTACT>

<NAME index="1"/>

Sample XML A-99

<CONTCTTYPE/>

<EMAIL/>

<FAX index="1"/>


</CONTACT>

</PARTNER>

<DROPSHIPDETAILS>

<DROPSHIPMENT/>

<DROPSHIPCUSTNAME/>

<SHIPINSTR>

<PACKINSTR/>

<SHIPMETHOD/>

<CUSTOMERPONUM/>

<CUSTOMERLINENUM/>

<CUSTOMERSHIPNUM/>

<CUSTOMERDESC/>

</DROPSHIPDETAILS>

<CONSIGNEDINV>N</CONSIGNEDINV>

<DISTPROJECT>

<REQUESTOR/>

<EMAIL/>


<DISTNUM>1</DISTNUM>

<PROJECTNUM/>

<PROJECTTYPE/>

<TASKNUM/>


<VALUE>10</VALUE>

<NUMOFDEC/>

<SIGN>+</SIGN>

<UOM>Ea</UOM>

</QUANTITY>

<CONVRATE/>


<YEAR>2006</YEAR>

<MONTH>10</MONTH>

<DAY>03</DAY>

<HOUR>00</HOUR>

<MINUTE>00</MINUTE>


<SECOND>00</SECOND>



</DATETIME>

<DESTTYPE>INVENTORY</DESTTYPE>

<DFFDISTRIBUTN>

<ATTRIBUTE1/>

<ATTRIBUTE2/>

<ATTRIBUTE3/>

<ATTRIBUTE4/>

<ATTRIBUTE5/>

<ATTRIBUTE6/>

<ATTRIBUTE7/>

<ATTRIBUTE8/>

<ATTRIBUTE9/>

<ATTRIBUTE10/>

<ATTRIBUTE11/>

<ATTRIBUTE12/>

<ATTRIBUTE13/>

<ATTRIBUTE14/>

<ATTRIBUTE15/>

<ATTRIBUTE16/>

</DFFDISTRIBUTN>

<DISTPROJECT>


<VALUE/>

<NUMOFDEC/>

<SIGN/>

<CURRENCY/>

<DRCR>C</DRCR>

</AMOUNT>

</USERAREA>

</POLINESCHD>

</POORDERLIN>

</PROCESS_PO>

</DATAAREA>

</PROCESS_PO_007>

Troubleshooting B-1

BTroubleshooting

Troubleshooting Common Errors

The OAGIS BOD is not being generated or consumed for a supported transaction in the E-Business Suite?Refer to the Oracle iProcurement Connector Setup instructions and ensure that all the setup steps are performed as described.

1. Check for transaction of interest in the setup for Internal Partner - OIPC Default TPin the XML Gateway Trading Partner Setup.

2. Enable Effectivities for the transaction.

3. Check the following system components and services are up and running.

• ECX Inbound Agent Listener

• ECX Transaction Agent Listener

• Workflow Deferred Notification Agent Listener

To verify the status of the service components mentioned above.

4. Navigate to System Administration > Oracle Applications Manager> Workflow Manager >Agent Listeners.

5. Ensure the status icon for each service is Green.

Note: Else, please contact your System Administrator to restart the services and resolve any issues in the underlying Workflow Container or FND's Generic Service Manager.

To check the Event Queue Summary (Outbound Transaction) window:

B-2 Oracle iProcurement Connector Implementation Guide

6. Navigate to Oracle Applications Manager >Workflow Manager > Agent Activity.

Search for the document in appropriate queue.

Note: The absence of the document in WF_IN, WF_OU, or ECX_Outbound Queue indicates that the transaction did not triggera business event. Open the Effectivities Manager window of the iProcurement Connector responsibility and check if the transaction is selected.

7. Restart the AQ agent if the document is in the ECX_Outbound Queue.

8. Check the propagation setting for WF_OUT and set it to run every 60 seconds in theCheck Event Manager Set Up Window.

9. Navigate to Administrator Workflow > Status Monitor.

10. Query for workflow internal type name -ITGSTD% to check the status.

11. Navigate to Collaboration Monitor >Collaboration History.

12. Query for collaborations of application - iProcurement Connector to check the status.

13. Check for any error information displayed in the Collaboration History records for the transaction.

To fix the workflow errors occurred during the Generate Trading Partner XML activity.

14. Enable statement level logging for XML Gateway and capture the log information to diagnose the problem.

The following steps can be used to generate an XML Gateway log:

• Navigate to System Administration>Oracle Applications Manager> Logs>Log Setup>Application.

• Choose XML Gateway as application name.

• Set Log Enabled to Yes.

• Set Log Level to Statement.

• Set Module to ECX%

• Run ECXLGINI.sql($ECX_TOP/patch/115/sql) and ECXTEST.sql($ECX_TOP/patch/115/sql)

Troubleshooting B-3

• The Log File name displays.

Note: You can generate the log file as physical file system running ECXLGUTIL.sql($ECX_TOP/patch/115/sql), which requires the log file name as module name (as input) for any error information.

15. To generate a statement level log for Oracle iProcurement Connector:

• Set the value of Profile - FND: Debug Log Level to statement.

• Set the value of Profile - FND: Debug Log Module to %itg%.

• Check for statement level and error log messages generated present in the log files starting with name itg* in the directory pointed by utl_file_dir for any error information.

16. To generate a statement level log for Oracle Supply Chain Trading Connector.

• Set the value for Profile - CLN: Debug Log Level to statement.

• Set value for Profile -CLN: Debug log directory to utl_file_dir.

• Rexecute the transactions and check for the cln*, itg* log files in this directory for any error information.

I disabled a business object using the Effectivities Manager, yet the OAGIS BOD is still being either sent or consumed.1. Navigate to Profile System Window > System Administrator responsibility.

2. Search for Profile -ITG% . The ITG: Enable Effectivities Manager Profile displays.

3. Set the value to Yes.

4. Click Save.

Glossary-1

Glossary

Advanced Queuing (AQ)

Advanced Queuing is the unique database integrated message queuing feature of the Oracle database. This functionality enables you to perform message queuing operations,similar to SQL operations from the Oracle database. Message queuing functionality enables applications on Oracle database to communicate asynchronously through messages in AQ lists. You can also perform AQ operations over the Internet through HTTP and E-mail.

Applications Program Interface (API)

Application Program Interface is a set of routines, protocols, and tools for building software applications.

Business Action Message

Business actions are the messages that contain information related to the business such as a purchase order.

Business Object Document (BOD)

Business Object Document is the model used to communicate a request from one sourceapplication to a destination application. It is also referred to as Open Applications Group Integration Specification (OAGIS).

Bill Of Materials (BOM)

Bill of Materials software is typically used by manufacturing firms. BOM is a recipe of sorts that details the ingredients needed to manufacture a particular item.

Business Service Request (BSR)

Business Service Request is an electronic request made for requisitions from an application.

Business Signal Message

Business signals are positive and negative acknowledgement (exception) messages that are sent in response to business actions.

Glossary-2

Chart Of Accounts (COA)

Chart Of Accounts is a list of all account names and numbers used in a company's general ledger.

Open Applications Group (OAG)

Open Applications Group is a non-profit consortium focusing on best practices and process based XML content for E-Business and application integration. It is the largest publisher of XML based content for business software interoperability in the world.

Open Applications Group Integration Specification (OAGIS)

Open Applications Group Integration Specification is an effort to provide a canonical business language for information integration. It uses XML as the common alphabet for defining business messages and for identifying business processes that let businesses and business applications to communicate.

Purchase Order

A purchase order is a document authorizing the purchase of goods or services from a specific vendor. The purchase order includes the terms of the purchase, delivery requirements, identification of goods or services ordered, as well as their quantities and prices.

Trading Partner

Any party transacting business with another on the basis of agreed set rules and commitments. Both the parties sign an agreement of approval for the proposed businessand agree upon certain procedures, to handle the intricacies involved.

XML Gateway (XMLG)

XML Gateway is used as a standard product to provide a single integration toolkit for the Oracle applications to create or consume XML transactions. The workflow process raises a business event to trigger the XML Gateway for the creation of the XML transactions. It integrates with the transport layer for the delivery or receipt of the messages. The Version 2 of XML Gateway (ECX2) will be used for the creation or use of the XML transactions.

Action

User defined message displayed to identify the need for and type of quality related action to be taken when a lot expires, or its results are not in conformance with quality requirements. Examples of actions are: quarantine, retest, resample, and hold.

Business Event

An event that is of interest to customers or business teams. For example, the movement of inventory to a subinventory is a business event.

Glossary-3

E-Records and e-signatures

To satisfy signoff requirements in regulated industries, electronic signatures are obtained before changes to records become accessible throughout the supply chain. Management configures where and when these signatures are collected by using an electronic record framework. If a signature is required, then an e-signature window displays. Application users are restricted from moving on to the next logical step or status until all required e-signatures are entered.

Event Subscription

Typically perform any or all of the following:

• Run custom PL/SQL code.

• Send the business event to a predefined workflow.

• Use Oracle Advanced Queuing for asynchronous messaging.

Refer to the Oracle Workflow Guide for details on subscribing to a workflow event.

Frequency Period

Defines the basis of frequency for a sampling plan in terms of hours, batches, lots, and kilograms produced. This corresponds to the frequency count.

Frequency Type

Identifies the type of sampling plan frequency as:

• Time-based

• Quantity-based

• Fixed Number

• Percent

Instrument

A resource that is linked to a test method so that test results can be traced to the equipment used in the analysis.

Oracle Workflow

A complete workflow management system that supports business process definition, automation, and integration. This technology routes information based on user defined business rules. Notification activities deliver messages to you through e-mail or a notification web page that is accessible using any browser.

Glossary-4

Storage Organization

Process-enabled inventory organization where a sample is stored.

Subinventory

A subdivision of an inventory organization that represents either a physical area or a logical grouping of items, such as a storeroom, damaged inventory, or receiving dock.

Test Replicate

An iteration of a test that is repeated on the same sample.

Test Units

Previously Assay Units. Unit of measure for quality tests. For example, pH. Test units ofmeasure often differ from inventory units of measure.

Testing Frequency

In stability studies. Frequency of testing sufficient to establish the stability characteristics of the item. Testing under long term conditions typically is every three months, over the first year, every six months over the second year and then annually.

Variant

In stability studies. The storage condition for a time point sample defined by a unique combination of the material source, stability study storage condition, test interval plan, and optional storage package.

WIP

See Work In Progress.

Work In Process

Also, WIP. Batches released to production.

Index-1

Index

AAbout This Guide, 1-1Add Requisition, A-1Add REQUISITN BOD, 3-7Advance Queue (AQ), 1-6Application to Application (A2A) Integration, 1-7

BBusiness Models, 1-7Business Model Summary, 1-9Business Object Document

Chart of Accounts, 3-14Unit of Measure, 3-11

Business To Business (B2B) Integration, 1-8

CCancel PO, A-65Cancel Purchase Order, 3-8

Cancel PO BOD, 3-9Cancel Requisition, 3-9, A-22

Cancel REQUISITN BOD, 3-9Change OIPC Message Confirmation, 2-3Change PO, A-48Change PO BOD, 3-3Change Purchase Order, 3-3Change Requisition, A-13Chart of Accounts (COA), 3-14

SYNC COA BOD, 3-14Collaboration History, 1-5Common Errors, B-1Confirm BOD, A-82

DDetermine required messages, 2-2

EEnable Messages, 2-2Exchange Rates, 3-14

SYNC EXCHNGRATE BOD, 3-14

FFeatures, 1-2Functioning of the Oracle iProcurement Connector , 1-2

GGlossary, Glossary-1

IImplementation Steps, 2-1Inbound, 1-6Install Oracle iProcurement Connector, 2-2iProcurement Connector Components, 1-4iProcurement Connector Flow, 1-6Item, 3-13

SYNC ITEM BOD, 3-13

MMessage Validation, 1-5

O

Index-2

OAGIS, 1-3OIP to Third Party Application, 1-9Oracle iProcurement Connector, 1-2Outbound, 1-6

PProcess PO, A-84Process PO BOD, 3-5Process Purchase Order, 3-5Purchase and Change Order, 1-8Purchase order, 3-1Purchase Order and Receipt, 1-8Purchase Order Number, 3-17

SYNC FIELD BOD, 3-17Purchase Order Status, 3-15

RReceipts, 3-10

Update Delivery BOD, 3-10Repository Based Manager Designer, 1-5Requisitioning, 1-7Requisitions, 3-7

SSetting Up, 2-viiiSet up Oracle Applications, 2-2Supplier, 3-11

SYNC SUPPLIER BOD, 3-11Sync COA, A-80Sync Exchange Rate, A-79Sync Inbound Invoice

Receipt Totals, A-77Sync Item, A-72Sync OIP with Third party system, 2-4Sync PO, A-23SYNC PO BOD, 3-2Sync PO Number, A-76Sync PO Release, A-36Sync Supplier, A-70Sync UOM, A-74

TThird Party to Oracle iProcurement, 1-9Transaction Flow from EBS, 3-1Transaction Flows

Cancel Purchase Order, 3-7

UUnderstanding Oracle iProcurement Connector, 1-viiiUnits Of Measure, 3-12

SYNC UOMGROUP BOD, 3-12Update Delivery, A-66Using Oracle iProcurement Connector, 2-5

WWorkflow Business Event System, 1-4

XXML Gateway, 1-4