How to increase the string length of an uploaded file

Hi,
i use a abap webser where i've uploaded some JAR files into the mime repository.
Unfortunately the string length is limited by 40 characters and so longer file names are cut.
How can I increase the default string length? Does somebody know a workaround?
Thanks.
Edited by: Martin Gardyan on Oct 22, 2008 9:48 AM

what i guess copying those jars should not create this problem.U just try in db using
"ALTER TABLE <table_name> MODIFY <column_name> VARCHAR2(<new, larger length>)"
may be it works.
Regards,
Anu

Similar Messages

How you increase the strength / length of an airport extreme?

How you increase the strength / length of an airport extreme? I find it hard to use wireless internet

Please checkout the following Apple Support article on details on the many ways you can extend the wireless range of your current AirPort base station.

How to increase the size (Length and width) of check box

Hi All,
I have to increase the size of ( width and length) of check box, I have revised to check box topic in dev guide but didnt find any clue, i have also tried to use CCStyle class but that is also not working, I would appreciate if some can help me out on this. Thanks in advance , let me know if any clarification required.
Thanks
Pratap

Hi Pratap ,
I honestly don't know how to increase the size
But i am giving you an alternate solution : we can create two Images with check box type 1 ) with checked
2 ) with unchecked . ( you can create image of any size ) and get them displayed on OAF screen dynamically using switcher case .
Dynamically displaying image will give the illusion of check box being checked and unchecked .
keep this image moved to following media directory
eg : /oraapp/mfgtestcomn/java/oracle/apps/media .
Implement the switcher case , add the fire action to this Image Column , create a transient attribute and attach to this
column . Depending on the value returned by transient attribute display the image on the column .
Let me know if its not clear .
Keerthi

How to increase the default length of an attribute of a BO

Hi All,
I have created a BO.It is having one attribute called title of type String with default length 30.I deployed it and it is working fine.
Now i want to increase its default length to 256.I opened the table generated for this BO and increased its length.But, when i regenerating the code its length is again getting reset to the default length 30.I tried it through Dictionary perspective also.
Any Suggestions.
Regards
Sampath

Hi All,
I resolved my problem. Just we have to change the data type to xLongText.
Sampath

How to increase the Field length

Hi All ,
I have to increase the Standard Field length in a transaction.
is that possible ? if yes , how we can do that ?
thanks and regards,
Deepak Rana.

it is not advisable to change the format of standard SAP table fields. most of them are being used in many different places, you will have a hard time making sure that all functionality still works OK after such a change.
maybe you can append new fields to ADRC and work with these.
Greetings
Thomas

How to Increase the Length of Condition table in OV20

While creating a condition table in T.code OV20 if fields length is more that 50 bytes table is not getting generated.it gives error as Too Many Fields Selected(More than 50 Bytes).
Actually i need to create a tabel with Basic Material(WRKST) which has length of 48 bytes.
Is there a solution on how to increase the length so that error is avoided.
There is no such error occuring while crating condition table in V/03

Hi,
You can try to use the type string:
form like zscr_data_hdr-form,
werks like zscr_data_hdr-werks,
matnr like zscr_data_hdr-matnr,
verid like zscr_data_hdr-verid,
lot like zscr_data_hdr-lot,
lot_qty like zscr_data_hdr-lot_qty,
udate like zscr_data_hdr-udate,
utime like zscr_data_hdr-utime,
zuser like zscr_data_hdr-zuser,
processed like zscr_data_hdr-processed,
defect like zscr_defect_data-defect,
vornr like zscr_route_data-vornr,
fieldxx type string,
dayst like zscr_data_hdr-dayst,
end of t_data.
So you can save you informations of every fld<n> concatenating their values into fieldxx.
Regards

How to increase the length of internal table dynamically

