Skip to content
JDE Reference

F47011

transactionAlso in JDE World

One row per inbound EDI customer purchase order (X12 850) waiting to become a JDE sales order header; staging mirror of F4201.

Notes

R47011 edits these rows into F4201/F4211 and sets EDSP to Y. Comparing EDSP='N' backlog against processed rows by trading partner is the standard 850-to-sales-order reconciliation dashboard.

Fields

31 fields · 3 key

KeyFieldAliasDescriptionTypeLengthFlags
SYEDTYEDTYIdentifies which record layout this row carries inside the EDI document (header, detail, address, text).Character1
Primary keySYEKCOEKCOKey company that scopes the EDI document number; part of the staging primary key.String5
Primary keySYEDOCEDOCEDI document number assigned when the transaction is staged; the primary handle for one staged EDI document.Numeric9
Primary keySYEDCTEDCTEDI document type qualifier; pairs with document number and key company to complete the staging key.String2
SYEDSTEDSTX12 transaction-set number this row stages (850, 855, 856, 810).String6
SYEDDTEDDTJulian date the transmission was created or received by the EDI translator.Numeric6
SYEDEREDERDirection flag: R for documents received from the trading partner, S for documents JDE is sending.Character1
SYEDDLEDDLCount of detail lines belonging to this EDI document.Numeric5
SYEDSPEDSPProcessed flag: Y once the edit/update program has moved this row to or from the live application tables. Filter N for the open queue; Y rows are the reconciliation audit trail.Character1
SYEDBTEDBTBatch number grouping documents staged in the same translator run.String15
SYPNIDPNIDTrading partner identifier agreed with the customer or supplier; the natural grain for partner-level EDI scorecards.String15
SYTPURTPURPurpose of the transaction set: original, change, cancellation, or response.String2
SYKCOOKCOOCompany segment of the JDE order number key.String5
SYDOCODOCOJDE sales order number created or matched when the 850 is processed; the join to F4201/F4211.Numeric8
SYDCTODCTOJDE order type of the related order (SO, OP, and so on).String2
SYSFXOSFXOOrder suffix; distinguishes multiple documents against the same order number.String3
SYMCUMCUBranch/plant on the order; right-justified 12-character business unit.String12
SYCOCOCompany that owns the transaction.String5
SYAN8AN8Primary address book number on the document: customer sold-to on sales documents, supplier on purchasing documents.Numeric8
SYSHANSHANShip-to address book number.Numeric8
SYDRQJDRQJRequested date on the order line or document (Julian).Numeric6
SYTRDJTRDJOrder or transaction date (Julian).Numeric6
SYPPDJPPDJPromised shipment date (Julian).Numeric6
SYVR01VR01Free-form customer reference; on customer-facing documents this usually carries the customer's PO number.String25
SYPTCPTCPayment terms code applied to the document.String3
SYFRTHFRTHFreight handling code describing who arranges and pays freight.String3
SYOTOTOTOTGross document amount staged for the transaction.Numeric15
SYCRCDCRCDTransaction currency code.String3
SYCRRCRRSpot exchange rate used to convert the transaction currency; implied decimals vary by setup.Numeric15
SYRQSJRQSJRequested ship date (Julian).Numeric6
SYHOLDHOLDHold code applied when the staged order needs review before release.String2

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading F47011on Databricks — Julian dates, implied decimals, and padded strings are already converted. Set your Unity Catalog location and filter values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : F47011 One row per inbound EDI customer purchase order (X12 850) waiting to become a JDE sales order header; staging mirror of F4201.
-- Purpose: Column-selected read of F47011 — auto-generated from field metadata
-- Grain  : One row per SYEKCO + SYEDOC + SYEDCT
-- Notes  : Auto-generated skeleton. Julian dates (CYYDDD) are converted to DATE and implied-decimal amounts are scaled (verify decimals in F9210); padded business-unit/UDC keys are TRIMmed. Audit columns (…USER/…PID/…UPMJ) are omitted — see the quirks guide. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
  f.SYEKCO AS "Key company that scopes the EDI document number; part of the staging primary key.",
  f.SYEDOC AS "EDI document number assigned when the transaction is staged; the primary handle for one staged EDI document.",
  f.SYEDCT AS "EDI document type qualifier; pairs with document number and key company to complete the staging key.",
  f.SYEDTY AS "Identifies which record layout this row carries inside the EDI document (header, detail, address, text).",
  f.SYEDST AS "X12 transaction-set number this row stages (850, 855, 856, 810).",
  CASE WHEN f.SYEDDT IS NULL OR f.SYEDDT = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.SYEDDT AS INT) DIV 1000, 1, 1), CAST(f.SYEDDT AS INT) % 1000 - 1) END AS "Julian date the transmission was created or received by the EDI translator.",  -- CYYDDD Julian → DATE
  f.SYEDER AS "Direction flag: R for documents received from the trading partner, S for documents JDE is sending.",
  f.SYEDDL AS "Count of detail lines belonging to this EDI document.",
  f.SYEDSP AS "Processed flag: Y once the edit/update program has moved this row to or from the live application tables. Filter N for the open queue; Y rows are the reconciliation audit trail.",
  f.SYEDBT AS "Batch number grouping documents staged in the same translator run.",
  f.SYPNID AS "Trading partner identifier agreed with the customer or supplier; the natural grain for partner-level EDI scorecards.",
  f.SYTPUR AS "Purpose of the transaction set: original, change, cancellation, or response.",
  f.SYKCOO AS "Company segment of the JDE order number key.",
  f.SYDOCO AS "JDE sales order number created or matched when the 850 is processed; the join to F4201/F4211.",
  f.SYDCTO AS "JDE order type of the related order (SO, OP, and so on).",
  f.SYSFXO AS "Order suffix; distinguishes multiple documents against the same order number.",
  TRIM(f.SYMCU) AS "Branch/plant on the order; right-justified 12-character business unit.",
  f.SYCO AS "Company that owns the transaction.",
  f.SYAN8 AS "Primary address book number on the document: customer sold-to on sales documents, supplier on purchasing documents.",
  f.SYSHAN AS "Ship-to address book number.",
  CASE WHEN f.SYDRQJ IS NULL OR f.SYDRQJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.SYDRQJ AS INT) DIV 1000, 1, 1), CAST(f.SYDRQJ AS INT) % 1000 - 1) END AS "Requested date on the order line or document (Julian).",  -- CYYDDD Julian → DATE
  CASE WHEN f.SYTRDJ IS NULL OR f.SYTRDJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.SYTRDJ AS INT) DIV 1000, 1, 1), CAST(f.SYTRDJ AS INT) % 1000 - 1) END AS "Order or transaction date (Julian).",  -- CYYDDD Julian → DATE
  CASE WHEN f.SYPPDJ IS NULL OR f.SYPPDJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.SYPPDJ AS INT) DIV 1000, 1, 1), CAST(f.SYPPDJ AS INT) % 1000 - 1) END AS "Promised shipment date (Julian).",  -- CYYDDD Julian → DATE
  f.SYVR01 AS "Free-form customer reference; on customer-facing documents this usually carries the customer's PO number.",
  f.SYPTC AS "Payment terms code applied to the document.",
  f.SYFRTH AS "Freight handling code describing who arranges and pays freight.",
  f.SYOTOT / POWER(10, 2) AS "Gross document amount staged for the transaction.",  -- implied decimals: 2 (verify in F9210)
  f.SYCRCD AS "Transaction currency code.",
  f.SYCRR AS "Spot exchange rate used to convert the transaction currency; implied decimals vary by setup.",
  CASE WHEN f.SYRQSJ IS NULL OR f.SYRQSJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.SYRQSJ AS INT) DIV 1000, 1, 1), CAST(f.SYRQSJ AS INT) % 1000 - 1) END AS "Requested ship date (Julian).",  -- CYYDDD Julian → DATE
  f.SYHOLD AS "Hold code applied when the staged order needs review before release."
FROM <catalog>.<schema_data>.f47011 f
WHERE
  f.SYTRDJ >= <TRDJ_FROM>  -- Julian CYYDDD, e.g. 126001
  -- AND f.SYTRDJ <= <TRDJ_TO>  -- Julian CYYDDD, e.g. 126365
ORDER BY f.SYEKCO;

4 parameters not filled: <catalog>, <schema_data>, <TRDJ_FROM>, <TRDJ_TO>

Relationships

1-hop neighbors — click a table to navigate there. UDC decode edges point coded fields at their F0005 lookup.

Join details

  • F47011F47012header detail · 1:N
    ON f47011.SYEDOC = f47012.SZEDOC

Programs That Use This Table