SAP LOAN_CHECK_MANSP Function Module for Loans: Check the Lock Reasaons for Dunning Notices
LOAN_CHECK_MANSP is a standard loan check mansp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Loans: Check the Lock Reasaons for Dunning Notices 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 loan check mansp FM, simply by entering the name LOAN_CHECK_MANSP into the relevant SAP transaction such as SE37 or SE38.
Function Group: TRDS
Program Name: SAPLTRDS
Main Program: SAPLTRDS
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LOAN_CHECK_MANSP 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 'LOAN_CHECK_MANSP'"Loans: Check the Lock Reasaons for Dunning Notices.
EXPORTING
I_MANSP = "
IMPORTING
E_T040S = "
EXCEPTIONS
MANSP_NOT_FOUND = 1
IMPORTING Parameters details for LOAN_CHECK_MANSP
I_MANSP -
Data type: VZZKOPO-MANSPOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for LOAN_CHECK_MANSP
E_T040S -
Data type: T040SOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MANSP_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LOAN_CHECK_MANSP 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_e_t040s | TYPE T040S, " | |||
| lv_i_mansp | TYPE VZZKOPO-MANSP, " | |||
| lv_mansp_not_found | TYPE VZZKOPO. " |
|   CALL FUNCTION 'LOAN_CHECK_MANSP' "Loans: Check the Lock Reasaons for Dunning Notices |
| EXPORTING | ||
| I_MANSP | = lv_i_mansp | |
| IMPORTING | ||
| E_T040S | = lv_e_t040s | |
| EXCEPTIONS | ||
| MANSP_NOT_FOUND = 1 | ||
| . " LOAN_CHECK_MANSP | ||
ABAP code using 7.40 inline data declarations to call FM LOAN_CHECK_MANSP
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 VZZKOPO INTO @DATA(ld_i_mansp). | ||||
Search for further information about these or an SAP related objects