Configuring Receiver File Adapter for J2SE

Hi All,
I have a scenario in which i need to convert the IDOC data into a fixed length file.
I did mapping according to the output structure of the file.
My Output file format is as follows...
Document1 document2 document3 etc
Each document contains different fields with different lengths
In XI-FIle adapter we give Recordset structure : Document1,Document2,Document3.
But while configuring Receiver File adapter in J2SE.
There is no option mentioned in J2SE Adapter.
http://saphelp.border-states.com/EN/95/bb623c6369f454e10000000a114084/content.htm
Please throw some light on the same.
Thank You
Regards,
Reehan

as far as i read the document, what i understood is that the J2SE adapter has a limitation.
your XML structure should be as mention in the link;
To convert a table in XML format to pure text format, the document format must be the same as that which is generated by the sender file/FTP adapter in mode FILE2XMBWITHROWCONVERSION (with the default value <row> for the structure) and the sender JDBC adapter. This means that the document structure looks like this:
<resultset>
<row>
<column-name1>column-value</column-name1>
<column-name2>column-value</column-name2>
<column-name3>column-value</column-name3>
</row>
<row>
<column-name1>column-value</column-name1>
<column-name2>column-value</column-name2>
<column-name3>column-value</column-name3>
</row>
</resultset>
This is an example for 3 columns and 2 lines. The number of lines and columns is, of course, unlimited. The XML elements in italics can be defined by the user and the elements of a line must be grouped within an element of type <row> </row>.
So cannot take the recordset structure as we have for the normal File adapter.

Similar Messages

Error in Receiver File adapter using File content Conversion

Hi,
I am getting the following error in the receiver file adapter.
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'statement.fieldFixedLengths' or 'statement.fieldSeparator' is missing
I am using the below parameters for FCC:
Recordset Structure - statement
statement.endSeparator - 'nl'
statement.fieldSeparator - '0X09'
statement.fieldNames -xblnr,wrbtr,newbs,kostl,newko,prctr,xref1,rke_wwfud,rke_wwst3,blart,bukrs,bldate,budat,gjahr,monat,ctype,waers,bktxt,posnr,wbs_element,mwxkz,businessplace,businessplace,c_waers,c_wrbtr,g_ctype,g_waers,g_wrbtr,h_ctype,h_waers,h_wrbtr,trade_id,lob,sgtxt,zuonr,reason_rev,ldgrp,tcode,lifnr
ignoreRecordsetName - true
Please let me know where i am going wrong.
Thanks,
Aparna

Hi Aparna,
I feel the problem in your content conversion parameters is with
statement.fieldNames and ignoreRecordsetName
When you are confirguring receiver file adapter for file content conversion the above one is not required. Please refer below link for details on configuring content conversion in file adapter
[http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm]
Hope this helps !!
Regards,
Amit

Receiver File Adapter Alerts.....

Hi Gurus,
I need to configure Receiver File Adapter specific alerts....to test the alerts ...i am just giving wrong credentials for FTP....
But..wot I c is that the alert is received after the predefined no. of retries(6 nos) in Comm Channel Monitoring are completed in an interval of 5 mins each..ie I am getting the alert after 30 mins...but if I stop the channel ..I get the alert instantly b4 the first retry starts......
Wot is the diffence btw the 2 cases???

The behavior is perfect.
When Adapter tries to send the message to target and if some error with channel parameters or target system then the processing will be marked as error only when all the retries are done....in your case after 6 attempts....this can be configured.
However when you stop the channel the message is not passed from IE to AE and you get the error in first instance itself....you might get the error information in SXMB_MONI....there is no retry limit for this part...it will be tried only once
The first alert is due to error in AE and the second error is due to error in IE
If you want to get the alert if first retry itself is in error then configure the retry interval to 1.
Regards,
Abhishek.

Receiver file adapter creates an innecesarry extra line

