SAP TB_API_CONDITION_KEY_BUILD Function Module for API: build condition key
TB_API_CONDITION_KEY_BUILD is a standard tb api condition key build SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for API: build condition key 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 api condition key build FM, simply by entering the name TB_API_CONDITION_KEY_BUILD into the relevant SAP transaction such as SE37 or SE38.
Function Group: TB12
Program Name: SAPLTB12
Main Program: SAPLTB12
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TB_API_CONDITION_KEY_BUILD 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_API_CONDITION_KEY_BUILD'"API: build condition key.
EXPORTING
IM_RKONDGR = "Direction of Transaction
IM_RKOND = "Condition
IM_DGUEL_KP = "Condition Item Valid From
IMPORTING
EX_BAPI_KEY = "Key which Identifies a Condition in the BAPI
IMPORTING Parameters details for TB_API_CONDITION_KEY_BUILD
IM_RKONDGR - Direction of Transaction
Data type: TB_RKONDGROptional: No
Call by Reference: Yes
IM_RKOND - Condition
Data type: TB_KONDOptional: No
Call by Reference: Yes
IM_DGUEL_KP - Condition Item Valid From
Data type: DGUEL_KPOptional: No
Call by Reference: Yes
EXPORTING Parameters details for TB_API_CONDITION_KEY_BUILD
EX_BAPI_KEY - Key which Identifies a Condition in the BAPI
Data type: TB_BAPI_COND_KEYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for TB_API_CONDITION_KEY_BUILD 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_im_rkondgr | TYPE TB_RKONDGR, " | |||
| lv_ex_bapi_key | TYPE TB_BAPI_COND_KEY, " | |||
| lv_im_rkond | TYPE TB_KOND, " | |||
| lv_im_dguel_kp | TYPE DGUEL_KP. " |
|   CALL FUNCTION 'TB_API_CONDITION_KEY_BUILD' "API: build condition key |
| EXPORTING | ||
| IM_RKONDGR | = lv_im_rkondgr | |
| IM_RKOND | = lv_im_rkond | |
| IM_DGUEL_KP | = lv_im_dguel_kp | |
| IMPORTING | ||
| EX_BAPI_KEY | = lv_ex_bapi_key | |
| . " TB_API_CONDITION_KEY_BUILD | ||
ABAP code using 7.40 inline data declarations to call FM TB_API_CONDITION_KEY_BUILD
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