Results for “hz_org_profiles_ext_sg”
29 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
HZ_ORG_PROFILES_EXT_SG is a staging table owned by the AR (Receivables) schema in Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. Its documented purpose is narrow and specific: it stages the copying of extension data during organization profile versioning. Oracle's organization profile model allows a party's organizational profile — its addresses, contact points, classification codes, and related attributes — to exist in multiple versions, with one version designated as active. When a profile is versioned, the extension attribute values attached to the profile must be carried forward from the old version to the new one. HZ_ORG_PROFILES_EXT_SG serves as the transient holding area for that operation, pairing an old profile identifier with a new one before the values are committed to the permanent profile tables.
The table is therefore not a source of business truth. It is an internal processing structure that is typically populated and consumed within the scope of a single versioning routine or concurrent program, and it may be empty in a steady-state production instance. Its structure reflects this transient role. Under the heuristic Data Vault classification mined from its foreign key structure, the object is modeled as standalone, meaning it exhibits no declared foreign key relationships and therefore is not classified as a hub, link, or satellite. This is consistent with a staging table's design: constraints are deliberately omitted to maximize insert throughput and to avoid referential integrity failures during intermediate processing states.
Key Information Stored
The documented physical schema comprises four columns in the AR schema. The primary key is defined by the constraint HZ_ORG_PROFILES_EXT_SG_PK, which spans the composite of NEW_PROFILE_ID and OLD_PROFILE_ID. Because this composite key is the only documented unique identifier, both columns function simultaneously as surrogate primary key components and as the only business-key candidates available in the metadata.
- NEW_PROFILE_ID — Identifies the target (newer) organization profile version that is receiving the copied extension data. Part of the composite primary key.
- OLD_PROFILE_ID — Identifies the source (older) organization profile version from which extension data is being copied. Part of the composite primary key.
- WORK_UNIT_NUMBER — A processing control value used to group or scope rows belonging to a particular versioning work unit, allowing batches to be tracked or purged independently.
- STATUS — Indicates the processing state of the staged row, distinguishing rows that have not yet been applied from those successfully transferred or rejected.
The composite key guarantees that a given old-to-new profile pairing appears only once, which prevents duplicate extension transfer during retries of a versioning operation.
Common Use Cases and Queries
Direct querying of this table is uncommon outside of development, data migration, and production support scenarios. The most frequent practical uses are identifying incomplete versioning operations and confirming that extension data was staged before being applied.
A support analyst investigating a stalled profile version might run:
SELECT old_profile_id, new_profile_id, work_unit_number, status FROM ar.hz_org_profiles_ext_sg WHERE work_unit_number = :work_unit ORDER BY old_profile_id;
To locate rows that never completed processing:
SELECT new_profile_id, old_profile_id, status FROM ar.hz_org_profiles_ext_sg WHERE status <> 'PROCESSED';
To confirm that staging was performed for a specific profile pair, the composite key is used directly:
SELECT 1 FROM ar.hz_org_profiles_ext_sg WHERE new_profile_id = :new_id AND old_profile_id = :old_id;
Reporting use is generally limited to data-quality checks that compare staged profile pairs against the corresponding rows in the permanent extension tables to detect orphaned or mismatched entries.
Related Objects
Because the metadata classifies this table as standalone, no foreign keys are documented. The relationship model below is therefore inferred from the profile identifiers the table carries and should be validated against the deployed instance.
- HZ_ORG_PROFILES — The master organization profile table; NEW_PROFILE_ID and OLD_PROFILE_ID both correspond to profile identifiers held here.
- HZ_ORG_PROFILES_EXT — The permanent extension attribute storage for organization profiles, which is the ultimate destination of the staged copy operation.
- HZ_PARTIES — The party record to which the organization profile belongs, reachable through the profile's party relationship.
- HZ_ORG_CONTACTS — Organization contact records that may participate in the same versioning transaction.
- HZ_CONTACT_POINTS — Contact point data versioned alongside profile extensions, useful for cross-checking staging completeness.
- HZ_LOCATIONS — Address records associated with the organization profile versions being copied.
No public APIs are documented against HZ_ORG_PROFILES_EXT_SG; it is accessed by Oracle's internal versioning logic rather than by customer-facing PL/SQL interfaces.
-
Staging table for copying extensions data for organization profile versioning.
-
Staging table for copying extensions data for organization profile versioning.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
eTRM - AR Tables and Views 12.1.1
Territory information
-
eTRM - AR Tables and Views 12.2.2
Territory information
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - AR Tables and Views 12.2.2
Territory information
-
eTRM - AR Tables and Views 12.1.1
Territory information