JD Edwards creates sales orders in bulk through its EDI inbound tables and R47011, and those tables only take rows.
PDF, JPG, PNG, BMP, HEIC, TIFF
Submit your purchase orders
Drop documents here, or choose a file
Up to 50 files per batch
Uploading...
JD Edwards creates sales orders in bulk through its EDI inbound tables and R47011, and those tables only take rows. Upload the purchase order a customer emailed and get the PO number, ship-to, dates and every line with part, quantity and price as F47011 and F47012 rows.
Your EDI customers flow through R47011 untouched. The ones who email a PDF land on the order desk, and someone keys every line into Sales Order Entry.
F47011 and F47012 are interface tables. A translator fills them for EDI partners, but nothing fills them from a PDF, so non-EDI customers get typed by hand.
EDOC, EDCT and EKCO tie the header to its lines, and JD Edwards does not number them for you. One mismatched key and the lines never meet the header.
EDLN is a three-decimal field, so line 1 is mapped as 1000 and line 2 as 2000. Load 1 and the sales order lines come out as 0.001.
Customers order by their own codes. Unless the line carries your item number or a cross-referenced customer item, R47011 stops the order.
Upload the purchase order your customer sent. The AI reads the header and every line and returns a spreadsheet with one row per line and the header values repeated, ready to split into the F47011 header and F47012 detail your load expects.
No per-customer template. Digital PDFs, scans and photographed pages from any buyer system come back in the same column layout.
Lines return in document order with a sequence number, so EDLN becomes 1000, 2000, 3000 with one formula.
The buyer PO number lands in a dedicated column for VR01, so the order desk can find the sales order when a buyer calls with only their reference.
Unit price comes off the document for each line, so you can carry it as an override or compare it with JD Edwards pricing before the order ships.
JD Edwards EnterpriseOne already has a route for turning a customer purchase order into a sales order without a person in Sales Order Entry. It is the inbound 850 path in system 47. An EDI translator writes the order into the EDI Purchase Order Header (F47011) and EDI Purchase Order Detail (F47012) interface tables, plus addresses in F4706 and order text in F4714 and F4715 when there are any. EDI Inbound Purchase Order Edit/Create (R47011) then reads those staging rows, validates them through the version of Sales Order Entry (P4210) named in its processing options, and writes real sales orders to F4201 and F4211.
That route is built for trading partners who send X12. Most distributors and manufacturers also have customers who email a PDF, upload to a portal or fax a scan, and for those the 850 path sits idle while the order desk keys every line. PurchaseOrders fills that gap. It reads the customer document and returns the header and every line as Excel, CSV or JSON, so the same F47011 and F47012 rows your EDI partners produce can be built for PDF customers too. The load itself stays yours: the Inbound Flat File Conversion program (R47002C), an Orchestrator, or the integration your team already uses for EDI.
Oracle documents a short list of fields that must be filled, and none of them is assigned by JD Edwards. On the header, EDOC (EDI document number), EDCT (EDI document type) and EKCO (EDI document key company) form the key, EDST is the transaction set and holds 850, and EDER is the send or receive flag and holds R. The detail rows repeat the same EDOC, EDCT, EKCO, EDST and EDER values. If one line carries a different document number, R47011 never joins it to the header, and you get an order with missing lines or no order at all.
Two rules catch most first loads. The line number EDLN is a field with three decimals, so line 1 must be loaded as 1000 and line 2 as 2000, and the value carries into the sales order line number. And the address numbers must be consistent: if the header carries the sold-to in AN8 only, the detail carries AN8 only; if the header carries the ship-to in SHAN, the detail does too. Every detail row also needs one item number (short ITM, second LITM, third AITM or a customer item in CITM) and an ordered quantity in UORG.
Buyers print their own part numbers. R47011 can translate them if you load the customer code as the item and maintain an item cross-reference of the customer type, so set the cross-reference once per customer and every later PO matches. The customer PO number belongs in VR01, Reference 1, on the header and lines. For price, the transmitted unit price can be carried into the sales order as an override or ignored so JD Edwards prices the line; that choice is a processing option, and an override switches off advanced pricing discounts for those lines, so decide it with your pricing team before the first batch.
Errors land in the Work Center, and the staging rows stay in the interface tables. Fix them with Inbound EDI Order Inquiry (P47010) and its revisions forms, which change the interface tables and not F4201 or F4211, then run R47011 again. Processed records are flagged in the processed field (EDSP) so a rerun does not create the same order twice. A 0425 Status Flow Not Set Up error means the order type and line type combination has no order activity rules, a setup issue rather than bad data. Test with one two-line order from a single customer before you load a batch, and check the result in Sales Order Entry.
For the buying side, supplier POs you issue, see JD Edwards purchase order import and the reference on JD Edwards purchase order tables F4301 and F4311. If you also receive real X12 from some customers and want to read it in a spreadsheet, the EDI 850 to Excel converter covers that side.
What comes off the customer document and which inbound 850 field it usually fills. Header aliases use the SY prefix in F47011 and the SZ prefix in F47012. Confirm against your release before the first load.
| Field | Table | Where it comes from | Notes |
|---|---|---|---|
| EDOC | F47011 and F47012 | Your own number for the incoming document. | Not auto-numbered, same on every line |
| EDCT | F47011 and F47012 | Fixed EDI document type you choose. | Same on header and lines |
| EKCO | F47011 and F47012 | Your key company. | Same on header and lines |
| EDST | F47011 and F47012 | Fixed value 850. | Transaction set |
| EDER | F47011 and F47012 | Fixed value R for receive. | Send or receive flag |
| AN8 or SHAN | F47011 and F47012 | The buyer and ship-to on the PO, matched to address book numbers. | Use the same choice on header and lines |
| VR01 | F47011 and F47012 | The purchase order number the customer printed. | Reference 1 |
| DRQJ | F47011 and F47012 | The requested delivery date. | On or after the order date |
| EDLN | F47012 | Line sequence from the document. | Line 1 = 1000, line 2 = 2000 |
| LITM or CITM | F47012 | Your item number, or the customer part number with a cross-reference. | One item field required |
| UORG | F47012 | Ordered quantity on each line. | Required |
| UPRC | F47012 | The unit price the buyer printed. | Override or ignored per processing option |
Four steps from the customer attachment to sales orders in JD Edwards.
Drop in the PDF, the scan or the email attachment. Up to 50 files per bulk upload, with no per-customer setup.
Tip: Portal downloads and forwarded attachments work the same way.
Check the header and lines on screen, then map the buyer to an address book number and confirm each part has an item or a customer cross-reference.
Tip: Add missing cross-references once and every later order matches.
Download CSV, add your EDOC, EDCT and EKCO keys, set EDST to 850 and EDER to R, and turn the line sequence into EDLN 1000, 2000, 3000.
Tip: Save the renamed header rows as the template for every future batch.
Write the rows to F47011 and F47012 with your loader, run R47011, and review the order in Sales Order Entry.
Tip: Start with one two-line PO before a full batch.
Load the orders into the inbound 850 interface tables, header rows in F47011 and line rows in F47012, then run EDI Inbound Purchase Order Edit/Create (R47011). It validates each order through the P4210 version in its processing options and creates sales orders in F4201 and F4211.
R47011 is EDI Inbound Purchase Order Edit/Create, the batch program that turns inbound customer purchase orders in F47011 and F47012 into JD Edwards sales orders. It uses the Sales Order Entry version named in its processing options, so holds, pricing and line defaults follow that version.
The key fields EDOC, EDCT and EKCO, the transaction set EDST (850) and the receive flag EDER (R) on both tables, plus a sold-to or ship-to address number. Each F47012 line also needs EDLN, one item number field and the quantity in UORG. JD Edwards does not number the keys for you.
EDLN was loaded as 1, 2, 3. The field holds three decimals, so line 1 must be loaded as 1000 and line 2 as 2000. The value carries into the sales order line number, so fix the staging rows and reprocess rather than editing the order.
Correct the staging record with Inbound EDI Order Inquiry (P47010), which revises the interface tables rather than F4201 and F4211, then run R47011 again. Processed records are flagged in EDSP so a rerun does not duplicate orders that already went through.
Not directly. The inbound 850 tables and R47011 expect structured rows. A customer PO that arrives as a PDF has to become rows first, typed into Sales Order Entry or extracted, before R47011 can create the sales order.
In Reference 1, the VR01 field, on the F47011 header and F47012 lines. R47011 carries it into the sales order, so the order desk can search by the buyer reference when a customer calls without your order number.
No. PurchaseOrders reads the customer purchase order and returns structured data as Excel, CSV or JSON. It does not install in JD Edwards, write to F47011 or run R47011. You load the rows with R47002C, an Orchestrator or your own integration.
Customer POs into Oracle Order Management.
The same workflow on SAP Business One.
The buying side: POs you issue.
Read real X12 850 files.
The same workflow on Sage 100.
The same workflow on Epicor.
Choose your plan