SAP has its own internal workflow engine, that includes standard workflow templates for many relevant accounts payable activities. For example, completing parked invoices, coding and approving FI invoices, and resolving line-level blocks on MM-LIV invoices. You can also develop your own workflows in SAP.

For implementations that do not utilize a third-party workflow, you can use the SAP workflow to complete Invoice Processing for documents where Kofax AP Agility Invoice Processing is unable to create a document that is ready for payment in SAP. This may be because it is an FI invoice and coding or approval is required, or because line pairing cannot be completed for an MM-LIV invoice, so the system must park it. In these cases, the documents are routed to users in SAP so that they can be completed at a later time.

An instance of SAP workflow is triggered by an event in SAP. This event can be document parking, or the line item on a posted MM-LIV invoice is blocked by SAP during the three-way match process.

The simplest way to integrate Kofax AP Agility and SAP workflow is to leverage the workflow framework provided by SAP, and hang completion workflows from events that are generated when Kofax AP Agility Invoice Processing creates an incomplete document.

The following list details some example SAP events that are generated when Kofax AP Agility Invoice Processing creates an incomplete document.

PARKED

The SAP business object associated with this event is BUS2081 (MM-LIV document). This system event is raised automatically by SAP when an MM-LIV document is parked, such as, the document has a status of A.

BLOCKEDPRICE

The SAP business object associated with this event is BUS2081. This system event is raised automatically by SAP when one or more line items on a posted MM-LIV document are blocked during the three-way match process on grounds of price.

BLOCKEDQUANT

The SAP business object associated with this event is BUS2081. This system event is raised automatically by SAP when one or more line items on a posted MM-LIV document are blocked during the three-way match process on grounds of quantity.

CREATED

The SAP business object associated with this event is FIPP (parked FI document). This system event is triggered when an FI document is parked. The triggering of this event must be configured within the FI business framework in SAP (SAP transaction FIBF), and is done programmatically using SWE_EVENT_CREATE_FOR_UPD_TASK.

You are responsible for ensuring that the appropriate SAP workflows are available and are configured correctly. You can write a wrapper BAPIs that shares the same interface as BAPI_INCOMINGINVOICE_PARK, which subsequent to parking a document, triggers an instance of the appropriate SAP workflow.