SAP MAHNSP_CHECK Function Module for NOTRANSL: Prüfen der Mahnsperre









MAHNSP_CHECK is a standard mahnsp check 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 der Mahnsperre 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 mahnsp check FM, simply by entering the name MAHNSP_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function MAHNSP_CHECK 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 'MAHNSP_CHECK'"NOTRANSL: Prüfen der Mahnsperre
EXPORTING
I_MANSP = "Dunning Block
* I_MSG_HANDLING = 'X' "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
NOT_VALID = 1
.



IMPORTING Parameters details for MAHNSP_CHECK

I_MANSP - Dunning Block

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

I_MSG_HANDLING - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_VALID - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

Copy and paste ABAP code example for MAHNSP_CHECK 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_i_mansp  TYPE KNB5-MANSP, "   
lv_not_valid  TYPE KNB5, "   
lv_i_msg_handling  TYPE C. "   'X'

  CALL FUNCTION 'MAHNSP_CHECK'  "NOTRANSL: Prüfen der Mahnsperre
    EXPORTING
         I_MANSP = lv_i_mansp
         I_MSG_HANDLING = lv_i_msg_handling
    EXCEPTIONS
        NOT_VALID = 1
. " MAHNSP_CHECK




ABAP code using 7.40 inline data declarations to call FM MAHNSP_CHECK

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 MANSP FROM KNB5 INTO @DATA(ld_i_mansp).
 
 
DATA(ld_i_msg_handling) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!