Search Results ap_period_close_pkg




Overview
Explore in AI Chat

Overview

APPS.AP_PERIOD_CLOSE_PKG is a server-side PL/SQL package in the Oracle E-Business Suite Payables (AP) module that supports the Accounts Payable period close and period-end reporting process. In Oracle EBS 12.1.1 and 12.2.2, closing an AP accounting period requires reconciling the subledger against the general ledger, identifying unaccounted or unposted transactions, validating that all operating units tied to a ledger are ready to close, and producing audit and exception reports before the period status is advanced in General Ledger. This package encapsulates much of that logic, including the collection of reporting context information and the generation of the standard Payables period-close exception and audit reports.

The package is registered in the APPS schema and is documented as VALID in ETRM with an API classification of OTHER, indicating that it is an internal, application-owned package rather than a published public API intended for customer extension. It is not referenced by any other package, confirming that it sits near the top of the AP period-close call stack and is typically invoked directly by concurrent programs and Oracle Forms.

Key Procedures and Functions

The ETRM metadata documents six procedures and functions within the package:

  • PROCESS_PERIOD — the main driver routine that orchestrates the period close processing. It is responsible for assembling the data needed to evaluate and report on the status of a Payables period.
  • BEFORE_REPORT_APXPCER — a pre-report hook associated with the Payables Period Close Exception Report (APXPCER). It prepares or validates the data set before the report output is produced.
  • BEFORE_REPORT_APXUATR — a pre-report hook associated with the Payables Unaccounted/Unposted Audit Report (APXUATR), used to gather the reporting context before the report is run.
  • GET_REPORTING_CONTEXT — returns the reporting context (ledger, period, operating unit, and related parameters) used by the period-close reports.
  • GET_REPORTING_LEVEL_NAME — supplies the descriptive name of the reporting level so that reports and messages can identify the level at which results are being presented.
  • CHECK_ORGS_FOR_LEDGER — validates the operating units associated with a given ledger, ensuring that all relevant organizations are accounted for before period close proceeds.

Consistent with the documented metadata, no parameter lists are published; these routines are called from within the EBS application layer.

Tables Accessed

The package reads and writes against a defined set of APPS synonyms. Setup and calendar tables include AP_SYSTEM_PARAMETERS_ALL, GL_SETS_OF_BOOKS, GL_PERIODS, GL_PERIOD_STATUSES, and HR_OPERATING_UNITS, which provide ledger, period, and organization context. Transaction tables include AP_CHECKS_ALL, AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, AP_INVOICE_LINES_ALL, AP_INVOICE_PAYMENTS_ALL, AP_INV_SELECTION_CRITERIA_ALL, AP_PAYMENT_HISTORY_ALL, and AP_PREPAY_HISTORY_ALL, which supply the invoice, payment, and prepayment data evaluated during close. Global temporary and work tables such as AP_ORG_ATTRIBUTES_GT, AP_PERIOD_CLOSE_EXCPS_GT, and AP_SELECTED_INVOICES_ALL hold intermediate and exception results, while FND_NEW_MESSAGES is used to raise or display messages.

Usage Notes

AP_PERIOD_CLOSE_PKG is normally invoked indirectly through the Payables period-close concurrent programs and the Payables Period Close form. The BEFORE_REPORT hooks are called automatically as part of running the Period Close Exception Report and the Unaccounted/Unposted Audit Report. Because the package is classified as OTHER and is not referenced by other packages, it is not intended as a public API. Customizations should not call these routines directly; instead, standard concurrent programs, report submission, and supported open interfaces should be used to drive period-close functionality.