Fixed Length Flat File

I am working on creating a fixed length flat file with data from multiple files.
This flat file will have 4 different record formats.
My idea is to create a table for each one of these record formats, populate it in my PL/SQL program and utilize the [DUMP_CSV|http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:95212348059] procedure to then select from each of these tables. My idea is that if the record format changes it could be as simple as altering the table, and recompiling the program. Suggestions/comments on my approach?
Thanks

Use External Tables. By that you can even skip the PL/SQL code that you may need to write if you use normal table to load them.

Similar Messages

How to create Fixed Length Flat File from Open Hub in BI 7.0

My requirement is to produce a Fixed length Flat file by Open Hub destination. My Open Hub has four fields. Now the requirement is to create another extra field in Open Hub which will contain all of the four fields value. In addition to that the fields should be fixed length that means if for any field no value is there and the field length/type is CHAR4 then 4 spaces should be there as the field value. SO, basically the Open Hub output will be single field which will contain information of four fields.
How to get this using End Routine of Transformation (from DSO to Open Hub) ?

Hi,
You can map the four input fields to the new field in the Open Hub, and change rule type to "Routine".
For example, if your source fields are called "first", "second", "third" and "forth", the ABAP routine could be similar to:
DATA: l_t_1 TYPE C LENGTH 4,
      l_t_2 TYPE C LENGTH 4,
      l_t_3 TYPE C LENGTH 4,
      l_t_4 TYPE C LENGTH 4.
IF source_fields-first IS INITIAL.
l_t_1 = '    '.
else.
MOVE source_fields-first TO l_t_1.
endif.
IF source_fields-second IS INITIAL.
l_t_2 = '    '.
else.
MOVE source_fields-second TO l_t_2.
endif.
IF source_fields-third IS INITIAL.
l_t_3 = '    '.
else.
MOVE source_fields-third TO l_t_3.
endif.
IF source_fields-forth IS INITIAL.
l_t_4 = '    '.
else.
MOVE source_fields-forth TO l_t_4.
endif.
CONCATENATE l_t_1 l_t_2 l_t_3 l_t_4 into result.
In the example, the program uses four blank spaces if any of the fields has no value.
Additionally, if non-initial values in input fields could be shorter than 4 characters (if the input fields have no fixed length), you could use STRLEN to evaluate if it is necessary to add blank spaces to complete the fixed length of 4.
I hope this helps you.
Regards,
Maximiliano

Conversion of fixed length flat files to oracle table

hello friends
Please help me getting the code for conversion of fixed length flat files to oracle table
Should the tables be pre-defined ?????
In this case the de-limiters are variable length spaces and not commas.Please help me with the same
Regards,
-Mahesh

You can use SQL*Loader to load fixed-width files into Oracle. Instructions on writing appropriate control files are in the Oracle Utilities manual
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96652/ch03.htm#1004687
You can also use external tables, assuming you're using 9i or later (the syntax for external table definitions is nearly identical to the syntax for SQL*Loader control files).
You'll need to create a table definition in Oracle. You can either create a "normal" table and use SQL*Loader to populate it or you can create an external table definition.
Justin

Problem while writing to fixed length flat file from xml

Hi,
I have a problem in writing data into a flat file of fixed length...
My input is a xml file and i want the output as a flat file. I am successful in converting the xml into flat file... But the main problem is, i am unable to insert spaces in between my fields in the flat file.
The data in the flat file comes without spaces... Any suggestions on writing the schema...
Regards
Surya.

Have a look at this doc
http://otndnld.oracle.co.jp/document/products/as10g/101310/doc_cd/integrate.1013/b28994/nfb.htm#BGBBAJFD
your element should be something like this, it pads with a space using the paddedBy expression
<xsd:element name="C1" type="xsd:string" nxsd:style="fixedLength" nxsd:length="4" nxsd:paddedBy=" " nxsd:padStyle="tail" />if having trouble post what you want the file to look like, and the xsd you are using.
cheers
James

