Restrict the field selection

Hi,
i would like to restrict the field selection upto 20 from left to right pane in the field choice popup.
when the user cliks on the push button in selction screen, pop up will come for field selection for sorting order. now user will have a facility to move the fields from left box to right box, where we have to restrict only 20. if it exceeds, need to pass a message.
Could some one help on this.
Regards
KER

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/840ad679-0601-0010-cd8e-9989fd650822#q-3

Similar Messages

Date picker - is there a way to restrict the minuit select list to 1/4 hr

Hi,
When using date picker item with format 'DD-MON-YYYY HH24:MI',
Is there a way to restrict the minuit select list on the calendar to 1/4 hr instead of 00 to 59. Example: 00,15,30,45
Thank you,
Francis

Hold down command key to select multiple songs, then "Get Info", and you will modify all fields at the same time.

How to restrict the fields in a std screen i.e addtional data b of va01

how to restrict the fields in a std screen i.e addtional data b of va01
certain document type
as i already added some fields in it
can u help me with the setp
With regards
rohan Shetty

Hi Rohan,
Can you please let us know the solution that you had, i have similar requirement?
Thanks,
Manohar.

How to change a value of the field Selection Conditions in Manage- Request

Hi,
How to change manualy a value of the field Selection Conditions in Manage infocube -> Requests ?

Hi,
Here is the reason i need to do this:
The data is loaded by DTP in process chain. Overlaping requests are deleted. But, iIn some cases requests with the same selection options need not to be deleted. My idea was to change selection options in Manage(infocube) with Abap program without changing selection options in DTP filter, so that the system would not recognize requests as "overlaping requests".
So, where is the information about shown in the field Selection Options is stored? In which tables?
Thanks
Tigr_Z

How to restrict the cell selection in JTable based on cell contents...

Hi all,
I have some problem related to table cell selection.
I have a table that represets the calendar of some month and year.
I have the restriction that at one time only one cell could be selected.
Now i want the cell seletion like this,
I want only those dates to be selected if that date is after 'today'.
that is I want to restrict the selection of previous dates.
how can i do this.
I have overridden the table methods like this, still no use.
table = new JTable(model) {
setOpaque(false);
setSurrendersFocusOnKeystroke(false);
setRowHeight(20);
JTableHeader header = getTableHeader();
header.setOpaque(false);
getTableHeader().setReorderingAllowed(false);
setSelectionMode(ListSelectionModel.SINGLE_SELECTION);
getTableHeader().setResizingAllowed(false);
setCellSelectionEnabled(true);
setFocusable(true);
setBackground(new Color(247, 251, 255));
setFont(newFont);
public boolean isCellEditable(int row, int col) {
return false;
public boolean isCellSelected(int row, int col) {
int r = getSelectedRow();
int c = getSelectedColumn();
String val = (String)getValueAt(r,c);
Calendar cal = Calendar.getInstance();
cal.set(currentYear+1900, month,Integer.parseInt(val));
Date d = cal.getTime();
Date currentDate = new Date();
if (d.before(currentDate)) {
     return false;
} else {
     return true;
Someone please help...
-Soni

Try overriding the changeSelection(....) method of JTable.
public void changeSelection(int row, int column, boolean toggle, boolean extend)
     if (d.after(currentDate)
          super.changeSelection(row, column, toggle, extend);
}

How to restrict the field in invoice documnet

Hi All,
We don't want to allow users to change the vendor at the time of creation of invoice.
we want to restict the filed invoice praty (under details tab) to display only.
Is it possible?
How to achieve it.
Thank you.

Hi,
For MIRO, SAP doesn't provide any field selection facility, this can be done by creating screen variants for MIRO in OLMRLIST
You can also use transaction SHD0 for creation of Screen variants of MIRO.

How to restrict the default selection of first row in ALV in Webdynpro

Hi Experts,
In webdynpro i used ALV to display the bulk amount of datas under a view container. While running it ll cme by default selection on first row. how to restrict that.....

Hi Vimal,
Whenever we create nodes then by default the Initialization lead selection property of node is always checked. That why in the alv by default the first row is selected.
To restrict this default selection just unchecked the Initialization lead selection property of your node.
Regard
Manoj Kumar

Restricting the Multiple Selection for the Standard PCH selection Screen.

Hi -
I want to Hide the Extension pushbutton for the OBJID in the PCH LDB Standard Selection Screen. How do I do that ??
Thanks,
Mullai

Hi,
In the screen layout, open the attributes for push button. there u find four columns of group.
Enter any text in that and write a query like this......
(if text eneterd is GR1).
Loop at screen.
if screen-group1 = 'GR1'.
screen-input = 0.
modify screen.
endif.
endloop.

How to restrict the record selection for PLPO table .

Hi,
Am selecting 'plnnr' and 'vornr' from PLPO table . For one Plnnr their are multiple Vornr including 0001 & 9999.
I want to select only those entries which have only Vornr 0001 & 9999.
Ex : 1) Plnnr - 5689
           Vornr - 0001,2536,8989,9999
       2) Plnnr - 8787
           vornr - 0001
       3) Plnnr - 5936
           vornr - 9999
       4) Plnnr - 2345
           vornr - 0001,9999
