Screen field copy

Hi,
I want to copy screen field value from one screen to another
SAPLE10R 2015 -
> SAPLXES30 0100
Please let me know how to do this
Present i want print the value in screen: SAPLXES30 0100
Thanks

Ho to use this FM:    DYNP_VALUES_READ
DATA: GLOBAL_DYNPFIELDS    LIKE DYNPREAD OCCURS 0 WITH HEADER LINE.
        GLOBAL_DYNPFIELDS-fieldname = 'EDEVICED-ZWGRUPPE'.
         APPEND GLOBAL_DYNPFIELDS.
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
    DYNAME                               = lv_repid
    DYNUMB                               = lv_dynnr
TABLES
    DYNPFIELDS                           = GLOBAL_DYNPFIELDS
EXCEPTIONS
   INVALID_ABAPWORKAREA                 = 1
   INVALID_DYNPROFIELD                  = 2
   INVALID_DYNPRONAME                   = 3
   INVALID_DYNPRONUMMER                 = 4
   INVALID_REQUEST                      = 5
   NO_FIELDDESCRIPTION                  = 6
   INVALID_PARAMETER                    = 7
   UNDEFIND_ERROR                       = 8
   DOUBLE_CONVERSION                    = 9
   STEPL_NOT_FOUND                      = 10
   OTHERS                               = 11

Similar Messages

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

Value Transport (Exporting) to multiple screen fields in Search Help

Hi all,
I have created elementary search help using exit and attached it to data element. After F4 when I get hitlist I want all the values from the selected rows to get copied to the screen fields. I.e. I want the value transport.
In the search help I am exporting those values which I want to get copied back but I am unable to get the result.
With Regards,
Chandra

Hi,
You can get this behaviour only by making the SEARCH HELP assignment at the STRUCTURE level.
You need to create or use an existing structure to create your screen fields which you want to populate using the search help. Then assign this search help directly to the structure and there do the mapping between structure fields and the search help export params.
Only by doing this you can autopopulate the values using one search help.
Regards,
Sesh

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 AT SELECTION-SCREEN and NOT in END-OF-SELECTION.
Regards,
Subramanian V.

To populate a ComboBox according to a screen field

Hi folks! I'm newbie on ABAP and I have the following problem:
I have a screen field. According with the data entered on this field I want to populate a ComboBox using the function VRM_SET_VALUES, but I can't found a proper event to do the population.
The "at selection-screen on field_name" option is executed at the end, with all checks, but not after I live or change the first field. Anybody knows a solution for it?
Thanks in advance.

Check the below code:
*& Report YSAMPLE12 *
REPORT ysample12 .
DATA: i_dynpfields TYPE dynpread OCCURS 0 WITH HEADER LINE.
TYPE-POOLS : vrm.
DATA : vrm_data TYPE vrm_values.
DATA : wa_vrm LIKE LINE OF vrm_data.
PARAMETERS : p_val TYPE c.
PARAMETERS : p_opt(10) TYPE c AS LISTBOX VISIBLE LENGTH 10.
AT SELECTION-SCREEN.
REFRESH: i_dynpfields.
i_dynpfields-fieldname = 'P_VAL'.
APPEND i_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
TRANSLATE_TO_UPPER = ' '
REQUEST = ' '
PERFORM_CONVERSION_EXITS = ' '
PERFORM_INPUT_CONVERSION = ' '
DETERMINE_LOOP_INDEX = ' '
 TABLES
 dynpfields = i_dynpfields
EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
AT SELECTION-SCREEN OUTPUT.
REFRESH: vrm_data.
READ TABLE i_dynpfields WITH KEY fieldname = 'P_VAL'.
IF i_dynpfields-fieldvalue = 'A'.
 wa_vrm-key = '1'.
 wa_vrm-text = 'Create'.
 APPEND wa_vrm TO vrm_data.
 wa_vrm-key = '2'.
 wa_vrm-text = 'Change'.
 APPEND wa_vrm TO vrm_data.
 wa_vrm-key = '3'.
 wa_vrm-text = 'Delete'.
 APPEND wa_vrm TO vrm_data.
