Featured post

Functionality of Segment Value Inheritance ESS Process

  The Segment Value Inheritance process simplifies the maintenance of the chart of accounts. When the characteristics of values in the value...

Sunday 9 April 2017

PROJECT PERFORMANCE CONCURRENT PROCESSES: OVERVIEW AND FAQ

Sections This white paper contains the following information. 

  1. Project Performance Concurrent Processes Overview
  2. How and when to run Project Performance Concurrent Processes
  3. What's New in each Family Pack M Rollup
  4. Frequently Asked Questions (FAQ)
  5. Troubleshooting
  6. Change Record
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.

  • 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 following 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".

How and when to run Project Performance Concurrent Processes. This section describes the order in which project performance concurrent processes need to be run for existing customers who uptake Oracle Projects Family Pack M (FP.M) and for new customers who have bought Oracle Projects Management license after the release of Family Pack M. This document explains the sequence in which the concurrent processes must be run, along with when to run each process.

Initial Load of data into base level and project performance summary tables The initial load of plan and actuals (timecards and expense reports) into the project performance base summary tables involves following a number of steps (including running the project performance concurrent processes).

The series of steps mentioned below are in order. This order needs to be followed only once for initial install. All steps below need to be completed sequentially, i.e., go to the next steps only when the prior step completes successfully. Additionally, you must complete project performance set up and Business Intelligence profile options set up before running these processes.

If you are an existing customer of Oracle Projects and use the financial plan model for budgeting (as opposed to the old budget model), follow the sequence of actions mentioned below (in the order mentioned below):

  • Install Family Pack M (apply the Family Pack M patch)
  • Complete the required project performance setups
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to No. (Performs initial load of actuals into base level summary tables)
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to Yes. (Performs initial load of commitments into base level summary tables)
  • Run "PRC: Load Project Performance Data" (Performs initial load of actuals into project performance summary tables)
  • Run "PRC: Update Project Performance Data" (If you are an existing customer, you must run this process. This process serves a different purpose and is needed only when existing customers upgrade from earlier version of Oracle Projects to Family Pack M. The process creates report data in enterprise calendar and currency data for financial plans)
If you are an existing customer of Oracle Projects and use the old budget model for budgeting, you can only view actuals amounts in project performance. For budget data, you have to use Project Status Inquiry (PSI). If you are on the old budget model, you do not need to use project performance for reporting. You can use PSI for operational reporting on a project. Only if you want to use project performance to view actuals data, follow the sequence of actions mentioned below (in the order mentioned below):

  • Install Family Pack M (apply the Family Pack M patch)
  • Complete the required project performance setups
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to No. (Performs initial load of actuals into base level summary tables)
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to Yes. (Performs initial load of commitments into base level summary tables)
  • Run "PRC: Load Project Performance Data" (Performs initial load of actuals into project performance summary tables)
If you are a new customer and want to use project performance, run the processes in the order mentioned below (in the order mentioned below):

  • Install Family Pack M (apply the Family Pack M patch)
  • Complete the required project performance setups
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to No. (Performs initial load of actuals into base level summary tables)
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to Yes. (Performs initial load of commitments into base level summary tables)
  • Run "PRC: Load Project Performance Data" (Performs initial load of actuals into project performance summary tables)
The table below lists the processes you need to run for initial project performance data load depending on whether you are an existing or new Oracle Projects customer.

Serial Number Steps for summarizing data into base level and project performance summary tables Existing Customers on Budgets (Old Budget Model) - only if using project performance for viewing actuals data Existing Customers on New Financial Plan model (Family Pack K & above) Family Pack M (new customer) 1 Install Family Pack M (apply the Family Pack M patch) N/A Yes Yes 2 Complete the required project performance set ups Yes Yes Yes 3 Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to No. (Performs initial load of actuals into base level summary tables) Yes Yes Yes 4 Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to Yes. (Performs initial load of commitments into base level summary tables) Yes Yes Yes 5 PRC: Load Project Performance Data (Performs initial load of actuals into project performance summary tables) Yes Yes Yes 6 PRC: Update Project Performance Data (The process creates report data in enterprise calendar and currency for financial plans, and needs to be run only for existing customers who upgrade from previous versions of Oracle Projects to Family Pack M) N/A Yes Yes Ongoing update of incremental data into base level and project performance summary tables This step applies to all customers (new or existing users of Oracle Projects). Before this step, you must have successfully completed the steps mentioned above for "initial load" of data. The series of steps mentioned below are in order. All steps below need to be completed sequentially, i.e., go to the next steps only when the prior step completes successfully.