Here for this example i want to select only the entry with Plnnr = 2345 as it only contains 0001 & 9999.
Can any one let me know how to get this in a select query.
Your help is much appreciated.
Thanks in advance.
Ravi Kasnale.

Hi
Try with below code
RANGES:r_vornr FOR plpo-vornr.
TYPES:BEGIN OF ty_plpo,
plnnr TYPE plpo-plnnr,
vornr TYPE plpo-vornr,
END OF ty_plpo.
DATA:it_plpo_temp TYPE STANDARD TABLE OF ty_plpo.
DATA:it_plpo TYPE STANDARD TABLE OF ty_plpo.
DATA:it_plpo_temp1 TYPE STANDARD TABLE OF ty_plpo.
DATA:wa_plpo_temp1 TYPE ty_plpo.
DATA:v_line TYPE sy-tabix.
START-OF-SELECTION.
r_vornr-sign = 'I'.
r_vornr-option = 'EQ'.
r_vornr-low = '0000'.
CLEAR:r_vornr-high.
APPEND r_vornr.
r_vornr-sign = 'I'.
r_vornr-option = 'EQ'.
r_vornr-low = '9999'.
CLEAR:r_vornr-high.
APPEND r_vornr.
SELECT plnnr vornr FROM plpo INTO TABLE it_plpo_temp1 WHERE vornr IN r_vornr.
CLEAR:it_plpo[].
LOOP AT it_plpo_temp1 INTO wa_plpo_temp1.
    CLEAR:it_plpo_temp[].
    it_plpo_temp[] = it_plpo_temp1[].
    DELETE it_plpo_temp WHERE plnnr <> wa_plpo_temp1-plnnr.
    DESCRIBE TABLE it_plpo_temp LINES v_line.
    IF v_line EQ '2'.
      APPEND LINES OF it_plpo_temp TO it_plpo.
    ENDIF.
ENDLOOP.
SORT it_plpo BY plnnr.
DELETE ADJACENT DUPLICATES FROM it_plpo COMPARING plnnr.
Regards
Srilaxmi

Select options -restricting the operator value options.

Hi,
In selection screen for the select options or parameter declarations I need to restrict the operator options , like when they click for any select options it will give options to select = , #, <, <= , > , >=
all these options right.
I would like to restrict the user to select only > and >= while passing values.
Can anyone give me idea how I can approach this?
Thanks in advance.

Hi,
use this FM...
SELECT_OPTIONS_RESTRICT can be use to supress options available with a SELECT-OPTIONS on a selection screen.
jusy copy the code and execute it....It will give the exact output what u want.....
TYPE-POOLS sscr.
TABLES : marc.
*Define the object to be passed to the RESTRICTION parameter
DATA restrict TYPE sscr_restrict.
*Auxiliary objects for filling RESTRICT
DATA : optlist TYPE sscr_opt_list,
*** TYPE sscr_***.
*Defining the selection-screen
SELECT-OPTIONS : s_matnr FOR marc-matnr,
s_werks FOR marc-werks.
INITIALIZATION.
*Restricting the MATNR selection to only EQ and 'BT'.
optlist-name = 'OBJECTKEY1'.
optlist-options-eq = 'X'.
optlist-options-bt = 'X'.
APPEND optlist TO restrict-opt_list_tab.
***-kind = 'S'.
***-name = 'S_MATNR'.
***-sg_main = 'I'.
***-sg_addy = space.
***-op_main = 'OBJECTKEY1'.
APPEND *** TO restrict-***_tab.
*Restricting the WERKS selection to CP, GE, LT, NE.
optlist-name = 'OBJECTKEY2'.
optlist-options-cp = 'X'.
optlist-options-ge = 'X'.
optlist-options-lt = 'X'.
optlist-options-ne = 'X'.
APPEND optlist TO restrict-opt_list_tab.
***-kind = 'S'.
***-name = 'S_WERKS'.
***-sg_main = 'I'.
***-sg_addy = space.
***-op_main = 'OBJECTKEY2'.
APPEND *** TO restrict-***_tab.
CALL FUNCTION 'SELECT_OPTIONS_RESTRICT'
EXPORTING
restriction = restrict
EXCEPTIONS
too_late = 1
repeated = 2
selopt_without_options = 3
selopt_without_signs = 4
invalid_sign = 5
empty_option_list = 6
invalid_kind = 7
repeated_kind_a = 8
OTHERS = 9.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Regards
Kiran

