SAP AD_CHECK_SO Function Module for NOTRANSL: Check for single material proposal
AD_CHECK_SO is a standard ad check so SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Check for single material proposal 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 ad check so FM, simply by entering the name AD_CHECK_SO into the relevant SAP transaction such as SE37 or SE38.
Function Group: SPCWF
Program Name: SAPLSPCWF
Main Program: SAPLSPCWF
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function AD_CHECK_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 'AD_CHECK_SO'"NOTRANSL: Check for single material proposal.
EXPORTING
I_VBELN = "Sales Document
INITIATOR = "Initiator of workflow instance
IMPORTING
RESULT = "Generic Type
IMPORTING Parameters details for AD_CHECK_SO
I_VBELN - Sales Document
Data type: VBAK-VBELNOptional: No
Call by Reference: No ( called with pass by value option)
INITIATOR - Initiator of workflow instance
Data type: WFSYST-INITIATOROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for AD_CHECK_SO
RESULT - Generic Type
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AD_CHECK_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_result | TYPE C, " | |||
| lv_i_vbeln | TYPE VBAK-VBELN, " | |||
| lv_initiator | TYPE WFSYST-INITIATOR. " |
|   CALL FUNCTION 'AD_CHECK_SO' "NOTRANSL: Check for single material proposal |
| EXPORTING | ||
| I_VBELN | = lv_i_vbeln | |
| INITIATOR | = lv_initiator | |
| IMPORTING | ||
| RESULT | = lv_result | |
| . " AD_CHECK_SO | ||
ABAP code using 7.40 inline data declarations to call FM AD_CHECK_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 VBELN FROM VBAK INTO @DATA(ld_i_vbeln). | ||||
| "SELECT single INITIATOR FROM WFSYST INTO @DATA(ld_initiator). | ||||
Search for further information about these or an SAP related objects