Cost Type BP
The Cost type business process form enables you to track and manage cost information and interact with the Project/Shell cost sheet. Examples include base contracts or purchase orders, change orders, budget change requests, invoices, fund appropriations, and leases.
Note: With version 23 and later, a Total row on a non-standard tab of a line item grid is not displayed. For version 22 and earlier, the Total row displays a 0.
Additional cost-related functionality includes schedule of values (SOV) and payment applications.
In any change order (including change orders with Unit Cost-type Contract when the Unit Cost Contract option is selected), when you select a reference SOV, for selecting an SOV line item, the system uses the value of the Item Unit Cost field from the referenced SOV and makes the field read-only.
Cost type Business Process Form Sub-types
The Cost type BP form has several sub-types that are used to perform specific cost-type functions. The cost business process subtypes are:
- Commit at company level (also known as Blanket Purchase Order)
This sub-type allows tracking and control of costs at the company level above the CBS level.
It is independent of a budget or cost sheet, and it is used for tracking non-CBS expenses across projects or shells.
Project/Shell level Commit at company level sub-type can be set up to reference a company commit.
Example of Blanket Purchase Order
A Blanket Purchase Order is a type of purchase order that the customer makes with its supplier. A Blanket Purchase Order contains multiple delivery dates over a period of time (often negotiated) to take advantage of predetermined pricing. It is usually used when there is a recurring need for expendable goods.
- Line items with CBS code
This sub-type relates directly to the Project/Shell cost sheet.
The business processes that use a CBS picker to reference CBS codes must use the Line items with CBS code sub-type.
These business process transactions can directly affect the budget. Examples include Base Commits, Change Commits, General Spends, and Payment Applications.
- Line items with fund code
This sub-type is used for fund appropriation at the Project/Shell level.
Business processes can be created to automatically allocate or consume funding source funds, which are chosen using a Fund picker. These transactions are for fund management and do not necessarily affect the budget. Transactions on Line items with fund code sub-type roll up to the Fund Manager.
- Line items with both CBS and fund code
This sub-type is used during fund appropriation at the CBS level. These transactions are for fund management and do not necessarily affect the budget. Transactions on Line items with both CBS and fund code sub-type roll up to the Fund Manager and Cost Manager.
- Line Items with Both CBS and WBS Codes
This sub-type is used to roll up transaction data to the EVM-WBS Sheet and Cost Manager.
- Line items with company accounts code
This is a company-level business process that can be used to roll up transaction data to the company accounts sheet.
- Line items with multiple codes
This sub-type is for business processes that can be used with a generic (non-CBS) cost manager.
Cost-type BP Form and Picker Values
The picker field is used for selecting CBS codes, and the picker can be found on:
- Cost-type BPs
- Shell or project
- Shell cost sheets
- Schedule activity forms
- Company-level and Shell-level business processes in form view and grid view when records and line items are created or updated
The following information applies to the following pickers:
- CBS Picker
- CM0 Picker
- CMx Picker
- Funding Picker
When you create or update a BP record:
- The picker field enables you to select only relevant codes or data.
- You can search for a code in picker, in the Line Item Details tab of your BP record Line Items tab. This is so you can see a list of codes from the filtered list that matches your search criteria.
- By defining the query condition on pickers in BP Configuration, you can narrow down the list of codes in picker, in the Line Item Details tab of your BP record Line Items tab. This is so you can see a list of codes from the filtered list that matches your defined query conditions.
- The picker has an auto-completion feature. If you know the code, begin typing in the picker DE field, and the picker will show the top 10 matches. If you continue to type, the picker will narrow the list as it matches more of the characters you type.
You can also auto-create a BP record with the picker value that matches a previously-defined query condition, at the source BP. This so you can automatically create records or line items by ignoring the filter conditions that are set for the destination BP. The query condition is defined in the BP Configuration.
For flat-structured cost sheet, the filters are applied to all nodes, and for the tree-structured cost sheet the filters are applied to the leaf nodes, and the summaries are displayed base on the rollups.
Note: Auto-population and Reverse Auto-population processes will work in same way if the query conditions are defined in the picker.
When you create a new BP record by way of a CSV or Excel file import, or when you add a new line item through the line-item CSV or Excel file import, the system will use the defined query conditions in the picker. For BP record level import, if the CBS code does not match the query conditions, then the validation happens during the record creation process, and the system sends an email to the user that it has failed. For line item level import, the system displays a message and shows the error in the CSV.
You cannot create a BP record if the picker DE is a required field, and the data that you have entered does not match the available defined query conditions in the picker.
When you create a new BP record with line item by way of REST V1 and V2 web services, or when you add a new line item through the REST V1 and V2 web services, the system will use the defined query conditions in the picker. If the CBS code provided in the RESTful web services does not match the query conditions, then the record or line item creation will fail with an error.
Last Published Sunday, July 20, 2025