Johannes Auer

Hinweis: Wir veröffentlichen alle Blogbeiträge ausschließlich auf Englisch.

Author: Johannes Auer

Quick Fix: Resetting Document Layout Learning Data in SAP VIM
Are you struggling with single documents extracting wrong data in SAP VIM inbound process after coming back from extraction by IES (Intelligent Capture for SAP Solutions [IC4S] or Core Capture for SAP Solutions [CC4S])? Wrong training might be the reason for this.

The good news: You don’t have to reset all training data. With just a few steps, you can identify and reset the learning data for one specific layout.

What is a Document Layout?

On a very high level a Document Layout is a unique identifier for all documents that look the same. Meaning that usually all documents from one vendor share the same document layout while the content is different. In some cases it can also be that multiple vendors are using the same layout id. Machine learning through validation and feedback usually affects only one Document Layout.

How can I identify my LayoutID?

We can quickly find the Layout ID in the Inbound Administration:
```
/otx/pf03_wp
```
First you need to know your Registration ID or Target ID.

RegID is the ID you see in the Validation Client.

Example: RegID shown in the Validation Client for Windows

Target Key is the Workitem ID in the target process (e. g. VIM Doc. Id for invoice processing.

The Target Key may not be unique in your system. There can be an invoice with Doc. Id. 1 and an order confirmation using the same target process key.
Example: VIM Doc. Id in VIM Invoice Workplace ( /OPT/VIM_WP )

Once you know which ID to use for identifying your document you can utilize the selection pane. Make sure to press Apply once you have filled Registration ID or Target Process Key.

Once you have identified the document you want to reset the learning data for you can read the value in column Document Layout Id:

How can I reset the learning data for my Layout ID?

1) Switch to Work Center IES Administration

2) Select Layouts

3) Filter for your Layout Id and choose Reset Layout.

Conclusion

Resetting the learning data for a single layout in SAP VIM is a simple yet powerful way to fix recurring extraction issues without impacting other vendors or document types. By identifying the correct Layout ID, verifying which documents are linked to it, and resetting only that layout, you avoid unnecessary retraining and keep your inbound process running smoothly.

This targeted approach helps you regain accuracy quickly, reduces manual corrections, and ensures that SAP VIM continues to learn the right patterns from your documents.

At the end of the day, machine learning in SAP VIM Capture follows a simple rule: “garbage in, garbage out” If your training data is wrong, your results will be wrong. Resetting the layout gives you the chance to fix the root cause instead of just correcting errors endlessly.

If you have the impression that your capture application does not learn at all check out the article If your SAP VIM Capture feels like it is not learning at all, it might be missing this crucial setting!

Training

If you want to dive deeper into validation, training, and optimization of OpenText Capture in SAP VIM, check out my Udemy course: OpenText Capture Validation for SAP VIM & Beyond Invoices – where I walk you through practical examples, tips, and real-world troubleshooting strategies.

Your team could be spending hours every week on avoidable validation tasks — a frustrating effort that can often be avoided with the right setup and training. In this course, I walk you through practical examples, proven tips, and real-world troubleshooting strategies to help you cut down on wasted time and improve accuracy.
October 1, 2025
Struggling With Logic Modules in SAP VIM? Here’s How to Master the Debugger (Without Going Crazy)
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. For authoritative instructions and compliance requirements, refer to OpenText’s official documentation and support. Do not use this in production systems.
Debugging Logic Modules in SAP VIM is rarely straightforward. Setting multiple breakpoints, stepping through code execution, and still failing to reach the relevant section can quickly become frustrating and time-consuming.

However, there’s a little-known approach that can make this process far more efficient.

In case you are interested in creating your own Logic Module in VIM check this article: How to Create a Custom Logic Module (Data Enrichment) for SAP VIM Invoice Processing (Step-by-Step Guide)

The Hidden Program That Simplifies Debugging

Within the SAP VIM development packages, there is a program that can be executed via transaction SE38:
```
/OPT/DR_BPF_TEST
```
This program does not appear in the standard OpenText documentation, which means many consultants are unaware of its existence. Yet it provides a structured way to analyze and debug Logic Modules.

Key Capabilities
- Display a list of all Logic Modules executed for a given document
- View the sequence of module calls in detail
- Decide whether to simulate the process start, rerun business rules, or both.
- Set a breakpoint in the code and execute the program in SE38 to jump into the debugger without detours
This transforms debugging from a trial-and-error exercise into a transparent, manageable process. Instead of relying on chance to intercept the correct module, you can work systematically through the exact logic that is being applied.

