Populating PR No in collective no screen field of ME41

Hi all,
We have one requirement , when we are creating RFQ with reference to PR then collective no field ( EKKO-SUBMI ) should be updated automatically with the PR no which is referred in creating RFQ . Please help me in doing this requirement.
Thanks in Advance.
Manu

Hi Marvender,
I am facing same problem.
Can you please let me know is there any table which will contain PR number when we pass RFQ number as input?
Also how you populated the PR number into the field EKKO-SUBMI.
Thanks In advance,
Regards,
Prabu

Similar Messages

Populating the screen field when the cursor moves to that field

hi every one,
I want to populate the screen field(MODULE POOL) When the cursor moves to that field.
So can any one help me out with this.
EXAMPLE..
I want to populate 'S10_TOT_PRICE' (Total Price). When the fields like 'S10_PIECES' (Number of Pieces) will be entered. I want to populate 'S10_TOT_PRICE' without pressing any button on the screen nor when enter is hit. When the field 'S10_PIECES'' will be entered with some value and the cursor moves to 'S10_TOT_PRICE' . The Total Price field should be populated. Please help me out with this.
THANKS & REGARDS.
Mahanta.
POINTS WILL BE REWARDED.

Sorry but look at this SAP documentation <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/54/0608162d0711d295520000e8353423/frameset.htm">User Actions on Screens</a>
Extract :
<i>User Actions on Screens
There are various ways in which users can interact with screens.
Filling Input Fields
Users can enter values in any input field on the screen, or change the value using the mouse, in the case of radio buttons and checkboxes. The contents are placed in the corresponding screen field. Filling an input field does not normally trigger the PAI event. Exceptions to this are Checkboxes and Radio Buttons with Function Codes and input fields with Drop Down Boxes.</i>
So, i fear that you cannot "take hand" when user fill a numerical field to perform calculations and update the screen.
Regards

How to add fields in fp03 Extenal Collection agency screen

Hi All,
As per our requirement, I need to add a check box and a date field in FP03 transaction - Extenal collection agency screen. I couldn't find any screen exit,BADI. Any one know how to add these two fields on the screen and save the values in DFKKCOLL and DFKKCOLLH table.
Your answer is highly appreciated.

Hello,
I do not know the either user exit or BAdi for FP03. However I can suggest you a work around.
You can add an addl tabstrip in FPE2/FPE2M. This is possible by adding an addl field say 'ZZ' in tables DFKKOP/DFKKCOLL/DFKKCOLLH.
<also pls look into OSS Note 851023>
So when ever an item is submitted to collection agency, this field should be updated.
Hope this helps
Rgds
Rajendra

Screen field (MEPO1211-KONNR) not populated user exit ZXM06U43

Hi Expert,
I have to check Outline agreement (EKKO-KONNR) in the user exit ZXM06U43 when creating or changing PO. one screen field (MEPO1211-KONNR) is provided for that. But value is not populated into that field(MEPO1211-KONNR) for this user exit ZXM06U43, its always blank. Infact hole structure (MEPO1211) is blank for this exit.
So can anybody provide me the screen field name so I can get the value of KONNR in this exit.

Hi,
In the user exit - EXIT_SAPMM06E_012, YOU CAN ONLY DO CHECKS/VALIDATIONS;
you have a paramter I_BSTYP which hold the type of the document(PO/Out Agreement/PR).
Paramter I_EKKO will hold the data entered on the screen. It will be the incoming data which can be used to validate.
TO PASS THE DATA, CHECK the below exit:
EXIT_SAPMM06E_018 : Import Data from Customer Subscreen for Purchasing Document
EXIT_SAPMM06E_007/EXIT_SAPMM06E_006: Export Data to Customer Subscreen for Purchasing Document Header
Hope this helps
Regards
Shiva

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.

Screen Fields Not getting Updated with DYNP_VALUES_UPDATE

