Results for “contract_template_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OE_TRXT_TYPES_NOORGS_VL is a valid, organization-independent multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite. It belongs to the ONT – Order Management product family and is documented in Oracle's ETRM (E-Business Suite Technical Reference Manual) for release 12.1.1 and 12.2.2. its purpose, per the documentation, is explicit: it exists so that the Shipping integration team can retrieve the Order Type name without being constrained by, or required to supply, an operating unit (ORG_ID) context.
Internally, the ETRM describes it as an "Org independent VL view for Shipping integration team to get the Order Type name." In EBS terms, a "VL" view conventionally joins a base (_ALL or _B) table to its corresponding translation (_TL) table, resolving the translated NAME and DESCRIPTION based on the session language. The "NOORGS" prefix signals that this view deliberately does not filter by organization. This makes it suitable for cross-organizational lookups, background programs, and integration channels where the caller has no committed ORG_ID in session.
Underlying Base Objects
According to the documented ETRM metadata, the view is defined over two base objects, both referenced through synonyms:
- OE_TRANSACTION_TYPES_ALL (SYNONYM) — aliased as
Bin the view text; supplies the transactional and structural attributes of the order type. - OE_TRANSACTION_TYPES_TL (SYNONYM) — aliased as
T; supplies the translated NAME and DESCRIPTION.
The join predicate, per the view text, is B.TRANSACTION_TYPE_ID = T.TRANSACTION_TYPE_ID combined with T.LANGUAGE = USERENV('LANG'). Because it is built on a VL pattern and omits an ORG_ID filter in the join, the view returns a single row per order type for the current session language. Note, however, that the projected column list still includes ORG_ID — the column is carried through, but the view itself remains org-independent in behavior.
Key Columns
Because the view selects from a wide base table, it exposes a substantial column set. The most operationally significant columns include:
- TRANSACTION_TYPE_ID — Primary key of the order type; the join anchor between the two base objects.
- TRANSACTION_TYPE_CODE and ORDER_CATEGORY_CODE — The internal identifier and category (e.g., order, return, mixed) of the type.
- NAME and DESCRIPTION — Sourced from the TL table; the translated, user-facing Order Type name that the Shipping integration consumes.
- START_DATE_ACTIVE / END_DATE_ACTIVE — Date-range activation controls for the type.
- ORG_ID — Operating unit identifier; present in the projection but not used as a filter.
- CURRENCY_CODE, PRICE_LIST_ID, WAREHOUSE_ID, SHIPPING_METHOD_CODE, FREIGHT_TERMS_CODE, FOB_POINT_CODE, SHIP_SOURCE_TYPE_CODE — Default shipping and pricing attributes relevant to fulfillment.
- INVOICING_RULE_ID, ACCOUNTING_RULE_ID, CUST_TRX_TYPE_ID — Financial defaults tied to the order type.
- ATTRIBUTE1 through ATTRIBUTE15 plus CONTEXT — The standard EBS DFF columns for customer-defined extensions.
- ROW_ID — Row identifier derived from the base table's ROWID, useful for row-level identification.
Common Use Cases and Queries
The primary scenario is Shipping-style integration lookups, where a downstream system needs to resolve a Transaction Type Id to its human-readable name without an operating unit context. A representative query is:
SELECT TRANSACTION_TYPE_ID, TRANSACTION_TYPE_CODE, NAME, ORDER_CATEGORY_CODE FROM OE_TRXT_TYPES_NOORGS_VL ORDER BY NAME;- Targeted lookup:
SELECT NAME, DESCRIPTION FROM OE_TRXT_TYPES_NOORGS_VL WHERE TRANSACTION_TYPE_ID = :p_type_id; - Filtering active types for a code:
SELECT NAME FROM OE_TRXT_TYPES_NOORGS_VL WHERE TRANSACTION_TYPE_CODE = 'ORDER' AND NVL(END_DATE_ACTIVE, SYSDATE+1) > SYSDATE;
Because the view is org-independent, it is best used strictly for name resolution and validation rather than for org-specific policy enforcement; callers that require an operating unit scope should join to or query OE_TRANSACTION_TYPES_ALL with an explicit ORG_ID predicate. Additionally, since no ORDER BY or DISTINCT is applied, integrations should expect one row per type per language and handle language dependence through the USERENV('LANG') setting of the executing session.
-
Org independent VL view for Shipping integration team to get the Order Type name.
APPS.OE_TRXT_TYPES_NOORGS_VL·↳ OE_TRANSACTION_TYPES_ALL·↳ OE_TRANSACTION_TYPES_TL·Explore ONT module →
-
Lease Application Template Versions
-
quotations
APPS.ASO_QUOTE_HEADERS_ALL_V·↳ ASO_QUOTE_HEADERS·Explore ASO module →
-
View for OKL_LEASEAPP_TEMPL_VERSIONS_B and OKL_LEASEAPP_TEMPL_VERSIONS_TL
APPS.OKL_LEASEAPP_TEMPL_VERSIONS_V·↳ OKL_LEASEAPP_TEMPL_VERSIONS_B·↳ OKL_LEASEAPP_TEMPL_VERSIONS_TL·Explore OKL module →
-
PACKAGE: APPS.OE_VALIDATE 12.1.1
-
View: OE_TRANSACTION_TYPES_V 12.2.2
APPS.OE_TRANSACTION_TYPES_V·↳ HR_GENERAL·↳ HR_ORGANIZATION_UNITS·↳ HR_SECURITY·Explore ONT module →
-
quotations
APPS.ASO_QUOTE_HEADERS_ALL_V·↳ ASO_QUOTE_HEADERS·Explore ASO module →
-
MLS transaction types view for an organization.
APPS.OE_TRANSACTION_TYPES_VL·↳ OE_TRANSACTION_TYPES_SYN·↳ OE_TRANSACTION_TYPES_TL·Explore ONT module →
-
Org independent VL view for Shipping integration team to get the Order Type name.
APPS.OE_TRXT_TYPES_NOORGS_VL·↳ OE_TRANSACTION_TYPES_ALL·↳ OE_TRANSACTION_TYPES_TL·Explore ONT module →
-
This table stores information about the order and line transaction types
-
APPS.ASO_PVT_QUOTE_HEADERS_V·↳ ASO_I_ORDER_TYPES_V·↳ ASO_I_PRICE_LISTS_V·↳ ASO_QUOTE_HEADERS·Explore ASO module →
-
This table holds header level Order Capture quotation data.
-
PACKAGE: APPS.OE_VALIDATE 12.2.2
-
View: ASO_QUOTE_HEADERS_V 12.1.1
quotations
APPS.ASO_QUOTE_HEADERS_V·↳ ASO_I_PARTIES_V·↳ ASO_QUOTE_HEADERS·↳ ASO_QUOTE_STATUSES_B·Explore ASO module →
-
Common View on pon_auction_headers_all
APPS.PON_AUCTION_HEADERS_ALL_V·↳ FND_LOOKUP_VALUES·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HZ_PARTIES·Explore PON module →
-
Lease Application Template Versions
-
View for OKL_LEASEAPP_TEMPL_VERSIONS_B and OKL_LEASEAPP_TEMPL_VERSIONS_TL
APPS.OKL_LEASEAPP_TEMPL_VERSIONS_V·↳ OKL_LEASEAPP_TEMPL_VERSIONS_B·↳ OKL_LEASEAPP_TEMPL_VERSIONS_TL·Explore OKL module →
-
View: IBE_QUOTE_HEADERS_V 12.1.1
APPS.IBE_QUOTE_HEADERS_V·↳ ASO_QUOTE_HEADERS·↳ ASO_QUOTE_STATUSES_VL·↳ HZ_CUST_ACCOUNTS·Explore IBE module →
-
ASO_QUOTE_HEADERS holds Order Capture quotation information. it has the header data of a quote. For each quote header, there can zero or many quote lines attached to it.
-
View: OE_ORDER_TYPES_V 12.1.1
This is a view to show order transaction types for a specific organization and language.
APPS.OE_ORDER_TYPES_V·↳ OE_TRANSACTION_TYPES_VL·Explore ONT module →
-
View: OE_ORDER_TYPES_V 12.2.2
This is a view to show order transaction types for a specific organization and language.
APPS.OE_ORDER_TYPES_V·↳ OE_TRANSACTION_TYPES_VL·Explore ONT module →
-
View: OE_TRANSACTION_TYPES_V 12.1.1
APPS.OE_TRANSACTION_TYPES_V·↳ HR_GENERAL·↳ HR_ORGANIZATION_UNITS·↳ HR_SECURITY·Explore ONT module →
-
View: ASO_QUOTE_HEADERS_V 12.2.2
quotations
APPS.ASO_QUOTE_HEADERS_V·↳ ASO_I_PARTIES_V·↳ ASO_QUOTE_HEADERS·↳ ASO_QUOTE_STATUSES_B·Explore ASO module →
-
Common View on pon_auction_headers_all
APPS.PON_AUCTION_HEADERS_ALL_V·↳ FND_LOOKUP_VALUES·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HZ_PARTIES·Explore PON module →
-
MLS transaction types view for an organization.
APPS.OE_TRANSACTION_TYPES_VL·↳ OE_TRANSACTION_TYPES_SYN·↳ OE_TRANSACTION_TYPES_TL·Explore ONT module →
-
This table stores information about the order and line transaction types
-
View: IBE_QUOTE_HEADERS_V 12.2.2
APPS.IBE_QUOTE_HEADERS_V·↳ ASO_QUOTE_HEADERS·↳ ASO_QUOTE_STATUSES_VL·↳ HZ_CUST_ACCOUNTS·Explore IBE module →
-
APPS.ASO_PVT_QUOTE_HEADERS_V·↳ ASO_I_ORDER_TYPES_V·↳ ASO_I_PRICE_LISTS_V·↳ ASO_QUOTE_HEADERS·Explore ASO module →
-
Stores the negotiations header level details.
-
Stores the negotiations header level details.
-
VIEW: CS.CS_CONTRACTS_ALL# 12.2.2