Logical system and rfc destination

hello all,
what is the difference between logical system and RFC destination?
thanks for ur help in advance.
regards,
vikas

Hi,
In any ALE scenario u need one sender and one receiver system.
Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
Regards

Similar Messages

Logical system and rfc destination related Query?

Hi Dudes
Do we need to define logical system and RFC destination if they are in different clients in same server
Regards
Raj Kumar

Hi
Both are client independent setting, so even if you define in one client, it would be available in other clients also.
Regards,
Sanjeev

Confusion in Logical System, port & RFC Destination

hi,
I have still few doubts regarding Logical System, port and RFC destication
My SAP ECC6.0 and XI configuration is:
For ECC 6.0 : Logical system name : T03CLNT400
Client : 400
RFC Dest : XIDEST
Port : XIPORT
For XI 3.0 : Logical System name : WXI
client : 400
RFC Dest : ECCDEST
Port : SAPEC3
now my confusion is, in t-code WE19, when sending IDOC to XI (idoc - file scenario), which entry i've to use in prot and Partner No in Receiver side and which port and partner no i've to use in Sender Side.
also in XI side when creating Technical sys for web as ABAP which logical system name i've to use and in File to Idoc Scenario which logical system i've to use as sender business system (third party file business system)
If possible please give me detail idea to clarify my cofusion.
thanks
ritesh

Ritesh,
<b>now my confusion is, in t-code WE19, when sending IDOC to XI (idoc - file scenario), which entry i've to use in prot and Partner No in Receiver side and which port and partner no i've to use in Sender Side.</b>
If you are sending from R3 then give the sender details as R3 and the receiver side as XI where you have created the port from R3 to XI etc.
Check this help for clear understanding on all this settings:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Also can you check this weblogs on the same:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
---Satish

Logical System and Client copy

Hi Gurus ,
             I just now finished ECC 6.0 successfully , I want to take the client copy . But i hacve one doubt , In client creation one TAB logical system is there , Kindly advice me how to create Logical system and steps .
Regards
Selvan

Hi Manjula ,
              Below i mentioned the full detail about the error .
    RFC destination for client copy in systems with Financials Basis     (FINBASIS) component.
The system could not find any suitable RFC destination for processing     for client 000.     This note also appears if an RFC destination was found but this does not     work.     o   RFC destination: FINBTR@ID3CLNT000     o   Error text: Error during the retrieval of the logon data     Proceed as follows to eliminate this error:
1. Start the wizard to create a new RFC connection     or perform the following steps manually:     1. Create an RFC destination with the target ZK>source client of client         copy (in this case 000).
2. Check whether the RFC destination works in transaction SM59.         To avoid errors when assigning the password or the authorizations of         the RFC user, use the authorization test Test -> Authorization.
3. Enter the RFC destination:         -   Transaction: FINB_TR_DEST (Destinations for Transport Methods of             the Financials Basis)         -   Client: 000
4. Start the client copy again.
Kindly advice me
selvan

Configuring ALE Logical Systems and Partner Profiles

hi,
Trying to build a scenario which deals with two third party systems transfering XML file from one to another. Sender is using a file adapter. Reciever is using an Idoc adapter. However the pre-requisite mentioned for this exercise are that ALE logical systems and partner profiles must be configured (these steps are not outlined in the exercise) . Could i get help on what steps i need to carry out for sender/reciever to configure logical systems and partner profiles.
regards,
Manpreet

Hi Manpreet
At the R/3 system the partner profile should be maintained for both the third parties.
for creating the partner profile go to transaction we20, give the
partner number :your logical system name or customer number or vendor no
partner type:LS(logical system)or ku(customer)OR LI(vendor)
give the message type in the outbound parameters
after this double click on the message type and give the login deatils for the RFC destination define the port and all
if you still have problem please reply back
Thanks
Rinku

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

System cancel RFC destination - /TMWFLOW/TRACK_N107

