SAP /PM0/FPP_INTERFACE Function Module for









/PM0/FPP_INTERFACE is a standard /pm0/fpp interface SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 /pm0/fpp interface FM, simply by entering the name /PM0/FPP_INTERFACE into the relevant SAP transaction such as SE37 or SE38.

Function Group: /PM0/FPP1
Program Name: /PM0/SAPLFPP1
Main Program: /PM0/SAPLFPP1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function /PM0/FPP_INTERFACE 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 '/PM0/FPP_INTERFACE'"
  EXPORTING
*  INTERVAL_NUMBER =  "
*  APPL =  "
*  MID =  "
*  APPLCATG =  "
*  PROGNAME =  "
*  PROGDATE =  "
*  PROGNUMBER =  "
*  JOBNO =  "
*  PID =  "
*  JOBCOUNT =  "
*  JOBNAME =  "

 IMPORTING
   E_INTERVAL_NUMBER =  "
   E_APPL =  "
   E_MID =  "
   E_APPLCATG =  "
   E_PROGNAME =  "
   E_PROGDATE =  "
   E_PROGNUMBER =  "
   E_JOBNO =  "
   E_PID =  "
   E_JOBCOUNT =  "
   E_JOBNAME =  "
.



IMPORTING Parameters details for /PM0/FPP_INTERFACE

INTERVAL_NUMBER -

Data type: /PM0/FPP_INT_NUM
Optional: Yes
Call by Reference: Yes

APPL -

Data type: /PM0/FPP_APPL
Optional: Yes
Call by Reference: Yes

MID -

Data type: /PM0/FPP_MID
Optional: Yes
Call by Reference: Yes

APPLCATG -

Data type: BANK_DTE_PP_PAAPPLCATG
Optional: Yes
Call by Reference: Yes

PROGNAME -

Data type: BANK_DTE_PP_PROGN
Optional: Yes
Call by Reference: Yes

PROGDATE -

Data type: BANK_DTE_PP_PROGDATE
Optional: Yes
Call by Reference: Yes

PROGNUMBER -

Data type: BANK_DTE_PP_PROGNO
Optional: Yes
Call by Reference: Yes

JOBNO -

Data type: BANK_DTE_PP_JOBNO
Optional: Yes
Call by Reference: Yes

PID -

Data type: /PM0/FPP_PID
Optional: Yes
Call by Reference: Yes

JOBCOUNT -

Data type: BTCJOBCNT
Optional: Yes
Call by Reference: Yes

JOBNAME -

Data type: BTCJOB
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for /PM0/FPP_INTERFACE

E_INTERVAL_NUMBER -

Data type: /PM0/FPP_INT_NUM
Optional: No
Call by Reference: Yes

E_APPL -

Data type: /PM0/FPP_APPL
Optional: No
Call by Reference: Yes

E_MID -

Data type: /PM0/FPP_MID
Optional: No
Call by Reference: Yes

E_APPLCATG -

Data type: BANK_DTE_PP_PAAPPLCATG
Optional: No
Call by Reference: Yes

E_PROGNAME -

Data type: BANK_DTE_PP_PROGN
Optional: No
Call by Reference: Yes

E_PROGDATE -

Data type: BANK_DTE_PP_PROGDATE
Optional: No
Call by Reference: Yes

E_PROGNUMBER -

Data type: BANK_DTE_PP_PROGNO
Optional: No
Call by Reference: Yes

E_JOBNO -

Data type: BANK_DTE_PP_JOBNO
Optional: No
Call by Reference: Yes

E_PID -

Data type: /PM0/FPP_PID
Optional: No
Call by Reference: Yes

E_JOBCOUNT -

Data type: BTCJOBCNT
Optional: No
Call by Reference: Yes

E_JOBNAME -

Data type: BTCJOB
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /PM0/FPP_INTERFACE 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_interval_number  TYPE /PM0/FPP_INT_NUM, "   
lv_e_interval_number  TYPE /PM0/FPP_INT_NUM, "   
lv_appl  TYPE /PM0/FPP_APPL, "   
lv_e_appl  TYPE /PM0/FPP_APPL, "   
lv_mid  TYPE /PM0/FPP_MID, "   
lv_e_mid  TYPE /PM0/FPP_MID, "   
lv_applcatg  TYPE BANK_DTE_PP_PAAPPLCATG, "   
lv_e_applcatg  TYPE BANK_DTE_PP_PAAPPLCATG, "   
lv_progname  TYPE BANK_DTE_PP_PROGN, "   
lv_e_progname  TYPE BANK_DTE_PP_PROGN, "   
lv_progdate  TYPE BANK_DTE_PP_PROGDATE, "   
lv_e_progdate  TYPE BANK_DTE_PP_PROGDATE, "   
lv_prognumber  TYPE BANK_DTE_PP_PROGNO, "   
lv_e_prognumber  TYPE BANK_DTE_PP_PROGNO, "   
lv_jobno  TYPE BANK_DTE_PP_JOBNO, "   
lv_e_jobno  TYPE BANK_DTE_PP_JOBNO, "   
lv_pid  TYPE /PM0/FPP_PID, "   
lv_e_pid  TYPE /PM0/FPP_PID, "   
lv_jobcount  TYPE BTCJOBCNT, "   
lv_e_jobcount  TYPE BTCJOBCNT, "   
lv_jobname  TYPE BTCJOB, "   
lv_e_jobname  TYPE BTCJOB. "   

  CALL FUNCTION '/PM0/FPP_INTERFACE'  "
    EXPORTING
         INTERVAL_NUMBER = lv_interval_number
         APPL = lv_appl
         MID = lv_mid
         APPLCATG = lv_applcatg
         PROGNAME = lv_progname
         PROGDATE = lv_progdate
         PROGNUMBER = lv_prognumber
         JOBNO = lv_jobno
         PID = lv_pid
         JOBCOUNT = lv_jobcount
         JOBNAME = lv_jobname
    IMPORTING
         E_INTERVAL_NUMBER = lv_e_interval_number
         E_APPL = lv_e_appl
         E_MID = lv_e_mid
         E_APPLCATG = lv_e_applcatg
         E_PROGNAME = lv_e_progname
         E_PROGDATE = lv_e_progdate
         E_PROGNUMBER = lv_e_prognumber
         E_JOBNO = lv_e_jobno
         E_PID = lv_e_pid
         E_JOBCOUNT = lv_e_jobcount
         E_JOBNAME = lv_e_jobname
. " /PM0/FPP_INTERFACE




ABAP code using 7.40 inline data declarations to call FM /PM0/FPP_INTERFACE

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



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!