Max field length

HI Experts,
In SAP normally max field length is 255 characters.....but if i want to store 1000 character string into my field how can i do this..
any ideas..
Thanks
PT

Hi,
We can store in another way.
By creating table with the fields as in the structure 'TLINE'.
Two fields are there, one is for Line format and another one for Line Content.
In SAPscript, this is the concept used.
Using function module 'CONVERT_ITF_TO_ASCII', you will get your original text.
Regards,
R.Nagarajan.

Similar Messages

R/3 Field length 80, BW field max allowed 60

Hi all,
Field ABC is in R/3 production system.
Its length is 80(CHAR).
This field data is now to be extracted to BW.
It is used in extract program and updated to an extract table(R/3), then this has be loaded into a master load(BW).
But in BW the field length allowed is 60(Max).
So how to get in this 80 char data into BW??
Please let me know in detail.
Also please share links pertaining to this if possible.
Thanks,
Sowrabh

Hi Sowrabh,
Create two Infoobjects one with length 60 and one with length 20.
Now in transfer rules write routines for both.
IOB1 = <r/3 field>+0(60)
IOB2 = <r/3 field>+60(20)
Regards,
Mansi
Edited by: mansi dandavate on Apr 23, 2009 6:23 PM

Control an Integer field Length without using Validation ??

Hi,
I have Couple of fields where I need to configure them as Integers.
Now each one has a fixed length that i need to limit to.
But when i create a field of type: integer, i cannot select teh length!!!
To achive this the idea i have is to write a validation which checks length..
But can i achive it without going for a validation on each field???
PS: I am aware that TEXT field can limit the length But it also allows me to enter text values, my requirement clearly says that to allow users to only enter Numeric values..
Did anyone face a similar Case?
Kind Regards
Eva

Hi Eva,
I didn't try in the system, but I feel there are two solutions to achieve your requirement (*of course in both cases you will need to write a simple validation)
Solution 1 : When field is defined as "Integer" in Console.
lets take an example, you want to restrict an integer field with a limit of max 4 characters.
Maximum value of a 4 character integer can be "9999". So, you can put a simple validation to compare the field value with 9999. if the value is less then this means fields values is less than 4 characters, else more than 5 characters.
In this case Your validation expression in expression editor will be:
FIELD NAME<= "9999"
Solution 2 : When field is defined as "Text" in Console.
In this case you can restrict the maximum field length through Console. But you will also need to write a validation to ensure that user is not entering any alphabets or special characters in this field.
In this Case you can use below validation:
HAS_ALL_CHARS(FIELD NAME, "0","9")
This will ensure that field has all characters between 0 and 9 and doesn't hold any special character or alphabets.
In Both cases you will need to set "Automatic Execution" property as "Error". Also please do not manually type any function or value in expression editor. use drop down for fields, operators, functions etc. and enter numeric values using the first blank box before dimension list.
Kindly revert if you face any issues.
-Shiv

Token longer than max allowable length of 258 chars

