Results for “jgzz_attribute_category”
50+ 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 withPAYMENT_NUM, forms the composite primary keyJG_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_INFO1throughJGZZ_PS_INFO30— Thirty generic attribute columns holding country-specific payment schedule information. These follow the standard Oracle flexfield pattern ofATTRIBUTE_CATEGORYplus 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 onINVOICE_IDandPAYMENT_NUM.AP.AP_INVOICES_ALL— Parent invoice header; joined onINVOICE_ID.AP.AP_INVOICE_LINES_ALL— Invoice distributions, related throughINVOICE_ID.AP.AP_INVOICE_PAYMENTS_ALL— Payment application records linked viaINVOICE_ID.AP.JG_ZZ_PAY_SCHED_INFOlocalization views and the AP Payables Open Interface — import paths that populate regional attributes.
-
Additional country-specific information for payment schedules
-
Holds Country Specific Format Data
-
Additional country-specific information for vendor sites
-
(Release 12.0 Only)
APPS.AR_CUSTOMER_PROFILE_CLASSES_V·↳ ARPT_SQL_FUNC_UTIL·↳ AR_AUTOCASH_HIERARCHIES·↳ AR_COLLECTORS·Explore AR module →
-
JTF_CUSTOMER_PROFILES_V retrieves credit information for your customer accounts and customer account sites.
APPS.JTF_CUSTOMER_PROFILES_V·↳ HZ_CUSTOMER_PROFILES·Explore JTF module →
-
View for profile class amounts
APPS.AR_CUST_PROF_CLASS_AMTS·↳ ARPT_SQL_FUNC_UTIL·↳ AR_CHARGE_SCHEDULES·↳ GL_DAILY_CONVERSION_TYPES·Explore AR module →
-
Additional country-specific information for payment schedules
-
JTF_CUSTOMER_PROFILES_V retrieves credit information for your customer accounts and customer account sites.
APPS.JTF_CUSTOMER_PROFILES_V·↳ HZ_CUSTOMER_PROFILES·Explore JTF module →
-
Additional country-specific payment information for invoices
-
Stores information about the credit limits specified for a customer's profile.
-
View: AR_CUSTOMER_PROFILES_V 12.1.1
(Release 11.5 Only)
APPS.AR_CUSTOMER_PROFILES_V·↳ ARPT_SQL_FUNC_UTIL·↳ AR_AUTOCASH_HIERARCHIES·↳ AR_COLLECTORS·Explore AR module →
-
Credit information for customer accounts and customer account sites
-
(Release 12.0 Only)
APPS.AR_CUSTOMER_PROFILE_CLASSES_V·↳ ARPT_SQL_FUNC_UTIL·↳ AR_AUTOCASH_HIERARCHIES·↳ AR_COLLECTORS·Explore AR module →
-
Customer profile class amount limits for each currency
-
Customer profile amount limits for each currency
-
Customer profile class amount limits for each currency
-
Holds Country Specific Format Data
-
Additional country-specific payment information for invoices
-
Additional country-specific information for vendor sites
-
Customer profile class information
-
EFT Payments Table Data
-
EFT Payments Table Data
-
Customer profile amount limits for each currency
-
Customer profile class amount limits for each currency
-
Customer profile class amount limits for each currency
-
Stores information about the credit limits specified for a customer's profile.
-
Customer profile class information
-
Standard credit profile classes
-
This table is used to store the deleted records for hz_customer_profiles during account merge
-
The HZ_CUST_PROFILE_AMTS_M table stores the information of customer profile amounts from HZ_CUST_PROFILE_AMTS table before the account merge happens.The primary key for this table is CUST_ACCT_PROFILE_AMT_ID, CUSTOMER_MERGE_HEADER_ID.
-
View: AR_CUSTOMER_PROFILES_V 12.2.2
(Release 11.5 Only)
APPS.AR_CUSTOMER_PROFILES_V·↳ ARPT_SQL_FUNC_UTIL·↳ AR_AUTOCASH_HIERARCHIES·↳ AR_COLLECTORS·Explore AR module →
-
Standard credit profile classes
-
View for profile class amounts
APPS.AR_CUST_PROF_CLASS_AMTS·↳ ARPT_SQL_FUNC_UTIL·↳ AR_CHARGE_SCHEDULES·↳ GL_DAILY_CONVERSION_TYPES·Explore AR module →
-
The HZ_CUST_PROFILE_AMTS_M table stores the information of customer profile amounts from HZ_CUST_PROFILE_AMTS table before the account merge happens.The primary key for this table is CUST_ACCT_PROFILE_AMT_ID, CUSTOMER_MERGE_HEADER_ID.
-
Customer credit information
-
Customer credit information
-
This table is used to store the deleted records for hz_customer_profiles during account merge
-
Credit information for customer accounts and customer account sites