Hierarchy
IS-H (Software Component) SAP Healthcare⤷
IS-H (Application Component) SAP Healthcare - Industry-Specific Components for Hospitals⤷
NEO1 (Package) IS-H: External Order
IMG Activity
| ID | ISH_EO_BILLTYP_DET | Determine Billing Types |
| Transaction Code | S_P7C_98000304 | (empty) |
| Created on | 20070711 | |
| Customizing Attributes | ISH_EO_BILLTYP_DET | Determine Billing Types |
| Customizing Activity | ISH_EO_BILLTYP_DET | Determine Billing Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISH_EO_BILLTYP_DET |
Use
In this IMG activity you can stipulate which billing type is to be used for a special service for the external order.
You can use the following criteria:
- Institution
- Order Type
- Performing Organizational Unit
- Service Catalog
- Service
- Service Category
You can also use masking (* entry) for certain criteria.
At billing, the system uses these values to determines the billing type for each individual service.
Requirements
Standard settings
Activities
You make an entry for billing type determination by specifying
- Institution
- Order Type (for example, 'O'= medical opinion, can be masked using '*' )
- Performing OU (for example, SURG1 = surgery 1, can be masked using '*' )
- Service Catalog (can be masked using '*' )
- Service (can be masked using '*' )
- Service Category (can be masked using '*' )
- Billing Type to be used.
Example
Inst. O Perf.OU SC Service SvceCtgry BT
1000 * SURG1 * * * EO
The above example stipulates that for the institution 1000 and the performing OU SURG1, the system is to use the billing type EO to bill for any service or service category.
Further notes
- The specification of certain criteria is optional and you can make masked specifications using an asterisk (*). Partly generic masking (for example 'SURG*' in the Perf.OU field) is not allowed.
- The possibility to use masking means that you have to define a specific sequence in which the system is to access the rules. Before maintaining the rules, see the access steps for rule interpretation.
Access Steps
More specific rules take priority over more general rules. For example, an entry for a service takes priority over a specification at service category level.
Thus the entries in the table that # starting from the left # do not have an * apply.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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 | ISH_EO_BILLTYP_DET | 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 |
| V_TVKV | V - View | OVKI | 3 | Define Document Pricing Procedure | ||
| V_TN21 | V - View | NT50 | 4 | Define Billing Types | ||
| TNEO_BILLTYP_DET | S - Table (with text table) | SM30 | Determine Billing Types |
History
| Last changed by/on | SAP | 20070711 |
| SAP Release Created in |