ALV report using the field catalog

which is the quickest way to generate an ALV report using the field catalog merge. without needing to build the field catalog manually .
is it easier to create a structure and passe it in the field catalog merge . if yes can i have an example plzzzz

hI
Supports the creation of the field catalog for the ALV function modules
based either on a structure or table defined in the ABAP Data
Dictionary, or a program-internal table.
The program-internal table must either be in a TOP Include or its
Include must be specified explicitly in the interface.
The variant based on a program-internal table should only be used for
rapid prototyping since the following restrictions apply:
o Performance is affected since the code of the table definition must
always be read and interpreted at runtime.
o Dictionary references are only considered if the keywords LIKE or
INCLUDE STRUCTURE (not TYPE) are used.
If the field catalog contains more than 90 fields, the first 90 fields
are output in the list by default whereas the remaining fields are only
available in the field selection.
If the field catalog is passed with values, they are merged with the
'automatically' found information.
Below is an example ABAP program which will populate a simple internal table(it_ekpo) with data and
display it using the basic ALV grid functionality(including column total). The example details the main
sections of coding required to implement the ALV grid functionality:
                         Data declaration
                         Data retrieval
                         Build fieldcatalog
                         Build layout setup
*& Report ZDEMO_ALVGRID                                               *
*& Example of a simple ALV Grid Report                                 *
*& The basic requirement for this demo is to display a number of       *
*& fields from the EKKO table.                                         *
REPORT zdemo_alvgrid                 .
TABLES:     ekko.
type-pools: slis.                                 "ALV Declarations
*Data Declaration
TYPES: BEGIN OF t_ekko,
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
statu TYPE ekpo-statu,
aedat TYPE ekpo-aedat,
matnr TYPE ekpo-matnr,
menge TYPE ekpo-menge,
meins TYPE ekpo-meins,
netpr TYPE ekpo-netpr,
peinh TYPE ekpo-peinh,
END OF t_ekko.
DATA: it_ekko TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_ekko TYPE t_ekko.
*ALV data declarations
data: fieldcatalog type slis_t_fieldcat_alv with header line,
      gd_tab_group type slis_t_sp_group_alv,
      gd_layout    type slis_layout_alv,
      gd_repid     like sy-repid.
*Start-of-selection.
START-OF-SELECTION.
perform data_retrieval.
perform build_fieldcatalog.
perform build_layout.
perform display_alv_report.
*&      Form BUILD_FIELDCATALOG
*       Build Fieldcatalog for ALV Report
form build_fieldcatalog.
* There are a number of ways to create a fieldcat.
* For the purpose of this example i will build the fieldcatalog manualy
* by populating the internal table fields individually and then
* appending the rows. This method can be the most time consuming but can
* also allow you more control of the final product.
* Beware though, you need to ensure that all fields required are
* populated. When using some of functionality available via ALV, such as
* total. You may need to provide more information than if you were
* simply displaying the result
*               I.e. Field type may be required in-order for
*                    the 'TOTAL' function to work.
fieldcatalog-fieldname   = 'EBELN'.
fieldcatalog-seltext_m   = 'Purchase Order'.
fieldcatalog-col_pos     = 0.
fieldcatalog-outputlen   = 10.
fieldcatalog-emphasize   = 'X'.
fieldcatalog-key         = 'X'.
* fieldcatalog-do_sum      = 'X'.
* fieldcatalog-no_zero     = 'X'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'EBELP'.
fieldcatalog-seltext_m   = 'PO Item'.
fieldcatalog-col_pos     = 1.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'STATU'.
fieldcatalog-seltext_m   = 'Status'.
fieldcatalog-col_pos     = 2.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'AEDAT'.
fieldcatalog-seltext_m   = 'Item change date'.
fieldcatalog-col_pos     = 3.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'MATNR'.
fieldcatalog-seltext_m   = 'Material Number'.
fieldcatalog-col_pos     = 4.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'MENGE'.
fieldcatalog-seltext_m   = 'PO quantity'.
fieldcatalog-col_pos     = 5.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'MEINS'.
fieldcatalog-seltext_m   = 'Order Unit'.
fieldcatalog-col_pos     = 6.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'NETPR'.
fieldcatalog-seltext_m   = 'Net Price'.
fieldcatalog-col_pos     = 7.
fieldcatalog-outputlen   = 15.
fieldcatalog-do_sum      = 'X'.        "Display column total
fieldcatalog-datatype     = 'CURR'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'PEINH'.
fieldcatalog-seltext_m   = 'Price Unit'.
fieldcatalog-col_pos     = 8.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
endform.                    " BUILD_FIELDCATALOG
*&      Form BUILD_LAYOUT
*       Build layout for ALV grid report
form build_layout.
gd_layout-no_input          = 'X'.
gd_layout-colwidth_optimize = 'X'.
gd_layout-totals_text       = 'Totals'(201).
* gd_layout-totals_only        = 'X'.
* gd_layout-f2code            = 'DISP'. "Sets fcode for when double
*                                         "click(press f2)
* gd_layout-zebra             = 'X'.
* gd_layout-group_change_edit = 'X'.
* gd_layout-header_text       = 'helllllo'.
endform.                    " BUILD_LAYOUT
*&      Form DISPLAY_ALV_REPORT
*       Display report using ALV grid
form display_alv_report.
gd_repid = sy-repid.
call function 'REUSE_ALV_GRID_DISPLAY'
       exporting
            i_callback_program      = gd_repid
