in SEGW T.Code 2nd Time Run Time Object's creation removes the older methods implementation's

[Balu483]

hello OData Service Consultants,

i am facing a Problem that ,

i Created the Entity Type , Corresponding Entity Set in Data model then Generated a Run Time Object's for this , then Register the Service,then Implemented the service as GetEntitySet(Query) Method,GetEntity(Read) method.

and it was working fine.

later i Got a Changes in Entity Type to Add Some Other New Fields .unless and until i Generate a Run Time Object's the new FieldsAre Not Getting Reflected

in DPC,MPC classes .

if i regenerate the Run Time Object's then, older Method's Implementation's i.e GetEntitySet(Query) Method,GetEntity(Read) code is Vanished .

so how to do Modification's after Generated the Run Time Object's

[venkatakalyan_karanam · Accepted solution]

Please redefine the methods you mentioned (GetEntitySet(Query) Method,GetEntity(Read) method)in the Data Provider extension class, so that when you generate the artifacts again, your code will exists.

[Balu483]

the problem solved my self.

previously,

when ever i want to implement the entity method in service implementation (ex <*_get_entity,*_get_entityset,....>) i directly double clicking the method and writing my business logic inside it. when i double click the method it was promoting the message like

"Method <*>_CREATE_ENTITY is implemented in class <*>_DPC".

this means i am implementing the business logic inside the base class i.e DPC not in DPC_EXT .

so when ever i regenerate the objects, my Business logic is gets over Writing .

so the solution is you have to redefine the method inside the DPC_EXT class .

[kammaje_cis]

See Ashwin's answer here.

https://archive.sap.com/discussions/thread/3615845

[dinakaran_g]

Hi,

If you have to need any additional implementation to use Extension class(DPC_EXT, MPC_EXT).

Thanks.