Search Results acct_rule




Overview
Explore in AI Chat

Overview

APPS.OEFV_SALES_ORDER_TYPES is a reporting and forms-support view in Oracle E-Business Suite that exposes the configuration of Order Management sales order (transaction) types alongside their descriptive and translated attributes. It is defined over OE_TRANSACTION_TYPES_ALL and its translation table OE_TRANSACTION_TYPES_TL, and it enriches those records with lookups, currencies, price lists, warehouses, invoicing rules and accounting rules. In the ETRM reference model it is classified under the Order Management transaction type family and is used both by concurrent reporting and by the Order Management setup forms that render descriptive flexfields and value-set driven fields using the special _LA, _DF and _KF tagged pseudo-columns.

Because the view is owned by APPS and the base objects are consumed through synonyms, it is queried by Oracle Application Object Library, Order Management, Receivables and general ledger reporting components, and it is frequently used as a source for integration extracts that require order type attributes in a decoder-friendly form.

Underlying Base Objects

The documented base objects, all referenced through APPS synonyms, are:

All non-driving joins are outer joins, so every order type row is returned even when a related rule, price list or currency reference is missing. Because the view exposes the account rule and invoicing rule identifiers obtained through RA_RULES, it is a legitimate starting point for enquiries about the acct_rule referenced by an order type, although the rule detail itself resides in RA_RULES and RA_RULE_DETAILS.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting all active order types with their accounting rule and invoicing rule, validating pricing defaults, and feeding integration extracts that need order type configuration.

SELECT transaction_type_id,
       name,
       order_category_code,
       account_rule_id,
       accounting_credit_method_code,
       invoicing_rule_id,
       currency_code,
       start_date_active,
       end_date_active
FROM   apps.oefv_sales_order_types
WHERE  order_category_code = 'ORDER'
AND    SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1)
ORDER BY name;

To examine the accounting rule linked to each sales order type:

SELECT t.name          order_type,
       t.account_rule_id,
       r.name          accounting_rule,
       t.accounting_credit_method_code
FROM   apps.oefv_sales_order_types t,
       apps.ra_rules r
WHERE  t.account_rule_id = r.rule_id
ORDER BY t.name;

Because the view is a denormalized convenience layer, request-level reporting should filter by ORG_ID to honor operating unit security, and should reference TRANSACTION_TYPE_ID rather than description text when joining to transactional tables such as OE_ORDER_HEADERS_ALL.