Search Results fnd_vault

Overview

The concurrent program FND_VAULT_REKEY is owned by the FND — Application Object Library product, the foundational module in Oracle E-Business Suite that supplies shared security, configuration, and infrastructure services across all applications. Its user-facing name is FND_VAULT Rekey, and it is enabled by default in the documented ETRM 12.2.2 metadata.

The program relates to the Oracle Applications Vault, the underlying security component that stores and protects sensitive credentials — most notably database connection passwords used by application-tier services, concurrent managers, and WebLogic data sources. Rather than persisting such secrets in clear text, the Vault encrypts them under a key issued and maintained by the application. The FND_VAULT Rekey program performs a controlled re-encryption of Vault-stored secrets, generating a new encryption key and re-securing the stored values under that key. Organizations typically invoke it as part of periodic cryptographic key rotation, following security policy requirements, or when complying with audit mandates that require the periodic replacement of encryption keys protecting privileged credentials.

Execution Details

The documented execution characteristics are as follows:

• Product: FND — Application Object Library
• User-facing name: FND_VAULT Rekey
• Enabled: Yes
• Execution Method: PL/SQL Stored Procedure
• Argument Method: Standard
• Executable: FND_VAULT_REKEY
• Execution Filename: fnd_vault.rekey_concurrent

Because the execution method is PL/SQL Stored Procedure, the program runs entirely within the database tier and does not spawn an external executable, shell script, or Java class. The entry point is the packaged procedure FND_VAULT.REKEY_CONCURRENT, called by the concurrent manager under the FND_VAULT_REKEY executable definition. No executable file path, subroutine, or host-level component is involved. The standard argument method means parameter entry uses the conventional Oracle SRS parameter window, though the documented metadata does not enumerate specific parameters; in practice this program is generally submitted with no user arguments.

How to Run

Users submit FND_VAULT_REKEY through the standard Submit Request (SRS) flow: Requests → Run in the EBS navigation, selecting the request name FND_VAULT Rekey from the list of available concurrent programs. Because the executable belongs to the FND product, the program is visible to appropriately authorized users without additional menu configuration beyond standard concurrent program security.

Operational guidance:

• Because it manipulates Vault encryption state, run it during a planned maintenance window or low-activity period, and confirm that no dependent services are mid-operation.
• Verify backups of the relevant FND tables and the applications configuration before execution.
• Review the concurrent request log and output for completion status; a rekey operation must complete successfully to avoid credential inconsistency.
• Confirm that the new key is recognized by application-tier services afterward, particularly WebLogic data sources and the concurrent manager environment.

Related Objects

The program operates against the Oracle Applications Vault schema objects and supporting FND tables that persist encrypted credentials and encryption key material. Directly associated components include the FND_VAULT package (which supplies the REKEY_CONCURRENT entry point) and the view or table family that stores Vault entries. Related administrative activities include managing the applications database password and configuring data source credentials through Oracle Applications Manager. No interface tables or Oracle Reports outputs are documented for this program; it is an internal maintenance routine rather than a data-integration or reporting concurrent program.