Oracle Trading Community Architecture (TCA) provides business events to signal the creation or update of information in the TCA Registry. You can attach your own callout subscriptions to the events to perform additional business logic without modifying TCA.

This infrastructure is based on the Oracle Workflow Business Event System. Several Oracle E-Business Suite products provide additional functionality using the same callout infrastructure.

Business Event Types

Oracle Trading Community Architecture provides two types of business events.

• Granular Events: These events are raised at physical table or entity level, which is the lowest, most granular level. All TCA granular (V2, or Version 2) API calls raise one such event.

  For example, when an organization record is created, the oracle.apps.ar.hz.Organization.create event is raised. Later, if that organization name is modified, a relationship for the organization is created, and two contact points are added, then four separate events are raised:

  • One oracle.apps.ar.hz.Organization.update event

  • One oracle.apps.ar.hz.Relationship.create event

  • Two oracle.apps.ar.hz.ContactPoint.create events

  See: Trading Community Architecture Business Object Events, Oracle Trading Community Architecture Technical Implementation Guide.

• Business Object Events: These events are raised at the business object level. A business object is a hierarchical collection of physical entities pertaining to a logical business-oriented object. For example, an Organization business object includes the organization's profile information, addresses, contacts, contact points, relationships, and so on.

  Business object events include:

  • Persons Created - oracle.apps.ar.hz.personBO.create

  • Persons Updated - oracle.apps.ar.hz.personBO.update

  • Person Customers Created - oracle.apps.ar.hz.CustBO.create

  • Person Customers Updated - oracle.apps.ar.hz.CustBO.update

  • Organizations Created - oracle.apps.ar.hz.orgBO.create

  • Organizations Updated - oracle.apps.ar.hz.orgBO.update

  • Organizations Customers Created - oracle.apps.ar.hz.orgCustBO.create

  • Organizations Customers Updated - oracle.apps.ar.hz.orgCustBO.update

  Creating any entity within a business object is considered as one update to the business object. Like the example for granular events, when the organization is first created, the oracle.apps.ar.hz.orgBO.create event is raised. However, for the update and additional creation of relationship and contact points, only one business object event is raised: oracle.apps.ar.hz.orgBO.update.

  See: Trading Community Architecture Business Object Events, Oracle Trading Community Architecture Technical Implementation Guide.

Business Event Setup Process

Business event setup involves:

• Setting profile options for the business objects events infrastructure. When setting the profile options, consider the requirements of your installation and the ways in which other Oracle E-Business Suite applications use TCA events.

  Profile option for granular events and business object events:

  • HZ: Raise API Events. See: Defining the Business Event Types to Raise.

  Profile options for business object events only:

  • HZ: Format Business Object Business Events as Bulk. See: Defining How Business Events Are Raised.

  • HZ: Number of Days to Preserve Business Object Business Event Information. See: Preserving Event Information.

• Executing specific Oracle E-Business Suite functions that use TCA granular (V2) business events, even when those events are disabled. See: Schedule Event Raising and Impact and Alternatives of Not Raising Granular Business Events.

• Subscribing to business object events. This is done for both granular events and business object events. See: Event Subscription.

• For business object events, schedule concurrent programs. See: Events Raising.