File-to-file scenario: unable to trace cause of error

hi
i m new to Xi..
i have made a file -> XI -> file scenario, with a BPM having one receive and two send steps, sending message to two receiver-business-service.
the sender of the file is a sender-business-service, file adapter is using FTP.
the file is being picked up, but it is not put to the two destinations.
in SXMB_moni...i cant trace the error...
but in the respnse xml i cant see the payload...
pls tell me how to see where the error is.
pls help me....coz any scenario i make the main problem i face is to trace the error(file not being put to the destination directories),

hi sreeram and rajeev,
this is the trace from the response xml from the sxmb_moni enrty for the message send from the BPM to the final receiver-business-service through the send step(asynchronously).
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XIT</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2007-03-13T16:14:45Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 5922E409A745CA4BAE129D025CA22AE6</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XIT</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2007-03-13T16:14:45Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO60__0002</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XIT</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2007-03-13T16:14:48Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">No mapping required</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="1" type="T">system-ID = XIT</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2007-03-13T16:14:48Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

Similar Messages

When attempting to install Acrobat IX i get the following error "Error 1335" "pcw-cab-acr 11007" saying the file is corrupt. What causes this error and how do I fix it?

Has anyone else found this error?

I have found a temporary solution, allowing the previous version of iTunes (v. 11.1.3 (x64) in my case) to be re-installed. It will allow you to re-establish use of iTunes until the Apple software engineers fix the most recent disasterous upgrade (v. 11.1.4). Please see and follow the procedure in the following article:http://smallbusiness.chron.com/reverting-previous-version-itunes-32590.html The previous version works beautifully.

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

Idoc 2 File Scenario

Hi Experts,
I am doing Idoc to file scenario (bypass).
I got below error in sxmb_moni. Plz tell me what might be the proble?
<b>Unable to convert the sender service BS1_SENDER to an ALE logical system</b>

Hi Moorthy,
I am explaining my total scenari here.....
Its Bypass, Idoc to file.
I am sending idoc-xml as it is to receiver as file-xml.
I am not doing any IR objects.
I have configured ID (RD, ID & RA) objects.
I have used Idoc name(i.e Orders.Orders05) as Inbound & Outbound Interfaces.
But in SXMB_MONI, the error was showing as
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION"><b>NO_RECEIVER_CASE_ASYNC</b></SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack><b>No receiver could be determined</b></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please provide the solution.
Thanks in advance.

Error Resource not Found in SXMB_MONI while doing IDoc to File Scenario

Hi Experts,
I am doing IDoc to File Scenario and I am facing Following Error in SXMB_MONI,
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">RESOURCE_NOT_FOUND</SAP:Code>
<SAP:P1>193c0e01-bd37-11dd-850c-d879ac131b1f</SAP:P1>
<SAP:P2>http://clarityPOC</SAP:P2>
<SAP:P3>com/sap/xi/tf/_MM_Timesheets_iDocToFile_.class</SAP:P3>
<SAP:P4>-1</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Unable to find resource 193c0e01-bd37-11dd-850c-d879ac131b1f in the following software component versions: http://clarityPOCcom/sap/xi/tf/_MM_Timesheets_iDocToFile_.class-1</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have tested the same file in test tab of mapping, execution of mapping is successful there.
Regards,
Nitin Patil
Edited by: Nitin Patil on Dec 5, 2008 7:09 AM

Hi Dharmveer I have done the cache refresh ID in XI Data Cache Refresh using link
http://sapnbipoc:50000/rep/support/admin/index.html
but still same error persisting
and in Integration Builder> Environment>Cache Status Overview >Problem tab
following error (initial part of the error pasted) is shown
Thrown:
com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Adapter Engine af.npi.sapnbipoc not found in SLD
     at com.sap.aii.ib.server.abapcache.sld.AdapterEngineQueries.getAEUrl(AdapterEngineQueries.java:56)
     at com.sap.aii.ib.server.abapcache.sld.AdapterEngineQueries.getAEUrl(AdapterEngineQueries.java:41)
     at com.sap.aii.ib.server.abapcache.logons.IR_LogonData.<init>(IR_LogonData.java:26)
Regards,
Nitin Patil

CC error in RFC to File Scenario

Hi ,
While am trying to do end-to-end test for a RFC to file Scenario. Am getting this below error. Please help me to proceed further.
Could not process due to error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '2008-08-13' too long (>8 for 2. column) - must stop', probably configuration error in file adapter (XML parser error)'
Regards,
Hemanthika

