Can not find Segment Elements for messageVersion

[Former Member]

Hi All,

I am developing below screnario

IDOC--PI--AS2(7.31)

while testing I am getting below error.

0}: The module-paramteter "eancom.subversion.prefix" is not set. Using default value "false"

0}: The module-paramteter "eancom..audit" is not set. Using default value "false"

MP: exception caught with cause com.sap.aii.af.lib.mp.module.ModuleException: Can not find Segment Elements for messageVersion 96A, message subversion EAN007, message agency UN, segment S_CPS, newFirstlevelElement D_7164, currentIndexLevel1 0

Exception caught by adapter framework: Can not find Segment Elements for messageVersion 96A, message subversion EAN007, message agency UN, segment S_CPS, newFirstlevelElement D_7164, currentIndexLevel1 0

Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.lib.mp.module.ModuleException: Can not find Segment Elements for messageVersion 96A, message subversion EAN007, message agency UN, segment S_CPS, newFirstlevelElement D_7164, currentIndexLevel1 0

Thanks

Prem

[saurabhkumbhare]

Hi Prem,

Please check '

1.if messageVersion 96A, message subversion EAN007 exists in the content delivered by SAP.

In the standard content that I have on my system, i do not have EAN007. Do you see EAN007 in the drop down.

2.check if segment CPS exists in this message version.

If you dont see EAN007, create a new control key having EAN007.

Adjust your TPM Agreement and Control key association to match this new control key.

Regards

Saurabh

[Former Member]

Hi Saurabh,

If you don't see EAN007, create a new control key having EAN007.

I am not able see EAN007.please find the attached screenshot.

Adjust your TPM Agreement and Control key association to match this
new control key.

How to Adjust your TPM Agreement and Control key association to match
this new control key?

My scenarios is outbound interface (DESADV-->PI--AS2)and how it is related to TPM Agreement and Control key association. Could please suggest what is the importance of both. How it works in background.

Thanks,

Prem

[saurabhkumbhare]

Hi Prem,

Before elaborating on the steps, on how to create EAN007 can you please answer 2 questions :

1.Does EAN005 and EAN006 contain all the fields that the customer is expecting? In other words, Is there any field that is only available in EAN007 but not available in EAN005 and EAN006 - Yes / No

2.Does the end customer want EAN007 in the UNH ? - Yes / No

Thanks

Saurabh

[Former Member]

Hi Saurabh,

1.Does EAN005 and EAN006 contain all the fields that the customer is expecting? In other words, Is there any field that is only available in EAN007 but not available in EAN005 and EAN006 - Yes / No

Could you please explain for me, if Yes and No for both cases.

2.Does the end customer want EAN007 in the UNH ? - Yes / No

Could you please explain for me, if Yes and No for both cases.

Thanks,

Prem

[saurabhkumbhare]

Hi Prem,

1.A If yes, you can copy the message EAN005 / EAN006 to EAN007. There are defined steps which you need to follow which i can explain. Basically you should modify the backend tables if you are using SP3.. If you are on SP4, i guess it is much easier.I am on SP3.

1.B If No, then you can either raise OSS call to SAP and ask them to provide the content for EAN007. Alternatively you can again edit the backend tables.

2.A, If yes,there is no option for you but to create EAN007 message either manually or ask SAP. Once this is done, apply the note 2077700 and B2BToolkit SP03 Patch#15 because while sending custom outbound messages it will fail in the adapter.

2.b If no, it mean customer does not want EAN007 and you can use EAN005 or EAN006

Thanks

Saurabh

[saurabhkumbhare]

Sorry, but cant create a detailed guide for you for each Yes and NO case due to time constraints at my end.

[Former Member]

Hi Saurabh,

Thanks for your help.

Currently we are using SP3.

As per above suggestions we need to do modify backend tables manually if we raise OSS note to SAP.

As soon as they are going to upgrade SP4.What are the steps we need to do SP4.

Thanks

Prem

[saurabhkumbhare]

Hi Prem,

I have not used SP4 since it was released few days back.

You need not modify backend tables if you raise an OSS call to get the EAN007.

Thanks

Saurabh

[Former Member]

Hi Saurabh,

Could you please suggest me,what is the importance of Control key association and how it is related in background.

Thanks

Prem

[saurabhkumbhare]

Hi Prem,

You can get a very good understanding at the link below :

Thanks
Saurabh

[Former Member]

Hi Saurabh,

Why we need Control key association?

Thanks

Prem

[saurabhkumbhare]

Hello Prem,

Can you please open another thread so that I can answer this.

We have to put solutions in this thread so that others can benefit.

Thanks

Saurabh

[ruchir_sinha]

Hi Prem,

As I had mentioned you in the mail. You need to maintain proper scenario association for your XML to EANCOM. Please check other issues happening if proper association is not maintained.

Regards,

Ruchir

[Former Member]

Hi Dimtri,

Please find the input payload.

<?xml version="1.0" encoding="UTF-8"?>

<DESADV01>

   <IDOC BEGIN="1">

      <EDI_DC40 SEGMENT="1">

         <TABNAM>EDI_DC40</TABNAM>

         <MANDT>001</MANDT>

         <DOCNUM>000000009999999</DOCNUM>

         <DOCREL>777</DOCREL>

         <STATUS>30</STATUS>

         <DIRECT>1</DIRECT>

         <OUTMOD>2</OUTMOD>

         <IDOCTYP>DESADV01</IDOCTYP>

         <MESTYP>DESADV</MESTYP>

         <STDMES>DESADV</STDMES>

         <SNDPOR>SAPERT</SNDPOR>

         <SNDPRT>LI</SNDPRT>

         <SNDPRN>BBBB</SNDPRN>

         <RCVPOR>B000000999</RCVPOR>

         <RCVPRT>KU</RCVPRT>

         <RCVPFC>ZZ</RCVPFC>

         <RCVPRN>0000444444</RCVPRN>

         <CREDAT>20101102</CREDAT>

         <CRETIM>163706</CRETIM>

         <EERIAL>20101102160122</EERIAL>

      </EDI_DC40>

      <E1EDK07 SEGMENT="1">

         <ACTION>000</ACTION>

         <VBELN>6666666666</VBELN>

         <NNNO1>PIP</NNNO1>

         <NNNO2>.</NNNO2>

         <RRRRR>ESS928</RRRRR>

         <EEEEE>XXXX-X XXXXXX XXXX XXX</EEEEE>

         <DDDDD>Z1</DDDDD>

         <SSSSS>EES1</SSSSS>

         <KKKKK>XX.XX XXXXX XXXX</KKKKK>

         <VKORG>SES1</VKORG>

         <SSSSS>00001111111</SSSSS>

         <E1EDKA1 SEGMENT="1"/>

         <E1EDK03 SEGMENT="1"/>

      </E1EDK07>

      <E1EDK08 SEGMENT="1">

         <ACTION>000</ACTION>

         <VBELN>5555555555</VBELN>

         <NNNO1>PIP</NNNO1>

         <NNNO2>.</NNNO2>

         <ZZZZZ>ESS999</ZZZZZ>

         <EEEEEZ>XXXX-X XXXXXX XXXX XXX</EEEEE>

         <SSSED>ZZ</SSSED>

         <VVVVV>EEE1</VVVVV>

         <KKKKK>XX.XX XXXXX XXXX</KKKKK>

         <VKORG>SES1</VKORG>

         <VTWEG>01</VTWEG>

         <E1EDS01 SEGMENT="1">

            <SUMID>009</SUMID>

            <SUMME>1</SUMME>

         </E1EDS01>

         <E1EDS01 SEGMENT="1">

            <SUMID>021</SUMID>

            <SUMME>21.208</SUMME>

            <SUNIT>GGG</SUNIT>

         </E1EDS01>

         <E1EDS01 SEGMENT="1">

            <SUMID>022</SUMID>

            <SUMME>22.222</SUMME>

            <UUNIT>GGG</UUNIT>

         </E1EDS01>

         <E1EDS01 SEGMENT="1">

            <SUMID>023</SUMID>

            <SUMME>21.208</SUMME>

            <UUNIU>KGM</UUNIU>

         </E1EDS01>

         <E1EDKA2 SEGMENT="1">

            <PARVW>WE</PARVW>

            <PARTN>0000888338</PARTN>

            <LIFNR>00008883389999</LIFNR>

            <NAME1>SS XXXXX XXXXXX, X.X.</NAME1>

            <NAME2>-YYYY-</NAME2>

            <STRAS>XX XXXX, XX-XX</STRAS>

            <ORT01>XXXXXX</ORT01>

            <PSTLZ>28009</PSTLZ>

            <LAND1>ES</LAND1>

            <SPRAS>S</SPRAS>

            <HHHSN>000000</HHHSN>

            <REGIO>28</REGIO>

         </E1EDKA2>

         <E1EDKA2 SEGMENT="1">

            <PARVW>GG</PARVW>

            <PARTN>0000888338</PARTN>

            <LIFNR>00001883381111</LIFNR>

            <NAME1>XX XXXXX XXXXXX, X.X.</NAME1>

            <NAME2>-YYYY-</NAME2>

            <STRAS>XX YYYY, XX-XX</STRAS>

            <ORT01>SSSSSS</ORT01>

            <PSTLZ>289999</PSTLZ>

            <LAND1>ES</LAND1>

            <SPRAS>S</SPRAS>

            <HHHSN>000000</HHHSN>

            <EEGIG>28</EEGIG>

         </E1EDKA2>

         <E1EDK06 SEGMENT="1">

            <IDDAT>111</IDDAT>

            <DATUM>11166633</DATUM>

         </E1EDK06>

         <E1EDK06 SEGMENT="1">

            <IDDAT>035</IDDAT>

            <DATUM>11166633</DATUM>

            <UHHHH>000000</UHHHH>

         </E1EDK06>

         <E1EDKT3 SEGMENT="1">

            <TDID>Z000</TDID>

            <TSSSSSS>S</TSSSSSS>

            <E1EDKT4 SEGMENT="1">

               <DDLIND>XXXXX : 000, XXXX. : 000</DDLIND>

            </E1EDKT4>

         </E1EDKT3>

         <E1EDP07 SEGMENT="1">

            <BSTNK>78559555</BSTNK>

            <BSTDK>20100624</BSTDK>

            <VBELN>3202814444</VBELN>

            <VGBEL>3001165719</VGBEL>

            <VGPOS>000001</VGPOS>

            <VGTYP>C</VGTYP>

            <BSSSS>02</BSSSS>

            <ABRDT>00000000</ABRDT>

            <E1EDP09 SEGMENT="1">

               <VBELN>3202814444</VBELN>

               <POSNR>000009</POSNR>

               <MATNR>000000000000009999</MATNR>

               <WERKS>EEEE</WERKS>

               <LGORT>0001</LGORT>

               <LFIMG>7.000</LFIMG>

               <VRKME>CCC</VRKME>

               <BBGEW>22.222</BBGEW>

               <TTGEG>22.222</TTGEG>

               <EEWEI>XXX</EEWEI>

               <VOLUU>0.162</VOLUU>

               <VOLLL>MTQ</VOLLL>

               <XXXXX>200/00 XXX XXX55X YYY XX XX</XXXXX>

               <EANNR>1111111111111</EANNR>

               <TTTTT>00000000</TTTTT>

            </E1EDP09>

         </E1EDP07>

      </E1EDK08>

      <E1EDS02 SEGMENT="1">

         <SUMID>001</SUMID>

         <SUMME>1</SUMME>

      </E1EDS02>

   </IDOC>

</DESADV01>

Thanks

Prem

[Dimitri]

Hi Prem,

How is your message mapping created? And your AS2 receiver?

What about the Integration Cockpit settings?

Also, I saw your other threads. Please make sure your configuration is OK.

Kind regards,

Dimitri

[Former Member]

Hi Dmitri,

There is no issue with message mapping,it is working fine.
I have given modules also in module tab.

regarding cocpit,we are using SP3 and other interfaces it is working fine only for DESADV getting  error.

Thanks

Prem

[Dimitri]

bottom line is that your adapter does not recognize the message type and version.

How did you do the filling? In the message mapping?

Can you provide the XML, offered to the adapter. So, just before converting to EDI.

Also, please provide the AS2 adapter configuration.

Thanks

Dimitri