RFC system name...

Hi Experts,
I am a beginner , So please dont mind if my language is not proffessional...
i am creating a RFC application for which i want to know my system name...so that i can create a function module on one system and another call it from another system...
I have tried to find it on my R/3 system platform but it is showing the same system name on both systems...
please help me...
Thank you...
Shrikant.

When calling FM from one system(source) to another system (target), you need to create an RFC Destination in SM59 (in source).
You can give any name to the target system and provide the details of the system to be called. (IP/System no/login details etc for target).
Then in the FM call you can provide the name of the target system (RFC destination) that you have created.
Regards,
Aj

Similar Messages

How to get RFC Destination and Logical System name dynamically

Hi all,
I have a RFC FM written in CRM. I need to call this FM in R/3. So, i use the syntax " Call function <func> destination <destination name>. My problem is that i need to fetch the destination name dynamically..
There is a way to do so in CRM which is as follows:
DATA: lt_siteselect TYPE TABLE OF siteselect INITIAL SIZE 0,
           ls_siteselect TYPE siteselect.
CALL FUNCTION 'SMOF0_READ_SITESELECT'
    TABLES
      to_siteselect = lt_siteselect.
READ TABLE lt_siteselect INTO ls_siteselect
         WITH KEY sitetypeid = cl_smw1_siteprovider=>c_sitetype_r3oltp.
The above piece of code returns the site and also takes care of the client you are currently working on. But the specified FM is present only in R/3..
I want to achieve the functionality fulfilled by the above code in R/3.
Kindly help.
Useful answers will be rewarded.
Thanks in advance,
Karan Merwana
I can not use FM LOG_SYSTEM_GET_RFC_DESTINATION as for that i need to provide the logical system name. And the logical system name would be different for different clients.
Message was edited by:
        Karan Merwana

For those referring this thread later, I could not find a solution to this and ultimately had to do away with hardcoding of system names based on the DEV, Q, and PROD system names.
If anyone does manage to get a workaround, please let me know.

RFC and Logical System names

Hello......is it necessary to have RFC and Logical system name for the connected system to be identical?Is there any explanation behind this if thats true....

Hi Gaurav,
It is recommended, but not mandatory, right, Muthuraman?
The system uses some transactions to determine which RFC will be used for the communication between one system and another, for example, in transaction 'Define backend systems' in SPRO, you can define that the current SRM client has an ECC backend system named X and the RFC destination for this X system is Y (not necessarily the same name).
Regards,

Changing the default logical system names for adaptive RFC models

Hello,
When I create an Adaptive RFC model the dialog that asks me to specify the model name, package, source folder, etc. has default values in the "Default logical system name for model instances" and "... RFC metadata".
I know I can type in another name there but I'd like to change the default name to something that fits our naming conventions. Can I change that? If so, can someone tell me where?
Thanks in advance!
David.

Suresh,
Thank you for your response. However, that is not what I was looking for. Sorry if my post was not clear.
I knew that I could change it AFTER the import. I also know that I can type in something else besides the default DURING the import.
What I am asking is if there is a way to change some configuration setting so that the 'default' that comes up in the drop down DURING the import is something different than what comes 'out-of-the-box' with NWDS.
Hope that clears up what I'm looking for.
David.
Message was edited by:
David Z. Pantich

CCDB - RFC System Failure / Name or password is incorrect

SolMan 7.1 SPS10
TCode CCDB -> Techical Systems -> SM 7.1 ABAP -> 1 Error Main States :
Store Name: STANDARD_USERS
Group Name: ABAP~Security
Store Type: Table store
In "StoreDetails" -> Check Store return: "The status of the Store is still valid." , on "Log" Tab next message: "Upload failed 'Extractor Error' . RFC System Failure / Password logon no longer possible - too many failed"
What RFC & Login is used?
How to solve a problem ?

Hi Mikhail,
Please check the READ RFC destination for this system and user maintained is not locked.
Perform the authorization test for this RFC and check the results.
Hope this helps.
Thanks & Regards,
Nisha

Reg: Table name where logical system name will store in R/3 and CRM..

Hi
We are trying to replicate the sales order from CRM 5.0 to ECC 6.0. we mainatined publication, site, subscription and rfc connections. When the sales order is created in the CRM the BDOC is getting posted but it is picking up the wrong logical system which we were using earlier. Due to this wrong logical system, out-bound queue is getting generated in CRM but In-bound queue is not getting generated in the ECC.
Can anybody tell me where (in which table) we need to modify the things for getting the correct logical system.
Regards

