# JD Edwards Order Activity Rules and Sales Order Status Codes (F40203, UDC 40/AT)

> Source: https://netray.co/tools/jde-sales-order-status-codes-activity-rules-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

The typical SO / S status flow in JDE 9.2, the program that advances each step, special statuses such as 904 and 914, and the F40203 columns behind the rules.

## Category

oracle

## Erp

JD Edwards EnterpriseOne

## Audience

- Sales order functional consultant
- JDE developer
- Customer service lead

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Status / column

**Key:** code

**Type:** text

#### Description

**Key:** description

**Type:** text

#### Program that advances it

**Key:** program

**Type:** text

#### Typical next status

**Key:** next

**Type:** text

#### Notes

**Key:** notes

**Type:** text

**Rows:**

**Code:** 520

**Description:** Enter Sales Order

**Program:** Sales Order Entry (P4210)

**Next:** 540

**Notes:** Typical first status for SO / S in standard setups. Other allowed statuses let you skip steps.

**Code:** 540

**Description:** Print Pick Slips

**Program:** Print Pick Slips (R42520)

**Next:** 560

**Notes:** Pick slip number written to SDPSN. Hard commits are usually made by now.

**Code:** 560

**Description:** Ship Confirmation

**Program:** Shipment Confirmation (P4205)

**Next:** 580

**Notes:** After confirmation the line's last status (SDLTTR) is 560 and its next status (SDNXTR) is the following step, typically 580.

**Code:** 580

**Description:** Print Invoices

**Program:** Print Invoices (R42565)

**Next:** 620 (site specific)

**Notes:** Invoice number and date written to SDDOC and SDIVD. Some setups use 580 for cycle billing; check your rules.

**Code:** 620

**Description:** Sales Update

**Program:** Sales Update (R42800)

**Next:** 999

**Notes:** R42800 updates lines to 999 (or the status in its options), writes G/L and A/R, and can move lines to F42119.

**Code:** 999

**Description:** Complete - closed

**Program:** Set by the last step (R42800)

**Notes:** Closed. Only 999 lines can be purged to history. Status Code Update (P42040) cannot advance lines to 999.

**Code:** 904

**Description:** Backordered at Shipment Confirmation

**Program:** Created by P4205 for the unshipped quantity

**Next:** From the order process

**Notes:** New split line for the remaining quantity. Release it with Release Backorders - Online (P42117) or Backorder Release and Report (R42118).

**Code:** 914

**Description:** Added in Shipment Confirmation

**Program:** P4205 for intercompany orders created at confirmation

**Next:** Per rules

**Notes:** Status for lines added during shipment confirmation. Confirm the code and description in UDC 40/AT on your system.

**Code:** 980

**Description:** Canceled in Order Entry

**Program:** Cancel line in P4210

**Notes:** Canceled quantity in SDSOCN. Confirm the exact code in UDC 40/AT on your system.

**Code:** F40203.FSDCTO

**Description:** Order Type

**Program:** Order Activity Rules (P40204)

**Notes:** Key part 1. UDC 00/DT, e.g. SO.

**Code:** F40203.FSLNTY

**Description:** Line Type

**Program:** P40204

**Notes:** Key part 2. From line type constants (F40205), e.g. S.

**Code:** F40203.FSTRTY

**Description:** Status - Line (this step)

**Program:** P40204

**Notes:** Key part 3. The status code for this step (UDC 40/AT).

**Code:** F40203.FSNXTR

**Description:** Status Code - Next

**Program:** P40204

**Notes:** Expected next step. Must be a higher number.

**Code:** F40203.FSA1TR to FSA5TR

**Description:** Status Code Allowed 1 to 5

**Program:** P40204

**Notes:** Other allowed steps (overrides), e.g. skip pick slip for nonstock lines.

**Code:** F40203.FSWRTH

**Description:** Flag - Write Ledger Record (Y/N)

**Program:** P40204

**Notes:** Y writes a copy of the line to F42199 at this step.

**Code:** F4211.SDLTTR

**Description:** Status Code - Last

**Program:** Every step program

**Notes:** The step the line last completed.

**Code:** F4211.SDNXTR

**Description:** Status Code - Next

**Program:** Every step program

**Notes:** The step the line waits for. Filter on it to build work queues.

**Code:** P42040

**Description:** Sales Order Speed Status Update (Status Code Update)

**Program:** Manual advance of selected lines

**Notes:** Can skip only to statuses allowed in the rules; cannot set 999 or restricted statuses, and does not release held orders.

**Code:** R42997

**Description:** Inventory Commitment

**Program:** Batch

**Notes:** Commits future committed lines when they come within the commitment window.

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How order activity rules work

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### What are order activity rules in JDE?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

jde order activity rules, jde status code list, jde e1 speed status update, jde document type list, backorder release program in jde, jde f40203 table, jde status 520 540 560, jde 999 status

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json