Hi,
I have an issue with an extra line that add the receiver file adapter with the content conversion.
The file XML that the file adapter has to convert, is the next;
<root>
<cofig>
<FileName>NameOfTheFile.txt</FileName>
</cofig>
<lines>
<line>
<data>BBBBBBBBBBBBBBBBBBBBBB</data>
<data>Aaaaaaaaaaaaaaaaaaaaaa</data>
</lines>
</root>
Because FileName is not necessary, I remove it with:
cofig.fieldFixedLengths 0
cofig.fixedLengthTooShortHandling CUT
but it leaves an empty line that i don't want. that is, the text in the file start in the second line.
Any help?
Thank you in advance.

Can you do a small change in your mesg. structure ?
change it to....
<root>
<lines>
<line>
<data>BBBBBBBBBBBBBBBBBBBBBB</data>
<data>Aaaaaaaaaaaaaaaaaaaaaa</data>
</lines>
<cofig>
<FileName>NameOfTheFile.txt</FileName>
</cofig>
</root>
and then use
cofig.fieldFixedLengths 0
cofig.fixedLengthTooShortHandling CUT
followed by
endSeparator 0
Ref: Suppressing Field In Receiver File Adapter for more details.

J2Se receiver File adapter-HTTP 503 no listener registered for service

Hi,
We are using J2Se file adapter for one the interfaces and the logs of the J2se adapter engine has shown the following error-
Error: com.sap.aii.messaging.net.TransportException: HTTP 503 no listener registered for service /file/example_outbound
 at com.sap.aii.messaging.net.HTTPRequest.run(ServerHttpImpl.java:416)
I checked with the J2SE File/FTP receiver adapter configuration given at help.sap and found the following the following info related to the error-
Specifications for addressing by the Integration Engine
○ XI.httpPort=<port_no>
<port_no>specifies the HTTP server port that receives the messages from the Integration Engine.
○ XI.httpService=<service>
<service> describes the service part of the address where the Integration Engine must send its messages.
These specifications are mandatory.
If, for example, you have specified XI.httpPort=1234 and XI.httpService=/file/Receiver, the end point address of the file/FTP adapter in the Integration Engine must be specified as follows:
http://<fileadapterhost>:1234/file/Receiver
The end point address must be extended as follows for the Integration Engine in Release 1.0:
http://<fileadapterhost>:1234/file/Receiver?action=execute&pipelineid=Receiver
If the Integration Engine message is sent to a non-specified adapter service, the system displays the following error message:
*No registered listener for <Service> found*
The system displays the same message if the adapter is initialized, but has not been started (status STOPPED or INITIALIZED).
Where I need to check this Integration engine address specifications. I have't found any of the above code in the adapter configuration which we are using presently.The interface is running successfully before but thrown this error now.
Please reply me if some one has faced similar issue and get it resolved.

Hi
How was this issue resolved? I have the same problem.
I only have two receivers - the deafult j2se file receiver and my newly created one which used the default as a template. The ports and service's are different.
I've even tried deleting my custom receive adapter and using only the default one but i still get that error.

Receiver File Adapter J2SE Adapter Engine

Hi,
We have configured a receiver file adapter on a J2SE adapter engine through the administrator page of the J2SE adapter.
XI.httpPort=8222
XI.httpService=/file/Receive
and the rest of the adapter parameters.
I have configured a channel in ID as XI receiver adapter.
host: "hostname"
Service: 8222
Path Prefix: /file/Receive
The messages in sxmb_moni fail to be delivered with "HTTP error 404 Resource not found."
Through a browser I am also not able to make a connection to this url:
"host":8222/file/Receive
Getting Http error "501".
Please can someone shed some light on this problem.
Regards
Willie Hugo

>Through a browser I am also not able to make a connection to this url:
>"host":8222/file/Receive
>Getting Http error "501".
This is ok. Since get method not implemeted for this service.
Since from XI you are getting this error "HTTP error 404 Resource not found", can you logon to XI server at OS level and do a telnet test to check if the port is working.
cmd> telnet
telnet> open <J2SEAdpaterEngineHostName (or) IPAddress> 8222

Receiver file adapter error for special char.

