Search Results get_period_type

Overview

GL_PA_AUTOALLOC_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its business function is to support Project Allocation Rules processing by determining the appropriate accounting period type and by submitting the concurrent request that generates allocation transactions. Project Allocation Rules can be defined against either the General Ledger (GL) period calendar or the Projects (PA) period calendar, and the application must resolve, at runtime, which calendar to use for any given allocation set. This package encapsulates that resolution logic and the request submission that depends on it. The header comment ($Header: glalprjs.pls 120.2 2002/11/11 23:53:35 djogg ship $) indicates the package has been part of the shipped product since at least the 11i era and remains available in the 12.1.1 and 12.2.2 releases. ETRM classifies the package as an OTHER API, meaning it is a supporting/internal API rather than a formally published public interface, though it is callable from custom code.

Key Procedures and Functions

The package exposes five documented program units, each focused on period resolution or request lifecycle monitoring.

• GET_PERIOD_TYPE — The function most directly associated with this object. Given an allocation set identifier, it inspects the Project Allocation Rules defined in that set and returns a single-character code indicating the period type in use: 'P' when all rules use the PA period, 'G' when all rules use the GL period, 'B' when both types coexist, and 'N' when the set contains no allocation rules. This is the mechanism the rest of the package relies on to decide which period value to pass downstream.
• VALID_RUN_PERIOD — Calls GET_PERIOD_TYPE to determine whether a PA period or GL period is required, then verifies that the required period value is not null. Returns TRUE on success and FALSE on failure. This provides a pre-submission validation gate.
• SUBMIT_ALLOC_REQUEST — Performs two tasks: it identifies the period to be passed as a parameter to the allocation process, then submits the Generate Allocation Transactions Request. It returns the request identifier of the submitted concurrent request.
• GET_PA_STEP_STATUS — Retrieves status information associated with the allocation processing steps (documentation truncated in the source excerpt).
• UPD_GL_AUTOALLOC_BATCH_HIST — Maintains GL auto-allocation batch history records.

Tables Accessed

The documented table reference is GL_AUTO_ALLOC_BATCH_HISTORY, accessed through an APPS synonym. This table records the history of auto-allocation batch runs, and the package writes or updates rows in it via UPD_GL_AUTOALLOC_BATCH_HIST and reads it for status reporting through GET_PA_STEP_STATUS. In addition, GET_PERIOD_TYPE implicitly depends on the Project Allocation Rules definition tables that store each rule’s period type; these are queried to derive the single-character return value.

Usage Notes

GL_PA_AUTOALLOC_PKG is typically invoked indirectly: Oracle Projects forms and concurrent programs call GET_PERIOD_TYPE and VALID_RUN_PERIOD while validating an allocation run, and then call SUBMIT_ALLOC_REQUEST to launch the Generate Allocation Transactions concurrent program. Because it is classified as OTHER rather than as a public API, custom integrations should treat the signatures as subject to change and should prefer supported public APIs where one exists. The four packages documented as referencing this package confirm its role as a shared utility within the Projects allocation code path. When troubleshooting period-related submission errors, the character returned by GET_PERIOD_TYPE is the most useful diagnostic value.