How to use it
1. Execute the program in SE38
2. Enter the corresponding VIM DP document ID, decide if you want to check the process start, the re-run of business rules or both and decide if you want to show the modules only or process them:
3. Benefit from a clean list that gives all relevant information for debugging Logic Modules. You can pick up the class name, set a breakpoint in the code and repeat.
Why This Is Valuable

Effective debugging is essential in every OpenText Vendor Invoice Management for SAP Solutions (VIM) project, whether for customizing workflows, implementing enhancements, or analyzing issues in production support. By providing direct insight into the sequence and behavior of Logic Modules, /OPT/DR_BPF_TEST can significantly reduce the time spent on troubleshooting.

Because this tool is not part of the official documentation, knowledge of it can provide consultants and project teams with a clear advantage when working on complex VIM implementations.
September 18, 2025
What is Smart Coding and how can I use it in SAP VIM?
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. For authoritative instructions and compliance requirements, refer to OpenText’s official documentation and support.
In the world of Accounts Payable automation, efficiency is king. One of the standout innovations in Open Text Vendor Invoice Management (VIM) for SAP Solutions is Smart Coding — a feature designed to make invoice processing faster, more accurate, and less dependent on repetitive manual entries.

What is Smart Coding?

Smart Coding is a machine learning–driven function in VIM that helps users automatically assign coding proposals to invoice line items. Instead of manually entering cost centers, GL accounts, or other coding data every time, VIM learns from historical postings and suggests coding values during document indexing.

Availability of this feature depends on your VIM version, and the specific fields that can be learned may differ.
Benefits of Smart Coding
- Time savings: Reduces manual effort in entering repetitive cost allocations.
- Consistency: Ensures coding aligns with historical and organizational patterns.
- Fewer errors: Minimizes the risk of incorrect GL postings.
- Scalability: Supports large volumes of invoices without increasing headcount.
Basic Model and PAL Model: What’s the difference?

In Open Text VIM Smart Coding, the Basic Model and the PAL Model differ mainly in complexity and accuracy.

The Basic Model is a simple, frequency-based approach. It analyzes historical postings for a given company code and supplier, then suggests a GL account and cost object based on how often that combination was used before. It’s easy to set up and works as a foundation, but it’s limited to pattern recognition and doesn’t adapt well to complex scenarios.

The PAL Model, on the other hand, is powered by SAP HANA‘s Predictive Analytics Library (PAL). It applies machine learning, using multiple factors like company code, supplier, requester, expense type, tax rate, and invoice amount to generate proposals. This makes it far more accurate and dynamic than the Basic Model, but it requires SAP S/4HANA with PAL installed and builds on the Basic Model‘s training.

In short: the Basic Model is static and straightforward, while the PAL Model is context-aware and designed for higher accuracy in real-world invoice coding.

How to activate Smart Coding

Step 0: Read the documentation and test in a sandbox environment first.

Make sure to check chapter Smart coding in OpenText Vendor Invoice Management for SAP Solutions: Configuration Guide for Invoice Solution. Please understand that Step 1 deletes all coding statistics from your system.

Step 1: Delete Coding Statistics

To start with a clean surface the first step is to delete what is in the system using T-Code /OTX/PS302_TRAIN_CODING_DELETE.

Warning: This will delete the coding statistics in the selected system!

Step 2: Train Coding Statistics: Basic Model

Now that we have an empty Smart Coding environment we start by training the basic Smart Coding model using /OTX/PS302_TRAIN_CODING.

For the first run always use the “Test Mode” to make sure everything is working correctly. If the first run in test mode was successful, it can be repeated without test mode.

From this point of time it is already possible to use smart coding in the system by clicking on Smart Coding button in the Line Items Tab on the Indexing Screen:

Step 3: Train Coding Statistics: PAL Decision Model

To use the more advanced PAL Decision Model you must ensure that your system has the following prerequisites in place:
- SAP S/4 HANA
- PAL model installed and activated
- Basic Model training is completed (Step 2)
Similar to the Basic Model: for the first run always use the “Test Mode” to make sure everything is working correctly. If the first run in test mode was successful, it can be repeated without test mode.

Once you have completed the training for the PAL Decision Tree Model you can see an entry in VIM Central Workplace (/n/OTX/PF03_WP) in work center Smart Coding:

Final Thoughts

Smart Coding in OpenText VIM can offer significant benefits — especially for organizations processing moderate to high invoice volumes. It has the potential to reduce manual data entry, improve consistency, and help teams spend less time on repetitive tasks. However, it’s important to keep expectations realistic:
- Smart Coding usually requires a period of training before it produces reliable results. Initially, proposals will need review, and accuracy may be limited for uncommon combinations or new suppliers.
- The PAL model improves accuracy over the basic model, but it also requires a solid foundation: enough historical data, correct setup, and ongoing monitoring.
- Smart Coding won’t eliminate coding errors entirely. Edge cases, exceptions, complex allocations, or unusual cost objects will still require human intervention.
- Benefits are greatest when invoice volumes are high and coding rules relatively stable. In very volatile or complex environments, the value may be less dramatic.
In short: Smart Coding can be a useful tool to help reduce workload and increase consistency, but it’s not a magic bullet. Proper expectation setting, pilot testing, and incremental rollout are key for getting good value.