I am using MTB in my receiver file adapter. I am getting a special character from source system at end of the string. How to resolve this type of error u2013 please advice.
This error is not coming for every message.
Error message:
Column value xxxx Â too long - must stop, probably configuration error in file adapter
Thanks
Vick

Hi,
Itu2019s basically IDOC to file scenario.
This error is coming for name field.
What I am thinking at this stage to do changes in MTB by define parameters like (NameA.enclosureConversion)

Dynamic File Name for Receiver File Adapter

Hi All,
How can we use dynamic name for Receiver file adapter?
Can anyone help.
Thanks in Advance
Chemmanz

Hi Chemmanz,
The dynamic filename generation concept is as follows.
In your filename field. just give a variable with % symbols. (eg: %file% ).
Now, under the option Variable Name Substitution, you can give how the value has to be created.
It can be your interface name, sender service name, etc or it can be some value dynamically from your payload.
For the former, your give
message:interface_name ,etc
and for the payload part you give,
Payload: "your element root which u wanna acecss"
Just check this link out,
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
And read the contents under variable substitution and it will help you understand the concepts better.
If you have any clarifications, do get back,
Regards,
Bhavesh

Configuring File adapter for OSB

Hi,
I wish to process invoice data that will be in the csv file . The structure of the file is as following :
$H$<<Supplier Name>>,<<Supplier Site>>,<<Invoice Number>>
$D$<<Line Number>> ,<<Business Unit>>,<<Location>>,<<Store Name>>
$D$<<Line Number>> ,<<Business Unit>>,<<Location>>,<<Store Name>>
$H$<<Supplier Name>>,<<Supplier Site>>,<<Invoice Number>>
$D$<<Line Number>> ,<<Business Unit>>,<<Location>>,<<Store Name>>
$D$<<Line Number>> ,<<Business Unit>>,<<Location>>,<<Store Name>>
The intent is to configure the file adapter in such a fashion that it rejects the entire invoice if there are any errors in any of the lines that belong to that invoice. The invoices that follow the erred inovice should be processed normally. How do I configure the adapter to achieve this? Any help is greatly appreciated.

Hi,
Configuring the adapter for rejecting the invalid invoice rows is not possible. Adapter should be configured as usual to read all the rows. Once the rows are read, you can have all validation in the proxy service. If you find any invalid rows, you can write those rows to a saperate file so that it can be corrected and fed again. And all the other valid rows can be sent for further processing.
Thanks,
Vishwa

Receiver file adapter posts multiples for singel source files

Hi,
I am using wild character in my input source ftp adapter but my receiver file adapter is creating multiple duplicate files. I am not sure why this happens as QOS is set to "Exactly Once" with archive processing mode. I tried with delete mode and the same error occurs. We had no problems testing it in our Dev environment but in QA its acting so strangely...Any advise is appreciated..
-Teresa

Hi,
2. Homany files you posted at oubound directory?
1. You said duplicate files at receiver side, is the files having time stamp? if so those are not duplicate files.
Thanks,
Satish.

OS Command for receiver file adapter

Hi Guys,
I have a requirement that in the target folder before putting the file, I have to rename the exisitng file then put the file. The target folder is in another machine and I have to use FTP option to send file.
is it possible to use OS command after processing option in the receiver file adapter to do this? please let me know how to handle this.
Thanks
Mukesh

Mukesh,
You cannot rename the file in the FTP folder. What you can do is write a OS script where it logs in into the FTP site and renames the file. Then use this OS script before message processing so that it renames the file before you write the actual file.
If you want to rename a file which is on the applicaiton server using NFS then you can directly rename it from the command prompt.
Regards,
---Satish

Attachments for receiver file adapter

Hello gurus,
I think receiver file adapter does not support attachments. But I do have a scenario where I receive additional files as SOAP payloads accompanying the request message and I have to write them to a network directory. How can I achieve this?
Regards,
Gökhan

Hi Gokhan,
Please have a look at the following links and see if it helps
Re: File adapter with attachment to mail
Re: How to use File Adapter to transport files
Best Regards

Receiver file adapter settings

