How to increase field length?

How to increase field length?
path -> in T Code MM01 -> Additional Data ->Unit of mesure (tech name UMREZ)
default length is 5 digits i want increase 7 digits................

HI,
I don't thing it is at all possible. Because your field is a standard one and the 3 available exits in MM01
MGA00001            Material Master (Industry): Checks and Enhancements
MGA00002            Material Master (Industry): Number Assignment
MGA00003            Material Master (Industry and Retail): Number Display
can not help it.
Regards,
Anirban

Similar Messages

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 field size in Internal table

Hi friends,
I want to concatenate around 20 fields in one internal table field,
i declared the destination filed as character, now i am able to get around 12 to 13 fileds only , how to increase the length of this field to include all fields ?
or how can i do this ? can any body help me ?
I concatenate this to create a file which will be send as email attachment.
its very urgent issue, kindly help me to resolve as early as possible.
Thanks in advance.
Joseph

Hi,
Use the string data type..
Example
DATA: IT_STRING TYPE STRING OCCURS 0 WITH HEADER LINE.
DATA: BEGIN OF WA,
             MATNR(18),
             WERKS(4),
             VBELN(10),
           END OF WA.
CONCATENATE WA-MATNR WA-WERKS WA-VBELN INTO IT_STRING.
APPEND IT_STRING.
Thanks,
Naren

How to increase field's number when update

What value should I set when I want to make some field increase ,
such as "UPDATE table SET field = field + 1";

