Search Results delete_user

Overview

APPS.CSL_USER_PKG is a PL/SQL package in Oracle E-Business Suite that manages user provisioning for the Converged Self-Service/TeleService resource model. Its name prefix, "CSL," identifies it as part of the Customer Support/Service (formerly TeleService/CS) family of modules, and its header comment indicates it originated in the field service or TeleService diagnostics area of the application (source version 115.3, dated 2002). The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling schema rather than the definer, which is a common pattern for packages invoked from self-service or resource-facing contexts where the effective user matters for row-level access.

The package exposes only two procedures, CREATE_USER and DELETE_USER, indicating a narrow, purpose-built scope: synchronizing an EBS resource record with a corresponding application user account. It is classified in ETRM as an "OTHER" API rather than a public or private API, and it is referenced by one other package, confirming that it functions as a supporting utility rather than a primary integration point.

Key Procedures and Functions

• CREATE_USER — Accepts a resource identifier and returns a status indicator through an OUT parameter. It creates the user or user-linked resource entries required for that resource to operate within the CSL application context.
• DELETE_USER — Accepts the same resource identifier signature and an OUT return status. It removes the user association for the given resource, reversing the provisioning performed by CREATE_USER.

Both procedures take a resource ID as input and communicate outcome through x_return_status rather than exceptions, following the standard EBS API convention in which callers inspect the status string to determine success or failure. No other procedures or functions are documented for the package.

Tables Accessed

The package operates through APPS synonyms over a substantial set of CSL and HZ interface tables. The referenced tables fall into several functional groups:

• Party and contact data: CSL_HZ_PARTIES_ACC, CSL_HZ_PARTY_SITES_ACC, CSL_HZ_RELATIONSHIPS_ACC, CSL_HZ_CONTACT_POINTS_ACC, CSL_CS_HZ_SR_CONTACT_PTS_ACC, CSL_HZ_CUST_ACCT_SITES_ALL_ACC, CSL_HZ_CUST_SITE_USES_ALL_ACC, and CSL_HZ_LOCATIONS_ACC. These represent the TCA (Trading Community Architecture) party, location, and customer site records that identify the user being created or deleted.
• Service and task data: CSL_CS_INCIDENTS_ALL_ACC, CSL_JTF_TASKS_ACC, and CSL_JTF_TASK_ASS_ACC. These hold service requests, tasks, and task assignments associated with the resource, and are likely consulted to determine whether an existing user has active work before deletion.
• Contract and entitlement data: CSL_CONTR_BUSS_PROCESSES_ACC and CSL_CONTR_BUSS_TXN_TYPES_ACC, supporting service contract eligibility tied to the resource.
• Installed base and inventory: CSL_CSI_ITEM_INSTANCES_ACC and CSL_MTL_ONHAND_QTY_ACC, connecting the user to installed assets and on-hand quantities.

These "_ACC" suffixed synonyms are characteristic of the CSL "access" layer, which exposes summarized or security-relevant views of base tables to self-service code. Their presence indicates that the user lifecycle managed by this package is validated against the resource's full service footprint — parties, contacts, incidents, tasks, contracts, installed base, and inventory — before a create or delete is permitted to succeed.

Usage Notes

Because the package is invoked via a resource ID and returns status rather than throwing exceptions, it is typically called from other PL/SQL packages (consistent with the single documented referencing package) rather than directly from forms or concurrent programs. Typical invocation patterns include user-provisioning routines triggered when a service resource is onboarded or terminated, and cleanup logic executed when a resource is deactivated. Developers integrating with APPS.CSL_USER_PKG should treat both procedures as transactional units and check x_return_status after every call, committing or rolling back accordingly. Note that DELETE_USER removes the user association but, given the breadth of referenced tables, is expected to have already accounted for dependent service, contract, and installed base records; callers should confirm that no active incidents or tasks remain for the resource before invoking it. The package resides in APPS and should be referenced through that schema synonym in custom code.