Send idocs or RFC from R/3 to biztalk

hi All,
We have an requirement of transferring master data from R/3 to biztalk whenever any cahnge to the master data is made.
We are contemplating using IDocs or RFC to do this transfer. If it were a R/3 to R/3 transfer then I have come across many docs where it is stated that idocs is by far a better option than RFC but I am just wondering if same applies when we do it to biztalk.
The reason I had the above doubt was because I dont know if we can use ALE as means of transporting the idocs ( i vaguely remember creating partner profiles. since biztalk is not a SAP system how can I create a partner profile for it ).
I was wondering if someone has come across a similar situation and probably point me in the right direction.
thanks,
Gautam

Hi Gautam,
Yes, IDoc can be trigerred by configuring change pointer from SAP R/3 on change in master data. There are many ways to integrate SAP with Biztalk. Have a look at these links for more details -
1. http://www.microsoft.com/isv/sap/technology/interop/biztalk.aspx
2. http://download.microsoft.com/download/5/7/f/57f1490e-8a8d-497b-bbae-ec2a44b3799f/BizTalkSAPXIInterop.pdf
3. http://social.msdn.microsoft.com/Search/en-US?query=idoc%20from%20sap&ac=8
Regards,
Sunil Chandra

Similar Messages

Problems with sending IDOC via RFC from Unicode to NonUnic

Hello
I have following problem, sending an IDOC via RFC from Unicode to Non Unicode System. IDoc is not sent with error: codepage of receiver system cant determined. receiver destination was: Message no. B1999
I have tried different options in sm59, but it didnt help.
Any ideas? The recipient system is rather old, version 4.0

hey,
I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

Sending IDocs via RFC Adapter

Hello!
In an itegration scenario, we need to send (non XML) IDocs via RFC to a remote R/3 system (4.6C). As we don't want to get these IDocs persisted on the target system, it's intended to address the remote functions directly.
Now the problem:
- RFC Adapter only works with XML IDocs (so we cannot transfrom back to native IDoc)
- IDoc-Adapter sends native IDocs, but only to IDOC_INBOUND_ASYNCHRONOUS on target system (and the Idocs will be persisted)
In a next step, we also tried to implement a workaround with a local ABAP proxy on the XI system. But it seems, that it's not allowed to call a abap proxy locally on the integration engine.
Has anybody any idea to solve this problem? Maybe I'm thinking too complicated Help is highly appreciated!
Cheers,
Matthias

Hi,
what kind of document you want to post?
most (many) IDOCs use BAPIs so you can
just call the BAPI (RFC) from XI
>>>But it seems, that it's not allowed to call a abap proxy locally on the integration engine.
you can call it on another client on the XI
(which is set as application system in SXMB_ADM)
Regards,
michal

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

How to trigger automatically an IDOC and RFC from SAP R/3 system?

Hi ,
lets say if we are implementing IDOC to FILE &RFC to FILE scenario ,how can we trigger on timely basis(schedules)
1)standard IDOCs and BAPIs?
2)customized Idocs and Customized Bapis?
3)Master Idocs and transactiona Idocs?I think we need to use change pointers for master Idocs and donno about Transactional Idocs.
please explain ,
thank you very much for your help.
regards,
Babu

sorryfor the late reply, I was busy with my work.thank you for your posts.
so all of you say just run the RSEOUT00 no matter what interface we use in XI like Master ,transactional Idocs,standard or customized BAPIs?
And I think we use RSNASTED if we have on recieving side right?
<b>then when we would use a report of format below to trigger an RFC,is this format for Asunc RFC ?</b>
REPORT Z_SEND_DATA_TO_XI.
parameters: dest like rfcdes-rfcdest default '(RFC Destination you defined in SM59)'.
<<your other variable declaration and ABAP Code here>>
call function 'ZXI_SEND_DATA'
in background task
destination dest
exporting
Name = John
City = Smith. (The values to pass to XI)
commit work.
<<Any Write statements or sy-subrc statements here>>
6) Save and Activate your ABAP program.
6) After all these steps, execute your ABAP Program to send the data to file via XI.

