Search Results copy_org_conc_main




Overview
Explore in AI Chat

Overview

APPS.HZ_EXTENSIBILITY_PVT is a private PL/SQL package within the Oracle E-Business Suite Trading Community Architecture (TCA) that provides the internal implementation layer for handling extensible attributes (also called descriptive flexfields and user-defined attributes) on party, person, and organization records. In Oracle EBS 12.1.1 and 12.2.2, the extensibility framework allows customers to add custom attributes to standard TCA entities without modifying the underlying schema. This package encapsulates the heavy lifting required to read, transform, copy, and persist those user-defined attribute values across the various extensibility tables.

Because the package carries the _PVT suffix, it is classified as a private API. It is not intended to be called directly by customer or partner code; instead, it sits beneath the public API surface (HZ_EXTENSIBILITY_PUB) and other higher-level packages, providing the reusable logic that those public interfaces depend upon. Its principal business role is to guarantee that flexfield data associated with a party, organization, or person is correctly materialized when records are created, updated, or copied.

Key Procedures and Functions

The ETRM documentation identifies eight documented procedures and functions. Their purposes are as follows:

  • PROCESS_USER_ATTRS_FOR_ITEM — Applies user attribute values to a specific extensibility item, orchestrating the persistence of attribute data for the target entity.
  • GET_USER_ATTRS_FOR_ITEM — Retrieves the user-defined attribute values associated with a given extensibility item for downstream consumption.
  • COPY_PERSON_EXTENT_DATA — Copies extensibility data for a person entity, supporting duplication or clone scenarios.
  • COPY_ORG_EXTENT_DATA — Copies extensibility data for an organization entity, mirroring the person-level logic at the organization level.
  • COPY_ORG_CONC_MAIN — Main (driver) routine for the organization copy operation in concurrent-processing mode.
  • COPY_PER_CONC_MAIN — Main (driver) routine for the person copy operation in concurrent-processing mode.
  • COPY_ORG_CONC_SUB — Subordinate worker routine for the organization copy process, invoked for individual records or chunks.
  • COPY_PER_CONC_SUB — Subordinate worker routine for the person copy process.

No parameter signatures are documented in the ETRM metadata, and none should be assumed.

Tables Accessed

The package references a set of TCA and extensibility framework tables through APPS synonyms. The extensibility framework tables — EGO_EXTFWK_S and PLITBLM — support the attribute framework metadata and value storage. The core TCA extensibility tables include HZ_ORG_PROFILES_EXT_B, HZ_ORG_PROFILES_EXT_SG, and HZ_ORG_PROFILES_EXT_TL for organization-level flexfield data, and the parallel HZ_PER_PROFILES_EXT_B, HZ_PER_PROFILES_EXT_SG, and HZ_PER_PROFILES_EXT_TL tables for person-level flexfield data. HZ_ORGANIZATION_PROFILES and HZ_PERSON_PROFILES serve as the parent profile records to which the extensibility data is attached. The B, TL, and SG suffixes reflect the standard TCA multi-lingual, translation, and secured-group storage design.

Usage Notes

HZ_EXTENSIBILITY_PVT is referenced by HZ_EXTENSIBILITY_PUB, by itself (recursive/internal calls), and by HZ_PARTY_V2PUB. In practice it is invoked indirectly when a caller uses the public extensibility or party APIs to create, update, or copy party, person, or organization records that carry custom attributes. The concurrent-copy routines (COPY_ORG_CONC_MAIN/SUB and COPY_PER_CONC_MAIN/SUB) indicate that bulk duplication of extensibility data can be driven from concurrent programs rather than from a single interactive transaction. Because the package is a private API, customizations should never call it directly; developers should route requests through the corresponding public packages. It also depends on FND_API and the standard EGO_ATTR_GROUP_REQUEST_TABLE, EGO_USER_ATTR_DATA_TABLE, and EGO_USER_ATTR_ROW_TABLE structures supplied by the extensibility framework, confirming its integration with the shared Oracle attribute engine.