Skip to Content

Assignments of ABAP types to entity attributes gone on redifined services

Hi there,

in my service I assigned ABAP types (both internal types and data elements) to the attributes of my entity using the ABAP type editor.

When I now create a new project and redefine the service from the first project all those assignments are gone (in the new project). The assignments are set back to 'Determination by Runtime Object Generator'.

A little bit different is the behaviour of date fields (both Edm.DateTime and Edm.DateTimeOffset): They are always re-set to ABAP data element 'TIMESTAMP' (length 15), which means that I need to do some conversion on my date values in the DPC_EXT class.

Seems to be a similar problem as the one regarding assignment of labels I described in a recent post:

Does anybody have similar problems - or even a solution to keep the original assignments?

Thank you!

Best regards,


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Sep 24, 2014 at 07:08 AM


    in this context I also realized the following:

    If I create a gateway service with an entity (not linked to an ABAP structure) which contains a date related attribute the ABAP field name is automatically set to internal type 'TIMESTAMP' (as mentioned in original post).

    In the next step I create the runtime artifacts just by mapping the GettingEntitySet method to a RFC (in the Service Implementation section of the Service Builder). Assuming the date field in the resulting list of the function module is related to internal type DATE the generated OData service will return an error.

    The reason is that in the generated method the value of a DATE field shall be moved to a TIMESTAMP field.

    That means that if I create a simple service in that way I also have to change all date attributes (or redefine the DPC class and do a DATE -> TIMESTAMP conversion in the data mapping).



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.