SAP RPM_TASK_SPLIT_ATTRIBUTES Function Module for RPM: Split up integrated attributes into DB format
RPM_TASK_SPLIT_ATTRIBUTES is a standard rpm task split attributes SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RPM: Split up integrated attributes into DB format 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 rpm task split attributes FM, simply by entering the name RPM_TASK_SPLIT_ATTRIBUTES into the relevant SAP transaction such as SE37 or SE38.
Function Group: RPM_DB
Program Name: SAPLRPM_DB
Main Program: SAPLRPM_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RPM_TASK_SPLIT_ATTRIBUTES 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 'RPM_TASK_SPLIT_ATTRIBUTES'"RPM: Split up integrated attributes into DB format.
EXPORTING
IT_TASKS_INT = "RPM Table Type: Task attributes stored in the database
IMPORTING
ET_TASKS_DB = "RPM: Task attribute DB table type
ET_TASKS_CUST_DB = "xRPM Task Customer Fields
ET_PROJ_DEPENDENCY_DB = "Project and Task Dependencies
IMPORTING Parameters details for RPM_TASK_SPLIT_ATTRIBUTES
IT_TASKS_INT - RPM Table Type: Task attributes stored in the database
Data type: RPM_TT_TASKS_DB_INTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RPM_TASK_SPLIT_ATTRIBUTES
ET_TASKS_DB - RPM: Task attribute DB table type
Data type: RPM_TT_TASK_DBOptional: No
Call by Reference: No ( called with pass by value option)
ET_TASKS_CUST_DB - xRPM Task Customer Fields
Data type: RPM_TT_TASKS_DB_CUSTOptional: No
Call by Reference: No ( called with pass by value option)
ET_PROJ_DEPENDENCY_DB - Project and Task Dependencies
Data type: RPM_TT_PROJ_DEPENDENCY_DBOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RPM_TASK_SPLIT_ATTRIBUTES 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_tasks_db | TYPE RPM_TT_TASK_DB, " | |||
| lv_it_tasks_int | TYPE RPM_TT_TASKS_DB_INT, " | |||
| lv_et_tasks_cust_db | TYPE RPM_TT_TASKS_DB_CUST, " | |||
| lv_et_proj_dependency_db | TYPE RPM_TT_PROJ_DEPENDENCY_DB. " |
|   CALL FUNCTION 'RPM_TASK_SPLIT_ATTRIBUTES' "RPM: Split up integrated attributes into DB format |
| EXPORTING | ||
| IT_TASKS_INT | = lv_it_tasks_int | |
| IMPORTING | ||
| ET_TASKS_DB | = lv_et_tasks_db | |
| ET_TASKS_CUST_DB | = lv_et_tasks_cust_db | |
| ET_PROJ_DEPENDENCY_DB | = lv_et_proj_dependency_db | |
| . " RPM_TASK_SPLIT_ATTRIBUTES | ||
ABAP code using 7.40 inline data declarations to call FM RPM_TASK_SPLIT_ATTRIBUTES
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