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_CFMENUNMOGPR12 | Create Condition Tables |
| Transaction Code | S_KK4_74000091 | IMG Activity: SIMG_CFMENUNMOGPR12 |
| Created on | 19990816 | |
| Customizing Attributes | SIMG_CFMENUNMOGPR12 | Create Condition Tables |
| Customizing Activity | SIMG_CFMENUNMOGPR12 | Create Condition Tables |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUNMOGPR12 |
In this IMG activity, you define condition tables. These tables are used to define influencing factors for price dependencies, in other words, to specify for which combinations of fields condition records can be created in order to define prices or price elements (e.g. surcharges, discounts).
The IS-H System uses the "condition technique" from the Sales and Distribution (SD) component. This technique is also used within many components of the SAP System.
This technique is used for pricing in the IS-H System. Here specific influencing factors in the form of IS-H specific fields (e.g. case-related fields or performed service fields) are used.
When creating a condition table, you have to decide whether or not you want to use condition records with a validity period.
Standard Settings
The following predefined condition tables for billing (Germany only) are delivered in the standard IS-H System:
- 400 for condition records for external physician discount
- 401 for condition records for chief physician discount
SAP Recommendation
- You should neither delete nor change the predefined condition tables.
- In most cases, it is recommended to define condition tables with a validity period.
- The above mentioned condition tables are, in general, no longer relevant for billing pursuant to BPflV95 in Germany.
- For more often than not, condition tables should be defined with restricted validity.
- IS-H fields can be identified by the first three letters of the field's technical name (LS>ISH).
Activities
- Define the name of the condition table by entering a three-digit number of the customer number range.
- Select the fields (influencing factors) your require.
- Generate the condition table.
For more information about maintaining condition tables, refer to the Sales and Distribution Implementation Guide.
Note
Condition tables are cross-client.
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_CFMENUNMOGPR12 | 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 |
| ONBE | T - Individual transaction object | ONBE | 0000000001 | IS-H: Create Condition Table |
History
| Last changed by/on | SAP | 19990816 |
| SAP Release Created in |
