SAP RPM_MIGRATION_RETRIEVE_DATA Function Module for Retrieve data from various tables
RPM_MIGRATION_RETRIEVE_DATA is a standard rpm migration retrieve data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieve data from various tables 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 migration retrieve data FM, simply by entering the name RPM_MIGRATION_RETRIEVE_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: RPM_MIGRATION
Program Name: SAPLRPM_MIGRATION
Main Program: SAPLRPM_MIGRATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function RPM_MIGRATION_RETRIEVE_DATA 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_MIGRATION_RETRIEVE_DATA'"Retrieve data from various tables.
EXPORTING
* IT_EXTERNAL_ID = "Table for having multiple project ids
IMPORTING
ET_RPM_OBJ_LINKS = "Object Link Table Type
TABLES
* ET_RPM_PROJECT = "Project data
* ET_RPM_ROLES_CUST = "Customer Fields for Role
* ET_RPM_ROLE_DEMANDS = "Project Role Demand
* ET_RPM_TASKS = "Project Task Data
* ET_RPM_TASKS_CUST = "Customer Fields at Task Level
* ET_RPM_RESOURCES = "Project Resource
* ET_RPM_RELATES = "RPM: Relationship table
* ET_RPM_RELATES_CUST = "Customer Fields for Relatinship
* ET_RPM_RESOURCE_ALLOCS = "RPM: Relationship table
* ET_RPM_ROLE_SKILL = "Skill sets for roles
* ET_CGPL_PROJECT = "Project Planning: Project Headers Attribute Table
* ET_RPM_PROJECT_CUST = "RPM Project: Customer data
* ET_CGPL_TASK = "Project Planning: Activities Attribute Table
* ET_CGPL_TEXT = "Proj. Planning of Lang. Depend. Short Text for Proj./Tasks
* ET_RPM_PROJECT_DER = "Project data
* ET_CGPL_HIERARCHY = "Project Planning: Activities and Projects Hierarchy Table
* ET_RPM_PROJ_STKHLD = "Project Stakeholders
* ET_RPM_ROLES = "RPM: Role attributes
IMPORTING Parameters details for RPM_MIGRATION_RETRIEVE_DATA
IT_EXTERNAL_ID - Table for having multiple project ids
Data type: RPM_TT_FI_RANGE_PROJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RPM_MIGRATION_RETRIEVE_DATA
ET_RPM_OBJ_LINKS - Object Link Table Type
Data type: RPM_TT_OBJ_LINK_DBOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RPM_MIGRATION_RETRIEVE_DATA
ET_RPM_PROJECT - Project data
Data type: RPM_PROJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_ROLES_CUST - Customer Fields for Role
Data type: RPM_ROLE_CUSTOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_ROLE_DEMANDS - Project Role Demand
Data type: RPM_ROLE_AVLOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_TASKS - Project Task Data
Data type: RPM_TASKOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_TASKS_CUST - Customer Fields at Task Level
Data type: RPM_TASK_CUSTOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_RESOURCES - Project Resource
Data type: RPM_RESOURCEOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_RELATES - RPM: Relationship table
Data type: RPM_RELATEOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_RELATES_CUST - Customer Fields for Relatinship
Data type: RPM_RELATE_CUSTOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_RESOURCE_ALLOCS - RPM: Relationship table
Data type: RPM_RELATE_ALLOCOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_ROLE_SKILL - Skill sets for roles
Data type: RPM_ROLE_SKILLOptional: Yes
Call by Reference: Yes
ET_CGPL_PROJECT - Project Planning: Project Headers Attribute Table
Data type: CGPL_PROJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_PROJECT_CUST - RPM Project: Customer data
Data type: RPM_PROJECT_CUSTOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_CGPL_TASK - Project Planning: Activities Attribute Table
Data type: CGPL_TASKOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_CGPL_TEXT - Proj. Planning of Lang. Depend. Short Text for Proj./Tasks
Data type: CGPL_TEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_PROJECT_DER - Project data
Data type: RPM_PROJECT_DEROptional: Yes
Call by Reference: No ( called with pass by value option)
ET_CGPL_HIERARCHY - Project Planning: Activities and Projects Hierarchy Table
Data type: CGPL_HIERARCHYOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_PROJ_STKHLD - Project Stakeholders
Data type: RPM_PROJ_STKHLDOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RPM_ROLES - RPM: Role attributes
Data type: RPM_ROLEOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RPM_MIGRATION_RETRIEVE_DATA 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: | ||||
lt_et_rpm_project | TYPE STANDARD TABLE OF RPM_PROJECT, " | |||
lv_it_external_id | TYPE RPM_TT_FI_RANGE_PROJID, " | |||
lv_et_rpm_obj_links | TYPE RPM_TT_OBJ_LINK_DB, " | |||
lt_et_rpm_roles_cust | TYPE STANDARD TABLE OF RPM_ROLE_CUST, " | |||
lt_et_rpm_role_demands | TYPE STANDARD TABLE OF RPM_ROLE_AVL, " | |||
lt_et_rpm_tasks | TYPE STANDARD TABLE OF RPM_TASK, " | |||
lt_et_rpm_tasks_cust | TYPE STANDARD TABLE OF RPM_TASK_CUST, " | |||
lt_et_rpm_resources | TYPE STANDARD TABLE OF RPM_RESOURCE, " | |||
lt_et_rpm_relates | TYPE STANDARD TABLE OF RPM_RELATE, " | |||
lt_et_rpm_relates_cust | TYPE STANDARD TABLE OF RPM_RELATE_CUST, " | |||
lt_et_rpm_resource_allocs | TYPE STANDARD TABLE OF RPM_RELATE_ALLOC, " | |||
lt_et_rpm_role_skill | TYPE STANDARD TABLE OF RPM_ROLE_SKILL, " | |||
lt_et_cgpl_project | TYPE STANDARD TABLE OF CGPL_PROJECT, " | |||
lt_et_rpm_project_cust | TYPE STANDARD TABLE OF RPM_PROJECT_CUST, " | |||
lt_et_cgpl_task | TYPE STANDARD TABLE OF CGPL_TASK, " | |||
lt_et_cgpl_text | TYPE STANDARD TABLE OF CGPL_TEXT, " | |||
lt_et_rpm_project_der | TYPE STANDARD TABLE OF RPM_PROJECT_DER, " | |||
lt_et_cgpl_hierarchy | TYPE STANDARD TABLE OF CGPL_HIERARCHY, " | |||
lt_et_rpm_proj_stkhld | TYPE STANDARD TABLE OF RPM_PROJ_STKHLD, " | |||
lt_et_rpm_roles | TYPE STANDARD TABLE OF RPM_ROLE. " |
  CALL FUNCTION 'RPM_MIGRATION_RETRIEVE_DATA' "Retrieve data from various tables |
