The following outlines the design steps necessary to create this business process.
- Create a Data Structure (if necessary)
- Launch the Design
- Design an Upper Form
- Design a Detail Form
- Create a Line Items list
- Create a Workflow
- Create a Log
The following explains each step in detail:
1. Create a Data Structure (if necessary)
This structure will include the data elements to be used on the forms. (If the data structure has not already been created, see the instructions beginning with Creating a Data Structure.)
(Optional) If you are designing a business process that will roll up data across shells to a code-and-record-based manager, you will need to design data pickers to help Primavera Unifier users locate and pick the correct BP records within the hierarchy. For more information on data pickers, see Across-Shell Functioning and also About Data Pickers.
Reservation sub-type, you need to create one or more data pickers. Primavera Unifier users will use these data pickers to choose the objects to reserve. The data pickers will be populated with the business process records (such as a space) that have been "calendar enabled."
2. Launch the Design
This step initializes the design process for the BP. See Starting a New Design (Edit Studio).
3. Design an Upper Form
See the instructions in Designing Upper Forms.
For Change Commit sub-type, this field is mandatory:
A reference ID (Refid)
You will need to link the Change Commit BP to the Base Commit BP using this reference ID.
For Spends sub-type, this field is mandatory:
A reference ID (Refid)
You will need to link the Spends BP to the Base Commit BP using this reference ID.
For Lease sub-type:
If you want the straight-line rent amount to appear on the upper form of the lease, include this field:
uuu_lse_sl_rent
If you include this field on the form, the user will not have to open the Payment Schedule to see the rent amount.
If you want to allow the Primavera Unifier user to adjust the date terms of a straight-line lease, or to add or subtract a one-time currency amount to/from the lease amount, include these fields on the Upper Form:
- Commencement date (
uuu_lse_commencement_date
) - Termination date (
uuu_lse_termination_date
) - Lease term modifier (
uuu_lse_term_modifier
) - Currency amount adjustment (
uuu_lse_sl_adjustment
)
For Reservation sub-type:
- Reserved from date (
uuu_date_from
) - Reserved to date (
uuu_date_to
) - Reservation name (
uuu_rsv_calendar_item_name
) - Set reservation recurrence (
uuu_recurrence
)
If a Reservation business process should auto-create another business process before or after the reserved event takes place, these fields are mandatory and can be placed on the upper or Detail Form:
- BP Creator element
- When the auto-creation should occur, relative to the reservation (
uuu_before_after
) - Date the auto-creation should occur (
uuu_rsv_trigger_date
) - # of days before/after the reservation the auto-creation should occur (
uuu_rsv_trigger_days
) - # of hours before/after the reservation the auto-creation should occur (
uuu_rsv_trigger_hrs
) - # of minutes before/after the reservation the auto-creation should occur (
uuu_rsv_trigger_min
)
4. Design a Detail Form
If this business process is to roll up data from across shells, the following fields are mandatory on these forms to provide user navigation to records across shells:
- A data picker for each manager class
- A configurable manager picker
These fields are mandatory for the form, but are not required to be filled in at runtime. However, if these fields are left blank on the form at runtime, data rollups will not occur.
See the instructions in Designing Upper Forms.
For Base Commit sub-type, these fields are mandatory:
- Manager picker (uuu_cm[1...25]_picker)
- Cost code picker (uuu_cm0_code)
- Effective date for the code (uuu_effective_date)
- Amount (amount)
- Short description (short_desc)
For Change Commit sub-type, these fields are mandatory:
- Manager picker (uuu_cm[1...25]_picker)
- Cost code picker (uuu_cm0_code)
- Effective date for the code (uuu_effective_date)
- Commit line item picker (uuu_sovlinum)
- Amount (amount)
- Short description (short_desc)
- Reference (ref_bpo_lineitem)
For Spends sub-type,these fields are mandatory:
- Manager picker (uuu_cm[1...25]_picker)
- Cost code picker (uuu_cm0_code)
- Effective date for the code (uuu_effective_date)
- Amount (amount)
- Short description (short_desc)
For Generic sub-type, these fields are mandatory:
- Manager picker (uuu_cm[1...25]_picker)
- Amount (amount)
- Short description (short_desc)
For Payment Application sub-type, these fields are mandatory:
- Manager picker (uuu_cm[1...25]_picker)
- Scheduled value (scheduled_value)
- Amount (amount)
- Short description (short_desc)
For Lease sub-type, these fields are mandatory:
- Manager picker (uuu_cm[1...25]_picker)
If the lease BP is linked to a configurable manager.
- Generic Cost Manager picker (uuu_cm0_picker)
If the lease BP is linked to a Generic Cost Manager.
- uuu_lse_start_date
- uuu_lse_end_date
- uuu_lse_frequency
- uuu_lse_pay_due_day
- uuu_lse_pay_latest_due_day
- uuu_lse_pay_creat_lead_time
- uuu_lse_pay_type
- uuu_lse_proration_method
- uuu_lse_esc_method
- uuu_lse_esc_value
- uuu_lse_esc_freq_len
- uuu_lse_esc_freq_type
- uuu_lse_add_pay_amt
- uuu_lse_pay_due_date
- uuu_lse_pay_latest_due_date
- uuu_lse_pay_creation_date
- uuu_lse_pay_amount
- Amount (amount)
- short_desc
To accommodate lease payment allocation, these fields are also mandatory:
- uuu_allocation_amount
- uuu_lse_allocation_name (this is a picker)
- The amount of lead time a payment request needs for approval and payment—uuu_lse_pay_creat_lead_time
If you want to allow the user to manually specify a first payment due date, include this field:
- uuu_lse_first_pay_due_date
For Reservation sub-type, f the detail form should auto-create another business process before or after the reserved event takes place, these fields are mandatory:
- BP Creator element
- When the auto-creation should occur, relative to the reservation (uuu_before_after)
- Date the auto-creation should occur (uuu_rsv_trigger_date)
- # of days before/after the reservation the auto-creation should occur (uuu_rsv_trigger_days)
- # of hours before/after the reservation the auto-creation should occur (uuu_rsv_trigger_hrs)
- # of minutes before/after the reservation the auto-creation should occur (uuu_rsv_trigger_min)
5. Create a Line Items list
See Adding an Item Log to a Detail Form.
6. Create a Workflow
See the instructions beginning with Starting a Workflow.