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

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

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)

Task Name - Field length Change

Can we change the task name length for team members when adding a new task?
Regards, Syed Faizan ur Rehman, CBPM®,PRINCE2®, MCTS

Hi Syed,
If you want to change the task field length, it is not possible. It is a native field which is predefined in the system.
But if you want to change the length of the task name itself (for example "design" by "system design"), then it it possible since what matters is the task UID and not the task name.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

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).

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

Inter-Organization transfer is not being possible..any workaround?

We were using Inter ORG transfer whiich is a seeded function in Oracle Inv module to transfer material from ORG A to ORG B
Navigation
(N)Inventory>Transactions>Inter-Organization Transfer
Now the problem is our items are not centralised.That is For example an item semi-conductors has a different item code opened for ORG A and a different for ORG B
Suppose ORG A code is SCND.000001
and ORG B code is SCND.000002
we have a two segment item flexfield
When ORG A tries to ship to ORG B, it doesnt appear in InterORG form since an item has to be enables in both the ORGS, source and detination, and since opur items are not centralised thats not possib
So what the user does is assigns the itemcode associated with his ORG to the Destination ORG too
Now when the Destination ORG receives the shipment , he has to receive in the new code assigned to him..Now has a result he has two codes which means reporting gets disturbed, history is difficult to find, manageability becomes hard..
Could you please suggesta workaround for this

Sandeep Gandhi, Independent Consultant wrote:
Any workaround is going to be hard and cumbersome. And that is because you are running counter to the industry practice of having the same item number across for the same item in your organizations? What is the second segment for? Is it a revision of sorts?We have 3 segment item categories
only the first segment is used , ACCS for accessory items, CHEM for chemical items, MECH for mechanical items
and in item, the first segment is used to represent the category the item belongs to
like ACCS or CHEM or MECH
than each new item is incremented by 1 in second segment, like ACCS.000001, next one would be ACCS.000002 and so on
We have more than 150,000 items and duplication cannot be eliminated, but it can be reduced..any advices for it??
>
One of the workaround will be to receive SCND.0002 and then do a RE-ID transaction (i.e. issue out 0002 and issue in 0001). But you will still need some kind of custom reports /screens if you need to tie the history together.I have already given this workaround but this is not acceptable and effective
Can we use internal requisitions?? i guess we cant without OM? right?

Getting correct field length when creating formats for delimited flat files

Using Data Services 3.2 to pull in tsv and Excel source files.
When creating a new format for each file, DS tries to intelligently set the field size for each column. However, it seems to sample only a portion of the file. The end result is that it often determines too short a length for a field.
Is there a way to force it to scan an entire file before it sets the field length? Or alternatively, how to get it to at least throw an error instead of silently truncating my data?

I am not aware of any way to force DS to scan the whole file, or to log a warning when it truncates. The field sizes DS sets by using a sample of the data is only really to give you a starting point, you need to try and determine the maximum possible lengths preferably from someone who understands the source of the data or through profiling. But the profiling method will obviously only be based on the data you have at the time of profiling, new data added to the source later could exceed the field lengths. The way I prefer to handle this is to set all the field lengths to longer than expected, eg. varchar(999) and then use a validation transform immediately after reading the file to check for any fields that exceed the maximum allowed for the target system and send these to an error file/table.

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

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

Date field Length in Java Webdynpro

Hi Experts,
I have a strange case.
I created a new filed in the infotype 0175: ZZDAT like the standard field AUSGD (type DATS length 8)
I modified the ESS view and added the new fields.
The view is working perfectly, the data is transfered between the databse and the webdynpro, the only problem is, that the user can't enter the date manually, because last point after the day can't be entered: e.g.: 2010.01.01 instead of 2010.01.01.
If the user uses the search help, and selects the date form the popup calendar, then the date format is correct: 2010.01.01.
(there is a point after the DAY ) I tried to change the field length manually but still, the last point after the day can't be entered.
Can you please help me to find out what is the problem?
Thanks
N.

Unfortunatelly this doesn'T help at all.
I reimported the data element, and restarted the server, but the result is the same. I can'T enter the date manually..
To be honest, i'm fed up with this stupid java webdynpro. I hope there is a special place in hell, for the people who invented this....
Anyway, I think the only solution here is to limit the field, capabilities. I'll try to set the Date picker as the only input way... I hope this is possible... it's easy in ABAP I just hope that java can do this the same "non-somplicated" way.
If you have any idea how to do this I'll be very greatfull for any kind of help.
Bye
N.

Field length restrictions - any workaround possible?

Similar Messages

Maybe you are looking for