Search Results check_start_end_date




Overview

PA_BILLING_SCHEDULE_UTILS is an Oracle Projects (PA) utility package that centralizes validation and identifier-resolution logic for billing schedules used throughout Oracle E-Business Suite. In the Projects module, revenue, invoice, and labor billing arrangements are driven by named schedules stored in the PA standard billing rate schedule tables and in labor multiplier tables. Forms, concurrent programs, and downstream PL/SQL logic must frequently convert a user-entered schedule name into its internal identifier, verify that a job group belongs to a valid project type and class, and confirm that required billing attributes such as bill information, labor multipliers, and start/end dates are present before a transaction can be processed.

PA_BILLING_SCHEDULE_UTILS consolidates these common routines so that billing and labor cost logic does not have to re-implement them independently. It is a public package with no prerequisites, returning status through the standard FND_API return status and error message code conventions rather than raising exceptions directly. This makes it suitable for reuse across multiple entry points, and it is referenced by three other packages in the ETRM repository. The header dates to 2005 and remains part of the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

Tables Accessed

  • PA_LABOR_MULTIPLIERS — read to validate labor multiplier definitions and detect duplicates.
  • PA_PROJECTS_ALL — read to retrieve project context, including project type and class.
  • PA_PROJECT_TYPES — read to resolve project type and its classification for validation logic.
  • PA_STD_BILL_RATE_SCHEDULES — read to resolve schedule names to identifiers across the employee, job, revenue, invoice, and non-labor schedule routines.

Usage Notes

The package is typically invoked from Oracle Projects forms and from concurrent or custom PL/SQL that must validate billing schedule selections before committing data. Callers pass the schedule name or id, then inspect x_return_status and x_error_msg_code to determine success. Because the name-to-id routines return identifiers rather than raising exceptions, custom extensions can call them safely inside larger validation flows. The parameters that accept FND_API.G_MISS_NUM and FND_API.G_MISS_CHAR defaults support the standard Oracle API pattern of identifying records by either surrogate id or descriptive name, with the check-id flag controlling which key is treated as authoritative.