Hi All,
I am using FM DYNP_VALUES_READ to read the screen field values and then modifying those values and passing the modified table to DYNP_VALUES_UPDATE. But the problem is screen fields are not populated with these values . The values I wish to populate are footer values . I am using OO ALV for this wherein I am handling an event for filter of records and accordingly I need to modify my footer. Any Suggestions??
*&      Form footer
      Caslculate Total items, number of hits/Miss and percent MSP
--> p1        text
<-- p2        text
FORM footer .
CLEAR : io_totitems,
          io_tothit,
          io_totmiss,
          io_permiss.
IF NOT l_flag EQ 1.
Get total items
DESCRIBE TABLE i_outdata LINES io_totitems.
LOOP AT i_outdata INTO wa_outdata.
calculate number of hits
    IF wa_outdata-hit_miss = 'HIT'.
      io_tothit = io_tothit + 1.
    ENDIF.
calculate number of Miss
    IF wa_outdata-hit_miss = 'MISS'.
      io_totmiss = io_totmiss + 1.
    ENDIF.
    CLEAR wa_outdata.
ENDLOOP.
calculate percent MSP
io_permiss = ( ( io_totitems - io_totmiss ) / io_totitems ) * 100 .
IF l_flag EQ 1.
    wa_dynpread-fieldname = 'IO_TOTITEMS'.
    APPEND wa_dynpread TO t_dynpread.
    wa_dynpread-fieldname = 'IO_TOTHIT'.
    APPEND wa_dynpread TO t_dynpread.
    wa_dynpread-fieldname = 'IO_TOTMISS'.
    APPEND wa_dynpread TO t_dynpread.
    wa_dynpread-fieldname = 'IO_PERMISS'.
    APPEND wa_dynpread TO t_dynpread.
    CLEAR wa_dynpread.
    d020s-prog = sy-repid.
    d020s-dnum = sy-dynnr.
    CALL FUNCTION 'DYNP_VALUES_READ'
            EXPORTING
               dyname               = d020s-prog
               dynumb               = d020s-dnum
               translate_to_upper   = 'X'
          REQUEST              = ' '
            TABLES
               dynpfields           = t_dynpread.
    MOVE io_totitems TO io_totitem.
    CONDENSE io_totitem NO-GAPS.
    MOVE io_tothit TO io_tothits.
    CONDENSE io_tothits NO-GAPS.
    MOVE io_totmiss TO io_totmis.
    CONDENSE io_totmis NO-GAPS.
    MOVE io_permiss TO io_permis.
    CONDENSE io_permis NO-GAPS.
    LOOP AT t_dynpread INTO wa_dynpread.
      CASE: wa_dynpread-fieldname.
        WHEN 'IO_TOTITEMS'.
          wa_dynpread-fieldvalue = io_totitem .
          MODIFY t_dynpread FROM wa_dynpread.
        WHEN 'IO_TOTHIT'.
          wa_dynpread-fieldvalue = io_tothits.
          MODIFY t_dynpread FROM wa_dynpread.
        WHEN 'IO_TOTMISS'.
          wa_dynpread-fieldvalue = io_totmis.
          MODIFY t_dynpread FROM wa_dynpread.
        WHEN 'IO_PERMISS'.
          wa_dynpread-fieldvalue = io_permis .
          MODIFY t_dynpread FROM wa_dynpread.
      ENDCASE.
      CLEAR wa_dynpread.
    ENDLOOP.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = d020s-prog
        dynumb               = d020s-dnum
      TABLES
        dynpfields           = t_dynpread
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 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.
Get all fotter details in a internal table
this is used to download footer in Excel
wa_footer-fldname = 'Total Items '.
wa_footer-value = io_totitems.
APPEND wa_footer TO i_footer.
wa_footer-fldname = 'Number of HIT'.
wa_footer-value = io_tothit.
APPEND wa_footer TO i_footer.
wa_footer-fldname = 'Number of MISS'.
wa_footer-value = io_totmiss.
APPEND wa_footer TO i_footer.
wa_footer-fldname = 'Percentage MISS '.
wa_footer-value = io_permiss.
APPEND wa_footer TO i_footer.
CLEAR wa_footer.
ENDFORM.                    " footer

