{"id":916,"date":"2025-02-22T11:25:55","date_gmt":"2025-02-22T11:25:55","guid":{"rendered":"https:\/\/sapvimtraining.com\/?p=681"},"modified":"2025-06-09T16:13:22","modified_gmt":"2025-06-09T14:13:22","slug":"intelligent-capture-for-sap-solutions-ic4s-stays-at-the-same-level-forever-without-feedback-does-this-setting-hold-back-your-capture-process","status":"publish","type":"post","link":"https:\/\/johannesauer.com\/de\/sap-vim\/intelligent-capture-for-sap-solutions-ic4s-stays-at-the-same-level-forever-without-feedback-does-this-setting-hold-back-your-capture-process\/","title":{"rendered":"If your SAP VIM Capture feels like it is not learning at all, it might be missing this crucial setting!"},"content":{"rendered":"\n
<\/path><\/svg><\/span>\n

This article is intended for informational purposes only and does not supersede or replace the official documentation provided by OpenText. It serves as supplementary guidance to assist with common challenges that may arise during installation and upgrades. For authoritative instructions and compliance requirements, refer to OpenText\u2019s official documentation.<\/p>\n<\/div><\/div>\n\n\n\n

The capture component used in conjunction with OpenText Vendor Invoice Management for SAP Solutions (SAP VIM) is usually Intelligent Capture for SAP Solutions<\/strong> (short: IC4S; on premise) or Core Capture for SAP Solutions<\/strong> (short: CC4S; hosted in the OpenText Cloud). <\/p>\n\n\n\n

Continuous feedback<\/strong> allows the capture component of VIM to read and interpret more and more incoming .pdf-documents fully or partly. In some systems, however, it is simply never switched on<\/strong>. As a result, the automatic recognition of data on the documents never improves<\/strong> and a high manual validation effort<\/strong> is required. This is not only annoying<\/strong> but also expensive<\/strong>.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

How does the learning work?<\/h2>\n\n\n\n

In simple terms, the process for continuous learning<\/strong> works like this: <\/p>\n\n\n\n

    \n
  1. The system (IC4S or CC4S) extracts as much data as possible from the document <\/li>\n\n\n\n
  2. The extracted data is corrected and supplemented by users in the validation client.<\/li>\n\n\n\n
  3. The corrected results are sent back to the capture component via the so-called feedback link, which expands the set of rules for extracting data and generally delivers a better result for the next similar document.<\/li>\n<\/ol>\n\n\n\n
    \"\"<\/figure>\n\n\n\n

    What is an Archive Link Document Type?<\/h2>\n\n\n\n

    An Archive Link Document Type<\/strong> refers to a classification used for documents that are stored in an external archive system but linked to SAP transactions via SAP ArchiveLink<\/strong>. ArchiveLink is an SAP technology that enables the connection of external document management systems (DMS) to SAP applications.<\/p>\n\n\n\n

    In the simplest case, there is one archive link document type in a VIM project for storing, for example invoices, let’s call it \u201cZINVOICE\u201d. Whether the learning is executed or not depends on the settings assigned for this archive link document type. <\/p>\n\n\n\n

    In VIM projects, usually one or more archive link document types are created for both invoicing and non-invoicing processes. These allow you to create your own scenarios independently of the document types supplied with the product. <\/p>\n\n\n\n

    My recommendation here is always to create your own archive link document types. This makes customization easier and you don’t run the risk of accidentally resetting all possible settings during the next VIM upgrade. However, this also opens the door for the customizing mistake which I describe in this article.<\/p>\n\n\n\n

    Is my system learning or is it standing still?<\/h2>\n\n\n\n

    You can find out in just a few minutes whether your system is learning, or at least is encouraged to learn (in addition to this setting, there are also other reasons that can prevent learning).<\/p>\n\n\n\n

    First we find out which Archive Link document type we are using, the quickest way to do this is in transaction \/OTX\/PF03_WP (VIM Central Workplace) in the work center Inbound administration.<\/p>\n\n\n\n

    <\/circle><\/circle><\/circle><\/g><\/svg><\/span>