EXPORTING | ||
IT_EXTERNAL_ID | = lv_it_external_id | |
IMPORTING | ||
ET_RPM_OBJ_LINKS | = lv_et_rpm_obj_links | |
TABLES | ||
ET_RPM_PROJECT | = lt_et_rpm_project | |
ET_RPM_ROLES_CUST | = lt_et_rpm_roles_cust | |
ET_RPM_ROLE_DEMANDS | = lt_et_rpm_role_demands | |
ET_RPM_TASKS | = lt_et_rpm_tasks | |
ET_RPM_TASKS_CUST | = lt_et_rpm_tasks_cust | |
ET_RPM_RESOURCES | = lt_et_rpm_resources | |
ET_RPM_RELATES | = lt_et_rpm_relates | |
ET_RPM_RELATES_CUST | = lt_et_rpm_relates_cust | |
ET_RPM_RESOURCE_ALLOCS | = lt_et_rpm_resource_allocs | |
ET_RPM_ROLE_SKILL | = lt_et_rpm_role_skill | |
ET_CGPL_PROJECT | = lt_et_cgpl_project | |
ET_RPM_PROJECT_CUST | = lt_et_rpm_project_cust | |
ET_CGPL_TASK | = lt_et_cgpl_task | |
ET_CGPL_TEXT | = lt_et_cgpl_text | |
ET_RPM_PROJECT_DER | = lt_et_rpm_project_der | |
ET_CGPL_HIERARCHY | = lt_et_cgpl_hierarchy | |
ET_RPM_PROJ_STKHLD | = lt_et_rpm_proj_stkhld | |
ET_RPM_ROLES | = lt_et_rpm_roles | |
. " RPM_MIGRATION_RETRIEVE_DATA |
ABAP code using 7.40 inline data declarations to call FM RPM_MIGRATION_RETRIEVE_DATA
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