cancel
Showing results for 
Search instead for 
Did you mean: 

Extending PR Approval OData Service

vishnucta
Active Participant
0 Kudos

Hi mates,

     As a use case i took PR approval app for extending the ODATA Service and when i tried to redefine the service it showed me that 'Service doesnt exist' .But we have already implemented PR approval fiori app in our landscape and and service name is 'GBAPP_PRAPPROVAL'.Below i have mentioned the screen shots.

Regards,

Vishnu

Accepted Solutions (1)

Accepted Solutions (1)

Andre_Fischer
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Vishnu,

are you using a SAP Gateway hub deployment or are you using an embedded deployment?

Where do you start transaction SEGW?

Is it on the hub or on the backend?

The service registration takes place on the backend and you can check it there via transaction /IWBEP/REG_SERVICE.

The service is then published on the hub via transaction /IWFND/MAINT_SERVICE.


From the screen shots you shared a possible error could be that you checked on the hub for the backend service registration rather than on the backend itself.

Best Regards,

Andre


vishnucta
Active Participant
0 Kudos

Hi Fischer,

We have a central hub deployment and i use the tcode segw on the frontend server where i tried redefining the service.Should i do some other configurations other than this to redefine the standard OData service for PR Approval.Please do mention if i mention some steps in-between.

Regards,

Vishnu

Andre_Fischer
Product and Topic Expert
Product and Topic Expert
0 Kudos


Hi Vishnu,

you have to do the redefinion in the backend system not in the frontend server.

Regards,

Andre

vishnucta
Active Participant
0 Kudos

Thanx .You just saved my day..

Why SAP Standard services resides in Backend.All my custom Odata Services are created and redefined in my frontend server.If you have doc explaining the same pls share..:)

Andre_Fischer
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Vishnu,

the services of SAP Fiori applications are implemented in the backend because it is best to have the implementation as close as possible to the data that is to be read.

If you implement a service in the frontend server you are limited to use RFC enabled interfaces in the ERP backend.

If the implementation takes place in the backend you can write code that is much more efficient.

An advantage for you (personally) from a live cycle management perspective to have the code in the hub system is however that you only have to deal with one implementation in case you are using multiple backends.

Regards,

Andre


vishnucta
Active Participant
0 Kudos

that was awesome,you helped me a lot,thanks.

Regards,

Vishnu

Answers (0)