Java value objects to fixed-length flat file?

I am searching for framework or third party API, which can convert a java bean to fixed length record.
I want to automate this solution, using some mapping files. (Like hibernate API for java <----> xml conversions)
if anybody can give me any url or suggest ways, i would appreciate that...
thanks
ashish

But as business requirements change or new
integration happens.. it is possible, You can count on it.
java beans get
more data elements.. so i want solution which is
flexible easy to change or experiment ..during
development and after being deployed. I would create two classes for representing the copybook layout. One for the whole thing and another for each element. Each field will have the length type and any special formatting rules. i.e. you will have mutiple types of field classes implementing the Field interface. Then put these in a LinkedHashMap and as you are adding them set another field which will be the offset from the beiginning of the record. The Record class will hold these Fields and other Records.
Then create a schema text file format and load that in on startup. Then you buld the data like a you would a DOM model in your application.
I wish someone had done that in our code instead of copying, pasting and editing this:
int length = 10;
int offset = 500;a bazillion times. That's real fun when you want to add fields. The damn methods aren't even in consecutive order.

Require script to load fixed length flat file

Hi
Can anyone provide me a script to load a flat file into database ? A sample script would be ok
thanks in advance
Siva

You can use SQL*Loader to do this, or external tables in 9i or higher. These methods are well-documented in the Utilities Guide.
Cheers, APC

Exporting Crystal .rpt to a fixed length text file

Post Author: jnesbitt
CA Forum: Exporting
I am attempting to write a Crystal report that formats data to be exported to a fixed length text file. Each record will be made up of a number of fields with specific start locations and lengths. Is there any way to set the field start position and field length. I've been able to adjust the character per inch text export parameter to get close, but I can't update the paramete any longer.
How can I reset the "Characters per inch" text export parameter?
Version: Crystal 9.2

Hi Jakob
Take a look a this
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/edc2f3c2-0401-0010-8898-acd5b6a94353
Regards
DV

Download data to Fixed Length Text File

Can anyone share the sample code on how to download data into fixed length text file and place the file in the server directory?

One way i would advice is to declare a text variable and move values using offset.
Eg:
move: <struc>-fld1 to l_text(8),
<struc>-fld2 to l_text+8(3),
<struc>-fld3 to l_text+11(15).
transfer l_text to <file>.
Try this approch and see the result.
Kind Regards
Eswar

Is there a way to change fixed width Flat file connection manager to delimited without losing all the column names ?

Is there a way to change fixed width Flat file connection manager to delimited without losing all the column names ?

Unfortunately not as it is a quite dramatic change causing the metadata being refreshed. I would try to open though the package file in a text editor and find them before doing the change, then after you made the change to the FF connector try to reconstitute
/ replace the autimatically generated columns with the old names.
Arthur
MyBlog
Twitter

How to add line breaks to output fixed width flat file

0
I need to create a Flat file without column headers, no comma separated values but each column will have a fixed starting position and a fixed length in the text file. For example, below is the text file to be created with six columns
Column1 Column2   Column3     Column4 Column5      Column6
abc          1             New emp      xxxx         xxxx
xxx
Fixed starting position and a fixed lenth values for these columns as are below;
Column1 : Starting Position -1, Fixed Length -4
Column2 : Starting Position - 8, Fixed Length - 2
Column3 : Starting Postion - 11, Fixed Length - 10
Column4 : Starting Position -1, Fixed Length -5
Column5 : Starting Position - 10, Fixed Length - 2
Column6 : Starting Postion - 15, Fixed Length - 5
The out put file each line have only 20 characters length.First 3 columns comes in first line and 4-6 columns comes in 2nd line.
OUTPUT FILE:
1234   89 11121314151617181920
12345    1011         151617181920

