SAP BSANLY_BCCREP_SEARCH Function Module for Search the BCC Repository
BSANLY_BCCREP_SEARCH is a standard bsanly bccrep search SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Search the BCC Repository 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 bccrep search FM, simply by entering the name BSANLY_BCCREP_SEARCH 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_BCCREP_SEARCH 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_BCCREP_SEARCH'"Search the BCC Repository.
EXPORTING
* I_BUS_CATEGORY = "Business Category
* I_REMOTE_CONTENT = RS_C_TRUE "Boolean
* I_DESCRIP = "Long description
* I_RFCDEST = "Logical Destination (Specified in Function Call)
* I_STATUS = "Activation Status
* I_ACTIVATED_FROM = "
* I_ACTIVATED_TO = "
* I_ACTIVATED_BY = "User Name
* I_DEVCLASS = "Package
* I_COMPONENT = "Software Component
* I_SAPRELEASE = "SAP Release
* I_BUNDLE = "BI Content Bundle
* I_EXTRELEASE = "Support Package Level of a Software Component
* I_LANGU = "Language Key of Current Text Environment
* I_AUTHOR = "User Name
* I_DATE_FROM = "
* I_DATE_TO = "
* I_OBJECT = "Object Type
* I_OBJ_NAME = "Object Name in Object Directory
* I_LOCAL_CONTENT = RS_C_TRUE "Boolean
IMPORTING
ET_BCCREP_C = "Assignment of Content Bundles to Business Categories
IMPORTING Parameters details for BSANLY_BCCREP_SEARCH
I_BUS_CATEGORY - Business Category
Data type: BS_ANLY_BUS_CATEGOptional: Yes
Call by Reference: Yes
I_REMOTE_CONTENT - Boolean
Data type: RS_BOOLDefault: RS_C_TRUE
Optional: Yes
Call by Reference: Yes
I_DESCRIP - Long description
Data type: RSTXTLGOptional: Yes
Call by Reference: Yes
I_RFCDEST - Logical Destination (Specified in Function Call)
Data type: RFCDESTOptional: Yes
Call by Reference: Yes
I_STATUS - Activation Status
Data type: BS_ANLY_ACT_STAOptional: Yes
Call by Reference: Yes
I_ACTIVATED_FROM -
Data type: DOptional: Yes
Call by Reference: Yes
I_ACTIVATED_TO -
Data type: DOptional: Yes
Call by Reference: Yes
I_ACTIVATED_BY - User Name
Data type: SYUNAMEOptional: Yes
Call by Reference: Yes
I_DEVCLASS - Package
Data type: DEVCLASSOptional: Yes
Call by Reference: Yes
I_COMPONENT - Software Component
Data type: DLVUNITOptional: Yes
Call by Reference: Yes
I_SAPRELEASE - SAP Release
Data type: SAPRELEASEOptional: Yes
Call by Reference: Yes
I_BUNDLE - BI Content Bundle
Data type: BS_ANLY_CONT_BUNDLEOptional: Yes
Call by Reference: Yes
I_EXTRELEASE - Support Package Level of a Software Component
Data type: SAPPATCHLVOptional: Yes
Call by Reference: Yes
I_LANGU - Language Key of Current Text Environment
Data type: SPRASOptional: Yes
Call by Reference: Yes
I_AUTHOR - User Name
Data type: SYUNAMEOptional: Yes
Call by Reference: Yes
I_DATE_FROM -
Data type: DOptional: Yes
Call by Reference: Yes
I_DATE_TO -
Data type: DOptional: Yes
Call by Reference: Yes
I_OBJECT - Object Type
Data type: TROBJTYPEOptional: Yes
Call by Reference: Yes
I_OBJ_NAME - Object Name in Object Directory
Data type: SOBJ_NAMEOptional: Yes
Call by Reference: Yes
I_LOCAL_CONTENT - Boolean
Data type: RS_BOOLDefault: RS_C_TRUE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BSANLY_BCCREP_SEARCH
ET_BCCREP_C - Assignment of Content Bundles to Business Categories
Data type: BSANLY_T_BCCREP_COptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BSANLY_BCCREP_SEARCH 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_bccrep_c | TYPE BSANLY_T_BCCREP_C, " | |||
| lv_i_bus_category | TYPE BS_ANLY_BUS_CATEG, " | |||
| lv_i_remote_content | TYPE RS_BOOL, " RS_C_TRUE | |||
| lv_i_descrip | TYPE RSTXTLG, " | |||
| lv_i_rfcdest | TYPE RFCDEST, " | |||
| lv_i_status | TYPE BS_ANLY_ACT_STA, " | |||
| lv_i_activated_from | TYPE D, " | |||
| lv_i_activated_to | TYPE D, " | |||
| lv_i_activated_by | TYPE SYUNAME, " | |||
| lv_i_devclass | TYPE DEVCLASS, " | |||
| lv_i_component | TYPE DLVUNIT, " | |||
| lv_i_saprelease | TYPE SAPRELEASE, " | |||
| lv_i_bundle | TYPE BS_ANLY_CONT_BUNDLE, " | |||
| lv_i_extrelease | TYPE SAPPATCHLV, " | |||
| lv_i_langu | TYPE SPRAS, " | |||
| lv_i_author | TYPE SYUNAME, " | |||
| lv_i_date_from | TYPE D, " | |||
| lv_i_date_to | TYPE D, " | |||
| lv_i_object | TYPE TROBJTYPE, " | |||
| lv_i_obj_name | TYPE SOBJ_NAME, " | |||
| lv_i_local_content | TYPE RS_BOOL. " RS_C_TRUE |
|   CALL FUNCTION 'BSANLY_BCCREP_SEARCH' "Search the BCC Repository |
| EXPORTING | ||
| I_BUS_CATEGORY | = lv_i_bus_category | |
| I_REMOTE_CONTENT | = lv_i_remote_content | |
| I_DESCRIP | = lv_i_descrip | |
| I_RFCDEST | = lv_i_rfcdest | |
| I_STATUS | = lv_i_status | |
| I_ACTIVATED_FROM | = lv_i_activated_from | |
| I_ACTIVATED_TO | = lv_i_activated_to | |
| I_ACTIVATED_BY | = lv_i_activated_by | |
| I_DEVCLASS | = lv_i_devclass | |
| I_COMPONENT | = lv_i_component | |
| I_SAPRELEASE | = lv_i_saprelease | |
| I_BUNDLE | = lv_i_bundle | |
| I_EXTRELEASE | = lv_i_extrelease | |
| I_LANGU | = lv_i_langu | |
| I_AUTHOR | = lv_i_author | |
| I_DATE_FROM | = lv_i_date_from | |
| I_DATE_TO | = lv_i_date_to | |
| I_OBJECT | = lv_i_object | |
| I_OBJ_NAME | = lv_i_obj_name | |
| I_LOCAL_CONTENT | = lv_i_local_content | |
| IMPORTING | ||
| ET_BCCREP_C | = lv_et_bccrep_c | |
| . " BSANLY_BCCREP_SEARCH | ||
ABAP code using 7.40 inline data declarations to call FM BSANLY_BCCREP_SEARCH
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_i_remote_content) | = RS_C_TRUE. | |||
| DATA(ld_i_local_content) | = RS_C_TRUE. | |||
Search for further information about these or an SAP related objects