F110 proposal workflow is not designed for approving/rejecting the runs. It is just to validate the F110 data ran by a user, agents can edit/block/delete according to the data before the actual payments.
Please see the detailed explanation in KBA 2765633 - Workflow-based release of payment proposal and payment approval in BCM
The F110 workflow does not support any multilevel release process for payments.
The workflow functions in the payment proposal of transaction F110 support the organization and automation of the work processes.
The Payment Proposal workflow is made to organize the work of the accounting clerks (agents) who have the task to edit and review the payment proposal before the payment run posts the payment documents. The system builds work packages for editing and assigns them to agents. With the usual workflow functionality one of the assigned agents picks a package, edits and reviews the proposal, finally confirms the package and then proceeds with the next package that is not yet assigned to another agent.This is all about work organization and automation.
When an approval process is needed in the SAP payment area, it is necessary to activate and use the product SAP Bank Communication Management (BCM).
The settings in transaction F110WFR determine to which package a payment is assigned and which agents may pick up the package for processing.
The settings do not lead to the work package automatically being assigned to one of the agents.The agent will not be automatically assigned to a work package in SAP standard.So, if the payment proposal has been created and the packages are available, the possible agents will be notified in their inbox of the Business Workplace and one of them has to pick up the packages for processing manually.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.