Hello Experts,
In ChaRM, when i release transport request from DEV to QAS occurs the error below:
"System cancel RFC destination SM_D01CLNT210_TMW, Call The name or password ins't correct.
Message no. /TMWFLOW/TRACK_N107"
I've checked in the SM59 all connections to DEV and to QAS environment and all are OK.
What's wrong with my ChaRM? Is possible to be a autorization problem?
Thanks to all,
FS.

Hello Fabio
'SM_D01CLNT210_TMW'
check both, the connection test and the authorization test for the RFCs

System crash RFC destination

Hi,
When creating projects it fails with the messages:-
1) System crash RFC destination , Call TMW_VERSION_TEST: User SAPSYS has no RFC authorization for function group TMW_TRACKING .
2) System crash RFC destination , Call TMW_VERSION_TEST: Name or password is incorrect. Please re-enter.
3) RFC destination error SM_PRDCLNT000_READ: RFC task PRD:000:TMW_GET_FULL_LIST already open.
It is my understanding that 1 and 2 are related. The question I have is: How do I assign auhtorisation for SAPSYS to the function group TWM_TRACKING?
Regards

Hi Ferrandi,
See if these notes are relevant to your scenario:
Note 896042 - RFC access from satellite systems generates dump
Note 920805 - Correction of the FM TMW_VERSION_TEST in Note 804198
Also Which user do you use to generate the RFC`s??? Check the authorization for that user to generate RFC`s.　Ｔｈｅ　ａｕｔｈ　ｏｂｊｅｃｔ　S_RFCACL and S_RFC which is not a part of SAP_ALL profile should be assigned to the user.
Hope this is helpful.
Regards,
P. Kumaravel.
Ps: Award points for helpful answers.

Logical system and business system

Hi experts, please help me with the below questions---
1) What is the diff between logical system and business system?
2)what is the difference between logical system(defined in R/3) and business system (defined in SLD) in idoc to file scenario.
3) Is it require to give the logical system name of the xi server(Which we define in idx1 port) to the 3rd party system(Application system at the FTP side) to carry out file to idoc scerario?

Hi,
Business System :
1. Business systems are logical systems, which function as senders or receivers within XI. Business systems can be SAP systems or third-party systems. Depending on the associated technical system.
2. Business Systems should be mandatory used when dealing with Idoc's and Proxies .
Business Service:
1. Business Service requires manual adding on Inbound and Outbound Interfaces, Business Systems do not.
2. Business Services are maintained across environments and so, their names cannot be changed. Business Systems names can be changed across environments by providing SLD level transport targets.
3.In the Business Services we cannot maintain the Group and Targets in SLD. For Ease in transporting your ID/Configuration objects Groups and Targets are used in SLD for Business Systems.
4.Business Service has no SLD Entries and No Assigned Products and SWCV's
Regards
Sangeetha

AC 5.3 Logical systems and multiple Physical systems

HI all:
We have set up a Logical System, and then have hooked up 2 Physical systems to it. Based on the documentation from SAP, the rule set (and the way we set it up) is at the Logical system level.
Physical system #1 is reporting the correct results, however, Physical system #2 results are not complete. My understanding is that both Physical systems should be drawing from the rule set based in the Logical system.
Results: Physical system #1 - correctly identifies 10 risks
Physical system #2 - incorrectly only identifies 5 of the expected 10 risks.
Role assignment to user is exactly same, authorizations are exactly the same. The User/Role/Profile Full Sync has been repeated as part of troubleshooting.
Has anyone experienced this? I'm looking for ideas/options on where to investigate why the results are different.
Thanks
Margaret

