Screen field access.

Hi,
We have created a screen field for a custom screen and used the T002-SPRAS name from the dictionary. But when tried to acces through program callin this screen, it throws a syntax error.
How to access the screen field ?
Rgd,
stc

Hi,
Did you check your top include. Make sure that you are including the required table in top include where all global variables are declared.
You can do like this.
TABLES: T002.
Thanks.
Nitesh

Similar Messages

How to access screen field value in a module pool programming?

Hi Experts,
   I have create a module pool program SAPMYDLG. It contains two screens 100 and 200.
   The first screen contains Employee_ID field. This field is not a dictionary field.
   In the second screen 200, I want to access the value of Employee_ID field from first screen.
   For this I created a global variable v_empid in TOP include.
   Then in the PAI of the screen 100 I have assigned the screen field value to global variable.
   v_empid = Employee_ID.
   But this gives an error saying " Field Employee_ID not defined".
   What am I doing wrong? How can I access the screen field value?
Thanks
Gopal

Hi,
Employee_ID field also must u define in the top include when u define that 100 screen and 200 screen will access.
regards,
muralii

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

I can't unlock the screen to access my macbook pro. When I enter the password it just jiggles. I'm not getting an error message, so I'm pretty certain that the password is correct. Any suggestions?

I can't unlock the screen to access my macbook pro. When I enter the password it just jiggles. I'm not getting an error message, so I'm pretty certain that the password is correct. Any suggestions?

I already checked that one.
I'm baffled, especially since it will usually give you the Invalid user name or password entered message. I'm not getting that. Instead the password field just jiggles back and forth. Very odd.

Fetch screen fields Line item wise

Hi All,
I have a requirement where i've to display some popup messages based on some conditions in MIGO transaction when POST button is clicked.
For that i have done certain changes in a BAdI IF_EX_MB_MIGO_BADI~POST_DOCUMENT .
But i require to read the screen field for G/L account ie GOITEM-KONTO of screen number 0345.
the G/L account can be accessed thru internal table IT_MSEG-SAKTO in the method, but the problem is the screen field has been left blank and when POST is clicked, by the time this BAdi is reached, the value is filled. And i need to add few codes only when the screen field has been left blank.
I found out FM - DYNP_VALUES_READ . But this reads only header screen data, so i'm unable to retrieve the line item wise G/L account screen values.
Please help.
Thanks,
Ateet

Hi Petr,
I dont think u read the question properly.
The problem is the screen field has been left blank and when POST is clicked, by the time that BAdi is reached, the value is filled. And requirement is to execute some part of code only when the screen field for G/L account is left blank/not blank. I want screen field value , not the value which is in IT_MSEG.
While giving inputs in MIGO screen it is blank but by the time it reaches the BAdI where i've written the code its getting filled. I want the values from screen just before it gets filled.
I was hoping to find some FM like DYNP_VALUES_READ which fetches screen elements line item wise too.
I think i will have to try n search a different BAdI where i can get the screen values b4 updation.
Regards,
Ateet

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

Problem in Screen field position ( Module pool )

Hi Experts,
We changed the screen field position ( GUI ) of SAP standard module pool program. we had taken the access key from SAP and modified the layout.
Our Problem : We had transported these change request to Quality and Pre Production. The changes are transferred correctly in Quality . when coming to Pre Production the changes are not visible on the screen.
Checks Performed : 1. We had analyzed the Transport request - They are imported correctly.
2. We had rechecked the layout that we had changed its good and correct.
Can you experts help me out in identify the exact solution for this problem.
- Best Regards,
Sudhakar Puppala
Edited by: CRM Sudhakar on Sep 16, 2010 11:25 AM

Hi, no idea can be given without having a look..
but just check the screen layout in the pre-production itself..instead checking transport..

Greyed out screen field in transaction but modifiable by batch input

Hi Gurus,
I have a requirement where a custom screen field in a transaction (FK01/FK02/XK01/XK02) has to be greyed out when a user access these transactions. However, these fields will have to be modifiable when LSMW/batch input is being done.
I hope someone can advise how I can do this.
I'll definitely reward points for helpful answers.
Thanks so much.
Rgds,
Joyie

Declare on your layout input is 0. Or the field cannot be filled by value.
After you have done that, create some code like this:
Loop at screen.
     IF sy-batch is not initial or sy-binpt is not initial.
            if screen-group1 = 'ANL'
               screen-input = '1'.
            endif.
        endif.
endloop.
Hope it helps solve your problem.

Screen Fields - HR

Hi ,
I need to access the screen field Q0235-EXMPT,But this field is not in PA0235.
Is there any way to get data from the same.
Plz guide me reg this.
Albert.

Hello,
The field you are looking for is from structure.
Please check any function module exists for the same.
Also please do a search for Q0235-exmpt in program
MP023500 this will give you an idea how they have arrived with the result for the particular field
Thanks,
Krishnakumar
Message was edited by: Krishnakumar

Disable IT0001 screen fields through PA40

Hi experts,
When I am running an action through PA40, after updating IT0000 it calls IT0001 after that 9001 and so on. For It0001 fields like position, employee subgroup, Org. Key and administrator fields are editable.
I want to disable all other It0001 screen fields except adminstrator fields for that particular action type. Please help me out how to solve this issue. I have tried to insert the code in user exit (PADU02) but i don't find any means to access the screen of IT0001.
Full reward points guaranteed for better solution
thanks and regards,
Murali

Hi Murali,
      I am sure did you check T588M (Infotype Screen Control), where you can set your own settings for the infotypes (fields, hide, disable, Required)
   However I got confoused with your requirement, you want the screen to be changed only for that action, does that means if he go to 0001 through PA30 user should have access to all the fields?
   -- In that case, you can set the feature P0001 and can use RPCADD00 program. (RPCADD00 might give a chance of accessing 0001 infotype - Not sure)
Regards
Mahesh

Hide or Show the Dialog Screen Field in a SAP Transaction

Hi All,
I am working on a SAP Upgrade Project (4.6C to ECC 5.0). In VA03 Transaction, There is a Filed Name VBAK-KTEXT with Field Text as Description appears in 4.6C. But it does not appear in ECC 5.0. I checked the screen Layout in 4.6C as well as ECC 5.0 and noticed that VBAK-KTEXT is available in the Layout of ECC 5.0 but does not appear in the Transaction VA03.
I was told that there is a way in Customization to Hide or Show a Screen Field for any Transaction. Can any one please guide me through this? I need this help as soon as possible.
Thanks,
Kannan.SA

Hi,
I am not sure if there's a tcode using which you can configure all the screens the only tool I know that can do this is GUIXT. Regarding the configuration some of the fields are configurable based on document types you should check with SD functional person regarding this. Unfortunately I don't have R/3 access right now, but you can look under SPRO in SD and look for document type.
thanks

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

Screen field access.

Similar Messages

Maybe you are looking for