OpenText VIM e Invoicing

OpenText™ Vendor Invoice Management for SAP® Solutions
OpenText™ Vendor Invoice Management

for SAP® Solutions
White Paper
e-Invoicing
Document Version: 2020-09-14
www.opentext.com/contact
Copyright © 2018 Open Text SA or Open Text ULC (in Canada).
All rights reserved. Trademarks owned by Open Text SA or Open Text ULC (in Canada).
The Information Company™
Contents
1 Introduction ...................................................................................................... 4
2 Country specific notes .................................................................................... 4
2.1 Italy - FatturaPA ......................................................................................... 4
2.2 Germany - XRechnung .............................................................................. 6
2.3 Generic UBL format and delivery networks ............................................... 6
3 Installation ........................................................................................................ 7
3.1 General package for electronic invoices .................................................... 7
3.2 Integration with SAP Document Compliance – BC Inbound ................... 10
3.2.1 Prerequisites .................................................................................. 10
3.2.2 Installation ..................................................................................... 12
3.3 Integration with SAP Document Compliance – VIM 7.5 IDH ................... 12
3.3.1 Prerequisites .................................................................................. 12
3.3.2 Installation ..................................................................................... 13
4 Integration with SAP Document Compliance ............................................. 13
5 Configuration ................................................................................................. 15
5.1 Provided Baseline Configuration ............................................................. 16
5.1.1 Archive Link sample configuration ................................................. 16
5.1.2 Business Center Inbound .............................................................. 16
5.1.3 VIM Configuration .......................................................................... 17
5.1.4 XML specific processing configuration .......................................... 18
5.2 Additional Required Configuration ........................................................... 23
5.2.1 BC Inbound .................................................................................... 23
5.2.2 HTML Visualization of FatturaPA .................................................. 23
5.2.3 HTML Visualization of XRechnung ................................................ 24
5.2.4 Plug-In configuration for XML visualization ................................... 25
5.3 Optional Configuration ............................................................................. 26
5.4 Special mapping logic .............................................................................. 27
5.5 Integration with SAP Document Compliance – General Configuration ... 27

6 Quick start ...................................................................................................... 30
6.1 OAWD upload with BC inbound .............................................................. 30
6.2 Email with BC inbound ............................................................................. 32
6.3 Email with VIM IDH (VIM 7.5 only) .......................................................... 33
7 Generic Peppol/UBL mapping ...................................................................... 38
7.1 XML Mapping ........................................................................................... 38
7.2 Enhancing the Transformation ................................................................ 42
8 Additional patches ......................................................................................... 46
8.1 Mapping of purchase unit of measure ..................................................... 46
8.2 Long values in input XML ........................................................................ 46
8.3 XML transformation of XRechnung files (Germany) ................................ 47
8.4 Handling of attachments .......................................................................... 47
9 Known Issues ................................................................................................. 47
9.1 Mapping of date fields.............................................................................. 47
10 About OpenText ............................................................................................. 48
1 Introduction
Electronic invoicing is gaining more and more acceptance and is even becoming
mandatory in many countries. VIM provided support for electronic invoices in Brazil for
few years now (see VIM Scenario Guide, section “Scenarios for special countries –
Brazil"). With more countries establishing their own or building on general international
standards of e-invoicing, VIM is introducing new modules to support the process.
The new features include processing modules and configuration based on Business
Center Inbound that allows starting VIM process with Early Archiving (OAWD file upload)
or E-Mail. Existing VIM 7.5 customers who upgraded from VIM 7.0 and using VIM
Incoming Document Handler framework (IDH) will be able to use new IDH modules to
start VIM process.
An option to integrate with SAP Document Compliance Solution is also provided by

OpenText. This allows the process to be fully automated and supports feedback functions
required by country standards like Italian FatturaPA. More details on the provided
functions are provided further in this document.
The integration with SAP Document Compliance is supported for BC Inbound and VIM
7.5 IDH scenario.
2 Country specific notes

This section provides country specific information, including installation notes for special
deliveries. Such deliveries allow to implement e-invoice processing with VIM by importing
a set of transports provided by Open Text outside of normal support package cycle.
Note that the configuration steps are provided in a separate general section further in the
document. They will list country specific object names where applicable.
2.1 Italy - FatturaPA

Starting 1st of January 2019, electronic invoicing (e-invoicing) will become mandatory for
all B2B supplies of goods and services between parties established or VAT-registered in
Italy.
E-invoice process is using the Exchange System ‘Sistema di Interscambio’ (SDI), which
will allow the Italian Revenue Agency to collect details of e-invoices. The invoices must
be transmitted in the format of Fattura PA, as defined by the Italian government.
Overview of the process:
Notes:
• The interaction with government system (connectivity / middleware) is outside of

scope of the support provided in Vendor Invoice Management by OpenText.
The current delivery provides the support for starting VIM process by uploading the XML
files with the Early Archiving (transaction OAWD) or Email – with BC Inbound, or with
Email – with VIM IDH. Such XML files can be received from SDI by several ways
supported by the process, like E-mail, sFTP, or through the SAP eDocument cockpit.
Integration with SAP Document Compliance is supported for automation of the process.
The following scenarios are currently supported by VIM with e-invoicing for Italy:
• PO based goods invoices
• NON-PO invoices
• Invoice attachments (such as PDFs) are supported with BC Inbound
VIM currently supports only one invoice per XML file. Invoices signed through Aruba PEC
are not supported directly – pure FatturaPA XML must first be extracted from the signed
message and then uploaded into BC Inbound, or the integration with SAP Document
Compliance must be used, which provides extracted XML files for VIM.
Multiple invoices sent in one XML file are not supported.
XML invoice visualization in HTML format can be implemented using the stylesheet
provided by the Italian Revenue Agency. The stylesheet must be modified to make it work
with VIM modules. The instructions are provided in the section “Additional Required
Configuration” further in this document.
2.2 Germany - XRechnung

German regulation for electronic invoicing (E-Rech-VO) mandates that in the future all
public sector institutions will support incoming invoices in the electronic form. The support
will be implemented step by step at different levels. The corresponding standard of the
electronic invoices, XRechnung, is developed by the Coordination Council for IT
Standards (KoSIT). XRechnung format is based on two different XML schemas, UBL and
UN/CEFACT. UBL support is provided since April 2019 (and VIM 7.5 SP9, VIM 16.3.3).
UN/CEFACT support is provided since April 2020 (and VIM 7.5 SP11, VIM 16.3.5).
The current delivery provides the support for starting VIM process by uploading XML files
with Early Archiving (transaction OAWD) or Email - with BC Inbound, or with Email – with
VIM IDH.
Both PO based and non-PO scenarios are supported. Invoice attachments (such as
PDFs) are supported with BC Inbound.
An example of transformation for XML invoice visualization is provided as a separate

download. That example transformation is currently not covered by standard product
support. The setup of the transformation is described later in this document.
2.3 Generic UBL format and delivery networks

Open Text will release generic UBL mappings with VIM 7.5 SP10 / VIM 16.3.4, to support
more countries. An update to transport based delivery for VIM 7.5 is available for
download at Open Text MySupport as patch01.
UBL based invoices delivered through PEPPOL network are contained within a
UN/CEFACT envelope (“Standard Business Document Header”). Such invoices must be
transferred through SAP Document Compliance that extracts the actual UBL from the
envelope. In case you are not using SAP Document Compliance, such extraction must be
implemented as a project specific extension, because VIM supports pure UBL files and
does not support UN/CEFACT envelope.
Countries supported for generic UBL format.
1) Netherlands.
2) Belgium
3 Installation
3.1 General package for electronic invoices
Support for processing electronic invoices is delivered with VIM support packages as
listed per country in the table below. Check the corresponding release notes for additional
requirements.
Country VIM SP Transport delivery

