FKK_BIX_BIT_REVERSE_CHECK_CC SAP Function module

FKK_BIX_BIT_REVERSE_CHECK_CC is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FKK_BIX_BIT_REVERSE_CHECK_CC into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FKKBIX_BIT_REVERSE
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM FKK_BIX_BIT_REVERSE_CHECK_CC - FKK BIX BIT REVERSE CHECK CC

CALL FUNCTION 'FKK_BIX_BIT_REVERSE_CHECK_CC' "
  EXPORTING
    i_srctaid_from =            " srctaid_kk    Source Transaction ID
    i_srctaid_to =              " srctaid_kk    Source Transaction ID
*   i_srctatype =               " srctatype_kk  Source Transaction Type
    i_bitrev_frdate =           " bitrev_frdate_kk  Reversal Start Date of Billable Item Package
    i_vtref =                   " vtref_kk      Reference Specifications from Contract
    i_subap =                   " subap_kk      Subapplication in Contract Accounts Receivable and Payable
  IMPORTING
    e_bitrev_permit =           " xfeld         Checkbox
    e_bitrev_permit_frdate =    " bitrev_frdate_kk  Reversal Start Date of Billable Item Package
    e_bitrev_permit_frtime =    " bitrev_frtime_kk  Reversal Start Time of Billable Item Package
    e_bitrev_permit_srctaid_from =   " srctaid_kk  Source Transaction ID
  TABLES
    t_vkont =                   " fkkbix_vkont  Contract Account
  EXCEPTIONS
    NO_AUTHORIZATION = 1        "               No Authorization for Reversing Billable Items
    .  "  FKK_BIX_BIT_REVERSE_CHECK_CC

ABAP code example for Function Module FKK_BIX_BIT_REVERSE_CHECK_CC

The ABAP code below is a full code listing to execute function module FKK_BIX_BIT_REVERSE_CHECK_CC including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_e_bitrev_permit  
 
 TYPE XFELD
,
ld_e_bitrev_permit_frdate  
 
 TYPE BITREV_FRDATE_KK
,
ld_e_bitrev_permit_frtime  
 
 TYPE BITREV_FRTIME_KK
,
ld_e_bitrev_permit_srctaid_from  
 
 TYPE SRCTAID_KK
,
it_t_vkont  
 
 TYPE STANDARD TABLE OF FKKBIX_VKONT,"TABLES PARAM
wa_t_vkont
 
 LIKE LINE OF it_t_vkont
.


DATA(ld_i_srctaid_from) = 'Check type of data required'.

DATA(ld_i_srctaid_to) = 'Check type of data required'.

DATA(ld_i_srctatype) = 'Check type of data required'.

DATA(ld_i_bitrev_frdate) = 'Check type of data required'.

DATA(ld_i_vtref) = 'Check type of data required'.

DATA(ld_i_subap) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_t_vkont to it_t_vkont.
.

CALL FUNCTION 'FKK_BIX_BIT_REVERSE_CHECK_CC'
  EXPORTING
    i_srctaid_from =             ld_i_srctaid_from
    i_srctaid_to =               ld_i_srctaid_to
*   i_srctatype =                ld_i_srctatype
    i_bitrev_frdate =            ld_i_bitrev_frdate
    i_vtref =                    ld_i_vtref
    i_subap =                    ld_i_subap
  IMPORTING
    e_bitrev_permit =            ld_e_bitrev_permit
    e_bitrev_permit_frdate =     ld_e_bitrev_permit_frdate
    e_bitrev_permit_frtime =     ld_e_bitrev_permit_frtime
    e_bitrev_permit_srctaid_from =    ld_e_bitrev_permit_srctaid_from
  TABLES
    t_vkont =                    it_t_vkont
  EXCEPTIONS
    NO_AUTHORIZATION =           1
    .  "  FKK_BIX_BIT_REVERSE_CHECK_CC

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_bitrev_permit
 
 TYPE XFELD ,
ld_i_srctaid_from
 
 TYPE SRCTAID_KK ,
it_t_vkont
 
 TYPE STANDARD TABLE OF FKKBIX_VKONT ,
wa_t_vkont
 
 LIKE LINE OF it_t_vkont,
ld_e_bitrev_permit_frdate
 
 TYPE BITREV_FRDATE_KK ,
ld_i_srctaid_to
 
 TYPE SRCTAID_KK ,
ld_e_bitrev_permit_frtime
 
 TYPE BITREV_FRTIME_KK ,
ld_i_srctatype
 
 TYPE SRCTATYPE_KK ,
ld_e_bitrev_permit_srctaid_from
 
 TYPE SRCTAID_KK ,
ld_i_bitrev_frdate
 
 TYPE BITREV_FRDATE_KK ,
ld_i_vtref
 
 TYPE VTREF_KK ,
ld_i_subap
 
 TYPE SUBAP_KK .


ld_i_srctaid_from = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_t_vkont to it_t_vkont.
ld_i_srctaid_to = 'Check type of data required'.
ld_i_srctatype = 'Check type of data required'.
ld_i_bitrev_frdate = 'Check type of data required'.
ld_i_vtref = 'Check type of data required'.
ld_i_subap = 'Check type of data required'.

SAP Documentation for FM FKK_BIX_BIT_REVERSE_CHECK_CC