SAP ABAP IMG Activity SIMG_CFMENUNMO3ON80 (Determine Billing Types)
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_CFMENUNMO3ON80 Determine Billing Types  
Transaction Code S_KK4_74000113   IMG Activity: SIMG_CFMENUNMO3ON80 
Created on 19990816    
Customizing Attributes SIMG_CFMENUNMO3ON80   Determine Billing Types 
Customizing Activity SIMG_CFMENUNMO3ON80   Determine Billing Types 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUNMO3ON80    

In this IMG activity, you specify on an institution basis which billing type is to be used for the services to be billed for in relation to a case. You can define the following criteria (in some cases using the wildcard character *):

When billing is carried out, the system determines the billing type for each individual service on the basis of the values specified for the service here (e.g. performing organizational unit).

Example

Inst CT Ins.Prov. IPT Bill.OU MT Bill.Type
1 2 * * * WT WT

The above example specifies that, for outpatient cases, service charges incurred for visits of visit type WT (workers' compensation association - treatment) are to be billed for using the billing type WT.

This rule applies independently of the

  • Insurance provider
  • Insurance provider type
  • Organizational unit

Requirements

You have to have already defined the criteria used here, for example:

  • Insurance provider type
  • Billing type

Standard settings

Recommendation

For outpatient billing, a specific visit type frequently corresponds to a specific billing type. For the sake of clarity, it is therefore recommended to use the same keys for the respective visit type and billing type.

Activities

You make an entry for the determination of billing types by specifying:

  • The Institution
  • The Case type (e.g. 1 = inpatient case)
  • The Insurance provider or alternatively Insurance provider type (you can use the wildcard character * in both fields)
  • The Self-Payer indicator (in this case you must leave the Insurance Provider field empty and enter an asterisk (*) in the Insurance Provider Type field
  • The Organizational Unit (use of wildcard character * possible)
  • The Movement Type (use of wildcard character * possible)
  • The Billing Type to be used.

Further notes

  • The specification of a number of criteria is facultative and can take the form of the wildcard character *. Generic specifications, however, (e.g. CHIR* in the Organizational Unit field) are not allowed.
  • You can make an entry either in the Insurance Provider field or in the Insurance Provider Type field. You cannot make entries in both fields. Enter an asterisk (*) in the field in which you have not made a specific entry. For self-payer rules, you can flag the Self-Payer checkbox on the detail screen. In this case, the Insurance Provider field should remain empty, and you must enter an asterisk (*) in the Insurance Provider Type field.
  • The Billing OU field specifies the organizational unit that performs the service.
  • The Movement Type field specifies:
    • The admission type for inpatient and day patient cases
    • The visit type for outpatient cases.
      • If a service was entered for a specific visit, enter the corresponding visit type here. Otherwise, enter the visit type of the first visit. Note: compare the effect of the parameter with the technical name AMB_BESF in Maintain Client-Specific, Institution-Independent Parameters.
  • The billing type can also be used when invoices are printed to determine different invoice forms. If, when a case is billed for, services with different billing types exist, several invoices are then created.
  • Since it is possible to work with generic entries, you have to stipulate a specific sequence in which the system is to access the billing type determination table. Before maintaining these rules, refer to these access steps for the interpretation of the rules.
  • By implementing the enhancement NBTYPE00, it is possible to replace the determination of billing types described here by a customer-specific determination procedure.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   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_CFMENUNMO3ON80 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
TN21A S - Table (with text table) ON80 1 Define Determination of Billing Type 
History
Last changed by/on SAP  19990816 
SAP Release Created in