SAP FTBP_READ_ROLES Function Module for Entries for Role Categories According to Application
FTBP_READ_ROLES is a standard ftbp read roles SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Entries for Role Categories According to Application 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 ftbp read roles FM, simply by entering the name FTBP_READ_ROLES into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTBP_BPAR
Program Name: SAPLFTBP_BPAR
Main Program: SAPLFTBP_BPAR
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTBP_READ_ROLES 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 'FTBP_READ_ROLES'"Entries for Role Categories According to Application.
EXPORTING
* I_ASSI_TYP = "Assignment Category
* APPL = ' ' "Application
* DISPLAY = ' ' "Display Mode
* FILL_TABLE = ' ' "'X', wenn Tabelle ausgegeben werden soll (Ausw.)
* NO_DISPL_IF_ONE = ' ' "'X', kein Popup, wenn nur 1 Treffer (Ausw.)
* PARTTYPE = ' ' "Business Partner Category
* I_ROLECATEGORY = "BP role category
* I_ROLE = "Business Partner Role
IMPORTING
E_ROLE = "Business Partner Role
TABLES
* T_TB003 = "BP Roles
EXCEPTIONS
APPLICATION = 1 ROLETYP = 2 TYPE = 3
IMPORTING Parameters details for FTBP_READ_ROLES
I_ASSI_TYP - Assignment Category
Data type: TPR1-ASSI_TYPOptional: Yes
Call by Reference: Yes
APPL - Application
Data type: TPZ12-APPLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DISPLAY - Display Mode
Data type: BPIB0-BP_SELECTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FILL_TABLE - 'X', wenn Tabelle ausgegeben werden soll (Ausw.)
Data type: BPIB0-BP_SELECTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_DISPL_IF_ONE - 'X', kein Popup, wenn nur 1 Treffer (Ausw.)
Data type: BPIB0-BP_SELECTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PARTTYPE - Business Partner Category
Data type: BU_TYPEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ROLECATEGORY - BP role category
Data type: BU_PARTNERROLECATOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ROLE - Business Partner Role
Data type: BU_PARTNERROLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FTBP_READ_ROLES
E_ROLE - Business Partner Role
Data type: TB003-ROLEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FTBP_READ_ROLES
T_TB003 - BP Roles
Data type: TB003Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
APPLICATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ROLETYP -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TYPE - Partnertyp unzulässig
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTBP_READ_ROLES 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_e_role | TYPE TB003-ROLE, " | |||
| lt_t_tb003 | TYPE STANDARD TABLE OF TB003, " | |||
| lv_i_assi_typ | TYPE TPR1-ASSI_TYP, " | |||
| lv_application | TYPE TPR1, " | |||
| lv_appl | TYPE TPZ12-APPL, " SPACE | |||
| lv_roletyp | TYPE TPZ12, " | |||
| lv_type | TYPE TPZ12, " | |||
| lv_display | TYPE BPIB0-BP_SELECT, " SPACE | |||
| lv_fill_table | TYPE BPIB0-BP_SELECT, " SPACE | |||
| lv_no_displ_if_one | TYPE BPIB0-BP_SELECT, " SPACE | |||
| lv_parttype | TYPE BU_TYPE, " SPACE | |||
| lv_i_rolecategory | TYPE BU_PARTNERROLECAT, " | |||
| lv_i_role | TYPE BU_PARTNERROLE. " |
|   CALL FUNCTION 'FTBP_READ_ROLES' "Entries for Role Categories According to Application |
| EXPORTING | ||
| I_ASSI_TYP | = lv_i_assi_typ | |
| APPL | = lv_appl | |
| DISPLAY | = lv_display | |
| FILL_TABLE | = lv_fill_table | |
| NO_DISPL_IF_ONE | = lv_no_displ_if_one | |
| PARTTYPE | = lv_parttype | |
| I_ROLECATEGORY | = lv_i_rolecategory | |
| I_ROLE | = lv_i_role | |
| IMPORTING | ||
| E_ROLE | = lv_e_role | |
| TABLES | ||
| T_TB003 | = lt_t_tb003 | |
| EXCEPTIONS | ||
| APPLICATION = 1 | ||
| ROLETYP = 2 | ||
| TYPE = 3 | ||
| . " FTBP_READ_ROLES | ||
ABAP code using 7.40 inline data declarations to call FM FTBP_READ_ROLES
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.| "SELECT single ROLE FROM TB003 INTO @DATA(ld_e_role). | ||||
| "SELECT single ASSI_TYP FROM TPR1 INTO @DATA(ld_i_assi_typ). | ||||
| "SELECT single APPL FROM TPZ12 INTO @DATA(ld_appl). | ||||
| DATA(ld_appl) | = ' '. | |||
| "SELECT single BP_SELECT FROM BPIB0 INTO @DATA(ld_display). | ||||
| DATA(ld_display) | = ' '. | |||
| "SELECT single BP_SELECT FROM BPIB0 INTO @DATA(ld_fill_table). | ||||
| DATA(ld_fill_table) | = ' '. | |||
| "SELECT single BP_SELECT FROM BPIB0 INTO @DATA(ld_no_displ_if_one). | ||||
| DATA(ld_no_displ_if_one) | = ' '. | |||
| DATA(ld_parttype) | = ' '. | |||
Search for further information about these or an SAP related objects