IT38262: DOCUMENT REQUIREMENTS FOR EXTENDED IDOC TYPES IN THE SAP NODES

APAR status

• Closed as documentation error.

Error description

• When using the SAP Nodes to process extended IDocs it is
  required that all of the segment details are populated in the
  EDISYN table however this is not documented in the
  KonwledgeCenter.
  

Local fix

• Execute  the WE60 TCODE on the extened Idoc definition. This
  will populate the EDISYN table for this Idoc.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  <span style="background-color:rgb(255, 255, 255)">DOCUMENT
  REQUIREMENTS FOR EXTENDED IDOC TYPES IN THE SAP NODES</span>
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  <span style="background-color:rgb(255, 255, 255)">When using the
  SAP Nodes to process extended IDocs it is </span><span
  style="background-color:rgb(255, 255, 255)">required that all of
  the segment details are populated in the </span><span
  style="background-color:rgb(255, 255, 255)">EDISYN table. This
  is not, however, documented in the </span><span
  style="background-color:rgb(255, 255, 255)">Knowledge Center.
                                                </span>
  

Problem conclusion

• Knowledge Center Topic
  https://www.ibm.com/docs/en/app-connect/12.0?topic=software-ale-
  interfaces has been updated to include the following note.
  
  In order to process extended IDoc types the EDISYN table must
  have been populated with all segments that are used by the
  extended IDoc. This can be done, for example, by using the
  transaction WE60 on the SAP system.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels