Function documentationGenerator Version 2

 

In the further development of PMD a new generator version has been created. This now generates an object-oriented application. In the following section we call documents generated with this generator version Gen-2 Documents.

Advantages

Stability when transporting document categories:

  • User exits remain valid

  • PMD external data modules remain valid after transport

The object orientation is a prerequisite for the enhancement of the PMD with the addition of new features, such as unlimited long texts (see Enhanced Text).

The explicit PMD-PMD communication (DDC) replaces the PMD-PMD external data modules from Generator Version 1.

Later, PMDs should also be integrated into other applications, for example the documentation work station or the clinical order.

Effects

External Data Supply

Gen-2 documents cannot be used as external data modules (EDMs). Gen-2 documents can be explicitly integrated into other Gen-2 documents as data sources. This results in the following possibilities regarding PMDs as a source of external data:

Data Source / Target

Supply

Gen-1 as data source in Gen-1

As until now (EDM)

Gen-1 as data source in Gen-2

As until now (EDM)

Gen-2 as data source in Gen-1

Not possible

Gen-2 as data source in Gen-2

Explicit data supply from document category

You should proceed as follows to supply an element from a document category:

Supply an atomic field

  1. You select Start of the navigation path Data Supply Next navigation step From Document Category (Explicit) End of the navigation path.

  2. You specify the institution and ID of the source document category.

  3. You name the source field.

Supply a simple structure

  1. You select Start of the navigation path Data Supply Next navigation step From Document Category End of the navigation path.

  2. You specify the institution and ID of the source document category.

  3. For the sub-element to be supplied, For the sub-element to be supplied Data Supply From Superordinate Document Category (Implicit) and specify the name of the source field.

Supply a multiple structure

  1. You select Start of the navigation path Data Supply Next navigation step From Document Category End of the navigation path.

  2. You specify the institution and ID of the source document category and the multiple structure which should be used as the source.

  3. For the sub-element to be supplied (columns) choose Start of the navigation path Data Supply Next navigation step From Superordinate Document Category (Implicit) End of the navigation path and specify the name of the source column.

    Note Note

    The source field name always means the corresponding alias name.

    No input help is available for selecting the source fields and, where necessary the multiple source structure. We therefore recommend that you open the definition of the source document category in a parallel session.

    End of the note.

Document Printing

The printing of the document is controlled by a function module (instead of by a report). All function modules are found in a function group.

User Exits

User exits can now only use APIs and released variables.

APIs: All methods of class cl_ishmed_pmd_services (see relevant documentation). The methods which exist in this class represent the valid state for the corresponding release. If you require further APIs for your user exits, you should fill out a corresponding development request.

Released variables are contained in the generated function group.

Field symbols beginning with <pub__...>

Variables beginning with pub__..

Other objects of generated function groups (function modules, methods, modules, form routines, variables) cannot be used under any circumstances; modification or discontinuation are possible at any time.

Specific ABAP statements are not allowed: COMMIT WORK, ROLLBACK WORK, MESSAGE (in all variants)

All user exits of a document category (for dialog and print) must be programmed in a single new INCLUDE (Start of the navigation path Header Data Next navigation step User Exits End of the navigation path).

All Gen-2 user exits of a document category are in a new INCLUDE.

Print User Exits

Print user exits and the separate form can be deactivated individually.

Do not Print Element

In system administration you can explicitly specify that a specific element should not be printed.

Get Data Function

The two-level tree structure has been replaced by the HTML document viewer. Using Cut&Paste you can copy data into the current document.

The viewer is called in amodal form.

SAPscript Texts

SAPscript texts with more than 4 rows are displayed as SAPscript Editor controls.

You should note that double-clicking here does not branch to the full screen editor, as the control interprets this function as a selection command. You access the editor using the Editor pushbutton.

Long Texts

Formatting can be retained in long texts.

Enhanced Text

You can now use the new Enhanced Text documentation element type.

Checks

Check user exits also run during the save process (previously only when releasing and checking).

You can use an API to determine which check mode the user exit is currently running in; this means that (in the same way as the automatic required entry field check) you can devise function-specific checks (save or release).

If you determine errors in check user exits, you must configure the relevant error message with corresponding APIs in the message list.

Error Messages

The errors are collected and displayed in an ALV grid. If the error is assigned to a documentation element, you can navigate to the defective element by double-clicking on the message.