SAP Knowledge Base Article - Public

2984202 - SF User Connector Error: "404 Obect not found": "COE0007","message":"Entity or ComplexType getStandardAndUserInfoSPDFields is not found"

Symptom

SF User Connector is generating the following error after 2H2020 preview release:

REST API failed due to 404 Not Found: [{"error":{"code":"NotFound","message":"Entity or ComplexType getStandardAndUserInfoSPDFields is not found.","details":[{"code":"COE0007","message":"Entity or ComplexType getStandardAndUserInfoSPDFields is not found."}]}}]Re-trying 0 more times; Error : 404 Not Found: [{"error":{"code":"NotFound","message":"Entity or ComplexType getStandardAndUserInfoSPDFields is not found.","details":[{"code":"COE0007","message":"Entity or ComplexType getStandardAndUserInfoSPDFields is not found."}]}}] 

Environment

SAP SuccessFactors Learning

Reproducing the Issue

User Connector is displaying the above error in the connector logs as well as in connector admin notification every time connector job completes after 2H2020 preview release (b2011 code version).

Cause

LMS is on b2011 but integrated BizX is on 2005 or less, meaning new Sensitive Data Safeguard feature is not present in BizX and SF Connector is triggering the exception when trying to call the feature via API.

Resolution

To resolve this there are 2 options:

  1. Wait until integrated BizX instance is upgraded to 2011 where the new Sensitive Data Safeguard Feature is present (recommended).
  2. Migrate your BizX instance to a preview stack so that it gets upgraded in the Preview upgrade cycle: Migration FAQ

Please Note: Whilst this error is triggering and is displayed in the related Connector logs and notifications sent out to Connector admins, the connector job is still processing the records in the file and completing successfully, provided no other fatal (unrelated) exceptions are triggered.

Workaround:

To prevent confusion for connector admins, one workaround would be to remove their email ID from the relative field on the Connector job's scheduling page in the LMS Admin area. This would prevent them from receiving recurring notifications about this error; which, if their email ID is not removed, they will receive until this BizX instance is upgraded to 2011.   

See Also

2981598 - API for retrieving Sensitive Private Fields Information Failed error in notification or SF User Connector

2981604 - Learning Admin UI rendering Issues - 2H 2020 Preview Release

Keywords

SAP, SuccessFactors, BizX, Learning, LMS, SF User Connector, Connector Error, 2H2020 Release, b2011, Sensitive Data Safeguard, REST API failed due to 404 Not Found, COE0007 , KBA , LOD-SF-LMS-CON , Connectors , Problem

Product

SAP SuccessFactors Learning 2011