Italy, FatturaPA 7.5 SP9 / VIM 16.3 SP3 yes
Germany, XRechnung (UBL) 7.5 SP9 / VIM 16.3 SP3 yes
Generic (UBL) 7.5 SP10 / VIM 16.3 SP4 yes

UN-CEFACT Version 1 7.5 SP11 / VIM 16.3 SP5 yes
UN-CEFACT Version 2 7.5 SP11 / VIM 16.3 SP5 yes

(including XRechnung in
CEFACT format)
Transport based deliveries are provided today at Open Text MySupport. The important
difference is that apart from product status tracking, support packages provide
configuration as BC sets, allowing selective activation. Configuration transports can be
installed only completely.
Open Text recommends that you implement the e-Invoicing support by upgrading to VIM
7.5 SP9 or VIM 16.3.3 and optionally installing the SAP Document Compliance
integration component (OTBCSL38) as described below.
The minimum supported VIM release and SP levels for the transport deliveries are VIM
7.5 SP7 with OpenText Business Center (BC) 16.3 update 1, and VIM 16.3 with Business
Center 16.3.
Note
Manual modification steps will need to be performed on VIM 7.5 SP7, VIM 16.3 and VIM
16.3 SP1 after the import of the transports, as described at the end of this section.
The transport delivery files are located in the following folder on Open Text MySupport:
https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=76775470
The same location can be reached by navigating to Resources > Patches >Vendor
Invoice Management>Vendor Invoice Management – E-invoicing.
The downloads are organized according to the scenario, Business Center Inbound or IDH
(VIM 7.5 only).
VIM 7.5 with BC Inbound
File name: vim-7.5-e-invoicing-bc.zip
Transports:
D9PK902778 – Workbench objects
D9PK902783 – Customizing objects
VIM 7.5 with BC inbound for generic UBL
File name: vim-7.5-e-invoicing-bc-patch01.zip
Transports:
D64K900474 Workbench objects
D64K900475 Customizing objects
VIM 7.5 with BC inbound for UN-CEFACT
Transports:
DM1K900310 Workbench objects
DM1K900311 Customizing objects
VIM 16.3 with BC Inbound
File name: vim-16.3-e-invoicing-bc.zip
Transports:
D02K902488 – Workbench objects
D02K902493 – Customizing objects
VIM 16.3 with BC Inbound for generic UBL
Transports:
VIM 16.3 with BC Inbound for UN-CEFACT
File name: vim-16.3-e-invoicing-bc-patch02-v2.zip
Transports:
VIM 7.5 with IDH
File name: vim-7.5-e-invoicing-idh.zip
Transports:
D9PK902777 – Workbench objects
D9PK902784 – Customizing objects
VIM 7.5 SP7, VIM 16.3 and VIM 16.3 SP1 – Manual modifications after the import.
Several function modules in the delivery contain calls to security check modules that are
delivered with later VIM SPs than mentioned above. To ensure package integrity, the
unified deliveries are produced for all supported SPs. This requires few simple manual
modifications for older SP levels:
Perform the same modification in the function modules listed below (transaction SE37):
/OPT/VIM_DATE_CONVERSION
/OPT/VIM_GET_EDOC_DATA
/OPT/VIM_EXIT_MAP_ENH_FATRURA
/OPT/VIM_EXIT_MAP_ENH_RECHNUNG
/OPT/VIM_EXIT_MAP_ENH_UBL
Delete or comment out the following three lines at the beginning of the function module:
IF /opt/vim_auth_check=>check_rfc( ) <> 0.
EXIT.
ENDIF.
3.2 Integration with SAP Document

