SAP TB_TRADER_AUTHORITY_DETERMINE Function Module for Determine Trader's Currently Assigned Transaction Authorizations
TB_TRADER_AUTHORITY_DETERMINE is a standard tb trader authority determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Trader's Currently Assigned Transaction Authorizations 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 tb trader authority determine FM, simply by entering the name TB_TRADER_AUTHORITY_DETERMINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: TB87
Program Name: SAPLTB87
Main Program: SAPLTB87
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TB_TRADER_AUTHORITY_DETERMINE 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 'TB_TRADER_AUTHORITY_DETERMINE'"Determine Trader's Currently Assigned Transaction Authorizations.
EXPORTING
BUKRS = "Company Code
* RDEALER = "Händler (optional)
* SFHAART = "Financial Transaction Type
SGSART = "Product Type
IMPORTING
AUTH_ALLOCATION = "Transaction authorization for traders
TABLES
* TRADER_R = "Händlerrangestabelle
* AUTH_ENTRY = "Transaction authorization for traders
EXCEPTIONS
AUTHORISATION_NOT_FOUND = 1 SFHAART_NOT_FOUND = 2 SGSART_NOT_FOUND = 3
IMPORTING Parameters details for TB_TRADER_AUTHORITY_DETERMINE
BUKRS - Company Code
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
RDEALER - Händler (optional)
Data type: VTBTRA1-RDEALEROptional: Yes
Call by Reference: No ( called with pass by value option)
SFHAART - Financial Transaction Type
Data type: VTBTRA1-SFHAARTOptional: Yes
Call by Reference: No ( called with pass by value option)
SGSART - Product Type
Data type: VTBTRA1-SGSARTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TB_TRADER_AUTHORITY_DETERMINE
AUTH_ALLOCATION - Transaction authorization for traders
Data type: VTBTRA1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TB_TRADER_AUTHORITY_DETERMINE
TRADER_R - Händlerrangestabelle
Data type: VTB_DEALEROptional: Yes
Call by Reference: No ( called with pass by value option)
AUTH_ENTRY - Transaction authorization for traders
Data type: VTBTRA1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
AUTHORISATION_NOT_FOUND - Keine Berechtigungen für Händler vorhanden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SFHAART_NOT_FOUND - Geschäftsart ist nicht vorgesehen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SGSART_NOT_FOUND - Produktart ist nicht vorgesehen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TB_TRADER_AUTHORITY_DETERMINE 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_bukrs | TYPE T001-BUKRS, " | |||
| lt_trader_r | TYPE STANDARD TABLE OF VTB_DEALER, " | |||
| lv_auth_allocation | TYPE VTBTRA1, " | |||
| lv_authorisation_not_found | TYPE VTBTRA1, " | |||
| lv_rdealer | TYPE VTBTRA1-RDEALER, " | |||
| lt_auth_entry | TYPE STANDARD TABLE OF VTBTRA1, " | |||
| lv_sfhaart_not_found | TYPE VTBTRA1, " | |||
| lv_sfhaart | TYPE VTBTRA1-SFHAART, " | |||
| lv_sgsart_not_found | TYPE VTBTRA1, " | |||
| lv_sgsart | TYPE VTBTRA1-SGSART. " |
|   CALL FUNCTION 'TB_TRADER_AUTHORITY_DETERMINE' "Determine Trader's Currently Assigned Transaction Authorizations |
| EXPORTING | ||
| BUKRS | = lv_bukrs | |
| RDEALER | = lv_rdealer | |
| SFHAART | = lv_sfhaart | |
| SGSART | = lv_sgsart | |
| IMPORTING | ||
| AUTH_ALLOCATION | = lv_auth_allocation | |
| TABLES | ||
| TRADER_R | = lt_trader_r | |
| AUTH_ENTRY | = lt_auth_entry | |
| EXCEPTIONS | ||
| AUTHORISATION_NOT_FOUND = 1 | ||
| SFHAART_NOT_FOUND = 2 | ||
| SGSART_NOT_FOUND = 3 | ||
| . " TB_TRADER_AUTHORITY_DETERMINE | ||
ABAP code using 7.40 inline data declarations to call FM TB_TRADER_AUTHORITY_DETERMINE
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 BUKRS FROM T001 INTO @DATA(ld_bukrs). | ||||
| "SELECT single RDEALER FROM VTBTRA1 INTO @DATA(ld_rdealer). | ||||
| "SELECT single SFHAART FROM VTBTRA1 INTO @DATA(ld_sfhaart). | ||||
| "SELECT single SGSART FROM VTBTRA1 INTO @DATA(ld_sgsart). | ||||
Search for further information about these or an SAP related objects