Results for “jg_zz_invoice_info”

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

Overview

JG_ZZ_INVOICE_INFO is a Regional Localizations (JG) table owned by the AP schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores additional country-specific payment information for invoices that cannot be accommodated by the standard Payables invoice model. The table is a descriptive (flexfield-style) extension of invoice data, allowing localizations to capture regulatory, banking, or statutory attributes required in specific countries without modifying the base AP_INVOICES_ALL structure.

From a data modeling perspective, the documented relationship metadata classifies JG_ZZ_INVOICE_INFO as a standalone object. The absence of foreign key relationships to other tables, combined with a single-column primary key on INVOICE_ID, suggests that this table functions as a satellite-like extension keyed directly to the invoice identifier rather than as a hub or link. This is a heuristic modeling suggestion based on the FK structure rather than a declared Data Vault classification.

Key Information Stored

The table contains 37 documented columns. The most significant are:

• INVOICE_ID — The primary key and sole business-key candidate. Physically, the table is keyed by the JG_ZZ_INVOICE_INFO_PK constraint on INVOICE_ID, with a unique index JG_ZZ_INVOICE_INFO_U1 also on INVOICE_ID. This column corresponds to the invoice in the Payables module.
• JGZZ_ATTRIBUTE_CATEGORY — A descriptive flexfield context column that determines which attribute segments are meaningful for a given invoice.
• JGZZ_INVOICE_INFO1 through JGZZ_INVOICE_INFO30 — Thirty generic, localization-defined attribute columns. These carry the country-specific payment details such as banking information, statutory identifiers, or regulatory references. Because they are generically named, their meaning is driven by JGZZ_ATTRIBUTE_CATEGORY and the localization configuration.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO audit columns that record which user created and last modified each row and when.

No additional descriptive columns beyond the attribute set and audit fields are documented, reinforcing the design as a pure flexfield extension.

Common Use Cases and Queries

Typical usage involves retrieving localization-specific payment details for a specific invoice, or reporting on invoices that carry non-null country-specific attributes. A basic retrieval pattern joins the extension to the base invoice table on INVOICE_ID:

• SELECT i.invoice_num, x.jgzz_attribute_category, x.jgzz_invoice_info1, x.jgzz_invoice_info2 FROM ap_invoices_all i, jg_zz_invoice_info x WHERE i.invoice_id = x.invoice_id AND i.invoice_id = :p_invoice_id;
• Reporting queries often filter on JGZZ_ATTRIBUTE_CATEGORY to isolate invoices of a particular country or payment scenario.
• Data-quality audits can count rows where JGZZ_ATTRIBUTE_CATEGORY is populated but the corresponding attributes are null, or vice versa, to validate localization configuration.

Because the attribute columns are generic, report developers must consult the localization setup that maps JGZZ_INVOICE_INFO1..30 to meaningful business labels before exposing them to end users.

Related Objects

The documented metadata identifies JG_ZZ_INVOICE_INFO as standalone, meaning no foreign keys are mined from its structure. The principal relationships are logical rather than enforced:

• AP_INVOICES_ALL — The primary Payables invoice table, joined on INVOICE_ID. This is the base object the extension supplements.
• AP_INVOICE_PAYMENTS_ALL — Payment records tied to invoices, relevant when the localization attributes describe payment instructions.
• AP_INVOICE_LINES_ALL — Invoice line detail, which may be combined with the extension in reporting.
• AP_INVOICE_DISTRIBUTIONS_ALL — Distribution accounting lines for the invoice.
• AP_SUPPLIERS / AP_SUPPLIER_SITES_ALL — Supplier and site records, used when reporting on banking or remittance details captured in the extension.

These relationships should be treated as logical joins on INVOICE_ID for query and reporting purposes; no declarative referential integrity is documented on JG_ZZ_INVOICE_INFO.