SAP ABAP IMG Activity SIMG_CFMENUNMO3ONB9 (Maintain Exclusions/Inclusions for Service Pairs)
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_CFMENUNMO3ONB9 Maintain Exclusions/Inclusions for Service Pairs  
Transaction Code S_KK4_74000420   IMG Activity: SIMG_CFMENUNMO3ONB9 
Created on 19990816    
Customizing Attributes SIMG_CFMENUNMO3ONB9   Maintain Exclusions/Inclusions for Service Pairs 
Customizing Activity SIMG_CFMENUNMO3ONB9   Maintain Exclusions/Inclusions for Service Pairs 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUNMO3ONB9    

In this IMG activity, you maintain exclusions and inclusions for service pairs.

Use

  • Rule Type

    The rule type determines whether an inclusion (R4) or an exclusion (R2) is concerned. The rule type also determines which check the system runs for the service pair in question.

  • The I indicator (service inclusion)

    The system automatically sets the I indicator for the standard SAP rule types.

  • In T field (message type)

    The specification you make in the T field determines how the system is to react to the corresponding rule violation. If you select the message type E, the system issues an error message when a rule is violated, and processing can only be resumed when the error has been eliminated.

  • Indicators Date(D), Quantity(Q) and Unidirectional (U)

    You can further tailor the inclusion and exclusion checks to meet your requirements using the indicators D, Q and U:

    • Exclusion checks (rule type R2)
      • You can set the D (date) indicator for service exclusion checks. If you do so, the system indicates a rule violation only if the two exclusion services overlap in time. For extended services, the date and time are taken into account for the check and for immediate services only the date is taken into account.
      This rule type supports service actions. This means that the system will try to correct any rule violations it encounters. In the case of rule R2, the system sets the service entered under Service 2 to "non-billable" and keeps the service entered under Service 1 as "billable".
    • Inclusion checks (rule type R4)
      • For inclusion checks, when the D (date) indicator is set, both inclusion services must exist on the same date. For extended services, the services must cover the same interval and immediate services must exist on the same day. If an inclusion consists of an extended and immediate service, the immediate service must occur within the interval of the extended service when the D indicator is set.
      By means of the Q (quantity) indicator, you can specify whether the system is also to compare the service quantities; in other words the second service should exist in at least the same quantity as the first service. If you set this indicator along with the D indicator, the system checks whether the same quantity of services exists on the same day.
      The U (unidirectional) indicator controls whether the system is to check service inclusions in both directions. Usually, a service inclusion where service 1 is S1 and service 2 is S2 means that the system checks whether service S2 exists when service S1 exists and also whether service S1 exists when service S2 exists. By setting the U indicator, you deactivate the second check.
      This rule type supports service actions. This means that the system will try to correct any rule violations it encounters. In the present case, this means that if the service entered under Service 2 is missing, the system attempts to create it. If the Quantity or Date indicator is set, the system tries to create the service with the missing quantity or for the corresponding date. If the U indicator is not set and the system determines that the service entered under Service 1 is missing, it does not attempt to create service 1. Instead it tries to cancel service 2 or to reduce the excess quantity.
      For more information about service actions, refer to the section entitled Maintain Check Procedure in this Implementation Guide.

Example

Field    Value

Inst.    1

RT    R4

SC    01

Svce    250

SC    01

Svce.    251

I    X

D    X

Q    X

U    X

T    E

Meaning:

The check Inclusion of billable services, by service pair (rule type R4) checks whether the service 251 from service catalog 01 exists when service 250 from service catalog 01 was entered. The system also checks whether service 251 exists in at least the same quantity as service 250 on the same day. If this is not the case, the system should issue a message of the type "E". A rule violation is not recorded if only service 251 exists.

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_CFMENUNMO3ONB9 NL Netherlands
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUNMO3ONB9 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
NLPA S - Table (with text table) ONB9 1 Define Service Rules for Service Pairs 
History
Last changed by/on SAP  19990816 
SAP Release Created in