Results for “inv_pk_key”

3 results




Overview
Explore in AI Chat

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

Overview

The EDW_IVTY_INV_LTC table is an invoice-level staging structure defined within the FII (Financial Intelligence) product family of Oracle E-Business Suite. FII is documented in ETRM as an obsolete module, and the table itself is explicitly flagged as "Not implemented in this database," meaning it is a legacy or reference-only object that will not be physically present in a standard 12.1.1 or 12.2.2 installation. Its purpose, as reflected in its name and description, is to hold one row per invoice record for downstream analytical or extract-load processing. Organizations researching this object are typically working with historical documentation, migrating legacy FII extracts, or reconciling obsolete ETL artifacts against the current EBS data model.

The ETRM metadata assigns a heuristic Data Vault classification of standalone (no foreign-key-driven link structure beyond a single referenced table). As a modeling suggestion, this table behaves closest to a satellite anchored on an invoice business key: the unique indexes on INV_PK_KEY and the composite INV_PK/INV_PK_KEY indicate a surrogate-key-driven dimension or satellite rather than a true transaction hub. Practitioners designing modern replacements should treat INV_PK_KEY as the stable business identifier and the remaining descriptive attributes as the satellite payload.

Key Information Stored

The table exposes 18 documented columns. The most significant are:

  • INV_PK_KEY — Surrogate key; subject of unique index EDW_IVTY_INV_LTC_U1 and the second element of composite unique index U2. This is the primary business-key candidate.
  • INV_PK — The invoice primary key carried from the source system; first element of the composite unique index U2.
  • INV_ID — Foreign-key column referencing JTF_XML_INVOCATIONS_B; links the invoice record to its XML invocation context.
  • INV_NAME and NAME — Human-readable invoice identifiers/descriptions used for reporting labels.
  • INV_TYPE_FK and INV_TYPE_FK_KEY — Foreign-key-style references to invoice type classification (surrogate and business form).
  • INV_SOURCE — Identifies the originating system or feeder process for the invoice.
  • INV_DP — Invoice data point or derived attribute value.
  • INSTANCE — Instance discriminator, used when the table is populated across multiple EBS instances or operating units.
  • USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — Descriptive flexfield-style placeholder columns for client-specific extension data.
  • CREATION_DATE, LAST_UPDATE_DATE, CANCELLED_DATE — Standard audit and lifecycle timestamps; CANCELLED_DATE supports soft-delete/void tracking.

Common Use Cases and Queries

The predominant use case is historical or migration reporting. Because the physical table is not implemented, queries in a live environment will typically fail unless the object was manually recreated. In legacy FII warehouses, extracts were used to trend invoice activity by source and type:

  • Invoice counts and classification: SELECT INV_TYPE_FK, INV_SOURCE, COUNT(*) FROM EDW_IVTY_INV_LTC GROUP BY INV_TYPE_FK, INV_SOURCE;
  • Cancellation analysis: SELECT INV_PK_KEY, CANCELLED_DATE FROM EDW_IVTY_INV_LTC WHERE CANCELLED_DATE IS NOT NULL;
  • Audit-window reconciliation: filter on CREATION_DATE and LAST_UPDATE_DATE to map invoices to load windows.
  • XML linkage: join INV_ID to JTF_XML_INVOCATIONS_B to trace invoice records back to their invocation payloads.

Related Objects

The documented foreign-key relationship anchors this table to one external object. Additional dependencies follow from standard FII and EBS invoice modeling:

  • JTF_XML_INVOCATIONS_B — joined on EDW_IVTY_INV_LTC.INV_ID = JTF_XML_INVOCATIONS_B.INVOCATION_ID; the only documented FK target.
  • EDW_IVTY_INV_ALL / FII invoice fact tables — sibling extract structures consuming the same invoice key space.
  • AR_INVOICE_HEADERS_ALL — the Receivables source of truth for invoice-level attributes mapped into INV_PK and INV_NAME.
  • RA_CUSTOMER_TRX_ALL — underlying transaction table for receivable invoice data flows.
  • GL_JE_LINES / XLA distributions — downstream accounting objects reconciled against invoice extracts.

Because the object is marked obsolete and not implemented, any integration referencing EDW_IVTY_INV_LTC should be reviewed for replacement by a supported FII or Fusion data model object.