Change Commit Business Processes
Change commit business processes (BPs) enable you to change the value of a base commit and to also update the SOV created by the contract. This BP is also known as a change order. Change commit BPs are designed in uDesigner. For more information, refer to the Unifier uDesigner User Guide.
When multiple Base Commit BPs with Payment Applications and corresponding SOVs are included in a project/shell, you can create multiple Change Commit records that update corresponding payment application SOVs.
You can use CSV import to create change commit BPs or to add SOV line items for an existing BP. You can export change commit BP templates at the log level (for header and line item templates with no data exported) and at the record level (for line item templates with SOV data exported). You can then modify the templates and import them to create records (at the log level) or to add line items to an existing record (at the record level).
An Integration interface must be defined to support CSV import. If you cannot import the file, contact your administrator.
Also, records can be created and line items added using Integration through Web Services. Integration through Web Services must be coordinated with Oracle Primavera Unifier Consulting Services.
When a Change Commit line item is selected using the Commit Line Item Picker, any data elements (DEs) present in both the SOV Line Picker Log and the Detail Form of the Change Commit, are auto-populated to the Change Commit Detail Form without requiring uDesigner configuration of the auto-population. If the picker value is changed and another line is selected, the auto-populate occurs again, overwriting Detail Form values with values from the new line. However, when the picker is cleared, any values in the auto-populated DEs are not cleared and remain in the form.
When a Change Commit line creates an SOV line, DEs selected for Show in SOV in the Base Commit configuration that are also present in the Detail Form (Standard tab) of the Change Commit cause the DE values to populate the column values within the SOV. Additionally, for Change Commit line items where you select an existing line using the Commit Line Item Picker (uuu_sovlinum) to update, the values auto-populate from the SOV. If you update the values of these DEs in the Detail Form, the values are updated in the SOV after the Change Commit reaches the defined terminal step.
In This Section
Import New Change Commit Records
Import Change Commit Line Items Into a BP
Linked Elements for Changed Commit and General Spends SOV Types
Last Published Friday, October 17, 2025