Search Results invoicing_credit_method_code




Overview
Explore in AI Chat

Overview

APPS.ASO_I_LINE_TYPES_V is a public Oracle E-Business Suite view owned by the APPS schema that exposes line type definitions used by the Order Management and Order Capture (ASO) modules. In the EBS 12.1.1 and 12.2.2 data models, this view is a thin projection over the underlying OE_LINE_TYPES_V view, presenting a stable, integration-friendly interface that surfaces the attributes required to classify order lines, drive fulfillment defaults, and determine downstream invoicing and accounting behavior. Because it is a view rather than a base table, it inherits the row-level security and org context applied by the Order Management layer while offering a logical column set curated for ASO consumers. Within the ETRM 12.2.2 metadata, the view is documented as being defined directly over one referenced base object, OE_LINE_TYPES_V.

Underlying Base Objects

The documented metadata lists a single referenced base object: OE_LINE_TYPES_V (VIEW). APPS.ASO_I_LINE_TYPES_V therefore does not select from base tables directly; instead it delegates all column derivation and join logic to OE_LINE_TYPES_V, which in turn resolves the transactional line type records in the Order Management schema. This single-layer indirection is significant for support and performance analysis: any change to OE_LINE_TYPES_V—such as an added column, a modified join, or a change in the org-filtering predicate—propagates immediately to ASO_I_LINE_TYPES_V. The view carries no independent WHERE clause, filter, or aggregation in the documented definition; column list and ordering are preserved exactly as exposed by the base view, including the ORG_ID column that anchors multi-org visibility.

Key Columns

Common Use Cases and Queries

The view is typically queried during order import validation, pricing and invoicing default derivation, and integration extracts where the called interface requires line type attributes. A representative lookup by name is:

SELECT line_type_id, name, transaction_type_code,
       invoicing_rule_id, invoicing_credit_method_code,
       accounting_rule_id, accounting_credit_method_code, org_id
  FROM apps.aso_i_line_types_v
 WHERE org_id = :p_org_id
   AND start_date_active <= SYSDATE
   AND (end_date_active IS NULL OR end_date_active >= SYSDATE);

A second common pattern joins the view to order or invoice interfaces to resolve defaults by line type:

SELECT o.line_type_id, v.name,
       v.cust_trx_type_id, v.invoicing_credit_method_code
  FROM apps.aso_i_line_types_v v, oe_order_lines_all o
 WHERE o.line_type_id = v.line_type_id
   AND o.org_id = v.org_id;

Because the view is read-only and effective-dated, reports should always filter on START_DATE_ACTIVE and END_DATE_ACTIVE and qualify by ORG_ID to respect the operating unit boundary. For performance and support purposes, it should be treated as a synonym for OE_LINE_TYPES_V, and any tuning or issue diagnosis should be performed against that underlying Order Management view.