SAP FKK_SAMPLE_3808 Function Module for









FKK_SAMPLE_3808 is a standard fkk sample 3808 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 fkk sample 3808 FM, simply by entering the name FKK_SAMPLE_3808 into the relevant SAP transaction such as SE37 or SE38.

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



Function FKK_SAMPLE_3808 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 'FKK_SAMPLE_3808'"
  EXPORTING
   I_RECEIVER =  "Receiver ID of Systems Connected
*  I_MODE =  "' ' Standard Mode, Error Mode 'X'
   IS_HEADER_INFO =  "Header Information for Business Partner
   IT_OPEN_ITEM =  "Outbound Interface: Open Item Information
   IT_CLEARING_ITEM =  "Outbound Interface: Information for Cleard Items
   IT_PAYMENT_ITEM =  "Outbound Interface: Payment Information

CHANGING
   ES_XI_DEBTOR_PARTY =  "XI: DebtorParty
   ET_XI_OPEN_ITEM =  "XI: OpenItem
   ET_XI_CLEARING_ITEM =  "XI: ClearingItem
   ET_XI_PAYMENT_ITEM =  "XI: PaymentItem
.



IMPORTING Parameters details for FKK_SAMPLE_3808

I_RECEIVER - Receiver ID of Systems Connected

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

I_MODE - SPACE Standard Mode, Error Mode 'X'

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

IS_HEADER_INFO - Header Information for Business Partner

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

IT_OPEN_ITEM - Outbound Interface: Open Item Information

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

IT_CLEARING_ITEM - Outbound Interface: Information for Cleard Items

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

IT_PAYMENT_ITEM - Outbound Interface: Payment Information

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

CHANGING Parameters details for FKK_SAMPLE_3808

ES_XI_DEBTOR_PARTY - XI: DebtorParty

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

ET_XI_OPEN_ITEM - XI: OpenItem

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

ET_XI_CLEARING_ITEM - XI: ClearingItem

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

ET_XI_PAYMENT_ITEM - XI: PaymentItem

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

Copy and paste ABAP code example for FKK_SAMPLE_3808 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_receiver  TYPE RCVER_KK, "   
lv_es_xi_debtor_party  TYPE FKKOI_PARTY, "   
lv_i_mode  TYPE XFLAG, "   
lv_et_xi_open_item  TYPE FKKOI_OPEN_ITEM_TAB, "   
lv_is_header_info  TYPE FKKOI_HEADER_INFO, "   
lv_et_xi_clearing_item  TYPE FKKOI_CLEARING_ITEM_TAB, "   
lv_it_open_item  TYPE FKKOI_OPEN_ITEM_T, "   
lv_et_xi_payment_item  TYPE FKKOI_PAYMENT_ITEM_TAB, "   
lv_it_clearing_item  TYPE FKKOI_CLEARED_ITEM_T, "   
lv_it_payment_item  TYPE FKKOI_PAYMENT_INFO_T. "   

  CALL FUNCTION 'FKK_SAMPLE_3808'  "
    EXPORTING
         I_RECEIVER = lv_i_receiver
         I_MODE = lv_i_mode
         IS_HEADER_INFO = lv_is_header_info
         IT_OPEN_ITEM = lv_it_open_item
         IT_CLEARING_ITEM = lv_it_clearing_item
         IT_PAYMENT_ITEM = lv_it_payment_item
    CHANGING
         ES_XI_DEBTOR_PARTY = lv_es_xi_debtor_party
         ET_XI_OPEN_ITEM = lv_et_xi_open_item
         ET_XI_CLEARING_ITEM = lv_et_xi_clearing_item
         ET_XI_PAYMENT_ITEM = lv_et_xi_payment_item
. " FKK_SAMPLE_3808




ABAP code using 7.40 inline data declarations to call FM FKK_SAMPLE_3808

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!