HI:
Thanks for answering!! I'm having trouble understanding the answers, sorry.
When you have a logical system...you upload the rules once to that system, and generate them. Then when you set up a physical system and hook it up to the logical system...the 1st, 2nd or 3rd physical system....they all use the same ruleset. The whole concept (as I understand) is that the use of Logical and Physical systems...and putting the rule set on the Logical system so you don't have to worry about one rule set taking precedence over another, is an advantage, if this is possible (ie: we don't have multiple rule sets).
Where should I be checking that the risks are defined properly? The rule set is the delivered one from SAP. The functions and risks match what we had (plus more) in the CC 4.0 system.
The first physical system we set up (example: Development) works fine, and all regular SoD risks are coming up as expected. When we added another system (example: Test)...the results of SoD analysis were incomplete.
Does that help clarify? Perhaps I'm just missing something?
Margaret
Edited by: Margaret Sokolov on Apr 28, 2009 4:34 PM

What is a R/3 system, logical system, and legacy system...???

Hi,
Please throw some light on...What is a R/3 system, logical system, and legacy system...???

Hi,
R/3 system is a normal SAP system that stores data.
A legacy system is an existing computer system or application program which continues to be used because the user does not want to replace or redesign it.
Logical System:
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/5aa2a0deb91548a1842f8485dee4a2/frameset.htm
Technical System:
http://help.sap.com/saphelp_nw2004s/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm
Regards,
Subhasha

Is it possible to chenage logical system and how after a system is beeing u

Hello
I wander is it possible to chenage logical system and how after a system is beeing used for a while and how?

Hello Tina,
If the system is NOT a production system transaction BDLS can be used to change the logical system. This would be necessary after refreshing a dev system from a production system, for example.
If the system is a production system, I would agree that this is NOT advisable.
Regards
Greg Kern

Transaction Launcher Logical Systems and URLs

Hi,
I'm facing a problem with Transaction Launcher.
I've done all the settings specified here: http://help.sap.com/saphelp_crm60/helpdata/en/46/231befc17b5872e10000000a11466f/frameset.htm
Under section "Define Transaction Launcher Logical Systems and URLs" I've specified the values for Quality System: the ECC system is MQAS200A
By the way, when I try to access an ERP Sales Order, the transaction CRM_TL_ERP_BUS2032_DISPLAY tries to access system MSVL200A (which is the Development ECC System).
I cannot change the Logical System within the Transaction Launcher Configuration (currently it is set to ERP), since the Transaction is standard.
Does anybody know how to map the generic value ERP with the correct value MQAS200A instead of MSVL200A?
Thanks in advance,
Regards,
Andrea Ricci

Hi,
You cannot generalize the Logical system name, for the workaround you need to put the logical system for quality and transport it to quality and it should work and to check in dev you need to again change the log. sys to dev and save it but dont transport it. Similarly you can do for production system.
Regards,
Shobhit

Define Logical Systems and Template Names for BW Reports

Hi experts
I would like to know if someone used the mentioned functionality 'Define Logical Systems and Template Names for BW Reports, I would like to know too IF I create a Z REPORT for example in webdynpro and insert it in this configuration it will work and where it will appear in sourcing cockpit?
sds.
Javier

Hello Muthu,
BW reports will be shown in SRM Box if the corresponding BW roles for SRM are integrated with SRM roles.
You might to activate the corresponding datasource of this in SRM.
And since you have to connect the source system to BW, I think you have to define SRM system as logical system in BW.
Regards,
Pavan

Charam - System cancel RFC destination SM_GSPCLNT300_TMW, Call BAPI_USER_EX

While configuring charm for my prd rfc im getting following error.
System cancel RFC destination SM_GSPCLNT300_TMW, Call BAPI_USER_EXISTENCE_CHECK: Password logon no longer possible - too many faile d attempts
RFC connection of type SPACE does not exist
RFC connection of type S does not exist
RFC connection of type T does not exist
System cancel RFC destination SM_GSPCLNT300_TMW, Call BAPI_USER_EXISTENCE_CHECK: Password
Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for GSP-300
Any solutions for this

Hi,
Please ensure RFC connection to GSPCLNT300 is working fine. You can go to SM59 to perform authorization testing. User & password set in RFC should match in GSPCLNT300. also, check logon group "SPACE" as well.
Thanks,
Nicholas Chang

Logical system and rfc destination

Similar Messages

Maybe you are looking for