Business process behavior is dependent on the how the business process was designed in Primavera uDesigner, and the assignment options chosen in the project/shell funding sheet. In general, the design determines when funding assignments can be viewed or performed, and the assignment options determine whether the assignment is done manually or automatically, and at what levels.
Spends type business processes (e.g., invoices or payment applications) can be designed in Primavera uDesigner to consume funds. Following is a summary of the business process types and design options that can be used:
Project level:
| • | Cost type, subtype line items with fund code, classification generic, general spends or payment application. |
| • | Workflow or non-workflow. |
| • | Each action form can be enabled with the following options: “View fund assignment” and “Allow fund assignment.” This option allows funding assignments to be viewed or performed at any step in the workflow (or any status if non-workflow). The “Allow fund assignment” option is applicable when the business process is set up for manual assignment in the funding assignment levels in the funding sheet properties. |
| • | An option can be set for the business process that disallows manual fund assignment once the record reaches end step (or terminal status for non-workflow). When this option is chosen, it takes precedence over the “Allow fund assignment” setting, even if an action form is used on the end step. This option does not affect automatic fund assignments. |
| • | This option is found on the Edit Studio window, Options tab. |
WBS level:
| • | Cost type, subtype line items with WBS and fund code, classification generic, general spends or payment application. |
| • | Other options are the same as for Project Level. |
Oracle Corporation
Primavera Unifier 9.10 • Copyright © 1998, 2012, Oracle and/or its affiliates. All rights reserved.