02-26-2015 5:15 PM
Hi all,
I am running a standard transaction between ECC and BW.
One standard function module doesn't return the expected results
and I can't change the coding to catch a SYSTEM_FAILURE or COMMUNICATION_FAILURE.
Here is what happens in details: the coding that causes issue is in
class CL_UA_FORMULA_PDCE, method GET_CO_AREA_CURRENCY, line 51.
CALL FUNCTION 'RSSEM_CHA_VALUES_GET'
DESTINATION ld_rfcdest
EXPORTING
i_chanm = cd_iobj_co_area
i_read_attr = abap_true
TABLES
ith_selopt = lt_selopt
eth_chavl = lt_chavl
EXCEPTIONS
unknown_iobj = 1
OTHERS = 2.
With values:
When run the transaction in ECC, I receive exception 2 (others).
When I run the RFC call in SE37 in ECC, I receive the expected values, no exception.
When I run the function module in SE37 in BI and with the RFC user in the debugger, I receive the expected values, no exception.
I believe there is a communication or authorization issue, which could be caught with
EXCEPTIONS
SYSTEM_FAILURE = 1 MESSAGE L_V_RFC_MESS
COMMUNICATION_FAILURE = 2 MESSAGE L_V_RFC_MESS
But since this is standard coding, I can’t change it.
I tried to run an RFC trace, but the content is useless.
I tried the System Debugging, but it won't jump into the BW system.
Is there a better basis transaction to see what happens between the 2 machines?
Any other idea?
Regards,
Julien
02-26-2015 8:17 PM
Hi Julien,
I think there might be some Basis security issues due to which the system is not the way it supposed to be perform
Yes you can find that what happened between 2 system - Please go through the following link I think you will get your solution
And another link
Thanks & regards
Saifur Rahaman
02-26-2015 10:57 PM
Firstly, if the RFC is working fine in SE37 but not in transaction, it could be due to conversion exits not running on exported values.
Running RFC in SE37 does it automatically, so no issue there. But for e.g., to run it through a program u need to make sure the values being exported are in SAP internal format, which could be done using conv. exit.
Check if something is missed there, possibility is least as its standard SAP, but still check.
Secondly, you can debug the RFC using following 2 approaches.
Approach 1 -
Approach 2 -
Hope it helps.
Cheers!
02-27-2015 8:36 AM
Lanch a system trace (ST01) in ECC (in the target system), check box "Authorization check", then call the FM via RFC from BW (from the source system) system, then back to ECC, stop trace and "Aanlysis" the trace to get any aithorization problem
Hint: If those are your first calls with this function , check authorization object S_RFC for allowed function groups (type FUGR)
Regards,
Raymond