Hi,
Please go through this Blog
RFC Scenario using BPM --Starter Kit
check this blog on how to configure sender rfc adapter.
The specified item was not found.
I hope it helps,
Regards,
Surya

RFC to multi file scenario

Hi,
I have to carry out a RFC to multi-file scenario. The requirement is that Error generating on whatever part XI will handle have to be reported. Is this possible in this scenario? What can be the mechanism?
I want to report these errors via a mail to an e-mail id.
Since i haven't done this scenario, i would appreciate if some link for carrying this out step-by-step is given.Also tell me what configuration for receiving RFC has to be done on XI and R/3.

Hi Arpit
<b>go through these blogs for the querry</b>
<b>For email alerts</b>
/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
You have to do SMTP Configuration for EMail and SMS.....
http://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/content.htm
Thanks !!

Reciver File channel unable to get message from Xi in file- file scenario

Hi All,
I have done a small File to File scenario.
Sender file adapter receiver the file and gives it to XI, then deletes the file from that directory.
Receiver is unable to get the file.
I have a message mapping defined for the receiver which concatenates two fields from one message type and transforms it to another.
I have configured the scenario.
When I check the adapter stats Sender channel picks the Xml deletes it from the directory.
<b>Sender channel:</b>
Sender Adapter v1014 for Party '', Service 'SourceFileBS':
Configured at 04:25:50 2006-06-03
Up and running: Last message processing started 05:10:50 2006-06-03
last poll interval started 05:10:50 2006-06-03
length 60,000 secs
<b>Receiver channel:</b>
Receiver Adapter v1027 for Party '', Service 'TargetFileBs':
Configured at 04:25:50 2006-06-03
Up and running - no message processing until now
I configured the scenario (receiver agreement, determination, sender agreement, and interface determination).
Instead of Business systems, I Configured Business services (Virtual) for inter company communication.
XI is unable to give the message to the receiver channel.
Please help me to debug the scenario.
Regards,
Meher

Hi All,
Thanks for all your Responses.
I see a high payload in my monitor belonging to some other process ( shipped with XI) MAT_LEGACY.
The scenario which I executed is showing up a status of <b>scheduled</b>
Adapter has picked the message at 01:59:37 2006-09-12
and start time and the end time of the message is shown as
01:59:37 2006-09-13 in the XI monitor with a status of scheduled .
can I purge the sceduled messages for MAT_LEGACY scenario?
if yes how do i do that?
is this causing a problem for the file not being received by receiver?
when i go to the transaction manager with SMQ1 with the client 100 i see the queue on which the above message is persisted with a queue status of ready.
help me.
Regards,
Meher

Unable to get filename from mail to XI to file scenario

Hi
How could i get the name of an attachment to be used as the file name on my File Adapter in a Mail to file scenario?
I recieve the files as attachments and I have used the payload swap bean to swap my actaull message content to attachment. That works perfect, the contents of the file are saved successfully on my file system. The file is sent as a plain text file and not xml and no mapping is done, I just get the files from the mail and save them into a file server for further processing.
Your help will be highly appreciated
Ronny

Hi
I have installed my Module, but when I try to call it from within the adapters I get an error
exception caught during processing mail message [614]com.sap.aii.af.mp.processor.ModuleProcessorException: Error during processing local bean: localejbs/mailAttachmentFileNames caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of mailAttachmentFileNames.
I have searched all the logs and the module is active. I even restarted my J2EE engine, twice but still nothing..
please assist
Ronny

Unable to do IDoc to File Scenario ; Please help me....

Hi Experts!!!,
I am trying to convert an IDoc to an .Txt or .Xml file, But I am un able to do it. Whenever I m trying to configure the Idoc adapter , it's not allowing me to select as "sender" (default it will be on the recvr side). Please help me in this regard.
Do I need to use RFC adapet, or BAPI instead of IDoc or any other way..to complete IDoc to File scenario...
THANKS IN ADVANCE!!!
Sunil K Shetty.

HI,
No need to use Sender Idoc adapter , default , IDoc adapter resides on Integration Engine. No sender communication channel and sender agreement also
see the below links
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
Idoc settings https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
Regards
Chilla

Unable to Test Idoc to File scenario

Hi All,
I am doing Idoc to file scenario.But dont know how to test this scenario.
I have done all the configuration in Backend and XIServer system.
Please help me out.
Thanks in Advance.
Regards,
Vikas

