Search Results concurrent




Overview
Explore in AI Chat

Overview

MRPRPPIT is an Oracle Reports–based concurrent program owned by the MRP - Master Scheduling/MRP product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The program is documented in ETRM under the user-facing name Financial Analysis Report, with the executable described as Inventory Turns Report. This dual naming reflects the program's placement in the inventory and financial analysis reporting stream within the Master Scheduling/MRP module. The program is enabled in the documented 12.2.2 metadata, confirming it remains available for submission against a valid MRP responsibility in both the 12.1.1 and 12.2.2 releases.

Functionally, MRPRPPIT supports inventory turns analysis — a measure of how efficiently inventory is converted into throughput over a defined period. Inventory turns reporting draws on on-hand balances, issue and receipt activity, and cost information to compute turnover ratios for planners and supply chain analysts. The "Financial Analysis Report" naming indicates the output is oriented toward financial and operational review rather than transactional replenishment, complementing the planning output generated by the MRP and MPS engines.

Execution Details

The ETRM metadata records the following execution attributes:

  • Concurrent Program: MRPRPPIT
  • Product: MRP - Master Scheduling/MRP
  • User-Facing Name: Financial Analysis Report
  • Description: Financial Analysis Report / Inventory Turns Report
  • Enabled: Yes
  • Execution Method: Oracle Reports
  • Argument Method: Standard
  • Executable: INVENTORY
  • Execution Filename: MRPRPPIT

Because the execution method is Oracle Reports, the program is implemented as an .rdf report definition registered against the MRP executable INVENTORY, with MRPRPPIT serving as the execution file name. The Standard argument method means the report's parameters are defined as ordinary concurrent program arguments rather than through a specialized argument framework such as a PL/SQL or host-based token set.

How to Run

MRPRPPIT is submitted through the standard Oracle EBS Submit Request (SRS) window. Users navigate to Requests > Run from an MRP or related responsibility, query the program by its user-facing name (Financial Analysis Report) or by the short name MRPRPPIT, and enter the required report arguments. Because the argument method is Standard, parameters appear as a conventional list of report parameters at submission time.

Typical parameter guidance for an inventory turns report of this type includes:

  • Organization / Organization Code: Restricts the report to a specific inventory organization or set of organizations.
  • Period or Date Range: Defines the window over which turns are calculated — commonly a fiscal period name or from/to date pair.
  • Category Set and Category: Filters items by inventory category for segment-level analysis.
  • Item Range: Limits output to a defined item range where supported.
  • Cost Type or Cost Group: Determines the valuation basis used in the turns calculation.

After submission, the request is processed by the Concurrent Manager and the Oracle Reports output can be reviewed via View > Requests or exported through the standard report viewer.

Related Objects

MRPRPPIT sits within the broader MRP and inventory analytics landscape. Commonly associated objects include:

  • MRP Executables: Other reports registered under the INVENTORY executable family within the MRP product.
  • Inventory Interface and Planning Tables: On-hand quantity and transaction history tables that supply source data for turns calculations.
  • MRP/MPS Planning Reports: Reports such as the MRP Plan and Exceptions reports, which are frequently run alongside financial analysis output for a complete planning picture.
  • Concurrent Manager: The standard submission and monitoring infrastructure used to run and schedule the program.
  • FND Request Tables: FND_CONCURRENT_REQUESTS and related views, used to track submission history and output.

Because ETRM documentation for MRPRPPIT is limited to metadata, the exact parameter list and output layout should be confirmed against the installed report definition in the target environment. The documented facts — product ownership, execution method, executable name, and enabled status — remain consistent across 12.1.1 and 12.2.2.