FCC Receiver Error :Column value ' ' too long

Hi Experts
I am getting data from SAP for which i should create a file which is fixed length on the target side
My structure is :
File----1.....Unbound
----->Header --- -1..1
>RecordType
>Transcode
>PO_Num
>Vend_ID
>Crea_date
>WHS_ID
>POM_Status
>Cancel_date
>Delv_date
>Ord_type
>POM_Char
---->Record_Detail---1..Unbound
>Record_typ
>PO_Num
>Line_no
>Itm_no
>Sch_No
>QTY
>UOM
>Vend_itm_no
>Delv_Date
>Buyer_name
>WHS_ID
---->var1-0..1
---->var2-0..1
var1 and var2 I am using for variable substitution.
I have configured the receiver FCC as below
Record Structure HeaderRecord,Record_Detail
HeaderRecord.fieldFixedLengths 1,1,30,10,8,2,1,8,8,8,1
Record_Detail.fieldFixedLengths 1,30,5,30,3,8,2,20,8,25,2
And I have given var1 and var2 in varaible substitution.
But I am getting the following error when recevier receiving the file
Could not process due to error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '0811200613.WAPONUM' too long (>1 for 0. column) - must stop', probably configuration error in file adapter (XML parser error)'
Please help me
Regards
Sowmya

Hi,
If u have added Trailer Node ( And Var1 & Var2 inside it) then try adding this:
Trailer.fieldFixedLengths 0,0
Trailer.fixedLengthTooShortHandling Cut
Hope it will solve ur problem.
For reference check:
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Check ur final structure is like this:
Recordset Structure: File,Header,Record_Detail,Trailer
Header.fieldFixedLengths: 1,1,30,10,8,2,1,8,8,8,1
Header.fieldNames: RecordType,Transcode,PO_Num,Vend_ID,Crea_date,WHS_ID,POM_Status,Cancel_date,Delv_date,Ord_type,POM_Char
Record_Detail.fieldFixedLengths: 1,30,5,30,3,8,2,20,8,25,2
Record_Detail.fieldNames: Record_typ,PO_Num,Line_no,Itm_no,Sch_No,QTY,UOM,Vend_itm_no,Delv_Date,Buyer_name,WHS_ID
Trailer.fieldFixedLengths: 0,0
Trailer.fieldNames: var1,var2
Trailer.fixedLengthTooShortHandling: Cut
File.fieldSeparator: 'nl'
Thanks,
Mahi
Edited by: Maheshwari Morbale on Nov 21, 2008 6:33 AM

Similar Messages

FCC error :java.lang.Exception: Column value ' ' too long

Hi all,
I am using FCC on receiving File adapter...
While executing i am getting this error in CC monitor
com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value ' ' too long (>1 for 2. column) - must stop',
i searched in SDN but no luck till now..
Plz help me out..
Thanx in advance.

Hi,
Check ur FCC parameters,
File content conversion sites
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani.
Reward points if Helpful

Column value ' ' too long - must stop', probably configuration error

Hi Experts,
I have a Proxy to File Scenario when I execute it I get this error in RWB. Can you please help me on this:
Message processing failed. Cause: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value ' ' too long - must stop', probably configuration error in file adapter (XML parser error)''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value ' ' too long - must stop', probably configuration error in file adapter (XML parser error)'
Thanks
Srikanth E

Hi,
if there is any empty tag coming from source then target structure tag will not be created and because of which ur payload structure and FCC configuration is not matching.
To use map with default between source and target strcture so in case source tag dont have value target structure will be created because of mapwithdegfault fuction and ur FCC will not fail.
Open SXMB_MONI output payload and compare the structre with Data type u will se for no source value target tag is not created at all and FCC is failed.
please refer below thread,
0 byte txt file using receiver File Adapter
regards,
ganesh.

Large XML Publisher reports fail with client-error-request-value-too-long

