cancel
Showing results for 
Search instead for 
Did you mean: 

Suppress acknowledgement for specific scenario - not for whole message type

JaySchwendemann
Active Contributor
0 Kudos

Hi all,

I have a scenario IDoc (ECC) --> PI --> File (Third party)

I would like to know if there's a way to suppress IDoc acknowledgement on a scenario basis. I know I can use report IDX_NOALE but this gives me only the options to suppress acknowledgement on basis of Port, Client, Message Type. I have, however other scenarios that use the same port, same client and same message type that should receive acknowledgements (because receiver is able to send application acknowledgements).

Do I have a chance to accomplish this?

Thanks and kind regards

Jens

Accepted Solutions (1)

Accepted Solutions (1)

former_member223322
Active Participant
0 Kudos

The best option would be to use the Ztype of your message type and then filter it in IDX_NOALE report in PI system.

This is a also a good option if you use the same message type for multiple receivers.

~Srini

JaySchwendemann
Active Contributor
0 Kudos

Thanks Srini,

this would definitely be an option. However I was hoping to get this settled on PI side because ECC guys would probably not be happy with creating a Z-Type just for the sake of suppressing acknowledgements.

@Srinivasan_R: Thanks, will resort to this if nothing else is applicable.

@All: Any other thoughts.

Cheers

Jens

former_member190624
Active Contributor
0 Kudos

Hi Jens,

AFAIK , there are no other options (as you are using ALEAUD Idocs for other scenarios). Why you want to disable/ suppress the ALEAUD (acknowledgement idocs ) ? Any error you are facing ?

Regards

Hari.

JaySchwendemann
Active Contributor
0 Kudos

Thanks Hari,

the reason why I want to disable / suppress ALEAUD for specific scenario is that depending on how the ECC guys set up distribution model / partner profile the outbound IDocs (INVOIC02) that reach PI have some partner number like 12345 and being of partner type KU. The ALEAUD that would get created automatically at SAP PI if I don't suppress it would not be able to be processed because of "EDI: Partner profile inbound not available". But this problem then maybe could be addressed differently.

So there may be two ways to takle this problem:

1. Suppress ALEAUD for specific scenario

2. Have ALEAUDs for the whole port / client / message type and get rid of the "EDI: Partner profile inbound not available" problem.

I would be glad to hear any further suggestions on this.

Thanks a bunch

Jens

former_member190624
Active Contributor
0 Kudos

Hello Jens,

2nd option will be best approach, Just include ALEUD message type as inbound idoc in PI partner profile (in ECC) and reprocess the ALEAUD Idocs. This should solve the issue.

Regards

Hari.

Answers (1)

Answers (1)

ambrish_mishra
Active Contributor
0 Kudos

Hi Jens,

I suggest you touch base with the ABAP specialist to explore if you could stop acknowledgement through user exit enhancement. Basically the idea would be to suppress the acknowledgment if it is from a particular sender(s).

Hope it helps!

Ambrish

JaySchwendemann
Active Contributor
0 Kudos

Hi Ambrish,

do you mean that I could stop acknowledgement from being created by using user exit in ECC system? Or would this to be happen in PI system?

Thanks

Jens

ambrish_mishra
Active Contributor
0 Kudos

Hi Jens,

Since the acknowledgement is being generated by ECC, you need to enhance the user exit to suppress it for certain scenarios.

Cheers,

Ambrish

JaySchwendemann
Active Contributor
0 Kudos

Hi Ambrish,

Correct me if I'm wrong, but the ALEAUD IDoc is generated in PI (if receiver system does not support applicatoin acknowledgements) or in third party system (if receiver system does support application acknowledgements). The ALEAUD IDoc is not generated in ECC. ECC is sender of the original IDoc (in our case it's an INVOIC IDoc).

To be clear: problematic scenario is

IDoc (ECC) --> PI --> File (Third party)

There could (not yet in place but may be in place some time) be also a scenario like this

IDoc (ECC) --> PI --> IDoc (Third party or in-house SAP System or System capable of processing IDocs)

So in my understanding ECC is never going to create the ALEAUDs. What do you then mean by?

Since the acknowledgement is being generated by ECC

Do you mean that the actual acknowledgement of the INVOIC IDoc is created in ECC out of the ALEAUD (which definitely isn't created in ECC) or did we missunderstand each other?

Thanks a bunch

Jens