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.

Similar Messages

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

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

Check Screen Fields in ME21n

Hi,
I have to put a check on Document type and plant combination in ME21n.
After i enter values in Doc Type and Plant and i hit enter it should perform a check.
Check Logic:
I have made a Z table and if the Doc type n plant combination does not exist in that Z table then it should throw an error.
Now my query is,
which exit or badi should i use? i cant find anything related to it.
Thanx in advance
Regards,
Shraddha

Hi shyam...
thanks for your reply...
me_process_po is only for internal use of SAP
me_process_po_cust-
actually i want plant info from item and doc type from header....which is not possible through this badi as the method in which both these parameters are there is not called at the time of enter or save.
rest no other badi is useful.
Do u know about any exit?
Regards,
shraddha

Screen exit for ME21N

Hi friends,
I need steps to create screen field in ME21N using the BADI ME_PROCESS_PO_CUST. Can anybody suggest me how to implement this.
Thanks in advance
Regards
Srikanth S

Hello Srikanth,
To created a screen exit you can use either a BADI or a USER EXIT.
BADI : ME_GUI_PO_CUST
USER EXIT: MM06E005
GO to transaction SMOD
and type MM06E005 and press display.
once inside the user exit, click on components, there you have function Module exits, screen exits and includes.
On the screen exits, you have to decide where you want to add the screen field, whether its on header or item level.
THE go to SE80, type the screen name as the program name. IT will give you all the objects for the particular program.
Choose screens, and then the relevent screen. Go to layout and add the field you want. Save and activate.
You also need to add the field in the Cl_include so that you could pass data and retrive data.
Write the relevant code in Function Modulte Exits.
ITEM LEVEL:
EXIT_SAPMM06e_016
EXIT_SAPMM06e_017
EXIT_SAPMM06e_018
Now you have to add the relevant code in the PAI and PBO module.
Reward if useful.
Regards,
Sandeep Salaria

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

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.

Disabling I/O Screen Field in Cost center Screen Enhancement

Hi all,
     I am doing screen exit for Cost center master. While using KS03 transaction, I have to disable the newly added I/O screen fields. So, I added the following code in PBO module.
*** PBO
     MODULE modify_screen_input.
*** Include program of PBO
     MODULE modify_screen_input OUTPUT.
       IF sy-tcode EQ 'KS03'.
         LOOP AT SCREEN.
           IF screen-group1 eq 'CO'.
             screen-input = 0.
             MODIFY SCREEN.
           ENDIF.
         ENDLOOP.
       ENDIF.
     ENDMODULE.
But, screen fields with that group are not getting disabled. Is there any way to disable those screen fields?
Thank You.

Hello Shrilatha,
Please try with below code
IF sy-tcode EQ 'KS03'.
         LOOP AT SCREEN.
           IF screen-name = 'CI_CSKS-ZFIELD' ->changeit to field name
             screen-input = 0.
             MODIFY SCREEN.
           ENDIF.
         ENDLOOP.
       ENDIF.
     ENDMODULE.
Thanks

ME21N to Add New Screen Fields ME_GUI_PO_CUST.

Hi All,
        Req : To New TAB with Custom Fields for ME21N.
                 I Created a Custom Module Pool Prog with Reruired SUBSCREEn.
                 I am able to See the TAB but Unable to See the SUBSCREEN
                 and it is Displaying the RUNTIME ERROR .
One of the programs "CL_SCREEN_VIEW_MM=============CP" or "ZGDEO_100 " is currently being developed.
The name "SET_SUBSCREEN_AND_PROG" of the called routine may be incorrect, or the routine "SET_SUBSCREEN_AND_PROG" is not yet implemented in the program "ZGDEO_100 ".
*SOURCE CODE OF SUBSCRIBE
Method SUBSCRIBE.
CHECK im_application = 'PO'.
CHECK im_element = 'ITEM'.
CLEAR re_subscribers[].
ls_subscriber-name = subscreen1. ( Not Sure WHAT TO PROVIDE )
IF Leave it as subscreen1, it Says that it is Not Declared.
ls_subscriber-dynpro = '0100'. "SubSCREEN.
ls_subscriber-program = 'ZGDEMO_100'. " Custom Module Pool prog
ls_subscriber-struct_name = 'CI_EKKODB'.
ls_subscriber-label = text-001.
ls_subscriber-position = 5.
ls_subscriber-height = 7.
APPEND ls_subscriber TO re_subscribers.
*SOURCE CODE OF MAP_DYNPRO_FIELDS
MAP_DYNPRO_FIELDS Code:
FIELD-SYMBOLS: <mapping> LIKE LINE OF ch_mapping.
LOOP AT ch_mapping ASSIGNING <mapping>.
CASE <mapping>-fieldname.
WHEN 'ZZMARK1'. <mapping>-metafield = mmmfd_cust_01.
ENDCASE.
ENDLOOP.
CAN ANY ONE PLEASE HELP ME In THIS REGARDS.
Note : Points Will be Awarded

