How to configure ZERO Retry in AAE

[former_member399424]

Dear Experts,

We have a File to ECC(Idoc) scenario, where in we are doing an RFC lookup to get the sequence number.

For every input file we get from source system the sequence will be incremented by 1.

We are validating the Incoming sequence number with the RFC sequence number & will only process the file if both are equal else fail the message in PI.

Incase of message failure due to some data issue or due to sequence mismatch there is a RETRY happening which is incrementing the value by 1 for each retry there by causing the next file to fail due to sequence mismatch.

So please let us know how can we prevent this Retry

Note : The scenario is ICO based and we also have tried by changing the retry option to zero in RFC communication channel but still there is no luck as retry continues to happens for 3 times.

Thanks,

Mohammed

[Former Member]

Hi Farooq

,

The RFC channel is not part of the ICO, could be the reason the '0' retry mechanism not working.

Can you please let me know where exactly the increment counter logic is implemented ?

Thanks,

Dhanish

[former_member193386]

Go to your runtime workbanch page, access Adapter Engine - COmmunicaiton Channel moitoring

Select you CC and change the option in settings ( image above )

[former_member184720]

>>> changing the retry option to zero in RFC communication channel but still there is no luck as retry continues to happens for 3 times.

This should work. In fact we tested this on RFC adapter itself and i can confirm that it's still works for us.

May be try reactivating, i.e. set to default and the overwrite it to zero and see if that helps.

If not i would suggest you to contact SAP. Of course changing the design is always an option but i believe standard functionality should work.

[former_member399424]

Hi Hareesh,

Thanks for your reponse.

Just wanted to know from where have you taken the log (Screen shot) ? Is it from channel monitoring or Message monitoring ?

Thanks,

Mohammed

[former_member184720]

From Message monitoring..

But it doesn't really matter. Audit log should remains same for a specific message ID

[iaki_vila]

Hi Mohammed,

Following a similar Praveen suggestion i would change the scenario by FILE to Proxy. In the proxy code i would do a first validation in the code with the inbound data and if it would be correct a i would raise an IDOC call. In this way you can create a Z table to have in the ECC a custom log.

Regards.

[former_member182412]

Hi Mohammed,

To keep it simple why don't you do the validation in IDOC inbound processing (User Exit or Enhancement Spot), if the sequence number is not equal then you can fail the IDOC in ECC. This is just my idea i don't know is it going to fit into your requirement. If you go with this approach you can avoid RFC lookup and the problem you are facing.

Regards,

Praveen.