For summarizing new timecards and expense reports (actuals) on a regular basis (weekly, bi-monthly, monthly etc.), the following concurrent processes need to be run one after the other (in the order mentioned below):

  • "PRC: Update Project and Resource Base Summaries" (this process runs for all projects - no parameters are required)
  • "PRC: Update Project Performance Data" (run this process for a specific project or range of projects)
What's New in each Family Pack M Rollup Are there any changes to concurrent processes in Oracle Project Management Family Pack M Roll up Patch 1? A new parameter has been introduced for project performance concurrent processes to allow it to run for a particular operating unit. This ensures that you can run the processes at different times for operating units that are located globally. Additionally, the From Project and To Project parameter field has been changed to a free text format and allows you to select the range from all the projects that are in the system

Are there any changes to concurrent processes in Oracle Project Management Family Pack M Roll up Patch 3? Oracle Projects now includes a new concurrent audit process, AUD: Project Performance Reporting Setup. You can run this process to generate a report that enables you to review setup information for Oracle Projects project performance reporting features. This capability enables you to quickly determine if all mandatory and optional setup parameters are defined correctly. The increased visibility that this report provides helps you to ensure that your project performance reporting summarization processes function correctly and do not generate reporting errors because of improper or incomplete setup.

The process PRC: Refresh Project Performance Data enables you to refresh all actual and plan amount data for a group of projects. Depending on factors such as the number of projects that you specify, and the number of workplan and financial plan versions that exist on each project, the refresh process can take a substantial time to complete. To help minimize processing time and provide you with greater flexibility in selecting the actual and plan amount data you want to refresh, this process now includes additional selection parameters. You can now choose whether to refresh only actual amounts or all amounts (plan and actual). In addition, you can optionally select the workplan and financial plan versions that you want to refresh.


Are there any changes to concurrent processes in Oracle Project Management Family Pack M Roll up Patch 4?The project performance summarization programs will continue to summarize projects even if some projects encounter processing errors. The PRC: Update Project Performance Data will display a list of projects that have exceptions during summarization
Frequently Asked Questions (FAQ) How often do I run the "Delete" project performance processes, i.e., how often to I truncate data? You should run "Delete" processes with caution. Once you run these processes, you will lose all the data that was summarized and available in project performance and project intelligence reports. Only if you want to get rid of all the data (for example - if you need to change project performance and/or business intelligence set up options) or you want to re-install project performance, your administrators should run these processes. The delete processes delete data for all projects in the system and cannot be run for a range of projects. Do not run these processes unless authorized by Oracle Support/Development.

What does it mean to run "Initial Loads" processes for new customers who bought Family Pack M? For new customers who bought Family Pack M, the initial load consists of following the 4 steps in the order mentioned below. Each step must complete successfully before you proceed to the next step.

  • Install Family Pack M (apply the Family Pack M patch)
  • Complete the required project performance setups
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to No. (Performs initial load of actuals into base level summary tables)
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to Yes. (Performs initial load of commitments into base level summary tables)
  • Run "PRC: Load Project Performance Data" (Performs initial load of actuals into project performance summary tables)
What does it mean to run "Initial Loads" processes for existing customers who are upgrading to Family Pack M? For existing customers who are upgrading to Family Pack M from prior Oracle Projects release, the initial load consists of following the 5 steps in the order mentioned below. Each step must complete successfully before you proceed to the next step. The following steps are necessary only if you are using the new financial plan model or if you are migrating to the new financial plan model, and want to use project performance for reporting actuals and budget amounts. If you are on the old budget model, then you can continue using Project Status Inquiry (PSI) for operational project reporting.

  • Install Family Pack M (apply the Family Pack M patch)
  • Complete the required project performance setups
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to No. (Performs initial load of actuals into base level summary tables)
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to Yes. (Performs initial load of commitments into base level summary tables)
  • Run "PRC: Load Project Performance Data" (Performs initial load of actuals into project performance summary tables)
  • Run "PRC: Update Project Performance Data" (If you are an existing customer, you must run this process. This process serves a different purpose and is needed only when existing customers upgrade from earlier version of Oracle Projects to Family Pack M. The process creates report data in enterprise calendar and currency data for financial plans)
What concurrent processes need to be run for summarizing incremental data after the initial loads have been completed? For incrementally summarizing new timecards and expense reports (actuals), the following concurrent processes need to be run one after the other:

  • "PRC: Update Project and Resource Base Summaries" (this process runs for all projects - no parameters are required)
  • "PRC: Update Project Performance Data" (run this process for a specific project or range of projects)
