File-Xi-File scenario donu00B4t work.

Hi!!
We have a poblem with a FILE-XI-FILE scenario via NFS. We have a Flat File in a Xi directory (AL11) . The first process work correctly. The file is deleted from this directory and mapped to a XML file into Xi. SXMB_MONI shows the message is correctly (green flag). But i can´t generate a Receiver file. We want to create a new file in /tmp directory of Xi. For do this one , we have a Communication Channel type File, with NFS option.
Someone can help me?¿
Thanks for all.

Hi! vishal!
Thanks for your fast reponse!
Adapters are configured correctly. I throw a test in Integration Builder and encountered a fatal error in step interfase determination & mapping.
"Runtime error
During the application mapping com/sap/xi/tf/_FILE_TO_FILE_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: Fatal Error: com.sap.engine.lib.xml.parser.Parser~"
The trace saids.
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace> <Trace level="2" type="T">......attachment XI_Context not found </Trace> <Trace level="3" type="T">Das Mapping wurde bereits in der Interface-Ermittlung bestimmt. </Trace> <Trace level="3" type="T">Object ID of Interface Mapping E5F0ADEF913F39CF82BC520FEBF6072A </Trace> <Trace level="3" type="T">Version ID of Interface Mapping FBF0D0004FBC11DABCBBE9C10A1F030C </Trace> <Trace level="1" type="T">Interface Mapping http://gencat.net/ics/xi/facturacio FILEINPUT_TO_FILEOUTPUT_INTERFACE </Trace> <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_FILE_TO_FILE_ </Trace> <Trace level="3" type="T">Dynamic configuration is empty </Trace> <Trace level="2" type="T">Mode 0 </Trace> <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_FILE_TO_FILE_. </Trace> <Trace level="3" type="T">Load fbf0d000-4fbc-11da-bcbb-e9c10a1f030c, http://gencat.net/ics/xi/facturacio, -1, com/sap/xi/tf/_FILE_TO_FILE_.class. </Trace> <Trace level="3" type="T">Search com/sap/xi/tf/_FILE_TO_FILE_.class (http://gencat.net/ics/xi/facturacio, -1) in swcv fbf0d000-4fbc-11da-bcbb-e9c10a1f030c. </Trace> <Trace level="3" type="T">Loaded class com.sap.xi.tf._FILE_TO_FILE_ </Trace> <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._FILE_TO_FILE_ </Trace> <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_FILE_TO_FILE_ </Trace> <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:66) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:77) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy32.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:130) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7)(:main:, row=1, col=7) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 3 more </Trace> <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_FILE_TO_FILE_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) </Trace> <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_FILE_TO_FILE_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy32.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:66) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:77) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy32.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:130) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7)(:main:, row=1, col=7) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 3 more </Trace> <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
Best regards....Help!!!!

Similar Messages

File-to-File Scenario Stopped Working

I have a file-to-file scenario that was working fine until recently. The logs show that the inbound (file to XI) part is successful. There are no logs for the outbound part. It is almost like the input file just goes to no-mans-land. I had printscreens of all of the Integration Builder settings and they are still the same. I cleared cache with SXI_CACHE. Any other suggestions?

Hi Ahmad,
Thanks for the response but my problem is still not solvedI am able to see all the XBTI* queue and unlock XBTI003 after that I processed the file again and it went into SYSFAIL state. Do I need to restart the server? Also , what is reason behind queue getting stopped? Is it due to running any faulty scenario?
Is it right that only one XBTI* queue will be active at any point of time bcos if I try to release the lock of any other XBTI queue then XBTI0003 goes into SYSFAIL state. Is there any document for understanding the queue usage in SAP XI context?
Thanks
Sanjeev Sinha

Idoc to file Scenario not working

