Role Resolution in Exception Handling 
Role Resolution in Exception Handling
Use
All tasks defined in the standard system for exception handling have a default role in order to restrict the number of possible agents responsible for the concrete exception situation. For this purpose, a function module derives agents from the partner profiles for the incorrect IDoc in role resolution. If this action fails or if an IDoc does not exist at all yet, the IDoc administrator is determined. Thus, agents with different responsibilities can be determined:
Integration
The actual agents (the recipients) of the work item are the agents determined in role resolution, who at the same time are possible agents of the standard task for the work item. The recipients therefore form the intersection from the possible agents of the appropriate standard task and the "permitted agents" of the appropriate partner profile or the IDoc administration.
Prerequisites
For receiver determination you must therefore maintain the following:
Partner profiles IDoc Administration
Agent assignment of the standard task
If the standard tasks are maintained as general tasks, the maximum number of possible agents (that is, all users in the R/3 System) is available, with the result that an agent can always be determined (exception: The IDoc administrator is not maintained).
Features
The following table shows the roles supplied with the standard system, with the function module (FM) which is used for role resolution. The table indicates the standard tasks to which the standard roles are assigned and describes what happens during role resolution.
Standard role/FM |
Standard role for standard task |
Role resolution |
Inbound, outbound |
||
30000013 EDI_ROLE_FOR_ PROCESSING |
TS00008068 (inbound processing error), TS00007989 (outbound processing error), TS00008070 (outbound syntax error), TS00008074 (inbound syntax error) TS30000207 (error during inbound processing of SYSTAT01) |
The permitted agents are determined from the partner profiles. The IDoc administrator is notified if no agent could be found. |
30000001 EDI_ROLE_FOR_ MESSAGE |
TS30000020 (error not assigned to IDoc) TS60001307 (error during outbound processing of IDoc stack, that is, output mode "Collect IDocs") |
The IDoc administrator is determined. |
70000141 EDI_ROLE_FOR_NAST_MESSAGE |
TS70008037 (error not assigned to IDoc for outbound MC) |
If an application problem is involved (for example if an error occurs when writing the application data in the IDoc), the procedure is the same as in function 30000013. If a technical problem is involved (for example if the outbound process code is missing or incorrect), then the IDoc administrator is searched for directly. |
Status confirmation |
||
30000001 EDI_ROLE_FOR_ MESSAGE |
TS30000078 (error status in status confirmation) TS70008373 (error during reading of a status file) |
The IDoc administrator is determined. |
Active Monitoring |
||
30200013 EDI_ROLE_FOR_ IDOC_ACT_MONIT |
TS30200108 (threshold value for active monitoring exceeded) |
The permitted agents entered when RSEIDOCM was started or scheduled are determined. If none is found or the agents are not part of the organization model, the IDoc administrator is determined. |