# SAP IDoc Control Record (EDIDC) Fields Reference > Source: https://netray.co/tools/sap-idoc-control-record-edidc-fields-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Look up every commonly used field of the IDoc control record (table EDIDC and structure EDI_DC40) with its meaning and data type. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP integration developer - SAP ABAP developer - SAP PI/PO consultant ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Field **Key:** field **Type:** text #### Meaning **Key:** meaning **Type:** text #### Data type **Key:** dtype **Type:** text #### Notes **Key:** notes **Type:** text **Rows:** **Field:** MANDT **Meaning:** Client **Dtype:** CLNT 3 **Notes:** Only in table EDIDC, not in the EDI_DC40 file structure **Field:** DOCNUM **Meaning:** IDoc number **Dtype:** NUMC 16 **Notes:** Unique number per client, assigned when the IDoc is created **Field:** STATUS **Meaning:** Current status of the IDoc **Dtype:** CHAR 2 **Notes:** Latest status is copied here from table EDIDS **Field:** DIRECT **Meaning:** Direction **Dtype:** CHAR 1 **Notes:** 1 = outbound, 2 = inbound **Field:** IDOCTP **Meaning:** Basic IDoc type **Dtype:** CHAR 30 **Notes:** Structure definition, for example ORDERS05 **Field:** CIMTYP **Meaning:** Extension (customer IDoc type) **Dtype:** CHAR 30 **Notes:** Only filled when a basic type is extended **Field:** MESTYP **Meaning:** Logical message type **Dtype:** CHAR 30 **Notes:** Business meaning, for example ORDERS; drives partner profile lookup **Field:** MESCOD **Meaning:** Logical message variant **Dtype:** CHAR 3 **Notes:** Optional, refines the message type in the partner profile **Field:** MESFCT **Meaning:** Logical message function **Dtype:** CHAR 3 **Notes:** Optional, further refines the message type **Field:** STD **Meaning:** EDI standard **Dtype:** CHAR 1 **Notes:** For example X for ANSI X12, E for EDIFACT **Field:** STDVRS **Meaning:** Version of the EDI standard **Dtype:** CHAR 6 **Notes:** Used with subsystem EDI conversion **Field:** STDMES **Meaning:** EDI message type **Dtype:** CHAR 6 **Notes:** For example 850 for X12 or ORDERS for EDIFACT **Field:** SNDPOR **Meaning:** Sender port **Dtype:** CHAR 10 **Notes:** Port defined in WE21 **Field:** SNDPRT **Meaning:** Sender partner type **Dtype:** CHAR 2 **Notes:** LS = logical system, KU = customer, LI = vendor **Field:** SNDPFC **Meaning:** Sender partner function **Dtype:** CHAR 2 **Notes:** For example SP, SH, BP when the partner type needs one **Field:** SNDPRN **Meaning:** Sender partner number **Dtype:** CHAR 10 **Notes:** Logical system name, customer number or vendor number **Field:** RCVPOR **Meaning:** Receiver port **Dtype:** CHAR 10 **Notes:** Port defined in WE21 **Field:** RCVPRT **Meaning:** Receiver partner type **Dtype:** CHAR 2 **Notes:** LS = logical system, KU = customer, LI = vendor **Field:** RCVPFC **Meaning:** Receiver partner function **Dtype:** CHAR 2 **Notes:** Same value set as the sender partner function **Field:** RCVPRN **Meaning:** Receiver partner number **Dtype:** CHAR 10 **Notes:** Key part of partner profile WE20 **Field:** CREDAT **Meaning:** Creation date **Dtype:** DATS 8 **Notes:** Date the IDoc was created **Field:** CRETIM **Meaning:** Creation time **Dtype:** TIMS 6 **Notes:** Time the IDoc was created **Field:** UPDDAT **Meaning:** Date of last change **Dtype:** DATS 8 **Notes:** Updated on each status change **Field:** UPDTIM **Meaning:** Time of last change **Dtype:** TIMS 6 **Notes:** Updated on each status change **Field:** SERIAL **Meaning:** EDI serialization field **Dtype:** CHAR 20 **Notes:** Used to detect out-of-order delivery of related IDocs **Field:** REFINT **Meaning:** Reference to transmission file **Dtype:** CHAR 14 **Notes:** Interchange reference from a file or EDI subsystem **Field:** REFGRP **Meaning:** Reference to message group **Dtype:** CHAR 14 **Notes:** Group reference from the EDI subsystem **Field:** REFMES **Meaning:** Reference to message **Dtype:** CHAR 14 **Notes:** Message reference from the EDI subsystem **Field:** ARCKEY **Meaning:** Archive key for external archive **Dtype:** CHAR 70 **Notes:** Set when the IDoc is archived with an external system **Field:** TEST **Meaning:** Test flag **Dtype:** CHAR 1 **Notes:** X marks a test IDoc **Field:** OUTMOD **Meaning:** Output mode **Dtype:** CHAR 1 **Notes:** Outbound only; 2 = transfer immediately, 4 = collect IDocs **Field:** TABNAM **Meaning:** Name of the control record structure **Dtype:** CHAR 10 **Notes:** Holds EDI_DC40 in the file or tRFC representation **Notes:** Field names and lengths are as delivered in standard SAP. Lengths of rarely used fields can differ by release, so confirm in SE11 for table EDIDC and structure EDI_DC40 on your system. ## Content **Intro:** The IDoc control record is the header that tells SAP who sent the document, who receives it, what business message it carries and which structure it uses. This table lists the fields you meet most often when debugging or coding IDoc interfaces. **Sections:** #### How to use this reference **Body:** Type a field name or a keyword such as partner or port into the search box to narrow the table. Use the Notes column to see typical values. Export the result to Excel or CSV if you want to paste field lists into an interface specification or a mapping document for the integration team. **Bullets:** - Search by field name to confirm length before building a file interface - Search by direction or partner to find the fields used by partner profile lookup - Export the table into your interface specification #### EDIDC versus EDI_DC40 **Body:** Table EDIDC stores the control record in the database. Structure EDI_DC40 is the representation used when IDocs travel through tRFC calls, files and middleware such as SAP PI/PO or Integration Suite. The two carry almost the same fields, but EDI_DC40 adds TABNAM and lacks the client field in file transfers. In ABAP, function modules such as IDOC_INBOUND_ASYNCHRONOUS take the older EDIDC format while newer interfaces use EDI_DC40. #### Message type versus IDoc type **Body:** MESTYP says what the document means, for example ORDERS for a purchase order or sales order. IDOCTP says which segment structure carries it, for example ORDERS05. One message type can use several IDoc types over releases, and one IDoc type can serve several message types. Partner profiles in WE20 are keyed by message type, not IDoc type, so a wrong MESTYP is a classic reason for status 56 or 64 errors. #### Common mistakes **Body:** Developers often fill sender and receiver partner numbers with system IDs instead of logical system names, forget the partner type, or leave the port blank. Another trap is confusing DIRECT values: outbound is 1 and inbound is 2, and the same partner can have a different profile entry per direction. **Bullets:** - Use the logical system name from BD54 when the partner type is LS - Check the port exists in WE21 before sending - Set DIRECT correctly before calling inbound function modules **Cta:** If your team spends time chasing IDoc errors across systems, Netray can build a private assistant that reads IDoc tables and explains failures in plain language, with read-only access by default. **Faq:** #### What is the difference between EDIDC and EDID4? **Answer:** EDIDC holds one control record per IDoc, which is the header. EDID4 holds the data records, which are the segments with their field content stored as a string. EDIDS holds the status history. Together these three tables are what you query to analyse IDoc traffic directly in the database. #### What does DIRECT mean in an IDoc? **Answer:** DIRECT is a one-character field that tells you the direction as seen from the system you are in. A value of 1 means outbound, so the IDoc was created here and sent out. A value of 2 means inbound, so it arrived here to be posted into an application. #### Which field links an IDoc to its partner profile? **Answer:** For outbound IDocs, SAP looks up the partner profile using the receiver partner number, partner type and message type, optionally with function, code and variant. For inbound IDocs it uses the sender partner details. The profile then decides the port, output mode and process code. #### Can I add my own fields to the control record? **Answer:** No. The control record structure is fixed by SAP. If you need extra data, carry it in a custom segment through an IDoc extension, or use the reference fields such as REFINT and REFMES only for what they are meant for, which is tracking external transmission references. ## Search terms edidc fields, edi_dc40 fields, idoc control record fields, sap idoc control record structure, idoc mestyp idoctp difference, sap idoc sender partner fields, edidc table sap, idoc direct field 1 2 --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json