Select-options pattern

Hi Experts,
i'm new to abap.
on selection screen there is a select-option for field city of LFA1 table.
the user wants that all city starting with (A* or a) till (H or h*) should be displayed.
how should i go about it.
plz help.

Hello Annie,
This link gives all the possible patterns:
http://help.sap.com/saphelp_46c/helpdata/en/34/8e72da6df74873e10000009b38f9b8/frameset.htm
In particular:
Example
TABLES SBOOK.
SELECT-OPTIONS FL_DATE FOR SBOOK-FLDATE.
INITIALIZATION.
MOVE: 'I' TO FL_DATE-SIGN,
'EQ' TO FL_DATE-OPTION,
<b>SY-DATUM TO FL_DATE-LOW.</b>
APPEND FL_DATE.
MOVE: 'BT' TO FL_DATE-OPTION,
<b>'19960101' TO FL_DATE-LOW,
'19960630' TO FL_DATE-HIGH.</b>
APPEND FL_DATE.
When the selection screen is displayed, FL_DATE already contains the selection by the single value SY-DATUM (current date) and the interval from January 1 to June 30, 1996.
Regards,
Beejal
**Reward if this helps

Similar Messages

Issue about Select-options in NWG

Hi Techies,
Greetings of the day.
I can able to get the data using Filter in the URI but when i want to use select-options as parameters in the URI it is giving me error.
kindly help me on this issue how to write select-options to get the data
Thanks In Advance.
Thanks & regards
Sathish

Hi Sathish,
Your question doesn't make a lot of sense. Filters are converted into select option format in the DPC, you can't "use select-options as parameters in the URI". The URI has to be OData-compliant and select-options are nothing to do with OData.
You should be using a filter and interpreting the select options in the DPC. Be aware that not all select-options patterns are converted from filters.
Regards
Ron.

Select-options ...as search pattern

Is this construct available in 46B? The help file mentions it but it never syntax checks. Would anyone be able to post some code of it? I wish to assign a specific sarch help to my select option (an elementary search help as part of a collective one defined at data element level).
Thanks
Ian

Hi,
See this link
http://www.sapdevelopment.co.uk/dictionary/shelp/shelp_basic.htm
http://www.sapdevelopment.co.uk/dictionary/shelp/shelp_imp.htm
http://www.sapdevelopment.co.uk/reporting/selscr/selscr_restrictso.htm
http://www.sapdevelopment.co.uk/dictionary/shelp/shelphome.htm
http://www.sapdevelopment.co.uk/dictionary/shelp/shelp_exit.htm

Checking against Select-Options with "CP" using "IF value IN select_option"

Dear experts,
first of all: I'm sorry, if this question already should have been asked and answered!
I tried quite a lot of search terms but didn't find anything helpful.
We are using a statement like "IF value IN select_option" to perform comparisons after the Select-Options have been used in a SELECT statement. This logical expression fails (compared to the results of the DB-SELECT) whenever a select-option line contains the option CP (Contains Pattern). To be more specific: The case sensitivity of the LOW value doesn't seem to play a role any more. A variable with the value 'ABCD' would be positively checked against a select-option with OPTION 'CP' and LOW 'abc*', whereas this value wouldn't have been selected if the select-option had been used in a DB-SELECT.
Does anybody know a workaround?
Thanks in advance
Andreas

Dear Keshav,
it's an own field in an own table, defined as CHAR of length 140 (lowercase allowed), reflecting to a line of remittance info of an account statement. A regular Select-Option for this field is provided in a report which works perfectly fine regarding the case sensitivity. For reasons I don't want to point out in detail we need to check a value in this field against the select-option without selecting it from the db again.
Let's assume that a field remittance_info contains the value 'ABCD'.
A line of the select-option table looks like this:
select_option_table-SIGN = 'I'
select_option_table-OPTION = 'CP'
select_option_table-LOW = 'abc*'.
Then an ABAP statement such as
IF remittance_info IN select_option_table.
* would be true !!!
ENDIF.
but wouldn't deliver a result in a SELECT such as
SELECT * FROM my_table INTO TABLE my_internal_table WHERE remittance_info IN select_option_table.
because of the differences in lower/upper case.
regards
Andreas

How to change the valueswhich are entered in select-options

