SAP ABAP IMG Activity SIMG_CFMENUORKAOKOR (Define Selection Rules)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ KAUC (Package) Customizing R/3 Cost Accounting, Orders
IMG Activity
ID SIMG_CFMENUORKAOKOR Define Selection Rules  
Transaction Code S_ALR_87005285   IMG Activity: SIMG_CFMENUORKAOKOR 
Created on 19981222    
Customizing Attributes SIMG_CFMENUORKAOKOR   Define Selection Rules 
Customizing Activity SIMG_CFMENUORKAOKOR   Define Selection Rules 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUORKAOKOR    

This function allows you to create rules that you can use when selecting orders for collective order processing.

These rules are created using the validation / substitution functions available in the FI-SL System, and use boolean statements to specify the criteria by which orders are to be selected.

Example

You want to select all orders that were either created or last changed by user SMITH.

If you were to select by entering SMITH in both fields "Created by" and "Last changed by" in your selection variant, you would receive a list of only those orders that were both created and last changed by this user. However, you also want to see orders created by SMITH that have since been changed by someone else, and orders created by someone else but since changed by SMITH.

Using normal selection procedures, you need two processing steps to do this:

  1. First select all orders created by user SMITH.
  2. Restart the selection for all orders last changed by user SMITH.

Using Boolean logic, on the other hand, you can create a flexible selection rule to select exactly the orders you want to see in a single step, with no overlaps:

<AUFK> $ERNAM = 'SMITH' OR

<AUFK> $AENAM = 'SMITH'

Key:

  • <AUFK>

    This table contains the fields that can be used in the selection. For internal orders, you can create rules using the fields in the order master (table AUFK).

  • $ERNAM and $AENAM

    Technical names of the fields "Created by" and "Last changed by" respectively.

    When processing a rule, you can access a list of the field names by clicking on the "Flds in Bool.statement" pushbutton.

  • =

    Operator "Equal to".

  • 'SMITH'

    The value to be selected. Always put this value in single inverted commas.

  • OR

    Boolean operator for disjunction, used when at least one of the logical statements must be true for the entire statement to be true.

    For a list of Boolean operators, see the field documentation for "Boolean statement".

Recommendations

To improve performance, you should use the selection rules only for complex inquiries (such as, with OR operations), as they are performance intensive. You should perform selections with simple limitations for the value area through upper- and lower limits by entering the values in the section "Define selection variants".

Activities

  1. Enter the name of the selection rule you want to maintain:
    • If you are maintaining an existing selection rule, choose "Enter".
    • If you are creating a new selection rule, choose "Rule -> Create" and then "Enter".
  2. Enter a short description of your rule in the field provided.
  3. If you want to protect your rules from unauthorized display, changes or deletions, choose "Goto -> Header" and enter the desired authorization group.
  4. Enter the Boolean statements you require in the fields provided. You can call up a list of available fields using the function "Flds in Bool.statement".

    To include existing Boolean rules within your new rules, choose "Rule list".

  5. Assign the defined rules to a selection field as variable (see "Define selection variants".

For more information on the structure and syntax of the Boolean statements see the help for the "Boolean statement" field.

Notes on transport

You can transport selection rules manually. Choose "Rule -> Transport".

Further notes

For more information on writing Boolean statements, see the SAP Library under "Financial Accounting - Validations and Substitutions".

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUORKAOKOR 0 HLA0001399 O HLA0001475  
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
OKOR T - Individual transaction object OKOR 01 Boolean rules for internal orders 
History
Last changed by/on SAP  19981222 
SAP Release Created in