Results for “pa_schedule_utils”

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

Overview

PA_SCHEDULE_UTILS is a utility PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM "OTHER" API category. It supports the Project Management (PA) scheduling subsystem by providing array-based manipulation routines for schedule detail records held in the PA_SCHEDULE_GLOB.ScheduleTabTyp PL/SQL collection type. The package does not expose a public business API in the conventional sense; rather, it supplies internal helper logic used by the scheduling forms, concurrent processes, and other PA packages that build, transform, and validate in-memory schedule record sets before posting them to the database.

The dominant theme of the package is bulk array processing. Procedures such as COPY_SCHEDULE_REC_TAB, ADD_SCHEDULE_REC_TAB, MARK_DEL_SCH_REC_TAB, SEP_DEL_SCH_REC_TAB, and UPDATE_SCH_REC_TAB operate over a bounded range of collection elements (identified by p_start_id and p_end_id) and return the standard File.Sql.39 concurrent-processing status trio: x_return_status, x_msg_count, and x_msg_data. This design allows callers to manipulate large schedule tables in memory rather than issuing row-by-row DML, which is critical in resource assignment and forecasting workloads.

Key Procedures and Functions

The twenty documented procedures and functions fall into several functional groups:

• Array manipulation: COPY_SCHEDULE_REC_TAB copies schedule detail rows from one collection to another; ADD_SCHEDULE_REC_TAB appends rows into an existing collection; MARK_DEL_SCH_REC_TAB flags rows for deletion; SEP_DEL_SCH_REC_TAB separates the records marked for deletion; UPDATE_SCH_REC_TAB applies updates to existing collection rows.
• Calculation: APPLY_PERCENTAGE applies a percentage value across schedule records, and GET_NUM_HOURS derives the number of hours associated with a schedule or assignment.
• Exception handling: COPY_EXCEPT_RECORD and UPDATE_EXCEPT_RECORD manage schedule exception records, typically used when assignments fall outside standard calendars.
• Calendar utilities: GET_RES_CALENDAR returns a resource calendar, GET_RES_CALENDAR_NAME resolves the display name of a resource calendar, and CHECK_CALENDAR validates calendar data.
• Validation and diagnostics: VALIDATE_DATE_RANGE verifies date interval correctness; CHECK_INPUT_SYSTEM_STATUS validates the input system context; LOG_MESSAGE and DEBUG provide internal tracing and error reporting.

Tables Accessed

The package references the following tables through APPS synonyms:

• PA_SCHEDULES — the core schedule detail table where produced records are ultimately persisted.
• PA_PROJECT_ASSIGNMENTS and PA_PROJECT_STATUSES — supply assignment and project lifecycle context for schedule records.
• PA_RESOURCES and PA_RESOURCES_DENORM — resolve resource definitions, including the denormalized variant used for performance-sensitive lookups.
• PA_FORECAST_ITEMS — links schedule entries to forecast lines.
• JTF_CAL_RESOURCE_ASSIGN — provides calendar-to-resource assignment mappings used by the calendar routines.
• PLITBLM — the standard PL/SQL integer table used for message handling.

Usage Notes

PA_SCHEDULE_UTILS is an internal (OTHER) package, not a documented public API. It is referenced by eleven other packages within the PA application family, meaning modifications carry broad regression risk and the package should never be called directly from custom code without Oracle support guidance. Typical invocation occurs from the Project Management schedule maintenance forms, resource assignment and forecasting flows, and concurrent programs that build schedule record collections before committing them. Developers extending schedule-related functionality should favor the supported public APIs that internally depend on this package, relying on PA_SCHEDULE_UTILS only for diagnostic or read-oriented investigation. Custom code that does reference it must respect the NOCOPY OUT parameters and always inspect x_return_status and the message stack before proceeding.