Monitoring of remote system's Transactional RFC and Queued RFC

Hello,
In our production system, in rz20- CCMS monitor templates- Communication-Transactional RFC and Queued RFc- outbound queues- Queues otherwise not monitored we can see blocked queues for each client.
System is connected to solution manager and we wish the central auto reaction is implemented in solution manager
However i am unable to find Transactional RFC and Queued RFC for the remote system, they exist only for solution manager itself
Tell me how can i do the central monitoring

Hello,
First you need to check with your Landscape in solman in order to monitor any kind of activities to do so pls follow these steps.
Go to SMSY in solman under Landscape components>Product systemsselect you satellite system example SAP ECC.
On the main screen you will find client for which you have generated RFC connection. Please check though connection are working fine, Go to edit mode and try to click on generate button there will be a pop-up, which gives a clear picture of RFC connection which already exists, and you can also re-generate this RFC connection by clean it up when you re-generate pls select under Actions after generation assign RFC dest for system monitoring.
But make sure there is no project impact on this RFC, like they are not using any logical components and already have some projects running on this RFC connection.
I would advise you to first you the option of assign and check RFC button which is next to generate icon.
Regards
JUDE

Similar Messages

CCMS qRFC Monitoring: Missing Transactional and Queued RFC Monitoring Nodes

Hi ,
We are trying to create a Queued RFC monitoring for VERTEX Queued , but we are missing CCMS Monitor Templates,in monitor Communications -->Transactional RFC and Queued RFC in Dev and PROD ,but its present in QA System .
I have checked all system are at same level for support packs , kernel version .
I have refered following Notes - 441269,437187,455431, 485826
Can we create manually new one , but we are missing MTE class also ?
Can we create new monitoring template ?
We are running 4.6c with basis support pack level :
SAP_BASIS 46C 0054 SAPKB46C54
SAP_ABA 46C 0054 SAPKA46C54
Thanks
Hamendra

Hamendra,
Please make sure background dispatching is activated in your system. Go to tcode RZ21 and menu Technical Infrastructure --> Method execution --> Active background dispatching.
This should schedule a job called SAP_CCMS_MONI_BATCH_DP. This is the job that will run the function for building the ALE/EDI monitoring segment.
After scheduling the job check back in a few hours, if the ALE/EDI monitor is still not there try the following.
1. Go to tcode RZ21
2. In the topology section choose radio button "Segment overview" and click display
3. Go into change mode and delete the monitoring segments
This will force the system to recreate all the monitoring contexts.
Check back in a few hours and see if the monitor is working.
Tarkesh

File to RFC, and through RFC response i am trying to trigger the Mail adapt

Hi All,
Right now i am doing File to RFC, its working fine but now the requirement is when xi connect to ftp and picks the file need to send one success mail after the file pickup and data sent to BW system again i need to send one mail and also error alerts to inbox.
Till now i am not using BPM, can we do this without BPM pls let me know
now i am trying to achieve this in File to RFC, and through RFC response i am trying to trigger the Mail adapter.
or else i need use only BPM pls share the steps which i need to be configure.
Am i correct or pls suggest me some idea to achive this and also pls share some smaple ones in BPM .
Thanks in advance
Venkat

With BPm, follow this:
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Instead of receiving the response in file, use mail adapter
Regards,
Prateek

Purpose of RFC and JCO-RFC destinations

Hi,
Can you please tell me what is the purpose of RFC and JCO-RFC destinations and where do we create them.
Regards
Rahul

Hi,
RFCs are SAP interfaces for communicating between SAP systems. They accept inputs, do the processing and return the output values. You can call rfcs through different applications like web dynpro.
http://help.sap.com/SAPhelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
JCO helps Java applications to connect and communicate with SAP backend systems. Using JCO we can make rfc calls. JCO will help in getting the rfcs in a java compatible format.
http://help.sap.com/saphelp_nw04/Helpdata/EN/6f/1bd5c6a85b11d6b28500508b5d5211/content.htm
Example for setting up jco destinations:
http://help.sap.com/saphelp_erp60/helpdata/EN/ca/115e4088dc0272e10000000a155106/content.htm
Regards,
Shyam.

Configuring ccms to monitor a remote system

