Search Results okl_checklist_status_code

Overview

APPS.OKL_CHECKLISTS_UV is a user-facing (validation) view in the Oracle E-Business Suite Enterprise Contracts (OKL) module that presents a denormalized, code-translated representation of checklist records used across the Oracle Contracts and Service Contracts infrastructure. Its primary function is to expose checklist header data together with human-readable lookup meanings for the various coded columns, sparing report authors, Oracle Forms validations, and integration extracts the effort of manually joining to FND_LOOKUPS. The view is significant because checklist templates and template groups underpin the delivery of structured task and verification lists against contract deliverables, service lines, and other objects managed by the ETRM (Enterprise Transaction and Resource Management) schema family.

The view derives its name suffix "_UV" from the common Oracle EBS convention for User Validation views — meaning its row content is filtered to only the meaningful business use case, specifically records whose CHECKLIST_PURPOSE_CODE is either 'CHECKLIST_TEMPLATE' or 'CHECKLIST_TEMPLATE_GROUP'. This filtering means the view does not return the full set of checklists stored in the base table; it returns only template-class checklists intended for user selection.

Underlying Base Objects

The view is defined over four referenced objects as documented in ETRM 12.2.2:

• OKL_CHECKLISTS (accessed via synonym) — the driving table, aliased CKL, supplying all core checklist attributes including ID, CHECKLIST_NUMBER, DESCRIPTION, dates, status, and DFF attribute columns.
• OKL_CHECKLISTS_ALL (accessed via synonym) — aliased CKL2 and joined with an outer join on ckl.id = ckl2.ckl_id. It is used to retrieve the parent checklist number for template groups.
• FND_LOOKUPS (view) — joined three times (FLK, FLK2, FLK4) to translate CHECKLIST_TYPE, CHECKLIST_PURPOSE_CODE, and STATUS_CODE into their respective MEANING columns.
• FND_GLOBAL (package) — referenced for multi-org (ORG_ID) security context resolution in typical EBS views of this class.

The use of outer joins on OKL_CHECKLISTS_ALL ensures that standalone checklist templates (those without a group parent) are still returned, while templates belonging to a group inherit the group's CHECKLIST_NUMBER for display purposes.

Key Columns

• ID, OBJECT_VERSION_NUMBER, CKL_ID — primary key and optimistic locking version; CKL_ID links children to their parent template group.
• CHECKLIST_NUMBER, CKL2.CHECKLIST_NUMBER — the checklist's own number and, where applicable, its parent group's number.
• CHECKLIST_TYPE and CHECKLIST_TYPE_MEANING — the raw lookup code and its translated meaning, drawn from lookup type OKL_CHECKLIST_TYPE. This is the column most commonly referenced by searches for "okl_checklist_type".
• CHECKLIST_PURPOSE_CODE and CHECKLIST_PURPOSE_MEANING — restricted to the template/template-group purposes; drawn from OKL_CHECKLIST_PURPOSE_CODE.
• STATUS_CODE and STATUS_CODE_MEANING — lifecycle status of the checklist, translated via OKL_CHECKLIST_STATUS_CODE.
• START_DATE, END_DATE, DECISION_DATE — effective period and decision date for the checklist.
• CHECKLIST_OBJ_ID, CHECKLIST_OBJ_TYPE_CODE — identifies the business object the checklist is associated with.
• ORG_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard multi-org and concurrent program audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the descriptive flexfield columns associated with the checklist.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include LOV validation in Oracle Forms, template selection during contract authoring, and custom reports listing available checklist templates by type or status.

To list all active checklist templates with translated codes:

SELECT id, checklist_number, checklist_type_meaning, checklist_purpose_meaning, status_code_meaning, start_date, end_date FROM apps.okl_checklists_uv WHERE status_code_meaning = 'Active' ORDER BY checklist_number;

To locate checklist templates of a given OKL_CHECKLIST_TYPE:

SELECT id, checklist_number, description, checklist_type_meaning FROM apps.okl_checklists_uv WHERE checklist_type = :p_checklist_type;

To list template groups and their member templates:

SELECT ckl_id, ckl2_checklist_number FROM apps.okl_checklists_uv WHERE checklist_purpose_code = 'CHECKLIST_TEMPLATE_GROUP' ORDER BY ckl_id;

Because the view filters to template purposes only, production usages requiring runtime (non-template) checklist instances must query the underlying OKL_CHECKLISTS table directly.