We are running BI Publisher 5.6.3 with Oracle Applications 11.5.10.2 (ATG.H RUP 5), and are having frequent failures with client-error-request-value-too-long messages on large PDF reports that cause the entire report to not print.
The exact error message is as follows:
lp: unable to print file: client-error-request-value-too-long
Pasta: Error: Print failed. Command=lp -c -dPDX_B6_1LJ5200NEAST /logs/temp/pasta3262_0.tmp
Pasta: Error: Check printCommand/ntPrintCommand in pasta.cfg
Pasta: Error: Preprocess or Print command failed!!!
APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 1
Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 1.
Action: Review your concurrent request log file for more detailed information.
I have Google'd client-error-request-value-too-long, and found it is a common CUPS issue on Linux. The popular solutions (having /var/spool/cups and /var/spool/cups/tmp) are already in place. Also, the temp files are nowhere near 2 GB (44MB).
Has anyone had this issue with BI Publisher on Linux?

Thanks for the link. It looks like the sysadmins have throttled cups to low to allow large bitmapped print jobs:
grep MaxRequestSize cupsd.conf
# MaxRequestSize: controls the maximum size of HTTP requests and print files.
MaxRequestSize 10M
I am trying to get a more reasonable size limit.

Large BI Publisher reports fail with client-error-request-value-too-long

We are running BI Publisher 5.6.3 with Oracle Applications 11.5.10.2, and are having frequent failures with client-error-request-value-too-long messages on large PDF reports that cause the entire report to not print.
The exact error message is as follows:
lp: unable to print file: client-error-request-value-too-long
Pasta: Error: Print failed. Command=lp -c -dPDX_B6_1LJ5200NEAST /logs/temp/pasta3262_0.tmp
Pasta: Error: Check printCommand/ntPrintCommand in pasta.cfg
Pasta: Error: Preprocess or Print command failed!!!
APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 1
Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 1.
Action: Review your concurrent request log file for more detailed information.
I have Google'd client-error-request-value-too-long, and found it is a common CUPS issue on Linux. The popular solutions (having /var/spool/cups and /var/spool/cups/tmp) are already in place. Also, the temp files are nowhere near 2 GB (44MB).
Has anyone had this issue with BI Publisher on Linux?

The linux sysadmins set the cups max_request_size at 10 MB, which was causing this error. Once the restriction was lifted, the reports ran without error.

Client-error-request-value-too-long

What is this error???? I am trying to add an Epson 1280 printer and I get this error. I have the most current driver and not sure why this isn't working.

My flatmate had this "client-error-request-value-too-long" problem with her (powerpc) powerbook. Nearly everything I tried didn't work:
1) Reinstalling drivers
2) Permissions repair
3) Resetting print system using Fixamac's Printer Setup Repair Utility
4) Updating from 10.4.10 to 10.4.11
5) Using the command line to try and recreate the directory: /var/spool/cups/tmp (which told me it already existed)
6) Using Transmit (with show invisible files turned on) to browse to /var/spool/cups/ and try and recreate the tmp folder
On the last point I couldn't change anything about the /var/spool/cups/ directory because the permissions were corrupted in some way. It keep telling me tmp already existed but I couldn't see it.
In the end what did work was enabling and logging in as root, browsing to /var/spool/ using Transmit and deleting the cups folder and then recreating. It took a few tries to delete too, but in the end I managed to remove it.
Of course I wouldn't actually recommend this. I'm no Unix geek so god knows what I might have broken in the process, so I'm going to reinstall her system with the Archive and Install options when I get a chance, which is what I'd recommend doing in the first place to anyone having this problem.

Error: "client-error-request-value-too-long" when trying to add printer

After installing the 10.4.9 Combo update, my HP 1350 All-in-One printer was not recognized. I reinstalled the driver, but now I can't add the printer. I get the error message "client-error-request-value-too-long" when trying to add the printer. Has anyone else experienced a similar problem.
Thanks in advance

Well, I tried all of that and I'm still getting the error message. I've also repaired disk permissions and run Disk Warrior. When I repaired disk permissions, many HP printer items showed up in the list.

USB Printing - client-error-request-value-too-long

