Problem in file to RFC Asynch interface.

Dear Experts,
One interface is there in Production environment that " file to RFC " receiver is SAP CRM system through BAPIs. frequency is daily one file from ftp to CRM system. One day file is getting updated in CRM properly, one day not getting updated like this way it is happening regularly. In sxmb_moni of PI system showing successfully processed. In sxmb_moni of CRM system no messages appearing whether successfully processed messages as well as failures. RFC connections also be good and in PI communication channel monitoring also showing successful.
In this case what i have to do? Kindly suggest me.
Thanks & Regards,
Srihari.

Hari,
If that is the case then cancel all the messages and also once do the full cache refresh with the following URL
http://host:50000/CPACache/refresh?mode=full
Regards
Praveen

Similar Messages

Problem in file to rfc scenario without using BPM concept

hi ,
I have configured the file to rfc scenatio and in that i have created a synchronous message interface .i have even aaded modules to my sender adapter .
I have one sender aggrement , 2 receiver aggrement , 1 interface determination , and 1 receiver determination .
the problem that i am facing is that i am able to perform the operations on r3 side succesfully but i am not getting the response back in xi .
can any one pls help me in getting out of this problem .
with regards
Bhawarlal Choudhary

Hi Amit ,
My scenario is for creating the notification ( in plant maintenance) . every time i transmit a file a new notification nos is generated and even i am able to see it in SAP . in RWB when i check my communication channel i am not getting any response . The synchronous process seems to be working fine according to me do i need to even create a FRC communiation channel for sender as i have not done that .
with regards
Bhawarlal Choudhary

Problem in FILE to RFC scenerio

Hi,
I am working on File to RFC Scenerio
I am getting a problime in Communication channel (Sender).
The problem is coming in File COntent Conversion
Parameters are like
Documenet name : MT_ROXY ( ->Header -> EMPNO
                                                             -> EMPNAME
                                                             -> DEPTNAME)
Recordset Name: Details
Recordset str     : HEADER,*
Recordset Seq   : Variable
" per message   :*
Conersion Params:
ignoreRecordsetName : True
HEADER.addHeaderLine : 0
HEADER.fieldSeperator: ,
HEADER.endSeperator: 'nl'
HEADER.fieldFixedLengths : 12,40,40
HEADER.fieldNames          :EMPNO,EMPNAME,DEPARTMENTNAME
HEADER.lastFieldsOptional : YES
Problem:The message content i am getting is like
<ns:MT_ABAPPROXY>
−
     <HEADER>
<EMPNO>IT,Munish,22</EMPNO>
</HEADER>
−
     <HEADER>
<EMPNO>IP,Munish1,2</EMPNO>
</HEADER>
−
     <HEADER>
<EMPNO>IS,Munish2,2</EMPNO>
</HEADER>
−
     <HEADER>
<EMPNO>IQ,Munish3,2</EMPNO>
</HEADER>
−
     <HEADER>
<EMPNO>IR,Munish4,2</EMPNO>
</HEADER>
</ns:MT_ABAPPROXY>
as it does not dividing the Fields by ,
as it shud come like
<EMPNO>IR,2</EMPNO>
<EMPNAME>Munish5</EMPNAME>?
<DEPARTMENTNAME>2</DEPARTMENTNAME>
but its not taking the other 2 filds and not separating by , sepreator,
Kindly guide me in solving this problem on urgent basis
Thanks in Advance
Munish SIngh

HI,
Then use only fieldSeparator see the spelling it should be in proper case.
refer the below weblog for more information:
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
Also refer the file FCC parameters.
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
Thnx
Chirag

Output XML file problem (in FILE to RFC scenario)

hi,
   my problem is that in the export parameter i have 3 variables but my output xml file shows only 2 parameters . I have checked my mapping all 3 parameters are mapped properly in output mapping .
Initially when i started the scenario there were only 2 parameters in my export list .
i completed this suuccesfully and then as per new requirement one more parameter was needed to be added i added a new parameter and reimported my rfc .
the response tab of the reimported RFC shows me the newly added parameter but my final xml file only shows me the previous 2 it doesnt show me the newly added one is there any seeting which i need to change like in idoc where we have to readd the idoc in IDX2
With regards
Bhawarlal Choudhary

Hi,
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
     The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
     The Client must be the client number of the backend SAP system.
     Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
     Double-click on the business system in the Integration Directory.
     Switch to Edit mode.
     Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
     The RFC Destination is from step 3.1.
     The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Regards
