Skip to Content
author's profile photo Former Member
Former Member

Problem in File to IDOC Scenario

Hi,

I am trying to test the demo example for Flight Booking using the "File Sender to IDoc" Scenario. I have done all the settings. As a last step after I copy the file in
[XI-hostname]\sapmnt\trans\tmp\fileadapter\group[XX] as per the Demo example guide and activate the changes for File_Sender communication channel, no action is triggered.

The file remains in the directory. When I want to see if my adapter is fine and I check the Adapter Lists in the Adapter Monitoring, it shows only JPR Adapter and that too in RED.

Then I check the tracefiles and find this error.

Date : 04/05/2006

Time : 16:44:52:264

Category : /Applications/ExchangeInfrastructure/Directory

Message ID : 00B0D03E9B4F005A0000000D000001F4000410AB0985C603

Severity : Error

Location : XIDIR.com.sap.aii.ibdir.server.abapcache.ErrorHandler

Source Name : /Applications/ExchangeInfrastructure/Directory

Thread : SAPEngine_Application_Thread[impl:3]_3

Message : Failure at Cache-Refresh data consumption !!!

<?xml version="1.0" encoding="UTF-8"?>

<CacheRefreshError>

<EngineType>AE</EngineType>

<EngineName>af.aba.singdemo1</EngineName>

<RefreshMode>C</RefreshMode>

<Channel>

<PartyName></PartyName>

<ServiceName>XI_LEGACY_BS_00</ServiceName>

<ChannelName>File_Sender</ChannelName>

<ChannelObjectId>838401f3335236bbadd7086c6711b070</ChannelObjectId>

<ChannelError>

<Message>

Could not parse Channel 'File_Sender'(ObjectId: 838401f3335236bbadd7086c6711b070) AdapterType: File|http://sap.com/xi/XI/System|3b787a8035c111d6bbe0efe50a1145a5:

</Message>

<Trace>

com.sap.aii.af.service.cpa.CPAException: Schema not available for File|3b787a8035c111d6bbe0efe50a1145a5|http://sap.com/xi/XI/System.

at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.endElement(DirectoryDataSAXHandler.java:262)

at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:154)

at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1826)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1722)

at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2298)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1719)

at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2701)

at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:126)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:136)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:209)

at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:270)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:331)

at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)

at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:54)

at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:713)

at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:595)

at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:440)

at com.sap.engine.frame.core.thread.Task.run(Task.java:60)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)

</Trace>

</ChannelError>

</Channel>

</CacheRefreshError>

Datasource : 48696150:E:\usr\sap\ABA\DVEBMGS04\j2ee\cluster\server0\log\applications.log

Application : sap.com/com.sap.xi.directory

Argument Objs :

Arguments :

Dsr Component : singdemo1_ABA_48696150

Dsr Transaction : 72d10590c48011da8a7100b0d03e9b4f

Dsr User : Guest

Indent : 0

Level : 0

Message Code :

Message Type : 0

Relatives : XIDIR.com.sap.aii.ibdir.server.abapcache.ErrorHandler

Resource Bundlename :

Session : 3816

Source : /Applications/ExchangeInfrastructure/Directory

ThreadObject : SAPEngine_Application_Thread[impl:3]_3

Transaction : SAP J2EE Engine JTA Transaction : [2ffffffe7b5600a31]

User : XIAFUSER

Any help will be great.

Regards,

Shubham

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Apr 05, 2006 at 09:36 AM

    Hi Shubham,

    Update the CAPCache, through http://<host>:<port>/CPACache/refresh?mode=full, which will refresh the Adapter Cache. Then you can monitor all the Adapters, not only JPR.

    Regards, Sreeni.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 05, 2006 at 09:29 AM

    Hi Shubham,

    Go to transaction SXI_CACHE on your XI box and manually refresh the cache.

    Cheers

    Manish

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 25, 2008 at 04:20 PM

    Closing as was unable to solve.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.