SAP RPM_CREATE_TEAM Function Module for RPM: Create a new project team









RPM_CREATE_TEAM is a standard rpm create team 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: Create a new project team 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 create team FM, simply by entering the name RPM_CREATE_TEAM into the relevant SAP transaction such as SE37 or SE38.

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



Function RPM_CREATE_TEAM 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_CREATE_TEAM'"RPM: Create a new project team
  EXPORTING
   IV_PROJECT_ID =  "Project Planning: External Indentifier of an Element
*  IV_PARENT_ID =  "Project Planning: External Indentifier of an Element
   IS_TEAM_INT =  "Project Team Attributes
*  IS_RESOURCE_TEMPL_INT =  "RPM Structure: Resource attributes (integrated)
*  IV_LANGUAGE =  "Language according to ISO 639
*  IV_SIMULATION =  "Checkbox
   IT_TEAM_MEMBERS =  "Team Member List

 IMPORTING
   ER_TEAM =  "Resource application object
   EV_RC =  "Return code (0 => successful)
   EV_MSG =  "Message
.



IMPORTING Parameters details for RPM_CREATE_TEAM

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_PARENT_ID - Project Planning: External Indentifier of an Element

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

IS_TEAM_INT - Project Team Attributes

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

IS_RESOURCE_TEMPL_INT - RPM Structure: Resource attributes (integrated)

Data type: RPM_TS_RESOURCE_INT
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)

IV_SIMULATION - Checkbox

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

IT_TEAM_MEMBERS - Team Member List

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

EXPORTING Parameters details for RPM_CREATE_TEAM

ER_TEAM - Resource application object

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

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_CREATE_TEAM 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_er_team  TYPE CL_RPM_TEAM, "   
lv_iv_project_id  TYPE RPM_TV_EXTID, "   
lv_ev_rc  TYPE I, "   
lv_iv_parent_id  TYPE RPM_TV_EXTID, "   
lv_ev_msg  TYPE STRING, "   
lv_is_team_int  TYPE RPM_TS_TEAM_INT, "   
lv_is_resource_templ_int  TYPE RPM_TS_RESOURCE_INT, "   
lv_iv_language  TYPE LAISO, "   
lv_iv_simulation  TYPE BOOLE_D, "   
lv_it_team_members  TYPE RPM_TT_TEAM_MEMBERS. "   

  CALL FUNCTION 'RPM_CREATE_TEAM'  "RPM: Create a new project team
    EXPORTING
         IV_PROJECT_ID = lv_iv_project_id
         IV_PARENT_ID = lv_iv_parent_id
         IS_TEAM_INT = lv_is_team_int
         IS_RESOURCE_TEMPL_INT = lv_is_resource_templ_int
         IV_LANGUAGE = lv_iv_language
         IV_SIMULATION = lv_iv_simulation
         IT_TEAM_MEMBERS = lv_it_team_members
    IMPORTING
         ER_TEAM = lv_er_team
         EV_RC = lv_ev_rc
         EV_MSG = lv_ev_msg
. " RPM_CREATE_TEAM




ABAP code using 7.40 inline data declarations to call FM RPM_CREATE_TEAM

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!