Standard screen field validation : ME21n/ ME22n

Hi experts,
I have a requirement in which we are supposed to do field validations while creating or changing POs/Purchase requistions.
Suppose if at item level in Account assignment category is 'F' and the order entered by user is of type 'Z560' then in that case user will be allowed to enter only specific G/L account for eg : 712546 or 715486.
Please guide how can that be accompalished. I couldn't find any proper exit for this.
Thanks
Vishal

Hi Vishal,
there is a very helpful BAdI for this: ME_PROCESS_PO_CUST.
Re: user exit/ badi for me21n
Roy
Edited by: RobbdB on Jun 30, 2010 9:09 AM

Similar Messages

Search Help - Standard Screen Field: ME21n / ME22n

Helow, experts.
I have to create a search help in the standard screen field "Our Reference" (UNSEZ) in the tab Communication to ME21n / ME22n, anyone could say me how can I code it?
To populate this search help, I have to use 3 different tables.
Thanks

hi shatish
code here in screen flow logic it will fire on F4 pressing.
PROCESS ON VALUE-REQUEST
module value_help.
in program
module value_help.
populate the itab.
CALL FUNCTION 'POPUP_WITH_TABLE'
                EXPORTING
                  ENDPOS_COL         = <colvaluea>
                  ENDPOS_ROW         = <colvaluea>
                  STARTPOS_COL       = <colvaluea>
                  STARTPOS_ROW       = <colvaluea>
                  TITLETEXT          = 'VALUE HELP'
              IMPORTING
                CHOICE             =
                TABLES
                  VALUETAB           = itab
              EXCEPTIONS
                BREAK_OFF          = 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.
endmodole.
regards
shiba dutta

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

To get f4 help for salesperson field ,transaction me21n & me22n

Hi Super-Techies,
I am a new-bie in the world of enhancement.
The reuirement here is I need to create a custom table with 1 field (prep_name). (This is done)
Now the reuirement is that whenever user goes to transaction ME21N/ME22N, he wants me to add a f4 help for salesperson field (navigation : ME21N/ME22N -> CLICK ON COMMUNICATION TAB -> SALESPERSON). The f4 help should display the field from my custom table.
As far as my knowledge is cond=cerned, I can use the function module 'F4IF_INT_TABLE_VALUE_REQUEST' to achieve this requirement.
But the issue I am facing is where to write this logic and how to proceed. Can anyone help me in this case?
Any help in this regard would be appreciated.
Thanks & Regards,
Vinit
Edited by: vinit005 on Nov 1, 2010 12:43 PM

Hi Vinit,
I also had that requirement. There is no customer exit/BADI by which we can achieve that(as far as my knowledge), we have to use access key to achieve that. So we have gone for customer exit "MM06E005" to add Customer data tab in header and added our own fields, like Sales Person, Buyer Details etc.
Thanks & Regards,
Faheem.

Enhancements:Search help addition to standard screen-field

Hi Guys,
I am trying to add search help to the standard screen field inco2 in transaction va02. for this I am trying to add inplicit enhancement point in include MV45AFZZ.
I right click over the yellow line and create enhancement implementation in local object. the moment I choose my enhancemetn implementation and press enter, it gives me dump, Please nebody tell me where am I going worng, or Is my approach correct.....Please suggest.......
thanks in advance

Hi Anil,
Can you please tell me how to approach for adding search help to standard screen field INCO2 in transaction VA02.

Selection-screen fields validation for dialog

Hello ABAP Gurus
Requirements: this is a report wherein , depending upon the correct select-options , user will pick some field values from table and some will be entered by the user in the next se51 custom screen for creation of a record in a ztable .
the problem is :without validating select-options values , it calls the se51 screen 100.
How to keep the cursor at the selection-screen field until & unless user enters the correct i/p s .if i/p are correct then only it should call screen 100 otherwise remain in the selection screen only .
*& Report ZSD_REP_QUOT_BANK_CREATE *
REPORT ZSD_REP_QUOT_BANK_CREATE NO STANDARD PAGE HEADING LINE-SIZE 255.
TABLES: VBAK,VBAP,VBRK,ZSD_TABL_QOTBANK,MARA,KONV.
DATA: OK_CODE LIKE SY-UCOMM,
SAVE_OK_CODE LIKE SY-UCOMM,
WA_ITAB LIKE ZSD_TABL_QOTBANK,
ANSWER TYPE C,
COPIED ,
STS TYPE N,
EMGRP LIKE MARA-EXTWG,
QTY LIKE ZSD_TABL_QOTBANK-QTY,
UPRICE LIKE ZSD_TABL_QOTBANK-UPRICE,
TOT LIKE ZSD_TABL_QOTBANK-TOT,
INO LIKE VBAP-POSNR.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-000.
SELECT-OPTIONS: S_QTNO FOR ZSD_TABL_QOTBANK-QTNO
NO INTERVALS NO-EXTENSION OBLIGATORY,
S_ITNO FOR ZSD_TABL_QOTBANK-ITNO
NO INTERVALS NO-EXTENSION OBLIGATORY.
S_MATNO FOR ZSD_TABL_QOTBANK-MATNO
NO INTERVALS NO-EXTENSION. "
SELECTION-SCREEN END OF BLOCK b1.
AT SELECTION-SCREEN.
SELECT SINGLE VBTYP
INTO VBAK-VBTYP
FROM VBAK
WHERE VBELN IN S_QTNO.
IF SY-SUBRC EQ 0 AND VBAK-VBTYP NE 'B'.
MESSAGE I005(ZQOTBANK).
SET CURSOR FIELD S_QTNO-LOW.
SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
ENDIF.
CLEAR WA_ITAB.
SELECT SINGLE QTNO ITNO
INTO WA_ITAB
FROM ZSD_TABL_QOTBANK
WHERE QTNO IN S_QTNO
AND ITNO IN S_ITNO.
IF SY-SUBRC EQ 0.
MESSAGE I001(ZQOTBANK).
SET CURSOR FIELD S_QTNO-LOW.
SET CURSOR FIELD S_ITNO-LOW.
SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
ENDIF.
*START-OF-SELECTION.
END-OF-SELECTION.
CALL SCREEN 0100.
*& Module STATUS_0100 OUTPUT
text
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS '0100'.
SET TITLEBAR '0100'.
ZSD_TABL_QOTBANK-QTNO = S_QTNO-LOW.
SELECT SINGLE BUKRS_VF VKORG VTWEG SPART KUNNR ERDAT BNDDT
KNUMV
INTO (ZSD_TABL_QOTBANK-CCODE,
ZSD_TABL_QOTBANK-SORG,
ZSD_TABL_QOTBANK-DISTCHAN,
ZSD_TABL_QOTBANK-DIV,
ZSD_TABL_QOTBANK-CUSTNO,
ZSD_TABL_QOTBANK-QTDAT,
ZSD_TABL_QOTBANK-QTVALDAT,
VBAK-KNUMV)
FROM VBAK
WHERE VBELN IN S_QTNO
AND VBTYP = 'B'.
IF SY-SUBRC EQ 0.
SELECT SINGLE KWMENG POSNR MATNR
INTO (QTY , INO , ZSD_TABL_QOTBANK-MATNO)
FROM VBAP
WHERE VBELN IN S_QTNO.
SELECT SINGLE EXTWG
INTO EMGRP
FROM MARA
WHERE MATNR EQ ZSD_TABL_QOTBANK-MATNO.
ZSD_TABL_QOTBANK-ITNO = INO.
ZSD_TABL_QOTBANK-EMATGRP = EMGRP.
ZSD_TABL_QOTBANK-QTY = QTY.
SELECT SINGLE KBETR
INTO UPRICE
FROM KONV
WHERE KNUMV = VBAK-KNUMV
AND KPOSN = INO
AND KSCHL = 'PR00'.
ENDIF.
ZSD_TABL_QOTBANK-UPRICE = UPRICE.
TOT = QTY * UPRICE .
ZSD_TABL_QOTBANK-TOT = TOT .
CLEAR: QTY, UPRICE, TOT.
QTY = ZSD_TABL_QOTBANK-CGL_QTY.
UPRICE = ZSD_TABL_QOTBANK-CGL_UPRICE .
TOT = QTY * UPRICE .
ZSD_TABL_QOTBANK-CGL_TOT = TOT .
CLEAR: QTY, UPRICE, TOT.
QTY = ZSD_TABL_QOTBANK-BHEL_QTY.
UPRICE = ZSD_TABL_QOTBANK-BHEL_UPRICE .
TOT = QTY * UPRICE .
ZSD_TABL_QOTBANK-BHEL_TOT = TOT .
CLEAR: QTY, UPRICE, TOT.
QTY = ZSD_TABL_QOTBANK-BHEL_QTY.
UPRICE = ZSD_TABL_QOTBANK-BHEL_UPRICE .
TOT = QTY * UPRICE .
ZSD_TABL_QOTBANK-BHEL_TOT = TOT .
CLEAR: QTY, UPRICE, TOT.
QTY = ZSD_TABL_QOTBANK-ALSTOM_QTY.
UPRICE = ZSD_TABL_QOTBANK-ALSTOM_UPRICE .
TOT = QTY * UPRICE .
ZSD_TABL_QOTBANK-ALSTOM_TOT = TOT .
CLEAR: QTY, UPRICE, TOT.
QTY = ZSD_TABL_QOTBANK-SIEMENS_QTY.
UPRICE = ZSD_TABL_QOTBANK-SIEMENS_UPRICE .
TOT = QTY * UPRICE .
ZSD_TABL_QOTBANK-SIEMENS_TOT = TOT .
CLEAR: QTY, UPRICE, TOT.
QTY = ZSD_TABL_QOTBANK-TELK_QTY.
UPRICE = ZSD_TABL_QOTBANK-TELK_UPRICE .
TOT = QTY * UPRICE .
ZSD_TABL_QOTBANK-TELK_TOT = TOT .
CLEAR: QTY, UPRICE, TOT.
QTY = ZSD_TABL_QOTBANK-OTH_QTY.
UPRICE = ZSD_TABL_QOTBANK-OTH_UPRICE .
TOT = QTY * UPRICE .
ZSD_TABL_QOTBANK-OTH_TOT = TOT .
CLEAR: QTY, UPRICE, TOT.
ENDMODULE. " STATUS_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT
text
MODULE USER_COMMAND_0100 INPUT.
CASE OK_CODE.
WHEN 'SAVE'.
INSERT ZSD_TABL_QOTBANK.
IF SY-SUBRC EQ 0.
MESSAGE I000(ZQOTBANK).
COMMIT WORK.
CALL SELECTION-SCREEN 1000.
ELSE.
MESSAGE E001(ZQOTBANK).
CALL SELECTION-SCREEN 1000.
ENDIF.
ENDCASE.
ENDMODULE. " USER_COMMAND_0100 INPUT
*& Module EXIT_COMMAND INPUT
text
MODULE EXIT_COMAND INPUT.
SAVE_OK_CODE = OK_CODE.
CLEAR OK_CODE.
CASE SAVE_OK_CODE.
WHEN 'CANCEL'.
CALL FUNCTION 'POPUP_TO_CONFIRM'
EXPORTING
TITLEBAR = 'Quotation Bank Entry'
TEXT_QUESTION = 'Do you want to Cancel ?'
TEXT_BUTTON_1 = 'Yes'
TEXT_BUTTON_2 = 'No'
DEFAULT_BUTTON = '2'
IMPORTING
ANSWER = ANSWER.
IF ANSWER = '1'.
LEAVE PROGRAM.
ELSE.
CALL SELECTION-SCREEN 1000.
ENDIF.
WHEN 'EXIT'.
CALL FUNCTION 'POPUP_TO_CONFIRM'
EXPORTING
TITLEBAR = 'Quotation Bank Entry'
TEXT_QUESTION = 'Do you want to Exit ?'
TEXT_BUTTON_1 = 'Yes'
TEXT_BUTTON_2 = 'No'
DEFAULT_BUTTON = '2'
IMPORTING
ANSWER = ANSWER.
IF ANSWER = '1'.
LEAVE PROGRAM.
ELSE.
CALL SELECTION-SCREEN 1000.
ENDIF.
ENDCASE.
ENDMODULE. " EXIT_COMMAND INPUT
Thnx in Advance

