SAP FVF4_RANL_CHECK Function Module for F4 Help for SID of Securities

Search SAP Function Modules

FVF4_RANL_CHECK is a standard fvf4 ranl 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 F4 Help for SID of Securities 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 fvf4 ranl check FM, simply by entering the name FVF4_RANL_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function FVF4_RANL_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 'FVF4_RANL_CHECK'"F4 Help for SID of Securities
  EXPORTING
   DYNPR_FIELDNAME =  "Screen Field
*  SANLF_RANGE =  "relevante Anlageformen
*  GSART =  "Selektion auf eine Produktart
*  CHANGE_FLAG = 'X' "'X' --> Dynpro-Feld wird verändert
*  TITEL = ' ' "Titel des F4-Dynpros
*  SINGLE_VALUE = 'X' "

 IMPORTING
   RANL =  "Ausgewählte KM-Nummer

EXCEPTIONS
   NO_POSTING_SELECTED = 1    POSTING_NOT_FOUND = 2 

.

IMPORTING Parameters details for FVF4_RANL_CHECK

DYNPR_FIELDNAME - Screen Field

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

SANLF_RANGE - relevante Anlageformen

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

GSART - Selektion auf eine Produktart

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

CHANGE_FLAG - 'X' --> Dynpro-Feld wird verändert

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

TITEL - Titel des F4-Dynpros

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

SINGLE_VALUE -

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

EXPORTING Parameters details for FVF4_RANL_CHECK

RANL - Ausgewählte KM-Nummer

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

EXCEPTIONS details

NO_POSTING_SELECTED - keine Bewegungsart ausgewählt

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

POSTING_NOT_FOUND - keine Bewegungsart gefunden

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

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

ABAP code using 7.40 inline data declarations to call FM FVF4_RANL_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.

Search for further information about these or an SAP related objects