COSTLINE: Cost Line
The COSTLINE entity stores cost lines. An individual OPEX cost line item tracking monthly forecast and actual expenditure, linked to a vendor, optional contract, and procurement records.
Default definition. This article describes the default
COSTLINE definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches COSTLINE.Entity properties
| Property | Value |
|---|---|
| Entity code | COSTLINE |
| Display name | Cost Line |
| Plural | Cost Lines |
| Level | 6300 |
Use cases
COSTLINE is the child entity used by the opextracker row type. Each record represents a single cost line tied to a parent entity (DPLAT, NWPLATINST, etc.) via comboKey.
Fields
Cost Line
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Description |
vendor | reference → VEN | Vendor | |
spendtype | reference → SPEND | Spend Type | |
pcon | reference → PCON | Contract | |
supportAgreement | reference → SUPAGREEMENT | Support Agreement | |
prreq | reference → PRREQ | Purchase Requisition | |
po | reference → PO | Purchase Order |
Relationships
- Lookups:
vendorpoints at aVENrecord;spendtypepoints at aSPENDrecord;pconpoints at aPCONrecord;supportAgreementpoints at aSUPAGREEMENTrecord;prreqpoints at aPRREQrecord;popoints at aPOrecord.
Creating a Cost Line via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "COSTLINE",
"level": 6300,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example value"
}Listing Cost Lines
GET /v1/entities/COSTLINE/SUB