What has been your experience with Smart Coding so far? Did it meet your expectations, or did you run into challenges? Share your thoughts in the comments below — I’d love to hear them.
September 11, 2025
How to Create a Custom Logic Module (Data Enrichment) for SAP VIM Invoice Processing (Step-by-Step Guide)
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’s official documentation.
When working with SAP Vendor Invoice Management (VIM), standard configurations often cover the majority of business needs — but not all of them. In many projects, there comes a point where additional data enrichments are required to ensure invoices are processed correctly and efficiently. This is where Logic Modules come into play. Logic Modules allow you to extend VIMs capabilities by injecting custom ABAP code into the document processing flow.

In this guide, I’ll walk you through creating a simple data enrichment logic module, step by step: from the ABAP implementation to configuration in /n/OPT/SPRO and finally the mapping to document types. By the end, you’ll have a working example that you can adapt to your own project requirements.

1. Creating the logic module class

Creating the logic module class using superclass /OPT/CL_D_LM_SUPER.

Redefine method /OPT/IF_D_BP_MODULE~PROCESSING

A very minimalistic logic module can just consist of one line:
```
  METHOD /opt/if_d_bp_module~processing.
    ev_success = 'X'. "this is important!
  ENDMETHOD.
```
It is important to remember giving back ev_success = ‘X’ in logic modules as the missing success indicator can cause the following logic modules to not start.

“Success” in this case does not mean that actual data was enriched but just that the logic module did not encounter any issue. This is different in VIM Beyond Invoices Data Enrichments where you only want to give the success marker back when there was really data enriched.

As an empty logic module does not bring any benefit so lets give it some simple logic. Here’s a basic example that sets an empty reference number to “Test” + DocID::
```
  METHOD /opt/if_d_bp_module~processing.

* in case the reference number is empty we fill it with "Test" and the current docid. Resulting in e. g. "Test5" for Doc. ID 5.
    IF cv_index_header-xblnr IS INITIAL.
      CONCATENATE 'Test' cv_index_header-docid INTO cv_index_header-xblnr.
    ENDIF.
    
    ev_success = 'X'. "this is important!

  ENDMETHOD.
```
Save and activate your Logic Module class.

2. Defining a Logic Module

Now that we have created the logic module class lets head to /n/OPT/SPRO and navigate to Document Processing Configuration > Document Type Configuration > Logic Module Processing > Logic Module Processing

Create an entry with an unique Module ID, a meaningful descripton and the name of the class you just created:

It is a good practice to start custom logic modules with a “Z” and stick to the naming convention from product standard.

Example: “ZN_ITEM_001” is affecting NPO Invoices and updates line item information (001 is a running number) while “ZP_HEAD_001” is affecting PO-Related invoices and header information is updated.

Remember the name and move on to the next step.

3. Processing Definition and Module Processing Steps

You can Imagine a “Processing Definition” as a collection of logic modules which you can later assign to a DP document type like “Z_NPO” or “PO_75”. It is not possible to directly assign a logic module to a document type therefore lets create a Processing Definition. Add a Process ID and a Description and you can move on the “Module Processing Steps”:

For a basic processing definition with just one module you can simply add a counter (We suggest using 10 so you can add something before this module later), the Module ID we defined before, the “Active” checkbox and the Processing mode (Run only at processing start, only when re-running business rules or both):

Now we have created our collection of logic modules (with just one logic module for now) and can can move on to the next step: Process Mapping.

4. Mapping groups of Logic Modules (“Processing Definition”) to DP Document Types

To complete the setup you simply assign you Process ID (“Processing Definition”) to one or more DP Document Types:

Official Documentation

Always cross-check your setup with the official Open Text Guides. Starting with chapter “Processing logic modules” in “OpenText Vendor Invoice Management for SAP Solutions: Configuration Guide for Invoice Solution” (for your Version of VIM) is good idea.

Outro

Logic Modules are a powerful way to adapt SAP VIM to the unique requirements of your organization. Even though the example shown here is very simple, the same principles can be applied to implement far more complex business logic — from tax code adjustments to automated field population.

