You are here: Primavera Unifier User Mode > Business Processes > Business Processes with Special Behaviors > Import new payment application records

Import new payment application records

You can export a CSV 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. The Reference Number field is exported as a column for payment application business processes that use individual line items. The Reference number field is not exported as a column for payment application business processes that use Group by WBS.

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

To export a copy of the payment application business process template

Navigate to the payment application business process log.

Choose File > Export Template > CSV.

Click Open to open the file in Excel, or click Save to save the file to your local drive. The template exports with no data in it, and contains only the column headings.

To modify the exported payment application business process template

Open the exported CSV 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.

Note the following:

•

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 Unit Cost Control.

•

Any line items with the Amount equal to zero will not be imported.

•

SOV locking is enforced

•

Use to add new business process records only; not to modify existing business processes.

•

You might find that you have to change some of the cells in the CSV file to Text type in order for data to import correctly. For example, if you have a WBS 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 WBS code.

•

If the Integration design for the business process includes a Description field for line items, and the associated SOV sheet also contains a Description field, the description from the SOV sheet is imported, and the line item description is not imported.

To import the payment application business process template

Navigate to the payment application business process log.

Choose File > Import.

Browse to select the file to import.

Click OK. The new business processes are listed in the log.

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.

Oracle Corporation