Standard transaction ME21N

Hi Experts,
Can we add new field for Time in standard transaction ME21N.If yes how is it possible tell me..
Its very urgent..
Thanks in advance
Srihari.

Hi Bhupal,
Thanks for giving the Userexit.I am new to user exits and Dialog programming.Please can any one explain me the step by step procedure for How to do the screen exit for standard transaction ME21N.
Thanks in Advance.
Regards
Srihari.

Similar Messages

Using BADI to change the field value in standard transaction ME21N

Hello People,
In transaction ME21N to create PO, i have a field where i want to allocate the batch ( CHARG ) NONRETG to all the PO's that are created. I have a BADI for that, however i do i implement the BADI so that the Batch 'NONRETG' is automatically allocated to all the PO's that are created. Please advise whether a USER EXIT would be better or a BADI would do the work. Right answer would be rewarded.
regards,
Sandeep Salaria

Hi,
YOU can very well implement.Use this BADi->ME_GUI_PO_CUST
Incase you are going to implemet userexit U can use the Exit: MM06E005.
Regards
Kiran Sure

CHANGE in standard transaction ME21n/ME22N/ME23N

Hello Forum,
My client's business require me to add two new columns in PO schedule line items.
These two columns are to be taken from EKET table.
I have got the access key to modify the standard transaction.
I have located that it has to be added in program:SAPLMEGUI at screen#1320.
Any inputs how to proceed further.
thanks

Sudheer, your point well taken
But I have to add two columns and not two fields, in PO Sch Line Item.
I have mentioned program name SAPLMEGUI at screen#1320. I guess its a table control and I have to add modify that table control to add new columns into it.
Kindly reply back with suggestions for the same.
In this case no screen exits can help me.

How to come out of standard transaction after giving error message

Hi Experts,
I have one requirement like i need to validate a field in standard transaction ME21N. If user enters wrong value then i have to give error message and leave the transaction ME21N immediately. If i do the code with error message then i struck in the same screen of ME21N(but i need to come out of ME21N).Can anybody help me for this particular scenario.
Regards,
Bujji

Ahhh, I see, this is a different story, now.
How about issuing an Information message, and saying LEAVE TO TRANSACTION 'ME21N'.
Message I001(00) with 'THere is some problem, transaction ending'.
leave to transaction 'ME21N'. " Or you may be able to use SY-TCODE here.
Regards,
Rich Heilman

Problem with transaction ME21N

Hi Experts,
          Please help me out my requirement,i m not getting what i will do.
           My requirement is Modify the Standard transaction ME21N. Means i need to delete some tabs in that transaction, which my client is not use and also add some fields to that transaction.
          I am not getting how to do this requirement.Please suggest me how to do this.
               Thanks in Advance.
Regards
Srihari.

Hi,
You can find the exits available with the transaction and code the enhancements there. Instead of deletin the fields Hide those fields.
Regards,
Renjith Michael.

Create a user-defined selection variant in transaction ME21N

Hi,
In transaction ME21N with the 'Document Overview' feature turned on we can view a list of standard selection variants. I would like to add a user-defined selection variant to that list. There is an OSS Note 377180 present which describes how to do that but(as per transaction SNOTE) that note cannot be implemented in our system. Is there any other way to get that done?
Any help would certainly be appreciated.
Thanks,
Alam.

I would suggest that you replay the transaction with breaks, so that you can see exactly what is happening (in the start options, set the SAPGUI replay options to stop at each ProcessedScreen)
It may be that the Selection Variant button is not present during replay. In this case, you would need to make the step where this button is pressed as optional.
ME21N is a difficult transaction to automate because it always remembers what you were last doing in it and restarts the transaction from that point. You can delete the user settings (so you always start the transaction as though for the first time) using the following code in your script:
ABAP.
* Delete all User-Settings in MM
DELETE FROM ESDUS WHERE UNAME = SY-UNAME.
* Delete all User-Settings in search help
DELETE FROM DDSHDEFSH WHERE USERNAME = SY-UNAME.
ENDABAP.

Creating a User-defined Selection variant for Transaction ME21N