To send IDOC to vendor from SAP for purchasing order

Hi Gurus,
I want to setpu an EDI for send the outbound & inbound idocs to vendor for purchasing order from SAP and below are the message type I am using:
Outbound message type :
ORDERS
Inbound message type :
ORDRSP
INVOIC
I know how to set up the link, making the partner profiles attaching the process code, assigning the ports but I want to know the below customize set up:
1) Which transaction I need to used for customize this sceranio
2) Could you provide me any documentation which specifies the steps for configuration
And other details which I am suppose to know.
Please reply me as soon as possible as I am urgently in need of this.
Regards,
Sagar

Hi Sagar
For the Confirmation you need to do the customizing for confirmation control, like what would you like to do after the confirmation. Confirmation is an inbound process.
For Invoice you need to complete the customizing under LIV in SPRO- for Invoices received via EDI.
Please go throught the help link for further details.
http://help.sap.com/saphelp_47x200/helpdata/en/a8/b99f58452b11d189430000e829fbbd/frameset.htm
Reward points if useful
Thanks & regards
Kishore

Sending Idocs from SAP-R/3 to XI, bundle and map them to one XML-file

Hi All,
We need to send IDoc's (DEBMAS06) from R/3 to XI and bundle and map them to a single xml-file. Please help us with your suggestions on how to proceed using a simple solution (probably need of BPM).
Regards,
Theo

Hi Theo,
there is an example in SAP Library: <a href="http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/frameset.htm">Collecting and Bundling Messages - One Interface</a>. Plz post us your detailed quetions.
Regards,
Udo

Sending IDoc from R/3 to XI -ongoing

Hi,
With reference to my previous errors while sending IDoc to XI from R/3 system. I have resolved errors with help of Seshagiri and Kummari advise and help. But now I am getting new kind of error, while sending IDoc from R/3 its getting passed from R/3, but while checking it in XI throug SXMB_MONI I am getting below error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_POCreateIdoc_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_POCreateIdoc_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any one advise me on this?
Thanks & Regards
Manish

Hi,
There were so many Mapping Objects under different Namespaces and under that different Message Mapping trees.
Under one tree I have tested the XML message and found the below error:
Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
Kindly check if this is the correct error I am getting related to SXMB_MONI error message.
Regards,
Manish

Sending IDoc from TIBCO to SAP

Hi,
request is to send IDoc type PURCONTRACT_CREATE01 from TIBCO to SAP.
After sending the data from Tibco there is nothing received in SAP although TIBCO adapter says successfully created.
But no entry in BD87 (IDoc monitor), no entry in SM48 (tRFC queue) on SAP side.
How can I recognize what went wrong - on TIBCO or SAP side?
Shouldn't there be an entry in IDoc monitor at least although content of sender or receiver data or IDoc would be wrong that was sent by TIBCO?
Has the TIBCO adapter to do a kind of commit ?
Help is highly appreciated.
thx.
Achim

Hi,
Configure the appropriate message type for the partner in the outbound parameter of the partner profile (WE20) . Afterwards reprocess your failed idoc using the program RBDAGAIN
Try Posting the Idoc with the help of WE19 instead of using your report
Status 29 indicates that the Partner Profile is not configured correctly.
As you know the target logical system is nothing but the partner, select that and click on Outbound Parameters and add the message type.
Status 30 indicates that the Idoc has been generated successfully.
Status 03 indicates that the Idoc has been reached Middleware.
Try running the standard program RSEOUT00.
All the Idocs in 30 statuses will change to 03.
To get all the IDOC's in status '03'
after MASTER_IDOC_DISTRIBUTE
Call FM "EDI_DOCUMENT_DEQUEUE_LATER"
Regards,
Shamma

IDOC Message type from XI

Hi,
I'm sending idoc type ORDERS05 from XI. Previously, I had set up message type ORDERS for this IDOC in the partner profile. But then I changed message type to ORDRSP, and process code ORDR for inbound idocs. I've also set message type ORDRSP for IDOC type ORDERS05 in WE82 message type - idoc type linking.
But for some reason, the IDoc is looking for message type ORDERS and not taking message type ORDERSP, and it is erroring in SAP, when I view the status of the IDoc it says that EDI Profile ORDERS Message type was not found.
So my question is - is this message type for an idoc type to be used passed somewhere from XI, do I have to make a change in XI side, or SAP side.