Hi ,
Iam passing Material Numner Vlaues through select-options.
My requirement is i need to prefix and postfix star to the Material.
For that i have written logic like below.
LOOP AT S_MATNR.
S_MATNR-SIGN = 'I'.
S_MATNR-OPTION = 'EQ'.
CONCATINATE '' S_MATNR-LOW '' INTO S_OBJKY-LOW.
APPEND S_OBJKY.
ENDLOOP.
What my problem is if user enters high low and high values how we can write the logic.

>
vinay raj wrote:
> What my problem is if user enters high low and high values how we can write the logic.
Hello Vinay,
I suppose you want to prefix & postfix a '*' to allow for selecting data using patterns.
Unfortunately you cannot use CP (read: patterns) if the HIGH value is not initial. read SAP documentation on SELECT-OPTIONS.
BR,
Suhas

Mix of Parameters & Select Options in a Selection screen in WD4A

Hi All.
I just created my first selection screen in WD4A couple of days back.
Now, we have to mix up some parameters and select-options just like in normal ABAP.
But I could only find a way to insert a "Range" into the WD4A screens via "Create_Range_table".
Supposing I have 2 select-options, then 2 parameters - i.e. no Pattern or range or intervals options (simple = option); then again 2 select-options.
Can't we make a simple Parameter option in WD4A selection screen? I know we can make no_extension and no_intervals as true so that it does look like a parameter. But still user can enter a pattern search in it like a select-option.
Hope my query is clear.
Another question is : As far as I understood, we ALWAYS need a IT_RESULT table in the method ADD_SELECTION_FIELD. Then why is it not mandatory in the method?
Thanks in adv.

Hi Aishi,
In an early version of SelectOptions, the parameter it_result was mandatory. Some time later, a developer contacted me and showed me an example where it was benefitial to first create the field and to pass in the range table at a later point in his algorithm. This can be done by calling set_range_table_of_sel_field( ). Hence, the parameter has become optional. Of course, a range table needs to be specified before the page gets rendered.
Best regards,
Thomas

Select option in web ui

Hi all expert,
May you know within GUi, we can define select option.With the select option, we can do choose EQ BT NE and not between.
Is there any possibility make the same select option in web UI ?
Thanks in advance
best regards

Hello Edward,
this will help you to select which select options you want to have per attribute:
1) Launch transaction 'sm34'
2) Enter view cluster name as 'CRMVC_DQ' and click on 'Maintain'
3) Find DQuery Object Name for example 'BTQOpp' under Comp Name 'BT' and click on'exceptions per attribute.'
4) Find the Attribute Name for example 'PROSPECT_NAME'
5) Check the boxes you need for example CP for "contain pattern"
Good luck.
Kind regards
Manfred

Select-option in module pool with table Control

HI,
How to use the select-option in Module Pool and how Can i use the Table control in it.
Can any body give me some Clues.
with rgds
Ranjith

Hi ..
PBO.
LOOP at <table contriol>
module --- Inside the module
DATA: g_uti TYPE REF TO cl_fobu_input_util.
if rollname <> space.
     CREATE OBJECT g_uti
       EXPORTING typename =rollname.
*....convert to external pattern
     CALL METHOD g_util->output_convert
       EXPORTING
         field_value_int = p_value                 " This is Tablecontrol-low
       IMPORTING
         field_value_ext = p_value.              " Retrun value for Low
ENDLOOP.
lly you have code in PAI
DATA: g_util_1 TYPE REF TO cl_fobu_input_util.
if rollname <> space.
     CREATE OBJECT g_util_1
       EXPORTING typename = rollname.
*....convert to internal pattern
     CALL METHOD g_util_1->input_convert
       EXPORTING
         field_value_ext   = p_value
       IMPORTING
         field_value_int_c = p_value.
The above code should be written for tablecontrol-high aswell..
you can also refer: Inlcude LSE16NF10 line no 341 & 434 (SE16n)
Nag

Selection option for variable entry in BEx in 2004s

Hi All,
Have any of you noticed that the selection option functionality for variable entry while creating a variable does not allow wild card entry,Even though you create the variable with selection option as input.
In 3.5 we had option the option "contains the pattern " but in 2004s its not available in the variable entry screen.

