Ansicht
Dokumentation

ISH_OM_BASICS - Explain Basics of Work Organizer Management

BAL Application Log Documentation   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

To understand work organizer management you must be familiar with SAPscript (meaning of windows, elements, and so on) and PDF-based print forms.

For information about PDF-based print forms, launch transaction SFP, and then choose Help -> Application Help.

You can trigger the printing of forms from the application transactions (for example, patient admission) in the IS-H system. It is, of course, also possible to print letters and labels, or to create magnetic cards (if an appropriate output device is available). For this reason, we prefer to use the umbrella term work organizer rather than simply 'form'.

• Definition of Work Organizer

Work organizers are forms, labels and magnetic cards in the IS-H system. Work organizers are usually linked to a SAPscript form and are formatted and output using SAPscript.

Whether or not a particular work organizer (for example, label, invoice) can be printed depends on events. The events determine which datasets ( work organizer types) are available for output.

• Definition of Work Organizer Type

Work organizer types represent datasets that are available for editing a work organizer.

Example

• When a patient is admitted to your hospital, you can create an admission notification for the insurance provider.

• You cannot, however, print an invoice when the patient is transferred.
  

The IS-H transaction triggers an event. One or more work organizer type(s) are assigned to each event. These assignments are either the default settings delivered by SAP, or a subset of those selected by the customer). The work organizer type determines the data set that can be printed in SAPscript on a work organizer.

Example

The work organizer types AUFDT, AUFK, AUFN, PDAT, PETK and STAM are provided for the event NP11P0 (Inpatient Admission: Create Planned Admission Data).

The work organizer type determines the dataset available for output in SAPscript or on PDF-based print forms. The data fields (symbols) available on a form are defined in RNF structures. RNF structures are structures in the R/3 Repository. By looking in this repository, you can tell which fields are available for each of the RNF structures and discover their respective meaning.

The Section entitled Display Standard Work Organizer Types tells you which work organizer types make available which RNF structures.

Caution: The work organizer types are predefined by SAP. You cannot add to them in Customizing.

Example

When you use work organizer type PETK, the RNF structures at your disposal include the following:

• RNF01 (Patient: Name, Address)

• RNF02 (Patient: Employer)

• RNF031 (Patient: Next of Kin1)

• RNF032 (Patient: Next of Kin2)

Caution: The category of a work organizer type is predefined by SAP. You cannot modify it.

A work organizer type is assigned to exactly one of the following three categories:

• Category ' ': No condition applies

You can only assign one form to a work organizer assigned to the work organizer type of the category ' ' (no condition).

• Category '1': Conditioned by insurance provider/insurance provider type

You can assign various forms, dependent on the insurance provider and/or the insurance provider type, to a work organizer assigned to a work organizer type of the category '1' (conditioned by insurance provider/insurance provider type).

• Category '2': Conditioned by billing type/insurance provider type

You can assign various forms, dependent on the billing type and the insurance provider type, to a work organizer assigned to a work organizer type of the category '2' (conditioned by billing type/insurance provider type).

Example

• Work organizer type PETK (patient labels) belongs to category ' ' (no condition). It is independent of the insurance provider.

• Work organizer type AUFK (admission data for insurance provider) belongs to category '1' (conditioned by insurance provider/insurance provider type). You can therefore use different for different insurance providers.

• Work organizer type RECH10A (outpatient invoice data (billing type) belongs to category '2' (conditioned by billing type/insurance provider type). You can therefore use different for different billing types and/or insurance provider types.
  

Usually, work organizer types of the categories '1' and '2' are used for correspondence with insurance providers.

Note: You can use SAPscript commands (such as IF..; CASE ..) in forms to output specific texts in relation to an insurance provider without having to create a separate form for this purpose.

In Customizing, you stipulate in relation to each institution which work organizer types you want to use with which events. You also specify whether you want to restrict the work organizers according to user-specific organizational units (see below).

Note: You can only use such event/work organizer type combinations that are listed under Assign Events to Work Organizer Types (SAP Preset Values).

A work organizer is a utility that primarily links a work organizer type with one or more SAPscript forms or PDF-based print forms. You can also control printout (number of copies, header) at work organizer level.

Examples

• Example 1

Whenever a patient is admitted to your hospital, the admitting release form is to be printed in duplicate. You use work organizer type AUFN, and create a corresponding SAPscript form or a PDF-based print form. A work organizer (for examplen, named VERTRAG) is required to link the work organizer type with the form. You start by assigning the work organizer to work organizer type AUFN. In output control, you specify for work organizer VERTRAG, that the corresponding SAPscript form is N_AUFVERTRAG, or, for a PDF-based print form it is ISH_ADM_RELEASE_FORM, and should be printed in duplicate.

• Example 2

Whenever a patient is admitted into your hospital, small and large labels are to be printed. You use work organizer type PETK, and create two SAPscript forms (for small and large labels). Two work organizers (for example, ETIKL and ETIGR) are required to link the work organizer type with the forms. You start by assigning both work organizers to the same work organizer type PETK. In output control, you specify that the corresponding SAPscript form is ZN_ETIKL (or ZN_ETIGR) for the work organizer ETIKL (or ETIGR). To output a PDF-based print form, you can use the form ISH_PATIENT_LABEL, for example.

• Example 3

When outpatient billing is carried out, different invoice forms are to be created for statutory insurance funds and private health insurers. Two different billing types have been defined for this in Customizing for Billing. You use work organizer type RECH10A since it belongs to category '2' (conditioned by billing type/insurance provider type) and therefore allows different forms for each billing type. You create two SAPscript forms (for example,. ZN_RECHGES for statutory insurance funds and ZN_RECHPRI for private health insurers). A work organizer (e.g. RECHAMB) is required to link the work organizer type with the forms. You assign this work organizer to the work organizer type RECH10A. Since the work organizer type is controlled by the billing type, two entries are required for the work organizer RECHAMB in output control:

• Assignment of SAPscript form ZN_RECHGES for billing type statutory

• Assignment of SAPscript form ZN_RECHPRI for billing type private.

As mentioned above, one or more forms are assigned to a work organizer. Depending on the work organizer type, the form windows of these forms must be controlled via a window table. This information is stored with the work organizer types. It can also be found in the IMG Section entitled Display Standard Work Organizer Types. In the table contained in this documentation, TNF05: yes or TNF05: no have the following meaning:

• TNF05: yes:

The form windows can, or must be controlled via the window table. In other words, you must assign all of the form windows and elements that are to be printed to the work organizer. Windows or window elements that are not specified in window control are not output.

• TNF05: no:

The form windows and elements to be printed are predefined by the SAP print program; You cannot control them.

Example:

When a patient is admitted into your hospital, you want to be able to print two different patient status reports (for example, one short report and one long report) with the same window assignment, but using two different datasets.

1. You use work organizer type SSTAM that is controlled via window table TNF05 (TNF05: yes).
2. You define two work organizers STAMKURZ and STAMLOANG.
3. You assign these work organizers to work organizer type STAM.
4. You can then create a SAPscript form which contains the complete detailed version of the patient status report.
5. In the main window, you use the elements

• E100 (for patient data)

• E105 (for next of kin data)

• E120 (for admission data), and so on.

1. You assign this SAPscript form to both of the work organizers.
2. When maintaining the window and text elements, you assign all of the window elements to the work organizer STAMLANG, but only use, for example, E100 and E120 for the work organizer STAMKURZ.

Hint: This technique allows you to considerably reduce the number of SAPscript forms you need to create, and thus the effort needed to maintain them. Rather than creating several similar forms, you create a single comprehensive form whose window is composed of several elements. These window elements are accessed depending on the work organizer.

Repetition structures are a special feature of window and element control. Repetition structures are structures that occur any number of times (for example, insurance relationships, newborns, invoice items), as opposed to once only (for example, patient address). The window elements for these repetition structures are predefined by SAP and cannot be controlled. The template forms contained in the standard SAP software already have this predefined structure. These forms have names that start with N_.

Hint: Use the template forms contained in the standard SAP system, or copy them if you want to tailor them to satisfy your own requirements.

Output control lets you specify

• Which SAPscript form or PDF-based form is to be used to print a work organizer

• Which further control parameters the system is to use.

As described above, three categories of work organizer type exist (no condition, conditioned by insurance provider/insurance provider type, conditioned by billing type/insurance provider type). Each of these categories has a corresponding table for output control.

Caution: You must make sure you enter your work organizer in the correct output control table in accordance with the category of the associated work organizer type. For example, if your work organizer is assigned to work organizer type AUFK, you should use the control table Output conditioned by insurance provider and insurance provider type since work organizer type AUFK belongs to category '1' (conditioned by insurance provider/insurance provider type).

For further information about the individual fields, read the following sections.

These fields in output control let you manage header texts, footer texts, and so on, in a flexible manner outside of the actual forms, and thus keep maintenance effort to a strict minimum.

The aim is not to maintain general specifications, such as the letter header, account details several times in all forms, but rather to store them centrally as standard texts which can be included in the forms.

You should begin by storing letter headers, footers, signatures and senders as standard texts. The following standard texts are delivered with the system:

• N_0000_HEADER

• N_0000_FOOTER

• N_0000_SENDER

• N_0000_SIGNATURE.

You need to make two settings to output the standard text N_0000_HEADER:

1. You must enter the text name N_0000_HEADER in the Header text field of the output control table.
2. Include the standard text using the SAPscript command INCLUDE &RNF19-TXTHE& OBJECT TEXT ID ST PARAGRAPH in the header window of the form.

The SAPscript symbol &RNF19-TXTHE& automatically contains the name of the standard text specified in the output control table. The following symbols are available to you:

• &RNF19-TXTFO& for the footer text

• &RNF19-TXTSI& for the signature

• &RNF19-TXTSE& for the sender.

Hint:: If you require different footer texts for different forms, created standard texts such as Z_0000_FOOTER, Z_0001_FOOTER, and enter these for the respective work organizers.

Hint: Also use symbols within this standard text, for example, to create your clinic header. You can use any of the fields in the institution table TN01 for this. You can get some ideas by looking at the standard texts contained in the standard SAP system (for example, N_0000_HEADER). This approach also enables you to use the same form with an identical header for several institutions.

If you want to print data using your own program rather than SAPscript or PDF-based print forms, you can write your own print function module and specify its name in the Print Program field.

To develop your function module, you must use the predefined interface. This interface is dependent on the work organizer type used. A function module is assigned to each work organizer type (in the IMG activity Display Keys / Texts. The source code of this function module gives you the interface for your own print function module. The interface usually contains all of the RNF structures defined for the work organizer type along with additional data.

Hint: Only use this technique if you cannot satisfy your requirements using SAPscript or PDF and all of the enhancement options.

If you want to implement an alternative program logic when retrieving the data, you can write your own function module containing the complete required functionality of the work organizer. You specify the name of this function module in the Customer FM field.

In such cases, you must use the predefined interface. This interface is dependent on the work organizer type used. A function module which you replace here by your own customer function module is assigned to each work organizer type (in the IMG activity Display Keys / Texts. For this reason, your function module must have the same interface.

In contrast to your own print program, to which all available patient data is passed in the interface, a customer function module must retrieve and output the data itself.

Hint: Only use this technique if you cannot satisfy your requirements using SAPscript or PDF and all of the enhancement options.

If you select Dialog Print, the user can change certain print parameters (for example, printer, number of copies) before printing takes place.

If you select Standard, the user can print the corresponding form by choosing Standard Form (or the equivalent print icon) in the application transaction.

The following conditions must be met for the standard print function to be active:

• You must select Standard for the event-to-work organizer combination when assigning the appropriate work organizer type to the event.

• You must also have configured printer determination such that the system can determine a printer automatically.

By evaluating two Customizing tables, the system attempts to automatically determine a printer (or an output device in general) for each work organizer. Printer determination is a prerequisite for standard form printout. The system proposes forms, for which standard print is not active, when you choose Choose Form... in the application. In this print mode, you can specify a printer to override the default printer setting.

The system evaluates the following settings when determining the printer:

• Printer-to-Work Organizer Assignment

For the printer-to-work organizer assignment, you specify which printers are to be generally available for a work organizer. You can also enter an asterisk (*) if the work organizer can be output on all printers.

• Output Device-to-Input Device Assignment

For the output device-to-input device assignment, you specify which output device (usually a printer) is assigned to which input device (usually a screen). You can assign several output devices to one input device. If you enter an asterisk (*) for the input device, you allow all input devices to access a particular output device.

The terminal or computer name should be entered as the input device name.

Hint: The quickest way of determining the name of your input device is to execute the transaction SM04.

Example:

The work organizer ETIKL can be output on the following printers:

• PR01

• PR03

• PR07
  

The printers

• PR03

• PR09

are assigned to the input device TERM01.

If the work organizer ETIKL is now requested from the input device TERM01, the system determines the printer PR03.

SAPscript and PDF-based printing enables you to print bar codes.

Hint: You can use the standard text SAPSCRIPT-BARCODETEST contained in the standard SAP system to test whether you can print bar codes on your printer.

You can specify the paper tray you want the target printer to use directly in a SAPscript form. This lets you, for example, print the first page from one paper tray and the next pages from another.

To do this, enter TRY01, TRY02 or TRY03 accordingly in the Resource Name field in the page definition of your SAPscript form.

Hint: You can use the standard text SAPSCRIPT-TRAYTEST contained in the standard SAP software to test if your printer supports paper tray control.

Optical archiving of forms requires an archive to be linked to the SAP system. For further information about this, see the Section Basis Components -> Basis Services -> SAP ArchiveLink of the Implementation Guide.

You can only store forms in an optical archive if this is supported by SAP. You can find this information in the Object Type field in the table of work organizer types. If archiving is allowed for a work organizer type, an object type is assigned to the work organizer type. The assignment of an object type to a work organizer type is predefined by SAP and you cannot change it.

You activate optical archiving within output control. For further information, see the documentation on the various fields (F1 Help), and the following sections pertaining to output control:

• Configure Unconditioned Output Control< />

• Configure Output Conditioned by Ins. Provider and IP Type

• Configure Output Conditioned by Billing Type and IP Type

You can tailor the archiving information to suit your own needs using the SAP enhancement NPRI0001.

Work Organizer Management supports the logging of printed forms and the mass printing of admission and discharge notifications. Form logging must be active if you want to use the mass print function.

When assigning a work organizer to a work organizer type, specify whether the system is to log form printout. If you activate logging for a work organizer, you should also specify the Logging type:

• 01: Admission notification

• 02: Discharge notification

• 03: Insurance verification request

You have to assign the correct logging type to be able to use the mass print function. The logging type 03 (insurance verification request) is currently not used.

If you activated form logging for admission notifications and/or discharge notifications, you can, for example, at the end of the day, print all of the admission notifications that have still to be printed, i.e. for which no form logging entry exists. You carry out mass printing with the RNPRIAU0 program.

It is possible to print different forms for the same events dependent on the user's organizational unit. The organizational unit in question is in fact the organizational unit to which the user is assigned and not, for example, the organizational unit assigned to the movement. The user's organizational unit is derived exclusively from the user parameter NF1.

Organizational unit-dependent control requires you to have made a restriction on organizational units in Customizing for work organizer types.

In such cases, the system would only print the work organizers that are assigned to the user's organizational unit. If a work organizer was not assigned to the user's organizational unit, the system does not find a form for print formatting.

You can also assign the organizational unit '*' to a work organizer to accommodate the remaining organizational units.

You can also specify an alternative output control for every combination of work organizer and work organizer type. This alternative control overrides all of the parameters you specified in output control for the work organizer. For instance, you can output a different number of copies for each organizational unit. To do this, you must select Alt. Parameters.

Note that if you set this indicator, you must have correctly maintained all the parameters listed here. Only these specifications are used. The standard specifications are no longer taken into account. This means, in particular, that you have to maintain all parameters, even if you want to specify only one parameter different to the standard parameter.

When printing invoice forms you can choose between live (production) and test print modes. When an invoice is printed in live mode, the system records the print date. In general, live print is performed when single print control is active. This means that a spool request is created for each invoice.
In test print mode, the system does not record the print date, and you can print an invoice as many times as you like. Test print is usually peformed with single print control deactivated. As a result, all the invoices that are printed in an invoice run are written to the same spool request. You can scroll through the invoices one by one in the form preview function.
For this to be technically possible, a one-time spool request must be created for all invoices to be printed when printing is initiated. Since the data for this spool request is valid for all invoices, the work organizer type RECH_TS or RECH_TSS exist specially for invoice printout Singapore/Switzerland.
To enable the system to determine the data for the spool request when single print control is deactivated, you have to perform the following IMG activities in the chapter entitled Work Organizer Management:

• Assign Events to Work Organizer Types (Customer)

Assign the event FAKTTS to the work organizer type RECH_TS or RECH_TSS.

• Work Organizers -> Maintain Keys/Texts

Define the work organizer RECH_TS.

• Assign Printers to Work Organizers

Assign the work organizer RECH_TS to a printer. All the invoices you output with deactivated single invoice control (test print) are output on this printer.

• Configure Unconditioned Output Control

Maintain output control for the work organizer RECH_TS.

Further information is provided in the SAP Notes 45109 and 443638.

You can list all of the settings for a work organizer. The system also checks the consistency of these settings while formatting the list. Errors are highlighted in color in this list.

The system also determines the possible output devices for the input device on which the program to list work organizer settings was executed. The user parameter NF1 is also evaluated.

On the program selection screen, you can also enter a user ID and an input device to determine the possible work organizers of another user or of another input device without you having to be logged on as this user or to this input device.

If you want to print data or values, which do not exist as RNF structures, in forms, you can call an ABAP subprogram from the SAPscript form to determine data or calculate values.

Example:

You want to print the patient's age on a form. However, the RNF structures only contain the date of birth and the admission date.

Within SAPscript, you can call your own ABAP program to which you pass the date of birth and the admission date and then calculate the age. The following SAPscript command lines would produce the desired result:

PERFORM GET_ALTER IN PROGRAM ZNSCRIPT

USING &RNF01-BIRTHDTPAT&

USING &RNF06-ADMISSDATE&

CHANGING &AGE&

ENDPERFORM

Upon completion of the subprogram, the SAPscript symbol &AGE& is available.

The ABAP program contains the USING parameter and the CHANGING parameter in two tables which use the repository structure ITCSY. This structure is composed of the field name and the field value. An ABAP subprogram for calculating the patient's age looks something like this:

form GET_ALTER tables IN_TAB structure ITCSY
OUT_TAB structure ITCSY.
data: DATUM1 type D, DATUM2 type D, AGE type I.

read table in_tab with key 'RNF01-BIRTHDTPAT'.
* convert birthdate into date format
DATUM1(4) = IN_TAB-VALUE+6(4).
DATUM1+4(2) = IN_TAB-VALUE+3(2).
DATUM1+6(2) = IN_TAB-VALUE(2).

read table in_tab with key 'RNF06-ADMISSDATE'.
* convert admission date into date format
DATUM2(4) = IN_TAB-VALUE+6(4).
DATUM2+4(2) = IN_TAB-VALUE+3(2).
DATUM2+6(2) = IN_TAB-VALUE(2).

clear AGE.
call function 'ISH_FIND_AGE'
exporting
DATE = DATUM2
DATE_OF_BIRTH = DATUM1
importing
AGE = AGE
exceptions
AGE_NEGATIVE = 01
OTHERS = 99.

read table OUT_TAB with key 'AGE'.
write AGE to OUT_TAB-VALUE USING EDIT_MASK '__.__.____'.
modify OUT_TAB index SY-TABIX.
endform.

Cautionn: Note that all SAPscript symbols are of the type CHAR, i.e. you may have to convert date fields yourself, as in the above example.

Caution: If you use ABAP subprograms to read additional data from the database, you must also remember that the data may not yet be updated and is consequently also not saved in the database. In such cases, you could read the data from the ABAP memory. For further information about this, see the standard function module (ISH_PRINT_...) for the work organizer type, since this module uses the same technique.

When reading the data from the database you must also take into consideration that the numerical data (e.g. the case number) is often stored with leading zeros in the database, whereas the SAPscript symbol does not have leading zeros.

Hint: If you want to call ABAP subprograms from several SAPscript forms, you should use customer-defined symbols instead of the RNF symbols in the ABAP program. In such cases, you would use ADMISSDATE rather than RNF06-ADMISSDATE in the above example. You then use the following command to define the symbol before calling the ABAP subprogram in the SAPscript form:

DEFINE &ADMISSDATE& = &RNF06-ADMISSDATE&.

This technique makes your work easier if the admission date is in a different symbol in another form.

• Use the standard forms delivered with the standard system, or copy these forms and tailor then to satisfy your requirements.

• Only modify the structure of the standard forms if this cannot be avoided.

• Whenever possible, use standard texts to avoid having to store the same information several times over. This greatly reduces maintenance effort.

• Develop and test SAPscript forms directly with the printer you will subsequently use in production operation. Try to use the same printer for the same work organizer in as many locations as possible.

• If you have several institutions in your system, try to standardize the forms. Instead of using several forms to create institution-specific details, use SAPscript commands (IF .., CASE ..) within one form.

• Only modify SAP print modules or create your own print modules if you cannot achieve the required functionality with an external PERFORM.

CPI1466 during Backup   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 37753 Date: 20240425 Time: 104755     sap01-206 ( 591 ms )