Hi Ganapati,
Please check this link:
http://wiki.sdn.sap.com/wiki/display/ABAP/DetailedexplanationaboutBADIandthewaystofindtheBADIwithanexample%28ME23n+transaction%29
Thanks,
Hung To

Addind field in ME21n

Hi friends ,
I m adding field in me21n using the enhancement MM06E005 in this i m adding field in screen 0111.
when i m going to check in me22n custom add is coming but when i m clicking custom tab a dump is coming.
error is 'THE ATTRIBUTE SCREEN TYPE WITH THE VALUES NORMAL SCREEN AND SUBSCREEN DETERMINES THE USE OF THE SCREEN .IF A NORMAL SCREEN IS USED AS SUBSCREEN OR VICE-VERSA AN ERROR OCCURS.
THE SCREEN SAPLXM06 011 HAS, IN THIS RESPECT AN INAPPROPRIATE SCREEN TYPE.
PLEASE GIVE THE STEPS..N HELP ME..
REGARDS
YOGESH

Hi Yogesh,
Check the screen type of 0111 in the attribute tab. It should be Subscreen.
Regards
Dillip Sahoo

Modify fields in ME21n

Hello All,
I have a requirement where in I need to modify fields of me21n based on a condition:
if the user enters a value in the field: MEPO1211-KONNR (Contract no./Number of principal purchase agreement) , then all the conditions (From KOMV table) fileds & all the Pricing terms should be disabled for change/input i.e. should be in display mode.
I tried to search for an exit for this but could not find an appropriate one to modify screen fields however, the alternae to this requirement is :
If the user enters a value in the field: MEPO1211-KONNR (Contract no./Number of principal purchase agreement) , then on entry of the conditions(TABLE KOMV) fields and pricing terms user should get an error message so that he cannot proceed.
Please suggest me a solution for any of the above two requirements.
Any help on this would be highly appreciated.
BR
Ankur

Hi,
Why dont you check with the enhancement project LO020 in CMOD.
Hope this would help you.
Or use the class CL_EXITHANDLER to find out the BADI used in ME21N for your requirement.
Regards,
Ranjith Nambiar

Adding the customer screen to enhance the header for Enjoy PO

Dear Expert's,
My requirement is to add a new tab on Header for Enjoy PO by enhancing ME21N/ME22N and ME23N.
I have already implemented the BADI's ME_GUI_PO_CUST and ME_PROCESS_PO_CUST.
Actions Taken:
I have created a custom Function group and subscreen '9000'.
I have created a 'Z' structure as per the screen layout on the Header Tab
I have appended the custom fields in EKKO custom include CI_EKKO.
Reactions:
1. I am able to successfully display the screen on additional tab at header level.
2. The Display & Change is working perfectly for screen '9000' on ME21N/ME22N and ME23N header.
Problem:
I am unable to read the 'Z' fields from EKKO to populate the TAB Screen '9000' and neither able to save the 'Z' fields from '9000' TAb screen for header data.
I am not using any EXIT for this and have to use only BADI for this solution. Please help me to implement this solution using BADI only.
Also i have tried implementaing the transport Data object -> Model + Model -> Dynpro + Dynpro -> Model + Model -> Data object methods, but these methods are not getting triggered.
Please let me know if i can use EVENT_PBO & EVENT_PAI if yes , than how to trigger these events and where..?