By following the approach outlined above, you now have a blueprint for creating, configuring, and deploying your own custom Logic Modules. With this flexibility, VIM becomes not just a standard solution but a platform you can tailor precisely to your processes.
August 29, 2025
Stay Ahead of SAP VIM Compatibility Issues: the Orange Compatibility Matrix for VIM and Capture
If you’re managing SAP Vendor Invoice Management (VIM) and Capture solutions, ensuring compatibility between different software versions is critical. Open Text provides an invaluable resource—the “Orange Compatibility Matrix”—to simplify this.

What is the Orange Compatibility Matrix?

The Orange Compatibility Matrix is an essential document provided by Open Text that outlines which versions of OpenText Vendor Invoice Management for SAP Solutions (VIM) are compatible with various Open Text Capture solutions. It clearly displays supported configurations, ensuring you always pair compatible software versions to maintain system stability and optimize performance.

How to Obtain the Orange Compatibility Matrix:
1. Navigate to support.opentext.com.
2. Log in using your Open Text Support credentials.
3. In the search bar, enter KB0795415.
4. You’ll be directed to the article with a download link for the latest “Orange Compatibility Matrix for VIM and Capture for SAP Solutions”.
5. Download and refer to the matrix when planning software updates or troubleshooting compatibility issues.
Why is the Orange Compatibility Matrix Useful?
- System Stability: Ensures your system operates reliably by confirming compatibility between VIM and Capture solutions.
- Support Assurance: OpenText Support verifies compatibility using this matrix. Unsupported combinations are not eligible for official support, potentially leaving your organization without assistance during critical issues.
- Simplifies Upgrade Planning: Clearly see what combinations of VIM and Capture solutions are certified to work together.
Regularly checking the Orange Compatibility Matrix will keep your SAP VIM environments running smoothly.
April 1, 2025
If your SAP VIM Capture feels like it is not learning at all, it might be missing this crucial setting!
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’s official documentation.
The capture component used in conjunction with OpenText Vendor Invoice Management for SAP Solutions (SAP VIM) is usually Intelligent Capture for SAP Solutions (short: IC4S; on premise) or Core Capture for SAP Solutions (short: CC4S; hosted in the OpenText Cloud).

Continuous feedback 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. As a result, the automatic recognition of data on the documents never improves and a high manual validation effort is required. This is not only annoying but also expensive.

How does the learning work?

In simple terms, the process for continuous learning works like this:
1. The system (IC4S or CC4S) extracts as much data as possible from the document
2. The extracted data is corrected and supplemented by users in the validation client.
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.
What is an Archive Link Document Type?

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

In the simplest case, there is one archive link document type in a VIM project for storing, for example invoices, let’s call it “ZINVOICE”. Whether the learning is executed or not depends on the settings assigned for this archive link document type.

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.

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.

Is my system learning or is it standing still?

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).

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.
```
/otx/pf03_wp
```
Select the “Processed” note and select the line of a recently processed document.

In the line you can scroll to the right until you see the column “Document type”. Note all the Document types you are using. For example “ZINVOICE”.

The next step ist to check the customizing in /OTX/PF00_IMG.
```
/otx/pf00_img
```
Navigate to Inbound Configuration > Capture > Feedback:

In the table you should see all active archive link document types you are using with an active checkbox next to them:

In case you archive link document type is missing here there will be no learning taking place after validating documents. This means that your validation process does not generate a sustainable learning effect but is only valid for the current document.

My learning is not activated, how do I solve the problem?

The problem is quickly solved. Add the missing entry in the development system, test, transport and the issue is resolved (learning will only take place for newly processed documents).

Why didn’t we realize this earlier?

In the case of non-invoice-related document processes, the problem is usually immediately apparent because without learning results, not a single field (with the exception of business entities) is recognized and therefore an exorbitantly high validation effort is required.

The situation is different for invoice-related processes, where the product standard already provides basic recognition results, which are then improved by validation. Therefore you already have a basis of recognition results and do not initially notice that the feedback is missing.

Conclusion

This setting is very simple but unfortunately easy to overlook. The system does not complain about the missing setting and everything initially appears to be working. If this article has helped you to resolve a big problem in a simple way, I would be happy if you share it!
February 22, 2025
Creating a Business Rule for SAP VIM Solutions Beyond Invoice (+ free Template)
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’s official documentation.

Please note that this article is not about the VIM Invoice process but VIM Solutions Beyond Invoice which is, for example, used to process sales orders, quotations, remittance advices, order confirmations or fully custom document processes (including capture & recognition using OpenText Intelligent Capture for SAP Solutions [IC4S]).

VIM Solutions Beyond Invoice is formerly known as Business Center and sometimes referred to as VIM Beyond.
Similar to the invoice process, the document process in SAP VIM Solutions Beyond Invoice is made up of data enrichments, roles, business rules and actions. In today’s article, I will show you how to quickly and easily create and configure an individual business rule. I also provide my template which allows an easy start for your new business rule.

