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_CFMENUNMOGONA6 | Define Usage of Condition Types (Direct Pat. Billing, etc.) |
| Transaction Code | S_KK4_74000101 | IMG Activity: SIMG_CFMENUNMOGONA6 |
| Created on | 19990816 | |
| Customizing Attributes | SIMG_CFMENUNMOGONA6 | Define Usage of Condition Types (Direct Pat. Billing, etc.) |
| Customizing Activity | SIMG_CFMENUNMOGONA6 | Define Usage of Condition Types (Direct Pat. Billing, etc.) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUNMOGONA6 |
In this IMG activity, you further qualify the use of the condition types you have defined for the IS-H System. For example, if direct patient billing is used within your healthcare facility, you can specify which of the condition types are intended for determining material costs or administrative costs.
You enter the condition types in the Customizing table, specify for what they are used and, if necessary, which rule type is to be accessed in service catalog column determination.
You can differentiate different kinds of condition types:
- Condition types that determine the basic price (for each case billed for, only one condition type should be used), for example GP00.
- Condition types that determine surcharges and discounts on the basis of a condition table with an access sequence, in order to specify the percentage surcharge for administrative costs, for example.
- Condition types that access a specific (additional) column of the service catalog for a surcharge or discount. This would also require you to maintain service catalog column determination
These conditions can also be "statistical" conditions. In other words, the value of a "statistical" condition is calculated while the bill is being created and is saved in the system. However, it does not affect the invoiced amount. This can be useful, if, when billing takes place, certain amounts are to be calculated which, although relevant within the organization of your hospital (e.g. costs to be refunded to hospital by physician) are of no relevance to the invoice recipient.
Requirements
You need to have created the relevant condition types beforehand.
Activities
Enter all condition types for which you want to further qualify the usage. You may also have to specify the condition type(s) which determine(s) the basic price.
Maintain the usage (Usg.) and - if an additional column is to be determined - the rule type (RT). The rule type points to service catalog column determination rules.
You can list the usage values supported by the system by calling the value help for the Usg field.
Subsequent Activities
Now maintain service catalog column determination for the specified rule type, if the system is to access columns of a service catalog.
Include the condition types in the relevant pricing procedure. If a condition type is to access a value in the service catalog columns, enter the value 501 in the AltCBV field.
Further notes
You can output the values calculated using special evaluations (RNAPRV00, RNAPRV01, RNABG000)
Direct patient billing or German workers' compensation association billing are but examples of how you can use this table. You can, of course, make entries in this table for condition types for which you want use a similar logic to determine the value of an alternative column when carrying out a different type of billing. In this case, enter 10 as the usage.
If you do not specify the usage of a basic price condition type correctly, this can result in the system calculating the wrong field for the basic price of an invoice item when billing is carried out. Although this does not usually result in the amount of the invoice item being calculated incorrectly, it can affect the invoice printout, if the value is to be output on a corresponding form. The value is also used program-internally in certain evaluations for determining the quantity for price-related insurance verification. For this reason, after making the corresponding changes in this configuration table, check whether the Service Basic Price field (technical name VBRP-ISHGPRS) is determined correctly.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | E | Invalid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| SIMG_CFMENUNMOGONA6 | NL | Netherlands |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUNMOGONA6 | 0 | I010004225 | Billing |
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 |
| TN21P | S - Table (with text table) | ONA6 | 1 | Condition Types for Direct Patient Billing |
History
| Last changed by/on | SAP | 19990816 |
| SAP Release Created in |
