SAP HRXSS_SPA_SUBMIT Function Module for RFC Submit Package
HRXSS_SPA_SUBMIT is a standard hrxss spa submit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RFC Submit Package 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 hrxss spa submit FM, simply by entering the name HRXSS_SPA_SUBMIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRXSS_SPA
Program Name: SAPLHRXSS_SPA
Main Program: SAPLHRXSS_SPA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function HRXSS_SPA_SUBMIT 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 'HRXSS_SPA_SUBMIT'"RFC Submit Package.
EXPORTING
REQUEST_ID = "Package variant ID
INFO_TABLE = "Salary packaging Salary component information table
VARIANTS_TABLE = "Table SPA_PACKAGE_VARIANT for SPA
SPA_EMPLOYEE_INFO = "HR-CM: Employee Data for Compensation Administration
PAY_FREQUENCE = "Payroll time units
VAR_F4_TABLE = "Table type DOMA for SPA
IMPORTING
REQUEST_DISP_TAB = "Salary packaging: package table
REQUEST_POOL_TAB = "Salary packaging: package table
HEADER_TEXT = "128 character
S1TXT_HEADER1 = "128 character
S1TXT_HEADER2 = "128 character
MESSAGES = "Table with BAPI Return Information
IMPORTING Parameters details for HRXSS_SPA_SUBMIT
REQUEST_ID - Package variant ID
Data type: SPA_PACKAGE_VARIANT-VARIDOptional: No
Call by Reference: No ( called with pass by value option)
INFO_TABLE - Salary packaging Salary component information table
Data type: INFO_TABOptional: No
Call by Reference: No ( called with pass by value option)
VARIANTS_TABLE - Table SPA_PACKAGE_VARIANT for SPA
Data type: HRXSS_SPA_PACKAGE_VARIANT_TOptional: No
Call by Reference: No ( called with pass by value option)
SPA_EMPLOYEE_INFO - HR-CM: Employee Data for Compensation Administration
Data type: HRCM_EMPINFOOptional: No
Call by Reference: No ( called with pass by value option)
PAY_FREQUENCE - Payroll time units
Data type: T549R-ZEINHOptional: No
Call by Reference: No ( called with pass by value option)
VAR_F4_TABLE - Table type DOMA for SPA
Data type: HRXSS_SPA_DOMA_TOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for HRXSS_SPA_SUBMIT
REQUEST_DISP_TAB - Salary packaging: package table
Data type: SPA_PACKAGE_TABOptional: No
Call by Reference: No ( called with pass by value option)
REQUEST_POOL_TAB - Salary packaging: package table
Data type: SPA_PACKAGE_TABOptional: No
Call by Reference: No ( called with pass by value option)
HEADER_TEXT - 128 character
Data type: CHAR128Optional: No
Call by Reference: No ( called with pass by value option)
S1TXT_HEADER1 - 128 character
Data type: CHAR128Optional: No
Call by Reference: No ( called with pass by value option)
S1TXT_HEADER2 - 128 character
Data type: CHAR128Optional: No
Call by Reference: No ( called with pass by value option)
MESSAGES - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HRXSS_SPA_SUBMIT 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_request_id | TYPE SPA_PACKAGE_VARIANT-VARID, " | |||
| lv_request_disp_tab | TYPE SPA_PACKAGE_TAB, " | |||
| lv_info_table | TYPE INFO_TAB, " | |||
| lv_request_pool_tab | TYPE SPA_PACKAGE_TAB, " | |||
| lv_header_text | TYPE CHAR128, " | |||
| lv_variants_table | TYPE HRXSS_SPA_PACKAGE_VARIANT_T, " | |||
| lv_s1txt_header1 | TYPE CHAR128, " | |||
| lv_spa_employee_info | TYPE HRCM_EMPINFO, " | |||
| lv_pay_frequence | TYPE T549R-ZEINH, " | |||
| lv_s1txt_header2 | TYPE CHAR128, " | |||
| lv_messages | TYPE BAPIRETTAB, " | |||
| lv_var_f4_table | TYPE HRXSS_SPA_DOMA_T. " |
|   CALL FUNCTION 'HRXSS_SPA_SUBMIT' "RFC Submit Package |
| EXPORTING | ||
| REQUEST_ID | = lv_request_id | |
| INFO_TABLE | = lv_info_table | |
| VARIANTS_TABLE | = lv_variants_table | |
| SPA_EMPLOYEE_INFO | = lv_spa_employee_info | |
| PAY_FREQUENCE | = lv_pay_frequence | |
| VAR_F4_TABLE | = lv_var_f4_table | |
| IMPORTING | ||
| REQUEST_DISP_TAB | = lv_request_disp_tab | |
| REQUEST_POOL_TAB | = lv_request_pool_tab | |
| HEADER_TEXT | = lv_header_text | |
| S1TXT_HEADER1 | = lv_s1txt_header1 | |
| S1TXT_HEADER2 | = lv_s1txt_header2 | |
| MESSAGES | = lv_messages | |
| . " HRXSS_SPA_SUBMIT | ||
ABAP code using 7.40 inline data declarations to call FM HRXSS_SPA_SUBMIT
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 VARID FROM SPA_PACKAGE_VARIANT INTO @DATA(ld_request_id). | ||||
| "SELECT single ZEINH FROM T549R INTO @DATA(ld_pay_frequence). | ||||
Search for further information about these or an SAP related objects