Hi,
I did all these changes, in the IDOC mapping in XI and also selected the option to select control record from payload in the idoc adapter. The messge in SXMB_MONI, I can see that EDI_DC40 has mestyp ORDRSP, but when I see SAP we02 IDOC transaction, it says that message type is ORDERS. Don't know why this is still happening? Any other option needs to be checked guys?
Regards,
Vijay
Message was edited by: vijay srikanth

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

Message SR 053 when i send idoc from SAp R/3 4.6C to PI 7

Hi,
I try to send idoc from SAP r/3 4.6C to PI 7. I had made ALE configuration in my sender system ( SAP 4.6C) but idocs are not sent to PI. In SM58 i have message "Name or password is incorrect (repeat logon)". Yet i'm sure that user and password are correct because if i test RFC destination using SM59 , test is OK.
Is somebody can help me ?

Hi,
In R/3 :
my RFC destination is type 3 and point to XI. The port in the partner profile point to this RFC destination. ( all seems good !).
In Xi : i created a port and i load manually idoc in idx2 to be sure that RFC destination was OK. Nothing in IDX5.
When i send idoc MATMAS using BD10 from R3 to Xi i have something very strange: first the message B1 038 "1 master IDocs set up for message type MATMAS" and just after
the XI logon screen appears !! Then message "1 communication IDoc(s) generated for message type MATMAS" and this idoc stay in SM58 with message "Name or password is incorrect (repeat logon)".
Somebody can give me requires caracteristics for XI user used in R/3 RFC destination ?

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

RFC error "No authorization to send IDOCs with message type ..."

Hi all,
I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
Any suggestions?
Regards,
Liesel

Hi Liesel,
The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
Please check if the user id/Password that you have given has all the authorization.
Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
Regards,
Abhy Thomas

Sending IDOC from R/3 to MII error

Hi,
We are trying to send IDOC from R/3 4.7 to MII 12.1 (SP8 patch 9 on NW CE 7.11).
We followed the guide below:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3861e693-0e01-0010-e791-9b44d2693e6c
Connection of message listener to R/3 works fine.
RFC connection test from R/3 to message listener was successful.
But when we try to do model distribution we get this error " - Communication error occured. Server repository could not create function template for 'MODEL_VIEW_REPLICATE'.
Maybe someone encountered this error and can help to resolve it.
Thanks in advance.

Hi Michael,
What do you mean by "manually registered the ProgID"? The message listener configuration property is as below:
ProgramID: MII_IDOC_CONNECT_5
MaxReaderThreadCount: 1
SAPClient: 800
UserName: GAOMX
Password: xxxxxxxx
Language: EN
ServerName: blade01a.memc.com
PortNumber: 00
BindingKey: XMIIIDOC
And also, following is error message found from LOG VIEWER of the MII server:
here is one
Message: not supported FunctionModule MODEL_VIEW_REPLICATE for IDocActivationSpec
Date: 2011-07-21
Time: 15:30:18:060
Category: /System/Server/Connector/Rfc
Location: com.sap.mw.jco.jra
Application: sap.com/sapjra~xMIIIDOC05
Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
Data Source: j2ee/cluster/server0/log/system/server_00.log
and another one
Message: Server repository could not create function template for 'MODEL_VIEW_REPLICATE' caused by: java.lang.RuntimeException: not supported FunctionModule MODEL_VIEW_REPLICATE used with IDocActivationSpec registered for MII_IDOC_CONNECT_5 on system blade04a_MIT_00
Date: 2011-07-21
Time: 15:30:18:061
Category: /System/Server/Connector/Rfc
Location: com.sap.conn.jco
Application: sap.com/sapjra~xMIIIDOC05
Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
Data Source: j2ee/cluster/server0/log/system/server_00.log
Thanks,
Mike

Send idocs or RFC from R/3 to biztalk

Similar Messages

Maybe you are looking for