Hello Community,

We are encountering an issue when posting inbound DESADV (SHPMNT) IDocs to SAP using the JCo Adapter from IBM Sterling B2B Integrator 6.2. The same IDoc loads successfully when sent from our legacy Gentran system but fails from Sterling with the following error:

"EDI: Table passed to EDI_SEGMENTS_ADD_BLOCK is empty."

What We Have Verified:

• The IDoc control record (EDI_DC40) is correct and matches expected routing in SAP (Message type: SHPCON, Basic type: DELVRY03, Version: X004010856).

• Segment lines were initially output as E2EDL20, E2EDL24, etc., but we updated the Sterling map to use E1* segments (E1EDL20, E1EDL24, etc.) to align with what IDOC_INPUT_DESADV1 expects.

• The IDoc format is flat file (no XML/tree structure), and it is being passed to SAP via JCo.

• We are assigning the translated document as PrimaryDocument before invoking JCo.

• The same IDoc file, when sent from Gentran, is processed successfully in SAP without error.

• We tested IDocs with E1 segments and ensured the message type/process code in WE20 correctly routes to IDOC_INPUT_DESADV1.

• Our ORDERS IDocs work fine via JCo, even with E2* segments.

• The DESADV IDOC generated out of SI works fine when I load it via GENTRAN but the idoc created in GENTRAN when loaded with SI, doesn't work. We cross-tested everything and everything or anything works from GENTRAN but nothing works from SI Inbound. ORDERS idoc on the other hand post without any issues. 

🧠 Summary of the Problem:

Even after converting segments to E1* and cleaning up the map, SAP still reports that the segment table is empty. However, when the same IDoc is sent from Gentran via ALE, SAP processes it without issue.

---

❓ Our Key Questions:

1. Has anyone encountered a similar issue with DESADV IDocs and the JCo Adapter

---

Any insights or shared experiences would be greatly appreciated. We are trying to avoid modifying our SAP FM logic and would prefer to handle this correctly from the Sterling/JCo side.

------------------------------
Vamsi Kamisetty
------------------------------

Hi Vamsi,

did you run into an error using the E2 segment names or why did you change it?

We send all idocs with E2* to SAP, also the DESADVs and are using the SAP standard process code.

Best regards

Manuel

------------------------------
Manuel Frank
Integration Architect
Andreas STIHL AG & Co. KG
Waiblingen
------------------------------

Original Message:
Sent: Wed June 25, 2025 05:13 PM
From: Vamsi Kamisetty
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hello Community,

We are encountering an issue when posting inbound DESADV (SHPMNT) IDocs to SAP using the JCo Adapter from IBM Sterling B2B Integrator 6.2. The same IDoc loads successfully when sent from our legacy Gentran system but fails from Sterling with the following error:

"EDI: Table passed to EDI_SEGMENTS_ADD_BLOCK is empty."

What We Have Verified:

• The IDoc control record (EDI_DC40) is correct and matches expected routing in SAP (Message type: SHPCON, Basic type: DELVRY03, Version: X004010856).

• Segment lines were initially output as E2EDL20, E2EDL24, etc., but we updated the Sterling map to use E1* segments (E1EDL20, E1EDL24, etc.) to align with what IDOC_INPUT_DESADV1 expects.

• The IDoc format is flat file (no XML/tree structure), and it is being passed to SAP via JCo.

• We are assigning the translated document as PrimaryDocument before invoking JCo.

• The same IDoc file, when sent from Gentran, is processed successfully in SAP without error.

• We tested IDocs with E1 segments and ensured the message type/process code in WE20 correctly routes to IDOC_INPUT_DESADV1.

• Our ORDERS IDocs work fine via JCo, even with E2* segments.

• The DESADV IDOC generated out of SI works fine when I load it via GENTRAN but the idoc created in GENTRAN when loaded with SI, doesn't work. We cross-tested everything and everything or anything works from GENTRAN but nothing works from SI Inbound. ORDERS idoc on the other hand post without any issues. 

🧠 Summary of the Problem:

Even after converting segments to E1* and cleaning up the map, SAP still reports that the segment table is empty. However, when the same IDoc is sent from Gentran via ALE, SAP processes it without issue.

---

❓ Our Key Questions:

1. Has anyone encountered a similar issue with DESADV IDocs and the JCo Adapter

---

Any insights or shared experiences would be greatly appreciated. We are trying to avoid modifying our SAP FM logic and would prefer to handle this correctly from the Sterling/JCo side.

------------------------------
Vamsi Kamisetty
------------------------------