Hemant
If find helpful plz award points

Problems escenari File - Xi - RFC(R3)

I have the following integration scenario
Field TXT separate for por ";", ejemplo: 123,wer,clp,001
Has been created comunication channel type sender: FILE_Mov_Conta_Valorados_Sender
Whit the following properties
<i>Document Name</i>: Mov_Conta_Valorados_L_MT
<i>Document NameSpace</i>: NameSpace   Mov_Conta_Valorados_L_MT
<i>Record Name</i>: Mov_Conta_Valorados_L_MT
<i>Recordset Structure</i>: SICC,*
<i>Recrodset Secuence</i>: Ascending
Name :SICC.fieldNames
Value:id_doc,fec_doc,cod_filial,fec_conta,cod_moneda,nro_doc,cod_banco,fec_valor,monto_doc,nro_doc_asig,txt_pos
Name : SICC.fieldSeparator Value: ;
Name : SICC.endSeparator    Value: 'nl'
The data type has been created wich will receive the sended file
XML:
<ns0:Mov_Conta_Valorados_L_MT xmlns:ns0="urn:vivesap:sap:legacy:sicc">
   <SICC>
      <id_doc/>
      <fec_doc/>
      <cod_filial/>
      <fec_conta/>
      <cod_moneda/>
      <nro_doc/>
      <cod_banco/>
      <fec_valor/>
      <monto_doc/>
      <nro_doc_asig/>
      <txt_pos/>
   </SICC>
</ns0:Mov_Conta_Valorados_L_MT>
The data mapping has been made with the imported RFC wich expect as data a "1 to N" data table
All objects has been activated, the message sending has been activated. Both states, monitoring and workbench,apeear as successfull and after checking the table in R3 shows no data
Please your help!!!!!!

Hello to all.
I found the error, the problem was the configuration of parametros:
Missing
SICC.processFielName -> fromConfiguration
and aditionaly in Message Mapping missing the function
- SplitByValue
- CollapseContext
Now it records a registry in the table, now the problem is to record more of a registry.
Thanks.

Message not coming to Receiver system - File to RFC

I have a small problem in File to RFC connection. We are trying to create a PO using a BAPI. In the XI system , it shows the XML is processed successfully but PO is not generated in the R/3 system.
Is there any way to check whether the message has come to the receiver system. In fact we tried with a dummy insert command in a Z table . Even thats not happening. I thing the message is not at all coming to the receiver system, but the SXMB_MONI in Xi shows the message got processed successfully.
Do we need to make any settings in the Receiver system?

hi,
did you commit this bapi:
a) in the rfc adapter (in your communication channel) if you have sp14
b) in the bapi wrapper if you have < sp14 ?
https://websmp206.sap-ag.de/~sapdownload/011000358700000328352005E/HowtouseBAPandccBPM.pdf
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

FILE - XI - RFC Problem

