Skip to Content

BOPF / GW service: BOPF failed validation still leads to HTTP 201

A BOPF validation works fine when testing.

When creating an entry with the generated GW service (based on our BOPF entity), the entry is not created (conform our failed validation) but the GW service responds with a HTTP 201.

Btw: for this question I cannot even select BOPF as primary tag. I wonder if BOPF is just forgotten by SAP and I should not use it.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jun 30, 2017 at 09:23 AM

    so much for BOPF

    Add comment
    10|10000 characters needed characters exceeded