Skip to Content

Convert a code based OData Project to SEGW(Transaction) based

There are various ways to convert a code based OData project to SEGW based :


Procedure 1:

Creating a New Project in SEGW , where Data Model has been created using Flat File.

Steps:

The Data Model has been extracted from the existing PDA App in to flat file of type .XML.

Using the option Import-> Data Model from File, the new data model has been created.

The business logic from the existing Data Provider Class has been implemented in the new Data provider extension class.

Pros:

Creation of Data model is easier.

Cons:

The Data model created does not match with the existing Front end UI5 elements property and data binding fails.

The Data model attributes with property of type GUID, Date, Numeric etc.. does not match with the UI5 and throws error.

The Underscores “_” in the ABAP Field name get removed and the Data mapping fails.

Procedure 2:

Creating a New Project in SEGW , where Data Model has been created using ABAP Dictionary.

Steps:

The Data Model has been created with the Entities reference to ABAP structure.

The business logic from the existing Data Provider Class has been implemented in the new Data provider extension class.

Pros:

The Data mapping of the entity will be created automatically.

Cons:

Creation of Data model takes time when comparing to Create using Flat file.

The Data model attributes with property of type GUID, Date, Numeric etc.. does not match with the UI5 and throws error.

Procedure 3:

Creating a New Project in SEGW , where Data Model has been created using Redefine option.

Steps:

The Data Model has been created with the redefine option, where the existing Gateway OData Service has been used to create this Data model.

Pros:

The Property names are created as similar as the Front end UI5 elements.

The Data mapping of the entity will be created automatically.

Cons:

As the Model references is with respective to the current existing model, we should not delete the current existing model objects.

The Data model attributes with property of type GUID, Date, Numeric etc.. does not match with the UI5 and throws error.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply