SAP ISM_SD_API_BAG_ISSUE_DELETE Function Module for Delete Recall Record
ISM_SD_API_BAG_ISSUE_DELETE is a standard ism sd api bag issue 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 Delete Recall Record 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 ism sd api bag issue delete FM, simply by entering the name ISM_SD_API_BAG_ISSUE_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKSDCOLLECTION_BAG
Program Name: SAPLJKSDCOLLECTION_BAG
Main Program: SAPLJKSDCOLLECTION_BAG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_SD_API_BAG_ISSUE_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 'ISM_SD_API_BAG_ISSUE_DELETE'"Delete Recall Record.
EXPORTING
* IM_ID = "GUID in 'RAW' Format
* IM_BAG = "GUID in 'RAW' Format
* IM_ISSUE = "Media Issue
* IM_VKORG = "Sales Organization
* IM_VTWEG = "Distribution Channel
* IM_RETURNPHASE = "Return Collection Phase
IM_TESTRUN = "Checkbox Field
IMPORTING
EX_RETURN_TAB = "IS-M: BAPIRET2 Table
IMPORTING Parameters details for ISM_SD_API_BAG_ISSUE_DELETE
IM_ID - GUID in 'RAW' Format
Data type: JKSDISSUEBAGIDOptional: Yes
Call by Reference: Yes
IM_BAG - GUID in 'RAW' Format
Data type: JKSDBAGIDOptional: Yes
Call by Reference: Yes
IM_ISSUE - Media Issue
Data type: ISMMATNR_ISSUEOptional: Yes
Call by Reference: Yes
IM_VKORG - Sales Organization
Data type: VKORGOptional: Yes
Call by Reference: Yes
IM_VTWEG - Distribution Channel
Data type: VTWEGOptional: Yes
Call by Reference: Yes
IM_RETURNPHASE - Return Collection Phase
Data type: JKSDCOLLPHASEOptional: Yes
Call by Reference: Yes
IM_TESTRUN - Checkbox Field
Data type: XFELDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_SD_API_BAG_ISSUE_DELETE
EX_RETURN_TAB - IS-M: BAPIRET2 Table
Data type: BAPIRET2TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_SD_API_BAG_ISSUE_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: | ||||
| lv_im_id | TYPE JKSDISSUEBAGID, " | |||
| lv_ex_return_tab | TYPE BAPIRET2TAB, " | |||
| lv_im_bag | TYPE JKSDBAGID, " | |||
| lv_im_issue | TYPE ISMMATNR_ISSUE, " | |||
| lv_im_vkorg | TYPE VKORG, " | |||
| lv_im_vtweg | TYPE VTWEG, " | |||
| lv_im_returnphase | TYPE JKSDCOLLPHASE, " | |||
| lv_im_testrun | TYPE XFELD. " |
|   CALL FUNCTION 'ISM_SD_API_BAG_ISSUE_DELETE' "Delete Recall Record |
| EXPORTING | ||
| IM_ID | = lv_im_id | |
| IM_BAG | = lv_im_bag | |
| IM_ISSUE | = lv_im_issue | |
| IM_VKORG | = lv_im_vkorg | |
| IM_VTWEG | = lv_im_vtweg | |
| IM_RETURNPHASE | = lv_im_returnphase | |
| IM_TESTRUN | = lv_im_testrun | |
| IMPORTING | ||
| EX_RETURN_TAB | = lv_ex_return_tab | |
| . " ISM_SD_API_BAG_ISSUE_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM ISM_SD_API_BAG_ISSUE_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