In fact the requirement to create an extension field with type Code List is still feasible. The entries in code list in this approach are fed by check table so we have to create a check table first.
I have the following check table:
It has a text table accordingly:
And fill some value into this check table:
Please notice that there are some prerequisites which a given check table must fulfill if it is expected to work as the datasource of a Code List extension field. You can find the prerequisite below:
Once the check table is ready, you can check extension field and assign this table to it. The attribute “Render/Validate As” must be set as “Show checktable as DDLB”:
In the runtime the extension field “JVM Type” works as below:
When the extension field is saved, the code description is displayed in the WebUI,
while in the backend table CRM_EXT_MAT, the code value is saved.
We can use tcode AXTSHOW to inspect the metadata for this extension field. Specify extension field name and execute:
Our assigned check table could be found here:
This assignment relationship is maintained in table AXT_EXT_PART_DTL: