Fixed record length

Hi All,
I' am trying to write data into application server using Transfer statement.
Sometimes data would not be present in last fields, so the file length is varying.
How to have fixed file length?
regards,
Aravind

If you are downloading the file to application server with TRANSFER statement and LENGTH option, your spaces will be there at the end of the record. Just do not try to look at the file from within SAP environment (like using AL11). Try to get the file to your desktop and you can see that it will have those spaces.
If you using GUI_DOWNLOAD, then set the parameter TRUNC_TRAILING_BLANKS_EOL to SPACE (it is defaulted to 'X').

Similar Messages

How to load unicode data files with fixed records lengths?

Hi!
To load unicode data files with fixed records lengths (in terms of charachters and not of bytes!) using SQL*Loader manually, I found two ways:
Alternative 1: one record per row
SQL*Loader control file example (without POSITION, since POSITION always refers to bytes!)<br>
LOAD DATA
CHARACTERSET UTF8
LENGTH SEMANTICS CHAR
INFILE unicode.dat
INTO TABLE STG_UNICODE
TRUNCATE
A CHAR(2) ,
B CHAR(6) ,
C CHAR(2) ,
D CHAR(1) ,
E CHAR(4)
) Datafile:
001111112234444
01NormalDExZWEI
02ÄÜÖßêÊûÛxöööö
03ÄÜÖßêÊûÛxöööö
04üüüüüüÖÄxµôÔµ Alternative2: variable length records
LOAD DATA
CHARACTERSET UTF8
LENGTH SEMANTICS CHAR
INFILE unicode_var.dat "VAR 4"
INTO TABLE STG_UNICODE
TRUNCATE
A CHAR(2) ,
B CHAR(6) ,
C CHAR(2) ,
D CHAR(1) ,
E CHAR(4)
) Datafile:
001501NormalDExZWEI002702ÄÜÖßêÊûÛxöööö002604üuüüüüÖÄxµôÔµ Problems
Implementing these two alternatives in OWB, I encounter the following problems:
* How to specify LENGTH SEMANTICS CHAR?
* How to suppress the POSITION definition?
* How to define a flat file with variable length and how to specify the number of bytes containing the length definition?
Or is there another way that can be implemented using OWB?
Any help is appreciated!
Thanks,
Carsten.

Hi Carsten
If you need to support the LENGTH SEMANTICS CHAR clause in an external table then one option is to use the unbound external table and capture the access parameters manually. To create an unbound external table you can skip the selection of a base file in the external table wizard. Then when the external table is edited you will get an Access Parameters tab where you can define the parameters. In 11gR2 the File to Oracle external table can also add this clause via an option.
Cheers
David

Fixed record length with GUI_DOWNLOAD

Hi All,
In our current system we set global variables GLOBAL_FIXLEN_* by calling form SET_FIXLEN(SAPLGRAP). This allows us to create ASCII download files using function module WS_DOWNLOAD that have a fixed record length of 160 as required by the bank.
We are now going to a unicode system and WS_DOWNLOAD is being replaced by GUI_DOWNLOAD. How can I continue to create a fixed record length of 160 using this function module? I cannot find any similar GLOBAL_FIXLEN* variables in GUI_DOWNLOAD.
Thanks in advance for suggestions,
Kirsten

Hi,
Kirsten,
I find form "set_trail_blanks" also not available in GUI_DOWNLOAD.
FYI
aRs

Converting fixed-record length file to XML

Hello all
I am trying to convert a fixed length flat file to XML.
I believe the only required information for such a coversion is- the element or field names, their data types, and the fixed length of each field.
I do not want to generate a xsl document by hand. Just looking if there are any open source tools which can help me out here.
Let me know if you guys have done this before.
Thanks
Mahesh :)

It all depends on the fixed length file format and the amount of money you are willing to spend. From what I can tell there's not much in the way of free tools for converting stuff like this. It's just not very sexy.

Sql loader - Data loading issue with no fixed record length

