Skip to Content
0

IDOC to File Scenario has a mysetrious flowback

Jan 06, 2017 at 01:01 PM

127

avatar image

We have designed a IDOC to file scenario, triggered IDOC has been requested to get saved in a SFTP server. We see successful transaction for this with no issues. But we see a reverse flow say from Recevier to Sender for the IDOC triggerred

flowback-error.png

On the image, we see a successful transaction from BS_PRD_004 to Recv_A and Recv_B, but we see a back flow with Recv_A and Recv_B as sender and BS_PRD as receiver.

And on looking into the message trace we get a error message there is no proper receiver agreement found.

flowback-error-trace.png

And looking into the actual payload of the flowback message, we don't see anything in it

flowback-payload.png

We have checked similar configurations which do not behave in such a manner. Also while searching for solutions we did find the IDOC acknowledgement suppression in the following link

https://archive.sap.com/discussions/thread/125190

Which we don't think would help on this.

Can you please help us finding the cause of this flowback? Thanks in advance.

10 |10000 characters needed characters left characters exceeded

Is your scenario synchronous or asynchronous?

0

Hi Dan

Our scenario is Asynchronous.

0
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Ryan Crosby Jan 06, 2017 at 01:21 PM
1

Hi Aananda,

Have you checked the acknowledgement settings of your IDoc sender channel? That's the only reason I can think of for messages appearing to flow back to the sender. We have a few acknowledgement scenarios in our system and that is the only time we get that type of behavior in the message monitoring.

Regards,

Ryan Crosby

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Ryan

As sender is IDOC from ECC there will be no sender channel for this scenario.

Also I have checked the IDX_NOALE report on the specified port in our system, it has the following entries

idx-noale.png

Is that if we un-check all these we will not get the reverse flow?

Any other clues?

idx-noale.png (18.9 kB)
0

Hi Aananda,

Yes, that should stop the messages that come in the reverse flow completely.

Regards,

Ryan Crosby

0
Apu Das Jan 09, 2017 at 08:30 AM
0

Hi,

You have checked system/application acknowledgement in the sender idoc channel and is creating the response flow.

Thanks,

Apu

Show 4 Share
10 |10000 characters needed characters left characters exceeded

Hi Apu

As IDOC is sent from ECC to PI, we don't have a explicit IDOC sender channel. Any other clues?

0

You will have an IDoc Sender Channel in your scenario - as that is what will be receiving the idoc xml in order to pass it through your scenario. Perhaps you are getting confused with the terminology?

The communication channel that you are sending the IDocs to from ECC will have the direction of 'Sender' in the configuration.

IE:

ECC IDoc generated -> RFC to PI -> received by the Sender Communication Channel -> Operational/Message Mapping -> sent to target system by the Receiver Communication Channel.

So go to the communication channel that is the entry point of the IDoc into your integration scenario and check your adapter specific, ack settings.

Cheers, Dan

0

Hi Dan

We have dual stack system and used Receiver determination configured for this scenario (not an Integrated configuration). As dual stack system does not need a sender channel for IDOC, we do not have a IDOC sender communication channel in our configuration.

Let me know if wrong anywhere in my statement.

0

Ok thanks for the info. Can you post screenshots of your sender and receiver agreements , and also the interface mapping please. Your first screenshot appears to indicate your receiving interface is the same as the sending interface. I suspect you have maintained the incorrect target interface in your interface mapping.

0
Anoop Rai Jan 13, 2017 at 03:12 PM
0

Hi,

Specify Logical System for IDoc Adapter in Adapter-Specific Identifiers of receiver BS. This may error due to Ack.

Regards,

Anoop Kumar Rai

Share
10 |10000 characters needed characters left characters exceeded