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

Function SO_KPRO_DECIDE 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 'SO_KPRO_DECIDE'".
EXPORTING
OBJTP = "Object Type
FILE_EXT = "File extension for PC application
* OBJHEAD = "Objcont and Objhead as Table Type
IMPORTING
PUT_INTO_KPRO = "
IMPORTING Parameters details for SO_KPRO_DECIDE
OBJTP - Object Type
Data type: SOOD-OBJTPOptional: No
Call by Reference: Yes
FILE_EXT - File extension for PC application
Data type: SOOD-FILE_EXTOptional: No
Call by Reference: Yes
OBJHEAD - Objcont and Objhead as Table Type
Data type: SOLI_TABOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SO_KPRO_DECIDE
PUT_INTO_KPRO -
Data type: SONV-FLAGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SO_KPRO_DECIDE 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_objtp | TYPE SOOD-OBJTP, " | |||
| lv_put_into_kpro | TYPE SONV-FLAG, " | |||
| lv_file_ext | TYPE SOOD-FILE_EXT, " | |||
| lv_objhead | TYPE SOLI_TAB. " |
|   CALL FUNCTION 'SO_KPRO_DECIDE' " |
| EXPORTING | ||
| OBJTP | = lv_objtp | |
| FILE_EXT | = lv_file_ext | |
| OBJHEAD | = lv_objhead | |
| IMPORTING | ||
| PUT_INTO_KPRO | = lv_put_into_kpro | |
| . " SO_KPRO_DECIDE | ||
ABAP code using 7.40 inline data declarations to call FM SO_KPRO_DECIDE
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 OBJTP FROM SOOD INTO @DATA(ld_objtp). | ||||
| "SELECT single FLAG FROM SONV INTO @DATA(ld_put_into_kpro). | ||||
| "SELECT single FILE_EXT FROM SOOD INTO @DATA(ld_file_ext). | ||||
Search for further information about these or an SAP related objects