Results for “update_party_site”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IES_TCA_BP_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It resides in the Oracle iSupport / Internet Expenses Service (IES) module and functions as a lightweight integration layer between iSupport (or a comparable self-service application) and the Oracle Trading Community Architecture (TCA) model. Its core business purpose is to programmatically create and maintain TCA party, party site, party site use, organization, person, location, and contact records without requiring the user to navigate the full TCA administration windows.

In EBS 12.1.1 and 12.2.2, TCA is the single source of truth for customer, supplier, contact, and address data. Rather than duplicating that logic, IES_TCA_BP_PKG delegates the heavy lifting to the TCA public APIs (for example, the HZ_PARTY_V2PUB and HZ_LOCATION_V2PUB family) and the shared FND_API error-handling framework. The package is therefore a thin wrapper: it normalizes input, calls the appropriate TCA API, interprets the returned status, and translates any TCA message stack into an EBS-friendly result. It is classified in ETRM as an "OTHER" API, meaning it is not a formally published public API and is not guaranteed to be upward compatible.

Because the documented dependency list shows both FND_API and the SQL STANDARD package, the code follows the common EBS pattern of returning a boolean or status code, with error messages conveyed through the FND message stack rather than raised exceptions.

Key Procedures and Functions

ETRM documents seven procedures/functions in this package. Their functional roles are:

  • CREATE_ORGANIZATION — Creates a TCA organization party, including the organization's name and related profile information, by invoking the organization creation API.
  • CREATE_PERSON — Creates a TCA person party, capturing personal name components and related attributes, and returns the newly created party identifier.
  • CREATE_LOCATION — Creates a TCA location record containing address elements (street, city, state, postal code, country), typically to be associated with a party site.
  • CREATE_PARTY_SITE — Associates a previously created or existing location with a party, producing a party site record that can then be referenced by transactions and contacts.
  • CREATE_ORG_CONTACT — Creates a contact associated with an organization party, tying a person to an organization for communication and relationship purposes.
  • UPDATE_ORG_CONTACT — Modifies an existing organization contact, for example to change the contact's role, phone number, or email address.
  • UPDATE_PARTY_SITE — Updates an existing party site, such as changing the site's purpose or effective dates.

The procedures are ordered logically (parties and locations first, then associations and subsequent maintenance), consistent with the TCA entity dependency hierarchy. No parameter lists are documented in the ETRM extract, so signatures should be confirmed in the package specification before calling.

Tables Accessed

The ETRM metadata records no directly referenced tables via APPS synonyms. This is expected: the package performs its data manipulation through TCA public APIs, which internally write to the HZ_* base tables — including HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_ORG_CONTACTS, and HZ_PARTY_SITE_USES. Direct DML against these tables from custom code is not advisable; the APIs maintain the internal keys, party relationships, and denormalized columns that TCA requires. Any custom reporting on data created by this package should query the HZ_* views rather than the underlying tables.

Usage Notes

IES_TCA_BP_PKG is an internal iSupport component. It is normally invoked indirectly — from iSupport forms, OAF pages, or iSupport concurrent/PLSQL processes that register parties and contacts as part of incident or customer management. In ETRM 12.2.2 the package is referenced by no other documented packages, confirming that its primary callers are application-layer artifacts rather than peer PL/SQL packages.

Developers extending or troubleshooting iSupport integration should treat this package as implementation detail: prefer the official TCA public APIs for new development, and reserve use of IES_TCA_BP_PKG to diagnosing existing iSupport behavior. When invoking it in custom code, always check the returned status and inspect the FND message stack for errors, since the TCA APIs it wraps return failure codes rather than raising exceptions. Testing should be performed on a full clone with a valid TCA setup, as the package requires a functioning Trading Community Architecture installation.