data: t_dynfields1 type table of dynpread with header line.
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
dyname = d020s-prog
dynumb = d020s-dnum
translate_to_upper = 'X'
REQUEST = ' '
TABLES
dynpfields = t_dynfields1.
<b>read table t_dynfields1 index 1</b> I hope this is missing
I will be selecting from a list .
Because once the value is read we need to update the screen field with that value .
Here the selected value will be in the first place
Now
Your operation is to populate the fields with some variables .
In the same when I do this there is only one value then
Im expecting only one entry here
LOOP AT t_dynpread INTO wa_dynpread.
CASE: wa_dynpread-fieldname.
WHEN 'IO_TOTITEMS'.
wa_dynpread-fieldvalue = io_totitem .
MODIFY t_dynpread FROM wa_dynpread.
WHEN 'IO_TOTHIT'.
wa_dynpread-fieldvalue = io_tothits.
MODIFY t_dynpread FROM wa_dynpread.
WHEN 'IO_TOTMISS'.
wa_dynpread-fieldvalue = io_totmis.
MODIFY t_dynpread FROM wa_dynpread.
WHEN 'IO_PERMISS'.
wa_dynpread-fieldvalue = io_permis .
MODIFY t_dynpread FROM wa_dynpread.
ENDCASE.
CLEAR wa_dynpread.
ENDLOOP. */
Comment this for a while and
Change the code as
t_dynfields1-fieldname = ' '. "<--- header name
t_dynfields1-fieldvalue = ' '."<----val
append t_dynfields1.
t_dynfields1-fieldname = ' '.
t_dynfields1-fieldvalue = ' '.
append t_dynfields1.
t_dynfields1-fieldname = ' '.
t_dynfields1-fieldvalue = ' '.
append t_dynfields1.
And check .
CALL FUNCTION 'DYNP_VALUES_UPDATE'
EXPORTING
dyname = d020s-prog
dynumb = d020s-dnum
TABLES
dynpfields = t_dynfields1.
regards,
vijay

Make Screen field non editable

Hi All,
We have following requirement in our project:
When entering infotype 1 in any action a check should be made to set default values in Work Contract. If Employee Group =u2019 1u2019, Work Contract u2018ZFu2019 should be set and this value must not be changed. If Employee Group u20181u2019 the Work Contract could be all other values except u2018ZFu2019.
We are using badi HRPAD00INFTY to handle the above requirement. But there is a problem. When we perform an action and go to infotype 1 screen the contract field is populated with correct value and is display only field. Once you press enter on the screen the field becomes an editable field and can be changed by the user. I debugged the program and found that PSYST-NSELC is set as NO (0) in the program MP000130 and is checked if it has a value YES in module p0001 called in PBO of screen 2000 include MP000120. If the value is YES only then BADI is called else not.
Can someone suggest what could be the problem area or any other way to meet the requirement ?
BR Jaideep,
Duplicate Post. Continue here: Screen field not getting editable..
Edited by: kishan P on Sep 9, 2010 2:20 PM

Can you explain how a physical inventory is done in your company., and what problems come up if a wrong date is entered?
In my company we create and print the inventory documents immediatly before counting, and we are making sure, that the volume can be counted, entered and difference posted on the same day.
Further we are setting a posting block in SAP, and of course we make sure that no physical movement happens during the count.
And of course we make sure that everyting what was received or issued prior to the count is already entered in sAP before we start creating the documents.
SAP takes the book inventory in the moment the counted quantity is entered in this case. No matter if the user enters a count date of today or of last week.
But if you close the field (which is not possible with customizing), then you have to make sure that you enter the count on the same day you have counted, because if you would enter the count on the next day, then your counting date would be wrong and you would not have a chance to enter the correct counting date.
And as SAP stores everything what a user enters, it is easy to identy the user who has fooled the system, and then the HR guy should do his job, especially as the physical inventory is in most countries a legal requirement, which has to be done seriously.
don't give authorization to the guys who dont follow your policies.

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

