Classification

overview classification of your invoices allows you to configure the rest of the docuflow ap workflow accordingly this include rule processing options such as auto create, auto post, etc approval levels agent determination agent load balancing applicable manual and auto exceptions prioritization further more, classification of invoices provides you many more options when working within docuflow tracklink for inbox work item queue management load balancing sorting filtering prioritization searching in additional, for docuflow statistics as well as your own, classification can provide further options for analysis each tier of classification is optional, and you can also created additional custom tiers if you need each tier can be logically associated with additional tiers to create a hierarchal structure, but this is optional as well classification sources in order for classification to be functional, the values of the classification have to come from somewhere these typically come from the below scenarios but again this is flexible to suite your ap process and business metadata from the time of invoice capture / ingestion direct values metadata from the time of invoice capture / ingestion derived values based on business logic values within sap based on business logic and metadata from 1 and 2 above values obtained only after the creation of an invoice and updated via a docuflow badi badi customization inbox mapping refer to the section inbox mapping in this configuration document values of classification are completely for your purpose only, and each tier can represent whatever you wish them to represent, with each tier being optional classification tiers that come with docuflow are document type this represent the archivelink document type determine by the configuration of docuflow docmanager which receives the inbound to sap request from you content management system the document type (not accounting document type) is the highest overall classification of an invoice companies often just have 1 document type this is the minimum classification you must have for the and is already built into the docuflow system note document type determine who can view images attached to invoices (outside of the docuflow ap workflow) if you require certain invoices to have different security requirements, consider implementing more document types locations location typically represent geographical regions invoice categories invoice categories are the highest level of invoice specific classification some common examples are commercial critical standard request for funds confidential business units business units and departments can also be used stand alone or with a relationship to location, invoice categories, or each other departments business units and departments can also be used stand alone or with a relationship to location, invoice categories, or each other invoice flags invoice flags tend to be very granular in nature and typically identify a very specific instance of an invoice that requires "special" processing along its lifecycle whether that be high priority processing from the ap team such as early pay discounts to an auto exception such as admin kick out invoice types invoice types are pre built in docuflow and consist of po non po docuflow determines this as to whether there is a po number at time of capture/ingestion or based on which type of invoice is chosen to be created by the system or the initial ap team invoice type is the minimum an invoice can be classified as workflow container names in the workflow trigger metadata mapping (or your customizing options), below are the corresponding workflow container names (must be upper case) zar object zlocation zinvoicecategory zbusinessunit zdepartment zinvoiceflag zinvoicetype badi customizing options the following badi customizing options are available for invoice processing for information on how to implement, please refer to the section "customizing" later in this document custom invoice classification to manipulate the classification for an invoice