cancel
Showing results for 
Search instead for 
Did you mean: 

How to ignore new Entity sets in OData added in Payload after go live (Inbound to SAP)

0 Kudos

When the data is posted from third party tool to SAP...

We have implemented ODATA services for one of the product which is live with the below baseline entity types...and later on we found that there were new entity types added to this by the payload.

when the request was sent now with the latest properties in the payload to SAP ,we noticed an error occurring ;;The Project is Invalid in the response payload.

From the below screenshot we have implemented the data model with the below entity types.
Later in the payload we noticed additional data models added to the service by third party to which we want to ignore those new entity type without adding to the current Data model.

Is there any options are available in SAP to ignore the new properties or entity types in the payload which are not part of the current OData data model.

####

We are trying to verify if any entity sets added to the payload third party software after the initial implementation.

For example below payload with the initial implementation . and later on new entity sets have been added in payload but not avialbe in SAP OData service.

We would like to check how we can ignore the newly added Entity sets .

Initial Implementation with Old Payload ::

{

"VendorRegistrationRecords": [

{

"Entity1": {

},

"Entity2": {

},

}

Question:

Below is the new payload with added entity sets. How can we ignore the new entity (3 and 4 )which is not available in current SAP OData implementation (without adding them to the SAP)

{

"VendorRegistrationRecords": [

{

"Entity1": {

},

"Entity2": {

},

"Entity3": {

},

"Entity4": {

}

}

Accepted Solutions (0)

Answers (0)