Enum 5526 "Planning Create Prod. Order"
Base Application · Microsoft.Manufacturing.Document
Across versions
- BC23-28present
- BC29declaration changed
- BC30declaration changed
Base Application · Microsoft.Manufacturing.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | true |
Values
| Ordinal | Name | Caption | Notes |
|---|---|---|---|
| 0 | (blank) | ||
| 1 | Planned | Planned | |
| 2 | Firm Planned | Firm Planned | |
| 3 | Firm Planned & Print | Firm Planned & Print | |
| 4 | Copy to Req. Wksh | Copy to Req. Wksh | |
| 5 | Released | Released | |
| 6 | Released & Print | Released & Print |
Recent changes
- 2026-09-29 #11522 [main] [Order Planning] Production copy allows Req. worksheet templates that cannot create production orders (main, BC30, fix)
- 2026-08-21 #10364 Create released production orders from planning worksheet (main, BC30, feature)
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "enum", object_name: "Planning Create Prod. Order"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.