*            i_callback_top_of_page   = 'TOP-OF-PAGE' "see FORM
*            i_callback_user_command = 'USER_COMMAND'
*            i_grid_title           = outtext
            is_layout               = gd_layout
            it_fieldcat             = fieldcatalog[]
*            it_special_groups       = gd_tabgroup
*            IT_EVENTS                = GT_XEVENTS
            i_save                  = 'X'
*            is_variant              = z_template
       tables
            t_outtab                = it_ekko
       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.                    " DISPLAY_ALV_REPORT
*&      Form DATA_RETRIEVAL
*       Retrieve data form EKPO table and populate itab it_ekko
form data_retrieval.
select ebeln ebelp statu aedat matnr menge meins netpr peinh
up to 10 rows
from ekpo
into table it_ekko.
endform.                    " DATA_RETRIEVAL

Restrict the payments according to Doc types while F110 PAYMENT RUN

dears
While doing F110 (Automatic payment run) we want restrict the payment as - the sytem should pick only a particular document type (WE type) sitting as open item or a particular document type for a particular vendor sitting as as open item?
For example KR DOC types only need to pick for a vendor code "XXXXX"
For this what setting is required at FBZP (Automatic payment ment Programme settng) and / or at any other area like XK02 (vendor master data) ?

Hello,
You dont need to make any changes in FBZP or vendor master.In F110, in the "Free selection" tab, in the Field selection do F4, choose Document type & in the values field give the Document type you want to include in the Proposal.
In the next line you can again choose the Field name as "Document type" with exclude tick, you can give the document type you dont require.
Save the proposal & run the payment run.
Hope this helps.
Regards,
WNR

FIELD SELECTION KEY

Hi,
       I have a query regarding Field Selection Key.
I want to know the difference between Field Selection Keys AKTH, ME21, and ME21N.
I have observed during Testing that, AKTH and ME21N are almost the same.
But, I like to know the difference.
Which is to be used when?
Please give suitable suggestions in this regard.
Thanks in advance.
Thanks & Regards,
Srinivasa M.S
+91-9910077829