Hi all!!
I'm doing tests with my FILE -> XI -> RFC interface.
The Status is Succesful, but the XI -> RFC mapping isn't done. Looking in SXMB_MONI in the Payload of Request Message Mapping I got:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:Z_F1FSD_REC_PEDIDO_EDI xmlns:ns1="urn:sap-com:document:sap:rfc:functions">
<T_REC_PEDIDO_EDI />
</ns1:Z_F1FSD_REC_PEDIDO_EDI>
I`ve already imported again the RFC, but nothing helps.
Does anybody knows what is the problem?
Tks a lot,
Daniela Machado

HI,
Test the Mapping in the Message Mapping with Test Tab.
For this,take message from SXMB_MONI and test the mapping..
If it works, then there is a problem with Cache. For RFC cache Refresh-
How to refresh XI RFC Metadata Repository?
Hope this helps,
REgards,
moorthy

File to RFC problem

Hi Friends,
I am doing a scenario CSV File to RFC. This is for SO creation in R/3 thru RFC.
I was provided with a wrapper RFC which internally calls the Sales order create BAPI.
Now my problem is When I go to SE37 and test the function module the SO is getting created but with the same data when I pass thru XI the so is not getting created. What can be the problem. Is there any authorization issue, if so tell me what auth should be given.
Vijay

Vijay,
Did you check the BAPI return parameter and what is the message you are getting. I think the problem is because of the conversion exit. I this this should be the problem R/3 expects leading zeros for vendor/customer numbers ans this is quite common error. Either change the wrapper RFC to handle this kind of values like calling the conversion routin before passing to the BAPI. This conversion routin can be foung in the domain.
Or add the leading zeros in XI mapping.
use this code in udf while mapping
int intDif, i;
String strDiff = new String();
intDif = 10 - Par_Input.length();
if(intDif > 0)
strDiff = "0";
for(i=1; i<intDif; i++)
strDiff = strDiff.concat("0");
strDiff = strDiff.concat(Par_Input);
return strDiff;
else return Par_Input;
Thanks,
Prakash

File to RFC Error com.sap.engine.interfaces.messaging.api.exception.Messagi

Hi ,
I am doing File to RFC Scenario.
My file get picked and I able to view the audit log under RWB message monitoring.
Here I am getting the error
u201CTransmitting the message to endpoint dest://XI_INTEGRATION_SERVER using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message using HTTPTransmitter. Reason: java.net.MalformedURLException: unknown protocol: dest.
Can any one tell me what is the reason.
Regards, Navneet

Hi Prakasu,
I am using PI 7.1 version .
When I opened SMICM there I am finding the HTTP Port as 52000.and the BS at SLD are also using the same Port in URL..
And when i verified with the Basis they confirmed that Exchange profile is set correctly.
But My file adapter is still not able to send the data to IS.
Than I configured a scenario file to file without IR object and in this case data is coming to IS and it is succesfull also.
what is the reason that in this case file adapter not able to push the data to IS.
I used File adapter with NFS protocol.
regards,
navneet

File-RFC Syncronous interface with out BPM

Hi experts,
i have a scenario syncrhonous: file to rfc and get back response rfc to other file. I have 3 communication channel: 1 sender file, 1 receiver file, 1 receiver RFC, sender aggrement, receiver aggrement, interface determination and receiver determination.
I also placed module parameters in the sender file CC as:
Processing sequence:
Module name Module type Module key
AF_Modules/RequestResponseBean Local Enterprise Bean 1
CallSapAdapter Local Enterprise Bean 2
AF_Modules/ResponseOnewayBean Local Enterprise Bean 3
Module configuration:
Modulekey parameter name parametervalue
1 passThrough true
3 receiverChannel <File receiver CC>
3 receiverService <Receiver service name>
File is processed and got response from RFC but I dont see any file in the required folder. I successful message in SXMB_MONI.
both FCCs in RWB is in green status.
Where would be the issue, any inputs.
Thanks
Rajeev.

HI All,
For response back from RFC to File in SXMB_MONI i see the successful message and the pipe line steps are as follows:
Inbound Message (Central)
XML Validation inbound channel respose
Request Message Mapping
XML Validation outbound channel response
Thats it.. I can see request and respose message successful but I dont see the file on the file server.
I created
Service Interface wtih request and respose message types
RFC is imported it contains request and respose
Created two Message mapping
created one Operation mapping with request and response
Created File sender Communicaton channel, receiver communication channel, RFC receiver Communication channel
Sender Communciation channel(Best effort) is updated with receiver communciaiton channel paramters
Receiver determination
sender aggrement
receiver aggrement
inerface determination
AM I missing some thing?
I can see the payload as required in response message of RFC but unable to see the file on the file server.
Any inputs are appreciated.
Thanks
Rajeev

File to RFC scenario - receiver determination problems

Hi ,
Im trying to work out a flat file to RFC scenario, and am facing problems in configuring the receiver determination .
While creating my receiver determination, in the configured receivers, when i click on the F4 help to select service, i do not see the business system that i configured in SLD .
This system i have configured as an WAS ABAP system and provided all relevant data. I can also import objects from this system into IR, so i dont think i have set it up wrongly. I have also created RFC destination .
Is there some setting that has to be made that im missing ? Could somebody point out why im not able to see this system in the list of business services available at receiver configuration time ?
Thanks,
Joe
I also cleared the SLD cache by the way.. that didnt work either .
Message was edited by:
Joe Stein

Thanks a lot for you replies guys , but problems still not solved ;
1. I looked at the blog given and ive done everything pretty much as given . My problem lies in not finding the business system itself in the list of services for the configured receiver. How to implement this has not been shown in the blog.
2. I tried refreshing the cache and checking again, but it still doesnt show me the necessary step.
SOS !
I checked in the inbound system , and found that an RFC wasnt created for the XI system . I created that but i still cant see this system as a business system when i try to create the receiver determination . Do i need to recreate the technical system in the landscape to incorporate this change ?
Any pointers at all ??
Message was edited by:
Joe Stein

File to RFC problem- data is not inserting into ztable in R3 system

Hi
i have done File to RFC scenario which picks data from flat file and inserts into ztable via RFC in R3. but while testing my scenario everything is successful in XI monitoring (Successful flag in MONI and RWB) and in auditlog message status is DLVD.
it seems to be everything successful in XI and RFC call also successful in R3 system.
but for some reason data is not inserting into table (RFC is used to insert data into ztable)
Is there any way to debug RFC call excecution in XI..?
RFC code is like this:
insert ZMM_AUTO_GR from INPUT_TABLE.
commit work.
END FUNCTION.
please advice what could be the reason not inserting into table.
Help would be appreciated.
Regards,
Rajesh

Hi Praveen,
please see audit log- from communication channel monitoring..
Receiver channel 'CC_INCA_RFC_SAPECC_Receiver' for party '', service 'R3DCLNT210' (internal name 'RfcClient[CC_INCA_RFC_SAPECC_Receiver]')
Client data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=210, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=jsaha, jco.client.sysnr=00, jco.client.ashost=ausr3devdc02}
Repository data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=210, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=jsaha, jco.client.sysnr=00, jco.client.ashost=ausr3devdc02}
Current pool size: 1, maximum pool size : 1
Channel History
- OK: 2008-07-28 04:32:04 PDT: Message processed for interface ZAUTO_GR_STAGE_INCA
- OK: 2008-07-28 04:31:04 PDT: Message processed for interface ZAUTO_GR_STAGE_INCA
- OK: 2008-07-28 03:56:56 PDT: Message processed for interface ZAUTO_GR_STAGE_INCA
- OK: 2008-07-28 03:49:04 PDT: Message processed for interface ZAUTO_GR_STAGE_INCA
- OK: 2008-07-28 03:48:04 PDT: Message processed for interface ZAUTO_GR_STAGE_INCA

Time recording interface - file to RFC

Hi all,
I am trying a file to RFC scenario for a time recording interface. The time recording machine will generate flat files with the following fields
empno, yyyymmdd, hhmmss, flag for check-in and check-out , terminal id
I wanna know which BAPI can be used for the RFC receiver?
what is the infotype for time recording?
Regards
Arun

Hi,
Please refer to the following URLS
Time Data Recording and Administration
http://help.sap.com/saphelp_46c/helpdata/en/54/095fa972f911d1a910080009ab6b44/frameset.htm
Time Management Infotypes
http://help.sap.com/saphelp_46c/helpdata/en/8a/98579c46c411d189470000e829fbbd/frameset.htm
Personnel Time Events (HR PDC)
http://help.sap.com/saphelp_46c/helpdata/en/eb/486f69730711d1a910080009ab6b44/frameset.htm
Connection to External Time Management Systems
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PT-BFA/PT-BFA_ALE_168.pdf
Hope these help
Cheers
Manish

Problem in storing data in BAPI in File to RFC Scenario

Hi everyone,
I m doing File to RFC Scenario.......I completed design and configuration part and actived the Communication Channels.....
Now when I check in Runtime workbench I am getting succefully executed both at outbound and Inbound Channels.......but
data is not updated in BAPI...........
I m getting following error when I check in Component monitoring......
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: RfcAdapter: receiver channel has static errors: configuration exception caused by: com.sap.aii.af.rfc.core.config.RfcChannelInactiveException: channel has status inactive: com.sap.aii.af.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: configuration exception caused by: com.sap.aii.af.rfc.core.config.RfcChannelInactiveException: channel has status inactive
Please help me out.......
Regards,
Sudheer.

Hi
"I took Business Service as Service but not Business System.....Will it effect the scenario???......"
I suggest While dealing with the SAP Systems we should use Business systems.
Pls check the foolowing Threads for the above Query
RFC - Business Service
Re: business service for file to rfc
Regards
Abhijit

File to RFC problem in the RFC side

hello
the scenario is file to RFC. the file is loaded to the XI, and in the SXMB_MONI it is green. in RWB I recieve this error. any ideas?
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Y_XI_TEST_01 in remote system (RfcClient[ChannelRFCIn]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Y_XI_TEST_01 in remote system (RfcClient[ChannelRFCIn]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user

Hi Check the same discussion in
roblem with WS_DOWNLOAD
also see this blog
Remote Enable your RFC_HOST_TO_IP to return Host IP to JCo
Thanks!

Problem in file to RFC Asynch interface.

Similar Messages

Maybe you are looking for