A little while back, my iSight suddenly stopped working and so I did a full format and reinstall to 'fix' the problem. The problem wasn't 'fixed' through this action. Instead, I had to disconnect power and let the computer sit there for a bit and think about what it had done (naughty iMac). Anyway... Another USB-related problem just popped up - this time with my printer.
The printer is a Canon IP4000 and I just installed the latest drivers to try to fix this error. The first error was something about not being able to write to the device. I thought that was stupid and would probably be fixed by deleting the printer and then reinstalling it. I have so far 'uninstalled' the printer (more or less just removed it from the printers list in the printer utility) and now I can't re-add it to the list to install it. The error reads as follows:
An error occurred while trying to add the selected printer.
client-error-request-value-too-long
I have tried Google but I just don't have the time to sort through all kinds of explainations on how CUPS works on Linux (apparently, this error is related to CUPS in some way). I also tried searching the forum for the error message but found nothing. So here I am again asking for some help from those who might have seen this problem before.
This is on a fresh install and I have tried it on newly created users to no avail.
Thanks for any help! -Thomas

I've recently had this error which came up because the spool folder was missing. In the terminal:
sudo mkdir /private/var/spool
sudo mkdir /private/var/spool/cups
puts the proper folders in their place. Repair permissions afterwards.
Through the cups web interface, the error is "Request entity too large"
Panther has the same folders, but a different error comes up.
The above cups folder has different permissions than the default. Probably the same for Tiger and Panther but just to be safe, repair permissions.

Error message: "client-error-request-value-too-long"

The system finds my printer and the driver (which I have re-installed) but when I click "add" it comes up with this message. Does anyone know what this means and how I can fix it so my printer can be added?
Thanks

thank you for not helping

Value too long in property 'Currency'

Hi SCN,
Im trying to upload AR Open Balance using DTW, But I encountered an error such Value too long in property 'Currency' And when I checked the template I used, I only used 3 values, which was PHP. How can I resolve this?
Regards,
Mahj

