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

Similar Messages

  • How to change the field length in standard sap program.

    Hi All,
    How to change the field length in standard sap program.
    Urgent
    Example:
    Text1 type c length 75,
    To change :
    Text1 type c length 150,
    Point will be rewarded..
    Thank you,
    Vikram.C

    If the only solution is to change the sap standard program, simply change the program, it will prompt for an access key. This key can be retrieved in the SAP support portal (service.sap.com) at keys and requests, sccr keys, register object.
    Sometimes these actions are outsourced to a competence center, so maybe youre not entitled to do this, in any case ask a resident senior developer for support.
    regards, Rob

  • 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 extend the fields length

    Hi Experts,
    I want to increase the fields length of my BP name in portal .
    now it is 40 char in one line but i want 60 char in one line .Can any body send the solution.
    Thanx in advance
    Regards,
    Khurram

    Default length of BP Name field is 40 chars in length.You cannot change this ..
    Thirumala.

  • How to increase the field size in modules

    Dear Oracle Team,
    When we add some items in reason codes from the dictionary, it has certain limit in reason code and title. So I can increase those field size to add bigger text for title names.
    I think it also applicable for the fields in other modules also. Looking your valuable support.
    Thanks & Regards,
    Sheik

    1.  Once you add a custom field to your database, it would be made available to either your reports (BI) or your layouts in PCM.
    2.  When you create the custom field, you would specify the field length/type/properties.  (i.e. "Char" field with 120 char field length)  If you set this to one value when you create (say 120 char) and want to CHANGE it to 140 characters, you cannot do this without deleting and re-creating the custom field.  I did check 14.0.3 and this continues in this version as well.
    2a.  Best practice is to be generous in your field sizes to avoid needing to change it later.
    As I mentioned before, any default fields in the database are fixed to their set properties and the only way to change them is to submit an SR to Oracle to request the change.

  • 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

  • Can we increase the field length of Packaging material type description

    Hi,
    The field length allowed for packaging material type description is 20 characters. If i need to have this length to be increased to 25-30.Is it possible?
    I mean the description that we give when we create new packaging material type.
    Pls let me know ur suggestions.

    Hi Dhilipan Nair,
    Unfortunately there is no standard way to change this, the desc. field of the view (V_TVTY-VTEXT) is created from the value T685T-VTEXT which has been defined with the Domain TEXT20, so in order to add addition characters to this field, you would need to redefine the preceding field type.
    Regards
    Stephen

  • How to increase the field lenght of file uplaod in BSP application

    Hi All,
       I am facing a problem with u201Cuploadu201D filed length in BSP application.
    When we upload the file in BSP page, the path displayed should be the full path (i.e. from where the file is being upload the file)
    Now this field is appearing 20 char length
    Now I want to increase the length of the upload field (Input field) to be 100 char so that the path is visible.
    In the current application the file upload is being done through a structure (attributes)
    In this structure the fields are like this
    PAGE_NAME
    ID
    FOR
    TAGS
    ROW_INDEX
    COLUMN_INDEX
    OTR_NAME
    REQUIRED_NAME
    MAXLENGTH
    SIZE
    TABLE_NAME
    ON_SELECT
    VALUE
    DISABLED
    ONCLICK
    TEXT
    TYPE
    Using this method:
    CALL METHOD cl_htmlb_fileupload=>factory
              EXPORTING
                Id      = ls_form_save-id
              RECEIVING
                Element = lv_fileup.
            bee_table->add ( level = 2 element = lv_fileup ).
    This cl_htmlb_fileupload is named as class interface.
    Which has the CLG_HTMLB_FILEUPLOAD (it is a class) it is defined in attributes.
    In this class it has the attribute u201CSIZEu201D by default string 20.
    Now I need to change this attribute length from 20 to 100
    For this I copied the standard class CL_HTMLB_FILEUPLOAD into ZCL_HTMLB_FILEUPLOAD.
    This ZCL_HTMLB_FILEUPLOAD contains all attributes of the standard class CL_HTMLB_FILEUPLOAD
    Including the one class (CLG_HTMLB_FILEUPLOAD), this is defined as an attribute (ABOVE MENTIONED?)
    This class is appearing in non editable mode, so   I have copied this class into zclass (ZCLG_HTMLB_FILEUPLOAD).but still I am not able to edit the attribute called u201Csizeu201D
    And also I am not bale to add the zclass in place of the ZCLG_HTMLB_FILEUPLOAD
    Kindly tell me how to modify the length of the field u201Csize u201Cand also how to add the zclass in the attributes of one class (syntax)
    Thanks in advance
    Rambabu.A

    Hi,
    Class CLG_HTMLB_FILEUPLOAD is a class automatically generated when a BSP Element is created. You should not change/create such a class, unless by creating your own BSP Element.
    As per your requirement, you can use the SIZE parameter of method factory:
    ls_form_save-size = '100'.
    CALL METHOD cl_htmlb_fileupload=>factory
    EXPORTING
    Id = ls_form_save-id
    Size = ls_form_save-size
    RECEIVING
    Element = lv_fileup.
    Regards,
    Tanguy

  • 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

  • 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 alert field size?

    Hi Experts,
        In Adapter Error Description , i am tryin to get the entire error through mail/In Alert Inbox ......I hav changed the data type from Char70 to Char512 which is there in XI server abap stack. But I cannot get an error in alert inbos or my gmail account more than approx 83-85 charecters!!
    I know due to technical restrictions between the Workflow Container and SAPscript,only the first 80 characters of a container element are taken into account, when the variables are replaced during runtime, But experts, any special techniques!!!
    Regards,
    Arnab

    Hi,
    Here is a thread but with negative answer. check if it helps
    Alert: to increase the field length
    Thanks!

  • How to change the field lenght in stanard structure.

    hai Gurus,
    When I enhanced the standard structure for the 1st time I got warning but I could able to replicate and pull the data from r3 to bw. When I tried to enhance it again it is not allowing me saying i the need to enhance the standard data field length or need to add a custom field for this. Can you tell me how can change the field length for a standard structure?.
    Thanks, VP.

    hi,
    u can add a custom field of the required length to your structure and write the exit to populate it. If its a standard field I dont think you will be able to alter the length of the field.
    Regards.

  • 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 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

Maybe you are looking for

  • Problem in moving project from Old Sol Man 3.1 to New Sol Man 4.0

    Hi All, I am trying to move a project from solution manager 3.1 version to a new solution manager 4.0 version. I followed the below steps: 1.Slected and transported the project using solar_project_admin tcode and created the transort requests in the

  • Acrobat 9 inserting vertical lines after Optimize - Deskew

    Hi, Acrobat 9 Standard, Vista x64, 4gb ram. Creating a PDF from a series of Tiff images.  All is fine so far. I run the "Optimized Scanned PDF", choose only option as Deskew (all others off), highest-quality setting.  Then, I see several pages where

  • How to fix Facetime if you have a Vonage Router & Windows 7

    How to fix Facetime on Vonage Router with Windows 7: You need to add these to addresses (8.8.8.8 and 8.8.4.4) to the DNS Settings Here's how in Windows 7 Go to Local Area Connection, then Rightclick and choose properties. Then, select the Internet Pr

  • Phone falls asleep in middle of a call

    I was in the middle of a call and being asked to press 1 for such and such and the phone just went black even tho the call was still connected. Couldn't do anything to get the screen up and I had to reset. This never happened on my original phone. An

  • JTable - column move and column spacing

    Hi, Can someone please show me how to prevent users from being able to move columns. I am not finding any code to do this. Also, how do I set fixed width for columns. I am using vectors to populate the data Much appreciated