How to increase the length of internal table dynamically depending on the number of fields fetched into the internal table ?
The requirement code :
types: begin of t_data,
         form          like zscr_data_hdr-form,
         werks         like zscr_data_hdr-werks,
         matnr         like zscr_data_hdr-matnr,
         verid         like zscr_data_hdr-verid,
         lot           like zscr_data_hdr-lot,
         lot_qty       like zscr_data_hdr-lot_qty,
         udate         like zscr_data_hdr-udate,
         utime         like zscr_data_hdr-utime,
         zuser         like zscr_data_hdr-zuser,
         processed     like zscr_data_hdr-processed,
         defect        like zscr_defect_data-defect,
         vornr         like zscr_route_data-vornr,
         fld1          like zscr_defect_data-defect_val,
         fld2          like zscr_defect_data-defect_val,
         fld3          like zscr_defect_data-defect_val,
         fld4          like zscr_defect_data-defect_val,
         fld5          like zscr_defect_data-defect_val,
         fld6          like zscr_defect_data-defect_val,
         fld7          like zscr_defect_data-defect_val,
         fld8          like zscr_defect_data-defect_val,
         fld9          like zscr_defect_data-defect_val,
         fld10         like zscr_defect_data-defect_val,
         fld11         like zscr_defect_data-defect_val,
         fld12         like zscr_defect_data-defect_val,
         fld13         like zscr_defect_data-defect_val,
         fld14         like zscr_defect_data-defect_val,
         fld15         like zscr_defect_data-defect_val,
         fld16         like zscr_defect_data-defect_val,
         fld17         like zscr_defect_data-defect_val,
         fld18         like zscr_defect_data-defect_val,
         fld19         like zscr_defect_data-defect_val,
         fld20         like zscr_defect_data-defect_val,
         fld21         like zscr_defect_data-defect_val,
         fld22         like zscr_defect_data-defect_val,
         fld23         like zscr_defect_data-defect_val,
         fld24         like zscr_defect_data-defect_val,
         fld25         like zscr_defect_data-defect_val,
         fld26         like zscr_defect_data-defect_val,
         fld27         like zscr_defect_data-defect_val,
         fld28         like zscr_defect_data-defect_val,
         fld29         like zscr_defect_data-defect_val,
         fld30         like zscr_defect_data-defect_val,
         fld31         like zscr_defect_data-defect_val,
         fld32         like zscr_defect_data-defect_val,
         fld33         like zscr_defect_data-defect_val,
         fld34         like zscr_defect_data-defect_val,
         fld35         like zscr_defect_data-defect_val,
         fld36         like zscr_defect_data-defect_val,
         fld37         like zscr_defect_data-defect_val,
         fld38         like zscr_defect_data-defect_val,
         fld39         like zscr_defect_data-defect_val,
         fld40         like zscr_defect_data-defect_val,
         fld41         like zscr_defect_data-defect_val,
         fld42         like zscr_defect_data-defect_val,
         fld43         like zscr_defect_data-defect_val,
         fld44         like zscr_defect_data-defect_val,
         fld45         like zscr_defect_data-defect_val,
         fld46         like zscr_defect_data-defect_val,
         fld47         like zscr_defect_data-defect_val,
         fld48         like zscr_defect_data-defect_val,
         fld49         like zscr_defect_data-defect_val,
         fld50         like zscr_defect_data-defect_val,
         fld51         like zscr_defect_data-defect_val,
         fld52         like zscr_defect_data-defect_val,
         fld53         like zscr_defect_data-defect_val,
         fld54         like zscr_defect_data-defect_val,
         fld55         like zscr_defect_data-defect_val,
         fld56         like zscr_defect_data-defect_val,
         fld57         like zscr_defect_data-defect_val,
         fld58         like zscr_defect_data-defect_val,
         fld59         like zscr_defect_data-defect_val,
         fld60         like zscr_defect_data-defect_val,
         fld61         like zscr_defect_data-defect_val,
         fld62         like zscr_defect_data-defect_val,
         fld63         like zscr_defect_data-defect_val,
         fld64         like zscr_defect_data-defect_val,
         fld65         like zscr_defect_data-defect_val,
         fld66         like zscr_defect_data-defect_val,
         fld67         like zscr_defect_data-defect_val,
         fld68         like zscr_defect_data-defect_val,
         fld69         like zscr_defect_data-defect_val,
         fld70         like zscr_defect_data-defect_val,
         fld71         like zscr_defect_data-defect_val,
         fld72         like zscr_defect_data-defect_val,
         fld73         like zscr_defect_data-defect_val,
         fld74         like zscr_defect_data-defect_val,
         fld75         like zscr_defect_data-defect_val,
         fld76         like zscr_defect_data-defect_val,
         fld77         like zscr_defect_data-defect_val,
         fld78         like zscr_defect_data-defect_val,
         fld79         like zscr_defect_data-defect_val,
         fld80         like zscr_defect_data-defect_val,
         fld81         like zscr_defect_data-defect_val,
         fld82         like zscr_defect_data-defect_val,
         fld83         like zscr_defect_data-defect_val,
         fld84         like zscr_defect_data-defect_val,
         fld85         like zscr_defect_data-defect_val,
         fld86         like zscr_defect_data-defect_val,
         fld87         like zscr_defect_data-defect_val,
         fld88         like zscr_defect_data-defect_val,
         fld89         like zscr_defect_data-defect_val,
         fld90         like zscr_defect_data-defect_val,
         fld91         like zscr_defect_data-defect_val,
         fld92         like zscr_defect_data-defect_val,
         fld93         like zscr_defect_data-defect_val,
         fld94         like zscr_defect_data-defect_val,
         fld95         like zscr_defect_data-defect_val,
         fld96         like zscr_defect_data-defect_val,
         fld97         like zscr_defect_data-defect_val,
         fld98         like zscr_defect_data-defect_val,
         fld99         like zscr_defect_data-defect_val,
         fld100         like zscr_defect_data-defect_val,
         fld101         like zscr_defect_data-defect_val,
         fld102         like zscr_defect_data-defect_val,
         fld103         like zscr_defect_data-defect_val,
         fld104         like zscr_defect_data-defect_val,
         fld105         like zscr_defect_data-defect_val,
         fld106         like zscr_defect_data-defect_val,
         fld107         like zscr_defect_data-defect_val,
         fld108         like zscr_defect_data-defect_val,
         fld109         like zscr_defect_data-defect_val,
         fld110         like zscr_defect_data-defect_val,
         fld111         like zscr_defect_data-defect_val,
         fld112         like zscr_defect_data-defect_val,
         fld113         like zscr_defect_data-defect_val,
         fld114         like zscr_defect_data-defect_val,
         fld115         like zscr_defect_data-defect_val,
         fld116         like zscr_defect_data-defect_val,
         fld117         like zscr_defect_data-defect_val,
         fld118         like zscr_defect_data-defect_val,
         fld119         like zscr_defect_data-defect_val,
         fld120         like zscr_defect_data-defect_val,
         fld121         like zscr_defect_data-defect_val,
         fld122         like zscr_defect_data-defect_val,
         fld123         like zscr_defect_data-defect_val,
         fld124         like zscr_defect_data-defect_val,
         fld125         like zscr_defect_data-defect_val,
         fld126         like zscr_defect_data-defect_val,
         fld127         like zscr_defect_data-defect_val,
         fld128         like zscr_defect_data-defect_val,
         fld129         like zscr_defect_data-defect_val,
         fld130         like zscr_defect_data-defect_val,
         fld131         like zscr_defect_data-defect_val,
         fld132         like zscr_defect_data-defect_val,
         fld133         like zscr_defect_data-defect_val,
         fld134         like zscr_defect_data-defect_val,
         fld135         like zscr_defect_data-defect_val,
         dayst         like zscr_data_hdr-dayst,
       end of t_data.