Hi ALL,
I have created one Idoc -XI-File scenario.I have done all the preconfiguartion in Backend and XI.
Now when i am testing in we19, it is showing that Idoc is sent and saved in the database but when i am going to sm58, there it is showing Status field "No service for system SAPSAI, client 800 in Integration directory
Can anybody tell where i am going wrong???
Thanks in Advance
Regards
Vikas

Hi,
Now i am able to see the message in sxmb_moni , it is showing Green status, but still am not getting the file in reciever side.
In communication channel monitoring it is showing green status,but not giving any messages theres
Any suggestions what do to next to get the file??
Thanks
Regards
Vikas
Message was edited by:
Vikas Agarwal

Simple File to File scenario not working

Hi all,
I am new XI, please help me out, I am getting this error when i am monitoring the message
2006-02-08 17:59:09 Success Channel DEMO_CC_S: Send binary file "D:\Input\nagesh_input.txt". Size 190 with QoS EO
2006-02-08 17:59:09 Success Application attempting to send an XI message asynchronously using connection AFW.
2006-02-08 17:59:09 Success Trying to put the message into the send queue.
2006-02-08 17:59:09 Success Message successfully put into the queue.
2006-02-08 17:59:09 Success The application sent the message asynchronously using connection AFW. Returning to application.
2006-02-08 17:59:09 Success File "D:\Input\nagesh_input.txt" deleted after processing
2006-02-08 17:59:09 Success The message was successfully retrieved from the send queue.
2006-02-08 17:59:09 Success The message status set to DLNG.
2006-02-08 17:59:09 Error Transmitting the message to endpoint http:
sapnet:8000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 501..
2006-02-08 17:59:09 Success The asynchronous message was successfully scheduled to be delivered at Wed Feb 08 18:04:09 IST 2006.

Hi Nagesh,
this thread is the solution to your problem.
No Adapters showing in Adapter Monitor
go thro this thread also
XI Installation : No adaters(except JPR) visible in Adapter framework
as given in the above threads to import take a look at:
Importing the XI Content for Software Component Version SAP Basis 6.40 SR1 from
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/sap xi 3.0 sr1 installation guide.pdf
think these links has full info to solve your problem.
regards,
P.Venkat
Message was edited by: venkataramanan

Error Handling on RFC - XI - File Scenario

I have an R/3 RFC -> XI -> FILE scenario that works, but does not adequately handle the error of my R/3 to XI connection being down.
The RFC call is async since I was under the impression that I had to do a "to file" scenario that way.
    CALL FUNCTION 'ZXO_SAP2RFC'
      IN BACKGROUND TASK
      DESTINATION wa-rfc_dest_1
      EXPORTING
        request          = request
        rfc_header       = rfc_header.
    COMMIT WORK AND WAIT.
    IF sy-subrc <> 0.
      [error handling]
If my rfc destination is down (for example when XI is down), this RFC call is still getting a sy-subrc of '0' (so my error handling does not kick in).
Any suggestions?

Hi Keith,
your scenario is working correctly. If XI is down you will find your message queued in transaction SM58, where you can restart it manually. Usually there should be standard job for report RSARFCEX, which is periodicly trieing to restard the message.
Asynchr Call (tRFC) means that your program continues completly undependent from that call.
Make a test: Change temporary the called machine in SM59 destination to senseless value and execute your programm. Your message should be in SM58. Then correct the destination and wait a few minutes...
Regards,
Udo

File - File Scenario - Mapping exception ( due to no of records ? )

I have a file to file scenario which works fine when the no of records in the file is less (say 2000 ).
Today it failed with the below given error, and that case the file had more than 19000 records.
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_msgIF_Independent_ERP_MainFraim_: Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:Stack>
Can anyone please advice?
Mathews

Hi Mathews,
It is the file size that would matter . check the note 821267 to find some help.
Raghu

File to File scenario is not working

