File transmission, file conversion in OS400

Hello Gurus,
We are sending the file from our Quality SAP to other AS400 server but we get an error.
From: SAP Quality as400
To: External server user SAPTEST
The file we are sending is SAP9530001_20100813from folder /usr/sap/Q00/INTERFACES/OUTBOUND/USSD002
Going to
External server user SAPTEST
SAP9530001_20100813 is a STMF format and according to the recipients they are expecting SAVE file that has a stream file in it.
Is there any way we can convert the file to SAV file that has a stream file in it? We used command CPYFRMSTMF but we ran a lot of errors. We just wanted to put the file in the library TESTISMS.
We use this command:
CPYFRMSTMF FROMSTMF('/usr/sap/Q00/INTERFACES/OUTBOUND/USSD002/SAP9530001_20100813') TOMBR('/QSYS.LIB/TESTIMSS.LIB/SAP9530001.file')
but it ended with error:
Owner of object SAP9530001 in TESTISMS type *FILE changed.
Incorrect record for output operation to save file
Object SAP9530001 in TESTISMS type *FILE deleted
Error writing to object.
Stream file not copied.
I would greatly appreciate your help. Thank you so much in advance.
BR,
Eco

If I understand your problem correctly, the following steps should help:
To convert a STMF into a SAVF that has a STMF in it, you must first save the stream file into the save file:
1. CRTSAVF FILE(<lib>/<savf>)
2. SAV DEV('/QSYS.LIB/<lib>.LIB/<savf>.FILE') OBJ('<stmf>')
Now you copy that save file into your outbound directory:
CPYTOSTMF FROMMBR('/QSYS.LIB/<lib>.LIB/<savf>.FILE') TOSTMF('/usr/sap/Q00/INTERFACES/OUTBOUND/USSD002')
Kind regards,
Christian Bartels.

Similar Messages

File Sender Content Conversion: Help needed

Hello Experts,
i need help with file sender content conversion:
i have a file which looks like this:
12329460 24.01.09/07:01 167     Y010122851 136086 43300007            E70115 1L2_96_1
12329660 25.01.09/07:02 157     Y010122851 136086 43390007            E711J5 1L2_96_1
as you can see 8 fields, separated with whitespaces
and i want and xml file which looks like this:
<DT_DATA_FILESENDER>
<Recordset>
      <Data>
        <field1>12329460</field1>
        <field2>24.01.09/07:01</field2>
        <field3>167</field3>
        <field4>Y010122851</field4>
        <field5>136086</field5>
        <field6>43300007</field6>
        <field7>E70115</field7>
        <field8>1L2_96_1</field8
     </Data>
      <Data>
        <field1>12329660</field1>
        <field2>25.01.09/07:02</field2>
        <field3>157</field3>
        <field4>Y010122851</field4>
        <field5>136086</field5>
        <field6>43390007</field6>
        <field7>E711J5</field7>
        <field8>1L2_96_1</field8
     </Data>
</Recordset>
Would you please let me know how the datatype has to look like?
And especially how the FCC has to be configured for this scenario?
Thanks in advance,
Chris

> With fixed lengths i get it working,
>
> but with de fieldseparator 0X09 it does not work,
> would you please tell me the complete FCC config not only the fieldSeparation line?
Well Christian,
There is one thing, eithere you can use fieldSeparator or fieldFixedLengths you can not use both together. So in your case do not use fieldSeparator.
The complete FCC is almost same as given in the blog in my previous reply. See the final output in that blog and create your data type accordingly. e.g.
Recordset
------Item 0...unbound
--------Field1 0..1
--------Field2 0..1
--------Field3 0..1
--------Field8 0..1
Regards,
Sarvesh

Problem with File CC filecontent conversion

