My Oracle Support Banner

Users Are Able To Create Change Commit Line Items Without the Required Short Description In the Cost Breakdown (Doc ID 2960508.1)

Last updated on JULY 27, 2023

Applies to:

Primavera Unifier Cloud Service - Version 18.1 and later
Primavera Unifier - Version 18.8 and later
Information in this document applies to any platform.


Users are able to create, and approve, Change Commit type Business Process (BP) (Summary Payment Application) records with line items that have a blank/empty/null entry for the Short Description in the Cost Breakdown which is a Required entry. This results in ${a(r_x_li).short_desc} being populated to the Schedule of Values (SOV), and resulting Payment Applications and Cost Sheet transaction details.

The system should stop users from saving line items when there is an blank/empty/null Required field in the Cost Breakdown.

The issue can be reproduced at will with the following steps:

  1. Sign into to Unifier.
  2. Navigate to the workspace where the Change Commit BP record can be created.
  3. Select Create > select workflow.
  4. In new record, fill in required fields.
  5. Navigate to Cost Line Items.
  6. Add > Lump Sum.
  7. Enter ONLY an Amount (leave Short Description empty).
  8. Navigate to Cost Breakdown
  9. Select Add Remaining > select any WBS code (leave Short Description empty).
  10. Navigate back to Line Item and populate a Short Description and click "Save".
  11. Submit/Send the record through the Terminal Status.
  12. Open the record, click on the hamburger menu, select SOV.
  13. Notice the description DE for the line item shows ${a(r_x_li).short_desc}.


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

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