Line Number Order Component

Understand how line numbers are assigned to order components and how they relate to segment material dependencies.

Order components are tracked with unique line numbers that identify each component within an order. This line numbering is essential for maintaining proper segment material dependencies when scheduling and executing production orders.

Overview

Each order component is uniquely identified by a combination of:

• Order ID — the order the component belongs to

• Line Number — the sequential number assigned to the component within that order

Line numbers ensure that materials and segments are correctly associated with specific components during production execution, particularly when working with the Scheduler's segment material dependencies.

Line Numbers in the User Interface

When you add components to an order in TilliT:

1. Line numbers are automatically assigned and incremented

2. They start at 1 and increment sequentially for each new component

3. The line number is displayed in the order component list

4. Line numbers cannot be manually changed through the UI

Line Numbers via API

When creating or updating order components through the API:

1. You must supply a line_number value for each component

2. The line number must be a unique integer within the order (no duplicates)

3. Line numbers do not need to be sequential, but sequential numbering is recommended for clarity

4. The system validates that each (order, line_number) combination is unique

Example API Request:

{
  "orderId": "ORD-12345",
  "lineNumber": 1,
  "materialId": "MAT-001",
  "quantity": 100
}

Segment Material Dependencies

Line numbers are critical when your order includes segment material dependencies. If you use the Scheduler to define which materials are used in which segments:

• Each segment material dependency references a specific order component via its line number

• Line numbers persist across the Scheduler and Direct Operations integration

• Ensure line numbers are consistent between the Scheduler and API calls to avoid mismatched dependencies

If you're not using segment material dependencies or the Scheduler, line numbers are less critical but are still required for API integration.