Hi,
all
iam doing file content conversion scenarion .
following this blog
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
file->file
in my CC
adapter type: sender
Transport Protocol:FTP
msg protocol:File Content Conversion
Adapter Engine:IS
FTP PARAMETERS
SERVER:*****
PORT:****
connection mode:per file transfer
Transfer Mode:Text
folder:**
name:input.txt(shall i give csv file here)
CONTENT CONVERSION PARAMETERS
Document Name: (my msg type)
Document name space:http:
DOument Offset:
Recordset Name:record
Recordset Namespace:
RecordSet Structure:row,*
Recordsets per message:
keyfield name:
keyfiled type:string(case-sensitive)
row.fieldNames
row.fieldSeparator
row.processConfiguration
row.endSeparator
thnx in advance
regards
kumar

Hi Kumar,
Yes the input file will be a csv file.
Document name will be your message type name.
For more details refer to this link.
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Regards,
Sudheer.

File adapter content conversion

Hi all,
We are having File to File Scenario
We are facing problem in Content conversion in File
Adapter(Sender)
The source file is in text format and fields are
seperated by '|' character
The source file structure is :
Header|No. of Records
Data Record1
Data Record2
Data Recordn
Trailer|No. of Records
     where Data Recordn is of type Field1|Field2|Field3|Field4
     and the number of data records is variable
     e.g.
     Header|5
     2|144012|20050801|20050801
     212|012|20050801|20050801
     244012|2|20050801|20050801
     2144|144012|20050801|20050801
     212|012|20050801|20050801
     Trailer|5
Now , we need to ignore the contents of Header and Trailer Records
     For Header , we are setting the property Document Offset to 1
     Hence the Header record is ignored
     However , we are facing problems in ignoring the Trailer record
     We want to know :
     1. Is there a direct way ( or some propety ) wherein we can ignore the last record of the file ,
        which in this case is Trailer record
     2. We also tried the following :
          a. We set the Recordset Structure to : row,*,trailer,1
          b. However in this case , the keyField is required for row ;
             but since the number of data records is variable ,
             the keyFieldValue cannot be specified
       How should we go about in this case
Please guide us on this
Regards
Shikha

Hi all
Thanks for replies
Actually , we are able to ignore header and that is not an issue
Now if we need to discard the trailer record , we believe that RecordSet Structure should be <b>row,,trailer,1</b> or <b>header,1,row,,trailer,1</b>
However , since structure is <b>row,*</b> ; we need to specify the <b>keyField</b> column for row ( data records )
Since <u>number of data records</u> is variable , we are not able to set the <b>keyFieldValue</b> for <u>row ( data record )</u>
Can you'all please guide us on this as we are stuck on this .
Regards
Shikha
Message was edited by: Shikha Jain

File Content Conversion : File to File Scenario

hi all,
I have a Input file
It has the following structure:
<?xml version="1.0" encoding="utf-8"?>
<n0:rfc_proxy_message_type xmlns:n0="http://kpr.com/sample">
<Name>abhishek</Name>
<Age>10</Age>
</n0:rfc_proxy_message_type>
I use a File to File Scenario, with Sender and receiver FTP adapters.
I would like to convert this file at the recieveing end into a flat file as follows:
Name     Age
abhishek 10
How can I do so?
Can anyone please help.
Thanks,
Best Regards
Abhishek

