The Schedule of Values (SOV) for Payment Application functionality provides a way to assemble information from the Base commits and Change commits (Commit), as well as the payment history, in an SOV sheet. You can open the SOV sheet either from the Schedule of Values (SOV) log, or from within a payment application record (the record must be in an editable mode).
When the base commit record is created and reaches a specified terminal status (for example, Approved), the SOV sheet is automatically created, and line items display as rows. As change commits are created and approved (or other specified status), they are added automatically to the SOV sheet. As payment records are created, these also will affect the SOV.
Data that is displayed on the SOV sheet will depend on the columns that have been added to the SOV structure.
The SOV displays the source information from the base commit any change commits. The source for each line can be one or more lines from one or more records.
Depending on the design of the associated business processes, the SOV may list each line entry for the base commit and all change commits as separate line items, or it may group entries with the same CBS code and display the total.
When you are working with the SOV sheets, in a Project/Shell, you can enter the item number (Item # field) for each of the SOV lines:
- Unifier stores the SOV sheet based on the Item # column.
- When line items roll up to the SOV sheet from the Base Commit and Change Commit BP records, then the system generates the values in the Item # field.
- The Item # for each SOV sheet starts with 000010 and this value is incremented by 10. So, if there are 2 lines coming from the Base Commit, then the values seen are: 000010 and 000020.
- Although the system generates these numbers, you can edit the numbers. This enables you to reorder the SOV lines. To edit the values, double-click on the field. Entries to this field must be Numeric. No alphanumeric fields are allowed. Similarly, no other characters such as punctuation marks, non ISO characters, -ve sign etc. are permitted. For the summary lines, you cannot enter dot "." character. Dots are reserved for costed lines.
- If you edit an existing value, for example 000030, and enter 27, then the value seen in the field will be 000027. The leading zeros are added by the system in order to align and help sort all the values in the column.
- The values entered should be in the range of 000000 to 999999.
- The subsequent lines coming from the Change Commit (CC )records (with reference to the above mentioned Base Commit (BC) record) can be seen in the SOV sheet with increments of 10.
- If you make any changes to the Item # field, click Apply to save the values in the column and to change the Sort order of the rows. The new sort order is maintained in the database and next time when you open the SOV sheet the sort order is displayed in the SOV sheet be based on the last saved view.
For Payment Applications SOV and Summary Payment Applications SOV, the structure is copied from the line item grid structure of the Payment Application BP.
When a Payment Application BP references a Base Commits of the Summary Payment Applications SOV, the line items of the Payment Application BP will reflect the line items of the Base Commits as well as any associated Change Commits.
In a Payment Application BP referring to the commits and the Summary Payment Applications SOV type, depending on the BP setup, you can:
- Include only one Payment Application record, or
- Include multiple Payment Application records
See Payment Application Business Processes for details.
To open the Line Item window of a Payment Application BP form, click Add. The window displays a list of line items from the Base Commits (and any Chance Commits), and the values are populated if auto-population (from Base Commits and Change Commits) has been defined.
To view the associated SOV sheet
- In the Navigator, click Cost Manager > Schedule of Values > Payment Applications. The Schedule of Values: Payment Applications log opens. The SOVs are listed by their associated base comment record numbers and descriptions (SOV Base Record and SOV Description).
- Select an SOV and click Open (or double-click the record). The Schedule of Values sheet for the base commit associated with the payment application opens.
- You can optionally split the grid so that the cost codes or other columns are always in view on the left, allowing you to scroll through other columns to view data on the right.
- To split the grid, click the Split button.
- You can click the Freeze button to make the left side of the vertical bar unmovable.
- To unfreeze the left side, click the Freeze button again. To remove the split, click the Split button again
- To view source information from the base commit and/or change commits, locate the Scheduled Value column.
Note: This assumes that a column has been added to the SOV that is associated with the datasource "Scheduled Value." The column name may vary. Click the link in a cell. The Cell Details window opens, displaying the source of the line item information -- the commit record(s) with a line item entry for that CBS code.
- Click Scheduled Value link (the column header) to open the View Column window and review the source information (Name, Data Source, Date Format, and Display Mode).
- Click the Close button to close the window.
To view the associated SOV sheet from within the payment application BP
- In the Navigator, click Logs > Payment Applications.
- Select a Payment Application record and click Open (or double-click the record). The Payment Application form opens.
- Click the SOV button from the record toolbar to open the Schedule of Values window for the Application BP record that you selected.
Note: Ensure that the form is not in a view-only mode.
- Click the Close button to close the window.