Ansicht
Dokumentation

ISH_NWPLACE_DTM - Determine Variant for Clinical Process Builder

BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by SAP AG.

In this IMG activity, you determine for a specific institution the variant the system is to use when the Clinical Process Builder is called from different places in the system (for example, case overview, clinical work station, visit overview). This IMG activity has no influence on the variant the system uses with a direct call, i.e. when you enter and execute the transaction code directly in the command field, or call the Clinical Process Builder directly from the SAP Easy Access menu.

Here you can determine the variant in relation to

1. Callpoint
2. Institution
3. Role
4. User
5. Processing mode (corresponds to the function that can be chosen on the initial screen: create, change, or display)
6. Processing mode for the case
7. Processing mode for the movement
8. Case type
9. Case category
10. Movement category
11. Movement type
12. Treatment category of the movement

The system determines the table entry for the relevant variant or transaction variant by scanning the table fields in the order given above. For example, if an explicit value exists for the current callpoint, all other entries (including *entries) are removed from the determination. Consequently, if a * entry exists for the callpoint and an explicit value exists for the current institution, the system ignores this entry in the table.

The system uses the settings for the following scenarios:

• Call the Clinical Process Builder in change or display mode (see processing mode) with initial screen

• Call Clinical Process Builder in change or display mode without initial screen

• Call Clinical Process Builder in create mode (see processing mode) without initial screen

When the Clinical Process Builder is called in create mode with initial screen, the settings are without effect as for a direct call (see above). In such cases, the system applies the variant last used by the user.

If you do not make any entries in this table, the system uses the variant last used by the user at all callpoints in create mode.

In change or display mode, the system uses the variant with which the selected object was last edited. If a variant is not saved for the selected object, the variant last used by the user is used.

In each of the above mentioned fields, you can enter an explicit value, or an * (representing all values for the field). Note that the explicit specification overrides the * entry.

In each case, you can select the explicit values from the value help for the field, or enter the required value directly. Note that only the following values are allowed for the processing mode (all three fields):

• INS (create admission)

• UPD (change admission)

• DIS (display admission)

• *

You wish users working in institution 1 to create all new inpatient admissions from the case overview using the variant Inpatient Admission and all new outpatient admissions from the case overview using the variant Outpatient Admission. After defining both variants in the Clinical Process Builder by choosing Settings -> Variant -> Create, make the following entries here:

• For inpatient admissions

• Institution,,1

• Callpoint,,Case Overview

• Processing Mode,,UPD

• Processing Mode for Case,,*

• Processing Mode for Movement,,INS

• Role,,*

• User,,*

• Case Type,,*

• Movement Category,,1

• Movement Type,,*

• Treatment Category,,*

• Work Environment Type,,Clinical Process Builder

• Work Environment,,Inpatient Admission

• Transaction Variant

• For outpatient admissions

• Institution,,1

• Callpoint,,Case Overview

• Processing Mode,,UPD

• Processing Mode for Case,,*

• Processing Mode for Movement,,INS

• Role,,*

• User,,*

• Case Type,,2

• Movement Category,,4

• Movement Type,,*

• Treatment Category,,*

• Work Environment Type,,Clinical Process Builder

• Work Environment,,Outpatient Admission

• Transaction Variant

Additionally, you wish to create a transaction variant for outpatient admission. Transaction variants make it possible to preset fields, to determine required-entry fields and display fields, and to suppress fields from the screen. Once you have created and saved a transaction variant in the transaction SHD0 (for example, Z_OUTPATIENT_ADMISSION), make the following additional specification for the above entry:

• Institution,,1

• Callpoint,,Case Overview

• Processing Mode,,UPD

• Processing Mode for Case,,*

• Processing Mode for Movement,,INS

• Role,,*

• User,,*

• Case Type,,2

• Movement Category,,4

• Movement Type,,*

• Treatment Category,,*

• Work Environment Type,,Clinical Process Builder

• Work Environment,,Outpatient Admission

• Transaction Variant,,Z_OUTPATIENT_ADMISSION

General Data in Customer Master   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 9393 Date: 20240425 Time: 192806     sap01-206 ( 95 ms )