Cost Type: Line Items with CBS Code

The Cost Type--Line Items with CBS Code Business Process (BP) type:

Is used for Project/Shell cost transactions.
Directly affect the budget and relate to the Project/Shell Cost Sheet.

Use the Cost Type--Line Items with CBS Code BP type for a BP that includes a CBS picker to reference CBS codes.

Use the Cost Type--Line Items in a:

Standard Project
Shell that uses the Standard Cost Manger

The Cost Type--Line Items with CBS Code has the following classifications:

Generic
Transfer
Base Commit
Change Commit
General Spends
Payment Applications

The following explains each of the classifications in detail:

Generic

To use for miscellaneous Line Items BPs that do not directly relate to commitments, change commits, spends, or funding.
Use it to automate fund consumption at a specific status (not necessarily a terminal status).

Transfer

To use for transferring currency from one account or line item to another.

Base Commit

For monies committed to be spent; for example, a contract or purchase order.
For creating a Schedule of Values (SOV) sheet for a General Spends, Payment Applications, or Summary Payment Applications.
Note: In Standard Cost Manager, the Base Commit BP creates a Schedule of Values (SOV) sheet.

Change Commit

For changing or adding to a previous Base Commit.
For modifying a General Spends, Payment Applications, or Summary Payment Applications.
Note: A Change Commit must reference a Base Commit.

General Spends

For monies to be spent; for example, an invoice or partial payment of services, often charged against a prior commit. Can be used for invoicing at the CBS or breakdown level. A General Spends BP does not calculate retainage, stored materials, etc.

Note: A General Spends must reference a Base Commit.

Payment Applications

To create an SOV from the Detail Form.
Supports complex construction calculations, such as retainage, stored materials, paid-to-date, and payment based on percentage complete. Use for invoicing at the CBS or breakdown level. Payment Applications auto-populate data to and from the SOV to manage balance-forward formulas.
For scheduling payments against construction contracts.
For tracking/viewing previous and current payments made against these contracts
For rolls up to the Cost Manager
Note: A Payment Application must reference a Base Commit.

For the Business Processes of Type: Cost, Sub-Type: Line Items with CBS Code, Classification: Payment Applications, the "Previous Payment Calculation" option in the BP Properties enables you to select additional data element for calculating the total previous payments from the payment application. This field (drop-down) enables you to select which value to add to the total previous payments. The values are:

Amount
Balance to Finish
Completed and Stored To Date
Material Stored Retainage Amount
Requested This Period
Work Retainage Amount

Transient Record Funding Option

Once a BP record reaches the terminal status (the end step of a workflow), the user cannot assign funds, even if the end step is using an Action form. For example, a user sends an invoice that is pending (a Transient Record) to the finance department for approval. The finance department approves the fund assignment. The invoice reaches the terminal status (the end step of a workflow). The process is confirmed and the invoice gets funded. In this example, once the funds have been assigned to the invoice, the funds cannot be changed and the fundings override any manual fund assignments, on an Action form, at the end step of a workflow.

The "Transient Record Funding Option" is available for the following Cost Type--Line Items with CBS Code classifications:

Generic
General Spends
Pay Application
Summary Pay Application

These classifications of Cost Type--Line Items with CBS Code allow you to design a BP that the user can:

Assign funds to
Route the BP record for review
Make changes to
Confirm the fund sources before the BP record reaches a terminal status (the end step of a workflow)

Design Requirements for Line Items with CBS Code Business Processes

For these business processes to work effectively in Primavera Unifier, you will need to create the following components in uDesigner:

Upper form
Detail form
Line Item List
Workflow
Log

In order to see the same Data Elements (DEs) on the Detail Form of a Cost-type Business Process, you need to add the DEs to the:

Detail Form, or the Item Log, of the Business Process.
Cost Code Attribute Form.

Design Flow

The following outlines, and explains, the design steps necessary to create this business process.

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.

2. Start 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 beginning with Designing Upper Forms.

4. Design a detail form

See the instructions beginning with Designing Detail Form. Also:

For this classification:	These fields are mandatory:
Base Commit	Amount (amount) Short description (short_desc) CBS picker (uuu_cost_code) If the transaction currency is different from project currency, include a currency picker (`currencyid`) on the form.
Change Commit	Amount (amount) Short description (short_desc) CBS picker (uuu_cost_code) Reference (ref_bpo_lineitem) If the transaction currency is different from project currency, include a currency picker (`currencyid`) on the form.
Spends	Amount (amount) Short description (short_desc) CBS picker (uuu_cost_code)
Generic	Amount (amount) Short description (short_desc) CBS picker (uuu_cost_code)
Payment Application	Scheduled value (scheduled_value) Amount (amount) Short description (short_desc) CBS picker (uuu_cost_code)
Transfer	Amount (amount) Short description (short_desc) CBS picker (uuu_cost_code)

5. Create a line item list

See Adding an Item Log to a Detail Form.

6. Create a workflow

See the instructions beginning with Starting a Workflow

7. Create a log

See Designing a Business Process Log (Standard or Picker).

Data Elements Properties for Auto Populate

The Auto Populate window contains the following fields and options:

Destination Element
Source Name
Source Element
Do not get latest SOV values when merging
Do not select the Do not get latest SOV values when merging option for scheduled_value, uuu_unit_price, and the system-defined uuu_spa_prev_amt because they are predefined data elements that receive the latest values from SOV, when the SOV is updated by a Change Order.

When you select the Do not get latest SOV values when merging option, you will not receive the latest value from SOV, when SOV merge occurs for in-flight and draft payments. That is to state that at the run time whenever a user opens a draft or an in-flight payment record and accepts the merge alert, the data elements that have the Do not get latest SOV values when merging option selected in uDesigner do not get refreshed with the latest updated values from SOV.

When the value of the Source Name field changes from SOV to other sources, the Do not get latest SOV values when merging option will not be displayed. In the Elements Properties window, the Do not update latest value from SOV field corresponds (Yes or No) to the Do not get latest SOV values when merging option.

Last Published Friday, April 9, 2021