RFC Destination Settings

Hello Gurus,
Earlier we had 2 ECC systems in the landscape.
Purchase requisition A from APO system supposed use RFC destination 1 and reflect in Plant XXXX
Purchase requisition B from APO system supposed use RFC destination 2 and reflect in Plant YYYY
Now we have only 1 ECC system in the landscape. we have changed the publication settings accordingly. but preq still not getting transferred correctly to ECC system.
Debugging the code shows system trying use wrong RFC destination.
Is there any other configuration setting we are missing.
Please advise.
Thanks In Advance
Shyam

Hi Shyam,
Please find my suggestions in regards to respective configuration settings.
1) Did you delete the obsolete RFC destination(Logical System) from your landscape?
2) Did you correct the RFC destination of plant YYYY to RFC Destination1 (incase you scrap RFC destination2 from landscape)?
3) Check what is the Logical System that is maintained for the location YYYY from the table /SAPAPO/LOCMAP in APO system.
4) Similar check for the products in the table /SAPAPO/MATMAP.
5) Remove the obsolete ECC System from the BSG using T-code /SAPAPO/C2.
Post checking and correcting, do an intial transfer of locations via CIF from the current ECC system.
Thanks,
Santosh KB.

Similar Messages

RFC Destination to test EDI outbound process

Hi,
I am configuring RFC Destination. SAP provides a tool to test EDI outbound process even when EDI subsystem is not actually connected. Do you know what the RFC destination settings should be in this scenario? Thank you.

Hi,
Please check this links perhaps they may help.
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/mysap3/sap109.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm
Regards,
Ferry Lianto

RFC destination and webserver settings

Hi,
I need to configure the RFC destination and other technical settings and certainly need help from Basis people. However what inputs we have to give them enabling us to set right configuration. I find different proxy class, RFC destination etc have been set for different object types.
For ex, I want to configure cproject with MM,SD, CO etc
What information as a functional consultant we have to provide to Basis people.
I met with following error in accounting.please tell the path for required settings.
An error occurred when connecting to the accounting system EC6CLNT100
Message no. DPR_FIN_GECCO001
Diagnosis
A connection to the Accounting system could not be made. Possible causes are:
The system is not available
The RFC destination for the Accounting system is incorrectly defined in Customizing.
System Response
The system could not read data from the Accounting system. The system cannot distribute project data to the Accounting system.
Procedure
In transaction SM59 check the RFC destination defined for the Accounting system.
Check whether you defined the correct RFC destination for the object type. See Customizing for Collaboration Projects under --> --> .
Zinni
Edited by: Makwana Zinni on May 27, 2009 1:58 PM

Hi,
I am getting the same error. Could you please elaborate on how you fixed the error. I am not sure what/how to test in tcode SM59. I am following the cofig guide for cProjects but the cProjects screen is still giving me the error msg and I am not able to understand the solution.
Here is the ERROR MSG
An error occurred when connecting to the accounting system
Message no. DPR_FIN_GECCO001
Diagnosis
A connection to the Accounting system could not be made. Possible causes are:
The system is not available
The RFC destination for the Accounting system is incorrectly defined in Customizing.
System Response
The system could not read data from the Accounting system. The system cannot distribute project data to the Accounting system.
Procedure
In transaction SM59 check the RFC destination defined for the Accounting system.
Check whether you defined the correct RFC destination for the object type. See Customizing for Collaboration Projects under --> --> .
ANYONE'S HELP WILL BE APPRECIATED!!

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

RFC destination BW could not be created in the source system R3073

I'm creating a source system for our BW (version 7.0) dev client.I'm linking it to our R/3 4.7 QA client. From RSA1 I select create source system, I enter the system information and in the next screen I'm prompted to log on as system administrator. I'm in QA now and the system automatically crated the RFC connection. I test the connection and it runs ok. I log on to the BW client from QA and it logs on just fine. When I exit the screen I get the following message:
RFC destination BW could not be created in the source system message number R3073
Why is this happening? The connection tests just fine.
I'm using RFCREMOTE user in BW and ALEREMOTE in QA with the same password
Any ideas?
thanks