Creating a Business Rule class

Create a new class using superclass /OTX/PF04_CL_MODULE. You can use for example SE24 or SE80 to achieve this.
```
/OTX/PF04_CL_MODULE
```
To implement a business rule you must redefine method /OTX/PF04_IF_MODULE~MODULE_EXEC_CHECK.
```
/OTX/PF04_IF_MODULE~MODULE_EXEC_CHEC
```
In earlier versions, data was changed with the help of business rules. This is becoming obsolete today and should therefore be avoided. Business rules check data, data enrichments change data. It is easy to convert old business rules into data enrichments.

As a starting point you can use my business rule template:
ABAP METHOD /otx/pf04_if_module~module_exec_check. DATA: ls_plh TYPE z01ca_otx_bc_plh, ” header table lt_pli TYPE TABLE OF z01ca_otx_bc_pli, ” line item table lv_pos TYPE c LENGTH 10, ” line item position for messages ls_msg TYPE SYMSG. ” message FIELD-SYMBOLS: <fs_pli> TYPE z01ca_otx_bc_pli. ” line item table ls_plh = pis_plh. lt_pli = pit_pli. pe_mod_run_status = /otx/pf04_if_category=>mc_run_stat_success. ” set rule to successful initially LOOP AT lt_pli ASSIGNING <fs_pli>. CLEAR: lv_pos, ls_msg. “[…] logic ” pe_mod_run_status = /otx/pf04_if_category=>mc_run_stat_failed. ” set rule to failed ls_msg-msgty = ‘E’. ls_msg-msgid = ‘Z…’. ls_msg-msgno = 123. ls_msg-msgv1 = ‘This rule always fails..’. “[…] APPEND ls_msg TO pet_mod_msg. ENDLOOP. ENDMETHOD.
```
   METHOD /otx/pf04_if_module~module_exec_check.

    DATA: ls_plh   TYPE z01ca_otx_bc_plh, " header table
          lt_pli   TYPE TABLE OF z01ca_otx_bc_pli, " line item table
          lv_pos   TYPE c LENGTH 10, " line item position for messages
          ls_msg   TYPE SYMSG. " message

    FIELD-SYMBOLS:  TYPE z01ca_otx_bc_pli. " line item table

    ls_plh = pis_plh.
    lt_pli = pit_pli.

    pe_mod_run_status = /otx/pf04_if_category=>mc_run_stat_success. " set rule to successful initially

    LOOP AT lt_pli ASSIGNING .

      CLEAR: lv_pos, ls_msg.
      
      "[...] logic
      
      " pe_mod_run_status = /otx/pf04_if_category=>mc_run_stat_failed. " set rule to failed 

      ls_msg-msgty = 'E'.
      ls_msg-msgid = 'Z...'.
      ls_msg-msgno = 123.  
      ls_msg-msgv1 = 'This rule always fails..'.
      "[...]

      APPEND ls_msg TO pet_mod_msg.
    ENDLOOP.

  ENDMETHOD.
```
Customizing for a SAP VIM Solutions Beyond Invoice Business Rule

Now we have created the class for our business rule and have to create the corresponding customising, which can be done very quickly in the transaction /otx/pf00_img.
```
/otx/pf00_img
```
Navigate to Process Configuration > Profiles:

Select your Profile Configuration and navigate to the corresponding Version > Characteristic Configuration and select Process Steps. Select the process step where you want to add the business rule, then navigate to Rules.

When creating the rule, it is important that the rule type here is CHK. Change (CHG) rules are obsolete and have been replaced by data enrichments. Your business rule should not change any data.

Don’t forget to activate the active checkbox on the right-hand side of the screen, as this can easily be overlooked depending on the screen resolution.

Basically, the rule is now active and can be tested. In Customizing, however, you still have to decide which role can skip which rules in which step. Depending on the number of steps and roles, this can be quite extensive:

In general, the simulation of each step should be allowed in all steps and the skipping of rules should also be permitted.

Final Thoughts: Less Is More

When crafting business rules for non-invoice scenarios in SAP VIM, it’s tempting to add a high number of rules to check every possible scenario. But complexity can lead to confusion of the end users and slow performance.

Focus on the minimal rules that truly matter—clearly defined conditions, straightforward actions, and well-documented workflows. It can also make sense to group multiple checks into one business rule to declutter the workspace. For example the rule missing material number and invalid material number can be combined into one rule.

By keeping it simple, you’ll speed up maintenance, reduce errors, and allows you to adapt more quickly when requirements change.
February 16, 2025
Creating a Data Enrichment for SAP VIM Solutions Beyond Invoice (+ free Template)
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’s official documentation.
A data enrichment is a logic or learning based data manipulation which can run, for example, at the begin of a process. From a usage point it is very comparable with a logic module in the VIM Invoice process.

