Search Results initialization_error

Overview

APPS.RCI_UNMTG_RISKS_ETL_PKG is a risk-management extract, transform, and load (ETL) package within the Oracle E-Business Suite environment. Its name reflects its role in processing unmitigated risks data for the Enterprise Risk Management / Risk Management (RCI) application family, which in Release 12.1.1 and 12.2.2 forms part of the broader governance, risk, and compliance solution set. The package is responsible for populating and maintaining the risk certification staging and reporting structures used by downstream risk dashboards and certifications.

The package is owned by APPS and is classified as OTHER in the ETRM documentation, indicating it is an internal processing package rather than a published, customer-facing API. It supports both full (initial) and incremental loading strategies, which is a common pattern for data warehouse-style loads feeding risk analytics.

Key Procedures and Functions

The package body exposes six documented procedures and one function (seven total callable units):

• INITIAL_LOAD — Performs the full, first-time load of unmitigated risks data. It is typically executed during initial implementation or when a complete refresh of the risk data set is required.
• INITIAL_LOAD_OBSOLETE — A retained but superseded version of the initial load routine, kept for backward compatibility and historical reference. New development should not invoke this procedure.
• INCR_LOAD — Performs the incremental load, processing only records changed or created since the last successful run. This is the routine intended for recurring scheduled execution.
• INCR_LOAD_OBSOLETE — A retained but superseded version of the incremental load routine, preserved for backward compatibility.
• GET_LAST_RUN_DATE — A function that returns the date of the last successful execution, used to establish the processing window for incremental loads.
• ERR_MESG — A utility procedure that formats and returns error messages to the concurrent manager log and output buffer.
• CHECK_INITIAL_LOAD_SETUP — Validates prerequisite setup before an initial load executes. As shown in the source, it retrieves the global start date via BIS_COMMON_PARAMETERS.GET_GLOBAL_START_DATE and resolves the RCI schema using FND_INSTALLATION.GET_APP_INFO ('AMW', …). If the global start date is null or the schema cannot be resolved, it raises INITIALIZATION_ERROR.

The body declares INITIALIZATION_ERROR EXCEPTION with PRAGMA EXCEPTION_INIT (INITIALIZATION_ERROR, -20900) and the message 'Error in Global setup'. This is the source of the "initialization_error" term associated with this object: when the required global setup (global start date, RCI/AMW schema registration) is missing or invalid, this exception is raised and propagated as concurrent manager error -20900.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• AMW_ACCT_ASSOCIATIONS, AMW_RISK_ASSOCIATIONS, AMW_EXECUTION_SCOPE, AMW_FIN_PROC_CERT_RELAN — Risk-to-account, risk, execution scope, and financial process certification relationship data that define the risk model being extracted.
• AMW_CERTIFICATION_B / AMW_CERTIFICATION_TL — Certification base and translated (TL) tables supplying certification content and descriptions.
• HR_ALL_ORGANIZATION_UNITS / HR_ALL_ORGANIZATION_UNITS_TL — Organization definitions and their translations, used to scope risk data by operating unit or organization.
• MTL_PARAMETERS — Inventory organization parameters, primarily to resolve the master organization identifier referenced by get_master_organization_id.
• RCI_DR_INC — The RCI incremental staging/driver table used to track changed records.
• RCI_ORG_CERT_RISKS_F — The fact table storing organization-level certified risk records produced by the load.

Usage Notes

RCI_UNMTG_RISKS_ETL_PKG is invoked exclusively by concurrent programs rather than from forms, and it is not referenced by any other PL/SQL package (referenced by 0 other packages). DBAs and functional administrators schedule INITIAL_LOAD once during implementation, then schedule INCR_LOAD on a recurring basis (typically nightly). Because CHECK_INITIAL_LOAD_SETUP depends on BIS_COMMON_PARAMETERS.GET_GLOBAL_START_DATE and FND_INSTALLATION.GET_APP_INFO for the AMW application, the -20900 initialization_error is most commonly encountered when the Global Start Date profile/setup is null or the AMW product is not correctly registered in the instance. Remediation consists of confirming the global start date setup and verifying AMW installation registration before re-running the concurrent request.