Search Results get_dock_date
Overview
APPS.MRP_REL_PLAN_PUB is a public PL/SQL package in Oracle E-Business Suite that supports the release of planning recommendations generated by Oracle Master Scheduling/MRP. Its principal role is to take the output of a plan—planned orders, requisitions, jobs, and repetitive schedules—and convert or confirm those recommendations into executable supply documents, such as purchase requisitions and discrete jobs. The package header carries the RCS identifier $Header: MRPPRELS.pls 115.11 2002/11/22, indicating a long-standing component of the MRP module that has been stable across the 12.1.1 and 12.2.2 releases. The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling user rather than the defining schema, a typical convention for public APIs in the EBS application schema. The current API version is documented as 1.0.
Key Procedures and Functions
The package exposes two documented entry points.
- MRP_RELEASE_PLAN_SC — The primary release procedure. It drives the conversion of selected plan recommendations for a given organization into their implementation documents, tracking counts of loaded and rescheduled jobs, requisitions, and schedules for the calling process. It accepts organizational context, a schedule designator (compile designator), a user identifier, grouping and batching controls for purchase order output, and mode/transaction identifiers for integration with concurrent processing. Several parameters are declared IN OUT NOCOPY, allowing the procedure to return row counts and generated identifiers back to the caller. Relevant to the user's search, the Bug#1519701 comment immediately preceding the function declaration shows that GET_DOCK_DATE was added as a new function in this same package as part of the release-enhancement work.
- GET_DOCK_DATE — A date-returning function, introduced under Bug#1519701 (with an additional owning-organization parameter referenced as 2448572). It computes an appropriate dock date for a supply recommendation, taking into account the schedule designator, plan owning organization, calendar and calendar exception set, implementation date, vendor and vendor site, item, and a supplied lead time. The function returns a DATE value, and its parameters include the calendar context needed to adjust dates for working-day exceptions.
Tables Accessed
The documented table references, resolved through APPS synonyms, reflect the package's dependence on both planning and execution data. Calendar tables such as BOM_CALENDAR_DATES support working-day and exception calculations used by GET_DOCK_DATE. Planning structures including MRP_PLANS, MRP_PLAN_PRARAMETERS-adjacent data, MRP_SYSTEM_ITEMS, MRP_RECOMMENDATIONS, MRP_SCHEDULE_DESIGNATORS, and MRP_SUGG_REP_SCHEDULES supply the recommendation, item, and schedule information being released. Supplier and sourcing data are read from MRP_ITEM_SUPPLIERS, MRP_ITEM_PURCHASE_ORDERS, and MRP_PROJECT_PARAMETERS, while MRP_ITEM_WIP_ENTITIES supports work-in-process recommendations. Execution-side tables include MTL_PARAMETERS and MTL_SYSTEM_ITEMS for organization and item attributes, CST_COST_GROUP_ACCOUNTS for costing context, and PO_REQUISITIONS_INTERFACE_ALL/S for writing requisition interface records during release.
Usage Notes
MRP_REL_PLAN_PUB is typically invoked from the Plan Release workflow within Oracle MRP, from concurrent program logic, or from custom extensions that automate the release of planned orders. The MRP_RELEASE_PLAN_SC procedure is the appropriate entry point when a client needs to release a batch of recommendations programmatically, and its OUT parameters allow the caller to report processing totals. GET_DOCK_DATE is called during release to derive a dock (receipt) date for planned supply, honoring the vendor site calendar and lead time. Because the package is classified as PUB and is referenced by two other packages, it is intended as a supported public interface, though custom callers should supply valid organization, designator, and calendar contexts and expect date calculations to respect the configured calendar exception set.
-
PACKAGE: APPS.MRP_REL_PLAN_PUB
12.2.2
-
PACKAGE: APPS.MRP_REL_PLAN_PUB
12.1.1
-
APPS.MRP_REL_PLAN_PUB SQL Statements
12.1.1
-
APPS.MRP_REL_PLAN_PUB SQL Statements
12.2.2
-
APPS.MSC_REL_WF SQL Statements
12.2.2
-
PACKAGE BODY: APPS.MRP_REL_PLAN_PUB
12.2.2
-
PACKAGE BODY: APPS.MRP_REL_PLAN_PUB
12.1.1
-
APPS.MSC_REL_WF SQL Statements
12.1.1
-
PACKAGE: APPS.MSC_REL_WF
12.1.1
-
PACKAGE: APPS.MSC_REL_WF
12.2.2
-
PACKAGE BODY: APPS.MSC_REL_WF
12.2.2
-
PACKAGE BODY: APPS.MSC_REL_WF
12.1.1
-
APPS.MRP_REL_PLAN_PUB dependencies on MRP_REL_PLAN_PUB
12.2.2
-
APPS.MRP_REL_PLAN_PUB dependencies on MRP_REL_PLAN_PUB
12.1.1