Search Results get_ent_dates_info




Overview

The APPS.PJI_PJP_FP_CURR_WRAP package body is a currency and financial-planning wrapper utility within the Oracle EBS Projects (PJI) module. Its principal business function is to provide a stable abstraction layer over currency conversion and multi-currency accounting (MAU) APIs used by the Project Financial Planning (PJP) functions. As its internal header comment indicates ("Misc apis.. wrappers for apis to be provided by Shane"), the package was created to insulate dependent code from the underlying currency utility implementations in PJI_UTILS, allowing the developer team to rename, re-point, or refactor the base objects (for example, renaming pji_fp_xbs_accum_f_2 to pji_fp_xbs_accum_f) without breaking callers. The package is registered in ETRM 12.1.1 and 12.2.2 with an API classification of OTHER and is documented primarily as a supporting utility for global currency rates, exchange dates, and error-handling routines invoked across the Projects suite.

Key Procedures and Functions

The ETRM metadata documents fifteen program units. Their purposes are:

Tables Accessed

The package references the following APPS synonyms:

  • PJI_SYSTEM_SETTINGS — the primary configuration source for global currency codes, rates, MAU, and worker identifiers consumed by the GET_GLOBAL* and GET_MAU* functions.
  • PJI_TIME_ENT_PERIOD — supplies time-entry period date information for GET_ENT_DATES_INFO.
  • DUAL — used for single-row scalar returns and default-value placeholders such as GET_RATE and GET_MAU.

Usage Notes

PJI_PJP_FP_CURR_WRAP is an internal wrapper rather than a user-facing API. It is referenced by 13 other packages, making it a shared dependency for downstream Projects currency and financial-planning logic. It is typically invoked indirectly from concurrent programs and forms that perform multi-currency aggregation for project planning, rather than being called directly from custom code. INIT_ERR_STACK, in particular, is called at the start of PL/SQL blocks (as shown in GET_WORKER_ID) to prepare the error stack before exception-prone processing begins — a convention that makes the string "init_err_stack" a common search term for developers troubleshooting error propagation in Projects currency routines.