This flow logic is only relevant if you are searching for a document. As the known search data you want to enter data for a SAP object that is integrated in a customer-specific implementation in the document management system.

In this editing process data is transferred between the following subscreens:

• Screen container for the processing of documents
  (subscreen 1500, function group CV130)

• Customer-specific subscreen for maintenance of link data

Screen layout occurs in the processing block Process Before Output (PBO), after a screen has been called, but before the display screen is processed.

The flow logic for the screen container 1500 (program SAPLCV100) is completely programmed in R/3. The customer-specific subscreen is determined using this BAdI interface, in which the link data for the document search is entered.

The instance for implementation is created with filters in PBO module DYN1500_INIT OUTPUT of the BAdI. The filter type is DOKOB (Linked SAP object).

The object links that have been read (table DRAD) are transferred in module DYN1500_SET_DATA to the user program.

In your enterprise-specific program, the subscreen that you programmed is called. The information must be stored in the implementation for each filter type (object).

Program in Screen Painter (transaction SE51) the following process logic:

• Get instance for object reference:

Screen processing occurs in the processing block Process After Input (PAI), after the display of a screen is processed. This processing block calls modules in ABAP programs, and establishes which processing takes place on screen after a user action.

The function code is transferred to the application program. In this position you can determine each function code in the application program by using the method GET_FUNCTION_CODE.

In implementation you can transfer and save the function code in the attribute provided for this purpose.

IF_EX_DOCUMENT_OBJ~FUNCTION_CODE = FUNCTION_CODE.

Alternatively:

FUNCTION_CODE = IF_EX_DOCUMENT_OBJ~FUNCTION_CODE.

Program in Screen Painter the program for screen processing. The following flow is a suggestion.

• Using the method PUT_DATA, transfer the data available on the table control.

• Selections must be marked with an ‘X’ in the field TAB_MARK in the interface table TAB_DRAD_WORK.

In order to prevent data inconsistencies, the flow logic for screen container 1500 (program SAPLCV100) includes a link data check.

• Transfer the data using method GET_DATA in module DYN1500_GET_DATA.

• Call current function in table control in module DYN1500_SAVE_EXECUTE.

Before the new link data from the table control for the customer-specific subscreen is saved, an additional confirmation prompt may appear. Here you can also cancel the saving of the link data.

• User:

• Application:

• Processing of OK code for the marked entry in transferred table TAB_DRAD_WORK.
• If you double click or choose the function Display, the method JUMP_TO_SCREEN is called. In this method the goto for each object must be implemented.