Hi,
Go through following information.
Field selection key: -
You should not delete the field selection keys listed below, which the dialog program uses for control purposes, otherwise the dialog may terminate during processing:
1. Field selection key: transaction
The field selection key that corresponds to the transaction code: for example, field selection key ME22 for the transaction "Change Purchase Order". For the Enjoy Purchase Order transactions (creating, changing, displaying), there is only field selection key ME21N.
2. Field selection key: activity type
Is set from the activity type as follows:
AKTH    In creation mode
AKTV    In change mode
AKTA    In display mode
AKTE    With PO extension
You should note that you can also add items in change mode (for example, transaction ME22). Field selection key AKTH would be used for this item.
3. Field selection key: purchasing document type
The field selection key that you have assigned to the document type for the purchasing document. For example, field selection key UBF is assigned to document type UB, which is used for stock transfer orders (within a company code). In this key, the fields Price and Price unit are suppressed.
4. Field selection key: item category/document category
This is determined from the item and document categories as follows: The first two characters consist of the letters 'PT', the third character of the item category (internal representation), and the fourth of the document category:
A   for RFQs,
B   for purchase requisitions
F   for purchase orders
K   for contracts
L   for scheduling agreements
Accordingly, field selection key PT3F would be used for a subcontracting item in a purchase order.
Field selection key: function authorization/release status
Purchasing documents: Used for authorization control. If the user parameter EFB (function authorizations in Purchasing) has been assigned and a field selection key has been assigned to the relevant value, this field selection key is used. Otherwise, field selection key $$$$ is used if the user has insufficient authorization to display prices.
Purchase requisitions: If the purchase requisition is subject to a release strategy and a field selection key has been assigned to the current release indicator, this field selection key is used.
Field selection key: subitem/creation indicator
Purchasing documents: Is only used in the case of subitems. The field selection key is put together in the same way as for the item categories (field selection key 4), with the string 'UP', the subitem category, and the document type.
Purchase requisitions: the field selection key that is derived from the creation indicator in the purchase requisition, that is, ESTV, ESTF, or ESTD, is used in the case of purchase requisitions generated from within Sales and Distribution, from a production order, or through direct procurement.
5. Field selection key: purchase requisition
In addition to the available field selection keys, you can define a field selection key at function authorization level to influence the input characteristics of fields in the Enjoy Purchase Requisition.
You can use this field selection key to set up groups of users that have certain restrictions when editing purchase requisitions.
SAP Recommendation: -
SAP recommends that you accept the settings defined in the standard system. In this case, no action is required on your part.

Can any one know how do restrict that fields in mm

hi gurus
can any one know how do we restrict the fields in the material master. Where do we control do any one know the transaction code for that.
Thanks in advance

OMSR
and
OMS9
Help for OMSR
Assign Fields to Field Selection Groups
To define whether a field is hidden or displayed, or whether an entry is mandatory or optional in material master maintenance, you must assign the field to a field selection group. You may assign a field to one field selection group only.
Before including customer-defined fields in a field selection group together with standard fields, or assigning standard fields to a different field selection group, familiarize yourself with the assignment of fields to field selection groups in the standard R/3 System.
Standard settings
The values of the field selection groups have been preassigned as follows:
001-110 Material master for industry
111-120 Reserved for customers (except where the values are already in use)
121-150 Material master for industry
151-210 Material master for retail
211-240 Reserved for customers
Recommendation
If possible, use the setting in the standard R/3 System. No further action is then required. If you want to make individual fields inaccessible, the easiest way is to group them together in a single field selection group and to set it to Display or Hide.
Activities
1. Check the setting in the standard R/3 System.
For this, you need to know the data screen on which the relevant field appears in the material master, and the name of the screen field, for example, MARA-MEINS in the case of the base unit of measure.
2. If necessary, change the assignment of fields to field selection groups as required.
Further notes
In the case of long texts, you define whether the entire screen is hidden or displayed, or whether entries are mandatory or optional. For this reason, each screen has been assigned to one of the following dummy fields:
LTEXT_BEST Purchase order text
LTEXT_GRUN Basic data text
LTEXT_IVER Internal comment
LTEXT_PRUE Inspection text
LTEXT_VERT Sales text
help for OMS9
Maintain Field Selection for Data Screens
In this IMG activity, you create and maintain field references. You can see where a field reference is used by choosing Where-used list.
Activities
Define or change the field references as required (except for field references with the prefix SAP which must not be changed). New field references must begin with Y or Z.
Changing the Field Selection Options for a Field Selection Group
1. Specify the field selection group.
2. Select the field selection option (hide, display, required entry, or optional entry) for each field reference as required.
3. Save your data.
Creating a Field Reference
1. Choose New entries.
2. Specify a field reference beginning with Y or Z.
3. Select the field selection option for each field selection group as required.
4. Save your data.
Changing a Field Reference
1. Double-click the relevant field reference.
2. Change the field selection option for each field selection group as required.
3. Save your data.
reward if usefull
Message was edited by:
Umakant Bhangale

Restricting the Visibility of FireFighter Roles to selcted users

Dear Experts,
Is there any way to restrict the visibiilty of FireFigher roles in GRC CUP to only few authorized users. we have a requirement where a group of authorized users should be able to check out fire fighter roles on their own and these roles should be provisioned automatically to these users and then de-provision those roels after some time. These rolese should not be visible to the rest of the users.
Any throughts on this would be greatly appreciated.
Thanks
Kumar

Kumar,
There is no straightforward or right way to do this as this feature is not available in CUP.
You can associate those users with a functional area and restrict the role selection by functional area. Also, associate the roles with the same functional area. Again, this is not going to force users unless you bring functional area from the data source like LDAP and keep the field non-editable.
Regards,
Alpesh

Restrict the field selection

Similar Messages

Maybe you are looking for