cancel
Showing results for 
Search instead for 
Did you mean: 

simple buiness case and big effort for CREATE_DEEP_ENTITY

Former Member
0 Kudos

Lets say we want to call from browser (UI5 app) FM which needs input like this

val1

val2

tab1

tab2

Am i right that in this case we have to make

1) entity1 for val1 and val2

2) entitySet for tab1

3) entitySet for tab2

4) associations

5) CREATE_DEEP_ENTITY method

its preatty common case but effort is big, that's why i am asking to be sure.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

Yup. That should do it.

You can go through the following link for Create_deep_entity

-Stanley

Former Member
0 Kudos

What about keys ? At least one is needed i guess and i have to introduce this key.

AshwinDutt
Active Contributor
0 Kudos

Yes u need to define atleast one key in ur model. What shyd be the key u will be knowing better.

Answers (2)

Answers (2)

kammaje_cis
Active Contributor
0 Kudos

Lukasz,

You need to understand that FMs were never designed to be consumed for creating OData services. OData services and FMs have their own use cases. The tool provided in SEGW to create an entity/service out of an FM is not supposed to suit every available FM.

Outside-In data modeling approach is the key here.

It means that you would look at the UI which will consume your OData service and create your OData model in SEGW as per that (yes, manually creating entities, properties and other artifacts). Generate runtime artifacts next Then you go to the generated *DPC_EXT class, identify the right method and write your own code to call the FM and populate the return table.

If it is a create_deep or a flat create should be decided from the UI screen and not from the FM's interface.

Thanks

Krishna

Former Member
0 Kudos

Seconded, thirded and fourthed

AshwinDutt
Active Contributor
0 Kudos

Hello,

Yes . Create Different entities and create association & navigation between them with appropriate cardinality.

This should help u.

Regards,

Ashwin