Compliance – BC Inbound
3.2.1 Prerequisites
The objects for integration with SAP Document Compliance are delivered as a new
component OTBCSL38. Before the installation, make sure that you installed and
configured the prerequisites. The component OTBCSL38 requires Business Center
Inbound, which is provided as the component OTBCSL03 with VIM 7.5 and included
directly into VIM 16.3. In both cases, you need to install Business Center core
components. For more information, see VIM and Business Center release notes and
installation guides.
The table below lists the SAP notes to be implemented for specific scenarios. It assumes
that you have already installed and configured SAP Document Compliance / eDocument
Framework. Note that the most current list of the notes can be found in SAP
documentation and support documents.
Note Scenario
2777052 eDocument: Prerequisites for SAP Note 2765690 General
2765690 eDocument Framework (21) General
2771424 eDocument Italy: Enhancements for Incoming Invoices Italy
2690949 - eDocument Germany - EU eInvoicing: Overview Note Germany
2690993 - eDocument Germany - EU eInvoicing: Prerequisite for SAP Note 2613785 Germany
2613785 - eDocument Germany - EU eInvoicing Germany
2690958 - eDocument Germany - EU eInvoicing: Configuration and Customizing Germany
2805582 - eDocument Germany - EU eInvoicing: Corrections Germany
2618098 - eDocument EU: Prerequisite for SAP Note 2523477 General/PEPPOL
2523477 - eDocument EU: eInvoice General/PEPPOL
2432169 - eDocument EU: ABAP Proxy Objects General/PEPPOL
2433472 - eDocument EU: Prerequisite for SAP Note 2390901 General/PEPPOL
2390901 - eDocument EU: AIF Implementation General/PEPPOL
2440686 - eDocument EU: AIF Customizing General/PEPPOL
2442063 - eDocument EU: AIF Setup General/PEPPOL
2778717 - eDocument EU: AIF Interface Connector Implementation General/PEPPOL
2783795 - eDocument EU PEPPOL: Installation Overview General/PEPPOL
2813297 - eDocument EU: Prerequisites for SAP Note 2805188 General/PEPPOL
2805188 - eDocument EU: eInvoice Corrections General/PEPPOL
2423423 - eDocument Netherlands - EU eInvoicing: Prereq. for SAP Note 2438748 Netherlands
2438748 - eDocument Netherlands - EU eInvoicing Netherlands
2420449 - eDocument Netherlands - EU eInvoicing: Configuration and Customizing Netherlands
2819556 - eDocument Netherlands: Enablement for Push Scenario Netherlands
2805560 - eDocument Netherlands - EU eInvoicing: Corrections Netherlands
For electronic invoices delivered over PEPPOL (Germany, Netherlands), also implement
the notes marked as “General/PEPPOL”.
3.2.2 Installation
In case you purchased VIM through SAP, you will be able to download the installation
package from SAP Marketplace. In case you purchased VIM directly from Open Text,
install the component OTBCSL38 using the SAINT transaction or with other tools like
SAP Maintenance Planner.
PAT file name: Q020020776277_0000140.PAT

Password: 8C87CF35A7
Activate the BC set /OTBCSL38/EDOCU_INTEGRATION_SAP.
Implement the manual corrections mentioned in the section Known Issues further in this
document, if applicable to your VIM SP level.
To enable ACCEPT/REJECT feedback messages, some changes are required in VIM

core modules. The changes will be included into VIM 7.5 SP10 and VIM 16.3.4. For
customers running older SPs, the changes are delivered as manual correction
instructions:
https://mimage.opentext.com/support/ecm/secure/patches/vim/oneoff/VIMI-
22539/vim_7.5_sp10_vimi-22539_ci-25.pdf
A mandatory update for the component OTBCSL38 is available for download as patch
01.
File name: OTBCSL38-patch01.zip
Transports:
The changes included into this patch will be delivered in the next support package for the
component.

Compliance – VIM 7.5 IDH
3.3.1 Prerequisites
In case of VIM 7.5 Incoming Document Handler (IDH), the objects for integration with
SAP Document Compliance are delivered as a transport at Open Text MySupport. Before
the installation, make sure that you installed and configured the prerequisites. Those are
the actual SAP Document Compliance module along with general and country specific
SAP Notes. The same notes apply as listed in the table found in the previous chapter.
The provided transport is an addition to the general e-Invoice support provided for VIM
7.5. Make sure you have installed and configured that as described in the earlier
chapters.
3.3.2 Installation
Download and import the transport D5EK900398.
4 Integration with SAP Document

Compliance
Open Text provides the following functions to integrate VIM with SAP Document
Compliance:
• Implementation of the BADI ES_EDOC_INCOMING to start VIM processing and

to provide navigation from eDocument cockpit into VIM.
• Navigation from VIM Analytics into eDocument cockpit
• Feedback (result, response) functions like ACCEPT or REJECT
After implementing SAP notes required for specific country scenarios and installing the
component OTBCSL38 or the transport provided for VIM 7.5 IDH, VIM process can be
started using electronic invoices that arrived into SAP eDocument environment.
A manual start is possible by selecting a document in the eDocument cockpit and clicking
the button “Create Incoming Invoice”.
To start VIM process automatically for currently available eDocuments, schedule the
report EDOC_BACKGROUND to run with eDocument Process corresponding to country
scenario (e.g. ITINVIN for Italy) and eDocument Action INCOM_AUTO.
For eDocuments sent into VIM, you can navigate from eDocument cockpit into VIM
Analytics or into BC Workplace depending on the processing step of the document. Note
that navigation into BC Workplace is not possible for one specific document. To help you
to find the corresponding registration ID, the ID will be shown in a popup when switching
transactions.
After the start of VIM workflow, a navigation hotspot will be shown in VIM Analytics if the
corresponding column is enabled:
Note: this navigation function is provided with VIM 7.5 SP10 and VIM 16.3.4.
Feedback functions are executed in the following way:
Accept – sent when an invoice is posted or parked successfully. For the case when
invoices are first parked, or posted with a payment block, it can be configured whether the
message will be sent upon parking/posting or only once the invoice is posted without
payment block or released. The customizing view /OPT/V_EDOC2_ACT is used for that.
Reject – sent when an invoice is rejected from BC Workplace, confirmed as a duplicate,

set to Obsolete status or when the standard Return to Vendor function is executed.
Note: when Return to Vendor function is executed, no email will be sent to vendor,
because the email will be generated by SAP eDocument framework if needed.
Additionally, the feedback functions are used to send the vendor determined by VIM into
eDocument framework, to be used to restrict access to documents based on Data Privacy
and Protection settings.
The database table /OPT/EDOC2_REG is used to store the link between the eDocument
and VIM objects. To delete older entries from the table, Open Text provides a report,
/OPT/EDOC2_DATA_CLEANUP.
Selection screen parameters:
Till date – use this to delete all entries for eDocuments that were created on or before the
specified date.
Force cleanup – use this option to delete all existing entries
Note that with entries deleted from the table, navigation and feedback functions are not
possible anymore. Therefore, only old entries for completely processed documents must
be deleted.
5 Configuration
The important configuration, most of which is not project specific, is provided by Open
Text. Along with this, sample Archive Link settings are also provided. That allows to
quickly set up inbound XML invoice processing through manual upload in Early Archiving
(transaction OAWD).
Note: For a description of minimal steps needed to achieve a completely working

solution, see the section “Quick start”.
OpenText recommends verifying that the provided settings do not introduce any conflicts
with the existing project specific configuration.
5.1 Provided Baseline Configuration

5.1.1 Archive Link sample configuration
Open Text provides sample configuration for two archiving document types:
/OPT/FATRA - Italy, FatturaPA
/OPT/RECHN - Germany, XRechnung
/OPT/UBL- Generic UBL format
5.1.2 Business Center Inbound

Channels
Two channel definitions are provided:
OAWD_FATRA VIM - Italian FatturaPA solution
OAWD_RECHN VIM - German XRechnung solution
OAWD_UBL VIM – Generic UBL solution
NOTE: These channels must be named identically with VIM input channels described
further in the document.
Document Handler definitions
Two handler definitions are provided:
PS03OFATRA - Italian FatturaPA solution
PS03RECHN – German XRechnung solution
PS03UBL- Generic UBL solution
The steps provided for handlers are:
REG_VIM – Register inbound document in VIM
IMG_ATUDF – Convert XML into HTML format and attach it to the BC Inbound
object. This step Currently provided only for Italian solution. The name of the
stylesheet used for transformation have to be maintained in the configuration
entry.
GETCONT – Store attached XML file in a database table of BC Inbound for later
use.
PARSEXML - Parse the XML input and store the parsed values in a database
table of BC Inbound.
IMG_ARCH - Archive any embedded attachments found in the XML input file.
IMG_LINK - Link the archived documents to BC registration object.
PROCESSING - Finalize BC Inbound process before starting VIM workflow.
BC Inbound Registration – Early Archiving
Entries are provided for following sample archiving document types:
/OPT/FATRA
/OPT/RECHN
/OPT/UBL
If different document types are used, create the corresponding entries by using the
provided ones as example.
5.1.3 VIM Configuration

Channels
The following predefined channels are delivered:
OAWD_FATRA – Italian FatturaPA solution
OAWD_RECHN – German XRechnung solution
OAWD_UBL – Generic UBL solution
All channels are using respective country specific mappings listed below.
Mapping definitions
The following predefined mappings are delivered:
XML_FATURA - Italian FatturaPA solution
XML_RECHN - German XRechnung solution
XML_UBL – Generic UBL solution
CEFACT - CEFACT XML Mapping

All mapping definitions provided for e-invoicing scenarios are delivered along with field
enhancement configuration maintained in the sub-node for each mapping. They provide
mapping logic implemented programmatically. This mapping logic is documented in a
separate section further in the document.
IDH Service Module definition (7.5 IDH scenario only)
The service module TRANSEDOC is provided for IDH scenario on VIM 7.5
5.1.4 XML specific processing configuration

This section describes configuration used to map the XML to VIM data. The first two
customizing activities can be done using the view cluster /OPT/XML_MAP in transaction
SM34. Individual views are also provided for each activity, as described below.
5.1.4.1 Assignment of transformations to scenarios.

XML transformations must be performed according to country specific formats. The
assignment of the transformation can be performed in the BC inbound handler definition.
In case the XML transformation name is not maintained in the step definition of the BC
Inbound handler, the transformation name will be read from the maintenance view
/OPT/XML_TRAN_HV based on the root node in the input file.
Open Text delivers entries for FatturaPA, XRechnung in UBL format, generic UBL, UN-
CEFACT version 1 and UN-CEFACT version 2 (supports XRechnung in CEFACT format).
Below you will find examples of configuring the modules for BC Inbound handler.
1) If using independent handler for each format of invoice, maintain the relevant
transformation.
For XRechnung in UBL format, maintain the transformation
/OPT/TRANS_XML_EDOC_UBL or /OPT/TRANS_XML_RECHNUNG_UBL.
For UN-CEFACT version 1, maintain /OPT/TRANS_XML_EDOC_CEFACT1

For UN-CEFACT version 2, maintain /OPT/TRANS_XML_EDOC_CEFACT
2) If using single handler for all the above transformations, no need to maintain
any transformation as shown below:
If the transformations are not maintained, then transformation names will be

picked up from the maintenance view /OPT/XML_TRAN_HV based on root node.
5.1.4.2 Mapping XML elements

The solution is using two step mapping procedure:
1. XML/External data to Semantic data model mapping.

2. Semantic data model to VIM mapping.
XML to Semantic data model mapping
Use the maintenance view /OPT/XML_MAPV to maintain the entries in the transaction
SM30.
Transformation 1 – Maintain the transformation name which is used to convert the

XML file to Semantic data model
Root Node – Maintain the root node provided in XML file
Transformation 2 – Maintain the transformation name which is used to convert the

XML file to user-friendly display format.
Generic UBL solution
UN-CEFACT Version 1 solution
UN-CEFACT Version 2 solution
Note: Semantic mapping is done for PO Goods invoices and NON-PO invoices. Service
POs mapping is not delivered with baseline.
Note: Maximum nodes depth are limited to 4.
Example: FatturaElettronicaBody-DatiGenerali-DatiTrasporto-DataOraConsegna
If the field appears to be on node hierarchy > 4, then ignore the root node (for example
Fattura Elettronica Body) and provide the remaining path. Make sure the external field
name is unique.
Two new fields in the mapping were introduced with the patch of April 2020 (included into
VIM 7.5 SP11 and VIM 16.3.5):
1) Field Value
2) Node Level
Sometimes the same node combination represents two different field values that must be
mapped into different target fields. The new fields can be used to differentiate based on
adjacent XML node.
Example:
➢ The following node combination represents two different fields those are
Seller/Vendor VAT number and Seller/Vendor Tax number (different target
names in VIM document header).
“AccountingSupplierParty-Party-PartyTaxScheme-CompanyID"
➢ The content can be mapped differently based on the adjacent XML node. If the
adjacent node value is ‘VAT’ then the field value is VAT number. If it is space
then it is TAX number. To implement such mapping, maintain the field value and
node level as shown below.
Semantic data model to VIM mapping.
The second step is performed with provided VIM mappings maintained in the respective
channels. (XML_FATURA, XML_RECHN etc.)
5.1.4.3 Mapping of Country specific codes to SAP codes

Country specific e-Documents can use different codes to pass information important for
further processing. For example, suppliers can tell buyers their preferred payment
method. Values for such data are normally established by specific e-Document format
and are not known to target systems where invoices are processed. To support the
mapping of such data to values that can be used in the processing system, a mapping
table is provided, /OPT/EDOC_CODES.The language specific text for codes can be
maintained in the table /OPT/CODES_TEXT.
The delivery includes values used for FatturaPA processing. Examples:
Document type
TD01 Invoice – SAP document type is RE
TD04 Credit note - SAP document type is KG
Payment method
MP02 Cheque – SAP payment method is A
MP05 Bank transfer – SAP Payment method is C
5.2 Additional Required Configuration

5.2.1 BC Inbound
Basic settings
Archive ID for XML – set the repository name according to your archiving system
5.2.2 HTML Visualization of FatturaPA

To be able to view the HTML rendering of FatturaPA XML files, a stylesheet can be
downloaded from the Italian Revenue Agency. It has to be modified to make it work with
VIM modules. This section described the necessary steps.
Download the stylesheet from the Web site https://www.fatturapa.gov.it (look for “Foglio di
stile per la visualizzazionedella Fattura Ordinaria” in the Italian language area as this will
normally be the most recent version).
In the transaction STRANS, create a new transformation. The transformation name

assumed in the baseline configuration is /OPT/TRANS_FATTURA_USER_DISP. You can
create the transformation in your name space and adjust the configuration in BC Inbound
handler definition and in the maintenance view /OPT/XML_TRAN_HV. Set the
transformation type to “XSLT Program”.
Paste the complete source of the downloaded stylesheet as the transformation source.
Search for similar as following code which exists as first line in the transformation.
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" x
mlns:a="http://ivaservizi.agenziaentrate.gov.it/docs/xsd/fatture/v
1.2" version="1.1">
Replace the above code the with the following.

<?xml version="1.0"?>
<xsl:stylesheetxmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fo="http://www.w3.org/1999/XSL/Format"
xmlns:dt="serpro.sped.nfe.visualizador.fronteira.paineis.util.Formatacao"
xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:p=
"http://www.fatturapa.gov.it/sdi/fatturapa/v1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1"
xmlns:n0="http://ivaservizi.agenziaentrate.gov.it/docs/xsd/fatture/v1.2"
xmlns:prx="urn:sap.com:proxy:PRT:/1SAI/TAS47553F10FD51AA9FB178:740"
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
version="FPA12">
Search for all occurrences of the following tags
a: FatturaElettronicaorp:FatturaElettronicaor n0:FatturaElettronica
Note: “Fattura Elettronica “is a common part in the search criteria, so make sure to search
and replace with the prefixes “a:”, “p:” or “n0:”.
Replace all occurrences of above search criteria with “*”.
Example: a: FatturaElettronica/FatturaElettronicaHeader must become

*/FatturaElettronicaHeader.
Activate the transformation.
5.2.3 HTML Visualization of XRechnung

A stylesheet to visualize XRechnung XML files by converting them into HTML and
attaching the result to VIM documents can be downloaded from Open Text MySupport.
Navigate to Patches > Vendor Invoice Management > Vendor Invoice Management – E-
invoicing and download the file xr-visualization.zip.
The archive contains the following files:
xr-visualization.txt – transformation source
Apache-LICENSE – Apache license
Note
The provided source file is a modified version of the XRechnung visualization stylesheet,
originally published under Apache license terms by the Koordinierungsstelle für IT-
Standards (KoSIT). For the terms of the Apache license, see the provided file Apache-
LICENSE.
The current version is provided as an unsupported example implementation solely for the
use by Open Text customers and partners implementing VIM. As a Derivative Work, it is
not licensed under the terms of the Apache license anymore, but is subject to your
respective VIM license.
In the transaction STRANS, create a new transformation, giving a name in your

namespace. Set the transformation type to “XSLT Program”.
Paste the source code found in the file xr-visualization.txt into the source code field.
Activate the transformation.
Add a new step with the ID IMG_ATUDF into the BC Inbound handler definition (standard
is PS03RECHN for XRechnung), after the step REG_VIM:
Use the module class /OPT/VIM_ATTACH_USER_FORMAT and enter your assigned

transformation name.
With this configuration change, an HTML file will be attached to each VIM document in
addition to the original XML file. You can also use the Z-constant 005 /
MAIN_FILE_TYPE described later in this document to set the HTML file as main
document image to be displayed in all dashboards automatically.
5.2.4 Plug-In configuration for XML visualization
Plug-In Id Configuration
Proceed to the following customizing node and create a new plugin ID to display the XML
in user friendly format.
Assign Plug-In Id to Plug-In type
Proceed to the following customizing node and assign the created plug-in ID to plug-in
type.
5.3 Optional Configuration

Related VIM Z-Constants
005 / EDOC_ATTACH_HTML - archiving document type for XML visualization (HTML file,
currently only for Italy solution)
005 / PLUG_IN_OBJECTDISP – function module name for URL generation. This is used
for XML visualization. Standard value for e-invoicing solution:
/OPT/VIM_GET_ARCH_URL.
005 / MAIN_FILE_TYPE – controls the file type of the main image assigned in DP
document and posted SAP invoice. Use this if you would like to display attached files
(PDF) as main invoice image. Example value: *;PDF;HTM – will replace any original file
(normally XML) with PDF if attached, or with HTM if no PDF found.
5.4 Special mapping logic

Special mapping logic is provided for company code and vendor number determination.
This is maintained as function module for each VIM mapping delivered. Company code
and vendor number are determined based on tax numbers maintained in company code
and vendor master respectively. If a valid purchase order is found on the invoice, the
company code and vendor number will be read from the purchase order.
If needed, the provided function modules can be copied and extended to suit project
specific needs.

