Parameter entry & standard DB field length

Hi All,
I'm accepting parameters entry length as 11 char.May I compair this entry to mara-matnr which length is 18 char.
Pls. suggest...If Possible write code for me.
Thanks.
Singha

Use Converssion Exit to change the field from length 11 to matnr length
Code as follows :
PARAMETERS : p_matnr(11) TYPE c.
DATA : o_matnr LIKE mara-matnr.
CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'
EXPORTING
    input        = p_matnr
IMPORTING
    output       = o_matnr
EXCEPTIONS
    length_error = 1
    OTHERS       = 2.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
SELECT SINGLE * FROM mast
WHERE matnr = o_matnr.

Similar Messages

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

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

GL Account Field length

Hi,
My client wants to change the account field length in the doc entry. Standard account field is length is 16 or 17 digits. Its length has to be reduced to 10 digits.
How can i do this ? Can I do this in the configuration (or) customisation ? If it is customisation what are the tables I need to touch ?
Awaiting for the reply
Thanks,
Krishna

Use Transaction code OB13 to maintain maiximum length of GL account length as 10 apart from this you can also write validation so that if any gl account with more that 10 digits is entered system gives error.
Regads,
Manish Jain
Assign points if it serves your purpose.

Need some help in creating Search Help for standard screen/field

I need some help in adding a search-help to a standard screen-field.
Transaction Code - PP01,
Plan Version - Current Plan (PLVAR = '01'),
Object Type - Position ( OTYPE = 'S'),
Click on Infotype Name - Object ( Infotype 1000) and Create.
I need to add search help to fields Object Abbr (P1000-SHORT) / Object Name (P1000-STEXT).
I want to create one custom table with fields, Position Abb, Position Name, Job. Position Abb should be Primary Key. And when object type is Position (S), I should be able to press F4 for Object Abb/Object Name fields and should return Position Abbr and Position Name.
I specify again, I have to add a new search help to standard screen/field and not to enhance it.
This is HR specific transaction. If someone has done similar thing with some other transation, please let me know.
There is no existing search help for these fields. If sm1 ever tried or has an idea how to add new search help to a standard screen/field.
It's urgent.
Thanks in advace. Suitable answers will be rewarded

