Table 49 lists the event notification features supported by the
connector.
Table 49. Event Notification Features
Category | Feature | Support | Notes |
---|---|---|---|
Connector Properties |
|
|
|
| Event distribution | Partial | The connector implements this differently from the standard, but provides all the functionality. |
| PollQuantity | Full |
|
event table |
|
|
|
| Event status values | Partial | The connector has similar status values to the standard values. However, it does not support IN_PROGRESS. |
| Object key | No |
|
| Object name | Full |
|
| Priority | Partial | The higher the number, the lower the priority. Every time the connector polls, an event priority is decremented. When the priority reaches 0, the event is processed. |
Misc. |
|
|
|
| Archiving | Full |
|
| CDK method gotApplEvent() | Full |
|
| Delta event notification | Partial | The connector operates by passing business object data into the SAP application via an ABAP function module. When this function executes successfully, the connector returns SUCCESS; when it fails, it returns FAIL. Because SAP is an open system, the connector supports an extremely open architecture, which allows an ABAP developer to do anything the SAP IDE permits. This includes support for the development of any verb as well as any database manipulation or code execution. |
| Event sequence | Full |
|
| Future event processing | Full |
|
| In-Progress event recovery | N/A |
|
| Physical delete event | No | Delete events are retrieved just like those of any other verb. |
| RetrieveAll | Full |
|
| Smart filtering | Full |
|
| Verb stability | Full |
|