Hierarchy

⤷

⤷

IMG Activity
ID | /IWFND/V_MGDETS | Flag OData Services to be error tolerant in case of MDC |
Transaction Code | /IWFND/59000026 | (empty) |
Created on | 20121206 | |
Customizing Attributes | /IWFND/V_MGDETS_ATTR | Flag OData Services to be error tolerant in case of MDC |
Customizing Activity | /IWFND/V_MGDETS_OBJ | Flag OData Services to be error tolerant in case of MDC |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /IWFND/V_MGDETS_TEXT |
Use
Use this configuration to make the READ feed requests of a service in "Multi Destination Composition" mode error tolerant.
Multi Destination Composition
If a feed of a service is called in "Multi Destination Composition" (MDC) mode, the service composes the data from all backend systems assigned to it. More precisely all system aliases assigned for the current user and service are identified. Then the backend system of each of these system aliases is called reading the data from each system. Finally the results of each backend system are composed into one feed that is returned to the client.
To call a service in MDC mode the segment parameter mo is added to the service name of the request URI.
Example
/sap/opu/odata/iwfnd/RMTSAMPLEFLIGHT;mo/TravelagencyCollection
Error behavior
The default error behavior is not error tolerant. If the data retrieval from any of the backend systems causes an error the READ feed request returns that error.
If a service is marked to be error tolerant this behavior changes:
- An error is returned only if the data retrieval from all backend systems causes an error. Otherwise if only some of the backend systems causes an error a feed is returned to the client.
- The data retrieved successfully from some of the backend systems is composed into that feed.
- The data missing form those backend systems that caused an error can be requested again. For that an OData skiptoken is added to that feed.
Example
<link rel="next" href=" TravelagencyCollection?$skiptoken=MISSING_DATA_FROM__1_2" />
Requirements
Standard settings
If a service is not listed in this configuration the service is not error tolerant.
Activities
Create an entry for each service that shall be error tolerant.
Example
Business Attributes
ASAP Roadmap ID | 105 | Define functions and processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
/IWFND/V_MGDETS | V - View | SM30 |
History
Last changed by/on | SAP | 20121206 |
SAP Release Created in | 250 |