Results for “name_column”

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

Overview

OKC_PROCESS_DEF_PARMS_B is a core configuration table in the Oracle Contracts (OKC) module of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It records the parameters belonging to a process definition stored in OKC_PROCESS_DEFS_B. Each row defines a single input or argument that a contract process expects, capturing the parameter name, its datatype, whether it is mandatory, and any default value. In this capacity the table acts as the metadata layer that drives the Contract Expert, user hook, and outcome-argument frameworks — the runtime engine reads these definitions to validate and bind values supplied by a contract or a calling program.

Under a heuristic Data Vault classification mined from its foreign-key topology, the table is assessed as hub-leaning. Each row carries a surrogate identifier and is referenced by multiple dependent tables, which suggests it behaves as a durable business key entity rather than a transactional satellite. This classification is offered as a modeling suggestion only; in native EBS terms the object is a standard seeded/transactional configuration table owned by OKC.

Key Information Stored

The table contains nineteen documented columns. The most operationally significant are listed below.

• ID — Surrogate primary key, enforced by the constraint OKC_PROCESS_DEF_PARMS_B_PK. It uniquely identifies each parameter definition.
• PDF_ID — Foreign key to OKC_PROCESS_DEFS_B; identifies the parent process definition to which the parameter belongs.
• NAME — The parameter name used within the process definition.
• DATA_TYPE — Declared datatype of the parameter (for example character, number, or date), used to validate supplied values.
• REQUIRED_YN — Optionality flag indicating whether the parameter must be populated at runtime.
• DEFAULT_VALUE — Default value applied when no explicit value is passed.
• SEEDED_FLAG — Indicates whether the row was delivered as Oracle seed data or created by the customer.
• APPLICATION_ID — Owning application identifier, supporting multi-application partitioning.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, controlling row visibility by security group.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard auditing and optimistic-locking columns.
• ZD_EDITION_NAME — Editioning column introduced under the EBS online patching (ADOP) architecture in 12.2, used together with the business-key index.

The documented unique index OKC_PROCESS_DEF_PARMS_B_U1 spans (ID, ZD_EDITION_NAME), reflecting the edition-aware key design of 12.2.2. The surrogate key remains ID, while the composite unique index is the business-key candidate.

Common Use Cases and Queries

Typical uses include reviewing which parameters a given process definition exposes, auditing seeded versus custom parameters, and troubleshooting runtime parameter binding errors.

• List parameters for a process definition: SELECT NAME, DATA_TYPE, REQUIRED_YN, DEFAULT_VALUE FROM OKC_PROCESS_DEF_PARMS_B WHERE PDF_ID = :pdf_id ORDER BY NAME;
• Identify mandatory parameters: filter on REQUIRED_YN = 'Y'.
• Distinguish customer extensions from Oracle seed data using SEEDED_FLAG.
• Join to dependent argument tables to trace how a parameter is consumed.

Related Objects

• OKC_PROCESS_DEFS_B — parent table, joined via OKC_PROCESS_DEF_PARMS_B.PDF_ID = OKC_PROCESS_DEFS_B.ID.
• OKC_FUNCTION_EXPR_PARAMS — references this table via PDP_ID.
• OKC_OUTCOME_ARGUMENTS — references this table via PDP_ID.
• OKC_QA_PROCESS_PARMS — references this table via PDP_ID.
• OKC_USER_HOOK_CALLS — references this table via PDF_USING_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID.