SAP FICO_API_COMPONENT_RELEASE Function Module for









FICO_API_COMPONENT_RELEASE is a standard fico api component release SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for fico api component release FM, simply by entering the name FICO_API_COMPONENT_RELEASE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FICO_API
Program Name: SAPLFICO_API
Main Program: SAPLFICO_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FICO_API_COMPONENT_RELEASE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'FICO_API_COMPONENT_RELEASE'"
EXPORTING
I_LIST = "Condition List
* I_LANGU = SY-LANGU "Language Key
* IO_LOGGER = "
I_COMP = "Key for a Component
I_BUFFER = "Indicator for Buffering
I_APPL = "Application
* IO_CALLBACKS = "
* I_FLG_INUPDATETASK = 'X' "Boolean Variable
I_USEDUNTIL = "Used until
* I_MIN_VALID_FROM = G_CON_MINDATE "Minimum Value for Valid-From
* I_MAX_VALID_TO = G_CON_MAXDATE "Maximum Value for Valid-To

IMPORTING
E_T_CONDI_CD = "Table for Correspondence Tool
E_RC = "Return Value, Return Value After ABAP Statements
E_T_RETURN = "Return Table
.



IMPORTING Parameters details for FICO_API_COMPONENT_RELEASE

I_LIST - Condition List

Data type: FICO_ILIST
Optional: No
Call by Reference: Yes

I_LANGU - Language Key

Data type: SPRAS
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

IO_LOGGER -

Data type: IF_FICO_LOGGER
Optional: Yes
Call by Reference: Yes

I_COMP - Key for a Component

Data type: FICO_ICOMP
Optional: No
Call by Reference: Yes

I_BUFFER - Indicator for Buffering

Data type: FICO_FBUFFER
Optional: No
Call by Reference: Yes

I_APPL - Application

Data type: FICO_OAPPL
Optional: No
Call by Reference: Yes

IO_CALLBACKS -

Data type: IF_FICO_CALLBACKS
Optional: Yes
Call by Reference: Yes

I_FLG_INUPDATETASK - Boolean Variable

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_USEDUNTIL - Used until

Data type: FICO_DUSEDUNTIL
Optional: No
Call by Reference: Yes

I_MIN_VALID_FROM - Minimum Value for Valid-From

Data type: FICO_DVALIDFROM
Default: G_CON_MINDATE
Optional: Yes
Call by Reference: Yes

I_MAX_VALID_TO - Maximum Value for Valid-To

Data type: FICO_DVALIDTO
Default: G_CON_MAXDATE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FICO_API_COMPONENT_RELEASE

E_T_CONDI_CD - Table for Correspondence Tool

Data type: FICO_TAS_CD_CONDI
Optional: No
Call by Reference: Yes

E_RC - Return Value, Return Value After ABAP Statements

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

E_T_RETURN - Return Table

Data type: BAPIRET2_T
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FICO_API_COMPONENT_RELEASE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_i_list  TYPE FICO_ILIST, "   
lv_e_t_condi_cd  TYPE FICO_TAS_CD_CONDI, "   
lv_i_langu  TYPE SPRAS, "   SY-LANGU
lv_io_logger  TYPE IF_FICO_LOGGER, "   
lv_e_rc  TYPE SY-SUBRC, "   
lv_i_comp  TYPE FICO_ICOMP, "   
lv_i_buffer  TYPE FICO_FBUFFER, "   
lv_e_t_return  TYPE BAPIRET2_T, "   
lv_i_appl  TYPE FICO_OAPPL, "   
lv_io_callbacks  TYPE IF_FICO_CALLBACKS, "   
lv_i_flg_inupdatetask  TYPE XFELD, "   'X'
lv_i_useduntil  TYPE FICO_DUSEDUNTIL, "   
lv_i_min_valid_from  TYPE FICO_DVALIDFROM, "   G_CON_MINDATE
lv_i_max_valid_to  TYPE FICO_DVALIDTO. "   G_CON_MAXDATE

  CALL FUNCTION 'FICO_API_COMPONENT_RELEASE'  "
    EXPORTING
         I_LIST = lv_i_list
         I_LANGU = lv_i_langu
         IO_LOGGER = lv_io_logger
         I_COMP = lv_i_comp
         I_BUFFER = lv_i_buffer
         I_APPL = lv_i_appl
         IO_CALLBACKS = lv_io_callbacks
         I_FLG_INUPDATETASK = lv_i_flg_inupdatetask
         I_USEDUNTIL = lv_i_useduntil
         I_MIN_VALID_FROM = lv_i_min_valid_from
         I_MAX_VALID_TO = lv_i_max_valid_to
    IMPORTING
         E_T_CONDI_CD = lv_e_t_condi_cd
         E_RC = lv_e_rc
         E_T_RETURN = lv_e_t_return
. " FICO_API_COMPONENT_RELEASE




ABAP code using 7.40 inline data declarations to call FM FICO_API_COMPONENT_RELEASE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
DATA(ld_i_langu) = SY-LANGU.
 
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_e_rc).
 
 
 
 
 
 
DATA(ld_i_flg_inupdatetask) = 'X'.
 
 
DATA(ld_i_min_valid_from) = G_CON_MINDATE.
 
DATA(ld_i_max_valid_to) = G_CON_MAXDATE.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!