Hi all,
i tried to apply a sql case statement in sql loader control file in " " the load succeed with 258 chars case or decode statement but when i add more cases it return
sql loader 350 token longer than max
LOAD DATA
INFILE 'F:\Vou\vou20110613_102_951454.unl'
BADFILE 'F:\Vou\vou.pad'
DISCARDFILE 'F:\Vou\vou.dic'
replace
INTO TABLE vou_test_2
FIELDS TERMINATED BY '|'
TRAILING NULLCOLS
(SERIALNO,TIMESTAMP "to_date(:TIMESTAMP,'yy/mm/dd hh24:mi:ss')",BRANDID,SUBCOSID,CHARGINGPARTYNUMBER,PAYTYPE,VOUCHERPINNUMBER,VOUCHERBATCHNUMBER,VOUCHERSEQUENCE,VOUCHERCOSID,VOUCHERSPID,CARDFACEVALUE,CARDVALUEADDED,CARDVALIDITYADDED,TRADETIME "to_date(:TRADETIME,'yy/mm/dd hh24:mi:ss')",OPERATEDBY,THIRDPARTYNUMBER,ACCESSMETHOD,TRADETYPE,RECHARGEAREANUMBER,TRANSITIONID,VOUCHERENCRYPTNUMBER,Location_Number,RESERVED2,RESERVED3,PRODUCTID,SERVICETYPE,OLDUSERSATE,CURRENTUSERSATE,PREVIOUSACTIVESTOP "to_date(:PREVIOUSACTIVESTOP,'yy/mm/dd hh24:mi:ss')",NEWACTIVESTOP "to_date(:NEWACTIVESTOP,'yy/mm/dd hh24:mi:ss')",SUSPENDSTOP "to_date(:SUSPENDSTOP,'yy/mm/dd hh24:mi:ss')",DISABLESTOP "to_date(:DISABLESTOP,'yy/mm/dd hh24:mi:ss')",VALIDITYADDED,REWARDCYCLES,REBATEPRODUCTID,BILLCYCLEID,SUBSCRIBERID,RESERVED4,RESULTCODE,ACCOUNTID,RECHARGETAX,RECHARGEPENALTY,CURRENCYCODE,RESERVED5,PREPAIDBALANCEBEFORE,RECHARGEFORPREPAID,PREPAIDBALANCE,POSTPAIDBALANCEBEFORE,RECHARGEFORPOSTPAID,POSTPAIDBALANCE,ACCOUNTTYPE1,REWARDAMOUNT1,CURRENTACCTAMOUNT1,ACCOUNTTYPE2,REWARDAMOUNT2,CURRENTACCTAMOUNT2,ACCOUNTTYPE3,REWARDAMOUNT3,CURRENTACCTAMOUNT3,ACCOUNTTYPE4,REWARDAMOUNT4,
CURRENTACCTAMOUNT4,ACCOUNTTYPE5,REWARDAMOUNT5,CURRENTACCTAMOUNT5,ACCOUNTTYPE6,REWARDAMOUNT6,CURRENTACCTAMOUNT6,ACCOUNTTYPE7,REWARDAMOUNT7
,CURRENTACCTAMOUNT7,ACCOUNTTYPE8,REWARDAMOUNT8,CURRENTACCTAMOUNT8,ACCOUNTTYPE9,REWARDAMOUNT9,CURRENTACCTAMOUNT9,ACCOUNTTYPE10,REWARDAMOUNT10,
CURRENTACCTAMOUNT10,BONUSVALIDITY1,BONUSVALIDITY2,BONUSVALIDITY3,BONUSVALIDITY4,BONUSVALIDITY5,BONUSVALIDITY6,BONUSVALIDITY7,BONUSVALIDITY8,
BONUSVALIDITY9,BONUSVALIDITY10,PREVIOUSSUSPENDSTOP "to_date(:PREVIOUSSUSPENDSTOP,'yy/mm/dd hh24:mi:ss')",
PREVIOUSDISABLESTOP "to_date(:PREVIOUSDISABLESTOP,'yy/mm/dd hh24:mi:ss')",AGENTNAME,ADDTIONALINFO,FILE_TIME,FILE_NAME,
ODATE "SYSDATE",ACCOUNT_2001 "CASE WHEN:ACCOUNTTYPE1='2001'THEN :REWARDAMOUNT1 WHEN :ACCOUNTTYPE2='2001' THEN :REWARDAMOUNT2
WHEN :ACCOUNTTYPE3='2001' THEN :REWARDAMOUNT3
WHEN :ACCOUNTTYPE4='2001' THEN :REWARDAMOUNT4
WHEN :ACCOUNTTYPE5='2001' THEN :REWARDAMOUNT5 END")
the above one succeed when i edit the case statement as follow
ACCOUNT_2001 "CASE WHEN:ACCOUNTTYPE1='2001'THEN :REWARDAMOUNT1 WHEN :ACCOUNTTYPE2='2001' THEN :REWARDAMOUNT2
WHEN :ACCOUNTTYPE3='2001' THEN :REWARDAMOUNT3
WHEN :ACCOUNTTYPE4='2001' THEN :REWARDAMOUNT4
WHEN :ACCOUNTTYPE5='2001' THEN :REWARDAMOUNT5
WHEN :ACCOUNTTYPE6='2001' THEN :REWARDAMOUNT6
WHEN :ACCOUNTTYPE7='2001' THEN :REWARDAMOUNT7
WHEN :ACCOUNTTYPE8='2001' THEN :REWARDAMOUNT8
WHEN :ACCOUNTTYPE9='2001' THEN :REWARDAMOUNT9
WHEN :ACCOUNTTYPE10='2001' THEN :REWARDAMOUNT10 END"
i got the Error sql loader 350 token longer than max allowable length of 258 chars .
note : i cant modify the table structure to shorten the column names .
please help me ....
thanlks
Edited by: user7998081 on Jun 23, 2011 3:24 AM

Ron Gittleman (guest) wrote:
: In migrating a Sybase 11 database to Oracle 8.0.5, there's a
: step toward the end of the data-moving endeavor in which a
script
: called genctl.scr is executed. This creates control files for
: 'sqlload'. For one-third or so of the source tables (.dat
files)
: sqlload complains about the control file:
: SQL*Loader-350: Syntax error at line 20.
: Token longer than max allowable length of 258 chars
: in_paid_period,15,6)

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

Field length during syndication & Automatic scheduling

Hi All,
I have 2 questions and need your valuable suggestions for same.
1) I have one field in MDM called Article code which contains value as 012345 thats 6 digit. My target system wants only 12345. Mean to say we need to do some settings in syndicator so that we can remove 0 and make it as 5 digit instead of 6 digit code.
2) Suppose I have schduled a automatic file generation in MDM that takes place in the evening 7PM daily. This will cover all the changes made in master data in whole day and will generate xml file covering all those changes. Let say on some day no changes were made. Then i need a file containing no values but it must generate a file atleast. How can we do this.
Please let me know if you ned any further info.
Thanks
Himanshu Nijhawan

Hi Himanshu,
See MAX ITEM LENGTH will take care of field value which will always have <= 5 characters.
Suppose if you set only this property then if you have length with 6 character then it will eliminate the last char of value.
e.g. 012345 to 01234 which you actually not looking for so alone this property will not solve your problem.
If you also set this property too along with MAX ITEM LENGTH, I mean Leading Character to strip = 0, then it will always eliminate field value with all the leading character's to 0 first and then count max item length should not > 5
e.g. 012345 to 12345
001234 to 1234 not 01234, if you want to contain 0 if it has length 5 then with leading char strip to 0 will not work.
It will work if your 5 char does not have leading zero. e.g 12345 to 12345 but not 01234 to 01234 but will result in 1234
So, If you are sure that when it comes to 5 char then it will not have leading 0 and for 6 char it will always have leading 0 then you can set these both properties in Syndicator and then can save in map which will give you desired result.
e.g. 12345 to 12345
e.g. 012345 to 12345
So, if you feel that you always want 5 char value irrespective of leading char 0 then you should go for this below approach.
e.g. you want when its 5 char value as 01234 and you want to maintain in the same manner during syndication 01234.
Here i would suggest go for assignment and write assignment expression as below in Data Manager.
IF(LEN(XXX) > 5 , RIGHT(XXX,5), XXX)
XXX is the Field name, this expression pass for value > 5 , e.g 6 then it will give the last 5 char of value
e.g. 012345 to 12345
It fails when the field value is not > 5 that means = 5 then it will put this same value e.g. 01234 to 01234. So in this manner you will always have length of 5 char and you don't need to cut off the 1st char and need to do this for 6 char only.
Regards,
Mandeep Saini

Restrict TextEdit field length to 240 chars

Hi,
In my Web-Dynpro application, I need to restrict the TextEdit field length to 240 chars maximum size.
The users shouldn't be allowed to enter more than 240 characters!
Best Regards,
Amol

Hi,
try creating a simple type under the dictionaries->logical dictionary->data types->simple type of type String and in the Definition tab set the max length to 240. create a value attribute under the context and set the type to the simple type created and bind it to the Input field.
This will restrict the length to 240.
Regards,
Poojith MV

Field length change in Web Dynpro Components iView

Hi,
We are using SAP MDM Web Dynpro Components - Configuration Manager (NW7.3) to develop the UI. One of the issue while disply field is, Though field maintained in MDM has only 2 charaters UI that displays a full-screen-width field.
I would like to display actual field length maintained in reposiroy for each field. Is it possible??
Cheers,
Rc

This is closed.
By mistake Raised Twice....I guess I need break

Changing field length of a standard field in standard table VBEP

Hi,
Please advice the possibility and the possible repercussions of changing field lengths in a standard table. Table in concern is VBEP.
Thanks & Rgds,
Pradeep

No you cannot change the field length
thanks
G. Lakshmipathi

Type conflict when calling a function module (field length)

Dear All,
            I am getting this following error while executing: Type conflict when calling a function module (field length)
This is piece of coding i have writern in my action button.
method SEARCH_MATERIAL .
data:
        node_mat_input TYPE REF TO if_wd_context_node,
        node_mat_output TYPE REF TO if_wd_context_node,
        material TYPE BAPIMATDET-MATERIAL,
        itab TYPE TABLE OF BAPIMATDOA.
node_mat_input = wd_context->get_child_node( 'NODE_MAT_INPUT' ).
node_mat_output = wd_context->get_child_node( 'NODE_MAT_OUTPUT' ).
node_mat_input->get_attribute( EXPORTING name = 'MATERIAL'
                                 IMPORTING value = material ).