In this fld1 to fld135 are defined in internal table.
But if the number of fields are more than 135 then the program is going to short dump.
Some times fld1 to fid170 or more fields will be there in my internal table.
Please suggest me how to make my requirement dynamic and display this data fetched into this internal table onto a .XLS file in the presentation server ?

Hi
You can try to use the type string:
form like zscr_data_hdr-form,
werks like zscr_data_hdr-werks,
matnr like zscr_data_hdr-matnr,
verid like zscr_data_hdr-verid,
lot like zscr_data_hdr-lot,
lot_qty like zscr_data_hdr-lot_qty,
udate like zscr_data_hdr-udate,
utime like zscr_data_hdr-utime,
zuser like zscr_data_hdr-zuser,
processed like zscr_data_hdr-processed,
defect like zscr_defect_data-defect,
vornr like zscr_route_data-vornr,
fieldxx type string,
dayst like zscr_data_hdr-dayst,
end of t_data.
So you can save you informations of every fld<n> concatenating their values into fieldxx.
Max

How to increase the row and Column length of Bex query in EP Portal 7.3

Dear All,
Please let me know the process to Increase the Rows and Columns Size of Bex Query in Enterprise Portal of SAP 7.3 .
Please let settings to increase rows up 10000 and column 100 in one page.
Thanks
Regards,
Sai

