SAP LOAN_PLANNED_ITEM_DEQUEUE_HF Function Module for Set OI Tool Block on Planned Record
LOAN_PLANNED_ITEM_DEQUEUE_HF is a standard loan planned item dequeue hf SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set OI Tool Block on Planned 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 loan planned item dequeue hf FM, simply by entering the name LOAN_PLANNED_ITEM_DEQUEUE_HF into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD0A_PLAN
Program Name: SAPLFVD0A_PLAN
Main Program: SAPLFVD0A_PLAN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function LOAN_PLANNED_ITEM_DEQUEUE_HF 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_PLANNED_ITEM_DEQUEUE_HF'"Set OI Tool Block on Planned Record.
EXPORTING
I_BUKRS = "Company Code
I_RANL = "Contract Number
I_DTRANS = "Flow data key: System date
I_TTRANS = "Schlüssel Bewegungsdaten: Systemzeit
I_NTRANS = "Schlüssel Bewegungsdaten: Laufende Nummer
I_APPLICATION = "CML: Application Name for Open Item Blocking Tool
* I_RBO = "CML: Application Name for Open Item Blocking Tool
EXCEPTIONS
NO_ITEMS = 1 UNLOCKING_IMPOSSIBLE = 2
IMPORTING Parameters details for LOAN_PLANNED_ITEM_DEQUEUE_HF
I_BUKRS - Company Code
Data type: VDBEPP-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_RANL - Contract Number
Data type: VDBEPP-RANLOptional: No
Call by Reference: No ( called with pass by value option)
I_DTRANS - Flow data key: System date
Data type: VDBEPP-DTRANSOptional: No
Call by Reference: No ( called with pass by value option)
I_TTRANS - Schlüssel Bewegungsdaten: Systemzeit
Data type: VDBEPP-TTRANSOptional: No
Call by Reference: No ( called with pass by value option)
I_NTRANS - Schlüssel Bewegungsdaten: Laufende Nummer
Data type: VDBEPP-NTRANSOptional: No
Call by Reference: No ( called with pass by value option)
I_APPLICATION - CML: Application Name for Open Item Blocking Tool
Data type: LOANREF_O-APPLICATIONOptional: No
Call by Reference: No ( called with pass by value option)
I_RBO - CML: Application Name for Open Item Blocking Tool
Data type: LOANREF_O-RBOOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_ITEMS - Keinen Plansatz gefunden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNLOCKING_IMPOSSIBLE - Plansatz durch andere Applikation gesperrt
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for LOAN_PLANNED_ITEM_DEQUEUE_HF 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_bukrs | TYPE VDBEPP-BUKRS, " | |||
| lv_no_items | TYPE VDBEPP, " | |||
| lv_i_ranl | TYPE VDBEPP-RANL, " | |||
| lv_unlocking_impossible | TYPE VDBEPP, " | |||
| lv_i_dtrans | TYPE VDBEPP-DTRANS, " | |||
| lv_i_ttrans | TYPE VDBEPP-TTRANS, " | |||
| lv_i_ntrans | TYPE VDBEPP-NTRANS, " | |||
| lv_i_application | TYPE LOANREF_O-APPLICATION, " | |||
| lv_i_rbo | TYPE LOANREF_O-RBO. " |
|   CALL FUNCTION 'LOAN_PLANNED_ITEM_DEQUEUE_HF' "Set OI Tool Block on Planned Record |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_RANL | = lv_i_ranl | |
| I_DTRANS | = lv_i_dtrans | |
| I_TTRANS | = lv_i_ttrans | |
| I_NTRANS | = lv_i_ntrans | |
| I_APPLICATION | = lv_i_application | |
| I_RBO | = lv_i_rbo | |
| EXCEPTIONS | ||
| NO_ITEMS = 1 | ||
| UNLOCKING_IMPOSSIBLE = 2 | ||
| . " LOAN_PLANNED_ITEM_DEQUEUE_HF | ||
ABAP code using 7.40 inline data declarations to call FM LOAN_PLANNED_ITEM_DEQUEUE_HF
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 BUKRS FROM VDBEPP INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single RANL FROM VDBEPP INTO @DATA(ld_i_ranl). | ||||
| "SELECT single DTRANS FROM VDBEPP INTO @DATA(ld_i_dtrans). | ||||
| "SELECT single TTRANS FROM VDBEPP INTO @DATA(ld_i_ttrans). | ||||
| "SELECT single NTRANS FROM VDBEPP INTO @DATA(ld_i_ntrans). | ||||
| "SELECT single APPLICATION FROM LOANREF_O INTO @DATA(ld_i_application). | ||||
| "SELECT single RBO FROM LOANREF_O INTO @DATA(ld_i_rbo). | ||||
Search for further information about these or an SAP related objects