Search Results product_rule_desc

Overview

The APPS.XLA_ACCTG_METHOD_RULES_FVL view is a subledger accounting (XLA) reference object that presents accounting method rules in a fully translated, user-friendly form. It is the "formal/lookup view" companion to the base transactional table XLA_ACCTG_METHOD_RULES, resolving internal code values, application identifiers, and context codes into their displayable meanings. In Oracle EBS 12.1.1 and 12.2.2, this view is primarily used for reporting, seeded page definitions, and integration lookups rather than for transactional processing. Because it exposes the translated PRODUCT_RULE_TYPE_DSP and PRODUCT_RULE_NAME, it is the recommended object for any query, extract, or interface that must present accounting method rule configuration to end users or downstream systems. Notably, the column PRODUCT_RULE_TYPE_DSP — the value for which the user searched — originates here, derived from the XLA_LOOKUPS lookup type XLA_OWNER_TYPE.

Underlying Base Objects

The view is defined over four documented, APPS-owned objects:

• XLA_ACCTG_METHOD_RULES (synonym to the base table) — the driving table holding each accounting method rule, keyed by ACCTG_METHOD_RULE_ID.
• XLA_PRODUCT_RULES_TL (synonym) — the translated product rule table, supplying NAME and DESCRIPTION for the rule's language-specific text.
• XLA_LOOKUPS (view) — used twice: once as K to resolve PRODUCT_RULE_TYPE_CODE against lookup type XLA_OWNER_TYPE into PRODUCT_RULE_TYPE_DSP, and once as K1 to resolve AMB_CONTEXT_CODE against lookup type XLA_AMB_CONTEXT_TYPE into AMB_CONTEXT_NAME.
• XLA_APPLICATIONS_XVL (view) — supplies the human-readable APPLICATION_NAME for the owning application.

Joins are performed on APPLICATION_ID, AMB_CONTEXT_CODE, PRODUCT_RULE_TYPE_CODE, and PRODUCT_RULE_CODE, with translation filtered by L.LANGUAGE = USERENV('LANG'). The ROW_ID pseudo-column provides a unique row identifier for the driving table record.

Key Columns

• ROW_ID / ACCTG_METHOD_RULE_ID — unique row and primary key of the accounting method rule.
• ACCOUNTING_METHOD_TYPE_CODE / ACCOUNTING_METHOD_CODE — the accounting method context to which the rule belongs.
• APPLICATION_ID / APPLICATION_NAME — owning subledger application and its display name.
• AMB_CONTEXT_CODE / AMB_CONTEXT_NAME — the accounting methods builder context and its translated meaning.
• PRODUCT_RULE_CODE / PRODUCT_RULE_NAME / PRODUCT_RULE_DESC — the product rule identifier and its translated name/description.
• PRODUCT_RULE_TYPE_CODE / PRODUCT_RULE_TYPE_DSP — the product rule type code and the corresponding display value drawn from lookup XLA_OWNER_TYPE (the requested product_rule_type_dsp).
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective date range for the rule.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include reporting active accounting method rules per application, extracting rule configuration with display values for integrations, and validating rule setup during implementation or reconciliation. The following query lists active rules with translated owner-type display.

• Filter active rules: WHERE TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE)
• Filter by application or context using APPLICATION_ID / AMB_CONTEXT_CODE.
• Group by PRODUCT_RULE_TYPE_DSP to summarize rule types.

Sample SQL:

SELECT application_name, amb_context_name, product_rule_code,
product_rule_name, product_rule_type_dsp, start_date_active, end_date_active
FROM apps.xla_acctg_method_rules_fvl
WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE)
ORDER BY application_name, amb_context_name, product_rule_name;