Payment Application Business Processes

Payment application business processes enable you to track your payment information using a standard payment application method (for example, tracking retainage, stored materials, past payments, etc.).

Each payment application record will reference a particular base commit record. The line items on the payment application will reflect the line items on the base commit plus any associated change commits.

Payment applications, and associated base commits and change commits, are designed in Primavera uDesigner. For more information, refer to the Primavera uDesigner User Guide.

Note: Only one payment applications type business process can be configured for a project or shell. Only one payment application record can be routed at any time for a commit.

You can use CSV import to create new payment application business processes or to add SOV line items to an existing business process. You can export payment application CSV templates at the log level (for header and line item templates) and at the record level (for line item templates). You can then modify the templates and import them to create new records (at the log level) or to add line items to an existing record (at the record level).

An Integration interface must be defined to support CSV import. If you find that you cannot perform the file import, see your Administrator. Also, new records can be created and line items added using Integration through Web Services. Integration through Web Services must be coordinated with an Oracle Primavera representative.

Oracle Corporation

Primavera Unifier 9.10 • Copyright © 1998, 2012, Oracle and/or its affiliates. All rights reserved.

Copyright Information

Open topic with navigation