on 01-18-2008 12:57 PM
Hi all,
I've created an rfc destination in SM59 and it works perfectly. But it doesn't works using the "call function 'xx' destination ...". I don't see any information in transaction SXMB_MONI.
What can I check? Please help.
Hi,
you can find the adapter identifiers in the configuration.
double click on the business system and go to SERVICES.
there u can find the adapter identifiers.
1)Also check whether u have created rfc destination having TCP/IP connection.
2) check whether u have registered the server program before giving the program id.
3) In gateway host and gateway servicegive the ip of your business system not the XI server
4) before checking the connection to xi make sure tht u have specify the program id in rfc adapater,activated it and then check the connection because when u click on test connection XI comes and registered itself there.
ALSO U Refresh the XI RUNTIME CACHE BEFORE U TEST CONNECTION
GO TO Transaction SXI_CACHE-> XI RUNTIME CACHE ->COMPLETE CACHE REFRESH
VIKAS JAIN..
Regards points if helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ismael,
Make sure the attribue "remote -enabled module" is selected for the function module you are calling.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
check the following link and confirm you have done all right
http://help.sap.com/saphelp_nw04/helpdata/en/22/04256b488911d189490000e829fbbd/frameset.htm
Also specify the error you are getting if any.
I can't make modifications in this R3.
My code is:
CALL FUNCTION 'my_function'
DESTINATION 'rfc_destination'
EXPORTING
COD_TRABAJO = IT_ORDENES-AUFNR
IMPORTING
CODERROR = CODERROR
MENSAJE = MENSAJE
EXCEPTIONS
OTHERS = 1.
My only clue about what's the matter is SY-SUBRC=1 .
I see it's possible to use:
CALL FUNCTION Remotefunction
DESTINATION Dest
EXPORTING...
IMPORTING...
TABLES...
EXCEPTIONS
SYSTEM_FAILURE = 1 MESSAGE msg
COMMUNICATION_FAILURE = 2 MESSAGE msg
Why can SYSTEM_FAILURE and COMMUNICATION_FAILURE occur?
Edited by: Ismael Perez on Jan 18, 2008 2:48 PM
Hi,
1. write commit work in RFC.
2. Communication faliure occurs when your login credentials dont match with R3 in RFC sender, like you have given language as en in PI and EN in RFC destination on R3.
3. first activate your communication channel then test connection. its a compulsion.
Rewards if found helpful.
Regards,
Alok
A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".
If a non-ABAP system is used to send RFC-calls to the RFC-Adapter sender channel it may is not possible to set the SYS-ID and CLIENT values in this external RFC client. The checking of these values can be disabled in the 'RFC Server Parameter' settings in the sender channel. Choose 'Advanced Mode' and deselect 'Verify Sender System'.
( reference from SAP note 730870)
Regards
Rao
I had a scenario working fine with R3_1 but I changed the data in the channel to test scenario with R3_2. It started to fail, so I change the Business System and assigned the Technical System of R3_2. It didn't works neither.
Finally, I didn't know why didn't work, so I decided to put everything like the original and ... now doesn't works.
Hi Ismael,
a) did you import the RFC into integration repository?
b) did you configure comminication chanel?
c) did you configure sender agreement?
Regards Mario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.