Agents: Core

overview core agents are based on the docuflow classification configuration approvers are separate from core agents there are 4 categories of agents associated with docuflow "core" processing initial ap agents review agents note review agents can also be configued according to asl thresholds (such as approvers) please refer to the next section agents approvers for more information final ap agents exception agents each one of those agent categories can also have assigned deadline and catch all agent you can specify as many agents as you would like to 1 processing rule, or you can also choose org units that reference multiple agents this creates virtual "teams" of processors per invoice classification (called "possible agents") docuflow ap and the underlying sap workflow runtime system manages the sharing of these workitems and prevents work items from being processed more than once once a user has "touched" a work item, it is reserved by them for processing until it is either completed or resubmitted back the larger "team" setup below are the options for configuring agents classification standard classification hierarchy wf stage core which stage of the workflow is this rule relevant to (this is mandatory unless you are configuring a "admin" or "deadline" agent) invoice type allows you to split out agents between po vs non po exception code for exception stage, specifies a particular exception admin there must be at least 1 admin agent in your docuflow implementation these are agents who can configure the system and access via tracklink, and also who can perform administrator functions via tracklink deadline indicates this agent is a deadline agent for a particular stage, approval amount, or exception catch all there must be at least 1 catch all agent in your docuflow implementation these are agents which will receive a work item if no agent is found for catch all agents, classification is ignored (only the flag that the agent is a catch all is utilized) workflow agent type choose the applicable agent type workflow agent specify the appropriate agent value based on the workflow type specified above badi customizing options the following badi customizing options are available for agent determination for information on how to implement, please refer to the section "customizing" later in this document custom role resolution / agent determination to implement your own exception processing logic in place/in addition to a docuflow ap workflow exception work item custom notifications to implement your own method of notifying agents