Results for “msc_get_profile”

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

Overview

The APPS.MSC_GET_PROFILE package is a utility package within the Oracle E-Business Suite (EBS) applications schema, distributed with the Advanced Supply Chain Planning (ASCP) module. Its purpose is to extract the runtime configuration of Oracle EBS profile options and write those values to an external file, giving administrators and implementers a portable snapshot of the current profile settings for a given user, responsibility, or application context. The package belongs to the MSC product prefix, which identifies the Oracle Supply Chain Planning family of database objects.

The package specification was last revised under header MSCPROFS.pls 115.1 (dated 2004/05/21), indicating it is a long-standing utility that has been carried forward from earlier EBS releases into both 12.1.1 and 12.2.2. It is classified as an OTHER API rather than a business API or public interface, which confirms that it is intended for internal or diagnostic use rather than for transactional integration by customers.

The user search term g_conc_error maps directly to a global constant declared in this package specification. It represents the concurrent-program return status indicating that the concurrent manager encountered an execution error. The package exposes four such constants that standardize return codes for concurrent program integration.

Key Procedures and Functions

The package exposes a single documented procedure, GETPROF. A set of public constants is declared alongside it and is visible to any calling program that references the package.

• GETPROF — The primary procedure of the package. It accepts an error buffer and return code as output parameters, together with a preference set name and optional user, application, and responsibility qualifiers, plus a schema name and target file name. The procedure resolves the applicable profile values and writes them to the designated file. It follows the standard concurrent program signature convention (ERRBUF, RETCODE) so it can be registered directly as a concurrent executable.
• G_CONC_ERROR (CONSTANT NUMBER := 3) — The return code signifying that an unhandled error occurred during concurrent program execution. This is the constant associated with the user's search term.
• G_SUCCESS (CONSTANT NUMBER := 0) — Indicates successful completion.
• G_WARNING (CONSTANT NUMBER := 1) — Indicates completion with warnings.
• G_ERROR (CONSTANT NUMBER := 2) — Indicates a handled business or validation error.

Tables Accessed

The package references the following tables through APPS synonyms in order to resolve profile option definitions and current values:

• FND_PROFILE_OPTIONS — Supplies the registered profile option names and their attributes, allowing the procedure to enumerate and describe each setting it extracts.
• FND_PROFILE_OPTION_VALUES — Provides the actual values assigned at the site, application, responsibility, and user levels, which the procedure resolves into a single effective value.
• FND_APPLICATION — Resolves application identifiers used to qualify profile values at the application level.
• FND_USER — Resolves user identifiers when a user-specific context is requested via the usr_name parameter.
• V$PARAMETER — Reads database initialization parameter values, allowing the output file to record the database configuration alongside the EBS profile settings.
• UTL_FILE — The Oracle-supplied PL/SQL file I/O package used to open, write, and close the target output file.

Usage Notes

MSC_GET_PROFILE is typically registered as a concurrent program in the Advanced Supply Chain Planning responsibility, where the concurrent manager supplies the ERRBUF and RETCODE output parameters automatically. When invoked in that mode, the procedure follows the standard return code protocol defined by its constants: zero for success, one for warnings, two for handled errors, and three (G_CONC_ERROR) for unhandled exceptions.

Because it writes to a file via UTL_FILE, successful execution requires a valid directory path and that the database server process has operating system write privileges to that location. The p_file_name parameter must correspond to an accessible path, and the schema supplied in schema_name determines which profile option values are treated as the reference values during extraction. The package is not referenced by any other package, so it functions as a standalone utility rather than a shared library. It is typically used during implementation, upgrades, or troubleshooting to capture and compare profile settings across environments in EBS 12.1.1 and 12.2.2.