Search Results activity_status_code

Overview

OE_PC_VTMPLTS_VL is a seeded, VALID view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ONT (Order Management) product family. The "_VL" suffix follows the standard Oracle Applications convention for a translated, language-sensitive view: it joins a base entity table to its corresponding translation table and filters the translation rows to the session language. In this case, the view exposes validation template definitions used by Order Management's Processing Constraints and validation framework, unifying the technical template definition with its language-specific display name and description. The view is available in both 12.1.1 and 12.2.2 and forms part of the public query surface through which validation template setup data is reported and consumed.

Notably, the view exposes API_PKG and API_PROC columns, which carry the name of the PL/SQL package and procedure invoked to perform the underlying validation logic. This makes the view directly relevant to the user's search term "api_pkg": the API_PKG column is the physical link between each configured validation template and the server-side API that implements it.

Underlying Base Objects

The view is defined over two base objects, both referenced in the ETRM metadata as synonyms:

• OE_PC_VTMPLTS — the base (untranslated) validation templates table, supplying all technical attributes including VALIDATION_TMPLT_ID, VALIDATION_TYPE, API_PKG, API_PROC, and the ATTRIBUTE1–15 descriptive flexfield columns.
• OE_PC_VTMPLTS_TL — the translation table, supplying DISPLAY_NAME and DESCRIPTION per language.

The view text performs an inner join on VALIDATION_TMPLT_ID between the two tables and applies the predicate TL.LANGUAGE = USERENV('LANG'), so only rows translated into the caller's session language are returned. The view also selects V.ROWID as ROW_ID, providing a row identifier through the join.

Key Columns

• ROW_ID — ROWID of the underlying OE_PC_VTMPLTS row.
• VALIDATION_TMPLT_ID — primary identifier of the validation template; the join key between base and translation tables.
• ENTITY_ID — identifies the business entity to which the validation template applies.
• VALIDATION_TMPLT_SHORT_NAME — internal short name used to reference the template in setup and code.
• VALIDATION_TMPLT_DISPLAY_NAME / VALIDATION_TMPLT_DESCRIPTION — language-specific text sourced from OE_PC_VTMPLTS_TL.
• VALIDATION_TYPE / SYSTEM_FLAG — classify the template and indicate whether it is seeded (system) or user-defined.
• API_PKG / API_PROC — the PL/SQL package and procedure executed for this validation; the operative columns for API-driven validation behavior.
• ACTIVITY_NAME / ACTIVITY_STATUS_CODE / ACTIVITY_RESULT_CODE — workflow activity context and outcome codes.
• WF_ITEM_TYPE — the workflow item type associated with the template.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — descriptive flexfield storage.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include setup reporting of validation templates, auditing which API package and procedure back each validation, and driving integration or extension logic that must resolve a template to its implementing API. Because the view is language-filtered, queries return display text in the session language.

List all validation templates with their implementing API:

• SELECT validation_tmplt_id, validation_tmplt_short_name, validation_tmplt_display_name, validation_type, system_flag, api_pkg, api_proc FROM oe_pc_vtmplts_vl ORDER BY validation_tmplt_short_name;

Find the templates backed by a specific package (matching the "api_pkg" search):

• SELECT validation_tmplt_short_name, validation_tmplt_display_name, api_pkg, api_proc, validation_type FROM oe_pc_vtmplts_vl WHERE api_pkg = :p_api_pkg;

Restrict to seeded templates for a given entity:

• SELECT validation_tmplt_id, validation_tmplt_short_name, api_proc FROM oe_pc_vtmplts_vl WHERE entity_id = :p_entity_id AND system_flag = 'Y';

As with all APPS views, access should respect the standard MO security model, and joins to OE_PC_VTMPLTS by VALIDATION_TMPLT_ID are required when untranslated technical data beyond the exposed columns is needed.