SAP RMPS_POST_CREATE_API Function Module for









RMPS_POST_CREATE_API is a standard rmps post create api SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 post create api FM, simply by entering the name RMPS_POST_CREATE_API into the relevant SAP transaction such as SE37 or SE38.

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



Function RMPS_POST_CREATE_API 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_POST_CREATE_API'"
  EXPORTING
   IM_DOCTYPE =  "
*  IM_NO_PATH = ' ' "
*  IM_ORIG_OBJTYPE =  "
*  IM_ORIG_OBJKEY =  "
*  IM_FILE_ID =  "

 IMPORTING
   EX_DOC_ID =  "
   EX_DOC_CLASS =  "
   EX_PATHID =  "
   EX_REJECTED_PROPERTIES =  "
   EX_PDIR_ID =  "
   EX_DOCID =  "
   EX_RETURN =  "

TABLES
*  IM_TAB_PROPERTIES =  "
.



IMPORTING Parameters details for RMPS_POST_CREATE_API

IM_DOCTYPE -

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

IM_NO_PATH -

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

IM_ORIG_OBJTYPE -

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

IM_ORIG_OBJKEY -

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

IM_FILE_ID -

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

EXPORTING Parameters details for RMPS_POST_CREATE_API

EX_DOC_ID -

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

EX_DOC_CLASS -

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

EX_PATHID -

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

EX_REJECTED_PROPERTIES -

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

EX_PDIR_ID -

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

EX_DOCID -

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

EX_RETURN -

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

TABLES Parameters details for RMPS_POST_CREATE_API

IM_TAB_PROPERTIES -

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

Copy and paste ABAP code example for RMPS_POST_CREATE_API 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_doc_id  TYPE SDOK_DOCID, "   
lv_im_doctype  TYPE SAEOBJART, "   
lt_im_tab_properties  TYPE STANDARD TABLE OF RMPS_POSTATTR_TYPE, "   
lv_im_no_path  TYPE SRMBOOLEAN, "   SPACE
lv_ex_doc_class  TYPE SDOK_CLASS, "   
lv_ex_pathid  TYPE SRMWFPTHID, "   
lv_im_orig_objtype  TYPE SWO_OBJTYP, "   
lv_im_orig_objkey  TYPE SWO_TYPEID, "   
lv_ex_rejected_properties  TYPE RMPS_POSTATTR_TYPE, "   
lv_ex_pdir_id  TYPE BAPIGUID, "   
lv_im_file_id  TYPE SAEPFAD, "   
lv_ex_docid  TYPE BAPIGUID, "   
lv_ex_return  TYPE BAPIRET2. "   

  CALL FUNCTION 'RMPS_POST_CREATE_API'  "
    EXPORTING
         IM_DOCTYPE = lv_im_doctype
         IM_NO_PATH = lv_im_no_path
         IM_ORIG_OBJTYPE = lv_im_orig_objtype
         IM_ORIG_OBJKEY = lv_im_orig_objkey
         IM_FILE_ID = lv_im_file_id
    IMPORTING
         EX_DOC_ID = lv_ex_doc_id
         EX_DOC_CLASS = lv_ex_doc_class
         EX_PATHID = lv_ex_pathid
         EX_REJECTED_PROPERTIES = lv_ex_rejected_properties
         EX_PDIR_ID = lv_ex_pdir_id
         EX_DOCID = lv_ex_docid
         EX_RETURN = lv_ex_return
    TABLES
         IM_TAB_PROPERTIES = lt_im_tab_properties
. " RMPS_POST_CREATE_API




ABAP code using 7.40 inline data declarations to call FM RMPS_POST_CREATE_API

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_im_no_path) = ' '.
 
 
 
 
 
 
 
 
 
 


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!