BOL says that:
The Fixed width with row delimiters option is not available in the Flat File Connection Manager Editor.
If necessary, you can emulate this option in the editor. To emulate this option, on the General page of the Flat File Connection Manager
Editor, for Format, select Ragged right. Then on the Advanced page
of the editor, add a new dummy column as the final column of data.
More details steps:
http://www.coderewind.com/2012/08/ssis-how-to-include-rowdelimiter-with-destination-flat-files/
Below blog should make things clear:
SSIS Flat File Export - "Fixed Width" vs "Ragged Right"
-Vaibhav Chaudhari

Loading "fixed length" text files in UTF8 with SQL*Loader

Hi!
We have a lot of files, we load with SQL*Loader into our database. All Datafiles have fixed length columns, so we use POSITION(pos1, pos2) in the ctl-file. Till now the files were in WE8ISO8859P1 and everything was fine.
Now the source-system generating the files changes to unicode and the files are in UTF8!
The SQL-Loader docu says "The start and end arguments to the POSITION parameter are interpreted in bytes, even if character-length semantics are in use in a datafile....."
As I see this now, there is no way to say "column A starts at "CHARACTER Position pos1" and ends at "Character Position pos2".
I tested with
load data
CHARACTERSET AL32UTF8
LENGTH SEMANTICS CHARACTER
replace ...
in the .ctl file, but when the first character with more than one byte encoding (for example ü ) is in the file, all positions of that record are mixed up.
Is there a way to load these files in UTF8 without changing the file-definition to a column-seperator?
Thanks for any hints - charly

I have not tested this but you should be able to achieve what you want by using LENGTH SEMANTICS CHARACTER and by specifying field lengths (e.g. CHAR(5)) instead of only their positions. You could still use the POSITION(*+n) syntax to skip any separator columns that contain only spaces or tabs.
If the above does not work, an alternative would be to convert all UTF8 files to UTF16 before loading so that they become fixed-width.
-- Sergiusz

Configuring unicode charcterset for fixed length control file

Hi all,
we are setting our control file to support any language characters while data loading, we all set with our database configuration , need to configure our control file which is fixed length, we are using CHARACTERSET UTF8 and and also tried with CHARACTERSET AL32UTF16, its working fine for variable length control file but for fixed length the foriegn charecers like latin-I,greek, danish charactrers are taking more byte and affecting to next position data. and our data file is in UTF8 (not in regular ANSI formatt).
please advise
here is our control file example:
options (errors=999,SKIP=0)
Load DATA
CHARACTERSET UTF8
append
INTO TABLE TABLE_NAME
TRAILING NULLCOLS
field_name1 position(1:30) "trim(:fiels_name1)",
field_name2 position(247:306) "trim(:field_name2)",
)

I think you should move thread to: {forum:id=732}.

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 Fixed Length File issue

Hi,
I have a fixed length flat file with each row 13 characters long. First character of each row represents a record type i.e. 0,1,2,3,4,5,6,7,8,9 here is my sample file:
0123456
960373
A602710542583
7602710542583
1602750499275
4602750499275
1602750529800
7602750529800
1603030507732
7603030507732
1603030509055
7603030509055
1603030509229
7603030509229
2603600556240
0603600566095
2603600567460
3603310536370
5603310525810
3603310531092
3603310521842
0603310521842
3603310521842
3603310521842
860201450SA A
560201451SA A
560201452SA A
560201453SAN
1603630565355
7603630565355
1603630565500
7603630565500
9603460539390
2603460535260
3603790509870
560200401ABIL
660372TX066
660373TX01531
660373TX01532
860373TX066
660373TX068
360373TX09465
660373TX09471Here is the schema
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://xmlns.oracle.com/pcbpel/tstSchema/SMP" xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd" targetNamespace="http://xmlns.oracle.com/pcbpel/tstSchema/SMP" elementFormDefault="qualified" attributeFormDefault="qualified" nxsd:version="NXSD" nxsd:stream="chars">
     <element name="SMP">
          <complexType>
               <choice maxOccurs="unbounded" nxsd:choiceCondition="fixedLength" nxsd:length="1">
                    <element ref="tns:smpRecords" nxsd:conditionValue="0" minOccurs="0" maxOccurs="unbounded"/>
                    <element ref="tns:smpRecords" nxsd:conditionValue="1" minOccurs="0" maxOccurs="unbounded"/>
                    <element ref="tns:smpRecords" nxsd:conditionValue="2" minOccurs="0" maxOccurs="unbounded"/>
                    <element ref="tns:smpRecords" nxsd:conditionValue="3" minOccurs="0" maxOccurs="unbounded"/>
                    <element ref="tns:smpRecords" nxsd:conditionValue="4" minOccurs="0" maxOccurs="unbounded"/>
                    <element ref="tns:smpRecords" nxsd:conditionValue="5" minOccurs="0" maxOccurs="unbounded"/>
                    <element ref="tns:smpRecords" nxsd:conditionValue="6" minOccurs="0" maxOccurs="unbounded"/>
                    <element ref="tns:smpRecords" nxsd:conditionValue="7" minOccurs="0" maxOccurs="unbounded"/>
                    <element ref="tns:smpRecords" nxsd:conditionValue="8" minOccurs="0" maxOccurs="unbounded"/>
                    <element ref="tns:smpRecords" nxsd:conditionValue="9" minOccurs="0" maxOccurs="unbounded"/>
               </choice>
          </complexType>
     </element>
     <element name="smpRecords" type="tns:smpRecordsType"/>
     <complexType name="smpRecordsType">
          <sequence>
               <element name="data1" type="string" nxsd:style="fixedLength" nxsd:length="2" nxsd:padStyle="tail" nxsd:paddedBy=" "/>
               <element name="data2" type="string" nxsd:style="fixedLength" nxsd:length="3" nxsd:padStyle="tail" nxsd:paddedBy=" "/>
               <element name="emp" type="string" nxsd:style="terminated" nxsd:terminatedBy="${eol}"/>
          </sequence>
     </complexType>