Hi All,
I am trying to load the following data through sql loader. However the records # 1, 3 & 4 are only loading succesfully into the table and rest of the records showing as BAD. What is missing in my syntax?
.ctl file:
LOAD DATA
INFILE 'C:\data.txt'
BADFILE 'c:\data.BAD'
DISCARDFILE 'c:\data.DSC' DISCARDMAX 50000
INTO TABLE icap_gcims
TRAILING NULLCOLS
     CUST_NBR_MAIN          POSITION(1:9) CHAR NULLIF (CUST_NBR_MAIN=BLANKS),
     CONTACT_TYPE          POSITION(10:11) CHAR NULLIF (CONTACT_TYPE=BLANKS),
     INQUIRY_TYPE          POSITION(12:13) CHAR NULLIF (INQUIRY_TYPE=BLANKS),
     INQUIRY_MODEL          POSITION(14:20) CHAR NULLIF (INQUIRY_MODEL=BLANKS),
     INQUIRY_COMMENTS     POSITION(21:60) CHAR NULLIF (INQUIRY_COMMENTS=BLANKS),
     OTHER_COLOUR POSITION(61:75) CHAR NULLIF (OTHER_COLOUR=BLANKS),
     OTHER_MAKE          POSITION(76:89) CHAR NULLIF (OTHER_MAKE=BLANKS),
     OTHER_MODEL_DESCRIPTION POSITION(90:109) CHAR NULLIF (OTHER_MODEL_DESCRIPTION=BLANKS),
     OTHER_MODEL_YEAR POSITION(110:111) CHAR NULLIF (OTHER_MODEL_YEAR=BLANKS)
data.txt file:
000000831KHAN
000000900UHFA WANTS NEW WARRANTY ID 000001017OHAL
000001110KHAP
000001812NHDE231291COST OF SERVICE INSPECTIONS TOO HIGH MAXIMA 92 MK
000002015TPFA910115CUST UPSET WITH AIRPORT DLR. $200 FOR PLUGS,OIL,FILTER CHANGE. FW
Thanks,

Hi,
Better if you have given the table structure, I check your script it was fine
11:39:01 pavan_Real>create table test1(
11:39:02   2 CUST_NBR_MAIN varchar2(50),
11:39:02   3 CONTACT_TYPE varchar2(50),
11:39:02   4 INQUIRY_TYPE varchar2(50),
11:39:02   5 INQUIRY_MODEL varchar2(50),
11:39:02   6 INQUIRY_COMMENTS varchar2(50),
11:39:02   7 OTHER_COLOUR varchar2(50),
11:39:02   8 OTHER_MAKE varchar2(50),
11:39:02   9 OTHER_MODEL_DESCRIPTION varchar2(50),
11:39:02 10 OTHER_MODEL_YEAR varchar2(50)
11:39:02 11 );
Table created.
11:39:13 pavan_Real>select * from test1;
no rows selected
C:\Documents and Settings\ivy3905>sqlldr ara/ara@pavan_real
control = C:\control.ctl
SQL*Loader: Release 9.2.0.1.0 - Production on Sat Sep 12 11:41:27 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Commit point reached - logical record count 5
11:42:20 pavan_Real>select count(*) from test1;
COUNT(*)
         5    control.ctl
LOAD DATA
INFILE 'C:\data.txt'
BADFILE 'c:\data.BAD'
DISCARDFILE 'c:\data.DSC' DISCARDMAX 50000
INTO TABLE test1
TRAILING NULLCOLS
CUST_NBR_MAIN POSITION(1:9) CHAR NULLIF (CUST_NBR_MAIN=BLANKS),
CONTACT_TYPE POSITION(10:11) CHAR NULLIF (CONTACT_TYPE=BLANKS),
INQUIRY_TYPE POSITION(12:13) CHAR NULLIF (INQUIRY_TYPE=BLANKS),
INQUIRY_MODEL POSITION(14:20) CHAR NULLIF (INQUIRY_MODEL=BLANKS),
INQUIRY_COMMENTS POSITION(21:60) CHAR NULLIF (INQUIRY_COMMENTS=BLANKS),
OTHER_COLOUR POSITION(61:75) CHAR NULLIF (OTHER_COLOUR=BLANKS),
OTHER_MAKE POSITION(76:89) CHAR NULLIF (OTHER_MAKE=BLANKS),
OTHER_MODEL_DESCRIPTION POSITION(90:109) CHAR NULLIF (OTHER_MODEL_DESCRIPTION=BLANKS),
OTHER_MODEL_YEAR POSITION(110:111) CHAR NULLIF (OTHER_MODEL_YEAR=BLANKS)
data.txt
000000831KHAN
000000900UHFA WANTS NEW WARRANTY ID 000001017OHAL
000001110KHAP
000001812NHDE231291COST OF SERVICE INSPECTIONS TOO HIGH MAXIMA 92 MK
000002015TPFA910115CUST UPSET WITH AIRPORT DLR. $200 FOR PLUGS,OIL,FILTER CHANGE. FW
CUST_NBR_MAIN     CONTACT_TYPE     INQUIRY_TYPE     INQUIRY_MODEL     INQUIRY_COMMENTS     OTHER_COLOUR     OTHER_MAKE     OTHER_MODEL_DESCRIPTION     OTHER_MODEL_YEAR
000000831     KH     AN     NULL     NULL     NULL     NULL     NULL     NULL
000000900     UH     FA      WANTS     NEW WARRANTY ID 000001017OHAL     NULL     NULL     NULL     NULL
000001110     KH     AP     NULL     NULL     NULL     NULL     NULL     NULL
000001812     NH     DE     231291C     OST OF SERVICE INSPECTIONS TOO HIGH MAXI     MA 92 MK     NULL     NULL     NULL
000002015     TP     FA     910115C     UST UPSET WITH AIRPORT DLR. $200 FOR PLU     GS,OIL,FILTER C     HANGE. FW     NULL     NULL- Pavan Kumar N
Edited by: Pavan Kumar on Sep 12, 2009 11:46 AM