HI
Chech that these steps have been done
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.
One these are done
1) U can trigger the the IDOC by scheduled job in BD87 immediately after the document is saved in R/3
2) Using transactions like bd10 and bd12 u can trigger IDOC for master data
3) While creating the partner profile there is a option trigger immediately . By enabling this option the idoc gets triggered.
4) Using the transaction WE19 u can trigger the IDOC mannually
Regards
Santhosh

File to multiple files scenario

Hi there,
I will try to explain my scenario. I pick up a file with several lines and I need to create one output file per line
- <RECORD>
+ <LINE_ITEM>
+ <LINE_ITEM>
+ <LINE_ITEM>
-</RECORD>
I set up message mapping and interface mapping target to unbounded, and select RB_SPLIT in the interface determination. But i find the following issues:
In the sxmb_moni: Trace level="3" type="T">Message Type 1 Number of messages 1</Trace> (Only 1 message seems to be sent)
In the message monitoring:
Error Unable to find channel ID
Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: 016b52c0-09df-11dc-c431-0011258f8d14
And the status is waiting...
Any idea about how to complete my scenario?
Thanks in advance,
Paco.

Hi Francis,
You can try BPM to achieve this multi mapping.
Go to Integration Repository, SAP BASIS SWCV, namespace http://sap.com/xi/XI/Demo/Agency, Integration Process Name MultipleFlightBookingCoordination. Design an Integration process taking reference from the above and model your scenario accordingly.
Regards,
Amitabha

Encountering error in simple file 2 file scenario

Hi,
Working on a very simple file 2 file scenario , where input contains 1 header record identified with a key field and detail record conntains more than 1 records identified with key field. Used very specific FCC. But it was unable to generate the output file (a simple text file without any translation) giving errors as below -
1. File Adapter Receiver Channel cc_target: Not initialized - cannot proceed: null
2. MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Channel has not been correctly initialized and cannot process messages
3. Adapter Framework caught exception: Channel has not been correctly initialized and cannot process messages
4. Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Channel has not been correctly initialized and cannot process messages.
Input File structure is like
H1,XXXXX
D1,YYYYYY
D1,ZZZZZ
D1,NNNN
H1 and D1 are key identifiers of header and detail record
Need same format output file, used FCCs (1) fieldSeperator (2) endSeparator (3)ignoreRecordsetname (4) fieldNames (5) keyfieldvalue.
Can anyone pls suggest ?
AC

Hi ,
Use FCC Like this.
Doccument Name                        MT_Source( Your Source Message Type name)
Doccument Namespace                   http://xxxxxx(Your Message type Name space)
Recordset Structure                   Header,1,Detail,*
Key Field Name                        field1
Key Field Type                        String
Header.fieldSeparator            ','
Header.fieldNames                field1,field2
Header.keyFieldValue             'H1'
Header.endSeparator              'nl'
Detail.fieldSeparator            ','
Detail.fieldNames                field1,field2
Detail.keyFieldValue             'D1'
Detail.ignoreRecordsetname        true
Detail.endSeparator              'nl'
Let me know if you are getting any problem.
Thanks.

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!!!!

Flat File scenario-error

Hi All,
I am trying a Flat File 2 File Scenario ...
my input file is..
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:MTYP_name xmlns:ns0="File_File">Mustafa</ns0:MTYP_name>
I am just doing simple mapping of single field, but I am getting the following error..
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>internal server error: com.sap.aii.messaging.mo.MalformedMessageException: Cannot find Main Header in XMBMessage - check the message version</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><html> <head> <title>Transport Service Error</title> </head> <body> <h1>HTTP/1.0 500</h1> <h3>internal server error: com.sap.aii.messaging.mo.MalformedMessageException: Cannot find Main Header in XMBMessage - check the message version</h3> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 500 with the description internal server error: com.sap.aii.messaging.mo.MalformedMessageException: Cannot find Main Header in XMBMessage - check the message version XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What is the cause of this error and also how do I change the trace logging levels?
regards,
Mustafa

Hi Raj,
Iam sending the Inbound payload
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_DB2_S_FF xmlns:ns="http://gsll.com/DB2">
- <RSETSTRUCT>
<S1>A</S1>
<S2>A</S2>
<S3>A</S3>
</RSETSTRUCT>
- <RSETSTRUCT>
<S1>B</S1>
<S2>B</S2>
<S3>B</S3>
</RSETSTRUCT>
</ns:MT_DB2_S_FF>
regads,
Jeevan

File-to-file scenario: unable to trace cause of error

Similar Messages

Maybe you are looking for