on 09-08-2014 1:26 PM
I am getting error Error in calling up function 'BAPI_APOATP_CHECK' in APO server The current application triggered a termination
when triggering for gatp.
Hi Virender,
Can you please share the ST22 error log? or in case there is no error in ST22, show the long text of your error message...
Kind Regards,
Mariano
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Virender,
Please check the RFC user used for ATP call in ECC system. If a trusted RFC connection is used, then the user who is trying to do GATP check should have an user setup in APO with GATP authorizations. If not, it will not call the GATP and you will get the above error.
Regards,
Manimaran M.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Virender,
This error can be experienced due to many reasons. based on my experience below reasons can cause this issue.
1) If you are using allocation check if allocation is correctly set.
2) In case you are using custom enhancements / user exits (in SD / GATP / CIF) check if any of them, causing this issue.
In my case correction of allocation setup could resolve this issue, so check what is the reason in your case.
Rgds
Sourabh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Virender,
For this error, you should logon to APO system and then see ST22 to find the reason for the short dump. In my view, either one of the notes is causing this or it may also be possible that some of the userexit coding is giving a short dump due to incorrect coding in place.
Correct that and then do the avaialbility check.
Thanks & Best Regards,
Babu Kilari
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If there is no dump that is showing up, I suggest you to find out the message number and message id from the error message and do a where-used list of the message id from SE91. Put the break-point in the relevant code and debug the ATP call from ECC to APO to get to the root cause.
But, I am surprised that there is no short dump. May be it is not captured. Also, you can activate ATP log temporarily and see the logs of ATP call.
Babu Kilari
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.