SAP RPM_IF_PROJECT_DATA_OUTBOUND Function Module for Outbound Processing of the Project Interfacing Process









RPM_IF_PROJECT_DATA_OUTBOUND is a standard rpm if project data outbound SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Outbound Processing of the Project Interfacing Process 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 if project data outbound FM, simply by entering the name RPM_IF_PROJECT_DATA_OUTBOUND into the relevant SAP transaction such as SE37 or SE38.

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



Function RPM_IF_PROJECT_DATA_OUTBOUND 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_IF_PROJECT_DATA_OUTBOUND'"Outbound Processing of the Project Interfacing Process
  EXPORTING
*  IV_ADJUST_BPS =  "Checkbox
*  IT_ROLES =  "Roles to be synchronized
*  IT_RESOURCES =  "Resources to be synchronized
*  IT_TEAMS =  "Teams to be synchronized
*  IT_RELATES =  "Relationships to be synchronized
*  IV_ADJUST_XRPM = 'X' "Checkbox
*  IV_SIMULATION = 'X' "Checkbox
*  IV_LANGUAGE =  "Language according to ISO 639
*  IV_BPS_APPLICATION =  "Application
*  IV_BPS_SYSTEM =  "Logical system
*  IV_RPM_PROJECT_ID =  "External ID
*  IS_PROJECT =  "Project data to be synchronized
*  IT_TASKS =  "Tasks to be synchronized

 IMPORTING
   ES_PROJECT =  "Project data to be synchronized
   ET_TASKS =  "Tasks to be synchronized
   ET_ROLES =  "Roles to be synchronized
   ET_RESOURCES =  "Resources to be synchronized
   ET_TEAMS =  "Teams to be synchronized
   ET_RELATES =  "Relationships to be synchronized
   ET_MSG =  "Table type for messages
   EV_MSG =  "
   EV_RC =  "
.



IMPORTING Parameters details for RPM_IF_PROJECT_DATA_OUTBOUND

IV_ADJUST_BPS - Checkbox

Data type: XFELD
Optional: Yes
Call by Reference: Yes

IT_ROLES - Roles to be synchronized

Data type: RPM_TT_ROLES_SYNC
Optional: Yes
Call by Reference: Yes

IT_RESOURCES - Resources to be synchronized

Data type: RPM_TT_RESOURCES_SYNC
Optional: Yes
Call by Reference: Yes

IT_TEAMS - Teams to be synchronized

Data type: RPM_TT_TEAMS_SYNC
Optional: Yes
Call by Reference: Yes

IT_RELATES - Relationships to be synchronized

Data type: RPM_TT_RELATES_SYNC
Optional: Yes
Call by Reference: Yes

IV_ADJUST_XRPM - Checkbox

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_SIMULATION - Checkbox

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_LANGUAGE - Language according to ISO 639

Data type: LAISO
Optional: Yes
Call by Reference: Yes

IV_BPS_APPLICATION - Application

Data type: RPM_TV_APPLICATION
Optional: Yes
Call by Reference: Yes

IV_BPS_SYSTEM - Logical system

Data type: LOGSYS
Optional: Yes
Call by Reference: Yes

IV_RPM_PROJECT_ID - External ID

Data type: RPM_TV_EXTID
Optional: Yes
Call by Reference: Yes

IS_PROJECT - Project data to be synchronized

Data type: RPM_TS_PROJECT_SYNC
Optional: Yes
Call by Reference: Yes

IT_TASKS - Tasks to be synchronized

Data type: RPM_TT_TASKS_SYNC
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for RPM_IF_PROJECT_DATA_OUTBOUND

ES_PROJECT - Project data to be synchronized

Data type: RPM_TS_PROJECT_INF
Optional: No
Call by Reference: Yes

ET_TASKS - Tasks to be synchronized

Data type: RPM_TT_TASKS_INF
Optional: No
Call by Reference: Yes

ET_ROLES - Roles to be synchronized

Data type: RPM_TT_ROLES_INF
Optional: No
Call by Reference: Yes

