GateWay oData runtime generating multiple interfaces for one RFC calls

[Tracy]

Hi Experts,

We are working Add-on package with AAK. We are trying to put everything in our own namespace. However, from the Gateway side, when I click the generate runtime objects button, every time it will generate a new interface file with new name instead of updating existing one. For Example, I have a backend RFC named as

                         /CNS/LOOKUPLOAD.

After I implemented the mapping for the query, every time it will generate a new interface as

                         /CNS/IF_LOOKUPLOAD,

                         /CNS/IF_LOOKUPLOAD1,

                         /CNS/IF_LOOKUPLOAD2,

                         /CNS/IF_LOOKUPLOAD3.....after I click the generate button multiple times.

I did the test with RFC name. If I name the RFC as ZLOOKUPLOAD, everything will be fine. But we have to add namespace for the RFC.

Could you please help me out?

Thanks for your help.

Tracy

[kammaje_cis · Accepted solution]

That sounds like a bug. You may consider raising to SAP.

Till then, I would suggest you manually delete the not required interface before regenerating the runtime artefacts.

[Tracy · Accepted solution]

Hi Krishna,

Thanks for your reply. I did delete them manually but just time consuming.

If anyone has some experience with this, could you please share it here?

Appreciate your endeavors.

Regards,

Tracy

[kolesnik]

I can here advice you to look main interfaces (without count) at transport request, then delete in SE80 all unnecessary interfaces and, finally, generate the service one more time. This approach should help, in my case it was so

with KR,

Ievgen