SAP SLS_CHECK_IOASGN Function Module for Check the existance of a record in table sls_ioasgn
SLS_CHECK_IOASGN is a standard sls check ioasgn SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check the existance of a record in table sls_ioasgn 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 sls check ioasgn FM, simply by entering the name SLS_CHECK_IOASGN into the relevant SAP transaction such as SE37 or SE38.
Function Group: SLS3
Program Name: SAPLSLS3
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SLS_CHECK_IOASGN 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 'SLS_CHECK_IOASGN'"Check the existance of a record in table sls_ioasgn.
EXPORTING
P_FUNC = "
IMPORTING
RETURN = "
TABLES
P_IOASGN = "
IMPORTING Parameters details for SLS_CHECK_IOASGN
P_FUNC -
Data type: SLS_FUNCOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SLS_CHECK_IOASGN
RETURN -
Data type: SLS_RETURNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SLS_CHECK_IOASGN
P_IOASGN -
Data type: SLS_IOASGNOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SLS_CHECK_IOASGN 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_p_func | TYPE SLS_FUNC, " | |||
| lv_return | TYPE SLS_RETURN, " | |||
| lt_p_ioasgn | TYPE STANDARD TABLE OF SLS_IOASGN. " |
|   CALL FUNCTION 'SLS_CHECK_IOASGN' "Check the existance of a record in table sls_ioasgn |
| EXPORTING | ||
| P_FUNC | = lv_p_func | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| P_IOASGN | = lt_p_ioasgn | |
| . " SLS_CHECK_IOASGN | ||
ABAP code using 7.40 inline data declarations to call FM SLS_CHECK_IOASGN
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