Cost Type--Line Items with WBS Code

You are here: Overview of Business Processes > Types of Business Processes > Cost Type--Line Items with WBS Code

Cost Type--Line Items with WBS Code

This business process type is for shell or project cost transactions. BPs of this type directly affect the budget and relate to the Shell/Project Cost Sheet. BPs that use a WBS picker to reference WBS codes must use this sub-type. You can use this BP in:

•

A Standard Project

•

A shell that uses the Standard Cost Manager

Note: For cost BPs of this type, you can give users permission to modify line items at any time during the workflow before the end step is reached.

There are several classifications of this BP type.

Generic

Use this for miscellaneous line item 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

Use this for transferring currency from one account or line item to another.

Base Commit

Use this for:

•

Monies committed to be spent; for example, a contract or purchase order

•

Creating an SOV for a general spends or pay application

Change Commit

Use this for:

•

Changing or adding to a previous base commit

•

Modifying a general spends or pay application SOV

Note: A Change Commit must reference a Base Commit.

General Spends

Use this 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 WBS 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

This BP will create an SOV from the detail form. It supports complex construction calculations, such as retainage, stored materials, paid-to-date, and payment based on percentage complete. Use for invoicing at the WBS or breakdown level. Payment Applications auto-populate data to and from the SOV to manage balance-forward formulas.

Use this for:

•

Scheduling payments against construction contracts

•

Tracking/viewing previous and current payments made against these contracts

•

Rolls up to the Cost Manager

Note: A Payment Application must reference a Base Commit.

Transient Record” Funding Option for Generic, General Spends, and Payment Applications

Using these Cost classifications, you have the option of designing the business process so that users can assign funds, route the record for review, make changes, and confirm the fund sources before the record reaches a terminal status or the end step of a workflow. However, once the record reaches the terminal status or end step, users cannot assign funds, even if the end step is using an action form.
For example, a user could send an invoice that is pending (called a transient record) to the finance department for approval. Once the finance department approves the fund assignment, the invoice would reach terminal status and confirm the funding source, and be funded. However, once the funds have been assigned to the invoice during this approval process, they cannot be changed. This funding will override any manual fund assignments on an action form at the end step of a workflow.

Design Requirements for Line Items with WBS Code Business Processes

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

•

Upper form

•

Detail form

•

Line Item List

•

Workflow

•

Log

Design Flow

The following table outlines the design steps necessary to create this business process.

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.)

Start the design

This step initializes the design process for the BP. See Starting a New Design.

Design an upper form

See the instructions beginning with Starting an Upper Form

Design a detail form

See the instructions beginning with Starting a Detail Form.

For this classification:

These fields are mandatory:

Base Commit

•

Amount (amount)

•

Short description (short_desc)

•

WBS 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)

•

WBS 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)

•

WBS picker (uuu_cost_code)

Generic

•

Amount (amount)

•

Short description (short_desc)

•

WBS picker (uuu_cost_code)

Payment Application

•

Scheduled value (scheduled_value)

•

Amount (amount)

•

Short description (short_desc)

•

WBS picker (uuu_cost_code)

Transfer

•

Amount (amount)

•

Short description (short_desc)

•

WBS picker (uuu_cost_code)

Create a line item list

See Adding a Line Item List to a Form.

Create a workflow

See the instructions beginning with Starting a Workflow.

Create a log

See Designing a Log.

Oracle Corporation