Search Results p_email_address

Overview

FND_OAM_METALINK_CREDS is an Oracle E-Business Suite PL/SQL package body residing in the APPS schema, classified under the ETRM taxonomy as OTHER. Its functional purpose is to manage the storage and retrieval of Oracle MetaLink (now My Oracle Support) user credentials on behalf of Oracle Applications users. The package persists an association between an Applications user name and the corresponding external support-portal user identifier, password, and e-mail address, holding these values in a dedicated repository table so that other Oracle Applications Manager (OAM) components can authenticate against the support infrastructure on the user's behalf. In the EBS 12.1.1 and 12.2.2 file systems, the body is deployed from the AFOAMMCB.pls source member, originating from header revision 120.2 and marked noship, indicating it is an internal, non-shipped product used by the Oracle Applications Manager diagnostics and patching framework rather than part of the customer-facing functional API surface.

Key Procedures and Functions

The ETRM metadata documents three procedures within the package body:

• PUT_CREDENTIALS — Stores MetaLink credentials for a specified Applications user. Per the inline source documentation, the procedure accepts an Applications user name, a MetaLink user id, a MetaLink password, and an e-mail address. It resolves the Applications user to an internal USER_ID via FND_USER, encrypts the supplied password using the FND_CRYPTO utility with a randomly generated key, and returns an error message and return code through output parameters. If a credential row already exists for the given user, the procedure performs an update; otherwise it inserts a new row into FND_OAM_METALINK_CRED. A return code of zero signals success.
• GET_CREDENTIALS — Retrieves previously stored credentials for a given Applications user, reversing the encoding applied by PUT_CREDENTIALS so that the MetaLink user id and password can be supplied to downstream support-integration calls.
• TEST — A diagnostic routine used to validate the package and its supporting credential storage, typically exercised during patching or OAM self-test activities.

The excerpt additionally shows a private DBG_PRINT helper, which in the shipped version is reduced to a null statement, confirming that debug output is suppressed in production.

Tables Accessed

• FND_OAM_METALINK_CRED — The primary repository for encrypted MetaLink credential rows; the package inserts, updates, and selects against this table.
• FND_USER — Read to resolve an Applications user name to its internal USER_ID, which is enforced as the unique key for credential storage.
• UTL_RAW — Referenced for binary conversion of plaintext password data prior to encryption; the source notes that UTL_RAW.CAST_TO_RAW is used and cautions that the call should ideally convert the password to AL32UTF8 first to guard against database character set changes.

Usage Notes

FND_OAM_METALINK_CREDS is invoked indirectly through Oracle Applications Manager functionality rather than through a public API contract. Typical invocation points include OAM setup pages that capture My Oracle Support credentials, patch and diagnostics flows that require outbound authenticated access, and internal self-test routines that exercise the TEST procedure. The ETRM metadata records zero dependent packages, meaning no shipped EBS package references it directly, which reinforces its role as an internal utility. Because the source is marked noship and the header is dated 2005, customers should not call these procedures from custom code without verifying the signature in their specific 12.1.1 or 12.2.2 release. Any custom integration that does so must also respect the encryption scheme, since the stored password is stored in encoded form (Base64 over the concatenated key and ciphertext) and cannot be safely read or written by external processes without replicating the FND_CRYPTO logic.