What concurrent processes need to be run for summarizing financial plan data? You do not need to run any concurrent processes to summarize financial plan data. Financial Plan data is summarized as soon as the changes are made and saved in the financial plans.

What do you mean by re-install of project performance? Re-install of project performance indicates a pre-condition: you have already completed installation of project performance (with Family Pack M) at least once. Now, for some reason (for example - if you need to change project performance and/or business intelligence set up options), if you want to start afresh by getting rid of all existing summarized data in base level and project performance summary tables, you do a re-install of project performance.

What steps need to be followed for re-install of project performance? Following steps need to be manually completed (in the order mentioned below) if you want to re-install project performance and re-summarize all the data in base level and project performance summary tables:

  • Set Profile option "PJI: Truncate PJI Summary Tables" to "yes" at the site level
  • Run "PRC: Delete Project Intelligence and Performance Reporting Data"
  • Set Profile option "PJI: Truncate PJI Summary Tables" to "yes" at the site level
  • Run "PRC: Delete Project Performance Reporting Data" process with "upgrade" parameter set to "yes"
  • If you need to change project performance set up options or Business Intelligence profile options, you can change it now.
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to No. (Performs initial load of actuals into base level summary tables)
  • Run "PRC: Load Project and Resource Base Summaries" with the ‘Extract Commitments” parameter set to Yes. (Performs initial load of commitments into base level summary tables)
  • Run "PRC: Load Project Performance Data" process (Performs initial load of actuals into project performance summary tables)
  • Run "PRC: Update Project Performance Data" process (This process serves a different purpose that usual only when existing customers upgrade from earlier version of Oracle Projects to Family Pack M. The process creates report data in enterprise calendar and currency data for financial plans)
What does "in-conjunction" means in concurrent process descriptions? "In-conjunction" in concurrent process description refers to a condition where 2 or more processes need to be run one after the other, i.e., in the order specified. In cases, where one process needs to be run after another (to ensure that the data is processed completely), the two processes are said to be running in-conjunction.

What is the difference between "upgrade" and "fresh install"? When existing customers of Oracle Projects (who are currently using Family Pack K or below) want to use functionalities delivered in Family Pack M, they are said to "upgrade" to Family Pack M. When new customers buy Oracle Projects Family Pack M and want to install it, they are said to be performing a "fresh install". For example - if you are an existing customer of Oracle Projects on Family Pack K or L, you will "upgrade" to Family Pack M.

Which processes can I run in parallel? How many instances of these processes can be run at the same time? To facilitate quick processing of summarizing data, "PRC: Load Project Performance Data" and "PRC: Update Project Performance Data" processes can be run in parallel. Up to 10 instances of these processes can be run at the same time. However, the parameters (range of projects) across different instances must not overlap, otherwise the process will error out. Thus, it is important to ensure that unique/distinct project ranges are selected when running these processes in parallel.

Why do the "PRC: Load Project and Resource Base Summaries" and "PRC: Update Project and Resource Base Summaries" processes do not run in parallel? "PRC: Load Project and Resource Base Summaries" and "PRC: Update Project and Resource Base Summaries" processes for base summary tables process data for all projects in bulk. As a result, at any given point in time, only one instance of these processes can run. If two users submit the same process, one will have to wait for the other to complete.

Can I run refresh processes to get new timecards and expenses in project performance? No. The refresh processes should be run only 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. To get new timecards and expenses in project performance, run the "PRC: Update Project and Resource Base Summaries" and "PRC: Update Project Performance Data" processes, in that order.

Why don’t I see WIP transactions in my project performance reports? If you are on 11.5.9 or earlier releases of Oracle e-business application, you must run "PRC: Update Transaction Attributes" concurrent process to see WIP transactions correctly in the project performance reports. This process needs to be run before running PRC: Load Project and Resource Base Summaries process, or PRC: Update Project and Resource Base Summaries process, or PRC: Refresh Project and Resource Base Summaries process, as and when needed. If you are currently on 11.5.10 and later releases of Oracle e-business application, you do not need to run this process to see WIP amounts in project performance reports.

When I run PRC: Update Project Performance Data why doesn't the the Project Type LOV show all project types? Please see MetaLink Note : 382617.1 



Troubleshooting What do I do if I get a ORA-06511: PL/SQL: cursor already open error? If you receive a ORA-06511: PL/SQL: cursor already open during PRC: Load Project Performance Data or PRC: Update Project Performance Data, please see MetaLink Note : 469120.1. Why do I see an ORA type error when I run the project performance concurrent processes? If you see an ORA type error on running the concurrent processes, check the set up profile options. Such profile options will include Business Intelligence profile options and "PJI Debug profile" option. Typically, these problems occur when the format of data entered for profile options do not match the format expected in defining the profile options. For example - if you enter the date in "mm/dd/yy" format, whereas profile option expects the date to be entered in "mm/dd/yyyy" format, then you may see this error. Similarly, for PJI Debug profile option, you need to enter a number from 1 to 5 to set levels at which debug messages are logged, rather than just say yes or no.