Issue in FCC paramenter in Fixed Filed Length file at reciver side

Hi,
I am doing IDOC to File interface. In that at receiver side I am sending file in Fixed Field Length Format.
Receiver File Message structure is as fallows.
Recordset
--Control
CTID
CTGUI
.... Control Fields
--Header
AHID
AHGUI
....Header Fields
--Detail
ADID
ADGUI
... Detail Fields
--Notes
INID
INGUI
...Notes Field
We want output File format in such a way that each Control, Header, Detail & Notes records should come on different line.
I am using following paramater in File Content conversion:
Recordset Structure* = Control,Header,Detail,Notes
Control.fieldFixedLengths = control field lengths
Header.fieldFixedLengths = header field lengths
Detail.fieldFixedLengths     = detail field lengths
Notes.fieldFixedLengths     = Notes field lengths
ignoreRecordsetName        = true
But the problem is I am getting all records in same line in file.
Any help on this issue will be appreciated.
Regards,
Prashant Kudtarkar

Hi Suraj,
You are right. When I open that file in notepad I am getting boxes at end of each record and all records are coming in same line but when I open that file in XL or wordpad I am getting each record on new line.
I am using following paramater in File Content conversion:
Recordset Structure* = Control,Header,Detail,Notes
Control.fieldFixedLengths = control field lengths
Header.fieldFixedLengths = header field lengths
Detail.fieldFixedLengths = detail field lengths
Notes.fieldFixedLengths = Notes field lengths
ignoreRecordsetName = true
Thanks and regards,
Prashant Kudtarkar

Transfer records to UNIX with different record length

Hi all,
I have the following problem. I have to transfer records to a UNIX file. The maximum length of a record is 2000. The records are TAB seperated. I also have records which have a length less then 2000. When i look at the file in Excel the last field is always very large. Isn't there a way to only transfer the real length of the record. I have tried to transfer the record in Binary an Text mode. I used the Length statement, but nothing worked for me.
Hope anyone can help me.
Greetings Maarten

Hi Maarten,
"Transfer" with "length" option should work. I am not sure what you passed as length to the "transfer" command. Did you used a fixed length of 2000 or did you actually found out the record length of each record and passed that value?
Scenario 1.
Here in this scenario, you will always have the last field set to maximum length.
loop at itab.
transfer itab-record to file length 2000.
endloop.
Scenario 2.
In this second scenario, you should have your excel's last field set to the maximum occupied length of that field.
loop at itab.
v_len = strlen( itab-record ).
transfer itab-record to file length v_len.
endloop.
Hope this helps.
Srinivas

Fixed note length in piano roll

Hello ,is there any way to draw notes with a fixed length in the piano roll rather than using the last edited note's length?
In other words,i want the default note length not to automatically change every time i draw/edit a new note (with a different length).
Im quite sure this cannot be done, but i thought i should ask to confirm...
I also feel i want to say my opinion on that,you dont have to read it or answer back to it:
I find this way of editing very confusing and counter creative ,it sure adds extra thinking proccess.While you are drawing notes it
constantly keeps your mind away from your melody line since in every step, you have to stop some milliseconds and think
"which side should i drag to resize now given the new facts left or right?"....
And extra (unnecessary) thinking always acts against creativity.
I think it seems very logical the way i said that and that objectively, irrelevant to any personal preferences, this way of editing
,even if i doesnt annoy everyone ,it is indeed counter creative.
Especcially if one really does a lot of editing rather than recording.
I wish there was an option for that in the preferences, maybe something very simple like a checkbox "Automaticaly define default note" to uncheck.
Im sure it would be only a few hours of programming for the developers to do something like that, but it would be such a saver for people
who edit a lot or for people coming from other DAWS, or for anyone that simply cant get used to it because they feel it anti-intuitive / unatural...
There...i shared my thoughts, at least i feel a better know...!
(However if you read my opinion i d like to hear what other people (that do a lot of editing) feel )

