How to deactive the EM enterprise services

[l_j_li]

Hi Expert,

    To integrate with 3rd party system for capturing events to EM system, we patched the XI content for SCEMSVR in PI system , currently we can get the event message from the enterprise service : TrackedProcessEventNotificationCreateRequest_IN,   but the system will automatically trigger another outbound Enterprise service 'TrackedProcessEventNotificationCreateConfirmation_OUT'.

How to deacitve the serivces 'Tracked ProcesEventNotificationCreateConfirmation_OUT'   ? 

Best regards

L.J. 

[Former Member · Accepted solution]

Hi Li,

Go to Tcode SPROXY -> Click Enterprise Services Repository -> SCEMSRV*(*denotes your version) -> http://sap.com/xi/EM/Global -> Service Interfaces -> Tracked ProcesEventNotificationCreateConfirmation_OUT -> Click Menu -> Proxy -> Active <->Inactive.

Check how to deactivate/delete in this link ABAP Proxy Generation - General Procedure - ABAP Workbench Tools - SAP Library

Regards

GGOPII

[l_j_li · Accepted solution]

Hi, Gopi

   Thanks for the reply . Is there any way to control the enterprise service TrackedProcessEventNotificationCreateConfirmation_out is not triggerred replacing inactive the enterprise service

Best regards

Liangjun

[Former Member · Accepted solution]

Hi Li,

I don't know it is possible to control internally in proxy TrackedProcessEventNotificationCreateRequest_In, because I could see class /SAPTRX/CL_TPEN_REQUEST_IMPL -> EXECUTE ->  lo_confirmation_proxy calls confirmation proxy inside.

Regards

GGOPII

[former_member190756 · Accepted solution]

Hi Li,

why do you want to deactivate it?

This is an asynchronous service sending the response with TrackedProcessEventNotificationCreateConfirmation_OUT.

Without response you don't get the info if the Event Message could be processed correctly or was maybe invalid.

Best regards,

Steffen

[sukumar_perumalsamy · Accepted solution]

Hi Li / Steffen,

As per understanding response from SAP is not required for the integration scenario , most of the cases event message response is not  required , besides that SAP standard ES supports only to synchronous call .

Changes could be required  in  /SAPTRX/SPOT_SE_EM_SERVICES (/SAPTRX/IF_BADI_TPEN_SEND-OUTBOUND_PROCESSING) outbound processing BADI with below logic

validation flag option for outbound notification should be enabled and the same has to be validated before the confirmation proxy call.

Hope it helps to solve the issue without changing the SAP standard objects and it avoids custom  asynchronous development  in PI/PO ,customer can control the outbound notification by implementing the BADI .

Cheers,

Sukumar

[l_j_li · Accepted solution]

Hi Steffen

We need to integrate with 3rd party system for capturing some events,   from the rigorous point view of solution , I think the response async. response is necessary;  from project view, if we sent this response, it means that we need to ask 3rd party system to add one interface and enhancement in 3rd party system. for error message and invalid message , we can check in sxmb_moni and EM application log and other ways for this async. interface.

@ Sukumar

I am afraid this conformation ES can not be triggerred via BADI: /SAPTRX/SPOT_SE_EM_SERVICES, I just see one parameter which only contains the BAPI return message of Inbound message  in the /saptrx/if_badi_tpen_send-outbound_processing

in second words, we patched XI Content for SCEMSVR,  I don't think extra PI effort 

[sukumar_perumalsamy · Accepted solution]

Hi Li,

my proposal is to have the additional flag variable in BADI , and the flag  variable has to be changeable field in BADI implementation .

Using the flag variable we can control the OB confirmation proxy call.

Pseudo logic :

1) implement the BADI and set the flag variable = space , add business logic here to set the flag variable .

2) check the flag variable before the  confirmation proxy call.

3) if flag_variable = X then send ob message

     if flag_variable = space then don't trigger the OB confirmation proxy call.

the above solution is achievable only if we get SAP OSS correction note  to change the BADI parameters and code logic before the OB confirmation proxy call.

hope it clarifies .

Cheers,

Sukumar