Results for “op_prsl_typ_vl”

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

Overview

OP_PRSL_TYP_VL is a translatable (VL) view owned by the APPS schema in Oracle E-Business Suite. It belongs to the GML – Process Manufacturing Logistics product family and exposes presales order type definitions used during the sales order and presales cycle for process manufacturing operations. The view functions as the user-facing translation layer over the underlying presales type base and translation tables, resolving the language-specific descriptive columns so that queries and forms return data in the session's active language. It is classified as VALID and is documented for both EBS 12.1.1 and 12.2.2.

Its primary role is to present presales order type configuration data — the presales order code and description, scheduling and pricelist behaviour flags — in a form suitable for reporting, integration, and lookup validation. Because the view filters on the user's language environment, it is the preferred object for any enquiry that needs readable presales type descriptions rather than internal identifiers.

Underlying Base Objects

The view is defined over two synonyms that resolve to base tables in the APPS schema:

• OP_PRSL_TYP_B — the base (non-translated) table holding the presales order type identifier, functional flags, and standard WHO audit columns.
• OP_PRSL_TYP_TL — the translation table holding language-specific values for the presales order code and description.

The two objects are joined on the PRESALES_ORD_TYPE key, with the translation row additionally restricted by T.LANGUAGE = USERENV('LANG'). This restricts returned rows to the language of the current session, which is the defining behaviour of a _VL view in an Oracle EBS multilingual installation.

Key Columns

• ROW_ID — the ROWID of the base table row (B.ROWID), used as a unique row identifier.
• PRESALES_ORD_TYPE — the primary identifier for the presales order type, defined on the base table and used as the join key.
• LANG_CODE / LANGUAGE — the language of the translated row, constrained to the current session language.
• PRESALES_ORD_CODE — the user-visible short code for the presales type (translated).
• PRESALES_ORD_DESC — the descriptive name of the presales order type, supplying the ordering description reported against presales transactions.
• RELEASE_SCHED_REQD — flag indicating whether release scheduling is required for this presales type.
• PRICELIST_IND — indicator controlling pricelist usage behaviour for the type.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from the base table.
• TRANS_CNT, TEXT_CODE, DELETE_MARK — standard multi-lingual support columns, where DELETE_MARK indicates the logical deletion state.

Common Use Cases and Queries

The view is typically queried to populate list-of-values, to display presales type descriptions on reports, and to validate presales order types during integration loads. A basic lookup returns all active, non-deleted presales types in the session language:

SELECT PRESALES_ORD_TYPE, PRESALES_ORD_CODE, PRESALES_ORD_DESC, RELEASE_SCHED_REQD, PRICELIST_IND FROM APPS.OP_PRSL_TYP_VL WHERE NVL(DELETE_MARK, 'N') = 'N' ORDER BY PRESALES_ORD_CODE;

A more targeted query resolves the description for a specific type, which is the pattern used when reporting against the searched term "presales_ord_desc":

SELECT PRESALES_ORD_CODE, PRESALES_ORD_DESC FROM APPS.OP_PRSL_TYP_VL WHERE PRESALES_ORD_TYPE = :p_type;

Because the language filter is embedded in the view definition, no additional language predicate is required at the query level; the view automatically returns the description matching the concurrent or session language. Report developers and integration specialists should therefore prefer OP_PRSL_TYP_VL over the base tables whenever a translated presales order description is required.