Skip to end of metadata
Go to start of metadata
Field Control

When you create a custom field control customizing, the system generates classes which contain the methods determining the properties and visibility of fields for projects which use this field control customizing. The naming of the generated class(es) is always "/1CPR/CL_(client)_(field control)_(object)". E.g. if you are on client "100" and have a field control "XYZ" for object "Tasks", the class will be called "/1CPR/CL_100_XYZ_TTO".
Please note: the above does not apply to the standard field control 0SAP, which uses classes called CL_DPR_FC_PROJECT_O, CL_DPR_FC_TASK_O etc.

Field Properties

Method GET_FIELD_PROPERTY of class CL_DPR_UI_LOG_DETAIL is processed to determine the properties for all fields when opening a project or accessing a project objects. These include e.g. the matchcodes ("F4 Help") and dropdown values for selection fields.


Check for mandatory fields:

CL_DPR_FC_GENERAL
METHOD  IF_DPR_FC_INFO~GET_FIELD_CONTROL_INFO

 

DPR_PROJECT_STRUCTURE            
COMPONENTCONTROLLER
ON_SAVE_REQUEST                

* get BAdI DPR_TREE and check if complete structure needs to
* be checked in required fields check
  lr_badi_tree = cl_dpr_badi_factory=>get_badi_tree_instance( ).
  IF lr_badi_tree IS BOUND.
    CALL BADI lr_badi_tree->switch_required_fields_check
      CHANGING
        cv_check_complete_struc = lv_chk_compl_struc.
  ENDIF.

 

DPR_PROJECT_STRUCTURE         
COMPONENTCONTROLLER
CHECK_REQUIRED_FIELDS          

 

BAdIs:

To check the whole structure for mandatory fields when saving the project the Badi DPR_TREE with method SWITCH_REQUIRED_FIELDS_CHECK can be implemented.
See SAP Note 1540270 "Required entry field check for all structure elements"

BAdI: DPR_DETAIL_TAB_CTRL - Field Control Detail Data Tab

 

 

Back

  • No labels