Design Requirements for a Code-Based Manager

For a manager to work effectively in Primavera Unifier, you will need to create the following components in uDesigner.

Data elements	To roll up quantity amounts to the manager sheet, you need to create specific data elements (fields) to place on the attribute form for the manager. These fields must be built on the following data definitions: SYS BP Currency Amount SYS BP Decimal Amount SYS BP Integer Amount
Attribute form	Defines a code. Primavera Unifier users will see the information from this form in the Code Details window in Primavera Unifier when they add a row to the manager sheet; also appears on the Code Picker on business processes where users must choose a code from a list. Note: This attribute form does not create a record; the information exists only as part of a manager sheet. Consequently, you will need to design a code picker for this form to populate.
Code Picker	Primavera Unifier populates most pickers with the records that you see in the logs on the right pane of the screen, and uses the layout of the headings on the logs for the layout of the picker. These logs show the records that were created, for the most part, with attribute forms. However, attribute forms for code-based managers use pickers designed specifically for them because they do not create records that will appear on logs; the codes exist only as part of a sheet. In these cases, you will need to design a picker in the same way you would design a log.

Data elements

To roll up quantity amounts to the manager sheet, you need to create specific data elements (fields) to place on the attribute form for the manager. These fields must be built on the following data definitions:

SYS BP Currency Amount
SYS BP Decimal Amount
SYS BP Integer Amount

Attribute form

Defines a code. Primavera Unifier users will see the information from this form in the Code Details window in Primavera Unifier when they add a row to the manager sheet; also appears on the Code Picker on business processes where users must choose a code from a list.

Note: This attribute form does not create a record; the information exists only as part of a manager sheet. Consequently, you will need to design a code picker for this form to populate.

Code Picker

Primavera Unifier populates most pickers with the records that you see in the logs on the right pane of the screen, and uses the layout of the headings on the logs for the layout of the picker. These logs show the records that were created, for the most part, with attribute forms. However, attribute forms for code-based managers use pickers designed specifically for them because they do not create records that will appear on logs; the codes exist only as part of a sheet. In these cases, you will need to design a picker in the same way you would design a log.

Design Flow

The following table outlines the steps necessary to design the coding structure and launch the manager.

1. Create a data structure See Creating a Data Structure	For this type of manager, you must create three data elements for the attribute form: One to gather currency values from the line items of a business process. Use the SYS BP Currency Amount data definition to build this element. One to gather decimal values from the line items of a business process. Use the SYS BP Decimal Amount data definition to build this element. One to gather integer values from the line items of a business process. Use the SYS BP Integer Amount data definition to build this element.
2. Launch the manager	This step initializes the design process for the manager. See Launching a Manager.
3. Create an attribute form	See the instructions beginning with Starting an Attribute or Detail Form for a Manager. Mandatory fields for the attribute form are: Code (uuu_cm[1...25]_code) Code Status (uuu_cm[1...25]_status) Code Name (uuu_cm[1...25]_name)
4. Create a picker for a code-based manager	See the instructions under Designing a Picker.

1. Create a data structure

See Creating a Data Structure

For this type of manager, you must create three data elements for the attribute form:

One to gather currency values from the line items of a business process. Use the SYS BP Currency Amount data definition to build this element.
One to gather decimal values from the line items of a business process. Use the SYS BP Decimal Amount data definition to build this element.
One to gather integer values from the line items of a business process. Use the SYS BP Integer Amount data definition to build this element.

2. Launch the manager

This step initializes the design process for the manager. See Launching a Manager.

3. Create an attribute form

See the instructions beginning with Starting an Attribute or Detail Form for a Manager.

Mandatory fields for the attribute form are:

Code (uuu_cm[1...25]_code)
Code Status (uuu_cm[1...25]_status)
Code Name (uuu_cm[1...25]_name)

4. Create a picker for a code-based manager

See the instructions under Designing a Picker.

Last Published Friday, April 9, 2021