SAP PTRM_WEB_FUNDS_CTR_FISTA Function Module for Input Help for Funds Centers with Search Help FISTA
PTRM_WEB_FUNDS_CTR_FISTA is a standard ptrm web funds ctr fista 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 Centers with Search Help FISTA 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 funds ctr fista FM, simply by entering the name PTRM_WEB_FUNDS_CTR_FISTA into the relevant SAP transaction such as SE37 or SE38.
Function Group: PTRM_WEB_FUNDS_CTR_VR
Program Name: SAPLPTRM_WEB_FUNDS_CTR_VR
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function PTRM_WEB_FUNDS_CTR_FISTA 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_FUNDS_CTR_FISTA'"Input Help for Funds Centers with Search Help FISTA.
EXPORTING
* I_FUNDS_CTR = "Funds Center
* I_FM_AREA = "FM Area
* I_FM_KEY_DATE = "Key Date
* I_FM_BOSSID = "Funds Center Manager in Organization Model
* I_FM_BOSSNAM = "FM: Name of Person Responsible
* I_FM_DFONDS = "Fund (Default Value in a Funds Center)
* I_MAXROW = 50 "Max. Number of Lines
IMPORTING
ET_VALUE_LIST_FISTA = "Input Help for Funds Centers with Search Help FISTA
ET_RETURN = "Table with BAPI Return Information
IMPORTING Parameters details for PTRM_WEB_FUNDS_CTR_FISTA
I_FUNDS_CTR - Funds Center
Data type: PTRV_WEB_FUNDS_CTR_FISTA-FUNDS_CTROptional: Yes
Call by Reference: No ( called with pass by value option)
I_FM_AREA - FM Area
Data type: PTRV_WEB_FUNDS_CTR_FISTA-FM_AREAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FM_KEY_DATE - Key Date
Data type: PTRV_WEB_INTERFACE_FM_KEYDATEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FM_BOSSID - Funds Center Manager in Organization Model
Data type: PTRV_WEB_FUNDS_CTR_FISTA-FM_BOSSIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FM_BOSSNAM - FM: Name of Person Responsible
Data type: PTRV_WEB_FUNDS_CTR_FISTA-FM_BOSSNAMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FM_DFONDS - Fund (Default Value in a Funds Center)
Data type: PTRV_WEB_FUNDS_CTR_FISTA-FM_DFONDSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MAXROW - Max. Number of Lines
Data type: PTRV_WEB_MAXROWDefault: 50
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PTRM_WEB_FUNDS_CTR_FISTA
ET_VALUE_LIST_FISTA - Input Help for Funds Centers with Search Help FISTA
Data type: PTRV_WEB_FUNDS_CTR_FISTA_TOptional: No
Call by Reference: No ( called with pass by value option)
ET_RETURN - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PTRM_WEB_FUNDS_CTR_FISTA 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_funds_ctr | TYPE PTRV_WEB_FUNDS_CTR_FISTA-FUNDS_CTR, " | |||
| lv_et_value_list_fista | TYPE PTRV_WEB_FUNDS_CTR_FISTA_T, " | |||
| lv_et_return | TYPE BAPIRETTAB, " | |||
| lv_i_fm_area | TYPE PTRV_WEB_FUNDS_CTR_FISTA-FM_AREA, " | |||
| lv_i_fm_key_date | TYPE PTRV_WEB_INTERFACE_FM_KEYDATE, " | |||
| lv_i_fm_bossid | TYPE PTRV_WEB_FUNDS_CTR_FISTA-FM_BOSSID, " | |||
| lv_i_fm_bossnam | TYPE PTRV_WEB_FUNDS_CTR_FISTA-FM_BOSSNAM, " | |||
| lv_i_fm_dfonds | TYPE PTRV_WEB_FUNDS_CTR_FISTA-FM_DFONDS, " | |||
| lv_i_maxrow | TYPE PTRV_WEB_MAXROW. " 50 |
|   CALL FUNCTION 'PTRM_WEB_FUNDS_CTR_FISTA' "Input Help for Funds Centers with Search Help FISTA |
| EXPORTING | ||
| I_FUNDS_CTR | = lv_i_funds_ctr | |
| I_FM_AREA | = lv_i_fm_area | |
| I_FM_KEY_DATE | = lv_i_fm_key_date | |
| I_FM_BOSSID | = lv_i_fm_bossid | |
| I_FM_BOSSNAM | = lv_i_fm_bossnam | |
| I_FM_DFONDS | = lv_i_fm_dfonds | |
| I_MAXROW | = lv_i_maxrow | |
| IMPORTING | ||
| ET_VALUE_LIST_FISTA | = lv_et_value_list_fista | |
| ET_RETURN | = lv_et_return | |
| . " PTRM_WEB_FUNDS_CTR_FISTA | ||
ABAP code using 7.40 inline data declarations to call FM PTRM_WEB_FUNDS_CTR_FISTA
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 FUNDS_CTR FROM PTRV_WEB_FUNDS_CTR_FISTA INTO @DATA(ld_i_funds_ctr). | ||||
| "SELECT single FM_AREA FROM PTRV_WEB_FUNDS_CTR_FISTA INTO @DATA(ld_i_fm_area). | ||||
| "SELECT single FM_BOSSID FROM PTRV_WEB_FUNDS_CTR_FISTA INTO @DATA(ld_i_fm_bossid). | ||||
| "SELECT single FM_BOSSNAM FROM PTRV_WEB_FUNDS_CTR_FISTA INTO @DATA(ld_i_fm_bossnam). | ||||
| "SELECT single FM_DFONDS FROM PTRV_WEB_FUNDS_CTR_FISTA INTO @DATA(ld_i_fm_dfonds). | ||||
| DATA(ld_i_maxrow) | = 50. | |||
Search for further information about these or an SAP related objects