SAP ABAP IMG Activity SIMG_CFMENUNMO3ONL5 (Define Rule Types and Maintain Check Procedure)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       NBAS (Package) Appl. development Hospital System master data, catalogs
IMG Activity
ID SIMG_CFMENUNMO3ONL5 Define Rule Types and Maintain Check Procedure  
Transaction Code S_KK4_74000414   IMG Activity: SIMG_CFMENUNMO3ONL5 
Created on 19990816    
Customizing Attributes SIMG_CFMENUNMO3ONL5   Maintain Check Procedure 
Customizing Activity SIMG_CFMENUNMO3ONL5   Maintain Check Procedure 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUNMO3ONL5    

Use

In this IMG activity, you carry out the following actions:

  • Maintain Service Rule Types and Check Procedure

    Here you can display an overview of the rule types in the standard SAP system and define your own rule types.

  • Display Check Procedure Overview

    Here you can display an overview of the existing settings.

Rule Types

Service rule types denote all processes that influence services. This can be, for example, the manual entry of services, the adjustment of nursing charges on the basis of the inpatient movements of a case, or even a highest value rule.

Rule types are used in two different contexts:

  • Firstly, any program that calls one of the BAPIs (Business Application Programming Interfaces) for processing performed services must pass a rule type to the service BAPI. Ideally the rule type corresponds to the purpose the program serves. For example, if you write a program that uses BAPIs to transfer services from a subsystem into the IS-H system, you should create a rule type that is specially reserved for this (for example, ZSUB001: "Transfer Services from Sub 001"), and specify this program in the BAPI calls.
  • The rule types are also used for the service rule check procedure. In this case, they characterize the service rules. They are used to analyze the services entered for a case with regard to specific criteria, to report inconsistencies, or to have the system automatically correct inconsistencies.

Activities

Maintain Service Rule Types and Check Procedure

At the uppermost level you are given an overview of the rule types in the standard SAP ssytem, and you can also define new rule types of your own. To do this, specify the rule type and a descriptive short text.

If you want to use the new rule type in the service rule check procedure, you must also specify a function module that runs the check. If the rule type supports service actions, you must also set the A indicator.

Service actions involve the system correcting any errors detected by the check. For information on the requirements to be satisfied by the function modules for service rules, see the end of this section.

Use Billing Catalog indicator: This indicator enables the rules of this rule type to work with the billing-revelant services and billing catalogs. This function is only available when the component ACM (SAP Ambulatory Care Management) is active.

Note

Note that many of the checks in the standard SAP system only verify services that are neither canceled nor planned. Moreover, the checks only consider services that are flagged as billable.

Use

The use of a rule type stipulates the purpose for which the rule type can be brought into play (see above). To display the uses of a rule type, select the required rule type, and then choose the Use level. If you process your own rule types, specify the uses to which these may be put here.

Callup Points

The following settings are only relevant if you wish to process a rule type that can be used for the service rule check procedure.

Service checks cannot be performed whenever you like. They can take place only when specific events or "callup points" occur.

To display the permitted callup points for a rule type, select the required rule type from the uppermost level, and then choose the Callup Points level. For the rule types in the standard SAP shipment, you see the callup points at which this check can be executed and whether actions are supported or not at the various callup points.

If you want to add new rule types to the check procedure, here you should specify the callup points at which you want the check to be performed. Keep in mind, however, that it is not useful to execute every check at every callup point (for example, if all of the information required for the check is not available).

Set the service action indicator A if you want service actions to be supported at this callup point.

Check Procedure

From a particular callup point, you can now create the check procedure. Here you specify for each institution whether the current check is actually to be performed at this callup point. In addition, you can store the following information for each check in your check procedure:

  • You can enter a function module if a function module other than the function module specified for the rule type is to be executed at this point in time. If you create new entries, you can leave the field for the function module name blank. In such cases, the system automatically uses the function module specified in the definition of this rule type when you press ENTER.
  • You can activate or deactivate each of the checks in the check procedure. The system only performs active checks. You activate a check by selecting A.
  • Specify a validity period for each check.
  • You can specify that the system is to abort the entire check procedure if a check generates an error message (message type E). To do this, flag Abort.
  • You can specify for which case types or case categories a check should be performed (for example, inpatient), and for which case types it should not be performed.
  • If a check supports actions, and these actions can be carried out by the system at this point in time, you can activate the actions for this check in the Service Actions group box. The following options are available to you as regards the performance of actions:
    • No Actions: Set this indicator if you do not want the system to automatically modify or generate services.
    • Before carrying out actions, the system usually displays a dialog box for you to confirm the actions to be performed. In this processing mode, the service actions are not processed in the background. If you require this variant, you have to set the Actions w. Confirmation indicator.
    • If you also require processing in the background, you have to set the Actions with Confirmation and in BI indicator.
    • If you set the Actions w/o Confirmation indicator, the system does not display the dialog box containing the actions for this rule type, and these actions are performed without user interaction, but not in the background.
    • By setting the Actions w/o Confirmation and in BI indicator you specify that the corresponding service actions should also be carried out in the background.
  • Setting Authoriz. Check specifies that the authorization checks for the authorization objects N_NLEI_ERB, N_NLEI_ANF and N_NLEI_ANP (authorization objects for service entry by particular organizational units) are to be carried out when services are created or modified by actions.
  • If several checks are active for a callup point, you can specify the sequence in which they are to be executed by entering a priority for each of them in the Rank field.
  • Use Billing Catalog. If the rule type permits the use of the billing-relevant services and the billing catalog for the check, you can set this indicator in the check procedure. Before they are passed to the rule module, the services are replaced by the billing-relevant services. These services must have been determined beforehand. The field is only displayed if SAP ACM (Ambulatory Care Management) is active.
  • Authorization check for the services in ACM. If the indicator is set, the system performs an authorization check for the authorization objects N_NLEI_ERB, N_NLEI_ANF, N_NLEI_ANP with the activity "Display" before passing the services to the rule module. Services for which no authorization exists, are not passed to the module. This indicator is only available if SAP ACM (SAP Ambulatory Care Management) is active.

Display Check Procedure Overview

In the second step of this IMG activity, you can display an overview of the settings made. The available selection criteria let you restrict the overview to particular data. Since you cannot see at a glance all of the active checks for an event in order to specify a particular sequence for the checks when actually maintaining the check procedure, you can specify this rank in the No. field in the overview list.

To enable you to locate errors in the check procedure more quickly, the function modules entered here that are different to the function modules of the definition of the corresponding rule type, are highlighted in color.

Caution
You have to make additional Customizing settings for particular rule types. For example, you must maintain the various service pairs for the rule type R2 (Exclude Billable Services by Pairs). Failure to do this can lead to errors during the service ch

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency E   Invalid for countries specified 
Customizing Attributes Country Key Country Name
SIMG_CFMENUNMO3ONL5 AT Austria
SIMG_CFMENUNMO3ONL5 NL Netherlands
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUNMO3ONL5 0 I010004204 Patient Accounting 
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
C_TNT3 C - View cluster SM34 1 Maintain Service Rule Types and Check Procedure 
V_TNRS2 V - View ONLA 0000000000 Display Check Procedure Overview 
History
Last changed by/on SAP  20020412 
SAP Release Created in