Sending Idocs/tRFC through saprouter ?

Hello,
I understand that it is technically possible to send Idocs (tRFC) through a saprouter.
But I couln't find any post/blog/articleof people who tried this setup.
Anyone has tried to send Idocs through a saprouter ?
Anything I should consider (besides adjusting the tRFC connexions) ?
Thanks
Raoul

Hi Raoul,
SAPROUTER allows or establishes a cross landscape/network communications. Eg: from your SAP system to SAP AG servers for remote support.
As far as I know, there is not method/procedure to process IDOCs through saprouter.
Thanks,
Siva Kumar

Similar Messages

QRFC/TRFC for sending idocs from SAP system to XI

Hi experts,
The standard program RFFOEDI1 generates payment orders - first PEXR2002 and then EUPEXR idocs. These idocs are to be sent to the bank from SAP through XI. Bank partner profile is maintained. But these idocs because of TRFC are not getting sent in the order in which they are generated by the SAP system. So I changed the bank partner profile settings from TRFC to QRFC and gave the rule name as first 16 of mes type. But the idocs are struck in the SAP system. Is there any standard program to be run to send the idocs out from SAP system or is it automatic.
Please suggest a standard method which is to be followed to send the idocs in the same order in which they are getting generated for the scenairo above.
Regards,
Asha

Hi Asha,
As you said Idocs are stucking,
To send Idocs to XI, you must have maintain some settings in XI to receive Idocs. Once they are done properly .in R3 side standard way to send idocs to XI is Maintaining Change Pointers and shedule the programe to trigger that most of Standard idocs will have standard programs to catch change pointers and send them to external system.
and to maintain the same order of idocs there is a setting called Quality Of Service in XI side ,that option should be set to Exactly Once In Order .
Regards,
Ramesh.

RFC_SYS_EXCEPTION when sending IDOC via tRFC from external program to R/3

Hi all,
using the RFCSDK 6.40 and writing a program in C which sends IDOC' s using tRFC to SAP.
When I send my EDI_DC40 and EDI_DD40 tables to R/3 with:
TCHAR strFktName[] = (_T("IDOC_INBOUND_ASYNCHRONOUS"));
     rfc_rc = ::RfcIndirectCallEx (m_rfc_handle,
                                strFktName,
                                exporting,
                                tables,
                                rfc_tid);
--> rfc_rc gets back an RFC_SYS_EXCEPTION
When I check for
RfcLastErrorEx(&m_error_info);
--> I get back:
Beim Empfangen von Daten für einen Rfc-Call ist ein Fehler aufgetreten
(in english --> an error occured when reciving data from rfc-call)
dump check in R/3 tells:
Fehleranalyse
Beim Ausführen eines Remote Function Calls trat ein Fehler auf.
"RFC_GET4"
Zustand der Verbindung.. " "
    Interner Fehlercode..... "RFC_GET4"
Any idea what goes wrong here?
Already checked very detailed the data I send to R/3 - but it doesent matter what I send - I get the same error every time.
Thanks,
Robert

Reviving an old thread...
I'm getting a similar error making RFC calls from a stand-alone program to an ABAP server using JCo:
RFC_GET4, GET_ID-3c05 LINE 990
Any ideas?
Thanks.
Tim

Sending IDOCS through transaction PFAL

Hi,
We have a requirement to send idocs through transaction PFAL for a set of PERNRs for all infotypes.What is the way to go about this?
Thanks ain Advance!
Regards,
Nejuma Iqbal

hi
you cannot send IDocs thru PFAL transaction.
you can send HR Master Data thru PFAL.
yes you can send the Pernrs as they are Components of Organizational Elements.
Here is the Procedure to send Personal Numbers:
1.Execute the transaction PFAL.
2.Give the object type as P.
3.Give the Pernr values in Object ID field
4.Select the transfer mode as Update
5.In the Receiving Partner give your receiver name
6.Give the message type as HRMD_A in the Message Type field.
7.Dont change the remaining values.Keep it as such.
8.Execute the Program.
Also keep in mind that while sending the HR data you need to follow the certain sequence
unless otherwise your data wont be replicated successfully.
Here is the sequence O,S,P and C.
Means before sending P you should send O and S.
Cheers,
Abdul Hakim
Mark all useful answers..

