Search Results csi_assign_role_pub




Overview
Explore in AI Chat

Overview

APP.CSI_ASSIGN_ROLE_PUB is a public PL/SQL API within the Oracle E-Business Suite that governs the assignment of roles to users within the context of the CSI (Customer Support and Installed Base) product family. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than the definer, which is consistent with controlled, caller-context security for administrative operations. Its version header (120.0, dated 2006) and the "noship" designation indicate it is an internal, non-shipped utility rather than a customer-facing integration point. Because the package is classified as PUB, Oracle documents its interface as a stable, callable entry point, though it remains a supporting infrastructure component rather than a primary business API. Its central purpose is to reconcile and provision role assignments by bridging Oracle EBS user and responsibility data with the JTF (Java Toolkit Foundation) authorization model that governs principals and role mappings. In release 12.1.1 and 12.2.2, this package is particularly relevant where role-based authorization must be synchronized between the FND application security layer and the JTF principal framework. A search for "role_assignment" surfaces this package because its single documented procedure carries that exact name.

Key Procedures and Functions

The package exposes one documented procedure, ROLE_ASSIGNMENT. It is a standard concurrent-program entry point, indicated by its conventional signature: a pair of OUT NOCOPY parameters—one returning an error buffer and one returning a completion code—matching the EBS concurrent manager calling convention. The procedure performs the bulk role-assignment processing for its governing business event; it does not return values to a caller beyond the status convention.

  • ROLE_ASSIGNMENT — Executes the assignment of roles to the appropriate principals, writing status and error text into the standard concurrent output parameters. No parameter list beyond the documented error buffer and return code should be assumed; the ETRM metadata documents no additional arguments.

Tables Accessed

The ETRM metadata records five referenced tables, all accessed through APPS synonyms, which reflects the package's role as an orchestration layer across multiple schemas.

  • CSI_INSTALL_PARAMETERS — Supplies CSI-level configuration and installation parameters that control processing behavior for the role assignment routine.
  • FND_USER — The Oracle EBS user repository; provides the user records to which roles are being assigned or reconciled.
  • FND_RESPONSIBILITY — Defines the responsibilities available in the application; these form the source of role definitions to be mapped.
  • JTF_AUTH_PRINCIPALS_B — Stores the JTF authorization principals, the base entity against which roles are assigned.
  • JTF_AUTH_PRINCIPAL_MAPS — Holds the principal mappings that link principals to their assigned authorization roles; this is the primary target of the procedure's write activity.

Usage Notes

Because ROLE_ASSIGNMENT follows the concurrent program parameter convention (error buffer and return code), it is designed to be registered and launched as a concurrent program rather than called interactively. It may also be invoked from custom PL/SQL code that requires role provisioning or reconciliation, though the "noship" status means Oracle does not guarantee the interface for external use and reserves the right to change it. It is not referenced by any other documented package, so callers are limited to concurrent program registrations, forms-level logic, or bespoke extensions. The AUTHID CURRENT_USER declaration requires that the invoking user hold the necessary privileges on the referenced APPS-synonym objects. Before relying on this package, implementers should confirm it exists and is accessible in the target instance, since its noship classification may result in differing availability across 12.1.1 and 12.2.2 environments.