on 04-19-2006 6:37 PM
Hi All,
I'm doing fixed lenghth file by small example. but my receiver adapter is showing following error
Receiver Adapter v2123 for Party '', Service 'F1_BS':
Configured at 2006-04-19 17:28:19 BST
No message processing until now
Following is my configuration
My file
123456
venugopalsirangi
Sender communication channel
Record structure: H1,,sub1,
FNAME Value
H1.fieldNames KF
H1.fieldFixedLengths 6
H1.fieldFixedType char
H1.endSeparator 'nl'
sub1.fieldNames KF,Lname,Sname
sub1.fieldFixedLengths 4,5,7
sub1..fieldFixedType char
sub1.endSeparator 'nl'
H1.keyFieldValue '144857'
sub1.keyFieldValue 'venu'
Receiver communication channel
Record structure:
FNAME Value
H1.fieldNames KF
H1.fieldFixedLengths 6
H1.fieldFixedType char
H1.endSeparator 'nl'
sub1.fieldNames KF,Lname,Sname
sub1.fieldFixedLengths 4,5,7
sub1..fieldFixedType char
sub1.endSeparator 'nl'
H1.keyFieldValue '144857'
sub1.keyFieldValue 'venu'
Regards,
venu.
Hi,
Should work with this, sorry no clue whats happening.
Thanks,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
In adapter specify following values.
Recordset Name - Any name
Recordset Structure - Seg1,1,Seg2,*....
Key Field Name - KZ
In content conversion, specify the following
ignoreRecordsetName true
Seg1.fieldFixedLengths .....
Seg1.fieldNames ....
Seg1.keyFieldValue 01
Try and let me know.
Thanks,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Venu,
Do one thing, try to remove content conversion and allow the adapter to pick up the XML file. If it works fine then we know the problem is in content conversion. Use any XML file for same purpose and let me know the results.
Thanks,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prateek,
XML file is successfully picked up by the adpater without content conversion.
If I do content conversion it is not receiver adapter not processing the message.
MY file.
0112345010101
021111112222
03100001111112222
03100011111212223
041000011111
021231116722
03100781119012332
041005611001
059453287699
MY xml file
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:LSOUT_MT xmlns:ns0="urn://LengthSpecific">
- <Header>
<Key1>01</Key1>
<name>12345</name>
<date>010101</date>
</Header>
- <Hbatch>
<Key2>02</Key2>
<hvalue1>11111</hvalue1>
<hvalue2>12222</hvalue2>
</Hbatch>
- <body>
<Key3>03</Key3>
<bvalue1>10000</bvalue1>
<bvalue2>111111</bvalue2>
<bvalue3>2222</bvalue3>
</body>
- <tbatch>
<Key4>04</Key4>
<tvalue1>10000</tvalue1>
<tvalue2>11111</tvalue2>
</tbatch>
- <trailer>
<Key5>05</Key5>
<value1>94532</value1>
<value2>87699</value2>
</trailer>
</ns0:LSOUT_MT>
MY content conversion of sender adapter is:
record struct :Header,1,Hbatch,,body,,tbatch,*,trailer,1
Header.fieldFixedLengths 2,5,6
Header.keyFieldValue 01
Header.fieldNames Key1,name,date
the same approach i used for Hbatch, body and tbatch..
My content conversion for receiver adapter is.
Record structure: Header,Hbatch,body,tbatch,trailer
Header.fieldFixedLengths 2,5,6
Header.fieldNames Key1,name,date
Header.processFieldNames fromConfiguration
rest as above.
Regards,
venu.
Hi,
Refer to this weblog.
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
Thanks,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Venu,
The file which you have given is not the same what you have specified in your structure. So kindly check your file and update the structure accordingly.
Also go through this urls:
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
---Mohan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Venu,
Check with MDT(message display tool) of Message Monitoring in the RWB. There will be a Content COnversion problem in Receiver Side.
For Receiver Communication Channel, it is not required to have Key Values etc. Only fieldfixed lengths,End Separator, field names.
http://help.sap.com/saphelp_nw2004s/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
Hope this helps,
regards,
Moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.