Results for “order_leadtime”

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

Overview

OP_ORDR_TYP_VL is a seeded, VALID view owned by the APPS schema within Oracle E-Business Suite. It is delivered as part of the GML (Process Manufacturing Logistics) product family and is documented in ETRM for both 12.1.1 and 12.2.2. The object is described simply as an "order type view," reflecting its purpose as the user-facing, language-aware presentation layer for process manufacturing order type definitions. It is not a transactional table; it is a denormalized read surface that joins the base order type entity to its translated (TL) counterpart.

In EBS architecture, views suffixed with _VL typically combine a base (or _B) table with a translation (_TL) table, filtered by USERENV('LANG'), so that consumers see descriptive text in the session's current language. OP_ORDR_TYP_VL follows exactly this convention, exposing both the non-translatable attributes from OP_ORDR_TYP_B and the translatable name and description from OP_ORDR_TYP_TL. For reporting, integrations, and personalizations, this view is the appropriate Oracle-recommended access point rather than querying the underlying tables directly.

Underlying Base Objects

The documented view text joins two referenced base objects, both exposed as synonyms in the APPS schema:

• OP_ORDR_TYP_B — the base table holding language-independent order type attributes (flags, indicators, and audit columns).
• OP_ORDR_TYP_TL — the translation table holding ORDER_TYPE_CODE and ORDER_TYPE_DESC per language.

The join predicate is B.ORDER_TYPE = T.ORDER_TYPE AND T.LANGUAGE = USERENV('LANG'), which restricts the row set to the session language. Notably, the view can return duplicate-looking characteristics per order type because translation rows exist per installed language; the language filter ensures a single effective row per order type for the active session. Both referenced objects are documented as APPS synonyms rather than direct table references, consistent with the standard EBS synonym pattern that allows the underlying object to be replaced or evolved without invalidating dependent views.

Key Columns

The view exposes an extensive set of columns. Principal among them are:

• ROW_ID — the ROWID of the base table row, used by Oracle Forms and certain APIs for row identification.
• ORDER_TYPE — the primary key value linking the base and translation records.
• ORDER_TYPE_CODE and ORDER_TYPE_DESC — the translated short code and descriptive text sourced from OP_ORDR_TYP_TL; these are the columns most often surfaced in reporting and LOVs.
• LANG_CODE / LANGUAGE — the language identifier, populated from USERENV('LANG').
• INVEN_TRANS_TYPE — indicates the inventory transaction type associated with the order type, governing inventory movement behavior.
• Behavioral indicators: SHIPMENT_IND, INVOICE_IND, PICKINGLST_IND, EXPORTDOC_IND, TOTALORD_IND, PRODORDR_IND, PRICE_ORDER, CALC_COMM_IND, CALC_TAX_IND, CREDITCHK_TYPE, SHIPTO_REQUIRED, and UPDATE_SALESHIST — these govern whether shipment, invoicing, picking lists, export documentation, total order processing, production orders, pricing, commission, tax, and credit checking apply.
• ORDER_LEADTIME — lead time value applied to the order type.
• UPDATE_AUDITTRAIL, TRANS_CNT, TEXT_CODE, DELETE_MARK — audit, concurrency, and soft-delete control columns inherited from the base table.
• Standard WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include populating order type lists of values, validating order type configuration during set-up, and joining order type descriptions to process manufacturing sales or shipping data in custom reports. Because the view is language-filtered, reports automatically display descriptions in the session language.

To list available order types in the current language:

• SELECT order_type, order_type_code, order_type_desc, shipment_ind, invoice_ind FROM apps.op_ordr_typ_vl WHERE NVL(delete_mark,0) = 0 ORDER BY order_type_code;

To examine configuration flags for a specific order type:

• SELECT order_type_code, order_type_desc, inven_trans_type, credit_chk_type, order_leadtime, price_order, calc_tax_ind FROM apps.op_ordr_typ_vl WHERE order_type = :p_order_type;

To join order type descriptions to downstream order data (illustrative):

• SELECT h.order_type, v.order_type_desc, h.order_number FROM apps.<order_header_table> h, apps.op_ordr_typ_vl v WHERE h.order_type = v.order_type;

Because the view is read-only and defined over translated data, it should not be used for DML. Inserts and updates must target the base tables (or supported public APIs) so that translation and audit columns are maintained correctly. When the view returns no rows for a given order type, the cause is ordinarily a missing translation row for the session language in OP_ORDR_TYP_TL rather than a missing base record.