SAP BAPI_INTENSIV_AT_CANCEL Function Module for
BAPI_INTENSIV_AT_CANCEL is a standard bapi intensiv at cancel SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bapi intensiv at cancel FM, simply by entering the name BAPI_INTENSIV_AT_CANCEL into the relevant SAP transaction such as SE37 or SE38.
Function Group: 1313AT
Program Name: SAPL1313AT
Main Program: SAPL1313AT
Appliation area: N
Release date: 24-Aug-2004
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_INTENSIV_AT_CANCEL 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 'BAPI_INTENSIV_AT_CANCEL'".
EXPORTING
CLIENT = "
INSTITUTION = "
PATCASEID = "
MOVEMNT_SEQNO = "
* TESTRUN = ' ' "
IMPORTING
WORST_RETURNED_MSGTY = "
TABLES
* RETURN = "
IMPORTING Parameters details for BAPI_INTENSIV_AT_CANCEL
CLIENT -
Data type: BAPINALL-CLIENTOptional: No
Call by Reference: No ( called with pass by value option)
INSTITUTION -
Data type: BAPI1313ATINTENS-INSTITUTIONOptional: No
Call by Reference: No ( called with pass by value option)
PATCASEID -
Data type: BAPI1313ATINTENS-PATCASEIDOptional: No
Call by Reference: No ( called with pass by value option)
MOVEMNT_SEQNO -
Data type: BAPI1313ATINTENS-MOVEMNT_SEQNOOptional: No
Call by Reference: No ( called with pass by value option)
TESTRUN -
Data type: BAPINALL-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_INTENSIV_AT_CANCEL
WORST_RETURNED_MSGTY -
Data type: BAPINALL-WORSTRETMSGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_INTENSIV_AT_CANCEL
RETURN -
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_INTENSIV_AT_CANCEL 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_client | TYPE BAPINALL-CLIENT, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_worst_returned_msgty | TYPE BAPINALL-WORSTRETMSG, " | |||
| lv_institution | TYPE BAPI1313ATINTENS-INSTITUTION, " | |||
| lv_patcaseid | TYPE BAPI1313ATINTENS-PATCASEID, " | |||
| lv_movemnt_seqno | TYPE BAPI1313ATINTENS-MOVEMNT_SEQNO, " | |||
| lv_testrun | TYPE BAPINALL-TESTRUN. " SPACE |
|   CALL FUNCTION 'BAPI_INTENSIV_AT_CANCEL' " |
| EXPORTING | ||
| CLIENT | = lv_client | |
| INSTITUTION | = lv_institution | |
| PATCASEID | = lv_patcaseid | |
| MOVEMNT_SEQNO | = lv_movemnt_seqno | |
| TESTRUN | = lv_testrun | |
| IMPORTING | ||
| WORST_RETURNED_MSGTY | = lv_worst_returned_msgty | |
| TABLES | ||
| RETURN | = lt_return | |
| . " BAPI_INTENSIV_AT_CANCEL | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_INTENSIV_AT_CANCEL
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 CLIENT FROM BAPINALL INTO @DATA(ld_client). | ||||
| "SELECT single WORSTRETMSG FROM BAPINALL INTO @DATA(ld_worst_returned_msgty). | ||||
| "SELECT single INSTITUTION FROM BAPI1313ATINTENS INTO @DATA(ld_institution). | ||||
| "SELECT single PATCASEID FROM BAPI1313ATINTENS INTO @DATA(ld_patcaseid). | ||||
| "SELECT single MOVEMNT_SEQNO FROM BAPI1313ATINTENS INTO @DATA(ld_movemnt_seqno). | ||||
| "SELECT single TESTRUN FROM BAPINALL INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
Search for further information about these or an SAP related objects