File adapter problem - message in RWB HOLDING msg status

Problem in XI File adapter recver comm channel.Getting msg in RWB Adapter Engine HOLDING status.
1. No explaination in RWB Details tab, of why status Holding.
2. File does not get created, because of Holding status.
3. Cannot Resend or Cancel in RWB the message.
Sometimes the msg goes through and other times does not and is stuck.
File Adapter Parms set as:
Connection Mode: Per File Transfer
Transfer Mode: Text
File Adapter setting Max concurrency = 1 would that have anything to do with it?
File Construction Mode:Create
Put Name: Direct
Empty msg-handling: Write Empty File
Type: Text
Any ideas Why holding? and Where to see more details.

Hey
exact same issue has been discussed today on SDN.anyways have a look at the following blog
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
Thanx
Aamir

Similar Messages

Sender File Adapter: No Messages

Hi,
I have configured a sender file adapter to read a flat file using file format conversion, in the file poler mode using NFS. I could confirm that the File is being read, and the adapter status from the Adapter framework (is:port/AdapterFramework) indicates the adapter is working fine (Green light, and last message processed at XXX........).
However, I did not find any messages from SXMB_MONI.
Further, I got inot the RWB, and found the following Audit log:
It indicates an error "Transmitting the message to endpoint http://kansbwul01:50000/sap/xi/engine/entry?action=execute using connection AFW failed, due to: Received HTTP response code 404.."
What is the problem, and how can I resolve it?
Thanks
Feroz
Success     Channel CDWFileReader: Entire file content converted to XML format
Success     Send text file "/tmp/XIDemo/3315-TL-20041126-0000IN.txt", size 164533, character encoding ISO8859-1 with QoS EO
Success     Application attempting to send an XI message asynchronously using connection AFW.
Success     Trying to put the message into the send queue.
Success     Message successfully put into the queue.
Success     The application sent the message asynchronously using connection AFW. Returning to application.
Success     Confirmation mode test found. File will be resent next time
Success     The message was successfully retrieved from the send queue.
Success     The message status set to DLNG.
Error     Transmitting the message to endpoint http://kansbwul01:50000/sap/xi/engine/entry?action=execute using connection AFW failed, due to: Received HTTP response code 404..
Success     The asynchronous message was successfully scheduled to be delivered at Sun Jan 09 19:13:21 CST 2005.
Success     The message status set to WAIT.

Hi,
Further to my earlier post, the following is the message log from the message monitor. Any clues whats going wrong. Can I configure a File Sender->File Receiver scenario?
Where and how are the port settings and user credentials configured for the AFW.
-Feroz
Message ID f49f6d21-632c-11d9-805a-0003ba54d619
RefToMsg ID
Conversation ID
Sequence Number 0
Message Type Asynchronously Sent Message (SEND)
From Party
From Service   Name: LB1_CDWFilePoler
To Party
To Service   Name: LB1_CDWFileWriter
Action   Namespace: http://erc.ge.com/cdw/poc Name: ReadFile
Connection Name   AFW
Status   Not Delivered
Profile   XI
Transport   HTTP
Delivery Semantics   Exactly Once
Times Failed   4
Number of Retries   3
Sent / Received 01/10/2005 12:42:33
Transmitted / Delivered 01/10/2005 12:57:33
Next Delivery 01/10/2005 12:57:33
Persist Until 02/09/2005 12:42:33
Valid Until
Retry Interval   5 Minutes
Address   http://kansbwul01:50000/sap/xi/engine/entry?action=execute
Credential   SAPPasswordCredential(XIAFUSER):password=********:sapclient=100:saplang=
Transport Headers   SOAPAction="http://sap.com/xi/XI/Message/30" Content-Type=Multipart/Related; boundary=SAP_63fa9d21-6337-11d9-8f3c-0003ba54d619_END; type="text/xml"; start="" HTTP=POST
Node ID   1485750

File adapter problem - xml file

Is there a way to define in the sender file adapter the document name for a XML file?
This is the xml file that arrives to XI,
<?xml version="1.0" encoding="UTF-8" ?>
<dataroot generated="">
<Materials1>
<CODE>FAMILY</CODE>
<TYPE>A75</TYPE>
<NAME_EN>LUBRICANT</NAME_EN>
<NAME_ES>LUBRICANTES</NAME_ES>
<NAME_DE>LUBRICANT_GERMAN</NAME_DE>
</Materials1>
</dataroot>
I have to define the name of the Message Type as "dataroot" in order to avoid problems at mapping time. The problem is that I get from MDM the same structure begin each time,
<dataroot generated="">
Is there a way to define the XML Document Name in the Sender File Adapter?

Hello Rob,
FOr ""dataroot" element "generated" is the attribute.... define this attbute in the datatype as well..
Thanks,
Himadri

File Adapter Problem