Hello Guys,
When I posted this thread we were upgrading to SP11, now I am in the middle of another upgrade (SP15) and I still notice that wild card option is yet to be made available for a variable of type selection option.
Back then I had sent a message to SAP and was told that the functionality would be rolled out in new SP's. I am very curious as too how others are handling this problem, as they are bound to be reports for which such variables are a must.
P.S - The option has been made available
Edited by: Karthik on Jul 22, 2008 6:52 PM

SELECT with pattern CP '50*' is not working on material numbers MATNR

Hello,
I have a specific matchcode for searching on material numbers with a function module as selection method.
In this function module, the SELECT clause is built dynamically as bellow.
      SELECT (temp3)
        INTO CORRESPONDING FIELDS OF TABLE result_tab UP TO CALLCONTROL-MAXRECORDS ROWS
         FROM (temp)
         WHERE (temp2) .
In the "temp2" variable, I use RANGES for the selection simply built with values of SELECT-OPTIONS coming from the search help selection screen.
I am facing the following problem :
When a search is executed on material number with the following pattern '50*' --> nothing is found !
When I run a search on '50575' --> the material number is found !
I expect it is a problem of convertion routines (external to internal format) but I am not able to fix a solution...
We are in SAP_BASIS 700.

I think it can be done.
I have -
CONCATENATE 'Z+_'   '00+' INTO r_ranges-low .
    r_ranges-sign = 'I'.
    r_ranges-option = 'CP'.
    APPEND r_ranges.
    SELECT ar_object FROM toasp
      INTO CORRESPONDING FIELDS OF table lt_toasp
       WHERE ar_object IN r_ranges.
And it returns all values with pattern 'Z_00'.
(Z1_001, Z1_002 etc.)
If the pattern '50*' is not working, you could try using '50+++'.
Regards,
MaryM

Case Sensitive problem in Select Option for wild card search

Hi,
Can anyone please let me know how to make the wild card search in any select-option non case-sensitive. What I mean by this is for eg. we want to find out all the POs with short text containing the word 'process', what we do we populate a range with OPTION = 'CP' and LOW = 'process' and select EKPO with short text in this range. This select is however case-sensitive and POs with short text containing 'Process' is not retrieved. But my requirement is that this should be non case-sensitive and both the POs should be in the result set.

Hi,
Hope this helps you
CS:
You can select characters in operand2 for a direct comparison by adding the escape symbol "#" before the required characters. For these characters, upper/lower case is taken into account, wildcard characters and the escape symbol itself do not receive special treatment, and trailing blanks in operands of type c are not cut off.
Covers Pattern: True, if the content of operand1 fits the pattern in operand2. Wildcard characters can be used for forming the operand pattern, where "" represents any character string, and "+" represents any character. Upper/lower case is not taken into account. If the comparison is true, sy-fdpos contains the offset of operand2 in operand1, whereby leading wildcard characters "" in operand2 are ignored if operand2 also contains other characters. If the comparison is false, sy-fdpos contains the length of operand1.
Regards
Krishna

How to prevent the use of wild cards in select-option

Hello experts,
Is it possible to prevent the use of wild cards in a select-option? If yes, how is it done please?
I have a
SELECT-OPTIONS: o_comp FOR dbtab-field OBLIGATORY DEFAULT 'FI'.
and, I want to prevent the users for giving in some thing like FI* with the wildcard bc it would lead to dump.
I want an error message to display and prevent the users for making such entry.
Please I need your help and I would be very grateful.
Thanks
Nadin

You have to use SELECT_OPTIONS_RESTRICT to restrict input allowed. Call this FM in INITIALIZATION or SELECTION-SCREEN OUPUT sections.
Sample :
TYPE-POOLS: sscr.
INITIALIZATION.
* Restrict SELECT-OPTIONS
PERFORM restrict_select.
FORM restrict_select.
DATA: restrict TYPE sscr_restrict,
        opt_list TYPE sscr_opt_list,
        *** TYPE sscr_***.
* Défine select-options modes (aka option list)
* - ALL standard - all options allowed
CLEAR opt_list.
MOVE 'ALL' TO opt_list-name.
MOVE 'X' TO: opt_list-options-bt,
               opt_list-options-cp,
               opt_list-options-eq,
               opt_list-options-ge,
               opt_list-options-gt,
               opt_list-options-le,
               opt_list-options-lt,
               opt_list-options-nb,
               opt_list-options-ne,
               opt_list-options-np.
APPEND opt_list TO restrict-opt_list_tab.
* - EQU only equality allowed (list of values)
CLEAR opt_list.
MOVE 'EQU' TO opt_list-name.
MOVE 'X' TO opt_list-options-eq.
APPEND opt_list TO restrict-opt_list_tab.
* Affect modes to parameters or block of parameters
* ALL by default
CLEAR ***.
MOVE: 'A'          TO ***-kind,
        '*'          TO ***-sg_main,
        'ALL'        TO ***-op_main.
APPEND *** TO restrict-***_tab.
* EQU to internal material number
CLEAR ***.
MOVE: 'S'          TO ***-kind,
        'S-MATNR'    TO ***-name,
        'I'          TO ***-sg_main, " no exclusion
        'EQU'        TO ***-op_main. " only value list
APPEND *** TO restrict-***_tab.
* Call FM
CALL FUNCTION 'SELECT_OPTIONS_RESTRICT'
       EXPORTING
            restriction = restrict
       EXCEPTIONS
            OTHERS      = 1.
ENDFORM.                    " restrict_select
In the sample, only select-options for matnr is restricted to single value list.
For your request build a mode with all options except "pattern" ones : CP and NP.
Regards

Fill select-options in Page with flow logic ???

Hello All,
          I created a BSP Application using Page with Flow Logic.
In the first page of my Application I'm using 2 input fields as select-options.
Now I'm populating a Ranges of that Field using the type :-
selopttab
I populated the ranges table like :-
wa_bname_sel-sign   = 'I'.
          wa_bname_sel-option = 'BT'.
          wa_bname_sel-low    = '*'.
          wa_bname_sel-high   = 'Z'.
        ELSE.
          wa_bname_sel-sign   = 'I'.
          wa_bname_sel-option = 'EQ'.
          wa_bname_sel-low    = p_bname.
          wa_bname_sel-high   = p_bname.
        ENDIF.
        APPEND wa_bname_sel TO p_bname_sel.
        CLEAR wa_bname_sel.
But the problem is I checked the corresponding DATABASE Table entries by passing thesame value .
i.e I passed the low and high values to the field as '*' and 'Z'.
The total number of entries differ when passing '*' and 'Z' to when passing SPACE.
I tried even with contains Pattern .This time the total number of records fetching has Increased but the sum is not exact when passed SPACE to the Database Table.
So what should I pass to the Low and High values of my Ranges Table to get all the entries ????
DOes this type of building the Ranges work in BSP's ?
How are u people working out for the select-options functionality in Page with flow logic ?
Message was edited by:
        deepu k

Hello Jessy,
To populate select-options or Ranges in Page with flow logic I used the following code :
************************ Bulid the Select-Options**************************************
      DATA: p_bname_sel     TYPE STANDARD TABLE OF selopttab,
            p_bsp_name_sel TYPE STANDARD TABLE OF selopttab,
            p_tcode_sel     TYPE STANDARD TABLE OF selopttab.
      DATA: wa_bname_sel    TYPE selopttab,
            wa_bsp_name_sel TYPE selopttab,
            wa_tcode_sel    TYPE selopttab.
* Select-Options for Username
      REFRESH p_bname_sel.
      CLEAR   wa_bname_sel.
      IF ( p_bname IS INITIAL ).
        wa_bname_sel-sign   = 'I'.
        wa_bname_sel-option = 'CP'.
        wa_bname_sel-low    = '*'.
        wa_bname_sel-high   = ''.
      ELSE.
        wa_bname_sel-sign   = 'I'.
        wa_bname_sel-option = 'EQ'.
        wa_bname_sel-low    = p_bname. " p_bname is the Input field and the value is taken from it
        wa_bname_sel-high   = p_bname.
      ENDIF.
      APPEND wa_bname_sel TO p_bname_sel.
      CLEAR wa_bname_sel.
