Instead of dealing with scanning and OCR, invoices can be sent electronically to SAP (thus, the concept of e-invoicing) through EDI or Electronic Data Interchange. This means that all steps are within SAP. In comparison to the previous process flow, you will notice that the green dotted lines cover the whole e-invoicing process. Payment proper will be triggered utilizing the posted SAP document. n/OPT/VIM_WP (VIM Workplace) /n/OPT/VIM_ANALYTICS (VIM Analytics) FB03 (View FI Document) If fully approved, SAP document will be posted. n/OPT/AR_COA (Chart of Authority) /n/ORS/MAIN_SUBS (Substitution Maintenance) /n/OPT/VIM_WP (VIM Workplace)Īpproval Process. n/OPT/VIM_7AX8 (Admin Tool for Monitoring) /n/OPT/VIM_WP (VIM Workplace)
#Open text workflow verification#
Verification / duplicate checks happen for the invoices in SAP. Scanning proper using ICC tool to interpret the document image and convert it to system text. Invoices are prepared as a pre-requisite for scanning. Automated paper to post invoice management (with OCR) process #
You can think of this as a separate server or environment where the scanning of invoices take place. The orange dotted lines indicate that this process happens outside of SAP – specifically in the ICC or the Invoice Capture Center. You will notice that in the process diagram below, the invoices need to be prepared and then scanned before it reaches SAP. This process involves the optical character recognition component of OpenText VIM. Integration of standard SAP functionalities such as invoice verification, financial processing, etc.Īutomated paper to post invoice management (with OCR) process.Take note that in this packaged solution, you can expect features such as: OpenTextĪs such, we can expect several vendor invoices in SAP managed through VIM for further processing. Stakeholders involved in any invoice problem can quickly and efficiently access invoice information, such as relevant PO number, status of invoice payments and more. OpenText™ Vendor Invoice Management for SAP® Solutions (VIM) optimizes and simplifies the process of receiving, managing, routing and monitoring invoices and related documentation. In case you need an overview on the accounts payable process, you may refer to “ SAP CHEAT SHEET: Basic Accounts Payable / Procure to Pay Process”.įrom the OpenText website, VIM for SAP is formally defined below. In this post, we will cover the basic end to end process of VIM for SAP and each of the transaction codes.įor now, let us focus on the keyword’s “vendor” and “invoice”. OpenText VIM or Vendor Invoice Management is associated with the accounts payable process.
odt (OpenDocument word processing format). Output formats: PDF, HTML, EPUB, PowerPoint.Input/storage formats: plain text (with or without markup).There is no lock-in and your content and data will always remain accessible to you and anyone you have shared it with.
#Open text workflow software#
If anything happens to one of the binary output files (e.g., data loss, file corruption, software becomes outdated or is unable to open the file anymore), just re-export or output to a different format. In this workflow, the canonical (reference) source of data is always the plain text format. Edit, process, and preview using any editing software or other program you prefer (or using a variety of tools, for example on the command-line).Create new plain text files or convert existing documents into plain text.The basic workflow for working with plain text document formats involves both input (getting files into Markdown or similar format) and output (converting Markdown into other formats).
0 kommentar(er)
