SAP MM_ARRANG_CHECK_KONA_DELETE Function Module for NOTRANSL: Prüfen, ob eine Absprache physikalisch von Datenbank gelöscht we

Search SAP Function Modules

MM_ARRANG_CHECK_KONA_DELETE is a standard mm arrang check kona 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 NOTRANSL: Prüfen, ob eine Absprache physikalisch von Datenbank gelöscht we 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 mm arrang check kona delete FM, simply by entering the name MM_ARRANG_CHECK_KONA_DELETE into the relevant SAP transaction such as SE37 or SE38.

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

Function MM_ARRANG_CHECK_KONA_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 'MM_ARRANG_CHECK_KONA_DELETE'"NOTRANSL: Prüfen, ob eine Absprache physikalisch von Datenbank gelöscht we
  EXPORTING
   I_ARRANGEMENT =  "Rebate Arrangement
*  I_T6B1 =  "Arrang. Type

TABLES
   T_CONDITION_RECORD_DB =  "

EXCEPTIONS
   INVALID_ARRANG_TYPE = 1    SETTLEMENT_PERFORMED = 2    BUSINESS_VOL_COMP_PERFORMED = 3    BUSINESS_VOLUME_EXIST = 4    BUSINESS_VOLUME_DOCU_EXIST = 5 

.

IMPORTING Parameters details for MM_ARRANG_CHECK_KONA_DELETE

I_ARRANGEMENT - Rebate Arrangement

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

I_T6B1 - Arrang. Type

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

TABLES Parameters details for MM_ARRANG_CHECK_KONA_DELETE

T_CONDITION_RECORD_DB -

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

EXCEPTIONS details

INVALID_ARRANG_TYPE -

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

SETTLEMENT_PERFORMED -

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

BUSINESS_VOL_COMP_PERFORMED -

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

BUSINESS_VOLUME_EXIST -

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

BUSINESS_VOLUME_DOCU_EXIST -

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

Copy and paste ABAP code example for MM_ARRANG_CHECK_KONA_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 MM_ARRANG_CHECK_KONA_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