Control record

General
IDoc control record for the IDoc interface of the SAP System R/3 to an external system.
The control record for Release 4.0 has the structure EDI_DC40. Each IDoc is initiated by exactly one control record. The record contains control information about outgoing and incoming IDocs as well as their processing in the SAP system and an external system.

Control record structure

Documentation

• TABNAM : Name of table structure

  internal data type : CHAR
  Internal length : 000010 characters
  Position in Segment : 001, Offset : 0000. external length : 000010
  

• MANDT : Client

  internal data type : CLNT
  Internal length : 000003 characters
  Position in Segment : 002, Offset : 0010. external length : 000003
  

• DOCNUM : IDoc number

  internal data type : CHAR
  Internal length : 000016 characters
  Position in Segment : 003, Offset : 0013. external length : 000016
  

• DOCREL : SAP Release for IDoc

  internal data type : CHAR
  Internal length : 000004 characters
  Position in Segment : 004, Offset : 0029. external length : 000004
  

• STATUS : Status of IDoc

  internal data type : CHAR
  Internal length : 000002 characters
  Position in Segment : 005, Offset : 0033. external length : 000002
  

• DIRECT : Direction

  internal data type : CHAR
  Internal length : 000001 characters
  Position in Segment : 006, Offset : 0035. external length : 000001
  

• OUTMOD : Output mode

  internal data type : CHAR
  Internal length : 000001 characters
  Position in Segment : 007, Offset : 0036. external length : 000001
  

• EXPRSS : Overriding in inbound processing

  internal data type : CHAR
  Internal length : 000001 characters
  Position in Segment : 008, Offset : 0037. external length : 000001
  

• TEST : Test flag

  internal data type : CHAR
  Internal length : 000001 characters
  Position in Segment : 009, Offset : 0038. external length : 000001
  

• IDOCTYP : Name of basic type

  internal data type : CHAR
  Internal length : 000030 characters
  Position in Segment : 010, Offset : 0039. external length : 000030
  

• CIMTYP : Extension (defined by customer)

  internal data type : CHAR
  Internal length : 000030 characters
  Position in Segment : 011, Offset : 0069. external length : 000030
  

• MESTYP : Message type

  internal data type : CHAR
  Internal length : 000030 characters
  Position in Segment : 012, Offset : 0099. external length : 000030
  

• MESCOD : Message code

  internal data type : CHAR
  Internal length : 000003 characters
  Position in Segment : 013, Offset : 0129. external length : 000003
  

• MESFCT : Message function

  internal data type : CHAR
  Internal length : 000003 characters
  Position in Segment : 014, Offset : 0132. external length : 000003
  

• STD : EDI standard, flag

  internal data type : CHAR
  Internal length : 000001 characters
  Position in Segment : 015, Offset : 0135. external length : 000001
  

• STDVRS : EDI standard, version and release

  internal data type : CHAR
  Internal length : 000006 characters
  Position in Segment : 016, Offset : 0136. external length : 000006
  

• STDMES : EDI message type

  internal data type : CHAR
  Internal length : 000006 characters
  Position in Segment : 017, Offset : 0142. external length : 000006
  

• SNDPOR : Sender port (SAP System, external subsystem)

  internal data type : CHAR
  Internal length : 000010 characters
  Position in Segment : 018, Offset : 0148. external length : 000010
  

• SNDPRT : Partner type of sender

  internal data type : CHAR
  Internal length : 000002 characters
  Position in Segment : 019, Offset : 0158. external length : 000002
  

• SNDPFC : Partner Function of Sender

  internal data type : CHAR
  Internal length : 000002 characters
  Position in Segment : 020, Offset : 0160. external length : 000002
  

• SNDPRN : Partner number of sender

  internal data type : CHAR
  Internal length : 000010 characters
  Position in Segment : 021, Offset : 0162. external length : 000010
  

• SNDSAD : Sender address (SADR)

  internal data type : CHAR
  Internal length : 000021 characters
  Position in Segment : 022, Offset : 0172. external length : 000021
  

• SNDLAD : Logical address of sender

  internal data type : CHAR
  Internal length : 000070 characters
  Position in Segment : 023, Offset : 0193. external length : 000070
  

• RCVPOR : Receiver port

  internal data type : CHAR
  Internal length : 000010 characters
  Position in Segment : 024, Offset : 0263. external length : 000010
  

• RCVPRT : Partner type of recipient

  internal data type : CHAR
  Internal length : 000002 characters
  Position in Segment : 025, Offset : 0273. external length : 000002
  

• RCVPFC : Partner function of recipient

  internal data type : CHAR
  Internal length : 000002 characters
  Position in Segment : 026, Offset : 0275. external length : 000002
  

• RCVPRN : Partner number of recipient

  internal data type : CHAR
  Internal length : 000010 characters
  Position in Segment : 027, Offset : 0277. external length : 000010
  

• RCVSAD : Recipient address (SADR)

  internal data type : CHAR
  Internal length : 000021 characters
  Position in Segment : 028, Offset : 0287. external length : 000021
  

• RCVLAD : Logical address of recipient

  internal data type : CHAR
  Internal length : 000070 characters
  Position in Segment : 029, Offset : 0308. external length : 000070
  

• CREDAT : Created on

  internal data type : DATS
  Internal length : 000008 characters
  Position in Segment : 030, Offset : 0378. external length : 000008
  

• CRETIM : Time created

  internal data type : TIMS
  Internal length : 000006 characters
  Position in Segment : 031, Offset : 0386. external length : 000006
  

• REFINT : Transmission file (EDI Interchange)

  internal data type : CHAR
  Internal length : 000014 characters
  Position in Segment : 032, Offset : 0392. external length : 000014
  

• REFGRP : Message group (EDI Message Group)

  internal data type : CHAR
  Internal length : 000014 characters
  Position in Segment : 033, Offset : 0406. external length : 000014
  

• REFMES : Message (EDI Message)

  internal data type : CHAR
  Internal length : 000014 characters
  Position in Segment : 034, Offset : 0420. external length : 000014
  

• ARCKEY : Key for external message archive

  internal data type : CHAR
  Internal length : 000070 characters
  Position in Segment : 035, Offset : 0434. external length : 000070
  

• SERIAL : Serialization

  internal data type : CHAR
  Internal length : 000020 characters
  Position in Segment : 036, Offset : 0504. external length : 000020
  

Control record documentation

Structure

• TABNAM : Name of table structure

  Use
  This field contains information about the IDoc structures exchanged with an external system. The following values are used:
  EDI_DC40 (Control record structure)
  EDI_DS40 (Status record structure)
  The data records (EDI_DD40) contain only the segment names.

• MANDT : Client

  Use
  From the R/3 side, the IDoc Interface enters the current client. An external system should not maintain this field (in inbound processing from the R/3 point of view and for status confirmation), to avoid unnecessary errors: transferred values are checked against the current client.

  Values
  
  '000' SAP AG Walldorf
  '001' Auslieferungsmandant R11 Kundstadt
  '020' Braun Europe production Kronberg
  '066' EarlyWatch Walldorf

• DOCNUM : IDoc number

  Use
  Identifies the IDoc. The number is client-specific and is determined via internal number assignment. The external system must consider the following:
  IDoc outbound processing (from the point of view of the R/3 System):
  The number must be kept for any later status confirmations (see below).
  IDoc inbound processing:
  This field remains empty (the IDoc is generated in the R/3 System).
  Status confirmation:
  The field must contain the number of the IDoc to which the status confirmation refers. Only in this way can the R/3 System assign the status records to an IDoc.

• DOCREL : SAP Release for IDoc

  Use
  Contains the R/3 release in which the IDoc was generated. In inbound processing (from the R/3 point of view), the external system should leave this field empty: if the value entered here does not correspond exactly to SY-SAPRL within the R/3 System, the IDoc status is marked as containing errors.

• STATUS : Status of IDoc

  Use
  IDoc processing can be monitored via the status. The external system must enter the correct value in the field in the status confirmation (see F4 help).
  The status for outbound IDocs is between '01' and '49', while the minimum status value for inbound IDocs is '50'.

  Outbound
  
  00 IDoc interface (SAP) : Not used, only R/2
  01 IDoc interface (SAP) : IDoc created
  02 IDoc interface (SAP) : Error passing data to port
  03 IDoc interface (SAP) : Data passed to port OK
  04 External system/EDI subsystem : Error within control information of EDI subsystem
  05 External system/EDI subsystem : Error during translation
  06 External system/EDI subsystem : Translation OK
  07 External system/EDI subsystem : Error during syntax check
  08 External system/EDI subsystem : Syntax check OK
  09 External system/EDI subsystem : Error during interchange handling
  10 External system/EDI subsystem : Interchange handling OK
  11 External system/EDI subsystem : Error during dispatch
  12 External system/EDI subsystem : Dispatch OK
  13 External system/EDI subsystem : Retransmission OK
  14 External system/EDI subsystem : Interchange Acknowledgement positive
  15 External system/EDI subsystem : Interchange Acknowledgement negative
  16 External system/EDI subsystem : Functional Acknowledgement positive
  17 External system/EDI subsystem : Functional Acknowledgement negative
  18 IDoc interface (SAP) : Triggering EDI subsystem OK
  19 IDoc interface (SAP) : Data transfer for test OK
  20 IDoc interface (SAP) : Error triggering EDI subsystem
  21 IDoc interface (SAP) : Error passing data for test
  22 External system/EDI subsystem : Dispatch OK, acknowledgement still due
  23 External system/EDI subsystem : Error during retransmission
  24 External system/EDI subsystem : Control information of EDI subsystem OK
  25 IDoc interface (SAP) : Processing despite syntax error (outbound)
  26 IDoc interface (SAP) : Error during syntax check of IDoc (outbound)
  27 IDoc interface (SAP) : Error in dispatch level (ALE service)
  28 IDoc interface (SAP) : Not used
  29 IDoc interface (SAP) : Error in ALE service
  30 IDoc interface (SAP) : IDoc ready for dispatch (ALE service)
  31 IDoc interface (SAP) : Error - no further processing
  32 IDoc interface (SAP) : IDoc was edited
  33 IDoc interface (SAP) : Original of an IDoc which was edited
  34 IDoc interface (SAP) : Error in control record of IDoc
  35 IDoc interface (SAP) : IDoc reloaded from archive
  36 External system/EDI subsystem : Electronic signature not performed (timeout)
  37 IDoc interface (SAP) : IDoc added incorrectly
  38 IDoc interface (SAP) : IDoc archived
  39 IDoc interface (SAP) : IDoc is in the receiving system (ALE service)
  40 IDoc interface (SAP) : Application document not created in receiving system
  41 IDoc interface (SAP) : Application document created in receiving system
  42 IDoc interface (SAP) : IDoc was created by test transaction
  50 IDoc interface (SAP) : IDoc added

  Inbound
  
  51 SAP application : Error: Application document not posted
  52 SAP application : Application document not fully posted
  53 SAP application : Application document posted
  54 SAP application : Error during formal application check
  55 SAP application : Formal application check OK
  56 IDoc interface (SAP) : IDoc with errors added
  57 SAP application : Test IDoc: Error during application check
  58 IDoc interface (SAP) : IDoc-Copy from an R/2 connection
  59 IDoc interface (SAP) : Not used
  60 IDoc interface (SAP) : Error during syntax check of IDoc (inbound)
  61 IDoc interface (SAP) : Processing despite syntax error (inbound)
  62 IDoc interface (SAP) : IDoc passed to application
  63 IDoc interface (SAP) : Error passing IDoc to application
  64 IDoc interface (SAP) : IDoc ready to be transferred to application
  65 IDoc interface (SAP) : Error in ALE service
  66 IDoc interface (SAP) : IDoc is waiting for predecessor IDoc (serialization)
  67 IDoc interface (SAP) : Not used
  68 IDoc interface (SAP) : Error - no further processing
  69 IDoc interface (SAP) : IDoc was edited
  70 IDoc interface (SAP) : Original of an IDoc which was edited
  71 IDoc interface (SAP) : IDoc reloaded from archive
  72 IDoc interface (SAP) : Not used, only R/2
  73 IDoc interface (SAP) : IDoc archived
  74 IDoc interface (SAP) : IDoc was created by test transaction

• DIRECT : Direction

  Use
  The field defines the direction of the IDoc transmission. This field is a required field.

  Values
  
  '1' Outbound
  '2' Inbound

• OUTMOD : Output mode

  Use
  In outbound processing, this value determines whether the IDocs are sent to the external system individually or in a packet. If an EDI subsystem
  is used, the output mode determines whether or not the R/3 System starts the subsystem.
  In inbound processing, this field should be left blank by the external system.

  Values
  
  '1' Transfer IDoc immediately and start external subsystem
  '2' Transfer IDoc immediately
  '3' Collect IDocs, transfer and start external subsystem
  '4' Collect IDocs and transfer

• EXPRSS : Overriding in inbound processing

  Use
  If this flag is set, the time plan control for inbound processing for ALE purposes is deactivated, i.e. the IDoc is processed immediately.

  Values
  
  '' No overriding
  'X' Overriding

• TEST : Test flag

  Use
  If a message is to be sent via IDoc for test purposes, the test indicator should be set in the partner profiles. Test messages in IDoc inbound processing cannot be posted 'live'. The external system must therefore enter 'X' in the field.
  The field is a key field in the partner profile for both inbound and outbound processing. The remaining key fields are the partner values (number, type and function) and the "logical" message values (type, code and function). These 7 fields determine the dependent parameters: the port in outbound processing or the process code in inbound processing.

  Values
  
  '' IDoc contains a productive message
  'X' IDoc contains a test message

