EDIFACT/EANCOM problem

[Former Member]

Hi Experts,

We have B2B SP 03 installed and imported the EDIFACT B2B
tables.

We were processing inbound and outbound EDIFACT messages
with EANCOM message formats like EAN006, EAN008, etc. without any problems.

The EDIFACT converter module was used and in channel the
EDIFACT protocol was used.

To check something else, we uploaded the EANCOM B2B tables.
But from that point the edifact module is throwing exception saying no control
key association.

It tries to find the control key for EANCOM.

I understand that we can sort it out by setting the Control
key scenario association but the EANCOM content does not have all the versions
that are needed.

How to make the EDIFACT Converter module process the EDIFACT messages as before to process them just as EDIFACT instead of EANCOM.

In fact, I have deleted the B2B tables content related to EDIFACT and EANCOM messages and reloaded the EDIFACT SP 03 content again, but
no luck.

Thanks.

Regards,

Sudharshan N A

[Former Member · Accepted solution]

Hi Ruchir,

Error at Inbound-

Searching sender
channel for Eancom message part message with Message type ORDERS, Message
version number D, Message release number 96A, Interchange sender identification
xxxxxx, Interchange sender identification code qualifier 14, Interchange recipient
identification xxxxxx, Interchange recipient identification code qualifier 14,
Message Subversion EAN008, Message Agency UN

I have a EDISeparator Sender channel for Order D 96A accepting all Sender/Receiver IDs with EDIFACT as message protocol.

Error at Outbound-

Cannot find a matching configuration for sender party "", service etc in
B2B_EDI_CTRL_IF

I have control key scenario association for EDIFACT only in B2B_EDI_CTRL_IF.

I have no EANCOM content and scenario key association now.

If I even add scenario association for EANCOM it complains that cannot find the Message Version.

All these were working before the EANCOM content upload. I have manually deleted the tables from EDI Content Manager and uploaded the EDI content one more time.

Thanks.

Regards,

Sudharshan N A

[ruchir_sinha · Accepted solution]

Hi Sudharshan,

You are using ORDERS 96A, Subversion EAN008. The EANCOM which SAP ships contains ORDERS 96A with both subversion EAN008, EAN009.

Once you import this successfully then the scenario should execute. Your EDI Separator sender channel should be selected for EANCOM. Your scenario association should be correctly defined. Please try to convert your payload from the B2B Integration cockpit UI. EANCOM-XML conversion. If the conversion works fine there then it should be able to convert in the actual scenario.

Also, you have mentioned that you deleted EANCOM from the EDI Content manager. My guess is that the all the entries were not deleted from the tables.

My suggestion is to import the EANCOM content and then proceed. You can share the payload and the configuration scenario along with the scenario association UI if you are still not able to proceed.

Best Regards,

Ruchir

[Former Member · Accepted solution]

Hi Ruchir,

For ORDERS its fine.

But I have transactions like INSDES where the major version D98B is not available in EANCOM and is available in EDIFACT and was working perfectly before the import.

That's why I want to use only EDIFACT and not EANCOM as message Protocol.

You mentioned if the EAN subversion is not present, it would fall back to EDIFACT. Does it apply main version also (say D98B)

Thanks,

Sudharshan N A

[ruchir_sinha · Accepted solution]

HI Sudharshan,

Yes you are correct. INSDES is not present for D98B. Could you let me know what is the subversion for the INSDES payload which you are using. Also, if possible I request you to share the payload with me so that I can check on our systems. If you are not willing to put the payload on SCN then you can mail it to me "ruchir.sinha@sap.com".

Best Regards,

Ruchir

[Former Member · Accepted solution]

Hi Ruchir,

I have attached the payload out of mapping in case of a outbound scenario.

Version - INSDES 98B and EAN 006.

Interestingly the payload works in EDIFACT XML to EDI converter in B2B Cockpit.

But at runtime EDIFACT Converter Module detects the format as EANCOM and looks for the Control Key Scenario association of EANCOM. I find it bit strange.

Any thoughts.

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

<ns0:INSDES98B xmlns:ns0="http://test">

   <S_UNA>:+.? &apos;</S_UNA>

   <S_UNB>

      <C_S001>

         <D_0001>UNOC</D_0001>

         <D_0002>3</D_0002>

      </C_S001>

      <C_S002>

         <D_0004>11114</D_0004>

         <D_0007>14</D_0007>

      </C_S002>

      <C_S003>

         <D_0010>222222</D_0010>

         <D_0007>14</D_0007>

      </C_S003>

      <C_S004>

         <D_0017>140620</D_0017>

         <D_0019>1531</D_0019>

      </C_S004>

      <D_0020>200</D_0020>

   </S_UNB>

   <M_INSDES>

      <S_UNH>

         <D_0062>1</D_0062>

         <C_S009>

            <D_0065>INSDES</D_0065>

            <D_0052>D</D_0052>

            <D_0054>98B</D_0054>

            <D_0051>UN</D_0051>

            <D_0057>EAN006</D_0057>

         </C_S009>

         <D_0068>0000000894</D_0068>

      </S_UNH>

      <S_BGM>

         <C_C002>

            <D_1001>351</D_1001>

            <D_3055>9</D_3055>

            <D_1000>101</D_1000>

         </C_C002>

         <C_C106>

            <D_1004>7100006532</D_1004>

         </C_C106>

         <D_1225>42</D_1225>

      </S_BGM>

      <S_DTM>

         <C_C507>

            <D_2005>137</D_2005>

            <D_2380>20140612</D_2380>

            <D_2379>102</D_2379>

         </C_C507>

      </S_DTM>

            <S_UNS>

         <D_0081>S</D_0081>

      </S_UNS>

      <S_CNT>

         <C_C270>

            <D_6069>2</D_6069>

            <D_6066>2</D_6066>

         </C_C270>

      </S_CNT>

      <S_UNT>

         <D_0074>1</D_0074>

         <D_0062>1</D_0062>

      </S_UNT>

   </M_INSDES>

   <S_UNZ>

      <D_0036>1</D_0036>

      <D_0020>200</D_0020>

   </S_UNZ>

</ns0:INSDES98B>

Many Thanks,

Sudharshan N A

[ruchir_sinha · Accepted solution]

Hi Sudharshan,

Thanks for sending the payload. I checked the issue which you are reporting. The UI conversion works on SP3 because you are explicitly telling which control key to be used. If you try this payload in EANCOM screen it won't work.

I request you to create an OSS message with SAP and we will look into it.

Best Regards,

Ruchir

[Former Member · Accepted solution]

Hi Ruchir,

Thanks.

We have created incident : 0000689142 to SAP.

But no response yet.

Best Regards,

Sudharshan N A

[Dimitri · Accepted solution]

Hi,

Did you get any feedback from SAP in the meantime?

If yes, please do update this thread to share the solution with the community.

Thank you.

Dimitri

[Former Member · Accepted solution]

Hi,

The solution is provided in this thread,

http://scn.sap.com/thread/3599098

So we have decided to process them as EDIFACT message instead of EANCOM since the customers treat them as EDIFACT messages (as per the agreement).

Thanks.

Regards,

Sudharshan N A

[ruchir_sinha]

HI Sudharshan,

What is the error which you are getting. If an EANCOM subversion is not found the control falls back EDIFACT and then the execution takes place. So ideally your file should get processed.

Best Regards

Ruchir

[Former Member]

Hi Ruchir ,

I am facing same issue .

Message should get processed as EDIFACT . But Sender is not identified when UNH segment is carrying "EAN008" subversion . On removing EAN008 from UNH segmenet message gets processed successfully .

Any hint ?

Regards ,

SR .