Cost Sheet Containing Transactions That Do Not Match the Data Source
Last updated on JUNE 28, 2017
Applies to:Primavera Unifier Cloud Service - Version N/A and later
Primavera Unifier - Version 9.7 and later
Information in this document applies to any platform.
On Unifier : Any Version
Expected Results: The Cost Sheet cell details should only contain transactions for the Data Source defined. E.g., 'Contracts (Approved)'
Actual Results: The Cost Sheet cell details is containing transactions that do not match the data source. E.g., 'Contracts (Pending)'
The column in the Cost sheet is defined to use a Single Source. These values roll up from other sources including Cost type Business Processes.
In this example the data source would be 'Contracts (Approved)', where "Contracts" is the name of the Business Process, and "(Approved)" is the Status of the record whose transaction should roll up to the column's Cell Details.
In this case the user opens the record and changes the Status from 'Pending' to 'Approved' but does not click on the Send and/or Finish Editing button and instead saves it as a Draft.
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