File Content Conversion in Receiver Adapter Help
Hi,
I need to have a flat file at receiver side with the following structure.
Product
LineItem
Notes
Product
LineItem
Notes
But i am getting as
Product
Product
LineItem
Notes
Notes
Please suggest me the changes to be made in File Content Conversion Parameter
Your Help will be appreciated.
Thanks in advance,
Ashok
Singh,
I think we wont give field names in the receiver file adapter. Please find the details below:
RecordSet Structure: Product,LineItem,Notes.....
Parameters:
Product.fieldFixedLengths:30,10...
Product.endSeparator:'nl'
LineItem.fieldFixedLengths:30,10..
LineItem.endSeparator:'nl'
Notes.fieldFixedLengths:30,10...
Notes.endSeparator: 'nl'
Thanks
Ashok
Similar Messages
-
File Content Conversion in Receiver Adapter
Hello Friends,
I have following message in reciever adapter. How to set the parameter to output flat file? I set but it dosent function:
Record structure: Category, Items, Item
Category.fieldSeparator ,
Category.endSeparator ,
Items.fieldSeparator ,
Items.endSeparator ,
Item.fieldSeparator ,
Item.endSeparator ,
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:UpdateCategories xmlns:ns0="urn:N02_TestComplexCategory">
- <ns0:Category>
<ns0:RootCategoryID>14</ns0:RootCategoryID>
<ns0:RootCategoryParentID>34</ns0:RootCategoryParentID>
<ns0:RootCategoryName>abcd</ns0:RootCategoryName>
- <ns0:Items>
- <ns0:Item>
<ns0:CategoryID>ID1</ns0:CategoryID>
<ns0:CategoryParentID>14</ns0:CategoryParentID>
<ns0:CategoryName>CAT1</ns0:CategoryName>
<ns0:Attributes />
</ns0:Item>
- <ns0:Item>
<ns0:CategoryID>ID2</ns0:CategoryID>
<ns0:CategoryParentID>14</ns0:CategoryParentID>
<ns0:CategoryName>CAT2</ns0:CategoryName>
<ns0:Attributes />
</ns0:Item>
</ns0:Items>
</ns0:Category>
</ns0:UpdateCategories>
Thanks
ZhipingAnother message:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:UpdateCategories xmlns:ns0="urn:N02_TestComplexCategory">
- <ns0:Category>
<ns0:RootCategoryID>14</ns0:RootCategoryID>
<ns0:RootCategoryParentID>34</ns0:RootCategoryParentID>
<ns0:RootCategoryName>abcd</ns0:RootCategoryName>
- <ns0:Items>
- <ns0:Item>
<ns0:CategoryID>ID1</ns0:CategoryID>
<ns0:CategoryParentID>14</ns0:CategoryParentID>
<ns0:CategoryName>CAT1</ns0:CategoryName>
- <ns0:Attributes>
- <ns0:Attribute>
<ns0:AttributeType>1</ns0:AttributeType>
<ns0:AttributeValue>1</ns0:AttributeValue>
</ns0:Attribute>
- <ns0:Attribute>
<ns0:AttributeType>2</ns0:AttributeType>
<ns0:AttributeValue>2</ns0:AttributeValue>
</ns0:Attribute>
- <ns0:Attribute>
<ns0:AttributeType>3</ns0:AttributeType>
<ns0:AttributeValue>3</ns0:AttributeValue>
</ns0:Attribute>
</ns0:Attributes>
</ns0:Item>
- <ns0:Item>
<ns0:CategoryID>ID2</ns0:CategoryID>
<ns0:CategoryParentID>14</ns0:CategoryParentID>
<ns0:CategoryName>CAT2</ns0:CategoryName>
- <ns0:Attributes>
- <ns0:Attribute>
<ns0:AttributeType>1</ns0:AttributeType>
<ns0:AttributeValue>1</ns0:AttributeValue>
</ns0:Attribute>
- <ns0:Attribute>
<ns0:AttributeType>2</ns0:AttributeType>
<ns0:AttributeValue>2</ns0:AttributeValue>
</ns0:Attribute>
- <ns0:Attribute>
<ns0:AttributeType>3</ns0:AttributeType>
<ns0:AttributeValue>3</ns0:AttributeValue>
</ns0:Attribute>
</ns0:Attributes>
</ns0:Item>
</ns0:Items>
</ns0:Category>
</ns0:UpdateCategories> -
Problem with file content conversion in receiver file adapter
Hi All
I have a problem with file content conversion in receiver file adapter.
This is my recordset structure: Header_Record,1,Claim_Record,*,Check_Rec,1
These are the content conversion parameters:
Header_Record.fieldSeparator = ,
Header_Record.endSeparator = 'nl'
Claim_Record.fieldSeparator = ,
Claim_Record.endSeparator = 'nl'
Check_Rec.fieldSeparator = ,
Check_Rec.endSeparator = 'nl'
In SXMB_MONI, i can see that the data is correctly extracted from proxy, and correctly mapped to receiver message, and i see a checkered flag (success).
But, Adapter status is RED with the following error message:
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
In communication channel monitoring, i get the following error message:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages
What is going wrong here? Can anyone please tell me?
Thanks
ChandraPosted in Incorrect forum.
Posted again in Process Integration forum -
How can I convert my specific file content in the Receiver Adapter(XI 7.0)?
Hi all,
I have a document structure as below:
<MT_MATERIAL>
<MATERIAL>
<WERKS>1000</WERKS>
<MATNR>HAD_00001</MATNR>
<MAKTX>CHEMICAL MATERIAL</MAKTX>
</MATERIAL>
</MT_MATERIAL>
This document structure is the file content in the Receiver Adapter (File Adapter). In the 'Content Conversion' tab of File Adapter of Communication Channel 'CC_OUT_MATERIAL_FILE', I have configured the parameters as below:
Recordset Structure: MATERIAL
MT_MATERIAL.fieldSeparator: '
MT_MATERIAL.endSeparator: 'nl'
MATERIAL.fieldSeparator: '
MATERIAL.endSeparator: 'nl'
*.fieldSeparator: ,
But, this Communication Channel 'CC_OUT_MATERIAL_FILE' (in the Runtime WorkBench/Component Monitoring/Adapter Engine/Communication Channel Monitoring) is error with the error message as below:
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
Could anyone please help me to correct this error, how should i configure the parameters in the 'Content Conversion' tab?
Thanks a lot in advance,
Vinh VoHi Vinho,
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
Have a look at the this blog by Arpit Seth ... its all about FCC at receiver side...
File Receiver with Content Conversion
Also have a look at this thread.. might be helps you....
RECEIVER file CONTENT CONVERSION
Above links be helpful.
Regards,
Jayasimha Jangam -
File content conversion in receiver
Hi,
My receiver Message type structure is
Heading1
subheading 1
FieldValue1
FieldValue 2
Fieldvalue3
I want to create file content conversion in receiver side.
plz help me to create what could be my recordset structure, name, value.
my scenario is Idoc to file.Ruban:
Your FCC goes like this
subheading1.fieldSeparator = ',' /* if comma is the separator you want, if u need any other replace it*/
subheading1.endSeparator = 'nl'
Did you check my previous post in your other thread, I posted similar example there. -
Idoc 2 file - file content conversion in receiver
Hi,
My scenario is idoc to file.
if i want to use file content conversion at receiver side,
so i need to create record set according to sender side data type or receiver data type?
plz give some inputs reg. this.
ThanksHi,
There is problem while refreshing in sap xi also.
when i pass new parameter like 7 in my recordset structure,
it is immediately reflecting in CC monitoring.
error it is showing that '7'.
but if i remove that in record set structure
(after activating that in ID)
even though
if i stop and start my CC manually also,
still it is showing that error in CC monitoring
like '7'
basic concept of this file content conversion is
I have to keep at least field separator (ie 'nl' )for outer most node element ie Customer_copy and record set stru. as Customer_copy
is it right?
I tried my own way...still it is giving that error.
what could my fieldSeparator, endSeparator, for ur last case plz tell me?
Edited by: ruban R on Apr 22, 2008 3:01 AM -
Supress Column Heading - File Content Conversion in Sender Adapter
Hi,
Let me give a more clear picture about my scenario. I need to convert CSV File to XML output:-
My source file has column heading and values. The sample data is mentioned hereunder:-
PERNR;KID;PNALT;NACHN;NAME2;VORNA
;1200;1200;Angus
I have created a data type as under:-
DT_LegacyEmployee (Category - Complex Type)
Employees (Category - Element, Occurence - 1)
Header (Category - Element, Occurence - 0...1)
PERNR_H
KID_H
PNALT_H
NACHN_H
NAME2_H
VORNA_H
Employee (Categroy - Element, Type - DT_LegacyEmployee_Row, Occurence - 0...unbounded)
PERNR
KID
PNALT
NACHN
NAME2
VORNA
The file conversion parameters in the file sender adapter are mentioned hereunder:-
Document Name - MT_LegacyEmployee
Document Namespace - http://abc.com/xi
Recordset Name - Employees
Rescordset Structure - Header,1,Employee,*
Recordsets per Message - 1
Key Field Type - String (Case Sensitive)
Employee.fieldSeparator - ;
Employee.endSeparator - 'nl'
Employee.fieldNames - PERNR,KID,PNALT,NACHN,NAME2,VORNA
I dont' have a key field value. How do we remove the header and show only the values in the xml output. I have searched the forum topics as well checked many blogs related to file content conversion, but nothing helped. Kindly advice how to fix this issue. Thanks in advance.
Regards.
PraveenHi Praveen,
Change your File Adapter as below
Document Name - MT_LegacyEmployee
Document Namespace - http://abc.com/xi
Recordset Name - Employees
Rescordset Structure - Employee,*
Recordsets per Message - 1
Key Field Type - String (Case Sensitive)
Employee.fieldSeparator - ;
Employee.endSeparator - 'nl'
Employee.fieldNames - PERNR,KID,PNALT,NACHN,NAME2,VORNA
There is no need for the Header required in the data type.
DT_LegacyEmployee (Category - Complex Type)
Employees (Category - Element, Occurence - 1)
Employee (Categroy - Element, Type - DT_LegacyEmployee_Row, Occurence - 0...unbounded)
PERNR
KID
PNALT
NACHN
NAME2
VORNA
Now the trick is in the mapping program
Lets assume your mapping looks like
MT_LegacyEmployee ---> MT_TargetEmployee
- Employees ---> Records
- Employee ---> Record
- PERNR ---> TargetPERNR
- .. so on
When you do a mapping from Employee ---> Record apply the following logic.
(PERNR)--->
(TestEquals =) --->(NOT)--->
(Constant) ---> (IF)
(PERNR) (IF Without Else) ---> (Record)
(THEN)
(Employee)--->
When doing this make sure RightClick on PERNR and Select Context ---> Employees.
By default context would be from Employee and it will give you an error of XSD format. So make sure you are changing the context. -
File content conversion using SOAP adapter
Hi,
I'm using a receiver SOAP adapter in my IDOC to file scenario and need to do file content conversion in the receiver side.
Are any standard modules available for file content conversion in the SOAP adapter or do I need to write custom EJB modules for this.
Please note that I have to use a SOAP adapter, can't use any other adapter.
Thanks in advance
ShiladityaHi,
XML Document Conversion Type
● Enter recordTypes as the parameter name.
Under Parameter Value, enter the complete, comma-separated list of all names of recordset types that occur in the document to be converted.
If you decide to use this method, you can define a different conversion type for each recordset type that occurs in the XML document.
For example, you could name the recordset types as follows: RecordType1,RecordType2,RecordType3.
● Enter singleRecordType as the parameter name.
Under Parameter Value, enter the name of a recordset type that is to be used to convert all elements that occur in the XML document.
If you decide to use this method, define the same conversion type for each recordset type that occurs in the XML document.
You must enter exactly one parameter only. Whichever parameter you choose, you automatically exclude the second parameter.
You define further parameters for each recordset type.
In the remainder of this documentation the parameters are specified by the prefix <RecordType>. In your configuration, replace this name with the name of the recordset type.
Conversion Type List with Separators
● <RecordType>.fieldSeparator
Enter the field separator that is written between the individual fields of a record.
This specification is mandatory.
Conversion Type List with Fixed Field Length
● <RecordType>.fieldLengths
Specify a character string that contains a list of fixed field lengths that are separated by commas and which determines the number and the length of fields generated in the text file.
For example, you want to write a recordset with three elements that have field widths of five, ten, and fifteen characters. Enter:
<RecordType>.fieldLengths = 5,10,15
This specification is mandatory.
● <RecordType>.fieldLengthExceeded
Specify how you want to handle fields that exceed the configured field length. Permitted values for the parameter value are:
○ error (default)
Interrupts processing of message with error
○ cut
Cuts off superfluous characters
○ ignore
Ignores the field length restriction
Further Entries
● <RecordType>.beginSeparator
Enter a string. The string is placed in front of the first field of a recordset.
● <RecordType>.endSeparator
Enter a string. The string is appended to the last field of a recordset as a concluding character. The default is \r\n.
● contentType
Enter the MIME type of the converted payload. The default value is text/plain.
● addHeaderLine
Only define this parameter if you have already defined singleRecordType.
Define whether a header line is to be added to the result of the conversion.
○ none (default)
Does not insert a header line
○ fromXML
The header line is generated from the element name of the first recordset of the XML document
○ fromConfiguration
The header line is determined by the configuration parameter headerLine.
● headerLine
Only define this parameter if you have already set addHeaderLine=fromConfiguration.
The value that you define is placed in front of the result of the conversion as a header line.
● fixedLineWidth
Enter the maximum line length n (in characters) that can be written to the resulting document. The separator specified by lineSeparator is inserted in the resulting document every n characters.
● lineSeparator
Only define this parameter if you have already defined fixedLineWidth.
Specify the string that is written to the resulting document at the end of each line that is written with fixedLineWidth. The default is \r\n.
Use of Special Characters
You can use special characters in the following parameters: <RecordType>.fieldSeparator, <RecordType>.beginSeparator, <RecordType>.endSeparator, headerLine, and lineSeparator.
● Tabulator: \t
● Carriage Return (CR): \r
● Line Feed (LF): \n
● Arbitrary character: \x<code>
<code>indicates the hexadecimal character code of the character to be displayed.
Regards,
Phani -
Hierarchy on file content conversion for receiver?
Y'all,
I'm stuck in this problem and I haven't find a solution to solved it... so, all your clues and reply's are really appreciate...
The basic problem is a File content conversion for a receiver C.C. that is not working and it's raising some errors in the RWB, I have gone thru some blogs but I still having a lot of doubts...
I want to produce a flat TXT file that will have a line for every node or subnode, it doesn't matter if it's not represented as hierarchical structure like this one... but the records must be produced or written in the same order...
Man_Del_Header as main node with Man_Header, Delete_Detail and Trailer as subnodes...
<?xml version="1.0" encoding="UTF-8"?>
<ns1:MT_DISTRIBUTOR_DELETE xmlns:ns1="http://xxx.com/xi/POSout">
<Man_Del_Header>
<MD_Header>|HM|1|</MD_Header>
<MD_StoreNumber>051</MD_StoreNumber>
<MD_filler1>|2|0000|3|</MD_filler1>
<MD_EffDate>09/17/07</MD_EffDate>
<MD_filler2>|4|005|5|dsdvnd|7|</MD_filler2>
<MD_BatchNumber>500</MD_BatchNumber>
<MD_fiiller3>|8|</MD_fiiller3>
<MD_BatchDescr>DELETE PREV CST BTCH</MD_BatchDescr>
<MD_filler4>|10|D|</MD_filler4>
<MD_linef>1</MD_linef>
<Man_Header>
<Man_Header>|HM|1|</Man_Header>
<Man_StoreNumber>051</Man_StoreNumber>
<Man_filler1>|2|0000|3|</Man_filler1>
<Man_EffDate>09/17/07</Man_EffDate>
<Man_filler2>|4|005|5|dsdvnd|7|</Man_filler2>
<Man_BatchNumber>500</Man_BatchNumber>
<Man_filler3>|8|</Man_filler3>
<Man_BatchDescription>Delete Distributor</Man_BatchDescription>
<Man_filler4>|</Man_filler4>
<Man_linef>Constant</Man_linef>
</Man_Header>
<Delete_Detail>
<Delete_Detail>|D|901|170|</Delete_Detail>
<Delete_DistribNumber>0000005010</Delete_DistribNumber>
<filler9>|</filler9>
<delete_linef>1</delete_linef>
</Delete_Detail>
<Delete_Detail>
<Delete_Detail>|D|901|170|</Delete_Detail>
<Delete_DistribNumber>0000005011</Delete_DistribNumber>
<filler9>|</filler9>
<delete_linef>1</delete_linef>
</Delete_Detail>
<Trailer>
<Trailer>|T|1|</Trailer>
<TotalRecCnt>00005</TotalRecCnt>
<filler1>|2|</filler1>
<NoOfHeaders>00002</NoOfHeaders>
<filler2>|3|</filler2>
<NoOfAdds>00000</NoOfAdds>
<filler3>|4|</filler3>
<NoOfChanges>00000</NoOfChanges>
<filler4>|5|</filler4>
<NoOfDeletes>00002</NoOfDeletes>
<filler5>|13|</filler5>
<NoOfSubstitution>00000</NoOfSubstitution>
<filler6>|</filler6>
<linef>1</linef>
</Trailer>
</Man_Del_Header>
<Man_Del_Header>
<MD_Header>|HM|1|</MD_Header>
<MD_StoreNumber>061</MD_StoreNumber>
<MD_filler1>|2|0000|3|</MD_filler1>
<MD_EffDate>09/17/07</MD_EffDate>
<MD_filler2>|4|005|5|dsdvnd|7|</MD_filler2>
<MD_BatchNumber>500</MD_BatchNumber>
<MD_fiiller3>|8|</MD_fiiller3>
<MD_BatchDescr>DELETE PREV CST BTCH</MD_BatchDescr>
<MD_filler4>|10|D|</MD_filler4>
<MD_linef>1</MD_linef>
<Man_Header>
<Man_Header>|HM|1|</Man_Header>
<Man_StoreNumber>061</Man_StoreNumber>
<Man_filler1>|2|0000|3|</Man_filler1>
<Man_EffDate>09/17/07</Man_EffDate>
<Man_filler2>|4|005|5|dsdvnd|7|</Man_filler2>
<Man_BatchNumber>500</Man_BatchNumber>
<Man_filler3>|8|</Man_filler3>
<Man_BatchDescription>Delete Distributor</Man_BatchDescription>
<Man_filler4>|</Man_filler4>
<Man_linef>Constant</Man_linef>
</Man_Header>
<Delete_Detail>
<Delete_Detail>|D|901|170|</Delete_Detail>
<Delete_DistribNumber>0000005012</Delete_DistribNumber>
<filler9>|</filler9>
<delete_linef>1</delete_linef>
</Delete_Detail>
<Delete_Detail>
<Delete_Detail>|D|901|170|</Delete_Detail>
<Delete_DistribNumber>0000005013</Delete_DistribNumber>
<filler9>|</filler9>
<delete_linef>1</delete_linef>
</Delete_Detail>
<Delete_Detail>
<Delete_Detail>|D|901|170|</Delete_Detail>
<Delete_DistribNumber>0000005014</Delete_DistribNumber>
<filler9>|</filler9>
<delete_linef>1</delete_linef>
</Delete_Detail>
<Trailer>
<Trailer>|T|1|</Trailer>
<TotalRecCnt>00006</TotalRecCnt>
<filler1>|2|</filler1>
<NoOfHeaders>00002</NoOfHeaders>
<filler2>|3|</filler2>
<NoOfAdds>00000</NoOfAdds>
<filler3>|4|</filler3>
<NoOfChanges>00000</NoOfChanges>
<filler4>|5|</filler4>
<NoOfDeletes>00003</NoOfDeletes>
<filler5>|13|</filler5>
<NoOfSubstitution>00000</NoOfSubstitution>
<filler6>|</filler6>
<linef>1</linef>
</Trailer>
</Man_Del_Header>
</ns1:MT_DISTRIBUTOR_DELETE>
|HM|1|051|2|0000|3|09/17/07|4|005|5|dsdvnd|7|500|8|DELETE PREV CST BTCH|10|D|1
|HM|1|051|2|0000|3|09/17/07|4|005|5|dsdvnd|7|500|8|Delete Distributor|Constant
|D|901|170|0000005010|1
|D|901|170|0000005011|1
|T|1|00005|2|00002|3|00000|4|00000|5|00002|13|00000|1
|HM|1|061|2|0000|3|09/17/07|4|005|5|dsdvnd|7|500|8|DELETE PREV CST BTCH|10|D|1
|HM|1|061|2|0000|3|09/17/07|4|005|5|dsdvnd|7|500|8|Delete Distributor|Constant
|D|901|170|0000005012|1
|D|901|170|0000005013|1
|D|901|170|0000005014|1
|T|1|00006|2|00002|3|00000|4|00000|5|00003|13|00000|1
So as you can see, i wanna produce a flat file that will have line or record for each node, it doesn't matter that it has a hierarchy or a deeper level, it should be a simple flat file...
The thing is that i have been trying to setup the receiver comm. channel and it's raising some errors like Could not process due to error:
<i>java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value 'XXXX')', probably configuration error in file adapter (XML parser error)'</i>
I have checked this blog:
/people/karthiknarayan.kesavan2/blog/2007/08/22/file-content-conversion-for-multi-hierarchical-structure
Unfortunately i don't know if there's another way to achieve this...Jerry,
it easy if you go with multi mapping concept and without BPM if you are above >XI3.0 SP14.and use Append mode in the receiver file adapter.
just create the target structure like root under that Man_Del_Header,Man_Header,Detail,Trailer at the same level but got be careful with occurences.
<b>Source:</b>
I think from your structure you have
Man_Del_Header (1-unb)
Man_Header (1-1)
detail (0-unb ) may be (1-unb)
trailer (1-1)
create <b>target DT</b> like:
ROOT
..Man_Del_Header (1-1)
..Man_Header (1-1)
..detail (0-unb ) may be (1-unb)
..trailer (1-1)
all are at same level under ROOT.
create MT,MI,MM,IM.
in MM just map correspoding fields and if you have any unbounded onces map the nodes too. and map Man_Del_Header in the source to MT_XYZ (important)
and in the MM go to MESSAGES tab and change the occurences of the target Message to 0-unbounded same way in the interface mapping 0-unbounded.
here it create anothe extra node in the mapping something like Message1,this is ok.
and in ID just create all other objects like as usual except creating Interface determination ,in that select the extended radio button.
in reciever File CC use FCC ,would be very simple in the recordsetstrcture give
your four nodes Man_Del_Header,Man_Header,Detail,Trailer.
and use either fixed or field seperator.use append mode in recv File CC otherwise it will generate files as many occurences your source "Man_Del_Header" has ,cos we are mapping it to the MT--xyz .
thats it you are ready to go...
if any error post back here again.
you can make use of this thread
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible (here there are two target DT ,but you just create one DT,remaining are similar)
good luck.
Babu -
IDOC to flat File----Problem in File Content Conversion at receiver
hi experts,
I am doing a IDOC to flat file secnario.
My requirment is IDOCXI-Flat file
Format of flat file is like:--
Every segment in the IDOC will be converted into a single line of file(without any delimiter). So number of lines in flat file will be equal to number of segments in IDOC.
I am facing problem in File Content conversion.
Please help me out..
Thanks
JaideepCheck this doc...
[How To...Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0 |https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a] -
REG: File content conversion in Receiver file adapter
HI Gurus,
I have the scenario like proxy to file with content conversion
my message type for the source like this
MT_SOURCE
-----||
|---ROW
------------||
|---LINE
target strucuture also same
MT_TARGET
-----||
|---ROW
------------||
|---LINE
i am using the following FCC parameters in receiver file adapter
LINE.fieldSeparator = ' '
LINE.fixedLineWidth = 90
LINE.lineSeparator = 'nl'
LINE.fieldFixedLengths = 200
LINE.endSeparator = 'nl'
the output file show the data differently in note pad when compare to word
word output
dgepvs 023456987
kgdd0016155710 SS Smw Ne 01
kgdd0016155710 SS Smw Ne 01
kgdd0016155710 SS Smw Ne 01
kgdd0016155710 SS Smw Ne 01
kgdd0016155710 SS Smw Ne 01
kgdd0016155710 SS Smw Ne 01
kgdd0016155710 SS Smw Ne 01
notepad out put
dgepvs 023456987 kgdd0016155710 SS Smw Ne 01 kgdd0016155710 SS Smw Ne 01 kgdd0016155710 SS Smw Ne 01 kgdd0016155710 SS Smw Ne 01 kgdd0016155710 SS Smw Ne 01
word output is the correct output wat i am expect but same out put i want in note pad can any help me out for this how can i resolve this
Thanks in advanceThere is nothing wrong in your content conversion parameters. This is pure editors interpretation for the next line character.
I would do in java program to fix this issue using '\r\n' You might want to try and see how that helps for notepad editor. -
File Content Conversion at receiver end
Hi
My XML structure is
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:MT_CreatePurchaseOrder xmlns:ns0="http://demo.com/POCreate">
<recordset>
<POHeader> (min 1 max 1)
</POHeader>
<POLineItem> (min 1 max unbounded)
</POLineItem>
<POScheduleLine> (min 1 max unbounded)
</POScheduleLine>
<POPromiseScheduleLine> (min 1 max unbounded)
</POPromiseScheduleLine>
</recordset>
</ns0:MT_CreatePurchaseOrder>
I am mapping this particular structure from Idoc orders05(PO create). My client needs the out file as txt with tab as delimiter and should be one line.(Nodes POLineItem and POScheduleline will repeat)
Help me out what should be passed as Content conversion Parameters..
Thanks in advance
Gowri KHi Gowri,
Please take a look at these threads.. They clearly explain File CC on the reciever side
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
Hope this helps you out!
cheers,
Prashanth
P.S Please mark helpful answers
It shows the CC params done on the reciever side. -
File content conversion for receiver file structure(fixed length)
Hi Experts,
I am tryinng reciver file FCC for the following strcuture. it seems I have done some wrong configuration,and failing at conversion level. so experts please help me to get the correct content conversion parameters.
note : ( * Nothing can be altered at repository side * ) and the fields are fixed in length so the file needs to be fixed lentgh format.
Tree--Occ--
TYPE
SBLSALDATA--1..1--
SBLSALDATA
SALDATA----
1..1
Headrec----
1..1
XXX----
1..1
XXX----
1..1
XXX----
1..1
TotalDatarec----
1..Unbounded
YYY----
1..1
YYY----
1..1
YYY----
1..1
YYY----
1..1
LASTREC----
1..1
ZZZ----
1..1
ZZZ----
1..1
Thanks in advance.I have done in the same procedure as in above link. its not working either.
My receiver structure looks like below.
<?xml version="1.0" encoding="UTF-8"?>
<ns1:TaxData xmlns:ns1="urn:XXXXXXXX">
<EmpTaxDat>
<Header>
<A/>
<B/>
<c/>
</Header>
<Detail>
<D/>
<e/>
<f/>
</Detail>
<Trail>
<g/>
<h/>
<i/>
</Trail>
</EmpTaxDat>
</ns1:TaxData>
Edited by: Harish.k on Jan 2, 2010 2:15 PM -
File Content Conversion in Receiver File Adapter
Hi Experts,
I got a requirement like "I have to read the below XML and convert into text file with '|' seperator".
Below is the XML structure.<Header> is 1..1 cardinality and <Item> is 0..n cardinality and <Response> is 0..1 cardinality.
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:Response xmlns:ns1="urn:test.com">
<Header>
<Header1>abc</Header1>
<Header2>def</Header2>
<Header3>ghi</Header3>
<Item>
<Item1>Item1Val1</Item1>
<Item2>Item1Val2</Item2>
</Item>
<Item>
<Item1>Item2Val1</Item1>
<Item2>Item2Val2</Item2>
</Item>
</Header>
<Response>
<Message>Some Values are Missing</Message>
<Status>E</Status>
</Response>
</ns1:Response>
I want to generate the file in the way that for every item one row should be generated and in every row the header(1..1) should get repeated.
And I don't want the response node in the file. I want to ignore it.The file structure should look like below:
abc | def | ghi | Item1Val1 | Item1Val2 |
abc | def | ghi | Item2Val1 | Item2Val2 |
Please let me know how the header should be repeated in every row. I need this very urgent.
Your help will be greatly appreciated.
Thanks,
SwapnikaHi Swapnika,
you have change your receiver message type as per your requirement.
for example
<Record>
</Header>
<item1>
<item2>
</Record>
in the mapping use OneAsMany node function to replicate the nodes.
http://****************/Tutorials/XI/NodeFunctions/Page5.htm
https://help.sap.com/saphelp_nw04/helpdata/en/ef/df564b6aa24fc9ab0d685460747de5/content.htm
Explain node functions - Process Integration - SCN Wiki
Then use FCC.
how do you want to convert
like this abc | def | ghi | Item1Val1 | Item1Val2 |
or like below
abc | Item1Val1 | Item1Val2 |
abc Item1Val1 | Item1Val2 |
abc | Item1Val1 | Item1Val2 |
Regards,
Muni. -
Regd file content conversion in receiver FTP adapter
Hi All,
I m trying to do FCC at receiver, i have to convert Idocxml in to a flat file.
Input structure is smthing like this:
MT_source
<Header>
<ZXw>test1<ZXw>
<ZYe>test2<ZYe>
<ZZR>test2<ZZR>
</Header>
<ZJDU>
<ZXd>xyz<ZXd>
<ZYE>wer<ZYE>
<ZZw>wer<ZZw>
</ZJDU>
I have to get the output as:
test1test2test2xyzwerwer..etc i mean to say i have not feildseparator and i have to revome all the tages in in put file and paste the only values in the output.Its like getting all the things in the same line.
it tried giving like . header.feildSeperater ""
ZJDU.feildseperater ""
I am very new to this,searched .. bt didnt get what to write when there is no feild seperator and i have to paste complete file in text format.
thanks
Anika> it tried giving like . header.feildSeperater ""
> ZJDU.feildseperater ""
>
I could see spelling mistate in the above line..... fieldSeparator
if the above setting didn't work. did u try with the running scripts after the adapter has finished it's job. You can replace the fieldSepartor with "" empty string.
Maybe you are looking for
-
Please help with the following error while downloading I-tunes version 9 on Windows business Vista. An error occurred during the installation of assembly 'Microsoft.VC80.CRT, version = "8.0.50727.4053" HR result 0x80070422
-
Have downloaded firefox update 3 times and it doesn't run
I have just started to use firefox on my pc which has windows 7. I keep getting a message saying I need to update the version of firefox, so I down load it and it says it is downloaded ( I now have it 3 times) but it doesn't run and still keepstellin
-
How to bring a .jpg into an open PSD file as a layer & smart object
Note: Posted in MAC section also. Goal: Using a script - Bring a .jpg an artist chooses, into Photoshop in an existing project into its own layer, and make it a smart object. This way, when the artist double-clicks on the smart object in Photoshop, i
-
Sorting /Grouping Issue: Single Artist Compilation Album Doesn't Group
iTunes 8 Sorting / Grouping Issue EXAMPLE • Album: Essential Willie Nelson • There are 22 songs on this Disc • 19 of them are labelled "Willie Nelson" in the artist field • 3 of them are lebelled "Willie Nelson Feat. Waylon Jennings" in the artist fi
-
Create a DVD movie using AVI clips stored on my I Book G4
I need to know how to create a movie to be read by any DVD player. I have my project set up as a I-movie project with I-Movie HD 5.0 but I don't know how to convert it. Using Magic Movie creator, it doesn't work because I have to camcorder connected