Change record object addition in Object links of DIR

For GUI:

In include LCV130F25:

CALL METHOD CL_EXITHANDLER=>GET_PROG_AND_DYNP_FOR_SUBSCR      EXPORTING        EXIT_NAME       = 'DOCUMENT_OBJ'        CALLING_DYNPRO  = '1500'        CALLING_PROGRAM = 'SAPLCV130'        FLT_VAL         = lf_dokob_filt        SUBSCREEN_AREA  = 'SUB_OBJ'      IMPORTING        CALLED_DYNPRO   = gf_call_dynp        CALLED_PROGRAM  = gf_prog_name.

The above function fetches the screen name based on the filter defined in DOCUMENT_OBJ.

In include LCV130F26:

IF NOT lf_act_imp_existing IS INITIAL.    CALL METHOD lf_object_instance->put_data      EXPORTING        table_drad_work = lt_drad_work        table_drad_db   = lt_drad_db        activity        = lf_activity        flt_val         = lf_dokob_filt        draw            = gs_draw_save.  ENDIF.

Above code puts the data in the object link. This is also inside the DOCUMENT_OBJ Badi for a specific filter type.

For example, for recipe, the program name maintained is /PLMI/RCP_DOCLINK with the dynpro number 2000 and all the functionalities are maintained inside this Dynpro screen. Similarly, for Engineering change record a program has to be called with the Dynpro number, incorporating the functionalities provided in object links tab.

Additional information:

In include LCV130O01:

READ TABLE inttdwot WITH KEY tabidx = idx.  IF sy-subrc EQ 0.    drad-dokob = inttdwot-dokob.    if  inttdwot-dynpronr >= 9000.

*****> 9000 = customer dynpro->>therefore do not use  +1000      dynprnr = inttdwot-dynpronr.    else.*****  get dynpro number      dynprnr = inttdwot-dynpronr + 1000.    endif.    objlink_strip_400-screen_nr = dynprnr.

The above code generates the Dynpro screen number based on the number assigned to a particular Document type and if it is 500 then the screen and program name should come from the Badi and for Change record it is 500.