Delivered with XML Gateway are two standard item types:

• XML Gateway Standard Item Type

• XML Gateway Error Processing Item Type

An Item Type is a group of components of a particular category that share the same set of item attributes (also known as variables).

Both the XML Gateway Standard Item Type and XML Gateway Error Processing Item Type can be accessed using the Oracle Workflow Builder.

Common to all item types are the following components:

• Attributes

• Process Activity

• Notification Activity

• Function Activity

• Event Activity

• Messages

• Lookup Types

A Workflow process may be made up of event activities, function activities, notification activities, or process activities. A message is the information sent in a notification activity. Lookup types represent a list of valid values. Attributes represent variables used to share data between activities in the Workflow process.

See the Oracle Workflow User's Guide for more information.

The XML Gateway Standard Item Type is a toolkit consisting of attributes, processes, functions, and event activities. Configure the seeded events and event subscriptions delivered by the Oracle E-Business Suite for prebuilt XML messages in support of B2B integration requirements.

In addition, the function activities can be used to define Workflow processes in support of A2A integration requirements.

See XML Gateway Standard Item Type for details regarding the function and event activities.

The XML Gateway Error Processing Item Type contains error handling processes to manage errors detected by Oracle Workflow Business Event System or Oracle XML Gateway.

Oracle Workflow sends a notification to the Trading Partner contact for data errors or to the XML Gateway system administrator for system or process errors. For errors that require collaboration between the Trading Partner contact and the XML Gateway system administrator, a notification is sent to both parties to encourage discussion and to expedite problem solution.

In addition, Oracle Workflow sends a notification to an appropriate transaction owner depending on the transaction type of an erred inbound transaction. If a transaction owner for a particular transaction type is identified, and the transaction error belongs to the transaction type with the owner defined, then the transaction owner will receive a notification in addition to the XML Gateway system administrator and Trading Partner contact depending on the error type. For example, if an inbound transaction error belongs to the Purchasing transaction type, then the Purchasing transaction owner also receives the notification if his or her user name is defined in the Define Transactions form.

A transaction owner can act on an error notification if needed. Once the notification has been responded on either reprocess or abort, any other subsequent response from the system administrator will be ignored and the notification should be closed.

For more information on the error handling process, see XML Gateway Error Processing Item Type.

The seeded event subscription delivered for Oracle prebuilt messages is delivered in an Oracle E-Business Suite application module-specific item type. The seeded event subscription may be configured using the function activities defined in the XML Gateway Standard Item Type or customized to support the application-specific requirement.

See Configure Oracle Prebuilt Inbound Messages or Configure Oracle Prebuilt Outbound Messages for details on how to configure a seeded event subscription.