Professional Documents
Culture Documents
e-Invoicing
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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 ..................................................................................... 11
3.3 Integration with SAP Document Compliance – VIM 7.5 IDH ................... 12
3.3.1 Prerequisites .................................................................................. 12
3.3.2 Installation ..................................................................................... 12
4 Integration with SAP Document Compliance ............................................. 12
5 Configuration ................................................................................................. 15
5.1 Provided Baseline Configuration ............................................................. 15
5.1.1 Archive Link sample configuration ................................................. 15
5.1.2 Business Center Inbound .............................................................. 15
5.1.3 VIM Configuration .......................................................................... 17
5.1.4 XML specific processing configuration .......................................... 17
5.2 Additional Required Configuration ........................................................... 20
5.2.1 BC Inbound .................................................................................... 20
5.2.2 HTML Visualization of FatturaPA .................................................. 20
5.2.3 HTML Visualization of XRechnung ................................................ 21
5.2.4 Plug-In configuration for XML visualization ................................... 22
5.3 Optional Configuration ............................................................................. 23
5.4 Special mapping logic .............................................................................. 24
5.5 Integration with SAP Document Compliance – General Configuration ... 24
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
The integration with SAP Document Compliance is supported for BC Inbound and VIM
7.5 IDH scenario.
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.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
Notes:
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:
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
• 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.
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.
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.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
1) Netherlands.
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.
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.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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).
Transports:
Transports:
Transports:
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
Transports:
Transports:
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:
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
IF /opt/vim_auth_check=>check_rfc( ) <> 0.
EXIT.
ENDIF.
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 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
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
Implement the manual corrections mentioned in the section Known Issues further in this
document, if applicable to your VIM SP level.
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.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
Transports:
The changes included into this patch will be delivered in the next support package for the
component.
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.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
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
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
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.
Till date – use this to delete all entries for eDocuments that were created on or before the
specified date.
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.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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).
OpenText recommends verifying that the provided settings do not introduce any conflicts
with the existing project specific configuration..
NOTE: These channels must be named identically with VIM input channels described
further in the document.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
/OPT/FATRA
/OPT/RECHN
/OPT/UBL
If different document types are used, create the corresponding entries by using the
provided ones as example.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
All channels are using respective country specific mappings listed below.
Mapping definitions
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.
The service module TRANSEDOC is provided for IDH scenario on VIM 7.5
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.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
Open Text delivers entries for FatturaPA, XRechnung & generic UBL.
Use the maintenance view /OPT/XML_MAPV to maintain the entries in the transaction
SM30.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
Note: Semantic mapping is done for PO Goods invoices and NON-PO invoices. Service
POs mapping is not delivered with baseline.
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.
The second step is performed with provided VIM mappings maintained in the respective
channels. (XML_FATURA, XML_RECHN etc.)
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
Document type
Payment method
Archive ID for XML – set the repository name according to your archiving system
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).
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.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
<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">
<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">
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:”.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
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:
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.
Plug-In Id Configuration
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
Proceed to the following customizing node and create a new plugin ID to display the XML
in user friendly format.
Proceed to the following customizing node and assign the created plug-in ID to plug-in
type.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
If needed, the provided function modules can be copied and extended to suit project
specific needs.
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):
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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:
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
In the transaction SM30, view EDOINCOMSOLV, maintain entries for each scenario,
company code and OPT automation solution. Below is an example for Italian invoices:
In addition to the general configuration described in the section above, perform the steps
described below.
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
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
Archive Link:
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
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).
Business Center:
In BC customizing, assign handler and other parameters to the new archiving document
type for early archiving
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
One for XML files. /OPT/FATRA, /OPT/RECHN and /OPT/UBL are provided by
Open Text.
One for visualization HTML files. Assign the value to the Z-constant 005 /
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.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
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:
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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:
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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 all baseline settings like channels and mappings are in place
and lists the additional, project specific steps based on VIM baseline.
One for XML files. /OPT/FATRA, /OPT/RECHN and /OPT/UBL are provided by
Open Text.
One for visualization HTML files. Assign the value to the Z-constant 005 /
EDOC_ATTACH_HTML.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
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.
One for XML files. /OPT/FATRA, /OPT/RECHN and /OPT/UBL are provided by
Open Text.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
One for visualization HTML files. Assign the value to the Z-constant 005 /
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:
Verify the service module definition of the module TRANSEDOC. Make the
Transformation field empty if it is not:
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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 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.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
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.
https://mimage.opentext.com/support/ecm/secure/patches/vim/ci/7.5/sp09/vim_7.5_sp09_
vimi-23854_ci-59.pdf
The correction is also released with VIM 7.5 SP10 / VIM 16.3.4.
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).
OpenText™ Vendor Invoice Management for SAP® Solutions
https://mimage.opentext.com/support/ecm/secure/patches/vim/ci/7.5/sp10/vim_7.5_sp10_
vimi-23870_ci-75.pdf
The correction is also released with VIM 7.5 SP10 / VIM 16.3.4.
8 Known Issues
8.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.
9 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.
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).