• IDOCTYP : Name of basic type

  Use
  In the IDoc control record, the fields IDOCTYP and CIMTYP serve as a unique ID for the IDoc type: they specify the syntax, i.e. the segment sequence.
  When data is transferred between two systems, IDOCTYP must always be maintained, as the field contains the basic type
  ; CIMTYP contains the extension, and must therefore be maintained if an extension is used.

  Values
  
  '100_01' Output
  '682_01' Access sequence
  '683_01' Pricing Procedure (only in 40c)
  '684_01' Condition Exclusion Groups
  '685_01' Condition type
  '686A_01' Conditions: Exclusion indicator:
  'ABSEN1' Attendance/Absence in CC1
  'ACCONF01' Confirmation of IDoc processing from the application
  'ACC_ACT_ALLOC01' Accounting: Post activity allocation
  'ACC_ACT_ALLOC02' Accounting: Post activity allocation
  'ACC_ASSET_TRANSFER01' Accounting: Post Acquisition from Transfer
  'ACC_ASSET_TRANS_ACQ_POST01' Accounting: Post Acquisition from Transfer
  'ACC_BILLING01' Accounting: Post Billing Document (OAG: LOAD RECEIVABLE)
  'ACC_BILLING02' Accounting: Post Billing Document (OAG: LOAD RECEIVABLE)
  'ACC_DOCUMENT01' Accounting: Posting
  'ACC_EMPLOYEE_EXP01' FI/CO: HR Posting GL(AcctngEmplyeeExpnses)
  'ACC_EMPLOYEE_EXP02' FI/CO: HR posting GL(AcctngEmplyeeExpnses)
  'ACC_EMPLOYEE_PAY01' FI/CO: HR Posting AP(AcctngEmplyeePaybles)
  'ACC_EMPLOYEE_PAY02' FI/CO: HR posting AP(AcctngEmplyeePaybles)
  'ACC_EMPLOYEE_REC01' FI/CO: HR Posting AR(AcctngEmplyeeRcvbles)
  'ACC_EMPLOYEE_REC02' FI/CO: HR posting AR(AcctngEmplyeeRcvbles)
  'ACC_GL_POSTING01' Accounting: General G/L Account Posting
  'ACC_GOODS_MOVEMENT01' Accounting: Post Goods Movement (OAG: POST JOURNAL)
  'ACC_GOODS_MOVEMENT02' Accounting: Post Goods Movement (OAG: POST JOURNAL)
  'ACC_INVOICE_RECEIPT01' Accounting: Post Invoice Receipt (OAG: LOAD PAYABLE)
  'ACC_INVOICE_RECEIPT02' Accounting: Post Invoice Receipt (OAG: LOAD PAYABLE)
  'ACC_INVOICE_RECEIPT03' Accounting: Post Invoice Receipt (OAG: LOAD PAYABLE)
  'ACC_PRIM_COSTS01' Accounting: Post primary costs
  'ACC_PURCHASE_ORDER01' Accounting: Post Purchase Order
  'ACC_PURCHASE_REQUI01' Accounting: Post Purchase Requisition
  'ACC_REVENUES01' Accounting: Post revenues
  'ACC_SALES_ORDER01' Accounting: Post Sales Order
  'ACC_SALES_QUOTA01' Accounting: Post Customer Quotation
  'ACC_SENDER_ACTIVITIES01' Accounting: Post Sender Activities
  'ACC_STAT_KEY_FIG01' Accounting: Post statistical key figures
  'ACC_TRAVEL01' Accounting: Post trip
  'ACLPAY01' Posting in Accounting: Incoming Invoice
  'ACLREC01' Posting in accounting: Billing document
  'ACPJOU01' Posting in Accounting from Materials Management
  'ACTIV3' Units in KK3
  'ACTIV4' Units in KK4
  'ADR2MAS01' BAPI for inbound distribution of private addresses
  'ADR2MAS02' BAPI for inbound distribution of private addresses
  'ADR3MAS01' BAPI for inbound distribution of contact person addresses
  'ADR3MAS02' BAPI for inbound distribution of contact person addresses
  'ADRMAS01' BAPI for inbound distribution of organizational addresses
  'ADRMAS02' BAPI for inbound distribution of organizational addresses
  'ALEAUD01' Confirmations of the processing status of inbound IDocs
  'ALEREQ01' General request - Basis IDoc type
  'ARTMAS01' Create and Change Material Master Data (Retail)
  'ARTMAS02' Create and Change Material Master Data (Retail)
  'ASSET_POSTCAP_POST01' Post post-capitalization
  'ASSET_RETIREMENT_POST01' Post asset retirement
  'ASSMOD01' Assortment (manual modules)
  'ASSORTMENT01' Maintenance of assortments
  'ATT_ABS01' BAPI ext. Att./absence: Insert in IFT (w/o acct assgnmnt)
  'ATT_ABS_WITH_ACTIVITY01' Ext. Att./absence (PTManagerExtAttAbs)
  'ATT_ABS_WITH_COST01' BAPI ext. Att./absence: Insert in IFT (acct assgnmnt)
  'BATCH5' Batch in CC5
  'BATMAS01' Replicate batch
  'BATMAS02' Replicate Batch
  'BBPCO01'
  'BBPIV01' BBP Create Invoice
  'BBP_IV_T01' BBP Create Invoice
  'BENEFIT1' HR: Benefits
  'BETMAS01' Site master data distribution ALE
  'BLAORD01' Purchasing contracts
  'BLAORD02' Purchasing contracts
  'BLAORD03' Purchasing contracts
  'BLAREL01' Contract release order statistics
  'BLAREL02' Contract release order statistics
  'BMUMAS01' Replicate batch-specific material quantity units
  'BOMDOC01' Master BOM - document
  'BOMDOC02' Master BOM - document
  'BOMMAT01' Master BOM - material
  'BOMMAT02' Master BOM - material (2)
  'BOMMAT03' Material BOM (from 4.6B)
  'BOMORD01' Master BOM - sales order
  'BTC_ID01' Process order with components
  'BTC_ID02' Production requirement from superior system
  'BTC_ID03' Production commitment to superior system
  'CAP_ACTIN01' Activity input planning: Posting
  'CAP_ACTIN02' Activity Input Planning: Posting
  'CAP_ACTOUT01' Activity/Price planning: Posting
  'CAP_ACTOUT02' Activity/Price Planning: Posting
  'CAP_KEYFIG01' Stat. Key Figure Planning: Postings
  'CAP_PRIMCOST01' Primary Cost Planning: Postings
  'CATS_CHANGE01' CATS: Change data records
  'CATS_DELETE01' CATS: Delete data records
  'CATS_INSERT01' CATS: Insert data records
  'CBPRCP01' Rough-cut planning profile
  'CCLONE01' Duplicate company address in another system
  'CHRMAS01' Master characteristic basic data
  'CHRMAS02' Master attribute with object dependencies
  'CLFMAS01' Master object classification
  'CLONE02'
  'CLSMAS01' Master class
  'CLSMAS02' Distribution of classes with object dependencies
  'CLSMAS03' Classes with long texts and document links
  'CMREQU01' TR-CM: Invitation to TR-CM system to send data
  'CMSEND01' TR/CM-IDOC: Transfer of TR-CM data
  'CNPMAS01' Master configuration profile
  'CNPMAS02' Master configuration profile
  'COABCM01' Replicate individual business process (ALE)
  'COABC_BUSPROCSTRUCTURE_CREAT01' Create process struct.(BusProcStructureCO)
  'COACOR01' Core master activity type
  'COACTV01' IDoc for cost center/activity type
  'COAMAS01' Master activity type
  'COCOKA01' Control segment CO object/cost element
  'CODCMT01' IDoc for a CO document
  'COELEM01' Cost elements: Master data distribution
  'COGRP01' IDoc for CO groups (e.g. cost center groups)
  'CONDA201' ALE Customizing Distribution Add-On
  'CONDAT01' Change to customizing data
  'CONDAT02' Distribution of Control Data
  'COND_A01' Interchange of conditions: Master data for price determ.
  'COND_A02' ALE condition records
  'CONF11' Confirmations in CC1
  'CONF21' Confirmations in KK2, time events
  'CONF31' Confirmations in KK3, time events
  'CONF32' Confirmations in KK3, wage slips
  'CONF41' Confirmations in KK4, time events
  'CONF42' Confirmations in KK4, wage slips
  'CONF51' CC5 confirmations run schedules
  'CONF_ACT1001' Enter activity confirmation
  'COPAGN01' CO-PA entry
  'COPCPA01' Transfer product costing CO-PC -> CO-PA
  'COPCPA02' Copy product cost estimate
  'COSCOR01' Core master cost center
  'COSMAS01' Master cost center
  'COTOTL01' IDoc for CO totals records
  'CO_ABC_BPROC_CREATE01' Create one or more business processes
  'CO_ABC_BPROC_SETSTRUC01' Enter template in business process master data
  'CRECOR01' Vendor master data distribution ALE Core master data
  'CREMAS01' Vendor master data distribution ALE
  'CREMAS02' Vendor master data distribution ALE
  'CREMAS03' Vendor master data distribution
  'CRESTA01' Copy credit status (DebtorCreditAccount)
  'DANGEROUSGOOD01' Dangerous goods: Save replicated instances
  'DD01L_01' Domains
  'DD03L_01' Table Fields
  'DD04L_01' Data elements
  'DEBCOR01' Core master - customer
  'DEBMAS01' Customer master
  'DEBMAS02' Customer master
  'DEBMAS03' Customer master
  'DEBMAS04' Customer master data distribution
  'DELFOR01' Delivery schedule/JIT schedule
  'DELVRY01' Delivery interface
  'DELVRY02' Delivery interface with dangerous goods data
  'DELVRY03' Delivery interface
  'DEPNET' Master data of dependency net
  'DESADV01' External service agent processing (notifications)
  'DES_ID01' Shipping notification
  'DIFFE2' Differences in KK2
  'DIFFE3' Differences in KK3
  'DIFFE4' Differences in KK4
  'DISTU2' Reasons for problems KK2
  'DOCMAS01' Master document
  'DOCMAS02' Document 02
  'DOCMAS03' Document
  'DOCMAS04' Documents
  'DOCUMENT_LOAD01' Load document data (Document transfer)
  'DOLMAS01' Document-object links
  'DWLOAD' Download transceiver configuration
  'ECMMAS01' IDoc structure for ECM
  'ECMREV01' IDOC structure for revision level
  'EKSEKS01' Purchasing document data for Purchasing Info System
  'EXCHANGE_RATE01' Replication of currency rates
  'EXPINV01' Export Invoice IDOC (E.F.I.)
  'EXPINV02' Foreign Trade - Billing Doc. IDoc
  'EXPINV03' Foreign trade - billing doc. IDoc
  'EXTWA1' External wage types
  'FIDCCH01' IDoc for FI document changes (dunning block)
  'FIDCCP01' IDoc: Complete FI document
  'FIDCMT01' IDoc for FI documents
  'FINANCIALPRODUCT_CREATE01' Create security
  'FINANCIALTRANSACTION_CREATE01' Create financial transaction
  'FINSTA01' Account Statement, Lockbox, Polling Info
  'FIPARQ01' IDoc for FI payment data
  'FIXEDASSET_CHANGE01' Changes an asset
  'FIXEDASSET_CHANGE02' Changes an asset
  'FIXEDASSET_CREATE01' Creates an asset
  'FIXEDASSET_CREATE02' Creates an asset
  'FIXEDASSET_CREATEFROMDATA101' Creates an Asset
  'FIXEDASSET_CREATEINCLVALUES01' BAPI for Legacy Data Transfer
  'FTDABA01' Foreign Trade Data Service Basic Data
  'FTDACU01' Foreign Trade Data Service Customs Data
  'FTRCON01' Confirm transaction
  'GLCORE01' Documentation deleted
  'GLDCMT01' IDoc type for GLX rollups
  'GLMAST01' Master data G/L accounts: Max. IDoc
  'GSVERF01' IDoc input credit memo procedure
  'GSVERF02' Cred. memo procedure
  'HRCC1DNATTAB01' CC1: Download permitted att./absence reasons
  'HRCC1DNBALAN01' CC1: Download Employee Balances
  'HRCC1DNCOSTC01' CC1: Download Cost Centers
  'HRCC1DNEXTWT01' CC1: Download permitted external wage types
  'HRCC1DNINORD01' CC1: Download Internal Orders
  'HRCC1DNOBJID01' CC1: Download Objects (such as Positions)
  'HRCC1DNPERSO01' CC1: Download HR Mini-Master
  'HRCC1DNTEVGR01' CC1: Download Time Event Type Groups
  'HRCC1DNWBSEL01' CC1: Download Work Breakdown Structure Element
  'HRCC1REQUPEXTWT01' CC1: Upload Request for Employee Expenditures
  'HRCC1REQUPTEVEN01' CC1: Upload Request for Time Events
  'HRCC1UPEXTWT01' CC1: Upload external wage types
  'HRCC1UPTEVEN01' CC1: Upload time events
  'HRCNF01' Transfer confirmations (TimeMgtConfirmation)
  'HRKK1ABSR' HR TIM CC1: Allowed Attedance/Absence Reasons
  'HRKK1EWUP' HR TIM CC1: External Wage Types Confirmation
  'HRKK1EXWT' HR TIM CC1: Permitted External Wage Types
  'HRKK1PERS' HR TIM KK1: HR Mini Master for Time Recording
  'HRKK1TBAL' HR TIM CC1: Employee Time Balances
  'HRKK1TEUP' HR TIM KK1: Confirmation of person time events
  'HRKK1TEVT' HR TIM CC1: Permitted Time Event Types
  'HRKK1WRKC' HR TIM CC1: Permitted Work Centers
  'HRMASTER01' Replicate (HRMasterDataReplica)
  'HRMASTER02' Replicate (HRMasterDataReplica)
  'HRMD_A01' HR: Master and organizational data (application system)
  'HRMD_A02' HR: Master and organizational data (application system)
  'HRMD_A03' HR: Master and organizational data (application system)
  'HRMD_A04' HR: Master and organizational data (application system)
  'HRMD_B01' HR: Master and organizational data (basis system)
  'HRMD_B02' HR: Master and organizational data (basis system)
  'HROT558D' HR: Outsourcing US: Inbound IDOC Table T558A (Test)
  'HROTIN' HR: Outsourcing: Inbound Payroll Results
  'HROTUSTR' HR-PY-US : Tax Remittance Outsourcing
  'HROT_CAM' HR: Canadian Master Data Payroll Outsourcing
  'HROT_CAP' Payroll Outsourcing - Canada
  'HROT_USM' HR: US Master Data Payroll Outsourcing
  'HROT_USP' HR: Generic US Payroll Outsourcing
  'HRPAYP01' HR - Transfer FI/CO
  'HRPLL40' Logistics confirmations for Human Resource Management
  'HRSM_A01' HR: HR data for personnel actions
  'HRSM_B01' HR: Confirmation for personnel actions
  'HRTRPR01' Transfer TRV-PAY(PayrollTravelExpenses)
  'HRTRVL01' HR-TRV: Transfer travel expenses FI/CO
  'HRTRVL03' HR-TRV: Transfer Trip Costs to Payroll
  'HR_INBND' HR: OUTSOURCING: Inbound IDoc Tables
  'IDCREF01' Reference message as logical grouping for electron.signature
  'IMATIS01' Unplanned material issues
  'IMEASR01' Measurement reading IDOC
  'IMPINV01' Import Basis IDoc (I.B.I.)
  'IM_PROGDEF_SAVEREPLICA01' Method 'SaveReplica' for ExpenditureProgDef
  'INFREC01' Purchasing info record
  'INOTIF01' Notification IDOC
  'INTERNAL_ORDER01' Replicate individual internal order (ALE)
  'INTERNAL_ORDER_CREATE01' Create internal order from transferred data
  'INTUPD01' Notification status update IDoc
  'INVCON01' Stock change data for inventory controlling
  'INVOIC01' Invoice/Billing document
  'INVOIC02' Invoice/Billing document
  'INV_ID01' Invoice
  'IOAUPD01' Work order assignments IDOC
  'IORDER01' SM/PM order IDoc
  'IORUPD01' Order status update IDoc
  'IWKCEN01' Work Center IDOC
  'KANBAN01' Kanban Call for Kanban With SD Delivery
  'KNOMAS01' Master object dependencies basic data
  'LABELS00' ISR labeling: label
  'LIKOND01' Listing conditions
  'LIS_EXTR' LIS inbound interface for external data
  'LOCAT5' Location in KK5
  'LOIBOM01' Master bill of material
  'LOICAL01' Master calendar
  'LOIMSO01' Storage location stock material
  'LOINUM01' Number of IDocs sent
  'LOIPGR01' IDOC for product group
  'LOIPLO01' Master planned order
  'LOIPRO01' Master production order
  'LOIRNH01' Master hierarchy/networks
  'LOIROU01' Master routing
  'LOIROU02' Master routing
  'LOIRSH01' Master run schedule header
  'LOISTD01' Master requirements/stock list
  'LOITMX01' Transition matrix
  'LOIWCS01' Master work center
  'LOIWCS02' Master work center IDoc
  'LPIEQU01' IDoc: quota arrangement
  'LPIPCM01' Production campaign
  'MALFK5' CC5 reasons for scrap
  'MANAGEREXTPAYROLL_INSERTLEGA01' Transfer payroll account
  'MANAGEREXTPAYROLL_INSERTOUT01' Update of a payroll result using an outsourcer
  'MATCOR01' Core master material
  'MATMAS01' Material Master
  'MATMAS02' Material Master
  'MATMAS03' Material Master
  'MATMAS_BAPI01' Create and Change Material Master Data
  'MATQM01' Replication of QM Inspection Setup
  'MBGMCA01' Reverse goods movements with MB_CANCEL_GOODS_MOVEMENT
  'MBGMCR01' BAPI Posting of goods mvts with MB_CREATE_GOODS_MOVEMENT
  'MBGMCR02' Post goods movements with MB_CREATE_GOODS_MOVEMENT
  'MC1_01' Condition tables
  'MMADDI01' Create and change additionals (retail)
  'MRESCR01' Create reservation
  'OPERA2' Operations in KK2
  'OPERA3' Processes in KK3
  'OPERA4' Operations in KK4
  'OPERS3' Operation status in KK3
  'OPERS4' Operation status in KK4
  'ORDERS01' Purchasing/Sales
  'ORDERS02' Purchasing/Sales
  'ORDERS03' Purchasing/Sales
  'ORDERS04' Purchasing/Sales
  'ORDERS05' Purchasing/Sales
  'ORDLGT01' Purchase order/order with Orders Light
  'ORD_ID01' Req.for quot./quotation/purchase order/order change
  'ORGMASTER01' BAPI for replication of HR organizational data
  'OSTAT2' Process status CC2
  'PALMAT01' Plant assignment to material BOM
  'PCHEAD01' Replicate basic and structure data of a product catalog
  'PCITEMS01' Replicate item data of a product catalog
  'PDTCO_POSTPRIMARY01' Transfer of Planning Data: Post Primary Costs
  'PERSO1' Personnel master records in CC1
  'PERSO2' Personnel master in CC2
  'PERSO3' Personnel master in CC3
  'PERSO4' Personnel master in CC4
  'PEXR2001' Payment/payment advice note/credit memo/debit advice
  'PEXR2002' Payment/payment advice note/credit memo/debit advice
  'PIECEOFEQUIPMENT_DISMANTLEAT01' Dismantle equipment at functional location
  'PIECEOFEQUIPMENT_INSTALLATFU01' Install equipment at functional location
  'PKHD5' CC5 kanban control cycles
  'PKPS5' CC5 Kanban container
  'PKST5' CC5 status for kanban container
  'PLANDATATRANSFERCO_POSTACTIO01' Planning Data Transfer: Post Activity Planning
  'PLANDATATRANSFERCO_POSTACTIV01' Planning Data Transfer: Post Activity Input
  'PLANDATATRANSFERCO_POSTKEYFI01' Transfer of Planning Data: Post Stat. Key Figures
  'PLANT3' Plants in CC3
  'PLANT4' Plants in CC4
  'PORDCR01' Create purchase order
  'PORDCR03' Create purchase order
  'PORDCR04' Create purchase order
  'PPCC2PRETEVENT01' Transfer time event confirmations from PDC system
  'PPCC2PRETTICKET01' Transfer time ticket confirmations from PDC system
  'PPCC2RECORDER01' Send production orders to PDC system
  'PPCC2RECWORKCENTER01' Send work centers to PDC system
  'PPCC2REQCONF01' Send upload request to PDC system
  'PRCDOC01' Replicate PCA line items (ALE)
  'PRCDOCD01' Delete profit center documents (ALE)
  'PRCDOCP01' Replicate EC-PCA plan line items (ALE)
  'PRCDOCR01' Reversal of existing document line items (ALE)
  'PRCMAS01' Profit center master record
  'PRCMAS02' Profit Center master record (with company code assignment)
  'PRDCAT01' Product catalog
  'PRDPOS01' Product catalog item
  'PREQCR01' Create purchase requisition
  'PREQDL01' Delete/close purchase requisition
  'PRICAT01' Price/sales catalog
  'PRICECATALOGUE01' Store price catalog instance
  'PROACT01' Transfer of stock and sales data
  'PROFITCENTER_CHANGE01' Change Profit Center
  'PROFITCENTER_CREATE01' Create Profit Center
  'PROJECT01' Replicate entire work breakdown structure (ALE)
  'PTOVERVIEW01' Insert/Delete employee time overviews
  'QALITY01' Quality data and sending of certificate reference
  'RCYINF01' Information about IDocs and their application documents
  'RCYSYS01' Information about the reset system
  'REMURQSLIST_CHANGE01' Agency Business: Change Invoice List Documents BAPI
  'REMURQSLIST_CREATE_CBD01' Create from posting list (invoice list)
  'REMURQSLIST_CREATE_REMU01' Create from shipping document (invoice list)
  'REMURQSLIST_CREATE_SETT01' Create from payment document (invoice list)
  'REMURQSLIST_RELEASE01' Release to Accounting (Invoice List)
  'REM_SPEC01' Insert Ext. EE Remun. Info in Table (w/o Account Assignment)
  'REM_SPEC_WITH_ACTIVITY01' Insert employee remuneration info (PTMgrExtRemunSpec)
  'REM_SPEC_WITH_COST01' Insert External EE Remun. Info in Table (w/ Cost Assignment)
  'REQUI1' Confirmation request in CC1
  'REQUI2' Confirmation request in CC2
  'REQUI3' Confirmation request in CC2
  'REQUI4' Confirmation request in CC4
  'REQUI5' Confirmation request in CC5
  'RESOURCECO01' Replicate individual CO resources (ALE)
  'RPLMAS01' Create and change replenishment master data
  'RSINFO' Info IDoc
  'RSREQUST' Data request to the source system
  'RSSEND' Data transfer from the source system (template)
  'SAPRDI01' SAPscript Raw Data Interface IDOC Type
  'SAPRDI02' SAPscript Raw Data Interface IDOC Type
  'SCERTKB' Knowledge base for configurator
  'SDPAID01' Shipping element data confirmation to customer delivery
  'SDPIID01' Picking data confirmation to customer delivery
  'SDPIOD01' Picking notification to subsystem:
  'SERDAT01' Control data serialization
  'SERVICENOTIFICATION_CREATEFR01' Create service notification
  'SETTRQSLIST_CHANGE01' Agency Business: Change Settlement Request List BAPI
  'SETTRQSLIST_CREATE01' Agency Business: Create Settlement Request List BAPI
  'SETTRQSLIST_RELEASE01' Release to Accounting (SettlementRequstList)
  'SFADCH01' SFA download salesorder (change pointers)
  'SFADDE01' SFA Download Debitor
  'SFADOR01' SFA Download Salesorder
  'SFADPSA01' BAPI Partner Sales Activity Receiver
  'SFAMAT01' SFA MATERIAL DOWNLOAD IDOC
  'SHPMNT01' Shipment
  'SHPMNT02' Shipment
  'SHPMNT03' Shipment
  'SHPMNT04' Transport
  'SHP_IBDLV_CONFIRM_DECENTRAL01' BAPI Confirmation(InboundDelivery)
  'SHP_IBDLV_SAVE_REPLICA01' BAPI Function Module for Replication of Inbound Deliveries
  'SHP_OBDLV_CONFIRM_DECENTRAL01' BAPI Verification (OutboundDelivery)
  'SHP_OBDLV_CONFIRM_DECENTRAL02' BAPI Verification (OutboundDelivery)
  'SHP_OBDLV_SAVE_REPLICA01' BAPI Function Module for Replication of Outbound Deliveries
  'SINGLEREMUNRQS_CANCEL01' Agency Business: Cancel Vendor Billing Documents BAPI
  'SINGLEREMUNRQS_CHANGE01' Agency Business: Change Vendor Billing Documents BAPI
  'SINGLEREMUNRQS_CREATE01' Agency Business: Generate Vendor Billing Documents BAPI
  'SINGLEREMUNRQS_RELEASE01' Release to Accounting (Vendor Billing Documents)
  'SINGLESETTRQS_CANCEL01' Agency Business: BAPI Cancel Single Settlement Requests
  'SINGLESETTRQS_CHANGE01' Agency Business: BAPI Change Single Settlement Requests
  'SINGLESETTRQS_CREATE01' Agency Business: Create Single Settlement Request BAPI
  'SINGLESETTRQS_RELEASE01' Release Accounting (SingleSettlementReqs)
  'SISCSO01' VIS - Sales order
  'SISDEL01' VIS - delivery
  'SISINV01' VIS - billing document
  'SOPGEN01' General info structure distribution
  'SRCLST01' Source List
  'SRVMAS01' Service master record with texts
  'STTMAT01' STTMAT : Material variants
  'SYIDOC01' CA-EDI: Transport of IDoc types
  'SYNCHRON' Dummy IDoc type for synchronous communication
  'SYPART01' Transfer from partner profiles
  'SYRECD01' CA-EDI: Transport of IDoc record types
  'SYRECD02' IDoc interface: Transport IDoc record types
  'SYSTAT01' CA-EDI: Transfer from status records
  'T006_01' Units of measurement
  'TCURC_01' Currency Codes
  'TCURR_01' Exchange rates
  'TPSDLR01' Selection via variant from external system
  'TPSDLS01' Dispatch of delivery documents to shipping planning system
  'TPSLOC01' Dispatch of location master data to transport planning syst.
  'TPSSHT01' Dispatch of planned shipments from transport planning system
  'TXTRAW01' Transfer free text to SAPoffice format 'RAW'
  'TXTRAW02' Transfer free text to SAPoffice format 'RAW'
  'UNIMA2' Alternative units of measure with acquisition of materials
  'UNIT2' Units in CC2
  'UNIT3' Units in CC3
  'UNIT4' Units in CC4
  'UPLOAD' Configuration transceiver for upload
  'USERCLONE01' Create user with template in another system
  'USERCLONE02' Create user with template in another system
  'VENDCBDLIST_CHANGE01' Agency Business: Change Posting Lists BAPI
  'VENDCBDLIST_CREATE01' Agency Business: Generate Posting Lists BAPI
  'VENDCBDLIST_RELEASE01' Agency Business: BAPI Release Posting Lists Document to FI
  'VFNMAS01' Master Variant Function
  'VTAMAS01' Master variants table
  'VTMMAS01' Master maintenance table contents
  'WALNOT01' Allocation: Allocation table notification
  'WALREQ01' Allocation: Report requested quantities
  'WBBDLD01' Assortment list: Material data
  'WBBDLD02' Assortment list: material data (Rel. 4.0)
  'WBBDLD03' Assortment lists: Material data (Rel. 99A)
  'WGSREQ01' Order receipt IS-R
  'WGSREQ02' Store order IDoc (inc. condition segment)
  'WMBIID01' Block Storage Bins
  'WMCAID01' Reversal/Reversal request for transfer order
  'WMERCAT01' Merchandise Category and associated data IDoc
  'WMINID01' Information text for link to subsystems
  'WMIVID01' Enter count results
  'WMMBID01' Goods movements for mobile data entry
  'WMMBID02' Stock movements from ext. systems
  'WMPHID01' Pick HU (Handling Unit)
  'WMRRID01' Release reference number
  'WMSUID01' Move storage unit
  'WMTCID01' Confirm transfer order
  'WMTCID02' Confirm transfer order
  'WMTCID03' Confirm TO
  'WMTOID01' Transfer order
  'WMTOID02' Send pick HU
  'WMTRID01' Transfer requirement
  'WORKC2' Workcenters in CC2
  'WORKC3' Workcenters in CC3
  'WORKC4' Workcenters in CC4
  'WPDBBY01' POS outbound: bonus buy conditions
  'WPDCUR01' POS interface: Download exchange rates
  'WPDNAC01' POS interface: Download products
  'WPDSET01' POS interface: Download set assignments
  'WPDTAX01' POS interface: Download tax rates
  'WPDWGR01' POS interface: Download material group master
  'WPUBON01' POS interface: Upload sales docs (trnsctns), non-aggregated
  'WPUERR01' POS interface: Upload messages SRS/POS/SCS
  'WPUFIB01' POS interface: Upload Fin.Acc. interface SRS/POS
  'WPUKSR01' POS Interface: Inbound processing cashier data for POS stats
  'WPUTAB01' POS interface: Upload day-end closing POS
  'WPUUMS01' POS interface: Upload sales data (compressed)
  'WPUWBW01' POS interface: Upload goods movements
  'WP_EAN01' POS interface: Upload/Download EAN assignments
  'WP_PER01' POS interface: Upload/Download person data
  'WP_PLU01' POS interface: Upload/Download article master
  'WP_PLU02' POS interface: material and condition (inbound and outb.)
  'WTADDI01' Additionals
  'WVINVE01' Store phy.inv.: phy.inv. docs outbound; count data inbound
  'WVINVE02' Store phy.inv.: phy.inv. docs outbound; count data inbound
  'W_WGRP01' Distribution of material groups
  'ZAK_ID01'
  'ZGMATD01' MATERIAL DETERMINATION CUSTOM IDOC FOR PCAT INTERFACE LOAD
  'ZIFTSTA0' GBPI : Transport Status IDoc type for IFTSTAT message
  'ZIFTSTA00' GBPI: Transport Status Container IDoc type for IFTSTAT
  'ZKBKOMAT' PROLOG
  'ZKBLGORT' storage location
  'ZKBMARKN' Reference number / PROLOG
  'ZKMTMAT1' IDOC for ZKMT, Configurable Matl. Characteristic Assignment
  'ZMATMAS' GBPI Material master IDoc for MM Data interface
  'ZMATMAS1' GBPI Material master IDoc type (succ.)
  'ZOR_ID01'
  'ZPPKBF' Production Confirmations - PDC Inbound
  'ZPPK_BF' Production Confirmations - PDC Inbound
  'ZSPA084' Basis IDoc type ür PKACLI001
  'ZSTE087' Basis IDoc type ür TKWCLI020

