Search Results po_reschedule_pkg




Overview
Explore in AI Chat

Overview

PO_RESCHEDULE_PKG is a public PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified by ETRM as an "OTHER" API rather than a formal public interface. Its business function is to support the rescheduling of purchase order lines and shipments — changing the promised or need-by dates on open purchasing documents so that supply dates remain aligned with current demand, production schedules, or supplier commitments. In Oracle Purchasing, rescheduling is a routine maintenance activity: buyers and planners adjust dates on standard purchase orders, blanket agreement releases, and internal requisitions to keep delivery expectations synchronized with MRP output and master scheduling. Rather than forcing every date change through the full document update and revision-control framework, PO_RESCHEDULE_PKG provides a dedicated, narrower entry point for date manipulation. Because it references FND_API, FND_MSG_PUB, and PO_API_ERRORS_REC_TYPE, the package adheres to the Oracle Application Object Library error-handling model, accumulating messages and returning a standard API result rather than relying on raw exceptions. Its dependency on FND_CLIENT_INFO and FND_PROFILE further indicates that it is intended to be called within an EBS session that carries the correct operating unit, responsibility, and user context, so that MOAC (Multi-Org Access Control) validation and auditing behave correctly.

Key Procedures and Functions

ETRM documents a single public entry point in this package body:

  • RESCHEDULE — The principal routine exposed by PO_RESCHEDULE_PKG. It performs the date change on the target purchasing document line or shipment, applying the package's internal validation and error-collection logic. The documented metadata does not publish a parameter list, so the precise signature should be confirmed against the deployed source in the target instance before use. Callers should expect the routine to accept identifying information for the document being rescheduled along with the new date values, and to return or raise errors through the FND_MSG_PUB message stack and PO_API_ERRORS_REC_TYPE structure rather than through unhandled exceptions.

Supporting logic is distributed across the package's dependencies rather than additional documented procedures. PO_DOCUMENT_UPDATE_PVT and PO_CORE_S supply the underlying document manipulation and security primitives, while PO_DEBUG provides diagnostic tracing.

Tables Accessed

The documented table references reflect the full scope of documents the package can reschedule:

  • PO_HEADERS_ALL — The purchasing document header, used to identify and validate the parent document being rescheduled.
  • PO_LINES_ALL — The document line, the level at which date changes are typically initiated.
  • PO_LINE_LOCATIONS_ALL — The shipment or schedule line, which holds the promised, need-by, and ship dates that rescheduling actually modifies.
  • PO_RELEASES_ALL — Blanket agreement releases, allowing release-level dates to be adjusted independently of the underlying agreement.
  • PO_REQUISITION_LINES_ALL — Internal requisition lines, supporting rescheduling of demand that flows into purchasing.
  • PO_SESSION_GT — A global temporary table used to hold session-scoped context for the operation.
  • DUAL and PLITBLM — Standard single-row and PL/SQL index-by table support objects.

Note that PO_RESCHEDULE_PKG itself is not referenced by any database object, and ETRM records only two other packages referencing it. It should therefore be treated as a narrowly used internal utility rather than a broadly depended-upon integration point.

Usage Notes

PO_RESCHEDULE_PKG is most likely invoked from Oracle Purchasing forms during interactive date maintenance, and potentially from concurrent programs or workflow activities that perform bulk date adjustments. Custom code should call the RESCHEDULE procedure only inside a properly initialized EBS session, invoking FND_GLOBAL.APPS_INITIALIZE or equivalent setup so that FND_PROFILE and FND_CLIENT_INFO resolve the correct organization and user context. Always inspect the FND_MSG_PUB message stack for errors after the call, and respect the documented dependency direction: the package calls down into PO_DOCUMENT_UPDATE_PVT and PO_CORE_S, so changes to those internals can affect rescheduling behavior across releases such as 12.1.1 and 12.2.2. Because the metadata exposes only the procedure name and not its signature, validate the exact parameters in the deployed environment before building any interface on top of this package.