Use of Web Dynpro ABAP

Use

You can use the signature tool in conjunction with Web Dynpro ABAP. The signature tool for Web Dynpro ABAP is available as of SAP_ABA 7.00 (SP14) and SAP_ABA 7.10 (SP05).

The application component can use the interface view SIGNATURE as follows:

  • In the dialog box

    In this case, the signature screen is opened in a separate dialog box.

  • Inplace

    In this case, the signature screen is integrated in the interface of the application, that is, the signature screen is within the displayed dynpro.

The SIGNATURE component triggers the event INDIV_SIGN_FINISHED to show that the current individual signature or the signature process is completed.

Features

Signature Screen As Dialog Box

The procedure here is illustrated by the example of the Web Dynpro component DSIG_BOOKING_EX (DSIG_BOOKING_EX is the application component). This Web Dynpro component is used here as the application component. To be able to use the interface view SIGNATURE in a dialog box, you must perform the following steps:

  1. You perform the steps for linking the application to the digital signature (see Linking of Applications to Digital Signature).

  2. You make the Customizing settings for the digital signature.

  3. You must integrate the SIGNATURE component as a component usage:

    • DSIG_BOOKING_EX implements the dialog box version with the component usage SIGNATURE_2.

    • The attribute GO_SIGNATURE_2 (see package DS: Start of the navigation pathWeb Dynpro Component DSIG_BOOKING_EX Next navigation step COMPONENTCONTROLLER Next navigation step Attributes Next navigation step GO_SIGNATURE_2 End of the navigation path) saves a reference of the interface controller of the SIGNATURE component.

  4. Create an event handler for the event INDIV_SIGN_FINISHED of the SIGNATURE component. (See package DS: Start of the navigation pathWeb Dynpro Component DSIG_BOOKING_EX Next navigation step Views Next navigation step V_MAIN Next navigation step Method INDIV_SIGN_FINISHED_2End of the navigation path)

  5. To start the signature process, call the interface method IF_DS_SIGN~SIGN_WD. (See package DS: Start of the navigation pathDSIG_BOOKING_EX Next navigation step Views Next navigation step V_MAIN Next navigation step Method ONACTIONDISPLAY_SIGN_POPUPEnd of the navigation path)

    If you have not made any entries in the document when you call IF_DS_SIGN~SIGN_WD (parameter IM_DOC_TXT or IM_DOC_BIN), the document to be signed must be made available by the BAdI DS_CONTEXT.

Signature Screen Inplace

The procedure here is illustrated by the example of the Web Dynpro component DSIG_BOOKING_EX (DSIG_BOOKING_EX is the application component). To be able to use the interface view SIGNATURE as an inplace display, you must perform the following steps:

  1. You perform the steps for linking the application to the digital signature.

  2. You make the Customizing settings for the digital signature.

  3. You must integrate the SIGNATURE component as a component usage:

    • DSIG_BOOKING_EX implements the inplace version with the component usage SIGNATURE.

    • The attribute GO_SIGNATURE (see package DS: Start of the navigation pathWeb Dynpro Component DSIG_BOOKING_EX Next navigation step COMPONENTCONTROLLER Next navigation step Attributes Next navigation step GO_SIGNATUREEnd of the navigation path) saves a reference of the interface controller of the SIGNATURE component.

  4. Assign the interface context node DOCUMENT and make sure that the document to be signed is saved in one of the two following attributes before the SIGN function is executed:

    • Attribute DOCUMENT_TXT

    • Attribute DOCUMENT_BIN

    Alternatively, the document to be signed can also be made available by the BAdI DS_CONTEXT. In this case, you can skip the context mapping described above.

  5. You must embed the interface view SIGNATURE (see package DS: ViewContainerUIElement VCE_SIGNATURE in the layout of the view Start of the navigation pathDSIG_BOOKING_EX Next navigation step V_MAINEnd of the navigation path and in the MAIN window ( Start of the navigation pathDSIG_BOOKING_EX Next navigation step Windows Next navigation step MAINEnd of the navigation path).

  6. Create an event handler for the event INDIV_SIGN_FINISHED of the SIGNATURE component (see Start of the navigation pathDSIG_BOOKING_EX Next navigation step Views Next navigation step V_MAIN Next navigation step Methods Next navigation step INDIV_SIGN_FINISHEDEnd of the navigation path).

  7. To start the signature process, call the interface method IF_DS_SIGN~SIGN_WD_INPLACE (see Start of the navigation pathDSIG_BOOKING_EX Next navigation step Views Next navigation step V_MAIN Next navigation step Methods Next navigation step ONOACTIONDISPLAY_SIGN_POPUPEnd of the navigation path).

Use of Floorplan Manager (FPM)

The main task of FPM is to link together the subscreens made available by the application. As FPM is a framework for Web Dynpro ABAP-based applications, these subscreens are Web Dynpro ABAP interface views. In FPM, these subscreens are called user interface building blocks (UIBB). The application component into which the SIGNATURE component is embedded by component usage is assigned to FPM in the form of a UIBB.

Example

You can display the Web Dynpro application DSIG_BOOKING_EX as an example in the transaction SE80.

The example DSIG_BOOKING_EX comprises three parts:

  • Initial Screen

    On the initial screen, you select a document to be signed from the list and start the signature process by choosing Edit.

  • Signature Screen Inplace

    In the upper part of the screen, the data for the selected document is displayed. Select the Type of Signature (synchronous/asynchronous) and the Signature Strategy required. When you choose Start in the Signature Tool Inplace screen area, the signature screen is displayed:

  • Signature Screen As Dialog Box

    The document is displayed in the upper screen area. When you choose Start in the Signature Tool in Dialog Box screen area, the dialog box for the signature is displayed: