If line item auto-creation fails

You are here: Primavera Unifier User Mode > Business Processes > Creating Business Processes > Auto-create a business process records based on conditions or frequency

Auto-create a business process record or Line Item based on conditions or frequency

Primavera uDesigner users can design a form that automatically creates a new record, line item, or planning item if certain criteria are met. The criteria can be:

•

A condition, such as a dollar amount

•

A frequency, such as a daily or weekly time frame

Note: Line items cannot be created with a frequency trigger.

•

Both a condition and a frequency

When the business process, planning item, or line item reaches the condition or frequency trigger(s), the form will automatically create a new record and send it to an initiation step (I Step). These forms contain a "creator" field to activate the auto-creation, either automatically, or manually. If you have Modify Ownership permission on the source record, you can auto-create new records or line items. You can also override conditional auto-creation and immediately invoke the auto-creation manually if necessary.

Note: If the line items have been grouped (as part of the administrator's business process setup), you can manually invoke the auto-creation; however, only those line items in a status of "pending creation" will be grouped.

Bypassing the I Step

During business process setup in Primavera Unifier, the administrator can set up the auto-created workflow BP to skip the initiation step and send the record directly into the workflow, where it normally arrives at the first step after the Create step (or the first step in a conditional routing). For a workflow BP, the administrator specifies the schema, the step in the workflow that the record should use as its first step, the workflow duration, and the name of the person or group who will be the owner of the auto-created record. When the record is created, data will roll up to manager sheets at the appropriate status; however, if Primavera Unifier encounters errors or invalid data, the record will remain at the Create step, and roll-ups will not occur until the user resolves the errors.

For a non-workflow BP, the administrator can set up an auto-created record to skip the initiation step. In this case, the non-workflow BP will be created and will appear in the users' BP logs in either an “edit” or “finish edit” mode. If it appears in an “edit” mode, the user will have to open the record and add or correct information on the form. If it appears in a “finish edit” mode, the record is considered complete, and data will roll up to manager sheets.

Note: Business processes are not auto-created in projects or shells that have the view-only or inactive status.

Your administrator sets up the auto-creation by specifying:

•

The name of the person or group who will be the owner of the auto-created record

•

(For workflow BPs) The workflow schema to use

•

(For workflow BPs) Which step in the workflow the record should use as its first step

•

(For workflow BPs) The workflow duration

•

The criteria that will trigger the auto-creation

•

Whether or not attachments to the record or line item will be included when the record is auto-created

•

Whether or not records that were linked to the creating record should also be linked to the newly created record, or to the new line item

•

Whether or not the I Step should be bypassed when Primavera Unifier auto-creates a new record

•

Whether or not the line items from line item tabs should be grouped

If line item auto-creation fails

If the line-item creation is auto-created with a condition-based query (that is, not manually), Primavera Unifier will send an e-mail notification to the business process owner. The e-mail will contain location information so that the recipient can see where the auto-creation originated and where it failed. Following are conditions under which line item creation can fail:

•

The To field is empty. This is possible if the assignee becomes inactive after the schedule is created or if a group is empty.

•

WBS code is invalid, which can happen if the WBS code becomes inactive after selecting in the template.

•

The rules engine validation fails.

•

For payment applications, the associated SOV is locked, either by the payment application record in routing, or by a change commit with a negative line item value.

Note: If the destination business process does not exist or has not been imported into Primavera Unifier, the location specified in the e-mail notification might be non-existent or incorrect.

Oracle Corporation