Hi,
In CRM: look for the table CRMMLSGUID. This should have the logical system name of the R/3 that it is connected to CRM and also the GUID. To check if the GUID is correct cross check with GUID from R/3 table CRMPRLS.
In R/3: look for the table CRMRFCPAR. This will give you all the RFC connections that R3 is connected to. If you want to check whether the CRM RFC value is defined correctly compare it with RFC destination in the Administration Console (smoeac) from CRM.
If the entries are matching then the systems are connected correctly if not you need to look at the RFC destinations from SM59 transaction.
Hope this helps.
Thanks,
Karuna.

Logical System and Logical System Name

Hi,
I would like to create the following and please tell me how do I go about doing this. I am doing this because I am trying to implement both RFC/Idoc to File and File to Idoc/RFC. The basis admin guys are unavailble at the moment so I am on my own at this moment.
Creating a port(I suppose I need to do this on the R3. What are the steps involved)
Create a Partner Profile

Hi Sonia,
For XI communicating with SAP R/3 through Idocs ALE settings need to be done,
just go through the following steps and Configure ALE :-
SAP XI
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) Gateway service is 3300+system number#.
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
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
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) Gateway service is 3300+system number#.
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 (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination 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
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards,
Ashwin M
Reward If helpful

Business system and logical system names

hello experts,
Right now m creating scenarios of IDOCs, Files and RFCs. Just wanted to know that is it compulsory to give Business system name and Logical system names same?
Does it make difference if i will give both names different?
Regards,
H.S.

Hi,
I guess i have not explained you proprely.
Here logical system mean m asking abt the system name which we are using in RFC connections to make connection between two systems.
does Business system name and Logical system name should be same?
Actually right now we have done system copy of production system into our sandbox. So all the things are pointing to the production system.
I was just wondering, if i will just change ip/ hostname into the Technical system (ip of sandbox system) and keep business system name as it is( which is right now of production system)... then for me no need to create all ID Objects again. Its just an idea. So just wanted to check is it ok... bcz in ID i have more than 60 objects which i need to create again. and i have very less time
Or if anyone can tell me any good idea to do that.
Thankx in advance.
Regards,
H.S.

Logical system name has not been assigned to

Hi, Expert
I m trying to transferr DATA from ECC to APO . when I configured my ECC and APO systems according the SCM 210, but I still meet the error like this
logical system name has not been assigned to
syste: user:
Function/Q/SAPAPO/CIF_PRODUCT_INBOUND
text: logical system name has not been assigned to
my ECC is ECC6.0,and APO 7.0
Can u help me,Thank u. I m waiting the solution on desk
Rockey
Edited by: Xinyou Dong on Jun 2, 2011 9:11 AM

Hi,
I think you dont have partner profile created.
Try to create one with the RFC which is connecting ECC and APO.
Thanks,
Deepthi

Logical System Name after System Copy

Hello,
I have three questions about the logical system name after system copy.
Q1) When I change SID D22 to S11 during system copy,
do I have to change the logical system name of all clients in the target system? The target system is used for test, and the landscape has S11 and Virtial system. The target system S11 does not communicate with the source system D22.
Q2) If the answer for Q1 is YES, is it correct that the following procedure for changing logical system name?
1.Tr-CD:BD54
Add new logical system name for all clients in the target system.
2.Tr-CD:SCC4
As for all clients, select new logical system name with F4 help.
Q3) If the answer for Q1 is YES, do I have to add new RFC connection entries with SM59 for all clients in the target system?
I refer to the guide "Homogeneous and Heterogeneous
System Copy for SAP Systems Based
on SAP Web Application Server
ABAP 6.40 SR1".
thanks,
Keishi

Hi Keishi,
As a good and ideal practice the answer to your first question Q1 is yes. Infact I would say that in case you are using ALE then it is must
For Q2 there has to be an additional step which is most important one. Running BDLS transaction which would allow you to change logical systems in relevant tables from the one of source system to target system.
For Q3 the answer is agaain yes and you can have two approaches>
1. manually recreate all the RFC destinations after sys. copy.
2. Export all the RFC destination data relevant tables before system copy and then reimport them after sys. copy.
Regards.
Ruchit.

How to change or rename the logical system name T90CLNT090 IN BI 7

