SAP TEM_ALE_EXPOSURE_DELETE Function Module for BAPI -> IDoc: TEM_ALE_EXPOSURE_DELETE

Search SAP Function Modules

TEM_ALE_EXPOSURE_DELETE is a standard tem ale exposure 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: TEM_ALE_EXPOSURE_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 tem ale exposure delete FM, simply by entering the name TEM_ALE_EXPOSURE_DELETE into the relevant SAP transaction such as SE37 or SE38.

Function Group: TEM_BAPI_EXPOSURE
Program Name: SAPLTEM_BAPI_EXPOSURE
Main Program: SAPLTEM_BAPI_EXPOSURE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TEM_ALE_EXPOSURE_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 'TEM_ALE_EXPOSURE_DELETE'"BAPI -> IDoc: TEM_ALE_EXPOSURE_DELETE
  EXPORTING
   EXPOSUREID =  "Exposure ID
   EXPOSUREORIGIN =  "Exposure Origin
   LOGSYSTEM =  "Logical System
   TESTRUN =  "Switch to Simulation Mode for Write BAPIs
*  OBJ_TYPE = 'BUS5115' "
*  SERIAL_ID = '0' "

TABLES
   RECEIVERS =  "
*  COMMUNICATION_DOCUMENTS =  "
*  APPLICATION_OBJECTS =  "

EXCEPTIONS
   ERROR_CREATING_IDOCS = 1 

.

IMPORTING Parameters details for TEM_ALE_EXPOSURE_DELETE

EXPOSUREID - Exposure ID

Data type: BAPI5115-EXPOSURE_ID
Optional: No
Call by Reference: No ( called with pass by value option)

EXPOSUREORIGIN - Exposure Origin

Data type: BAPI5115-EXPOSURE_ORIGIN
Optional: No
Call by Reference: No ( called with pass by value option)

LOGSYSTEM - Logical System

Data type: BAPI5115-LOG_SYSTEM
Optional: No
Call by Reference: No ( called with pass by value option)

TESTRUN - Switch to Simulation Mode for Write BAPIs

Data type: BAPI5115-TESTRUN
Optional: No
Call by Reference: No ( called with pass by value option)

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'BUS5115'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for TEM_ALE_EXPOSURE_DELETE

RECEIVERS -

Data type: BDI_LOGSYS
Optional: No
Call by Reference: No ( called with pass by value option)

COMMUNICATION_DOCUMENTS -

Data type: SWOTOBJID
Optional: Yes
Call by Reference: No ( called with pass by value option)

APPLICATION_OBJECTS -

Data type: SWOTOBJID
Optional: 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 TEM_ALE_EXPOSURE_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.

ABAP code using 7.40 inline data declarations to call FM TEM_ALE_EXPOSURE_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.

Search for further information about these or an SAP related objects