Results for “sun_duration”

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

Overview

OKS_ACTION_TIMES is a Service Contracts (OKS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM metadata, its stated purpose is to "store Reaction/Resolution times" associated with service contract coverage actions. Reaction time typically denotes the interval between the logging of a service request and the first vendor response; resolution time denotes the interval between logging and final closure. By persisting these durations at the row level, the table supports service level agreement (SLA) definitions and the entitlement logic that Service Contracts applies when validating contractual commitments.

From a modeling perspective, the ETRM heuristic Data Vault classification for this table is standalone, mined from its foreign-key structure. This classification is a modeling suggestion rather than a normative statement: the object does not participate in the dense hub-and-link web typical of transactional schemas, and it carries a single outward reference to FND_SECURITY_GROUPS. The physical schema in 12.2.2 documents 23 columns in the OKS schema, with the object status recorded as VALID.

Key Information Stored

The most significant columns documented for OKS_ACTION_TIMES are:

• ID — surrogate primary key, enforced by the constraint OKS_AT_PK and by the unique index OKS_ACTION_TIMES_U1. It is the sole documented business-key candidate.
• COV_ACTION_TYPE_ID — identifies the coverage action type whose reaction or resolution timing is being defined.
• CLE_ID — reference to the coverage/entitlement line element against which the timing applies.
• DNZ_CHR_ID — reference to the denormalized contract header identifier, enabling efficient contract-level retrieval without traversing child structures.
• UOM_CODE — unit of measure governing interpretation of the duration values (for example, hours or days), drawn from the standard EBS unit-of-measure set.
• SUN_DURATION, MON_DURATION, TUE_DURATION, WED_DURATION, THU_DURATION, FRI_DURATION, SAT_DURATION — seven day-of-week duration columns that store the permitted time allowance per weekday. This day-specific granularity lets implementers model business calendars where reaction and resolution obligations differ between working days and weekends.
• SECURITY_GROUP_ID — the only documented foreign key, referencing FND_SECURITY_GROUPS; it enforces multi-tenant data segregation through Oracle's security group mechanism.
• Standard WHO/audit and concurrency columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID. The presence of the PROGRAM_* and REQUEST_ID set indicates the rows are commonly populated by concurrent programs, and OBJECT_VERSION_NUMBER supports optimistic locking in the OA Framework.

The seven weekday columns distinguish this table from a simple duration attribute: reaction and resolution policy is expressed as a weekly schedule rather than a single scalar value.

Common Use Cases and Queries

Typical use cases include verifying that a contract's SLA definition includes reaction and resolution times for each covered action type, reporting the distribution of timing policies across active contracts, and validating that durations are consistent with the referenced unit of measure and security group.

Representative query patterns:

• Retrieve timing rows for a contract: SELECT id, cov_action_type_id, cle_id, uom_code, sun_duration, mon_duration FROM oks_action_times WHERE dnz_chr_id = :contract_id.
• Join to the security group: SELECT a.id, g.security_group_id FROM oks_action_times a, fnd_security_groups g WHERE a.security_group_id = g.security_group_id.
• Audit program loads: SELECT id, program_id, request_id, creation_date FROM oks_action_times WHERE request_id = :concurrent_request_id, which is useful for tracing rows inserted by Service Contracts concurrent processes.

Because the table is classified as standalone and exposes no documented child references, reporting is generally driven from the contract or coverage side of the model. Implementations that do not configure weekday-specific reaction or resolution policies may find the table sparsely populated, making a row-count check a useful first step before building dependant reports.

Related Objects

The FK metadata documents one direct dependency:

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs row visibility by security group.

Additional context objects, inferred from the column semantics and the OKS module structure rather than from documented FK constraints, include:

• OKS_ACTION_TYPES — referenced logically by COV_ACTION_TYPE_ID; supplies the action type definition.
• OKS_COVERED_LEVEL_ELEMENTS (or the equivalent OKS coverage line element object) — referenced logically by CLE_ID.
• OKS_CONTRACTS / OKS_CHR — the contract header correlated by DNZ_CHR_ID.
• FND_UNITS_OF_MEASURE — resolves UOM_CODE to a descriptive unit of measure.
• FND_CONCURRENT_REQUESTS — joins on REQUEST_ID to attribute row creation to a specific concurrent request.

These inferred relationships should be confirmed against the actual database constraints in the target environment before being relied upon in production SQL, since the ETRM metadata records only the SECURITY_GROUP_ID foreign key as documented.