Skip to Content
avatar image
Former Member

HCI error when we attempt to access ODATA entity

Sep 15, 2017 at 07:38 PM | 377 Views

We get the below error in HCI when we attempt to access an ODATA entity:

  • com.sap.gateway.core.ip.component.odata.exception.OsciException: Bad Request : 400 : HTTP/1.1 <?xml version="1.0" encoding="utf-8"?><error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code>COE_BAD_PROPERTY_EXPRESSION</code><message lang="en-US">[COE0003]Bad property expression: FOLocation/addressState; FOLocation/addressState is not viewable</message></error>

we get this error only with 1 single entity. We're able to access other entities without issues.

Thanks

SAP Cloud Platform Integration tools
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Sriprasad Shivaram Bhat
    Sep 18, 2017 at 06:19 AM

    Hello,

    Basically this is issue with your SuccessFactors configuration.Ask your SuccessFactors consultant to enable or mark it viewable the field at API level.

    Got some KBA on enabling the visibility from API perspective( unfortunately not from field perspective) ,but you need to do it at field level.

    https://apps.support.sap.com/sap/support/knowledge/public/en/2148306

    Basically this setting needs to be done from SF side not from HCI end.

    Regards,

    Sriprasad Shivaram Bhat

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member
      Sep 21, 2017 at 09:18 PM

      Sriprasad, bear with the delayed response. Thanks for taking the time. I've requested our EC consultant to check the field properties. Meanwhile, I missed to include this in my initial note. We don't get this error in Boomi when we access the same entity and it works fine. Does HCI alone need this field property set?

      Thanks

  • avatar image
    Former Member
    Sep 26, 2017 at 10:03 PM

    Hi Sriprasad, We found out from the API guide, we were looking at the wrong entity. Once we changed the entity, we didn't see this error again. Thanks for taking the time.

    Add comment
    10|10000 characters needed characters exceeded