ELSEIF i_dynpfields-fieldvalue = 'B'.
 wa_vrm-key = '4'.
 wa_vrm-text = 'Copy'.
 APPEND wa_vrm TO vrm_data.
ENDIF.
CALL FUNCTION 'VRM_SET_VALUES'
 EXPORTING
 id = 'P_OPT'
 values = vrm_data
 EXCEPTIONS
 id_illegal_name = 1
 OTHERS = 2.
U have press enter after giving value in the P_VAL.
Regards,
Prakash.

Adding an extra screen field in CJ88

Hi,
The FICO consultant wants to know whether we can add an extra screen field in CJ88.He wants to add the posting year.Currently there is facility to add posting period and the posting year will be same as the fiscal.He wants to change the posting year.Due to this he wants to add an extra screen field - posting year so that the user can change it during reversal.
If yes then how it is bo done.
If not, is it possible to copy the entire CJ88 code and make zprogram and ztcode and add this extra field.
Please let me know your suggestion.
Thanks,
Rajani

HI,
Perhaps you can try with USEREXIT_CHECK_VBAP in report MV45AFZB.
Other possibilty is the BADI BADI_SD_SALES_ITEM, where the method ITEM_CHECK.
Perhaps the most powerful is userexit_save_document in report MV45AFZZ, but it works when you save the document. Here you can compare XVBAP (with the new item will have the field UPDKZ = 'I') with YVBAP (you can compare the line items of both internal tables). Finally, you can use the status of deliveried and billed of XVBUP, YVBUP, XVBUK, YVBUK to do the final checks.
Perhaps you can fix warning messages in the first exits (in dialog) and in the saving event set the error message.
Set the break point and check the data in these structures, and think in the right algorithm.
I hope this helps you
Regards,
Eduardo

Validating Screen Fields in FD32 - BTE 1520

Hello everyone,
I have a requirement to make various checks before saving in FD32. For example I want to make sure that KNKK-DBEKR will be less than or equal to KNKK-KLIMK.
I have searched SCN and I have implemented BTE 1520 (you can see an example thread here).
My problem is that while in BTE 1520 I don't have the screen fields available (or at least I don't know how to make them available to my function module).
Has anyone done something similar?
Thank you in advance.

Thanks Neal, but I already tried that. The function module (a copy of SAMPLE_INTERFACE_00001520) uses only two variables I_KUNNR and I_KKBER.
As you can see in the screenshot below (from the debugger), I have been trying to find whether I have anything else available at that point.

VL10 and new selection-screen fields

Hi experts.
My requirement is to add new selection-screen field to second tab in VL10.
After analyse many topics the solution was to copy VL10 to ZVL10.
Also V50R_USEREXIT_TRANSF was copyed and there was added specific code.
Furthemore note:524424 was implemented (header in form definition in V50R_USEREXIT_TRANSF ), and the SHP_VL10_SELECT_OPTIONS was enhanced. As I understood from this stage we have selection-criteria in repeort.
The problem is that I don't know how to transfer this data to ALV.
Any tips ?
Thanks .
Daniel.

hi
how did you do that. i have to add select options in coois tcode in header and operational level.but only using badi. using screen enhancement it is possible bt how to do that using bagi "workorder_infosystem"..
please help me out..

Change screen field network and upload additional wbs network activity

Dear All,
1st. How can i change the screen field company code in network header (assignment tab) to input or required. I tried OPUA but it doesnt show company code. In default it shows that network header (company code) in display mode.
2nd. How can i add additional WBS,network and activity using additional enhancement for easy use method. Or in other word, is there any enhancement program..not cj20n / cj20?
really appreciate.
nies

Hi
2nd. is there any other solutions? users donot convinience to use cj20n / or copy from template? is there badi /program upload to be used? in other words, users can maintain it in excel then upload it..
Use this BAPI to create WBS elements
BAPI_BUS2054_CREATE_MULTI
Sorry for the my last post on the point 1
The company code for network order is coming from thw WBS element, that you cannot change in network order. This is standard setting.
Thanks
S.Murali

Unable to capture screen fields in eCATT

Problem description 1 : Unable to capture screen fields in eCATT
Recording using SAP GUI Method.
Problem description 2 :Unable to capture Tab controls while recording
in eCATT using SAP GUI Method.
Thaks for any suggestion you could provide me and once again for your courtesy attention.
Regards,
Eric Monteiro

Hi Phani,
Please try below code:
*data declaration for reading values given by user in the selection screen field.
DATA: BEGIN OF i_tab OCCURS 0.
          INCLUDE STRUCTURE rsselread.
DATA: END OF i_tab.
MOVE: 'LOGSYS' TO i_tab-name,
        'P' TO i_tab-kind. u201CP For parameter
APPEND i_tab.
MOVE: 'GP_SIMVE' TO i_tab-name,
        'P' TO i_tab-kind. u201CCheck if field is Parameter
APPEND i_tab.
*move program name and screen number into local variable.
l_prog = sy-repid. u201C(Try by directly passing program name also)
l_dynnr = sy-dynnr. u201C(Try by directly passing Screen number also)
*calling function module to get the value given by user.
CALL FUNCTION 'RS_SELECTIONSCREEN_READ'
    EXPORTING
      program     = l_prog
      dynnr       = l_dynnr
    TABLES
      fieldvalues = i_tab.
Hope this should slove your issue.
Thanks & Regards,
Gaurav.

How to create a F4 help for a report selection screen field

hi,
can any one guide me to create F4 help for a field in a selection screen in a report program,plz give me a sample code

hi,
Here are the following ways
1.with the help of match code objects we can create the F4 Functionality for Field.
Syntax is :
PARAMETERS: p_org LIKE t527x-orgeh MATCHCODE OBJECT zorg.
2. One more thing is we can do it with Search Help's also.
3. Even we can do it HELP Views also.
Help Views:
You have to create a help view if a view with outer join is needed as selection method of a search help
The selection method of a search help is either a table or a view. If you have to select data from several tables for the search help, you should generally use a database view as selection method. However, a database view always implements an inner join. If you need a view with outer join for the data selection, you have to use a help view as selection method.
All the tables included in a help view must be linked with foreign keys. Only foreign keys that have certain attributes can be used here. The first table to be inserted in the help view is called the primary table of the help view. The tables added to this primary table with foreign keys are called secondary tables.
The functionality of a help view has changed significantly between Release 3.0 and Release 4.0. In Release 3.0, a help view was automatically displayed for the input help (F4 help) for all the fields that were checked against the primary table of the help view. This is no longer the case in Release 4.0.
As of Release 4.0, you must explicitly create a search help that must be linked with the fields for which it is offered (see Linking Search Helps with Screen Fields ).
Existing help views are automatically migrated to search helps when you upgrade to a release higher than 4.0.
A help view implements an outer join, i.e. all the contents of the primary table of the help view are always displayed. You therefore should not formulate a selection condition for fields in one of the secondary tables of the help view. If records of these secondary tables cannot be read as a result of this selection condition, the contents of the corresponding fields of the secondary table are displayed with initial value.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 15, 2008 3:15 PM

Truncation of selection screen field in reports

Hi,
Is there any way to avoid truncation of selection screen fields in ABAP reports? For eg, I declare:
SELECT-OPTIONS: s_test FOR ztest-test_field NO INTERVALS
The length of this field in the table is 30 chars. However, on displaying the field via selection screen, this gets truncated to around 18 or so. How do I avoid this as I need to display the full length of the field?

Hi,
Try this
Tables : makt.
select-options maknr for makt-maktx.
now go to the screen painter of your program in change mode and move the Help buttons first to the Right each. now increasethe length of the Matnr Field length so that they are equal to 40 Char. in your program you have handle the length now if you want to restrict to 18 otherwise it will be ok
if they don't fit you need incease the Size of the Screen Visible area both in the Screen Painter as well as in the
Screen Attributes
You also get an Information Message just ignore that.
Just open your program in SE80 if you can't go to the screen painter in SE38. the other way just keep this program in Display mode and execute then take F1 help , take Technical Information and double click on the Screen number now go to the Screen Layout and go to Change mode here.
Regards,
Shirisha

