Status record documentation

• 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.