Validation for a extension field in the BAPI ( BAPI_ACC_DOCUMENT_CHECK)

Question

Hi,
I am working on an in terface for upload of data in journal ledger(FB50)
Actually i need to validate a field which has been included in transaction FB50 as an enhancement based on customer need .
a function module was created as suggested in note 487722 earlier but now we require to validate that field(transaction type) as i am using this BAPI in an interface for journal ledger posting FB50 for data validation of the file data.
this field has been populated as a part of the extension parameter in the bapi -
(( BAPI_ACC_DOCUMENT_CHECK)
field values for this field have been passed in the business transaction.
but i am not sure where to code the validation for this field .
could anybody suggest if we need to do it in include ZXACCU15 .
if so then how do we populate the values for the return parameter.
i am post ing document using IDOC and need to generate the for the errors generated.
it already shows for all the standard fields of the transaction.
Its a bit urgent,
help wud be appreciated
jy

Answer 1

Hello Jy
The following coding shows how to evaluate the existence of the transaction type in table T856 and how to create the corresponding BAPI message (using function module <b>BALW_BAPIRETURN_GET2</b>):
*& Report  ZUS_SDN_BAPIRETURN_GET2
REPORT  zus_sdn_bapireturn_get2.
START-OF-SELECTION.
  " Call BTE function within BAPI (actually OPEN_FI_PERFORM_RWBAPI01_P
  " calls the z-function module)
**  CALL FUNCTION 'Z_FI_INTERFACE_RWBAPI01'
**    TABLES
**      c_accit           =
**      c_acccr           =
**      c_return          =
**      c_extension       =
**      c_accwt           =
**    changing
**      c_acchd           =
  " Coding within your BTE function module:
  DATA:
    ls_return    TYPE bapiret2.
* transaction type
  READ TABLE it_accit INTO ls_accit
       WITH KEY posnr = ld_posnr.
  CHECK ( sy-subrc EQ 0 ).
  ld_tabix = sy-tabix.
  ls_accit-posnr = ld_posnr.
  ls_accit-rmvct = ls_bapi_extension-field3.
  MODIFY it_accit FROM ls_accit INDEX ld_tabix.
" Validate existence of transaction type
  SELECT SINGLE * FROM  t856 into ls_t856
         WHERE  trtyp  = ls_accit-rmvct.
  if ( syst-subrc ne 0 ).
    " Note: the following IF condition looks apparently strange yet its primary
    "         use is to ensure that the Where-Used-List for message 014(GC)
    "         will find our function module
    if 1 = 2.  MESSAGE e014(gc) WITH ls_accit-rmvct.  endif.
*   Transaction type & is not defined
    clear: ls_return.
    ls_return-message_v1 = ls_accit-rmvct.  " type conversion
    CALL FUNCTION 'BALW_BAPIRETURN_GET2'
      EXPORTING
        type             = 'E'
        cl               = 'GC'
        number           = '814'
        PAR1             = ls_return-message_v1
*       PAR2             = ' '
*       PAR3             = ' '
*       PAR4             = ' '
*       LOG_NO           = ' '
*       LOG_MSG_NO       = ' '
*       PARAMETER        = ' '
*       ROW              = 0      " ld_tabix
*       FIELD            = ' '    " RMVCT
      IMPORTING
        RETURN           = ls_return.
    APPEND ls_return TO c_return.
  ENDIF.
END-OF-SELECTION.
The advantage of using the function module over directly filling the BAPIRET2 message variable is that the function module generated the message text (field BAPIRET2-message = 'Transaction type '<type>' is not defined').
Regards
  Uwe