Regarding rfc idocs

by using ale rfe idoc technology i tried to transfer the vendor master record ,after finishing all the steps iam getting the message like 'successfully transferred ' .when i checked in the receiver s/m database s/m the record was not found .plz help me in this session .how to handle this error .
thanks ...............

Similar Messages

Guarantee EOIO Processing in File-RFC-RFC-IDoc Scenario

Looking for some opinions on the following set up we've got. We're trying to build QoS EOIO on a scenario that goes File Sender->RFC and then RFC->IDoc. My question is basically have we effectively ensured that our scenario will be EOIO from file to IDoc. We want the first record in the file to always be the first created IDoc, the 10th record in the file to always be the 10th IDoc created etc..... We also want to make sure that if we encounter an error at any point that all subsequent processing stops and waits until the problem is resolved. We've successfully completed some steps but my biggest concern is in the area between where XI sends the data to SAP1 via RFC and the resulting return RFC from SAP1. I'm thinking we may not be quite there yet and would be interested to hear what others thought.
We're on SP15. The scenario goes like this (no BPM):
1) We have a legacy system LEG1 that we pick files up from using the Sender File adapter. This step will take the file from LEG1 into XI and map it to an SAP remote function on SAP system SAP1. We set QoS on the file adapter to EOIO. Our interface determination for the File to RFC component is set to QoS of "Maintain Order at Runtime".
2) XI makes the RFC call to SAP1 (6.20) using an RFC receiver adapter. The called function then processes the data and returns the data back to XI using another remote function call. This function call is of type tRFC where we call the function "in background task" and issue a commit after the RFC call.
3) We receive the data into XI from SAP1 using the RFC sender adapter. XI maps it to our IDoc layout and sends it onto another SAP system called SAP2. Again here our interface determination QoS is set to "Maintain Order at Runtime".
4) XI passes the IDoc onto SAP2 (7.00) using a receiver IDoc adapter. The paramter Queue Processing is turned on.

About EOIO in qRFCs, actually this is quite a polemic topic.
There is something you could do, allright, but it is controversial whether you could properly call it "EOIO" or not.
Refer to this thread for further discussion: use EOIO on Sender RFC and outbound ABAP proxy calls
Supposing you call the other RFC before you commit work in the receiver RFC, and supposing you could have EOIO at 2nd RFC (sender RFC), all these assumptions could mean that you would guarantee EOIO end-to-end. But they are just assumptions.
You have to try it and stress test the scenario to guarantee the validity of this design.
One other approach would be a BPM with all steps in one single transaction (check BPM transaction handling). The steps would be:
File -> sync RFC -> Idoc
where the response of RFC should be the necessary information for triggering the IDoc, and all send steps would be in EOIO mode (set queue name in Send steps). Also, file sender adapter QoS should be set to EOIO.
But I'm also not sure that this will guarantee EOIO end-to-end (possibly not...)
Good luck.
Regards,
Henrique.

Some PI questions regarding RFC and receiver determination

If we import the design objects in one customer system from another customer system , and in the original system there is an imported RFC ,
This RFC has been created in the new SAP customer system.
My question is do we have to import the RFC again , as it is already in the imported design objecs.
My second question is , di we need to create a receiver determination for the answe in a synchronous send step of the BPM ,
Thanks

My question is do we have to import the RFC again , as it is already in the imported design objecs
Yes....the RFC/ IDOC should be imported from the system to/ from which you will send/ receive the data.
If the RFC was in system1 earlier and now in system2.....then you have to delete the RFC imported from system1 (if it is not used) and then import it from system2
My second question is , di we need to create a receiver determination for the answe in a synchronous send step of the
BPM ,
Irrespective of sync/ async send step.....you should create Receiver Determination....which will have BPM as sender and the TO_SYSTEM as receiver.....not separately for response....just once
Regards,
Abhishek.

When to use RFC ,Idoc and proxies

When to use the RFC,IDoc and proxies.
What is the difference in using RFC,Idoc and proxies.
I want the therotical explanation of it.
I gone through some of the links.
i want the explanation which is there in simple words
and which is easily understand by the bigginers
those dont know more about adapters.

hi,
You use all these three things when the sender or receiver for XI is R/3 system.
You use proxy in sap 6.0 version or higher.
you use that when you dont want to use an adapter.
or very high volume of data has to be transfered.
you go for rfc which can be synchronous as well as asynchronous
http://help.sap.com/saphelp_nw04/helpdata/en/22/042a3e488911d189490000e829fbbd/frameset.htm
refer for idoc:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
regards,
ujjwal kumar

