SAP SIN_SET_COUNTER_SO Function Module for
SIN_SET_COUNTER_SO is a standard sin set counter so 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 sin set counter so FM, simply by entering the name SIN_SET_COUNTER_SO into the relevant SAP transaction such as SE37 or SE38.
Function Group: SIOWP2
Program Name: SAPLSIOWP2
Main Program: SAPLSIOWP2
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SIN_SET_COUNTER_SO 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 'SIN_SET_COUNTER_SO'".
EXPORTING
I_OWNER = "
* I_FOLRG = 'I' "
IMPORTING
E_CHANGES = "
TABLES
CT_COUNTER = "
IMPORTING Parameters details for SIN_SET_COUNTER_SO
I_OWNER -
Data type: SY-UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_FOLRG -
Data type: SIN_FOLRGDefault: 'I'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SIN_SET_COUNTER_SO
E_CHANGES -
Data type: SIN_FLAGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SIN_SET_COUNTER_SO
CT_COUNTER -
Data type: SIN_S_CNTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SIN_SET_COUNTER_SO 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_owner | TYPE SY-UNAME, " | |||
| lv_e_changes | TYPE SIN_FLAG, " | |||
| lt_ct_counter | TYPE STANDARD TABLE OF SIN_S_CNT, " | |||
| lv_i_folrg | TYPE SIN_FOLRG. " 'I' |
|   CALL FUNCTION 'SIN_SET_COUNTER_SO' " |
| EXPORTING | ||
| I_OWNER | = lv_i_owner | |
| I_FOLRG | = lv_i_folrg | |
| IMPORTING | ||
| E_CHANGES | = lv_e_changes | |
| TABLES | ||
| CT_COUNTER | = lt_ct_counter | |
| . " SIN_SET_COUNTER_SO | ||
ABAP code using 7.40 inline data declarations to call FM SIN_SET_COUNTER_SO
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 UNAME FROM SY INTO @DATA(ld_i_owner). | ||||
| DATA(ld_i_folrg) | = 'I'. | |||
Search for further information about these or an SAP related objects