User Added To 'P6 Analytics' Module Within P6 EPPM (After User Already Created And Publish Security Previously Executed) Not Moving Associated User And Security To Data Warehouse Through LOAD_PLAN_REALTIME_GLOBAL Or LOAD_PLAN_DAILY

(Doc ID 2377261.1)

Last updated on APRIL 19, 2018

Applies to:

Primavera Analytics Cloud Service - Version 17.11.2.0 and later
Primavera Data Warehouse - Version 17.11.2.0 and later
Primavera Analytics - Version 17.11.2.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
-----------------------
When assigning the P6 Analytics module to a user which has already been published to the extended schema the following two issues occur after re-executing the 'Publish Security' global scheduled service:


EXPECTED BEHAVIOR
-----------------------
When the P6 Analytics module is assigned to a user who has already been previously created/published, re-execution of the LOAD_PLAN_REALTIME_GLOBAL load plan should bring the associated user and user security into Data Warehouse after next execution of the 'Publish Security' global scheduled service within P6.

Additionally, LOAD_PLAN_DAILY should be capturing this data as well.

STEPS TO REPRODUCE
-----------------------
The issue can be reproduced at will with the following steps:

  1. Create a user in P6 (without initially assigning to the P6 Analytics module)
  2. Run P6 EPPM Publish Security global scheduled service.  Note, once this completes in P6, notice the LOAD_PLAN_REALTIME_GLOBAL kick off.
  3. Assign P6 Analytics module to user in P6
  4. P6 EPPM Publish Security global scheduled service.  Note, once this completes in P6, notice the LOAD_PLAN_REALTIME_GLOBAL kick off.
  5. Results:
    • The user may or may not come into w_users_ss table (preventing loading of the w_user_s and associated security tables).
    • When this occurs, execution of LOAD_PLAN_DAILY also does not bring the associated user and security data into Data Warehouse.

 

ADDITIONAL INFO:
-----------------------
Following SQL can be utilized to confirm this issue:

  1. Connect to database as staruser
  2. Execute following SQL to confirm the user is assigned to P6 Analytics module:
    • select name, moduletypecode, users.lastupdatedate, usermoduleaccess.lastupdatedate
      from users@dslink01, usermoduleaccess@dslink01
      where userobjectid=users.objectid and moduletypecode = 'P6 Analytics';
  3. Login to P6 EPPM and confirm that 'Publish Security' Executed after the module assignment:
    1. Login to P6
    2. Select Administration > Scheduled Services
    3. Select Global
    4. Confirm that the Publish Security ran after the date the module was assigned
  4. Execute the following to confirm the user module assignments are in Data Warehouse:
    • select um.userobjectid, u.name, count(um.userobjectid)
      from w_usermoduleaccess_ss um, users@dslink01 u
      where um.userobjectid=u.objectid and datasource_id = 1
      group by um.userobjectid, u.name;
  5. Execute the following to confirm the user is not in w_user_ss:
    • select user_name from w_user_ss where datasource_id = 1;
  6. If the user is not in w_user_ss, the associated user and security data will not move into the Data Warehouse source tables.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
When this issue occurs, any analysis / data within Primavera Analytics the user should have access to display will result in 'No Results'.

Changes

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms