Seeburger EDI to IDoc

[Former Member]

Hi,

The actual payload is not getting generated in the EDI to IDoc scenario.

The acknowledgment is getting generated.

What could be the possible error?

[Former Member]

Hi Anu,

Your question is a little vague can you please explain it a bit more. What do you mean by 'actual payload'?

what i am suspecting is your edifact to idoc is going fine; but you are not able to see either of the following:

1) EDIFACT incoming Message in EDIFACT format

2) EDIFACT - XML

Please advise

regards

[Former Member]

EDI to IDoc is not happening.

However the acknowledgement is getting triggered back to EDI.

The message in MONI is showing only the acknowledgment and the classifierAtt1 ( application/xml ) but not the actual payload of the EDI message.

We have specified the EDI BIC module parameters and all.

[sbuttler77]

Anu,

is your mapping determined automatically or are you explicitly stating the mapping name in your

module configuration?

If you set mappingName to Auto BIC tries determine the correct mapping by looking at the

the UNH segments, e.g. UNH1ORDERS:D:97A:AA'. If your mapping has been labeled

differently in the Mapping Designer, for instance E2X_ORDERS_UN_D97A the system

won't be able to find the mapping and therefore you won't get any payload.

As I suggested before try using the parameter u2018logAttIDu2019 Value u2018ConverterLogu2019 in your

module chain that will most likely tell you what the problem is.

Sven

Edited by: Sven Buttler on Jul 9, 2010 10:26 AM

[Former Member]

Anu,

Run the EDI file through BIC mapper in the Test environment. check whether the EDI file is valid. if EDI gets converted to EDI XML then go to the next step and try to debug your module configuration in communication channel.

Thanks,

Pavan

[Former Member]

Hi Anu,

Did you verified your configuration ...if not please cross check with the below blog of mine.

/people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster

HTH

Rajesh

[sbuttler77]

Add this to your module chains BIC configuration it will tell you what the problem is.

Parameter u2018logAttIDu2019 Value u2018ConverterLogu2019

[peter_wallner2]

Hello Anu,

I don't know what you mean by "acknowledgment".

But maybe you forgot to set the BIC-mapping parameters under "Module" in your communication channel?

You get the payload in EDIFACT format right? Then you need to generate that to EDIFACT XML and that you can message map in XI.

Best regards,

Peter