Please note that this article is not about the VIM Invoice process but VIM Solutions Beyond Invoice which is, for example, used to process sales orders, quotations, remittance advices, order confirmations or fully custom document processes (including capture & recognition using OpenText Intelligent Capture for SAP Solutions [IC4S]).

To be precise, Solutions Beyond Invoice describes the supplied solution packages, while the Foundation describes the creation of customised solutions, actions, rules and so on. For the sake of simplicity, I will refer to both as Solutions Beyond Invoice.

In the following steps I will describe how to create a logic based data enrichment for SAP VIM Solutions Beyond Invoice.

In case you are interested about learning based data enrichments please check the
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide for Foundation.

In case you are interested about using logic modules for the VIM Invoice process please refer to the OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide for Invoice Solution.

VIM Solutions Beyond Invoice is formerly known as Business Center and sometimes referred to as VIM Beyond.

In earlier versions, data was changed with the help of business rules. This is becoming obsolete today and should therefore be avoided. Business rules check data, data enrichments change data. It is easy to convert old business rules into data enrichments.
Creating a data enrichment ABAP class

The initial step in this process is to create a new class that is both appropriately named and described, while adhering to the relevant naming conventions. You case use for example SE24 or SE80 to achieve this.

It is essential to add the correct interface for data enrichments. In the version I am working with, this is /OTX/PF04_IF_DATA_ENRICH_EX.
```
/OTX/PF04_IF_DATA_ENRICH_EX
```
The implementation is carried out in method /OTX/PF04_IF_DATA_ENRICH_EX~DATA_ENRICH_LOGIC.
```
/OTX/PF04_IF_DATA_ENRICH_EX~DATA_ENRICH_LOGIC
```
I use the following minimalist template for my projects. It already declares the structures, table and field symbol which are needed for processing header and line information. In addition, the success marker is set, if you forget this, the data enrichment is not even executed.

As the naming conventions for variables and the tables used change from project to project, I recommend creating this template once for each project.

If the data enrichment is only executed at the start of the process, it will be helpful to use a debug loop. But beware: If only the VIM Solutions Beyond Invoice Invoices solution is used in the system, but not the packages for invoice processing, a custom debug table in the style of /opt/cp_debug must be created.
ABAP METHOD /otx/pf04_if_data_enrich_ex~data_enrich_logic. * Optional: Debug loop DATA: ls_plh TYPE […]_plh, ” header table lt_pli TYPE TABLE OF […]_pli, ” line item table ls_msg TYPE bapiret2. FIELD-SYMBOLS: <fs_pli> TYPE […]_pli. ” line item table lt_pli = pct_item. * ls_plh = pcs_head. pe_success = ‘X’. LOOP AT lt_pli ASSIGNING <fs_pli>. […] ENDLOOP. IF pe_success = ‘X’. * pcs_head = ls_plh. ” update header information pct_item[] = lt_pli[]. ” update item information ENDIF. ENDMETHOD.
```
  METHOD /otx/pf04_if_data_enrich_ex~data_enrich_logic.

* Optional: Debug loop

    DATA: ls_plh TYPE [...]_plh, " header table
          lt_pli TYPE TABLE OF [...]_pli, " line item table
          ls_msg TYPE bapiret2.

    FIELD-SYMBOLS:  TYPE [...]_pli. " line item table

    lt_pli = pct_item.
*   ls_plh = pcs_head.

    pe_success = 'X'. 

    LOOP AT lt_pli ASSIGNING .
      [...]
    ENDLOOP.

    IF pe_success = 'X'.
*     pcs_head = ls_plh. " update header information
      pct_item[] = lt_pli[]. " update item information
    ENDIF.

  ENDMETHOD.
```
Whenever data is changed, I recommend issuing a helpful and transparent message to users so that they know what has been changed and why. Here is an example of what such a message could look like in the code. You can of course also assemble the messages (ls_msg) manually, but I find the option mentioned here easier to read.
ABAPDATA ls_msg TYPE bapiret2. ” […] CALL METHOD /otx/pf02_cl_error_message=>message_return_build EXPORTING pi_type = ‘S’ ” “S” = Success / “E” = Error / “I” = Info pi_cl = ‘Z…’ ” name of your message class pi_number = 019 ” your message number. pi_par1 = ” message parameter 1 pi_par2 = ” message parameter … ” […] IMPORTING pes_return = ls_msg. APPEND ls_msg TO pet_return.
```
DATA ls_msg TYPE bapiret2.

" [...]

CALL METHOD /otx/pf02_cl_error_message=>message_return_build
  EXPORTING
    pi_type    = 'S' " "S" = Success / "E" = Error / "I" = Info
    pi_cl      = 'Z...' " name of your message class
    pi_number  = 019  " your message number.
    pi_par1    = " message parameter 1
    pi_par2    = " message parameter ...
    " [...]
  IMPORTING
    pes_return = ls_msg.
    
  APPEND ls_msg TO pet_return.
```
Customizing for a SAP VIM Solutions Beyond Invoice Data Enrichment

