In middleware why we give RFC destination as CRM and consumer as SRM?

Hi friends
In middleware why we give RFC destination as CRM and consumer as SRM
Regards
Vinny

Hi,
As Michaels said SRM and CRM are developed on same base and even still now if you go and check some tables u will find dataelements and others with CRM extension.
Regards
Anil

Similar Messages

Why to give "HTTP Destination" for Webservice automation using eCATT

Hi,
can anybody tell me, for Webservice automation why to give "HTTP Destination" in System Data Container when we have "RFC Destination" to connect to Target System.
Best Regards,
Pradeep
Edited by: Pradeep Singh Rawat on Jul 15, 2009 8:17 AM

Hi pradeep,
Any SOA architecture follows below process
Consumer -call ->HTTP layer( SOAP)->WS layer-->Application->DB
Our WS data is in WS layer mostly in form of XML,
To call any XML code we need a SOAP protocol and we need HTTP for this.
I hope you question is answered.
regards
vinay

Why Firefox Has Spikes In CPU Usage And Consumes A Lot Of RAM Since Security Update?

After applying security update 3.6.18 i started having this problem. I had this problem earlier but it only happened after several days Firefox was opened constantly. Now i have this problem several hours later after launching Firefox.
[http://i.stack.imgur.com/PJmH5.png '''Here is a picture of high RAM usage''']
'''[http://i.stack.imgur.com/tjsqt.png Here is a picture of high RAM and CPU usage]'''
I have Flash disabled.
What is going on? Should i reinstall Firefox 3.6.18?

Have you any particular reason for using an older version of Firefox.
Whilst I rarely use firefox 3.6 now, and do not know the answer I will comment that the now unsupported firefox 4 did have bad memory problems in some cases. Some of those problems were addressed in firefox 5, and others are addressed in Firefox 7, which is due out on the Aurora channel next week.
You could consider upgrading to a newer version of firefox. If you need firefox3.6 only for limited use you could consider using Firefox portable, alongside a newer version of Firefox.
* portable: http://portableapps.com/apps/internet/firefox_portable/localization#legacy36
* see also
**[[installing a previous version of firefox]]
**[[high memory usage]]
**[[firefox consumes a lot of CPU resources]]

Why do we need to define RFC destination and user for material replication

Dear Experts,
why do we need to define RFC destination and user for material replication? Here we use crm middleware only for material replication. Could you please help me to understand it?
regards,
Ranjan

Hello,
As far as I know, you can use the same RFC destination already available in ECC to SRM to replicate materials.
You can refer to note 720819.
Regards,
Ricardo

Creation of RFC Destination for Syncronouse RFC adapter.

Hi,
Can any one please give me step by step process to create RFC destination in XI and SAP-R3. plz help me out
thanks,
dhanush.

No one is going to help you if you keep posting same question multiple times.
You need to priovide more details on what you are doing ? There are many reasons why you create a RFC destination in XI and R3. There are multiple types of RFC destinations. What is the end to end scenario you want to implement. It all depends on this. Try to provide more details.
Regards
Bhavesh

RFC Destination was incorrect,send complete BP Data again from CRM to R3

Hello All
Iam facing in issue in CRM - BP Application due to incorrect RFC Destination maintained for SAP R3.
Our CRM Testing system (CRO - Client 300) is connected to R3 Testing System (NCQ - Client 300), but when CRM system went for refresh, RFC Destination was overwritten, and due to that CRM system started pointing to wrong R3 server (NCD - Client 002).
Till we got to know the problem, User had created a BP in CRM and it had flown to incorrect server. later we corrected the RFC Destination , but now the issue is that If I make any small change in CRM BP data, Bdoc is going in error state and message says:
Messages for business partner 0090001677:
No customer is assigned to business partner 4A13ACE0AB356006E10000000A212
Entry 0500 does not exist in - check your entry
I tried to send BP data through middleware tCode /CRMM_Bupa_Send as well, but Bdoc gain got in error state saying :
Entry 0500 does not exist in - check your entry
I think, these errors are coming because system is assuming that it has already sent the data to R3, and it expects certain data to be present in R3 system, which it is unable to find since data for corresponding BP is not present in SAP R3.
I there any way, transaction through which I can send complete BP data from CRM to R3??? Please help.
Edited by: Surbhi Goel on Jun 2, 2009 3:25 PM

Hi Surbhi,
Could you try transaction CRMM_BUPA_MAP in order to see what mapping the system thinks there is (if any). It then allows you to send (same as BUPA_SEND) or retrieve data. I guess this will run into the same error, but it might be worth a try.
Hope this helps.
Sincerely,
KZ

Error in SWF_XI_CUSTOMIZING - Configure RFC Destination

Dear Experts,
Basis team is performing PI 7.1(EHP1 - SP04) readiness check. We are not able to activate Configure RFC Destination. Please refer the following attachment.
We have checked if WF-BATCH user got locked. It is fine and in unlocked status. Is there any setting which are missing? Thanks in Advance.
[http://www.flickr.com/photos/49754947@N07/4657473257/]
Thanks,
Phani Akella.

Hi Phani,
Create a RFC connection of type R/3 in the transaction SM59.
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f62cfa8911d386e70000e82011b8/frameset.htm
Or you may go to:
Tcode SM59 -> R/3 connections -> Create
1) Give RFC destination name.
2) Connection type - 3.
3) Technical settings tab -> Target Host -> give the Application Server name -> press enter.
The IP address automatically gets filled up.
4) Logon security tab -> Assign the Logon details.
Also, on the button of the image you posted there is a:
"No Language Can Be Defined for the RFC Destination"
Check for that too.
Regards,
Caio Cagnani