Dear All,
Please find the attached screen shot.
The report be open with 4 or 5 columns and 5 or 6 rows.
So, please let me know how to increase the length of the table.
Do the needful for me to over come this issue.
Thanks
Regards,
Sai.

How to Increase the Selection screen window length width big....

How to Increase the Selection screen window length width big.... I cant able to do some enter text... because of the window size it gives error... can anyone help me out this...
Thanks in advance

hi,
Maximum size is fixed for selection-screen.
Split your text into different lines to fit it.
Create a text element for your text and write it as comments.
selection-screen begin of block b3 with frame title text-041.
selection-screen begin of line.
    parameters : p_all radiobutton group g2 default 'X'.
    selection-screen comment 10(75) text-049.
selection-screen end of line.
selection-screen begin of line.
    parameters : p_iloc radiobutton group g2.
    selection-screen comment 10(75) text-050.
selection-screen end of line.
selection-screen end of block b3.
Regards
Sailaja.

How to increase the DFF fields length

Hi Gurus,
its very urgent requirement ,how to increase the dff field length in standard page i.e self-service appraisal page,please help me
Regards,
Sreeni

Hi Ayaz/Sreese,
As per my requirement user enable the DFF Fields in perticuler pages in sshr module like PMS So ...i create the attribute columns and viewinstance through personlization create the column and i give the hight and lenght in column cration time i create the id like "XXApr" same id name i gave in DFF Field Names.....so i did like ....this is my approch.....
---u have any doubts fell free to post the mail..i fwd through screen shots then only u undershood ,([email protected])
Regards,
Srinivas

How can we increase the character length of SAP batch???

HI MM guru's,
we want to increase the character length for the SAP batch i.e raise it to 14 characters. how can we posibbly do that live.
Regards,
Sameer Jalal

thanks,
but any alternative?
Regards,
Sameer Jalal

How to increase the battery life of your N series ...

