Results for “use_ame_approval”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OE_TRANSACTION_TYPES_V view is a public Oracle E-Business Suite dictionary object owned by the APPS schema and validated under the ONT (Order Management) product family. It exposes the operational attributes of order transaction types — the classification codes that drive order entry behavior, credit checking, defaulting, scheduling, pricing, and invoicing within Oracle Order Management. The view consolidates the translated transaction type definition held in the multilanguage base table, resolved organization context, lookup meanings, and organization unit names into a single queryable interface.

Because it carries an ORG_ID column and joins to HR_ORGANIZATION_UNITS, the view is organization-secured. From a reporting and integration perspective, OE_TRANSACTION_TYPES_V is the standard read-only access point for transaction type setup data. Forms, concurrent programs, and custom interfaces query it rather than the underlying _VL table directly, since it supplies the row identifier (ROW_ID), the descriptive organization name, and the decoded lookup meaning that the base table alone does not provide.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects:

• OE_TRANSACTION_TYPES_VL (VIEW) — the primary source, providing all transaction type columns.
• HR_ORGANIZATION_UNITS (VIEW) — joined on ORG_ID to supply the operating unit NAME.
• OE_LOOKUPS (VIEW) — joined to decode SALES_DOCUMENT_TYPE_CODE into the SALES_DOCUMENT_TYPE meaning.
• HR_GENERAL (PACKAGE) and HR_SECURITY (PACKAGE) — supporting the organizational security predicates applied to the view.

The view text selects from OE_TRANSACTION_TYPES_VL as VL, joining HR_ORGANIZATION_UNITS (HOU) on ORG_ID and OE_LOOKUPS (OEL) to resolve the sales document type meaning. The ROWID of the _VL row is surfaced as ROW_ID.

Key Columns

The view exposes the full attribute set of an order transaction type. Notable columns include:

• TRANSACTION_TYPE_ID / TRANSACTION_TYPE_CODE / ORDER_CATEGORY_CODE — the key identifier, code, and category (e.g., order versus return).
• NAME / DESCRIPTION — the user-facing transaction type name and description.
• ENTRY_CREDIT_CHECK_RULE_ID, SHIPPING_CREDIT_CHECK_RULE_ID, PICKING_CREDIT_CHECK_RULE_ID, PACKING_CREDIT_CHECK_RULE_ID — the credit check rule to enforce at each order cycle stage. PACKING_CREDIT_CHECK_RULE_ID governs credit validation when the order reaches packing.
• INVOICING_RULE_ID / ACCOUNTING_RULE_ID and the related credit method codes — invoicing and revenue recognition behavior.
• PRICE_LIST_ID, ENFORCE_LINE_PRICES_FLAG, MIN_MARGIN_PERCENT — pricing defaults and controls.
• DEFAULT_INBOUND_LINE_TYPE_ID / DEFAULT_OUTBOUND_LINE_TYPE_ID — default line types for inbound and outbound flows.
• SALES_DOCUMENT_TYPE_CODE and SALES_DOCUMENT_TYPE — the code and its decoded lookup meaning.
• ORG_ID and the joined organization NAME — the operating unit context.

Common Use Cases and Queries

Typical uses include reporting transaction type setup across operating units, diagnosing credit check rule configuration, and driving interface validation. For example, to inspect credit check rules per transaction type:

SELECT transaction_type_code, name, entry_credit_check_rule_id, shipping_credit_check_rule_id, picking_credit_check_rule_id, packing_credit_check_rule_id FROM oe_transaction_types_v WHERE org_id = :p_org_id;

To list active transaction types with their operating unit:

SELECT v.transaction_type_code, v.name, v.order_category_code, v.sales_document_type FROM oe_transaction_types_v v WHERE v.org_id = :p_org_id AND TRUNC(SYSDATE) BETWEEN v.start_date_active AND NVL(v.end_date_active, TRUNC(SYSDATE)+1);