JDBC to File and RFC adapter

Hi All,
In my scenario, i am sending file from a database system to SAP system. Here I am using JDBC/ webserveices adapter at outbound side to query the database and FILE and RFC at inbound side to send file and workflow notification.
my requirement is to send file as batch to SAP system(after business hours), send workflow notiication to the responsible person, and when the file is stored on application server then only i should send the notification to the person.
I know this can be acheived by BPM by using wait step but I am not sure how to do it only for RFC adapter to kick the notification once the file has stored and confirmed.
Can anyone help me in this issue.
Reg
Sre.

>
sre wrote:
> Hi All,
>
> In my scenario, i am sending file from a database system to SAP system. Here I am using JDBC/ webserveices adapter at outbound side to query the database and FILE and RFC at inbound side to send file and workflow notification.
> my requirement is to send file as batch to SAP system(after business hours), send workflow notiication to the responsible person, and when the file is stored on application server then only i should send the notification to the person.
>
> I know this can be acheived by BPM by using wait step but I am not sure how to do it only for RFC adapter to kick the notification once the file has stored and confirmed.
>
> Can anyone help me in this issue.
>
> Reg
> Sre.
There are two options,
1. With BPM you can have the send step for file request an acknowledgment and then have the send step for the RFC call after the previous file send step.
2. Without BPM, use the same Business system (single receiver det.) and have multiple interface determination (file&RFC). Use the option maintain order at runtime and have the file interface above the RFC. This will act like an EOIO.

Similar Messages

RFC Sender problem between 46D and RFC adapter

Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
 CALL FUNCTION 'ZSD_DCF_SEND_TAG'
 IN BACKGROUND TASK
 DESTINATION 'XISYSTEM_TRFC_DCF'
 EXPORTING
 pt_filing_info = gt_filing.
 COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
Torstein

Hi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

FILE and FTP Adapter file size limit

Hi,
Oracle SOA Suite ESB related:
I see that there is a file size limit of 7MB for transferring using File and FTP adapter and that debatching can be used to overcome this issue. Also see that debatching can be done only for strucutred files.
1) What can be done to transfer unstructured files larger than 7MB from one server to the other using FTP adapter?
2) For structured files, could someone help me in debatching a file with the following structure.
000|SEC-US-MF|1234|POPOC|679
100|PO_226312|1234|7130667
200|PO_226312|1234|Line_id_1
300|Line_id_1|1234|Location_ID_1
400|Location_ID_1|1234|Dist_ID_1
100|PO_226355|1234|7136890
200|PO_226355|1234|Line_id_2
300|Line_id_2|1234|Location_ID_2
400|Location_ID_2|1234|Dist_ID_2
100|PO_226355|1234|7136890
200|PO_226355|1234|Line_id_N
300|Line_id_N|1234|Location_ID_N
400|Location_ID_N|1234|Dist_ID_N
999|SSS|1234|88|158
I would need a the complete data in a single file at the destination for each file in the source. If there are as many number of files as the number of batches at the destination, I would need the file output file structure be as follows:
000|SEC-US-MF|1234|POPOC|679
100|PO_226312|1234|7130667
200|PO_226312|1234|Line_id_1
300|Line_id_1|1234|Location_ID_1
400|Location_ID_1|1234|Dist_ID_1
999|SSS|1234|88|158
Thanks in advance,
RV
Edited by: user10236075 on May 25, 2009 4:12 PM
Edited by: user10236075 on May 25, 2009 4:14 PM