ET_RESOURCES - Resources to be synchronized

Data type: RPM_TT_RESOURCES_INF
Optional: No
Call by Reference: Yes

ET_TEAMS - Teams to be synchronized

Data type: RPM_TT_TEAMS_INF
Optional: No
Call by Reference: Yes

ET_RELATES - Relationships to be synchronized

Data type: RPM_TT_RELATES_INF
Optional: No
Call by Reference: Yes

ET_MSG - Table type for messages

Data type: RPM_TT_MESSAGES
Optional: No
Call by Reference: Yes

EV_MSG -

Data type: STRING
Optional: No
Call by Reference: Yes

EV_RC -

Data type: I
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RPM_IF_PROJECT_DATA_OUTBOUND 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_es_project  TYPE RPM_TS_PROJECT_INF, "   
lv_iv_adjust_bps  TYPE XFELD, "   
lv_it_roles  TYPE RPM_TT_ROLES_SYNC, "   
lv_it_resources  TYPE RPM_TT_RESOURCES_SYNC, "   
lv_it_teams  TYPE RPM_TT_TEAMS_SYNC, "   
lv_it_relates  TYPE RPM_TT_RELATES_SYNC, "   
lv_et_tasks  TYPE RPM_TT_TASKS_INF, "   
lv_iv_adjust_xrpm  TYPE XFELD, "   'X'
lv_et_roles  TYPE RPM_TT_ROLES_INF, "   
lv_iv_simulation  TYPE XFELD, "   'X'
lv_iv_language  TYPE LAISO, "   
lv_et_resources  TYPE RPM_TT_RESOURCES_INF, "   
lv_et_teams  TYPE RPM_TT_TEAMS_INF, "   
lv_iv_bps_application  TYPE RPM_TV_APPLICATION, "   
lv_et_relates  TYPE RPM_TT_RELATES_INF, "   
lv_iv_bps_system  TYPE LOGSYS, "   
lv_et_msg  TYPE RPM_TT_MESSAGES, "   
lv_iv_rpm_project_id  TYPE RPM_TV_EXTID, "   
lv_ev_msg  TYPE STRING, "   
lv_is_project  TYPE RPM_TS_PROJECT_SYNC, "   
lv_ev_rc  TYPE I, "   
lv_it_tasks  TYPE RPM_TT_TASKS_SYNC. "   

  CALL FUNCTION 'RPM_IF_PROJECT_DATA_OUTBOUND'  "Outbound Processing of the Project Interfacing Process
    EXPORTING
         IV_ADJUST_BPS = lv_iv_adjust_bps
         IT_ROLES = lv_it_roles
         IT_RESOURCES = lv_it_resources
         IT_TEAMS = lv_it_teams
         IT_RELATES = lv_it_relates
         IV_ADJUST_XRPM = lv_iv_adjust_xrpm
         IV_SIMULATION = lv_iv_simulation
         IV_LANGUAGE = lv_iv_language
         IV_BPS_APPLICATION = lv_iv_bps_application
         IV_BPS_SYSTEM = lv_iv_bps_system
         IV_RPM_PROJECT_ID = lv_iv_rpm_project_id
         IS_PROJECT = lv_is_project
         IT_TASKS = lv_it_tasks
    IMPORTING
         ES_PROJECT = lv_es_project
         ET_TASKS = lv_et_tasks
         ET_ROLES = lv_et_roles
         ET_RESOURCES = lv_et_resources
         ET_TEAMS = lv_et_teams
         ET_RELATES = lv_et_relates
         ET_MSG = lv_et_msg
         EV_MSG = lv_ev_msg
         EV_RC = lv_ev_rc
. " RPM_IF_PROJECT_DATA_OUTBOUND




ABAP code using 7.40 inline data declarations to call FM RPM_IF_PROJECT_DATA_OUTBOUND

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_adjust_xrpm) = 'X'.
 
 
DATA(ld_iv_simulation) = 'X'.
 
 
 
 
 
 
 
 
 
 
 
 
 


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!