Results for “msg_end_date_active”

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

Overview

The view APPS.JL_ZZ_AR_TX_LGL_MSG_V is a reporting and integration object delivered as part of the Oracle E-Business Suite localizations for Latin America (JL_ZZ_AR_TX schema components), specifically oriented toward the Argentine tax legal message and fiscal classification model used in Oracle Receivables transaction processing. The view consolidates the relationship between tax rules, legal messages, fiscal classifications, and the associated text that is printed or transmitted on legally required fiscal documents such as invoices, credit notes, and debit notes.

The name reflects its function: legal message (LGL_MSG) resolution for Argentina (AR) tax (TX) processing. Its principal role is to expose, in a single denormalized row set, the fiscal classification code, the exception code, the standard text message that must accompany the transaction, and the effective dating that governs both the message and its fiscal classification. The view is critical when a user investigates the rule identified by the literal 'GET_FISC_CLAS_TX_CODE', which is the rule name embedded in the view's defining WHERE clause to drive retrieval of the correct fiscal classification transaction code.

Underlying Base Objects

The view is defined over four principal objects joined in a UNION ALL construction, complemented by a library package used for lookup meaning resolution. The core join in the first branch is:

• JL_ZZ_AR_TX_RULES_ALL — the rule definitions; filtered by r1.rule = 'GET_FISC_CLAS_TX_CODE'.
• JL_ZZ_AR_TX_LGL_MSG — the legal message assignments keyed by rule_id and message_id.
• JL_ZZ_AR_TX_FSC_CLS_ALL — the fiscal classification master, restricted to enabled_flag = 'Y'.
• AR_STANDARD_TEXT_VL — the standard text that supplies the actual message body (st1.text), along with the standard_text_id.

A second UNION branch chains the same message/rule objects to location-based data, referencing JL_ZZ_AR_TX_LOCN_ALL, HZ_GEOGRAPHIES, and related geographies. Supporting objects referenced in the metadata include JL_ZZ_AR_TX_EXC_FSC_ALL, JL_ZZ_AR_TX_EXC_ITM_ALL, MTL_SYSTEM_ITEMS_B, HR_ORGANIZATION_UNITS, HR_GENERAL, HR_SECURITY, HZ_CUST_ACCOUNTS, HZ_PARTIES, AR_MEMO_LINES, AR_SYSTEM_PARAMETERS_ALL, and the MO_GLOBAL package for multi-org context. All lookups via JL_ZZ_AR_TX_LIB_PKG.get_lookup_meaning resolve the exception code against the JLZZ_AR_TX_LEGAL_MESSAGE lookup type and the fiscal classification against JLZZ_AR_TX_FISCAL_CLASS_CODE.

Key Columns

• rule_id, rule_data_id — identifiers linking the rule to its driving fiscal classification.
• exception_code / exception_desc — the legal message exception, resolved to its 80-character meaning.
• fiscal_classification_code / fiscal_classification_desc — the fiscal class code and its translated meaning, null in the location branch of the UNION.
• message_id, text — the standard text identifier and the printable legal message.
• start_date_active, end_date_active, msg_effective_date, msg_end_date_active — effective dating for the classification and the message.
• org_id, last_updated_by, last_update_date, creation_date, created_by — multi-org and audit attributes.
• Location columns (ship_from_code, ship_to_code, customer_id, inventory_item_id) — populated only in the geography-driven branch of the UNION.

Common Use Cases and Queries

Typical usage retrieves the legal message text and fiscal classification description for a given rule and organization. For example:

SELECT rule_id, exception_desc, fiscal_classification_code, fiscal_classification_desc, text, msg_effective_date FROM apps.jl_zz_ar_tx_lgl_msg_v WHERE org_id = :p_org_id AND fiscal_classification_code IS NOT NULL;

Another frequent pattern validates that every enabled fiscal classification has an assigned legal message for the GET_FISC_CLAS_TX_CODE rule, supporting compliance audits and localization configuration verification prior to period close.