Results for “jg_zz_sys_formats_all_b”

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

Overview

JG_ZZ_SYS_FORMATS_ALL_B is a base table within the Oracle E-Business Suite JG (Regional Localizations) product, owned by the AP schema. It stores EFT (Electronic Funds Transfer) payment format definitions used by regional localization extensions to drive outbound electronic payment file generation. In EBS 12.1.1 and 12.2.2 the table functions as the header-level repository that maps a given country code and EFT payment type to the format and system information required to construct a valid bank transmission file.

The table appears in the ETRM 12.2.2 documented physical schema with 39 columns and is defined in both releases under the same AP ownership. It is a multilingual-enabled entity, paired with a translation table (JG_ZZ_SYS_FORMATS_ALL_TL) that supplies language-specific descriptive text. From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification: the composite key (JGZZ_COUNTRY_CODE, JGZZ_EFT_TYPE) forms the natural business key, with descriptive attributes carried in the same structure rather than a separate satellite.

Key Information Stored

The primary key is JG_SYS_FORMATS_ALL_B_PK, defined on the composite of JGZZ_COUNTRY_CODE and JGZZ_EFT_TYPE. A unique index, JG_ZZ_SYS_FORMATS_ALL_B_U1, extends this to include ORG_ID, indicating that format definitions are partitioned by operating unit — a critical consideration for multi-org deployments where different legal entities in the same country may use distinct EFT format configurations.

The most significant columns are:

• JGZZ_COUNTRY_CODE — the ISO-style country identifier for which the EFT format applies.
• JGZZ_EFT_TYPE — the payment mechanism/format type (for example, a specific bank clearing scheme) valid for that country.
• ORG_ID — the operating unit context, enabling org-specific format resolution.
• JGZZ_ATTRIBUTE_CATEGORY — the descriptive flexfield context, allowing extensible format attributes to be defined and validated.
• JGZZ_SYSTEM_INFO1 through JGZZ_SYSTEM_INFO30 — a thirty-column block of localization-specific system parameters holding the positional, layout, and control values that the EFT file writer reads when rendering payment instructions.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• CREATED_BY, CREATION_DATE — creation audit columns.

Together these columns define the format header; the detailed record layout is largely expressed through the SYSTEM_INFO block rather than via normalized child tables.

Common Use Cases and Queries

The most frequent access pattern is resolution of the correct format for a payment run. A typical query filters on country, EFT type, and operating unit:

• SELECT * FROM ap.jg_zz_sys_formats_all_b WHERE jgzz_country_code = :p_country AND jgzz_eft_type = :p_eft_type AND org_id = :p_org_id;
• Joining to the translation table to obtain a user-facing description: SELECT b.jgzz_country_code, b.jgzz_eft_type, t.jgzz_format_name FROM ap.jg_zz_sys_formats_all_b b, ap.jg_zz_sys_formats_all_tl t WHERE b.jgzz_country_code = t.jgzz_country_code AND b.jgzz_eft_type = t.jgzz_eft_type AND t.language = USERENV('LANG');
• Reporting the full inventory of configured formats per operating unit for a localization rollout: SELECT org_id, jgzz_country_code, jgzz_eft_type FROM ap.jg_zz_sys_formats_all_b ORDER BY org_id, jgzz_country_code;
• Diagnostic queries that inspect the SYSTEM_INFO columns to verify layout configuration after a patch or localization upgrade.

Related Objects

The principal dependent object is JG_ZZ_SYS_FORMATS_ALL_TL, the translation table. The documented FK relationship is:

• JG_ZZ_SYS_FORMATS_ALL_TL.JGZZ_COUNTRY_CODE and JGZZ_EFT_TYPE reference the parent JG_ZZ_SYS_FORMATS_ALL_B. Sorting through the relationship metadata supplied here, this is the only table documented as referencing the parent through a formal foreign key.

Because the parent table is consumed by the JG localization formatter rather than exposed through a public PL/SQL API, dependencies on it are primarily through the EFT payment file generation programs and the localization setup forms that maintain format rows. Administrators should treat the table as configuration data, maintain format definitions through the JG setup UI, and avoid direct DML, as the SYSTEM_INFO columns are interpreted positionally by the formatter and are sensitive to structural change.