Hi,
I cannot tell you surely the settings for SCC4 now (I can't connect to my sys).
Nevertheless, create your R3QA RFCDEST manually in your BWDEV with SM59.
Create your BWDEV RFCDEST manually in your BWQA .
Perform test and authorization test within SM59 from both sys.
When creating the source system in BW the system will detect the RFC and ask you if you want to use it; accept an proceed the the rest of the procedure.
hope this helps...
Olivier.

RFC destination definition with non-unicode external program

Hello All,
we have one issue with our RFID system connecting to WM system (SWD).
For most functions, external RFID server/middleware makes RFC call to SAP system. Means, from outside system to inside SAP. This seems to be working fine.
But in one case, SAP needs to print label to RFID printer. In this case, SAP is calling external RFID server/middleware using RFC destination. Means, from inside SAP to outside system. This is failing.
We think this has something to do with ECC60 being unicode system, and the RFC destination setup. We define rfc destination "ZRFID_SSI" in SM59. We define it same way as in as-is SSI 4.6B production system. But in SWD ECC60 system, SM59 has more options. We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server. RFC destination is actually working ok.
To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI. Listener on RFID server/middleware will respond to function call. This also seems to be working. But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0". (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)
Compared with production environment, everything is the same, except that SAP is unicode system. So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data. I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange. Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.
Anyone know how to help ?

Hi Jeongbae,
as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.
In earlier releases, this is not possible.
In general, SAP systems use the logon language (SY-LANGU) to determine the code page, if this is available.
Please check SAP note 788239.
Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.
In addition I would recommend to have a look at SAP note 1021459.
However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).
For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !
Best regards,
Nils Buerckel
SAP AG

RFC destination for synchronous communication (message type SYNCH)

Hi experts,
I am trying to configuare ALE settings.waht i did is
My sending & receiving systems are one server with different clients.By using SALE transaction
1.crated logical systems.(LS_800 &LR_810)
2.Assigned those to clients.
3.Created RFC destination
4. Created modelview assign sending & receiving
systems and message type.saved it.
4.generated Partner profile.Here i am getting below problem
Target system LR_810
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LR_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Target system LS_800
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LS_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Regards;
Upender.

Hi Shital;
Thanks for your replay;
Still am getting the Same Error;
Thanks;
Upender.

RFC Destination not getting connected - IDoc to XI scenario

Hi Everybody,
I want send an IDoc from R/3 System to Xi, I have created Two logical systems (Sender and Receiver correspondingly) and i have assigned the clients to them.
Once i create RFC destination, i have specified all my technical settings as well as Login/Security settings, once i click, "Remote Log On" it takes me directly to Login page of XI. Please guide me how to solve the problem. If i click Test---> Authorization, it prompts out with an error "Name and Password is incorrect (repeat Logon)", but i have given exact username and password.
I am a fresher to XI.... please give me some documents related to IDoc to XI scenario step by step to [email protected] I would be grateful and appreciate you if u would help me to sort out this problem....
Please give me step by step solutions.... Thanks in Advance...
Regards/Guru

Requirements in R3 system:
1. Create RFC destination pointing to XI in SM59
2. Create port for XI using we21
3. create Outbound Entry in partner Profile for XI in we20.
Requirements in XI system:
1. Create Technical System pointing to the R3 system.
2. create Business System pointing to the R3 system.
If you want to send IIDOC out of XI,
1. SM59 - Create RFC destination
2. IDX1 - Create port
3. IDX2 - Import Metadata.
Note:u dont need a IDOC sender adapter or a Sender Agreement to sent a IDOC to XI.
Check dis link for more info:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
please refer to michel book on IDCO usage in XI
Message was edited by:
Sreeram Reddy

RFC destination with CIF application case !

Hi,
Can someone explain the difference between
Assigning a logical system to a RFC destination and
u201CAssigning a logical system to a RFC destination with CIF Application case" (there are 4 of them in all as i see - AC, RL, RQ, DG, AC- refers to availability check)
e.g I have 2 entries in the system landscape settings.
1) Logical system u2013 RFC destination
2) Logical system- application case AC u2013 RFC destination.
Even if I remove the 2nd entry, the relevant APO ATP FMu2019s are called (just a negative testing to see what goes wrong without application case) but am clueless about this concept of CIF application case. Why such a provision to begin with. The context help says. some transaction need to have synchrious RFC and hence the need but i see the same even without his entry.
Regards,
Loknath

Hello Loknath,
If I understand your query correctly,
1.Assign logical system to RFC destination is OK for you.
2.Assigning the RFC destination to a specific CIF application is used in the following case,
You have a system/service user set up for communicating with the R/3 system thru CIF & this is assigned to the RFC destination assigned to the point no:1
& for debugging purposed you need a dialogue user, so you may assign this dialogue user to a different RFC destination & assign it here in the customizing (Assign RFC to application cases) to the application Debugging..so that while the particulat application is called (Debugging...CIF cockpit...etc)the corresponding settings from the different RFC destinations will be used.
I could not understand your query, where u relate some ATP stuffs with this CIF topic...
Thanks,
Mahesh

RFC Destination Seetings Problem between R/3 and XI System