• CIMTYP : Extension (defined by customer)

  Use
  In the IDoc control record, the fields IDOCTYP and CIMTYP serve as a unique ID for the IDoc type: they specify the syntax, i.e. the segment sequence.
  When data is transferred between two systems, IDOCTYP must always be maintained, as the field contains the basic type
  ; CIMTYP contains the extension, and must therefore be maintained if an extension is used.

  Values
  
  '/GIL/EPG_ORDERS05' EDI Preprocessor: Extension of the ORDERS05 basic type
  '/GIL/EPG_POCHANGE' EDI Preprocessor: PO Change
  'ZBOMMAT1' PCat: Master BOM - Material
  'ZCUSTCON' Global Customer Conversions
  'ZDEBMAS1' Extension to DEBMAS01
  'ZDEBMAS3' Customer Master Global Interface
  'ZDELVRY1' GBPI Delivery Interface (Extension type)
  'ZDELVRY2' Successor of ZDELVRY1
  'ZDESADV1' BRAUN EDI DESADV01 Extensions Type
  'ZINVOIC1' BRAUN EDI Z1INVK1 Extension Type
  'ZKBCREM' Extension for CREMAS03
  'ZKBMATM' Extension for MATMAS03 MASCON
  'ZLOIROU1' Extended LOIROU01 with additional PLKO and PLPO fields
  'ZMATMAS3' Extended MATMAS03 with additional MARA fields
  'ZMATMAS4' Material Master (extended) v4
  'ZORDERS1' IDOC extension for Incoming 850 Orders
  'ZORDERS2' GBPI non PreProcessor ORDERS IDoc Typ
  'ZPEXR201' BRAUN EDI PEXR2001 Extension type
  'ZWMMBID1' GBPI Stock movements IDoc type

