Actions are the resolution steps that can be executed in BDEx in order to either investigate or resolve exceptions. The purpose of actions is to stream-line the navigation of the user from the BDEx framework into the appropriate transaction within the underlying system where the exception resides (e.g. SAP ECC, SAP CRM, XI/PI etc.). Note that this might also include a non-SAP system.
Further more, they may instead call standard BAPI’s or other internal function modules rather than navigating to the standard transaction(s) in order to perform the required function.
Action Header Configuration
Actions are configured within the table /BTI/MDE_C_ACT. This represents the header information of the action.
| Field | Description |
| Action ID | Unique reference to the action |
| Function Code | The function code of the action |
| Reference Class | The action’s executing class |
| Reference Method | The action’s executing method |
| Icon | Not longer supported |
| Refresh | A flag to indicate that the list of work requests should be refreshed after the action has executed |
| Inactive | Deactivates the action |
Custom actions not delivered in the standard product should have their “Action ID” within the customer name space (i.e. starting with Z or Y).
Refer to the BDEx developers guide.
Master Data Actions
Master data actions are those actions that can be executed upon the master data objects within the hierarchy. This table provides the link between a master data object and the relevant action, plus the order the actions will appear in the relevant context menu.
| Field | Description |
| Master Data Object ID | The ID of the master data |
| Action ID | The ID of the action |
| Sequence number | Determines the order in which master data actions will appear |
Work request actions
Work request actions are those actions that are executable upon the work requests themselves. These take the user into the appropriate underlying transaction for the exception itself in order to resolve the issue. As mentioned earlier, however, this may actually just call a BAPI or perform some underlying functionality without navigating to a separate screen.
| Field | Description |
| Work request class | The work request class ID |
| Work request subclass | The work request subclass ID |
| Status | The work request status ID |
| Action ID | The action ID |
| Action sequence | The order this action should appear in the context menu |
| Work request history relevance | Whether this action is available for work requests in the historical view |
Similarly to the master data actions, exception actions are linked from the action header to the work request via this table.
Post your comment on this topic.