Compliance – General Configuration
The customizing view /OPT/V_EDOC2_ACT is used to activate the inbound processing
per Company Code, eDocument process and eDocument type. An asterisk can be
entered as company code, which will allow processing incoming documents for all
company codes, selecting the processing with the eDocument process and type.
Each combination needs to be activated with the “Active” checkbox. The external profile
is a free text field to enter an identifier that serves as a link to the registration settings of
the Business Center Inbound or VIM 7.5 IDH channel settings.
Open Text provides baseline configuration entries for processing activation. Example
entry for the processing of FatturaPA (Italy):
Additional settings:
Accept for blocked: Enable this setting if you would like to send the ACCEPT
feedback in the relevant scenarios (e.g. Italy) for invoices blocked for payment
immediately after the posting. If not enabled, the ACCEPT feedback will be sent
once the invoice is released for payment.
Accept for parked: Enable this setting if you would like to send the ACCEPT
feedback in the relevant scenarios (e.g. Italy) for parked invoices immediately
after the parking. If not enabled, the ACCEPT feedback will be sent once the
invoice is posted.
The settings in SAP Document Compliance must be adjusted to ensure that BADI
implementation provided by Open Text will be called:
In the transaction SM30, view EDOINCOMSOLDEFV, maintain the entry for OPT
automation solution as shown below:
In the transaction SM30, view EDOINCOMSOLV, maintain entries for each scenario,
company code and OPT automation solution. Below is an example for Italian invoices:

The inbound processing is triggered through the implementation of the BADI
EDOC_INCOM_CONNECTOR. The implementation
/OPT/EH_E_EDOC2_BADI_INCOMING is delivered in an active state.
The BC set /OTBCSL38/EDOCU_INTEGRATION_SAP, provided with the installation of

the component OTBCSL38 delivers baseline configuration that must be adjusted to your
current settings.
In addition to the general configuration described in the section above, perform the steps
described below.
In the BC customizing node Inbound Configuration > Document Handler >

Registration > Custom / Others, create an entry with the same external profile that is
maintained in the activation table. Example entry for the processing of FatturaPA (Italy):
NOTE: The IDs of the channel, handler and archiving document types must be verified
and adjusted according to your existing configuration.
In the provided baseline configuration, the inbound handler PS03_EDOC2 differs from
the typical handler used for processing with Early Archiving (OAWD). The step
GETCONT is replaced with GETDOCID, which is implemented with by another class,

/OTX/PS38_CL_DOCID_UPDATE. The rest of the steps remains the same.

The inbound processing is triggered through the implementation of the BADI
EDOC_INCOM_CONNECTOR. The implementation
/OPT/EH_E_EDOC2_BADI_INCOMING is delivered in an active state.
The configuration for the IDH scenario builds on the existing IDH configuration for e-
Invoices provided with the general delivery. To enable the processing of invoices from
SAP Document Compliance, perform the configuration steps described in the section
“General configuration” and maintain the same profile name in the activation table and in
the external profile setup of the VIM inbound channel:
6 Quick start
This section lists minimal steps needed to achieve a completely working solution for
different scenarios.
6.1 OAWD upload with BC inbound

This section assumes that all baseline settings like channels and mappings are in place
and lists the additional, project specific steps based on VIM baseline.
Archive Link:
Create new archiving document types:
One for XML files. /OPT/FATRA , /OPT/RECHN & /OPT/VUBL are provided by
Open Text.
One for visualization HTML files. Assign the value to the Z-constant 005 /
EDOC_ATTACH_HTML.
Set or verify attachments archiving document type, per Z-constant 005 /

ADDL_DOCS_AR_OBJECT.
Link BC, VIM and SAP BOR objects mentioned below to the new archiving document
types:
/OPT/V1001
/OTX/PF01R
BKPF
BUS2081
Assign the new XML archiving document type to BC Inbound workflow (Object
/OTX/PF01R, template WS00297300).
Add a new OAWD upload node (in transaction OAWS).
Business Center:
In BC customizing, assign handler and other parameters to the new archiving document
type for early archiving
6.2 Email with BC inbound

Create new archiving document types:
One for XML files. /OPT/FATRA, /OPT/RECHN and /OPT/UBL are provided by
Open Text.
EDOC_ATTACH_HTML.

Create new identically named channels in VIM and BC. VIM channel must use the
mapping according to the scenario. Example: XML_RECHN mapping for XRechnung.
Maintain SAP connect settings for incoming email similarly to displayed below. BC
Inbound exit name to use is /OTX/PF01_CL_REGISTER_MAIL.
In BC Inbound customizing, Registration – Email, maintain an entry for the chosen e-mail
address. Use the channel and archiving document types created before. Most of the time,
the baseline inbound handler definition can be used for e-mail channel too.
6.3 Email with VIM IDH (VIM 7.5 only)

Create a new archiving document type for XML files. /OPT/FATRA and /OPT/RECHN
are provided by Open Text.
Maintain SAP connect inbound processing settings for incoming email similarly to
displayed below. IDH exit name to use is /OPT/CL_C_IDH_CHANNEL_EMAIL.
Create a new inbound Email channel that is using the provided mapping XML_RECHN:
Maintain the channel external profile according to the email address set up in SAP
connect, with the document class XML and the archiving document type created earlier:
Verify the service module definition of the module TRANSEDOC. Make the
Transformation field empty if it is not:
Define new IDH processing. You can copy the standard NFE (Brazilian invoices) and then
replace the transform step TRANSFORM with TRANSEDOC. The final definition should
look like:

This section assumes that you have configured SAP Document Compliance to receive
the inbound invoices for required scenarios. The baseline configuration for Open Text
eDocument solution and for the component OTBCSL38 must be present in the system.
Archive Link: Create new archiving document types:
Open Text.
EDOC_ATTACH_HTML.