• MESTYP : Message type

  Use
  This field must always be maintained, in order to identify the message. Further distinctions can be applied to messages via the fields MESCOD and MESFCT. The three fields belong to the key fields of the partner profiles, which are used to specify the port and the IDoc type in outbound processing.

  Values
  
  '/GIL/EPG_ALE_TO_PP' ALE to PreProcessor bridge message
  '/GIL/IMG_WIC_IR' Generic WIC IR Message
  '/GIL/IMG_WIC_IR_BX' Benelux WIC IR Message
  '/GIL/IMG_WIC_IR_GB' UK WIC IR Message
  '/GIL/IMG_WIC_IR_IB' Iberia WIC IR Message
  '/GIL/IMG_WIC_IR_IN' India WIC IR Message
  '/GIL/IMG_WIC_IR_NN' Nordic WIC IR Message
  '/GIL/IMG_WIC_IR_TR' Turkey WIC IR Message
  '/GIL/OMG_GGUK_WIC_ACC_OS_5' UK Bifurcation: Acceptance of Offer to Sell - step 5 of 7
  '/GIL/OMG_GUK_WIC_ACC_OB_3' UK Bifurcation: Acceptance of Offer to Buy - step 3 of 7
  '/GIL/OMG_GUK_WIC_RCMD_SHP_1' UK Bifurcation: Recommended Shipment - step 1 of 7
  '/GIL/OMG_WIC_GGUK_ACK_AOS_7' UK Bifurcation: Acknowledge Accept. Sell - step 7 of 7
  '/GIL/OMG_WIC_GGUK_OFFER_SELL_4' UK Bifurcation: Offer to Sell - step 4 of 7
  '/GIL/OMG_WIC_GUK_ACK_AOB_6' UK Bifurcation: Acknowledge Accept. Buy - step 6 of 7
  '/GIL/OMG_WIC_GUK_OFFER_BUY_2' UK Bifurcation: Offer to Buy - step 2 of 7
  '/GIL/OMK_IB_CUST_CHG' Track Cust changes for Iberia Disc/List Interface
  '/GIL/OMK_IB_CUS_HIER_CHG' Track Cust Hierarchy changes for Iberia Disc/List Interface
  '/GIL/OMK_IB_MAT_CHG' Track Material changes for Iberia Disc/List Interface
  '/GIL/OMK_PRICAT' Outbound price list interface
  '/GIL/SPG_ORDCHG_DE01' APO SNP TLB Purchase Order Change - DE01
  '/GIL/SPG_ORDERS_DE01' APO SNP TLB Purchase/Sales Orders - DE01
  'ABSEN1' Attendance/Absence in CC1
  'ACCONF' Confirmation of IDoc processing from the application
  'ACCSTA' Returnable packaging account statement transmission
  'ACC_ACT_ALLOC' Accounting: Post activity allocation
  'ACC_ASSET_TRANSFER' Accounting: Post acquisition from transfer
  'ACC_ASSET_TRANS_ACQ_POST' Accounting: Post acquisition from transfer
  'ACC_BILLING' Accounting: Post invoice (OAG: LOAD RECEIVABLE)
  'ACC_DOCUMENT' Accounting: Posting
  'ACC_EMPLOYEE_EXP' FI/CO: HR posting GL(AcctngEmplyeeExpnses)
  'ACC_EMPLOYEE_PAY' FI/CO: HR posting AP(AcctngEmplyeePaybles)
  'ACC_EMPLOYEE_REC' FI/CO: HR posting AR(AcctngEmplyeeRcvbles)
  'ACC_GL_POSTING' Accounting: General G/L account posting
  'ACC_GOODS_MOVEMENT' Accounting: Post goods movement (OAG: POST JOURNAL)
  'ACC_INVOICE_RECEIPT' Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
  'ACC_PRIM_COSTS' Accounting: Post primary costs
  'ACC_PURCHASE_ORDER' Accounting: Post purchase order
  'ACC_PURCHASE_REQUI' Accounting: Post purchase requisition
  'ACC_REVENUES' Accounting: Post revenues
  'ACC_SALES_ORDER' Accounting: Post sales order
  'ACC_SALES_QUOTA' Accounting: Post customer quotation
  'ACC_SENDER_ACTIVITIES' Accounting: Post Sender Activities
  'ACC_STAT_KEY_FIG' Accounting: Post statistical key figures
  'ACC_TRAVEL' Accounting: Post trip
  'ACLPAY' Accounting: Inbound invoice
  'ACLREC' Accounting: Billing document
  'ACPJMM' Posting in accounting from materials management
  'ACTIV3' Units in CC3
  'ACTIV4' Units in CC4
  'ADR2MAS' BAPI for inbound distribution of private addresses
  'ADR3MAS' BAPI for inbound distribution of contact person addresses
  'ADRMAS' BAPI for inbound distribution of private addresses
  'ALEAUD' Confirmations of the processing status of inbound IDocs
  'ALEREQ' General request message
  'APERAK'
  'ARTMAS' Create and change material master data (retail)
  'ASSET_POSTCAP_POST' Post post-capitalization
  'ASSET_RETIREMENT_POST' Post asset retirement
  'ASSMOD' Assortments
  'ASSORTMENT' Maintenance of assortments
  'ATT_ABS' BAPI ext. Att./absence: Insert in IFT (w/o acct assgnmnt)
  'ATT_ABS_WITH_ACTIVITY' Ext. Att./absence (PTManagerExtAttAbs)
  'ATT_ABS_WITH_COST' BAPI ext. Att./absence: Insert in IFT (acct assgnmnt)
  'BATCH5' CC5 Batch
  'BATMAS' Replicate batch
  'BBPCO' BBP: commitment posting
  'BBPIV' BBP invoice
  'BBP_IV_T' BBP Create Invoice TEMPLATE
  'BENREP' Benefits report
  'BETMAS' Plant master
  'BLAOCH' Purchasing contract change
  'BLAORD' Purchasing contracts
  'BLAREL' Release order documentation for distributed contracts
  'BMUMAS' Replicate batch-specific material quantity units
  'BOMDOC' BOMs: Document structure
  'BOMMAT' BOMs: Material BOM
  'BOMORD' BOMs: sales order BOM
  'CAP_ACTIN' Activity input planning: Posting
  'CAP_ACTOUT' Activity/Price planning: Posting
  'CAP_KEYFIG' Stat. Key Figure Planning: Postings
  'CAP_PRIMCOST' Primary Cost Planning: Postings
  'CARNOT' Delivery: Shipping notification
  'CATS_CHANGE' CATS: Change data records
  'CATS_DELETE' CATS: Delete data records
  'CATS_INSERT' CATS: Insert data records
  'CBPRCP' Rough-cut planning profile
  'CCLONE' Duplicate company address in another system
  'CHRMAS' Class system: Characteristics master
  'CIFCUS' APO-CIF: change documents for locations (customer)
  'CIFMAT' APO-CIF: change documents for products
  'CIFPLT' APO-CIF: change documents for locations (plant)
  'CIFPPM' APO-CIF: change documents for PPMs
  'CIFRES' APO-CIF: change documents for resources (not active)
  'CIFSRC' APO-CIF: change documents for sources
  'CIFVEN' APO-CIF: change documents for locations (vendor)
  'CLFMAS' Class system: Classification master
  'CLSMAS' Class system: Classes master
  'CMREQU' Invite TR-CM subsystem to send TR-CM data
  'CMSEND' TR-CM subsystem sends TR-CM data to central TR-CM
  'CNPMAS' Configuration profile
  'COABCM' Replicate individual business process (ALE)
  'COABC_BUSPROCSTRUCTURE_CREATE' Create process struct.(BusProcStructureCO)
  'COACOR' Core master activity type
  'COACSU' Commercial Summary
  'COACTV' IDoc for cost center/activity type
  'COAFET' Request activity type
  'COAMAS' Master activity type
  'COCOKA' Control segment CO object/cost element
  'CODCMT' IDoc for a CO document
  'COELEM' Cost element master data
  'COGRP1' Cost center groups
  'COGRP2' Cost element groups
  'COGRP5' Activity type groups
  'COGRP6' Profit center groups
  'COGRP9' Account groups (Profit Center Accounting)
  'CONDA2' ALE Customizing data synchronization
  'CONDAT' Obsolete: control data (use CONDA2!)
  'CONDBI' Condition index for document changes
  'COND_A' Conditions: master data for price determination
  'CONF11' Confirmations in CC1
  'CONF21' Confirmations in CC2, time events
  'CONF31' Confirmations in CC3, time events
  'CONF32' Confirmations in CC3, wage slips
  'CONF41' Confirmations in CC4, time events
  'CONF42' Confirmations in CC4, wage slips
  'CONF51' Confirmations in CC5, run schedules
  'CONFIG' Configuration for transceiver
  'CONF_ACT10' Enter activity confirmation
  'COPAGN' Profitability analysis
  'COPCPA' Costing data CO-PC -> CO-PA
  'COSCOR' Core master cost center
  'COSFET' Request cost center
  'COSMAS' Master cost center
  'COTOTL' IDoc for CO totals records
  'CO_ABC_BPROC_CREATE' Create one or more business processes
  'CO_ABC_BPROC_SETSTRUC' Enter template in business process master data
  'CPS001' Profitability analysis
  'CREADV' Credit memo display
  'CRECOR' Core vendor master data distribution
  'CREFET' Get vendor data
  'CREMAS' Vendor master data distribution
  'CRESTA' Copy credit status (DebtorCreditAccount)
  'CSCPBOM' Bill of Material for SDM
  'CSCPMAT' Master Material for SDM
  'CSCPNUM' Number Idoc for SDM Engine
  'CSCPROU' Routings for SDM
  'CSCPWCS' Working Centers for SDM
  'CURR_A' Exchange rates
  'DANGEROUSGOOD' Dangerous goods: Save replicated instances
  'DD01_A' Domains
  'DD03_A' Table Fields
  'DD04_A' Data elements
  'DEBADV' Debit display
  'DEBCOR' Core customer master data distribution
  'DEBFET' Request customer master
  'DEBMAS' Customer master data distribution
  'DELFOR' Delivery schedule for component supplier
  'DELINS' Delivery schedule/JIT schedule
  'DELJIT' JIT delivery schedule for component supplier
  'DELORD' Delivery order
  'DELPKB' KANBAN call
  'DEPNET' Dependency net
  'DESADT' Shipping notification
  'DESADV' Delivery: Shipping notification
  'DIFFE2' Differences in CC2
  'DIFFE3' Differences in CC3
  'DIFFE4' Differences in CC4
  'DIRDEB' Preauthorized withdrawal
  'DISTU2' Reasons for problems CC2
  'DOCMAS' Master document
  'DOCUMENT_LOAD' Load document data (data transfer)
  'DOLMAS' Document-object links
  'DWLOAD' Download transceiver configuration
  'ECMMAS' Engineering Change Management
  'ECMREV' Revision level
  'EDLNOT' EDL delivery notes
  'EKSEKS' Purchasing document for Purchasing Info system
  'EUPEXR' Reference message for electr. signature (for ext. payments)
  'EXCHANGE_RATE' Replication of currency rates
  'EXPINV' Export invoice
  'EXTWA1' External wage types
  'FIDCC1' Send entire FI documents (user exit 003/4)
  'FIDCC2' Send entire FI documents (user exit 005/6)
  'FIDCCH' Change in FI document
  'FIDCMT' Sending single items for FI-GL
  'FINANCIALPRODUCT_CREATE' Create security
  'FINANCIALTRANSACTION_CHANGE' Change transaction
  'FINANCIALTRANSACTION_CREATE' Create financial transaction
  'FINSTA' Bank Statement
  'FIPAYM' Payment data
  'FIROLL' General ledger rollup for FI-GL (delta f. line items FIDCMT)
  'FIXEDASSET_CHANGE' Changes an asset
  'FIXEDASSET_CREATE' Creates an asset
  'FIXEDASSET_CREATEFROMDATA1' Creates an Asset
  'FIXEDASSET_CREATEINCLVALUES' BAPI for legacy data transfer
  'FTRCON' Financial transaction confirmation
  'GLCORE' Master data G/L accounts (CORE IDOC)
  'GLFETC' Request G/L accounts
  'GLM000' Test reduction GLMAST
  'GLMAST' Master data G/L accounts (master IDOC)
  'GLROLL' FI-GLX message type rollup
  'GSVERF' Cred. memo procedure
  'HANMOV' HANMOV Handling Instruction for Movements
  'HRCC1DNATTAB' HR-PDC: Download permitted att./absence reasons
  'HRCC1DNBALAN' HR-PDC: Download employee balances
  'HRCC1DNCOSTC' HR-PDC: Download cost centers
  'HRCC1DNEXTWT' HR-PDC: Download permitted external wage types
  'HRCC1DNINORD' HR-PDC: Download internal orders
  'HRCC1DNOBJID' HR-PDC: Download objects (such as positions)
  'HRCC1DNPERSO' HR-PDC: Download HR Mini-Master
  'HRCC1DNTEVGR' HR-PDC: Download time event type groups
  'HRCC1DNWBSEL' HR-PDC: Download work breakdown structure element
  'HRCC1REQUPEXTWT' HR-PDC: Upload request for external wage types
  'HRCC1REQUPTEVEN' HR-PDC: Upload request for time events
  'HRCC1UPEXTWT' HR-PDC: Upload external wage types
  'HRCC1UPTEVEN' HR-PDC: Upload time events
  'HRCNF' Transfer confirmations (TimeMgtConfirmation)
  'HRCONF' Confirmations from Logistics for Human Resource Management
  'HRCPRQ' Personnel Cost Planning - inquiry from CO to HR
  'HRINW' Time tickets from Logistics
  'HRMASTER' Replicate (HRMasterDataReplica)
  'HRMD_A' HR: Organizational data and HR master data
  'HRMD_B' HR: Basis organizational data (SAP internal, use HRMD_A!)
  'HROTIN' HR: Outsourcing: Inbound Pay Results
  'HROTUST' HR: Outsourcing - US - Tax remittance
  'HROT_CA' HR: Outsourcing - Canadian Payroll
  'HROT_CM' HR: Outsourcing - Canadian Master Data Payroll
  'HROT_IN' HR: Outsourcing - Inbound IDOCs (Fill T558D !test!)
  'HROT_UM' HR: Outsourcing US
  'HROT_US' HR: Outsourcing - US Payroll
  'HRPAYP' HR: Transfer FI/CO
  'HRPRS' Attendances from Logistics
  'HRSM_A' HRSM: Personnel action
  'HRSM_B' HRSM: Confirmation personnel action
  'HRTRPR' Transfer TRV-PAY(PayrollTravelExpenses)
  'HRTRPY' HR-TRV: Transfer travel expenses after wage & salary
  'HRTRVL' HR-TRV: Transfer travel expenses FI/CO
  'IFTMIN' Forwarding Order
  'IFTSTA' Status transport information
  'IMATIS' Unplanned material issues
  'IMEASR' Measurement readings
  'IMPINV' Import declaration
  'IM_PROGDEF_SAVEREPLICA' Method 'SaveReplica' for ExpenditureProgDef
  'INFREC' Purchasing info record
  'INOTIF' Notifications
  'INSDES' Delivery outbound
  'INTERNAL_ORDER' Replicate individual internal order (ALE)
  'INTERNAL_ORDER_CREATE' Create internal order from transferred data
  'INTUPD' Notification Status Update
  'INVCON' Inventory Controlling IDOC
  'INVOIC' Invoice / Billing document
  'INVRPT' Stock Reconciliation
  'IOAUPD' work order assignments
  'IORDER' SM / PM order
  'IORUPD' Order Status Update
  'IWKCEN' Work Center IDOC
  'KANBAN' KANBAN call
  'KNOMAS' Global object dependencies
  'KOMMOD' Communication module / Transceiver
  'LABELS' Retail: Labeling
  'LCROLL' Legal consolidation
  'LIKOND' Listing conditions
  'LIP002' Distributed IS planning
  'LIP032' Upload infostructure storage loc.stocks (S032)
  'LIP035' Upload infostructure batch stocks (S035)
  'LIP076' Distributed IS planning
  'LIP125' Distributed IS planning
  'LIP750' Distributed IS planning
  'LIS000' LIS external data: sending
  'LOCAT5' Storage location for run schedules
  'LOCKBX' Lockbox
  'LOIBOM' Bill of Material
  'LOICAL' Calendar
  'LOIMSO' Storage location stock material
  'LOINUM' IDoc for number of IDocs sent
  'LOIPGR' IDoc for product group
  'LOIPLO' Planned order
  'LOIPRO' Production order
  'LOIRNH' Hierarchy/network
  'LOIROU' Routing
  'LOIRSH' Run schedule header
  'LOISTD' Stock/requirements list
  'LOITMX' Transition matrix
  'LOIWCS' Work center
  'LPIEQU' Quota arrangement
  'LPIPCM' Production campaign
  'MAKI01' Reduction test
  'MALFK5' Reasons for problems, run schedules
  'MALFU2' Problems in CC2
  'MANAGEREXTPAYROLL_INSERTLEGACY' Transfer payroll account
  'MANAGEREXTPAYROLL_INSERTOUT' Update of a payroll result using an outsourcer
  'MATCOR' Core master material
  'MATFET' Request material
  'MATMAS' Material Master
  'MATMAS_BAPI' Create and change material master data
  'MATQM' Replication of QM inspection setup
  'MBGMCA' Reverse goods movements with MB_CANCEL_GOODS_MOVEMENT
  'MBGMCR' BAPI Posting of goods mvts with MB_CREATE_GOODS_MOVEMENT
  'MKCLF1' ets clf
  'MK_MYSTD' test for loistd reduction
  'MMADDI' Create and change additionals (retail)
  'MRESCR' Create reservation
  'MY_MATMAS' test
  'OPERA2' Operations in CC2
  'OPERA3' Operations in CC3
  'OPERA4' Operations in CC4
  'OPERS2' Operation status in CC2
  'OPERS3' Workcenters in CC3
  'OPERS4' Workcenters in CC4
  'ORDCHG' Purchase order/order change
  'ORDERS' Purchase order / order
  'ORDLGT' Purchase order/order Orders Light
  'ORDRSP' Purchase order / order confirmation
  'ORGMASTER' Replicate (OrgMasterDataReplica)
  'OSTAT2' Process status CC2
  'PAB_ORDERS' Quantity release from KANBAN
  'PALMAT' Plant assignment to material BOM
  'PAYEXT' Extended payment order
  'PCHEAD' Basic and structure data of a product catalog
  'PCITEMS' Item data of a product catalog
  'PCROLL' Profit center rollup
  'PDTCO_POSTPRIMARY' Transfer of planning data: Post primary costs
  'PERSO1' Personnel master records in CC1
  'PERSO2' Personnel master in CC2
  'PERSO3' Personnel master in CC3
  'PERSO4' Personnel master in CC4
  'PFS_MATMAS01' PFS Master Material
  'PICKSD' Picking data confirmation to customer delivery
  'PIECEOFEQUIPMENT_DISMANTLEATFU' Dismantle equipment at functional location
  'PIECEOFEQUIPMENT_INSTALLATFUNC' Install equipment at functional location
  'PI_BTC' Data transfer
  'PKHD5' Kanban closed loops
  'PKPS5' Kanban container
  'PKST5' Possible status for Kanban containers
  'PLANDATATRANSFERCO_POSTACTIOUT' Planning data transfer: Post activity planning
  'PLANDATATRANSFERCO_POSTACTIVIT' Planning data transfer: Post activity input
  'PLANDATATRANSFERCO_POSTKEYFIGU' Transfer of planning data: Post stat. key figures
  'PLANT2' Plants in CC2
  'PLANT3' CC3: Plant table
  'PLANT4' CC4: Plant table
  'PORDCR' Create purchase order
  'PPCC2PRETEVENT' Transfer time event confirmations from PDC system
  'PPCC2PRETTICKET' Transfer time ticket confirmations from PDC system
  'PPCC2RECORDER' Send production orders to PDC system
  'PPCC2RECWORKCENTER' Send work centers to PDC system
  'PPCC2REQCONF' Send upload request to PDC system
  'PRCDOC' Replicate PCA line items (ALE)
  'PRCDOCD' Delete profit center documents (ALE)
  'PRCDOCP' Replicate EC-PCA plan line items (ALE)
  'PRCDOCR' Reversal of existing document line items (ALE)
  'PRCFET' Request profit center
  'PRCMAS' Profit center master record
  'PRDCAT' Product Catalog
  'PRDPOS' Product catalog item
  'PREQCR' Create purchase requisition
  'PREQDL' Delete/close purchase requisition
  'PRICAT' Price list / catalog
  'PRICECATALOGUE' Store price catalog instance
  'PROACT' Stock and sales data
  'PRODPL' Production plan reporting
  'PROFITCENTER_CHANGE' Change profit center
  'PROFITCENTER_CREATE' Create profit center
  'PROJECT' Replicate entire work breakdown structure (ALE)
  'PTOVERVIEW' Insert/Delete employee time overviews
  'QCERT' Certificate dispatch
  'QUOTES' Quotation
  'RCLROL' Reconciliation ledger rollup
  'RCYFET' Fetch exchanged IDocs from participating system
  'RCYLST' Message about objects from restarted system
  'RCYRSP' Confirmation about exchanged IDocs from participating system
  'RECADV' Receiving advice to MM & SD process
  'RECSHP' Recommended shipments
  'REMADV' Payment advice
  'REMURQSLIST_CHANGE' Agency business: Change invoice list documents BAPI
  'REMURQSLIST_CREATE_CBD' Create from posting list (invoice list)
  'REMURQSLIST_CREATE_REMU' Create from shipping document (invoice list)
  'REMURQSLIST_CREATE_SETT' Create from payment document (invoice list)
  'REMURQSLIST_RELEASE' Release to accounting (Invoice List)
  'REM_SPEC' Insert Ext. EE Remun. Info in Table (w/o Account Assignment)
  'REM_SPEC_WITH_ACTIVITY' Insert employee remuneration info (PTMgrExtRemunSpec)
  'REM_SPEC_WITH_COST' Insert External EE Remun. Info in Table (w/ Cost Assignment)
  'REQOTE' Inquiry
  'REQUI1' Confirmation request in CC1
  'REQUI2' Confirmation request in CC2
  'REQUI3' Confirmation request in CC2
  'REQUI4' Confirmation request in CC4
  'REQUI5' Confirmation request in CC5
  'RESOURCECO' Replicate individual CO resources (ALE)
  'RPLMAS' Create and change replenishment master data
  'RS0017' Master data delta 0MATERIAL Business Warehouse
  'RSINFO' BIW: Info message via OLTP selection process
  'RSRQST' BIW: Data request message to OLTP
  'RSSEND' BIW: Send requested data to OLAP
  'SAPRDI' IDoc type for raw data interface
  'SBINV' Credit memo procedure with invoice creation
  'SCS02O' Purchasing doc. for LIS; semi conductor purpose
  'SCS99N' Semiconductor supply qt
  'SDPACK' Packing confirmation
  'SDPICK' Picking confirmation
  'SEQJIT' Sequenced calls
  'SERDAT' Control message: Serialized distribution
  'SERVICENOTIFICATION_CREATEFROM' Create service notification
  'SETTRQSLIST_CHANGE' Agency Business: Change Settlement Request List BAPI
  'SETTRQSLIST_CREATE' Agency Business: Create Settlement Request List BAPI
  'SETTRQSLIST_RELEASE' Release to Accounting (SettlementRequstList)
  'SFADDE' SFA Download Debitor
  'SFADMA' sfa material download log msg.
  'SFADOR' sfa download orders log. msg
  'SFADORCH' sfa sales order (change pointers)
  'SFADPSA' BAPI Business Partner Activity Receiver
  'SFADSACTIVITY' Sales support document change point SFA download
  'SFATEST1' sfa sales order test
  'SHIPPL' Inbound planned shipments
  'SHPADV' Shipping notification
  'SHPCON' Delivery: Shipping confirmation
  'SHPMNT' Shipping outbound
  'SHPORD' Delivery: Dispatch order
  'SHP_IBDLV_CONFIRM_DECENTRAL' Confirmation(InboundDelivery)
  'SHP_IBDLV_SAVE_REPLICA' BAPI Function Module for Replication of Outbound Deliveries
  'SHP_OBDLV_CONFIRM_DECENTRAL' Confirmation(CustomerDelivery)
  'SHP_OBDLV_SAVE_REPLICA' BAPI Function Module for Replication of Outbound Deliveries
  'SINGLEREMUNRQS_CANCEL' Agency Business: Cancel Vendor Billing Documents BAPI
  'SINGLEREMUNRQS_CHANGE' Agency Business: Change Vendor Billing Documents BAPI
  'SINGLEREMUNRQS_CREATE' Agency Business: Generate Vendor Billing Documents BAPI
  'SINGLEREMUNRQS_RELEASE' Release to Accounting (Vendor Billing Documents)
  'SINGLESETTRQS_CANCEL' Agency Business: BAPI Cancel Single Settlement Requests
  'SINGLESETTRQS_CHANGE' Agency Business: BAPI Change Single Settlement Requests
  'SINGLESETTRQS_CREATE' Agency Business: Create Bapi Single Requests
  'SINGLESETTRQS_RELEASE' Release Accounting (SingleSettlementReqs)
  'SISCSO' SIS: Sales order
  'SISDEL' SIS: Delivery
  'SISINV' SIS: Billing document
  'SMMMAN' Material Master
  'SOPGEN' Distributed IS planning
  'SRCLST' Source List
  'SRVMAS' Master data service master
  'STATUS' Message about status information transmission
  'STPPOD' Acknowledgement of Receipt (POD)
  'STTMAT' STTMAT : Material variants
  'SYIDOC' Determination of IDoc types
  'SYNCH' Synchronous communication (e.g. ALE checks)
  'SYPART' Partner profiles
  'SYRECD' Determination of IDoc record types
  'T006_A' Dimension
  'T100_A' Messages
  'T682_A' Conditions: Access Sequences
  'T683_A' Costing sheets
  'T684_A' Condition Exclusion Groups
  'T685_A' Condition type
  'T686A' Conditions: Exclusion Indicator
  'TCUR_A' Currency
  'TEST01' test 01
  'TMC1_A' Condition table
  'TPSDLR' Shipping planning system: Trigger delivery selection
  'TPSDLS' Shipping planning system: Transfer delivery
  'TPSDST' Status change notification for sales document
  'TPSLOC' Shipping planning system: Transfer location master data
  'TPSSHT' Shipping planning system: Transfer planned shipments
  'TRIDOC' EDI: Transport of IDoc type definitions
  'TXTRAW' Message for free text in SAPoffice format 'RAW'
  'UNIMA2' Material-specific units of measurement
  'UNIT2' Units in CC2
  'UNIT3' Units in CC3
  'UNIT4' Units in CC4
  'UPLOAD' Configuration transceiver for upload
  'USERCLONE' Create user with template in another system
  'VENDCBDLIST_CHANGE' Agency Business: Change Posting Lists BAPI
  'VENDCBDLIST_CREATE' Agency Business: Generate Bapi Posting Lists
  'VENDCBDLIST_RELEASE' Agency Business: BAPI Release Posting Lists Document to FI
  'VFNMAS' Variant function
  'VTAMAS' Structure of variant table
  'VTMMAS' Contents of variant table
  'WALNOT' Allocation: Allocation table notification
  'WALREQ' Allocation: Report requested quantities
  'WBBDLD' Assortment list: Material data
  'WBBLAB' Assortment list: Reduced for labeling
  'WGSREQ' DRS: Incoming orders/order confirmation (GOODS_REQUIREMENT)
  'WHSCON' Delivery: Stock confirmation
  'WHSORD' Delivery: Stock order
  'WMBBIN' Block Storage Bins
  'WMCATO' Reversal/Reversal request for transfer order
  'WMERCAT' merchandise category and associated data
  'WMINFO' Information
  'WMINVE' Inventory count input
  'WMMBXY' IDoc Report goods movements in IM
  'WMPIHU' Pick HU
  'WMRREF' Release reference number
  'WMSUMO' Move storage unit
  'WMTOCO' Confirm transfer order
  'WMTORD' Transport request
  'WMTREQ' Create/Cancel transfer order
  'WORKC2' Workcenters in CC2
  'WORKC3' Workcenters in CC3
  'WORKC4' Workcenters in CC4
  'WPDBBY' POS interface: Download bonus buys
  'WPDCUR' POS interface: Download exchange rates
  'WPDNAC' POS interface: Download products
  'WPDSET' POS interface: Download set assignments
  'WPDTAX' POS interface: Download tax rates
  'WPDWGR' POS interface: Download material group master
  'WPUBON' POS interface: Upload sales docs (trnsctns), non-aggregated
  'WPUERR' POS interface: Upload messages SRS/POS/SCS
  'WPUFIB' POS interface: Upload Fin.Acc. interface SRS/POS
  'WPUKSR' POS upload cashier data
  'WPUPAE' POS interface: Upload price changes
  'WPUTAB' POS interface: Upload day-end closing POS
  'WPUUMS' POS interface: Upload sales data (compressed)
  'WPUWBW' POS interface: Upload goods movements
  'WP_EAN' POS interface: Upload/Download EAN assignments
  'WP_PER' POS interface: Upload/Download person data
  'WP_PLU' POS interface: Upload/Download article master
  'WP_PLU_RT'
  'WTADDI' Additionals
  'WTADDI_CVB1' Additionals w/o 06...
  'WVINVE' Store physical inventory/sales price revaluation
  'W_WGRP' Distribution of material groups
  'XSIDAT' XSI: Dummy message type for XSI data
  'XSITRK' XSI: Dummy message type for tracking
  'ZBOMAT' PCat BOM Extension: BOMs/Material BOM
  'ZDEBMS' Global Customer Conversions
  'ZGCUS1'
  'ZGMAT1'
  'ZGMATD' Material Determination Idoc for Pcat Interface
  'ZINVOIC' Message type for WIC invoices
  'ZKBCREMAS' CREMAS for MASCON
  'ZKBKOM' send PROLOG
  'ZKBLGT' Storage Location - Technik II
  'ZKBMATMAS'
  'ZKBMRK' Reference Number / PROLOG
  'ZKBOM1' BOM Technik II
  'ZKROU1' Routings Technik II
  'ZMATMS' Extended Material Master with addl.MARA fields
  'ZMDKCUST'
  'ZNCUS1' Customer Master
  'ZNCUS2' Reduced Customer Master - 2
  'ZNMAT1'
  'ZPPKBF' Production Confirmations - PDC Inbound
  'ZWICDLVYBX01' Benelux WIC PGI IDOC from GR
  'ZWICDLVYDE01' CE WIC PGI IDOC from GR
  'ZWICDLVYGB01' UK WIC PGI IDOC from GR
  'ZWICDLVYIB01' Iberia WIC PGI IDOC from GR
  'ZWICDLVYIN01' India WIC PGI IDOC from GR
  'ZWICDLVYNN01' Nordic WIC PGI IDOC from GR
  'ZWICDLVYTR01' Turkey WIC PGI IDOC from GR

• MESCOD : Message code

  Use
  The value can be selected by the user, in order to describe a message in more detail. MESTYP, MESCOD and MESFCT serve as a unique ID for the message, where MESTYP ("message type") must be maintained. They belong to the key fields in the partner profiles, which are used to specify the port and the IDoc type in outbound processing.
  For default values, the UN/EDIFACT data element 1001 can be used as an example.

• MESFCT : Message function

  Use
  The value can be selected by the user, in order to describe a message in more detail. MESTYP, MESCOD and MESFCT serve as a unique ID for the message, where MESTYP ("message type") must be maintained. They belong to the key fields in the partner profiles, which are used to specify the port and the IDoc type in outbound processing.
  For default values, the UN/EDIFACT data element 1225 can be used as an example.

• STD : EDI standard, flag

  Use
  The indicators and their meaning are freely compatible with the external EDI subsystem. They are only required when using the IDoc Interface for EDI. Within the R/3 System, the field is only used for documentary purposes.

• STDVRS : EDI standard, version and release

  Use
  The values and their meaning are freely compatible with the external EDI subsystem. The field is only required when using the IDoc Interface for EDI. Within the R/3 System, the field is only used for documentary purposes.

• STDMES : EDI message type

  Use
  Der EDI message type is freely compatible with the external EDI subsystem. The field is only required when using the IDoc Interface for EDI. Within the R/3 System, the field is only used for documentary purposes.

