OpenText™ Vendor Invoice Management for SAP® Solutions

OpenText™ Vendor Invoice Management

for SAP® Solutions
White Paper

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

The Information Company™

Contents
1 Introduction ...................................................................................................... 3
2 Installation ........................................................................................................ 4
3 Configuration ................................................................................................... 5
3.1 Business Center Configuration .................................................................. 5
3.1.1 Archive Document Configuration ..................................................... 5
3.1.2 Channel Configuration ..................................................................... 8
3.1.3 Inbound handler Configuration ........................................................ 9
3.1.4 Inbound registration ....................................................................... 10
3.1.5 Plug-In Id Configuration ................................................................. 10
3.1.6 Assign Plug-In Id to Plug-In type ................................................... 10
3.2 VIM Configuration .................................................................................... 11
3.2.1 Channel Configuration ................................................................... 11
3.2.2 Mapping Configuration .................................................................. 12
3.3 IDH configuration ..................................................................................... 15
3.3.1 Email Channel Configuration ......................................................... 15
3.3.2 Maintain Service modules ............................................................. 16
3.3.3 Maintain Process Ids ..................................................................... 17
3.4 Post Installation activities......................................................................... 17
3.5 Technical objects ..................................................................................... 19
3.6 Known Issues .......................................................................................... 20
About OpenText .............................................................................................. 21

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
This special delivery is part of OpenText Vendor Invoice Management for
SAP solutions. Only customers with an OpenText license for “OpenText
Vendor Invoice Management for SAP solutions” or an SAP license for
“SAP Invoice Management by OpenText” or “SAP Invoice Management
for SAP S/4HANA by OpenText” are entitled to download and install the
transports in their SAP system.

Starting 1st of January 2019, electronic invoicing (e-invoicing) will become mandatory for
all B2B and B2C 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:

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

Notes:

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

scope of the support provided in Vendor Invoice Management by OpenText.
• An option to interact with government system is SAP eDocument Framework
and the integration with SAP eDocument Solution is planned to be provided by
OpenText.

The current delivery provides the support for starting VIM process by uploading the XML
files with the transaction OAWD. 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.

The following scenarios are currently supported by VIM with e-invoicing for Italy:

• PO based goods invoices

• NON PO invoices

The minimum VIM release and SP levels are VIM 7.5 SP7 with OpenText Business
Center (BC) 16.0 update 1, and VIM 16.3 with Business Center 16.3.

OpenText provides two different way to implement e-invoicing for Italy: one based on the
BC Inbound framework of OpenText Business Center, and another based in the older
Incoming Document Handler (IDH). Please note that IDH is supported only on VIM 7.5 for
customers who upgraded from older SPs and VIM 7.0. IDH is not supported on VIM 16.3
and on new installations of VIM 7.5. We generally recommend using BC Inbound.

The content of this document will be integrated into VIM documentation (Installation and
Configuration guides) with the release of VIM 7.5 SP9 and VIM 16.3 SP3.

2 Installation
OpenText delivers the necessary objects as a separate set of transport files. You find the
transport files on Open Text My Support. The downloads are organized according to the
scenario (BC or IDH).

To import the transport files:

1. On My Support, access My Support > PATCHES > Vendor Invoice Management

> E-invoices Italy – Fattura PA.
2. Download the transport files. Two packages are being provided:
Fattura-PA-BC-Inbound-based-v3.zip for a solution based on BC
Inbound (recommended)
Fattura-PA-VIM-IDH-based-v2.zip for a solution based on VIM Incoming
Document Handler
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: in case you already imported the transports from the earlier
delivery, found in the same download folder, simply import the newer
versions.
3. Perform the import.

Transport list:

BC based solution:

D9PK902234 Workbench objects for BC Inbound

D9PK902180 Configuration for BC Inbound

VIM IDH based solution:

D9PK902230 Workbench objects for IDH

D9PK902144 Configuration for IDH

After the import, required baseline configuration will be present in your system. The steps
specific for each project and not delivered in the package are described in the next
sections.

3 Configuration
3.1 Business Center Configuration
The inbound invoice XMLs need to be processed by BC Inbound (via OAWD) and then
routed into VIM.

The first configuration steps to perform are the following:

3.1.1 Archive Document Configuration

