Results for “token_type”

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

Overview

PRP_TOKENS_VL is a translated (VL) view in the APPS schema belonging to the PRP – Proposals product module of Oracle E-Business Suite. In Oracle EBS, a "_VL" view presents the language-specific, translated attributes of an entity joined to its base (non-translated) attributes, filtered to the session's current language. PRP_TOKENS_VL therefore exposes the definition of "tokens" — the substitution placeholders used within Oracle Proposals templates — combining descriptive, translatable text with the operational columns that govern how each token behaves. The view carries a VALID status in the ETRM repository for both 12.1.1 and 12.2.2 and is owned by APPS, confirming it is a supported, queryable interface rather than an internal implementation artifact.

Because tokens drive the dynamic content of proposal documents, this view serves reporting and integration needs: it allows developers and report authors to enumerate available tokens, inspect their data types and Java program bindings, and resolve the human-readable prompts and descriptions in the user's own language.

Underlying Base Objects

The view is defined over two synonyms in the APPS schema: PRP_TOKENS_B, which holds the base (language-independent) token definition, and PRP_TOKENS_TL, which holds the translated token name, prompt, and description for each installed language. The join is performed on TOKEN_ID, and the translation table is restricted by T.LANGUAGE = USERENV('LANG'), ensuring the caller sees only the rows matching the current session language. This is the standard Oracle multi-language architecture: the _B table stores one row per token, while the _TL table stores one row per token per language. The B row provides identity, behavioral metadata, and audit columns; the TL row supplies the display-oriented text.

Key Columns

• ROW_ID – the ROWID of the underlying PRP_TOKENS_B row, provided for row-level identification.
• TOKEN_ID – the primary key linking the base and translated records.
• TOKEN_CODE – the internal code that identifies the token in templates.
• TOKEN_NAME, TOKEN_PROMPT, TOKEN_DESC – the translated name, prompt text, and description sourced from PRP_TOKENS_TL, resolved to the session language.
• TOKEN_TYPE, NATIVE_OBJECT_TYPE, DATA_TYPE, DISPLAY_LENGTH – the token's classification and the type/length of data it accepts or produces.
• JAVA_PROGRAM_NAME, USER_DEFINED_OPTIONS – the Java implementation or custom options associated with the token.
• START_DATE_ACTIVE, END_DATE_ACTIVE – the effective date range during which the token is usable.
• OBJECT_VERSION_NUMBER – optimistic locking column used by the underlying framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – the standard Oracle EBS descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include building token inventories for proposal authors, validating template configuration, driving LOVs and picklists in custom forms, and extracting metadata for integrations that generate proposal documents. Because the view resolves text in the runtime language, reports built directly on it automatically display prompts and descriptions in the user's language.

To list all currently active tokens with their prompts:

• SELECT token_code, token_name, token_prompt, data_type FROM apps.prp_tokens_vl WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) ORDER BY token_name;

To inspect a specific token by its code:

• SELECT token_id, token_code, token_name, token_prompt, token_desc, java_program_name FROM apps.prp_tokens_vl WHERE token_code = :p_code;

To retrieve translated content in a specific language independent of the session, query the underlying PRP_TOKENS_TL directly and join it to PRP_TOKENS_B. When using the _VL view, no language join is required, which simplifies reporting queries and keeps them aligned with Oracle's multi-language conventions.