All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
Target Descriptions:
1. Since the target description is assigned in common you can only have one description per table but in reality depending on what team/object that target is used in it may have a different purpose and therefor different description. For example EKKO holds many types of data POs, Contracts, etc. PLKO can be Routings, Task Lists, Inspection Plans, etc. In JDE F0006 can be nearly 100 Different things depending on perspective.
2. The Target Description is not exposed on the hor view in transform. When I mentioned this to Project management they said consultants didn’t need this and they wanted to save the space but everyone I have discussed this with agrees the target description is highly important. While yes one of our consultants on a long term project will know there targets in their limited object by name the business resources they interact with may not. On audit often we put people on objects they are not familiarly with or they whole team may work with a target that is new to BOA. Most systems do not have simple and easy to understand names like SAP does and even in SAP if I have a thousand check tables in my config team all starting with “T” I don’t expect any one person to definitively know the proper description of each table from memory.
I consider this one of the most critical bugs we need to address.
Jeremiah Gilmore
