Results for “rs_group”

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

Overview

CS_AUDIT_OWNER_UPD_CON_PRG is a concurrent-program driver package within the Oracle E-Business Suite Customer Care (Service) schema, owned by APPS and classified as OTHER. Its business purpose is to detect and record changes to the ownership attributes of service incidents and their associated installed-base records. Specifically, the package audits transitions in the owning resource, resource type, and owning group (including group type) on incidents recorded in CS_INCIDENTS_ALL_B, correlating those incidents to the customer product and item instance records in CSI_ITEM_INSTANCES. The resulting audit trail is persisted in CS_INCIDENTS_AUDIT_B, providing the historical record that Service users and downstream reporting rely upon to determine when and how an incident changed hands between support resources, teams, or organizations.

The package follows the standard Oracle EBS parent/worker multi-process pattern. The parent entry point acts only as a scheduler, delegating actual processing to a set of parallel workers managed through AD_CONC_UTILS_PKG. This design allows large volumes of incident and installed-base data to be audited efficiently without a single long-running transaction.

Key Procedures and Functions

• CREATE_AUDIT_GEN_MANAGER — The concurrent-program parent. It is the entry point registered against the concurrent program definition and is responsible for spawning the worker processes. It does not perform any audit logic itself; it invokes AD_CONC_UTILS_PKG.submit_subrequests to launch the worker program (identified by the application short name 'CS' and the worker concurrent program name 'CSSRAWGEN'), passing a batch size of 1000 rows and a worker count of 3. It returns the standard concurrent error buffer and return code to the concurrent manager.
• CREATE_AUDIT_GEN_WORKER — The parallel worker that performs the substantive audit processing. It receives the batch size, worker identifier, and total worker count so that each worker can claim a distinct slice of the eligible data range. It declares extensive collection-based working storage, including numeric, ROWID, and VARCHAR2 associative arrays, to buffer the audit comparison sets in bulk. A driving cursor (c_all_audit_cs) selects candidate incident records for evaluation. The procedure compares the current owning resource, owning resource type, owning group, and group type against their prior values and records an audit row when a change is detected, using the update entity code and update entity identifier columns to attribute the change.

Tables Accessed

• CS_INCIDENTS_ALL_B — The base incident table. The package reads current incident ownership columns and updates or tracks ownership state as part of the audit sweep.
• CS_INCIDENTS_AUDIT_B — The incident audit table. This is the principal write target: change rows for owning resource, resource type, group, and group type are inserted here.
• CS_INCIDENT_TYPES_B — The incident type reference table, used to resolve and validate incident type context during processing.
• CSI_ITEM_INSTANCES — The installed-base item instance table. It links incidents to the customer product instance whose ownership is being audited.
• MTL_PARAMETERS — The inventory organization parameters table, accessed to resolve the master and inventory organization identifiers relevant to the affected item instances.
• PLITBLM — The standard Oracle Applications PL/SQL index-by table of numbers (the "name-value" numeric collection type) used as a bulk-bind or lookup buffer utility within the package.

Usage Notes

This package is invoked exclusively through the concurrent manager as a registered concurrent program; it is not exposed as a form-level API and is not referenced by any other package in the ETRM repository. Administrators or integrators schedule it when audit history for incident ownership must be generated or backfilled, for example after ownership reassignments or data migration. Because processing is split into three parallel workers with a 1000-row batch size, runtime scales with incident volume and the number of eligible records. The worker program identified as CSSRAWGEN must be registered and enabled in the CS application for the parent to succeed. Users searching on the term "rs_team" typically arrive here in the context of resource-team ownership changes; note that this package captures ownership transitions on incidents rather than maintaining resource team definitions themselves.