Hi
I have done simple file to file scenario. I have done all the necessary cofigurations but XI is not picking the file
I have checked in adapter monitoring its saying "File Adapter monitoring is now part of Channel Communication" its not showing any color not in green or not in red its just in default color.
I have cheked in Channel Communication its status is green and log is "Communication Channel is correctly configured and started"
Following are the processing details displayed in Channel Communication
Polling interval started. Length: 5.0 seconds
3/17/08 11:36:19 AM   Processing finished successfully
3/17/08 11:36:19 AM   Processing started
3/17/08 11:36:14 AM   Polling interval started. Length: 5.0 seconds
3/17/08 11:36:14 AM   Processing finished successfully
3/17/08 11:36:14 AM   Processing started
3/17/08 11:36:09 AM   Polling interval started. Length: 5.0 seconds
3/17/08 11:36:09 AM   Processing finished successfully
I Didnt get any messages in Message Monitor and SXMB_MONI.
I checked in default trace and i got following errors
User J2EE_GUEST, IP address
HTTP request processing failed. HTTP error [401] will be returned. The error is [No login module succeeded.No details available].
*Message listener localejbs/TestListener could not be created for connection test after 60 attempts.
Exception getting currently running XMLForm Module version.
java.lang.IllegalStateException: No transaction
at com.adobe.service.J2EEConnectionFactoryManagerPeerImpl.getConnection(J2EEConnectionFactoryManagerPeerImpl.java:70)... [see
Cannot get the name of the EJBean for [email protected]893074.
The error is: java.lang.NullPointerException: null
Exception id: [00114326E0D9004E000005860000072F000448999A01A892
Assertion failed: Logging severity level is not set to 'None'
Assertion failed: Logging severity level is not set to 'None'
Could you please tell me do i need to any other configurations
Regards
Sowmya

Hi
I checked for XIAPPLUSER role in SU01 but it is not there?
What the role of XIAPPLUSER ?
Why do i need this role?
Here we have installed XI in solaries system so i asked my basis team to share one folder in XI system with full access.
First have given transport protocol as the Fil System, at that time communication Channel was in green but i got the above errors which i have mentioned earlier...
My question is can i give the transport protocol as File System because i am accessing the folder with in the XI server but i am accessing it through FTP.
Now i have configured the FTP I have configured everything correct but still i am getting the following errors...
An error occurred while connecting to the FTP server '10.30.3.23:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 530 Login incorrect.'. For details, contact your FTP server vendor
Could you please help me in this?
Regards
Sowmya

Mapping when working with file to file Scenario as Attachment

HI ALL,
I have a file to file scenario and we are sending 3 files in a single message using the file attachment .(Using additional files option option in file adapter)
My issue now is can we do mapping tor this file send using this option like fileA will have one mapping logic and FileB also will the same mapping logic ...?
Thanks
Souz

Yeah, requirements are still not very clear.
If what you meant was have a multimapping fromt he main payload + 2 attachments to a single destination file, it's possible to handle attachments in Java mappings if you're on PI 7.1+ and extend the new Java Mapping class (AbstractTransformation) instead of implementing the StreamTransformation interface.
Details here:
http://help.sap.com/saphelp_nwpi711/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/frameset.htm
Best regards,
Henrique.

IDOC-XI-FILE Scenario: Error in ABAP Mapping

Dear All,
I am working on IDOC-XI-Flat FIle scenario in which I am using ABAP Mapping as per document "How To Convert an IDoc-XML
structure to a flat file and vice versa in XI 3.0".
I created one customized Idoc for this. The Idoc is reacing XI but its flat file is not getting created. Its giving me following error:
<SAP:Stack>Error in mapping program Z_ABAP_MAPPING_PACKING_LIST (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
I have also gone thru threads posted for the same topic earlier but still I am not been to resolve this error.
Please help me out in resolving this error.
Regards,
N.Jain

HI,
   Log saying that, u have problem in the mapping program.
i.e Z_ABAP_MAPPING_PACKING_LIST
   the problem is due declaration of data.
   i hope that, you have some methods.
   those are declared under intialization section in mapping program.
please use start of selection before the method.
other wise, it will come under intilization section.
warm regards
mahesh.

How to use a existing Business Service in IDoc-File Scenario

Hi Experts,
I am new to XI.
I am working on a IDoc to File scenario where in i am importing the CREMAS.CREMAS03 IDoc from the R/3 System.
When i try to create a Business Service in Configuration Scenario Object in Integartion Directory, i get a message saying "SAP system ID ER1 and client 800 already exist in service | CLNT800ER1".
Can i reuse this Business Servie in my Configuration Object?
If yes, can you please guide me How to go about it?
Thanks for the effort.
Cheers
Gaurav Raghav

U may directly use it.
Just select the business service wherever required. It is not necessary that the Business Service is present in ur configuration scenario. But if u still want it, u may add it using "Add to Scenario" option from other configuration scenario or from Objects tab
Regards,
Prateek

Integration server as logical system in IDoc to file scenario

Hi,
Will we configure integration server as logical system in IDoc to file scenario or the RFC destination related to the port will be suffice?
For which logical system will the outbound partner profile configured?
Regards,
Gajendra.

Hello,
I feel that the RFC destination linked to the port is the key here.
Because the scenario (IDoc to File) works in both the cases:
Case 1: Used the logical system as Integration server
Case 2: Used the logical system related to the file (third party) in the SLD.
In both the above cases the RFC destination points to the integration server.
Is this the case that in the XI scenarios (where IDoc are sent) the logical system name in the partner profile is just dummy and has not much significance??
It is the port that matters and once the Idoc reaches XI the routing takes place based on the configuration in ID.
Thanks.
Regards,
Gajendra.

File to File scenario

Hi,
I have a problem in file to file scenario in which the file is not getting transferred from source to target.
Source communication channel - Transport protocol - NFS | Process mode : Delete | The file is picked but not able to delete from the directory.
Error: File: d:\test\file.txt deleting after processing failed - retry
The file is not transferred to target is it because of this CC is not able to delete the file. Does windows also have any authorization issue if so how should one check the authorization. I have the admin access of my system.
Thanks.

Hi,
Firstly, Since the scenario works perfectly while using Test mode, so all your design & configuration are OK.
Now, there can be Two reasons why PI is not able to delete the file and process it (during Delete Mode):
(The Problem will persists if you use Archive Mode also)
Prob 1. The directory is write protected or read only
Prob 2. The file is write protected or read only
Solution:
If Unix System
Soln for Prob 1. - go to the directory structure
for ex: if directory where file is kept is /staging/Interface/PI/Test/inbox/
then go to /staging/Interface/PI/Test/ and give command ls -lrt
It will show the directory names with permisions.
use chmod 777 inbox and the permissions willl be changed ( drwxrwxrwx )
Soln for Prob 2. - Get inside /staging/Interface/PI/Test/inbox/ and give command ls -lrt
if the file does not have authorizations as (-rwxrwxrwx) give chmod 777 <filename> and then give command touch <filename>
If Windows System
Soln for Prob 1. - Goto the directoty and right click on the folder and deselect the Read Only Checkbox.
Soln for Prob 2. - Right Click on the file and deselect the Read Only Checkbox
Try again and the scenario will work surely. Let me know if any issues.
Regards,
Souvik
Edited by: Souvik Chatterjee on Mar 14, 2011 8:14 AM

Testing HTTP to File scenario

Hey guys
i m testing a HTTP to file scenario for one of our clients and the test seems to be working fine when i test it in RWB under Integration Engine,MONI is chequered as well as i m getting the file on receiver side too.
but when i test it by making use of the HTTP client which i got from the followin link
/message/266750#266750 [original link is broken]
it gives and error saying http-status 404 not found.
the URL which is getting created is
http://scosap005.sap.com:50100/sap/xi/adapter_plain?namespace=urn%3ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=&sap-password=&sap-client=100&sap-language=EN
is this the same URL our client is gonna use to post the message to our XI server?
also why am i getting error in the second testing?
thanx
ahmad

Hi,
1) Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine ? Double click on service and check whether you have entered correct information.
2)Access the trace file and search for traces with severity ERROR, WARNING or stack traces.
If we do not find an error in the log file or the error message does not explain the problem sufficiently, access the default Trace. The default trace file contains detailed messages for developers. Extract the relevant trace information e.g. using the time stamp or the message ID.
If this does not explain the problem in more detail, increase the trace level and reproduce the problem. Then restart message processing using the message display tool. Mark the message and select repeat.
3)Check the Note-803145
4) 404 is an HTTP response code that indicates that the resource in question could not be found. Usually this is due to an incorrect URL check all URLs.
Regards
Agasthuri Doss