Now we have created the class for our data enrichment and still have to create the corresponding customising, which can be done very quickly in the transaction /otx/pf00_img.
```
/otx/pf00_img
```
Navigate to Process Configuration > Profiles:

Select your Profile Configuration and navigate to the corresponding Version Definition and then Data Enrichment Configuration. Here you can now create a Data Enrichment ID with a speaking name and description.

The enrichment point decides when a data enrichment should be executed. For my example I select ALL to execute it at all enrichment points.

Even if a data enrichment should only run at the beginning of the process, I like to use ALL at the beginning of my implementation because the jump to the debugger is super quick. Simply set a breakpoint in the class, execute the Enrich Data action and you are already in the ABAP Debugger and can analyse if everything is working according to plan.

The last step is often forgotten in data enrichments because it was not necessary in earlier versions. The newly created Data Enrichment ID must still be assigned to the corresponding Characteristics Configuration and given a sequence.

I have created a data enrichment but it is not working

If your data enrichment does not work, please check the following points:
- Is the success marker pe_success returned with true (‘X’)?
- Is the newly created Data Enrichment Configuration active? There is a checkbox on the far right which can easily be overlooked.
- Have you perhaps overlooked the last point Assign Data Enrichments?
- Perhaps your debug loop can help you here? If this is not activated, this can also be a finding.
Conclusion

When using SAP VIM Solutions Beyond Invoice, there is no getting round the use of data enrichments. Only with these can the process be properly tidied up and optimised.

Don’t forget to issue transparent and helpful messages for the users and make sure that the data enrichments run in a sensible sequence.

I wish you every success with the implementation!
February 8, 2025
Never forget this step before activating Business Configuration Sets (BC-Sets) for OpenText Vendor Invoice Management for SAP Solutions (SAP VIM) upgrade in SCPR20

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’s official documentation.
When upgrading or installing OpenText Vendor Invoice Management for SAP Solutions (SAP VIM), it is often necessary to activate so-called BC Sets (Business Configuration Sets). A BC Set (Business Configuration Set) in SAP is a tool that allows users to store, manage, and transport configuration settings efficiently. It acts as a template for predefined customizing settings that can be applied to an SAP system, ensuring consistency and reducing manual effort in system configuration.

Check all the available documentation before starting with the activation

Compiling a list of the necessary BC Sets and activating them in the correct order can be challenging, especially given the current state of the VIM documentation.

To ensure a smooth process, it is essential to not only refer to the Installation Guide but also carefully review the Configuration Guides and Release Notes. Also refer to the documentation for all service packs included in the upgrade, not only the latest one.

Never forget to export the table comparison

One of the most critical steps when performing an upgrade—especially in complex SAP environments—is to conduct a thorough comparison between the BC Set and the existing table contents before activation. This step ensures that no essential configurations are overwritten, lost, or modified unexpectedly, which could lead to system inconsistencies or functional disruptions.

During an upgrade, new BC Sets introduced by OpenText may contain updated settings that enhance functionalities or align with new system requirements. However, they may also overwrite existing custom configurations, potentially impacting workflows, document processing, or approval rules. A careful comparison allows you to identify discrepancies, retain necessary custom settings, and selectively adopt only the relevant changes.

To prevent accidental data loss, it is highly recommended to create a complete backup of the table contents before making any modifications. This backup acts as a safety net, allowing you to restore previous configurations if unexpected issues arise during or after the activation of new BC Sets.

Taking the time to perform this verification process not only safeguards critical system settings but also minimizes downtime and troubleshooting efforts in case of unintended changes. In the following section, we will go through the exact steps to compare BC Sets with table contents and securely back up configurations before proceeding with the upgrade.

Exporting the SCPR20 table comparison to .html (without cutting off important tables by mistake)

Entering the comparison in SCPR is easy by clicking on the button below:

The displayed list usually shows you all the data which is different (yellow) or new (green).

In general, the export of the table comparison is often forgotten. However, if the export is carried out, there is another pitfall that should not be overlooked, otherwise data may be lost. We have to go into the output options for this.

The output width is set to 150 by default, increase the number to 800. if tables, labels and content exceed 150 characters, they will otherwise be cut off and important information may be lost. Please also check whether 800 is sufficient here, I have not noticed any data loss in the exported files with this number. Do not change anything else in these settings.

