Search Results preprocessing_lead_time




Overview
Explore in AI Chat

Overview

The view MRP_RHX_SAFETY_STOCK_V is an Oracle E-Business Suite Integration Toolkit view belonging to the MRP (Master Scheduling/MRP) product family. Its stated purpose is to expose information regarding the safety stock of planned items in a form suitable for external integration and reporting. In Oracle EBS 12.1.1 and 12.2.2, the Integration Toolkit (the RHX family of views) provides a supported, denormalized interface over core planning tables so that reporting tools, data warehouses, and third-party applications can retrieve planning data without directly querying transactional base tables.

Safety stock is a fundamental planning buffer that protects against demand and supply variability. This view returns the safety stock quantity for a planned item, together with the associated effectivity date and a set of lead-time attributes carried on the item. It is designed to be consumed by integration processes rather than interactive forms, and the metadata notes that it is not implemented as a seeded database object in all environments, meaning availability depends on whether the Integration Toolkit components have been deployed.

Underlying Base Objects

The documented view text defines the object over two sources: MTL_SAFETY_STOCKS (aliased SAFETY) and MRP_RHX_PLANNED_ITEMS_V (aliased ITEMS). The first is the base table that stores effectivity-dated safety stock quantities by inventory item and organization; the second is a companion Integration Toolkit view that supplies planned-item attributes such as item number and lead-time values. The documented metadata lists no additional referenced base objects beyond these.

Joins are established on ORGANIZATION_ID and INVENTORY_ITEM_ID, and the view restricts results with ITEMS.MRP_SAFETY_STOCK_CODE = 1, so only items whose planning safety stock method is the safety stock code are returned. A correlated subquery against MTL_SAFETY_STOCKS selects the most recent effectivity date on or before SYSDATE - MRP_RHX_EXT_APS.GET_CONSTANT, and the outer query then retains rows whose effectivity date is at or after that value. The function MRP_RHX_EXT_APS.GET_CONSTANT supplies a planning constant used to shift the comparison window, and it also provides the fallback when no prior effectivity row exists.

Key Columns

Common Use Cases and Queries

Typical uses include extracting safety stock and lead-time data for planning analytics, validating safety stock buffers against lead-time exposure, and feeding external planning or inventory systems. A simple retrieval filtered by organization follows.

SELECT ITEM_NUMBER, EFFECTIVITY_DATE, SAFETY_STOCK_QUANTITY, PREPROCESSING_LEAD_TIME, POSTPROCESSING_LEAD_TIME, FULL_LEAD_TIME FROM MRP_RHX_SAFETY_STOCK_V WHERE ORGANIZATION_ID = :org_id ORDER BY ITEM_NUMBER, EFFECTIVITY_DATE;

To examine lead-time exposure alongside the buffer, select the lead-time columns together with the rounded safety stock quantity, as shown above. Because the view already filters for items with MRP_SAFETY_STOCK_CODE = 1 and applies the effectivity window, downstream queries need not repeat that logic. As with all Integration Toolkit views, access should be granted through the appropriate responsibility, and users should confirm deployment in the target instance before relying on the object.