SAP FKK_SAMPLE_2419 Function Module for Customer-Specific BPITEM: Segment Processing









FKK_SAMPLE_2419 is a standard fkk sample 2419 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Customer-Specific BPITEM: Segment Processing processing and below is the pattern details for this FM, 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 2419 FM, simply by entering the name FKK_SAMPLE_2419 into the relevant SAP transaction such as SE37 or SE38.

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



Function FKK_SAMPLE_2419 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_2419'"Customer-Specific BPITEM: Segment Processing
  EXPORTING
   X_IDOC_CONTRL =  "Control Record (IDoc)
   X_IDOC_DATA =  "Data Record (IDoc)
   X_SEGNAME =  "Segment Type
   X_FKKKO =  "Header Data for Open Item Accounting Document

 IMPORTING
   Y_POSID =  "FKKIDOC Open Item Transfer: External Item IDs
   Y_MWSKZ =  "Tax Code
   Y_PYMET =  "

CHANGING
   Y_FKKOP =  "Business Partner Items in Contract Account Document

TABLES
   T_FKKOPREL =  "Object Relations for DFKKKO and DFKKOP

EXCEPTIONS
   TYPE_CONVERSION_ERROR = 1
.



IMPORTING Parameters details for FKK_SAMPLE_2419

X_IDOC_CONTRL - Control Record (IDoc)

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

X_IDOC_DATA - Data Record (IDoc)

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

X_SEGNAME - Segment Type

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

X_FKKKO - Header Data for Open Item Accounting Document

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

EXPORTING Parameters details for FKK_SAMPLE_2419

Y_POSID - FKKIDOC Open Item Transfer: External Item IDs

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

Y_MWSKZ - Tax Code

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

Y_PYMET -

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

CHANGING Parameters details for FKK_SAMPLE_2419

Y_FKKOP - Business Partner Items in Contract Account Document

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

TABLES Parameters details for FKK_SAMPLE_2419

T_FKKOPREL - Object Relations for DFKKKO and DFKKOP

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

EXCEPTIONS details

TYPE_CONVERSION_ERROR - Error during Type Conversion

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

Copy and paste ABAP code example for FKK_SAMPLE_2419 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_y_fkkop  TYPE FKKOP, "   
lv_y_posid  TYPE FKK_TOI_POS_ID, "   
lt_t_fkkoprel  TYPE STANDARD TABLE OF FKKOPREL, "   
lv_x_idoc_contrl  TYPE EDIDC, "   
lv_type_conversion_error  TYPE EDIDC, "   
lv_y_mwskz  TYPE MWSKZ, "   
lv_x_idoc_data  TYPE EDIDD, "   
lv_y_pymet  TYPE EXT_PYMET_KK, "   
lv_x_segname  TYPE EDILSEGTYP, "   
lv_x_fkkko  TYPE FKKKO. "   

  CALL FUNCTION 'FKK_SAMPLE_2419'  "Customer-Specific BPITEM: Segment Processing
    EXPORTING
         X_IDOC_CONTRL = lv_x_idoc_contrl
         X_IDOC_DATA = lv_x_idoc_data
         X_SEGNAME = lv_x_segname
         X_FKKKO = lv_x_fkkko
    IMPORTING
         Y_POSID = lv_y_posid
         Y_MWSKZ = lv_y_mwskz
         Y_PYMET = lv_y_pymet
    CHANGING
         Y_FKKOP = lv_y_fkkop
    TABLES
         T_FKKOPREL = lt_t_fkkoprel
    EXCEPTIONS
        TYPE_CONVERSION_ERROR = 1
. " FKK_SAMPLE_2419




ABAP code using 7.40 inline data declarations to call FM FKK_SAMPLE_2419

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!