SAP BANK_DB_PP_PRE_INSERT_RUNDATA Function Module for









BANK_DB_PP_PRE_INSERT_RUNDATA is a standard bank db pp pre insert rundata 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 bank db pp pre insert rundata FM, simply by entering the name BANK_DB_PP_PRE_INSERT_RUNDATA into the relevant SAP transaction such as SE37 or SE38.

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



Function BANK_DB_PP_PRE_INSERT_RUNDATA 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 'BANK_DB_PP_PRE_INSERT_RUNDATA'"
  EXPORTING
   I_PROGN =  "Name of the Program/Report on an Application Process
   I_MAXSTEPNO =  "Number of a Processing Step
   I_XWRT_APPLLOG =  "Checkbox Field
   I_LOGEXTNUMBER =  "Application Log: External ID
   I_PROGDATE =  "Date of Program Run
   I_PROGNO =  "Sequential Number of the Program Run
   I_RUNKEY_TECH =  "Technical Key for a Mass Run
   I_RUNID_EXT =  "External Identification of a Mass Run
   I_APPLCATG =  "Application Type in Parallel Processing
   I_APPL_PARAM_TYPE =  "Absolute Category Name of a Data Object
   I_PROCESS_ID =  "Process ID
   I_XSIMULATION =  "Indicator: simulation run

EXCEPTIONS
   INSERT_FAILED = 1
.



IMPORTING Parameters details for BANK_DB_PP_PRE_INSERT_RUNDATA

I_PROGN - Name of the Program/Report on an Application Process

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

I_MAXSTEPNO - Number of a Processing Step

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

I_XWRT_APPLLOG - Checkbox Field

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

I_LOGEXTNUMBER - Application Log: External ID

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

I_PROGDATE - Date of Program Run

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

I_PROGNO - Sequential Number of the Program Run

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

I_RUNKEY_TECH - Technical Key for a Mass Run

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

I_RUNID_EXT - External Identification of a Mass Run

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

I_APPLCATG - Application Type in Parallel Processing

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

I_APPL_PARAM_TYPE - Absolute Category Name of a Data Object

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

I_PROCESS_ID - Process ID

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

I_XSIMULATION - Indicator: simulation run

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

EXCEPTIONS details

INSERT_FAILED -

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

Copy and paste ABAP code example for BANK_DB_PP_PRE_INSERT_RUNDATA 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_progn  TYPE BANK_DTE_PP_PROGN, "   
lv_insert_failed  TYPE BANK_DTE_PP_PROGN, "   
lv_i_maxstepno  TYPE BANK_DTE_PP_STEPNO, "   
lv_i_xwrt_appllog  TYPE XFELD, "   
lv_i_logextnumber  TYPE BALNREXT, "   
lv_i_progdate  TYPE BANK_DTE_PP_PROGDATE, "   
lv_i_progno  TYPE BANK_DTE_PP_PROGNO, "   
lv_i_runkey_tech  TYPE BANK_DTE_PP_RUNKEY_TECH, "   
lv_i_runid_ext  TYPE BANK_DTE_PP_RUNID_EXT, "   
lv_i_applcatg  TYPE BANK_DTE_PP_PAAPPLCATG, "   
lv_i_appl_param_type  TYPE BANK_DTE_PP_ABSTYPENAME, "   
lv_i_process_id  TYPE BANK_DTE_JC_PROC_ID, "   
lv_i_xsimulation  TYPE BANK_DTE_PP_XSIMULRUN. "   

  CALL FUNCTION 'BANK_DB_PP_PRE_INSERT_RUNDATA'  "
    EXPORTING
         I_PROGN = lv_i_progn
         I_MAXSTEPNO = lv_i_maxstepno
         I_XWRT_APPLLOG = lv_i_xwrt_appllog
         I_LOGEXTNUMBER = lv_i_logextnumber
         I_PROGDATE = lv_i_progdate
         I_PROGNO = lv_i_progno
         I_RUNKEY_TECH = lv_i_runkey_tech
         I_RUNID_EXT = lv_i_runid_ext
         I_APPLCATG = lv_i_applcatg
         I_APPL_PARAM_TYPE = lv_i_appl_param_type
         I_PROCESS_ID = lv_i_process_id
         I_XSIMULATION = lv_i_xsimulation
    EXCEPTIONS
        INSERT_FAILED = 1
. " BANK_DB_PP_PRE_INSERT_RUNDATA




ABAP code using 7.40 inline data declarations to call FM BANK_DB_PP_PRE_INSERT_RUNDATA

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!