cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

HTTP-Method not allowed ... no luck with nw gateway function import

0 Likes
2,206

Hi Netweaver experts.

Since today I am plagued by an incomprehensible problem with netweaver gateway function
imports.

Every call ends immediately with the indication that the http method is not allowed:

I tried out several combinations. PUT with/without parameters. POST also with and without parameters.

if anybody knows this kind of problem, please help. i already tried:

  1. regeneration of dpc & mpc
  2. clear model cache (fnd + bep)


Danilo Vorpahl

Accepted Solutions (1)

Accepted Solutions (1)

Andre_Fischer
Product and Topic Expert
Product and Topic Expert

POST is not allowed if the return type is 0..n or 1..n

https://blogs.sap.com/2018/06/29/function-import-the-specified-http-method-is-not-allowed-for-the-re...

Best regards,

Andre

Answers (3)

Answers (3)

Former Member
0 Likes

In Function Import ,For POST Return Cardinality should always be 1.

0 Likes

hi gregor,

yes i've tried with the urlparameters like function calls are documented. this should apply an action. imagine something like "aproveOrderAction" with url parameter "orderid=XS32323"... an entity with property "approved" is something i do not want to implement ;).

we figure out: seems to be a bug with BOPF and resulting Entity cardinality of the function import.


Danilo.

Andre_Fischer
Product and Topic Expert
Product and Topic Expert

It is not a bug of the BOPF Framework (see my answer below) but this kind of return type is already blocked by the SAP Gateway framework that handles the incoming OData request.

gregorw
SAP Mentor
SAP Mentor
0 Likes

Have you tried to add the import parameters to the URL instead of the HTTP Body? Do you use POST because you create something? Why don't you do that by creating an Entity?