Hi All,
we are having a simple scenario we have to use sender file adapter .
Our file is Simple Text File where one line is one reocrd . Do i need to do content conversion ? we don't have Header line item relation ship.Each flat file line should be a XML message. Now my problem is while configuring content Conversion parameter we have to pass structure in format of header and line item only is there any other way ?
Thanks & Regards,
Tuhin

No you do not have to pass Header and Line item records in the flat file.
Just use <documentName>.fieldFixedLength=1,2,3,4...
and it should work.
Thanks
Ashish

File Adapter problem for Fixed Length output file

Hi There!,
The following is my sample data format
ABCD 2345 03Accounting Swissland
ABCD 011234 1000Jack Gates 400000 03
ABCD 021234 1001Bill Welch 400000 03
In the first record has dept details:
DummyText, Row identifier(not given in case of dept), Identifier, Deptno, Deptname, Location
The second and third records are emp details:
DummyText,Row identifier, Identifier,EmptNo,Emp Name, Manager, Salary, Deptno.
Notice that the primary key is defined by the first three columns DummyText, Row identifier, Identifier.
When I use Native Format Builder from File Adapter and scan the first three columns I get all three records (i.e dept and both employees). I deleted the second employee and proceeded to finish the configuration. But, the problem I face is that the key value shows as "ABCD% 011234" for both the employee records where as I would like it to show as "ABCD 011234" for the first record and "ABCD 021234" for the second record.
How do I get around this problem?
Moreover if I have a group or recurring records and not just one record recurring. I mean assuming I have the following:
First row: Department
Second row: Employee
Thrid row: Manager
Fourth row: Employee
Fifth row: Manager
How do I get this done?
Does anyone have an idea where to find details of nxsd.
Thanks in Advance.

Hi Manoj
Give the FCC parameter as
RecordSet Structure = Header,,Detaillnes,,Detaillines2,*
Header.endSeparator = 'nl'
Header.fieldFixedLengths = field length
Header.fieldFixedLengthType = char/byte
Header.fieldNames = field1,field2,field3,.....
Header.keyFieldValue = Header
Detaillnes.endSeparator = 'nl'
Detaillnes.fieldFixedLengths = field length
Detaillnes.fieldFixedLengthType = char/byte
Detaillnes.fieldNames = field1,field2,field3,.....
Detaillnes.keyFieldValue = Detaillnes
Detaillines2.endSeparator = 'nl'
Detaillines2.fieldFixedLengths = field length
Detaillines2.fieldFixedLengthType = char/byte
Detaillines2.fieldNames = field1,field2,field3,.....
Detaillines2.keyFieldValue = Detaillines2
The keyFieldValue should be the Value which identifies your record either as Header/Detaillines/Detaillnes2.
Regards
Santhosh
Message was edited by:
Santhosh Kumar V

File adapter specific message attributes

Hi,
If we check ASMA of file adapter ......all the information corresponding to that attributes will be available in the SOAP header. If we check ASMA in the receiver file adapter then receiver file adapter will pick those values from the SOAP header and will assign to the target file.
Even we can directly set the target file name by accessing the system parameters through UDF.
please correct me if my understanding is wrong.
thanks
kumar

Hi Kumar,
If we check ASMA of file adapter ......all the information corresponding to that attributes will be available in the SOAP header
Every adapter has a defined set of attributes, which are described individually as part of the configuration for each of the adapters. So these attributes would be visible. And better to call it Message Header instead of SOAP header.
If we check ASMA in the receiver file adapter then receiver file adapter will pick those values from the SOAP header and will assign to the target file.
Yes, if mapping of these attributes are done.
Even we can directly set the target file name by accessing the system parameters through UDF.
Yes
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70c89607-e4d9-2910-7280-f6746e964516
[Reward points if helpful]
Regards,
Prateek

Sender File Adapter Problem when text document is a single line.

Hi All,
I have posted this question earlier too. But did not get a proper answer.
I am using File adapter to fetch data from a file system.
My input data is: AA123BB45678AA345BB78564.
It is just reading the first segment i.e.AA123 and not reading the remaining.
How can I configure my Sender File adapter to pick this pattern of data? It works fine if I have line break after each record that is if the input is as below.
AA123
BB45678
AA345
BB78564
In the above there is a Line break after each segment. So File adapter picks it fine.
I have also tried using xml.A.endSeparator equals to blank in the module configuration. But it does not work either.
Can anyone throw some light to this?