Reg: RFC / IDOC required for doing CIDX Scenario

Hi! Gurus,
This is Amar Srinivas Eli. I have task here to work and implement CIDX Scenario succesfully. There are some business cases as per the CIDX standards from that I was selected one Business case i,,e, FORECASTING.
But inorder to implement that scenario I need some RFC's or IDOC lists from SAP side whether it may be a source or target side..what ever it may be...and other side will be CIDX format.
Here I need your help in the below mentioned tasks. Kindly help me out in a detailed step by step guide and do the needful to me.
1. How to get RFC / IDOC name from R3 System and I know that I can get RFC from SE37 and IDOCs
from WE05 but I need whether all the required fileds are statisfying in the RFC's or not.
2. My first preference is only for STANDARD SAP RFCs or IDOCs.
3. Please let me know how to see the inner fields present in those RFC's
4. ALso please provide any configuration guide which contains screen shots if you already worked
earlier on CIDX Scenario I mean step by step and also for testing
5... tell me if there is any other tool other than STK kit for testing CIDX messages.
6. Is there any Freeware STK tool kit is there or not...
Also share your experience and errors that you have faces while doing this CIDX Scenario.
Regards:
Amar Srinivas Eli

Hi! All,
Thanks for your fast response..
Hi! Raja,
I gone through your points. Here I have few doubts on those please clarify that.
1. Coming to testing i didt used any testing tool , but you can comre your output using XML Spy or Stylus studio.*
*CIDx Documents,you wil find in SDN please search in SDN.
Means Without using STK Tool or else some other tool How can I get the CIDX response for my request in the Testing environment. See I am not doing this in real time I am trying to findout the solution for Business cases so I need one testing environment tool right ? Is that ALTOVA XML spy will give no right ?
Note: You told that you have done that business case IDOC--CIDX Order change / req Will you please share the information documentation I mean step by step procedure for end to end doc...based on your scenario ?
2. I know those R3 and PI settings I mean configurations means ports and RFC destinations and all those..but only thing I dono is "How you got that IDOC I mean on what basis and how did u search the IDOC?"
3. See Here I am working on topic FORECASTING it includes so many sub tasks like Deman PLan req and response, supply plan req and response and replenishment order and etc....so based on that how can I get those related RFC's or IDOC's in order to communicate from R3 Side
If Suppose I have seen one RFC/IDOC and for example out of 10 fields few are there in one IDOC and another few are there in another IDOC then in that case I need to go for Multimapping IDOCs I mean 2 Senders to one Receiver if yes Is it possible?
My first requirement is based on the above mentioned business cases how can I get the corresponding RFC's or IDOCs ?
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 5, 2009 12:19 PM

Import RFC/IDOC error

Hi all,
I am following "How to...push data in to BW from XI."
In the 5th step in the document it is given
Choose "Import RFC/IDOC" in the context menu of "Imported Objects" and enter your user data to logon to the BW system.
Select the function module /BIO/Q16ASENDXMLDATATOBW_RFC
Press "continue"
Press "Start"
But when I do this I am getting a java nullpointer exception error com.sap.aii.ibrep.sbeans.upload.remoteuploadexception:jsva.lang.nullpointerexception
I am using jre1.4.2_10 and java web start version 1.4.2
Please help me in resolving this issue.
Regards,
Aanand

Hi Anand,
Can you pls make sure that no other users have this same RFC imported into your XI integration builder and is waiting to get their change list activated. In that case also we get the error in importing...
check these links also.
Error importing RFC / idoc despite following note 769356
Cheers
JK

RFC, IDOC and secure connection

Hello
Does RFC/IDOC support secure connection like HTTPS?
How the data can be encrypted?

Hi,
As Moorthy Quoted RFC will help you,
This will be help you for encrypying the data.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b2cce390-0201-0010-5a9f-cca08c75b6ea
/people/kathirvel.balakrishnan2/blog/2006/06/13/sap-php-together-a-simple-base64-encoding-and-decoding
Encrypting data
Regards
Agasthuri Doss

Where to find documentation for RFCs / IDocs?

Hi all,
We're planning to implement some XI interfaces against the MM module - where can we find online docs for available RFCs/IDoc APIs?
Thanks very much in advance!
Steve

Hi,
have a look at this page:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/frameset.htm
to find many MM interfaces: invoices, orders etc
some are not well documented (material movements)
so just ask an interface consultant about them
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Regarding RFC Communication from SAP R/3 to SAP J2EE Engine 6.40