• SNDPOR : Sender port (SAP System, external subsystem)

  Use
  This field must be maintained with the value for the port
  in the sender system.
  The sender system can be an EDI subsystem or another SAP System (R/2 from 5.0F, R/3 from 2.1), for example.
  Outbound processing (from R/3):
  The sender system is an R/3 System. The port is called 'SAP', e.g. SAPC11 for an R/3 System with the name C11.
  Inbound processing:
  The external system must enter a value for a port in this field. This value must appear in the port definition for the IDoc Interface.

• SNDPRT : Partner type of sender

  Use
  Inbound processing (from R/3):
  This field must contain a description of the sender, e.g. customer ('KU') or vendor ('LI').
  SNDPFC, SNDPRN and SNDPRT serve as a unique ID for the sender. They are assigned to the corresponding key fields of the (inbound) partner profile, which is used to determine the process code, and therefore the internal R/3 processing. The external system must maintain the field with the value as entered in the inbound partner profiles.
  Outbound processing:
  The sender is the R/3 System. The field should contain the value 'LS' ('logical system').

• SNDPFC : Partner Function of Sender

  Use
  Inbound processing (from R/3):
  As an optional parameter, this field contains the partner function which includes both the sender and the recipient. Example: 'LF' for 'vendor' or 'AG' for 'ordering party'.
  SNDPFC, SNDPRN and SNDPRT serve as a unique ID for the sender. They belong to the key fields in the partner profiles, which is used in inbound processing to determine the process code, and therefore the internal R/3 processing, for the IDoc. Therefore, if the function of the sender is defined in the inbound partner profiles, the external system must enter the corresponding value in the field.
  Outbound processing:
  The sender is the R/3 System, which leaves the field blank.

• SNDPRN : Partner number of sender

  Use
  Inbound processing (from R/3):
  This field must contain the partner number of the sender, as entered in the R/3 master data (via internal number assignment).
  SNDPFC, SNDPRN and SNDPRT serve as a unique ID for the sender. They are assigned to the corresponding key fields of the (inbound) partner profile, which is used to determine the process code, and therefore the internal R/3 processing. The external system must enter the 'appropriate' number in the field.
  IDoc outbound processing:
  The sender is the R/3 System. The value 'CLNT' is entered in the field, e.g. C11CLNT003 for system C11, client 003.

  Value table: EDPP1

• SNDSAD : Sender address (SADR)

  General
  Reference to SAP directory service. The field is not currently used.

• SNDLAD : Logical address of sender

  General
  Reference to the table "Forwarding Inbound". The field is not generally used.

• RCVPOR : Receiver port

  Use
  This field must contain the port of the receiving system.
  Outbound processing (from R/3):
  The IDoc Interface determines the port from the partner profiles and writes the value in this field.
  Inbound processing:
  The receiving system is an SAP System. The external system must maintain the field by entering the value 'SAP', e.g. SAPC11.

• RCVPRT : Partner type of recipient

  Use
  Outbound processing (from R/3):
  This field describes the recipient, e.g. as a customer ('KU') or as a vendor ('LI').
  RCVPFC, RCVPRN and RCVPRT serve as a unique ID for the recipient. They are assigned to the corresponding key fields of the (outbound) partner profile, which is used to determine the port, for example. Therefore, the fields must be maintained correctly when IDocs are sent to the IDoc Interface.
  Inbound processing:
  The recipient is the R/3 System. The external system must enter the value 'LS' ('logical system').

• RCVPFC : Partner function of recipient

  Use
  Outbound processing (from R/3) using Message Control:
  The partner function must correspond with the appropriate Message Control field. Example: 'LF' for 'vendor' or 'AG' for 'ordering party'.
  Direct outbound processing:
  The partner function can be selected by the user; the field can also be left blank, but the following applies for outbound processing:
  RCVPFC, RCVPRN and RCVPRT serve as a unique ID for the recipient. They are assigned to the corresponding key fields of the (outbound) partner profile, which is used to determine the port, for example. Therefore, if the partner function is defined in the partner profiles, the function must also be present in the control record if an IDoc is sent to the IDoc Interface and the corresponding port is to be used.
  Inbound processing:
  The recipient is the R/3 System. The external system should leave this field blank.

• RCVPRN : Partner number of recipient

  Use
  Outbound processing (from R/3):
  This field must contain the partner number of the recipient, as entered in the R/3 System in the master data (e.g. via internal number assignment).
  RCVPFC, RCVPRN and RCVPRT serve as a unique ID for the recipient. They are assigned to the corresponding key fields of the (outbound) partner profile, which is used to determine the port, for example. Therefore, these fields must be maintained correctly when an IDoc is sent to the IDoc Interface.
  Inbound processing:
  The recipient is the R/3 System. The external system must maintain the field with the value 'CLNT', e.g. C11CLNT003 for system C11, client 003.

  Value table: EDPP1

• RCVSAD : Recipient address (SADR)

  General
  Reference to SAP directory service. The field is not currently used.

• RCVLAD : Logical address of recipient

  General
  Reference to table "Forwarding Inbound". The field is not generally used.

• CREDAT : Created on

  Use
  Contains the date on which the IDoc was generated. In IDoc inbound processing, this value cannot be entered by an external subsystem.

• CRETIM : Time created

  Use
  Contains the time at which the IDoc was generated. In IDoc inbound processing, this value cannot be entered by an external subsystem.

• REFINT : Transmission file (EDI Interchange)

  Use
  As a reference, this field contains the number of the interchange file, as entered in the EDI standards.
  An interchange file can therefore only exist in the external EDI subsystem. Depending on the transmission direction, this number should:
  either inform the R/3 System via status confirmation: in this case, the last returned number is saved in the control record of the relevant outbound IDoc (from R/3).
  or in inbound processing (from R/3), write to the field in the control record of the inbound IDoc.

• REFGRP : Message group (EDI Message Group)

  Use
  As a reference, this field contains the number of a message group, which is an optional feature when using EDI standards .
  A message group can therefore only exist in the external EDI subsystem. Depending on the transmission direction, this number should:
  either inform the R/3 System via status confirmation: in this case, the last returned number is saved in the control record of the relevant outbound IDoc (from R/3).
  or in inbound processing (from R/3), write to the field in the control record of the inbound IDoc.

• REFMES : Message (EDI Message)

  Use
  As a reference, this field contains the number of a message from EDI standards.
  An EDI message can therefore only exist in the external EDI subsystem. Depending on the transmission direction, this number should:
  either inform the R/3 System via status confirmation: in this case, the last returned number is saved in the control record of the relevant outbound IDoc (from R/3).
  or in inbound processing (from R/3), write to the field in the control record of the inbound IDoc.

• ARCKEY : Key for external message archive

  General
  If an EDI subsystem with archiving options is implemented, the R/3 System should be informed of the location of the messages via the archive key. From the point of view of the R/3 System, this takes place in:
  IDoc inbound processing:
  The archive key should be sent in the control record.
  Status record inbound processing:
  The archive key should be returned with the status report for outbound IDocs. The last key returned is always stored with the IDoc in R/3.

• SERIAL : Serialization

  Use
  The field is used by the ALE services for sequence identification purposes and contains information which allows the target system to recognize changes in the sequence of IDocs between the sending system and the receiving system.
  The field is only used within the SAP System.

Data record

General
IDoc data record from the IDoc interface in the SAP R/3 System to an external system.
The data record for Release 4.0 has the structure EDI_DD40. Each IDoc consists of exactly one control record, which is followed by several data records. The data record has organizational information in the first fields, which determines the syntactical construction of an IDoc and assigns the data record to an IDoc. The record also contains structural information about the application data. The field SDATA includes application data (up to 1000 bytes), interpretation occurs field by field via the segment. The segment is in the field SEGNAM.

Data record structure

Documentation

• SEGNAM : Segment (external name)

  internal data type : CHAR
  Internal length : 000030 characters
  Position in Segment : 001, Offset : 0000. external length : 000030
  

• MANDT : Client

  internal data type : CLNT
  Internal length : 000003 characters
  Position in Segment : 002, Offset : 0030. external length : 000003
  

• DOCNUM : IDoc number

  internal data type : CHAR
  Internal length : 000016 characters
  Position in Segment : 003, Offset : 0033. external length : 000016
  

• SEGNUM : Segment number

  internal data type : CHAR
  Internal length : 000006 characters
  Position in Segment : 004, Offset : 0049. external length : 000006
  

• PSGNUM : Number of superior parent segment

  internal data type : NUMC
  Internal length : 000006 characters
  Position in Segment : 005, Offset : 0055. external length : 000006
  

• HLEVEL : Hierarchy level of SAP segment

  internal data type : CHAR
  Internal length : 000002 characters
  Position in Segment : 006, Offset : 0061. external length : 000002
  

• SDATA : Application data

  internal data type : LCHR
  Internal length : 001000 characters
  Position in Segment : 007, Offset : 0063. external length : 001000
  

Data record documentation

Structure

• SEGNAM : Segment (external name)

  Use
  The field contains the external segment name (max. 30 characters); this specifies the structure of the application data stored in the field SDATA. SEGNAM must be maintained.
  SAP-defined segments begin with the prefix "E2" and conclude with 3 digits for version creation. For a newer version, only additional fields at the end of the segment can be added, making it possible to trace an older ("shorter") version at any time.

• MANDT : Client

  Use
  From the R/3 side, the IDoc Interface enters the current client. An external system should not maintain this field (in inbound processing from the R/3 point of view and for status confirmation), to avoid unnecessary errors: transferred values are checked against the current client.

  Values
  
  '000' SAP AG Walldorf
  '001' Auslieferungsmandant R11 Kundstadt
  '020' Braun Europe production Kronberg
  '066' EarlyWatch Walldorf

• DOCNUM : IDoc number

  Use
  Identifies the IDoc. The number is client-specific and is determined via internal number assignment. The external system must consider the following:
  IDoc outbound processing (from the point of view of the R/3 System):
  The number must be kept for any later status confirmations (see below).
  IDoc inbound processing:
  This field remains empty (the IDoc is generated in the R/3 System).
  Status confirmation:
  The field must contain the number of the IDoc to which the status confirmation refers. Only in this way can the R/3 System assign the status records to an IDoc.

• SEGNUM : Segment number

  General
  The field contains the sequential number of a segment. The data records are numbered sequentially, starting with 1. The IDoc Interface checks that the numbering is correct. The field must be maintained.
  In a status confirmation, the field should contain the number of the segment which caused the status change.

• PSGNUM : Number of superior parent segment

  Definition
  Contains the number of the parent segment which is superior to the segment, i.e. the contents of field SEGNUM from the corresponding data record.
  Use
  When generating an IDoc, the IDoc Interface maintains the field in the data records according to the syntax of the IDoc type being used.
  If an EDI subsystem is implemented, the system should not maintain this field (from the R/3 side) in inbound processing, in order to avoid unnecessary errors: the IDoc Interface checks all transferred values against the syntax of the relevant IDoc type.

• HLEVEL : Hierarchy level of SAP segment

  Use
  The hierarchy level of the segment is determined in the IDoc Interface, where the relevant IDoc type was defined. As a result, neither the external system (inbound) nor the application (
  outbound) should maintain this field, to avoid any errors. The IDoc Interface checks the values against the syntax description of the transferred IDoc type.
  Dependencies
  A segment can only be used on one hierarchy level for each IDoc type.

• SDATA : Application data

  Use
  The field contains the application data of an SAP segment. Using this field, the segment structure (name in field SEGNAM) can be created. This enables the application data to be accessed on a field-by-field basis.
  The field must be maintained.

Status record

General
IDoc status record from the IDoc interface in the SAP R/3 System to an external system. The record contains information about the processing status of an IDoc.

Status record structure

Documentation

• TABNAM : Name of table structure

  internal data type : CHAR
  Internal length : 000010 characters
  Position in Segment : 001, Offset : 0000. external length : 000010
  

• MANDT : Client

  internal data type : CLNT
  Internal length : 000003 characters
  Position in Segment : 002, Offset : 0010. external length : 000003
  

• DOCNUM : IDoc number

  internal data type : CHAR
  Internal length : 000016 characters
  Position in Segment : 003, Offset : 0013. external length : 000016
  

• LOGDAT : Date of status information

  internal data type : DATS
  Internal length : 000008 characters
  Position in Segment : 004, Offset : 0029. external length : 000008
  

• LOGTIM : Time of status information

  internal data type : TIMS
  Internal length : 000006 characters
  Position in Segment : 005, Offset : 0037. external length : 000006
  

• STATUS : Status of IDoc

  internal data type : CHAR
  Internal length : 000002 characters
  Position in Segment : 006, Offset : 0043. external length : 000002
  

• STAMQU : Status for message in status record

  internal data type : CHAR
  Internal length : 000003 characters
  Position in Segment : 007, Offset : 0045. external length : 000003
  

• STAMID : Message for status notification: Message class

  internal data type : CHAR
  Internal length : 000020 characters
  Position in Segment : 008, Offset : 0048. external length : 000020
  

• STAMNO : Message number for status message

  internal data type : NUMC
  Internal length : 000003 characters
  Position in Segment : 009, Offset : 0068. external length : 000003
  

• STATYP : ABAP message type (A, W, E, S, I) in status message

  internal data type : CHAR
  Internal length : 000001 characters
  Position in Segment : 010, Offset : 0071. external length : 000001
  

• STAPA1 : First parameter for message in status record

  internal data type : CHAR
  Internal length : 000050 characters
  Position in Segment : 011, Offset : 0072. external length : 000050
  

• STAPA2 : Second parameter for message in status record

  internal data type : CHAR
  Internal length : 000050 characters
  Position in Segment : 012, Offset : 0122. external length : 000050
  

• STAPA3 : Third parameter for message in status record

  internal data type : CHAR
  Internal length : 000050 characters
  Position in Segment : 013, Offset : 0172. external length : 000050
  

• STAPA4 : Fourth parameter for message in status record

  internal data type : CHAR
  Internal length : 000050 characters
  Position in Segment : 014, Offset : 0222. external length : 000050
  

• STATXT : Status text

  internal data type : CHAR
  Internal length : 000070 characters
  Position in Segment : 015, Offset : 0272. external length : 000070
  

• UNAME : User name

  internal data type : CHAR
  Internal length : 000012 characters
  Position in Segment : 016, Offset : 0342. external length : 000012
  

• REPID : Program

  internal data type : CHAR
  Internal length : 000030 characters
  Position in Segment : 017, Offset : 0354. external length : 000030
  

• ROUTID : Subroutine (routine, function module)

  internal data type : CHAR
  Internal length : 000030 characters
  Position in Segment : 018, Offset : 0384. external length : 000030
  

• SEGNUM : Segment number

  internal data type : CHAR
  Internal length : 000006 characters
  Position in Segment : 019, Offset : 0414. external length : 000006
  