HI Expert's,
i am really digging for the solution of changing or renaming the logical system name technical name T90CLNT090.
in our company we are using ecc5.0 with bi 3.5 and ecc6 with bi 7. In BW 3.5 having a connection with R/3 and the technical name of the myself bw source system(logical system) is T90CLNT090.
In bi 7 also the logical system name is same as T90CLNT090. Because of the same system name(Logical name) it is not active in BI7 and also it's giving error when i am activating the DSO Object as Transfer structure prefix for source system T90CLNT090 is not defined.
because of this i am not able to create the source system between r/3 also.
so how to change this source system name for T90CLNT090.
regards
harikrishna N

Hi,
Pls follow this OSS note : 325525.
Note 325525 - Copying and renaming systems in a BW environment
Summary
Symptom WARNING: THIS NOTE HAS BEEN REPLACED. FOR MORE CURRENT AND MORE COMPREHENSIVE INFORMATION SEE NEW NOTE 886102.
You want to copy and or rename one or more systems (database or client copy). One or more of the systems is a BW system or is connected to a BW system.
Caution: This note only deals with problems that occur in the BW source system connections. Other problems that occur in the BW environment (indexes) are NOT dealt with. See URL http://www.service.sap.com/bw --> Services & Implementation --> System copy & Migration.
Other terms BW, source system, OLTP, database copy, client copy, system infrastructure, transport system, connections, RFC connection, trfc, transfer structure, IDoc, ALE customizing, logical system name, system changeability, renaming systems, system copy
Solution Several scenarios are possible in this environment. Find the scenario relevant to your situation below and execute the steps listed or read the note(s) specified:
Scenario 1) You do not want to copy a system but only want to rename one (changing a logical system name).
           Solution scenario 1): Execute Transaction BDLS both in the client to be renamed and in the connected BWs or BW source systems. To do this, see Notes 121163 and 369758.
           Check the RFC destinations in all connected BWs/BW source systems as described in Note 524554.
           Reactivate all partner agreements that carry the new logical system name after renaming.
Scenario 2) You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group) by a database copy. SAP recommends this procedure for copying systems.
           Solution scenario 2):
If you want to rename one or more of the copied systems, then execute Transaction BDLS both in the client you wish to rename and in all the connected BW and BW source systems. See Note 121163.
                    Make sure that an RFC destination exists with the new logical name in every connected BW or BW source system.
                    Reactivate all partner agreements that carry the new logical system name after renaming.
Change the hosts in the appropriate RFC destinations so that they refer to the correct computer. For this, see Note 524554.
Scenario 3) You want to copy a single BW system of the group by database copy.
Scenario 3)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 3)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 3)b) You want to keep the original system of the copy so that you have two systems after copying.
                     Solution scenario 3)b): See Note 184754.
Scenario 4) You want to copy a single source system of the group by database copy.
Scenario 4)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 4)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 4)b) You want to keep the original system of the copy so that you have two systems after copying.
           Solution scenario 4)b): See Note 184322.
Scenario 5) You want to import a client copy in a source system.
           Solution scenario 5): See Note 325470.
Thanks & Regards,
Suchitra.V

Delta and logycal system name

Hi!
I have two identical BW systems: one is a copy another system.
BW1 - original system.
BW2 - copy.
We need 10 days to convert BW2 to UNICODE. During these 10 days datas are loaded from SAP ERP to original system, BW1.
After we convert BW2 to UNICODE we need to load delta-data(which we loaded to BW1 during 10 days) from BW1 to BW2.
How can we do it? We can't stop to load data during 10 days.
I want to create RFC-connection between BW1 and BW2, then replicate data sources, create transformations and DTPs between the same objects (cube or DSO). But how I can find out this delta?
For example, I have two cubes, one cube1 is from BW1, cube1 is from BW2. There are 5 requests in cube1, and 3 requests in cube2. I know that two last requests from cube1 I need to load to cube2, but in DTP I can't choose request filter.
Any idea?
I have another problem: these BW systems have identical logical system name. In future I would delete BW1 and use BW2.
If I rename logical system name of BW2 then I will destroy delta loadings from SAP ERP, because delta is depended on BW logical name.

