# SPS Commerce Fulfillment with JD Edwards: Retail EDI Without Writing Maps > Source: https://netray.co/stack/sps-commerce-fulfillment-edi-jd-edwards > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Stack ## Short answer SPS Commerce Fulfillment is a managed retail EDI network: SPS maintains the trading-partner maps and exchanges sales orders, advance ship notices and invoices with retailers. SPS documents a direct JD Edwards connection built on Oracle Application Integration Architecture that touches 47 JDE tables, covering EnterpriseOne and World. Manufacturers who sell to big-box and distribution accounts use it to avoid building and maintaining each retailer's EDI spec in house. ## Erp Oracle JD Edwards EnterpriseOne ## Erp Key jd-edwards ## On Prem true ## Product SPS Commerce Fulfillment ## Vendor SPS Commerce ## Category EDI ## Integration **Method:** Direct JDE connection on Oracle Application Integration Architecture **Detail:** Per SPS, the connector reads and writes JD Edwards through an integration layer built on Oracle AIA and touches 47 JDE tables, so inbound retailer purchase orders become JDE sales orders and outbound ASNs and invoices are built from JDE shipment and billing data. SPS owns the retailer-facing maps; your team owns the JDE-side configuration and master data. **Method:** Managed service model **Detail:** Because SPS operates the network and the maps, retailer spec changes (a new label standard, an extra segment) are handled on the SPS side. You still have to keep item cross-references, ship-to numbers and pricing in JDE aligned with what each retailer sends. ## Data Flows **From:** Retailer via SPS **To:** JD Edwards Sales Order (F4201/F4211) **Data:** 850 purchase order converted to a sales order **Trigger:** Order received on the SPS network and released to JDE **From:** JD Edwards **To:** Retailer via SPS **Data:** 855 acknowledgment or 856 advance ship notice **Trigger:** Order entry confirmation, then ship confirm in JDE **From:** JD Edwards **To:** Retailer via SPS **Data:** 810 invoice with PO, item and ship-to references **Trigger:** Invoice generated after shipment **From:** Retailer via SPS **To:** JD Edwards **Data:** Order changes and cancellations **Trigger:** Retailer sends a revised or cancelled PO ## Setup ### Confirm scope with SPS **Detail:** List the retailers, document types (850, 855, 856, 810) and whether you run EnterpriseOne or World. Ask SPS which JDE release levels and tool releases they have deployed against. ### Load customer and ship-to master data **Detail:** Create address book and customer master records for every retailer and DC, with the identifiers (DUNS, GLN, store numbers) the retailer sends in EDI. ### Build item cross-references **Detail:** Map retailer UPC or buyer item numbers to your JDE item numbers and units of measure. This is the most common cause of rejected orders. ### Agree pricing and tax handling **Detail:** Decide whether the EDI price or the JDE price wins and how a mismatch is flagged rather than silently accepted. ### Configure shipping and labeling **Detail:** Set up carton and pallet labeling (SSCC) and the data the 856 needs, such as pack hierarchy and carrier SCAC. ### Run retailer certification tests **Detail:** Complete each retailer's test cycle with sample orders end to end, from order to invoice, before going live. ### Cut over and monitor **Detail:** Go live one retailer at a time and review daily exception queues for the first few weeks. ## Pitfalls - Item cross-reference gaps: a retailer UPC not mapped to a JDE item stops the order at the door. - Unit of measure mismatch between the retailer's each/case and JDE primary and pricing units causes wrong quantities or prices on the 810. - ASN sent before JDE ship confirm completes, or built from a different pack structure than what was physically shipped, leads to retailer chargebacks. - Ship-to and store numbers not in the address book make orders fail validation or default to the wrong address. - Retailer spec changes land on a date, not your schedule; without a test order for each change you find out through a chargeback. - Duplicate or revised POs processed as new orders when the change logic is not agreed with SPS. ## Ai Layer ### Rejected order triage **Description:** A private assistant reading the SPS exception list and JDE master data can say why an order failed (missing cross-reference, unknown ship-to) and draft the fix for a person to approve. ### Chargeback explanation **Description:** Given a retailer chargeback, it can pull the matching PO, ASN timestamp and JDE shipment to show what differed, in plain language. ### Plain-language order status **Description:** Customer service can ask where a retailer PO stands across SPS and JDE without opening several screens, with the underlying query shown. ## Alternatives - If you only have one or two EDI partners, a lighter EDI service or direct AS2 with a mapping tool may cost less than a full managed network. - A general iPaaS EDI platform such as Cleo suits you if your partners are not mostly retailers. - Oracle's own B2B tooling in Oracle Integration fits if you are moving toward Oracle Cloud and want to stay in one stack. ## Faq ### Does SPS Commerce work with both JD Edwards EnterpriseOne and World? **Answer:** SPS lists JD Edwards as a supported integration and describes a direct connection built on Oracle Application Integration Architecture. Their page covers EnterpriseOne and World. Confirm your exact release and tools level with SPS during scoping, since the supported combinations are theirs to state, not something to assume from the product page. ### Who maintains the EDI maps? **Answer:** In the Fulfillment model SPS maintains the trading-partner maps, so a retailer changing its spec is generally handled on their side. You remain responsible for the JDE data those maps depend on: item cross-references, ship-to records, pricing and unit of measure. Most day-to-day failures are data problems, not map problems. ### Can a private AI help with EDI exceptions? **Answer:** Yes, as a read-only layer. An assistant running on your own infrastructure can read the exception list and JDE records, explain the cause of a rejected order or chargeback, and draft a correction. Any change to JDE data stays behind a person's approval. ## Source https://spscommerce.com/products/fulfillment/integrated-fulfillment/system-integrations/jd-edwards ## Search terms sps commerce jd edwards edi, jd edwards retail edi, sps commerce enterpriseone, jde 856 asn, jd edwards world edi, sps fulfillment jd edwards --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json