Results for “jl_zz_ar_tx_lmsg_create_v”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view JL_ZZ_AR_TX_LMSG_CREATE_V belongs to the Oracle EBS Latin America Localizations (JL) module, specifically the Brazilian and broader LatAm tax reporting enhancements layered on Oracle Receivables. It is a reporting and integration construct that surfaces legal messages, fiscal classifications, and exception descriptions associated with Receivables tax rules. Its purpose is to expose the configuration data needed to generate statutory tax messages that accompany fiscal documents, allowing external reporting processes, localization reports, or downstream interfaces to retrieve the appropriate message text and classification metadata for a given tax rule.
Importantly, the ETRM metadata records this object as Not implemented in this database in the reference instance. This is a configuration-dependent status: the view is shipped as part of the JL localization schema, but it exists only where the relevant LatAm tax localization patches have been applied and the supporting tables have been created. Its appearance is therefore tied to specific country localizations rather than to a base EBS installation.
Underlying Base Objects
The view is defined over a UNION of queries built from the following documented base objects:
JL_ZZ_AR_TX_RULES— the rule definitions driving tax message generation. AliasedR1and filtered toRULE = 'GET_FISC_CLAS_TX_CODE'.JL_ZZ_AR_TX_LGL_MSG— legal message assignments, aliasedM1, joined onRULE_ID.JL_ZZ_AR_TX_FSC_CLS— fiscal classification records, aliasedFC, restricted toENABLED_FLAG = 'Y'.AR_STANDARD_TEXT— the message text source, aliasedST1, joined viaMESSAGE_ID = STANDARD_TEXT_ID.FND_LOOKUPS— joined twice, once asLKPfor the fiscal classification code meaning (JLZZ_AR_TX_FISCAL_CLASS_CODE) and once asLKP_EXfor the exception description (JLZZ_AR_TX_LEGAL_MESSAGES).
The join conditions enforce active/dated lookup values through SYSDATE BETWEEN NVL(START_DATE_ACTIVE...) AND NVL(END_DATE_ACTIVE...), ensuring only currently effective classifications and messages are returned. A UNION combines parallel rule branches that share the same output shape.
Key Columns
RULE_ID/RULE_DATA_ID— identify the tax rule and its associated data record.EXCEPTION_CODE/EXCEPTION_DESC— the exception condition and its lookup meaning.FISCAL_CLASSIFICATION_CODE/FISCAL_CLASSIFICATION_DESC— statutory classification and description.SHIP_FROM_CODE/SHIP_FROM_DESC— explicitly cast asTO_CHAR(NULL)in the documented query, so these columns are placeholders that resolve to NULL in this branch.SHIP_TO_CODE,ITEM_NAME,CUSTOMER_NAME,ORG_NAME— similarly NULL placeholders in the documented branch, populated by other UNION members.MESSAGE_ID,TEXT— the standard text message identifier and content.START_DATE_ACTIVE,END_DATE_ACTIVE,MSG_EFFECTIVE_DATE,MSG_END_DATE_ACTIVE— date-range validity.- WHO columns (
CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE).
The user search term "ship_from_code" maps directly to the SHIP_FROM_CODE column. Because it is defined as TO_CHAR(NULL) in the documented query text, callers filtering on ship-from values will receive no data from that branch; the value is intended to be supplied by other UNION legs of the view.
Common Use Cases and Queries
Typical usage centers on retrieving the legal message text and fiscal classification for tax rule output. A representative query is:
SELECT rule_id, fiscal_classification_code, exception_desc, text FROM jl_zz_ar_tx_lmsg_create_v WHERE fiscal_classification_code = :code;- Filtering by ship-from origin:
SELECT ship_from_code, message_id, text FROM jl_zz_ar_tx_lmsg_create_v WHERE ship_from_code = :ship_from;— noting the NULL placeholder caveat. - Validity-windowed extraction joining effective dates for a reporting period.
Because the view aggregates lookup meanings, standard text, and fiscal classification in a single denormalized result set, it is suited to localization report generation and interface extraction rather than transactional processing.
-
Not implemented in this database·Explore JL module →
-
Not implemented in this database·Explore JL module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2