Using CSV Integration for Summary Payment Application SOV

You can use a comma-separated values (CSV) file to save cost allocation (CA) data for Base Commit and Change Commit records of the Summary Payment Application Schedule of Values (SOV) type.

The Payment Application of the Summary Payment Application (SPA) SOV type supports record creation, line item creation, and cost allocation creation through CSV integration.

If payment line items exist in the Standard tab, CSV import of line items is not permitted.

CSV Row Types

The CA row contains cost allocation information, including the following fields:

• Cost Code
• Short Description
• Quantity
• Amount

Enter all costed line item details in the CA row. You can add multiple cost allocation line items to the CSV file by using multiple CAA rows.

If the CSV template includes cost allocation details, but the BP design does not allow cost breakdown, CSV import fails and returns an error message.

Creating Lump Sum and Entering Unit Cost details

The D row contains summary line item information. If the Cost Line Item type is Unit Cost, enter the Unit Cost in the D row.

Based on the Cost Line Item type in the D row, the system checks for the required fields for that line item type.

Modifying Committed Lines

The CSV template includes a Reference field that you can use to add lines that exist in a reference commit. The system uses the Reference value to select a specific row in the committed lines (SOV).

Note:

The availability of the Reference field depends on the BP design. If the field is not present in the Detail Form integration interface, you cannot modify committed lines.

The Costed Line Item that needs to be updated is identified by the Reference value and the Cost Code. The Reference column label is the label set for sovlinum, and it appears after the CA column.

After record creation, all Costed Line Items that belong to the selected line item, including the Summary Line Item and child line items, are added to the record.

Payment Application

For the Payment Application of SPA SOV type, the CA row includes columns similar to the details row.

Unit Cost

The exported CSV template includes these additional fields:

• Cost Code
• Short Description
• Quantity
• Unit Cost
• Amount

Enter the unit cost value in either the D row or the CA row, but not both. For variable unit cost lines, enter the unit cost in the CA row.

For Lump Sum and Fixed Unit Cost line items, the Unit Cost value in the CA row is ignored, even when the CA row includes a Unit Cost column.

When you import Lump Sum or Fixed Unit Cost line items, and the CA row includes values based on the cost line item type in the D row, the system checks for the required fields.

You can create both Base Commit and Change Commit records with variable unit cost line items. In the D row for the summary line item, if uuu_li_cost_type is set to Variable Unit Cost, and you enter the Unit Cost in the CA rows, the system creates the variable Unit Cost line items.

If you enter a unit cost value and select Variable Unit Cost as the cost line item type in the summary D row, the system displays this message: Unit Cost is not allowed on summary line for variable unit cost lines.

If the BP design does not allow cost breakdown, and the CSV template includes cost allocation details, the system displays this message: Business Process design does not allow cost allocation.