3713131 - BCO Text Property not being formed on a Custom OData Collection

The BCOText property is not being formed in the metadata of a custom OData collection.

The issue prevents the use of this Custom OData in integration scenarios that depends on said properties.

Error message that may appear when this property is missing:

• org.apache.olingo.odata2.api.uri.UriNotMatchingException: Could not find property with name

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

• SAP Cloud for Customer

1. Create a custom OData collection using the SDK.
2. Add a BCO property to the collection.
3. Observe that the BCOText property is not formed in the metadata.

The "Include Code Descriptions" option is disabled in the Header section of the custom OData service, which prevented the BCOText property from being exposed in the service metadata.

1. Access the OData editor for the custom OData service.
2. Enable the Include Code Description option under the Header section.
   
3. Reactivate the custom OData service.
4. Verify the updated metadata to ensure the BCOText property is now visible.

BCOText, custom OData collection, metadata, Include Code Description, OData editor, integration scenario, CPI, Data Workbench, BCO property , KBA , LOD-CRM-INT-DWB , Data Workbench , Problem

SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions