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 class. Primavera Unifier users will see the information from this form in the Code Details window in Primavera Unifier; also appears on the Code Picker on business processes where users must choose a code from a list. |
Log (standard or advanced) | Lists all the records that were created for the manager in Primavera Unifier at runtime. Standard logs display fields from the manager’s attribute form that you want to monitor. For example, you might want a log for the Document Manager to include the names of all documents and their creators as well as their locations. For the Resource Manager, you might want the log to include the names of all resources and their current status. Advanced logs support data pickers. An advanced log should be designed for any shell, configurable manager class, or business process that contains records that will be displayed on a data picker. (For more information on data pickers, see About Data Pickers.) |
Reference process | If you include a BP Picker on the form, a reference process is necessary to point to the BP you want to reference. |
Data Picker(s) | (Optional) If you are designing a code-and-record-based manager that will operate across shells, data pickers will help Primavera Unifier users locate and pick the correct BP records within the hierarchy. A data picker filters the information that appears on the picker so that users do not have to search through a multitude of records in the shell hierarchy. |
Design Flow
Following are the overall steps necessary to design the coding structure and launch a code-and-record-based manager.
- Create data elements for the purpose of populating the sheet from business processes. These fields must be included on the attribute form.
Note: Do not confuse these data elements with those you choose on the Options tab when you launch the manager: Those elements work in conjunction with the data elements discussed here. The elements discussed here serve as "containers" on the sheet for collecting values from the data elements you specify on the Options tab, and they must be created from data definitions developed especially for these managers.
- Place a class code field on the detail form for the manager and create a pool of segment fields from which to create the code. On the detail form, you must create a concatenated formula for this class code field using segments from the pool. When you design this field, mark all these fields "editable and required."
- If the manager sheet will be in a tree format, you must include a navigation code field on the detail form and create a concatenated formula for this field.
The fields selected in the formula of the Navigation code are used for the Navigation tree structure. The ordering of data elements, for the tree structure, will be the order that the Navigation code data element has formulated.
Example
The uuu_cm_navigation_code is fomulated as: Manufacturer<upmManufacturerTXT120> + Material Category<umatCategoryPD> + Material Sub Category<umatSubTypePD> + Material Name<uuu_cm5_name>
In the Formula user interface, you will see:
Navigation Code = Manufacturer (-) Material Category (-) Material Sub Category (-) Material Name
As a result, the data element ordering in the tree structure, in User mode, will be:
1) Manufacturer > 2) Material Category > 3) Material Sub > Material Name
Note: The Advance Log Navigation has no effect in Code-based and Record-based Configurable module tree structure. This is governed by uuu_cm_navigation_code. The data elements with data definition type "String" will be shown in Formula data element selection list.
The following table outlines these steps with additional details.
1. Create 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 (Optional) If you are designing a code-and-record-based manager that will operate across shells, data pickers will help Primavera Unifier users locate and pick the correct BP records within the hierarchy. For more information on data pickers, see About Data Pickers. See the instructions beginning with Creating a Data Structure. |
---|---|
2. Launch the manager | This step initializes the design process for the manager. See Starting an Attribute or Detail Form for a Manager. |
3. Create an attribute form | See the instructions beginning with Designing a Form. 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) Any fields that should be used as part of the code. If the manager sheet is in a tree format, this field is mandatory: Navigation code (uuu_code_navigation_code) If users should be able to reserve this item, these fields are mandatory: Allow item to be reserved (uuu_rsv_reservable) Allow over-booking (uuu_rsv_overbook) |
4. Create a log |