SAP FCOM_RECEIVER_DERIVE Function Module for









FCOM_RECEIVER_DERIVE is a standard fcom receiver derive 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 fcom receiver derive FM, simply by entering the name FCOM_RECEIVER_DERIVE into the relevant SAP transaction such as SE37 or SE38.

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



Function FCOM_RECEIVER_DERIVE 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 'FCOM_RECEIVER_DERIVE'"
  EXPORTING
*  I_KOKRS =  "
*  IS_SENDER_FIELDS =  "
*  IS_DERIVE_FIELDS =  "
*  I_SR_FLAG =  "
*  I_VORGN =  "
*  I_UPDATE_DATE =  "
*  I_OBJNR_RECEIVER =  "
*  I_KSTAR_RECEIVER =  "
*  IS_PERIOD =  "
*  IS_COBL_RECEIVER =  "
*  IS_ALLOC_RECEIVER =  "
*  IS_OBJECT_INFO =  "

 IMPORTING
   ES_RECEIVER_FIELDS =  "

EXCEPTIONS
   INPUT_NOT_SUFFICIENT = 1    ERROR_OCCURRED = 2
.



IMPORTING Parameters details for FCOM_RECEIVER_DERIVE

I_KOKRS -

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

IS_SENDER_FIELDS -

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

IS_DERIVE_FIELDS -

Data type: FCOM_S_SUBKEY_ACTIVE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SR_FLAG -

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

I_VORGN -

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

I_UPDATE_DATE -

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

I_OBJNR_RECEIVER -

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

I_KSTAR_RECEIVER -

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

IS_PERIOD -

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

IS_COBL_RECEIVER -

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

IS_ALLOC_RECEIVER -

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

IS_OBJECT_INFO -

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

EXPORTING Parameters details for FCOM_RECEIVER_DERIVE

ES_RECEIVER_FIELDS -

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

EXCEPTIONS details

INPUT_NOT_SUFFICIENT -

Data type:
Optional: No
Call by Reference: Yes

ERROR_OCCURRED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FCOM_RECEIVER_DERIVE 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_kokrs  TYPE KOKRS, "   
lv_es_receiver_fields  TYPE FCOM_S_SUBKEY2_FIELDS, "   
lv_input_not_sufficient  TYPE FCOM_S_SUBKEY2_FIELDS, "   
lv_is_sender_fields  TYPE FCOM_S_SUBKEY2_FIELDS, "   
lv_is_derive_fields  TYPE FCOM_S_SUBKEY_ACTIVE, "   
lv_i_sr_flag  TYPE C, "   
lv_i_vorgn  TYPE CO_VORGANG, "   
lv_error_occurred  TYPE CO_VORGANG, "   
lv_i_update_date  TYPE DATUM, "   
lv_i_objnr_receiver  TYPE J_OBJNR, "   
lv_i_kstar_receiver  TYPE KSTAR, "   
lv_is_period  TYPE PERIODS, "   
lv_is_cobl_receiver  TYPE COBL, "   
lv_is_alloc_receiver  TYPE KALC_VALRC, "   
lv_is_object_info  TYPE ANY. "   

  CALL FUNCTION 'FCOM_RECEIVER_DERIVE'  "
    EXPORTING
         I_KOKRS = lv_i_kokrs
         IS_SENDER_FIELDS = lv_is_sender_fields
         IS_DERIVE_FIELDS = lv_is_derive_fields
         I_SR_FLAG = lv_i_sr_flag
         I_VORGN = lv_i_vorgn
         I_UPDATE_DATE = lv_i_update_date
         I_OBJNR_RECEIVER = lv_i_objnr_receiver
         I_KSTAR_RECEIVER = lv_i_kstar_receiver
         IS_PERIOD = lv_is_period
         IS_COBL_RECEIVER = lv_is_cobl_receiver
         IS_ALLOC_RECEIVER = lv_is_alloc_receiver
         IS_OBJECT_INFO = lv_is_object_info
    IMPORTING
         ES_RECEIVER_FIELDS = lv_es_receiver_fields
    EXCEPTIONS
        INPUT_NOT_SUFFICIENT = 1
        ERROR_OCCURRED = 2
. " FCOM_RECEIVER_DERIVE




ABAP code using 7.40 inline data declarations to call FM FCOM_RECEIVER_DERIVE

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!