cancel
Showing results for 
Search instead for 
Did you mean: 

SAP PI Sender NFS channel error (Seeburger BIC mapping)

former_member585940
Participant
0 Kudos

Hi Experts,

We are facing one error while using sender NFS channel.

I ll explain the scenario and error:

It is related to EDI files. We are picking the edi files from PI application server and that file contains multiple UNH.

So, it will be splitted at seeburger BIC mapping level.But we had to avoaid it because of specific requirement.

To avoid it, we did not maintain any splitter entry and maintained everything in Channel module parameter i.e. BIC Mapping name, EDI type and all.

The files are getting processed without UNH split and everything is ok.

Now the issue is, if one file is getting failed at BIC mapping level, lets say if amount is too larger and BIC mapping can not handle it.

The NFS channel will not pick the other file until this file is not processed.

So, it is blocking the whole interface.

I tried using archive Archive Faulty file also, but it didn't work.

Is there any different way to define archive faulty file?

I would really appreciate your quick response.

Thanks,

Vikram

Accepted Solutions (1)

Accepted Solutions (1)

S0003485845
Contributor
0 Kudos

Hi Vikram,

this issue is related to the design of how the PI-Channels work, which means that the process only is successfull if the complete module-chain can be executed successfully. Otherwise the whole task of pickung up the file is rolled back again...and PI tries to pick the file again after some seconds (whatever retry time is setuo) .... and therfor there will always be this "Looping" - Situation.

=> This is the reason, why Seeburger has implemented the "Recovery-Functionality" in the EDI-Adapters to avoid this behaviour in EDI-scenarios.

Also the BIC has been designed in a way '(with the Splitter) to handle syntax errors in the data without blocking a channel.

As a work-around for the channel behaviour, you could try the following 2 ways:

1.

- remove the module-chain steps from your Sender Channel and pick up the file without any conversion

- route the file to a Receiver NFS-Channel and include your mapping there (so if the mapping fails there it has no impact on any other file)

- pick up the translated XML-Data with another Serner-Channel and process it.

2.

maybe you can also try to use the typical setup (Classifier, BIC,Split)... but use the option

split=false

and verify if this way the BIC itself handles the wrong data

(while you still have one big file)

KInd Regards

Stefan

former_member585940
Participant
0 Kudos

Hi Stefan,

Thanks for your response.

And yes,it makes sense now.

I have used the other solution to avoid this sender channel error.

I just wanted to know if there was any solution for this.

Regards,

Vikram

Answers (1)

Answers (1)

former_member184720
Active Contributor
0 Kudos

Hi Vikram - What is the quality of service configured in your sender channel?

If it is EOIO- try changing it to EO and see if that helps..

former_member585940
Participant
0 Kudos

Hi Hareesh,

I have tried with EO as well as best effort but it didn't work.