The TCA API is an integrated set of code designed in a highly modular fashion, resulting in codes that are easy to understand, maintain and extend.
The modular approach defaults and validates users who enter information; default information not provided by the user and calls the appropriate entity handler to perform the business related tasks.
Customers, consultants, and Oracle internal development teams can use Version 2 of the public TCA application programming interfaces (APIs). Version 1 of the APIs is only made available to Oracle internal development teams. The Version 2 Public API feature is available from HZ Patch set E.The Trading Community Architecture (TCA) data model is the foundation for the 11i Oracle e-Business Suite of Applications via PL/SQL APIs. These APIs (version 2) will be supported for use by customers and consultants and are available for use by internal product teams in ERP and CRM. This is a step forward from the version 1 APIs that are available only for use by internal product teams.
API Components
__API category
__PL/SQL package
__PL/SQL record structure
__PL/SQL procedure
__Parameter description
__Validations
Advantages of Using TCA API
__Flexible, easy to understand and modular.
__Extensive debugging capability.
__Extensive error handling and reporting capability.
__Robust validation in all of the APIs.
__A new locking mechanism based on the OBJECT_VERSION_NUMBER field, which has been included in all of the HZ entities for which the public APIs have been provided.
__Standard signature and availability of common parameters
The following main categories of entities are covered:
__Parties - person, organization, group
__Locations
__Party sites, party site use
__Organization contact, organization contact role
__Contact points
__Contact preferences
__Relationship types
__Relationships
__Classification
__Customer accounts
__Account sites and site uses
__Customer account role, role responsibility Customer profile and customer profile amount.