BDC-How to get the value of the screen field

Hi All,
I am facing a problem while writing the BDC code for the XK02 transaction.
Recording:
We have recorded like this :after giving the values in the initial screen(vendor no and purchase group and selecting the purchasing data check box) and enter into the second screen and then click on alternative data icon.There we ll have set of plants we have to check auto ordering (by selecting the plant and click purchasing icon)for the plants which are in the given file.
Problem:
Suppose there are five plants(like 1,2,3,4,5) for a particular vendor but we are having only three plants in the file for which auto ordering check has to be done.The problem is that its doing auto ordering check for the first three plants(1,2,3) in the transaction.But in the file we are having Plants like (1,3,5).How to get the screen field value directly or is there any other way to resolve the problem?

Dear Raja,
You cannot get hold of screen values while running through the BDC Operation.
Only way you can get the value --> populating an Internal Table from the Database Table.
Regards,
Abir
Don't forget to award Points *

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.

Module-pool screen field value under POV event

Hi All,
I have one issue...please suggest me solution for this.
In module-pool program i have one screen(1000) which has one field(hrname_1000).
Under this event:
PROCESS ON VALUE-REQUEST.
FIELD hrname_1000 MODULE hrname_1000.
under this module hename_1000 i have used F4IF_INT_TABLE_VALUE_REQUEST to put a search help for field hrname_1000.
after that i am trying to retrive HR related stuff's based on the field on module-pool i.e i am using hrname_1000 in the where condition.
but problem is that im not getting value for hrname_1000 which im giving in the module-pool screen.
thats y my select query is not working.
Where as im getting values for the hrname_1000 under PBO & PAI.
It will look like below.
PROCESS ON VALUE-REQUEST.
FIELD hrname_1000 MODULE hrname_1000.
(under the above module)
SELECT DISTINCT ename plans FROM pa0001 INTO CORRESPONDING FIELDS OF TABLE itab WHERE stell = '50001026'.
      LOOP AT itab INTO wa WHERE ename = hrname_1000.
      ENDLOOP.
Please suggest
Thanks & regards
Ansumesh

In some of the cases the screen field is present in the screen but not holding the value in the required structure or field.
so here u need to check the option of reading the screen field values explictly..
//once u hit an enter and do the f4 i think the value will be there ...but if u dont hit enter and do an F4 the value cannot hold and i think u r in this case ..
1.Fill the screen field name in the structure dynpread.
DATA: BEGIN OF DYNP_VALUES OCCURS 10.
        INCLUDE STRUCTURE DYNPREAD.
DATA: END   OF DYNP_VALUES.
DYNP_VALUES-FIELDNAME = 'HRNAME_1000'.
APPEND DYNP_VALUES.
* read screen values
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      DYNAME     = HELP_REPID "call the repid of ur prog
      DYNUMB     = HELP_DYNNR "pass the screen number
    TABLES
      DYNPFIELDS = DYNP_VALUES
    EXCEPTIONS
      OTHERS     = 1.
now dynp_values hold the field name and field value of the screen .
now
SORT DYNP_VALUES BY FIELDNAME.
    READ TABLE DYNP_VALUES WITH KEY 'HRNAME_1000' BINARY SEARCH.
    IF SY-SUBRC EQ 0.
      HELP_XXXX = DYNP_VALUES-FIELDVALUE. "store the value into a variable
      TRANSLATE HELP_XXXX TO UPPER CASE.
    ENDIF.
Now check the code with the value if its getting populated which once there will make ur select work ..
Vijay..

Read screen field in infotype 8

Hi all,
I am using exit Exit_SAPFP50M_002 for transaction PA30.In the include, i have to read the basic salary field (Q0008-betrg).
But, my problem is Q0008 is structure.How to read the screen field. That value does not exists in any table.
Please help.

