This chapter covers the following topics:
These callouts, to the Oracle Workflow Business Event System, enable you to customize data usage in the TCA registry and the customer account layer without modifying the core TCA product.
Third party applications can subscribe to TCA events.
Easy to administer and maintain third party processes.
Includes published events.
The TCA callout structure is based on the Business Event System (BES) using Oracle Workflow.
The following procedure describes how to setup event subscription.
Log on to Oracle Applications using the Workflow Administrator Web Application responsibility.
Navigate to Business Events and search for a business event.
Click Create Subscription.
Enter the action and other parameters for the subscription.
For granular events, TCA uses the same naming convention:
oracle.apps.ar.hz.<Entity name>.<action>
For business object events, TCA uses the following naming convention:
oracle.apps.ar.hz.<Entity name>BO.<action>
For example, if you subscribe your business process to the Customer Account creation event, then you must subscribe your routine to the oracle.apps.ar.hz.CustAccount.create event. Or, if you subscribe your business process to the modification of an organization, then you must subscribe your routine to the oracle.apps.ar.hz.Organization.update event.
For more information on subscribing to events, see: Defining Event Subscriptions, Oracle Workflow Developer's Guide.
You should run subscriptions in deferred mode using the Oracle Workflow Business Event System, so that no overhead is added to the process that raised the event. The phase number of a user defined subscription should be greater than 99.
When the TCA callout structure raises an event, the event message, corresponding to that instance of event, is sent to the deferred queue. Subscriptions are executed when the event message is consumed. That is when the Workflow Agent Listener with the WF_DEFERRED parameter runs. When this concurrent program runs, every subscription from every instance of events currently in the DEFERRED queue runs. The request group of the System Administrator responsibility includes this concurrent program.
For more information, see: Deferring Subscription Processing Using Subscription Phase Numbers, and Managing Business Events in Oracle Workflow Developer's Guide.
Related Topics
Setting Up Business Events, Oracle Trading Community Architecture Administration Guide
Business Object API Attributes Information Overview
This table provides the following information about the TCA events:
Name of the event
Description of the physical entity
ID parameter name
| Name | Description of the Physical Entity | ID Parameter Name |
|---|---|---|
Person:
|
Party is a generic concept about an entity that can establish relationships with another entity. For example, a party can be an Organization like Oracle, a Person like Jane Doe, a Group like World Wide Web Consortium, or a Relationship like Jane Doe at Oracle. Based on this concept, a person is a party of the Person type. The HZ_PERSON_PROFILES table stores personal and family information about a party of the Person type. For example, this table could contain the correct spelling and phonetic pronunciation of the person's name. HZ_PARTIES table contains denormalized information from the HZ_PERSON_PROFILES, HZ_ORGANIZATION_PROFILES, HZ_LOCATIONS, HZ_CONTACT_POINTS and HZ_PERSON_LANGUAGE tables. |
PARTY_ID |
Organization:
|
An organization is a party of the Organization type. HZ_ORGANIZATION_PROFILES table stores a variety of information about a party. This table gets populated during the creation of a party of the Organization type. This table can also store historical data for the organization. Each time an organization's information is updated, the effective end date column for the original record is updated and a new record that contains the updated information is created. |
PARTY_ID |
Group:
|
A group is a party of the Group type. There is no specific table for groups. The parties are stored in the HZ_PARTIES table. | PARTY_ID |
Location:
|
HZ_LOCATIONS table stores information about a delivery or postal address such as building number, street address, postal code, and directions to location. This table provides physical location information about parties (organizations and persons) and customer accounts. | LOCATION_ID |
Party Site:
|
A party can have one or more locations and a location can be used by one or more parties. The Party Site relational entity represents the association of a party and its locations. The HZ_PARTY_SITES table links a party (HZ_PARTIES) and a location (HZ_LOCATIONS), and stores location-specific party information such as MAILSTOP and ADDRESSEE. For example, 500 Oracle Parkway can be specified as a party site for Oracle. This party site can n be used for multiple customer accounts with the same party. |
PARTY_SITE_ID |
Party Site Use:
|
A relation between a party and a location can have several uses such as delivery or billing. The HZ_PARTY_SITE_USES table stores information about how a party site is used. Party sites can have multiple uses, for example; Ship-To and Bill-To. | PARTY_SITE_USE_ID |
Relationship:
|
The HZ_RELATIONSHIPS table stores information about relationships between one party and another party. The table specifies the subject and object, as well as the relationship that exists between the two parties. For example, if the party relationship is a Parent Of relationship, a holding company could be the subject in the relationship while one of its subsidiaries could be the object. |
RELATIONSHIP_ID |
Organization Contact:
|
A contact is a contact person for a party. HZ_ORG_CONTACTS table stores information about the position of the contact for a party or party site. The records in this table provide information about a contact's position such as JOB_TITLE, RANK and general contact information. This table is not used to store information about a specific person or organization. For example, the table may include a record for the position of vice president of manufacturing that indicates that the contact is a senior executive, but it would not include the name of the person in that position. |
ORG_CONTACT_ID |
Organization Contact Role:
|
Contacts could have multiple roles. The HZ_ORG_CONTACT_ROLES table stores information about the role of the contact position that is specified in HZ_ORG_CONTACTS table. For example, a vice president of manufacturing may have a custom-defined role as a member of a capital expenditures review board. |
ORG_CONTACT_ROLE_ID |
Customer Account:
|
A customer account is a customer relationship established with a party. The HZ_CUST_ACCOUNTS table stores information about customer relationships established with a party. Because a party can have multiple customer accounts, this table could contain several records for a same party. For example, an individual person may establish a personal account, a family account, and a professional account for a consulting practice. Note the focus of this table is a business relationship and how the transactions are conducted in the relationship. |
CUST_ACCOUNT_ID PARTY_ID CUST_ACCOUNT_PROFILE_ID P_CREATE_PROFILE_AMT |
Customer Account Role:
|
A party can play a role in a customer account. HZ_CUST_ACCOUNT_ROLES table stores information about the role or function that a party performs in relation to a customer account. For example, Jane Doe might be a legal contact for Vision Corporation. |
CUST_ACCT_ROLE_ID |
Role Responsibility:
|
A party can play a role in a customer account. A role in a customer account can have several responsibilities. HZ_ROLE_RESPONSIBILITY table stores information about the required or expected activities of a party based on the party's role or function in relation to an account. Note that the role referred to in this table may not be the same as the role of a contact in an organization. For example, in this table you may store "Accepts quality of received materials" as a responsibility of the Incoming Material Quality Control role specified in the HZ_CUST_ACCOUNT_ROLES table. The party with the role responsibility may not be an individual person. |
RESPONSIBILITY_ID |
Customer Account Relationship:
|
Customer Accounts can have relationships between m. HZ_CUST_ACCT_RELATE_ALL table stores information about relationships between customer accounts. A flag lets you indicate whether a relationship is reciprocal. |
CUST_ACCOUNT_ID RELATED_CUST_ACCOUNT_ID |
Customer Account Site:
|
A customer account can have several customer account sites. Each customer account site is located in one location. HZ_CUST_ACCT_SITE_ALL table stores information about customer sites, or locations, for customer accounts. One customer account can have multiple sites. Address information for a site is stored in HZ_LOCATIONS table. |
CUST_ACCT_SITE_ID |
Customer Account Site Use:
|
A customer site in one location can have several business purposes. HZ_CUST_SITE_USES_ALL table stores information about the business purposes assigned to a customer account site. A customer account site can have multiple purposes for a customer account site; however each record in this table only specifies one purpose for a customer account site. For example, a customer account site may be assigned as the Ship-To site in one record and as the Bill-To site in another. Note that address information is stored in the HZ_LOCATIONS table. |
SITE_USE_ID CUST_ACCOUNT_PROFILE_ID P_CREATE_PROFILE P_CREATE_PROFILE_AMT |
Customer Profile Amount:
|
A customer account has an updateable, defaulted credit limit, which is part of the customer's profile information. HZ_CUST_PROFILE_AMTS table stores information about the credit limits specified for a customer profile class for a single currency. The credit limits of the profile class can be assigned to specific customer accounts or customer account sites. Many of the values in this table may be default values from the HZ_CUST_PROF_CLASS_AMTS table, which can be modified in this table for a specific customer account or customer account site. For example while the profile class Large Independent Retail Stores may have an overall credit limit of 250,000 Irish punts, you may limit a new customer in this class to an overall credit limit of 50,000 Irish punts. |
CUST_ACCT_PROFILE_AMT_ID |
Customer Profile:
|
A customer account has a customer profile class that provides default customer account attributes. The HZ_CUST_PROFILES table stores information about credit characteristics that are common across a group of customer accounts. The characteristics specified in this table can be used as default characteristics for similar customer accounts. For example, you can create a profile class called Large Independent Retail Stores and specify several attributes that describe this class of customer. In future, you can assign new customers to this class so that new customer inherits characteristics of class. |
|
Contact Point:
|
The HZ_CONTACT_POINT table stores information about how to communicate to parties or party sites using electronic media such as e-mail, Electronic Data Exchange Interface (EDI), telephone, telex and the Internet. For example, telephone-related data can include the type of telephone line, a touch-tone indicator, a country code, the area code, the telephone number, and an extension number to a specific handset. |
CONTACT_POINT_ID |
Contact Preference:
|
A customer account can express preferences on when and how to be contacted. The HZ_CONTACT_PREFERENCES table stores information on how to contact a customer. The major related tables are the HZ_PARTIES, HZ_PARTY_SITES table and the HZ_CONTACT_POINTS table. For example, a customer of the Person type, Ms Jane Doe could express the preference not to be contacted from October 1, 2000 to October 15, 2000, in this case the record in the HZ_CONTACT_PREFERENCES table is related to the HZ_PARTIES table. Ms Doe can also restrict her contact preference to a particular address, in which case, the record in the HZ_CONTACT_PREFERENCES table is related to the HZ_PARTY_SITE table. |
CONTACT_PREFERENCE_ID |
Credit Rating:
|
Creditworthiness is part of the information about a party. The HZ_CREDIT_RATINGS table stores information about the creditworthiness of a party. A credit rating firm, such as D&B, usually supplies this information. |
CREDIT_RATING_ID |
Certification:
|
Certification is part of an organization's information. The HZ_CERTIFICATIONS table stores information about accreditation that is usually awarded to an Organization party following the evaluation of the party by the awarding organization. For example, the International Organization for Standardization has established standards for quality systems. An ISO9000 certification is awarded after an evaluation of an organization that demonstrates adherence to the standards specified by ISO. |
CERTIFICATION_ID |
Citizenship:
|
Citizenship is part of a person's information. The HZ_CITIZENSHIP table stores information about a person's claimed nationality. People can have more than one citizenship in their lifetimes and can have multiple citizenships at the same time. |
CITIZENSHIP_ID |
Class Category:
|
Class Categories provides a way to classify parties and party sites. The HZ_CLASS_CATEGORIES table stores the information about categories that is used to classify parties and related entities. The possible values for class categories include NAICS, SIC1987 and customer category. |
CLASS_CATEGORY |
Class Category Use:
|
Classification is an open structure. Class Category Use indicates which table uses which class category. The HZ_CLASS_CATEGORY_USES table stores information about the tables that use a particular class category. For example, the SIC 1987 class category can be used to classify the parties that have the Organization party type. |
CLASS_CATEGORY OWNER_TABLE COLUMN_NAME |
Class Code Relationship:
|
Class Code Relationships provides a method to build hierarchy structures within Class Codes. The HZ_CLASS_CODE_RELATIONS table stores information about relationships between parent and child classification codes and the categories in the HZ_CLASS_CATEGORIES table. For example, within the North America Industry Classification System NAICS Manufacturing category (code 33), the code for radio and TV manufacturers (code 33422) is the child in relation to the classification code for Communications Equipment manufacturer (code 3342). |
CLASS_CATEGORY CLASS_CODE SUB_CLASS_CODE |
Code Assignment:
|
Code Assignment links an instance of the class code to an instance of the classified table. The HZ_CODE_ASSIGNMENTS table is an intersection table that links the classification codes in the FND_LOOKUP_VALUES table to the names of the parties or other entities stored in the table identified in the OWNER_TABLE_NAME column. |
CODE_ASSIGNMENT_ID |
Education:
|
A party of the Person type can have an education history. The HZ_EDUCATION table stores general information about the educational history of a party of the Person type. For example, a person may have attended the University of California from 1995 to 1999 and received an undergraduate degree in Computer Science with a GPA of 4.0. This table stores the information about the university, the period when the person attended, and the subject that the student majored in. |
EDUCATION_ID |
Employment History:
|
A party of the Person type can have an employment history. The HZ_EMPLOYMENT_HISTORY table stores information about the employment and military service history of a party of the Person type. For example, John Smith, an accountant, whose supervisor was Jane Doe, worked in US Operation division of Vision Corporate from July 12, 1994 to January 23, 2000. |
EMPLOYMENT_HISTORY_ID |
Financial Profile:
|
The HZ_FINANCIAL_PROFILE table stores information about the financial accounts owned by a party. For example, when you perform a credit evaluation of a prospective customer, data may be entered about the balance in he prospective customer's bank account. |
FINANCIAL_PROFILE_ID |
Financial Report:
|
The HZ_FINANCIAL_REPORTS table stores information about the reports on the financial status of a party. Detailed nmerical financial data is available in the HZ_FINANCIAL_NUMBERS table. For example, the records in this table can indicate whether the numerical data in the HZ_FINANCIAL_NUMBERS table are actual, estimated, consolidated, and so on. |
FINANCIAL_REPORT_ID |
Financial Number:
|
The HZ_FINANCIAL_NUMBERS table stores detailed financial information for the HZ_FINANCIAL_REPORTS table. For example, a record could store the information that projected leasing revenue includes 1,000,000 Italian lira. |
FINANCIAL_NUMBER_ID |
Person Interest:
|
The HZ_PERSON_INTEREST table stores information about sports, hobbies and personal interests of a party of the Person type. This information could be helpful in developing a more personalized relationship with a business contact. For example, a customer may indicate that he has had an interest in driving in sports car races for the past seven years or that he enjoys attending baseball games. |
PERSON_INTEREST_ID |
Person Language:
|
The HZ_PERSON_LANGUAGE table stores information about a language spoken by a party of the Person type. For example, a person may speak Spanish as her primary language. You would create another record if she speaks French, but it is not her primary language. Note that a separate record must exist for each language. |
LANGUAGE_USE_REFERENCE_ID |
Work Class:
|
The HZ_WORK_CLASS table stores custom-defined classification information about a person's job title and work experience. For example, one system may use classifications such as "Electrician" and "Master" while another may use job codes and seniority indicators such as "EM3" and "over 20" to indicate a class 3 Master Electrician with over 20 years of experience. Note that there may be multiple records in the HZ_WORK_CLASS table for each record in the HZ_EMPLOYMENT_HISTORY table. |
WORK_CLASS_ID |
Original System Reference:
|
The HZ_ORIG_SYSTEM_REFERENCES table stores the mapping between source system references and the owner tables. The source system reference identifies the system that was the source of the data stored in a record. The owner table is the TCA table that stores that data. | ORIG_SYSTEM_REF_ID |
Account Merge:
|
||
Party Merge:
|
Related Topics
Business Object API Attributes Information Overview
This table provides the following information about the TCA Business Objects Events:
Name of event
Description
| Event Name | Event Description |
|---|---|
| Persons Created oracle.apps.ar.hz.personBO.create |
Raised when one or more Person business objects are completely created for all mandatory embedded objects, structures, and entities. |
| Persons Updated oracle.apps.ar.hz.personBO.update |
Raised when one or more TCA entities embedded within a complete Person business object are created or modified. |
| Person Customers Created oracle.apps.ar.hz.CustBO.create |
Rasied when one or more Person Customer business objects are completely created for all mandatory embedded objects, structures, and entities. This business object combines TCA Party and Account layers and is created when a Customer Account business object is created for and existing Person business object. |
| Person Customers Updated oracle.apps.ar.hz.CustBO.update |
Raised when one or more TCA embedded entities within a complete Person Customer business object are created or modified. |
| Organizations Created oracle.apps.ar.hz.orgBO.create |
Raised when one or more Organization business objects are completely created for all mandatory embedded objects, structures, and entities. |
| Organizations Updated oracle.apps.ar.hz.orgBO.update |
Raised when one or more TCA entities embedded within a complete Organization business object are created or modified. |
| Organization Customers Created oracle.apps.ar.hz.orgCustBO.create |
Raised when one or more Organization Customer business objects are completely created for all mandatory embedded objects, structures, and entities. This business object combines TCA Party and Account layers and is created when a Customer Account business object is created for and existing Organization business object. |
| Organization Customers Updated oracle.apps.ar.hz.orgCustBO.update |
Raised when one or more TCA embedded entities within a complete Organization Customer business object are created or modified. |
Related Topics