My Oracle Support Banner

Scheduled Service "Use Service's Run Time" Option to Change Data Date Does Not Ignore Seconds (Doc ID 2568708.1)

Last updated on JULY 23, 2019

Applies to:

Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 17.12.10.0 to 17.12.12.0 [Release 17.12]
Information in this document applies to any platform.

Symptoms

DESCRIPTION OF PROBLEM:
--------------------------------

When using the "Use Service's Run Time" option to change a data date for any of the following jobs:

The data date can be stored in the database (PROJECT.last_recalc_date) with seconds in the timestamp other than 00.

STEPS TO REPRODUCE:
--------------------------

  1. Create a project in P6.
  2. Add a single activity to the project.
  3. Browse to Administration > Scheduled Services > Project.
  4. Click any of the following:
    • Add > Apply Actuals
    • Add > Schedule
    • Add > Level

  5. For the job:
    • Click Project settings.
    • Add the project created in step 1.
    • Set "Change Data Date" to "Use Service's Run Time"
    • Save Changes.

  6. Run the service on-demand.
  7. Once the job completes, review the data date in the database (PMDB) using the following SQL:

EXPECTED OUTCOME:
------------------------

When using the "Use Service's Run Time" option to change a data date for an Apply Actuals, Schedule, or Level job
, servicesshould only select down to the minute for the service's run time so the seconds are stored as "00".

For example:

If using SYSDATE to set the PROJECT.LAST_RECALC_DATE, you can set the column using "to_date(to_char(sysdate,'DD-MON-YYYY HH24:MI'))" which will always set the seconds to 00.

ADDITIONAL INFO:
----------------------

  1. All dependency data *_start_date fields (such as TASK, TASKRSRC, etc.) to store seconds in the timestamp after the job is run.
  2. Activities created through P6 Web Services (if not defining a start date) to use the project's data date and generate dates with seconds other than 00 in the timestamp.
  3. This situation has downstream effects when calculating associated data (and if the duration was incorrectly calculated due to date rounding). The SummarizeCBS job service which can populate the ADMUSER.PROJECTCOSTCBSSPREAD (based on an expense assigned to the activity) will results in a mismatch for its associated data.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.