Link BC, VIM and SAP BOR objects mentioned below to the new archiving document
types:
/OPT/V1001
/OTX/PF01R
BKPF
BUS2081
Assign the new XML archiving document type to BC Inbound workflow (Object
/OTX/PF01R, template WS00297300).
For each of the scenarios (e.g. FatturaPA), configure the SAP Document Compliance
integration settings together with BC registration settings:
In the transaction SM30, view /OPT/V_EDOC2_ACT, adjust the settings for your scenario
or create new ones by copying the existing.
In BC customizing, Inbound Configuration, Registration, Custom / Others, verify the

archiving document types provided with the standard configuration. Enter the archiving
document for the main XML document and the one used for attachments. If you would
like to use your own inbound handler, and not the provided PS03_EDOC2, verify the
handler steps (make sure to use the step GETDOCID instead of GETCONT). The rest of
the settings must be the same as used for the Early Archiving scenario (channel and
classification).

This section assumes that you have configured SAP Document Compliance to receive
the inbound invoices for required scenarios. The baseline configuration for Open Text
eDocument solution and the transport for VIM 7.5 IDH must be present in the system.
Archive Link: Create new archiving document types:
Open Text.
EDOC_ATTACH_HTML.

Link VIM and SAP BOR objects mentioned below to the new archiving document types:
/OPT/V1001
BKPF
BUS2081
For each of the scenarios (e.g. FatturaPA), configure the SAP Document Compliance
integration settings together with VIM inbound channel settings:
In the transaction SM30, view /OPT/V_EDOC2_ACT, adjust the settings for your scenario
or create new ones by copying the existing.
Create a new inbound channel that is using the provided mapping, for example
XML_RECHN:
Maintain the channel external profile according to the settings in /OPT/V_EDOC2_ACT,

with the document class XML and the archiving document type created earlier.
Verify the service module definition of the module TRANSEDOC. Make the
Transformation field empty if it is not:
Define new IDH processing. You can copy the standard NFE (Brazilian invoices) and then
replace the transform step TRANSFORM with TRANSEDOC. The final definition should
look like:
7 Generic Peppol/UBL mapping

7.1 XML Mapping
There are two cases in extending of mapping:
Case 1: In the XML document, a new section was added, and it was not covered under
the transformation. The system is not parsing the new added section in the XML
document.
Case 2: A section of XML document is being parsed by transformation, but the field is not
included in the mapping.
Case 1:
Method 1:
Enhance the transformation as mentioned in section 9.2 and get the external field as
mentioned in Case 2.
Method 2:
In the XML document, there are different nodes in different hierarchies. A field can be
mapped by using its path over the hierarchy.
1. Identify the section in the XML document that is not being parsed.
Example: Suppose that the highlighted part was added in the XML document:
2. Determine the combination of nodes to map the field. To get the combination, get
the current node and the nodes above, up to 4 levels including the current node.
In the example above, we will map the value of node <IdPaese>IT</IdPaese>
The field node is IdPaese
The nodes above are IdFiscaleIVA, DatiAnagrafici, and CedentoPrestatore
The mapping path for the field is: “CedentoPrestatore-DatiAnagrafici-IdFiscaleIVA-

IdPaese"
Case 2:
1. If you want to get the combination of nodes that was already covered in the
transformation, go to the transaction STRANS, enter the relevant transformation
name, and click the Test button.
2. In the next screen, enter the source file path and click the View HTML button.
The output is displayed as pair of “EXTFIELD” and “EXTVALUE”.
The data enclosed between “EXTFIELD” tags is the path that needs to be entered as
“External field” in the mapping configuration.
XML Mapping Configuration:
1. In both described cases, when you extend the transformation or when you
identify the path, you will determine the external field name, that is, the path
made of XML nodes separated with dashes. Now it needs to be added into the
field mapping table.
2. Go to transaction /OPT/XML_MAP
3. Select an existing transformation and root node entry, or add a new
transformation if you have created one.
If there is any transformation for user display format, configure it in the third
column. This is optional.
4. If a new transformation has been added, save the entry.
5. Select the transformation and double click on the subnode “Mapping of XML data
and Semantic data” at the left in the Dialog Structure.
6. In the next screen, enter the transformation name, root node. The root node
should be the top node of the XML document.
Example: XML documents and its root nodes
7. In the Serial number column, enter a unique number.

8. In the External Field column, enter the combination of nodes as mentioned in
step 1.
9. Select the Field Type, either “Header” or “Item”.
10. Enter a meaningful name in the Semantic Name column. It is better to enter a
name in UBL format. Make sure that there are no spaces in the name.
11. For more details about the remaining columns, check the section “5.1.4.2
Mapping XML elements”.
7.2 Enhancing the Transformation

1. To create or enhance the transformation, divide the data in the XML document
into three parts. Header data, item section, and attachments.
2. Enclose Header data between tags “<HEAD_DATA>” and “</HEAD_DATA>”.
The system will consider the data between these tags as header data.
3. Similarly, enclose item data between tags “<ITEM_DATA>” and
“</ITEM_DATA>”.
4. Similarly, enclose attachments and its relevant data between tags
“<ATTACH_DATA>” and “</ATTACH_DATA>”.
5. Enclose the external field name between the tags “<EXTFIELD>” and
“</EXTFIELD>”.
6. Enclose the Field value between tags “<EXTVALUE>” and “</EXTVALUE>”.
7. Enclose every pair of external field name and the corresponding field values
between tags “<ITEM>” and “</ITEM>”.
8. Enclose all listed tags between tags “<RESULT>” and “</RESULT>”.
Example:
9. Identify the section of the XML document that needs to be mapped and decide
whether its data must be mapped as a header field, item field or attachment.
Example: Suppose the highlighted part was newly added in the XML document:
10. The highlighted part was identified as header data. Identify the corresponding
node level in the hierarchy in the XML document. In the example, it is at level 3.
Get the previous nodes up to root node.
11. Get the combination of nodes:
Node at level 1 / Node at level 2 / Node at level 3.
“/p:FatturaElettronica/FatturaElettronicaHeader/CedentePrestatore
12. Based on the above combination, write the following code:

<xsl:apply-templates
select="/p:FatturaElettronica/FatturaElettronicaHeader/CedenteP
restatore"/>
This syntax results into the transformation navigating over the child nodes of the
node set as the parameter.
13. To process further, write the following code:

