Results for “application_id”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PA_PERIOD_PROCESS_PKG is a PL/SQL package owned by the APPS schema that governs the interaction between Oracle Projects (PA) accounting periods and Oracle General Ledger (GL) accounting periods. Its primary business function is to enforce and support the implementation option "Maintain Common PA and GL Periods," which allows an installation to keep the PA and GL period calendars synchronized rather than managing them independently. The package also centralizes the logic that determines whether the newer "Enhanced Period Processing" behavior is active, based on profile options such as PA_EN_NEW_GLDATE_DERIVATION and PA: Enable Enhanced Period Processing.

The package is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than as the definer, which is consistent with standard Oracle EBS APPS schema design. Its documented metadata notes that it is referenced by 57 other packages, indicating that it functions as a foundational utility within the Projects period and GL-date derivation framework rather than an end-user-facing component.

Key Procedures and Functions

  • IS_ENABLED — Returns 'Y' if the profile option PA_EN_NEW_GLDATE_DERIVATION is set to 'Y', otherwise 'N'. This acts as the master switch that tells callers whether the new GL date derivation logic applies.
  • APPLICATION_ID — Returns an application identifier derived from the same profile. When the profile is 'Y', it returns 8271; otherwise it returns 101. This allows period-processing logic to route to the correct application context depending on whether enhanced derivation is enabled.
  • USE_SAME_PA_GL_PERIOD — Returns 'Y' if the implementation option "Maintain Common PA and GL Periods" is set to 'Y', otherwise 'N'. The signature was enhanced via Bug#2103722 to accept an optional p_org_id parameter, enabling correct evaluation in multi-organization environments.
  • UPDATE_PA_PERIOD_STATUS — Updates PA period status when the implementation option "Maintain Common PA and GL Periods" is set to Yes and the profile "Enable Enhanced Period Processing" is set to Yes. It is invoked from the GL Periods form, PAXPAGLP.fmb.
  • CHECK_IMP_OPTION_CONTROLS — Executes validation when a user changes the "Maintain Common PA and GL Periods" option from N to Y in the implementation form. Documented checks include confirming that the GL and PA calendar and period type match, and verifying that the "Enable Enhanced Period Processing" profile is enabled.

Tables Accessed

  • PA_IMPLEMENTATIONS_ALL and PA_IMPLEMENTATIONS — Source of the implementation option values, including the org_id used by USE_SAME_PA_GL_PERIOD and the "Maintain Common PA and GL Periods" setting.
  • GL_PERIOD_STATUSES — Read to compare GL period definitions with PA periods when validating common period configuration.
  • PA_PERIODS and PA_PERIODS_ALL — The Projects period definitions whose status is synchronized by UPDATE_PA_PERIOD_STATUS.
  • PLITBLM — The PL/SQL internal table utility used for array processing within the package.

Usage Notes

PA_PERIOD_PROCESS_PKG is not typically called directly by end users. It is invoked from the GL Periods form (PAXPAGLP.fmb) for status synchronization and from the Projects implementation form when the common-period option is changed. The CHECK_IMP_OPTION_CONTROLS procedure acts as a guard preventing inconsistent configuration. Given that 57 other packages reference it, custom code extending period processing, GL date derivation, or period-status reconciliation should call the documented functions rather than reimplementing profile or implementation-option checks. The p_org_id parameter on USE_SAME_PA_GL_PERIOD should be supplied wherever multi-org data is involved to obtain a correct result.