Ok Here are the steps
1. Create an inbound file adapter as you normally would. The schema is opaque, set the polling as required.
2. Create an outbound file adapter as you normally would, it doesn't really matter what xsd you use as you will modify the wsdl manually.
3. Create a xsd that will read your file. This would typically be the xsd you would use for the inbound adapter. I call this address-csv.xsd.
4. Create a xsd that is the desired output. This would typically be the xsd you would use for the outbound adapter. I have called this address-fixed-length.xsd. So I want to map csv to fixed length format.
5. Create the xslt that will map between the 2 xsd. Do this in JDev, select the BPEL project, right-click -> New -> General -> XSL Map
6. Edit the outbound file partner link wsdl, the the jca operations as the doc specifies, this is my example.
<jca:binding />
 <operation name="MoveWithXlate">
 <jca:operation
 InteractionSpec="oracle.tip.adapter.file.outbound.FileIoInteractionSpec"
 SourcePhysicalDirectory="foo1"
 SourceFileName="bar1"
 TargetPhysicalDirectory="C:\JDevOOW\jdev\FileIoOperationApps\MoveHugeFileWithXlate\out"
 TargetFileName="purchase_fixed.txt"
 SourceSchema="address-csv.xsd"
 SourceSchemaRoot ="Root-Element"
 SourceType="native"
 TargetSchema="address-fixedLength.xsd"
 TargetSchemaRoot ="Root-Element"
 TargetType="native"
 Xsl="addr1Toaddr2.xsl"
 Type="MOVE">
 </jca:operation> 7. Edit the outbound header to look as follows
 <types>
 <schema attributeFormDefault="qualified" elementFormDefault="qualified"
 targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/file/"
 xmlns="http://www.w3.org/2001/XMLSchema"
 xmlns:FILEAPP="http://xmlns.oracle.com/pcbpel/adapter/file/">
 <element name="OutboundFileHeaderType">
 <complexType>
 <sequence>
 <element name="fileName" type="string"/>
 <element name="sourceDirectory" type="string"/>
 <element name="sourceFileName" type="string"/>
 <element name="targetDirectory" type="string"/>
 <element name="targetFileName" type="string"/>
 </sequence>
 </complexType>
 </element>
 </schema>
 </types> 8. the last trick is to have an assign between the inbound header to the outbound header partner link that copies the headers. You only need to copy the sourceDirectory and SourceGileName
 <assign name="Assign_Headers">
 <copy>
 <from variable="inboundHeader" part="inboundHeader"
 query="/ns2:InboundFileHeaderType/ns2:fileName"/>
 <to variable="outboundHeader" part="outboundHeader"
 query="/ns2:OutboundFileHeaderType/ns2:sourceFileName"/>
 </copy>
 <copy>
 <from variable="inboundHeader" part="inboundHeader"
 query="/ns2:InboundFileHeaderType/ns2:directory"/>
 <to variable="outboundHeader" part="outboundHeader"
 query="/ns2:OutboundFileHeaderType/ns2:sourceDirectory"/>
 </copy>
 </assign>you should be good to go. If you just want pass through then you don't need the native format set to opaque, with no XSLT
cheers
James

Soap Sender and RFC Adapter receiver getting APPLICATION_ERROR

Hi, all,
I have a webservice soap sender and RFC Adapter receiver scenario, it works fine with RFC "RFC_SYSTEM_INFO", When i tried the RFC "RFC_READ_TABLE", getting the following error message, <SAP:Code area="RFC_ADAPTER">APPLICATION_ERROR</SAP:Code> in
SXI_MONITOR, in webservice client, i am getting error message like this:
<faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <rfc:ZZTEST_RFC_READ_TABLE.Exception xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
 <Name>TABLE_NOT_AVAILABLE</Name>
 <Text>QUERY_TABLE not active in Dictionary</Text>
 </rfc:ZZTEST_RFC_READ_TABLE.Exception>
Thanks a lot!

Hi
Its not compulsory but its good to wrap it as Z object.
Well if you are facing problem with SOAP data. Then try to do one thing. Check with the data you received from SOAP message. If this works
Then try to check in mapping is it passing the data correctly or not. With this check with the user authorization PIAPPLUSER. if its having less authorizations to execute this BAPI in ECC
Thanks
Gaurav

How to use IDOC and RFC adapter in 1 scenario?

