My Oracle Support Banner

FA:SCM:COMMON - REST API Framework Version and Converting XML To JSON (Doc ID 2747771.1)

Last updated on MAY 06, 2022

Applies to:

Oracle Fusion Inventory Management Cloud Service - Version and later
Information in this document applies to any platform.


How to user REST API Framework Version When Converting XML To JSON?

How to eliminate the user of "@" in REST API response?


Users are using below API to get field LotControlValue and expanding ItemEffCategory to get child API.'12345' and OrganizationCode='INV_ORG'&expand=ItemEffCategory&fields=LotControlValue,OrganizationCode,ItemNumber,ItemId&onlyData=true

API response is having value "@" which is causing issue while configuring REST adapter with Response payload in OIC.

  "@context": {
  "key": "100000008602997,300000043094541,100000008602997,300000043094541",
  "headers": {
  "ETag": "ACED0005737200136A6176612E7574696C2E41727261794C6973747881D21D99C7619D03000149000473697A65787000000002770400000002737200116A6176612E6C616E672E496E746567657212E2A0A4F781873802000149000576616C7565787200106A6176612E6C616E672E4E756D62657286AC951D0B94E08B0200007870000000017371007E00020000000578"

If user remove "@" while configuring response in OIC, we are getting below error:

"Failed to translate JSON to XML. Expected attribute value The incoming data does not conform to the NXSD schema. Please correct the problem."


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.