Results for “jgzz_ps_info30”

8 results




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

Overview

The AP.JG_ZZ_PAY_SCHED_INFO table is a Regional Localization (JG) object that stores additional country-specific attributes associated with payment schedules in Oracle Payables. It resides in the AP schema and is classified as VALID in the ETRM catalog for Oracle EBS 12.1.1 and 12.2.2. The "ZZ" naming convention and the presence of a generic JGZZ_ATTRIBUTE_CATEGORY column with 30 sequentially numbered flexfield-style attributes position this table as a DESCRIPTIVE FLEXFIELD extension to the standard Payables payment schedule infrastructure. It allows localizations to capture statutory, regulatory, or reporting data required by specific countries without altering the core AP_PAYMENT_SCHEDULES structure.

From a Data Vault modeling perspective, the documented relationship data classifies this object heuristically as standalone, with no enforced foreign key relationships mined from the FK structure. This suggests it may be modeled as a standalone hub or satellite rather than a true link. Because it shares INVOICE_ID and PAYMENT_NUM with the payment schedule entity but has no documented FK constraint to it, the association is logical rather than enforced. The classification is a modeling suggestion only; referential behavior should be confirmed against the actual AP domain model before building a Data Vault layer.

Key Information Stored

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

  • INVOICE_ID — Together with PAYMENT_NUM, forms the composite primary key JG_ZZ_PAY_SCHED_INFO_PK. Identifies the parent invoice whose schedule line is being extended.
  • PAYMENT_NUM — The payment schedule line number for the invoice. This is the column the user searched for; it is a business-key component, not a surrogate.
  • JGZZ_ATTRIBUTE_CATEGORY — A descriptive flexfield context or category value that determines which regional attributes are meaningful for a given row.
  • JGZZ_PS_INFO1 through JGZZ_PS_INFO30 — Thirty generic attribute columns holding country-specific payment schedule information. These follow the standard Oracle flexfield pattern of ATTRIBUTE_CATEGORY plus numbered segments and are intended to be interpreted per localization.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle WHO audit columns tracking the user, date, and session of the last modification.
  • CREATED_BY, CREATION_DATE — Standard audit columns recording the creating user and timestamp.

The surrogate primary key JG_ZZ_PAY_SCHED_INFO_PK is composite over INVOICE_ID and PAYMENT_NUM. The unique index JG_ZZ_PAY_SCHED_INFO_U1 shares the identical column list, confirming that the business key and the primary key are the same pair. There is no single surrogate sequence column documented.

Common Use Cases and Queries

Typical usage involves retrieving the country-specific attributes for a given invoice payment line. A standard lookup by the searched term appears as:

SELECT INVOICE_ID, PAYMENT_NUM, JGZZ_ATTRIBUTE_CATEGORY,
       JGZZ_PS_INFO1, JGZZ_PS_INFO2, JGZZ_PS_INFO3
FROM   AP.JG_ZZ_PAY_SCHED_INFO
WHERE  PAYMENT_NUM = :payment_num;

Reporting queries commonly join to AP_INVOICES_ALL and AP_PAYMENT_SCHEDULES_ALL on INVOICE_ID and PAYMENT_NUM to present localized attributes alongside standard schedule amounts, due dates, and payment status. Localization patches populate the JGZZ_PS_INFO* columns through forms and concurrent programs; reporting should scope queries by JGZZ_ATTRIBUTE_CATEGORY to avoid misinterpreting segments across countries. Audit-oriented extracts frequently filter on LAST_UPDATE_DATE for incremental loads.

Related Objects

Because no enforced foreign keys are documented, the following relationships are logical and based on shared business keys:

  • AP.AP_PAYMENT_SCHEDULES_ALL — The core payment schedule table; joined on INVOICE_ID and PAYMENT_NUM.
  • AP.AP_INVOICES_ALL — Parent invoice header; joined on INVOICE_ID.
  • AP.AP_INVOICE_LINES_ALL — Invoice distributions, related through INVOICE_ID.
  • AP.AP_INVOICE_PAYMENTS_ALL — Payment application records linked via INVOICE_ID.
  • AP.JG_ZZ_PAY_SCHED_INFO localization views and the AP Payables Open Interface — import paths that populate regional attributes.