We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and what are the design and configuration objects we require to create?

To achieve this you have to use
Two Interface Determinations
Two Communication Channels (IDOC & RFC)
& Two Receiver Aggrements.
Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively.

HTTP and RFC Adapter are not Required Sender

Hi All,
I have one dought....
Why Plain HTTP and RFC Adapter are not Required Sender Communication Channel and Sender Agreements...
I Know this two Adapter are in ABAP Stack....
Please clarify my dought...
Regards

Idoc Adapters do NOT require Sender Communication Channel.
The Sender System identifies itself at the Integration Server, with the fields SNDPOR and Client of the Control Record.
Sender Communication channels are used for communication betweeen the Application System and the Integration Server.
In the case of Idocs, all idocs are tranferred to the Integration Server pipeline and NOT to the regular EDI/IDOC interface.
The RECEVIER DETERMINATION is based on the values in the Control Record.
If you are doing ALE, then you have to maintain the idoc types which are NOT to be transferred to the Integration server by executing report IDX_SELECT_IDOCTYP_WITHOUT_IS.
By maintaining the Idoc Types using this report, only these idoc types are sent to the regular EDI/IDOC interface.

IDOC Adapter and RFC Adapter

Hi experts,
Q1. What are the configurations steps (Transaction codes) required at R/3 and XI while sending the IDOC to XI? Please provide the list of TCodes required at both sides. if any weblog is exists which provides detail explanation on IDOC scenarios plz provide the path.
Q2. While sending the IDOC we need to generate partner profile and port. How many types of port exist and wht each port represents?
Q3. In RFC Sender Adapter we need to create RFC port in R/3 and there we specify Connection type as T which TCP/IPwhy we use connection type T instead of 3 (which represents connection type as R/3). While communicating with SAP systems we need to specify the connection type as 3.
Q4. How many types of partner profiles exist and wht each type represents?
Q5. How to transport design, configuration objects and SLD objects from Development system to Quality system. Please provide me the steps to transport the objects?
Q6. Once the objects are transported a .tpz file is created wht is the purpose of the file and where it will generated? Suppose if Ive transported the namespace from Dev to Quality system then at quality side to which SWC this transported namespace is assigned. Do we need to create any SWC at quality system side?
Cheers
Faisal

Hi Abdul,
for the first one u need to create a logical system and assign that logical system and need to create a port and partner profile and distribute the system,, for that follow this blog
Steps
SAP XI
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.
2.& 3 ) for the 2nd question the answer was in above u need to create the partner profile and port.
port can be created as HTTP Port and RFC port which are used to communicate with the R/3 server and depends on the requirement we need to choose the port..
4. partner profile creation depends on ur scenario, it is a custmized one it purely depends on the customer requirement, there is no specific partner profiles exists in R/3.
5. For transportation u may choose File level transport or CMS, if u trnasfer through File level it is very easy to maintain and reimport in the production server,, just while exporting from the development server a .TPZ file was created and import this .TPZ file in the production server this gives the entire objects of IR and ID, but when u deal with SLD instead of .tpz there u will be creating .zip file, so u neeed to reimport the file in the production server..
6. The .TPZ file will be created when u export the objects either in IR and ID..., so as i explained in the above point it will go top the export directory of development server and import in production server with IMPORT directory..
regards,
Kishore

XI and RFC adapter

Hi
The RFC Adapter configuration has been done successfully and the adapter starts up successfully.
In our scenario, we attempt to receive an xml message from my local machine through a file adapter, and pass this along to the RFC Outbound adapter to execute a RFC on the CRM box.
The following error message is encountered in the XI monitoring tool.
==============================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="connection closed (no data)" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (connection closed (no data))</SAP:Text>
</SAP:ErrorHeader>
===================================================================================================
I then stop the RFC adapter and attempt the scenario again. I get the following error message in XI monitoring tool.
================================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n)</SAP:Text>
</SAP:ErrorHeader>
==================================================================================================================