If you are on 11i Family Pack M Rollup Patch 3 or later, run the AUD: Project Performance Reporting Setup to verify that all required setups are completed.


What do I do if I get a 'This plan version is locked by another user' message in Project Management? If you receive a "This plan version is locked by another user" along with one or more messages starting with 'ORA-00054: resource busy and acquire with NOWAIT specified…' in any of the following flows:

- Baseline Budget
- Update Workplan
- Send Project Data from Microsoft Project
- Baseline Funding

The issue may be that a user has run "Process Structure Updates" on the current project and that this program has not completed. While this concurrent program is running a user cannot baseline a budget or update the workplan.


What do I do if I get a ‘ETC cost calculation failed’ message in PRC: Update Project Performance Data? You may receive the following messages in the output of the PRC: Update Project Performance Data:

1) ETC cost calculation failed. Task:136265, Res Assign Id:184945 , Budget VerId:185861, Txn Curr:USD


2) Exception reason of “A required cost rate is missing”

This may be caused by a workplan tht has rows that are missing planning amounts. In order to summarize and display actual amounts against the planned amount, the planned amount must be non-zero.

In workplan check whether the planned amount column has an indicator of ‘Cost and/or Conversion Rates are missing for some resources.’

Ensure that you either have rates defined for the resource or enter a cost rate over-ride for each resource showing the above message.

If you believe that the rates were not properly defaulted, check the following:

1) Make sure that resource class rate schedules are defined in the workplan setup.
2) Rates are defined for the given resource.
3) If the planning resource is an inventory item, ensure that the resource class rate schedule has a rate for the same Unit of Measure as the inventory item.

How can I speed up the summarization programs? There are a number of settings that impact the overall performance:


1) Project eligibility

The following programs will summarize transactions for eligible projects.

- PRC: Load Project and Resource Base Summaries
- PRC: Update Project and Resource Base Summaries

An eligible project is

1) The project status has the control action “Include in Status Reports” enabled.
2) If the project is closed, the project’s closure date must be after the date defined for the profile “PJI: Global Start Date Over-ride”. If this profile is not set, then the project’s closure date must be after the date defined for the profile “BIS: Global Start Date”

Customers can change the profile values to change the set of projects that are eligible for summarization.


2) Disable Transaction Currency

Summarizing by transaction currency can result in a large volume of stored data. Choose this option only if you need to build custom reports in transaction currency. The Transaction Currency is enabled via the Project Performance Setup screen. Note that changing this value requires a re-install of project performance.


3) Delete Historical Workplan Versions


Starting with 11iFP.M Rollup Patch 3 users can delete published workplan versions as long as the workplan version is not the baseline, latest published, or a published workplan version belonging to a program hierarchy.

Project performance stores data for each published workplan version. Deleting historical versions on a project will reduce the data volume and may improve the overall performance of workplan functionality.


4) Delete old financial plans


Users can delete baselined budgets and approved forecasts in the financial planning model as long as the budgets/forecasts are not marked as the original or current version.

Project performance stores data for each baselined budget and approved forecast. Deleting historical versions on a project will reduce the data volume and may improve the overall performance of financial planning.


What do I do if I get a ORA-20000: error during Load/Update Project and Resource Base Summaries? If you receive an ORA-20000 error when running PRC: Load Project and Resource Base Summaries or PRC: Update Project and Resource Base Summaries, and if the error looks like “FDPSTP failed due to ORA-20000: The summarization process failed. Please contact your system administrator". Followed by text like “ORA-06512: at "APPS.PJI_FM_SUM_MAIN", line 1694 ORA-06512: at line 1”

Then the issue may be that one or more of the PRC: Process Project Financial Data concurrent requests did not complete with a status of “Normal”. When the PRC: Load or Update Project and Resource Base Summaries runs, it creates multiple child concurrent requests for the PRC: Process Project Financial Data concurrent program. If one or more of these programs does not complete with a phase of “Completed” and a status of ‘Normal” then the parent program may fail with the above error.

Please review the child concurrent programs and resolve any issues (incorrect printer setup…) and re-submit the base program.

