Search Results update_enddate




Overview

APPS.CST_ACCOUNTINGPERIOD_PUB is the public PL/SQL API that governs the Oracle EBS Cost Management accounting period close lifecycle. It provides the programmatic entry points used to open, verify, close, and summarize an inventory/costing accounting period for a given organization, and to inspect the state of pending transactions that would block a period close. The package is classified as a public (PUB) API in the ETRM registry, meaning its signatures are treated as a supported integration surface for both Oracle's own application modules and customer extensions. Its core design intent is to centralize the validation logic that determines whether a period is eligible to close, and to expose that logic consistently to Oracle Inventory, Work in Process, and external calling programs. The package header carries the EBS source control signature CSTPAPES.pls 120.1.12010000.2, consistent with the 12.1.1 code line and carried forward into 12.2.2. Seven documented subprograms make up the API, supported by a set of cost and period temporary tables and base transaction tables.

Key Procedures and Functions

  • GET_PENDINGTCOUNT — Returns counts of outstanding transactions for a given period that may prevent period close from continuing. Documented blocking categories include unprocessed material transactions, uncosted transactions, pending WIP costing transactions, uncosted WSM transactions, and pending WSM interface transactions; pending shipping delivery transactions are client-dependent.
  • OPEN_PERIOD — Opens a costing/inventory accounting period for an organization, establishing the period state required before transactions can be processed and later closed.
  • VERIFY_PERIODCLOSE — Performs pre-close validation for the target period and organization, confirming that prerequisites and pending-transaction conditions permit closure.
  • CLOSE_PERIOD — Executes the period close for the organization, finalizing the accounting period once verification has succeeded.
  • UPDATE_ENDDATE — Adjusts the end date of the accounting period. This is the procedure most commonly associated with the search term update_enddate, and it allows the period boundary to be maintained without directly modifying the underlying period records.
  • REVERT_PERIODSTATUS — Reverts the status of a period, providing the rollback path when a close or open action must be undone.
  • SUMMARIZE_PERIOD — Produces the period summary information used for reporting and for the close-summary records retained by the application.

Tables Accessed

The package operates across cost, period, and organization metadata. Reference and period tables include GL_PERIODS and GL_LEDGERS for calendar and ledger context, HR_ORGANIZATION_INFORMATION and MTL_PARAMETERS for organization-level costing setup, and MTL_DEFAULT_CATEGORY_SETS for category set defaults. Transaction state is read from MTL_MATERIAL_TRANSACTIONS and MTL_MATERIAL_TRANSACTIONS_TEMP, which drive the pending-transaction counts returned by GET_PENDINGTCOUNT. Costing resolution and interface activity draw on CST_LC_ADJ_INTERFACE. Period close output and intermediate processing use CST_PERIOD_CLOSE_SUMMARY, CST_PER_CLOSE_SUMMARY_TEMP, and the temporary working sets CST_CG_LIST_TEMP, CST_INV_COST_TEMP, CST_INV_QTY_TEMP, CST_ITEM_LIST_TEMP, and CST_SUB_LIST_TEMP. All are accessed through APPS synonyms.

Usage Notes

The package is normally invoked by Oracle Inventory and Cost Management period-close windows and by the concurrent programs that drive period close processing, rather than being called directly by end users. The documented callers include three other packages, indicating its role as a shared service within the cost period-close stack. Custom code should invoke these procedures only through the APPS synonym, supply the standard API version parameter first, and honor the NOCOPY OUT parameters returned by GET_PENDINGTCOUNT without assuming a fixed width or ordering beyond the documented signature. Because close operations are organization-specific, callers must pass the correct organization identifier; UPDATE_ENDDATE in particular should be used instead of direct DML against period records to preserve consistency with the close summary tables.