Hi Eduardo ,
Please check wether the following steps are done in BPM:
1.Async Recieve
A.Properties :
Please set the following
Message:Message 1
Mode:asynchronous
B.Container Data :
Declare Message 1 as asynchronous abstract interface with message type of outbound interface(File Structure).
2.Sync Send
Pre-Requisite:
Copy the inbound Syncronous Interface to Sync_interface_abstract by changing the direction in the message interface of Interface object in the Integration Repository.
A.Properties
Mode:Synchronous
Request:Message 1
Response:Message 2
Syncronous Interface:Sync_interface_abstract
Recievers From :Send Context
B.Container Data:
Message 2 should be declared as the asynchronous message interface with Response message type in inbound interface(Rec Syst Interface).
3.Async send
A.Properties:
Mode:Asynchronous
Message:Message 2
Acknowledgment:None
Recievers From :Send Context
Integration directory has to be configured to send data forth and back to BPM.
1.Send MESSAGE From Outbound interface to BPM.
OutBound and Abstract Interface needs to be mapped in the interface determination and Abstract interface has to be binded to Business Process Name in the repository.
Outbound->Your OutBound Interface(File Interface)
Abstract->Message 1
Reciever Service-> Your Business Process Name
2.Send MESSAGE From BPM to Inbound interface.
Abstract and Inbound interface needs to be mapped in the interface determination and Abstract Interface has to be binded to the Receiver Service/Business System.
Abstract->Message 1
Inbound->Your Inbound Interface(RFC)
Reciever Service-> RFC SYSTEM(SAP)
These are the general steps to follow for Async/sync pattern.
Please let me know if all the steps are configured.

Urgent ! BPEL file and ftp adapter problem.

Hi All!
I have created a bpel process having two partner links.One for the ftp adapter and one for the file adapter. I want the ftp adapter to poll the *.pdf files in the specified directory on the remote machine periodically and get them to my local machine here. For this I am using ftp adapter with read operation and with opaque schemas(because I want the files as they are without any transformation). I am using a receive activity with the ftp adapter, with the create instance box checked.
To write the file to the local machine I am using file adapter and write operation.File adapter also uses opaque schema.With this file adapter I am using invoke activity.Invoke is below the receive activity in the bpel process. I deployed this successfully on the default domain. I want the bpel process to run automatically,depending on the polling frequency given and create instances and bring the files to my machine.
But it is not happening.
Can anybody tell me where I am going wrong.How to accomplish this? It is very urgent issue for me.
Thanking in advance,
Regards,
Deepika.

Hi All!
Now I am able to write files and also read files successfully with the remote server. I followed the same method described above.I am using binary format itself for pdf files.But I have to check the option 'to delete files after successful retrieval' to make this happen.I created several partnerlinks with the option in the ftp adapter not checked,but it is not working. Has anybody done successful retrieval without deleting the files at the remote server? If so please let me know.
Thanking in advance,
Regards,
Deepika.
Message was edited by:
Deepika

Offline backup and RFC adapter

Hello,
I have a scenario where sap ECC 6.0 send data to XI via RFC adapter. Because we are on SP12 I set Maximum Reconection Delay parameter of sender agreement to make sure that adapter will work when the system is up again. Unfortunatly when in CC-monitoring I get a green light, but in sm59 on ECC 6.0 I get error. Data are not send to XI. Could anyone help me?
Many thanks,
Milan

Hi you are doing RFC----Xi-----scenario....
now first you have to make t type rfc destination .......you will define program is here and you will be used same program id in sender communication channel(program id is case sensetive)...
define gateway host and gateway service of your r3 system not xi.....
you can get the gateway service from SMGW transaction.......it will be like this....sapgw..you have to put the two digit system no of ur r3 system on dots ....like this sapgw02.
go to tcode smgw >>>>goto>>>> Logged on clients and seeyour connection is active or not.....
then test ur connection sm59....
thanks
kunaal