Put the statement
CALL SCREEN 100
in the event <b>AT SELECTION-SCREEN</b> and NOT in <b>END-OF-SELECTION</b>.
Regards,
Subramanian V.

BADI for Disabling NetPrice field in ME21N & ME22N based of Material Type.

Hi.
I had a requirement to disable "net price" field while creating or changing a PO (ME21N & ME22N) based on the type of material entered.
Please asssit me in finding the BADI or exit name which can meet my requirement. Thanks.

Hi Ranga nadh,
The BAdi what you have mentioned is correct.
ME_PROCESS_PO_CUST - In this BAdi, we are having a method PROCESS_ITEM. These method is used to process all the Item data. As the field Netprice is at the level. You can use this method.
Here inside this method we are having a parameter IM_ITEM
So, You create a implementation and inside this method you can code here to appear the field in disable mode.
Cheers,
Swamy Kunche

Screen field validation

Hi,
My requirement is to validate a particular screen field.......while user enters the value on that field....(i.e) the message should not come after the user action....it should get displayed while entering the value itself.....is it possible...if so...how.?
Thanks in advance,
Varsha..

Hi Varsha,
If you use a field of type NUMC the system doen't allow you to enter CHARS
i dont to that deapth, even for type i and type SY-DATUM Fields system doesnt allow to enter chars aswell.
Check this out.
CL_GUI_DATAMANAGER
in the above class there is a method ON_INPUT
CL_PARSER_PII
in the above classes there is a method PARSE_INPUT which might work as on focus event
but we need to know the functionality in deapth.
which might be useful to you
Regards
Ramchander Rao.K
Edited by: Ramchander Krishnamraju on Dec 26, 2008 8:09 AM
Edited by: Ramchander Krishnamraju on Dec 26, 2008 8:11 AM

Add new field in me21n/me22n/me23n

Hi everyone,
Is it possible to add a field in the Additional Data tab in the PO header and append the field in the PO table(EKKO) also or should I add a new tab and place my new field in the new tab? Is it possible also to add the field using a user exit instead of BADI?

Hi ,
U can add the additional screen field in the additional data tab or u can have a seperate tab for it. If u want to go for the additional data tab the badi ME_GUI_PO_CUST will be usefull here u can add the additional screen fields directlly . Please check this...
U can add the field in the statndard table like ekko by using the append structures.
To add a screen field u need a screen field exit or a badi that allow u to add a acreen field . In PO the SAP has provided the above mentioned BADI for doing this..
Hope this will solve ur query to an extent ... Reward points if found useful .

Customer exit for validation of PO fields in ME21N / ME22N - After pressing enter & save button

Hi,
I am looking to validate the standard fields(EKKO-IHREZ, Your reference under communication) of Purchase order . So for this I used the customer exit EXIT_SAPMM06E_012 under the enhancement MM06E005 . I am able to validate but it is triggering only when SAVE selected.
1. Can we implement the same when we press enter button ?
2. How to log error message using macro for the field EKKO-IHREZ with error message ? As of now I am using message 'asdfasdfasdf' type 'E' which is appearing now in the log messages.
Regards,
Praveen CHITTURI .

