SAP BAPI_PIRSRVAPS_DELMULTI Function Module for Deletion of Planned Independent Requirements









BAPI_PIRSRVAPS_DELMULTI is a standard bapi pirsrvaps delmulti SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Deletion of Planned Independent Requirements 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 bapi pirsrvaps delmulti FM, simply by entering the name BAPI_PIRSRVAPS_DELMULTI into the relevant SAP transaction such as SE37 or SE38.

Function Group: 10020
Program Name: SAPL10020
Main Program: SAPL10020
Appliation area: C
Release date: 12-Dec-2002
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_PIRSRVAPS_DELMULTI 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 'BAPI_PIRSRVAPS_DELMULTI'"Deletion of Planned Independent Requirements
  EXPORTING
   LOGICAL_SYSTEM =  "Logical System from which Query Originates
*  COMMIT_CONTROL = 'E' "COMMIT Control
*  PLANNING_VERSION = '000' "Planning Version (Operative or Simulation Version)
*  PLANNING_MODE_USAGE =  "Parameters for Controlling the Scheduling Mode

TABLES
   REQUIREMENT_KEYS =  "Data for Deleting Planned Independent Requirements
*  RETURN =  "Messages Generated During Call
*  EXTENSION_IN =  "Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
.



IMPORTING Parameters details for BAPI_PIRSRVAPS_DELMULTI

LOGICAL_SYSTEM - Logical System from which Query Originates

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

COMMIT_CONTROL - COMMIT Control

Data type: BAPI10020GENFIELDS-COMMCTRL
Default: 'E'
Optional: No
Call by Reference: No ( called with pass by value option)

PLANNING_VERSION - Planning Version (Operative or Simulation Version)

Data type: BAPIGENFIELDS-VRSIOEX
Default: '000'
Optional: No
Call by Reference: No ( called with pass by value option)

PLANNING_MODE_USAGE - Parameters for Controlling the Scheduling Mode

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

TABLES Parameters details for BAPI_PIRSRVAPS_DELMULTI

REQUIREMENT_KEYS - Data for Deleting Planned Independent Requirements

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

RETURN - Messages Generated During Call

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

EXTENSION_IN - Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut

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

Copy and paste ABAP code example for BAPI_PIRSRVAPS_DELMULTI 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_logical_system  TYPE BAPIGENFIELDS-LOGSYSTEM, "   
lt_requirement_keys  TYPE STANDARD TABLE OF BAPI10020PIRDEL, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_commit_control  TYPE BAPI10020GENFIELDS-COMMCTRL, "   'E'
lt_extension_in  TYPE STANDARD TABLE OF BAPIPAREX, "   
lv_planning_version  TYPE BAPIGENFIELDS-VRSIOEX, "   '000'
lv_planning_mode_usage  TYPE BAPI10020GENFIELDS-PLANNING_MODE. "   

  CALL FUNCTION 'BAPI_PIRSRVAPS_DELMULTI'  "Deletion of Planned Independent Requirements
    EXPORTING
         LOGICAL_SYSTEM = lv_logical_system
         COMMIT_CONTROL = lv_commit_control
         PLANNING_VERSION = lv_planning_version
         PLANNING_MODE_USAGE = lv_planning_mode_usage
    TABLES
         REQUIREMENT_KEYS = lt_requirement_keys
         RETURN = lt_return
         EXTENSION_IN = lt_extension_in
. " BAPI_PIRSRVAPS_DELMULTI




ABAP code using 7.40 inline data declarations to call FM BAPI_PIRSRVAPS_DELMULTI

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 LOGSYSTEM FROM BAPIGENFIELDS INTO @DATA(ld_logical_system).
 
 
 
"SELECT single COMMCTRL FROM BAPI10020GENFIELDS INTO @DATA(ld_commit_control).
DATA(ld_commit_control) = 'E'.
 
 
"SELECT single VRSIOEX FROM BAPIGENFIELDS INTO @DATA(ld_planning_version).
DATA(ld_planning_version) = '000'.
 
"SELECT single PLANNING_MODE FROM BAPI10020GENFIELDS INTO @DATA(ld_planning_mode_usage).
 


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!