How to add an end date code for resources.

You can avoid pre-populating all of the code values and just add them on the fly. First create a Code called End Date in Summary & Settings (as described above). Do not create any code values under End Date (for now). Then add End Date as a column in your Resource List grid. When you go to assign a new end date to a particular resource, you can create a code value on-the-fly at the bottom of the popup dialog. Enter ‘29-Sep-20’ as the value name and ID. See below (I’m using Department as an example code.)

 

S-Curve report in P6 EPPM

This report consists of a chart and a table. The chart shows Planned Labor Units on the y-axis and date on the x-axis and plots the Original Planned Labor Units, Achieved versus Plan, Additional Work and Milestone Dates. The table gives the Total Target Planned Work, Planned Work To Date, Cancelled Work To Date, Additional Work To Date, Planned Work Achieved To Date, Total Work Achieved To Date, Manhours Planned, Manhours Achieved, Lost Time Manhours To Date, Actual Percent Complete To Date, Target Percent Complete To Date, and Actual Manhours To Date.

Location

1. Click Reports.
2. On the Report page:
   1. Click View and select Reports.
   2. Expand the P6Reports folder.
   3. Expand the Project folder.
   4. Click S Curve.
   
   
    

 

How to create a S-Curve in P6 Professional by TenSix Consulting

 https://tensix.com/2020/05/how-to-create-s-curve-in-primavera-p6-professional/

Construction & Engineering Product Documentation

Everything you want to know about the C&E product suite.

https://docs.oracle.com/en/industries/construction-engineering/index.html 

Change the company name in Cloud Adminstration

Manage Companies

The Manage Companies table in Primavera Administration enables you to manage companies for your applications. A company represents a logical container of users in Primavera Administration.

There are two types of companies:

• Owner company: An owner company has been created for you. A single owner company is required by Primavera Administration. You can modify certain aspects of the owner company (including the company full name and the password policy). It is not possible to delete an owner company.
• Partner companies: A partner company is a separate entity from the owner company that needs to access your applications. Examples of partner companies include vendors, resellers, subcontractors, suppliers, and other consultants. Partner companies are listed under the owner company on the left side of the Manage Companies page.

  When you add a partner company in Primavera Administration, you can also assign one or more applications to the company. If you assign Primavera Unifier, the partner company is also created within that application.

Click the Manage Companies tab to view the Manage Companies table.

Connecting OPC to P6

 https://www.youtube.com/watch?v=Cw1DS9oYNQs

Prerequisites to Sync P6 Cloud and On-Premises Data

 

Administering Analytics on the Cloud

 https://docs.oracle.com/cd/F25683_01/index.htm

Error Logging Into P6 Professional "Unable to connect to the database. Please run the database configuration tool or contact your administrator" (Doc ID 2370322.1)

 

---

In this Document

Symptoms

Changes

Cause

Solution

References

---

Oracle Confidential INTERNAL - Do not distribute to customer (OracleConfidential). Reason: km issue Created from SR 3-16914810421[This section is not visible to customers.]

Applies to:

Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 18.2 and later
Information in this document applies to any platform.

Symptoms

When user is attempting to log into P6 Professional, the following error is received:

Error
Unable to connect to the database. Please run the database configuration tool or contact your administrator.

The user is unable to access P6 Professional, but, is able to log into P6Web.

Steps to Reproduce
1. Launch P6 Professional.
2. Enter login credentials.
3. Observe connection is not made - error is returned.

Changes

 

Cause

This is caused by a defect in P6 EPPM.

A defect in the POPULATE_UACCESS stored procedure causes it to create 2 UACCESS records for the same proj_id which can result in a a unique constraint violation during login to P6 Professional by a non-admin superuser.  This was determined through the following bug request - Bug 27683951 - P6 PROFESSIONAL LOGIN ERROR "UNABLE TO CONNECT - PLEASE RUN THE DATABASE CONFIG"

Solution

This issue has been resolved, and the fix has been included as of release 18.4.  The latest patchset can be downloaded from:

• What Are The Latest Patch Sets For Primavera P6 Release 18 (Both PPM and EPPM Releases)?(Doc ID 2449247.1)

To implement the solution, please execute the following steps:

• Download and review the README documentation and prerequisites for the Patch Set.
• Ensure that you have taken a backup of your system before applying the recommended Patch Set.
• Apply the Patch Set in a test environment.
• Retest the issue.
• Implement the solution as appropriate on other environments.
  
  

Cloud Hosted Customers

• Enter an SR for the appropriate Solution and reference this KM as a solution to the issue.
• Work with Support to apply patch or upgrade account.
• After notification that upgrade, or patch install is complete, have users ensure the patch resolves the issue.
• Approve closure of SR when the fix has been applied and verified.

 

Workaround Available

To workaround this defect (until P6 can be upgraded):

1. Recreate the populate_uaccess stored procedure to prevent more than one proj_id row being created in the UACCESS table. 
2. Remove any potential duplicate rows created in the OBSPROJ table as a result of the UACCESS stored procedure.

For low level steps to implement the workaround:

1. Download the following script for an updated copy of the populate_uaccess stored procedure (with fix):  populate_uaccess_fix.sql
2. Connect to the database as the schema owner (by default, ADMUSER)
3. Execute the script to recreate the stored procedure.  Note, this script can be run against any 18.x, 17.x, 16.x, 15.x, or 8.4 database
4. Rebuild the OBSPROJ table by completing steps outlined in the following knowledge base document - Doc id 908570.1 - How to rebuild the obsproj table

 

Note:  There is a 2nd article that ALSO must be run.  It contains a script by the same name (populate_uaccess_fix.sql) that should be run.  Run the populate_uaccess_fix.sql from this article, followed by the populate_access_fix.sql from Doc id 2452802.1.

After both scripts have been run, rebuild the obsproj table.

Refer to the attachment in Error 'Unable to connect to the database. Please run the database configuration tool or contact your administrator' When Logging into P6 Professional (Doc ID 2452802.1)

To Bottom

P6 EPPM - What's New for 20.9

 https://docs.oracle.com/cd/F25599_01/English/User_Guides/whats_new/whats_new_in_p6_eppm.pdf

Project Governance Non-Compliance Report

Description

Lists core project-level settings for each project, highlighting setting values that are not compliant.
Location
Click Reports.
On the Report page:
Click the Reports tab.
Expand the P6Reports folder.
Expand the Administrative folder.
Click Project Governance Non-Compliance Report.

 

Working with documents in P6 Pro

 https://docs.oracle.com/cd/F25600_01/client_help/ar_EG/helpmain.htm?toc.htm?work_products_and_documents.htm

 

Working with documents in P6 web

 https://docs.oracle.com/cd/F25599_01/p6help/en/index.html