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
- Navigate to the summary payment application business process log.
- 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
- Open the exported CSV or Excel file in Microsoft Excel.
- 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.
- 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
- Navigate to the summary payment application business process log.
- Click the Actions menu and hover over Import.
- Select either Data From CSV File or Data From Microsoft Excel File.
- Browse to select the file to import, then click Next.
- Add any attachments to the import.
- 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 lin 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.
Best Practice Recommendations for CSV and Excel Imports -
The following best practices are recommended for CSV and Excel imports:
- Only include the summary line and the costed lines that are getting paid.
- Include all the costed lines of a summary line, even when partial costed lines are paid
- Do not include summary and costed lines that are not getting paid. Similarly, for classic payments do not include lines that are not getting paid.
- If the total number of paid lines in a the payment record exceeds 500 lines, Oracle recommends you to complete the process using multiple payment records, each containing 500 or fewer line items, including summary and costed line items, in the payment grid. To accomplish this, configure the Payment Business Process using the Save Edited Lines check box.
See Also
SOV Summary Payment Application Business Process
Import Summary Payment Application Line Items Into a BP
Last Published Saturday, July 12, 2025