Search Results accounting_line_name




Overview
Explore in AI Chat

Overview

APPS.XLA_PAD_INQ_LINES_AF_SD_FVL is a Subledger Accounting (SLA) inquiry view shipped with Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its name encodes its function: XLA is the Subledger Accounting schema prefix, PAD denotes the Product Accounting Definition / application accounting definition inquiry family, INQ_LINES indicates it exposes accounting rule line definitions, and the AF_SD suffix reflects that the view aggregates the "Application First" and "Standard" flexfield variants. The trailing _FVL indicates a flexfield value view constructed for inquiry and reporting purposes.

The view presents the metadata that defines how accounting lines are generated from subledger transactions. Each row describes a line definition within a product rule: the application, the accounting method context, the event class and event type, the accounting line code and name, the entry type, the accounting class, the debit/credit side, and the associated analytical criteria, description rules, and segment rules. It is primarily consumed by the Create Accounting and accounting program setup inquiry forms and by reporting and integration routines that need to enumerate accounting line definitions without navigating the underlying normalized SLA tables. The accounting_line_name column, which matches the user's search term, is the descriptive label of the accounting line definition.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, the view is defined as a UNION of two underlying views:

  • XLA_PAD_INQ_LINES_AF_FVL — the "Application First" variant of the accounting line inquiry view, exposing product rule and accounting line definitions as stored against the application accounting definition.
  • XLA_PAD_INQ_LINES_SD_FVL — the "Standard" (default/seeded) variant of the same inquiry view.

The UNION of these two sources produces a consolidated, deduplicated result set in which both application-specific and standard line definitions are visible through a single query point. Both branches project identical column lists, which guarantees union compatibility. The row_id column is included in each branch, allowing the unioned rows to be uniquely identified and located in the originating view.

Key Columns

The view exposes a comprehensive set of descriptive and coded columns. Principal among them are:

  • row_id — unique row identifier for the unioned record.
  • application_id — the subledger application (e.g., Payables, Receivables, Assets) owning the accounting definition.
  • amb_context_code — the Accounting Methods Builder context.
  • product_rule_code / product_rule_name / product_rule_type_code — the product rule to which the line belongs.
  • line_definition_owner_code / line_definition_code / locking_status_flag — ownership and lock state of the line definition.
  • event_class_code / event_class_name / event_type_code / event_type_name — the event class and event type that trigger line creation.
  • accounting_line_code / accounting_line_name / accounting_line_type_code — the accounting line identifier, its user-facing accounting_line_name, and its type classification.
  • accounting_entry_type_code / accounting_class_code / accounting_line_side_code — the entry type, accounting class, and debit/credit side (with switch_side_flag and merge_duplicate_code for generation control).
  • description_code / description_name, analytical_criterion_code, and segment_rule_code / segment_rule_name — the description rule, analytical criteria, and segment (accounting flexfield) mapping rules attached to the line.
  • accounting_coa_id / accounting_coa_name, flexfield_segment_code / flexfield_segment_name, flexfield_assign_mode — the chart of accounts and segment-level flexfield mapping context.
  • Standard WHO columns (creation_date, created_by, last_update_date, last_update_login, last_updated_by).

Common Use Cases and Queries

Typical use cases include locating an accounting line definition by its descriptive name, auditing which product rules and event types reference a given accounting line, and extracting setup metadata for documentation or migration analysis.

To find a line definition by name:

  • SELECT application_id, product_rule_name, event_class_name, event_type_name, accounting_line_code, accounting_line_name, accounting_line_side_code FROM apps.xla_pad_inq_lines_af_sd_fvl WHERE accounting_line_name LIKE '%Payables%';

To enumerate lines for a specific product rule and event type:

  • SELECT accounting_line_code, accounting_line_name, accounting_entry_type_code, accounting_class_code FROM apps.xla_pad_inq_lines_af_sd_fvl WHERE product_rule_code = :product_rule AND event_type_code = :event_type ORDER BY accounting_line_code;

To inspect segment and analytical criteria mapping for a line:

  • SELECT accounting_line_name, segment_rule_name, analytical_criterion_code, flexfield_segment_name FROM apps.xla_pad_inq_lines_af_sd_fvl WHERE accounting_line_code = :line_code AND application_id = :app_id;

Because the view is a union of the Application First and Standard variants, queries should filter by application_id and product_rule_code to avoid returning both variants when only one is relevant. Access is granted to the APPS schema, and standard EBS security applies.