IDOC communication thorugh tRFC connection

Hello All,
We all know we can communicate b/w two SAP systems by posting IDOCs using tRFC connection.
I am sending one material master IDOC from 800 client to 811 client using BD10. It is getting posted successfully.
Now, while transferring this data from 800 client, there must be some file which will be getting generated which the destination system must be using for incoming IDOC processing.
Here I would like to know at which location exactly this IDOC file is getting generated?
Regards
Munish Garg

Hello Uwe,
Then how tRFC post the IDOC.....Data must be sent from one system to other using some media.....ideally it should be file....
How destination system knows that some IDOC is coming to the system and how to post it?
I heard that at OS level startrfc.exe is getting executed......with following notation:
startrfc -3 -d <sys_id> -u <sap_rfc_user> -p <password> -c <mandt> -l <login_language, E for English> -h <sap_host_name> -s <system_number> -F EDI_DATA_INCOMING -E PORT=<edi_port> -E PATHNAME=<file_path>
So here we must be having some PATHNAME and PORT......
Regards
Munish Garg
Edited by: MunishGarg on Feb 4, 2011 3:36 PM

Similar Messages

One TRFC connection how many idoc we can send?

Hi Experts,
singel TRFC connection,how many Idoc can we send?appreciate any can tell me size also?
Thanks
Narendra

Hi Narendra,
As far as i know you can configure it. Check this link Transaction WE14 Max. Number of IDOCs in program RSEOUT00 - ABAP Connectivity - SCN Wiki
Regards.

Doubt on IDOC communication

Hi Experts,
                  I have a doubt on IDOC to IDOC communication:
Plz clarify it
                    1. what is the need of passing same IDOC from one system to other system    through XI while communicating between two systems,it can be done by using ABAP also ?
                     2.what is the advantage of passing like this through XI compared to ABAP?
               Plz clarify good answers will be rewarded .
                                                                                Regards,
                                                                                Vinod.

The need for an XI to transfer IDOC from one system to another sytem : the answer for this comes from the basic of using XI as a middle ware.
1. When you connect IDOC directly to another system without using XI....you are going for P2P connections then this leds to problem in monitoring if the data breaks, you have to login to both systems to check......
2. we have a central monitoring tool for check this iterface..
3. You can build a message orchestration using the BPM if required for this IDOC...
4. You can have full control in the IDOC processing...i mean do you want to send ot not and so on.
Beofre XI or typical connection between 2 SAP Systems were using IDOC directly but they are P2P connectinons,,,no control, no monitoring....NO orcheatreation...etc.....

Monitoring receiver idoc communication channel

Hi All
I have an idoc to idoc scenario.
I am unable to see my receiving idoc communication channel in communication channel monitoring of RWB. It is not available in the dropdown list.
I want to have a look at the audit log to see if the idoc is delivered to the receiving system.
How can i monitor receiver idoc communication channel?
How can i ensure that the idoc is delivered to the receiving system?
In sxmb_moni, status is checkered flag.
Many Thanks
Chandra Sekhar

Hi,
IDOC is on ABAP stack hence u can not monitor IDOC.
For testing purpose
1) GO to SXMB_MONI check the status of message.
2) Go to R3 and enter Tcode WE02 and check the IDOC which is send from XI. enter the idoc name and see the status of IDOC it should be in green status if it is posted successful or else see the status record for checking the error message.
chirag

Doubt on IDOC TO IDOC communication

Hi Experts,
I have a doubt on IDOC to IDOC communication:
Plz clarify it
1. what is the need of passing same IDOC from one system to other system through XI while communicating between two systems,it can be done by using ABAP also ?
2.what is the advantage of passing like this through XI compared to ABAP?
                       Plz clarify good answers will be rewarded .
                                                                                Regards,
                                                                                Vinod.

Hi,
See when you are dealing with Only IDOC to IDOC Communication means there is no need of XI here.
You can go with ALE also here.
Situations to go to XI.
1) when you have the Different field mappings
2) When you are having the multiple receivers
3) when you are dealing with Bundling & Transformations
Reward Ponts If Helpful
Regards
Giri

BD87 hide "idoc entries in tRFC queue" by assigning to status or other meth

Hi,
I am working on the inbound side of an idoc interface for message type MATMAS. My problem is that when I enter in BD87 there are more than 400 hundred entries in "idoc entries in tRFC queue". Now, whatever filter I put on the first screen this line appears. Even, if I enter with a specific idoc number. These entries are obviously outbound errors and are completely irrelevant to the interface I am working on but will make the reprocessing screen unnecessarily complicated for the users. So, basically I want to allow the end user to filter out these messages.
I noticed that the errors "idoc entries in tRFC queue" aren't associated to a status and I was wondering if it is possible to give them a status value and so make them sensitive to a status filter. But if this isn't possible any solution to hide these error messages from the end user would be equally valid.
I know someone will probably suggest that the best solution would be to remove all old entries from tRFC queue in SM58 and that there shouldn't be so many idoc in entries in the tRFC queue. The problem is that it is not my role to monitor tRFC in production and if it has not been regularly monitored up to now then it probably won't be in the future.
Many thanks in advance,
Jamie.

Hi Jamie,
To the best of my knowledge the shown outbound RFC entries in BD87 are a feature that cannot be suppressed. I.e. in the coding of BD87 one can see logic where it automatically checks for outbound RFC errors and adds those to the output.
In general IDoc status 03 should be associated with the outbound RFC errors. Yet, when one sees those in BD87, the IDoc status field is empty. Along your train of thought I had also previously tried to suppress those displayed IDocs by adding a filter for suppressing status 03 or blank status, but nothing helps. And as you correctly point out, even when using BD87 on a single IDoc (e.g. specified via IDoc number), the transaction will still display the outbound RFC errors.
So unless somebody else has some good idea or insight, I'm afraid you're stuck with that behavior.
Cheers, harald

Idoc Communication Configurations and Proxy Runtime Configurations for PI

We have a fresh PI 7.1 system, fresh ECC6 system, and an existing 4.6C system.
is there any blog/doc with step-by-step instructioins/screenshots for following tasks:
1. Configuring Abap proxy runtime between ECC6 and PI 7.1 Systems, for using sproxy from ECC6.
2. Configuring for IDOC communication between ECC6 and PI 7.1
3. Configuring for IDOC communication between 4.6C system and PI 7.1
It involves creating of sm59 rfc destination creations, usage of idoc related transactions on PI system and the other system.. I searched on sdn/forum, but it seems to be addressing specific issues faced.
Pls suggest any step-by-step instructions docs/blogs available.
thanks in advance.
Madhu.

Madhu,
Refer the links below:
1. /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
2& 3 :
https://wiki.sdn.sap.com/wiki/display/XI/SAPR3%28Idocs%29ToXI--Steps+Summarized
http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c&overridelayout=true
http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
Also, I think u hv just started learning XI ..so following link might help:
http://wiki.sdn.sap.com/wiki/display/NWTech/QAforPI-Onestopforall%28Part-1%29

RFC to send an idoc PEXR2002 using HTTP connection to an external server

Hi,
Iam working on RFC to send an idoc PEXR2002 using HTTP connection to an external server. first time iam working on this particular scenario on http connections. please clarify on this and explai me in detail about this.
Points will be rewarded **
Thanks & Regards,
Ravi

HI Jagruthi,
Have you loaded the metadata into the XI system by using IDX2?
If it is done then try to delete once and do once again.
And also delete the IDoc from IR and reimport the IDoc and activate it once again.
Regards
Goli Sridhar

Idoc to Idoc communication thru XI

Hi,
Any one can explain the step by step configuration details about IDOC to IDOC communication through XI not an ALE concept.
Thanks
Rao

There are some good IDOC How To guides here:
Exchange Infrastructure How-to Guides for SAP NetWeaver 2004 [original link is broken]
Nice step by step instructions.
I am configuring several IDOC to IDOC scenarios.
They are relatively staright foward.

IDOC COmmunication Channel

Hi
i have created a receiver idoc communication channel, and when i want to check whetehr its working fine or not in Runtime Work Bench , when giving the receiver communication channel name it is saying " Communication Channel" does not exist??
plz help me

Hi,
As you said you have created the receiver idoc communication channel and if you are monitoring the idocs in IDX5 for the same then the idoc will be outbound and not inbound....
if you are confused with directions then check with out giving the directions in filter criteria....
Also are you sure that the idocs have generated successfully in PI for sending..check the interface message in MONI for the same...
Hope this clears you
Regards
Rajesh

RTMFPTurnProxy for peer to peer communication in proxy connection