Hello KEU,
I understand your issue like below:
1. BW1 & BW2 is non-unicode at present. BW2 is a copy of BW1 and hence BW2 objects also non-unicode and you want to migrate all the data and objects into Unicode at present.
2. BW1 is connected to the ECC and you need to dump all the Delta data for the 10 days of period to be posted into BW2 so that you can connect BW2 to ECC once BW1 is retired after the Unicode migration.
You have the below possibilities..
1. Connect BW1 and BW2 thru RFC and create a BW1 source system in BW2. Now you need to replicate all data sources from BW1 source system in BW2. Create required transformations which are necessary to connect to the required targets.
2. To load the Delta data you need a right strategy so that dont miss any of the information from BW1 to BW2. I can say as you are in BI7.0 you have the PSA to store all the data in all the trasactional targets where you are looking to move the data.
- For me you have to take care of this once after the copy is done -
Maintain the connection as stated earlier, create the neceaary transformation, and then you need to maintain the init without data transfer in BW2 for the required data sources (8**) so that the Delta data can be pusched from there onwards. So this is required for all the data flows with respect to the individual targets where are getting oprated with DELTA loads...
-- If you have missed then the other option is that, make sure that in BW1 the data is updated in the targets as per the data flow like target 1 to final targets (considering there is no compression), as you have the PSA's for all the data flows, you need to delete the entries which are made after the system copy is done, so that BW1 and BW2 are at the same level, once after this initi without data transfer needs to be done in BW2. Once this is done you need to reconstruct all the deleted entries in the total flow so that there will not be any data mart symbol exisits so that it can be pushed in the Delta load in BW2. (This operation needs to be handled carefully. If not clear then its not suggestable). Also once the Delta loads are moved to BW2, then you need to work in BW1 to maintain the proper Init status.
3. The final option is to get the 10 days of Data in a flat file from different targets in BW1 and then maintain a right strategy to load the same in the respective targets in BW2. Needs proper attention.
So handle the points carefully as its a complex situation.
Hope this helps..
Murali
Edited by: Murali M on Aug 29, 2010 9:10 AM

RFC & Logical Name difference-connectivity

Hi
I have by mistake given different name of logical & RFC systems in CRM & ECC. Like if name of logical & RFC systems in CRM is X, then in ECC I have named them as Y.
Now I have downloaded BP & Products without any problem. My question is :
In future can it cause, problem in any way. I have seen various documents but no where it is mentioned that they have to be same in the two systems.
Thanx in advance.
Cheers
Hits

Hi Piyush
Thanx for your reply. In my scenario name of CRM system is different in ECC & CRM. In CRM I have defined RFC & Logical CRM system name as X, whereas in ECC it is Y.
When I goto SMWP for adapter status information, in ECC table CRMRFCPAR it is expecting value X. The status of adapter status is yellow. Till now I have downloaded product & BP, no problem has occured.
Cheers
Hits

Business system name important for IDoc scenario message routing?

Hello all,
I have following problem.
I have to setup with our client an IDoc scenario which is a little difficult.
The client sends project IDocs from Client ERP system to his own XI system next to our XI sytem and at last Internal Order IDocs to our ERP system. We use for each environments (DEV, TEST, PROD) a separately SLD, the client a central SLD. In each environments we use the same business name for our XI system "BS_XI". Now the problem. The client aren't able to configure two times the same business name "BS_XI" for routing to our TEST respective Production environment. DEV will not used. I know the B2B scenario should be used in this case but i have no chance to think about this. Manager decision!
So what can be the workaround.
I think about to provide our client a different Business system name "BS_XI_PROD" with different technical system informations for our PROD environment. So for my understanding, the business system name is unimportant in this case, important here the technical informations which you are able to see in "Display Adapter-Specific Identifiers". Technical system, Port and RFC configuration.
The namings convention for Business system is unimportant in this case, yes?
Many thanks in advance!
Regards,
Jochen

Dear Jochen,
Can you please clarify a bit? Is it a problem between customer's XI system and your XI system?
I think you can use Parties here. In the Party you can define some additional identifiers, with which you can differentiate the incoming IDocs.
(e.g.: in the identifiers tab, Agency=BS_XI, Scheme=ALE#KU (defined in the customer's partner profile), Name=a defined name in the IDoc control record)
So with this you will have a "Business System+Party" as an identifier, where you can use several parties with the same business system.
I hope it helps!
Regards,
Andras

Changing Default logical system names of a model.

Hi
    How could i change the
     Default logical system name for model instances:
     Default logical syatem name for RFC metadata:
    values for existing model? without recreating the model.
     Thanx

Hi shah kond,
you can change rfc destinations of model in 2 differnet ways.
firs one: right clcik on project
          from the context menu select propeties
          it will open a dialogbox from that select dynpro references then click on jco references tab
by using add and remove buttons u can add and remove joc destnations
2.expand ur model class double click output class.now seelct properties view.there u can change the jco destination
hope this will use ful for u
Regards
Naidu

RFC system name...

Similar Messages

Maybe you are looking for