Abhi
I tried a different approach to send your file data In..
You can get each line in the source structure in separate row as
<?xml version="1.0" encoding="utf-8" ?>
- <ns:SingleRowDT xmlns:ns="http://xxxxx.com/xi/pocs/sriram">
- <Recordset>
- <row>
<rowElt>AA123BB45678AA345BB78564</rowElt>
</row>
- <row>
<rowElt>AA123BB45678AA345BB78564AA123BB45678AA345BB78564</rowElt>
</row>
- <row>
<rowElt>AA123BB45678AA345BB78564AA123BB45678AA345BB78564AA123BB45678AA345BB78564</rowElt>
</row>
</Recordset>
Now you can use a suitable mapping logic to split the individual records into the 2 field structure as expected in the target..
Trying your way would be a limitation on file adapter I think..Let me know if this helps..I can give you the content conversion config for this model..
its simply
RecordSet - Leave it empty
RecordSet Seq - Row, *
Recordsets/msg - *
row.fieldSeparator - 'nl'
row.endSeparator - 'nl'
row.fieldNames - 'rowElt
..So each line will be pulled into a single Row in the source structure and then u can apply a specific mapping to split into 2 fields for your target
Regards
Sriram V.
Regards
Sriram V.

Sender file Adapter, problem with proxy authentication

HI all,
i'm having some problems with the following scenario, i need to configure a sender file adapter which connects to a FTP server. To connect this FTP server i need to set a proxy (and so a username and a password), and i don't know how to do.
From note 821267 seems that the proxy is not supported for an FTP adapter, but the are some workaround like the ones described in the following link
Re: Proxy server inFTP adapter
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=57137
They don't work in my case as i need to se two username (the one for proxy and the one for the ftp server) and i cannot force the proxy use for all XI applications.
Can anyone help me?
Thanks a lot
Aldo

Proxy is necessary to exit the customer local intranet. It's not possible to go outside network without going through the proxy server.
I cannot set the proxy server in file adapter as it's not supported like described in SAp note, a possible workarounf is to force the proxy server in the J2ee stack but in this way all PI calls would use that proxy..

Inbound File Adapter problem

Can someone tell me why my message is not processed by XI. I use a File Adapter. The File Adapter is "active" with the following configuration.
Adapter type = File
transport protocal = Filesystem
message protocol = File
adapter engine = integration server
Source directory = "e:/XIprocessFiles"
File name = *.xml
File type = text

Edward,
What do you exactly meant with not processed? Is the file adapter not processing/sending your xml file to the XI system? Or
is your interface defined in XI not doing anything with the input message?
Assuming your situation is the first one; Then you should start by checking the source file name, source directory name, contentType (you have text, this should be text/xml), ContentKind (this should be T) and PollingInterval...
In the second situation you should then look at adapter config settings like: namespace, sender interface name, sender business name etc...
Cheers,
Rob

File Adapter-Problem Reading Huge Files

Hi,
Here is the issue that i am facing
When reading huge file(csv file upto 6MB-8MB) the communication channel configured as File Adapter with a polling interval of 7 min(420 sec) is inconsistent in reading the complete file.Sometimes it reads the the complete file of 6 MB and sometimes it reads a part of the file say 3MB/6MB.Can this inconsistent behaviour be resolved.??
Your suggestions highly appreciated.
Regards
Pradeep

Hi Pradeep !
8mb is not a huge file for XI, I think it is a small one. Maybe your problem is not the size..please check if XI is not starting to read the file before it is completely written to the source folder. If you are creating that csv file from another application directly to the poll source directory of the XI scenario specified in the file adapter, and your poll interval is small, XI could start reading the file while you are still writing it. If this is the case, try to put the file with a different extension or filename than the specified in file adapter comm channel and when the file is completely written, rename it to its final filename and check if you are still having that misbehavior.
You can write the file to a temp directory and the move it to the XI directory once finished.
Regards,
Matias.

XI 3.0 PROXY/ File adapter problem

We have XI 3.0. We used the proxy to send a file from R3 to XI and used file adapter in XI to put the file back to R3 file server.
From the SXMB_MONI in R3, the message was successfully sent from R3 to XI.
From the SXMB_MONI in XI, the URL address https://aaaa###.com:52201/MessagingSystem/receive/AFW/XI (the SAI_AE_DETAILS_GET returned) had the SSL service number(port number 52201) that I do not know where it was defined. I checked the communication channel and SM59 but found out nothing about 52201, neither the SSL part.
Would some one please tell me where the SSL security was defined?
Thanks for your help in advance!

Satish,
I checked the communication channel in the Configuration and the the transport protocol was "File System(NFS). We did not use FTP.
Thanks!
Fisher

Sender File Adapter - Problem with field separator

Hi,
I want to upload a CSV file into XI.
The file contains a text part which uses from time to time quotation marks like this:
SD,575757,383838,N/A,XYZ,"This is a text part",7676
But besides there are lines like this:
SD,575757,777722,N/A,XDE,FREETEXT,7575
Has anyone any idea how to configure the file adapter to get it recognize the quotation marks not as field separator?
I've already tried the enclosureSign parameters but that leads to an total unconverted line.
Is it maybe possible to customize two field separators like this:
Structure.fieldSeparator - ,"
Thanks for any answer,
Christina