Hi Pradeep,
Please have a look into the below site which might be useful
Enhancing a Standard Search Help
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/daeda0d7-0701-0010-8caa-
edc983384237
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee93446011d189700000e8322d00/frameset.htm
A search help exit is a function module for making the input help process described by the search help more flexible than possible with the standard version.
This function module must have the same interface as function module F4IF_SHLP_EXIT_EXAMPLE. The search help exit may also have further optional parameters (in particular any EXPORTING parameters).
A search help exit is called at certain timepoints in the input help process.
Note: The source text and long documentation of the above-specified function module (including the long documentation about the parameters) contain information about using search help exits.
Function modules are provided in the function library for operations that are frequently executed in search help exits. The names of these function modules begin with the prefix F4UT_. These function modules can either be used directly as search help exits or used within other search help exits. You can find precise instructions for use in the long documentation for the corresponding function module.
During the input help process, a number of timepoints are defined that each define the beginning of an important operation of the input help process.
If the input help process is defined with a search help having a search help exit, this search help exit is called at each of these timepoints. If required, the search help exit can also influence the process and even determine that the process should be continued at a different timepoint.
timepoints
The following timepoints are defined:
1. SELONE
Call before selecting an elementary search help. The possible elementary search helps are already in SHLP_TAB. This timepoint can be used in a search help exit of a collective search help to restrict the selection possibilities for the elementary search helps.
Entries that are deleted from SHLP_TAB in this step are not offered in the elementary search help selection. If there is only one entry remaining in SHLP_TAB, the dialog box for selecting elementary search helps is skipped. You may not change the next timepoint.
The timepoint is not accessed again if another elementary search help is to be selected during the dialog.
2. PRESEL1
After selecting an elementary search help. Table INTERFACE has not yet been copied to table SELOPT at this timepoint in the definition of the search help (type SHLP_DESCR_T). This means that you can still influence the attachment of the search help to the screen here. (Table INTERFACE contains the information about how the search help parameters are related to the screen fields).
3. PRESEL
Before sending the dialog box for restricting values. This timepoint is suitable for predefining the value restriction or for completely suppressing or copying the dialog.
4. SELECT
Before selecting the values. If you do not want the default selection, you should copy this timepoint with a search help exit. DISP should be set as the next timepoint.
5. DISP
Before displaying the hit list. This timepoint is suitable for restricting the values to be displayed, e.g. depending on authorizations.
6. RETURN (usually as return value for the next timepoint)
The RETURN timepoint should be returned as the next step if a single hit was selected in a search help exit.
It can make sense to change the F4 flow at this timepoint if control of the process sequence of the Transaction should depend on the selected value (typical example: setting SET/GET parameters). However, you should note that the process will then depend on whether a value was entered manually or with an input help.
7. RETTOP
You only go to this timepoint if the input help is controlled by a collective search help. It directly follows the timepoint RETURN. The search help exit of the collective search help, however, is called at timepoint RETTOP.
8. EXIT (only for return as next timepoint)
The EXIT timepoint should be returned as the next step if the user had the opportunity to terminate the dialog within the search help exit.
9. CREATE
The CREATE timepoint is only accessed if the user selects the function "Create new values". This function is only available if field CUSTTAB of the control string CALLCONTROL was given a value not equal to SPACE earlier on.
The name of the (customizing) table to be maintained is normally entered there. The next step returned after CREATE should be SELECT so that the newly entered value can be selected and then displayed.
10. APP1, APP2, APP3
If further pushbuttons are introduced in the hit list with function module F4UT_LIST_EXIT, these timepoints are introduced. They are accessed when the user presses the corresponding pushbutton.
Note: If the F4 help is controlled by a collective search help, the search help exit of the collective search help is called at timepoints SELONE and RETTOP. (RETTOP only if the user selects a value.) At all other timepoints the search help exit of the selected elementary search help is called.
If the F4 help is controlled by an elementary search help, timepoint RETTOP is not executed. The search help exit of the elementary search help is called at timepoint SELONE (at the
F4IF_SHLP_EXIT_EXAMPLE
This module has been created as an example for the interface and design of Search help exits in Search help.
All the interface parameters defined here are mandatory for a function module to be used as a search help exit, because the calling program does not know which parameters are actually used internally.
A search help exit is called repeatedly in connection with several
events during the F4 process. The relevant step of the process is passed on in the CALLCONTROL step. If the module is intended to perform only a few modifications before the step, CALLCONTROL-STEP should remain unchanged.
However, if the step is performed completely by the module, the following step must be returned in CALLCONTROL-STEP.
The module must react with an immediate EXIT to all steps that it does not know or does not want to handle.
Hope this info will help you.
***Reward points if found useful
Regards,
Naresh

Pass parameter through standard page "import xml content and actions"

Dear Portal experts,
As you know, a standard portal page is configured to allow the import of XML file. It is located in the portal in the path system admin -> transport -> xml content and actions -> import
I configured a quick link u201Cimportu201D to the page so now the link http://myserver:port/irj/portal/import allows me to access directly to this screen.
What I would like to do now is to pass the parameter related to u201Cfile nameu201D through this screen meaning that I would like that http://myserver:port/irj/portal/ import/filename=C:\test.xml fills automatically the fields u201CXML fileu201D with C:\test.xml
Please do you know how to achieve this ?
Thank you very much and regards

hi,
@Maksim :
When user launch an URL like http://myserver:port/irj/portal/ import/*filename=C:\test.xml, he is requested to provide username and password; as this link is a shortcut for the upload xml page, there is a check of authorization and only portal admin that have authorization and permission on this page/iview will be able to upload xml file through the URL. Hope this clarify.
@Kumar :
thank you for your answer. What a pity to not be able to pass parameter through standard portal page/iview particularly knowing that we can pass paramater through many kinds of iviews (transactional iview, url iview, VC iview...). I explored some option on file com.sap.portal.ivs.init.par but this was unsuccessful. However, thanks to this [link bellow|http://wiki.sdn.sap.com/wiki/display/Snippets/ComponenttouploadXMLfilewithPCD+objects], I was able to upload through URL the XML file.
The problem is that I can upload only XML file that are stored in the server not in the local user computer. My requirement is to be able to upload local XML file stored on user's computer.
If someone could provide and idea/solution, I would be very grateful.
Cheers

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

Info on CCM 2.0 characteristics - Fields length, data types & Desc

Dear All,
Does anybody know how or where I can get information about CCM 2.0 standard characteristics data structure?
Or maybe the table name that holds this information?
I need the following info:
1. List of all Standard CCM 2.0 Characteristics
2. Characteristics Data types (i.e Char)
3. Characteristice Field lengths
I have looked into the SAP help for CCM 2.o and the on SAP Servicemarketplace under instguides&IBC....could not find every thing I wanted.
Regards,
Grace

Hi Grace,
you can look in tables
/CCM/C_CHAR
/CCM/C_CHAR_ALS
/CCM/C_CHAR_ASPT
/CCM/C_CHAR_TXT
/CCM/C_CHR_ALIAS
and
/CCM/C_DTYPE
/CCM/C_DTYPE_HDR
/CCM/C_DTYPE_T
/CCM/C_DTYPE_TXT
/CCM/C_DTYPE_VL
/CCM/C_DTYPE_VLT
in CCM to get the standard charcateristics and their default settings.
Chris

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 can i increase table field length?

Hi all!
Little URGENT!
I am stuck up at one point. I have dmbtr currency field which has 13 length. Now i would like to increse the length of it as per client's requirement.
Can anyone guide me to do that?
Thanks in advance.

Hi Prasad,
DMBTR is standard SAP field having fixed length.If you want to increase the length, you need togo to data element and domain and change there, but it asks accesskey becasue its standard field. Thats is not advisable.
regards
Chandra.
Note: Please reward if helpful.

ANSI X12 EDI 850 V4010 - REF Field length Increase

Hi,
The standarad EDI V4010 definiation contains Segment:REF, Field:127, MaxLength:30 (ISA.GS.ST.REF:127), partner sending a EDI data with more than 30 characters for this field. As per their EDI guide lines the MaxLength allows upto 50 chars for this field.
Have changed the field length from 30 to 50 chars in ANSI X12 850 V4010 message structure and re-generated EDI To XML mapping.When test the mapping in BIC tool, the EDI file is getting converted to EDI XML when the field value is more than 30 chars i.e upto 50 chars. Also Tested by giving more than 50 chars value for this field and it's failed to convert in BIC mapping tool saying 'The length of the field value is too big'.
As the change working in BIC tool, generated sda file and deployed on PI QA system. While test the change after .sda file deployment the change of Field Length is not reflecting and it's only allowing upto 30 chars only., and more than 30 chars data for this field EDI files are failing.
As the change working alone in BIC tool fine and not reflecting thefield length after sds file deployment. Any ideas about this issue and how to handle this requirement.
Thanks
Veera

Hi John,
If you see the documentation what you have given :
Parameters:
on: delimiters at the end do not appear
off: delimiters at the end appear
it clearly says the parameter is used for the delimiters, but not for truncating length of the fields in Seeburger.
I'm not sure if you've ever used the BIC Mapping tool and what I'm really looking for is someone with experience in this area to give a solution that works for this question:
By the way I have used the seeburger and this requirement we have done within XI because we have done all the rules within XI not in seeburger. But I will give a try with this requirement and will try to update you. Until unless I work with any of the issue I will not suggest. Even If I didnt I will try and then will suggest. Dont get me wrong.
Cheers,
John.

Signon user name field length

Folks - this might be a VERY simple question, but here goes.
We have been trying to confirm the userid length available in ECC6/etc. Knowing that this has been constrained in previous releases to a shorter field length, i.e.?12? chars...we want to be able to use a firstname.lastname login format via SAP GUI, which for many of our users exceeds that character count.
Can someone confirm that the permissable field length has been extended?
thanks in advance,
Al

Hi Al,
the username field in ABAP systems has still 12 character length. The username is stored in upper case.
However, if you are running a SAP NetWeaver Portal you have another option:
- You use an LDAP directory as the user store for the portal -> The username is not limited anymore.
- You add an additional LDAP attribute (e.g. SAPusername) to map the entries to the ABAP username (which still is limited to 12 character upper case)
- You use LDAP syncronization in the ABAP system to keep the users in the directory and in the ABAP in sync.
- Finally you use the Single Sign-On capabilities to call ABAP applications using the portal.
Kind regards
Frank
P.S. The ITS is able to use the alias-field in the ABAP user master record, too. See Online Help for details:
http://help.sap.com/saphelp_nw2004s/helpdata/en/52/67119e439b11d1896f0000e8322d00/frameset.htm

Need to add leading zeros to the field if field length is less than 6

Actually the field length is 16.
But for some manual entries it is comming as 4 chars.
so if field length is less than 6 then it should be replaced by leading zeros.
Moderator message: very basic, please (re)search yourself before asking, @all: please do not reply to basic questions, points removed.
locked by: Thomas Zloch on Sep 9, 2010 11:43 AM

Hi Ravi,
Do it in 2 steps.
1. check the length of your entry by strlen function and get the length.
2. If the output is less than 6 call the FM CONVERSION_EXIT_ALPHA_INPUT to get leading zero
Regards,
anirban

Create data daynamic from field length

HI All
There is a way to create data dynamically if i have in parameter field length
like char10 or KUNNR or char25.
Thanks,
Joy

field-symbol: <fs_dyn_wa>    TYPE ANY.
loop at lt_tab INTO ls_tab.
CREATE DATA kunnr TYPE (ls_tab-fieldname).
or if you have a fixed strucutre for the fields in the internal table, define the workarea and use the below code to push the values
           MOVE ls_tab-fieldname TO ls_fieldname.
          ASSIGN COMPONENT ls_fieldname OF STRUCTURE <fs_dyn_wa> TO <fs_val>.
endloop.
Edited by: ssm on Jul 26, 2011 7:51 PM

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.

Parameter entry & standard DB field length

Similar Messages

Maybe you are looking for