SAP RSBB_AGR_NAME_CONVERT Function Module for Conversion of Aggregation Name to BW Naming Convention
RSBB_AGR_NAME_CONVERT is a standard rsbb agr name convert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Conversion of Aggregation Name to BW Naming Convention 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 rsbb agr name convert FM, simply by entering the name RSBB_AGR_NAME_CONVERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSMENU
Program Name: SAPLRSMENU
Main Program: SAPLRSMENU
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RSBB_AGR_NAME_CONVERT 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 'RSBB_AGR_NAME_CONVERT'"Conversion of Aggregation Name to BW Naming Convention.
EXPORTING
* I_OBJVERS = RS_C_OBJVERS-ACTIVE "Object Version
CHANGING
C_AGR_NAME = "Activity group name
EXCEPTIONS
INVALID_COMBINATION = 1
IMPORTING Parameters details for RSBB_AGR_NAME_CONVERT
I_OBJVERS - Object Version
Data type: RSOBJVERSDefault: RS_C_OBJVERS-ACTIVE
Optional: No
Call by Reference: Yes
CHANGING Parameters details for RSBB_AGR_NAME_CONVERT
C_AGR_NAME - Activity group name
Data type: AGR_DEFINE-AGR_NAMEOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_COMBINATION - D-Version of Customer Objects Requested
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSBB_AGR_NAME_CONVERT 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_objvers | TYPE RSOBJVERS, " RS_C_OBJVERS-ACTIVE | |||
lv_c_agr_name | TYPE AGR_DEFINE-AGR_NAME, " | |||
lv_invalid_combination | TYPE AGR_DEFINE. " |
  CALL FUNCTION 'RSBB_AGR_NAME_CONVERT' "Conversion of Aggregation Name to BW Naming Convention |
EXPORTING | ||
I_OBJVERS | = lv_i_objvers | |
CHANGING | ||
C_AGR_NAME | = lv_c_agr_name | |
EXCEPTIONS | ||
INVALID_COMBINATION = 1 | ||
. " RSBB_AGR_NAME_CONVERT |
ABAP code using 7.40 inline data declarations to call FM RSBB_AGR_NAME_CONVERT
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_objvers) | = RS_C_OBJVERS-ACTIVE. | |||
"SELECT single AGR_NAME FROM AGR_DEFINE INTO @DATA(ld_c_agr_name). | ||||
Search for further information about these or an SAP related objects