Multiline BAPI return structure and RFC Adapter

Since SP14 RFC Adapter check return structure of RFC function.
But how it works if BAPI returns multiline BAPIRET2?
Will adapter loop all elements and perfom commit only if all alements don't have errors.

I'am about this:
As of SP 14 support for commit handling for single BAPI calls was added to the RfcAdapter receiver channel. If activated in the receiver channel setting, the received XI message will be executed as synchronous RFC (sRFC) in the receiving system. This is also true for asynchronous (QoS EO) XI messages to receive and analyze the execution result by the RfcAdapter.
 The received response is parsed by the RfcAdapter to get the BAPI return parameter with name "RETURN". This return parameter can be of BAPIRETURN, BAPIRET1 or BAPIRET2 types. The "RETURN" parameter is checked for the response status (field TYPE) which can take following values:
 1. 'S' : Success
 2. 'I' : Information
 3. 'W' : Warning
 4. '' : Empty String
 5. 'A' : Abort
 6. 'E' : Error
 If the response contains one amongst the first four response status then it implies that the BAPI was successful. If the response contains one amongst the last two response then the BAPI failed. If the BAPI "RETURN" parameter is of not of type ABAP structure rather of type ABAP table, a empty table is also considered as successful execution result.
 In case of a successful execution the BAPI function module "BAPI_TRANSACTION_COMMIT" is called within the same context to trigger the commit of the BAPI. In case of a failure the BAPI function module "BAPI_TRANSACTION_ROLLBACK" is executed by RFC Adapter which rolls back the changes.

How to implement Exception Handling error in IDoc to File and RFC to File

Hi,
We are implementing the two below scenarios :
1. IDOC to File
2. RFC to File
We have to implement the Exception Handling for the above two cases. Kindly could you provide the inputs to implement the Exception Handling for the above two cases.
Please provide the precious inputs to implement this.
Thanks,
Ramesh

Hi Ramesh,
The exception handling for idocs
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm
Exception handling in File to IDoc Scenario
For RFCs
Re: Passing SAP Exceptions to a sync SOAP Call
Error Handling when using RFC
Exception Handling while Calling RFC - BPM
handle exceptions in remote function modules
Regards,
Prateek

RFC Adapter - JCO Exception - Please Urgent

