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_PROCEDURE_ | BAdI: Change Default Values for Case-Related Procedures |
| Transaction Code | S_KK4_96000515 | IMG Activity: BADI: ISH_PROCEDURE_ |
| Created on | 20020104 | |
| Customizing Attributes | BADI: ISH_PROCEDURE_ | BAdI: Change Default Values for Case-Related Procedures |
| Customizing Activity | BADI: ISH_PROCEDURE_ | BAdI: Change Default Values for Case-Related Procedures |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISH_PROCEDURE_PROPOS |
Use
This Business Add-In (BAdI) enables you to preset certain fields and change the values in special fields in the following functions:
- When creating a procedure in case-related procedure entry
- In surgical data entry
- In DRG data maintenance.
You must not issue error messages from this BAdI, since this could result in an abnormal termination or an ABAP short dump when the call is made from an external function module.
You can modify the following fields in case-related procedure entry and DRG data maintenance:
- Start date
- Start time
- End date
- End Time
- Departmental organizational unit
- Nursing organizational unit
- Main code (country version Germany only: §301, statistics)
- Surgery type
- DRG category (primary procedure, or secondary procedure)
- DRG entry sequence (sequence number or 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
- 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 determine the data, the current case date, current movement and all movements that exist for the case are passed to the interface.
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 determine other default values 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 still 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
By implementing this BAdI and your own source code, you can
- Have the system set or cancel the main code indicator
- Have the system propose the performing organizational unit from a parallel visit
- Have the system always start the time specification with 00:00:01
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 | 20020104 |
| SAP Release Created in | 463B |
