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.

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

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.

Hey Manuel, 

I ran into the same issue with the E2 segments. I then started looking on the internet and there was a suggestion about changing the segments to E1. I then gave it a try and still nothing. When you mean by the standard SAP code, do you know if there is a function module involved or what standard are we talking about? 

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

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.

Hi Vamsi,

I mean the process code which handles the idocs once created.

This is how an DESADV idocs looks when sending it to a SAP system from our SI:

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

Original Message:
Sent: Thu June 26, 2025 06:56 AM
From: Vamsi Kamisetty
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hey Manuel, 

I ran into the same issue with the E2 segments. I then started looking on the internet and there was a suggestion about changing the segments to E1. I then gave it a try and still nothing. When you mean by the standard SAP code, do you know if there is a function module involved or what standard are we talking about? 

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

Original Message:
Sent: Thu June 26, 2025 12:57 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

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

Hello Manuel,

Am attaching the idoc I am trying to push into SAP. We are using the same BP that process ORDERS idocs into SAP which works fine. Not sure why the DESADV or SHPCON won't work. Our current application GENTRAN loads the same idoc generated out of SI without any issues. I compared the idoc side by side between GENTRAN and SI and they are identical. That's where the confusion is. We are using the same JCo for inbound and outbound documents. 

The process code in SAP is DELS for DESADV idocs and DELV for SHPCON idocs. No changes there. The process codes don't show up in the idoc on our side. The process codes have their own functional modeules in them but I don't see how that matters from where the data is being sent. GENTRAN or SI. 

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

Original Message:
Sent: Mon June 30, 2025 09:17 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hi Vamsi,

I mean the process code which handles the idocs once created.

This is how an DESADV idocs looks when sending it to a SAP system from our SI:

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

Original Message:
Sent: Thu June 26, 2025 06:56 AM
From: Vamsi Kamisetty
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hey Manuel, 

I ran into the same issue with the E2 segments. I then started looking on the internet and there was a suggestion about changing the segments to E1. I then gave it a try and still nothing. When you mean by the standard SAP code, do you know if there is a function module involved or what standard are we talking about? 

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

Original Message:
Sent: Thu June 26, 2025 12:57 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

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

Hi Vamsi,

we always populate the client also in the each segment.

Further the segment number in EDL22 seems off.

Best regards

Manuel

Hello Manuel,

Am attaching the idoc I am trying to push into SAP. We are using the same BP that process ORDERS idocs into SAP which works fine. Not sure why the DESADV or SHPCON won't work. Our current application GENTRAN loads the same idoc generated out of SI without any issues. I compared the idoc side by side between GENTRAN and SI and they are identical. That's where the confusion is. We are using the same JCo for inbound and outbound documents. 

The process code in SAP is DELS for DESADV idocs and DELV for SHPCON idocs. No changes there. The process codes don't show up in the idoc on our side. The process codes have their own functional modeules in them but I don't see how that matters from where the data is being sent. GENTRAN or SI. 

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

Original Message:
Sent: Mon June 30, 2025 09:17 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hi Vamsi,

I mean the process code which handles the idocs once created.

This is how an DESADV idocs looks when sending it to a SAP system from our SI:

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

Original Message:
Sent: Thu June 26, 2025 06:56 AM
From: Vamsi Kamisetty
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hey Manuel, 

I ran into the same issue with the E2 segments. I then started looking on the internet and there was a suggestion about changing the segments to E1. I then gave it a try and still nothing. When you mean by the standard SAP code, do you know if there is a function module involved or what standard are we talking about? 

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

Original Message:
Sent: Thu June 26, 2025 12:57 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

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

Hello Manuel,

Am attaching the idoc I am trying to push into SAP. We are using the same BP that process ORDERS idocs into SAP which works fine. Not sure why the DESADV or SHPCON won't work. Our current application GENTRAN loads the same idoc generated out of SI without any issues. I compared the idoc side by side between GENTRAN and SI and they are identical. That's where the confusion is. We are using the same JCo for inbound and outbound documents. 

The process code in SAP is DELS for DESADV idocs and DELV for SHPCON idocs. No changes there. The process codes don't show up in the idoc on our side. The process codes have their own functional modeules in them but I don't see how that matters from where the data is being sent. GENTRAN or SI. 

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

Original Message:
Sent: Mon June 30, 2025 09:17 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hi Vamsi,

I mean the process code which handles the idocs once created.

This is how an DESADV idocs looks when sending it to a SAP system from our SI:

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

Original Message:
Sent: Thu June 26, 2025 06:56 AM
From: Vamsi Kamisetty
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hey Manuel, 

I ran into the same issue with the E2 segments. I then started looking on the internet and there was a suggestion about changing the segments to E1. I then gave it a try and still nothing. When you mean by the standard SAP code, do you know if there is a function module involved or what standard are we talking about? 

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

Original Message:
Sent: Thu June 26, 2025 12:57 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

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

Hi Vamsi,

I have seen this before.  It looks like you have an IDOC number in the control record, 010.  This needs to be on each of the segments as well. You can see that on Manuel's example.

The function module in SAP inputs the control record and the segments in separate tables. It then tries to match them up based on the IDOC number. It also works if you leave the IDOC number off the control record and segments and you are only passing 1 IDOC at a time.  Either way it needs to match.

Hello Manuel,

Am attaching the idoc I am trying to push into SAP. We are using the same BP that process ORDERS idocs into SAP which works fine. Not sure why the DESADV or SHPCON won't work. Our current application GENTRAN loads the same idoc generated out of SI without any issues. I compared the idoc side by side between GENTRAN and SI and they are identical. That's where the confusion is. We are using the same JCo for inbound and outbound documents. 

The process code in SAP is DELS for DESADV idocs and DELV for SHPCON idocs. No changes there. The process codes don't show up in the idoc on our side. The process codes have their own functional modeules in them but I don't see how that matters from where the data is being sent. GENTRAN or SI. 

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

Original Message:
Sent: Mon June 30, 2025 09:17 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hi Vamsi,

I mean the process code which handles the idocs once created.

This is how an DESADV idocs looks when sending it to a SAP system from our SI:

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

Original Message:
Sent: Thu June 26, 2025 06:56 AM
From: Vamsi Kamisetty
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hey Manuel, 

I ran into the same issue with the E2 segments. I then started looking on the internet and there was a suggestion about changing the segments to E1. I then gave it a try and still nothing. When you mean by the standard SAP code, do you know if there is a function module involved or what standard are we talking about? 

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

Original Message:
Sent: Thu June 26, 2025 12:57 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

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

Hello John, Thank you for the detailed information. I tried inputting the client record 010 on every segment and no luck. I am also attaching the ORDERS IDOC which is working fine and it doesn't have client record on every segment. I am attaching the DESADV idoc that isn't working even after updating the client record along with the error shown in the BP. 

Hi Vamsi,

I have seen this before.  It looks like you have an IDOC number in the control record, 010.  This needs to be on each of the segments as well. You can see that on Manuel's example.

The function module in SAP inputs the control record and the segments in separate tables. It then tries to match them up based on the IDOC number. It also works if you leave the IDOC number off the control record and segments and you are only passing 1 IDOC at a time.  Either way it needs to match.

Hello Manuel,

Am attaching the idoc I am trying to push into SAP. We are using the same BP that process ORDERS idocs into SAP which works fine. Not sure why the DESADV or SHPCON won't work. Our current application GENTRAN loads the same idoc generated out of SI without any issues. I compared the idoc side by side between GENTRAN and SI and they are identical. That's where the confusion is. We are using the same JCo for inbound and outbound documents. 

The process code in SAP is DELS for DESADV idocs and DELV for SHPCON idocs. No changes there. The process codes don't show up in the idoc on our side. The process codes have their own functional modeules in them but I don't see how that matters from where the data is being sent. GENTRAN or SI. 

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

Original Message:
Sent: Mon June 30, 2025 09:17 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hi Vamsi,

I mean the process code which handles the idocs once created.

This is how an DESADV idocs looks when sending it to a SAP system from our SI:

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

Original Message:
Sent: Thu June 26, 2025 06:56 AM
From: Vamsi Kamisetty
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hey Manuel, 

I ran into the same issue with the E2 segments. I then started looking on the internet and there was a suggestion about changing the segments to E1. I then gave it a try and still nothing. When you mean by the standard SAP code, do you know if there is a function module involved or what standard are we talking about? 

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

Original Message:
Sent: Thu June 26, 2025 12:57 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

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

Hi Vamski,

please try to delete the 16 zeros in the field DOCNUM.

As you don't have the DOCNUM in the DC40 segment, you should not fill it in the segments. Or use the same number in all of them (which has to be used when you are sending more than one idoc in the same document).

Best regards

Manuel

Hello John, Thank you for the detailed information. I tried inputting the client record 010 on every segment and no luck. I am also attaching the ORDERS IDOC which is working fine and it doesn't have client record on every segment. I am attaching the DESADV idoc that isn't working even after updating the client record along with the error shown in the BP. 

Hi Vamsi,

I have seen this before.  It looks like you have an IDOC number in the control record, 010.  This needs to be on each of the segments as well. You can see that on Manuel's example.

The function module in SAP inputs the control record and the segments in separate tables. It then tries to match them up based on the IDOC number. It also works if you leave the IDOC number off the control record and segments and you are only passing 1 IDOC at a time.  Either way it needs to match.

Hello Manuel,

Am attaching the idoc I am trying to push into SAP. We are using the same BP that process ORDERS idocs into SAP which works fine. Not sure why the DESADV or SHPCON won't work. Our current application GENTRAN loads the same idoc generated out of SI without any issues. I compared the idoc side by side between GENTRAN and SI and they are identical. That's where the confusion is. We are using the same JCo for inbound and outbound documents. 

The process code in SAP is DELS for DESADV idocs and DELV for SHPCON idocs. No changes there. The process codes don't show up in the idoc on our side. The process codes have their own functional modeules in them but I don't see how that matters from where the data is being sent. GENTRAN or SI. 

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

Original Message:
Sent: Mon June 30, 2025 09:17 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hi Vamsi,

I mean the process code which handles the idocs once created.

This is how an DESADV idocs looks when sending it to a SAP system from our SI:

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

Original Message:
Sent: Thu June 26, 2025 06:56 AM
From: Vamsi Kamisetty
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hey Manuel, 

I ran into the same issue with the E2 segments. I then started looking on the internet and there was a suggestion about changing the segments to E1. I then gave it a try and still nothing. When you mean by the standard SAP code, do you know if there is a function module involved or what standard are we talking about? 

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

Original Message:
Sent: Thu June 26, 2025 12:57 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

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

Manuel, this suggestion looks promising. Let me make some changes and test. I will keep you posted in a few days. Much appreciate the help. 

Hi Vamski,

please try to delete the 16 zeros in the field DOCNUM.

As you don't have the DOCNUM in the DC40 segment, you should not fill it in the segments. Or use the same number in all of them (which has to be used when you are sending more than one idoc in the same document).

Best regards

Manuel

Hello John, Thank you for the detailed information. I tried inputting the client record 010 on every segment and no luck. I am also attaching the ORDERS IDOC which is working fine and it doesn't have client record on every segment. I am attaching the DESADV idoc that isn't working even after updating the client record along with the error shown in the BP. 

Hi Vamsi,

I have seen this before.  It looks like you have an IDOC number in the control record, 010.  This needs to be on each of the segments as well. You can see that on Manuel's example.

The function module in SAP inputs the control record and the segments in separate tables. It then tries to match them up based on the IDOC number. It also works if you leave the IDOC number off the control record and segments and you are only passing 1 IDOC at a time.  Either way it needs to match.

Hello Manuel,

Am attaching the idoc I am trying to push into SAP. We are using the same BP that process ORDERS idocs into SAP which works fine. Not sure why the DESADV or SHPCON won't work. Our current application GENTRAN loads the same idoc generated out of SI without any issues. I compared the idoc side by side between GENTRAN and SI and they are identical. That's where the confusion is. We are using the same JCo for inbound and outbound documents. 

The process code in SAP is DELS for DESADV idocs and DELV for SHPCON idocs. No changes there. The process codes don't show up in the idoc on our side. The process codes have their own functional modeules in them but I don't see how that matters from where the data is being sent. GENTRAN or SI. 

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

Original Message:
Sent: Mon June 30, 2025 09:17 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hi Vamsi,

I mean the process code which handles the idocs once created.

This is how an DESADV idocs looks when sending it to a SAP system from our SI:

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

Original Message:
Sent: Thu June 26, 2025 06:56 AM
From: Vamsi Kamisetty
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

Hey Manuel, 

I ran into the same issue with the E2 segments. I then started looking on the internet and there was a suggestion about changing the segments to E1. I then gave it a try and still nothing. When you mean by the standard SAP code, do you know if there is a function module involved or what standard are we talking about? 

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

Original Message:
Sent: Thu June 26, 2025 12:57 AM
From: Manuel Frank
Subject: Issue Posting Inbound DESADV IDoc via JCo Adapter - Segment Table Empty Error

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