SAP SPAM_CREATE_HR_SUBCOMPS Function Module for
SPAM_CREATE_HR_SUBCOMPS is a standard spam create hr subcomps 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 spam create hr subcomps FM, simply by entering the name SPAM_CREATE_HR_SUBCOMPS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SPAM
Program Name: SAPLSPAM
Main Program: SAPLSPAM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SPAM_CREATE_HR_SUBCOMPS 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 'SPAM_CREATE_HR_SUBCOMPS'".
EXPORTING
* IV_MASTERCOMP = ' ' "
IMPORTING
ET_MSGS = "
EXCEPTIONS
T500L_SUBCOMP_DOESNT_EXIST = 1 INTERNAL_ERROR = 2
IMPORTING Parameters details for SPAM_CREATE_HR_SUBCOMPS
IV_MASTERCOMP -
Data type: DLVUNITDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SPAM_CREATE_HR_SUBCOMPS
ET_MSGS -
Data type: SPROT_U_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
T500L_SUBCOMP_DOESNT_EXIST -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SPAM_CREATE_HR_SUBCOMPS 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_et_msgs | TYPE SPROT_U_TAB, " | |||
| lv_iv_mastercomp | TYPE DLVUNIT, " SPACE | |||
| lv_t500l_subcomp_doesnt_exist | TYPE DLVUNIT, " | |||
| lv_internal_error | TYPE DLVUNIT. " |
|   CALL FUNCTION 'SPAM_CREATE_HR_SUBCOMPS' " |
| EXPORTING | ||
| IV_MASTERCOMP | = lv_iv_mastercomp | |
| IMPORTING | ||
| ET_MSGS | = lv_et_msgs | |
| EXCEPTIONS | ||
| T500L_SUBCOMP_DOESNT_EXIST = 1 | ||
| INTERNAL_ERROR = 2 | ||
| . " SPAM_CREATE_HR_SUBCOMPS | ||
ABAP code using 7.40 inline data declarations to call FM SPAM_CREATE_HR_SUBCOMPS
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.| DATA(ld_iv_mastercomp) | = ' '. | |||
Search for further information about these or an SAP related objects