Hello,
     We have an application deployed in SAP J2EE engine 6.20. From SAP R3 (SAP R/3 version is 6.4C), We are communicating to the application deployed in SAP J2EE Engine 6.20 using RFC protocol. EJB module (Deployed in SAP J2EE Engine 6.20) which is being invoked from a Function Module using RFC protocol has the same name as the Function Module name. We were able to communicate to SAP J2EE Engine 6.20 this way.
     Currently, I have deployed the same application in SAP J2EE Engine 6.40. I have followed the same procedure which i have used while depolying and working with SAP J2EE Engine 6.20. But, it is not working, and i was not able to communicate to SAP J2EE 6.40, the same way i did in SAP J2EE Engine 6.20.
   Please let me know whether the procedure for communicating to SAP J2EE Engine 6.40 has changed in comparison with SAP J2EE Engine 6.20.
Also,Any pointers regarding RFC and JCO implementation in SAP J2EE Engine 6.40 willl be helpful.
Thank you.
Regards,
-Shabir Rahim.

Hello ,
      The Connection in sm59 is established successfully> there were no Error thorwn in SAP when testing the connnection. But when i am making background call using a Function Module in SAP R3, the calls reaches Application deployed in SAP J2EE Engine 6.40, But it is failing with the error as,
#1.5#005056A24413003C000000240000126000042853BD899290#1170240034258#/System/Server##com.sap.engine.services.dsr####sstra902_IPC_2629150#Guest#6813e650a93f11dba9f5005056a24413#Thread[JCO.ServerThread-1,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Plain####
#1.5#005056A244130042000000000000126000042853CFDB80F8#1170240341655#/System/Server##com.sap.engine.services.dsr#Guest#2####322aaa71b11811db85e1005056a24413#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#com.sap.engine.services.dsr#Java#DSR_36#com.sap.engine.services.dsr.res.DSRResourceBundle#Error while taking over external passport null#1#null#
#1.5#005056A244130042000000030000126000042853CFDB86BD#1170240341671#/System/Server##com.sap.engine.services.jndi#Guest#2####322aaa71b11811db85e1005056a24413#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.engine.services.jndi#Plain###Incorrect name parameter rfcaccessejb//DCEUR/Z_AIS_IPC_CFG_PRICE in naming operation.#
#1.5#005056A244130042000000040000126000042853CFDB8745#1170240341671#/System/Server##com.sap.engine.services.jndi#Guest#2####322aaa71b11811db85e1005056a24413#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.engine.services.jndi#Plain###Incorrect name parameter java:rfcaccessejb//DCEUR/Z_AIS_IPC_CFG_PRICE in naming operation.#
#1.5#005056A24413003C000000280000126000042853CFDBC4AA#1170240341686#/System/Server##com.sap.engine.services.dsr####sstra902_IPC_2629150#Guest#6813e650a93f11dba9f5005056a24413#Thread[JCO.ServerThread-1,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Plain####
Here, //DCEUR/Z_AIS_IPC_CFG_PRICE is the Funcrtion module name in SAP R/3 6.4C.
Also Please let me know whether is there any Operating Differences between WAS 6.20 and WAS 6.40, for JCO/RFC based Communication( ie Comunicating with WAS 6.40 from SAP r/3 using RFC Protocol). Any materials and Information on how to work on SAP J2EE Engine 6.4 will also be very helpful.
Thank you.

Problem importing RFC/IDOC

Hi All,
While importing RFC/IDOC, there are 3 steps
1. Logon
2. Choose Objects
3. Execute imports
After giving the reqd info in logon, I can go to the next step, but here when I click on RFC or IDOC, I am not able to see the RFCs or IDOCS, IR is not responding, the screen goes blank and I have to close the application(IR).
Any help is appreciated.
Thanks,
Jai Shankar

>>wasn't it 3 that felt like 15 ?
No i guess it is a 15 actually.
>>do you have many Zidoc - ZRFC ?
Yes. This is a IDES system I am connectin to. So lot of them.
Thanks,
Jai Shankar

Regarding ale idocs

Hi....
Please send some FAQ'S regarding ale,idocs
thanks
k..swaminath

Hi,
plz go through the links...
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Reward points if u find useful.
Regards,
Nagaraj

Error importing RFC / idoc despite following note 769356

We have been experiencing a number of problems where we cannot import RFC / idocs in the integration repository. The BASIS team have followed note 769356 and originally this solved the problem but meant that we reverted back to old screens in the Integration Builder and some German texts in the Integration Repository.
Current patch version is Support Stack 4
To get to this point the following steps were followed:
Undeployed com.sap.xi.repository
Deployed the install version of com.sap.xi.repository.
In order to correct the problems with the incorrect screens etc.. The following steps were carried out:
Undeployed com.sap.xi.repository
Deployed the Support Stack 4 version of XITOOLS (includes com.sap.xi.repository)
Applied Support Stack 5 for the Abap kernel
Applied SAPXIAFC04P_1-20000272 and SAPXITOOL04P_1-20000274 via SDM
This fixed all of the problems with German texts etc.. but now we cannot import RFC / idocs again. In the Java Web Start Log (attached) we still get the error message
mentioned in note 769356. We have deleted the Web Start Cache on the client hosts (several restarts of the machine and deletions of the cache). The BASIS guys are going to undeploy and redeploy the repository again but failing that we are running out of ideas.
Does anyone have any suggestions?
Here is the entry in the log file:
java.lang.AbstractMethodError: com.sap.aii.ibrep.sbeans.upload.UploadServiceRemote_Stub.openSAPSource(Lcom/sap/aii/utilxi/misc/r3Connect/SAPConnectionData;Lcom/sap/aii/utilxi/misc/r3Connect/SAPLoginData;Lcom/sap/aii/ib/bom/gen/VersionContext;)Lcom/sap/aii/ibrep/sbeans/upload/SourceID;at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient$ConnectionImpl.connectBean(RemoteUploadClient.java:107)at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient$ConnectionImpl.<init>(RemoteUploadClient.java:91)at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient.getSAPUploadConnection(RemoteUploadClient.java:66)at com.sap.aii.ibrep.gui.tools.r3import.wizard.SAPLogonPage.connect(SAPLogonPage.java:94)at com.sap.aii.ibrep.gui.tools.r3import.wizard.R3ImportWizard$LoginTask.run(R3ImportWizard.java:456)at com.sap.aii.utilxi.misc.thread.ThreadPool$ThreadPoolThread.run(ThreadPool.java:321)

Dan,
you are almost there!
If you religiously follow note 769356, you should not have this problem.
Just do the following as the note suggests:
- From SDM, undeploy only the com.sap.xi.repository
- Unzip SAPXITOOL04P_1-20000274.SCA.zip
- The file ExchangeRepository.sda will be one of the extracted files
- Only import the ExchangeRepository.sda. Do not import the entire ZIP package.
- Restart the J2EE engine.
- Delete Webstart Cache
- From the XI admin page:
http://XIhost:50000/rep/support/admin/status.html
Re-Initialize the Jars for resigning.
- Wait for 5 minutes for the jar signing to finish. Sometimes, the jar signing gets interrupted, you have to let it finish.
The above steps worked for me.
thanks,
Manish

Is SAP Adapter(RFC, IDOC) dead?

Hi
SAP plan to create ESA services for all SAP applications.
But has RFC/IDOC technology future? What do you think?
Companies will not need expensive SAP Adapter more
and XI will not have an advantage in this case.
It will be enough to have some lightweight and cheap ESB with BPEL engine.

Denis
It is not that if we are going to have a new product / service in market then the old technology will not be used. Take an example of Business connector which is there before years but still is being used eventhough XI is present in the market. Still SAP says that it will support but they ask to migrate to the new technology to keep pace with the growing market. There are lot of companies who are using SAP with RFC/IDOC technology. Hence eventhough SAP plans to create ESA services it still will support the existing technology.
---Mohan

Regarding RFC connection in File to IDOC Scenario

Hi everyone,
I was configuring file to Idoc Scenario, i have made all the required configurations in SLD, IR and ID, in XI system and in R/3 System. i have created RFC connection from XI to R/3 system, and its working fine. i have created an Partner profile in WE20 with sender file system name with inbound parameters. But still i am getting error as EDI Partner Profile not defined in WE05- iDOC ADDED WITH ERRORS. Do we need to create an RFC connection from R/3 system to XI for file to Idoc Scenario
!!! Note: RFC connection from R/3 system to XI is not working, will this be a problem for file to idoc scenario. !!!
Regards,
Varun Reddy.K

Hi Varun
Follow these steps
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
Regards,
Santosh

Regarding Error handling and customisation in RFC, Idocs and Proxy

Hi,
I wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means and also the error handling provided in these methods.
Please let me know in detail if possible.
Regards,
Sampada

Hi ,
Check this blog to know when to use which adapter:
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
we use proxy in sap 6.0 version or higher.
Basically used for adapter less communication
& very high volume of data has to be transfered.
Step for Configuration fo IDOC in R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards,
Vinod.

Regarding rfc idocs

Similar Messages

Maybe you are looking for