SAP CTW_UI_PROCESS_PROPOSAL Function Module for
CTW_UI_PROCESS_PROPOSAL is a standard ctw ui process proposal 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 ctw ui process proposal FM, simply by entering the name CTW_UI_PROCESS_PROPOSAL into the relevant SAP transaction such as SE37 or SE38.
Function Group: CTW_UI
Program Name: SAPLCTW_UI
Main Program: SAPLCTW_UI
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CTW_UI_PROCESS_PROPOSAL 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 'CTW_UI_PROCESS_PROPOSAL'".
EXPORTING
* IV_ACTION = 'DISP' "
* IV_NO_RELEASE_CHECK = ' ' "General Flag
* IV_RELEASE_IN_BACKGROUND = ' ' "Boolean
* IS_PROPOSAL = "
IMPORTING
ES_PROPOSAL = "
ES_TRWBO_REQUEST = "
ET_TRWBO_DELETED_TASKS = "
EXCEPTIONS
INVALID_INPUT = 1 CANCELLED_BY_USER = 2 ABORTED = 3 NO_AUTHORIZATION = 4 WF_NOT_ACTIVE = 5
IMPORTING Parameters details for CTW_UI_PROCESS_PROPOSAL
IV_ACTION -
Data type: SY-UCOMMDefault: 'DISP'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_RELEASE_CHECK - General Flag
Data type: FLAGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_RELEASE_IN_BACKGROUND - Boolean
Data type: TRBOOLEANDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IS_PROPOSAL -
Data type: CTWFFORMOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CTW_UI_PROCESS_PROPOSAL
ES_PROPOSAL -
Data type: CTWFFORMOptional: No
Call by Reference: No ( called with pass by value option)
ES_TRWBO_REQUEST -
Data type: TRWBO_REQUESTOptional: No
Call by Reference: Yes
ET_TRWBO_DELETED_TASKS -
Data type: TRWBO_T_E070Optional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_INPUT - Invalid entry
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANCELLED_BY_USER - Action canceled by user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ABORTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WF_NOT_ACTIVE - Workflow not active
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CTW_UI_PROCESS_PROPOSAL 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_iv_action | TYPE SY-UCOMM, " 'DISP' | |||
| lv_es_proposal | TYPE CTWFFORM, " | |||
| lv_invalid_input | TYPE CTWFFORM, " | |||
| lv_es_trwbo_request | TYPE TRWBO_REQUEST, " | |||
| lv_cancelled_by_user | TYPE TRWBO_REQUEST, " | |||
| lv_iv_no_release_check | TYPE FLAG, " ' ' | |||
| lv_aborted | TYPE FLAG, " | |||
| lv_et_trwbo_deleted_tasks | TYPE TRWBO_T_E070, " | |||
| lv_iv_release_in_background | TYPE TRBOOLEAN, " ' ' | |||
| lv_is_proposal | TYPE CTWFFORM, " | |||
| lv_no_authorization | TYPE CTWFFORM, " | |||
| lv_wf_not_active | TYPE CTWFFORM. " |
|   CALL FUNCTION 'CTW_UI_PROCESS_PROPOSAL' " |
| EXPORTING | ||
| IV_ACTION | = lv_iv_action | |
| IV_NO_RELEASE_CHECK | = lv_iv_no_release_check | |
| IV_RELEASE_IN_BACKGROUND | = lv_iv_release_in_background | |
| IS_PROPOSAL | = lv_is_proposal | |
| IMPORTING | ||
| ES_PROPOSAL | = lv_es_proposal | |
| ES_TRWBO_REQUEST | = lv_es_trwbo_request | |
| ET_TRWBO_DELETED_TASKS | = lv_et_trwbo_deleted_tasks | |
| EXCEPTIONS | ||
| INVALID_INPUT = 1 | ||
| CANCELLED_BY_USER = 2 | ||
| ABORTED = 3 | ||
| NO_AUTHORIZATION = 4 | ||
| WF_NOT_ACTIVE = 5 | ||
| . " CTW_UI_PROCESS_PROPOSAL | ||
ABAP code using 7.40 inline data declarations to call FM CTW_UI_PROCESS_PROPOSAL
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.| "SELECT single UCOMM FROM SY INTO @DATA(ld_iv_action). | ||||
| DATA(ld_iv_action) | = 'DISP'. | |||
| DATA(ld_iv_no_release_check) | = ' '. | |||
| DATA(ld_iv_release_in_background) | = ' '. | |||
Search for further information about these or an SAP related objects