Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NPAS (Package) Application development patient accounting system
IMG Activity
| ID | BADI: ISH_PROC_CHECK | BAdI: Check and if Necessary Change Procedure Data |
| Transaction Code | S_KK4_96000663 | (empty) |
| Created on | 20021001 | |
| Customizing Attributes | BADI: ISH_PROC_CHECK | BAdI: Check and if Necessary Change Procedure Data |
| Customizing Activity | BADI: ISH_PROC_CHECK | BAdI: Check and if Necessary Change Procedure Data |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISH_PROCEDURE_CHECK |
Use
This Business Add-In (BAdI) enables you to check and, if necessary, correct the values of a procedure and send an error message to the calling program via an error table.
You can modify the following fields in case-related procedure entry and in DRG data maintenance:
- Procedure code (ICPM)
- Start date
- Start time
- End date
- End time
- Departmental organizational unit
- Nursing organizational unit
- Main code indicator (country version Germany only: §301, statistics)
- Surgery type
- DRG category (principal or secondary procedure)
- DRG entry sequence (sequence number for DRG coding and grouping system)
- Number of additional surgeries
- Localization of a procedure
- Identification key from an external system
- Comment (if a SAPscript text does not yet exist)
Not all of the above named fields can be modified in surgical data maintenance, since these fields have to come from the current surgery movement. You may only modify the following fields:
- End time
- Main code indicator
- Surgery type
- DRG category
- DRG entry sequence
- Number of additional surgeries
- Localization of a procedure
- Identification key from an external system
- Comment (if a SAPscript text does not yet exist)
To check the data, the current case data, the current movement and all movements that exist for the case are passed to the method.
The passed transaction code and the indicator designating whether the user selected a movement from the case list or simply the case are used to run special checks here.
If parameter I_NBEW_SELECT has the value 'X', the movement that is passed to the method in parameter I_NBEW_ACT was explicitly selected from the case list by the user.
Requirements
The billing status of the case or the Customizing settings determine whether procedures can be changed. Your Customizing settings stipulate whether procedures can be changed when the case has billing status "final billed" or "provisional billed".
If in Customizing for IS-H you set the message type for message "298", function NICP, application area N3 to E in the message control table, this BAdI is not called for final billed or provisional billed cases.
For further information, see the documentation for the method.
Standard settings
Activities
Example
If you have implemented this BAdI, you can execute customer-specific checks that run before the SAP standard checks. For example, you can make sure that the Main Code indicator is not selected for any procedures that start with 5-1*.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20021001 |
| SAP Release Created in | 471 |
