Import Summary Payment Application Line Items Into a BP

You can export a template that includes the detail form fields as columns for a specific business process. These fields include the detail form line item fields defined in Integration.

You can then modify the exported template and import it to create new line items for the business process. The exported template contains SOV record information.

When importing Summary Payment line items for Payment Applications BPs, the system uses the values that the user provided for the auto-populate data elements, if the fields were editable originally; otherwise, the system uses the values that are from Base Commit line items or Change Commit line items.

To export the summary payment application line item template

If multiple tabs are designed for the line items in the business process, only the data in the Standard tab is exported. For the other tabs, the tab name is included in the exported data for reference, but no data in these tabs is exported. Data from all columns in the Reference Base Commit is exported.

  1. Navigate to the summary payment application business process log.
  2. Click Create to create a new business process.
  3. Select a Reference Base Commit for the business process. If you do not select a Reference Base Commit, the exported template will not contain data. Data from all columns in the Reference Base Commit is exported.
  4. Open the Menu Options ( ) and hover over Export Line Item Template, then select CSV or Microsoft Excel.

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

To modify the summary payment application line item template

  1. Open the exported CSV or Excel file in Microsoft Excel. The SOV line items are listed.
  2. Enter the line item information into the spreadsheet. Each line 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.
    • Ensure that you are importing the records you want to import. Any line items that you import will be added after any existing line items.
    • Use to add new lines only, not to modify existing lines
    • All data created through the CSV import is rolled up to the cost sheet
    • 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 line item template

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

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

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 New Summary Payment Application Records


Last Published Sunday, July 20, 2025