AIF and ECH integration not working properly

[js2]

When specifying ECH as the Interface Engines in /AIF/CUST we can link in service interface errors that use ECH/PPO and view the errors in /AIF/ERR. However this only *half* works... /AIF/ERR does not update the error/message counts for ECH errors.

There is also conflicting instructions regarding whether you need to disable ECH in SPRO or not. For example OSS note 1799544 states that you must disable ECH for the AIF/ECH link to work. But when doing this, new messages no longer appear in /AIF/ERR at all.

In the document provided by SAP here: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e065a3c5-3824-3010-17b0-e9cb3fdf6...

it states to turn ECH on. Which is what I have, but as mentioned above it does not update the error counts and doesn't seem to work properly in the web version of /AIF/ERR either.

Any ideas...

[YapingGao]

Hi Jason,

It seems that you've deeply dived into AIF already.

Regarding to your first inquiry, I personally doubt if it is reasonable to define it as a real bug or a kind of function defect, because it is technically not supported so far to calculate the "counter" without invovlving AIF runtime or AIF enabler (the 2 components are responsible for calculating "counters",  not Error Handling) during processing data message.

The use case of ECH engine (engine ID 04) is that:

- ECH is switched on

- The Service (Proxy Class) is implemented on ECH framework.

- No AIF runtime or AIF enabler is invovled in the implementation.

- So that, ECH (not AIF) takes over the error handling task (by creating PPO document according to the data message) if there is any error occurs during processing data message.

- BUT, it is supported to monitor PPO in the AIF Error Handling transcation using ECH Engine (Engine ID 04)

The note 1799544 describes another use case which is actually coflict with above mentioned typical ECH use case, as you observed.

Either ECH is on, the service (Proxy class) to be monitored is implemented on ECH framework. You monitor PPO (forwarded from original data message into ECH) in AIF Error Handling by ECH engine.

Or ECH is off, the service (Proxy class) to be monitored is not "purely" implemented on ECH framework. Here, "purely" stands for: all the processing log messages (as well as exception) are inject in PPO (ECH), not returned to Proxy Framework. You monitor original data messages in the AIF Error Handling.

It is not supported that,

- ECH is on, The service (Proxy class) to be monitored is not implemented on ECH framework.

- ECH is off, The service (Proxy class) to be monitored is purely implemented on ECH framework.

- Even more complex use case is that, you want to monitor 2 services implemented in different ways, 1 is on ECH framework, another is not. It is not supported very well, to be honest.

Above constraints may change in the future, but so far those are constraints.

Hope I can answer your question.

Kind regards

Yaping