Hi.
Im trying to configure my ccms system to monitor a remote epp 6.0.
As it is now, the epp has a ccms agent installed.
Question is:
how and where do I change the agent to send data to my ccms and not to the currently configured system.
and.
when I click "agent working dir" on the ccms system. (under agents for remote SAP system tab) I get this:
Cannot display information due to older age
I know this is sparse info, but what Im looking for are pointers to help me on the way...maybe someone has "the link" im looking for.
I have created an rfc to the remote system. A type T to program ID: host.sapccmsr.99 this hos is the reciepient of the agent data as it is configured now... this host now, collects all ccms data..what I want is, my system to get this info

Hi
I'm getting exactly the same error message when playing back the script I've recorded. Albeit in our SAP system (not BW system)
I'm in our Development System at the moment and want to reply back into the same System that I have created the eCATT in and created the recording to run the eCATT in.
Did you manage to resolve this?
If so could you share
Thanks
Steve

Help required for Sender Proxy/RFC and Receiver RFC approach. Urgent please

Hi All,
I have one sender R/3 system
I have two receivers R/3 systems
Business Partners data from sender R/3 system needs to be repliacted to 2 receivers R/3 systems
From sender R/3 system one Sync Abap Client Proxy or
Sync RFC will send Business Partners data to XI.
For both receivers R/3 systems there is only one RFC Currently there is no flag condition for 2 receivers as this is
Business Partner replication scenario.
Also In XI there is restriction that multiple sync receivers cannot be there.
Please let me know how to make this approach.
Regards

Rich,
Create two O/B Interfaces - Synch. Create Proxy1 for O/B Interface1 , Proxy2 for O/B interface 2.
So while defining Receiver determinatio, you will define as following,
Receiver Determination----1
Sender : Sender_BusinessSystem
Sender Interface : O/B Interface 1 ( i.e Proxy1)
Receiver : BusinessSystem_ C
Interace Determination
Sender : Sender_BusinessSystem
Sender Interface : O/B Interface 1 ( i.e Proxy1)
Inbound Interface: RFC_Rec
Receiver Determination----2
Sender : Sender_BusinessSystem
Sender Interface : O/B Interface 2 ( i.e Proxy2)
Receiver : BusinessSystem_D
Interace Determination
Sender : Sender_BusinessSystem
Sender Interface : O/B Interface 2 ( i.e Proxy2)
Inbound Interface: RFC_Rec
Hope it helps!
raj.

What is RFC and how does work

Hi Sap Guru's
I want to know the RFC in SAP and how does it work?
Thanks in advance
Regards
Ramesh

Hi Ramesh,
These are the types of RFC
Asynchronous RFC (aRFC)
Synchronous RFC (sRFC)
Transactional RFC (tRFC)
Queued RFC (qRFC)
Parallel RFC (pRFC)
Asynchronous RFC :
This is used when you need to increase the performance of ABAP program by having system call more than one function module in parallel than forcing the program to wait for results .
Transactional RFC
This let you group one or more function module call together o tRFC LUW and ensure that fucnction module within LUW is called once . In contrast to aRFC and sRFC the tRFC belonging to tRFC LUW are executed in order .
tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls are
1.Executed in the order in which they are called
2.Executed in the same program context in the target system
3.Run as a single transaction: they are either committed or rolled back as a unit.
Implementation of tRFC is recommended if you want to guarantee that the transactional order of the calls is preserved
Asynchronous remote function calls (aRFCs) are similar to transactional RFCs, in that the user does not have to wait for their completion before continuing the calling dialog. There are three characteristics, however, that distinguish asynchronous RFCs from transactional RFCs:
When the caller starts an asynchronous RFC, the called server must be available to accept the request.
The parameters of asynchronous RFCs are not logged to the database, but sent directly to the server.
Asynchronous RFCs allow the user to carry on an interactive dialog with the remote system.
The calling program can receive results from the asynchronous RFC.
You can use asynchronous remote function calls whenever you need to establish communication with a remote system, but do not want to wait for the functions result before continuing processing. Asynchronous RFCs can also be sent to the same system. In this case, the system opens a new session (or window). You can then switch back and for between the calling dialog and the called session
RECEIVE RESULTS FROM FUNCTION Remotefunction is used within a FORM routine to receive the results of an asynchronous remote function call. The following receiving parameters are available:
IMPORTING
TABLES
EXCEPTIONS
The addition KEEPING TASK prevents an asynchronous connection from being closed after receiving the results of the processing. The relevant remote context (roll area) is kept for re-use until the caller terminates the connection.
Hope this resolves your query.
Reward all the helpful answers.
Regards

Differences between rfc and ale/idoc.

