SAP Knowledge Base Article - Public

2628379 - Working with generateNextPersonID - 405 Response

Symptom

In this document we will go through the process of working with the Entity generateNextPersonID in the context of OData API.

In particular we will be reviewing the 405 Response error code.

Environment

  • BizX
  • OData API
  • Postman

Reproducing the Issue

  1. Create the query as follows - for example using Postman Enviornment:
    GET: https://apiXXpreview.sapsf.eu/odata/v2/generateNextPersonID
  2. View response error code:
    {
    "fault": {
    "faultstring": "Received 405 Response without Allow Header",
    "detail": { "errorcode": "protocol.http.Response405WithoutAllowHeader" }

    }

Cause

The entity generateNextPersonID is a function import, the request header should be POST.

It should not be GET.

Resolution

Create the query using the POST operation as such:

PostmanWorking.PNG

See Also

OData API: Reference Guide:
https://help.sap.com/doc/74597e67f54d4f448252bad4c2b601c9/1802/en-US/SF_HCM_OData_API_REF_en.pdf

Keywords

  • OData API
  • b1802
  • generateNextPersonID
  • Response 405
, KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , SF Integrations - EC Payroll, Boomi/ HCI, API , How To

Product

SAP SuccessFactors HCM Core 1802