• SEGFLD : Segment field

  internal data type : CHAR
  Internal length : 000030 characters
  Position in Segment : 020, Offset : 0420. external length : 000030
  

• REFINT : Transmission file (EDI Interchange)

  internal data type : CHAR
  Internal length : 000014 characters
  Position in Segment : 021, Offset : 0450. external length : 000014
  

• REFGRP : Message group (EDI Message Group)

  internal data type : CHAR
  Internal length : 000014 characters
  Position in Segment : 022, Offset : 0464. external length : 000014
  

• REFMES : Message (EDI Message)

  internal data type : CHAR
  Internal length : 000014 characters
  Position in Segment : 023, Offset : 0478. external length : 000014
  

• ARCKEY : Key for external message archive

  internal data type : CHAR
  Internal length : 000070 characters
  Position in Segment : 024, Offset : 0492. external length : 000070
  

Status record documentation

Structure

• TABNAM : Name of table structure

  Use
  This field contains information about the IDoc structures exchanged with an external system. The following values are used:
  EDI_DC40 (Control record structure)
  EDI_DS40 (Status record structure)
  The data records (EDI_DD40) contain only the segment names.

• MANDT : Client

  Use
  From the R/3 side, the IDoc Interface enters the current client. An external system should not maintain this field (in inbound processing from the R/3 point of view and for status confirmation), to avoid unnecessary errors: transferred values are checked against the current client.

  Values
  
  '000' SAP AG Walldorf
  '001' Auslieferungsmandant R11 Kundstadt
  '020' Braun Europe production Kronberg
  '066' EarlyWatch Walldorf

• DOCNUM : IDoc number

  Use
  Identifies the IDoc. The number is client-specific and is determined via internal number assignment. The external system must consider the following:
  IDoc outbound processing (from the point of view of the R/3 System):
  The number must be kept for any later status confirmations (see below).
  IDoc inbound processing:
  This field remains empty (the IDoc is generated in the R/3 System).
  Status confirmation:
  The field must contain the number of the IDoc to which the status confirmation refers. Only in this way can the R/3 System assign the status records to an IDoc.

• LOGDAT : Date of status information

  Use
  Contains the date on which a status change (success or error) was written, entered in the format YYYYMMDD. This field must be maintained. In the case of a status confirmation, the external system enters the system date in this field.

• LOGTIM : Time of status information

  General
  Contains the time at which a status change (success or error) was written, entered in the format HHMMSS. This field must be maintained. In the case of a status confirmation, the external system enters the system time in this field.

• STATUS : Status of IDoc

  Use
  IDoc processing can be monitored via the status. The external system must enter the correct value in the field in the status confirmation (see F4 help).
  The status for outbound IDocs is between '01' and '49', while the minimum status value for inbound IDocs is '50'.

  Outbound
  
  00 IDoc interface (SAP) : Not used, only R/2
  01 IDoc interface (SAP) : IDoc created
  02 IDoc interface (SAP) : Error passing data to port
  03 IDoc interface (SAP) : Data passed to port OK
  04 External system/EDI subsystem : Error within control information of EDI subsystem
  05 External system/EDI subsystem : Error during translation
  06 External system/EDI subsystem : Translation OK
  07 External system/EDI subsystem : Error during syntax check
  08 External system/EDI subsystem : Syntax check OK
  09 External system/EDI subsystem : Error during interchange handling
  10 External system/EDI subsystem : Interchange handling OK
  11 External system/EDI subsystem : Error during dispatch
  12 External system/EDI subsystem : Dispatch OK
  13 External system/EDI subsystem : Retransmission OK
  14 External system/EDI subsystem : Interchange Acknowledgement positive
  15 External system/EDI subsystem : Interchange Acknowledgement negative
  16 External system/EDI subsystem : Functional Acknowledgement positive
  17 External system/EDI subsystem : Functional Acknowledgement negative
  18 IDoc interface (SAP) : Triggering EDI subsystem OK
  19 IDoc interface (SAP) : Data transfer for test OK
  20 IDoc interface (SAP) : Error triggering EDI subsystem
  21 IDoc interface (SAP) : Error passing data for test
  22 External system/EDI subsystem : Dispatch OK, acknowledgement still due
  23 External system/EDI subsystem : Error during retransmission
  24 External system/EDI subsystem : Control information of EDI subsystem OK
  25 IDoc interface (SAP) : Processing despite syntax error (outbound)
  26 IDoc interface (SAP) : Error during syntax check of IDoc (outbound)
  27 IDoc interface (SAP) : Error in dispatch level (ALE service)
  28 IDoc interface (SAP) : Not used
  29 IDoc interface (SAP) : Error in ALE service
  30 IDoc interface (SAP) : IDoc ready for dispatch (ALE service)
  31 IDoc interface (SAP) : Error - no further processing
  32 IDoc interface (SAP) : IDoc was edited
  33 IDoc interface (SAP) : Original of an IDoc which was edited
  34 IDoc interface (SAP) : Error in control record of IDoc
  35 IDoc interface (SAP) : IDoc reloaded from archive
  36 External system/EDI subsystem : Electronic signature not performed (timeout)
  37 IDoc interface (SAP) : IDoc added incorrectly
  38 IDoc interface (SAP) : IDoc archived
  39 IDoc interface (SAP) : IDoc is in the receiving system (ALE service)
  40 IDoc interface (SAP) : Application document not created in receiving system
  41 IDoc interface (SAP) : Application document created in receiving system
  42 IDoc interface (SAP) : IDoc was created by test transaction
  50 IDoc interface (SAP) : IDoc added

  Inbound
  
  51 SAP application : Error: Application document not posted
  52 SAP application : Application document not fully posted
  53 SAP application : Application document posted
  54 SAP application : Error during formal application check
  55 SAP application : Formal application check OK
  56 IDoc interface (SAP) : IDoc with errors added
  57 SAP application : Test IDoc: Error during application check
  58 IDoc interface (SAP) : IDoc-Copy from an R/2 connection
  59 IDoc interface (SAP) : Not used
  60 IDoc interface (SAP) : Error during syntax check of IDoc (inbound)
  61 IDoc interface (SAP) : Processing despite syntax error (inbound)
  62 IDoc interface (SAP) : IDoc passed to application
  63 IDoc interface (SAP) : Error passing IDoc to application
  64 IDoc interface (SAP) : IDoc ready to be transferred to application
  65 IDoc interface (SAP) : Error in ALE service
  66 IDoc interface (SAP) : IDoc is waiting for predecessor IDoc (serialization)
  67 IDoc interface (SAP) : Not used
  68 IDoc interface (SAP) : Error - no further processing
  69 IDoc interface (SAP) : IDoc was edited
  70 IDoc interface (SAP) : Original of an IDoc which was edited
  71 IDoc interface (SAP) : IDoc reloaded from archive
  72 IDoc interface (SAP) : Not used, only R/2
  73 IDoc interface (SAP) : IDoc archived
  74 IDoc interface (SAP) : IDoc was created by test transaction

• STAMQU : Status for message in status record

  Use
  In a status record, the three fields STAMQU, STAMID and STAMNO identify a message. This is important for error messages, and also for other messages (e.g. success messages).
  STAMQU defines how the contents of the fields STAMID and STAMNO are to be interpreted. The value 'SAP' means the following:
  STAMID: the message class is from table T100
  STAMNO: the message number is from table T100
  Messages from the external system in a status confirmation can be displayed individually, if STAMQU is assigned a value which is not 'SAP' and this value is assigned to a corresponding function module under Control -> Status record display (from the IDoc Interface area menu, transaction WEDI). Even when the status has not changed, several status records containing various messages about the IDoc are sent.

• STAMID : Message for status notification: Message class

  Use
  In a status record, the three fields STAMQU, STAMID and STAMNO identify a message. This is important for error messages, and also for other messages (for example, success messages).
  STAMQU defines how the contents of the fields STAMID and STAMNO are to be interpreted. The value 'SAP' means the following:
  STAMID: the message class (application area) is from table T100
  STAMNO: the message number is from table T100
  Messages from the external system in a status confirmation can be displayed individually, if STAMQU is assigned a value which is not 'SAP' and this value is assigned to a corresponding function module under Control -> Status record display (from the IDoc Interface area menu, transaction WEDI). Even when the status has not changed, several status records containing various messages about the IDoc are sent.

• STAMNO : Message number for status message

  Use
  In a status record, the three fields STAMQU, STAMID and STAMNO identify a message. This is important for error messages, and also for other messages (e.g. success messages).
  STAMQU defines how the contents of the fields STAMID and STAMNO are to be interpreted. The value 'SAP' means the following:
  STAMID: the message class is from table T100
  STAMNO: the message number is from table T100
  Messages from the external system in a status confirmation can be displayed individually, if STAMQU is assigned a value which is not 'SAP' and this value is assigned to a corresponding function module under Control -> Status record display (from the IDoc Interface area menu, transaction WEDI). Even when the status has not changed, several status records containing various messages about the IDoc are sent.

• STATYP : ABAP message type (A, W, E, S, I) in status message

  Use
  An ABAP message in the status record has a certain type (e.g. 'E' for error message) which is stored here. In the case of a status confirmation, this value can be maintained by the external system.

  Values
  
  'A' Cancel
  'W' Warning
  'E' Error
  'S' Success message
  'I' Information

• STAPA1 : First parameter for message in status record

  Use
  In the status record, the field includes a value determined at runtime which is used to replace the first variable (& or &1) in the field STATXT. In the case of a status confirmation, the external system can also use this variable concept.

• STAPA2 : Second parameter for message in status record

  Use
  In the status record, the field includes a value determined at runtime which is used to replace the second variable (& or &2) in the field STATXT. In the case of a status confirmation, the external system can also use this variable concept.

• STAPA3 : Third parameter for message in status record

  Use
  In the status record, the field includes a value determined at runtime which is used to replace the third variable (& or &3) in the field STATXT. In the case of a status confirmation, the external system can also use this variable concept.

• STAPA4 : Fourth parameter for message in status record

  Use
  In the status record, the field includes a value determined at runtime which is used to replace the fourth variable (& or &4) in the field STATXT. In the case of a status confirmation, the external system can also use this variable concept.

• STATXT : Status text

  Use
  If a program (e.g. an application module) writes a status_record, a message about the three fields STAMQU, STAMID and STAMNO can also be created. STATXT contains the relevant text, which is either a text from R/3 table T100 or a text from the external system.
  The text can contain up to four parameters (& symbols in the correct order or &1, &2, &3, &4), which are later replaced in the status record display by the values from fields STAPA1, STAPA2, STAPA3 and STAPA4. These fields must, of course, be maintained by the program which writes the status record.
  Status confirmation:
  The external system can maintain the field. Even if the value of the field STATUS does not change, several status records with different texts can be sent to the SAP System.

• UNAME : User name

  Use
  When an IDoc is edited, the status changes. The name of the active user at the time of the status change should be entered in this field (however, this entry is optional).

• REPID : Program

  General
  The field can contain the name of the program which caused the status change. If, for example, the IDoc is processed in the application and the corresponding status records are written, the application can store the required programs here.

• ROUTID : Subroutine (routine, function module)

  General
  The field should contain the name of the subroutine active at the time of the status change.

• SEGNUM : Segment number

  General
  The field contains the sequential number of a segment. The data records are numbered sequentially, starting with 1. The IDoc Interface checks that the numbering is correct. The field must be maintained.
  In a status confirmation, the field should contain the number of the segment which caused the status change.

• SEGFLD : Segment field

  Use
  When a program writes a status record using a single segmentfield, the field name can be stored here. This usually happens when an error occurs:
  The update module for the application discovers a field for which the contents are incorrect.
  The EDI subsystem cannot convert a field.

• REFINT : Transmission file (EDI Interchange)

  Use
  As a reference, this field contains the number of the interchange file, as entered in the EDI standards.
  An interchange file can therefore only exist in the external EDI subsystem. Depending on the transmission direction, this number should:
  either inform the R/3 System via status confirmation: in this case, the last returned number is saved in the control record of the relevant outbound IDoc (from R/3).
  or in inbound processing (from R/3), write to the field in the control record of the inbound IDoc.

• REFGRP : Message group (EDI Message Group)

  Use
  As a reference, this field contains the number of a message group, which is an optional feature when using EDI standards .
  A message group can therefore only exist in the external EDI subsystem. Depending on the transmission direction, this number should:
  either inform the R/3 System via status confirmation: in this case, the last returned number is saved in the control record of the relevant outbound IDoc (from R/3).
  or in inbound processing (from R/3), write to the field in the control record of the inbound IDoc.

• REFMES : Message (EDI Message)

  Use
  As a reference, this field contains the number of a message from EDI standards.
  An EDI message can therefore only exist in the external EDI subsystem. Depending on the transmission direction, this number should:
  either inform the R/3 System via status confirmation: in this case, the last returned number is saved in the control record of the relevant outbound IDoc (from R/3).
  or in inbound processing (from R/3), write to the field in the control record of the inbound IDoc.

• ARCKEY : Key for external message archive

  General
  If an EDI subsystem with archiving options is implemented, the R/3 System should be informed of the location of the messages via the archive key. From the point of view of the R/3 System, this takes place in:
  IDoc inbound processing:
  The archive key should be sent in the control record.
  Status record inbound processing:
  The archive key should be returned with the status report for outbound IDocs. The last key returned is always stored with the IDoc in R/3.

Info...