BAPI_ACC_DOCUMENT_POST - User Exit is not working

Question

Hi all,
I need to perform a posting and pass in some field into the extension table. I have follow the sap note recomendation and created a project in CMOD using ACBAPI01 as the component. I then added the coded into the user exit. When I tried to debug it doesn't not execute the code inside the user exit. Also BAPI_ACC_DOCUMENT_POST was executed w/o any error. However when I check the system, there's no document posted.
Also please correct me if I'm wrong. I'm not so sure what to populate for the following field in the header. Is the following correct?
  gt_docheader-obj_type   = 'IDOC'.
  gt_docheader-obj_key    = '$'.
  gt_docheader-obj_sys    = 'BGS1'.
  gt_docheader-bus_act    = 'RFBU'.
Thanks in advance
Ricky

Answer 1

Hi Ricky and Igor,
Rick is right: You can use userexit wherever they are provided. Many BAPIs as i.e.
[code]BAPI_ACC_DOCUMENT_POST        
BAPI_ACC_DOCUMENT_CHECK
BAPI_ACC_GL_POSTING_POST      
BAPI_ACC_GL_POSTING_CHECK
BAPI_ACC_BILLING_POST         
BAPI_ACC_BILLING_CHECK
BAPI_ACC_INVOICE_RECEIPT_POST
BAPI_ACC_INVOICE_RECEIPT_CHECK
BAPI_ACC_GOODS_MOVEMENT_POST  
BAPI_ACC_GOODS_MOVEMENT_CHECK
[/code]
are implemented including userexit (to be seen as CALL CUSTOMER-FUNCTION in coding). Only the most impotant and regularily used fields are part of the BAPI interface. If the customer makes an append to any table or structure, the handling of the additional fields does not always happen automatically in the BAPI.
We created a User exit for BAPI BAPI_ACC_GL_POSTING_POST because the customer made extensions to the posting block.
The additional parameter values are passed in the BAPI extension table which is a genereric character table. In include ZXACCU15 we do the transfer of values passed via extension table to table t_accit which is part of the interface of the ueserexit.
If then BAPI is executed but it does not trigger the userexit, then you can put a breakpoint at the statement before CALL CUSTOMER-FUNCTION and see if you get there. If CALL CUSTOMER-FUNCTION is not executed, then try do de-activate the CMOD project and activate it again. This usually helps.
For the document header I can provide you just anaother example which works for us:
[code]  ls_documentheader-obj_type              = 'BKPFF'.
  ls_documentheader-obj_sys               = lv_logsys.
  ls_documentheader-obj_key               = '$'.
  ls_documentheader-username              = sy-uname.
  ls_documentheader-header_txt            = 'Investment Notes reconciliation'(026).
  ls_documentheader-comp_code             = ps_alv_display-bukrs.
  ls_documentheader-doc_date              = p_bldat.
  ls_documentheader-fisc_year             = p_gjahr.
  ls_documentheader-pstng_date            = p_budat.
  ls_documentheader-fis_period            = p_bper .
  ls_documentheader-doc_type              = p_blart.
[/code]
Hope this helps.
Regards,
Clemens