</schema>When I run the process I get the following output and that is not correct as the first character is also being shown in the output as opposed to be skipped as it is the record type and the output should start from second character.
output
<SMP>
<smpRecords>
<data1>12</data1>
<data2>345</data2>
<emp>6 </emp>
</smpRecords>
<smpRecords>
<data1>96</data1>
<data2>037</data2>
<emp>3 </emp>
</smpRecords>
<smpRecords>
<data1>A16</data1>
<data2>027</data2>
<emp>10542583</emp>
</smpRecords>
<smpRecords>
<data1>76</data1>
<data2>027</data2>
<emp>10542583</emp>
</smpRecords>
<smpRecords>
<data1>16</data1>
<data2>027</data2>
<emp>50499275</emp>
</smpRecords>
<smpRecords>
<data1>46</data1>
<data2>027</data2>
<emp>50499275</emp>
</smpRecords>
<smpRecords>
<data1>16</data1>
<data2>027</data2>
<emp>50529800</emp>
</smpRecords>
<smpRecords>
<data1>76</data1>
<data2>027</data2>
<emp>50529800</emp>
</smpRecords>
<smpRecords>
<data1>16</data1>
<data2>030</data2>
<emp>30507732</emp>
</smpRecords>
<smpRecords>
<data1>76</data1>
<data2>030</data2>
<emp>30507732</emp>
</smpRecords>
<smpRecords>
<data1>16</data1>
<data2>030</data2>
<emp>30509055</emp>
</smpRecords>
<smpRecords>
<data1>76</data1>
<data2>030</data2>
<emp>30509055</emp>
</smpRecords>
<smpRecords>
<data1>16</data1>
<data2>030</data2>
<emp>30509229</emp>
</smpRecords>
<smpRecords>
<data1>76</data1>
<data2>030</data2>
<emp>30509229</emp>
</smpRecords>
<smpRecords>
<data1>26</data1>
<data2>036</data2>
<emp>00556240</emp>
</smpRecords>
<smpRecords>
<data1>06</data1>
<data2>036</data2>
<emp>00566095</emp>
</smpRecords>
<smpRecords>
<data1>26</data1>
<data2>036</data2>
<emp>00567460</emp>
</smpRecords>
<smpRecords>
<data1>36</data1>
<data2>033</data2>
<emp>10536370</emp>
</smpRecords>
<smpRecords>
<data1>56</data1>
<data2>033</data2>
<emp>10525810</emp>
</smpRecords>
<smpRecords>
<data1>36</data1>
<data2>033</data2>
<emp>10531092</emp>
</smpRecords>
<smpRecords>
<data1>36</data1>
<data2>033</data2>
<emp>10521842</emp>
</smpRecords>
<smpRecords>
<data1>06</data1>
<data2>033</data2>
<emp>10521842</emp>
</smpRecords>
<smpRecords>
<data1>36</data1>
<data2>033</data2>
<emp>10521842</emp>
</smpRecords>
<smpRecords>
<data1>36</data1>
<data2>033</data2>
<emp>10521842</emp>
</smpRecords>
<smpRecords>
<data1>86</data1>
<data2>020</data2>
<emp>1450SA A</emp>
</smpRecords>
<smpRecords>
<data1>56</data1>
<data2>020</data2>
<emp>1451SA A</emp>
</smpRecords>
<smpRecords>
<data1>56</data1>
<data2>020</data2>
<emp>1452SA A</emp>
</smpRecords>
<smpRecords>
<data1>56</data1>
<data2>020</data2>
<emp>1453SAN </emp>
</smpRecords>
<smpRecords>
<data1>16</data1>
<data2>036</data2>
<emp>30565355</emp>
</smpRecords>
<smpRecords>
<data1>76</data1>
<data2>036</data2>
<emp>30565355</emp>
</smpRecords>
<smpRecords>
<data1>16</data1>
<data2>036</data2>
<emp>30565500</emp>
</smpRecords>
<smpRecords>
<data1>76</data1>
<data2>036</data2>
<emp>30565500</emp>
</smpRecords>
<smpRecords>
<data1>96</data1>
<data2>034</data2>
<emp>60539390</emp>
</smpRecords>
<smpRecords>
<data1>26</data1>
<data2>034</data2>
<emp>60535260</emp>
</smpRecords>
<smpRecords>
<data1>36</data1>
<data2>037</data2>
<emp>90509870</emp>
</smpRecords>
<smpRecords>
<data1>56</data1>
<data2>020</data2>
<emp>0401ABIL</emp>
</smpRecords>
<smpRecords>
<data1>66</data1>
<data2>037</data2>
<emp>2TX066 </emp>
</smpRecords>
<smpRecords>
<data1>66</data1>
<data2>037</data2>
<emp>3TX015 </emp>
</smpRecords>
<smpRecords>
<data1>66</data1>
<data2>037</data2>
<emp>3TX01531</emp>
</smpRecords>
<smpRecords>
<data1>66</data1>
<data2>037</data2>
<emp>3TX01532</emp>
</smpRecords>
<smpRecords>
<data1>86</data1>
<data2>037</data2>
<emp>3TX066 </emp>
</smpRecords>
<smpRecords>
<data1>66</data1>
<data2>037</data2>
<emp>3TX068 </emp>
</smpRecords>
<smpRecords>
<data1>36</data1>
<data2>037</data2>
<emp>3TX09465</emp>
</smpRecords>
<smpRecords>
<data1>66</data1>
<data2>037</data2>
<emp>3TX09471</emp>
</smpRecords>
</SMP>As the output for the very first row comes up fine i.e. 0123456
for this the output is
<smpRecords>
<data1>12</data1>
<data2>345</data2>
<emp>6 </emp>
</smpRecords>But for all the rest it keeps adding the first character too i.e. 960373
for this the output is wrong
<smpRecords>
<data1>96</data1>
<data2>037</data2>
<emp>3 </emp>
</smpRecords>as the correct output should be:
<smpRecords>
<data1>60</data1>
<data2>373</data2>
<emp/>
</smpRecords>Any idea what I am doing wrong or how I can fix the schema. Also if I add any character other than 0....9 for the first character it still picks up the record i.e. A602710542583
as it should only process records starting with 0....9
Thanks

