SAP PTRM_WEB_FUND_FICOV Function Module for Input Help for Funds with Search Help FICOV









PTRM_WEB_FUND_FICOV is a standard ptrm web fund ficov SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Input Help for Funds with Search Help FICOV 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 ptrm web fund ficov FM, simply by entering the name PTRM_WEB_FUND_FICOV into the relevant SAP transaction such as SE37 or SE38.

Function Group: PTRM_WEB_FUND_VR
Program Name: SAPLPTRM_WEB_FUND_VR
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function PTRM_WEB_FUND_FICOV 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 'PTRM_WEB_FUND_FICOV'"Input Help for Funds with Search Help FICOV
  EXPORTING
*  I_FUND =  "Funds
*  I_FM_AREA =  "FM Area
*  I_APPLICATION_OF_FUND =  "Application of Secondary Source Funds
*  I_SEARCH_TERM_FOR_MC_SEARCH =  "Search Term for Matchcode Search
*  I_FUND_TYPE =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  I_GM_FUND_TYPE =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  I_MAXROW = 50 "Max. Number of Lines

 IMPORTING
   ET_VALUE_LIST_FICOV =  "Input Help for Funds with Search Help FICOV
   ET_RETURN =  "Table with BAPI Return Information
.



IMPORTING Parameters details for PTRM_WEB_FUND_FICOV

I_FUND - Funds

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

I_FM_AREA - FM Area

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

I_APPLICATION_OF_FUND - Application of Secondary Source Funds

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

I_SEARCH_TERM_FOR_MC_SEARCH - Search Term for Matchcode Search

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

I_FUND_TYPE - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

I_GM_FUND_TYPE - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

I_MAXROW - Max. Number of Lines

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

EXPORTING Parameters details for PTRM_WEB_FUND_FICOV

ET_VALUE_LIST_FICOV - Input Help for Funds with Search Help FICOV

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

ET_RETURN - Table with BAPI Return Information

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

Copy and paste ABAP code example for PTRM_WEB_FUND_FICOV 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_fund  TYPE PTRV_WEB_FUND_FICOV-FUND, "   
lv_et_value_list_ficov  TYPE PTRV_WEB_FUND_FICOV_T, "   
lv_et_return  TYPE BAPIRETTAB, "   
lv_i_fm_area  TYPE PTRV_WEB_FUND_FICOV-FM_AREA, "   
lv_i_application_of_fund  TYPE PTRV_WEB_FUND_FICOV-APPLICATION_OF_FUND, "   
lv_i_search_term_for_mc_search  TYPE PTRV_WEB_FUND_FICOV-SEARCH_TERM_FOR_MC_SEARCH, "   
lv_i_fund_type  TYPE PTRV_WEB_FUND_FICOV-FUND_TYPE, "   
lv_i_gm_fund_type  TYPE PTRV_WEB_FUND_FICOV-GM_FUND_TYPE, "   
lv_i_maxrow  TYPE PTRV_WEB_MAXROW. "   50

  CALL FUNCTION 'PTRM_WEB_FUND_FICOV'  "Input Help for Funds with Search Help FICOV
    EXPORTING
         I_FUND = lv_i_fund
         I_FM_AREA = lv_i_fm_area
         I_APPLICATION_OF_FUND = lv_i_application_of_fund
         I_SEARCH_TERM_FOR_MC_SEARCH = lv_i_search_term_for_mc_search
         I_FUND_TYPE = lv_i_fund_type
         I_GM_FUND_TYPE = lv_i_gm_fund_type
         I_MAXROW = lv_i_maxrow
    IMPORTING
         ET_VALUE_LIST_FICOV = lv_et_value_list_ficov
         ET_RETURN = lv_et_return
. " PTRM_WEB_FUND_FICOV




ABAP code using 7.40 inline data declarations to call FM PTRM_WEB_FUND_FICOV

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 FUND FROM PTRV_WEB_FUND_FICOV INTO @DATA(ld_i_fund).
 
 
 
"SELECT single FM_AREA FROM PTRV_WEB_FUND_FICOV INTO @DATA(ld_i_fm_area).
 
"SELECT single APPLICATION_OF_FUND FROM PTRV_WEB_FUND_FICOV INTO @DATA(ld_i_application_of_fund).
 
"SELECT single SEARCH_TERM_FOR_MC_SEARCH FROM PTRV_WEB_FUND_FICOV INTO @DATA(ld_i_search_term_for_mc_search).
 
"SELECT single FUND_TYPE FROM PTRV_WEB_FUND_FICOV INTO @DATA(ld_i_fund_type).
 
"SELECT single GM_FUND_TYPE FROM PTRV_WEB_FUND_FICOV INTO @DATA(ld_i_gm_fund_type).
 
DATA(ld_i_maxrow) = 50.
 


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!