Why don’t I see amounts for all of my tasks? If you do not see data for specific tasks it is possible that you have created new tasks and have not performed the “Process Updates” step. When new tasks are created, the “Process Updates” must be run before any planned or actual amounts are summarized for the new tasks.

If you navigate to the Workplan or Reporting tab, you will see a message like “The structure of the project or program has changed. You can make additional changes or select Process Updates to submit the Process Structure Updates process. You must run this process to ensure that plan and actual information is synchronized with the latest changed structure.”. This message indicates that you must run Process Updates before you will see plan or actual data for the new/changed tasks.

How does the PRC: Update Project Performance concurrent program determine what to summarize? Users may notice that the time taken to run PRC: Update Project Performance may differ significantly between different runs. This is likely due to different types of data being summarized.

The program first selects all projects based on the program parameters (operating unit, project type, project organization, project range). If any of these projects are part of a program, then all projects in those programs are added to the list of projects to be summarized.

For each of the projects to be summarized, the concurrent program processes the following items

1) New actual and commitment transactions that have been summarized by the PRC: Update Project and Resource Base Summaries program.

2) Project Performance “Events”. When a user performs an action on-line that requires data to be summarized, some activities are logged as an event. This event is processed the next time that project is summarized. Some activities that create events are:

a) adding or removing a resource breakdown structure to a project or program

b) adding a project to a program

3) Transactions that were not processed in previous runs due to missing conversion rates or missing periods.

4) Financial plans created in Family Pack K or L that have been partially summarized. These financial plans require 2 runs to be fully summarized. The PRC: Load Project Performance Data performs the first part of the summarization while the first run of PRC: Update Project Performance Data will perform the second (and last) part of the summarization.

How To Respond To Reporting Tab Message For Structure Change Displayed For Program Sub Projects?
Q1: The user receives the follwing error message when viewing the reporting tab:

The structure of the project or program has changed. You can make additional
changes or select Process Updates to submit the Process Structure Updates
process. You must run this process to ensure that plan and actual information
is synchronized with the latest changed structure.

On a project with a program in Project Management self service applications;
Navigate: >>Financial tab
Update or create new tasks on the Financial tab of a fully shared structure
Run the "Process Updates" function

Receive the following message:
! Information
1. The Process Structure process is in progress. Until this process
completes, you cannot make
changes to the structure or view the latest plan and actual information for
the structure.
2. View Concurrent Process - Select to view the status of the process.

View the process and it finishes to completion.
Go back to the Financial tab and the message is now gone.

But, go to the Reporting tab and an information message is there but does not go away.

Receive the following message on the Reporting tab:
! Information
The structure of the project or program has changed. You can make additional
changes or select
Process Updates to submit the Process Structure Updates process.
You must run this process to ensure that plan and actual information is
synchronized with the latest changed structure.

Even though the message states the process has changed, if you click on the
link to view the process, there is no process updates process listed.
The process updates drop down menu is now not displayed on the Workplan or
Financial Plan tab's LOV.

The user cannot proceed with the Reporting tab message displayed.
Why is the message displayed when the Process Structure Updates process was run?
How do we clear this message?

Solution A1: If a program has project associations and one of these projects within the program has a structure
change, then the "Process Structure updates" message will appear if any sub-project has not had the
Process Structure Updates process run.

Run the Process Structure Updates process for any project within the program that had structure
updates.

Contact Oracle Projects Support for more information of a possible query to identify the projects
within a program that need the Process Structure Updates process run.

Reference:
Bug 7027502
Enhancement Bug 7366276


PRC: Update Project Performance Data ORA-20040:Overlap [ID 391069
Multiple Project Performance processes collide if two or more processes overlap project ranges. However, sometimes Project Performance process is automatically kicked-off when making workplan updates on a program. If the automatic process collides with a another process, that process fails with ORA-20040.

Steps to ReproduceLogin with Project Manager responsibility :
1. Create a program
2. Attach a project to a task
3. In the Workplan->Tasks screen
     a. Choose Apply and Process Updates
     b. Select Go button
4. Results Two concurrent processes are kicked-off - 'PRC:Process Structure Updates' and 'PRC:Update Project Performance Data'.

If the 'PRC:Update Project Performance Data' is running for a range of projects which include the project above, we get the error :

'Cause: FDPSTP failed due to ORA-20040: The projects in this request overlap with the projects of one or more submitted processes. Please wait for the submitted processes to complete successfully before you sub'
CauseIf the project is linked to a program, Publishing the Workplan will internally submit "PRC: Update Project Performance Data" for the program linked projects".  If PRC: 

No comments:

Post a Comment

Please review my topic and update your comments

Note: only a member of this blog may post a comment.