Search Results po_dates_s




Overview
Explore in AI Chat

Overview

APPS.PO_DATES_S is a server-side PL/SQL package body in the Oracle E-Business Suite Purchasing module. Its name and dependency footprint identify it as the date-handling utility package for the purchasing application. It supplies the reusable date logic that the Purchasing forms, concurrent programs, and workflow activities rely on to determine the correct accounting date, period, and effective dates for purchasing documents such as requisitions, purchase orders, releases, and their associated distributions.

The package is classified as OTHER in the ETRM metadata, meaning it is an internal supporting package rather than a published public API. It exists in a VALID state in the APPS schema and depends on several foundational Purchasing and General Ledger objects to resolve organizational accounting periods and application context before returning date values to its callers.

Key Procedures and Functions

The ETRM metadata documents four procedures or functions within the package body, though individual signatures are not enumerated in the source. Based on the package's name and dependency set, these routines collectively provide the following capabilities:

  • Resolution of the default accounting date or period name for a given operating unit and purchasing transaction, using GL period status and organization accounting period data.
  • Validation logic to confirm that a supplied date falls within an open or valid accounting period, returning the appropriate period name or status indicator.
  • Calculation of derived dates such as promise dates, need-by dates, or effective dates used when creating and updating purchasing documents.
  • Utility functions that convert between date formats and period identifiers required by downstream Purchasing APIs and validation routines.

Because the metadata does not expose parameter lists, no signatures are asserted here. Consumers should reference the deployed package specification for exact argument definitions.

Tables Accessed

The documented dependencies establish the tables read by this package:

  • FND_APPLICATION — resolves the application identifier and context for Purchasing, ensuring date logic is applied within the correct application boundaries.
  • GL_PERIOD_STATUSES — supplies the open, closed, or future status of General Ledger periods, which is essential for validating that an accounting date can be posted.
  • ORG_ACCT_PERIODS — provides organization-specific accounting period definitions, allowing the package to map a transaction to its correct open period within the operating unit.

These relationships confirm the package does not maintain its own data but derives date validity from the standard GL and organization period tables.

Usage Notes

PO_DATES_S is referenced by nine other database objects, indicating that it is a widely consumed internal utility rather than an entry point invoked directly by end users. It is typically called from Purchasing forms and concurrent programs when a document's accounting date or period must be defaulted or validated, and from workflow and control routines that pass purchasing transactions to subledger accounting. Customizations that create or modify purchasing documents should call the package's public routines rather than reimplementing period validation, so that the same open-period rules enforced by standard Purchasing functionality are applied consistently. Because the package is internal and its procedures are not documented as a formal API, developers should verify the specification in each environment before relying on specific routines.