SAP FDT_BRS_SAVE_DEPLOYMENT Function Module for Check whether a new assembly of the classes is needed









FDT_BRS_SAVE_DEPLOYMENT is a standard fdt brs save deployment 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 whether a new assembly of the classes is needed 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 save deployment FM, simply by entering the name FDT_BRS_SAVE_DEPLOYMENT 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_SAVE_DEPLOYMENT 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_SAVE_DEPLOYMENT'"Check whether a new assembly of the classes is needed
  EXPORTING
   IV_SERVICE_ID =  "Service ID
   IS_SERVICE_INFO =  "Information about a service (Name + Description)
*  IV_NON_PRODUCTIVE_MODE = ABAP_FALSE "Save the deployment in the non productive db tables
*  IV_BLOB =  "Deployment BLOB
*  IV_APPLICATION_ID =  "Application ID
*  IV_EXIT_NAME =  "Exit name
*  IV_VALID_FROM =  "Desired Validity period start
*  IV_OVERWRITE_FUTURE = ABAP_TRUE "Overwrite Future Deployments
*  IV_NEW_ASSEMBLY = ABAP_TRUE "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
*  IV_ACTIVATE_CODE = ABAP_TRUE "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
   IS_CLASS =  "Metadata for ABAP OO class
   IS_CLASS_TRACE =  "Metadata for ABAP OO class - Trace
   IS_DEPL_ADMIN =  "Administrational Data for the Deployment
   IV_XML =  "XMl in a string format

 IMPORTING
   ET_MESSAGE =  "FDT: Table type for messages
   EV_ERROR =  "Has the generated calss a syntax error?
   EV_VALID_FROM =  "Actual valid from timestamp for the deployment
   EV_VALID_TO =  "Actual valid to timestamp the deployment

EXCEPTIONS
   DEPLOY_AUTH_FAILED = 1
.



IMPORTING Parameters details for FDT_BRS_SAVE_DEPLOYMENT

IV_SERVICE_ID - Service ID

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

IS_SERVICE_INFO - Information about a service (Name + Description)

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

IV_NON_PRODUCTIVE_MODE - Save the deployment in the non productive db tables

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

IV_BLOB - Deployment BLOB

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

IV_APPLICATION_ID - Application ID

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

IV_EXIT_NAME - Exit name

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

IV_VALID_FROM - Desired Validity period start

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

IV_OVERWRITE_FUTURE - Overwrite Future Deployments

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

IV_NEW_ASSEMBLY - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

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

IV_ACTIVATE_CODE - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

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

IS_CLASS - Metadata for ABAP OO class

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

IS_CLASS_TRACE - Metadata for ABAP OO class - Trace

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

IS_DEPL_ADMIN - Administrational Data for the Deployment

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

IV_XML - XMl in a string format

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

EXPORTING Parameters details for FDT_BRS_SAVE_DEPLOYMENT

ET_MESSAGE - FDT: Table type for messages

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

EV_ERROR - Has the generated calss a syntax error?

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

EV_VALID_FROM - Actual valid from timestamp for the deployment

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

EV_VALID_TO - Actual valid to timestamp the deployment

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

EXCEPTIONS details

DEPLOY_AUTH_FAILED - Authorization for deployment failed

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FDT_BRS_SAVE_DEPLOYMENT 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_message  TYPE FDT_T_MESSAGE, "   
lv_iv_service_id  TYPE FDT_UUID, "   
lv_deploy_auth_failed  TYPE FDT_UUID, "   
lv_is_service_info  TYPE FDT_S_SERVICE_INFO, "   
lv_iv_non_productive_mode  TYPE BOOLE_D, "   ABAP_FALSE
lv_iv_blob  TYPE STRING, "   
lv_iv_application_id  TYPE FDT_UUID, "   
lv_iv_exit_name  TYPE SEOCLSNAME, "   
lv_ev_error  TYPE BOOLE_D, "   
lv_iv_valid_from  TYPE TIMESTAMP, "   
lv_ev_valid_from  TYPE TIMESTAMP, "   
lv_iv_overwrite_future  TYPE BOOLE_D, "   ABAP_TRUE
lv_ev_valid_to  TYPE TIMESTAMP, "   
lv_iv_new_assembly  TYPE BOOLE_D, "   ABAP_TRUE
lv_iv_activate_code  TYPE BOOLE_D, "   ABAP_TRUE
lv_is_class  TYPE FDT_S_CLASS, "   
lv_is_class_trace  TYPE FDT_S_CLASS, "   
lv_is_depl_admin  TYPE FDT_S_DEPL_ADMIN, "   
lv_iv_xml  TYPE STRING. "   

  CALL FUNCTION 'FDT_BRS_SAVE_DEPLOYMENT'  "Check whether a new assembly of the classes is needed
    EXPORTING
         IV_SERVICE_ID = lv_iv_service_id
         IS_SERVICE_INFO = lv_is_service_info
         IV_NON_PRODUCTIVE_MODE = lv_iv_non_productive_mode
         IV_BLOB = lv_iv_blob
         IV_APPLICATION_ID = lv_iv_application_id
         IV_EXIT_NAME = lv_iv_exit_name
         IV_VALID_FROM = lv_iv_valid_from
         IV_OVERWRITE_FUTURE = lv_iv_overwrite_future
         IV_NEW_ASSEMBLY = lv_iv_new_assembly
         IV_ACTIVATE_CODE = lv_iv_activate_code
         IS_CLASS = lv_is_class
         IS_CLASS_TRACE = lv_is_class_trace
         IS_DEPL_ADMIN = lv_is_depl_admin
         IV_XML = lv_iv_xml
    IMPORTING
         ET_MESSAGE = lv_et_message
         EV_ERROR = lv_ev_error
         EV_VALID_FROM = lv_ev_valid_from
         EV_VALID_TO = lv_ev_valid_to
    EXCEPTIONS
        DEPLOY_AUTH_FAILED = 1
. " FDT_BRS_SAVE_DEPLOYMENT




ABAP code using 7.40 inline data declarations to call FM FDT_BRS_SAVE_DEPLOYMENT

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.

 
 
 
 
DATA(ld_iv_non_productive_mode) = ABAP_FALSE.
 
 
 
 
 
 
 
DATA(ld_iv_overwrite_future) = ABAP_TRUE.
 
 
DATA(ld_iv_new_assembly) = ABAP_TRUE.
 
DATA(ld_iv_activate_code) = ABAP_TRUE.
 
 
 
 
 


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!