No, it doesn't work.
I've specified now:
Structure.fieldSeparator        ,
Structure.enclosureSign         "
Structure.enclosureSignEscape   ""
Every line without quotation marks is converted fine. Lines with quotation marks stay like in the original CSV file and the whole line is put into one XML tag (still comma separated).
Also the parameter fieldContentFormatting - nothing doesn't make a difference.
Other ideas?

Receiver file adapter problem in file to file scenario

My situation is: I created the scanrios with file adapters, using
FTP, the sender adapter is picking up the file, but the output file
is not been created in the path mentioned, both the adapter status
looks green, I have no error message in the sxmb_moni for this
scenario. my adapter status looks as below:
kris_scenario1_filetofile_receiverCC Receiver Adapter v2112 for
Party '', Service 'krishna_bussystem01':
Configured at 2006-05-28 20:14:19 EDT
No message processing until now
kris_scenario1_filetofile_senderCC Sender Adapter v2126 for
Party '', Service 'krishna_bussystem01':
Configured at 2006-05-28 20:11:35 EDT
History:
- 2006-05-28 20:16:25 EDT: Polling interval started. Length: 10.000 s
- 2006-05-28 20:16:25 EDT: Processing finished successfully
- 2006-05-28 20:16:25 EDT: Processing started
- 2006-05-28 20:16:15 EDT: Polling interval started. Length: 10.000 s
- 2006-05-28 20:16:15 EDT: Processing finished successfully

Moorthy,
as you suggested I checked in MDT, FYI I am doing without content coversion. from the below message I dont see any problem, so what could be a problem
The sender has 'delivered' status but the receiver has 'to be delivered' status
Receiver audit log:
2006-05-29 00:07:56 Success The message was successfully received by the messaging system. Profile: XI URL:
2006-05-29 00:07:56 Success Using connection AFW. Trying to put the message into the receive queue.
2006-05-29 00:07:56 Success Message successfully put into the queue.
Sender audit log:
2006-05-29 00:07:54 Success Send binary file "filetofile.xml" from FTP server "xx.xx.xxx.xxx:/yyyyy", size 221 bytes with QoS EO
2006-05-29 00:07:54 Success Application attempting to send an XI message asynchronously using connection AFW.
2006-05-29 00:07:54 Success Trying to put the message into the send queue.
2006-05-29 00:07:54 Success Message successfully put into the queue.
2006-05-29 00:07:54 Success The application sent the message asynchronously using connection AFW. Returning to application.
2006-05-29 00:07:54 Success The message was successfully retrieved from the send queue.
2006-05-29 00:07:54 Success File "filetofile.xml" deleted after processing
2006-05-29 00:07:54 Success The message status set to DLNG.
2006-05-29 00:07:55 Success The message was successfully transmitted to endpoint http://host:port/sap/xi/engine?type=entry using connection AFW.
2006-05-29 00:07:55 Success The message status set to DLVD.

Sender File adapter problem

Hi,
I have File to JDBC sceanrio, File is on FTP server and data is added in file in every 15 mint. while adding data to file its takes some time.
My problem : when data is being added to file, sender adapter picks the file when addition of data is not completed. so it picks incomplete file and send to target.
What can be the possible solution to be used for this problem or what configurtaion can be done in CC required.
Thanks
Laxmi Bhushan

Hi Laxmi,
is PI picking file in NFS mode or FTP mode?
With NFS mode, you can use setting wait for file modification check. Same setting is available for FTP but it doesnt not work for FTP.
Another option could be ask Source system to generate file with a temporary name & rename once file is writen completely.
Regards
Sushil

Reciever file adapter problem

hi Gurus
We have 5 msgs stuck in 'delivering' status . I have checked http://<server>:<port>/MessagingSystem/monitor/systemStatus.jsp link and found that these 5 are holding up the queue. Below is the statistics.
File_http://sap.com/xi/XI/SystemRecv true 0 5 (5) 5
I went and saw in Received Messages-> Asynchronus and found these 5 msgs in 'delivering' status but there is no option to delete that or make it as failed.
Can someone pls hlep me how to clean up this queue so that the msgs wont come and lock here.
thank you

>>We have 5 msgs stuck in 'delivering' status
you are talking about IE or AE,
SMQ2 and SMQ1 only work for messages stuck in IE,if your messages are stuck in AE they won't do no good,if they are stuck in IE,then go to SMQ2 give the client name as * and then see and clear the stucked queues.
i guess ur messages are stuck in AE.if yes,then since they are in delivering status you should not mess up with it,its possible that the messages is huge or is taking more time due to some issue,but as long as they are delivering its fine.
if the status is Holding or system error or something like that then u need to re-process it
thanx
Aamir

File adapter problem - message in RWB HOLDING msg status

Similar Messages

Maybe you are looking for