Project Performance Concurrent Processes overview
Project Performance processes can be inherently grouped in 5 different
logical groups based on what each process does when summarizing the
transactional data:
1. Initial Load Processes
The Initial Load processes are run after you have applied Family Pack M and
once you have performed the necessary setups steps for Project Performance.
Note:
These two processes must be run in the order listed above. The initial load
processes should be run only once to summarize all historical and current data
in transaction system. Once the initial load of all data is completed
successfully, the corresponding "update" processes should be run to summarize
any new transactions such as timecards, expense reports, inventory transactions.
In addition, the time taken to run these Load processes is dependent upon the
number of transactions that need to be summarized. So plan your production
downtime accordingly to allow successful completion of these processes. Please
refer to Oracle Metalink (note id: 311745.1) for guidelines on database sizing if
you are using project performance reporting.
2. Update Processes
The update processes are run after you have applied Family Pack M, performed
the necessary setups steps, and Initial Load processes have completed
successfully. You should use only these update processes to summarize
incremental data on a regular basis.
Note:
These two processes must be run in the order listed above. For any new
transactions such as timecards, expense reports, inventory transactions, that
come on a regular basis after the initial load is done, these update processes
should be run to summarize that information in reports. You should schedule runs
of these processes daily, weekly or monthly based on how frequently you need to
see updated data in reports.
3. Refresh Processes
The refresh processes are run if you face problems such as duplicate, missing
or non-reconciled data. Such problems can occur due to incorrect data entry
and/or data discrepancy in the transaction systems. These two processes must be
run in the followin g order:
These two processes must be run in the order listed above. These two
processes need to be submitted in conjunction when you encounter data problems
such as duplicate, missing or non-reconciled amounts. These processes should
only be run by administrators and should not be run frequently.
Note: It is normally suggested to run both the processes to keep the activity
(funding/invoice) data in synch. If the project in question does not have
activity data then it is not required to run both the processes in
conjunction.
For modification done to planning resource list, it is not required to run
PRC: Refresh Project and Resource Base Summaries. Running only PRC: Refresh
Project Performance Data should be adequate
Note:
Do not run these processes for getting incremental data in the project
performance tables.
Warning:
Do not run these processes unless authorized by Oracle Support/Development,
except in following cases:.
4. Delete Processes
The delete processes remove all existing financial and resource-related
amounts that were extracted and updated for project performance reporting. These
processes delete data for all the projects in the system and cannot be run for a
range or projects.
These two processes must be run in the order listed above. Only
administrators should run these processes. Do not run these processes
frequently. Run these processes only when you need a fresh install of project
performance, or when you need to change the project performance or business
intelligence set up options.
Warning:
Do not run these processes unless authorized by Oracle
Support/Development.
Warning:
If you run these processes, you will lose all existing data on the project
performance and project intelligence reports. It is recommended not to run these
processes unless absolutely essential.
NOTE:
If your environment is setup for Project Intelligence also and you
have run the truncate and delete steps, it is required to include the "PRC: Load
Project Intelligence Data" process in the load steps to rebuild that data as it
was deleted.
5. Process Resource Breakdown Structure Updates Process
Submit this process when a new version of a resource breakdown structure is
frozen. This process refreshes the summarized amounts for all projects with
amounts that are based on an older version of a resource breakdown structure.
This process refreshes the amounts used by project allocations, budgets and
forecasts, workplan, and project performance reporting.
Further details on each process and associated parameters can be found in the
"Performance and Exceptions Reporting Processes" section of the "Oracle Projects
Fundamentals Guide".
Project Performance processes can be inherently grouped in 5 different
logical groups based on what each process does when summarizing the
transactional data:
1. Initial Load Processes
The Initial Load processes are run after you have applied Family Pack M and
once you have performed the necessary setups steps for Project Performance.
- PRC: Load Project and Resource Base Summaries - This process summarizes
transactional data and populates the base level summary tables when the Oracle
Projects Family Pack M is installed. The base level summaries are used as the
basis for further summarizing the data for project performance, project
intelligence and allocations. - PRC: Load Project Performance Data - This process summarizes and populates
the project performance summary tables using the data from the base summary
tables. Once the project performance summary tables are populated, project
performance reports will be available for viewing. In addition, the data on View
Workplan pages, View Budget and View Forecast pages, and Project list will also
be populated.
Note:
These two processes must be run in the order listed above. The initial load
processes should be run only once to summarize all historical and current data
in transaction system. Once the initial load of all data is completed
successfully, the corresponding "update" processes should be run to summarize
any new transactions such as timecards, expense reports, inventory transactions.
In addition, the time taken to run these Load processes is dependent upon the
number of transactions that need to be summarized. So plan your production
downtime accordingly to allow successful completion of these processes. Please
refer to Oracle Metalink (note id: 311745.1) for guidelines on database sizing if
you are using project performance reporting.
2. Update Processes
The update processes are run after you have applied Family Pack M, performed
the necessary setups steps, and Initial Load processes have completed
successfully. You should use only these update processes to summarize
incremental data on a regular basis.
- PRC: Update Project and Resource Base Summaries - This process summarizes
and populates the project performance base summary tables with incremental data
changes. Examples of these changes are: new timecards, new expense reports
etc. - PRC: Update Project Performance Data - This process summarizes and populates
the project performance summary tables with incremental data changes. Examples
of these changes are: new timecards, new expense reports etc. This process
summarizes data for certain other changes in the system, for example -
associating a Resource Breakdown Structure (RBS) to a project.
Note:
These two processes must be run in the order listed above. For any new
transactions such as timecards, expense reports, inventory transactions, that
come on a regular basis after the initial load is done, these update processes
should be run to summarize that information in reports. You should schedule runs
of these processes daily, weekly or monthly based on how frequently you need to
see updated data in reports.
3. Refresh Processes
The refresh processes are run if you face problems such as duplicate, missing
or non-reconciled data. Such problems can occur due to incorrect data entry
and/or data discrepancy in the transaction systems. These two processes must be
run in the followin g order:
- PRC: Refresh Project and Resource Base Summaries
- PRC: Refresh Project Performance Data
These two processes must be run in the order listed above. These two
processes need to be submitted in conjunction when you encounter data problems
such as duplicate, missing or non-reconciled amounts. These processes should
only be run by administrators and should not be run frequently.
Note: It is normally suggested to run both the processes to keep the activity
(funding/invoice) data in synch. If the project in question does not have
activity data then it is not required to run both the processes in
conjunction.
For modification done to planning resource list, it is not required to run
PRC: Refresh Project and Resource Base Summaries. Running only PRC: Refresh
Project Performance Data should be adequate
Note:
Do not run these processes for getting incremental data in the project
performance tables.
Warning:
Do not run these processes unless authorized by Oracle Support/Development,
except in following cases:.
- When a resource list is changed by adding or disabling resources for a
workplan or financial plan. - If you were on pre-11.5.10 Oracle Applications release (e.g. 11.5.9, or
11.5.7 etc.), and you failed to run the process "UPG: Upgrade Transaction
Attributes" when you installed Family Pack M, and Oracle Project Performance.
Such customers should run "UPG: Upgrade Transaction Attributes" process,
followed by "PRC: Refresh Project and Resource Base Summaries", and then "PRC:
Refresh Project Performance Data".
4. Delete Processes
The delete processes remove all existing financial and resource-related
amounts that were extracted and updated for project performance reporting. These
processes delete data for all the projects in the system and cannot be run for a
range or projects.
- PRC: Delete Project Intelligence and Performance Reporting Data
- PRC: Delete Project Performance Reporting Data
These two processes must be run in the order listed above. Only
administrators should run these processes. Do not run these processes
frequently. Run these processes only when you need a fresh install of project
performance, or when you need to change the project performance or business
intelligence set up options.
Warning:
Do not run these processes unless authorized by Oracle
Support/Development.
Warning:
If you run these processes, you will lose all existing data on the project
performance and project intelligence reports. It is recommended not to run these
processes unless absolutely essential.
NOTE:
If your environment is setup for Project Intelligence also and you
have run the truncate and delete steps, it is required to include the "PRC: Load
Project Intelligence Data" process in the load steps to rebuild that data as it
was deleted.
5. Process Resource Breakdown Structure Updates Process
- PRC: Process Resource Breakdown Structure Updates
Submit this process when a new version of a resource breakdown structure is
frozen. This process refreshes the summarized amounts for all projects with
amounts that are based on an older version of a resource breakdown structure.
This process refreshes the amounts used by project allocations, budgets and
forecasts, workplan, and project performance reporting.
Further details on each process and associated parameters can be found in the
"Performance and Exceptions Reporting Processes" section of the "Oracle Projects
Fundamentals Guide".