Problems with sending IDOC in tRFC.

Hi All,
I am sending IDOC to websphere from SAP.
Problem is very weird. All the IDOCs have status 03, but some of them never reach webshpere.
I checked SM58 and there are some tRFC entries for the same.
Following is the error there:
Check SAP Connector log. Error in BO Handler.
I think problem is after the data has been sent to ALE layer.
Can anyone suggest what can be the issue? And how can this be resolved.
Regards
Anuj

Hi Anuj,
As it seems like from the error message there is some problem with the way BO handler is responding to request BOs .
The base class to initialize the connector has been set properly though.
Check the log in SM21 on this and it might give you the detailed information.
Also check if you are passing the large objects, which might require some additional config.
Hope these pointers help in solving the issue.
Cheerio,
Disha

Sending sales order through idoc

hai,
Is it possible to send IDOC of sales order in IDES.
If so can anyone pls let me the solution

Yes, You can send IDOC's in IDES for Testing (Client to Client 800 to 000).
For Configuration related you can search in ABAP General Forum
Regards,
Ramesh

Send IDoc through adapter IDoc_AAE

Hi, guys!
We have SAP PO version 7.4
We need to setup the unloading of the IDoc from BI in PO
I used the following sources:
http://scn.sap.com/docs/DOC-31398
http://help.sap.com/saphelp_nw74/helpdata/en/34/66c81241874285851e2497aa6f0573/content.htm?frameset=/en/c2/91865252c84716b3b8be394851c9c0/frameset.htm
http://scn.sap.com/docs/DOC-34155
http://scn.sap.com/people/william.li/blog/2011/05/04/configuring-pi-730-java-idoc-adapter
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/08/05/connect-multiple-sap-ecc-clients-from-java-idoc-sender-adapter-by-resource-adapter-cloning
http://scn.sap.com/community/pi-and-soa-middleware/blog/2010/10/21/pixi-pi-73-new-java-based-idoc-adapters-configuration-sender-receiver--teaser
but it doesn’t work.
I created Jco provider xi_idoc_default_pid (where PID replaced the SID BI system)
I created the RFC in PO for BI xi_idoc_default_ destination _pid (ping successful)
in inboundRA have in ProgrammID: xi_idoc_default_pid
in destination - xi_idoc_default_ destination _pid
I created Sender channel (manual and default)
I created in BI in sm59 RFC T
I input the program xi_idoc_default_pid , which was created in the first step, in field, and input
gateway and host - my PO
but the test does not pass the RFC.
Could you please tell me, what the problem is?
I configured IDoc_AAE receiver. data arrives in BI, help me to setup up send IDoc from BI in PO
Thanks.

Hi,
We also faced same issue for the RFC created from our ECC to SAP PO (netwaever 7.4 ) system. It is TCP/IP connection.
there are 2 solutions:
1) set gw/acl_mode parameter to 0 in ECC system resolved the issue. Ofcourse you need restart of Source(ECC) system. But it is not recommended in Prod systems
2) Regenerated Reg info and sec info files in Source system(ECC) and created them in target system also and kept them in /usr/sap/SID/SYS/SCS01/data.
The created files are given below for reference.
Reginfo file:
P TP=* HOST=*
P TP=* HOST=*
Secinfo file:
P TP=* USER=* USER-HOST=* HOST=*
P TP=* USER=* USER-HOST=* HOST=*
BR
Ravikiran

Send INVCON02 IODC display 0 IDOC generate through T-code "poit"