Hi...
In my RFC to File Scenario I cant see the messages in MONI......
When we create RFC destination through SM59.....we will fill gateway host and service
of R/3......Then we Configure the RFC Sender CC and fill same Program ID, Gateway host & service of R/3.
My doubt is,after this should I have to configure SM59 at XI side ???.....
I am getting confused in this RFC Settings between R/3 & XI....Can u explain the flow correctly.....
Please help me out.....
Thanks,
Sudheer.

Hello Sudheer,
1.Configure the Sender communication channel by giving the programId there,
2.You need to create RFC Destination at Sender R/3 system pointing to PI, there you need to mention the programId, specified in Sender CC,
3. In RFC destination you need to specify your XI system details for Host/ServiceName nameand gateway service .
Note: programId is case sensitive.
No need to create any RFC Destination in XI system.
check the following thread for further clarifications.
Re: TCP/IP connection for RFC sender adapter
Regards,
Prasanna

Help with RFC sender, Program And RFC Destination

Hi!!
my scenary is asynchronous
     RFC Sender -> SAP-XI -> Oracle reciever
I have a problem with abap, especially rfc, program and rfc destination. The connection with SAP-XI exist and SAP-XI receive the message but the message is empty.
1. In my program on the line
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          catch an error system_failure = 2 and it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC
2. I rewrite my program, that line to
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' STARTING NEW TASK 'NEW' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          catch an error communication_failure = 1 but the rfc ZBAPI_SD_PED_ORD_SERVIC is executed but no send to SAP-XI
3. I rewrite my program, that line to
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' IN BACKGROUND TASK DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          No error but it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC and the message in SAP-XI is empty, display the tables but not the row. i check the table PED_ORDEN and RETURN but the controls fields dont are afected.
What is my Error?
Where am i making a mistake?
RFC
FUNCTION zbapi_sd_ped_ord_servic.
*"Interfase local
*" TABLES
*"      PED_ORDEN STRUCTURE ZSD_RFC_T04
*"      RETURN STRUCTURE ZSD_RFC_R06
TABLES: zsd_ped_orden, zsd_rfc_r01.
DATA: tb_ped_orden LIKE zsd_ped_orden OCCURS 0 WITH HEADER LINE,
               tb_rfc_orden_error LIKE zsd_rfc_r01 OCCURS 0 WITH HEADER LINE.
*Get Pedido by Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_ped_orden
          FROM zsd_ped_orden
          WHERE estatus EQ space.
LOOP AT tb_ped_orden.
    MOVE-CORRESPONDING tb_ped_orden TO ped_orden.
    APPEND ped_orden.
    tb_ped_orden-estatus = 'X'.
    tb_ped_orden-fecha_actualiz = sy-datum.
    tb_ped_orden-hora_actualiz = sy-uzeit.
    MODIFY tb_ped_orden.
ENDLOOP.
MODIFY zsd_ped_orden FROM TABLE tb_ped_orden.
COMMIT WORK.
*Errors in Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_rfc_orden_error
          FROM zsd_rfc_r01
          WHERE estatus EQ space.
LOOP AT tb_rfc_orden_error.
    MOVE-CORRESPONDING tb_rfc_orden_error TO return.
    APPEND return.
    tb_rfc_orden_error-estatus = 'X'.
    tb_rfc_orden_error-fecha_actualiz = sy-datum.
    tb_rfc_orden_error-hora_actualiz = sy-uzeit.
    MODIFY tb_rfc_orden_error.
ENDLOOP.
MODIFY zsd_rfc_r01 FROM TABLE tb_rfc_orden_error.
COMMIT WORK.
ENDFUNCTION.
PROGRAM
REPORT ZBAPI_SD_PED_ORD_SERVIC.
DATA: ped_orden LIKE ZSD_RFC_T04 OCCURS 0 WITH HEADER LINE,
      return LIKE ZSD_RFC_R06 OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
     TABLES
          ped_orden             = ped_orden
          return                = return
EXCEPTIONS
    communication_failure = 1
    system_failure        = 2
    OTHERS                = 3.
IF sy-subrc <> 0.
MESSAGE 'error' type 'I'.
ENDIF.
COMMIT WORK.
RFC DESTINATION
RFC Destination: ZXI_ENVIAR_PED_ORD_SERVIC
Connection TYpe: TCP/IP Connection
Register Server Program: ZBAPI_SD_PED_ORD_SERVIC
Gateway host: host00
Gateway service: sapgw00

