SAP BBP_SC_APP_VALID_SOS_GET Function Module for
BBP_SC_APP_VALID_SOS_GET is a standard bbp sc app valid sos get 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 bbp sc app valid sos get FM, simply by entering the name BBP_SC_APP_VALID_SOS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_SC_APP
Program Name: SAPLBBP_SC_APP
Main Program: SAPLBBP_SC_APP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_SC_APP_VALID_SOS_GET 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 'BBP_SC_APP_VALID_SOS_GET'".
EXPORTING
IS_ITEM = "
IS_IMPORT = "
IS_GLOBAL = "
IS_HEADER = "
IMPORTING
ET_VALID_SOS = "
IMPORTING Parameters details for BBP_SC_APP_VALID_SOS_GET
IS_ITEM -
Data type: BBPS_SC_APP_ITEMOptional: No
Call by Reference: Yes
IS_IMPORT -
Data type: BBPS_SC_APP_IMPORTOptional: No
Call by Reference: Yes
IS_GLOBAL -
Data type: BBPS_SC_APP_GLOBALOptional: No
Call by Reference: Yes
IS_HEADER -
Data type: BBPS_SC_APP_HEADEROptional: No
Call by Reference: Yes
EXPORTING Parameters details for BBP_SC_APP_VALID_SOS_GET
ET_VALID_SOS -
Data type: BBPT_SC_APP_SOSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_SC_APP_VALID_SOS_GET 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_is_item | TYPE BBPS_SC_APP_ITEM, " | |||
| lv_et_valid_sos | TYPE BBPT_SC_APP_SOS, " | |||
| lv_is_import | TYPE BBPS_SC_APP_IMPORT, " | |||
| lv_is_global | TYPE BBPS_SC_APP_GLOBAL, " | |||
| lv_is_header | TYPE BBPS_SC_APP_HEADER. " |
|   CALL FUNCTION 'BBP_SC_APP_VALID_SOS_GET' " |
| EXPORTING | ||
| IS_ITEM | = lv_is_item | |
| IS_IMPORT | = lv_is_import | |
| IS_GLOBAL | = lv_is_global | |
| IS_HEADER | = lv_is_header | |
| IMPORTING | ||
| ET_VALID_SOS | = lv_et_valid_sos | |
| . " BBP_SC_APP_VALID_SOS_GET | ||
ABAP code using 7.40 inline data declarations to call FM BBP_SC_APP_VALID_SOS_GET
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