SAP RPM_CHANGE_RELATE_DATA Function Module for Create a relationship object Assignment









RPM_CHANGE_RELATE_DATA is a standard rpm change relate 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 Create a relationship object Assignment 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 change relate data FM, simply by entering the name RPM_CHANGE_RELATE_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: RPM_RELATE
Program Name: SAPLRPM_RELATE
Main Program: SAPLRPM_RELATE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RPM_CHANGE_RELATE_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_CHANGE_RELATE_DATA'"Create a relationship object Assignment
  EXPORTING
   IV_PROJECT_ID =  "Project Planning: External Indentifier of an Element
   IV_RELATE_TYPE =  "RPM Relation type
*  IV_TASK_ID =  "Task External ID
*  IV_ROLE_ID =  "Role External ID
*  IV_RESOURCE_ID =  "Resource External ID
*  IV_TEAM_ID =  "Team External ID
*  IS_ATTRIBUTES =  "External Attributes for Relation assignments
*  IV_SIMULATION =  "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
*  IV_LANGUAGE =  "Language according to ISO 639

 IMPORTING
   EV_RC =  "Return code (0 => successful)
   EV_MSG =  "Message
.



IMPORTING Parameters details for RPM_CHANGE_RELATE_DATA

IV_PROJECT_ID - Project Planning: External Indentifier of an Element

Data type: RPM_TV_EXTID
Optional: No
Call by Reference: No ( called with pass by value option)

IV_RELATE_TYPE - RPM Relation type

Data type: RPM_RV_RELTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

IV_TASK_ID - Task External ID

Data type: RPM_TV_EXTID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_ROLE_ID - Role External ID

Data type: RPM_TV_EXTID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_RESOURCE_ID - Resource External ID

Data type: RPM_TV_EXTID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TEAM_ID - Team External ID

Data type: RPM_TV_EXTID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_ATTRIBUTES - External Attributes for Relation assignments

Data type: RPM_TS_RELATE_API
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SIMULATION - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

Data type: BOOLE_D
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_LANGUAGE - Language according to ISO 639

Data type: LAISO
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RPM_CHANGE_RELATE_DATA

EV_RC - Return code (0 => successful)

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

EV_MSG - Message

Data type: STRING
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RPM_CHANGE_RELATE_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:
lv_ev_rc  TYPE I, "   
lv_iv_project_id  TYPE RPM_TV_EXTID, "   
lv_ev_msg  TYPE STRING, "   
lv_iv_relate_type  TYPE RPM_RV_RELTYPE, "   
lv_iv_task_id  TYPE RPM_TV_EXTID, "   
lv_iv_role_id  TYPE RPM_TV_EXTID, "   
lv_iv_resource_id  TYPE RPM_TV_EXTID, "   
lv_iv_team_id  TYPE RPM_TV_EXTID, "   
lv_is_attributes  TYPE RPM_TS_RELATE_API, "   
lv_iv_simulation  TYPE BOOLE_D, "   
lv_iv_language  TYPE LAISO. "   

  CALL FUNCTION 'RPM_CHANGE_RELATE_DATA'  "Create a relationship object Assignment
    EXPORTING
         IV_PROJECT_ID = lv_iv_project_id
         IV_RELATE_TYPE = lv_iv_relate_type
         IV_TASK_ID = lv_iv_task_id
         IV_ROLE_ID = lv_iv_role_id
         IV_RESOURCE_ID = lv_iv_resource_id
         IV_TEAM_ID = lv_iv_team_id
         IS_ATTRIBUTES = lv_is_attributes
         IV_SIMULATION = lv_iv_simulation
         IV_LANGUAGE = lv_iv_language
    IMPORTING
         EV_RC = lv_ev_rc
         EV_MSG = lv_ev_msg
. " RPM_CHANGE_RELATE_DATA




ABAP code using 7.40 inline data declarations to call FM RPM_CHANGE_RELATE_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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!