Search Results financials_system_parameters




Overview
Explore in AI Chat

Overview

The concurrent program POMRCUPG, presented to users as MRC Setup - Purchasing Transactions Upgrade, is a Purchasing (PO) module utility within Oracle E-Business Suite 12.1.1 and 12.2.2. Its role is to support the Multiple Reporting Currencies (MRC) feature by upgrading and populating MRC-related columns on Purchasing transaction data. The program belongs to the PO - Purchasing product and is part of the broader MRC setup and migration toolchain.

According to the ETRM metadata, the program is currently documented as not enabled (Enabled: No). This is an important operational characteristic: although the executable and concurrent program definitions exist in the environment, the program is not exposed for normal submission and is typically invoked only during specific MRC implementation, upgrade, or migration activities, or selectively as part of a controlled support procedure. The user-facing name and the underlying "POMRCUPG" short name confirm its association with Purchasing MRC upgrade processing.

Execution Details

The documented execution method is PL/SQL Stored Procedure, with a Standard argument method. This indicates the program is not a Java or host-based executable but a database-stored procedure invoked through the concurrent manager. The ETRM metadata does not supply a clear executable name or execution file name in the provided excerpt, so the effective call is governed by the concurrent program definition registered in the Purchasing application.

Because the program is a PL/SQL stored procedure, it executes within the database session managed by the concurrent manager and inherits the standard concurrent processing framework behaviors, including request logging and completion status reporting. Its disabled status means the definition may need to be enabled in the Concurrent Programs form before submission where a controlled run is required.

How to Run

When active, the program is submitted through the standard Submit Request (SRS) window in the Purchasing responsibility, or programmatically via the concurrent manager. The metadata explicitly states that the program is run separately for each table. This means a complete upgrade of Purchasing MRC data generally requires multiple submissions, each targeting one table rather than a single consolidated run.

The request set arguments reveal two principal parameters. ATTRIBUTE1 identifies the target table, with documented values including PO_HEADERS_ALL, PO_DISTRIBUTIONS_ALL, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS, RCV_RECEIVING_SUB_LEDGER, and RCV_SUB_LEDGER_DETAILS. ATTRIBUTE2 supplies the primary set of books name, defaulted through the query:

This default resolves the primary (P) MRC set of books via FINANCIALS_SYSTEM_PARAMETERS, the very object the user searched for. The dependence on FINANCIALS_SYSTEM_PARAMETERS means a correctly configured primary set of books is a prerequisite for submission.

Related Objects

The program directly touches the core Purchasing and Receiving transaction tables listed as ATTRIBUTE1 values, including PO_HEADERS_ALL, PO_DISTRIBUTIONS_ALL, RCV_TRANSACTIONS, and the receiving sub-ledger tables. It relies on GL_SETS_OF_BOOKS and FINANCIALS_SYSTEM_PARAMETERS for parameter defaulting. Related setup objects include MRC sets of books definitions and the Purchasing MRC upgrade request set. Administrators should verify these prerequisites and run the program table by table when performing MRC-related data preparation.