Using Responsibilities to Define Roles
A responsibility is an organizational object where you group together the criteria that workflow needs in order to match work items to possible agents at runtime. This is a straightforward way to define these criteria, and you do not need to customize anything or use ABAP coding.
There are many ways in which you benefit when you use responsibilities to define roles. By doing so you can:
Before defining roles, you must define workflow steps using the processes set out in SAP Business Workflow. Then define the tasks which must be performed. You then use standard roles to assign and locate a list of the possible agents for the task at runtime.
Responsibilities can only be created for existing standard roles.
To define roles using responsibilities, you:
A container is a generic structure which transfers data at runtime. It is essential to create the container definition first, because the responsibility depends on the data you select in the container. For each criterion that you choose to evaluate at runtime, you must define an appropriate container element.
Here you can also edit the values and view the container elements.
If at runtime the values in the role container match the criteria defined at a responsibility, the organizational objects assigned to that responsibility are identified as possible agents of the work item.
By matching the values in the role container with the criteria defined at the responsibilities, SAP Business Workflow identifies the possible agents of a work item. As a result, the right person receives the right work item at the right time, ensuring that your business processes take place efficiently and on time.