SAP ALE_PIRSRVAPS_SAVEMULTI Function Module for BAPI -> IDoc: ALE_PIRSRVAPS_SAVEMULTI

Search SAP Function Modules

ALE_PIRSRVAPS_SAVEMULTI is a standard ale pirsrvaps savemulti SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: ALE_PIRSRVAPS_SAVEMULTI 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 ale pirsrvaps savemulti FM, simply by entering the name ALE_PIRSRVAPS_SAVEMULTI into the relevant SAP transaction such as SE37 or SE38.

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

Function ALE_PIRSRVAPS_SAVEMULTI 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 'ALE_PIRSRVAPS_SAVEMULTI'"BAPI -> IDoc: ALE_PIRSRVAPS_SAVEMULTI
  EXPORTING
   LOGICALSYSTEM =  "
*  COMMITCONTROL = 'E' "
*  PLANNINGVERSION = '000' "
*  PLANNINGMODEUSAGE =  "
*  BUCKETCOMPARISON =  "
*  OBJ_TYPE = 'BUS10020' "
*  SERIAL_ID = '0' "

TABLES
   REQUIREMENTS =  "Data for Creating/Changing Forecast Orders
*  EXTENSIONIN =  "
   RECEIVERS =  "
*  COMMUNICATION_DOCUMENTS =  "
*  APPLICATION_OBJECTS =  "

EXCEPTIONS
   ERROR_CREATING_IDOCS = 1 

.

IMPORTING Parameters details for ALE_PIRSRVAPS_SAVEMULTI

LOGICALSYSTEM -

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

COMMITCONTROL -

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

PLANNINGVERSION -

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

PLANNINGMODEUSAGE -

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

BUCKETCOMPARISON -

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

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'BUS10020'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_PIRSRVAPS_SAVEMULTI

REQUIREMENTS - Data for Creating/Changing Forecast Orders

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

EXTENSIONIN -

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

RECEIVERS -

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

COMMUNICATION_DOCUMENTS -

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

APPLICATION_OBJECTS -

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

EXCEPTIONS details

ERROR_CREATING_IDOCS -

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

Copy and paste ABAP code example for ALE_PIRSRVAPS_SAVEMULTI 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.

ABAP code using 7.40 inline data declarations to call FM ALE_PIRSRVAPS_SAVEMULTI

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