Version 1 (without feedback yet)
Starting ST 7.10, SP5, in the area Change Management Request a new UI object control is introduced and functional available Depending from transaction type and user status specific, UI object visibility and editability can be controlled via table entries. Additionally it is possible to create your own UI control class and implement your own code (see further down).
The following ChaRM specific UI objects are supported for user status dependent UI control for the following transaction types, sorted by assignment block:
The entries marked have a UI control assigned. I will further down explain how to implement your own UI control class.
Here is some more detail how to use the Basis Enhancement Framework in SE24:
Go into the class in SE24
Create an enhancement:
Type in to your liking...
Choose the type of enhancement...
The enhancement has been created:
Click on the marked place to access the coding place.
The interface hands over:
Fields
MANDT client
PROCESS_TYPE transaction type
FIELDNAME UI object ID
STSMA user status profile
USER_STATUS user status
EDITABLE UI object is editable
MANDATORY do not use
VISIBLE UI object is visible
CLASS assigned UI control class
METHOD called UI control class method
ACTIVE customizing entry is active
ES_UI_CONTROL is the important one to change, especially fields EDITABLE and VISIBLE.
Tips and Tricks to program in method IF_AIC_AREA_CONTROL~DEFINE_EDIT_VISIBILITY
METHOD if_aic_area_control~define_edit_visibility.
DATA: lv_project_id TYPE project_id,
lt_context TYPE STANDARD TABLE OF tsocm_cr_context,
ls_orderadm_h TYPE crmt_orderadm_h_wrk.
DATA: ls_proxy TYPE tsocm_proxy_impl.
DATA: lv_project_cr TYPE project_id.
DATA: lv_non_smcg TYPE flag.
DATA: l_doc_flow_tab TYPE crmt_doc_flow_wrkt.
FIELD-SYMBOLS: <fs_context> TYPE tsocm_cr_context.
es_ui_control = is_ui_control.
CHECK iv_fieldname = cl_wdcm_extchreq_scoping_asst=>c_project_id OR
" the constants of the UI objects can be found in class cl_wdcm_extchreq_scoping_asst or class cl_ai_crm_action_utility
iv_fieldname = cl_wdcm_extchreq_scoping_asst=>c_ibase_component.
* read project id
lv_project_id = cl_al_crm_cm_utility=>read_project_id( iv_guid ).
IF iv_fieldname EQ cl_wdcm_extchreq_scoping_asst=>c_project_id.
TRY.
Here, we call the process type from the BOL
CALL METHOD io_bol_header->get_property_as_value
EXPORTING
iv_attr_name = 'PROCESS_TYPE' "#EC NOTEXT
IMPORTING
ev_result = ls_orderadm_h-process_type.
CATCH cx_sy_ref_is_initial cx_sy_move_cast_error
cx_crm_genil_model_error.
RETURN.
ENDTRY.
ENDIF.
.
.
.
.
ENDMETHOD.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
38 | |
19 | |
13 | |
13 | |
11 | |
10 | |
10 | |
10 | |
8 | |
8 |