SAP TB_MASTER_AGREEMENT_CALL Function Module for External Call of Processing Transactions for Master Agreements
TB_MASTER_AGREEMENT_CALL is a standard tb master agreement call SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for External Call of Processing Transactions for Master Agreements 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 master agreement call FM, simply by entering the name TB_MASTER_AGREEMENT_CALL into the relevant SAP transaction such as SE37 or SE38.
Function Group: TBM1
Program Name: SAPLTBM1
Main Program: SAPLTBM1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function TB_MASTER_AGREEMENT_CALL 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_MASTER_AGREEMENT_CALL'"External Call of Processing Transactions for Master Agreements.
EXPORTING
* I_RMAID = "Master Agreement
* I_SMATYPE = "Rahmenvertragsart
* I_TRANSACTIONTYPE = '03' "Art der Transaktion --> Langtext
IMPORTING Parameters details for TB_MASTER_AGREEMENT_CALL
I_RMAID - Master Agreement
Data type: VTBMA-RMAIDOptional: Yes
Call by Reference: Yes
I_SMATYPE - Rahmenvertragsart
Data type: VTBMA-SMATYPEOptional: Yes
Call by Reference: Yes
I_TRANSACTIONTYPE - Art der Transaktion --> Langtext
Data type:Default: '03'
Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for TB_MASTER_AGREEMENT_CALL 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_rmaid | TYPE VTBMA-RMAID, " | |||
lv_i_smatype | TYPE VTBMA-SMATYPE, " | |||
lv_i_transactiontype | TYPE VTBMA. " '03' |
  CALL FUNCTION 'TB_MASTER_AGREEMENT_CALL' "External Call of Processing Transactions for Master Agreements |
EXPORTING | ||
I_RMAID | = lv_i_rmaid | |
I_SMATYPE | = lv_i_smatype | |
I_TRANSACTIONTYPE | = lv_i_transactiontype | |
. " TB_MASTER_AGREEMENT_CALL |
ABAP code using 7.40 inline data declarations to call FM TB_MASTER_AGREEMENT_CALL
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 RMAID FROM VTBMA INTO @DATA(ld_i_rmaid). | ||||
"SELECT single SMATYPE FROM VTBMA INTO @DATA(ld_i_smatype). | ||||
DATA(ld_i_transactiontype) | = '03'. | |||
Search for further information about these or an SAP related objects