Field length restriction

Hi Experts,
I am uploading some customer witht the help of BAPI BAPI_BUPA_FS_CREATE_FROM_DATA2.
While uploadig the customer , I am getting a Warning message " The use of last 5 character in field NAME1 is restricted (>35 to 40) "
Message type 'W' , ID - 'AM' , No -'228'.
This warning is coming because the length of field NAME1 is 40 character.We want to eliminate this warning
Can anyone give suggestion where this check is maintained.
Help will be appreciated.
Regards
Sourabh

Hi Sourabh,
Please refer OSS Note No. 777639
Please find points useful for you from the note.
Please reward points if helpful.
The wrong field is used for the mapping: The Outbound Idoc CREMDM and DEBMDM contain both the name fields from the Address management ( 40 characters long) and from the Master data itself (35 characters long)Due to historical reasons the fields are saved in these 2 places redundantly.
During XI XSLT mapping to the MDS the fields were taken from the Master data and not from the Address
management.
Solution
Change of the XSLT mapping: pick the name fields from the Address fields and not from the master data fields.
Regards,
Deepak

Similar Messages

Problem with the field length restrictions in the WSDL file

Hi all,
We have created a XSD file where we have defined fields and given some restrictions (like minLength, maxLength) for each field. See below one ex of one element "Id":
{code     <xs:simpleType name="Id">
          <xs:restriction base="xs:string">
               <xs:maxLength value="40"/>
          </xs:restriction>
     </xs:simpleType>
{code}
Here we have defined maxLength of this field as 40 chars. Our WSDL uses (refers/import) this XSD file and we ganerates java skeleton using RAD. But at runtime if we set more than 40 chars then also it is accepting. It is not throwing an exception. (In the generated java skeletion these restrictions are not reflected antwhere)
I have one question that, if such restrictions defined in the XSD file works or not? and is it a industry standard to define restriction in the XSD file?
If yes then what i need to do more to make it working?
If not then is there any way to do such validation of the fields that are input to the webservice? Or shall i have to just write my own java class to validate each field?
Regards,
Ravi

Or is it possible that we give length restrictions in the XSD (and import this XSD in WSDL) and generate java skeleton from WSDL then the restrictions defined in XSD are mapped into java classes?
For ex:
<xs:simpleType name="Id">
    <xs:restriction base="xs:string">
        <xs:maxLength value="40"/>
    </xs:restriction>
</xs:simpleType>so when in generated java skeleton we set value to "Id" element which is more than 40 charsthen it should throw a exception?
Is it possible by default or do we need to write custom validation classes to do validations on such fields?
Has anybody worked in such scenerios?
Or how to do field validations in webservice? Simple question.
Thanks In Advance.

Field length restrictions - any workaround possible?

Ladies and gents,
Here is a question for which I would love to get some feedback.
In an ongoing project, i'm migrating from a legacy system that has document numbers longer than 30 characters. I'm looking to see whether you have any suggestions as how to handle this in SAP.
My ideas are either around extending the document number, but that really does not appeal to my and i dont think it is feasible.
The other idea was if there was some way of extending the length of characteristics. Why anybody in SAP thought the longest meta-data you would need is 30 characters it beyond me though.
The last option, that could work is to add an include to table DRAW, and change the original screens to include the new field(s) added.
So anybody with similar experiences, either successes or failures, please come forward.
As always, points will be given etc etc.
Regards,
Espen Leknes
Edited by: Espen Leknes on Feb 28, 2008 2:49 PM

Hi Espen,
from SAP point of view I can only tell you that this restriction is due to the field definition of table DRAW. I never came accross a system where this field was increased to more than 30 characters.
As this is defined on database level I'm not sure if this really works as the document number is used to create the document key for several different other functionalities like object links.
Best regards,
Christoph

Field length restrictions

Hello,
I have a postal code field that is currently restricted to 7 characters including a space. The format is A0A0A0 and the program will automatically put the space in the middle when the user tabs over. I want the user to enter only 6 characters but If i put that restriction in, it hides one of the letters as it it counts the space as one of the 6 characters. If I change it to allow 7 characters, then the user can enter the whole 7 characters, but I only want them to enter 6 plus still allow for a space. Does this make sense?

Thank you for your response radzmar. Below is what I have in the exit event currently. So I tried what you suggested by going to paterns but it is still not working for me.
if (!(this.isNull)) {
var str = this.rawValue;
if (str.length != 6) {
    xfa.host.messageBox("Please enter a six character postal code in the format A9A9A9.");
else {
    var regExp = /^([R]\d[A-Z]\d[A-Z]\d)$/i;
    if (regExp.test(str)) {
      str = str.toUpperCase();
      this.rawValue = str.substring(0,3) + " " + str.substring(3,6);
    else {
      xfa.host.messageBox("Please enter the postal code in the format A9A9A9, where the postal code must begin with R.");

Field Length Restriction on DATA_COLUMN_MEMBERS while loading from ODI into Essbase.

Hi All,
I have a question on Data Loading process into Essbase using ODI using ‘RKM Hyperion Essbase’. While doing the custom Reverse Engineering for level 0 columns, we find a message popup with the below message:
Unable to save Test( ORA-12899: value too large for column "ODI_HYP_W"."SNP_UE_USED"."SHORT_VALUE"(actual: 368, maximum: 250)).
The error says the total length of all the DATA_COLUMN_MEMBERS (Level 0 columns) exceeds 250 characters, which is usually the case in a real world scenario. Is there a setting to bypass this or a config tag to ignore or so ? How has others go around this issue ?
Would appreciate your responses.
thanks,
Sandeep.

Hi John,
I have marked the ExportColHeader as Period as i need data for all the months. Even then the same error.
Also,
When i tried to load data from a file to table, the following error is encountered.
java.lang.NumberFormatException: For input string: "#Mi"
     at java.lang.NumberFormatException.forInputString(Unknown Source)
     at java.lang.Integer.parseInt(Unknown Source)
     at java.math.BigInteger.<init>(Unknown Source)
     at java.math.BigInteger.<init>(Unknown Source)
     at java.math.BigDecimal.<init>(Unknown Source)
     at com.sunopsis.sql.SnpsQuery.updateExecStatement(SnpsQuery.java)
     at com.sunopsis.sql.SnpsQuery.addBatch(SnpsQuery.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execCollOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)

How to restrict io field length...?

hi,
how can we restrict the io screen field length on the screen with out changing field type....
Regards,
Anil.

Hi ,
Do you want to restrict the display or the input length.
In case you want to restrict the display with the select-options or parameters then simply use the extension
... VISIBLE LENGTH vlen
Effect
This addition allows you to shorten the visible length of the corresponding screen field on the selection screen to vlen.
and in case you want to restrict it based on the number of characters then check out the following code.
PARAMETERS p_test TYPE c LENGTH 10.
DATA test TYPE i.
AT SELECTION-SCREEN ON p_test.
test = STRLEN( p_test ).
IF test > 4 .
MESSAGE 'Length greater than 4' TYPE 'E'.
ENDIF.
reward if usefull.
regards
taher

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

How can I restrict field lengths in a field?

I have a field that I want the user to only enter a 5 character response, not a 4 or 6 character response. Is '?????' field validation the only option?

There is a LEN function that you can use to validate the entry. It returns the length of the field. You could build a validation rule to ensure the field length is 5 and that anything other than 5 characters returns an error message. You would need to build more specific validation rules if your result needed to be numeric or non-numeric. The LEN function only rerturns the length.
Good Luck,
Thom

How to restrict field length upon Export - OFR

Hi,
I am working with the standard AP solution. We are experiencing an issue with the Invoice Number and PO Number exporting lengths that are longer than we have allowed in IPM. Therefore, we are having multiple documents fail with input agent in IPM because the number of characters are over the limit in the .txt file for those fields.
Thanks,
Natalie

Have your tried to adjust the application fields' lengths?
(see http://docs.oracle.com/cd/E23943_01/admin.1111/e12782/c04_applications.htm#CIHCJFEF )
Note that if you exceed the type's limits (like mentioned 'Possible string length is specified in the Length element with a maximum of 200 characters supported.') you might have to go with a workaround, but for fields like Invoice Number it can be a challenge (this field is probably heavily used in searching).

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

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

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

Field length restriction

Similar Messages

Maybe you are looking for