SAP DISUB_CHECK_CHANGE_SC_TYPE Function Module for Check change of type of subcontracting
DISUB_CHECK_CHANGE_SC_TYPE is a standard disub check change sc type 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 change of type of subcontracting 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 disub check change sc type FM, simply by entering the name DISUB_CHECK_CHANGE_SC_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: DI_SUBCON_08
Program Name: SAPLDI_SUBCON_08
Main Program: SAPLDI_SUBCON_08
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DISUB_CHECK_CHANGE_SC_TYPE 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 'DISUB_CHECK_CHANGE_SC_TYPE'"Check change of type of subcontracting.
EXPORTING
I_EBELP = "Purchasing document item
I_EBELN = "Purchasing Document Header
SERRU_PAI = "Type of subcontracting
IMPORTING Parameters details for DISUB_CHECK_CHANGE_SC_TYPE
I_EBELP - Purchasing document item
Data type: EKPO-EBELPOptional: No
Call by Reference: Yes
I_EBELN - Purchasing Document Header
Data type: EKKO-EBELNOptional: No
Call by Reference: Yes
SERRU_PAI - Type of subcontracting
Data type: EKPO-SERRUOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for DISUB_CHECK_CHANGE_SC_TYPE 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_ebelp | TYPE EKPO-EBELP, " | |||
| lv_i_ebeln | TYPE EKKO-EBELN, " | |||
| lv_serru_pai | TYPE EKPO-SERRU. " |
|   CALL FUNCTION 'DISUB_CHECK_CHANGE_SC_TYPE' "Check change of type of subcontracting |
| EXPORTING | ||
| I_EBELP | = lv_i_ebelp | |
| I_EBELN | = lv_i_ebeln | |
| SERRU_PAI | = lv_serru_pai | |
| . " DISUB_CHECK_CHANGE_SC_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM DISUB_CHECK_CHANGE_SC_TYPE
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 EBELP FROM EKPO INTO @DATA(ld_i_ebelp). | ||||
| "SELECT single EBELN FROM EKKO INTO @DATA(ld_i_ebeln). | ||||
| "SELECT single SERRU FROM EKPO INTO @DATA(ld_serru_pai). | ||||
Search for further information about these or an SAP related objects