SAP FDT_BRS_GET_DEPLOYMENTS Function Module for Retrieve the deployments for a certain function









FDT_BRS_GET_DEPLOYMENTS is a standard fdt brs get deployments SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieve the deployments for a certain function 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 fdt brs get deployments FM, simply by entering the name FDT_BRS_GET_DEPLOYMENTS into the relevant SAP transaction such as SE37 or SE38.

Function Group: FDT_BRS_REMOTE_GENERATION
Program Name: SAPLFDT_BRS_REMOTE_GENERATION
Main Program: SAPLFDT_BRS_REMOTE_GENERATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function FDT_BRS_GET_DEPLOYMENTS 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 'FDT_BRS_GET_DEPLOYMENTS'"Retrieve the deployments for a certain function
  EXPORTING
*  IV_SERVICE_ID =  "Service ID
*  IV_VALID_FROM =  "Validity period start
*  IV_VALID_TO =  "Validity period end
*  IV_ONLY_APPL =  "ABAP_TRUE: Return only the application information
*  IV_ONLY_SERVICE =  "ABAP_TRUE: Return only the service information

 IMPORTING
   ET_DEPLOYMENT =  "Table with deployment data
   EV_SERVICE_COUNT =  "Number of different services
.



IMPORTING Parameters details for FDT_BRS_GET_DEPLOYMENTS

IV_SERVICE_ID - Service ID

Data type: FDT_UUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_VALID_FROM - Validity period start

Data type: TIMESTAMP
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_VALID_TO - Validity period end

Data type: TIMESTAMP
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_ONLY_APPL - ABAP_TRUE: Return only the application information

Data type: BOOLE_D
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_ONLY_SERVICE - ABAP_TRUE: Return only the service information

Data type: BOOLE_D
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FDT_BRS_GET_DEPLOYMENTS

ET_DEPLOYMENT - Table with deployment data

Data type: FDT_T_BRS_CC_0002
Optional: No
Call by Reference: No ( called with pass by value option)

EV_SERVICE_COUNT - Number of different services

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FDT_BRS_GET_DEPLOYMENTS 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_et_deployment  TYPE FDT_T_BRS_CC_0002, "   
lv_iv_service_id  TYPE FDT_UUID, "   
lv_iv_valid_from  TYPE TIMESTAMP, "   
lv_ev_service_count  TYPE I, "   
lv_iv_valid_to  TYPE TIMESTAMP, "   
lv_iv_only_appl  TYPE BOOLE_D, "   
lv_iv_only_service  TYPE BOOLE_D. "   

  CALL FUNCTION 'FDT_BRS_GET_DEPLOYMENTS'  "Retrieve the deployments for a certain function
    EXPORTING
         IV_SERVICE_ID = lv_iv_service_id
         IV_VALID_FROM = lv_iv_valid_from
         IV_VALID_TO = lv_iv_valid_to
         IV_ONLY_APPL = lv_iv_only_appl
         IV_ONLY_SERVICE = lv_iv_only_service
    IMPORTING
         ET_DEPLOYMENT = lv_et_deployment
         EV_SERVICE_COUNT = lv_ev_service_count
. " FDT_BRS_GET_DEPLOYMENTS




ABAP code using 7.40 inline data declarations to call FM FDT_BRS_GET_DEPLOYMENTS

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!