* Select-Options for BSP_Application
      REFRESH p_bsp_name_sel.
      CLEAR   wa_bsp_name_sel.
      IF ( p_bsp_name IS INITIAL ).
        wa_bsp_name_sel-sign   = 'I'.
        wa_bsp_name_sel-option = 'CP'.
        wa_bsp_name_sel-low    = '*'.
        wa_bsp_name_sel-high   = ''.
      ELSE.
        wa_bsp_name_sel-sign   = 'I'.
        wa_bsp_name_sel-option = 'EQ'.
        wa_bsp_name_sel-low    = p_bsp_name.       " Input field
        wa_bsp_name_sel-high   = p_bsp_name.
      ENDIF.
      APPEND wa_bsp_name_sel TO p_bsp_name_sel.
      CLEAR wa_bsp_name_sel.
* Select-Options for TCODE
      REFRESH p_tcode_sel.
      CLEAR   wa_bsp_name_sel.
      IF ( p_tcode IS INITIAL ).
        wa_tcode_sel-sign   = 'I'.
        wa_tcode_sel-option = 'CP'.
        wa_tcode_sel-low    = '*'.
        wa_tcode_sel-high   = ''.
      ELSE.
        wa_tcode_sel-sign   = 'I'.
        wa_tcode_sel-option = 'EQ'.
        wa_tcode_sel-low    = p_tcode.       " Input field
        wa_tcode_sel-high   = p_tcode.
      ENDIF.
      APPEND wa_tcode_sel TO p_tcode_sel.
      CLEAR wa_tcode_sel.
* Select all the related entries when either BSP or TCode is choosen
      IF ( ( p_bsp_name IS NOT INITIAL ) AND ( p_tcode IS INITIAL ) )
                 OR
         ( ( p_bsp_name IS INITIAL ) AND ( p_tcode IS INITIAL ) ).
        REFRESH gt_final.
        SELECT bname
               bsp_name
               description
               ldate
               ltime
               calls
               FROM <custom_table>
               INTO TABLE gt_final
               AND   bsp_name IN p_bsp_name_sel
               AND   ldate          IN p_ldate_sel.
endif.
Hope that wud help u !!!
Regards,
Deepu.K

Generating HANA where clause for select options having CP as the operator

Hi All
I am trying to generate where clause in HANA sql from the select options range table .
I tried using the function modules RSDS_RANGE_TO_WHERE and RH_DYNAMIC_WHERE_BUILD .
They are working for most of the cases . But , when the range table has entries like
Fieldname   sign opt low high
VBELN        I/E    CP *4*
Both of them fail to generate the right result .
Could you suggest any other function modules , which take care of all such cases like include single values , exclude single values , incluse and excluse ranges , patterns etc .
Thanks and Best Regards
Varsha