You can use the transform tool but it's "after the fact". Simply rubberband a group of notes to be changed and use the Transform tool under the piano roll's "function" menu. Choose "Fixed Note Length" then set the parameter box to the value you need.
There's also this workaround: Find a note of the correct length already in the sequence or create temporary notes of the correct length. I'm assuming by "draw" you mean using the pencil tool. Move the pencil over the *center of note with the length you need, left mouse click and hold for a second, until the pencil turns into a hand, you will now have the length set for drawing new notes. The pencil tool is still selected so you don't have any additional selections to make.
Yes, it's a hassle, but once you get used to it you will find it's faster than what you've been doing.
*slight correction: when moving the pencil tool over the *center of a note, it will change into the pointer arrow, left click and hold and it will change into the hand, move the pointer away and it goes back to the pencil.

How to create variable record length target file in SAP BODS

Hi All
I have a requirement to create target file which will have various record layout; meaning different record length (similar to cobol file format), but this is for the target. Please let me know what is the best practice and how to solution this requirment.
Thanks
Ash

Hi Shiva,
Thanks for your feedback. My issue is that I have 10 different detail records (each record type is fixed length).
For each customer account, I have to write to file the header record, the detail records in the exact order, then continue with next account and so on and then write the trailer record. I have given sample layout below. Highlighted text is the record identifier in this exmaple while the underlineds are account numbers. Fields are fixed length right padded with space or 0.
220700000000SA00    Wednesday     2014-12-12 ASA00034 334 000   ---> (this is header)
220700000010SA10 AAb   00000+000000+ Akab xxxx bb   0000000000943 3433 --> (detail rec)
220700000010SA14 AAA 00034354 DDD 000000000+    --> (detail rec)
220700000010SA15 888e a88 00000000+            --> (detail rec)
. . . . . remaining detail records
220700000012SA10 AAb   00000+000000+ Akab xxxx bb   0000000000943 3433 --> (detail rec)
220700000012SA14 AAA 00034354 DDD 000000000+   --> (detail rec)
220700000012SA15 888e a88 00000000+           --> (detail rec)
. . . . . remaining detail records
220700000000SA99    Wednesday     2014-12-12 d334 000   --> (trailer is header)

How to fix the length of select list box?

Halo, i am doing the research. I need to find out what is the method to fix the length of select list box. This is b'cos i can set the length of select list due to different length of record(s)/data(s).
Another question to select list box. What is the maximum length of the select list box?? Can i enter the character with 255 lenght??
Thank you very much..... a prompt reply will be appreciate!!

Thanks for ur reply! actually that answer that you gave is right, but i also need to know what is the maximum lenght of character in the select list box?? any idea to that??
Meanwhile, i also need to know how can i make the character display in select list box dynamically?? that means i can change the font style or font size??
Anyway, thanks for ur answer.
bscs.

Schema for File with Multiple Fixed Records using Native Schema builder

Hi All:
The below is the sample file format which i need to read through file adapter
HeaderReacord
FailureOrderRecord
ChildFailureRecord
ChildFailureRecord
SuccessOrderRecord
SuccessOrderRecord
HeaderReacord
FailureOrderRecord
ChildFailureRecord
In the above file, totally three records are repeatedly present with fixed length eg. HeaderReacord length is 50, SuccessOrderRecord and FailureOrderRecord length is 100, ChildFailureRecord length is 25. The file may have more than one header group i.e. A single header group contain one HeaderReacord, more than one SuccessOrderRecord, more than one FailureOrderRecord and more than one ChildFailureRecord after each FailureOrderRecord.
I have created the below xsd for this scenario and get the below output. Kindly tell how to do this in Native builder using fixed length type for different fixed records options
<xsd:element name="BatchOrder">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="OrderGroupCollection" type="OrderGroup" minOccurs="1" maxOccurs="unbounded"
nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="OrderGroup">
<xsd:sequence>
<xsd:element name="HeaderRecord" type="xsd:string" minOccurs="1" maxOccurs="1"
nillable="false"/>
<xsd:element name="RecordList" type="RecordList" minOccurs="1" maxOccurs="unbounded"
nillable="false"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="RecordList">
<xsd:sequence>
<xsd:element name="OrderRecord" type="xsd:string" minOccurs="1" maxOccurs="1"
nillable="false"/>
<xsd:element name="ChildErrorRecord" type="xsd:string" minOccurs="0"
maxOccurs="unbounded" nillable="true"/>
</xsd:sequence>
</xsd:complexType>
Output:
=======
<BatchOrder>
<OrderGroupCollection>
<OrderGroup>
<HeaderRecord>HeaderReacord</HeaderRecord>
<RecordList>
<OrderRecord>FailureOrderRecord</OrderRecord>
<ChildErrorRecord>ChildFailureRecord</ChildErrorRecord>
<ChildErrorRecord>ChildFailureRecord</ChildErrorRecord>
<ChildErrorRecord>SuccessOrderRecord</ChildErrorRecord>
<ChildErrorRecord>SuccessOrderRecord</ChildErrorRecord>
<ChildErrorRecord></ChildErrorRecord>
<ChildErrorRecord>HeaderReacord</ChildErrorRecord>
<ChildErrorRecord>FailureOrderRecord</ChildErrorRecord>
<ChildErrorRecord>ChildFailureRecord</ChildErrorRecord>
</RecordList>
</OrderGroup>
</OrderGroupCollection>
</BatchOrder>

you cant acheive this heirarchy using the file adapters cont. conv, cos it supports only to a single level.
Maybe you can have a module or use the conversion agent !!
Some good reads on the Conv. agent!!!
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/18/conversion-agent-a-free-lunch
/people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield

OL 5.6 mcelog - warning: record length longer than expected

OS: Oracle Linux 5.6 x86_64 UEK 2.6.32-100 under Virtualbox.
Problem: root mail account filling up with cron messages:
/etc/cron.hourly/mcelog.cron:
mcelog: warning: record length longer than expected. Consider update.
Apparently this issue is still present in OL 5.6 as it was in OL 5.5:
mcelog-error in mail from hourly cron job using Unbreakable Kernel
The following may not be the correct or best way to fix the problem, but it works for me:
rpm -ivh http://public-yum.oracle.com/repo/OracleLinux/OL5/6/base/x86_64/mcelog-0.9pre-1.30.el5.src.rpm
cd /usr/src/redhat/SOURCES/
tar zxvf mcelog-0.9pre.tar.gz
cd mcelog-0.9pre
Test:
/usr/sbin/mcelog --ignorenodev --filter >> /var/log/mcelog
mcelog: warning: record length longer than expected. Consider update.
./mcelog --ignorenodev --filter >> /var/log/mcelog
(quiet)
Implement:
mv /usr/sbin/mcelog /usr/sbin/mcelog.orig
cp /usr/src/redhat/SOURCES/mcelog-0.9pre/mcelog /usr/sbin/mcelogRegards.

Username:SQL*Loader-350: Syntax error at line 14.What is line 14 in your script?
Thanks,
Hussein

Failed to open a rowset....offset and/or length of column {table_name} exceeds maxium record length of 0

Post Author: anand.kolipakkam
CA Forum: Data Connectivity and SQL
hi all,
I moved Transoft USQL Database from one server to another, even though i am able to validate the server with usql client but my crystal reports is giving errors while trying to open up some of the reports.
Unfortunately doesnt happens for all the reports, it happens for only for the reports which prompts for values in preview screen.
This is the error i get
first error screen....Failed to open a rowset....
second error screen
Failed to open a rowset
Details:HY000:[Transoft][TSODBC][MF](log: 3816-175022)offset and/or length of column exceeds maxium record length of 0
Thats it i get a blank crystal report screen.
I would appreciate if experts would help me out..

Don't use localhost as your server name. It's a reserved name and should not be used in code.
Try this also [Kbase |http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333533353333333433363339%7D.do] SAP Note 1553469 - How to enable Database logging in Crystal Reports for Visual Studio 2010
Edited by: Don Williams on Jan 30, 2011 6:02 AM

SQL Loader-704: Internal error: Maximum record length must be = [10000000]