Hi, chan15
Please checkou this tutorial, it shows you how to increase field counter by updating the field value by adding +1 everytime you reload th page...
:: Visits Hit Counter ::
Herein this tutorial we will learn how to implement an auto visits hit counter. The visits hit counter uses an "After" "Custom_Trigger" to update the (hits_ht) field by adding (current field value
+1
) to it, This script is very useful, specially when used to view member`s profiles, photo albums etc... by implementing this hit counter script with your database records you will get full reports about how many times profile, photo viewd by members or visitors.

SAP - How To increase Spool Length

Hi All,
I had some text to display but its length is very large and while displaying in the spool the text is getting truncated and even when i am downloading the spool i am getting the Truncated text.
Please let me know how to increase the length of the spool so that i can get the full text at the spool request.
Regards,
Himanshu Sharma

Report zreport line-size 300
Also while defineing jon in background see you select the printer with maximun column length.

How to increase the length of the subject line in email using FM

Hi
we have maintained 50 characters for the subject line initially, but some subjects are having more than 50 characters. how can we increase the length of the subject line in email.
urgent.
points will be rewarded generousely.

Hi Rana,
In this case, you have to create a user defined field of required length under Journal Transactions Header to fill the data.
Regards,
Vijay Kumar
SAP Business One Forums Team

Increase field length in a Generic extractor

Hello All,
We have a generic extractor which extracts data from a function module. How can I increase the length of a field in this extractor. Please sugest.
Regards
Madhavi

Dear Madhavi,
Edit that field in relevant R/3 table and increase the length.
Dont forget to change the same in the code of your FM Global Data declaration if you have.
Regards,
R.

How to increase the length of the identifier?

I want to create a table with a column name as:
"domainnameregistrationassistance"
oracle 9i does not allow me to do this.
as the identifier length is fixed to 30 characters.
how do i increase the length of the identifier?
any help on this will be great!

Don't forget that there is a comment space for each table
and column, so calling the column DNR_ASSIST doesnt
revent you from doing ...
COMMENT ON TABLE M_SCHEMA.DNR_ASSIST IS '
Domain Name Registration Assistance';

How to increase the length of Remarks in Journal Vouchers

Hi SAP Guru,
I am new in SAP Business One. Normally our Narration which we feed in Details of Journal Voucher is longer than the space provided. Is there any way to increase the length of Details field in Journal Voucher or Some other way we can cater this requirement.
Thanks for answers in advance
J.S.Rana

Hi Rana,
In this case, you have to create a user defined field of required length under Journal Transactions Header to fill the data.
Regards,
Vijay Kumar
SAP Business One Forums Team

How to increase the length of description

Dear Guru's
we want to increase the length of Decription field in thBOM Item line 1 item line 2.can we increase the length.presently its having 40 characters capacity.
Thanks & Rgds
Pankaj Agarwal

1.I dont think this is possible as this is a standard SAP requriement.
2.check the data eleaement -which has the 40 as character lenth.
so it is not recomended to change it.
Solution
3.You can use the ItemLongTEXT - which doesnt have any restriction in the lenght.
so dont change the standard setting use the itmelONGTEXT this should solve ur issue
Reg
Dsk
Edited by: SatheeshkumarD on May 8, 2008 11:01 AM

How to set field length in Dynamic IT tab

Hi All,
 I am creating 1 dynamic internal table with refrence of field catalog, but in the dynamic IT tab and work area i am gettinf field length is 10 char.
But i want to change this into 15 or 20 char like this.... how can i change this
Please help me .
DATA: ep_tab TYPE REF TO data,
 new_line TYPE REF TO data.
FIELD-SYMBOLS: <l_table> TYPE table,
 <l_line> TYPE ANY.
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 I_STYLE_TABLE = c_char
 it_fieldcatalog = it_fieldcatalog
 I_LENGTH_IN_BYTE = ' '
 IMPORTING
 ep_table = ep_tab.
ASSIGN ep_tab->* TO <l_table>.
CREATE DATA new_line LIKE LINE OF <l_table>.
ASSIGN new_line->* TO <l_line>.
This is my code.
Regards,
Arjun.

Hi,
try this
** ALV DECALRATION
DATA : wa_lvc_cat TYPE lvc_s_fcat,
 gt_lvc_cat TYPE lvc_t_fcat.
DATA : wa_fieldcat TYPE slis_fieldcat_alv,
 gt_fieldcat TYPE slis_t_fieldcat_alv.
DATA : wa_slis_layout TYPE slis_layout_alv.
PERFORM create_dynamic_itab. " Fill fieldcatlog and create dynamic itab
*& Form CREATE_DYNAMIC_ITAB
* text
* --> p1 text
* <-- p2 text
FORM create_dynamic_itab .
CLEAR g_pos .
PERFORM fill_gt_lvc_cat_fld USING 'MATNR' 18 . "fieldname outputlen.
PERFORM fill_gt_fieldcat_field USING c_x 'MATNR' 'CHAR' 18 text-006.
PERFORM fill_gt_lvc_cat_fld USING 'CODE' 40 .
PERFORM fill_gt_fieldcat_field USING ' ' 'CODE' 'CHAR' 40 text-024.
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = gt_lvc_cat
 IMPORTING
 ep_table = new_table.
ENDFORM. " CREATE_DYNAMIC_ITAB
*& Form FILL_gt_lvc_cat_FLD
* text
* -->P_0006 text
* -->P_18 text
FORM fill_gt_lvc_cat_fld USING p_fieldname TYPE any
 p_outputlen TYPE any.
wa_lvc_cat-fieldname = p_fieldname . " 'MATNR'
wa_lvc_cat-outputlen = p_outputlen. " 18
APPEND wa_lvc_cat TO gt_lvc_cat.
CLEAR wa_lvc_cat.
ENDFORM. " FILL_gt_lvc_cat_FLD
*& Form FILL_GT_FIELDCAT_FIELD
* text
* -->P_C_X text
* -->P_0012 text
* -->P_0013 text
* -->P_18 text
* -->P_TEXT_006 text
FORM fill_gt_fieldcat_field USING p_key TYPE any
 p_fieldname TYPE any
 p_datatype TYPE any
 p_outputlen TYPE any
 p_seletext_m TYPE any.
g_pos = g_pos + 1.
wa_fieldcat-col_pos = g_pos. " 1.
wa_fieldcat-key = p_key . " c_x.
wa_fieldcat-fieldname = p_fieldname. " 'MATNR'.
wa_fieldcat-datatype = p_datatype. " 'CHAR'.
wa_fieldcat-outputlen = p_outputlen. " 18.
wa_fieldcat-seltext_m = p_seletext_m. " text-006. "'Material'.
APPEND wa_fieldcat TO gt_fieldcat.
CLEAR wa_fieldcat.
ENDFORM. " FILL_GT_FIELDCAT_FIELD
PERFORM fill_output_layout. " Fill the output data into field symbol
*& Form FILL_OUTPUT_LAYOUT
* text
* --> p1 text
* <-- p2 text
FORM fill_output_layout .
ASSIGN new_table->* TO <fs_table>.
CREATE DATA new_line LIKE LINE OF <fs_table>.
ASSIGN new_line->* TO <fs_line>.
LOOP AT gt_mseg INTO wa_mseg.
 ASSIGN COMPONENT 'MATNR' OF STRUCTURE <fs_line> TO <fs_field>.
 <fs_field> = wa_mseg-matnr.
 READ TABLE gt_grdtrans INTO wa_grdtrans WITH KEY mawerk = wa_mseg-WERKS
 matnr = wa_mseg-matnr
 mat_doc = wa_mseg-mblnr binary search.
 IF sy-subrc = 0.
 LOOP AT gt_qmfe INTO wa_qmfe WHERE qmnum = wa_grdtrans-qmnum.
 READ TABLE gt_qpct2 INTO wa_qpct2 WITH KEY codegruppe = wa_qmfe-fegrp
 code = wa_qmfe-fecod
 BINARY SEARCH .
 IF sy-subrc = 0.
 ASSIGN COMPONENT 'CODE' OF STRUCTURE <fs_line> TO <fs_field>.
 <fs_field> = wa_qpct2-kurztext.
 ENDIF.
 endloop.
 clear wa_qmfe.
 ENDIF.
ENDLOOP.
 CLEAR wa_mseg.
PERFORM fill_layout. " Filling the layout of REUSE_ALV_GRID_DISPALY
*& Form FILL_LAYOUT
* text
* --> p1 text
* <-- p2 text
FORM fill_layout .
wa_slis_layout-zebra = c_x.
wa_slis_layout-colwidth_optimize = c_x.
ENDFORM. " FILL_LAYOUT
Edited by: ShaliniSinha on Mar 30, 2009 1:49 PM
Edited by: ShaliniSinha on Mar 30, 2009 1:55 PM

How to add field length constraints when using an existing JavaBean model

Within our current project we used a O/R mapping tool to generate our JavaBean model. For e.g.
public class Person{
private String name; ...getName() ...setName(...)
}
The whole model is used within our Web Dynpro project. Now it's a requirement to implement field length constraints. Normally this is no problem using ISimpleType like the following:
attributeInfo = wdContext.nodePerson().getNodeInfo().getAttribute
(IPrivate...IPersonElement.NAME);
ISimpleTypeModifiable type = attributeInfo.getModifiableSimpleType();
type.setLength(60);
But we've got an runtime exception that it is not allowed to modify the models datatype:
com.sap.tc.webdynpro.progmodel.context.ContextException: AttributeInfo
(Basics.Person.name): must not modify the datatype of a mapped attribute
at
com.sap.tc.webdynpro.progmodel.context.AttributeInfo.getModifiableSimpleType
(AttributeInfo.java:337)
The question is how could a workaround look like. Or is there nothing like that and we have to build a dictionary type tier upon our JavaBean model. Any ideas ?
thx,
s.w.

Sabine,
You may:
1. Import JavaBeans model
2. Create DDIC type with necessary constarints (string-based, max. length 60)
3. Open editor for target model class and change type of property.
See my blog /people/valery.silaev/blog/2005/06/29/apojo--almostplain-old-java-objects-as-model (section "Tweaking model classes") for details.
Valery Silaev
EPAM Systems
http://www.NetWeaverTeam.com

How to increase the length of the Info object

Hi All
Any one have idea about how to increse the length of the Info object Char(beyond 60). Can you please explain me in detail we are using BI7.0.
Thanks
Vani

Hello Vani,
You cannot increase the length of an info-object beyond 60 chars.However if you want to store a characteristics data with more than length 60, then you may create separate info-objects
for example: if you need to store 'notes' which might have length more than 60,
then you may create info-objects like notes 1/3 ---store first 60 chars.
notes 2/3 --- store next 60 characters and so on.
Thanx
Priyanka

How to Increase the length of Material Code (MATNR)

Hi all,
I have the requirement to increase the size of Material code (from 18 characters to 30 Characters) .
Is their any provision for this in ERP 2005.
Let me know.
regards,
Sheo

You should not increase the length of the field.
You can do it by changing the domain for MATNR, but then you have to modify all programs and screens where MATNR is used.
The only impact of this is that SAP will disown your implementation and will not provide any free support. You have to pay their hefty consulting fee every time
Hope this answers,
Lakshman

How to increase field length?

Similar Messages

Maybe you are looking for