SAP BAPI_PRTLOCSRVAPS_SAVEMULTI Function Module for Create or Change Partner Locations
BAPI_PRTLOCSRVAPS_SAVEMULTI is a standard bapi prtlocsrvaps 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 Create or Change Partner Locations 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 prtlocsrvaps savemulti FM, simply by entering the name BAPI_PRTLOCSRVAPS_SAVEMULTI into the relevant SAP transaction such as SE37 or SE38.
Function Group: 10012
Program Name: SAPL10012
Main Program: SAPL10012
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_PRTLOCSRVAPS_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 'BAPI_PRTLOCSRVAPS_SAVEMULTI'"Create or Change Partner Locations.
EXPORTING
LOGICAL_SYSTEM = "Logical System from which Message Originates
TABLES
* PARTNERLOCATION_HEAD = "Partner Location: Header Data
* PARTNERLOCATION_HEAD_X = "Partner Location: Header Data, Change Parameters
* PARTNERLOCATION_TEXT = "Partner Location: Return Structure Texts
* PARTNERLOCATION_TEXT_X = "Partner Location: Texts, Change Parameters
* RETURN = "Return Parameters
* EXTENSION_IN = "Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
IMPORTING Parameters details for BAPI_PRTLOCSRVAPS_SAVEMULTI
LOGICAL_SYSTEM - Logical System from which Message Originates
Data type: BAPISCMBGENFIELDS-LOGICAL_SYSTEMOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_PRTLOCSRVAPS_SAVEMULTI
PARTNERLOCATION_HEAD - Partner Location: Header Data
Data type: BAPI10012PRTLOCHEADOptional: Yes
Call by Reference: Yes
PARTNERLOCATION_HEAD_X - Partner Location: Header Data, Change Parameters
Data type: BAPI10012PRTLOCHEADXOptional: Yes
Call by Reference: Yes
PARTNERLOCATION_TEXT - Partner Location: Return Structure Texts
Data type: BAPI10012PRTLOCTEXTOptional: Yes
Call by Reference: Yes
PARTNERLOCATION_TEXT_X - Partner Location: Texts, Change Parameters
Data type: BAPI10012PRTLOCTEXTXOptional: Yes
Call by Reference: Yes
RETURN - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSION_IN - Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_PRTLOCSRVAPS_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.| DATA: | ||||
| lv_logical_system | TYPE BAPISCMBGENFIELDS-LOGICAL_SYSTEM, " | |||
| lt_partnerlocation_head | TYPE STANDARD TABLE OF BAPI10012PRTLOCHEAD, " | |||
| lt_partnerlocation_head_x | TYPE STANDARD TABLE OF BAPI10012PRTLOCHEADX, " | |||
| lt_partnerlocation_text | TYPE STANDARD TABLE OF BAPI10012PRTLOCTEXT, " | |||
| lt_partnerlocation_text_x | TYPE STANDARD TABLE OF BAPI10012PRTLOCTEXTX, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_extension_in | TYPE STANDARD TABLE OF BAPIPAREX. " |
|   CALL FUNCTION 'BAPI_PRTLOCSRVAPS_SAVEMULTI' "Create or Change Partner Locations |
| EXPORTING | ||
| LOGICAL_SYSTEM | = lv_logical_system | |
| TABLES | ||
| PARTNERLOCATION_HEAD | = lt_partnerlocation_head | |
| PARTNERLOCATION_HEAD_X | = lt_partnerlocation_head_x | |
| PARTNERLOCATION_TEXT | = lt_partnerlocation_text | |
| PARTNERLOCATION_TEXT_X | = lt_partnerlocation_text_x | |
| RETURN | = lt_return | |
| EXTENSION_IN | = lt_extension_in | |
| . " BAPI_PRTLOCSRVAPS_SAVEMULTI | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_PRTLOCSRVAPS_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.| "SELECT single LOGICAL_SYSTEM FROM BAPISCMBGENFIELDS INTO @DATA(ld_logical_system). | ||||
Search for further information about these or an SAP related objects