SAP SCCMS_SLD_DEPLOYED_OBJ Function Module for
SCCMS_SLD_DEPLOYED_OBJ is a standard sccms sld deployed obj 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 sccms sld deployed obj FM, simply by entering the name SCCMS_SLD_DEPLOYED_OBJ into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCCMS_SLD
Program Name: SAPLSCCMS_SLD
Main Program: SAPLSCCMS_SLD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SCCMS_SLD_DEPLOYED_OBJ 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 'SCCMS_SLD_DEPLOYED_OBJ'".
EXPORTING
* SLD_ALIAS = "
* FILTER = "
TABLES
T_DEPLOYED = "
T_ERROR = "
IMPORTING Parameters details for SCCMS_SLD_DEPLOYED_OBJ
SLD_ALIAS -
Data type: SLD_ALIASOptional: Yes
Call by Reference: No ( called with pass by value option)
FILTER -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SCCMS_SLD_DEPLOYED_OBJ
T_DEPLOYED -
Data type: SCCMSDEPLOYEDOptional: No
Call by Reference: Yes
T_ERROR -
Data type: SCCMSERRORTXTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SCCMS_SLD_DEPLOYED_OBJ 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_sld_alias | TYPE SLD_ALIAS, " | |||
| lt_t_deployed | TYPE STANDARD TABLE OF SCCMSDEPLOYED, " | |||
| lv_filter | TYPE STRING, " | |||
| lt_t_error | TYPE STANDARD TABLE OF SCCMSERRORTXT. " |
|   CALL FUNCTION 'SCCMS_SLD_DEPLOYED_OBJ' " |
| EXPORTING | ||
| SLD_ALIAS | = lv_sld_alias | |
| FILTER | = lv_filter | |
| TABLES | ||
| T_DEPLOYED | = lt_t_deployed | |
| T_ERROR | = lt_t_error | |
| . " SCCMS_SLD_DEPLOYED_OBJ | ||
ABAP code using 7.40 inline data declarations to call FM SCCMS_SLD_DEPLOYED_OBJ
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