How to find out, which RFC-Destinations are in use?

Hi community
We have a huge list of RFC-Destinations in our productive system and I want to delete unneeded entries.
Is there a report or a log, which shows, which RFC-Destinations were used, and when?
Thanks in advance.
Regards, Michael

HI
can you see the default trace in tcode SMGW, Be careful about deleting any system rfc.
Read the documentation about default RFC, internal RFC, LDAP_RFC, transport RFC.
I don't know other way to do that you need
Regards
William Neira

Clarification regarding RFC destination

Hi Ramesh,
Thanks for your information, can you please tell me do we need to create port and logical system name for creating RFC destination.
Thank
siva

Siva,
You do not need to create port / logical system while creating RFC destination.
Port and Logical system comes into picture while setting up Partner profile for idoc communication.
Nilesh

RFC destination & Port Configuration in XI

Hi All,
I have sap system with 2 client 230 and 231. The RFCdestination,IDX1 and IDX2 are configured in XI and I am able to send the IDoc successfully. But in case of client 231 I got a doubt that we can use the same RFCdestination, port if I am going to send the same IDoc.
As per my undestanding we need to create RFCdestination , port for each and every client separately please tell me whether it is right and sorry for asking silly doubt but got confused to proceed futher.
Regards,
Dhill.

Hi wojciech,
Thank you one moer clarification required that in case of my sap system I think we can use the same RFC destination,Partner Profile and port because I am going to connect to the same XI server.
And also with regards to IDX2 I think we don't need o add the same IDoc in both the client. Since it is only the metadata please confirm on this.
Regards,
Dhill

RFC destination for VMC (Virtual Machine Container)

Hi ,
Just loaded the CRM 70 system (customers, materials, contacts, ... ) and the KB from the back-office (ECC 6.0).
Calling the IPC via transaction COMMPR01 for a configurable material we have the following call in error :
FUNCTION ipc_get_knowledgebase.
CALL FUNCTION 'CFG_API_GET_KNOWLEDGEBASE' DESTINATION gv_vmc_dest
The RFC destination 'gv_vmc_dest' is empty . How to setup the RFC destination for VMC and the configuration so SAP know the RFC destination is the one to use for the VMC.
Thank you

Klaus ,
Thank you , yes VMC is on the same CRM7.0 server , I do get the following short-dump .
Short text
    "Found no handler for remote function module CFG_API_GET_KNOWLEDGEBASE"
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLIPC_API_CFG_COMMAND" had to be terminated because
     it has
    come across a statement that unfortunately cannot be executed.
    The error occurred during an RFC call to another system.
    In the target system, a short dump has been written as well.
    More detailed information on the error cause can be found there.
Error analysis
    An error occurred when executing a REMOTE FUNCTION CALL.
    It was logged under the name "RFC_EXTERNAL_ABORT"
    on the called page.
Trigger Location of Runtime Error
    Program                                 SAPLIPC_API_CFG_COMMAND
    Include                                 LIPC_API_CFG_COMMANDU07
    Row                                     19
    Module type                             (FUNCTION)
    Module Name                             IPC_GET_KNOWLEDGEBASE

Steps to create rfc destination

hi,
what are the steps to create rfc destination

