Search Results okc_process_def_parameters_v




Overview
Explore in AI Chat

Overview

OKC_PROCESS_DEF_PARAMETERS_V is a PL/SQL-based view owned by the APPS schema within the OKC - Contracts Core product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the definition-time metadata that governs parameters accepted by contract processes configured through Oracle Contract Terms and Conditions (ETRM), the application responsible for authoring, authoring workflows, and lifecycle management of contracts. The view presents a single, translated, language-aware picture of each process definition parameter: the physical parameter row plus its user-facing (translated) name and description. Because it joins the base and translation tables, it behaves as a reporting convenience layer, hiding the multi-table translation pattern required for a complete record from the consumer. It is read-only by design and is intended for reporting, integration, and diagnostic queries that need to enumerate the parameter contract for a given process definition (identified by PDF_ID) without manually joining translation tables or resolving language codes.

Underlying Base Objects

The view is defined over two tables in the OKC schema, available to APPS through synonyms: OKC_PROCESS_DEF_PARMS_B, the base (non-translated) table holding the canonical parameter row, and OKC_PROCESS_DEF_PARMS_TL, the translated table holding language-specific NAME and DESCRIPTION values. The metadata lists both as OKC_PROCESS_DEF_PARMS_B (SYNONYM) and OKC_PROCESS_DEF_PARMS_TL (SYNONYM). The join condition is PDPB.ID = PDPT.ID AND PDPT.LANGUAGE = USERENV('LANG'), so the view returns exactly one row per parameter, filtered to the session's current language. This is the standard "_B/_TL" EBS pattern: the _B table carries structural attributes such as DATA_TYPE, DEFAULT_VALUE, and REQUIRED_YN, while the _TL table supplies locale-sensitive text. Callers that require all languages must query the _TL table directly.

Key Columns

  • ROW_ID — the physical ROWID of the _B row; useful for diagnostics and direct row addressing.
  • ID — the primary identifier for the parameter, used in the join between _B and _TL.
  • PDF_ID — foreign key to the process definition (the parent process) that owns this parameter. This is the principal filter key in most queries.
  • NAME / USER_NAME — NAME is the internal parameter name from _B; USER_NAME is the translated, display-oriented name from _TL. Applications should prefer USER_NAME for presentation.
  • DESCRIPTION — translated description of the parameter, sourced from _TL.
  • DATA_TYPE — declares the parameter's expected type (for example, string, number, or date), driving validation.
  • DEFAULT_VALUE — the default applied when the caller supplies no value.
  • REQUIRED_YN — indicates whether the parameter must be provided.
  • APPLICATION_ID — the owning application, supporting multi-product lookups.
  • SEEDED_FLAG — distinguishes Oracle-delivered seed data from customer-defined parameters.
  • OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit and optimistic-locking columns.
  • SFWT_FLAG — translated-table flag carried through from _TL.
  • JTOT_OBJECT_CODE, NAME_COLUMN, DESCRIPTION_COLUMN — metadata used by the JTOT (Terms and Conditions) framework to map the parameter to its target object and to the columns that supply its name and description.

Common Use Cases and Queries

Typical scenarios include enumerating the parameters required to invoke a contract process, validating configuration during a migration or upgrade, and building integration payloads that must conform to a process definition's parameter contract. The view is also used in diagnostics to confirm whether a parameter is seeded or customer-defined.

List all parameters for a given process definition:

SELECT id, user_name, name, data_type, required_yn, default_value
FROM   okc_process_def_parameters_v
WHERE  pdf_id = :p_pdf_id
ORDER  BY user_name;

Identify required, seed-delivered parameters across all processes:

SELECT pdf_id, user_name, data_type
FROM   okc_process_def_parameters_v
WHERE  required_yn = 'Y'
AND    seeded_flag = 'Y'
ORDER  BY pdf_id, user_name;

Because the view filters on USERENV('LANG'), results are returned in the language of the current session. Consumers needing untranslated or all-language data should query OKC_PROCESS_DEF_PARMS_B and OKC_PROCESS_DEF_PARMS_TL directly. As with any APPS view, access is controlled through grants and synonyms rather than direct table privileges, and it should be treated as read-only.