hi
For rfc sender adapter we hv to do some settings .Please chk whether this settings are well configured or not.
a) RFC destination
b) RFC channel in the XI directory
This weblog is a response to a few question about the basic configuration of the RFC sender adapter
that were posted on the XI forum (and also on my e-mail)
So here we go, basically we have to configure 2 things:
a) RFC destination
b) RFC channel in the XI directory
RFC destination:
1. To create the RFC go to TCODE: SM59
2. Create new destination of type T (TCP/IP)
3. Make sure you select Registered Server Program option before writing your program ID
4. Write you program ID (remember it's case-sensitive)
5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)
7. No configuration in the J2EE administrator nessecary
Now we can proceed to RFC channel configuration:
1. Enter your Application Server
2. Your Application Server Service
3. Enter your Program ID from the RFC destination
And we're done:)
Now you can test the RFC destination in SM59 to see if it works.
Please chk this following link.
1. RFC Processing with the RFC Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
2. Configuring the Sender RFC Adapter -
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
3. /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
regards
Manas

RFC destination not defined for SAP global trade services

HI friends,
I have created a delivery against a sales order. Maintained the storage location and the picking quantity for the item.
Now trying to post the goods issue but system is giving short dump and error message says:
"RFC destination is not defined for SAP global trade services"
We are not using SAP global trade services module and no IDocs are involved in the process.
Please help
Thanks in advance
Veer

Hi Mohit,
Thank you for replying.
It was not an issue with RFC destination but to do with transfer of outbound delivery processes to SAP global trade services.
As we were not using global trade services, we had to deactivate the transfer of data from SD application to global trade services.
The settings are under IMG>SD>foreging trade>SAP global trade services-plug-in> control data transfer to SAP global trade services
Deactivate all the activities.
Now this issue has been resolved.
Thank you again for replying.
Regards
Veer

Creating RFC destination in Visual Administrator results in error

Hi.
I am trying to set up ESS and MSS on a EP 6.0 with SP15.
According to a Post-installation guide for SLD i have to create a RFC destination, but when i save the settings i get the following error: Error changing bundel's properties, see LOG for details!.
And when i try to start the RFC destination i get the following error: Error starting bundle, see LOG for details!
Have anybody encountered this problem, and if so, can you give me a hint to what the problem might be?
Regards Liselotte

hi
I am also running into this error, and this is preventing me from completing my xi configuration as after i create the bundle..and select start..i get a msg "error starting bundle see log for details.."
what log do i see...?
and a test connection from sm59 also fails..
any help on this is appreciated.
Regards
Ravi

Transaction IDX1: Port SAPPRD, client , RFC destination contain errors

Hi all,
when I send an IDOC from Xi to R/3 I get the following message in XI monitoring:
Transaction IDX1: Port SAPPRD, client , RFC destination contain errors
ERROR= 2:IDOC_ADAPTER(151)
However everything is maintained correctly (i think) in IDX1. I can upload the IDOC metadata with IDX2 from the R/3 system.
I seems that Xi doesn't have the clientnumber available. (should be 600) but is not mentioned in the error.
Did I miss something?
Thanx Ron
Message was edited by: Ron van der Sterren

Hi Ron,
Settings in XI side.
1. Create the RFC Destination(SM59) with connection type 3, pass the target host pass is R/3 server name and logon tab enter the R/3 logon details.
Test the connection is success and check the Remote login button it's connecting the R/3 system or not.
2. Create the Port IDX1 and pass the client number is (R/3 client) and pass the RFC destination which you created above.
R/3 side
1. Create the RFC Destination(SM59) with connection type 3, pass the target host pass is XI server name and logon tab enter the XI logon details.
Test the connection is success and check the Remote login button it's connecting the XI system or not.
2. Create the TRFC port to transfer the IDOC'S and pass the RFC destination which you created above.
3. create the logical system in BD54 this name should be same as XI logical system name.
4. Create the partner profile (WE20) and partner type is 'LS' with inbound parameters and pas the appropriate values.
Let me know if you have any issues.
Regards,
venu.

Transaction IDX1: Port SAPQA1, client 500, RFC destination contain error

Hi experts
I am configuring XI for MM-SUS scenario, when I try to send Idocs from R/3 to XI I have this message:
Transaction IDX1: Port SAPQA1, client 500, RFC destination contain error
In XI transaction IDX1 I have maintened a port (MM_QA1) and RFC (MM_RFC) that points to R/3
In XI transaction IDX2 there is no entries
Some idea how to solve it?
Thanks
Nilson

Hi,
>>Could you clarify it for me, In XI side Transaction IDX1 I have a PORT and RFC destination to R/3?
Yes you are correct..
You should have done this..
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Define Gateway service
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
Thanks
SaNv...

RFC Destination Settings

Similar Messages

Maybe you are looking for