Search Results jg_zz_ta_rule_sets_u2

Overview

GL.JG_ZZ_TA_RULE_SETS is a transaction-accounting rule set definition table owned by the GL schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is registered in FND Design Data as JG.JG_ZZ_TA_RULE_SETS, though the physical object resides in the GL schema within the APPS_TS_TX_DATA tablespace. The object is documented as VALID. Its purpose is to store named groupings of transaction-accounting rules, scoped to a specific chart of accounts, that govern how accounting flexfield combinations are derived or upgraded during the transition from the pre-11i accounting model to the Release 12 subledger accounting architecture. The JG_ZZ_TA_RULE_SETS# entry in the dependency list indicates the table participates in an editioning view arrangement typical of 12.2.x online patching, and the table is not referenced by any other database object.

From a heuristic Data Vault modeling perspective, JG_ZZ_TA_RULE_SETS classifies as a standalone object. No foreign keys are declared on the table itself, and no documented child tables reference it, so it does not naturally resolve into a hub, link, or satellite pattern. A modeler treating it as a hub would need to synthesize relationships with the rule detail tables that logically consume RULE_SET_ID.

Key Information Stored

Each row describes one rule set. The most significant columns are:

• RULE_SET_ID — the numeric surrogate primary key and the column indexed by the unique index JG_ZZ_TA_RULE_SETS_U1.
• CHART_OF_ACCOUNTS_ID — identifies the chart of accounts to which the rule set belongs.
• NAME — the user-facing rule set name, limited to 100 characters.
• PARTIAL_ALLOCATION — a flag indicating whether partial allocation behavior applies to the rule set.
• ENABLED_FLAG — controls whether the rule set is active for use.
• ACCOUNT_TYPE — the account type classification the rule set targets.

The business key is defined by the unique index JG_ZZ_TA_RULE_SETS_U2 on the composite of CHART_OF_ACCOUNTS_ID and NAME, meaning a rule set name must be unique within a chart of accounts. Standard EBS audit columns are present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The table also includes CONTEXT and fifteen ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns, all VARCHAR2(150), available for client-specific extensions.

Common Use Cases and Queries

Typical use cases center on validating rule set configuration before running the transaction-accounting upgrade, and on reporting which rule sets are active for a given chart of accounts. A representative query filtering active rule sets is:

SELECT RULE_SET_ID, NAME, ACCOUNT_TYPE, ENABLED_FLAG FROM GL.JG_ZZ_TA_RULE_SETS WHERE ENABLED_FLAG = 'Y' AND CHART_OF_ACCOUNTS_ID = :coa_id;

Reporting queries should join CHART_OF_ACCOUNTS_ID to the chart of accounts definition and use NAME as the display key, since RULE_SET_ID is an internal surrogate with no business meaning. When investigating duplicate names, the composite uniqueness enforced by U2 explains any insert failures encountered during setup data migration.

Related Objects

The documented dependency data is sparse for this object; it references no database object directly and is not referenced by any named table. One relationship is recorded through the column-level mapping:

• GL.JG_MGT_SEG_UPGRADE_H — referenced through CHART_OF_ACCOUNTS_ID, linking the rule set to management segment upgrade history.
• GL.JG_ZZ_TA_RULE_SETS# — the editioning backing object in Release 12.2.x, relevant when tracing online patching behavior.
• Rule detail tables that consume RULE_SET_ID as a parent key are logical dependents; they are not enumerated in the supplied metadata and should be confirmed against the live data dictionary before use.