SAP AEM requirement and guidance

[ramu_g4]

Hi Experts,

We have requirement where when ever "Material Number" is getting updated on sender system(we) then event should be sent with only "Material Number" to receiver partner system.. Then the receiver partner system makes an API call with "Material Number" value as input to us(sending system) and then as a response to that API call updated price info(plus other fields) should be sent back as API response..

In this case, Advanced Event Mesh(AEM) comes in to picture only in case of sending "Material Number" when ever there is a change right? Does sending notification event makes sense when there is only one field value to be sent to the partner system? Should we choose Notification event over data event in this case? I have experience on configuration of Queues/topics in AEM for Data event but not for notification event..  Could you please let me know if there is any difference in terms of configuration in AEM for Data Vs Notification event?

Also most importantly, should we ask receiving partner system to develop an API on their side to consume the "Material Number" value (or) should they pull and consume the data via AMQP protocol? (or) what do you propose in this scenario to establish stable interface which is cost minimal solution as well?

Regards!

[sivaramaraju_danthuluri]

HI Ramu,If Partner needs only one field ,May be we can use AEM-->CI(format the data based on requirement) -->partner APi call So we no need to ask him for Modification r

[Vidyadhar_Kothekar]

Hi Rama - some of your questions are easy to answer whereas others need further exploration / thinking. For example, there is no difference from AEM perspective whether you are sending a data or notification event. AEM can carry both. Regarding partner consuming the event using AMQP, it is possible and in that case it is better you send out a full data event instead of notification event. It really depends on what you want to achieve. If you don't want your partner to call S4 then use data event - that's my favourite approach as it reduces the chatter between S4 and consumer application and also reduces query load on S4. Hope this helps.