Hi ,
try to enhance PO header using SAP Note 407975
Summary
Symptom
You are using SAP customer enhancement MM06E005. There is no sample source
code for this enhancement.
More Terms
User exit, customer enhancement, MM06E005, example, sample
Cause and Prerequisites
You want to activate user exit MM06E005. Note that this is a consulting
note and not a correction of the user exit.
Solution
You can use the sample source code attached here to recognize the basic
functions of the exit. This example is, however, only one of many options
that are offered by the customer enhancement.
The sample source code includes the following functions:
o Supply of an additional field on header level
o Supply of an additional field on item level
o Derivation of a field on item level from the copied reference
document
Now, in order to be able to use the sample source code, you must create
field ZZFLAG on the header level of the document and field ZZFIELD on the
item level.
Double-click on Include table CI_EKKODB
Enter the following values:
- Name Component type DType Length DecPlace Short text
- ZZFLAG CHAR1 CHAR 1 0 1-digit indicator
Save and activate the include table.
Double-click on Include table CI_EKPODB
Enter the following values:
- Name Component type DType Length DecPlace Short Text
- ZZFIELD CHAR1 CHAR 1 0 1-digit indicator
Save and activate the include table.
In order to activate the sample source code, you additionally have to carry
out the following changes on screens 0101 and 0111.
1. Screen 0101: Create the following fields:
2010.02.05 Page 2 of 3
SAP Note 407975 - MM06E005: Collective note: Examples for
implementation
"Checkbox" Name: EKKO_CI-ZZFLAG
2. Screen 0111: Create the following fields:
"Input/output field" Name: EKPO_CI-ZZFIELD
"Pushbutton" Name: BUTTON
FctCode: ZZDETERMINE
The following assignments apply to the sample source code:
EXIT_SAPMM06E_006 --> LXM06F36
EXIT_SAPMM06E_007 --> LXM06F38
EXIT_SAPMM06E_008 --> LXM06F37
EXIT_SAPMM06E_009 --> LXM06F39
EXIT_SAPMM06E_016 --> LXM06F41
EXIT_SAPMM06E_017 --> LXM06F42
EXIT_SAPMM06E_018 --> LXM06F40
Copy the source code from the attachment and insert it into the
corresponding function modules. Save and activate the function modules.
Create the following variables in the corresponding TOP include in order
not to get any syntax errors:
INCLUDE ZXM06TOP
data: gl_aktyp type c,
gl_no_screen type c,
gl_rekko like ekko,
gl_ekko_ci like ekko_ci,
gl_ekpo_ci like ekpo_ci,
gl_ekpo like ekpo,
gl_ucomm like sy-ucomm.
types: begin of ekpo_tab,
ebeln like ekpo-ebeln,
ebelp like ekpo-ebelp,
ekpo like ekpo,
end of ekpo_tab.
data: gt_ref_ekpo_tab type table of ekpo_tab.
Save and activate the TOP include.
On header level, you can now store a character, X or space, via field
ZZFLAG on the database with the document and read it also again.
On item level, you can fill field ZZFIELD with a one-digit value and save
it with the document. If you copy this document, the system displays an
additional function button on tab page "Customer data". If you press this
button, the value of the reference document is copied to field ZZFIELD.
If you want to store the source code as sample source code in your system,
start Transaction SMOD. Enter MM06E005 as an enhancement. Select
"Components". Press "Change". Position the cursor on the corresponding
module and choose "Sample code". Create the corresponding include and copy
2010.02.05 Page 3 of 3
SAP Note 407975 - MM06E005: Collective note: Examples for
implementation
the source code from the note. Save the include. Note that, of course,
syntax errors may occur when you check components. This is because the
includes of the sample code are not integrated into a program but rather
are completely independent and, therefore, do not have any relationship to
each other either. For this reason, only save the include and do not
activate or check it. The sample code has to be copied into the
corresponding function modules in order to become active.
If you use the user exit in the new purchase order, it is not guaranteed
that the customer screen is always processed. To make sure that possible
required fields are checked, include a corresponding message into the
EXIT_SAPMM06E_012. This screen is always processed.

How to add additional tab or fields in ME21n

Hi all.
I included some fields in EKKO table.
I want to add these fields in ME21n, ME22n, ME23n Header screens.
How to add?
I can't find screen exit and user exit.
Plz, let me know how to do in detail.
Regards,
nam
Message was edited by:
Kil Nam Kim

Hi
It is very much possible. Please discuss with your development team with the exact requirements. They should be able to do it with screen exits.
Reward if this helps.

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

Grey out of component screen fields in sub contracting PO.

Hi!!!!!!!! Sapers
When i am creating subcontracting Purchase order , In this i want restrict the users to add or modify the components screen fields. what i need exactly is i want to gray out the fields of these component screen .
Is it Possiable? Or required any user exit?
Please suggest
Thanks
Prashant

Hi Prashant
Please fallow the below steps
1. Goto me21n screen and note down program? and screen? using F1
2. Use tcode SHDO, Enter transaction code as "mE21N" goto screen variant tab and enter some name in screen variant field
3. also enter program name and screen name then click create icon
4. It will take you to the mm01 screen Enter reqd defauls value press Enter
5. then it will take you to another window there you can hide required field & save
6. come to the SHDO screen and select Transaction tab & enter some name
7. enter you already created screen variant name & save
8. table Standard variant tab and it might alredy taken Transaction variant which was created already
9. now you can check ME21N
Raju

Screen Field Enhancement (ME21N)

Similar Messages

Maybe you are looking for