Import New Summary Payment Application Records

You can export a CSV or Excel template that includes the upper form and detail form fields as columns. These fields include the header fields from the upper form and the line item SOV fields from the detail form, including the detail line item fields defined in Integration.

You can modify the exported CSV or Excel template and import it to create the upper form header information and the detail line items for the new business process.

To export a copy of the summary payment application business process template

  1. Navigate to the summary payment application business process log.
  2. Click the Actions menu and select Export CSV Template or Export Microsoft Excel Template.

Depending on your browser, the template will automatically be downloaded to your computer, or you will be prompted to download it manually.

To modify the exported summary payment application business process template

  1. Open the exported CSV or Excel file in Microsoft Excel.
  2. Enter the business process information into the spreadsheet. Each upper form header record must begin with an "H". Each line item must begin with a "D". For multiple tabs, you must enter appropriate tab name in the Tab Name column.
  3. Enter data into the required fields, as well as non-required fields as needed.

    Notes:

    • Data for formula-based columns is ignored.
    • If auto-populated data is provided, the system will import the value, and will not override the imported values except for fields auto-populated by Base Commit, Change Commit, or from SOV.
    • Any line items with the Amount equal to zero will not be imported.
    • Use to add new business process records only; not to modify existing business processes.
    • For data to import correctly, you might have to change some of the cells in the CSV file to Text type. For example, if you have a CBS code of 1-1, Microsoft Excel can interpret this entry as a month‐day combination and reformat it to Jan-1. In this case, your data import will fail because this data is now an invalid CBS code.

To import the summary payment application business process template

  1. Navigate to the summary payment application business process log.
  2. Click the Actions menu and hover over Import.
  3. Select either Data From CSV File or Data From Microsoft Excel File.
  4. Browse to select the file to import, then click Next.
  5. Add any attachments to the import.
  6. Click Upload when finished.

    If there are any import errors, you can open the CSV file to view and correct the error. No records are imported if any rows contain an import error.

    Note: If the Add Only SOV edited line items option is selected in uDesigner, only the edited line items will be saved when the summary payment application template is imported through CSV, Excel, or RESTful services.

Adding Partial Line Items by way of CSV or Excel import or RESTful web services

When you add partial line items by way of CSV-Excel import or RESTful web services to the Summary Payment Applications BP, the system will add all of the other existing SOV lines, along with the line items provided in the CSV-Excel template or RESTful web services input request.

When you are scheduling payments by creating the payment line items by way of CSV or Excel import or RESTful web services, you can add all of the payment line items to the grid to prevent data discrepancy in the Schedule of Value (SOV). To be able to prevent data discrepancy in the SOV when the payment record is approved, you can view all of the SOV line items that have been added to the payment grid (Standard tab):

When you creating new payment applications, in the Payment Items tab, and you are exporting the record CSV or Excel template (or line item CSV or Excel template):

Oracle recommends that you should set the DD value as default, or define the auto-population, when the payment detail form has "required" string DEs, such as a short description. If the required" string DE does not include any value, then the CSV or Excel import or RESTful web services request will fail because the system will add all of the existing line items from SOV into the payment grid. In this scenario, the system will generate an error email for record creation, or the system will generate an error message, in the imported CSV template, for line item creation.

The system will validate when you add payment line items (by way of CSV or Excel import or RESTful web services request) to the SOV line items even if partial line items have been added, previously.

Note: The existing process will remain as is for CSV or Excel import or RESTful web services request of line items in non-standard tabs, within the Summary Payment Applications SOV BPs.

When you export the record, or line item, CSV or Excel template, the template will display the following information: "The system will add existing SOV lines into the payment grid when importing partial line items."

See Also

SOV Summary Payment Application Business Process

Import Summary Payment Application Line Items Into a BP



Last Published Sunday, July 20, 2025