Hi,
I have a scenario in which I need to generate a file in tab delimited format. But in the receiver file adapter configuration we have only text/binary file creation mode. By setting the File Type in TEXT mode will I be able to do a tab de-limited file?? Or is there any other configuration settings need to be done?
-Ken

Hi Amanda,
Thank you so much for the great info. I think I can find some stuff but still it would be helpful if you could forward the doc to [email protected] Also, yeah it looks like the receiving file format would be complex with header and footer. In the content conversion can we specify header and footer?? or is there any other way to define...FYI my source file also contains header and footer..I am just a little confused on how to set up the message types for mapping...
Many thanks..
-ken

Sender_interface_name in Variable Substitution in Receiver File Adapter CC

Hi,
as per this page : http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm
it says:
Variable Substitution (Target Directory/File Name Scheme)
If you set the Enable indicator, you can enter variables for the Target Directory and File Name Scheme. Enter the names of the variables and references in the table.
●      Enter each variable that you reference in the Target Directory and File Name Scheme fields without the surrounding percentage sign under Name of Variables in the table.
The variables can refer to attributes of the message header or elements of the message payload.
○       If the variables are to refer to an attribute of the message header, add the prefix message: to the name of the variable under Reference. You can specify the following attributes of the message header:
sender_party, sender_service, receiver_party, receiver_service, interface_name, interface_namespace, message_id, message_id_hex
Can we not access sender_interface_name and sender_interface_namespace are not mentioned in above list of variables.
Is it not possible to access sender_interface_name or sender_interface_namespace as variable substitute parameters from within Receiver File Adapter Communication channel.
thanks.

>Shabarish Vijayakumar wrote:
>>the sender interface details will always remain a constant
>>so you can hard code the value, isnt it?
Yes, i can hardcode, thats not a bad idea, i need to create then 3 different Reciever File Communication Channel objects, as I am dealing with 3 scenarios for which sender system and sender interface is different.
>Shabarish Vijayakumar wrote:
>>if you look at the mapping runtime constants, those are also for the receiver since the sender interface will always remain constant for any particular CC.
>>http://help.sap.com/saphelp_nw04/helpdata/en/b3/9a2aeb24dc4ab6b1855c99157529e4/content.htm
yes in this link you provided i can see..
INTERFACE     Interface
INTERFACE_NAMESPACE     InterfaceNamespace
SENDER_SERVICE     SenderService
RECEIVER_SERVICE ReceiverService
RECEIVER_NAME     ReceiverName
RECEIVER_NAMESPACE     ReceiverNamespace
it seems both INTERFACE (,INTERFACE_NAMESPACE) and RECEIVER_NAME(,RECEIVER_NAMESPACE) are present, may be one is for sender, and another is for receiver.. may be if i use dynamic configuration, possibly my issue would be addressed.. correct me if i am wrong.
thanks.

0 byte txt file using receiver File Adapter

HI,
My scenario is Flat File to Fixed Length File.
Mapping : Based on the condition Reciever node need to generated , In some cases it wont generate any node ( No data )
Receiver Communication channel : I used FCC for Fixed length Format.
Problem : When i am generatingf the receiver file with some data it executes. But when i am generating the file with no data , it fails in the receiver comminication channel.
Could not process due to error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Message1' found in document', probably configuration error in file adapter (XML parser error)'
I need the receiver file to generate with 0 bytes when there is empty data.
can any one help on this.
Thanks

Hi,
>>Problem : When i am generatingf the receiver file with some data it executes. But when i am generating the file with no data , it fails in the receiver comminication channel.
What happens in this case is, when you send a blank file to PI it processes but once it went to Receiver Adapter, it looks out for some fields because of the FCC settings. So it throws an error/exception because some fields are expected and it is not coming. Because of that you getting below exception.
Secondly, Once you send data with few values or fields it will process in Receiver file adapter FCC and if there is some error it throws error. this is why you getting exception in moni, and other places.
Regards
Aashish Sinha

Configuring Receiver File Adapter for J2SE

Similar Messages

Maybe you are looking for