JD Edwards Order Activity Rules and Sales Order Status Codes (F40203, UDC 40/AT)
This reference shows the typical JD Edwards EnterpriseOne 9.2 sales order status flow for order type SO and line type S, which program moves each step, and the special statuses you meet in practice. It also lists the F40203 order activity rules columns so you can read your own rules directly.
| Status / column | Description | Program that advances it | Typical next status | Notes |
|---|---|---|---|---|
520 | Enter Sales Order | Sales Order Entry (P4210) | 540 | Typical first status for SO / S in standard setups. Other allowed statuses let you skip steps. |
540 | Print Pick Slips | Print Pick Slips (R42520) | 560 | Pick slip number written to SDPSN. Hard commits are usually made by now. |
560 | Ship Confirmation | Shipment Confirmation (P4205) | 580 | After confirmation the line's last status (SDLTTR) is 560 and its next status (SDNXTR) is the following step, typically 580. |
580 | Print Invoices | Print Invoices (R42565) | 620 (site specific) | Invoice number and date written to SDDOC and SDIVD. Some setups use 580 for cycle billing; check your rules. |
620 | Sales Update | Sales Update (R42800) | 999 | R42800 updates lines to 999 (or the status in its options), writes G/L and A/R, and can move lines to F42119. |
999 | Complete - closed | Set by the last step (R42800) | Closed. Only 999 lines can be purged to history. Status Code Update (P42040) cannot advance lines to 999. | |
904 | Backordered at Shipment Confirmation | Created by P4205 for the unshipped quantity | From the order process | New split line for the remaining quantity. Release it with Release Backorders - Online (P42117) or Backorder Release and Report (R42118). |
914 | Added in Shipment Confirmation | P4205 for intercompany orders created at confirmation | Per rules | Status for lines added during shipment confirmation. Confirm the code and description in UDC 40/AT on your system. |
980 | Canceled in Order Entry | Cancel line in P4210 | Canceled quantity in SDSOCN. Confirm the exact code in UDC 40/AT on your system. | |
F40203.FSDCTO | Order Type | Order Activity Rules (P40204) | Key part 1. UDC 00/DT, e.g. SO. | |
F40203.FSLNTY | Line Type | P40204 | Key part 2. From line type constants (F40205), e.g. S. | |
F40203.FSTRTY | Status - Line (this step) | P40204 | Key part 3. The status code for this step (UDC 40/AT). | |
F40203.FSNXTR | Status Code - Next | P40204 | Expected next step. Must be a higher number. | |
F40203.FSA1TR to FSA5TR | Status Code Allowed 1 to 5 | P40204 | Other allowed steps (overrides), e.g. skip pick slip for nonstock lines. | |
F40203.FSWRTH | Flag - Write Ledger Record (Y/N) | P40204 | Y writes a copy of the line to F42199 at this step. | |
F4211.SDLTTR | Status Code - Last | Every step program | The step the line last completed. | |
F4211.SDNXTR | Status Code - Next | Every step program | The step the line waits for. Filter on it to build work queues. | |
P42040 | Sales Order Speed Status Update (Status Code Update) | Manual advance of selected lines | Can skip only to statuses allowed in the rules; cannot set 999 or restricted statuses, and does not release held orders. | |
R42997 | Inventory Commitment | Batch | Commits future committed lines when they come within the commitment window. |
Status codes are user defined in UDC 40/AT and the sequence is set per order type and line type in F40203 via P40204, menu G4241. The flow above is a common standard setup, not a rule: always read F40203 for your order type and line type before writing reports or automation.
Get your activity rules checked
Export F40203 for your sales order types and we will map the real flow, the skips it allows and where lines tend to stall.
Optional. The tool and every export work without this. No spam.
How order activity rules work
Every sales order line carries a last status (SDLTTR) and a next status (SDNXTR) in F4211. Order activity rules in F40203, keyed by order type, line type and status, define the expected next step (FSNXTR) and up to five other allowed steps (FSA1TR to FSA5TR). Status codes must be in ascending order, and each code must exist in UDC 40/AT. You maintain the rules in Order Activity Rules (P40204) from Sales Order Management Setup (G4241). The Write Ledger flag decides whether the line is copied to F42199 at that step.
- Rules are per order type and line type
- Codes are site defined in UDC 40/AT
- Other allowed steps enable skips
Worked example: tracing a stuck line
A customer service rep says order 104512 SO line 2.000 never invoiced. F4211 shows SDLTTR 560 and SDNXTR 580, so it was ship confirmed and is waiting for Print Invoices. The R42565 version run nightly selects SDNXTR = 580, but its data selection also filters a ship-to that this line does not match. Fixing the version selection, or running the invoice print for that order, moves the line to 620. If the line showed 904, it would be a backorder split created at ship confirmation, waiting for P42117 or R42118.
Version differences and gotchas
Do not hard code 520, 540, 560, 580 and 620 in reports: many sites add steps such as credit check or EDI acknowledgment, and some use 580 for cycle billing. Read F40203 for the order type and line type instead. P42040 can advance only to statuses in the rules and cannot close lines to 999, so lines must go through the real steps. Holds are separate from status: advancing a held order does not release it. If FSWRTH is N everywhere, F42199 will have no ledger rows to audit.
Frequently Asked Questions
What are order activity rules in JDE?
Order activity rules, stored in F40203 and maintained in P40204, define for each order type and line type the sequence of status codes a line passes through, the expected next status, up to five other allowed statuses and whether to write a ledger record to F42199 at each step.
What is speed status update in JDE?
Sales Order Speed Status Update, P42040 (also called Status Code Update), lets you manually advance selected lines to the next or another allowed status. It cannot move lines to 999 or to restricted statuses, and it does not release held orders. Steps must exist in the order activity rules.
Which program releases backorders in JDE?
Release Backorders - Online (P42117) releases selected backordered lines interactively. Backorder Release and Report (R42118) does it in batch. Lines backordered at ship confirmation are split into a new line at status 904 (Backordered at Shipment Confirmation) with the remaining quantity.
What does status 999 mean on a JDE sales order?
999 means the line is closed. Sales Update (R42800) normally sets it, and only lines at 999 can be purged from F4211 to the F42119 history table by R42800 or Purge Detail to History (R42996). P42040 cannot set a line to 999.
If your customer service team wants to ask 'which lines are stuck before invoicing and why' in plain English, answered from F4211 and F40203 on your own servers, we can build that.
Related Tools
JD Edwards F4211 vs F42119 Sales Order Detail and History Columns Reference
Column-by-column reference for the JDE 9.2 sales order family: F4201 header, F4211 detail, F42119 and F42019 history and the F42199 detail ledger, with keys, data types and storage notes.
OracleJD Edwards Document Types Reference (OP, SO, OV, PV)
Searchable lookup of common JD Edwards document types such as OP, SO, OV and PV, with the module and the table that normally holds them.
OracleJD Edwards Inventory Tables Reference (F41021, F4111, F4105, F4108, F4100)
Reference for the JDE 9.2 inventory tables with key columns, the programs that maintain them, joins, and one row per F41021 quantity bucket explaining what drives it.
OracleJD Edwards AAI and DMAAI Reference (F0012, F4095)
The financial AAIs (F0012) and distribution/manufacturing AAIs (F4095) that cause most posting questions in JDE 9.2, with the program that uses each and a typical setup mistake.
More Oracle tools
See all- JD Edwards EnterpriseOne Private AI Layer Blueprint Generator
- JD Edwards EnterpriseOne AI Assistant Sizing and Value Calculator
- JD Edwards EnterpriseOne System and Object Librarian Tables Reference
- JD Edwards EnterpriseOne 9.2 Tools Release History Reference
- JD Edwards AP and AR Ledger Tables Reference (F0411, F0413, F0414, F03B11, F03B13, F03B14)
- JD Edwards Security Tables and Security Types Reference (F00950, F95921, F9312)
- JD Edwards EnterpriseOne 9.2 Upgrade Retrofit Effort Calculator
- JD Edwards Orchestrator Error Handling and Production Readiness Checklist
- JD Edwards EnterpriseOne 9.0 / 9.1 to 9.2 Application Upgrade Checklist
Keep exploring
Free tools
- JD Edwards Work Order Status Codes TemplateEditable worksheet to document your JD Edwards work order status codes, what each one means, who owns it and where an order can move next.
- JD Edwards System Codes ReferenceLook up what each JD Edwards system code stands for and how it shows up in table, application and UDC names.
- JD Edwards EnterpriseOne Core Table ReferenceSearchable list of the JD Edwards EnterpriseOne tables you query most often, with column prefix and the key fields to filter on.
ERP fixes and how-tos
- How to Add a Private AI Layer to JD Edwards EnterpriseOne On-PremAdd a private AI layer to JD Edwards EnterpriseOne: AIS data service, Orchestrator, Security Workbench mapping, a local model and human approval.
- How to Release a Sales Order on Hold in JD EdwardsFind why a JD Edwards sales order is held, release credit, margin or manual holds with Release Held Orders, and tune hold codes so fewer orders get stuck.
- JD Edwards Advanced Pricing: Adjustment Types, Schedules and Definitions ExplainedHow JD Edwards Advanced Pricing works: price adjustment types, definitions, schedules, price groups and the pricing tables, with a setup order and pitfalls.
Runs with your ERP
- Oracle CPQ and JD Edwards EnterpriseOne: quote to sales orderHow Oracle CPQ integrates with JD Edwards EnterpriseOne: customer data into quotes, sales orders created from quotes, and status back, with setup and pitfalls.
- Vertex Tax Connectors with JD Edwards EnterpriseOneHow Vertex calculates sales, use and VAT tax for JD Edwards EnterpriseOne and World, plus Oracle EBS and Cloud ERP: integration model, flows, setup, pitfalls.
- Avalara AvaTax with JD Edwards EnterpriseOne: automated sales and use taxHow Avalara AvaTax calculates sales, use and VAT tax in JD Edwards EnterpriseOne order-to-cash and procure-to-pay: connector, setup, pitfalls and AI help.
AI on your ERP
- AI for JD Edwards EnterpriseOne Procurement, From Requisition to VoucherPrivate AI for JD Edwards EnterpriseOne procurement: F4301 and F4311 purchase orders, receipts and voucher match, via AIS and Orchestrator, on-prem ready.
- AI for JD Edwards Inventory Management and Shop Floor ManufacturingAI on JD Edwards EnterpriseOne inventory and manufacturing: item ledger, work orders, MRP messages and cost variances, answered in plain English on your own servers.
Integrations
- How to add an AI chatbot to JD Edwards EnterpriseOneAdd an AI chatbot to JD Edwards EnterpriseOne: grounded in ERP data via AIS, for planners, buyers and customers, and able to run fully on-prem.
- How to add AI agents to JD Edwards EnterpriseOneHow to add AI agents to JD Edwards EnterpriseOne: Orchestrator and AIS as the tool layer, read-only first, human approval on writes, on-prem models.