Better use methods like PROCESS_HEADER or PROCESS_ITEM of BAdI ME_PROCESS_PO_CUST.
There are many threads and documents on this BAdI at scn.
In the chosen methods use Macros mmpur_metafield to attach error to a field (defined in type-pool MMMFD, mmmfd_ref_1 ?) and mmpur_message_forced to raise error message and add it to log.
include mm_messages_mac.
im_item->invalidate( ).
mmpur_metafield mmmfd_matnr.
mmpur_message_forced 'E' 'ZFSM' '613' ls_item-matnr ls_item-werks ls_header-bsart ls_material_plant-mmsta.
Regards,
Raymond

Want to update standard field in ME21N/ ME22N

Hi All,
I have a requirement to block all the line item of the standard PO if any of the line item does not satisfy specific condition (as per the requirement). But I am not able to do so.
I have tried to use the BADI ME_PROCESS_PO_CUST~PROCESS_ITEM. But, here it is not possible to block all the line item(s) if any of the specific line item fails the condition check. So, can any body help me to find the way out.
Thanks--
Debojit.

Hi,
Thanks for ur reply. But, I have a requirement to block all the line item(s) of the PO if any of the line item(s) does not satisfy the specific condition checking.
Also, I have to put the error message in the message log, but how can I block (set LOEKZ = 'S') every line items of a PO in this case?
Thanks -
Debojit.

Grayout of component screen fields in ME21N transaction

Hi experts,
I have a problem while creating subcontracting PO i want to gray out the fields of component screen...in ME21N transaction...is it possible through the screen varient or else should i go for exit ??...could u please help me in finding the right procedure...........
Best Regards,
shanker

Go to the screen where u want to make the changes.
Click on System -> Status. Double click on the screen Number (like 1121).
Then on the PBO module screen click on 'Layout'. You will go to graphical screen painter.
Then DOUBLE CLICK on the column/field you want to gray out and on Attribute part, Program Input -> Not possible .(save + activate)
You will need an Access Key to change the standard SAP Screen...
Fawaz

How to make the logs captured for Z fields in ME21N/ ME22N

Hi
I have devloped new tab(Screen) and added Z field in the PO header (ME21N) as per my requirement. But whenever I do changes to the perticular Z field, logs are not captured (ME21N->ENVIRONMENT-->HEADERLOG). How to make the logs captured for Z fields like standard fields. Is there any way?
Regards
Raj.

HI Ranjitha
For the data element of Z fields go to further caracteristics of tab and make change document checkbox ticked.

Screen Field Enhancement (ME21N)

Hi
I have done some screen enhancement in Tcode ME21N. i made 2 fields in Customer data Tab. Data is also savin.
But i am not able to disable the fields at the time of display mode. Is there anyone who has done some enhancement in PO or faced this same problem ?
please do tell me the solution for this.
Regards
Abhishek

T160-TRTYP = 'H'   FOR ME21N
T160-TRTYP = 'V'   FOR ME22N
T160-TRTYP = 'A'   FOR ME23N
IN THE exit code
make use of this screen conditions to differentiate for Create, Change and display mode before teh logic.
as
   IF T160-TRTYP = 'H'.
   PROCESS LOGIC ..
   ENDIF.
Table is T160.
regards,
vijay.

Enable fields in ME21N/ME22N(WBS Element & Network)

Hi, need your help!
How to enable the fields WBS Element and Network in transaction codes: ME21N and ME22N?
Thanks in Advance

Hi,
You can implement BADI ME_PROCESS_PO_CUST and implement the method FIELDSELECTION_ITEM. For srep by step process check below link. Thanking you.
how to keep wbs element field in display mode in me22n?

Standard screen field validation : ME21n/ ME22n

Similar Messages

Maybe you are looking for