hi ..
       will u please send the differences between rfc and ale/idoc's.

Hi,
Please reward with points if helpful................
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
Application Link Enabling comprises the following three layers:
application services
distribution services
communication services
Two Development Models
     Distribution using BAPIs
     Distribution using Message type
The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
Defining message types and IDoc types:
If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
Writing ABAP code:
         Outbound Processing
           Inbound Processing
You can find information on other ALE functions under:
                               Master Data Distribution
                              Communicating with Non-R/3 Systems
1. The Remote Function Call facility allows you to call an R/3 Function module on a remote machine.
2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.
3. RFC or sRFC - Synchronous RFC
                 aRFC - Asynchronous RFC
                  tRFC - Transactional RFC
                  qRFC - Queued RFC (I.e. Serialization of tRFC)
Types of RFC Call
Synchronous
CALL FUNCTION Func Destination Dest
CALL FUNCTION func DESTINATION 'NONE' ...
CALL FUNCTION func DESTINATION BACK' ...
Asynchronous
CALL FUNCTION func STARTING NEW TASK taskname
PERFORMING form ON END OF TASK
RECEIVE RESULTS FROM FUNCTION func
Thanks
sivaparvathi

What is rfc. and uses

<u></u>what is rfc. and uses

Hi,
RFC
Remote Function Call:
RFCs are requests that an SAP component sends to invoke functions on remote systems, or calls that remote systems initiate to invoke functions on an SAP component.A process that can accept RFCs from SAP components. This allows SAP components to access functions in external systems. In SAP BC terminology, the process is called a Listener. Listeners are one or more threads on SAP Business Connector that wait for incoming requests from SAP components. Listeners are named and register with an SAP gateway to indicate that they are ready to accept requests. Listeners can accept RFC or tRFC requests.
Transactional RFC (tRFC) and Queued RFC (qRFC). tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
Transactional RFC:
If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
Queued RFC:
When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously.
RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.
RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.
RFCs manage the communication process, parameter transfer and error handling.
Have a look at this link.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
Please go through the following link. You will get good info on RFC & its types.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
Regards,
Priyanka.

Unable to Edit/Remove Remote Systems using MDM 7.1

Unable to find an answer to this in either the forums or the Wiki...
Using MDM 7.1 through the SAP MDM Console 7.1.03.54
I can add a new Remote System, it comes up with the default values for the Remote System fields:
Name: New Remote System, Code: NewRemoteSystem, Type: Inbound, Key Generation: None
But I cannot modify the field values nor can I delete the Remote System.
The right-click context menu always has 'Delete Remote System' greyed out.
Nor do I see any mechanism to modify the fields' values. Moving to the Remote System Detail pane, none of the fields are edittable; I have tried left-clicking, right-clicking, double clicking, using the Edit tool bar menu - nothing lets me edit these fields.
My user account has the Admin role. Looking to the Admin role, it has Execute for all functions, and Read-Write to the Remote Systems in the Tables and Fields tab.
Any help would be appreciated.

Hi Andrew,
Your repository should be in unloaded state to make changes in any table whether main table, subtable, Ports, Special tables or Remote Systems table etc. As you want to make changes in your repository Remote Systems, please unload your repository->Go to Admin>Remote systems>Make necessary changes (Add/Delete/update)--> Then load repository.
Note: You can only add User and Roles during Repository loaded state.
Regards,
Mandeep Saini

Unable to syndicate same Remote System with differnt value

Hi,
I am working on MDM 7.1 SP05 and I have the following issue with syndication:
I have a remote system table (Key Enabled) with System as Non-Qualifier and value as Qualifier and I have values in the MDM Datamanager as
MDM ID, Remotesystem (Multivalue Qualifier Table with Key Enabled)
111,((Qual1-Key,Val1),(Qual1-Key,Val2),(Qual1-Key,Val3))
When I syndicate I see only one value as 111, (Qual1,Val3)... But I want to have all the Qualifiers-Key with multiple values.. Where as in MDM 5.5 I can see all the Qualifiers with out any issues..Is this a restriction in MDM 7.1?
If I map System instead of Remote Key of Qualifier Table then I can see multiple times of same remote system with appropriate values.. But If I map remote key then I see the consolidated/the latest system-remote key wiht value... But I want system-remote key value appear multiple times...
Thanks alot
Rajeev

