EDI 997 acknowledgement error

[#1]

Hi Experts,

I am working on EDI 945 to JDBC.

for this scenario, i need to send 997 back to customers for each 945.

I have craeted EDI 945 to JDBC, its working fine. File sender and i have added classifier, BIC and split modules in file sender communicatoon channel. Its working fine.

For acknowlegements, used standard mapping "FunctionalAcknowledgement_to_A_997_ALL / http://seeburger.com/B2BContent"

Created ICO with Split997 sender and file reciver.

Problem is i am not getting 997, can you pls help on this. What i have missed to configure.

Thank you.

[nabendu_sen]

Hi Sruthi,

Please cross check with below documents to ensure all the configurations are in proper place:

Regards,

Nabendu.

[Former Member]

Hi Nabendu,

Thanks for your reply.

Unfortunately my SAP PI is 7.3 dual stack not B2B add on.

Any other guess?

Thank you.

[nabendu_sen]

Hi Sruthi,

Cross check the adapter modules in the below thread:

Regards,

Nabendu.

[Former Member]

Hi Nabendu,

Thanks for your reply.

Still i am not able to see 997. for testing purpose i have created below.

Two File sender channels i have configured, one for sending 945 (used classifier, bic an dsplit modules), another sender channel is split 997 configured module tab as per your screen shot.

Two File receiver channels, one for getting JDBC xml, another for getting 997 back.

EDI 945 to JDBC working fine, i can see file in target directory.

Why split 997 is not responding, its not throwing error also... pls help where i have missed. All i am testing locally, two business components configured, its not party based.

Thank you.

[nabendu_sen]

Hi Sruthi,

You should use Split Adapter. Please find the configurations and adapter types in the below document:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ac...

Regards,

Nabendu.

[Former Member]

Oh..Yes..I have used split adapter only... mistype in my previous post

Adapter Type: Split997

[Former Member]

I have followed below link, still no luck.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ac...

[engswee]

Hi Sruthi

Did you use AUTO for your mappingName in the BIC module? Also, have you configured the message splitter in the Seeburger Workbench?

Did you check the audit log from your original source message? Was there any indication there if the split was successful? Maybe the split was successful, but the intermediate FA message generated had some errors?

Also, would be good if you can provide screenshot of your module configuration here.

Rgds

Eng Swee

[Former Member]

Hi Eng,

Thanks for your reply.

can you provide your mail id, so that i can send the document with all details. module screen shot and audit log.

Thank you.

[Dimitri]

Hi,

Check your module names. It should be like this

Especially check the Seeburger modules names. They are case sensitive an must be 100% correct.

Also, have a look at the classifierMappingID. Within that mapping, you create your child mapping at runtime. We did something like this in the parent mapping:

I guess you also created a adapter type Split997 like this to be able to split incoming EDI interchanges?

Finally, do not forget to fill the Seeburger Message Splitter configuration part in the Seeburger Workbench and create the Sender Agreement(s) accordingly.

Kind regards,

Dimitri

[Former Member]

Hi Dimitri,

Thanks for your reply.

These modules should be in file sender channel for 945 right, not in split 997 adapter right?

I guess you also created a adapter type Split997 like this to be able to split incoming EDI interchanges?

Yes

I have done seeburger Message Splitter configuration in Seeburger Workbench .

If I specify mapping name as "AUTO", i am not getting proper output like i am getting target xml as

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

<ns0:MT_Receiver xmlns:ns0="Namespace">

</ns0:MT_Receiver>

If i specify mapping name as "E2X_945_V4010", i am getting proper output like below

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

<ns0:MT_Receiver xmlns:ns0="Namespace">

<Statement><up_CFI_InsertEDIShipment action="EXECUTE"><Order_Number isInput="true" type="CHAR">ORD04</Order_Number><Delivery_Number isInput="true" type="CHAR">DEL04</Delivery_Number><Origin_Name isInput="true" type="CHAR">3063</Origin_Name><Origin_Code isInput="true" type="CHAR">3063</Origin_Code><Shipped_Datetime isInput="true" type="CHAR">20130903141738</Shipped_Datetime><Seal_Numbers isInput="true" type="CHAR">5851-5852-5853-5854</Seal_Numbers><Mode_Code isInput="true" type="CHAR">RAIL</Mode_Code><Manual_Carrier_Desc isInput="true" type="CHAR">CSXT</Manual_Carrier_Desc></up_CFI_InsertEDIShipment></Statement></ns0:MT_Receiver>

Any idea why its happening?

Thank you.

[Former Member]

Hi Dimitri,

I have configured as you mentioned, still no luck.

Splitt 997 adapter not polling any message it's just in active status thats all.. what will be the reason?

Thank you.

[engswee]

Hi Sruthi

It's better if you just share the screenshots in this thread instead of mailing it. The forum supports that capability (as shown by the replies from others here) and other members can also look into the issue and provide assistance.

Rgds

Eng Swee

[Dimitri]

Hi,

Like Eng Swee already mentioned, please do share your configuration using screen shots.

The modules I mentioned must be in the sender adapter picking up the EDI interchanges.

Also, make sure the sender agreement matches the Seeburger splitter configuration.

Kind regards,

Dimitri

[engswee]

Btw, if you don't use AUTO, then no FA will be generated, therefore which explains why you are not getting your 997 too.

My guess is your scenario is not designed correctly, if my guess is correct, you are doing the following:-

Sender 945 channel (BIC mapping with E2X_945_V4010) --> Message Mapping (Map 945 to JDBC structure) --> JDBC channel

This approach will not generate any 997 since you are not using AUTO.

Please do check the document Nabendu provided, as well as your Seeburger manual for proper setup required to achieve FA/997.

To get it to work, you need two configurations, it should be roughly like below:-

i) Parent message

Sender 945 channel (BIC mapping with AUTO) --> Message Mapping (Map FA structure to 997 structure) --> back to originator (with BIC mapping to convert to 997 EDI)

ii) Child messages

Splitter channel --> Message Mapping (Map 945 to JDBC structure) --> JDBC channel

Rgds

Eng Swee

[Former Member]

Hi Dimitri / Eng,

Thanks for your reply.

I will try to re create the objects as per link provided by Nabendu.

Mean while, I got one doubt, we are using custom 945, not standard one.

So is module will send the 997 back to custom EDI 945 as well or is there any restrictions to it?

Thank you.

[Former Member]

Hi Experts,

We have seeburger license , I am working on EDI 945 scenario, the thing is we did not purchase EDI 945 standard from seeburger, we have used custom one.

Now i am using File adapter with classifier, BIC and split modules to convert EDI 945 to xml structure.

It's not executing operation mapping if i use AUTO in mappingName parameter.

So all this because of custom EDI 945?

We are doing EDI 850 to Idoc with the same modules and its working fine, getting 997 back, EDI 850 is standard structure from seeburger. So EDI 850 is working since its a standard and EDI 945 is not working since its a custom. is it correct?

Thank you.

Modules i have used for EDI 945 is below.