SAP SAMPLE_PROCESS_00001820 Function Module for
SAMPLE_PROCESS_00001820 is a standard sample process 00001820 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 sample process 00001820 FM, simply by entering the name SAMPLE_PROCESS_00001820 into the relevant SAP transaction such as SE37 or SE38.
Function Group: BFFMSMPL3
Program Name: SAPLBFFMSMPL3
Main Program: SAPLBFFMSMPL3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SAMPLE_PROCESS_00001820 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 'SAMPLE_PROCESS_00001820'".
EXPORTING
* I_BSID = "Accounting: Secondary Index for Customers
* I_BSIK = "Accounting: Secondary index for vendors
I_KOART = "Account Type
* I_BUDAT = "Posting Date in the Document
* I_NEDAT = "Posting Date of the next Payment Run
* I_FDEBI = "'To' Due Date for Customer Items
* I_TRACE = "Trace
IMPORTING
E_NO_FREE_SELECTIONS = "
CHANGING
C_ZLSPR = "Payment block key
C_ZLSCH = "Payment Method
TABLES
* T_FLDTAB_1820 = "Transfer Free Selections to BTE 00001820 (F110)
IMPORTING Parameters details for SAMPLE_PROCESS_00001820
I_BSID - Accounting: Secondary Index for Customers
Data type: BSIDOptional: Yes
Call by Reference: Yes
I_BSIK - Accounting: Secondary index for vendors
Data type: BSIKOptional: Yes
Call by Reference: Yes
I_KOART - Account Type
Data type: BSEG-KOARTOptional: No
Call by Reference: Yes
I_BUDAT - Posting Date in the Document
Data type: F110C-BUDATOptional: Yes
Call by Reference: Yes
I_NEDAT - Posting Date of the next Payment Run
Data type: F110V-NEDATOptional: Yes
Call by Reference: Yes
I_FDEBI - 'To' Due Date for Customer Items
Data type: F110V-FDEBIOptional: Yes
Call by Reference: Yes
I_TRACE - Trace
Data type: TRCOPTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SAMPLE_PROCESS_00001820
E_NO_FREE_SELECTIONS -
Data type: COptional: No
Call by Reference: Yes
CHANGING Parameters details for SAMPLE_PROCESS_00001820
C_ZLSPR - Payment block key
Data type: BSEG-ZLSPROptional: No
Call by Reference: Yes
C_ZLSCH - Payment Method
Data type: BSEG-ZLSCHOptional: No
Call by Reference: Yes
TABLES Parameters details for SAMPLE_PROCESS_00001820
T_FLDTAB_1820 - Transfer Free Selections to BTE 00001820 (F110)
Data type: F110_FLDTAB_1820Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for SAMPLE_PROCESS_00001820 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_bsid | TYPE BSID, " | |||
| lv_c_zlspr | TYPE BSEG-ZLSPR, " | |||
| lt_t_fldtab_1820 | TYPE STANDARD TABLE OF F110_FLDTAB_1820, " | |||
| lv_e_no_free_selections | TYPE C, " | |||
| lv_i_bsik | TYPE BSIK, " | |||
| lv_c_zlsch | TYPE BSEG-ZLSCH, " | |||
| lv_i_koart | TYPE BSEG-KOART, " | |||
| lv_i_budat | TYPE F110C-BUDAT, " | |||
| lv_i_nedat | TYPE F110V-NEDAT, " | |||
| lv_i_fdebi | TYPE F110V-FDEBI, " | |||
| lv_i_trace | TYPE TRCOPT. " |
|   CALL FUNCTION 'SAMPLE_PROCESS_00001820' " |
| EXPORTING | ||
| I_BSID | = lv_i_bsid | |
| I_BSIK | = lv_i_bsik | |
| I_KOART | = lv_i_koart | |
| I_BUDAT | = lv_i_budat | |
| I_NEDAT | = lv_i_nedat | |
| I_FDEBI | = lv_i_fdebi | |
| I_TRACE | = lv_i_trace | |
| IMPORTING | ||
| E_NO_FREE_SELECTIONS | = lv_e_no_free_selections | |
| CHANGING | ||
| C_ZLSPR | = lv_c_zlspr | |
| C_ZLSCH | = lv_c_zlsch | |
| TABLES | ||
| T_FLDTAB_1820 | = lt_t_fldtab_1820 | |
| . " SAMPLE_PROCESS_00001820 | ||
ABAP code using 7.40 inline data declarations to call FM SAMPLE_PROCESS_00001820
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.| "SELECT single ZLSPR FROM BSEG INTO @DATA(ld_c_zlspr). | ||||
| "SELECT single ZLSCH FROM BSEG INTO @DATA(ld_c_zlsch). | ||||
| "SELECT single KOART FROM BSEG INTO @DATA(ld_i_koart). | ||||
| "SELECT single BUDAT FROM F110C INTO @DATA(ld_i_budat). | ||||
| "SELECT single NEDAT FROM F110V INTO @DATA(ld_i_nedat). | ||||
| "SELECT single FDEBI FROM F110V INTO @DATA(ld_i_fdebi). | ||||
Search for further information about these or an SAP related objects