Results for “intransit_lead_time”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MSC_X_VMI_UTIL_NEW is a PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM taxonomy as an "OTHER" API. Its name and constituent procedures indicate that it serves the Vendor Managed Inventory (VMI) and supplier/customer collaboration functionality delivered through Oracle Advanced Supply Chain Planning (ASCP) and the MSC (Manufacturing Supply Chain) schema family. The package consolidates calculation and graph-generation logic used to present VMI demand, on-hand, and usage metrics to trading partners within the collaborative planning framework. It is documented as VALID in both 12.1.1 and 12.2.2, and ETRM records it as referencing only SYS.STANDARD at the direct dependency level, while being referenced by the view MSC_SUP_DEM_ENTRIES_VMI_V and by one additional package. Table access occurs through APPS synonyms rather than direct MSC schema references, consistent with the standard EBS synonym-layer convention.
Key Procedures and Functions
ETRM documents nine callable units within the package:
- VMI_DETAILS_SUPPLIER — returns VMI detail information from the supplier perspective, drawing on supplier demand and item-supplier relationships.
- VMI_DETAILS_CUSTOMER — the customer-facing counterpart, returning VMI detail data relevant to the buying organization.
- VMICUSTOMERGRAPHCREATE and VMICUSTOMERGRAPHTEST — construct and validate customer-side VMI graph data, typically for display in collaborative planning or supplier portal screens.
- VMISUPPLIERGRAPHONHAND — generates supplier-side on-hand graph data used in VMI dashboards.
- AVG_DAILY_DEMAND, SUPPLIER_AVG_DAILY_USAGE, and CUSTOMER_AVG_DAILY_USAGE — compute average daily demand and average daily usage metrics from the supplier and customer vantage points, serving as planning inputs and graph series values.
- INTRANSIT_LEAD_TIME — derives in-transit lead time, supporting replenishment and visibility calculations for goods moving between source and receipt organizations.
No parameter signatures are documented in the ETRM extract; consumers should validate interfaces against the deployed package specification rather than assuming argument lists.
Tables Accessed
Via APPS synonyms, the package reads and writes the following documented tables:
- MSC_SUP_DEM_ENTRIES — supplier demand entries, the primary transaction source for demand and usage calculations.
- MSC_ITEMS, MSC_SYSTEM_ITEMS, MSC_ITEM_SUPPLIERS — item master and sourcing definitions, including approved supplier relationships.
- MSC_COMPANIES, MSC_COMPANY_RELATIONSHIPS, MSC_COMPANY_SITES, MSC_COMPANY_USERS, MSC_TRADING_PARTNERS — the trading-partner and company model that governs which supplier/customer sees which data.
- MSC_ASSIGNMENT_SETS, MSC_SR_ASSIGNMENTS, MSC_SR_RECEIPT_ORG, MSC_SR_SOURCE_ORG, MSC_PLAN_ORG_STATUS — planning assignment and source/receipt organization configuration used to scope queries.
- MRP_ATP_SCHEDULE_TEMP_S — a temporary ATP schedule table, consistent with lead-time computation.
Usage Notes
The package is not designed for direct end-user invocation; it is called programmatically by the VMI view MSC_SUP_DEM_ENTRIES_VMI_V and by at least one other package, meaning it surfaces indirectly through OBI/HTML-based collaborative planning and supplier portal pages that render VMI graphs and metrics. Because it is classified as OTHER rather than a public API, Oracle does not guarantee interface stability. Customizations should treat it as internal, avoid direct calls where a supported alternative exists, and re-validate behavior after applying 12.1.1 or 12.2.2 patches, since graph and demand-calculation logic in the MSC schema family is frequently revised.
-
APPS.MRPFV_PLAN_ITEM_SOURCES·↳ FND_GLOBAL·↳ HR_ALL_ORGANIZATION_UNITS·↳ MRP_ASSIGNMENT_SETS·Explore MRP module →
-
View: MRP_SC_BILL_SF_V 12.2.2
Supply chain bill source from view
APPS.MRP_SC_BILL_SF_V·↳ BOM_BILL_OF_MATERIALS·↳ BOM_CALENDAR_DATES·↳ BOM_INVENTORY_COMPONENTS·Explore MRP module →
-
APPS.MRPFV_PLAN_ITEM_SOURCES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MRP_ASSIGNMENT_SETS·↳ MRP_ITEM_SOURCING·Explore MRP module →
-
View: MRP_SC_BILL_WU_V 12.2.2
Supply chain bill where used view
APPS.MRP_SC_BILL_WU_V·↳ BOM_BILL_OF_MATERIALS·↳ BOM_CALENDAR_DATES·↳ BOM_INVENTORY_COMPONENTS·Explore MRP module →
-
View: MRP_ATP_PROPERTIES_V 12.2.2
APPS.MRP_ATP_PROPERTIES_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·↳ MFG_LOOKUPS·Explore MRP module →
-
View: MSC_SC_BILL_SF_V 12.2.2
Supply chain bill source from view
APPS.MSC_SC_BILL_SF_V·↳ MSC_ASSIGNMENT_SETS·↳ MSC_BOMS·↳ MSC_BOM_COMPONENTS·Explore MSC module →
-
APPS.MRP_ATP_SCHEDULE_TEMP_V·↳ MFG_LOOKUPS·↳ MRP_ATP_SCHEDULE_TEMP·↳ OE_ORDER_LINES_ALL·Explore MRP module →
-
Supply Chain ATP supply source view
APPS.MRP_SCATP_SUPPLY_SOURCES_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·↳ MTL_DEMAND_INTERFACE·Explore MRP module →
-
Supply Chain ATP supply source view
APPS.MRP_SCATP_SUPPLY_SOURCES_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·↳ MTL_DEMAND_INTERFACE·Explore MRP module →
-
View: MRP_SC_BILL_WU_V 12.1.1
Supply chain bill where used view
APPS.MRP_SC_BILL_WU_V·↳ BOM_BILL_OF_MATERIALS·↳ BOM_CALENDAR_DATES·↳ BOM_INVENTORY_COMPONENTS·Explore MRP module →
-
View: MRP_SC_BILL_SF_V 12.1.1
Supply chain bill source from view
APPS.MRP_SC_BILL_SF_V·↳ BOM_BILL_OF_MATERIALS·↳ BOM_CALENDAR_DATES·↳ BOM_INVENTORY_COMPONENTS·Explore MRP module →
-
APPS.MRP_ATP_SCHEDULE_TEMP_V·↳ MFG_LOOKUPS·↳ MRP_ATP_SCHEDULE_TEMP·↳ OE_ORDER_LINES_ALL·Explore MRP module →
-
This table stores sales order demand and reservations from source application instances.
-
View: MSC_SC_BILL_WU_V 12.1.1
Supply chain bill where used view
APPS.MSC_SC_BILL_WU_V·↳ MSC_ASSIGNMENT_SETS·↳ MSC_BOMS·↳ MSC_BOM_COMPONENTS·Explore MSC module →
-
This table stores all the demands taken into account for planning. Disposition_id would be a foreign key to MSC_SUPPLIES for dependent demands. For independent demands, disposition_id holds MRP_SCHEDULE_DATES.MPS_TRANSACTION_ID.
-
APPS.MRPBV_PLAN_ITEM_SOURCES·↳ FND_GLOBAL·↳ HR_ALL_ORGANIZATION_UNITS·↳ MRP_ITEM_SOURCING·Explore MRP module →
-
View: MSC_SC_BILL_WU_V 12.2.2
Supply chain bill where used view
APPS.MSC_SC_BILL_WU_V·↳ MSC_ASSIGNMENT_SETS·↳ MSC_BOMS·↳ MSC_BOM_COMPONENTS·Explore MSC module →
-
View: MSC_SC_BILL_SF_V 12.1.1
Supply chain bill source from view
APPS.MSC_SC_BILL_SF_V·↳ MSC_ASSIGNMENT_SETS·↳ MSC_BOMS·↳ MSC_BOM_COMPONENTS·Explore MSC module →
-
APPS.MRPBV_PLAN_ITEM_SOURCES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MRP_ITEM_SOURCING·↳ MRP_PLANS·Explore MRP module →
-
Holds ATP results
-
View: MRP_ATP_PROPERTIES_V 12.1.1
APPS.MRP_ATP_PROPERTIES_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·↳ MFG_LOOKUPS·Explore MRP module →
-
Table: MSC_TEMP_SALES_ORDERS 12.2.2
-
View: MRP_ATP_V 12.1.1
ATP/CTP view
APPS.MRP_ATP_V·↳ BOM_BILL_OF_MATERIALS·↳ BOM_CALENDAR_DATES·↳ BOM_DEPARTMENTS·Explore MRP module →
-
Table: MSC_TEMP_SALES_ORDERS 12.1.1
-
The staging table used by the collection program to validate and process data for table MSC_SALES_ORDERS.
-
Holds ATP result details for Supply/Demand, Horizontal ATP and sourcing.
-
View: MSC_ORDERS_V 12.2.2
This view shjows all the supplies,demands anf sales orders
APPS.MSC_ORDERS_V·↳ MFG_LOOKUPS·↳ MSC_DEMANDS·↳ MSC_DMD_SCN_METRICS·Explore MSC module →
-
this view picks up all the valid exception details
APPS.MSC_EXCEPTION_DETAILS_V·↳ MSC_DEMANDS·↳ MSC_EXCEPTION_DETAILS·↳ MSC_FULL_PEGGING·Explore MSC module →
-
this view picks up all the valid exception details
APPS.MSC_EXCEPTION_DETAILS_V·↳ MSC_DEMANDS·↳ MSC_EXCEPTION_DETAILS·↳ MSC_FULL_PEGGING·Explore MSC module →
-
Temporary demand storage for the transaction processor
-
Temporary demand storage for the transaction processor
-
View: MRP_ATP_V 12.2.2
ATP/CTP view
APPS.MRP_ATP_V·↳ BOM_BILL_OF_MATERIALS·↳ BOM_CALENDAR_DATES·↳ BOM_DEPARTMENTS·Explore MRP module →
-
This table stores sales order demand and reservations from source application instances.
-
The staging table used by the collection program to validate and process data for table MSC_SALES_ORDERS.
-
Holds ATP result details for Supply/Demand, Horizontal ATP and sourcing.
-
View: MSC_ORDERS_V 12.1.1
This view shjows all the supplies,demands anf sales orders
APPS.MSC_ORDERS_V·↳ MFG_LOOKUPS·↳ MSC_DEMANDS·↳ MSC_DRP_UTIL·Explore MSC module →
-
Holds ATP results
-
This table stores all the demands taken into account for planning. Disposition_id would be a foreign key to MSC_SUPPLIES for dependent demands. For independent demands, disposition_id holds MRP_SCHEDULE_DATES.MPS_TRANSACTION_ID.
-
This table lists all the supplies for this plan. The supplies created by the planning process are added to this table.
-
This table lists all the supplies for this plan. The supplies created by the planning process are added to this table.
-
Constrained Plan View
APPS.MSD_CONSTRAINED_FORECAST_V·↳ FND_PROFILE·↳ MSC_DEMANDS·↳ MSC_PLANS·Explore MSD module →
-
Constrained Plan View
APPS.MSD_CONSTRAINED_FORECAST_V·↳ FND_PROFILE·↳ MSC_DEMANDS·↳ MSC_PLANS·Explore MSD module →