CALL FUNCTION 'BAPI_MATERIAL_GET_DETAIL'
    EXPORTING
      material                    = material
    PLANT                       = plant
    VALUATIONAREA               =
    VALUATIONTYPE               =
    MATERIAL_EVG                =
   IMPORTING
     MATERIAL_GENERAL_DATA       = itab
    RETURN                      =
    MATERIALPLANTDATA           =
    MATERIALVALUATIONDATA       =
node_mat_output->bind_table( itab ).
endmethod.
Attributes are:
Node name = INPUT its structure is BAPIMATDET
INPUT attributes = MATERIAL of type BAPIMATDET-MATERIAL
Thanks,
Gopi.

Hi Amit,
           I have used service call to fetch records from that bapi..
The following is the code generated by service call:-
METHOD execute_bapi_material_get_deta .
declarations for context navigation
DATA:
    node_bapi_material_get_de   TYPE REF TO if_wd_context_node,
     node_exporting   TYPE REF TO if_wd_context_node,
     node_material_general_dat   TYPE REF TO if_wd_context_node,
     node_importing   TYPE REF TO if_wd_context_node,
      lri_element    TYPE REF TO if_wd_context_element.
declarations for fuba parameters
data:
    stru_c_material_general_dat    TYPE if_componentcontroller=>element_material_general_dat.
DATA:
    attr_material    TYPE bapimatdet-material,
    attr_plant    TYPE bapimatall-plant.
get all involved child nodes
node_bapi_material_get_de = wd_context->get_child_node( `BAPI_MATERIAL_GET_DE` ).
node_exporting = node_bapi_material_get_de->get_child_node( `EXPORTING` ).
node_material_general_dat = node_exporting->get_child_node( `MATERIAL_GENERAL_DAT` ).
node_importing = node_bapi_material_get_de->get_child_node( `IMPORTING` ).
get input from context
node_importing->get_attribute(    EXPORTING      name = `MATERIAL`
                                                     IMPORTING      value = attr_material ).
node_importing->get_attribute( EXPORTING       name = `PLANT`
                                                          IMPORTING       value = attr_plant ).
the invocation - errors are always fatal !!!
CALL FUNCTION 'BAPI_MATERIAL_GET_DETAIL'
    EXPORTING
      material =                        attr_material
      plant =                           attr_plant
"      valuationarea =                   wd_This->Valuationarea
"      valuationtype =                   wd_This->Valuationtype
"      material_Evg =                    wd_This->Material_Evg
    IMPORTING
      material_general_data =           stru_c_material_general_dat
"      return =                          wd_This->Return
"      materialplantdata =               wd_This->Materialplantdata
"      materialvaluationdata =           wd_This->Materialvaluationdat
node_material_general_dat->bind_structure( stru_c_material_general_dat[] ).
ENDMETHOD.
                             but the problem is I am getting the following error while compiling...
" stru_c_materialplantdata " is not an internal table - the " OCCOURS n" specification is missing.
Thanks,
Gopi.
Edited by: Yegalaivan on Nov 18, 2009 8:30 AM

How to create an infotype with one of its field length eq 1000.??

hi ,
i need to create a infotype where one of the field length is 1000 characters how do i achieve this. if i give more than 255 in the PS structure it will not allow. then how do i get a text field of 1000 chars in the screen ( which is an input field)

You can use those function calls even inside a PA Infotype.. they just invoke the text ediotr table control.. I gave you the reference of the PD infotype 1002 just for an idea. I don't think you will able to meet your 1000 char reqt without using the text editor.
~Suresh

CATT - vendor/customer master address field length over

Dear all,
when use CATT to record vendor/customer master,the address some fields length are over recorded field length(ex. ADDR1_DATA-NAME4,ADDR1_DATA-STR_SUPPL3...etc)
is there any config in CATT to solve this kind of problem?

When you are doing your LSMW batch input recording, on selection screen (where you specify the sales org, distribution channel, division, account group, etc) please put a flag on "Use central address management" checkbox (SAPMF02D 0100 > USE_ZAV).
In this case you should be able to see and fill the desired fields.

I am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

i am trying to generate purchase order and i create a BAPI also which is active.
But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

