SAP RCP305_CHANGE_STATE_CREATE Function Module for RMS-RCP: Create New Change State
RCP305_CHANGE_STATE_CREATE is a standard rcp305 change state create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RMS-RCP: Create New Change State 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 rcp305 change state create FM, simply by entering the name RCP305_CHANGE_STATE_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RCP305
Program Name: SAPLRCP305
Main Program: SAPLRCP305
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RCP305_CHANGE_STATE_CREATE 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 'RCP305_CHANGE_STATE_CREATE'"RMS-RCP: Create New Change State.
EXPORTING
I_DATA_SCENARIO = "Data Scenario for API Recipe
IMPORTING
ET_ERROR = "RMS-RCP: API - Table Type for Error Table
ET_NO_AUTH = "RMS-RCP: API - Table Type for Authorization
CHANGING
XT_RCP = "RMS-RCP: API - Table Type for Recipe Data
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for RCP305_CHANGE_STATE_CREATE
I_DATA_SCENARIO - Data Scenario for API Recipe
Data type: RCPE_DATASCENOptional: No
Call by Reference: Yes
EXPORTING Parameters details for RCP305_CHANGE_STATE_CREATE
ET_ERROR - RMS-RCP: API - Table Type for Error Table
Data type: RCPTY_API_ERROROptional: No
Call by Reference: Yes
ET_NO_AUTH - RMS-RCP: API - Table Type for Authorization
Data type: RCPTY_API_NO_AUTHOptional: No
Call by Reference: Yes
CHANGING Parameters details for RCP305_CHANGE_STATE_CREATE
XT_RCP - RMS-RCP: API - Table Type for Recipe Data
Data type: RCPTY_API_RCPOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR - Error When Editing the Change State
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RCP305_CHANGE_STATE_CREATE 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_error | TYPE STRING, " | |||
lv_xt_rcp | TYPE RCPTY_API_RCP, " | |||
lv_et_error | TYPE RCPTY_API_ERROR, " | |||
lv_i_data_scenario | TYPE RCPE_DATASCEN, " | |||
lv_et_no_auth | TYPE RCPTY_API_NO_AUTH. " |
  CALL FUNCTION 'RCP305_CHANGE_STATE_CREATE' "RMS-RCP: Create New Change State |
EXPORTING | ||
I_DATA_SCENARIO | = lv_i_data_scenario | |
IMPORTING | ||
ET_ERROR | = lv_et_error | |
ET_NO_AUTH | = lv_et_no_auth | |
CHANGING | ||
XT_RCP | = lv_xt_rcp | |
EXCEPTIONS | ||
ERROR = 1 | ||
. " RCP305_CHANGE_STATE_CREATE |
ABAP code using 7.40 inline data declarations to call FM RCP305_CHANGE_STATE_CREATE
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