2019 Sep 13 1:58 PM - edited 2024 Feb 03 5:13 PM
Hello Experts,
Summary:
We've a requirement that when an error occurs in SRT_MONI for a proxy call we need to notify the intended recipients about the error so that a necessary action could be taken.
Detail:
On calling BP replication service BusinessPartnerSUITEBulkReplicateRequest_In through SLP many a times we have a scenario where the data doesn't get updated due to some or the other issue. For e.g. Vendor Locked or maybe some mandatory value missing in XML request.
In such a case if the error occurs we want to notify the intended recipients about the failure. Many of such errors are captured in SRT_MONI. At least if we can get these errors emailed to the user that would be helpful. Any help? Any custom solution or standard feature that am missing on?
OBJECT DETAILS –
Inbound Service: BusinessPartnerSUITEBulkReplicateRequest_In
Namespace: http://sap.com/xi/SAP_BS_FND/MDG/Global2
Package: MDG_BS_BP_XI_PROXY
Interface: II_MDG_BP_RPLCTRQ
Thanks
Chandan Jha
Request clarification before answering.
Hi Chandan,
No such standard out of box solution available, you have to go build a custom report. I had the same requirement and we built a custom program which read the SLG1 logs (check if you AIF integration enabled, if yes then check standard namespace /CMDBP BP_IN) based on the date & time range; we schedulded the job to run in background and it triggered an email to a DL
Cheers,
Varun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@chandan_jha72, Did you find any resolution for this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chandan,
There are few options for the monitoring.
1. Use SOLMAN Monitoring capability to track webservice messages or PI monitoring options. (I am not an expert in both topics, but they are valid options for monitoring)
2. On processing of BusinessPartnerSUITEBulkReplicateRequest_In, system typically triggers BP*Confirmation_Out message. If it happens so in SLP integration, this XML will have the error details on why the webservice has failed. Find the class linked on BP*Confirmation_Out and enhance the class to send emails.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Saravanan,
For option 2, is it true that even failures for Request_In messages should trigger a Confirmation_Out message? We have the same need to monitor failures with our SLP integration and currently, failures during the request_in step are not triggering confirmation_out messages.
It would be ideal if they did. Are we missing some part of the setup?
Thanks,
Anna
User | Count |
---|---|
62 | |
10 | |
8 | |
8 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.