Search Results get_bill_rates_all_nextseq




Overview
Explore in AI Chat

Overview

PA_INTEGRATION_UTILS is a utility package owned by the APPS schema in Oracle E-Business Suite Projects (PA). It is declared with AUTHID DEFINER, meaning its procedures and functions execute with the privileges of the APPS owner rather than the calling user, and it is classified under the ETRM as an OTHER-type API rather than a public or private interface. As the source header ($Header: PAINTUTS.pls 120.1 2010/06/24) indicates, the package is a longstanding internal helper component for the Projects integration layer, packaging together small, reusable routines that resolve project budgeting identifiers, generate sequencing values for billing rates, populate integration staging data, and emit diagnostic log messages. It is not a business-facing API: it provides shared plumbing consumed by the Projects integration and budgeting processes, and ETRM records zero other packages referencing it directly.

Key Procedures and Functions

  • GET_BUDGET_VERSION_ID — Accepts a parent structure version identifier and returns the corresponding budget version identifier. This is the entry most commonly searched by developers, since downstream budgeting and integration logic typically requires translating a structure/version context into an explicit PA_BUDGET_VERSIONS record key.
  • GET_BILL_RATES_ALL_NEXTSEQ — Returns the next available sequence value for the bill rates table, providing a safe surrogate key for inserts into PA_BILL_RATES_ALL.
  • POPULATE_RESOURCE_ACTUALS_DATA — Populates actuals data for a given project and resource list; takes a project identifier and resource list identifier as inputs and drives the staging/accumulation of resource actuals used by integration processing.
  • WRITE_LOG — Accepts a module name and message text and writes a diagnostic entry to the system debug repository, used for tracing integration execution.
  • GET_BUDGET_LEVEL — Returns a budget level value as a VARCHAR2, based on a project identifier and, optionally, a budget type, financial plan type identifier, and a mode (defaulting to 'BUDGET'). It encapsulates the logic for determining whether budgeting is performed at project, task, or resource level.

No parameter signatures beyond those documented in the package specification are asserted here.

Tables Accessed

The package resolves several base tables through APPS synonyms. PA_BUDGET_VERSIONS and PA_BUDGET_ENTRY_METHODS support budget version resolution and budget-level determination. PA_PROJ_FP_OPTIONS provides financial plan configuration controlling how budget levels and versions are interpreted. PA_PERIODS_ALL supplies the accounting period context. PA_BILL_RATES_ALL_SEQ backs the next-sequence function. PJI_FM_XBS_ACCUM_INT and PJI_FM_XBS_ACCUM_TMP1 are the integration accumulation interface and temporary staging tables written by POPULATE_RESOURCE_ACTUALS_DATA. PJI_SYSTEM_DEBUG_MSG and its synonym PJI_SYSTEM_DEBUG_MSG_S receive the rows written by WRITE_LOG, and DUAL is used for scalar lookups such as sequence retrieval.

Usage Notes

PA_INTEGRATION_UTILS is an internal utility layer rather than a published API, so it is normally invoked only from Projects integration code, concurrent programs, and occasionally from Forms-based budgeting flows that need to resolve budget version identifiers or budget levels. Developers extending Projects budgeting or external-system integrations may call GET_BUDGET_VERSION_ID and GET_BUDGET_LEVEL to avoid re-implementing identifier and level resolution logic, while WRITE_LOG offers a convenient way to emit trace messages into PJI_SYSTEM_DEBUG_MSG during debugging. Because the package is AUTHID DEFINER and has no documented exception interface, callers should treat failures as internal errors, wrap invocations in their own exception handlers, and avoid relying on undocumented overloads; behaviour is consistent across EBS 12.1.1 and 12.2.2 as reflected in the ETRM metadata.