RoutingOperation — data reference
All 18 fields BSuit stores for RoutingOperation (Manufacturing), with the record types they refer to.
On this page
#About RoutingOperation
RoutingOperation is a record type in the Manufacturing area of BSuit. This page lists everything BSuit stores for each routingoperation — 18 fields. It is maintained on the “Routing Operations” page.
| Screen | Module |
|---|---|
| Routing Operations | Manufacturing |
#Fields
Every field stored for a routingoperation. “Stored as” is the technical field name, useful when talking to support or building reports. 4 fields are references to other record types.
| Field | Stored as | Type | Required | Max length | Refers to |
|---|---|---|---|---|---|
| Company Id | CompanyId | Text | No | — | Company |
| Routing Id | RoutingId | Text | No | — | Routing |
| Sequence | Sequence | Whole number | No | — | — |
| Operation Id | OperationId | Text | No | — | Operation |
| Work Center Id | WorkCenterId | Text | No | — | WorkCenter |
| Setup Hours | SetupHours | Number (decimal) | No | — | — |
| Run Time Per Unit Hours | RunTimePerUnitHours | Number (decimal) | No | — | — |
| Standard Hours | StandardHours | Number (decimal) | No | — | — |
| Queue Time Hours | QueueTimeHours | Number (decimal) | No | — | — |
| Move Time Hours | MoveTimeHours | Number (decimal) | No | — | — |
| Scrap Percent | ScrapPercent | Number (decimal) | No | — | — |
| Is Quality Check | IsQualityCheck | Yes / No | No | — | — |
| Notes | Notes | Text | No | — | — |
| Sort Order | SortOrder | Whole number | No | — | — |
| Id | Id | Text | No | — | — |
| Created At | CreatedAt | Date and time | No | — | — |
| Updated At | UpdatedAt | Date and time | No | — | — |
| Is Deleted | IsDeleted | Yes / No | No | — | — |
#Where RoutingOperation is referenced
Other record types point to this one, so changing or removing a record here can affect them:
| Record type | Field |
|---|---|
| WorkOrder | Routing Operation Id |
#About this guide
Generated from BSuit’s data model on the date shown under “Seen on a running system”. Field names, types and lengths come from the model itself. References are inferred from field names (a field called “Ledger Id” is treated as pointing to Ledger); the model does not declare relationships, so an inferred link can occasionally be wrong or missing.
About this guide
- Status
- Partially reviewed
- Application
- BSuit ERP
- Audience
- Administrators, analysts and support staff
- Owner
- BSuit documentation team
- Reviewer
- Not yet reviewed
- Last verified
- Never
- Checked against
- Generated from source revision a36c7a086 on 2026-10-02
- Seen on a running system
- Not yet
- Help version
- 2026.0.0-preview
- Guide ID
erp:data/mrp.routingoperation