Mandatory and optioonal parameters mapping issue in Gateway

[Pavan_Golesar]

Hi,

I am facing issue with mapping fields to my RFC(BAPI) in service implementation - FOR Get_entity-READ 

Lets suppose we have 3 Fields as input for BAPI. 2 of which are mandatory and remaining 1 is optional.

Now, Data model->entity type, allows only Primary keys to be part of input paramters to the BAPI under mapping.

Can anyone share how can we pass this optional parameter (in case of Read-Get_entity) to bapi without setting it as Key under entity type.

Thanks in advance,

PavanG

[AshwinDutt · Accepted solution]

Hello Pavan,

In that case try as below :

Create model alone in SEGW by setting which ever parameters you need as Keys.

Do not implement any operation in implementation section.

Generate Run-time objects.

Manually implement Get_Entity in DPC_EXT class and add code.

Regards,

Ashwin

[Pavan_Golesar · Accepted solution]

Hey Ashwin,

Thanks for Quick reply

Do not implement any operation in implementation section.

Do we have any other solution in this case.. As I have already implemented almost all the CRUDQ operation for that set.

Can we have some other solution.

Thanks,

--PavanG

[EkanshCapgemini · Accepted solution]

Hi Ashwin,

In this case, wouldn't it raise error while calling the URL as the framework wouldn't allow the third parameter(non-key) to be passed as key in READ call?

Regards,

Ekansh

[AshwinDutt · Accepted solution]

Hello Ekansh,

Yes error will come.

To use this BAPI for READ, we are forced to make that 3rd field also as key in the GW model. Only then we will be able pass that as part of KEY's to make that BAPI work.

Or else we need to implement QUERY for this so that we can define first 2 as keys and third as non key and pass as filters.

Regards,

Ashwin

[EkanshCapgemini · Accepted solution]

I Agree.

He needs to redefine the GET_ENTITYSET method for QUERY because if he opts for mapping, it will throw error as "no output table is mapped....". Here I am assuming that there is a flat structure in the exporting parameters since he was trying to use READ.

Regards,

Ekansh

[Pavan_Golesar · Accepted solution]

Thanks Ekansh,

Yes, I have got to redefine the get_entityset method to make this possible. which is the another way to get things done..

But I felt there might be some way to get rid of this primary key input fuunction for read

Best Regards,

Pavan G

[EkanshCapgemini · Accepted solution]

Hi Pavan,

This is as per the OData v2 standards that Read operation can be performed using all the key values and there can not be any other input other than key. Since gateway foundation runs on OData v2 standards, there is no way to escape this.

Regards,

Ekansh

[Pavan_Golesar · Accepted solution]

Hi Ekansh,

Thanks.

I'll certainly checking out on

OData standard v2

To get more clarity on other upcoming issues.

Thanks again

--PavanG

Message was edited by: Pavan Golesar

[vivek_gaurav]

Hi Pavan,

You can do it by redefining DPC Class in se80 or se24.

you can get help from bellow link:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0d92637-3d0d-2f10-ebb2-efc1f40a8...

http://scn.sap.com/community/gateway/blog/2014/04/27/step-by-step-development-guide-for-createdeepen...

Regards

Vivek