Results for “retrieve_pwd_challenge”

8 results




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

Overview

PON_USER_PROFILE_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an OTHER API within the ETRM 12.2.2 repository. It is part of the Oracle Sourcing (PON) product family and provides the user profile management layer used by Oracle Sourcing to authenticate users, maintain profile attributes, and synchronize user data between the E-Business Suite FND_USER repository and the Oracle Trading Community Architecture (TCA) and Human Resources person model. The package is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 environments.

Functionally, PON_USER_PROFILE_PKG sits between the Sourcing application and the foundational user tables. It encapsulates the logic required to register, retrieve, update, and remove sourcing users, including supplier-facing users whose identities are derived from TCA parties and contacts, and internal enterprise users sourced from HR person records. It also centralizes password and password-challenge handling, which supports secure login flows for Sourcing and its associated negotiation and sourcing workspaces.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions within the package. Their purposes are as follows:

  • UPDATE_USER_LANG — Updates the preferred language setting for a sourcing user record.
  • UPDATE_USER_INFO — Persists changes to a user's profile attributes.
  • RETRIEVE_VENDOR_USER_INFO — Returns profile information for a supplier or vendor user by resolving the associated TCA party, contact, and site records.
  • RETRIEVE_ENTERPRISE_USER_INFO — Returns profile information for an internal enterprise user, drawing on HR person data.
  • RETRIEVE_USER_INFO — Returns general user profile information, serving as the common retrieval entry point.
  • CHANGE_PASSWORD — Updates a user's password following validation of the change request.
  • LOGIN — Authenticates a sourcing user, validating credentials before establishing the session context.
  • DELETE_USER — Removes a user's sourcing profile.
  • RETRIEVE_PWD_CHALLENGE — Retrieves the password challenge (security question) associated with a user.
  • UPDATE_PWD_CHALLENGE — Sets or updates the password challenge for a user.
  • RETRIEVE_USER_DATA — Returns the user data payload required by the Sourcing application for profile display and processing.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • FND_USER — The foundation user repository; stores login name, encrypted password, and user status.
  • PER_ALL_PEOPLE_F — The HR person datastore used to identify internal enterprise users and their effective-dated attributes.
  • PER_PHONES — Stores telephone details associated with HR person records.
  • HZ_PARTIES — The TCA party master, providing the identity of supplier-side individuals and organizations.
  • HZ_PARTY_SITES — Links parties to sites, supporting location-aware supplier user resolution.
  • HZ_CONTACT_POINTS — Stores contact point data such as email and phone for TCA parties.
  • HZ_PERSON_PROFILES — Holds person-level profile attributes for TCA persons.

Together these tables allow the package to distinguish enterprise users (FND_USER and PER tables) from supplier users (FND_USER plus TCA HZ tables) and to return a unified profile representation.

Usage Notes

PON_USER_PROFILE_PKG is referenced by PON_SOURCING_USER_MANAGER_PKG, which acts as the higher-level manager for sourcing user operations, and by itself for internal recursion of shared logic. It does not appear as a dependency of general application frameworks, confirming its role as a Sourcing-specific utility rather than a global user API (the global equivalent being FND_USER_PKG).

Typical invocation occurs from Oracle Sourcing application flows—login pages, supplier registration, profile maintenance, and password management screens—rather than from standalone concurrent programs. Customizations that need to authenticate or provision sourcing users should call PON_USER_PROFILE_PKG procedures instead of modifying FND_USER directly, because the package also maintains the TCA and HR-related profile data that Sourcing relies upon. Direct DML against the underlying tables bypasses this synchronization and is not supported.