Results for “parent_party_id”

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

Overview

The table FII_AR_CACCTS_TMP_GT belongs to the FII (Financial Intelligence) product family, a legacy analytical and reporting layer that shipped with earlier Oracle E-Business Suite releases. In Oracle EBS 12.1.1 and 12.2.2, FII objects are classified as obsolete; they are retained for backward compatibility with historical patch levels and are not part of the supported functional footprint. The _TMP and _GT suffixes indicate that this object is a temporary, session-scoped staging structure, typically a Global Temporary Table (GTT), used to materialize intermediate result sets before they are consumed by downstream FII reports or concurrent programs.

The object is owned by the FII schema and is documented with four columns. It carries a heuristic Data Vault classification of standalone, meaning that within the mined foreign-key structure it is neither a hub, link, nor satellite, but rather a transient staging artifact. From a Data Vault modeling perspective, this structure is best treated as a load-support object rather than a durable entity, and it should not be promoted into an enterprise data warehouse without transformation.

The ETRM documentation records the object as "Not implemented in this database." This is a critical operational fact: the table may exist only as a metadata placeholder, may be deployed conditionally by specific FII patches, or may have been dropped in later AD (Applications DBA) upgrade passes. Any code referencing it should defensively validate existence at runtime.

Key Information Stored

The documented physical schema exposes four columns. They represent a denormalized snapshot of customer account information scoped to a parent party hierarchy:

• PARENT_PARTY_ID — Identifies the top-level party in a related-party or hierarchy grouping. This is the business grouping key that drives report rollups.
• CUST_ACCOUNT_ID — The customer account surrogate identifier. This column is documented as a foreign key to HZ_CUST_ACCOUNTS, making it the primary join path back to the Trading Community Architecture (TCA) model.
• ACCOUNT_PARTY_ID — The party identifier that owns the account, allowing the staging set to relate accounts to their underlying parties without an additional lookup.
• ACCOUNT_NUMBER — The human-readable account number, a business-key candidate used for reconciliation against the operational Receivables ledger.

No documented surrogate primary key or unique index is recorded in the ETRM metadata. In a global temporary table of this shape, uniqueness is normally enforced by the loading program rather than by a database constraint.

Common Use Cases and Queries

The typical consumption pattern is a concurrent program that populates the GTT for the current session, then joins it to permanent tables for reporting. A representative query pattern follows:

• Account hierarchy rollup: SELECT t.parent_party_id, t.account_number, a.account_name FROM fii_ar_caccts_tmp_gt t JOIN hz_cust_accounts a ON a.cust_account_id = t.cust_account_id;
• Reconciliation of staged accounts against live Receivables balances, using ACCOUNT_NUMBER as the matching business key.
• Party-level aggregation joining ACCOUNT_PARTY_ID to HZ_PARTIES.

Because the object is a temporary staging structure, queries must execute within the same session that performed the load. Reporting tools should avoid caching results across sessions.

Related Objects

• HZ_CUST_ACCOUNTS — joined on CUST_ACCOUNT_ID; the documented foreign-key target and the master source of customer account records.
• HZ_PARTIES — joined on ACCOUNT_PARTY_ID or PARENT_PARTY_ID to resolve party names and hierarchy attributes.
• HZ_CUST_ACCOUNT_ROLES — used to expand account-to-party relationships beyond the flattened staging columns.
• AR_HZ_CUST_ACCOUNTS_V — a common Receivables view for validating staged account numbers.
• FII_AR_* reporting objects — sibling FII staging and output structures consumed by the same analytical programs.

Given the obsolete status of the FII product, implementations should plan migration of any dependent logic to supported Receivables and TCA interfaces.