I am using customised...
Did you tried syndicating Remote key of that table or the field of the Qualifer table?
I am able to syndicate out with the system field and values.. But I want to syndicate out the multiple values wiht remote key of the table..
As mentioned Remote keys are AAA and BBB for System Sys1 and Sys2..
First I imported remote system table with Sys1 and Sys2 with remote Keys as AAA and BBB. then along wiht main table record I imported Sys1 and Sy2...
While Syndicating I want to syndicate AAA and BBB values along with Value field...
Suppose:
I have data :
MDM ID, RemoteSystem(System, Value)
111, ((Sys1,Val1),(Sys1,Val2),(Sys1,Val3),(Sys2,Val1))
Remote Keys for Sys1AAA and Sys2BBB
In the Syndication Manager I mapped as below: RemoteSystems RemoteKey and value are mapped to target...
RemoteSystem
--RemoteKey
System(DFNQ)
--Value(Qualifier)
I mapped RemoteKey and Value to the target fields.. Which is a XML output..
<REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>AAA</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val3</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>BBB</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val1</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
</REMOTE_SYSTEM>
Where I need the following Output:
<REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>AAA</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val1</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>AAA</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val2</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>AAA</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val3</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>BBB</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val1</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
</REMOTE_SYSTEM>
Any inputs.
Thanks
Rajeev

Remote System Explorer on a Wireless LAN

On a wireless LAN when I use Remote System Explorer, it knocks our Fieldpoint network modules off-line. We are unable to ping them. Once we restart the units, they work fine until someone uses the Remote System Explorer again. Any ideas?

We have FP1600s and FP2015s. It only affects certain FP1600s. Firmware revision is 3.0 on the 1600s. Some older ones are not affected and some newer ones are. We configure them in the shop on a LAN, then move them to a field environment. The only firewall is point of entry onto the post.
When using Remote System Explorer (the latest and greatest version), one at a time is "knocked off line". Every time Remote System Explorer refreshes another 1600 is knocked off line. I see no relevance to a crossover cable. This occurs over a WLAN. If we don't use Remote System Explorer then they just chug along fine.
I have used the FP1600 Diagnostic Utility which was a mistake. Now the status LEDs blinks red 7 times.

Handling process in a remote system

how to list processes,
start processes,
and kill processes in a remote system from a server. and how to get configuration information of a remote system.
Return information regarding: logical memory configuration, physical and logical disk and partition configuration including free-space, processor information, network adapter configuration and information, page file configuration and information, OS information.

Write a program that collects the information and sends it to another system. How to get the data: consult your operating system's programming manuals. How to send data through sockets: google for java socket tutorial.
Much of the information you list can be accessed only using non-portable operating system and CPU dependent means. If you write the program in Java you may need to call C, C++, and assembly language code through JNI to gather some of the information. Unless your operating system offers a Java API for that information; most OSs only offer C or C++ APIs.

RFC and PROXY

Hi all,
i have a standard bapi which is at receiver side,and i neeed to update the data .it is asynchronous.can i use a RFC adapter or should i use proxy here?
Regards,
keerthi

Hi,
There are advantages / disadvantages for RFC / Proxies / Idocs. Some of the differences are:
RFC and Proxy:
RFC/BAPI has its own overhead of function call.
Proxies communicate with the XI server by means of native SOAP calls over HTTP .RFC does not, so you have to convert from SOAP to RFC calls and vice versa. So XML conversion is required.
ABAP Proxies uses Webservice and Http Protocols.
If you use ABAP Proxy , you can reduce the overhead calling the function again and again.
Proxy and Idoc:
IDOC : After recieving the strucutred data It processes it using a Function Module associated with it.
Proxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here
Also go through this urls which may help you:
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
RFC VS PROXY
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Re: IDOC and RFC
Re: Proxy Vs IDOC
Regards,
Rajani.

To get a popup on remote system

My application needs cteating a popup window on remote system which in LAN and that popup should be displayed with provided information.
help me,
thanks.

not the net send thing, the graphics device thing...
you can use an instanct messenger app to broadcast,
maybe...
but that or the net send thing still require the same
basic concept I first mentioned: an app running on
the client machines to receive the message.Aye, the "net send" thing uses a client server relationship but the client is installed and enabled by default on windows boxes.
I do not think the graphics device thing will work on windows boxes. It should not work by default on X-based systems if they have any security enabled. If they have no security enabled then you could open any applications display on that X server.
matfud

Monitoring of remote system's Transactional RFC and Queued RFC

Similar Messages

Maybe you are looking for