I am developing a scenario from File--RFC integration. I am using File and RFC adapter to perform this transaction.
The File Adapter is picking the file properly and the trnaformation (Mapping Program) is also happening properly. But the RFC is throwing the following error. I got this error info from the Runtime Workbench.
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZPS_XI_ACTIVITY_CREATE in remote system (RfcClient[BAPI_CreateActivity_Receiver]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR
Error Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZPS_XI_ACTIVITY_CREATE in remote system (RfcClient[BAPI_CreateActivity_Receiver]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR.
The RFC is executing without any problem when I execute this from the transaction SE37.
I have created communication channel in Integration Directory in appropriate manner.
I also created RFC destination in the XI system (TCODE SM59) and the same is using in the "Receiver Determiiation - Service".
I have not done any configuration at SAP R/3 side. Is any config required at R/3 end for this scenario - please let me know.
Please throw some light on this. I will greatly appreciate your help.

Friends,
Please suggest on this vague problem that I am facing. Your help would be greatly appreciated.
1. I am using SAP-PS (Projects & Systems) BAPI 'BAPI_BUS2002_ACT_CREATE_MULTI' to create the activities for a project. According to this BAPI documentation,
- First call 'BAPI_PS_INITIALIZATION' before make this BAPI call
- After BAPI call, we should use 'BAPI_PS_PRECOMMIT' and 'BAPI_TRANSACTION_COMMIT'.
2. Hence, I have developed Z-Func Module with Initialize, BAPI call - then Pre Commit and Commit.
3. This is executing from SE37 without any issues. Other parameters to make a remote call is also set properly.
4. To make sure that, I made a JCO call from Java Program using PDK for Java. This is also working fine.
5. But when I used this in the XI scenario (File-XI-RFC) this is showing ABAP dump and this is invoking from Pre-Commit module.
I couldn't figure it out why it's happening like this.
I did lot of troubleshooting and the details are as follows for your reference.
1. The mapping program is working fine without any issues. I confirmed this by writing these input values to the file (ofcourse lot of pain) inside the function module. All the values have been parsed by XI and coming to Func Module as expected.
2. No issues with logical destinations (SM59).
3. I have tried other options such as clearing the Cache...etc.
Hence, please throw up some light. If any body tried with these kind of BAPI (needs initialize, pre-commit and commit) I really appreciate your effort.
Can we enable the debugging of func module when the XI makes a call...? - I tried with Standard options that seems doesn't work.

FILE-RFC ADAPTER problem

Hi all,
I am trying file->xi->rfc adapter scenario.
My scenario is employee information is written to flat file n will be kept on ftp server.THe file adapter will pickup the file and sends it to rfc adapter through pipeline service.
This is going well. The problem is the data is not being updated into receiving sap system.
in SXMB_MONI transaction the messages are successully processed . But there are no messges in rfc adapter when i gone through idx5 transaction???
Any one have idea??
Thanks in advance.
Rgds,
Ram Sri

sxmb_moni only shows the status of the integration engine's processing, not the result of what happened in the rfc call. First, you can check if the adapter framework successfully passed the message to the destination system (not on moni, thru RWB)
as far as did the rfc succeed - it's as difficult as always with internal processing. We did a lot of testing by debugging modules on the destination side (manually putting in the data as the adapter would've to step thru & see where the message is "lost") - have not yet found a better way, sorry. It's not so much a problem with XI, just in general the difficulty to debug rfc's

Graphical message mapping examples for JDBC and RFC lookup

hi, can any body provide me graphical message mapping examples for the "JDBC Lookup" function and "RFC Lookup" function?
I'm now studying the graphical message mapping and want to try those 2 functions. thank you.
I expect the examples to be simple enoung, not need to set up much.

>
Madhu_1980 wrote:
> can u check this link:
>
> PI 7.0 & 7.1 Mapping - Blogs,Articles,Wiki,Code Samples and Videos Collections https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=79955426
>
> it contains a link : SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups /people/jin.shin/blog/2008/02/15/sap-pi-71-mapping-enhancements-series-graphical-support-for-jdbc-and-rfc-lookups
May be I'm too foolish to follow those links, I got issues of each links.
What I really want is an example from step0
Swarup:
Refer the Lookup document - Easy Lookup in Process Integration 7.1
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20befc9a-aa72-2b10-ae9b-b0988791d457
The first step is "Create an RFC Enabled Function Module for look up", but where can I create the function module? Should I use ESB, IB? or use transaction 'SE11' ?
Kulkarni:
Very good links for RFC lookup with 7.0/3.0
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70d90a91-3cf4-2a10-d189-bfd37d9c3231&overridelayout=true
At page6 "PI Development/Configuration", it saies "You are on the design maintenance screen in the Integration Builder.Expand the subnodes for the software component version for which you want to import interfaces".
What is "design maintenance screen" ? My IB version is: Service Pack:08 Release:NW07_08_REL.
When I open IB, it display a screen titled with "Configuration: Intergation Builder", I did not find "software component version" node on the left tree.
Madhu_1980 :
it contains a link : SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups /people/jin.shin/blog/2008/02/15/sap-pi-71-mapping-enhancements-series-graphical-support-for-jdbc-and-rfc-lookups
The Prerequisites state:
The JDBC channel to be used for the lookup must be configured and activated in the Integration Directory.
The definition of the table used for the lookup must already be imported into the ES Repository as an external definition
But I don't know how to create a JDBC channel and define the table.

JDBC to File and RFC adapter

Similar Messages

Maybe you are looking for