Results for “new_resolution_code”

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

Overview

CS_SR_ACTION_CODES_B is the base definition table for all service request (SR) action codes within the Oracle E-Business Suite Service (CS) module. It resides in the CS schema and serves as the authoritative registry of discrete actions that can be executed against a service request, such as status transitions, notification dispatches, or resolution assignments. Applications in the TeleService and field service flows reference this table to determine which actions are valid, when they are active, and what downstream effect each action triggers. In the documented ETRM 12.2.2 physical schema, the table contains 16 columns and is owned by the CS schema with a VALID status.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is best modeled as hub-leaning. This is a modeling suggestion rather than a mandated construct: ACTION_CODE functions as the natural business key that anchors the hub, while the two inbound foreign keys from CS_SR_ACTION_DETAILS and CS_SR_EVENT_ACTIONS behave as link and satellite dependencies. Modelers following a Data Vault approach would treat CS_SR_ACTION_CODES_B as the central hub of action definitions, with edition-sensitive attributes captured in a satellite keyed by ACTION_CODE and ZD_EDITION_NAME.

Key Information Stored

The table's documented columns capture both the identity of each action and its behavioral configuration. The most significant attributes are:

• ACTION_CODE — the primary key and the business identifier for each action definition; every downstream reference resolves to this value.
• ZD_EDITION_NAME — the edition discriminator supporting multi-edition (Online Patching / EBR) deployment in 12.2.2.
• NEW_STATUS — the service request status the action transitions the SR into upon execution.
• NEW_RESOLUTION_CODE — the resolution code applied when the action completes.
• NOTIFICATION_TEMPLATE_NAME — the notification template triggered by the action.
• RELATIONSHIP_TYPE — the relationship context in which the action applies.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective dating window controlling when the action is selectable.
• SEEDED_FLAG — indicates whether the row is shipped by Oracle or customer-defined.
• APPLICATION_ID — the owning application identifier.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the ORM layer.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

The surrogate primary key is defined by CS_SR_ACTION_CODES_B_PK on ACTION_CODE. The documented unique index CS_SR_ACTION_CODES_B_U1 spans (ACTION_CODE, ZD_EDITION_NAME), confirming that the business-key candidate is edition-scoped — the same action code may exist once per edition.

Common Use Cases and Queries

Typical usage centers on validating which actions are available for a given SR and tracing the effect of an action through its status and resolution mappings. A common reporting pattern joins the base table to its detail and event-action children to produce an action catalog:

• Lov/validation queries filtering on START_DATE_ACTIVE and END_DATE_ACTIVE to return only currently effective actions.
• Administrative reports distinguishing Oracle-seeded rows (SEEDED_FLAG) from custom action definitions.
• Integration extracts enumerating ACTION_CODE, NEW_STATUS, and NEW_RESOLUTION_CODE to replicate SR lifecycle rules into external workflow engines.
• Audit queries using OBJECT_VERSION_NUMBER and the audit columns to detect concurrent modifications.

A representative query selecting effective actions is: SELECT action_code, new_status, new_resolution_code FROM cs_sr_action_codes_b WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE) AND zd_edition_name = 'SET1';

Related Objects

CS_SR_ACTION_CODES_B is referenced by two documented child tables and is consumed by the broader SR action framework:

• CS_SR_ACTION_DETAILS — joins on ACTION_CODE; holds the per-action detail rows that further qualify the action definition.
• CS_SR_EVENT_ACTIONS — joins on ACTION_CODE; maps actions to service request events, driving event-triggered automation.
• CS_SR_ACTION_CODES_TL — the translation table supplying language-specific action names and descriptions (conventional companion to the _B table).
• CS_SR_ACTION_CODES_B_PK / CS_SR_ACTION_CODES_B_U1 — the constraints enforcing identity and edition uniqueness.

Because both foreign keys originate in child tables and point inward to ACTION_CODE, this object sits at the top of the action-definition hierarchy and must be treated as the reference (hub) record when performing joins, ensuring that detail and event-action rows are interpreted against the correct action semantics.