Hi,
In transaction ME21N with the 'Document Overview' feature turned on we can view a list of standard selection variants. I would like to add a user-defined selection variant to that list. There is an OSS Note 377180 present which describes how to do that but(as per transaction SNOTE) that note cannot be implemented in our system. Is there any other way to get that done?
Any help would certainly be appreciated.
Thanks,
Alam.

So I am having a similar issue. I have a fixed length flat file with 3 different record types.
1 a header ( length is 82 bytes with the first byte set to H ( single record always the first )
2 a detail record ( length is 382 bytes ) with the first byte set to D ( multiple records )
3 a trailer record ( length is 82 bytes ) with the first byte set to T ( single record always the last )
I created a UD OTD with 3 elements for each record type, RECORD_TYPE is the first field 1 byte. Matching for each on either H,D, or T. When I try and test the OTD with the Run Test button I get an unmarshal error
<SOD>""<POS>"HACCUMULAT..." failed input match, Fog#431, after <no path>: failed node: trailing junk in fixed/parent
HACCUMULATED BENEFIT TRANSACTION FILE 20080801 20080825 0 0
D ar3531 ar3531 ar3531 ar3531000 55887027260 30.000 30 5098765 20080804 000T114 120080806 82820P30000001024511 25.00 0.00 25.00 0.00 25.00 25.00 0.00 0.00 0.00 0.00 0.00T
TACCUMULATED BENEFIT TRANSACTION FILE 20080801 20080825 2894 0 0
Not sure whats going on, so if anyone has any suggestions on where to look that would be great
Thanks

Transaction ME21n (Will not run as a BACKGROUND SESSION)

The requirement is to generate Purchase Orders (Stock Transport Orders to be precise).
The RFC has to create a session which will be executed...say...before midnight to generate the sto (TC -> SM35).
I have used BDC inside my RFC calling the transaction ME21n. It runs fine as a foreground session, but will give a error if the session is run as a background session (Due to the dropdown lists in ME21n I guess).
The solution I figured out is to use ME21. This does execute in the background successfully.
But given the fact that ME21 is the OLD transaction and ME21n (enjoy sap transaction, right?) to be the one to be used now, my dilemma is in choosing ME21 and risk the scenario of this transaction being obsolete and not supported the SAP for technical support in the future.
Can any body please help me on this.
Thank you.
Message was edited by: Sai Sanathan

hello,
with transaction VL10BATCH you can create new variants, and shedule background jobs. This should work.
However, you need another user role. (on the last tab of the selection screen of VL10B)
It is the F code profile you have to change. With this profile you can choose whether a list needs to be shown, or whether the deliveries have to be created right away (without showing the list). The second option should work in background. After delivery creation, you can check the   log using transaction V_SA.
So you need to create a selection variant with changed user-role for the backround job.
You can maintain user-roles via transaction VL10CUA.
You can input-enable user-role via transaction VL10CUV.
If you don't want the users to be able to run VL10B without showing the list, you have to create your own scenario, and use VL10X to start this scenario. Although this is not really necessary.
I hope this makes things more clear for you.
regards,
Joris.
Here is a copy of the OSS-note (310022) I was talking about:
Symptom
o For regular planning, you want to transfer the delivery creation
       in a job to the system administration. Here, you have
       difficulties.
o Background processing of Transaction VL10* does not generate
       deliveries but only a list in the spool.
Additional key words
VL10BATCH, VL10A, VL10B, VL10C, VL10D, VL10E
Cause and prerequisites
Solution
For planning the delivery creation in background processing you must
o activate a user role for immediate creation of deliveries (in the
       standard system, the immediate delivery creation is deactivated
       for all user roles for reasons of safety),
o create a selection variant for one of Transactions VL10*.
Activation of the user role for background processing
The user role controls the entire processing of the delivery list.
Within Transactions VL10*, you can display and maintain the user role on
the "User role" tab page. You can carry out the maintenance also via
Transaction VL10CUA. Note 301578 describes how to make a user role ready
for input.
An F-code profile is linked to the user role. The F-code profile
controls the internal process of the transaction. Two F-code profiles
are provided in the standard system:
o 0001 Display delivery list
o 5001 Supply delivery list
In the user role you want to use for background processing, you have to
replace F-code profile (not "AllowedDialogFCodes") 0001 with profile
5001:
1. Call Transaction VL10CUA for maintenance of the user roles.
2. You might want to copy one of standard user roles 5001 to 5103 that
    is planned for processing in the background to a separate role in
    the customer namespace, for example, 9001 or Z***.
3. Branch to the detail view of the user role and change the entry for
    the F-code profile from "Display delivery list" to "Supply delivery
    list".
Creation of the selection variant
1. Call the desired Transaction VL10* and branch to the "User role" ta
    page. Do not use Transaction SE38 or VL10BATCH for variant
    maintenance of VL10*.
2. Here, enter the user role that you have maintained for background
    processing.
    Caution! If you use a user role with an F-code profile for the
    immediate creation of deliveries, you receive no dialog with a
    shipping due list but the deliveries are created immediately at the
    start of the selection!
3. Enter the remaining selection criteria on the various other tab
    pages.
4. Select function "Goto -> Variants -> Save as variant..." and save
    the selection criteria entered as a variant. You might classify the
    variant as "Only for background processing", in order to avoid a
    start of the delivery creation in the dialog by mistake.
5. Make sure that the objects of selection screen 1060 have been saved
    and that checkboxes "Save field without values" are not filled with
    all objects (in particular in Release 4.6B) for the desired
    settings.
You can schedule the selection variant via Transaction VL10BATCH for
regular use in the batch.
And also the OSS-note (301578) about input-enabling user-role:
SAP Note No. 301578                          22.08.2005           Page 1
Number              301578
Version             4 from 08.05.2000
Status              Released for Customer
Set on              08.05.2000
Language            EN
Master language     DE
Short text          VL10: Ready to input status of user role
Responsible         SAP AG
Component           LE-SHP-DL
                    Delivery Processing
Long text
Symptom
On the selection screen of transaction family VL10*, the selection
criteria in the 'user role' tab are no longer ready for input of Release
4.6C.
They are delivered in the standard SAP system not ready for input.
Additional key words
Cause and prerequisites
As of Release 4.6C, the ready for input status in the 'user role' tab is
linked to settings in the scenario and the user role.
1. In order to get the ready for input status for the "Role" field, set
    "Allow assignment" to 'X' in the scenario that you are using
    (Transaction VL10CUV or SM31, V_T186V, T186V-ALLOW_USER_ROLE = 'X').
The system administrator (Customizing authorization) can then
    determine whether only the user role preset in the system is allowed
    or whether any number of other user roles may also be used for this
    scenario.
2. For the check box "Use list profile" and therefore all possible
settings for the "user role" tab, the ready for input status in the
    user role can be allowed in "Chang. attrbute" (changeability of the
    attributes).
    Set this field with Transaction VL10CUA for the used user role to
    'X' (Transaction VL10CUA, or SM31, V_T186, t186-CHANGE_ALLOW = 'X').
Background:
The settings in the scenario and user role have in the course of time
become so wide-ranging and far-reaching that an additional feature had
to be implemented: a system administrator must be able restrict the
changes by the end user at different levels .
You now have the option of determining for every user role whether that
settings determined on the selection screen may be changed again.
You also have the option of determining in every scenario in which this
user role is used whether the change is allowed for another user role.
In the context of the fixed link of the scenario to a transaction and
therefore to the authorization concept of mySAP.com - user-roles can be
controlled at user level - whether the settings for the user role tab of
the selection screen of VL10* may be changed by a user or not.
Solution
Maintain setting in scenario (VL10CUV) and user role (VL10CU)
(Customizing authorization required).

Screen Exits for Transaction ME21N

Hi Experts ,
my requirement is to add a new screen field of time for the transaction ME21N .Can any one guide me how to do This.I am new to user exits and dialog programming.Please can any one help me out regarding this.
Thanks in Advance.
regards
Srihari.

HI
GOTO TCODE SMOD,
CREATE A PROJECT AND CALL COMPONENT - MM06E005
THIS ALLOWS U TO CREATE A ADDITIONAL SUBSCREEN
CALL THE REQUERD FIELD IN THE SCREEN
THIS WILL ADD FIELD TO THE STANDARD TABLE UNDER STRUCTURE CI_EKKO
NOW IN THE CODE PART JUST PASS SCREEN VALUE TO TABLE VALUE
TC
SAJI

Jump to transaction me21n from output screen.

hi,
   I am displaying PO ,item no from ekpo table.On the output screen where data is displayed , when i click on PO no i need to go to transaction me21n.Can anyone plz help me and tell me the mechanism.

you can go to ME23N where it will display the particular PO.
Check this alv report.
REPORT ZMM_PO_TEXT
        no standard page heading
        line-size 300
        message-id zmsg.
                        Tables                                         *
TABLES : EKKO,         "Purchasing Document Header
         EKPO,         "Purchasing Document Item
         EKBE.         "History per Purchasing Doc
    Internal table   for display                                *
DATA : begin of it_item occurs 0 ,
       ebeln like ekpo-ebeln,        "pur doc no
        ebelp   like ekpo-ebelp,        "pur doc no item
        matnr   like ekpo-matnr,        "material no
        werks   like ekpo-werks,        "Plant
        bedat   like ekko-bedat,        "pur doc date
        banfn   like eban-banfn,        "Purchase requisition number
        bnfpo   like eban-bnfpo,        "Item number of purchase requisition
        charg like ekbe-charg ,       "Batch Number
        end of it_item.
DATA it_temp like table of it_item with header line.
ALV VARIABLES AND INTERNAL TABLES
TYPE-POOLS: slis.
DATA:st_layout      TYPE slis_layout_alv,
       it_fieldcat    TYPE slis_t_fieldcat_alv,
       it_listheader TYPE slis_t_listheader,
       it_event       TYPE slis_t_event,
       keyinfo        TYPE slis_keyinfo_alv.
DATA:ls_selfield TYPE slis_selfield.
                   VARIABLES                                     *
DATA:
        v_repid       LIKE sy-repid,
        name like thead-tdname,
        lines like tline occurs 0 with header line.
*SELECTION SCREEN DEFINITIONS
SELECTION-SCREEN: BEGIN OF BLOCK a1 WITH FRAME    TITLE     TEXT-001.
    SELECT-OPTIONS:
                     so_plant FOR ekpo-werks,
                     so_date FOR ekko-bedat OBLIGATORY,
                     so_matnr for ekpo-matnr,
                     so_ebeln for ekko-ebeln,
                     so_ekorg for ekko-ekorg,
                     so_ekgrp for ekko-ekgrp.
SELECTION-SCREEN: END OF BLOCK a1.
                  INITIALIZATION                                *
INITIALIZATION.
      v_repid = sy-repid.
*START-OF-SELECTION
START-OF-SELECTION.
      PERFORM get_data.
      IF it_item[] IS NOT INITIAL.
         PERFORM display_data.
      ELSE.
         MESSAGE i012(zmsg).
      ENDIF.
                    END-OF-SELECTION                                 *
END-OF-SELECTION.
*START-OF-SELECTION.
*perform get_data.
*perform display_data .
*******AT LINE-SELECTION.
******if it_data-banfn is initial.
******SET PARAMETER ID 'BES' FIELD it_data-EBELN.
******CALL TRANSACTION 'ME23N'.
******else.
******SET PARAMETER ID 'BAN' FIELD it_data-Banfn.
******CALL TRANSACTION 'ME53N'.
******endif.
          Form get data                        ******************
FORM get_data.
if so_date-high is initial.
so_date-high = sy-datum.
endif.
select aebeln aebelp amatnr awerks
          b~bedat
          c~charg
          into corresponding fields of table it_item
          from ekpo as a inner join ekko as b
          on aebeln = bebeln
          inner join eket as c on aebeln = cebeln and aebelp = cebelp
          where a~werks in so_plant
          and   a~matnr in so_matnr
          and   a~ebeln in so_ebeln
          and   b~bedat between so_date-low and so_date-high
          and   b~ekorg in so_ekorg
          and   b~ekgrp in so_ekgrp .
DELETE ADJACENT DUPLICATES FROM it_item.
SORT it_item by ebeln bedat.
loop at it_ITEM.
select single banfn bnfpo into (it_ITEM-banfn,it_ITEM-bnfpo) from eban where ebeln = it_ITEM-ebeln
                                                                          and ebelp = it_ITEM-ebelp.
*select single charg into (it_ITEM-charg) from ekbe where ebeln = it_ITEM-EBELP.
    if sy-subrc IS INITIAL.
CONCATENATE it_item-banfn it_item-bnfpo INTO NAME.
CALL FUNCTION 'READ_TEXT'
EXPORTING
   CLIENT                        = SY-MANDT
    ID                            = 'B06'
    LANGUAGE                      = sy-langu
    NAME                          = NAME
    OBJECT                        = 'EBAN'
TABLES
    LINES                         = lines
EXCEPTIONS
   ID                            = 1
   LANGUAGE                      = 2
   NAME                          = 3
   NOT_FOUND                     = 4
   OBJECT                        = 5
   REFERENCE_CHECK               = 6
   WRONG_ACCESS_TO_ARCHIVE       = 7
   OTHERS                        = 8
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
MODIFY IT_ITEM.
else.
CONCATENATE it_item-EBELN it_item-EBELP INTO NAME.
CALL FUNCTION 'READ_TEXT'
EXPORTING
   CLIENT                        = SY-MANDT
    ID                            = 'F10'
    LANGUAGE                      = sy-langu
    NAME                          = NAME
    OBJECT                        = 'EKPO'
TABLES
    LINES                         = lines
EXCEPTIONS
   ID                            = 1
   LANGUAGE                      = 2
   NAME                          = 3
   NOT_FOUND                     = 4
   OBJECT                        = 5
   REFERENCE_CHECK               = 6
   WRONG_ACCESS_TO_ARCHIVE       = 7
   OTHERS                        = 8
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endif.
IF LINES[] IS INITIAL.
DELETE IT_ITEM.
ENDIF.
CLEAR: IT_ITEM, LINES.
REFRESH : LINES.
endloop.
ENDFORM.                    " display_data
*FORM FOR DISPLAY DATA
FORM display_data .
          PERFORM fill_layout_structure.
          PERFORM fill_field_catalog_table.
          PERFORM get_event USING it_event.
          PERFORM fill_listheader USING it_listheader.
          perFORM call_alv_function.
ENDFORM.                    " display_data
*&      Form fill_layout_structure
      text
--> p1        text
<-- p2        text
FORM fill_layout_structure .
    st_layout-zebra = 'X'.
ENDFORM.                    " fill_layout_structure
*&      Form fill_field_catalog_table
      text
--> p1        text
<-- p2        text
FORM fill_field_catalog_table .
PERFORM fill_field_catalog USING :
           'EBELN'    'P.O Number'       'IT_ITEM' 'X'      space '10' 'X',
           'EBELP'    'P.O. Item No' 'IT_ITEM' space    space '10'    space,
           'BEDAT'     'P.O. Date'     'IT_ITEM' space    space '10'    space,
           'WERKS'     'Plant'            'IT_ITEM' space    space '10'    space,
           'MATNR'     'Material no'      'IT_ITEM' space    space '18'    space,
           'BANFN'     'P.R. Number'   'IT_ITEM'     space    space '18'    space,
           'CHARG'     'Batch Number' 'IT_ITEM' space space '10'    'space'    .
ENDFORM.                    " fill_field_catalog_table
*FORM FOR FILLING FIELD CATALOG
FORM fill_field_catalog USING f d t p S o h.
      DATA: wa_fieldcat TYPE slis_fieldcat_alv.
      STATICS v_pos TYPE i VALUE 1.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = v_pos.
      wa_fieldcat-fieldname = f.
      wa_fieldcat-seltext_m = d.
      wa_fieldcat-tabname    = t.
       wa_fieldcat-hotspot = h.
      APPEND wa_fieldcat TO it_fieldcat.
      v_pos = v_pos + 1.
ENDFORM.                    "fill_field_catalog
*&      Form fill_listheader
      text
     -->P_IT_LISTHEADER text
FORM fill_listheader USING    P_IT_LISTHEADER TYPE   slis_t_listheader.
DATA : wa_listheader TYPE slis_listheader.
CLEAR wa_listheader.
wa_listheader-typ = 'S'.
wa_listheader-info ='PURCHASE ORDER TEXTS '.
APPEND wa_listheader TO it_listheader.
ENDFORM.                    " fill_listheader
*&      Form get_event
      text
     -->P_IT_EVENT text
FORM get_event USING    P_IT_EVENT    TYPE slis_t_event.
   DATA : wa_event TYPE slis_alv_event.
   CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
      I_LIST_TYPE           = 0
    IMPORTING
      ET_EVENTS             = it_event.
      READ TABLE it_event WITH KEY name = slis_ev_top_of_page INTO wa_event.
       IF SY-SUBRC = 0.
       MOVE 'TOP_OF_PAGE' to wa_event-form.
       APPEND wa_event to it_event.
   ENDIF.
ENDFORM.                    " get_event
*FORM FOR TOP_OF_PAGE(to assign form for the top-of-page event)
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      it_list_commentary = it_listheader.
ENDFORM.                    "top_of_page
*FORM FOR ALV FUNCTIONS
FORM call_alv_function.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
    I_INTERFACE_CHECK              = ' '
    I_BYPASSING_BUFFER             =
    I_BUFFER_ACTIVE                = ' '
      I_CALLBACK_PROGRAM             = v_repid
    I_CALLBACK_PF_STATUS_SET       = ' '
     I_CALLBACK_USER_COMMAND        = 'CALL_TCODE'
    I_STRUCTURE_NAME               =
     IS_LAYOUT                      = st_layout
     IT_FIELDCAT                    = it_fieldcat[]
    IT_EXCLUDING                   =
    IT_SPECIAL_GROUPS              =
    IT_SORT                        =
    IT_FILTER                      =
    IS_SEL_HIDE                    =
    I_DEFAULT                      = 'X'
    I_SAVE                         = ' '
    IS_VARIANT                     =
     IT_EVENTS                      = it_event[]
    IT_EVENT_EXIT                  =
    IS_PRINT                       =
    IS_REPREP_ID                   =
    I_SCREEN_START_COLUMN          = 0
    I_SCREEN_START_LINE            = 0
    I_SCREEN_END_COLUMN            = 0
    I_SCREEN_END_LINE              = 0
IMPORTING
    E_EXIT_CAUSED_BY_CALLER        =
    ES_EXIT_CAUSED_BY_USER         =
    TABLES
      T_OUTTAB                       = it_item
EXCEPTIONS
    PROGRAM_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.
endform.
*FORM FOR ALV CALL_TCODE
FORM call_tcode USING r_ucomm ls_selfield LIKE ls_selfield.
    CASE r_ucomm.
      WHEN '&IC1'.
        IF ls_selfield-fieldname = 'EBELN'.
          SET PARAMETER ID 'BES' FIELD ls_selfield-value.
          CALL TRANSACTION 'ME23N'.
        ENDIF.
        IF ls_selfield-fieldname = 'BANFN'.
          SET PARAMETER ID 'BAN' FIELD ls_selfield-value.
          CALL TRANSACTION 'ME53N' AND SKIP FIRST SCREEN.
        ENDIF.
    ENDCASE.
For classical
use HIDE statement, AT LINE SELECTION event and CALL TRANSACTION Statement.
regards,
Prabhu
Reward if it is helpful.

How to add function key to a menu exit in a standard transaction

Hi all,
I have a requirement to add a function key for a menu item in a standard transaction.
In Menu bar we have an option Extras->Other->Repricing . Now my requirement is if i click a function key (ex. F9) the code under the menu exit (Repricing) should trigger. For that i had a function exit EXIT_SAPLJHPA_011 and in this the menu exit SAPLJHPA +CU7 is defined.could anyone suggest me the procedure in detail to add a function key..
Thanks in advance,
Uday.

Hi
for this u have to edit standard PF-status, that particular transaction is using. becarefull as the same pf-status may be used for many programs.
get the PF-status for that program. you can get the pf-status via se80, give the program name and u can get the the list of all the objects of that prigram, there you can edit the standard status and can add the function key to your menu item.

How to transfer data in A tableview control in transaction ME21n

Dear friends,
I m new in the field of SAP ABAP.
And right now i m trying to transfer the data in a tableview control in transaction ME21n. I've recorded the sequence of mandatory fields in transaction ME21n but, when i try to transfer the data using BDC call transaction method the order of manadatory fields change.
I m trying to transfer data from text file.
If anybody has a solution to this problem please tell me how to sort out this.
Thanks in advance.

Hi Vivek,
Welcome to SDN.
BDC solution will not work with transaction ME21N.
ME21N is an enjoy SAP transaction which has a lot of new objects that BDC can not call/use.
Please use transaction ME21 instead of ME21N.
Hope this will help.
Regards,
Ferry Lianto
Please reward points in helpful.

Add button to RF Standard transaction

Hello,
Is it possible to add a push button to an RF Standard transaction? and How?
Thx

Hi,
SAP has provided Dummy screens to each RF screen for you to enhance it. They usually named as 'SAPLXLRF' and screen number would be 9XXX . 'XXX' being the original screen number. Then you need to activate the corresponding user exit that starts with MWMRF* for the corresponding screen. Also in the RF Screen Management you need to add an entry with Variant '1'.
Hope that helps.
Thanks
Vinod.

How to create F4 for the standard transaction

Hi all ,
How to create F4 for the standard transaction for a particular field .
Bye

Santosh,
You can create F4 values for a field in a standard Transaction .
1. First search for a standard search help meeting your requirement .
2. If you don't find one, create your own custom (z) serach help .
( 1 is preferable )
After that, include that serch help to the standard field in the transaction .
For this u need to go to the screen
( F1->F9-> screen-> Field )
Click on the property of the field and include the search help .
You ll require the access key from the basisi guys as u r changing standard .
Hope it helps,
~ laxmi
Reward for helpful answers

Calling custom dialog screen from Standard Transaction(user Exit)

Hi, I'm calling Standard Transaction from a Custom Screen. I'm calling a custom screen again with in standard transaction (implemented custom screen thru user exits using macros). But when I click 'continue/cancel' in the custom screen, control is going back to main cutom screen rather go back to standard transaction. Could anyone please help me out how to come back to standard transaction from custom screen rather going back to main cutom screen.
***INCLUDE LZ_R_FORWARD_FORWARD_LOADI01 .
*&      Module USER_COMMAND_9000 INPUT
MODULE user_command_9000 INPUT.
CASE sy-ucomm.
    WHEN 'EXEC'.
      PERFORM validate_popup_data.
      IF flag_error_screen NE 'X'.
        MOVE-CORRESPONDING ZFFL_POPUP to var_ZFFL_POPUP.
        clear flag_return.
        SET SCREEN 0.
        LEAVE SCREEN.
      ENDIF.
    WHEN 'CANC'.
      flag_return = 'X'.
      SET SCREEN 0.
      LEAVE SCREEN.
    WHEN OTHERS.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_9000 INPUT
*&      Module exit_9000 INPUT
MODULE exit_9000 INPUT.
CASE sy-ucomm.
    WHEN 'CANC'.
*      MOVE perf_flag TO lbpla_exist_flag.
      flag_return = 'X'.
      SET SCREEN 0.
      LEAVE SCREEN.
ENDCASE.
ENDMODULE.                 " exit_9000 INPUT
Thanks in advance.

Hi
So the command SET SCREEN 0. LEAVE SCREEN. should "place" the program just after the calling of the popup so here:
FUNCTION z_call_screen.
* Call the Pop up screen
    CALL SCREEN 9000 STARTING AT 35 05.
"<------------------------- The program should be here after going back from popup 9000
ENDFUNCTION.
Is it true?
Max

Standard transaction ME21N

Similar Messages

Maybe you are looking for