on 08-14-2014 7:02 AM
Dear All,
We have messages being triggered from PI to proxy and to AIF.
Messages status is shown as successful in sxmb_moni transaction but I don't get to see these in /AIF/err - error handling and monitoring transaction.
WHat could be the possible reason? would there be any missing authorization.
Note: this is working in Development but having this issue in test environment.
Thanks and Regards,
Archana
Hi Archana,
Could you please let us know how you resolved this issue.
Thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Archana,
we had a similar issue after our first deployment to the first test instance. Messages could be seen in /AIF/LOG but could not be seen in /AIF/ERR.
It was an authorization issue. We setup the AIF roles for these systems by copy the standard AIF roles and composite roles from AIF Master Guide. The issue was that our AIF composite roles were activated but not the included single roles.
Perhaps this could be the issue.
Best wishes
Christoph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Christoph,
Thanks for your response! Sorry for the delayed response from my end. I couldn't even see the messages in /AIF/LOG.
regarding system roles for AIF, i See that other interfaces in AIF are working properly. So would there still be an issue specific to one Interface alone?
Thanks and Regards,
Archana
Hi Archana,
use the table /AIF/STD_IDX_TBL to find the message log , you have to enable the AIF configuration under error handling to select the message from above mentioned table .
you can use the append structure to store the message value in table /AIF/STD_IDX_TBL and same will be used as selection screen values in /n/aif/err transaction.
1) use SU53 to find the authorization issue
2) check the above table with SXMB_MONI message GUID .
3) check the inbound queue logs
4) Are you capturing/passing the application system(RFC/BAPI/Call Transaction) exception to AIF Function module?
Regards
Sukumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sukumar,
Index table has been used and the message logs are captured if i run a test from proxy.
Only issue is when we get the message triggered from PI. But SXMB_MONI, when you check for payload status its successful, and no error. But i dont get to see those messages reach AIF at all.
Unfortunately for test system i do not authorization to check su53, but then i have requested to check.
These message Guids doesnt exist in index table as i suppose the message didnt reach AIF at all.
Thanks and Regards,
Archana
Due to requirement of passing multiple records at once, have used 'aif/cl*xml*=>send_to_aif ' method .
changed the selection engines accordingly.
And it works well when tested through sproxy.
Have maintained a separate index table in name space specific features.
now only issue is when triggered from PI.
Hi Archana,
Here are some hints about what you could try:
Best regards,
Verena
Hi Verena,
- Engines are configured correctly in test system as in development system.
- Interface determination is not configured at all in any systems.
I couldnt even find messages in /AIF/LOG when they are sent from PI. It's only in SXMB_MONI where i find these messages are successful and no other trace of them.
Thanks for your hint! any further suggestions are appreciated!
Thanks and Regards,
Archana
try to see the logs in /AIF/LOG or the successful messages in /AIF/ERR_WEB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Archana,
About ERR_WEB, probably run an old version, but this won't help you either, I think.
Another tip is to look in PI:
Is your service synchronous? For synchronous messages PI only persists the message in PI's message store if the abap proxy returns an error, such as a SOAP Fault. If your abap proxy is not returning an error, then make sure it does. You can raise an application error in AIF.
If PI already receives a SOAP fault, then I suggest you to check if the message was stored in PI: see SAP note 872388 to guide you on this task.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.