Results for “action_type_code”

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

Overview

OKS_ACTION_TIME_TYPES is a reference and configuration table owned by the OKS schema (Service Contracts module) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is forward-looking: it was introduced to support a proposed capability for user-defined action time types. In the current release, the table is populated with a fixed set of system values — 'RCN' for reaction times and 'RSN' for resolution times — while the ACTION_TYPE_CODE column is designed so that customer-defined codes can be accommodated in future releases without structural change. In practice, OKS_ACTION_TIME_TYPES acts as a lightweight lookup that classifies service-contract time commitments on entitlements and service requests, enabling reporting that separates first-response (reaction) targets from full-resolution targets.

From a Data Vault modeling perspective, the mined metadata classifies this object as standalone — that is, it does not participate as a hub, link, or satellite in a typical integration model, and is best treated as a static reference dimension. Its only declared foreign key relationship is to FND_SECURITY_GROUPS via SECURITY_GROUP_ID, which is a Multi-Org / data-security artifact rather than a business relationship.

Key Information Stored

The table contains 18 documented columns. The most significant are:

• ID — the surrogate primary key, enforced by unique index OKS_ACTION_TIME_TYPES_U1. It is also the business-key candidate in the documented structure.
• ACTION_TYPE_CODE — the functional discriminator holding 'RCN' (reaction time) and 'RSN' (resolution time). This is the column the design intends to extend for user-defined values.
• CLE_ID — references the contract line / entitlement context to which the action time type applies.
• DNZ_CHR_ID — the denormalized character ID, a standard OKS pattern that stores a concatenated parent key for fast lookup without joins.
• SECURITY_GROUP_ID — the operative organization / data-security grouping; the sole declared foreign key target is FND_SECURITY_GROUPS.
• ORIG_SYSTEM_ID1, ORIG_SYSTEM_REFERENCE1, ORIG_SYSTEM_SOURCE_CODE — the standard Oracle "origin system" trio, used for cross-system reconciliation and data migration lineage.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrent Manager audit columns recording which program last touched the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the WHO columns.
• OBJECT_VERSION_NUMBER — optimistic locking for the OAF/ADF layer.

Note that there is no separate meaningful business key beyond ID in the documented metadata; ACTION_TYPE_CODE plus CLE_ID often functions as the de facto composite identifier in queries.

Common Use Cases and Queries

Typical uses involve joining the table to entitlement or service-request data to resolve the numeric code into a human-readable time type, filtering by security group, or auditing which program inserted or updated a row.

SELECT a.ID,
       a.ACTION_TYPE_CODE,
       DECODE(a.ACTION_TYPE_CODE, 'RCN', 'Reaction', 'RSN', 'Resolution', 'Other') AS time_type
FROM   OKS.OKS_ACTION_TIME_TYPES a
WHERE  a.SECURITY_GROUP_ID = :org_id
ORDER  BY a.ACTION_TYPE_CODE;

For reconciliation against a source system:

SELECT a.ID, a.ORIG_SYSTEM_SOURCE_CODE, a.ORIG_SYSTEM_ID1, a.ORIG_SYSTEM_REFERENCE1
FROM   OKS.OKS_ACTION_TIME_TYPES a
WHERE  a.ORIG_SYSTEM_REFERENCE1 IS NOT NULL;

Reporting scenarios commonly count reaction versus resolution rows per contract line to validate SLA coverage, or use the PROGRAM_ID/REQUEST_ID pair to trace which concurrent program populated the table during implementation.

Related Objects

The documented foreign-key metadata identifies only one outbound reference, but the surrounding OKS service-contract objects that logically depend on it include:

• FND_SECURITY_GROUPS — referenced by OKS_ACTION_TIME_TYPES.SECURITY_GROUP_ID; the sole declared FK.
• OKS_ENTITLEMENTS — entitlement records that define reaction and resolution commitments.
• OKS_K_HEADERS / OKS_K_LINES — contract headers and lines that consume the CLE_ID/DNZ_CHR_ID context.
• OKS_SERVICE_REQUESTS — runtime transactions measured against RCN/RSN targets.
• OKS_ACTION_TIMES — the operational sibling table that stores the actual measured times keyed by action type.
• FND_CONCURRENT_PROGRAMS / FND_CONCURRENT_REQUESTS — joined on PROGRAM_ID, PROGRAM_APPLICATION_ID, and REQUEST_ID for audit tracing.
• OKS_ATT_PK — the named primary-key constraint underpinning the unique index OKS_ACTION_TIME_TYPES_U1.