What I am about to post here is valid for any 3G phone or device regardless of model but it is particularly focused towards the N series devices and their power hogging features.
Your battery life is dependant on many many things. How often you take calls on the device, the condition of your battery, the features you use on the device and so on and on. Therefore it is impossible to say that by following the information in this post you will get x amount of days battery life, but it will get you more time out of the battery than you otherwise would have got.
So with that out the way, if your looking to increase your battery life then follow these tips and your battery should start looking a lot healthier.
First of all lets start with THE big one. The one that is going to save you the most juice. Switching 3G off.
Yep, you heard me right. Just by switching the 3G capability of your phone off you will add hours and hours to your battery life. How is this so? Allow me to explain...
Due to the rather poor delivery of 3G in the UK by the network operators, it is rare for any 3G phone to maintain a constant 3G signal. Instead you will find that the phone constantly flips between 3G and GSM mode (Keep an eye on your signal one day). Even those of you on Vodafone who probably have the best 3G network coverage will find this is the case.
Unfortunately, this constant flipping between the two modes sucks power from the battery like a vampire as it alters its reception state for the different modes and the constant flipping is..well...causing it do this constantly! It can sometimes even make your phone unavailable for calls for very brief periods as it trips from GSM to 3G and vice versa.
If you need to use 3G for video calls or whatever then I'm afraid your just going to have to live with this but if you don't (And lets face it few of us do) then you can switch 3G off and increase your battery life considerably.
To do this, go into the "Settings" application (Found in the menu somewhere, by default Nokia normally stick it in "Tools"), and then to the "Phone" tab. In there you will see an option that says "Network mode" and you have a choice of "GSM" or "Dual Mode" (I.e. UMTS and GSM). Set it to GSM and your phone will restart. Once it restarts it will be working in GSM with GPRS speeds only but really for most purposes this is fine.
You have now just extended your battery capability considerably. You can further extend it by going to the "Connection" tab, going into "Packet data" and changing it to "When needed" so it is not constantly checking for a data connection.
The second big change you can make is to turn your phones wifi scanning capability off. The last time I looked not all Nokia's phones that have wifi capability can have their wifi cards switched off entirely but if you can, turn it off except for when you need to use it. Wifi is a power hog.
The next big change you can make is to lower the screen brightness settings on your phone. The less bright your screen is the less power is being used to light it up. Nokia by default leave the screen brightness at something like 50%. Lowering this a bit more will conserve more juice. Before you do this though please consider the fact that lowering the brightness setting will have a big impact on your ability to see the screen clearly in sunny conditions although you will be fine in the dark as you can't lower the brightness that far.
To lower the brightness, go to the settings tool in your phone and into the display option (Hidden in a subcategory called "Personalisation" on the N95). It won't hurt to set the power saving time out to 1 minute and the backlight time out to 10 seconds while your here (Although these are the Nokia default so they should already be set to this).
Finally in regards to the screen, although they may look pretty, animated screensavers use more battery power than the standard blank screen with time and date so avoid them if you can.
It also helps to keep Bluetooth switched off until you need it although the power savings are minimal in comparison to the other changes but every little milliamp counts!
Using the above methods I generally get about 3 to 4 days with about 3 hours talktime on my N95 without using Bluetooth, GPS or anything like that (I might be able to get more but so far I have not paid attention to the battery state before I put it on charge). If I am on a long train journey I can get about 4 hours worth of full screen video and about 2 hours talktime over the period of about 24 hours before it needs a recharge. As I said at the start of the post your mileage will vary greatly depending on how you use your device.
Hope this helps.
Useful links: Phone firmware update | Nokia support site

02-May-200701:14 PM
bixby wrote:
no keffa it is a cop out from nokia
its not unfai as its a premium device with a premium price
the n95 battery is atrocious
dont change the post content as the title is 'How to increase the battery life of your N series device'
your talking about nokia phones specifically
the networks are not to blame
they do not make the handsets : Nokia do !!!!!!!!!!
I'm going to choose my words carefully here...
I would never deny the battery on the N95 is not really up to the job of powering the N95 with its power hungry features. To put the same battery into a phone that has WiFi, GPS and a large 320x240 screen, the same one that goes into the E65 which has comparatively nothing compared to it is a bit pants.
However at no point was I criticising them for the band hopping problem. I labelled the post as how to increase the battery life of your N series device because this is a board for the N series devices. It was a simple choice of wording and not intended to be cutting in any way and I did make a remark that the details would be true of any 3G device at the top of the post.
What I was trying to point out in my second post is that the constant band hopping the phone is being forced to do that is draining its battery so much more quicker than it would if it had a constant signal of one kind or another isn't quite Nokia's fault.
They build it to conform to a laid out specification for 3G. However if the network operators cannot be bothered to roll out their 3G infrastructure adequately enough that the phone can find and remain locked onto a 3G signal that is usable then what are Nokia to do other than offer you the capability to turn 3G off until you need it (Although note to Nokia: That **bleep** reboot the phone does when you do this is entirely unneeded and you know it).
Blaming Nokia for this would be like blaming the manufacturer of your radio for failing to pick up radio because the radio station does not have any transmitters within range of your radio's receiver.
Finally...this band hopping is exhibited by all 3G phones built by Samsung, Nokia, Sony Ericsson, etc, from their most budget 3G model to their priciest piece and is the reason that all phones with 3G capabilities have batteries that do not last for any respectable length of time because these phones are also having to band hop between 3G and GSM.
Finally the proof is in the pudding. Turn 3G off for a few days. See your battery improve. Then (Although admittedly this will be harder to do...mcuh harder) find an area where you get a fairly decent 3G signal constantly. Again, see your battery improve. Try it with a different 3G phone...different manufacturer even. The same will be true.
So I stand by my comment, the network operators and their woeful 3G rollout are the villains costing you a fair chunk of your battery and Nokia cannot be expected to mitigate this....but a better battery would be nice all the same...
Useful links: Phone firmware update | Nokia support site

