SAP ABAP IMG Activity ISH_WP_VW123_COLUMN (BAdI: Add Columns to Arrivals/Departures/Occupancy View)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ NPVS (Package) Application development patient management system
IMG Activity
ID ISH_WP_VW123_COLUMN BAdI: Add Columns to Arrivals/Departures/Occupancy View  
Transaction Code S_KK4_96000703   (empty) 
Created on 20030113    
Customizing Attributes ISH_WP_VW123_COLUMN   BAdI: Add Columns to Arrivals/Departures/Occupancy View 
Customizing Activity ISH_WP_VW123_COLUMN   BAdI: Add Columns to Arrivals/Departures/Occupancy View 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISH_WP_VW123_COLUMN    

Use

The Business Add-In (BAdI) IS-H: Modify Columns in Clinical Work Station (ISH_WP_VW123_COLUMN) lets you modify elements of the occupancy, departure and arrivals views of the Clinical Work Station. The system calls the BAdI every time the views are called or the Clinical Work Station is refreshed.

For more information, refer to the

Requirements

Standard settings

The import interface consists of the view tables for each view, the selection criteria, and the field catalog of the SAP List Viewer Control that appears on screen:

  • CRITERIA (IS-H: Table Type for Generic Selection Criteria)

    This RSPARAMS structure contains the selection criteria used by the view program. Example: Entries of SE_EINRI, KEYDATE and KEYTIME correspond to the institution, date and time criteria specified on the initial screen of the Clinical Work Station.

  • DISPVAR (Field Catalog for SAP List Viewer Control)

    This table contains a detailed catalog of the columns displayed by the SAP List Viewer Control in the Clinical Work Station (column title, width, data type, field name, etc.). Refer to the SAP List Viewer documentation for a complete description of field catalog properties and settings.

    Example: The field NO_OUT in the catalog structure can be used to determine which fields will be displayed to the user. By inspecting this value, hidden fields can be ignored, resulting in a load performance increase:

    IF DISPVAR-FIELDNAME = 'BED_RESV_ICON' AND

    DISPVAR-NO-OUT = 'x'.

    "field 'bed_resv_icon' is not output

    ELSE.

    "load field value

    ENDIF

    If more than one SAP List Viewer Control is displayed on screen - for example, when the occupancy and arrivals lists are presented together in separate panes - the DISPVAR structure will contain the field catalog entries for both lists.

  • OCCUPANCY_LIST (IS-H: List Table Occupancy List)
  • ARRIVAL_LIST (IS-H: List Table Arrivals List)
  • DEPARTURE_LIST (IS-H: List Table Departures List)

The view table parameters are internal tables that contain the source data for the SAP List Viewer Control in the Clinical Work Station. The parameters are passed to the BAdI each time the views are called or refreshed. If a view is not displayed in the current context (for example, the user has requested only the occupancy view), the corresponding parameter will be empty. The fields and records of these tables correspond to the columns and rows displayed in the output list. By modifying the view tables in the ABAP code, the output lists can be directly controlled; user-defined columns can be populated and individual cells can be updated based on the results of a calculation, etc.

In order to create a new user-defined column in any of the views, you must add a new field to the corresponding master structure of the data dictionary. (For example, to create a new occupancy view column, you would create a new field in the structure RNWP_OCCUPANCY_LIST). SAP recommends that you do this via a customer include. Once a customer field is defined, it may be accessed exactly like the standard fields. Refer to the sample method implementation for an example.

Exceptions

ERROR signals to the system that any changes made to the view tables within the BAdI should be discarded before the views are displayed to the user. Use this exception to abort any changes made by the BAdI if an error condition is encountered during processing and the content of the list is made suspect.

Note

This BAdI replaces the component EXIT_SAPLN1WP_001 of the customer exit SAPLN1WP. For new enhancements to the Clinical Work Station, you should use Business Add-Ins and not SMOD exits. You should migrate existing SMOD implementations to BAdIs wherever possible.

Activities

You call the BAdI using the function ISH_WP_VW123_COLUMN in the function group N_WP_INPMOVEMENTS.

To implement the BAdI, proceed as follows:

  1. Use the transaction SE19 to create an implementation of the BAdI in the customer namespace.

    Note: This implementation does not yet have any program code for the method.

  2. The interface of your implementation contains the method MODIFY. Double-clicking on the method takes you into the editor, where you can write your own code from scratch, or use the sample implementation as a template.
  3. Once the code is complete, you must activate the implementation so the application programs can execute the modification. Only one implementation can be active at any given time.

Example

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 ISH_WP_VW123_COLUMN 0 KK43000011 Clinical Work Station 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030113 
SAP Release Created in 471