Hi,
Yeah i tried my Z_BAPI in R3 and then giving some ERROR.
This is my CODE-
FUNCTION ZBAPIPOTV2.
*"*"Local Interface:
*" IMPORTING
*"     VALUE(POHD) TYPE ZPOHD OPTIONAL
*"     VALUE(POITEM) TYPE ZPOITEM OPTIONAL
*" TABLES
*"      RETURN STRUCTURE BAPIRET1 OPTIONAL
data: ls_pohd type bapimepoheader,
         ls_pohdx TYPE bapimepoheaderx,
         lt_poit TYPE TABLE OF bapimepoitem,
         lt_poitx TYPE TABLE OF bapimepoitemx,
         ls_poit TYPE bapimepoitem,
         ls_poitx TYPE bapimepoitemx.
   MOVE-CORRESPONDING pohd to ls_pohd.
   MOVE-CORRESPONDING poitem to ls_poit.
   ls_pohdx-comp_code = 'x'.
   ls_pohdx-doc_type = 'x'.
   ls_pohdx-vendor = 'x'.
   ls_pohdx-purch_org = 'x'.
   ls_pohdx-pur_group = 'x'.
   ls_poit-po_item = '00010'.
   APPEND ls_poit to lt_poit.
   ls_poitx-po_item = '00010'.
   ls_poitx-po_itemx = 'x'.
   ls_poitx-material = 'x'.
   ls_poitx-plant = 'x'.
   ls_poitx-quantity = 'x'.
   APPEND ls_poitx to lt_poitx.
CALL FUNCTION 'BAPI_PO_CREATE1'
   EXPORTING
     POHEADER                     = ls_pohd
    POHEADERX                    = ls_pohdx
*   POADDRVENDOR                 =
*   TESTRUN                      =
*   MEMORY_UNCOMPLETE            =
*   MEMORY_COMPLETE              =
*   POEXPIMPHEADER               =
*   POEXPIMPHEADERX              =
*   VERSIONS                     =
*   NO_MESSAGING                 =
*   NO_MESSAGE_REQ               =
*   NO_AUTHORITY                 =
*   NO_PRICE_FROM_PO             =
*   PARK_COMPLETE                =
*   PARK_UNCOMPLETE              =
* IMPORTING
*   EXPPURCHASEORDER             =
*   EXPHEADER                    =
*   EXPPOEXPIMPHEADER            =
TABLES
    RETURN                       = return
    POITEM                       = lt_poit
    POITEMX                      = lt_poitx
*   POADDRDELIVERY               =
*   POSCHEDULE                   =
*   POSCHEDULEX                  =
*   POACCOUNT                    =
*   POACCOUNTPROFITSEGMENT       =
*   POACCOUNTX                   =
*   POCONDHEADER                 =
*   POCONDHEADERX                =
*   POCOND                       =
*   POCONDX                      =
*   POLIMITS                     =
*   POCONTRACTLIMITS             =
*   POSERVICES                   =
*   POSRVACCESSVALUES            =
*   POSERVICESTEXT               =
*   EXTENSIONIN                  =
*   EXTENSIONOUT                 =
*   POEXPIMPITEM                 =
*   POEXPIMPITEMX                =
*   POTEXTHEADER                 =
*   POTEXTITEM                   =
*   ALLVERSIONS                  =
*   POPARTNER                    =
*   POCOMPONENTS                 =
*   POCOMPONENTSX                =
*   POSHIPPING                   =
*   POSHIPPINGX                  =
*   POSHIPPINGEXP                =
*   SERIALNUMBER                 =
*   SERIALNUMBERX                =
*   INVPLANHEADER                =
*   INVPLANHEADERX               =
*   INVPLANITEM                  =
*   INVPLANITEMX                 =
ENDFUNCTION.
i am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

Table field length problem

Hi Team,
We r tring to create table with field length 250 and 'CHAR' type and one more field 'STRING 'for unlimited length.While creating table entries ,it is tsking only 130 length for all fields.it is not taking 250 characters for 250 length field.and it is not taking unlimited length for String field.Plz let me know.

Hello Mohan,
CHAR 250 is right. i am not facing any problem.
can you please explain in detail what you have done and what error you are getting.
Regards,
Sujeet
Edited by: Sujeet Mishra on Dec 2, 2009 4:42 AM

Idoc segment field length changes

Hi friends,,
I am new to idoc.
My requirement is in my segment
i am having 5 fields and also this segment is already realeased one.
i wnat to change the field length from 10 to 20 . how to do this ?
actually what i did is
1. i cancel the release for that segment.
2. in that field inside the dataelement i changed the field length from 10 to 20.
3. data elemnt get chaged from 10 to 20 but Export length for that field in Idoc segment still retain the 10 only
can you plz how to resolve this
deva

Hi,
The way you used is right. ( cancel release or create a new segment )
After you cancel release, try delete that field, and insert a new one.
If it isn't valid still, create a new segment instead.
Regards
Sam

Max field length

Similar Messages

Maybe you are looking for