SAP ABAP IMG Activity ISHMED_PLGR_BADI_WPL (BAdI for Labelling Nodes in Worklist)
Hierarchy
☛ IS-H (Software Component) SAP Healthcare
   ⤷ IS-HMED-SC (Application Component) Planning
     ⤷ N1APMG_MED (Package) IS-H*MED: Appointment Management
IMG Activity
ID ISHMED_PLGR_BADI_WPL BAdI for Labelling Nodes in Worklist  
Transaction Code S_KK4_98000052   (empty) 
Created on 20031031    
Customizing Attributes ISHMED_PLGR_BADI_WPL   BAdI for Labelling Nodes in Worklist 
Customizing Activity ISHMED_PLGR_BADI_WPL   BAdI for Labelling Nodes in Worklist 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISHMED_PLGR_BADI_WPL    

Use

This Business Add-In (BAdI) is used in i.s.h.med Planning (IS-HMED-SC).

Day-based planning and the planning grid compile all patients, tasks, and services for which appointments must be planned, into one worklist. The worklist is structured as a tree, you can freely select the columns to be displayed from a column selection. However, the first column of the tree in the planning grid cannot be set using the column selection.

You can use this BAdI to determine the information which the system displays in the first column of the planning grid worklist.

To change the information displayed in the first column of the day-based planning worklist, the user exit EXIT_SAPLN1ANFTREE_001 is available.

Requirements

You must use the planning grid in order to be able to use the BAdI.

The implementation of the BAdI must be activated.

Standard settings

As standard, the first column of the worklist will display the name of the patient, the services of the order item, and the names of the services.

The BAdI is not active as standard.

The BAdI cannot be used multiple times.

The BAdI is not filter-dependent.

Activities

You use this BAdI to create a character string for each level when labeling the nodes in the worklist of the planning grid, which is displayed instead of the information displayed as standard.

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

At order item level you do not wish to display the names of the services contained in the order item. Instead, the name of the organizational unit to which this order item is addressed should appear.

See also

Method: LABEL_NODE

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 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG ISHMED_PLGR_BADI_WPL 0 I041002041 Planning 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20031230 
SAP Release Created in 472