How to increase the size of the applet/ form displayed on the bowser

kindly guide me how to increase the size of the applet / forms displayed on the browseri.e the width and length of the forms/applet so that i can display all the controls on the form .
thanks with regards

i changed the value of width and height in formsweb.cfg file in my devsuite_home/forms/server/formsweb.cfg , i am able to see the result when i compile and run the form in devsuite, whereas the same is not reflected when i run the same form in application server.
when i tried to change the value of abbovementioned file in oracle_home /forms/server/formsweb.cfg of the application server file , the file does not have the applet wdth and applet height values. in fact this file does not have any applet information..
pls guide
thanks with regards.

How To Increase the Size of Memo Fields 4000 Char in WebCenter 11g?

How To Increase the Size of Memo Fields greater than 4000 Char in WebCenter Content (UCM) 11g?
I was able to increase the size of Memo field from 2000 Char to 4000 by setting parameter value MEMOFIELDSIZE=4000 . But the requirement is to increase the size more than 4000 around 7000 char but Database(Oracle 11G) is not supporting more than 4000 char.
Is there any other way to increase the size of Memo field?
Thanks in Advance!!
Regards
Ram

Hello All,
Thanks for your responses.
Let me explain the scenario again in detail:
1. we have three meta-data fileds xProductCategory,xProductFamily and xProducts
2. These fields are related with DCL feature and corresponding values are being stored in corresponding custom Views
3. xProducFamily is dependent of xProductCategory and xProduct is dependent on xProductFamily
4. currently, there are around 250 Product values and average name of Product can be of 25 Char, so if we are selecting all product values for some Contents then Product Values are being stored in DocMeta table as comma separated values with one space, so total characters are being very high than 4K Char.
5. Currently view that is storing the Product values, stores "Name" column instead of ID(like 1,2,3....)
6. And our Content Server is integrated with Oracle WebSenter Portal, where logic has written to retrieve the contents based on "Product Name" instead of "Product ID" and already we are in UAT phase.Currently we are not in situation to revert the changes from Product Name to Product ID.
7. Also if we are storing the values on the basis of Product ID, then again the issue may arise in Future, if the number of Products increased.
Hoping the issue explanation is clear now and waiting for some possible solution for increasing the length of memo field.
Thanks in Advance !!
Regards
Ram

How to Increase the retreving size of instances using PAPI filters.

Hi,
How to Increase the retreving size of instances using PAPI filters.
In my engine database instance size exceeds 2500 then we are getting following exception.
If we login in to user workspace able to see the instances but while trying to retrieve from PAPI getting below exception and showing the user's inbox aize as 0.
In Process Admin console we set all the required parameters.
Still I m getting the same problem.
Can you please lgive mev the solution.
<Mar 23, 2010 8:58:24 PM SGT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: fuego.ejbengine.EJBProcessControl_1zamnl_EOImpl.getInstancesByFilter(Lfuego.papi.impl.j2ee.EJBSecureEngineInfo;Ljava.lang.String;Lfuego.papi.Filter;)
java.lang.ClassCastException: cannot assign instance of java.util.HashSet to field fuego.view.FilterImpl.attributes of type java.util.List in instance of fuego.view.FilterImpl.
java.lang.ClassCastException: cannot assign instance of java.util.HashSet to field fuego.view.FilterImpl.attributes of type java.util.List in instance of fuego.view.FilterImpl
     at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2032)
     at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1212)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1953)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
Regards,
Bharath.
Edited by: bg57295 on Mar 24, 2010 6:45 PM

Hi Bharath,
Believe me, you have an incompatibility between different build#.
PAPI has an instance cache. When certain process has more instances than the maximum specified, the cache is switch to status OPEN. That means, that PAPI will not be able to resolve some instance queries using the information in the cache. When that occurs, PAPI forward all those queries to the engine.
The incompatibility introduced is in the communication between PAPI and Engine. So, you only get the exception when you have more instances than the maximum cache size.
Regards,
Ariel

How to increase the string length of an uploaded file

Similar Messages

Maybe you are looking for