Add custom fields in header of FI documents using FI_HEADER_SUB_1300IM

Question

Hi
We are trying to add a couple of custom fields in header area of FB01 by making a copy of badi FI_HEADER_SUB_1300IM. With this method we are facing a couple of problems
- The custom fields added in bkpf structure,  only appears in FB01 just in the case we have go before to FB03 or FB02.
- We don´t reach to save data of these fields in table BKPF.
can anybody help us with these problems?
thanks in advance for your help
I leave here the code we have used in the copy of badi FI_HEADER_SUB_1300IM
MODULE d1300_pbo OUTPUT.
  IF exit IS INITIAL.
    CALL METHOD cl_exithandler=>get_instance_for_subscreens
      CHANGING
        instance                      = exit
       EXCEPTIONS
*      NO_REFERENCE                  = 1
*      NO_INTERFACE_REFERENCE        = 2
*      NO_EXIT_INTERFACE             = 3
*      DATA_INCONS_IN_EXIT_MANAGEM   = 4
*      CLASS_NOT_IMPLEMENT_INTERFACE = 5
         OTHERS                        = 6.
    IF sy-subrc <> 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
  ENDIF.
  CALL METHOD exit->get_data_from_screen_pbo
    EXPORTING
      FLT_VAL       = 'ES'
    IMPORTING
      ex_bkpf       = g_bkpf
      ex_x_no_input = g_no_input.
  loop at screen.
   if g_no_input = 'X'.
     screen-input = 0.
     modify screen.
   endif.
  endloop.
ENDMODULE.   
**************************+
FORM put_value .
* import header data from main screen
  call method exit->get_data_from_screen_pai
    EXPORTING
      FLT_VAL  = 'ES'
    importing
      ex_bkpf  = g_bkpf.
* set reference fields
g_bkpf-ZZDPTOAPROBADOR = bkpf-ZZDPTOAPROBADOR.
g_bkpf-ZZDELAPROBADOR = bkpf-ZZDELAPROBADOR.
* put data to main screen
  call method exit->put_data_to_screen_pai
    exporting
      im_bkpf  = g_bkpf
      flt_val  = 'ES'.
ENDFORM.
Added code tags
Edited by: Rob Burbank on May 10, 2011 12:17 PM

Answer 1

SriVarma,
Cool! I didn't know this BADI!
Playing around with existing implementations I can see that, BADI_SD_TAB_CUST_H, can definitely enhance the Sales order header with additional tab strip screens. Similarly BADI_SD_TAB_CUST_I can be used to enhance Sales order item screens.
Here is what I understand from the coding of an existing implementation
ACTIVATE_TAB_PAGE - takes a module pool program name and a subscreen that you created and adds it as a additional tab page to sales order header screen. You need to pass back f_program and f_dynpro with your program and screen number that you painted
TRANSFER_DATA_TO_SUBSCREEN - can be used to read and pass data to the fields on the subscreen you created
TRANSFER_DATA_FROM_SUBSCREEN - can be used to pass back whatever changes done by user to the respective Z variables in VBAK
PASS_FCODE_TO_SUBSCREEN - Pass the fcode the user selected to your subscreen.
I would suggest that you create a function group and create screens, functions etc within that and use those in these methods. Refer existing implementations. The global data of the function group can then be used to communicate between all the above methods