SAP SAMPLING_STATUS_CHK Function Module for Active check of Payment Sampling Process
SAMPLING_STATUS_CHK is a standard sampling status chk SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Active check of Payment Sampling Process 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 sampling status chk FM, simply by entering the name SAMPLING_STATUS_CHK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMFG_SS
Program Name: SAPLFMFG_SS
Main Program: SAPLFMFG_SS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SAMPLING_STATUS_CHK 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 'SAMPLING_STATUS_CHK'"Active check of Payment Sampling Process.
EXPORTING
I_COMPANY_CODE = "Company Code
IMPORTING
E_SSP_ACTIV = "
IMPORTING Parameters details for SAMPLING_STATUS_CHK
I_COMPANY_CODE - Company Code
Data type: BKPF-BUKRSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for SAMPLING_STATUS_CHK
E_SSP_ACTIV -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SAMPLING_STATUS_CHK 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_e_ssp_activ | TYPE STRING, " | |||
| lv_i_company_code | TYPE BKPF-BUKRS. " |
|   CALL FUNCTION 'SAMPLING_STATUS_CHK' "Active check of Payment Sampling Process |
| EXPORTING | ||
| I_COMPANY_CODE | = lv_i_company_code | |
| IMPORTING | ||
| E_SSP_ACTIV | = lv_e_ssp_activ | |
| . " SAMPLING_STATUS_CHK | ||
ABAP code using 7.40 inline data declarations to call FM SAMPLING_STATUS_CHK
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 BUKRS FROM BKPF INTO @DATA(ld_i_company_code). | ||||
Search for further information about these or an SAP related objects