Hi,
running SQL*Loader (Release 8.1.7.2.1) causes an error "SQL*Loader-704: Internal error: Maximum record length must be <= [10000000]". This error occurs when SQLLoader is trying to load several thousand records into a database table. Each record is less than 250 bytes in length.
Any idea what could cause the problem?
Thanks in advance!
Ingo
And here's an extract from the log file generated by SQLLoader :
Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array: 1360 rows, maximum of 10485760 bytes
Continuation: none specified
Path used: Conventional
Table "SYSTEM"."BASICPROFILE$1", loaded from every logical record.
Insert option in effect for this table: APPEND
TRAILING NULLCOLS option in effect
Column Name Position Len Term Encl Datatype
UUID FIRST * O(X07) CHARACTER
DOMAINID NEXT * O(X07) CHARACTER
LASTMODIFIED NEXT * O(X07) DATE DD/MM/YYYY HH24:MI:SS
ANNIVERSARY NEXT * O(X07) CHARACTER
BIRTHDAY NEXT * O(X07) CHARACTER
COMPANYNAME NEXT * O(X07) CHARACTER
DESCRIPTION NEXT * O(X07) CHARACTER
FIRSTNAME NEXT * O(X07) CHARACTER
COMPANYNAMETRANSCRIPTION NEXT * O(X07) CHARACTER
FIRSTNAMETRANSCRIPTION NEXT * O(X07) CHARACTER
GENDER NEXT * O(X07) CHARACTER
HOBBIES NEXT * O(X07) CHARACTER
HONORIFIC NEXT * O(X07) CHARACTER
JOBTITLE NEXT * O(X07) CHARACTER
KEYWORDS NEXT * O(X07) CHARACTER
LASTNAME NEXT * O(X07) CHARACTER
LASTNAMETRANSCRIPTION NEXT * O(X07) CHARACTER
NICKNAME NEXT * O(X07) CHARACTER
PREFERREDLOCALE NEXT * O(X07) CHARACTER
PREFERREDCURRENCY NEXT * O(X07) CHARACTER
PROFESSION NEXT * O(X07) CHARACTER
SECONDLASTNAME NEXT * O(X07) CHARACTER
SECONDNAME NEXT * O(X07) CHARACTER
SUFFIX NEXT * O(X07) CHARACTER
TITLE NEXT * O(X07) CHARACTER
CONFIRMATION NEXT * O(X07) CHARACTER
DEFAULTADDRESSID NEXT * O(X07) CHARACTER
BUSINESSPARTNERNO NEXT * O(X07) CHARACTER
TYPECODE NEXT * O(X07) CHARACTER
OCA NEXT * O(X07) CHARACTER
SQL*Loader-704: Internal error: Maximum record length must be <= [10000000]

As a second guess, the terminator changes or goes missing at some point in the data file. If you are running on *NIX, try wc -l data_file_name. This will give a count of the number of lines (delimited by CHR(10) ) that are in the file. If this is not close to the number you expected, then that is your problem.
You could also try gradually working through the data file loading 100 records, then 200, then 300 etc. to see where it starts to fail.
HTH
John

Maximum record length in internal table?

Is there a maximum record length in an internal table? Please note: My question is NOT related to table space. I'm referring only to the length of an individual record (A.K.A. row length).
I am using a work area to insert data into an internal table. Both the work area and internal table are defined by the same structure.
The structure has a total length of 672 bytes. For the sake of this discussion I'll point out that at the end of the structure, bytes 669, 670, 671, and 672 are four separate fields of 1 character each.
When viewing the work area record in the debugger I'm seeing all the fields and all the values. When viewing the internal table in the debugger after a record is inserted, the internal table ends with the field defined at Byte 670. The internal table does not include the two fields defined at Bytes 671 and 672.
Am I to assume from the above explanation that the length of a record ( A.K.A. row) in an internal table cannot exceed 670 bytes?
Thank you.

Manish,
False alarm! While, technically, you didn't answer my question, your request for code ended up helping me answer my own question.
To provide you with some code I wrote a simple test program using the record layout referred to above, with a DO loop to put some records into the internal table, followed by a LOOP AT, with accompanying WRITE statements to display the contents of the internal table and demonstrate that the last two fields weren't being stored.
However, when I ran the test program, the last two fields were being displayed.
It was at that point, when stepping through the debugger that I noticed the scroll arrows above the last column of my internal table that allowed me to scroll to the right and see my final two fields.
Apparently, because of the large number of fields in my internal table I had reached the default display length of the debugger. While I was obviously aware of the scroll bar found at the bottom of the display, I had never worked with an internal table of that width in the past and hadn't even noticed the scroll arrows above the last column before.
Thanks for taking the time to respond helping me get to the solution.

Fixed record length

Similar Messages

Maybe you are looking for