You are here: Primavera Unifier User Mode > Business Processes > Business Processes with Special Behaviors > Import payment application line items into a BP

Import 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 SOV data and 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. If multiple tabs are designed for the line items in the business process, the tab columns are included in the export. All of the data on the Standard tab is exported; no data on the other tabs is exported.

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.

To export the 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.

Navigate to the payment application business process log.

Click New to create a new business process.

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.

Choose File > Export Line Item Template.

Click Open to open the file in Microsoft Excel, or click Save to save the file to your local drive. The template exports with SOV line item data in it, based on the selected Reference Base Commit.

To modify the payment application line item template

Open the exported CSV file in Microsoft Excel. The SOV line items are listed.

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.

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

•

Any line items that you import will replace the existing line items in the business process.

•

Use to add new lines only, not to modify existing lines

•

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 line item template

Note: Line items you import will replace any existing line items.

Navigate to the Payment Application business process log.

Select a business process and click Open.

Click the Import button. The imported line items replace any existing line items.

If there are any import errors, you can open the CSV file to view and correct the error. No line items are imported if any row contains an import error.

Oracle Corporation