Hi Karthik,
this is the api, I have done,
create or replace
FUNCTION get_where_clause_for_emp_req (
   emp_id       IN   NUMBER,
   salary            IN   NUMBER,
   job         IN   VARCHAR2,
   dept IN NUMBER
   RETURN VARCHAR2
IS
   l_where_clause   VARCHAR2 (2000);
BEGIN
   IF (    (emp_id IS NULL)
       AND (salary IS NULL)
       AND (job IS NULL)
       AND (deptIS NULL)
   THEN
      RETURN NULL;
   ELSE
      l_where_clause := 'WHERE ';
   END IF;
   IF (emp_id IS NOT NULL)
   THEN
      l_where_clause :=
                    l_where_clause || ' emp_id =' || emp_id || '';
   END IF;
   IF ((emp_id IS NOT NULL) AND (salary IS NOT NULL))
   THEN
      l_where_clause :=
                      l_where_clause || ' AND salary= ' || salary;
   ELSIF (salary IS NOT NULL)
   THEN
      l_where_clause := l_where_clause || ' salary= ' || salary;
   END IF;
   IF (((salary IS NOT NULL) AND (dept IS NOT NULL)) OR ((emp_id IS NOT NULL) AND (salary IS NULL) AND (dept IS NOT NULL)))
   THEN
      l_where_clause := l_where_clause || ' AND dept= ' || dept;
   ELSIF (status_i IS NOT NULL)
   THEN
      l_where_clause := l_where_clause || ' dept= ' || dept;
   END IF;
l_where_clause := l_where_clause || ' ;';
   RETURN l_where_clause;
END;I have done for three parameters, i need to include two more input parameters for this function, so I see going forward my testing cases will increases,
so am looking for the best solution
Thanks
Edited by: NSK2KSN on Jul 7, 2010 3:11 PM

Restricting Select Options to Multiple Single Entries

Hi All,
       I have a requirement where we have two select options. I need to restrict only One of the select options to only accept multiple single entries. I have tried using the 'SELECT_OPTIONS_RESTRICT' Function module. But it provided little help to me.
Please check the below code.
gv_w_opt_list-name = 'A'.
gv_w_opt_list-options-eq = 'X'.
APPEND gv_w_opt_list TO gv_w_res-opt_list_tab.
gv_w_***-kind = 'A'.
gv_w_***-name = 'YTRADE_DESC'.
gv_w_***-sg_main = '*'.
gv_w_***-sg_addy = 'N'.
gv_w_***-op_main = 'A'.
APPEND gv_w_*** TO gv_w_res-***_tab.
It allows to restrict intervals for select-options in selection screen
    CALL FUNCTION 'SELECT_OPTIONS_RESTRICT'
      EXPORTING
        program                = sy-repid
        restriction            = gv_w_res
      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.
Please help me if you have any information related to this requirement. Relevant anwers will be surely rewarded.
Regards
Nagaraj

I have a code sample I use in a report. Result is only EQ and no intervals and no excludes
LOAD-OF-PROGRAM.
    Subscreen: Select Options for delivery                                    *
SELECTION-SCREEN BEGIN OF SCREEN 1100 AS SUBSCREEN
                                      NO INTERVALS.
SELECT-OPTIONS:
so_dlvno FOR /scwm/s_aspq_tu-docno
                                 MODIF ID dlv .
SELECTION-SCREEN END OF SCREEN 1100.
    Subscreen: Select Options Restrictions                                  *
Include type pool SSCR
TYPE-POOLS sscr.
Define the object to be passed to the RESTRICTION parameter
DATA restrict TYPE sscr_restrict.
Auxiliary objects for filling RESTRICT
DATA t_opt_list TYPE sscr_opt_list.
DATA ***      TYPE sscr_***.
CLEAR ***.
***-kind    = 'S'.        "Apply only to the named SELECT-OPTION
***-name    = 'SO_DLVNO'. "This is name of the SELECT-OPTION
***-sg_main = 'I'.        "I = ONLY Inclusions; * = Both
***-op_main = 'NOINTERVALS'. "This must match opt_list-name
APPEND *** TO restrict-***_tab.
Create t_opt_list entry to specify capabilities of S_BUKRS.
CLEAR t_opt_list.
t_opt_list-name       = 'NOINTERVALS'."This must match ***_tab-op_main
t_opt_list-options-bt = space.     "Do not permit BETWEEN
t_opt_list-options-cp = space.     "Do not permit MATCHES-PATTERN
t_opt_list-options-eq = 'X'.       "       Permit EQUALS
t_opt_list-options-ge = space.     "Do not permit GREATER-OR-EQUAL
t_opt_list-options-gt = space.     "Do not permit GREATER-THAN
t_opt_list-options-le = space.     "Do not permit LESS-OR-EQUAL
t_opt_list-options-lt = space.     "Do not permit LESS-THAN
t_opt_list-options-nb = space.     "Do not permit NOT-BETWEEN
t_opt_list-options-ne = space.     "Do not permit NOT-EQUAL
t_opt_list-options-np = space.     "Do not permit NO-PATTERN-MATCH
APPEND t_opt_list TO restrict-opt_list_tab.
Call function module
CALL FUNCTION 'SELECT_OPTIONS_RESTRICT'
    EXPORTING
      restriction                = restrict
    EXCEPTIONS
      too_late                   = 1
      repeated                   = 2
      not_during_submit          = 3
      db_call_after_report_call = 4
      selopt_without_options     = 5
      selopt_without_signs       = 6
      invalid_sign               = 7
      report_call_after_db_error = 8
      empty_option_list          = 9
      invalid_kind               = 10
      repeated_kind_a            = 11
      OTHERS                     = 12.
Exception handling
IF sy-subrc NE 0.
ENDIF.
Edited by: Suhel Awad on Feb 1, 2011 3:06 PM

Select-options pattern

Similar Messages

Maybe you are looking for