SAP THA_ALE_TRANS_IR_DELETE Function Module for BAPI -> IDoc: THA_ALE_TRANS_IR_DELETE
THA_ALE_TRANS_IR_DELETE is a standard tha ale trans ir delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: THA_ALE_TRANS_IR_DELETE 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 tha ale trans ir delete FM, simply by entering the name THA_ALE_TRANS_IR_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: THA_BAPI_TRANS_IR
Program Name: SAPLTHA_BAPI_TRANS_IR
Main Program: SAPLTHA_BAPI_TRANS_IR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function THA_ALE_TRANS_IR_DELETE 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 'THA_ALE_TRANS_IR_DELETE'"BAPI -> IDoc: THA_ALE_TRANS_IR_DELETE.
EXPORTING
COMPANYCODE = "Company Code
HEDGEPLAN = "Hedge Management: Hedge Plan ID
TRANSACTIONID = "Hedge Management: Transaction
* TESTRUN = ' ' "Switch to Simulation Mode for Write BAPIs
* OBJ_TYPE = 'BUS5107' "
* SERIAL_ID = '0' "
TABLES
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for THA_ALE_TRANS_IR_DELETE
COMPANYCODE - Company Code
Data type: BAPI5105-COMPANY_CODEOptional: No
Call by Reference: No ( called with pass by value option)
HEDGEPLAN - Hedge Management: Hedge Plan ID
Data type: BAPI5105-HEDGE_PLANOptional: No
Call by Reference: No ( called with pass by value option)
TRANSACTIONID - Hedge Management: Transaction
Data type: BAPI_THA_TRANS_IR_DETAIL-TRANSACTION_IDOptional: No
Call by Reference: No ( called with pass by value option)
TESTRUN - Switch to Simulation Mode for Write BAPIs
Data type: BAPI5105-TESTRUNDefault: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)
OBJ_TYPE -
Data type: SERIAL-OBJ_TYPEDefault: 'BUS5107'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SERIAL_ID -
Data type: SERIAL-CHNUMDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for THA_ALE_TRANS_IR_DELETE
RECEIVERS -
Data type: BDI_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_DOCUMENTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
APPLICATION_OBJECTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_CREATING_IDOCS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for THA_ALE_TRANS_IR_DELETE 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: | ||||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lv_companycode | TYPE BAPI5105-COMPANY_CODE, " | |||
| lv_error_creating_idocs | TYPE BAPI5105, " | |||
| lv_hedgeplan | TYPE BAPI5105-HEDGE_PLAN, " | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_transactionid | TYPE BAPI_THA_TRANS_IR_DETAIL-TRANSACTION_ID, " | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_testrun | TYPE BAPI5105-TESTRUN, " SPACE | |||
| lv_obj_type | TYPE SERIAL-OBJ_TYPE, " 'BUS5107' | |||
| lv_serial_id | TYPE SERIAL-CHNUM. " '0' |
|   CALL FUNCTION 'THA_ALE_TRANS_IR_DELETE' "BAPI -> IDoc: THA_ALE_TRANS_IR_DELETE |
| EXPORTING | ||
| COMPANYCODE | = lv_companycode | |
| HEDGEPLAN | = lv_hedgeplan | |
| TRANSACTIONID | = lv_transactionid | |
| TESTRUN | = lv_testrun | |
| OBJ_TYPE | = lv_obj_type | |
| SERIAL_ID | = lv_serial_id | |
| TABLES | ||
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| EXCEPTIONS | ||
| ERROR_CREATING_IDOCS = 1 | ||
| . " THA_ALE_TRANS_IR_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM THA_ALE_TRANS_IR_DELETE
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 COMPANY_CODE FROM BAPI5105 INTO @DATA(ld_companycode). | ||||
| "SELECT single HEDGE_PLAN FROM BAPI5105 INTO @DATA(ld_hedgeplan). | ||||
| "SELECT single TRANSACTION_ID FROM BAPI_THA_TRANS_IR_DETAIL INTO @DATA(ld_transactionid). | ||||
| "SELECT single TESTRUN FROM BAPI5105 INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
| "SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type). | ||||
| DATA(ld_obj_type) | = 'BUS5107'. | |||
| "SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id). | ||||
| DATA(ld_serial_id) | = '0'. | |||
Search for further information about these or an SAP related objects