SAP ALE_ORGMASTER_SAVE_REPL_MULT Function Module for
ALE_ORGMASTER_SAVE_REPL_MULT is a standard ale orgmaster save repl mult 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 ale orgmaster save repl mult FM, simply by entering the name ALE_ORGMASTER_SAVE_REPL_MULT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RHALMULT1
Program Name: SAPLRHALMULT1
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALE_ORGMASTER_SAVE_REPL_MULT 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_ORGMASTER_SAVE_REPL_MULT'".
EXPORTING
* SERIAL_ID = '0' "
TABLES
HROBJECTHEADER = "
* PDOBJECTADDRESS = "
* PDOBJECTMAILADDRESS = "
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
* HRINFOTYPEHEADER = "
* PDOBJECT = "
* PDOBJECTRELATIONSHIPS = "
* PDRELSPECIFIEDSUBSTITUTE = "
* PDRELMESSAGETYPE = "
* PDOBJECTDESCRIPTION = "
* PDOBJECTSTANDARDPROFILES = "
* PDOBJECTPDPROFILES = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for ALE_ORGMASTER_SAVE_REPL_MULT
SERIAL_ID -
Data type: SERIAL-CHNUMDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ALE_ORGMASTER_SAVE_REPL_MULT
HROBJECTHEADER -
Data type: BAPIHROBJOptional: No
Call by Reference: No ( called with pass by value option)
PDOBJECTADDRESS -
Data type: BAPIHR1028Optional: Yes
Call by Reference: No ( called with pass by value option)
PDOBJECTMAILADDRESS -
Data type: BAPIHR1032Optional: Yes
Call by Reference: No ( called with pass by value option)
RECEIVERS -
Data type: BDI_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_DOCUMENTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
APPLICATION_OBJECTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
HRINFOTYPEHEADER -
Data type: BAPIHRINFOptional: Yes
Call by Reference: No ( called with pass by value option)
PDOBJECT -
Data type: BAPIHR1000Optional: Yes
Call by Reference: No ( called with pass by value option)
PDOBJECTRELATIONSHIPS -
Data type: BAPIHR1001Optional: Yes
Call by Reference: No ( called with pass by value option)
PDRELSPECIFIEDSUBSTITUTE -
Data type: BAPIHRADD2Optional: Yes
Call by Reference: No ( called with pass by value option)
PDRELMESSAGETYPE -
Data type: BAPIHRADXNOptional: Yes
Call by Reference: No ( called with pass by value option)
PDOBJECTDESCRIPTION -
Data type: BAPIHR1002Optional: Yes
Call by Reference: No ( called with pass by value option)
PDOBJECTSTANDARDPROFILES -
Data type: BAPIHR1016Optional: Yes
Call by Reference: No ( called with pass by value option)
PDOBJECTPDPROFILES -
Data type: BAPIHR1017Optional: 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_ORGMASTER_SAVE_REPL_MULT 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_serial_id | TYPE SERIAL-CHNUM, " '0' | |||
| lt_hrobjectheader | TYPE STANDARD TABLE OF BAPIHROBJ, " | |||
| lv_error_creating_idocs | TYPE BAPIHROBJ, " | |||
| lt_pdobjectaddress | TYPE STANDARD TABLE OF BAPIHR1028, " | |||
| lt_pdobjectmailaddress | TYPE STANDARD TABLE OF BAPIHR1032, " | |||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lt_hrinfotypeheader | TYPE STANDARD TABLE OF BAPIHRINF, " | |||
| lt_pdobject | TYPE STANDARD TABLE OF BAPIHR1000, " | |||
| lt_pdobjectrelationships | TYPE STANDARD TABLE OF BAPIHR1001, " | |||
| lt_pdrelspecifiedsubstitute | TYPE STANDARD TABLE OF BAPIHRADD2, " | |||
| lt_pdrelmessagetype | TYPE STANDARD TABLE OF BAPIHRADXN, " | |||
| lt_pdobjectdescription | TYPE STANDARD TABLE OF BAPIHR1002, " | |||
| lt_pdobjectstandardprofiles | TYPE STANDARD TABLE OF BAPIHR1016, " | |||
| lt_pdobjectpdprofiles | TYPE STANDARD TABLE OF BAPIHR1017. " |
|   CALL FUNCTION 'ALE_ORGMASTER_SAVE_REPL_MULT' " |
| EXPORTING | ||
| SERIAL_ID | = lv_serial_id | |
| TABLES | ||
| HROBJECTHEADER | = lt_hrobjectheader | |
| PDOBJECTADDRESS | = lt_pdobjectaddress | |
| PDOBJECTMAILADDRESS | = lt_pdobjectmailaddress | |
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| HRINFOTYPEHEADER | = lt_hrinfotypeheader | |
| PDOBJECT | = lt_pdobject | |
| PDOBJECTRELATIONSHIPS | = lt_pdobjectrelationships | |
| PDRELSPECIFIEDSUBSTITUTE | = lt_pdrelspecifiedsubstitute | |
| PDRELMESSAGETYPE | = lt_pdrelmessagetype | |
| PDOBJECTDESCRIPTION | = lt_pdobjectdescription | |
| PDOBJECTSTANDARDPROFILES | = lt_pdobjectstandardprofiles | |
| PDOBJECTPDPROFILES | = lt_pdobjectpdprofiles | |
| EXCEPTIONS | ||
| ERROR_CREATING_IDOCS = 1 | ||
| . " ALE_ORGMASTER_SAVE_REPL_MULT | ||
ABAP code using 7.40 inline data declarations to call FM ALE_ORGMASTER_SAVE_REPL_MULT
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 CHNUM FROM SERIAL INTO @DATA(ld_serial_id). | ||||
| DATA(ld_serial_id) | = '0'. | |||
Search for further information about these or an SAP related objects