Search Results compile_all

Overview

The concurrent program COMPILE_ALL is an Oracle Projects (PA) utility responsible for compiling all uncompiled burden schedule revisions. Its user-facing name in Oracle E-Business Suite is Compile All Uncompiled Burden Schedule Revisions, and it is registered under the PA - Projects product family. The program belongs to the Oracle Cost Plus (PA_COST_PLUS) subsystem, which governs the burdening logic applied to project expenditure items, including the derivation, application, and compilation of burden schedules and their associated structures.

Burden schedules in Oracle Projects are versioned as revisions, and each revision must be compiled before it can be used to calculate burden costs on transactions. Compilation resolves the schedule's structure — including burden multipliers, precedence, and cost bases — into a form usable by the costing engine. When revisions remain uncompiled, burden calculations for the affected schedules cannot proceed correctly, and expenditure items tied to those schedules will not receive burden cost. The COMPILE_ALL program addresses this by scanning for uncompiled burden schedule revisions and compiling them in a single batch operation, eliminating the need to compile each revision individually through the burden schedule maintenance window.

Execution Details

The documented execution metadata for COMPILE_ALL specifies a PL/SQL Stored Procedure execution method with a Standard argument method. The executable is registered as PA_COST_PLUS, with the execution file identified as pa_cost_plus.compile_all. This reflects the standard Oracle EBS concurrent program architecture in which the executable holds the execution file reference and the program definition points to the specific stored procedure contained within that package.

The metadata indicates the program is Enabled: No in the documented environment. This is a notable operational detail: although the program definition exists and the executable mapping is intact, the program is not enabled for submission in that configuration. Administrators should verify the enablement status from the Concurrent Programs form before attempting to schedule or submit the program, and should review whether this utility has been superseded by alternative compilation paths.

How to Run

Within Oracle EBS, COMPILE_ALL is submitted through the Standard Request Submission (SRS) interface. Because the program uses the Standard argument method, its parameters — if any are defined — are presented on the SRS submission form and are validated by the concurrent manager in the conventional manner. Given the program name and purpose, it is commonly treated as a batch maintenance utility that processes all qualifying uncompiled revisions, rather than one targeted at a single schedule; parameters, where present, typically scope the run by operating unit, burden schedule, or compilation range.

General guidance for administrators submitting this program:

• Confirm the program is enabled before submission, since the documented metadata shows Enabled: No.
• Run during periods of low transactional activity, as compilation can hold locks or consume significant concurrent processing resources.
• Review the concurrent request log and output for the count of revisions compiled and any records that failed validation.
• Re-run the burden costing processes for affected expenditures after compilation completes, so that newly compiled schedules are applied.
• Coordinate with the Projects accounting calendar to ensure compiled revisions align with the intended effective periods.

Related Objects

COMPILE_ALL operates within the burden schedule framework of Oracle Projects. Related components commonly encountered alongside it include the burden schedule and burden schedule revision definition forms, which produce the uncompiled revisions the program processes; the PA_COST_PLUS package family that contains the compilation logic; and the burden costing processes such as Distribute Costs and the burdening programs that consume compiled schedule structures. Because compilation affects the cost bases and multipliers used by the costing engine, the program indirectly supports the expenditure item cost distribution, cost adjustment, and accounting generation flows within Project Costing. Administrators should treat COMPILE_ALL as a prerequisite maintenance step for burden schedule revisions and validate results through the burden schedule maintenance and costing reconciliation processes.