Symon(bg) Showing In Activities View In Last Modified By Column

(Doc ID 2307128.1)

Last updated on OCTOBER 09, 2017

Applies to:

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

Symptoms

ACTUAL BEHAVIOR

When making changes like adding constraints, modifying finish dates, or deleting activities, the last user to update appears to be Symon(bg) instead of the user who made the change. In the database, the created_user column is being set to Symon(bg) for activities.

EXPECTED BEHAVIOR

The last update should reflect the user who made the update.

STEPS

The issue can be reproduced at will with the following steps:
1. Log in
2. Do an activity while SYMON is running
3. Check the TASK table in the database and notice the create_user and update_user columns have values symon(bg) and not the user making the changes.

BUSINESS IMPACT

The issue has the following business impact:
Due to this issue, users cannot see the last user making changes when a change is made while SYMON is running.

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