Skip to Content

Best approach to design entity for description details


Suppose I have a UI5 screen where-in I am going to display purchase order header details (from zekko copied from ekko with limited fields) .For that I created a odata webservice with entity having the fields Ebeln , Bukrs, Bstyp, Bsart , Statu, Lifnr.

Now in my frontend , i also to want to display description for some of the above fields for eg. description for bukrs , bstyp, bsart , lifnr(vendor name for corresponding vendor number). These description will either come from some other table joined with ekko or from data element/domain list. In both cases , what will be the best approach to achieve this??

One way is I can add these description fields in the above entity itself and write a code in odata service to fetch them accordingly. But in that case , in future when I will implement CreateEntity method , the user from frontend will be forced to enter the description details as well since the same entity structure will be used in case of Create operation also.

Hence I wanted to know , what is the best practice followed in real time in such cases.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Oct 05, 2015 at 11:40 AM

    It is not mandatory to pass all the filed of entity from front-end.
    You can keep them blank in payload, can perform operation in create entity method reading required properties.

    Add comment
    10|10000 characters needed characters exceeded