Value-helps for customer extension fields in Web-Client UI
[BTCUSTOMER] [CRMD_CUSTOMER_H] [CRMD_CUSTOMER_I] [CUSTOMER_H] [CUSTOMER_I]
Symptom
The CRM Order has been extended by the customer on the header or item level via the Easy Enhancement Workbench (EEW). The new fields are made available in the corresponding customer assignement blocks. The value-helps for these fields are generically determined. The customer may want to further influence this behavior of these value-helps.
Possible reasons to change the default behavior include:
For domains with only few valid inputs: the system uses a dropdown-listbox instead a value-help popup. The customer may a preference for one technique over the other.For components with a check table that has a related text table: if the related text table does not follow the EEW naming convention, i.e. ‘_T’ appended to the source table name, then the value help will not find the descriptive texts.Other terms
CUSTOMER_H, CUSTOMER_I, CRMD_CUSTOMER_H, CRMD_CUSTOMER_I, BTCUSTOMER_H, BTCUSTOMER_I, customer fields
Reason and Prerequisites
Customer fields have been added to CRMD_CUSTOMER_H or CRMD_CUSTOMER_I
Solution
Use Framework Enhancement Concept as described in Note 1122248 to enhance the context nodes of either UI Component BTCUSTOMER_H and/or BTCUSTOMER_I, (”Business Tranaction Customer Header Fields” and/or “Item Fields”).
Redefine the “V-getter” method for context node BTCUSTOMERH and/or BTCUSTOMERI. The method is called “get_v_s_struct” and can be redefined to call a different “V-getter” method per field (component) name, e.g. “GET_V_<Fieldname>”.