Results for “ship_to_segment_id”

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

Overview

JL_ZZ_AR_TX_LGL_MSG_V is a VALID view owned by the APPS schema within the JL – Latin America Localizations product. It exposes the legal tax message configuration used by the Latin American ETRM (Electronic Tax Reporting) engine, joining fiscal classification rules, legal messages, and standard text messages into a single queryable structure. The view is primarily consumed by tax reporting logic and inquiry screens that need to determine which legal message, fiscal classification code, and inventory organization apply to a given exception condition during tax calculation. Because the view is defined with a UNION of multiple SELECT statements, it consolidates message definitions originating from more than one rule context (fiscal classification rules and item-based rules) into a uniform column layout.

The view is significant in a multi-org context because it carries ORG_ID and applies NVL-based org filtering against each joined source, ensuring that legal messages are matched only to rules and fiscal classifications in the same operating unit (or to records with a null ORG_ID).

Underlying Base Objects

The documented referenced objects include AR_MEMO_LINES, AR_STANDARD_TEXT_VL, AR_SYSTEM_PARAMETERS_ALL, HR_GENERAL, HR_ORGANIZATION_UNITS, HR_SECURITY, HZ_CUST_ACCOUNTS, HZ_GEOGRAPHIES, HZ_PARTIES, JL_ZZ_AR_TX_EXC_FSC_ALL, JL_ZZ_AR_TX_EXC_ITM_ALL, JL_ZZ_AR_TX_FSC_CLS_ALL, JL_ZZ_AR_TX_LGL_MSG, JL_ZZ_AR_TX_LIB_PKG, JL_ZZ_AR_TX_LOCN_ALL, JL_ZZ_AR_TX_RULES_ALL, MO_GLOBAL, and MTL_SYSTEM_ITEMS_B.

The visible SELECT text shows the first branch joining JL_ZZ_AR_TX_RULES_ALL (rule header), JL_ZZ_AR_TX_LGL_MSG (message mapping), JL_ZZ_AR_TX_FSC_CLS_ALL (fiscal classification), and AR_STANDARD_TEXT_VL (message text). The join conditions restrict rules to RULE = 'GET_FISC_CLAS_TX_CODE', active fiscal classifications (ENABLED_FLAG = 'Y'), and enforce ORG_ID consistency through NVL(M1.ORG_ID,-99) = NVL(R1.ORG_ID,-99) and NVL(M1.ORG_ID,-99) = NVL(FC.ORG_ID,-99). The message text itself is resolved via JL_ZZ_AR_TX_LIB_PKG.GET_LOOKUP_MEANING for the exception code and fiscal classification code lookups. Additional referenced objects such as HR_ORGANIZATION_UNITS and MTL_SYSTEM_ITEMS_B support organization and item descriptions used in the union's other branches.

Key Columns

• ROW_ID – the ROWID of the underlying JL_ZZ_AR_TX_LGL_MSG record.
• RULE_ID / RULE_DATA_ID – identifier of the rule and its associated fiscal class or location, linking the message to its applicability context.
• EXCEPTION_CODE / EXCEPTION_DESC – the exception lookup code and its translated meaning.
• FISCAL_CLASSIFICATION_CODE – the fiscal classification applied to the transaction, with its lookup meaning exposed alongside.
• INVENTORY_ITEM_ID / ITEM_NAME / INVENTORY_ITEM_FLAG / INVENTORY_ORGANIZATION_ID – item-level context for message applicability.
• MESSAGE_ID / TEXT – the standard text message identifier and its full text.
• ORG_ID – the operating unit identifier used for multi-org filtering.
• START_DATE_ACTIVE / END_DATE_ACTIVE / MSG_EFFECTIVE_DATE / MSG_END_DATE_ACTIVE – date-ranged validity of the rule and message.
• Standard WHO columns: LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage includes validating which legal message will be printed for a given fiscal classification and exception, and building reports for tax message maintenance. Given the user's interest in ORG_ID, queries should either rely on MO_GLOBAL initialization or filter explicitly.

• Retrieve all messages for an operating unit: SELECT rule_id, exception_code, fiscal_classification_code, text FROM jl_zz_ar_tx_lgl_msg_v WHERE org_id = :p_org_id;
• Find messages by exception: SELECT * FROM jl_zz_ar_tx_lgl_msg_v WHERE exception_code = :p_exception AND org_id = :p_org_id;
• Inspect item-specific messages: SELECT inventory_organization_id, inventory_item_id, item_name, text FROM jl_zz_ar_tx_lgl_msg_v WHERE inventory_item_flag = 'Y' AND org_id = :p_org_id;
• Check effective-dated messages: SELECT rule_id, text, msg_effective_date, msg_end_date_active FROM jl_zz_ar_tx_lgl_msg_v WHERE SYSDATE BETWEEN msg_effective_date AND NVL(msg_end_date_active, SYSDATE+1);

Because the view enforces org consistency through NVL comparisons, records with a null ORG_ID are matched to rules with a null ORG_ID, making the view suitable for both operating-unit-specific and global tax message configurations.