SAP THMEX_GET_SIGN_BY_TRANSCAT Function Module for Get Sign from Transaction Category
THMEX_GET_SIGN_BY_TRANSCAT is a standard thmex get sign by transcat SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Sign from Transaction Category 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 thmex get sign by transcat FM, simply by entering the name THMEX_GET_SIGN_BY_TRANSCAT into the relevant SAP transaction such as SE37 or SE38.
Function Group: THMEX_FRONTEND
Program Name: SAPLTHMEX_FRONTEND
Main Program: SAPLTHMEX_FRONTEND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function THMEX_GET_SIGN_BY_TRANSCAT 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 'THMEX_GET_SIGN_BY_TRANSCAT'"Get Sign from Transaction Category.
EXPORTING
PI_TRANSCAT = "Transactioncategory
PI_TRANSACT = "Transactionactivity
* PI_RISKCAT = "Hedge Risk Category
IMPORTING
PE_SIGN = "Sign
EXCEPTIONS
DB_ERROR = 1
IMPORTING Parameters details for THMEX_GET_SIGN_BY_TRANSCAT
PI_TRANSCAT - Transactioncategory
Data type: THM_TRANSCATOptional: No
Call by Reference: Yes
PI_TRANSACT - Transactionactivity
Data type: THM_TRANSACTOptional: No
Call by Reference: Yes
PI_RISKCAT - Hedge Risk Category
Data type: THM_RISKCATOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for THMEX_GET_SIGN_BY_TRANSCAT
PE_SIGN - Sign
Data type: COptional: No
Call by Reference: Yes
EXCEPTIONS details
DB_ERROR - No value found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for THMEX_GET_SIGN_BY_TRANSCAT 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_pe_sign | TYPE C, " | |||
| lv_db_error | TYPE C, " | |||
| lv_pi_transcat | TYPE THM_TRANSCAT, " | |||
| lv_pi_transact | TYPE THM_TRANSACT, " | |||
| lv_pi_riskcat | TYPE THM_RISKCAT. " |
|   CALL FUNCTION 'THMEX_GET_SIGN_BY_TRANSCAT' "Get Sign from Transaction Category |
| EXPORTING | ||
| PI_TRANSCAT | = lv_pi_transcat | |
| PI_TRANSACT | = lv_pi_transact | |
| PI_RISKCAT | = lv_pi_riskcat | |
| IMPORTING | ||
| PE_SIGN | = lv_pe_sign | |
| EXCEPTIONS | ||
| DB_ERROR = 1 | ||
| . " THMEX_GET_SIGN_BY_TRANSCAT | ||
ABAP code using 7.40 inline data declarations to call FM THMEX_GET_SIGN_BY_TRANSCAT
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