HTTP to File Scenario using URL parameters.

Hi,
I am working on a HTTP to file scenario where POST method is hirring the XI server with authentication parameters.
CAD application is trying to hot our XI server using POST Method and the application does not have ability to send XML payload to XI server directly.
So we are simply receiving parameters in plain text in inbound payload.
I need to convert this payload to XML format and am tring to work this out using dynamic configuration.
But It is throwing parser error.
BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 73, 75, 62(:main:, row:1, col:3) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:770)
Here I have to use HTTP sender adapter.
Please suggest how can I acheive this.??
Regards,
Sachi

Hi Mark and Maciej,
The Inbpound payload we are reciving is of the kind:
sap-user=<UserID>&sap-password=<Pwd>&Param1=Sachi&submit=submit
As in HTML we ar using hidden parameters to given authentication details and submmit button to hit XI serrver.
Can you please help me to out how can I add prolog and epilog.
How can I change my payload to XML format.
Regards,
Sachi

Error in HTTP to file scenario

Hey guys
we have a HTTP to file scenario in which our client has to send the Invoices over HTTP in XML format,when we test the scenario from within our landscape we are getting the output file correctly but when we test from the client site,we get an error message saying that the file has missing semi colon (,the URL which we are getting from the local HTTP client is something like this
http://scosap005.sap.com:8001/sap/xi/adapter_plain?namespace=urn%3ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=&sap-password=&sap-client=100&sap-language=EN
and the one which we are getting from the client is
http://xx.xxx.xx.xx:8001/sap/xi/adapter_plain?namespace=urn%3ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=&sap-password=&sap-client=100&sap-language=EN
why am i getting this error?
thanx
ahmad

Hey guys
i m having a very strange problem with my scenario,we are doing a HTTP to file scenario,now as both the sender and receiver have same structure i havent done any mapping,client is sending XML over HTTP from another location which is not in our landscape,he is using web methods Business connector .when he send us the XML message to our XI server some stuffs are added at the top of the payload,its something like this
namespace=urn%253ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=nov_test&sap-password=xi_test&sap-client=100&sap-language=EN&
these are actually the parameters which are used in the URL to send the XML to us.but because of this i m unable to process the XML .
so my XML looks something like this
namespace=urn%253ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=nov_test&sap-password=xi_test&sap-client=100&sap-language=EN&
<?xml version="1.0" encoding="UTF-8"?>
<Invoice transactionPurposeIndicator="Original">
     <InvoiceProperties>
          <InvoiceNumber>0094372098</InvoiceNumber>
          <InvoiceDate>20070319</InvoiceDate>
          <VendorNumber>VENDOR #</VendorNumber>
but when i try this scenario from within our landscape it works fine and nothing is added on top of XML.
they are sayin that nothin extra is being added from thr side and their XML does not have the extra addition on top.
how should i solve dis problem?
its urgent
thanx
ahmad

File-Xi-File scenario donu00B4t work.

Similar Messages

Maybe you are looking for