Which server ip i have to mention in mms.cfg against Rtmfpturnproxy either the fms server ip or the deployment server for peer to peer communication
For peer to peer communication, it is said to add a variable RTMFPTURNProxy in mms.cfg and assign the value the ip address of the turn server. The mms.cfg file is not in the specified location in my windows 7 system. It is mentioned that Flash Player only supports IETF BEHAVE TURN draft 8, not the current TURN RFC. So i create the mms.cfg file with the UTF-8 format in textpad and add the function RTMFPTURNProxy and assign the value of the AMS server ip. Still I could not connect to the server and received NetConnection failed message in proxy internet connection.
My doubt is which ip address the RTMFPTURNProxy should refer. The AMS server or the application deployed server or something the assigned public address. Should I need to do anything regarding the mms.cfg file. What are the conditions I need to check for peer to peer communications in proxy connection? My heartfelt gratitude for any helping mind. Thanks in advance.

The provider system in soamanager must have the same name as in table BBP_BACKEND_DEST field SLD_SYS_NAME (System Landscape Directory Name).

What is memory idoc , communication idoc

plz tell me about
         memory idoc , communication idoc.

hi kalyan,
Master IDOC : This idoc collects all the required data into
single IDOC and this is temporarily stored in memory.
Communication IDOC: there can be n number of communication
IDOCs generated. This comes into picture after the Master
IDOC is validated from the distribution model . And this
IDOC is stored in database table . you can see this IDOC
from we02 tcode..comm idoc is the physical idoc which is reciever specific
IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
   Depending upon the triggering mechanism i.e change pointer,message control
   etc the programming technique changes and the type of process.
2)Existing IDOC was extended
   User Exits are used to populate data in new segments added and to read them
   back.
3)To enhance an exsiting process.
   User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP      IDOC type
MESTYP    Message Type
RCVPRN    Recieving Partner (Destination)
RCVPRT    Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
                is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
       INT_EDIDD-SEGNAM = 'ZSEGMENT'
       W_SEGDATA-field1 = value    "taken from some table
       W_SEGDATA-field2 = value    "taken from some table
       INT_EDIDD-SEGDATA = W_SEGDATA
       APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
      There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
      In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in
the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
thanks
abdul
reward me if usefull

How to correct socket communications error 10054: connection reset by peer

We are running Lookout 5.1 (build 8) reading data through Modbus Ethernet Drivers and we are constantly getting "socket communications error 10054: connection reset by peer" alarms on the server. When I connect to the server file with a client file the client is experiencing communications problems including locking up when editing, trends not showing up, stops updating completely (can only be corrected by restarting server file), and losing symbolic link.
Does anyone know how to stop this alarm from happening and if this could be the cause of my faulty server-client connection or is this strictly a problem between the server and the ethernet radios in the field?
Any response would be appreciated.
Thanks!
Jason
Jason Phillips

DST1,
All I had to do was increase the receive timeout in each driver's properties until the socket errors disappeared. I have them all set to 30000 msec. Communications have been great on this wireless ethernet system ever since.
Sorry for not answering sooner - needed to make time to go back and look at the file and then TS Lee came our way!
Jason Phillips

Error in TRFC Connection

Hi Experts ,
Pls help us in solving this error Some of our process chain are throwing error like Trfc connection not available
Points will be assigned for right answer

Hi ,
See ur trfc connection not available may be because due to the work processors in R/3 would have not been available for the whole period of ur loading process .
Pls wait for the parallel processes to end and then load ur data again after deleting the bad req from the manage tab
if this error persists then go for a Ticket
Assign some good points if answer helpfull
Regards ,
Subash Balakrishnan

IDOC to SOAP Scenario : Connection Refused

Hi Everybody,
I am working on Idoc to SOAP Asynchronous scenario.
I have an issue with the connection from SOAP to the websystem at the receiver.
Around 60% of the messages are processed successfully and the rest of the messages throws up errors at the receiver Adapter.
Below is the log from Communication channel for the unsuccessful messages.
Message processing started
request entering
SOAP: call failed: java.io.EOFException: Connection closed by remote host.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connection closed by remote host.: java.io.EOFException: Connection closed by remote host.
Is there any setting we need to make for the SOAP adapter to reduce these failures?
Or is it a problem with the receiver websystem?
Can somebody help me out on this?
Thanks & Regards,
Zabiulla

Hi,
For some reason the client (from the server's point of view - it might be some other device between the actual client and the server) is closing connection during the SSL handshake. As we can't get more info from the standard J2EE Dispatcher log files, we need more detailed info.
Please check
1. Execute network router trace utility (tracert for Windows systems or traceroute for UNIX flavours) to the J2EE Engine's host. It will show the active and non stealth routers between the client and the server:
c:\> tracert [J2EE_host] (windows)
$ traceroute [J2EE_host] (UNIX)
2. Activated low level SSL tracing
regards
Aashish Sinha

IDOC communication thorugh tRFC connection

Similar Messages

Maybe you are looking for