Hi,
Your Xml file should be like this.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Employee_MT xmlns:ns0="http://sap.com/demo">
   <Recordset>
      <item>
         <Name>vinod</Name>
         <Id>12</Id>
         <Age>30</Age>
         <***>male</***>
      </item>
   </Recordset>
</ns0:Employee_MT>
In the content conversion parameters mention the following
Document name:    Student_MT
Document Namespace:   enter your namespace
RecordsetName:    Recordset
Recoedset Structure:   item,*
item.endSeparator = 'nl'
item.fieldSeparator= ,
item.fieldnames= Name,Id,Age,***
Hope this helps you.

...file Sender content conversion 'lastFieldsOptional' error

Hi All,
I am working on a File Sender content conversion--> flat file to XI.
it's fixed length field all the rows with same column.
090627 344535AFDFG+GBP65433 ASDSSD GFD dFSSGFD 6757532
090627 344535AFDFG-GBP65433 ASDSSD GFD dFSSGFD 6757532
090627 344535AFDFG-GBP65433 ASDSSD GFD dFSSGFD 6757532
090627 344535AFDFG-GBP65433 ASDSSD GFD dFSSGFD 6757532
090628 344536AFDFG+GBP45434 ASDSSD GFD dFSSGFD 6757532
090628 344536AFDFG-GBP45434 ASDSSD GFD dFSSGFD 6757532
**EOF**
I am sucessfully able to handle the file if i remove "**EOF*" from incoming file. But i get "lastfieldsOptional" error with "*EOF**"
>
Parameters-
     Recordset Structure - ROW,*
     Recordsets per message - *
    ROW.fieldFixedLengths - 6,8,20,10,30,1,3,1,11,1,11,6,10,10,20,10,10,2,6,6,2,6,6,3
    ROW.fieldNames - INV_DATE,INV_NO,PAYMENT_REF,CUST_NO,CUST_NAME...etc etc
   ignoreRecordsetName - true
There are parameters available to ignore Last field(last column) of a Row/Rocerdset
but how to ignore the last row of the file.
Plz suggest some parameter to ignore the last row/field of the file.
Regs,
Ansh

Ansh,
.lastFieldsOptional is obselete and you cannot use. Please see sap help:
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
The best thing comes to my mind is use:
.keepIncompleteFields as YES
Also give a try with:
.missingLastfields as add
So with this I think your last line in the file will read into XI. But the value of last line is **EOF**. So the length is 9. Since your the first two fixed lengths are 6 and 8. You will have these values as ***EOF and ***. So while mapping you can use doesnot satrt with * and map it, so that your last line will be ignored.
Note: with this apporach you have to make sure your first two columns never start with *. If you have a doubt then you can use the condition doesnot equal to ***EOF for first field and doesnot equal to *** for the second field when you map. I hope it makes sense to you.
Regards,
---Satish

File Adapter with Conversion - XML with Hierarchy?

XI 3.0 (SP9)
We are using the inbound file adapter with conversion to convert a flat file that has header and line items. I would have thought that the data type should have been setup something like this:
<data type>
<header>
<item>1</item>
<item>2</item>
</header>
</data type>
Our flat file looks like this:
H12345
I12345
We have only been able to configure the file adapter to bring in the data like this:
<data type>
<header></header>
<item>1</item>
<item>2</item>
</data type>
What is the proper way to inbound data through a file adapter that has structure conversion like this?
Do all of the elements get put under the root node, or is there a way to build structure?
Do we need to build the data type to correspond with the exact way that the data will come in from the file adapter?
Thanks
Peter

Not quite sure what you want to get, as the flatfile and xml structure does not contain the same values.
However, I will try to give you an example:
Your flat file looks like this:
H12345
I12345
If the first row is header and the next is a line, then you need to specify the fila adapter with the following:
Document name = datatype
Recordset name = recordset
Recordset structure = header,1,item,*
Recordsets per message = *
Recordset sequence = Ascending (need SP10 for this, but you do not need it for this)
Keyfieldname = id
header.fieldFixedLengths = 1,5
header.fieldNames = id,number
header.keyFieldValue = H
header.lastFieldsOptional = Yes
item.fieldFixedLengths = 1,5
item.fieldNames = id,number
item.keyFieldValue = H
item.lastFieldsOptional = Yes
This will create something like this:
<datatype>
<recordset>
<header>
<id>H</id>
<number>12345</number>
</header>
<item>
<id>I</id>
<number>12345</number>
</item>
</recordset>
</datatype>
Hoever, if both rows are "item" rows , then you need to specify the file adapter with the following:
Document name = datatype
Recordset name = header
Recordset structure = item,*
Recordsets per message = *
Recordset sequence = Ascending (need SP10 for this, but you do not need it for this)
item.fieldFixedLengths = 1,5
item.fieldNames = id,number
item.lastFieldsOptional = Yes
This will create something like this:
<datatype>
<header>
<item>
<id>H</id>
<number>12345</number>
</item>
<item>
<id>I</id>
<number>12345</number>
</item>
</header>
</datatype>
Q: Do we need to build the data type to correspond with the exact way that the data will come in from the file adapter?
A: Yes!
Good luck!

Problem in message mapping due to file sender content conversion

Hi all
basically i m using file sender content conversion and couldn't make file in a proper nested structure where weight was the nested field of detail as there is a limitation of content conversion in file adapter:
My file came out like this:
<header>
</header>
<Detail>
</Detail>
<Weight>
</Weight>
<Weight>
</Weight>
<Detail>
</Detail>
<Weight>
</Weight>
<Weight>
</Weight>
<trailer>
</trailer>
and i wanted it like:
<header>
</header>
<Detail>
<Weight>
</Weight>
<Weight>
</Weight>
</Detail>
<Detail>
<Weight>
</Weight>
<Weight>
</Weight>
</Detail>
<trailer>
</trailer>
so now the problem is i want to generate an idoc from it....but theres no way out to determine which weight is related to what detail except that the weight related to detail 1 comes after start and end of detail 1 tag and then weights of second detail comes after start and end of detail 2 tag in my source xml file.
The structure of the target idoc is
<header>
</header>
<Detail>
<Weight>
<flag>D1</flag>
</Weight>
<Weight>
<flag>D1</flag>
</Weight>
</Detail>
<Detail>
<Weight>
<flag>D2</flag>
</Weight>
<Weight>
<flag>D2</flag>
</Weight>
</Detail>
<trailer>
</trailer>
so i was wondering if i can make a user defined function in which i feed detail and weight and result a flag d1/ d2 inside the tag field. My logic is smth like
while detail is 1 make all the tag weights coming after detail 1 inside <detail1> tag then resultlist.CC for context change then while detail is 2 make a loop to fill the weight coming after detail 2 inside the <detail2>
Is this possible by any means. I really need help
Thnks
Naina

Hi
My sender file content conversion have this setting:
HEADER,1,DETAIL,*,Weights,*,TRAILER,*
And plz give me more idea of the adapter module ....is there any blog available which is related to my problem.
Naina

File content conversion (file to file)

Hi Guys,
Sender File
@! is the delimiter
LEVEL1@!227833338@!08710@!REPAIR@!20080101@!99990909@!0000212897@!0000000001000@!0000000500000@!R400@!A@!Assigned
LEVEL2@!227833338@!08710@!000099071608@!Blind@!20020115@!20020115@!R400@!1@!3@!20020430@!99990909@!SLC-@!VESSELLS@!A@!Assigned
LEVEL3@!227833338@!08710@!000099071608@!0010@!Blind@!20020115@!20020115@!20020430@!20020430@!10000414@!Assigned
LEVEL1@!4501065777@!00010@!SUPERHEAT@!20071206@!99990909@!0000219169@!00000001000@!0000002000000@!R020@!A@!Assigned
LEVEL2@!4501065777@!00010@!000009416742@!Alky@!20080107@!99990909@!R020@!E@!2@!20080101@!99990909@!LAT@!COKE@!A@!Assigned
LEVEL3@!4501065777@!00010@!000009416742@!0010@!v-895@!20080107@!99990909@!20080101@!99990909@!10001577@!Assigned
Sender Structure
<?xml version="1.0" encoding="UTF-8"?>
<ns0:CostObjects xmlns:ns0="http://*****************">
   <LEVEL1>
      <LevelID/>
      <PONumber>35435454</PONumber>
      <POLineNo>545</POLineNo>
      <ShortText>AAAAAAA</ShortText>
      <StDate>20080101</StDate>
      <EndDate>20080101</EndDate>
      <Vendor/>
      <POValue/>
      <ExpectedValue>4343</ExpectedValue>
      <Plant/>
      <Status>A</Status>
      <OrderType>Assigned</OrderType>
   </LEVEL1>
   <LEVEL2>
      <LevelID/>
      <PONumber>35435454</PONumber>
      <POLineNo>545</POLineNo>
      <Level2ID>457899</Level2ID>
      <Level2Desc>bbbbbbbbb</Level2Desc>
      <L2StDate>20080101</L2StDate>
      <L2EndDate>20080101</L2EndDate>
      <L2Plant>y001</L2Plant>
      <L2Priority>3</L2Priority>
      <L2SAPStatus>a</L2SAPStatus>
      <L2ActStDate>20080101</L2ActStDate>
      <L2ActEndDate>20080101</L2ActEndDate>
      <L2FuncLoc>LAR</L2FuncLoc>
      <L2FuncDesc>LOS ANGLES</L2FuncDesc>
      <L2Status>1</L2Status>
      <L2OrderType>Assigned</L2OrderType>
   </LEVEL2>
   <LEVEL3>
      <LevelID/>
      <PONumber>35435454</PONumber>
      <POLineNo>545</POLineNo>
      <Level2ID>457899</Level2ID>
      <Level3ID>10</Level3ID>
      <Level3Desc>cccccccc</Level3Desc>
      <L3StDate>20080101</L3StDate>
      <L3EndDate>20080101</L3EndDate>
      <L3ActStDate>20080101</L3ActStDate>
      <L3ActEndDate>20080101</L3ActEndDate>
      <L3WorkCenter>los</L3WorkCenter>
      <L3OrderType>Assigned</L3OrderType>
   </LEVEL3>
</ns0:CostObjects>
Receiver Structure
<?xml version="1.0" encoding="UTF-8"?>
<ns0:TCostObject xmlns:ns0="http://**************">
   <LEVEL1>
      <L1RecordIndicator><L1></L1RecordIndicator>
      <L1ID>35435454545</L1ID>
      <L1Desc>AAAAAAA</L1Desc>
      <L1StartDate>20080101</L1StartDate>
      <L1EndDate>20080101</L1EndDate>
      <L1Hours>0</L1Hours>
      <L1Costs>4343</L1Costs>
      <L1Status>A</L1Status>
      <L1OrderType>Assigned</L1OrderType>
   </LEVEL1>
   <LEVEL2>
      <L2RecordIndicator><L2></L2RecordIndicator>
      <L1ID>35435454545</L1ID>
      <L2ID>457899</L2ID>
      <L2Desc>bbbbbbbbb</L2Desc>
      <L2StartDate>20080101</L2StartDate>
      <L2EndDate>20080101</L2EndDate>
      <L2Hours>0</L2Hours>
      <L2Costs>0</L2Costs>
      <L2OrderType>Assigned</L2OrderType>
      <L2Plant>y001</L2Plant>
      <L2Priority>3</L2Priority>
      <L2SAPStatus>a</L2SAPStatus>
      <L2CostObject/>
      <L2CostObjectDesc/>
      <L2ActStartDate>20080101</L2ActStartDate>
      <L2ActEndDate>20080101</L2ActEndDate>
      <L2AreaID>01</L2AreaID>
      <L2FuncLoc>LAR</L2FuncLoc>
      <L2FuncLocDesc>LOS ANGLES</L2FuncLocDesc>
      <L2UnitName/>
      <L2MaintCatCode/>
      <L2MiscInfo1/>
      <L2MiscInfo2/>
      <L2SAPExempt/>
      <L2ShortWorkOrderID/>
      <L2Status_AorI>1</L2Status_AorI>
      <L2LaborTaxFlag/>
      <L2EquipTaxFlag/>
      <L2MaintTaxFlag/>
   </LEVEL2>
   <LEVEL3>
      <L3RecordIndicator><L3></L3RecordIndicator>
      <L1ID>35435454545</L1ID>
      <L2ID>457899</L2ID>
      <L3ID>10</L3ID>
      <L3Desc>cccccccc</L3Desc>
      <L3PlanStartDate>20080101</L3PlanStartDate>
      <L3PlanEndDate>20080101</L3PlanEndDate>
      <L3ActStartDate>20080101</L3ActStartDate>
      <L3ActEndDate>20080101</L3ActEndDate>
      <L3OrderType>Assigned</L3OrderType>
      <L3WorkCenter>los</L3WorkCenter>
      <L3WorkAmtScheduled/>
      <L3UnitofWork/>
      <L3DurationScheduled/>
      <L3UnitofDuration/>
      <L3NoofEmp/>
   </LEVEL3>
</ns0:TCostObject>
The receiver file look more or less the same as sender file but with delimiter @# and the fields are different
<L1>@#...........
<L2>@#..........
<L3>@#............
<L1>@#...........
<L2>@#..........
<L3>@#............
Sender file adapter content conversion:
LEVEL1.fieldNames     LevelID,PONumber,POLineNo,ShortText,StDate,EndDate,Vendor,POValue,ExpectedValue,Plant,Status,OrderType
LEVEL1.fieldSeparator     @!
LEVEL1.endSeparator     'nl'
LEVEL1.processFieldNames     fromConfiguration
LEVEL1.keyFieldValue     LEVEL1
LEVEL2.fieldNames     LevelID,PONumber,POLineNo,Level2ID,Level2Desc,L2StDate,L2EndDate,L2Plant,L2Priority,L2SAPStatus,L2ActStDate,L2ActEndDate,L2FuncLoc,L2FuncDesc,L2Status,L2OrderType
LEVEL2.fieldSeparator     @!
LEVEL2.endSeparator     'nl'
LEVEL2.processFieldNames     fromConfiguration
LEVEL2.keyFieldValue     LEVEL2
LEVEL3.fieldNames LevelID,PONumber,POLineNo,Level2ID,Level3ID,Level3Desc,L3StDate,L3EndDate,L3ActStDate,L3ActEndDate,L3WorkCenter,L3OrderType
LEVEL3.fieldSeparator     @!
LEVEL3.endSeparator     'nl'
LEVEL3.processFieldNames     fromConfiguration
LEVEL3.keyFieldValue     LEVEL3
ignoreRecordsetName     true
Receiver Adapter content conversion:
LEVEL1.fieldSeparator     @#
LEVEL2.fieldSeparator     @#
LEVEL3.fieldSeparator     @#
LEVEL1.endSeparator     'nl'
LEVEL2.endSeparator     'nl'
LEVEL3.endSeparator     'nl'
The file is not being picked up.I am sure sender file adapter is correct as I have used this for (file to soap) and the scenario works file.I am not sure of receiver file adapter,do we have to use adavanced mode in receiver file adapter?Can you guys plz help me.Let me know if you have any questions
Thanks

Can someone let me know what are the parameters to give in FCC receiver file adapter.
Thanks

File sender content conversion

hello
I have a txt file sender content conversion in SAP PI.
I define in the content conversion 6 fields names(field1, field2, field3,field4,field5,field 6) but the fie that I am loading has only three field(field1,field2,field3). the file is still loading though there is a different in the structure between what I define in the PI to what is loading to the PI.
is there a way to send an error with out loading the file?
I read about the count function in the mapping. isnt there a build in function that suppose to load only the structure that is define?
Thanks
Kfir

If you define 6 fields and only 3 are present in the test file then you wont get an error (AFAIK)
However, if you define 3 fields and there are 6 present in the source file then you will get an error saying more number of parameters found.
isnt there a build in function that suppose to load only the structure that is define?
I dont think so....this may however be achieved using a custom adapter module.
Update:
Just remembered that SAP PI (7.1 and above) comes with inbuilt XML-validation function....check if that helps in your design.
Regards,
Abhishek.
Edited by: abhishek salvi on Dec 15, 2010 1:12 PM

File to File scenario, file content conversion

HI there,
I am facing this scenario, flat file -> XI -> flat file. Files are fixed length ones and .txt.
the structure of the incoming file is something like:
field1field2field3field4
field1field2field3field4field5
That means that there is no separation between fields (neither comma nor space) and there are optional fields that may appear or not.
My aim is to transform this file into another file, XI will do some maps with some fields but the rest will be the same (same fieldnames and same field lengths). So, the outcoming file should be similar as the incoming one:
field1field2field3field4(transformed)
field1field2field3field4field5
These are my FCC parameters (i think i have to use FCC):
Row.fieldNames= field1,field2,field3....
Row.fieldFixedLengths=1,3,4....
Row.processConfiguration=FromConfiguration
Row.endSeparator='nl'
...and my data type structure:
DT_XX
Record
     Row
       field1
       field2
Here are my questions:
I have configurated the file content conversion in sender and receiver adapter, are they both necessary or should i only configurate the sender??
How can i manage the fields that are not mandatory?
What should be the transfer mode, binary or text?
I am a new come in development so, could anyone of you please give some support??
Thanks in advance and kind regards,
David

Hi David,
I have configurated the file content conversion in sender and receiver adapter, are they both necessary or should i only configurate the sender??
YES.
Suppose you only confgure it for sender then the target file that is generated will be in XML format.
How can i manage the fields that are not mandatory?
If the inbound structure has less fields than specified in the configuration then the XML outbound structure the you can set
Row.missingLastfields = ignore / add / error
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
What should be the transfer mode, binary or text?
If it is a txt file then text and set code page as UTF-8else binary.
<b>Cheers,
*RAJ*</b>

Challenge in File Sender Content Conversion

Hi,
I have a real challenge concerning File Sender content conversion in SAP XI.
My flat file looks like this:
##H   300
MAR   206
KAS 1
DAT 01.03.08
ART 1.129
KUN 118
EAN 4.499
REL 5.0j 16.05.06
SER             1
##E   300
##H   301
DAT 01.03.08
ZEI 07:54
KAS 1
##E   301
Each row represents a data field and has two values: The first one defines the field name, the second represents the field value. E.g. 'DAT' stands for Date and has the value 01.03.08 in the example.
The fields belonging together in one data set are enclosed by a start qualiefier (##H)and an end qualifier (##E).
The value after these qualifiers (i.e. '300' and '301' in the example above) represent a certain record type, e.g. '300' represents Customer data and '301' represents Account Data.
Is it possible with file content conversion to create the following XML structure:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_DATA xmlns:ns0="http://sap.com/xi/account">
     <300>
          <MAR>206</MAR>
          <KAS>1</KAS>
          <DAT>01.03.08</DAT>
          <ART>1.129</ART>
          <KUN>118</KUN>
          <EAN>4.499</EAN>
          <REL>5.0j 16.05.06</REL>
          <SER>1</SER>
     </300>
     <301>
          <DAT>01.03.08</DAT>
          <ZEI>07:54</ZEI>
          <KAS>1</KAS>
     </301>
</ns0:MT_DATA>
If it is not possible with content conversion, what could be an alternative? Adapter Module? MultiMapping?
I'd really appreciate your input as I am working on this since several days without a solution.
Thanks in advance.
Alex

It is not possible thru adapter..
There is one blog to convert such files to XML sing java mapping. Search for any flat file to Idoc or xml in the forum.
VJ

File sender content conversion 0..unbounded does not pull file

i am trying to map a flat file using content conversion to this xml structure:
<Header>
<Field_ID/>
<Filler/>
<Record_type/>
<File_name/>
<File_date/>
<File_time/>
<Heb_code/>
<Claim_no/>
<Cont_no/>
<Remark/>
</Header>
<Claim_Header>
<Field_ID/>
<Filler/>
<Record_type/>
<Vendor_code/>
<Garage_no/>
<Data_code/>
<Year/>
<Job_no/>
<Cont_no/>
<License_no/>
<ODO_meter/>
<Claim_type/>
<VIN_code/>
<Claim_open_date/>
<Claim_fix_date/>
<N_code/>
<C_code/>
<Ejob1/>
<Ejob2/>
<Page_no/>
<Pre_conf_date/>
<Pre_conf_no/>
<Part_buy_date/>
<KM_prev_fix/>
<Bill_prev_fix/>
<Material_fault/>
<Damage_whole/>
<Damage_code/>
<Job_amount/>
<Towing_amount/>
<Parts_amount/>
<Hour_rate/>
<Cont_mark/>
</Claim_Header>
<job_row>
<Field_ID/>
<Filler/>
<Record_type/>
<Vendor_code/>
<Garage_no/>
<Data_code/>
<Year/>
<Job_no/>
<Cont_no/>
<page_no/>
<line_no/>
<shaaton_code/>
<job_finish_code/>
<amount/>
<job_time/>
<row_value/>
<color_code/>
</job_row>
<part_row>
<Field_ID/>
<Filler/>
<Record_type/>
<Vendor_code/>
<Garage_no/>
<Data_code/>
<Year/>
<Job_no/>
<Cont_no/>
<page_no/>
<line_no/>
<material_code/>
<amount/>
<unit_price/>
<row_value/>
</part_row>
<remark>
<Field_ID/>
<Filler/>
<Record_type/>
<Vendor_code/>
<Garage_no/>
<Data_code/>
<Year/>
<Job_no/>
<Cont_no/>
<page_no/>
<line_no/>
<remark/>
</remark>
<footer>
<Field_ID/>
<Filler/>
<Record_type/>
<File_name/>
<File_Record_no/>
<Claim_no/>
<Cont_no/>
<Remark/>
</footer>
job_row, part_row and remark are records that occur 0..unbounded.
when i write in recordset structure: Header,1,Claim_Header,1,Job_Row,1,Part_Row,1,Remark,1,Footer,1
and put file with one record each, the file is pulled, but when i change recordset structure to:
Header,1,Claim_Header,1,Job_Row,* ,Part_Row,* ,Remark,*,Footer,1
the file is not pulled.
can anyone tell me what i'm doing wrong?
thanx
Tomer

Hi,
Refer this links for FCC.
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)
File Receiver with Content Conversion
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
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)
How to send a flat file with various field lengths and variable substructures to XI 3.0
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
File Content Conversion for Unequal Number of Columns
Content Conversion ( The Key Field Problem )
The specified item was not found.
File Receiver with Content Conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani

Flat files to XML conversion module?

Hi Experts,
I would like to know from where I can have free download for flat files to XML conversion module which I can test in development server. Your help will be well appreciated.
Thanks and Regards,
Praveen.

u have file adapter with FCC which does the flat file to XML conversion. wat is ur requirement?
refer the help or search on SDN for file content conversion.
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
few examples:-
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Key value:
How to send a flat file with various field lengths and variable substructures to XI 3.0
File Receiver with Content Conversion
chirag

Sorting the file in file content conversion.

Hi all,
we have a file(xml)-pi-file(flat file) scenario,
where we need to sort the output file by employee id field.
Where can we achieve the sorting of file by particular field.
Do we have any option in Mapping(Functions) ??
Any option is Reciever File Adapter??
Reciever File content conversion??
Any inputs will be of gr8 help.
Regards.
santosh.

Hello,
Where can we achieve the sorting of file by particular field.
Do we have any option in Mapping(Functions) ??
Yes, there is a function in message mapping called sort and sortByKey, these can be found under node functions. To sort the ID, you can use this code
ID --> removeContext --> sort:(ascending or descending) --> ID
Use sortByKey to sort the additional details of the flatfile according to ID number e.g.
ID --> removeContext --> sortByKey:(ascending or descending) --> IDDetails
Details --> removeContext --> /
Any option is Reciever File Adapter??
Reciever File content conversion??
The receiver file adapter with FCC only converts the structure that is defined in your target message type into, say for example a text file. You have to do the manipulations in the message mapping.
Hope this helps,
Mark

File transmission, file conversion in OS400

Similar Messages

Maybe you are looking for