Results for “create_role”

37 results




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

Overview

IGP_USER_GEN_001 is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the generic ETRM API category OTHER. Its documented purpose is to provide the facility to create an ad hoc user with a specified e-mail address, and to associate that ad hoc user with an ad hoc role. The package header carries the source control identifier $Header: IGSPUSAS.pls 120.0 2005/06/01 22:11:05 appldev noship $, indicating it belongs to the Internet Government Procurement (IGP) product family and that it was created by SMVK on 12-Feb-2004. The "noship" designation in the header reflects its original internal deployment status.

In the functional context of Oracle iProcurement and the IGP schema, this package supports the generation of transient or "ad hoc" users that participate in approval and role-based workflow routing without requiring full, persistent user provisioning in the standard application user tables. The creation of a role-and-user pair keyed to an external e-mail address allows workflow notifications and approvals to be delivered to recipients who are not otherwise defined as named application users.

Key Procedures and Functions

The package exposes two procedures, both declared in the package specification.

  • CREATE_ROLE — The primary functional entry point. It creates the ad hoc user and the associated ad hoc role, taking the role and user identifiers, their display values, and an e-mail address as inputs. The parameters p_adhoc_role, p_role_dsp, p_adhoc_user, and p_user_dsp are declared IN OUT NOCOPY, indicating that the procedure both consumes and returns these values, most likely generating or resolving identifiers during processing. The p_mail_address parameter carries the target e-mail address for the ad hoc user.
  • CHECK_ACTION — A workflow callback procedure. Its parameters itemtype, itemkey, actid, funcmode, and resultout follow the standard Oracle Workflow function activity signature, where funcmode selects the execution mode (for example, RUN or SET) and resultout returns the activity result. This procedure is designed to be registered as a Workflow function activity rather than called directly by application code.

Tables Accessed

The ETRM metadata excerpt for this object does not document any referenced tables via APPS synonyms, and the package is likewise recorded as referenced by zero other packages. Because the specification does not enumerate table dependencies, direct DML targets cannot be confirmed from the available documentation. Functionally, an ad hoc user and role generation utility of this type would be expected to write to IGP ad hoc user and role repository tables and to read from the underlying Workflow directory structures that hold role and user definitions, but no specific table names are attested in the metadata and none should be assumed.

Usage Notes

IGP_USER_GEN_001 is an internal utility package rather than a public integration API. Its typical invocation paths are:

  • Workflow function activities, through CHECK_ACTION, where the procedure is registered as the PL/SQL callback for a workflow node and invoked by the Workflow Engine with the standard itemtype/itemkey/actid/funcmode signature.
  • Internal iProcurement or IGP code paths that need to materialize an ad hoc role and user for a one-off approval or notification scenario, through a call to CREATE_ROLE.

Customizations should not call this package directly unless the surrounding ad hoc role and user lifecycle is fully understood, since the IN OUT NOCOPY parameters imply that the caller supplies and then consumes generated identifiers. The package should be treated as subject to change between releases; the 120.0 version stamp indicates it has been stable since 2005, and no dependencies from other packages were recorded in ETRM. Note that the user query referenced the term "กรมพัฒนาสั facebook," which is unrelated to this database object; that search term does not correspond to any documented element of APPS.IGP_USER_GEN_001 and has no bearing on its technical behavior.