Dear Gurus,
when I send inventory data from SAP ERP to SAP ME via MII,I use the sap T-code "poit". In "poit", In "selection parameters:warehouse stock", I fulfill "storage location" , and send, but sap returns "0 IDoc generated".
we tested the basic type "INVCON02" using "we19", it can send IDoc to MII, but could not sucess in POIT.
Anybody can tell me what's the problem, and Is there anybody know other tcode to send INVCON02 to Mii or other system?
It is very appreciate for your help. Thank you advance.

POIT is for the generation of Production (Order) related IDocs. POIM is for the generation of Production (Order) related master data downloads. I think there are two ways of downloading Material Master IDocs, but BD10 is the one I remember.
You will probably be amused, but the fastest way to find INVCON t-code is to google it. Here is the one I use most frequently:
[IDoc T-codes|http://www.sap-img.com/basis/important-idoc-transaction-codes.htm]
But remember you have to set up the two sections in ECC or the IDocs will not be either generated or distributed. Go back to the listener configuration document to see where (which t-codes) the modifications need to be made.
I suspect, but don't know for sure, that the instructions are also in the installation/configuration guide for ME.
Good luck,
Mike
Edited by: Michael Appleby on Feb 17, 2011 3:32 PM

Sending IDocs from R/3 to XI

Hello,
I try to connect a R/3 system to an XI system. I have made the SLD configuration, created RFC destinations, ports and so on. Sending IDoc from XI to R/3 was successful.
No I would like to send IDocs from R/3 to XI. I did the necessary steps at R/3 as described in several blogs etc.:
SM59 rfc dest to XI
WE21 tRFC port
I also read about this step: Create receiver sys as logical system in BD54. What is this for? I am not sure if this step was done in my case, cannot check it at the moment.
I am trying to send an IDoc via transaction WE19 (Idoc Test tool). I think there is no need to create a partner profile?
Now I am wondering: Which values must be set in the control record? I inserted the port pointing towards XI, but I am not sure about the other fields.
I know there are several blogs on this topic but for me there are some details missing. I am also interested in some kind of explanation not just WHAT steps have to be done, but WHY they have to be done.
Thanks in advance, point will be awarded.
CHRIS

> 1. The process is like this: The Logical system is
> defined (as its name suggest ) just for Logical
> definition of the communicting parties. The technical
> details are not provided here.
> 2. Then RFC Destination is maintained where actual
> connection parameters r maintained.
> 3. Port here act as the medium through which the
> transmission is done.
> 4. To identify ur particular message, Partner Profile
> is maintained.
>
> Now in we19 test tool, the port provides the medium
> where the data should be sent. Through this medium,
> the connection to the receiver is checked via RFC
> destination.
Also thanks to you. I understand that the message is sent to a port, which points to a certain RFC destination. But still I don't get it: I thought thats exactly what WE19 is for: To send IDocs for testing purposes to ports, while there is no partner profile needed? I thought there is no partner profile necessary as I can set all fields manually in the control record (receiver port, sender port, message type, receiver type and so on).
Kind regards
CHRIS

Partner profile to send Idoc to PI 7.4 system from ECC

Dear Experts ,
Do we need a partner profile to send Idoc to PI 7.4 system from ECC.
or Just Port on TRFC is enough ..?
if i need to create a Partner profile ...how to define a logical system and how Assign Logical System to Client... when there is no client for JAVA only PI system ..?
thanks
Shakif

Hi Mohamed,
You need to create a tRFC port on sending ECC system. The RFC destination selected in this port os the one created for IDOC transfer.
Also you need a logical system, use client 000, i.e. PI1CLNT000.
At last you have to create a partner profile to define the IDOC type used.
Best Regards
Harald

Idoc to file scenaro ( sending IDOC as it is to NON-SAP)

Hi Experts,
I am doing idoc to file scenario.
I am having SAP R/3 system with 3 clients(100, 200 & 300), IDOC is comming from SAP R/3( any one of the client)
In this is scenario, I am sending IDOC-XML as it is to the NON-SAP system.
I heard that, i can do in 3 ways. those are
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
2. Without message type: create a message interface whose message type would be idoc itself
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
If i go without IR objects,Please tell me whether i need to create Interface objects(i.e. DT,MT & MI) & Mapping objects (MM & IM) or not for the reciever.
MY ASSUPTION:
step1: I will import the IDOC into IR.
step2: Directly i will go to the ID without desiging any object in IR ( is it ok).
Is my assuption or correct or not?, please tell me.
So please tell me the entire scenario how to achieve this.
Please help in this issue.

Hi Laxmi
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
-- Not Possible
2. Without message type: create a message interface whose message type would be idoc itself
-- No need for the Message Interface for IDOC. You will directly import the IDOC and do the Mapping
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
-- This is Possible. you are export the IDOC as XSD File and reimport the same. so there is no difference. If you are going to change the IDOC Structure then this is possible.
Here I am sending some links which are useful for IDOC to File Scenario. Please go thru the links given below..
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
IDoc-XI-File scenario
File -> IDOC ref:
File to IDOC
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope this answers your query.
Award the POINTS if it is useful **
Cheers
Vasu

Get IDoc number for IDoc generated through RBDMIDOC

Hi All,
I have a requirement where in I need to send Vendor master information through CREMAS to PI system. I am using change pointer and batch job to trigger RBDMIDOC and send IDocs.
In case the IDoc fails a mail needs to be triggered to concerned person giving vendor number, Idoc number and date. Can anyone suggest any user exit/BADI where this can be done ??
Note: system is 4.7C.

Hi Chinmay
I didn't knew you were in 4.7. Since you mentioned about the details of the workflow getting triggered, here are the options i can think of.
In case of error it is triggering the standard task 00007989 which you can check in PFTC. This task calls the method ERRORPROCESS from Business Object IDOCAPPL. My suggestion here would be to create a subtype of BO IDOCAPPL in SWO1 transaction and add additional logic in method ERROR_PROCESS to send the mail. The details of the IDOC number and other things are available in the task container of TS00007989. But make sure you do it specific for your message type, as this will be triggered for all message types. And then change the BO and method reference in task 00007989 to point to your new BO method.
Other options would be to delegate the BO IDOCAPPL to a new Z BO, and then modify the method IDOCAPPL. This way you don't have to change the task BO assignment, as it will implicitly use the Z BO method. May be you can get in touch with your Workflow consultant who can help you more on this.
Regards
Ranganath

Error in Sending IDoc to XI

Hi Gurus,
We are not being able to send Idocs from one of our Back-end SAP system. The Idoc status in we05 is successful but it doesn't reach XI. So we checked in SM58 in the Back-end R/3 system and there it shows the error:
No Service For System SAP*** , Client *** in Integration Directory
We tried almost every possible setup
-The System is defined in SLD and has the logical system name.
-The Adapter Specific Identifiers are correct for the corresponding business system in ID
-The RFC destination in R/3 system is defined.
- Read through other similar threads in SDN about the similar problem.
Do anyone have a more definite solution for this particular problem? The other R/3 systems are connected to XI system and all IDocs from those systems are arriving at XI.
Waiting for your valuable advices!
Regards,
Suddha

Hi All,
We had eventually found the solution to this problem we were facing in sending IDoc, though I couldn't manage to update the thread with the solution. I think this would be a very helpful information for those who face similar problems.
Let me describe the scenario first briefly,
We are sending an IDoc (Idoc extension), from SAP system to XI and then send the XML payload as mail attachment to the receiver via receiver mail adapter. Since this is a cross company transaction, hence we have configured the scenario as a B2B in ID, which means we use Parties for both the sender and receiver.
Now in the ID we had done all necessary configurations and used parties and services under Party. For the sender SAP system we assigned a Business System to Sender Partner, configured the Party Alternative Identifiers correctly. The ports were created in IDX1.
On the other hand the SAP system was also configured successfully - including Partner Profile, Distribution List, RFC destinations and ports.
In SLD we created Business System for the SAP system and in ID the Business System under party had the correct logical system name as Adapter Specific Identifiers.
But after all these, the IDoc was not arriving at XI, though in R/3 the status of the IDoc was 03 in we02. When we checked in sm58 in R/3, it showed us the error message that "No Service For System SAP*** , Client *** in Integration Directory".
The cause to this problem was:
We created (assigned from SLD) Business System only under Party (Sender), as this was a B2B scenario, and didn't create (assign) a Business System without Party, as we didn't need one at all in the scenario configuration. And this the reason behind this error. When an Idoc arrives at XI, before the Inbound IDoc adapter converts the IDoc to IDoc XML using IDoc metadata............it checks in Configuarion to see if any Service without Party (Busniess System) is defined for the Sender SAP System and Client (The SNDPOR and MANDT field values from IDoc Control header are taken as the SAP SID and Client). If it finds one it accepts the IDoc and starts the Normalization (Sender Party, Service......in the message header) and IDoc to XML conversion. If it cannot find an Service without Party in ID for sender system, it rejects the Idoc with the error message that we saw in sm58 in backend R/3 system.
In this step the Service under Party doesn't help, because at this point the Inbound IDoc adapter can not deterimine the sender party.
Hence for sending an IDoc from an SAP system to XI, we need to have an Service Without Party in ID, whether or not we require it in our actual Scenario Configuration, which is ofcourse not a case for the Reverse Scenario, ie Sending an IDoc into SAP system from XI.
This is the similar with BC adapter as well. I was already aware about this behaviour of BC adapter from my past experience and this actually helped to troubleshoot this IDoc adapter problem.
This was ofcourse a useful and new learning for me and hope would be helpful to others as well. Let me know if anyone has any doubts on this.
Regards,
Suddha
Edited by: Suddhasatta Guha on Aug 28, 2008 1:03 PM

Assignment IDX1 port to sender idoc adapter ...

Hi gurus,
I have a big problem and I don't have any idea how to solve it. Please, help me.
I have a non-SAP system, regular SAP ERP and SAP XI and I need to transfer IDocs between them.
There is no problem to send IDoc from ERP to XI and forward it to non-SAP system. Unfortunatelly communication in opposite direction doesn't work. XI is not able to receive IDoc sent from non-SAP system because appropriate metadata can not be found in IDX2 cache.
In configuration of communication channel for sending IDocs to non-SAP (receiver idoc adapter) I selected IDX1 port that is directed to the ERP and it's worknig fine. I can send IDoc from XI to non-SAP.
But in configuration of communication channel for receiving IDocs from non-SAP (sender idoc adapter) is not possibility to determine any port. Does exist a way how to force sender idoc adapter to use some specific IDX1 port?
Thank you in advance for every reply!
Regards,
Zbynek

The IDocs are sent from non-SAP system by means of tRFC. Connection type of the RFC destination is type T (TCP/IP) and activation type is Registered Server Program.
If we sent the IDoc directly into SAP ERP (where the IDoc Type is known) everything is fine
Edited by: Zbynek Kabrt on May 19, 2009 8:59 PM

RE:SENDER IDOC ADAPTER

Hi ,
why don't we crate a communication channel for idoc on sender side,but when we go for receiver side we create communication channel .
please let me know how an idoc converted in to idoc-xml while transfer to integartion engine from sender side.( with out idoc adapter on sender side)

hi prateek,
The communication at sender also passes through the Idoc adapter.
with our configuring idoc adapter on sender side, how can an idoc passes through idoc adapter, is this because idoc adapter resides in abap stack.
can u briefly describe how can an idoc convert in to idoc-xml before comming to integration engine.
if idoc adapter is on abap stack then
in case of file to idoc
why we go for idoc adapter . (con't the process same as reciver side) .
please give brief explain to each of my questions.

Sending Idocs/tRFC through saprouter ?

Similar Messages

Maybe you are looking for