ParentKey
LineNum
ItemCode
ItemDescription
Quantity
ShipDate
Price
PriceAfterVAT
Currency
Rate
AccountCode
UseBaseUnits
SupplierCatNum
CostingCode
ProjectCode
BarCode
VatGroup
Height1
Hight1Unit
Height2
Height2Unit
Lengh1
Lengh1Unit
Lengh2
Lengh2Unit
Weight1
Weight1Unit
Weight2
Weight2Unit
Factor1
Factor2
Factor3
Factor4
BaseType
BaseEntry
BaseLine
Volume
VolumeUnit
Width1
Width1Unit
Width2
Width2Unit
Address
TaxCode
TaxType
TaxLiable
BackOrder
FreeText
ShippingMethod
CorrectionInvoiceItem
CorrInvAmountToStock
CorrInvAmountToDiffAcct
WTLiable
DeferredTax
MeasureUnit
UnitsOfMeasurment
LineTotal
TaxPercentagePerRow
TaxTotal
ConsumerSalesForecast
ExciseAmount
CountryOrg
SWW
TransactionType
DistributeExpense
ShipToCode
RowTotalFC
CFOPCode
CSTCode
Usage
TaxOnly
UnitPrice
LineStatus
LineType
COGSCostingCode
COGSAccountCode
ChangeAssemlyBoMWarehouse
GrossBuyPrice
GrossBase
GrossProfitTotalBasePrice
CostingCode2
CostingCode3
CostingCode4
CostingCode5
ItemDetails
LocationCode
ActualDeliveryDate
ExLineNo
RequiredDate
RequiredQuantity
COGSCostingCode2
COGSCostingCode3
COGSCostingCode4
COGSCostingCode5
WithoutInventoryMovement
AgrementNo
AgreementRowNumber
ShipToDescription
DocNum
LineNum
ItemCode
Dscription
Quantity
ShipDate
Price
PriceAfVAT
Currency
Rate
AcctCode
UseBaseUn
SubCatNum
OcrCode
Project
CodeBars
VatGroup
Height1
Hght1Unit
Height2
Hght2Unit
Length1
Len1Unit
length2
Len2Unit
Weight1
Wght1Unit
Weight2
Wght2Unit
Factor1
Factor2
Factor3
Factor4
BaseType
BaseEntry
BaseLine
Volume
VolUnit
Width1
Wdth1Unit
Width2
Wdth2Unit
Address
TaxCode
TaxType
TaxStatus
BackOrdr
FreeTxt
TrnsCode
CEECFlag
ToStock
ToDiff
WtLiable
DeferrTax
unitMsr
NumPerMsr
LineTotal
VatPrcnt
VatSum
ConsumeFCT
ExciseAmt
CountryOrg
SWW
TranType
DistribExp
ShipToCode
TotalFrgn
CFOPCode
CSTCode
Usage
TaxOnly
PriceBefDi
LineStatus
LineType
CogsOcrCod
CogsAcct
ChgAsmBoMW
GrossBuyPr
GrossBase
GPTtlBasPr
OcrCode2
OcrCode3
OcrCode4
OcrCode5
Text
LocCode
ActDelDate
ExLineNo
PQTReqDate
PQTReqQty
CogsOcrCo2
CogsOcrCo3
CogsOcrCo4
CogsOcrCo5
NoInvtryMv
AgrNo
AgrLnNum
ShipToDesc
900000001
1
SERVICE MAINTENANCE FOR THE MONTH OF NOVEMBER 2011
4939.20
PHP
1
19121104
900000002
1
SERVICE MAINTENANCE FOR THE MONTH OF SEPTEMBER 2013
2074.48
PHP
1
19121104
900000003
1
SERVICE MAINTENANCE FOR THE MONTH OF JULY 2014
93351.30
PHP
1
19121104
900000004
1
SERVICE MAINTENANCE FOR THE MONTH OF AUGUST 2014
93351.30
PHP
1
19121104
900000005
1
SERVICE MAINTENANCE FOR THE MONTH OF JULY 2014
50909.09
PHP
1
19121104
900000006
1
SERVICE MAINTENANCE FOR THE MONTH OF AUGUST 2014
50909.09
PHP
1
19121104
900000007
1
SERVICE MAINTENANCE FOR THE MONTH OF MAY 2014
131007.00
PHP
1
19121104
900000008
1
SERVICE MAINTENANCE FOR THE MONTH OF JUNE 2014
131007.00
PHP
1
19121104
900000009
1
SERVICE MAINTENANCE FOR THE MONTH OF JULY 2014
131007.00
PHP
1
19121104
900000010
1
SERVICE MAINTENANCE FOR THE MONTH OF AUGUST 2014
131007.00
PHP
1
19121104
900000011
1
SERVICE MAINTENANCE FOR THE MONTH OF JUNE 2014
148512.00
PHP
1
19121104
900000012
1
SERVICE MAINTENANCE FOR THE MONTH OF JULY 2014
148512.00
PHP
1
19121104
900000013
1
SERVICE MAINTENANCE FOR THE MONTH OF AUGUST 2014
148512.00
PHP
1
19121104
900000014
1
SERVICE MAINTENANCE FOR THE MONTH OF NOVEMBER 2009
14500.00
PHP
1
19121104

How to Update a clob column..it gives error string literal too long

I am trying to update a clob column of a table but it gives error string literal too long plz tell me what's the issue
ORA-01704: string literal too long

Peeyush wrote:
I am trying to update a clob column of a table but it gives error string literal too long plz tell me what's the issue
ORA-01704: string literal too longThere's a problem with my car. It won't start. Why won't it start? Please tell me!
Oh wait, you can't, because I haven't given you nearly enough information...
In other words, if you would like help in trying to work out where you've gone wrong, you should provide a small enough example of your code that demonstrates the error. We might then actually stand a chance of being able to help you!

Solved printer installation problem – "error-user-request-value-too-long"

A discussion in July 2006 left the problem of printer installation unsolved. My contacts with Apple Support have also led to frustration for everyone.
Whenever I have tried to install any printer I end up with the error message:
"error-user-request-value-too-long".
Luckily I discovered the shareware program "Printer set up repair" on Versiontracker. It worked wonders in 5 minutes. Now everything is fully functioning. It also provides an extremely useful log-file telling you which (often hidden) files that are missing or damaged.
Address: www.fixamacsoftware.com/software
Phew!

Well, I tried all of that and I'm still getting the error message. I've also repaired disk permissions and run Disk Warrior. When I repaired disk permissions, many HP printer items showed up in the list.

How to find the exact coloumn which fired the column value too large error

Hi all
I have a procedure which has a insert statement init.
I have encountered an column value too large error in that procedure.
I want to know exactly in which column the error has come
Any ideas,
Thanks
Hari

What is your insert statement? I get the exact column name here.
SQL> create table sample1(col1 number(1), col2 number(3), col3 varchar2(2))
2 /
Table created.
SQL> insert into sample1
2 select 1, 2, 'A' from dual
3 union
4 select 1,333, 'B' from dual
5 union
6 select 2, 44, 'CCC' from dual
7 /
insert into sample1
ERROR at line 1:
ORA-12899: value too large for column "ETL_USER"."SAMPLE1"."COL3" (actual: 3,
maximum: 2)
SQL> Cheers
Sarma.

FRM-40831 : Truncation occured: value too long for filed MAST_EMP_NAME

Hi
I'm using Forms 5 and getting following error.
FRM-40831 : Truncation occured: value too long for filed MAST_EMP_NAME.
When i checked in the column Mast_emp_name, all the values are with in the limit.
Table contains some 9 lacs record.
Please help me. this is very urgent

check the maximum length - property of all those 5 columns in your form. They have to be as long as in the database. Except number. They have to be 1 char longer than in the db.
Forms-Online-Help says:
This property can potentially limit the amount of data that an item is allowed to contain internally (in the Forms server) when it's in native format. It can also potentially limit the number of character (or bytes) displayed or entered by the end user. That is, it can specify a data limit and/or a user interface (UI) limit. The exact effect depends upon several factors, including the item's Data type, Data Length Semantics, and Format Mask properties. For a character item (datatypes CHAR, ALPHA, LONG), the Maximum Length property specifies a data limit. The property value specifies either the maximum number of bytes or else the maximum number of characters, depending upon the value of the Data Length Semantics property. Within a group of character mirror items, the Maximum Length property is always taken from the master mirror item. A compiler (generator) warning is issued if a non-zero non-default value is specified in a subordinate mirror item. If a character item has no format mask (the Format Mask property is null), then the Maximum Length property (taken from the master mirror item) also specifies a UI limit. When the Forms server is using the UTF8 character set , this UI limit has the same semantics (byte versus character) as the data limit. When the Forms server is using a multi-byte character set other than UTF8, and the Data Length Semantics property specifies byte semantics, Forms cannot prevent the end user from typing in too many bytes. Instead, it uses character semantics for the UI limit. In such a case, the end user is allowed to type in too many bytes. When the end user attempts to navigate out of the current validation unit, one of two things will happen. If the application property FLAG_USER_VALUE_TOO_LONG is set, an error will be flagged and the excess characters on the right will be selected. If this application property is not set, the excess characters will be quietly truncated, and the navigation will succeed. If a character item has a format mask, then the item's UI limit is derived from the format mask. This limit is always a character limit. For a number item (datatypes NUMBER, INT, MONEY, RNUMBER, RINT, RMONEY), the Maximum Length property specifies a user interface limit. This limit is always a character limit. There is no data limit. The data item can always internally hold up to 23 bytes (which is the maximum size of an Oracle number in native format), regardless of the value of the Maximum Length property. For a date or time item (datatypes DATETIME, DATE, TIME, JDATE, EDATE), the Maximum Length property specified in Forms Builder has almost no effect (See the Query Length property for a discussion of the only effect). As with "number" items, there is no data limit. For DATE and DATETIME items, the internal value is 7 bytes long, and for TIME, JDATE and EDATE items, the internal value is 4 bytes long . The user interface limit is derived from the format mask. This limit is always a character limit which is what is returned by GET_ITEM_PROPERTY(item, MAX_LENGTH).

FRM-40831: Value too long for field ROWID.

Hi,
I'm a newbie in forms and I've a problem when working with index organized tables, it post me this error:
FRM-40831: Truncation occurred : Value too long for field ROWID.
How can I solve this problem?
Thanks for your help.
RaÃºl

This is a bug in Forms 9i (bug 2408210). The workaround is to:
- change block property Key Mode to Updatable or Non-Updatable
- set item property Promary Key to Yes for all items that correspond to an index column in the index-organized table

FCC Receiver Error :Column value ' ' too long

Similar Messages

Maybe you are looking for