My Oracle Support Banner

Error In Primavera Gateway "Either Filter Or A Valid ProjectObjectId Parameter Must Be Specified" When Running a Primavera Gateway Synchronization (Doc ID 1585120.1)

Last updated on MAY 15, 2023

Applies to:

Primavera Gateway - Version 1.0 and later
Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 8.2.4.0 and later
Primavera Unifier Cloud Service - Version 9.7 and later
Information in this document applies to any platform.

Symptoms

When attempting to run an project data business flow, the following error occurs on the Load from Primavera side step:

Flow Step 'Load from Primavera side' contains error: 'Either filter or a valid ProjectObjectId parameter must be specified.'. Please drill down into the Job to see the details.

Drilling down into the Load from Primavera side step contains the following:

Failure: Either filter or a valid ProjectObjectId parameter must be specified.

com.oracle.pgbu.pdi.provider.ProviderException: Either filter or a valid ProjectObjectId parameter must be specified.

at com.oracle.pgbu.pdi.p6provider.c.b.load(ExportProjectLoadStep.java:68)
at com.oracle.pgbu.pdi.service.jobs.JobSimulator.executeLoadStep(JobSimulator.java:358)
at com.oracle.pgbu.pdi.service.jobs.JobSimulator.executeSourceSteps(JobSimulator.java:265)
at com.oracle.pgbu.pdi.service.jobs.JobSimulator.access$000(JobSimulator.java:52)
at com.oracle.pgbu.pdi.service.jobs.JobSimulator$SourceStepsExecutor.run(JobSimulator.java:525)
at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

 

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
Cause
 Cause 1: Invalid or no project id specified in business flow or synchronization parameters.
 Cause 2: The P6 Deployment is not configured correctly.
 Cause 3: The user configured on the P6 Deployment does not have access to the project
Solution
 Solution to Cause 1:
 Solution to Cause 2:
 Solution to Cause 3:


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