Now that we have prevented the file from being truncated, we can continue with the export. To do this, we go to List, Save/send and then to File.

I prefer to save the comparison files as .html. This is small, clear and universally applicable. In addition, I don’t have to worry about Microsoft Excel versions and separators.

For the file name I recommend using the BC Set name with “/” replaced by “_”. Also creating a folder per service pack level does help to keep the overview. I also recommend to replace the suggested .htm with .html. At least on my computer this helps with directly opening in my browser on double click.

The export gives you a .html file which is lightweight and provides a very good overview. I recommend storing all the BC-Set comparisons together with your documentation. This is applicable for every single BC-Set in every service pack level.

If you have paid very close attention, you will notice that in the screenshot above the BC sets of VIM 7.6 SP 5 are compared with the table contents of VIM 7.6 SP 6. This is of course not a realistic scenario and the BC sets should never be activated as shown in the comparison.
One of the main reasons I prefer using .html as an export format is that it allows for seamless copying and pasting into Excel while preserving the structure and formatting of the data. Unlike plain text or CSV files, which may require additional adjustments, HTML tables often retain proper column alignment, making the data immediately usable for further processing, analysis, or reporting in Excel. This method helps avoid common issues like misaligned columns, missing delimiters, or incorrect data types, ensuring a smooth workflow when handling exported information.

Conclusion

This may seem like a lot of effort, but failing to carefully verify BC Sets before activation can lead to serious issues. If a BC Set overwrites an important configuration, and you only realize it after deploying transport requests into the production system, it becomes extremely difficult to trace back what was changed and when. At that point, identifying the root cause of the issue can be time-consuming and complex, often requiring manual comparisons, system rollbacks, or troubleshooting unexpected system behavior. Taking the time to perform a thorough review and backup beforehand can save countless hours of debugging and help avoid disruptions in critical business processes.

With that in mind, I hope this guide helps make your VIM upgrade process smoother and more efficient. Wishing you great success with your upgrade.

January 31, 2025
Using ABAP Debug Loops in OpenText Vendor Invoice Management for SAP Solutions (SAP VIM)
When analysing problems in OpenText Vendor Invoice Management for SAP Solutions (SAP VIM), depending on the system architecture and authorisations, there are parts of the source code that are very difficult to access with the ABAP debugger. This is the case, for example, with data enrichments (e.g. logical modules) executed by a background user at the start of the process.

A debug loop is an endless loop in the code which you can activate when required. The infinite loop allows you to find and debug the running code in the process monitor.

Adding a debug loop to your ABAP code

In order to be able to use a debug loop, it is first necessary for it to exist. This is the case in many parts of the product standard, but should not be forgotten in custom developments either. A debug loop can look like this, for example:
ABAP
```
DO.  

  SELECT SINGLE value 
  FROM /opt/cp_debug 
  INTO @DATA(lv_debug) 
  WHERE debugarea = 'Z_LOGIC_MODULE'.  " keep text below 20 chars
    
  IF lv_debug IS INITIAL.  
    EXIT.  
  ENDIF. 
     
ENDDO.  
```
Activating a debug loop using the ABAP Editor SE38

The table /opt/cp_debug has some advantages over self-built tables. It is used in the product standard and the loop can be activated and deactivated with the ABAP Editor (SE38) using the program /OPT/VIM_DEBUG.

If a debugging area is activated, the system remains in an infinite loop until it is deactivated again or until the infinite loop is exited manually in the debugger.

But be careful, the debug loop runs for all users on the system, so this tool should only be used with caution. In the production system only in absolutely exceptional cases and only for a short time in consultation with the system supervisor.

Some consultants even comment out the coding for debug loops before productive operation, but I find that the possibility of debugging in the P system can be a great advantage for tracking down tricky errors.

Tip: As you often spend a long time in the code when debugging, I suggest that the debugging loop is always exited via /OPT/VIM_DEBUG. This way you cannot forget to deactivate the loop.

Starting the debugger in Work process overview (SM50)

If your debug loop is active, you are ready to go: Provoke the system to run the loop, for example by processing a new document.

As soon as the corresponding line in the source code is run through, the process stops and we have the opportunity to jump to the debugger, for which we use the transaction code SM50.

To make it easy to find our process, we switch to the Active Work Processes view.

If you cannot find your process, have a look at the System-Wide List. The process you are looking for may be running on a different application server.

Now we can select our process and start it via Administration > Program > Debugging in the ABAP Debugger and eliminate the error.

Do you have any tips or best practices for dealing with debug loops in ABAP? Let us know in the comments!
January 25, 2025