30-Min-Call DE
SAP VIM customizing



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

Category: Documentation

  • What is Smart Coding and how can I use it in SAP VIM?

    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!

    blank
    blank

    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.

    blank

    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.

    blank

    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:

    blank
    blank

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

    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:

    blank

    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.

  • Let’s Make History! Enabling the SAP VIM Workflow History Log

    Let’s Make History! Enabling the SAP VIM Workflow History Log

    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.

    When working with OpenText Vendor Invoice Management (VIM) for SAP, one of the most overlooked yet powerful features is the Workflow History PDF Log. This capability automatically generates a comprehensive PDF at the conclusion of the VIM process—capturing every key detail, from process milestones and approvals to workflow logs and user comments.

    This isn’t just a convenience for auditors or a checkbox for compliance. It’s a transparent, time-stamped audit trail that gives AP managers and business users immediate visibility into how an invoice was handled. What’s more, the history log is securely archived and linked to both the DP document and the SAP invoice—so it’s always accessible and never lost.

    blank

    Benefits of the Workflow History PDF

    • Audit-ready: A single document with all approvals, comments, and workflow steps.
    • Transparency: Clear visibility into who did what and when.
    • Compliance: Securely archived and linked to the invoice for future reference.
    • Flexibility: Can be customized to include company-specific information.
    blank

    How to Set It Up

    You configure the PDF history log within a profile which describes all settings for the creation of the PDF history log. You assign this profile to a OpenText VIM for SAP process step.


    You must specify that the PDF history log will be created at the end of the OpenText VIM for SAP process. To enable the creation of the PDF history log, you must assign the profile for the PDF history log (default profile: HISTORY) to the OpenText VIM for SAP process “VIM process is finished”. Without this, the PDF history log will not be created at the end of the OpenText VIM for SAP process.

    1) Define the profile for the PDF History Log

    Run the /n/OPT/SPRO transaction and navigate to OpenText Vendor Invoice Management Invoice Solution > Cross Component Configuration > PDF Log >Maintain Customizing Profiles.

    blank

    The PDF profile ‘HISTORY‘ is delivered with the baseline. You can either customize it or create your own custom profile.

    blank
    blank

    In the Define Profiles screen, you will find the following parameters that are specific for the PDF history log:

    PDF Log Class
    The complete logic of the PDF history log is included in the PDF log class /OPT/CL_C_PDF_LOG, which is delivered with the baseline. You can enhance the class by redefining components of the class within a custom class, which you can maintain instead of the baseline class.

    PDF Form Type
    Enter the type of the PDF form.

    Currently, Smart Forms is the only available entry for this field. However, it is also possible to redefine the logic of the PDF log class /OPT/CL_C_PDF_LOG within a custom class to support other techniques, for example SAP Interactive Forms.

    Default value: Smart Forms

    Form Name
    Enter the name of the SAP Smart Forms form.
    Baseline delivery includes a Smart Form /OPT/C_WORKFLOW_HISTORY01. You can copy the Smart Form using the smartforms transaction and adjust it to
    your needs. You can maintain this adjusted Smart Form in the Form Name box instead of the baseline Smart Form. The baseline Smart Form uses the SAP Smart Style /OPT/C_SF_STYLE01 for the format options of the Smart Form, for example the font and the font size of headers or default paragraphs. You can copy the Smart Style using the smartstyles transaction and adjust it to your needs. Additionally, copy the Smart Form and maintain your new Smart Style in the Output Options tab of the Form Attributes screen of the Smart Form.

    Document type
    Enter the archive document type to be used for archiving the PDF history log. Within baseline, the archive document type /OPT/PDF is delivered (we suggest that you create your own archive link document type for this).

    You must link the archive document type to the OpenText VIM for SAP Business Object and to SAP Business Objects (in case it’s not already linked by default, you can link the document type ‘/OPT/PDF’ to object types ‘/OPT/V1001’ and ‘BKPF’ via transaction OAC3).

    Overwrite
    Select this check box to overwrite PDF history logs that have already been linked to the DP document and its SAP invoice with the same archive document type.
    It is possible to create a PDF history log to a DP document manually by using the /OPT/CR_PDF_LOG report. When using this report, a PDF history log linked to the DP document and its SAP invoice can already exist.

    Selecting the Overwrite check box deletes the physical PDF document (the PDF history log) and its links to the DP document and the SAP invoice. This PDF history log can either be created manually or automatically.
    Default value:

    2) Assigning the profile to a OpenText VIM for SAP process step

    To create this PDF history log at the end of the OpenText VIM for SAP process, you must assign the profile to the VIM process is finished process step for your company codes. If you leave Company Code empty, the setting is used for all
    company codes.

    blank

    By setting up the Workflow History PDF log, you create a single source of truth for your invoice processes. With just a few configuration steps, your organization gains audit-ready documentation, transparent tracking of every approval and action, and a secure archive that is always accessible.

    Whether for compliance, audit preparation, or day-to-day process insight, the Workflow History PDF log ensures that your AP processes are not only more transparent but also more reliable and future-proof.

  • 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.
    blank

    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.