FICO_API_COMPONENT_RELEASE SAP Function module

FICO_API_COMPONENT_RELEASE 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 FICO_API_COMPONENT_RELEASE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FICO_API
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM FICO_API_COMPONENT_RELEASE - FICO API COMPONENT RELEASE

CALL FUNCTION 'FICO_API_COMPONENT_RELEASE' "
  EXPORTING
    i_list =                    " fico_ilist    Condition List
    i_comp =                    " fico_icomp    Key for a Component
    i_buffer =                  " fico_fbuffer  Indicator for Buffering
    i_appl =                    " fico_oappl    Application
*   io_callbacks =              " if_fico_callbacks
*   i_flg_inupdatetask = 'X'    " xfeld         Boolean Variable
    i_useduntil =               " fico_duseduntil  Used until
*   i_min_valid_from = G_CON_MINDATE  " fico_dvalidfrom  Minimum Value for Valid-From
*   i_max_valid_to = G_CON_MAXDATE  " fico_dvalidto  Maximum Value for Valid-To
*   i_langu = SY-LANGU          " spras         Language Key
*   io_logger =                 " if_fico_logger
  IMPORTING
    e_t_condi_cd =              " fico_tas_cd_condi  Table for Correspondence Tool
    e_rc =                      " sy-subrc      Return Value, Return Value After ABAP Statements
    e_t_return =                " bapiret2_t    Return Table
    .  "  FICO_API_COMPONENT_RELEASE

ABAP code example for Function Module FICO_API_COMPONENT_RELEASE

The ABAP code below is a full code listing to execute function module FICO_API_COMPONENT_RELEASE 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_t_condi_cd  
 
 TYPE FICO_TAS_CD_CONDI
,
ld_e_rc  
 
 TYPE SY-SUBRC
,
ld_e_t_return  
 
 TYPE BAPIRET2_T
.


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

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

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

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

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

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

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

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

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

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

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

CALL FUNCTION 'FICO_API_COMPONENT_RELEASE'
  EXPORTING
    i_list =                     ld_i_list
    i_comp =                     ld_i_comp
    i_buffer =                   ld_i_buffer
    i_appl =                     ld_i_appl
*   io_callbacks =               ld_io_callbacks
*   i_flg_inupdatetask =         ld_i_flg_inupdatetask
    i_useduntil =                ld_i_useduntil
*   i_min_valid_from =           ld_i_min_valid_from
*   i_max_valid_to =             ld_i_max_valid_to
*   i_langu =                    ld_i_langu
*   io_logger =                  ld_io_logger
  IMPORTING
    e_t_condi_cd =               ld_e_t_condi_cd
    e_rc =                       ld_e_rc
    e_t_return =                 ld_e_t_return
    .  "  FICO_API_COMPONENT_RELEASE

IF SY-SUBRC EQ 0.
  "All OK
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_t_condi_cd
 
 TYPE FICO_TAS_CD_CONDI ,
ld_i_list
 
 TYPE FICO_ILIST ,
ld_e_rc
 
 TYPE SY-SUBRC ,
ld_i_comp
 
 TYPE FICO_ICOMP ,
ld_e_t_return
 
 TYPE BAPIRET2_T ,
ld_i_buffer
 
 TYPE FICO_FBUFFER ,
ld_i_appl
 
 TYPE FICO_OAPPL ,
ld_io_callbacks
 
 TYPE IF_FICO_CALLBACKS ,
ld_i_flg_inupdatetask
 
 TYPE XFELD ,
ld_i_useduntil
 
 TYPE FICO_DUSEDUNTIL ,
ld_i_min_valid_from
 
 TYPE FICO_DVALIDFROM ,
ld_i_max_valid_to
 
 TYPE FICO_DVALIDTO ,
ld_i_langu
 
 TYPE SPRAS ,
ld_io_logger
 
 TYPE IF_FICO_LOGGER .


ld_i_list = 'Check type of data required'.
ld_i_comp = 'Check type of data required'.
ld_i_buffer = 'Check type of data required'.
ld_i_appl = 'Check type of data required'.
ld_io_callbacks = 'Check type of data required'.
ld_i_flg_inupdatetask = 'Check type of data required'.
ld_i_useduntil = 'Check type of data required'.
ld_i_min_valid_from = 'Check type of data required'.
ld_i_max_valid_to = 'Check type of data required'.
ld_i_langu = 'Check type of data required'.
ld_io_logger = 'Check type of data required'.