Search Results accounting_class_name




Overview
Explore in AI Chat

Overview

XLA_PAD_INQ_LINES_AF_SD_FVL is an APPS-owned database view within the Oracle E-Business Suite Subledger Accounting (XLA) module. It is a composite inquiry view that consolidates accounting line definition data used by the Subledger Accounting "Product Accounting Definition" (PAD) inquiry pages. The view exposes configuration metadata describing how subledger transactions are transformed into accounting entries, including product rules, event classes and types, accounting line definitions, accounting classes, and segment rules. In EBS 12.1.1 and 12.2.2, this object is marked VALID in the APPS schema and is designed primarily for read-only reporting and integration use, allowing technical consultants and developers to interrogate subledger accounting configuration without navigating the standard forms. Its naming convention — PAD (Product Accounting Definition) plus INQ (Inquiry) plus the AF/SD suffix — reflects that it serves the seeded inquiry infrastructure and combines multiple underlying line-definition views through a UNION.

Underlying Base Objects

The documented metadata identifies two referenced base objects: XLA_PAD_INQ_LINES_AF_FVL and XLA_PAD_INQ_LINES_SD_FVL, both themselves views. The view is defined as a UNION of the two, meaning it returns the combined result set of the "AF" (Application/After-Flexfield, or seeded application definition) lines and the "SD" (Subledger Definition, or user-defined) lines. Because both branches project an identical column list — beginning with ROW_ID, APPLICATION_ID, AMB_CONTEXT_CODE, and PRODUCT_RULE_CODE, and continuing through the accounting line and flexfield attributes — the UNION produces a vertically stacked, homogeneous dataset. This design lets the inquiry layer present both Oracle-seeded and customer-defined accounting line definitions in a single queryable structure, with the AMB_CONTEXT_CODE and LINE_DEFINITION_OWNER_CODE columns effectively distinguishing the source population.

Key Columns

The view projects a broad set of configuration attributes. Identity and context columns include ROW_ID, APPLICATION_ID, and AMB_CONTEXT_CODE. Product rule columns include PRODUCT_RULE_CODE, PRODUCT_RULE_NAME, PRODUCT_RULE_TYPE_CODE, and its display variant PRODUCT_RULE_TYPE_CODE_DSP. Event information is exposed through EVENT_CLASS_CODE, EVENT_CLASS_NAME, EVENT_TYPE_CODE, and EVENT_TYPE_NAME. Accounting line definition columns include ACCOUNTING_LINE_CODE, ACCOUNTING_LINE_NAME, ACCOUNTING_LINE_TYPE_CODE, ACCOUNTING_LINE_TYPE_CODE_DSP, ACCOUNTING_ENTRY_TYPE_CODE, ACCOUNTING_ENTRY_TYPE_DSP, ACCOUNTING_LINE_SIDE_CODE, and ACCOUNTING_LINE_SIDE_DSP. Notably, ACCOUNTING_CLASS_CODE and ACCOUNTING_CLASS_NAME are exposed here — the columns most relevant to a search for "accounting_class_name" — classifying each line into its accounting class (for example, asset, liability, revenue, or expense). Further columns cover SWITCH_SIDE_FLAG, MERGE_DUPLICATE_CODE, DESCRIPTION_CODE/NAME/TYPE_CODE, ANALYTICAL_CRITERION_CODE/TYPE_CODE, SEGMENT_RULE_CODE/NAME/TYPE_CODE, FLEXFIELD_ASSIGN_MODE, ACCOUNTING_COA_ID/NAME, FLEXFIELD_SEGMENT_CODE/NAME, and standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY). The _DSP suffixed columns carry translated or display-ready values.

Common Use Cases and Queries

Typical uses include auditing which accounting class a subledger line definition maps to, tracing a product rule to its event class and accounting lines, and building custom reports or integration extracts of subledger accounting configuration. Because ACCOUNTING_CLASS_NAME is a projected column, it is commonly filtered or grouped directly.

  • Locate lines by accounting class: 
    SELECT application_id, product_rule_name, accounting_line_name,
       accounting_class_name
FROM   apps.xla_pad_inq_lines_af_sd_fvl
WHERE  accounting_class_name = 'Revenue';
  • Inspect all definitions for an application: 
    SELECT event_class_name, event_type_name,
       accounting_line_code, accounting_line_side_dsp
FROM   apps.xla_pad_inq_lines_af_sd_fvl
WHERE  application_id = 222;
  • Distinguish seeded versus user-defined lines: 
    SELECT line_definition_owner_code, COUNT(*)
FROM   apps.xla_pad_inq_lines_af_sd_fvl
GROUP  BY line_definition_owner_code;

Consultants should query the view with the APPS schema or appropriate synonym and treat results as read-only configuration reference data.