I tried using transformation to check if the starting 2 chars are 56 then output else continue but the ourput is blank even though I have multiple records that start with 56. Here is the xsl I have
<?xml version="1.0" encoding="UTF-8" ?>
<?oracle-xsl-mapper

<mapSources>
    <source type="XSD">
      <schema location="test2.xsd"/>
      <rootElement name="SMP" namespace="http://xmlns.oracle.com/pcbpel/tstSchema/SMP"/>
    </source>
</mapSources>
<mapTargets>
    <target type="XSD">
      <schema location="test2.xsd"/>
      <rootElement name="SMP" namespace="http://xmlns.oracle.com/pcbpel/tstSchema/SMP"/>
    </target>
</mapTargets>

?>
<xsl:stylesheet version="1.0" xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap" xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:tns="http://xmlns.oracle.com/pcbpel/tstSchema/SMP" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:ns0="http://www.w3.org/2001/XMLSchema" xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc" xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd" exclude-result-prefixes="xsl tns ns0 nxsd ldap xp20 bpws ora orcl">
<xsl:template match="/">
    <tns:SMP>
      <xsl:for-each select="/tns:SMP/tns:smpRecords">
        <xsl:if test="tns:data1 = '56'">
          <tns:smpRecords>
            <tns:data1>
              <xsl:value-of select="tns:data1"/>
            </tns:data1>
            <tns:data2>
              <xsl:value-of select="tns:data2"/>
            </tns:data2>
            <tns:emp>
              <xsl:value-of select="tns:emp"/>
            </tns:emp>
          </tns:smpRecords>
        </xsl:if>
      </xsl:for-each>
    </tns:SMP>
</xsl:template>
</xsl:stylesheet>and here is the out I get
<part   name="SMP" >
<SMP/>
</part>Any ideas what might be wrong in the xsl itself.
Thanks

How to create the Export Data and Import Data using flat file interface

Hi,
Request to let me know based on the requirement below on how to export and import data using flat file interface.....
Please provide the steps involved for the same.......
BW/BI - Recovery Process for SNP data.
For each SNP InfoProvider,
create:
1) Export Data:
1.a) Create an export data source, InfoPackage, comm structure, etc. necessary to create an ASCII fixed length flat file on the XI
ctnhsappdata\iface\SCPI063\Out folder for each SNP InfoProvider.
1.b) All fields in each InfoProvider should be exported and included in the flat file.
1.c) A process chain should be created for each InfoProvider with a start event.
1.d) If the file exists on the target drive it should be overwritten.
1.e) The exported data file name should include the InfoProvider technical name.
1.f) Include APO Planning Version, Date of Planning Run, APO Location, Calendar Year/Month, Material and BW Plant as selection criteria.
2) Import Data:
2.a) Create a flat file source system InfoPackage, comm structure, etc. necessary to import ASCII fixed length flat files from the XI
ctnhsappdata\iface\SCPI063\Out folder for each SNP InfoProvider.
2.b) All fields for each InfoProvider should be mapped and imported from the flat file.
2.c) A process chain should be created for each InfoProvider with a start event.
2.d) The file should be archived in the
ctnhsappdata\iface\SCPI063\Archive directory. Each file name should have the date appended in YYYYMMDD format. Each file should be deleted from the \Out directory after it is archived.
Thanks in advance.
Tyson

Here's some info on working with plists:
http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Introduc tion/chapter1_section1.html
They can be edited with any text editor. Xcode provides a graphical editor for them - make sure to use the .plist extension so Xcode will recognize it.

Fixed Length Flat File

Similar Messages

Maybe you are looking for