<xsl:template
match="/p:FatturaElettronica/FatturaElettronicaHeader/CedentePr
estatore">
<xsl:apply-templates select="DatiAnagrafici"/>
<xsl:apply-templates select="Sede"/>
<xsl:call-template name="select-for-each"/>
</xsl:template>
To process “leaf nodes”, that provide values and do not start a nested structure, the
following statement can be used to extract all node values:
14. In the following example, a section of data was newly added in the XML
document. This section can be divided further as shown in the following: main
node, sub nodes that start a nested structure, and value nodes.
15. The value (leaf) nodes can be processed with the syntax select-for-each, as
mentioned above. But other sub nodes need to be processed further to get the
value nodes. To get the relevant data of those sub nodes, add the following code.
<xsl:apply-templates select="DatiAnagrafici"/>
<xsl:apply-templates select="Sede"/>
16. To process further, add the following code in the transformation:

<xsl:template match="DatiAnagrafici">
<xsl:apply-templates select="IdFiscaleIVA"/>
<xsl:apply-templates select="Anagrafica"/>
</xsl:template>
<xsl:template match="Sede">
</xsl:template>
17. Finally process the value nodes using the following code:
8 Additional patches
This section lists additional code or configuration changes that are to be performed after
the installation of packages. The changes will be included into the future support
packages, as specified for each entry.
8.1 Mapping of purchase unit of measure

The provided mappings do not provide conversion exits to map commercial units of
measure correctly. To solve this problem, maintain the conversion function
CONVERSION_EXIT_CUNIT_INPUT for the field BSTME as shown below, for all
mappings used for electronic invoices. This change will be included into VIM 7.5 SP10 /
16.3.4.
8.2 Long values in input XML

Very long element values present in input XML cause a problem with transformation.
Incoming documents won’t be processed and BC Inbound or IDH processing will stop.
The problem has internal code VIMI-23351.
To solve this, implement a manual correction instruction available at:
https://mimage.opentext.com/support/ecm/secure/patches/vim/ci/7.5/sp10/vim_7.5_sp10_
vimi-23351_ci-28.pdf
The correction is also released with VIM 7.5 SP10 / VIM 16.3.4.
8.3 XML transformation of XRechnung files

(Germany)
XML files for XRechnung scenario (Germany) that have been received through Peppol
network cannot be parsed correctly. A correction instruction can be downloaded with the
following URL:
8.4 Handling of attachments

Attachments from XML files are sometimes not stored properly, without correct MIME
type, or not stored at all, when the file name is longer than 20 characters. A correction
instruction can be downloaded with the following URL:
9 Known Issues
9.1 Mapping of date fields
The standard delivery performs mapping with conversion for several date fields. In case
the date values in the resulting DP document are invalid and contain non allowed
characters, you can make the mapping remove those characters by maintaining “Ignore
characters” field in the corresponding mapping entry.
10 About OpenText
OpenText enables the digital world, creating a better way for organizations to
work with information, on premises or in the cloud. For more information about
OpenText (NASDAQ: OTEX, TSX: OTC) visit opentext.com.

OpenText VIM e Invoicing

Uploaded by

Copyright:

Available Formats

OpenText VIM e Invoicing

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText VIM e Invoicing

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management for SAP® Solutions

OpenText™ Vendor Invoice Management

Document Version: 2020-09-14

The Information Company™

5.6 Integration with SAP Document Compliance – BC Inbound ................... 29

An option to integrate with SAP Document Compliance Solution is also provided by

2 Country specific notes

2.1 Italy - FatturaPA

Overview of the process:

• The interaction with government system (connectivity / middleware) is outside of

• PO based goods invoices

Multiple invoices sent in one XML file are not supported.

2.2 Germany - XRechnung

An example of transformation for XML invoice visualization is provided as a separate

2.3 Generic UBL format and delivery networks

Countries supported for generic UBL format.

Country VIM SP Transport delivery

Germany, XRechnung (UBL) 7.5 SP9 / VIM 16.3 SP3 yes

Generic (UBL) 7.5 SP10 / VIM 16.3 SP4 yes

UN-CEFACT Version 2 7.5 SP11 / VIM 16.3 SP5 yes

VIM 7.5 with BC Inbound

File name: vim-7.5-e-invoicing-bc.zip

D9PK902778 – Workbench objects

D9PK902783 – Customizing objects

VIM 7.5 with BC inbound for generic UBL

File name: vim-7.5-e-invoicing-bc-patch01.zip

D64K900474 Workbench objects

D64K900475 Customizing objects

VIM 7.5 with BC inbound for UN-CEFACT

File name: vim-7.5-e-invoicing-bc-patch02.zip

DM1K900310 Workbench objects

DM1K900311 Customizing objects

VIM 16.3 with BC Inbound

File name: vim-16.3-e-invoicing-bc.zip

D02K902488 – Workbench objects

D02K902493 – Customizing objects

VIM 16.3 with BC Inbound for generic UBL

File name: vim-16.3-e-invoicing-bc-patch01.zip

D02K903002 – Workbench objects

D02K903436 – Customizing objects

VIM 16.3 with BC Inbound for UN-CEFACT

File name: vim-16.3-e-invoicing-bc-patch02-v2.zip

D02K904109 – Workbench objects

D02K904108 – Customizing objects

VIM 7.5 with IDH

File name: vim-7.5-e-invoicing-idh.zip

D9PK902777 – Workbench objects

D9PK902784 – Customizing objects

3.2 Integration with SAP Document

PAT file name: Q020020776277_0000140.PAT

Activate the BC set /OTBCSL38/EDOCU_INTEGRATION_SAP.

To enable ACCEPT/REJECT feedback messages, some changes are required in VIM

File name: OTBCSL38-patch01.zip

D02K902954 – Workbench objects

3.3 Integration with SAP Document

4 Integration with SAP Document

• Implementation of the BADI ES_EDOC_INCOMING to start VIM processing and

Feedback functions are executed in the following way:

Reject – sent when an invoice is rejected from BC Workplace, confirmed as a duplicate,