SOV Summary Payment Applications Sheets and Business Processes

The Summary Payment Applications Schedule of Values (Summary Payment Applications SOV) allows users to allocate cost to line items based on the line item type (Lump Sum or Unit Cost). Use the Summary Payment Applications SOV type in association with Commit and Spends Business Processes (BPs) that are designed for Summary Payment Applications SOV (SPA SOV) type.

For a given Project/Shell, there can be multiple Payment Application Business Processes of Summary Payment Applications SOV Type.

For Base Commits Business Processes (BPs) with SOV type of "Summary Payment Applications," a special behavior line item has been provided to allow you to add further cost distribution details to the line items.

Note: Cost allocation/distribution can be done only for line items that are in the Standard tab of the Base Commits and Change Commits BPs of SPA SOV type.

The Standard detail tab of the properties window contains two options:

Click Add and select the appropriate option. For more information, see the topic "Cost Distribution Grid log columns," below.

The Summary Payment Applications sub-node will be available under the Schedule of Values node only if a Base Commits or Change Commits of SOV type Summary Payment Applications is deployed in uDesigner.

The Grid functionality is not supported for the Base Commits BP with SOV type of "Summary Payment Applications."

When a Base Commits BP with SOV type of "Summary Payment Applications" is configured to auto-populate Data Elements on a Payment Application with values from the Base Commits, the runtime auto-populate occurs for the:

The Audit log, at the record level, captures the Line Item as well as the Costed Line Item changes (taking place through Web Services) for both Base Commits and Change Commits BPs with SOV type of "Summary Payment Applications." In this case the Event field of the Audit Log for the BP displays "Line Items: Costed Line Item." In other words, any updates that are made to the Costed Line Items, through Update calls, will have the Event as “Costed Line Item” for Costed Line Item changes.

Grid functionality is not supported for Change Commits BPs with SOV type of "Summary Payment Applications."

Summary Payment Applications SOV sheet is created when the Base Commits BP reaches the terminal step as set in uDesigner.

Note: If a BP has been set up in uDesigner to automatically create a Summary Payment Applications SOV sheet upon the end step, the following procedures are not applicable.

See Also

Unifier Business Processes with Special Behaviors

Schedule of Values (SOV) Sheets and Business Processes

Payment Application Business Processes

General Spends Business Processes

Change Commit Business Processes

SOV Summary Payment Application Business Process (Standard View)

Overpayment in Summary Payment Applications SOV

Totaling Cost Breakdown Values

Request for Bid (RFB) Business Processes

Lease Business Processes

Reservation Business Process

In This Section

Adding Values to a Summary Payment Applications SOV Sheet

Summary Payment Applications SOV Sheet window

Grid Support in Base Commit and Change Commit

Summary Payment Application Grid Column Total



Legal Notices | Your Privacy Rights
Copyright © 1998, 2022

Last Published Monday, April 11, 2022