Show TOC

Constraints Using BOR Data SourcesLocate this document in the navigation structure

Constraints

Note the following constraints, together with workarounds when using BOR data sources. Workarounds for constraints 2 and 3 are must-haves (that is, there is no OData exposure at all without them).

Workarounds for constraints 4 to 6 are required to support modifying operations.

  1. There should be at least one GetList (Query) and one GetDetail (Read) operation in a Data Model; for more information, see the OData specification at http://www.odata.orgInformation published on non-SAP site.

  2. Check for the availability of a BAPI that can be mapped to the Query operation (typically the GetList method of the corresponding BOR object).

    Check for mandatory importing parameters.

    Note

    Tabular parameters cannot be supported, that is, they will rule out a BAPI.

    Workaround: Extend the BAPI; see Customer Enhancement of BAPIs.

  3. Check for the availability of a BAPI that can be mapped to the Read operation (typically the GetDetail or GetProperties method of the corresponding BOR object).

    You need to have simple importing parameters and fields of the structure, importing parameters uniquely identifying an instance of the BOR object.

  4. Check for the availability of a BAPI that can be mapped to the Create operation:

    In the same way as for Query (above), check that there is no mandatory table import parameter.

    If there is, check if it can be supplied with empty content (that is, with no lines).

  5. Check for the availability of a BAPI that can be mapped to the Update operation (typically the Change method of the corresponding BOR object):

    In the same way as for Read (above), key parameters identifying the instance to be updated must be simple or structure fields.

    Check if the BAPI can be used to update all fields of the BOR object or if there are multiple BAPIs for updating different parts of the BOR object.

    In the latter case, a full update cannot be supported because only one BAPI can be mapped to the Update operation of the Data Model.

  6. Check for the availability of a BAPI that can be mapped to the Delete operation.

    In the same way as for Read (above), parameters identifying the instance to be deleted must be simple or structure fields.

More Information

For more information on possible constraints see SAP note 1574568 Information published on SAP site.