Search Results csp_rs_cust_relations_pkg




Overview
Explore in AI Chat

Overview

CSP_RS_CUST_RELATIONS_PKG is an Oracle EBS Applications (APPS) PL/SQL package that maintains the relationship between field service resources and customers. In the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this package resides in the CSP (Customer Support / Field Service) product family and is defined with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than its owner.

The package header, identified by the revision marker csptrcrs.pls 115.5, exposes a set of low-level data manipulation routines corresponding to the CSP_RS_CUST_RELATIONS entity. The "RS" prefix denotes the resource side of the relationship (that is, a service resource such as a field service engineer or technician), while CUST_RELATIONS denotes the customer association. The package therefore acts as the data-access layer that records which resources are linked to which customers, supporting the assignment and management of service personnel against customer accounts.

The metadata classifies this object under API classification OTHER, indicating that it is not a public, business-level API intended for unrestricted external calls, but rather a table-maintenance or internal access package used by other Application Technology components and forms.

Key Procedures and Functions

The ETRM metadata documents four procedures in this package. Their purposes are consistent with standard Oracle Forms-generated table handler packages:

  • Insert_Row — Creates a new row in the CSP_RS_CUST_RELATIONS table, populating the relationship between a resource and a customer along with the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the fifteen descriptive ATTRIBUTE columns. The primary key RS_CUST_RELATION_ID is passed as an IN OUT NOCOPY parameter, allowing the sequence-generated identifier to be returned to the caller.
  • Update_Row — Modifies an existing relationship record, accepting the RS_CUST_RELATION_ID as the key and updating the resource, customer, audit, and attribute columns.
  • Lock_Row — Acquires a row-level lock on the specified relationship record to support optimistic concurrency control, typically used by Oracle Forms during update processing to prevent conflicting modifications.
  • Delete_Row — Removes the specified resource-to-customer relationship record from the underlying table.

No parameter lists are invented here; the parameter structure follows the columns of the CSP_RS_CUST_RELATIONS table, with the identifier parameter being IN OUT NOCOPY on insert and a required key on the other operations.

Tables Accessed

The package operates against two documented objects referenced through APPS synonyms:

  • CSP_RS_CUST_RELATIONS — The base table storing resource-to-customer relationship rows. The insert, update, lock, and delete operations all target this table directly.
  • CSP_RS_CUST_RELATIONS_S1 — The associated unique index (or sequence-related object) supporting the primary key RS_CUST_RELATION_ID. Its presence indicates that the identifier is enforced as a unique access path during insert and lookup operations.

The WHO columns confirm that the package participates in Oracle's standard audit trail mechanism, allowing change tracking through the EBS application auditing framework.

Usage Notes

Because the package is classified as OTHER rather than a public API, it is typically invoked indirectly. The most common callers are Oracle Forms modules built on the CSP_RS_CUST_RELATIONS block, which use the Insert_Row, Update_Row, Lock_Row, and Delete_Row procedures to persist user changes. The ETRM metadata notes that this package is referenced by two other packages, indicating layered internal dependencies within the Customer Support schemas.

Custom development should avoid calling this package directly unless the caller can safely supply the full set of WHO and attribute values; using the supported business APIs or forms is preferred. When invoked from custom code, callers must ensure the sequence value for RS_CUST_RELATION_ID is supplied and that the WHO columns are populated to avoid audit inconsistencies. Given its AUTHID CURRENT_USER definition, execute privileges must be granted explicitly to any schema that invokes it. The package is present in both 12.1.1 and 12.2.2, where the EBS schema and synonym structure remain consistent, so no version-specific differences apply beyond standard EBS 12.2 online patching considerations.