Results for “rule_data_id”

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

Overview

The JL.JL_ZZ_AR_TX_LGL_MSG_ALL table is a Latin America Localizations (JL) data object that stores legal message assignments for Latin American tax reporting. Within Oracle EBS 12.1.1 and 12.2.2, it functions as an intersection between tax rule configuration and the standard text messages displayed on printed invoices and legal tax documents. Each row associates a specific tax rule, rule data value, and optional exception condition with a standard text message that carries legal or fiscal significance for the localization country.

The ALL suffix indicates the table is partitioned or org-striped by operating unit through the ORG_ID column, consistent with multi-org access control. From a modeling perspective, the FK structure — a single foreign key to AR_STANDARD_TEXT_B for message content plus a business-key unique index — suggests the table leans toward a satellite classification, capturing descriptive message-assignment attributes that depend on a parent rule identity rather than acting as an independent hub or a pure link between two hubs.

Key Information Stored

The table is documented with 14 columns. Key columns include:

• MESSAGE_ID — foreign key to AR_STANDARD_TEXT_B, identifying the legal message text to be applied.
• RULE_ID, RULE_DATA_ID, EXCEPTION_CODE, and ORG_ID — together these constitute the unique index JL_ZZ_AR_TX_LGL_MSG_U1, the business-key candidate that guarantees one message assignment per rule, rule data value, exception, and operating unit.
• INVENTORY_ITEM_FLAG and INVENTORY_ORGANIZATION_ID — indicate whether the legal message is scoped to an inventory item and, if so, which inventory organization.
• START_DATE_ACTIVE and END_DATE_ACTIVE — define the effective date range during which the message assignment is valid.
• ORG_ID — multi-org operating unit discriminator.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Who columns for audit tracking.

Common Use Cases and Queries

Typical usage centers on resolving which legal text should print on a tax document given a rule and item context. A representative join resolves the message body through the standard text table:

• Report the legal message text active for a given rule: SELECT m.RULE_ID, m.MESSAGE_ID, t.TEXT FROM JL_ZZ_AR_TX_LGL_MSG_ALL m, AR_STANDARD_TEXT_B t WHERE m.MESSAGE_ID = t.STANDARD_TEXT_ID AND TRUNC(SYSDATE) BETWEEN m.START_DATE_ACTIVE AND NVL(m.END_DATE_ACTIVE, SYSDATE);
• Filter by operating unit: add AND m.ORG_ID = :org_id.
• Item-specific message lookup: filter on INVENTORY_ITEM_FLAG = 'Y' and INVENTORY_ORGANIZATION_ID.
• Configuration audit: list assignments by RULE_ID and EXCEPTION_CODE to verify coverage against legal requirements.
• Validity reporting: identify assignments with expired END_DATE_ACTIVE to flag stale configuration.

These queries support localization compliance teams verifying that every taxable scenario maps to a legally required message.

Related Objects

• AR_STANDARD_TEXT_B — primary FK target via JL_ZZ_AR_TX_LGL_MSG_ALL.MESSAGE_ID = AR_STANDARD_TEXT_B.STANDARD_TEXT_ID; supplies the base message text.
• AR_STANDARD_TEXT_TL — translation table providing language-specific message content for the base text.
• JL_ZZ_AR_TX_RULES_ALL — parent tax rule definition referenced conceptually through RULE_ID.
• JL_ZZ_AR_TX_RULE_DATA_ALL — rule data values referenced through RULE_DATA_ID.
• JL_ZZ_AR_TX_EXCEPTIONS_ALL — exception definitions referenced through EXCEPTION_CODE.
• HR_OPERATING_UNITS / FND_ORG_ACCESS — resolve ORG_ID and enforce multi-org security.
• MTL_SYSTEM_ITEMS_B / MTL_PARAMETERS — context for INVENTORY_ITEM_FLAG and inventory organization scoping.