Regarding Search help on selection-screen field

Hi there,
I am working on custom tables.
I have a requirement to maintain search pattern on a selection-screen field.
selection-screen parameter: p_name which is company name filed from Z table.
By giving a string like Holl* and by pressing F4 on the field p_name it has to popup a dialogbox having list of company names starting with Holl.
Thanks in advance.
-Tulasi

Hi
Go through the link given below :
How to create a search help for my own fields in selection screen
F4 search help on report selection screen
also try :
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
DDIC_STRUCTURE = ' '
RETFIELD = 'VKORG'
PVALKEY = ' '
DYNPPROG = SY-REPID
DYNPNR = SY-DYNNR
DYNPROFIELD = 'P_VKORG'
STEPL = 0
WINDOW_TITLE =
VALUE = ' '
VALUE_ORG = 'C'
TABLES
VALUE_TAB = T_TABLE1
FIELD_TAB = field_tab
RETURN_TAB = RET_TAB
DYNPFLD_MAPPING = DYN_TAB
EXCEPTIONS
PARAMETER_ERROR = 1
NO_VALUES_FOUND = 2
OTHERS = 3
With Regards
Nikunj shah

Selection screen field problem

Hello experts..
i have a selection screen , in that i have a field   s_bwart for mseg-bwart.
some times the user will input the data in the field and sometimes he wont. we have fixed movement types combination like
11-21 , 13-24 , 13-56 , 101-543 , 101-544 etc.
if the user did not input any thing in the selection screen , i am populating s_bwart in at-selection screen event with all the mvt types. after executing the report when user presses the back button to come to the selection screen, there the s_bwart field is containing all the mvt types in single values ie in the select options screen. So the user dont want that, if he comes back nothing should be there in the selection screen field s_bwart if he has not inputted anything. if he inputs only 11 mvt type then when he comes back after executing the report he should see only 11 in the select screen field ie s_bwart. Please send the replies on how to solve the problem.

hi,
in ur program try to display values for users in START-OF-SELECTION event as it triggers after the selection screen displayed for users. if user doesn't give any input then display default values in this event. and also create a variable
for ex:
data: ws_flag type c,
         p_value type i.
after u display default values for users in selection screen assign the flag as ' X '
ws_flag = 'X'.
before leaving ur program based on flag try to do like this.
if ws_flag = ' X '.
    clear s_data. // s_data is the select options for u.
else.
     s_data = p_value. // the value which user gave in selection screen as i/p.
endif.
if helpful reward some points.
with regards,
Suresh Aluri.

Regarding Selection-Screen Field Display

Hi All,
I have issues with Selection-Screen field display.
The Actual issue is i had declared a selection screen field as: s_exgen FOR embk-exgen.
EMBK-EXGEN is actually 20 Char length field.
But in output display it is being shown as 18 Char field though i can type in all 20 characters.
But display restricted to 18 Characters only.
Can anybody give me the solution for the same!
Thanks in advance.
Thanks & Regards,
Prasad.

Hi,
You can decrease the visible length of the field but you can not increase more than database field length. check SAP help on this :
select-options: s_exgen FOR embk-exgen VISIBLE LENGTH 5.
... VISIBLE LENGTH vlen
Effect
This addition allows you to shorten the visible length of the corresponding screen field on the selection screen to vlen.
Variant 2
SELECT-OPTIONS sel FOR (f).
Additions as in variant 1.
Effect
In this variant, (f) must be a field containing the name of the actual reference field at runtime. The system creates the LOW and HIGH fields as character fields with length 45. However, their appearance on the selection screen is inherited from the reference field whose name is contained in field f at runtime.
Regards
Appana

Screen field copy

Similar Messages

Maybe you are looking for