SAP RMPS_AI_SESSION_OPEN Function Module for Accept an incoming session request









RMPS_AI_SESSION_OPEN is a standard rmps ai session open SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Accept an incoming session request 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 rmps ai session open FM, simply by entering the name RMPS_AI_SESSION_OPEN into the relevant SAP transaction such as SE37 or SE38.

Function Group: RMPS_AI_FILING
Program Name: SAPLRMPS_AI_FILING
Main Program: SAPLRMPS_AI_FILING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function RMPS_AI_SESSION_OPEN 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 'RMPS_AI_SESSION_OPEN'"Accept an incoming session request
EXPORTING
* IM_BUS_OBJECT = "BOR Object type
* IM_LOGSYSTEM = "Remote system ID
IM_OBJECT_KEY = "BOR Object ID
IM_ATTRIBUTES = "Attributes for the BOR Object
IM_SESSION_ID = "Incoming Session ID
IM_C_POID_ID = "Class directory POID ID
IM_F_POID_ID = "Folder directory POID ID

IMPORTING
EX_SESSION_ID = "Session ID
EX_NAVIGATION = "Table of class/folder poids

EXCEPTIONS
INVALID_BOR_OBJECT = 1 NO_CUSTOMIZING_FOR_BOR_OBJECT = 2 INVALID_LOGICAL_SYSTEM = 3 INVALID_SESSION_ID = 4 INVALID_CLASS_DIRECTORY_ID = 5 INVALID_FOLDER_DIRECTORY_ID = 6
.



IMPORTING Parameters details for RMPS_AI_SESSION_OPEN

IM_BUS_OBJECT - BOR Object type

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

IM_LOGSYSTEM - Remote system ID

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

IM_OBJECT_KEY - BOR Object ID

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

IM_ATTRIBUTES - Attributes for the BOR Object

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

IM_SESSION_ID - Incoming Session ID

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

IM_C_POID_ID - Class directory POID ID

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

IM_F_POID_ID - Folder directory POID ID

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

EXPORTING Parameters details for RMPS_AI_SESSION_OPEN

EX_SESSION_ID - Session ID

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

EX_NAVIGATION - Table of class/folder poids

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

EXCEPTIONS details

INVALID_BOR_OBJECT - The supplied BOR Object Type does not exist

Data type:
Optional: No
Call by Reference: Yes

NO_CUSTOMIZING_FOR_BOR_OBJECT - There is no specific or default scenario for BOR

Data type:
Optional: No
Call by Reference: Yes

INVALID_LOGICAL_SYSTEM - The remote system identifier is invalid

Data type:
Optional: No
Call by Reference: Yes

INVALID_SESSION_ID - The Session ID does not exist

Data type:
Optional: No
Call by Reference: Yes

INVALID_CLASS_DIRECTORY_ID - The Class POID ID is invalid

Data type:
Optional: No
Call by Reference: Yes

INVALID_FOLDER_DIRECTORY_ID - The Folder POID ID is invalid

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RMPS_AI_SESSION_OPEN 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_ex_session_id  TYPE RMPS_OP_GUID, "   
lv_im_bus_object  TYPE SWO_OBJTYP, "   
lv_invalid_bor_object  TYPE SWO_OBJTYP, "   
lv_im_logsystem  TYPE LOGSYSTEM, "   
lv_ex_navigation  TYPE RMPS_AI_NAV_T, "   
lv_no_customizing_for_bor_object  TYPE RMPS_AI_NAV_T, "   
lv_im_object_key  TYPE SWO_TYPEID, "   
lv_invalid_logical_system  TYPE SWO_TYPEID, "   
lv_im_attributes  TYPE BAPIPROPTB, "   
lv_invalid_session_id  TYPE BAPIPROPTB, "   
lv_im_session_id  TYPE RMPS_OP_GUID, "   
lv_invalid_class_directory_id  TYPE RMPS_OP_GUID, "   
lv_im_c_poid_id  TYPE SRMPOIDID, "   
lv_invalid_folder_directory_id  TYPE SRMPOIDID, "   
lv_im_f_poid_id  TYPE SRMPOIDID. "   

  CALL FUNCTION 'RMPS_AI_SESSION_OPEN'  "Accept an incoming session request
    EXPORTING
         IM_BUS_OBJECT = lv_im_bus_object
         IM_LOGSYSTEM = lv_im_logsystem
         IM_OBJECT_KEY = lv_im_object_key
         IM_ATTRIBUTES = lv_im_attributes
         IM_SESSION_ID = lv_im_session_id
         IM_C_POID_ID = lv_im_c_poid_id
         IM_F_POID_ID = lv_im_f_poid_id
    IMPORTING
         EX_SESSION_ID = lv_ex_session_id
         EX_NAVIGATION = lv_ex_navigation
    EXCEPTIONS
        INVALID_BOR_OBJECT = 1
        NO_CUSTOMIZING_FOR_BOR_OBJECT = 2
        INVALID_LOGICAL_SYSTEM = 3
        INVALID_SESSION_ID = 4
        INVALID_CLASS_DIRECTORY_ID = 5
        INVALID_FOLDER_DIRECTORY_ID = 6
. " RMPS_AI_SESSION_OPEN




ABAP code using 7.40 inline data declarations to call FM RMPS_AI_SESSION_OPEN

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!