Create a new document type for e-invoices via OAC2 (/OPT/EDOC is used 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

Assign the new document type to the following business objects in OAC3.

/OPT/V1001

/OTX/PF01R

BUS2081

BKPF

Assign the e-invoices archiving document type to Business object and Workflow template
to register the document (OAD5).

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

3.1.2 Channel Configuration

To support e-invoicing via OAWD, a new channel OAWD_EDOC is needed. The
channels are maintained in the BC customizing transaction /OTX/PF00_IMG. Proceed to
the following customizing node:

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

3.1.3 Inbound handler Configuration

Proceed to the following customizing node and create new BC Inbound handler for e-
invoices.

Configure the modules for this BC Inbound handler.

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.

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

3.1.4 Inbound registration

Proceed to the following customizing node and create a new entry linking archiving
document type, channel and handler.

3.1.5 Plug-In Id Configuration

Proceed to the following customizing node and create a new plugin ID to display the XML
in user friendly format.

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

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

3.2 VIM Configuration

3.2.1 Channel Configuration
To support e-invoicing for Italy via OAWD, a new channel OAWD_EDOC is needed. The
channels are maintained in the VIM customizing transaction /OPT/SPRO. Proceed to the
following customizing node:

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

3.2.2 Mapping Configuration

To make the mapping generic, we are using two step mapping procedure.

1. XML/External data to Semantic data model mapping.

2. Semantic data model to VIM mapping.

3.2.2.1 XML to Semantic data model mapping

Go to transaction /OPT/XML_MAP or maintenance view /OPT/XML_TRAN_HV
and maintain the entries.

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.

Note: Semantic mapping is done for PO Goods invoices and NON-PO invoices.
Service POs mapping is not delivered with baseline.
Limitation on nodes – Maximum nodes are limited to 4.
Example: FatturaElettronicaBody-DatiGenerali-DatiTrasporto-DataOraConsegna

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 the field appears to be on node hierarchy > 4, then ignore the root node (for
example FatturaElettronicaBody) and provide the remaining path. Make sure the
external field name is unique.

3.2.2.2 Semantic data model to VIM mapping

Proceed to the following customizing node and create a new mapping.

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

3.2.2.3 Automated Field Enhancement

3.2.2.4 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 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

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

3.3 IDH configuration

The inbound invoice XMLs need to be processed by IDH (via Email channel) and then
routed into VIM.

The first configuration steps to perform are the following:

3.3.1 Email Channel Configuration

Create a new channel ID EDOC_EMAIL for e-invoices and set up the external profile ID.

For more details, refer to VIM 7.5 Configuration guide for Email channel 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

3.3.2 Maintain Service modules

Proceed to the following customizing node and create a new module Id TRANSEDOC for
data 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

3.3.3 Maintain Process Ids

Proceed to the following customizing node and configure the modules for e-invoices.

3.4 Post Installation activities

Step 1: HTML document type configuration

If HTML document type is not yet available, do the following.

Create a new archiving document type /OPT/HTM for document class HTM in OAC2.

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

Assign the created archiving document type to business object /OPT/V1001 in OAC3.

Step 2: HTML document type Z constant for user-friendly display format in VAN report

To view the XML file in user-friendly display format in VAN report, maintain the following
Z-constant.

Product code 005

Constant PLUG_IN_OBJECTDISP

Description Web Viewer Customization

Constant Value /OPT/VIM_GET_ARCH_URL

/OPT/VIM_GET_ARCH_URL is a function module that is delivered with package.

Step 3: Pass HTML VIEW Parameter to Plug-In Definition: Image display

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

Once the above mentioned constant is configured, start the transaction SE24, enter the
class name /OPT/CL_C_UI_PLUGIN_DEF_IMAGE and perform a modification in the
method PLUGIN_CONTROL_INIT.

The modification will pass the HTML Control proxy class to the call
CALL FUNCTION lv_funcname "'/IXOS/OA_X_OA_OBJECTDISPLAY_01'.

Note: This must be done as a modification, later it will be included into standard VIM.

After modifications, the code should be as shown below.

3.5 Technical objects

All the objects are delivered with package /OPT/VIM_EDOC.

Transformations:

OPT/TRANS_XML_FATTURA – Data Mapping

/OPT/TRANS_FATTURA_USER_DISP – User Friendly format

Classes:

/OPT/VIM_ATTACH_USER_FORMAT - Attach user friendly format as HTML

document

/OPT/VIM_CL_MODULE_PARSE_EDOC - Get the data from XML and convert into

sematic data

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

/OPT/VIM_GET_XML_CONTENT - Fetch the XML content and update the

Reg table (Used for OAWD
channel

/OPT/PLUGIN_DEF_IMAGE_FATURA - To display the user friendly format in plugin

/OPT/CL_MODULE_PARSEXML_NOTRAN - Convert the xml data without

transformation

Tables:

/OPT/XML_TRAN_H - Intermediate mapping transformation

/OPT/XML_MAP - Mapping between XML data and Semantic data

/OPT/EDOC_CODES - Mapping between Italy specific codes and SAP codes (ex:
Document Type, Payment Method etc.)

/OPT/CODES_TEXT - Texts for Italy specific codes

Table Type

/OPT/VIM_TT_EXTDATA_FIELD – Used in the transformation

Function modules:

/OPT/VIM_ATTACH_EDOC_USRFORMAT - Attach user friendly format as HTML

document

/OPT/VIM_EXIT_MAP_ENH_FATRURA - Data mapping of derived fields

/OPT/VIM_GET_ARCH_URL - Get the URL to display the user-friendly

format in plugin

3.6 Known Issues

In case of IDH scenario, the file to display e-invoices in user-friendly display format is not
generated and attached as a separate attachment. However, by configuring the image
display user exit as described in the “Post installation” section (Z-constant
PLUG_IN_OBJECTDISP) you will still be able to see the e-invoice in user friendly format
in VIM Analytics report or in VIM workplace.

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

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