I am using BAdi HRPAD00INFTY (before output) for defaulting some values of the HR infotypes such as Salary.I am accessing those values by using following code.
data : I0008 TYPE P0008.
CALL METHOD CL_HR_PNNNN_TYPE_CAST=>PRELP_TO_PNNNN
EXPORTING
PRELP = INNNN
IMPORTING
PNNNN = I0008.
all the values all populating in I0008 but when i change the value of bet01(I0008-bet01 = 123456.) , it is not displaying on screen.
any idea??
Thanks,
Prashant

How to populate 2 screen-fields with one [ON VALUE-REQUEST FOR input] evnt?

I have a selection screen with 2 text inputs - input1, input2.
For the first one I have an "AT SELECTION-SCREEN ON VALUE-REQUEST FOR input1" event.
I successfully get a value there and that is set to the screen field. But I also want input2 to be automatically populated with a value corresponding to the selected input1 (eg. input1=ID, input2=Name).
I'm able to set input2 ABAP variable but not the screen-element.
(I guess that ON VALUE-REQUEST doesn't fire any events for screen fields update, because if I press ENTER after using my search-help, then input2 is set with the right value)
How to solve the problem?

Hi Ramchander,
Actually I used FM F4IF_FIELD_VALUE_REQUEST which doesn't have mapping parameters.
But after your advice I looked through F4IF_INT_TABLE_VALUES_REQUEST and found that it's
DYNP_VALUES_UPDATE FM that solves my task.
Thanks!

Attaching search help to SCREEN FIELDS AND TABLE FIELDS

Hello experts,
Himanshu here.
Could you please explain how we can assign search Help to a screen field AND TABLE FIELDS in ABAP?
Please reply at the earliest,as we have some deliverables to be met
Thanks

Hi,
In the initial screen of the ABAP Dictionary, select object class Search help, enter the name of the search help and choose Create.
A dialog box appears in which you must select the type of search help.
Select Collective search help and choose .
The maintenance screen for collective search helps is displayed.
Enter an explanatory text in the field Short text.
You can for example find the search help at a later time using this short text.
In the Definition tab page enter the parameters of the collective search help.
Select the Imp flag if it is an import parameter. Select the Exp flag if it is an export parameter.
Define the types for the parameters of a collective search help by assigning a data element. Enter the name of the data element that describes the contents of the search help parameter in the Data element field.
You can assign the parameter a default value in the Default value field.
In exceptions it could be necessary to change the standard process defined by the search help. You can implement the deviation from the standard using a search help exit.
In this case enter the name of the search help exit in the corresponding field.
On the Included search helps tab page, define the search helps that you want to include in the collective search help.
You can include elementary search helps and collective search helps.
Use the Hide flag to control whether an included search help should appear in the dialog box for selecting the elementary search help. If the flag is set, the search help is not offered.
It makes sense to hide search help inclusions if one or more search paths in the standard system should not be used in a concrete R/3 System. Similarly, search help inclusions can also be already hidden in the standard system because they only can be used meaningfully in a few R/3 Systems. You have to cancel the flag in this case.
Position the cursor one after the other on each allocated search help and choose Parameter assignment.
In the next screen, enter the parameter names of the elementary search helps to which the corresponding parameters of the collective search help should be assigned in the field Reference parameter.
You can select the parameters contained in the included search help using the input help. Create a proposal for the assignment with Proposal.
Save your entries.
A dialog box appears in which you have to assign a development class to the search help.
Choose .
Result
The collective search help is activated. You can find information about the activation flow in the activation log, which you can display with Utilities ® Activation log. If errors occurred when the collective search help was activated, the activation log is automatically displayed.
Do not forget to link the search help to a screen field. The search help attachment is not part of the search help definition; it is part of the object definition to which the search help is attached.
regards,
veeresh.

Screen Field in VBO2

Hi,
Can anyone tell me from which table does the screen field KONPD-MPWRT is getting populated.

Hi Dude,
Check with this table /BEV1/RBWE trans table ..

Populating PR No in collective no screen field of ME41

Similar Messages

Maybe you are looking for