SAP BSANLY_ACTIVATION_STATUS_READ Function Module for Read the overall status information of the activation run









BSANLY_ACTIVATION_STATUS_READ is a standard bsanly activation status read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read the overall status information of the activation run 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 bsanly activation status read FM, simply by entering the name BSANLY_ACTIVATION_STATUS_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: BSANLY_ACTIVATION_API
Program Name: SAPLBSANLY_ACTIVATION_API
Main Program: SAPLBSANLY_ACTIVATION_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BSANLY_ACTIVATION_STATUS_READ 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 'BSANLY_ACTIVATION_STATUS_READ'"Read the overall status information of the activation run
  EXPORTING
*  I_BUNDLE =  "BI Content Bundle
*  I_RFCDEST =  "Logical Destination (Specified in Function Call)
*  I_ACTIVATION_DATE =  "Current Date of Application Server
*  I_ACTIVATION_TIME =  "Current Time of Application Server
*  I_ACTIVATION_USER =  "User Name

 IMPORTING
   ES_BCACT_STA =  "Activation Status for Content Bundles
   ET_BCACT_STA =  "Activation Status for Content Bundles
   ET_BCACT_SYS =  "Source Systems for Content Activation
   ET_BCACT_LOG =  "Activation Log for Content Bundles

EXCEPTIONS
   ILLEGAL_SELECTION = 1
.



IMPORTING Parameters details for BSANLY_ACTIVATION_STATUS_READ

I_BUNDLE - BI Content Bundle

Data type: BS_ANLY_CONT_BUNDLE
Optional: Yes
Call by Reference: Yes

I_RFCDEST - Logical Destination (Specified in Function Call)

Data type: RFCDEST
Optional: Yes
Call by Reference: Yes

I_ACTIVATION_DATE - Current Date of Application Server

Data type: SYDATUM
Optional: Yes
Call by Reference: Yes

I_ACTIVATION_TIME - Current Time of Application Server

Data type: SYUZEIT
Optional: Yes
Call by Reference: Yes

I_ACTIVATION_USER - User Name

Data type: SYUNAME
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BSANLY_ACTIVATION_STATUS_READ

ES_BCACT_STA - Activation Status for Content Bundles

Data type: BSANLY_BCACT_STA
Optional: No
Call by Reference: Yes

ET_BCACT_STA - Activation Status for Content Bundles

Data type: BSANLY_T_BCACT_STA
Optional: No
Call by Reference: Yes

ET_BCACT_SYS - Source Systems for Content Activation

Data type: BSANLY_T_BCACT_SYS
Optional: No
Call by Reference: Yes

ET_BCACT_LOG - Activation Log for Content Bundles

Data type: BSANLY_T_BCACT_LOG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ILLEGAL_SELECTION - Selection not allowed

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BSANLY_ACTIVATION_STATUS_READ 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_i_bundle  TYPE BS_ANLY_CONT_BUNDLE, "   
lv_es_bcact_sta  TYPE BSANLY_BCACT_STA, "   
lv_illegal_selection  TYPE BSANLY_BCACT_STA, "   
lv_i_rfcdest  TYPE RFCDEST, "   
lv_et_bcact_sta  TYPE BSANLY_T_BCACT_STA, "   
lv_et_bcact_sys  TYPE BSANLY_T_BCACT_SYS, "   
lv_i_activation_date  TYPE SYDATUM, "   
lv_et_bcact_log  TYPE BSANLY_T_BCACT_LOG, "   
lv_i_activation_time  TYPE SYUZEIT, "   
lv_i_activation_user  TYPE SYUNAME. "   

  CALL FUNCTION 'BSANLY_ACTIVATION_STATUS_READ'  "Read the overall status information of the activation run
    EXPORTING
         I_BUNDLE = lv_i_bundle
         I_RFCDEST = lv_i_rfcdest
         I_ACTIVATION_DATE = lv_i_activation_date
         I_ACTIVATION_TIME = lv_i_activation_time
         I_ACTIVATION_USER = lv_i_activation_user
    IMPORTING
         ES_BCACT_STA = lv_es_bcact_sta
         ET_BCACT_STA = lv_et_bcact_sta
         ET_BCACT_SYS = lv_et_bcact_sys
         ET_BCACT_LOG = lv_et_bcact_log
    EXCEPTIONS
        ILLEGAL_SELECTION = 1
. " BSANLY_ACTIVATION_STATUS_READ




ABAP code using 7.40 inline data declarations to call FM BSANLY_ACTIVATION_STATUS_READ

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!