Follow the following steps :
1. Create RFC destination for both the systems on CRM and R/3 in SM59.
2. Create the logical systems and assign clients to logical system in SALE transaction both on CRM and R/3.
3. Create a user in the R/3 table CRMCONSUM with the name CRM.
4. Maintain the Middlware Parameter tables on CRM : Table SMOFPARSFA:
Create an entry for following parameter entry:
Key - R3A_COMMON
Para name - CRM_DEFAULT_DESTINATION
Value - R/3 logical system
5. Maintain the parameter tables on R/3 system : CRMRFCPAR, CRMPAROLTP
CRMRFCPAR :
Create new entry with following data:
User - CRM
Object name - *
RFC Destination - RFC destination for CRM
Load types - All Load Types
In Queue flag - X
Send XML No XML
CRMPAROLTP :
Create the following parameter entry:
Para name - CRM_DEFAULT_DESTINATION
User - CRM
Value - Name of the CRM logical system
6. Create Sites and attach subscriptions in Admin Console : Tcode SMOEAC
Create a Site as CRM and another as R/3. Attach the required subscriptions to the R/3 site.
7. Register the queues in SMQR and SMQS transactions.
PS : For detailed steps refer the Middlware Base Customizings(CR500 and CR100)
Regards.

Logs of used rfc destinations

Hi Guys,
i'm looking for some tables including log-information of used rfc destinations. For now i have table EDIDC for IDoc-Logs. Do you know more tables, e.g. regarding BAPI usage? RFC logs in general (here i found ARFCSSTATE/ARFCRSTATE and some others, but they don't look as they would log all records, do they?
i just want to find out which rfc destinations are used and which not!
Best Regards
Stefan

Hi Stefan,
Generally we will RFC logs from SM58.
(Or) Check tcode SLG1 for application Log.
Thanks,
Krishna.

RFC connection - SAP CRM to SAP R/3

Hello all,
We have a requirement in the project, where client is already using SAP R/3 ERP system, and is going for CRM for e-commerce. Now as they have most of the development already done in R/3, they want to use some Function Module or say Report Program already developed in R/3 to be used in CRM system.
Please tell, if this thing is possible via RFC connection, and if yes, then how can we go about doing it? It is a critical requirement.
Thanks in advance,
Rohit Khetarpal

In transaction sm59 define an rfc destination in CRM that connects back to R/3.
You most likely already have one for bdocs etc. You can use this one or create one specific to your task.
Create an RFC user in R/3 that will have sufficent authorization to run your remote enabled function modules in R/3. Assign the user to your new CRM rfc destination in sm59 if you've created a new rfc destination.
Make sure the remote enabled check box in your R/3 function modlule attributes are ticked.
In your CRM program call the R/3 function module with the name of the rfc destination you created, as below.
call function ' my_r3_function_module_name' destination 'the_rfc_destination_name'.
You will need to add in the fm interface manually, i.e. importing, exporting, etc.

Any SAP Note for RFC Error between BI and ECC 5.0

Hi..
the RFC Destination between BI and ECC 5.0 is giving errors.
Plz let me know if there is any Support pack or any solution to fix this error.
thanks..

Hi,
pls find the RFC connection details
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Technical name Description File name for upload
B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu Define Client Administration (SAP R/3)
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1. Choose Display  Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
u2022 Automatic recording of changes
u2022 Changes to Repository and cross-client Customizing allowed
u2022 eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code SPRO
SAP R/3
IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
Log. System Name
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Assign Logical System to Client
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Creating an RFC User (SAP R/3)
Transaction Code SU01
SAP R/3 Menu Tools  Administration  User Maintenance  Users
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type System
Password LOGIN
Profile
Profiles SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language EN
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
SAP BW Role Menu Local Settings ® Define Client Administration
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
Transaction Code SPRO
IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
Field name Description R/O/C User action and values Note
Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
Name Textual Description of the Logical System Enter a clear description for the logical BW system
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu Assigning Logical System to Client (SAP BW)
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
1. In the view Display View "Clients": Overview, choose Display.  Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Modeling  Administrator Workbench: Modeling
Transaction Code RSA1
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Creating RFC User
Transaction Code SU01
SAP BW Menu Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
Field Entry
User RFCUSER
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
Field Entry
Last Name RFCUSER
Function Default-User for RFC connection
c. Choose the Logon data tab.
d. Enter the following data:
Field Entry
Password LOGIN
User type System
e. Choose the Profiles tab.
f. Enter the following data:
Field Entry
Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu Define RFC-USER as default (SAP BW)
Transaction Code RSA1
SAP BW Menu Modeling  Administrator Workbench: Modeling
1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
a. Choose Display  Change.
b. Enter RFCUSER in the BW User ALE field.
c. Choose Save.
Hope this helps in solving u r problem
Regards
Ramakrishna Kamurthy

In middleware why we give RFC destination as CRM and consumer as SRM?

Similar Messages

Maybe you are looking for