on 10-17-2013 7:20 AM
Hi All,
We have a requirement to be able to create dropdown values in our change requests to be able to select some field values and hide other available fields. Is there anyone that have managed to do this in the past or any documentation available. We would also like to know if this could be possible with freetext values. There are options available to add buttons dropdowns etch in floorplan manager but we do not know where to populate the values because when we select the dropdown it will be empty.
Thanks and best regards
Riaan
Hello Riaan,
in the UIBB configuration you have the option to define the field's look and feel (e.g. common input fields, fields with search helps, dropdown listboxes, and others).
If you decide to use dropdown listboxes, you have to ensure that the actual values are bound to the field. This needs to be implemented in the feeder class being responsible for the actual UIBB. The suitable method is GET_ATTR_VALUE_SET.
Before you start, please make yourself familiar with the various enhancement guides offered on SCN as well as the FPM cookbook (you will find the link inside the mentioned guides)!
Best regards
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
I have similar kind of requirement but not exactly the same. I need to add "Units of Measure" field (MEGRU) to Sales View of the MDG Change Request (ECC6/Ehp5).
When I am adding the attribute and providing the data element I am getting error "Data Model MM, entity type ZMVKE, attribute ZZMEGRU: Invalid check table"
When I provided the data element with data type CHAR4 it allowed me to create it and i was able to map it. The field is also available in MDG CR but the F4 drop down is not enabled.
Request you to please advise.
Regards,
Rama
Rijan:
Another option you have is to create an S/UT-2 (Storage & Use Type) entity in the data model and load it with the subset of values that you would normally be pulling from the S/UT-3 entry lookup table.You would then set up referencing relationship(s) with the S/UT-2 entity and remove it(them) from the S/UT-3 entity.
When the drop down list is activated, it then reads the entries from the S/UT-2 entity table instead of the ECC (S/UT-3) table.
Caveats:
1) This assumes that the list is fairly static in nature (as a lookup table should be).
2) This approach has a downside that when anything changes in the initial lookup table, you may have to maintain it here as well for relevant values
Freetext fields:
With respect to the freetext fields, the entered values could be copied into an S/UT-2 table as part of the update of the Change Request (checking for duplicates, of course), and would then be available for use by any later invocations of the drop-down list
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To create a dropdown values you have to do following -
1. Copy your data model and create a Z data model
2. Create a search help - Z searc help for your field
3. Change your UI and update the field's search help with the one you have created
For changing free text values to F4 or dropdown, you have to make a Z development.
Kiran
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.