opentext vendor invoice management for sap solutions 7.0 - installation ....pdf

OpenText Vendor Invoice Management forSAP Solutions

Installation Guide

This guide describes the installation of all Vendor InvoiceManagement (VIM) 7.0 components: Vendor InvoiceManagement SAP ERP component, optional OpenTextApproval Portal, optional Mobile Approval Portal, optional KPIDashboard, optional Vendor Invoice Management SAP CRMSAP Shared Service Framework component, optional VendorInvoice Management SAP NetWeaver® Business Warehouse(VIM BW) component, optional Vendor Invoice ManagementSAP NetWeaver Gateway component, optional Vendor InvoiceManagement Supplier Self Service component, and optionalVendor Invoice Management input channel for Ariba NetworkIntegration for SAP Business Suite.

VIM070000-IGD-EN-6

OpenText Vendor Invoice Management for SAP SolutionsInstallation GuideVIM070000-IGD-EN-6Rev.: 18. July 2014

This documentation has been created for software version 7.0.It is also valid for subsequent software versions as long as no new document version is shipped with the product or ispublished at https://knowledge.opentext.com.

Open Text SA

40 Avenue Monterey , Luxembourg, Luxembourg L-2163

Tel: 35 2 264566 1

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Tel: +1-519-888-7111Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440Fax: +1-519-888-0677Support: http://support.opentext.comFor more information, visit https://www.opentext.com

Copyright © 2014 Open Text SA and/or Open Text ULC. All Rights Reserved.

Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is notexhaustive of other trademarks, registered trademarks, product names, company names, brands and service namesmentioned herein are property of Open Text SA or other respective owners.

Disclaimer

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for theaccuracy of this publication.

https://knowledge.opentext.com

http://support.opentext.com

https://www.opentext.com

Table of ContentsPart 1 About Vendor Invoice Management 7

1 About This Document ............................................................... 91.1 Target Audience ............................................................................... 91.2 Document Overview .......................................................................... 9

Part 2 Vendor Invoice Management SAP ERP ComponentInstallation 11

2 Preparing Installation .............................................................. 132.1 General .......................................................................................... 132.2 Password Control ............................................................................ 142.3 Checking Prerequisites .................................................................... 142.4 Notes on Transports ........................................................................ 16

3 Installing the OpenText Package ........................................... 173.1 Installing the Package ..................................................................... 173.2 Post Installation Activities ................................................................ 173.3 Language Packs ............................................................................. 38

4 Verifying Installation ............................................................... 39

5 Installing a VIM Support Package .......................................... 415.1 SAP ERP Prerequisites ................................................................... 415.2 Handling Workflow Container Inconsistencies ................................... 425.3 SAP Installation .............................................................................. 43

6 Upgrading ................................................................................. 496.1 Upgrade Overview .......................................................................... 496.2 Handling Workflow Container Inconsistencies ................................... 516.3 Upgrading SAP ERP ....................................................................... 526.4 Upgrading VIM ................................................................................ 566.5 Post Installation Activities After an Upgrade ...................................... 62

7 Troubleshooting ...................................................................... 677.1 FAQs ............................................................................................. 67

Part 3 KPI Dashboard Installation 69

8 Installing the KPI Dashboard .................................................. 71

9 Post Installation Activities ...................................................... 739.1 Activating the SAP Web Dynpro Service ........................................... 739.2 Setting the Connection for the SAP Web Dynpro Service ................... 78

OpenText Vendor Invoice Management for SAP Solutions – Installation Guide iiiVIM070000-IGD-EN-6

9.3 Setting Up the SAP NetWeaver Portal Integration ............................. 79

Part 4 OpenText Approval Portal Installation 83

10 Preparing Installation .............................................................. 8510.1 Installation Prerequisites .................................................................. 8510.2 Installation Components .................................................................. 8810.3 System Architecture ........................................................................ 89

11 Installing the Approval Portal ................................................. 9311.1 Preparing the Installation ................................................................. 9311.2 Configuring the Administrator Role ................................................... 9611.3 Deploying the Software Component Archive ................................... 10111.4 Deploying the Software Component Archive with SAP NetWeaver

7.3 and 7.4 ................................................................................... 105

12 Configuring SAP NetWeaver Portal Components .............. 10912.1 Creating AppIntegrator IViews for Users ......................................... 10912.2 Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3

and 7.4 ......................................................................................... 11512.3 Creating Roles for Users ............................................................... 12512.4 Creating Roles for Users with SAP NetWeaver 7.3 and 7.4 .............. 12912.5 Assigning Roles to SAP NetWeaver Portal Users ............................ 13212.6 Configuring IViews and Roles for the Administrator ......................... 13312.7 Administering the OpenText Approval Portal ................................... 134

13 Applying a New Patch ........................................................... 135

14 Upgrading the Approval Portal from Previous Versions ... 137

15 Troubleshooting .................................................................... 139

16 Supporting Installation of the Standalone NWAS Portaland Mobile Approval Portal on Unix or Linux ..................... 141

17 Uninstalling the Approval Portal .......................................... 14317.1 Uninstalling Using Software Deployment Manager .......................... 14317.2 Uninstalling with SAP NetWeaver 7.3 and 7.4 ................................. 14417.3 Removing SAP NetWeaver Portal Components .............................. 14517.4 Deleting Properties Files ................................................................ 14617.5 Optional: Removing the Startup Parameter in the Config Tool .......... 146

Part 5 Mobile Approval Portal Installation 149

18 Introduction to the Mobile Approval Portal ......................... 151

19 Authentication for the Mobile Approval Portal ................... 155

Table of Contents

iv OpenText Vendor Invoice Management for SAP Solutions – Installation GuideVIM070000-IGD-EN-6

20 Installing Web Viewer for the Mobile Approval Portal ....... 157

21 Installing the Mobile Approval Portal .................................. 15921.1 Installing the Mobile Approval Portal on Standalone NWAS

7.0/7.3/7.4 .................................................................................... 15921.2 Installing the Mobile Approval Portal on SAP NetWeaver Portal

7.0/7.3/7.4 .................................................................................... 159

Part 6 Vendor Invoice Management SAP CRM SAP SharedService Framework Component Installation 161

22 Preparing Installation ............................................................ 16322.1 Password Control .......................................................................... 16322.2 Checking Prerequisites .................................................................. 163

23 Installing the OpenText Package ......................................... 167

24 Post Installation Activities .................................................... 16924.1 Activating Business Configuration Sets in the CRM System ............. 16924.2 Maintaining a Logical System for the CRM System in VIM ............... 17324.3 Installing Support Packages 1 and 2 ............................................... 173

25 Verifying Installation ............................................................. 175

Part 7 Vendor Invoice Management SAP NetWeaver BusinessWarehouse Component Installation 177



28 Verifying the Installation ....................................................... 185

29 Upgrading SAP NetWeaver BW ............................................ 187

Part 8 Vendor Invoice Management SAP NetWeaver GatewayComponent Installation 189




Table of Contents

OpenText Vendor Invoice Management for SAP Solutions – Installation Guide vVIM070000-IGD-EN-6

Part 9 Vendor Invoice Management Supplier Self ServiceComponent Installation 197

33 Preparing Installation ............................................................ 19933.1 Installation Prerequisites ................................................................ 19933.2 Installation Components ................................................................ 20033.3 System Architecture ...................................................................... 200

34 Installation on the SAP HANA Cloud ................................... 20134.1 Preparing the Installation ............................................................... 20134.2 Deploying the Application on the SAP HANA Cloud Server .............. 20134.3 Installing the SAP HANA Cloud Connector ...................................... 202

Part 10 Vendor Invoice Management Input Channel for AribaNetwork Integration for SAP Business Suite Installation 205



37 Post Installation Activities .................................................... 21137.1 Activating Business Configuration Sets for the OTVIMARB

Component ................................................................................... 211


GLS Glossary 215

Table of Contents

vi OpenText Vendor Invoice Management for SAP Solutions – Installation GuideVIM070000-IGD-EN-6

Part 1About Vendor Invoice Management

Vendor Invoice Management (VIM) is a packaged business solution that basicallysolves a business problem – paying correct amount to vendors on-time. VIM is anadd-on to your SAP ERP system, the majority of its functions and processes runinside the SAP ERP system; it deals only with invoices that will be posted to SAPERP. It integrates with standard SAP functions such as Invoice Verification,Financial Processing, and so on.

Patches (Hot Fixes), Support Packages and the latest versions of the Release Notesfor VIM are available in the OpenText Knowledge Center: https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151605. The latest versionsof the documentation are also available in the Knowledge Center: https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151494.

For SAP Invoice Management by OpenText customers: To obtain access to theKnowledge Center, initiate a ticket request in SAP Service Marketplace.

For OpenText customers: Send an email to [email protected].

Important note for SAP Reseller Customers

For information about all OpenText products resold by SAP (including VIMand ICC), check SAP Marketplace Note 1791874: SAP Products by OpenText- Software and Support Lifecycle. This note provides detailed informationabout software life cycle, access to Support Packages, access to latestdocumentation, language packages, and other patches, as well as Supportticket handling.

Patches

Part 1 About Vendor Invoice Management

8 OpenText Vendor Invoice Management for SAP Solutions – Installation GuideVIM070000-IGD-EN-6

https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151605




Chapter 1

About This Document

1.1 Target AudienceThis document addresses those who participate in the administration andmaintenance of Vendor Invoice Management (VIM). This includes

• SAP Basis Administrators• SAP Workflow Administrators• SAP Configuration and Development Support

VIM features the optional component Web Invoice Approval. The target audience forthis component includes:

• Site administrators• Database administrators• Network administrators

1.2 Document OverviewThis Installation Guide includes the complete installation information for all VendorInvoice Management components:

• “About Vendor Invoice Management” on page 7• “Vendor Invoice Management SAP ERP Component Installation” on page 11• “KPI Dashboard Installation” on page 69• “OpenText Approval Portal Installation” on page 83• “Mobile Approval Portal Installation” on page 149• “Vendor Invoice Management SAP CRM SAP Shared Service Framework

Component Installation” on page 161• “Vendor Invoice Management SAP NetWeaver Business Warehouse Component

Installation” on page 177• “Vendor Invoice Management SAP NetWeaver Gateway Component

Installation” on page 189• “Vendor Invoice Management Supplier Self Service Component Installation”

on page 197• “Vendor Invoice Management Input Channel for Ariba Network Integration for

SAP Business Suite Installation” on page 205

OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 9VIM070000-IGD-EN-6

Part 2Vendor Invoice Management SAP ERP

Component Installation

This part describes the installation of the SAP ERP component of Vendor InvoiceManagement (VIM).

Part 2 Vendor Invoice Management SAP ERPComponent Installation


Chapter 2

Preparing Installation

2.1 General

CautionThe following information is very important. Read the table carefullybefore the installation.

Disclaimer This guide delivers an overview of the installation procedures.OpenText disclaims all warranties for an unauthorized use of thisguide. Any unauthorized use is conducted on your ownresponsibility excluding any liability of OpenText. If you haveany questions, contact OpenText Global Services.

Supported versions Only the products and versions specified in the Release Notes aresupported. Other versions have not been tested and are thereforenot officially supported for this version. The Release Notescontain the definitive list of supported versions. Any otherversions mentioned in this guide are superseded by the versionsspecified in the Release Notes.

OpenText SupportCenter

If you require additional help with technical problems, contactOpenText Customer Support. You can find the contactinformation for your region at http://www.opentext.com/services/support.html.

ImportantMake sure the SAP workflow system is configured to run workflows. Tocheck this, run the SWU3 transaction. Make sure most of the relevant items areconfigured correctly, indicated by the icon. It is very important that, in theMaintain Runtime Environment node, Configure RFC destination has the

icon.

Note: Check for and download the available latest support packs and hot fixesat the OpenText Knowledge Center: https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151605.


http://www.opentext.com/services/support.html

http://www.opentext.com/services/support.html



2.2 Password ControlThe OpenText Vendor Invoice Management package is protected with a specificpassword. During installation, this password is requested by the SAP Add-OnInstallation Tool (SAINT).

The following table shows the passwords for VIM installation, SAP ERP upgradeand VIM upgrade.

VIM Package SAP ECC 6.0

VIM installation E067B86AE9

SAP ERP upgrade E067B86CFE

VIM upgrade E067B86AEE

2.3 Checking Prerequisites

2.3.1 Required KnowledgeThe following knowledge is required for the person dealing with the installation asdescribed in this document:

• In-depth knowledge of SAP administration tasks, in particular the SAP Add-OnInstallation Tool (SAINT)

• Basic knowledge of the employed operating system

2.3.2 SAP ERP PrerequisitesCheck the following prerequisites prior to installation:

SAP ECC 6.0

• Support Package Manager (transaction code SPAM) level 35• Apply OSS note 1082597: Not enough business functions activated in SFW5; this is

used for Switch Frame Work for activating the PO based invoice parkinginfrastructure.

• Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0s ASABAP

• Apply OSS note 1462364: Dependent structure has inconsistent runtime objectafter mass activation. This is specific to SAP ECC 6.0 system, up to EHP5.

• Apply OSS note 1390369: ALV graphic: Double number of bars• For a list of available software components, check OSS note 1791715: SAP Invoice

Management by OpenText 7.0

The following components must be installed for SAP ECC 6.0 up to EHP7:

Chapter 2 Preparing Installation


Option Component: SAP_BASIS

Release Level Support package

1 700 0013 SAPKB70013

2 701 0003 SAPKB70103

3 702 0003 SAPKB70203

4 higher -

2.3.3 Workflow CustomizingMake sure the SAP workflow system is configured to run workflows.

To check for correct workflow configuration:

• Run the SWU3 transaction.

Make sure that the complete section Maintain Runtime Environment isconfigured correctly, indicated by the icon.

2.3.4 Installation ToolOpenText Vendor Invoice Management uses the SAP Add-On Installation Tool(SAINT) for installation. SAINT uses single PAT files (extension *.PAT) whichintegrate several transport files; these collections are also called packages.

On the product CD, the single PAT files are archived in SAPCAR files (extension*.SAR) that can be extracted using the SAPCAR command line tool. The differentSAPCAR files are located in a DATA folder below the respective package folder namedas the package and SAP release.

2.3. Checking Prerequisites


2.4 Notes on TransportsThis section applies to EHP5 and higher. SAP has implemented additional checksduring the import of transports.

Some steps of the installation and upgrade procedures make use of transports. Thesetransports have been created in the OpenText development or packaging systems.These systems do not have the same components and component versions as yoursystems. So, when the transport is imported, you must select the Ignore invalidcomponent version check box.



Chapter 3

Installing the OpenText Package

This chapter describes the installation of the Basis package of Vendor InvoiceManagement (VIM) on an SAP ERP system. Read also “Preparing Installation“on page 13 with general information on installation in an SAP environment.

3.1 Installing the PackageThe basic components are installed with the Basis package.

To install the Basis package:

1. Copy the respective SAPCAR file (*.SAR) from the product CD to the target SAPapplication server in the \usr\sap\trans folder (this is the parent folder of theDIR_EPS_ROOT folder).

SAP version File Source path Target path

SAP ECC 6.0 OTEXVIM_INST_700_700.SAR

INST_ERP\DATA\ \usr\sap\trans\EPS

2. Extract the SAPCAR file to the \usr\sap\trans\EPS\in folder with thefollowing command: SAPCAR -xvf <name of SAPCAR file>.

The resulting PAT file will be extracted to the EPS\in folder relative to the pathof the SAPCAR file.

3. Carry out the import of the package as described in the respective SAPdocumentation.

4. To finish installation, install the most recent VIM 7.0 Support Package (SP). Youfind the SPs in the Knowledge Center: https://knowledge.opentext.com/knowledge/cs.dll/Open/10151605. For further information, see the Release Notesof the respective SP.

3.2 Post Installation ActivitiesTo ensure the integrity of the installed transports, you have to perform and validatethe following procedures:

• “Activating Business Configuration Sets” on page 18• “Configuring Workflow Dialog Tasks” on page 22• “Refreshing SAP Workflow Runtime Buffer” on page 24• “Configuring Object Services” on page 25• “Maintaining Number Ranges” on page 27


https://knowledge.opentext.com/knowledge/cs.dll/Open/10151605


• “Linking Events for VIM Workflows” on page 30

• “Maintaining the SAPscript Form for Approval” on page 33

• “Maintaining Standard Text” on page 34

• “Setting Background User Parameters for Non PO Invoice Posting” on page 36

• “Configuring Additional Settings” on page 37

• “Installing Transports with Layout Variants for Integrated Invoice Cockpit andIDH Admin Tool” on page 38

3.2.1 Activating Business Configuration Sets

ImportantThis section is only relevant for VIM installation. For an SAP and VIMupgrade, do not perform the actions described in this section. In case of aVIM upgrade, previous VIM configuration data will be overwritten afteractivating Business Configuration Sets (BC Sets). Any custom changesperformed in a previous version of VIM need to be redone after the BC Setsactivation.

Notes

• For every client, you must activate new BC Sets after installing VIM 7.0.

• You need the appropriate security authorization to run some of thetransactions.

• Depending on the SAP version, the following screens might look different onyour system.

You activate the BC Sets in the following steps:

1. Apply recommended user settings

2. Activate BC Set /OTEXVIM/VIM70_BASELINE_LEGACY

Activate the BC set in the Configuration client of the Development system andcreate a transport from BC set activation, move the transport to requiredsystems.

Don’t activate the BC set in the production system. Create a customizationtransport in Development System configuration client by activating the BC setand move it to desired systems.

To apply recommended user settings:

1. To access the Business Configuration Sets: Activation screen, run the SCPR20transaction.

From the Utilities menu, click User Settings.

Chapter 3 Installing the OpenText Package


VIM 7.0 supports the following languages:

• Chinese

• Dutch

• English

• French

• German

• Hungarian

• Italian

• Japanese

• Portuguese

• Romanian

• Russian

• Spanish

3.2. Post Installation Activities


New languages for VIM 7.0 are the following:

• Czech

• Polish

• Turkish

To select your applicable languages, select the respective check box in theManual Selection column.

2. Click the Maint. Transaction tab.

Apply the settings, as shown in the screenshot.

3. To copy the settings, click .

You are now ready to activate the BC set.

To activate BC Sets:




2. Enter the BC set name /OTEXVIM/VIM70_BASELINE_LEGACY and click theActivate button .

Note: If you are prompted to create a new transport, follow your standardchange request process for tracking changes.

3. Apply the recommended settings, as shown in the screenshot.

4. Click the Activate button.After BC Set activation, a message is displayed in the lower left of the SAP GUI,for example: Activation ended with warning.

Tip: You can ignore any warnings during the activation. If you get anerror during activation of a BC set, then activate it again. In many cases theerror will disappear. You can ignore activation errors like No data foundfor writing activation links for object <xxx>.

5. After you have activated the BC set /OTEXVIM/VIM70_BASELINE_LEGACY,continue and activate BC set /OTEXVIM/VIM70_BASELINE_NEWFOR70.



3.2.2 Configuring Workflow Dialog TasksUse the instructions in this section to set the attribute to “General Task” for thefollowing tasks:

Table 3-1: Workflow dialog tasks

Task Dialog Task ID

1 DP WF 00275278

2 PO Parked 00275262

3 PO Blocked Line level 00275265

4 PO Blocked Header 00275267

5 NPO parked 00275260

6 IAP 00275253

7 Referee workitem 00275283

To configure a General Task:

1. Run the PFTC transaction.

2. In the Task type field, select Standard task, enter the task ID and click the button.



3. In the Standard Task: Display screen, select Additional data > Agentassignment > Maintain.

4. In the Standard task: Maintain Agent Assignment screen, select the name ofthe assignment and then click the Attributes button.



5. In the Task popup, select General Task and click the Transfer button.

The standard task is now configured as a General Task.

If you are prompted to create a new transport, continue with the next step.

If you are asked if you want to Transfer missing elements from the objectmethod?, click No.

6. Follow your standard change request process for tracking changes.

7. Repeat the procedure for all the tasks mentioned in Table 3-1 on page 22.

3.2.3 Refreshing SAP Workflow Runtime BufferFor proper operation of VIM, you need to refresh the SAP workflow runtime buffer.

To refresh runtime buffer:

1. Run the SWU_OBUF transaction.



2. To refresh the runtime buffer, click the Start Synchronization button.

3.2.4 Configuring Object Services

Note: The new table entries should have been installed by the package. Tocheck the settings, use Step 1 to Step 4 of the following procedure. You mustlink the new services to WF_START (Step 5).

The VIM dashboard and the OpenText Document Processing document services areaccessible from the SAP Invoice function.

To activate the object services:

1. Run the SM30 transaction.

2. Enter SGOSATTR in the Table/View field and click the Maintain button.



3. When a popup is displayed, indicating that the table is cross client, click the button.

4. Check whether the entries for the services WF_ZOPT/VIM and ZOPT_SERVC arepresent.

If the entries are not present, add these entries, as shown in the screenshotsbelow.



5. Double-click WF_START. Enter WF_ZOPT/VIM in Next service and save.

If you are prompted to create a new transport, continue with the next step.

6. Follow your standard change request process for tracking changes.

3.2.5 Maintaining Number RangesYou have to maintain number ranges for the following objects:

Object Description

/PTGWFI/RI CP Document

/OPT/DOCID Document Processing

/ORS/STACK Invoice Approval

/ORS/USRMP Invoice Approval Usermap

/OPT/REGID Incoming Document Handling (IDH) framework

ImportantAll the number ranges intervals must be 01.

To maintain the number range:

1. Run the SNRO transaction.



2. Enter the object name from the table above, for example /OPT/DOCID and clickthe Number ranges button.

3. Click the button.



4. Click the button to add a new number range.

5. Enter required value and save it.



3.2.6 Linking Events for VIM Workflows

Note: The entries should have been installed by the activation of the BC sets.But you have to activate the linkages and switch on the event queue. If an entryis missing, add the entry.

SAP events are trigger points for VIM workflows. For example, when a logisticinvoice is posted, SAP ERP generates the event POSTED from the business objectBUS2081. The event is linked to trigger the VIM workflow solution for blockedinvoices if the invoice is blocked.

With VIM 6.0 and higher, event linkages are no longer created automatically. Youmust add the event linkages manually.

Note: OpenText advises against parking documents outside of VIM andstrongly recommends parking documents through the DP workflow. If parkingis done outside the DP workflow, then sometimes, due to system limitations,parking events are not raised properly. In this case, parked documents do notshow up in the VAN report. To prevent this issue (if it occurs), OpenTextrecommends queuing the parking events.

In case of not properly raised parking events, perform the following actions:

1. To queue parking events, run the SWE2 transaction.

Select the check box Enable event queue for the events /OPT/B2081 -ZWFI_PARKED and /OPT/FIPP - ZWFI_CREATED and save the configuration.

2. To schedule the Event Queue Job, run the SWEQADM transaction. You canset the frequency according to your requirement how often to update therespective data.

The following event linkages can be turned on or off to enable or disable VIMworkflows:

Table 3-2: Event linkages for VIM workflows

Object type Event

Receiver type

Receiver function module

Check function module

Usagecomments

FIPP DELETED

TS00275270

SWW_WI_CREATE_VIA_EVENT

—

InvoiceApproval (IAP)

FIPP POSTED

TS00275270


—

IAP

BUS2081 DELETED

TS00275270


—

IAP



Object type Event

Receiver type

Receiver function module

Check function module

Usagecomments

BUS2081 POSTED

TS00275270


—

IAP

BUS2081 POSTED

WS00275264

/OPT/BL_PO_BLK_RECEIVER

/OPT/BL_PO_CHECK_ROLL_OUT

InvoiceException (IE)

BUS2081 POSTED

TS00275264

/OPT/BL_PO_BLK_RECEIVER

/OPT/BL_PO_CHECK_ROLL_OUT

IE

/OPT/FIPP ZWFI_CREATED

WS00275254

/OPT/BL_NPO_PRK_RECEIVER

/PTGWFI/PIR_F_CHECKFM

IE

/OPT/B2081 ZWFI_PARKED

WS00275260

/OPT/BL_PO_PRK_RECEIVER

/PTGWFI/PRK_M_CHECKFM

IE

FIPP DELETED

—

/OPT/VIM_RPT_RECEIVER_FM

—

VIM Analytics(VAN)

FIPP POSTED

—

/OPT/VIM_RPT_RECEIVER_FM

—

VAN

BUS2081 DELETED

—

/OPT/VIM_RPT_PO_INV_RECEIVER

—

VAN

BUS2081 POSTED

—


—

VAN

May be used inspecialsituation.Should beinactive instandardconfiguration.

BUS2081 RELEASED

—


—

VAN

BUS2081 CANCELLED

—


—

VAN

/ORS/INVAP POSTED

—

/OPT/AAFS_POST_RECEIVER

—

PostedApproval



Note: There is a dependency between two entries for Object Type BUS2081 andEvent POSTED, the one with Receiver Type WS00275264, and the one with anempty Receiver Type.

In transaction SWETYPV, make sure that only one of these event linkages isactivated.

• If you use your own blocking workflow, activate only the event linkage withempty Receiver Type. This event linkage ensures that VAN will be correctlyupdated.

• If you use the standard blocking workflow template, activate only the eventlinkage with Receiver Type WS00275264. This event linkage updates VANwith the same function module as the other event linkage but it also startsthe blocking workflow.

One of the two event linkages must be activated.

To enable and disable VIM workflows:

1. To open the Event Type Linkages screen, run the SWE2 transaction.

2. Create the event linkage entries shown in “Event linkages for VIM workflows”on page 30 (if not already existing) by clicking the New Entries button.

To edit an existing event linkage entry, double-click the entry.

3. To enable the workflow, select the Type linkage active check box.

To disable the workflow, clear the check box.

4. Save your changes with a transport and move this transport to subsequentsystems.

Note: Repeat the procedure for all event linkage entries shown in “Eventlinkages for VIM workflows” on page 30.



3.2.7 Maintaining the SAPscript Form for ApprovalThe SAPscript form is client-dependent. You must copy it from client 000 to allrequired clients. Perform the following steps to do a client copy of the standardSAPscript form SYSTEM to the form /ORS/SAPSCRIPT, which is used in VIMapproval.

To maintain the SAPscript form:

1. Make sure that namespace /ORS/ is modifiable.

Therefore, run the SE03 transaction, and, under Administration, run SetSystem Change Option.

The value for namespace /ORS/ must be Modifiable.

2. Run the SE71 transaction.

3. On the Utilities menu, click Copy from Client.



4. Enter values in the required fields. In Form Name, enter SYSTEM, and in TargetForm, enter /ORS/SAPSCRIPT.

5. To submit, click .

If you are asked for a package, enter /ORS/000007.

3.2.8 Maintaining Standard TextThis activity is only required if the SRM PO functionality is being implemented inVIM.

The standard text is client dependent and should be copied from client 000 to allrequired clients. Perform the following steps to do a client copy of the followingstandard text in the required languages:

• /OPT/VIM_DP_SRM_PRICE_HEADER

• /OPT/VIM_DP_SRM_QTY_FOOTER

• /OPT/VIM_DP_SRM_QTY_HEADER

• /OPT/VIM_DP_SRM_QTY_URL_HEAD

To maintain standard text:

1. Run the SO10 transaction.



2. Navigate to the menu path Utilities > Copy from Client.

Note: To copy the text in all languages at once, you can use an asterisk inthe Language field.

3. Enter values in the required fields. Text Name and Target Name must be thesame.



Click .

4. If a dialog box like the following opens, click Yes.

5. Click the Back button on the confirmation page.

6. Repeat the steps for all standard text shown in the list above.

3.2.9 Setting Background User Parameters for Non POInvoice PostingIf Non PO invoices are posted in background with an alternative BDC ID 41, it isnecessary to adjust user parameters for the background posting user, typically WF-BATCH.

To set background user parameters for Non PO invoice posting:

1. Run the SU01 transaction and open the user WF-BATCH in edit mode.

2. Enter the following parameter:

Parameter ID Parameter value

FO3 2

Note: Use O like Oscar in FO3. Note that there is a blank in front of theparameter value 2. The 2 is the second character.



3.2.10 Configuring Additional SettingsThis section lists topics that are important for post installation actions and that arealready described in other guides.

• Regarding online posting using the MIRO transaction and Enhancement Points(for ECC 6.0 version), see section 9.9.4 “Enhancing MIRO for Pre-population ofData During Online Invoice Creation” in OpenText Vendor Invoice Management forSAP Solutions - Configuration Guide (VIM-CGD).

• Regarding the configuration of BAdIs for invoice processing, see section 9.5.1“Activating BAdI for Invoice Processing” in OpenText Vendor Invoice Managementfor SAP Solutions - Configuration Guide (VIM-CGD).

Use transaction SE19 to check the runtime behavior of the BAdIs. The followingare the standard values:

BAdI Implementation Runtime behavior

/OPT/VIM_MIGO_ENH /OPT/VIM_CHECK_MIGO Implementation is called

/OPT/VIM_MIRO_ENH /OPT/VIM_CHECK_MIRO Implementation is called

/OPT/VIM_ENH_SPOT_MIRO

/OPT/CL_IM_VIM_BADI_MIRO

Implementation is notcalled



3.2.11 Installing Transports with Layout Variants for IntegratedInvoice Cockpit and IDH Admin ToolThe layouts provided in the baseline for the Integrated Invoice Cockpit and the IDHAdmin Tool are stored in the table LTDX. Due to limitations of BC set technology, theentries are not correctly entered in the table when the BC sets are activated.Therefore copy the transports D89K901617 and QW3K900246 into the transportdirectory and install the transports using STMS.

OpenText recommends setting the layout /IDH as default layout for the IDH AdminTool (transaction /OPT/VIM_7AX8; report /OPT/VIM_ICC_ADMIN_TOOL).

3.3 Language PacksLanguages for VIM 7.0 (other than English and German) are delivered in languagepacks, which you can obtain on the OpenText Knowledge Center: https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151605.

Beginning with VIM 7.0 SP2, VIM provides a cumulative language pack with everySP. You need this language pack, if you did not install the initial language pack ofthe VIM version along with the installation package. You can obtain the cumulativelanguage pack in the Knowledge Center in the folder of the respective SP.

You can import the cumulative language pack after the respective SP is installed.The initial language pack of the VIM version is not required. To import the languagepack, use the SMLT transaction. You can import the language pack multiple times forseveral languages.

VIM provides a translation guide that describes the various aspects of translatingVIM into new languages. In addition, the translation guide contains a sectionexplaining what to do if you want to use the available SAP tools “SecondaryLanguage” and “Language Supplementation” instead of translating into a newlanguage. The translation guide is available in the Knowledge Center: https://knowledge.opentext.com/knowledge/llisapi.dll/Properties/46423475

Cumulativelanguage pack

TranslationGuide





https://knowledge.opentext.com/knowledge/llisapi.dll/Properties/46423475

https://knowledge.opentext.com/knowledge/llisapi.dll/Properties/46423475

Chapter 4

Verifying Installation

Make sure that the OpenText Vendor Invoice Management add-on is reflected in theinstalled components.

To verify the installation:

1. From the SAP menu, open System > Status.

2. Click the button next to Component version.


In the System: Component information dialog, you should see the OTEXVIMadd-on component installed, with Release number 700.

Chapter 4 Verifying Installation


Chapter 5

Installing a VIM Support Package

This chapter describes the installation of a Support Package (SP) for VIM.

5.1 SAP ERP PrerequisitesMake sure that you already have installed the latest VIM SP. Any repairs made tothe VIM objects will be overwritten by the new SP.

To check the SAP ERP prerequisites:


2. Click the button next to Component version.

In the System: Component information dialog box, you should see theOTEXVIM add-on component installed, with Release number xxx_yyy wherexxx is the VIM version (for example 600) and yyy is the SAP basis componentversion.


5.2 Handling Workflow Container InconsistenciesIn certain cases, workflow containers of open VIM workflows may get inconsistentas a result of an SP installation. This can happen when a new field is introduced intoone of VIM data structures and, by some reason, it must be introduced not at the endof the structure but in the middle. OpenText tries to avoid such changes, butsometimes they cannot be avoided.

Note: If possible, finish the processing of all currently open DP documentsbefore the SP installation. Do not create new DP documents during the SPinstallation procedure.

Inconsistent data in workflow containers often results in short dumps. They happenwhen, after an SP installation, a user tries to open a work item that was createdbefore the SP installation.

To solve the problem, the workflow containers can be processed by a specialprogram provided by SAP in OSS note 910573. The program requires that a newtable is created with the same structure as the table changed in the SP installationprocess, in the version that existed in the system before the SP installation. You cannormally find the old version using ABAP dictionary version management.However, to simplify the solution of potential problems, OpenText recommends thatyou create that copy before the SP installation is started.

The only VIM database table that is currently known to cause these problems istable /OPT/VIM_1HEAD. OpenText recommends that you create a copy (for examplewith the name ZZZ1HEAD) in transaction SE11. It is important that the table copy willnot reference any include or append structures. You can achieve this by performingthe following steps:

To expand includes:

1. Copy the table /OPT/VIM_1HEAD.

2. Without activating the copy, open it in change mode.

3. Set the pointer on each include line (.INCLUDE) that is still displayed, and, onthe Edit menu, click Include > Copy Components.

Normally, all fields will be expanded at once. After this, you can activate thetable.

Chapter 5 Installing a VIM Support Package


5.3 SAP Installation1. Determine which VIM SP file is needed based upon your SAP version. For more

information, see the Release Notes for the SP.

2. Log on to the SAP server and copy the corresponding file to the followinglocation on the server: \usr\sap\trans\EPS\in.

3. Open the SAP GUI and access client 000 as the DDIC user.

4. Run the /nSPAM transaction.

5. In the Support Package Manager window, click Support Package > LoadPackages > From Application Server.

6. You are asked to confirm if you want to upload the OCS Package for the VIMSP. Click Yes.

The package is uploaded into the system, and a confirmation screen isdisplayed.

5.3. SAP Installation


7. Click the back arrow button to return to the previous screen.

8. To define the SPAM Queue, click the Display/define button.

The Component Selection window opens.

9. Scroll down until you find the OTEXVIM component and click this line.

A dialog box opens, with the OTEXVIM Patch highlighted.

10. Click the checkmark button to confirm the queue selection. The Release may bedifferent in your SAP implementation.

You now see the package name in the queue. The Status is yellow and readsNext action: Import queue.

11. In the Extras menu, click Settings.



The SPAM: Settings screen opens.

12. Click the Always radio button in the section ABAP/Screen Generation. Thenclick the confirmation checkmark.

13. In the Extras menu, click Ignore generation errors.

Note: This step is Support Package specific. Perform it if it is mentioned inthe Release Notes of the Support Package.

The Support Package may contain Data Dictionary changes that requiredatabase table conversions or other additional activities. Without performing



these additional activities, the generation will result in errors that must beignored first.

14. You are now ready to import. Click the Import Truck button to begin.

The Import Queue confirmation is displayed.

15. At this point, you can choose the Start Options, which control whether eachphase executes in a dialog process or a background process. Make yourselections and start by clicking the confirmation checkmark button.

The import starts running. If you chose to run in dialog, you see the processsteps running at the bottom of the screen. Otherwise you need to monitor thelog.

When the import has completed, you see a message Queue <queue name>imported successfully (ECC 6.0) in the dialog box.

16. Click the Checkmark button.

17. Now check the import logs for errors, code 8 or above. To display the logs, clickthe Import Log button.

18. Verify that you do not have any error codes eight (8) or above. Warning codesof four (4) are acceptable.

Note: Some objects can display generation errors. For a list of theseobjects, see the Release Notes for the SP.

19. When you have finished viewing, click the Back button.

20. To resolve the domain and tables generation errors (see Step 13 on page 45), thetable data must be converted with the SAP Database Utility (transaction SE14).Open this transaction in a new window and perform the conversion for each ofthe tables listed in the Release Notes for the SP.



21. Click Edit.

22. Select Background and Save data, and click Activate and adjust database. Youcan set the parameters of the proposed background job to immediate execution.



As soon as the jobs created this way for all tables are finished, activate thedomain /OPT/VIM_TAXRATE in the SE11 transaction. There should be no errorsin the activation log.

Note: You must perform the database adjustment in each of the systemswhere the SP is installed or transported, including the production system.

23. Return back to the SPAM transaction screen.

Now you can confirm the queue to complete the task.

24. To confirm the queue, click the checkmark icon in the application toolbar.

The SPAM status changes to a green light and the queue is cleared. Thefollowing message will appear: You have applied OTEXVIM <patch number>successfully.



Chapter 6

Upgrading

This chapter describes the upgrade procedure for both SAP ERP upgrade and VIMupgrade.

Terminology

Former versions of SAP (4.6C and 4.7) are no SAP ERP versions, but SAP R/3versions. Therefore, the wording in many locations would have to be “SAPERP or R/3” instead of “SAP ERP”. To make reading more convenient in thischapter, also the R/3 versions (4.6C and 4.7) are called “SAP ERP”.

6.1 Upgrade OverviewAn upgrade from VIM versions since 5.1.6 to VIM 7.0 is possible directly or in twosteps using a VIM 6.0 version as intermediate version.

The following tables show the details.

Table 6-1: VIM upgrades for SAP version ERP 6.0

VIM source version Recommendedstart level

Upgrade Guide

VIM 5.1.6 installed, butnot productive (or data tobe discarded)

Installation Guide VIM 7.0, “UpgradingVIM” on page 56.You must use the upgrade package, andyou must follow the post installationactivities for installation.

VIM 5.2 VIM 5.2 SP6 Installation Guide VIM 7.0, “UpgradingVIM” on page 56

VIM 6.0 VIM 6.0 SP1 Installation Guide VIM 7.0, “UpgradingVIM” on page 56

Table 6-2: Exchange upgrades for other SAP versions

Source version Recommendedstart level

Upgrade Guide

VIM 6.0 / 4.6C VIM 6.0 SP1 Installation Guide VIM 7.0, “UpgradingSAP ERP” on page 52

VIM 6.0 / 4.7 VIM 6.0 SP1 Installation Guide VIM 7.0, “UpgradingSAP ERP” on page 52

VIM 6.0 / ERP 5.0 VIM 6.0 SP1 Installation Guide VIM 7.0, “UpgradingSAP ERP” on page 52


The following 2-step upgrades have a VIM upgrade to VIM 6.0 SP1 as a first step.Perform this intermediate step completely. Activate all BC sets mentioned in theUpgrade Guide and execute all the conversion and migration tools according to theUpgrade Guide.

Table 6-3: VIM upgrades in 2 steps for SAP version ERP 6.0

Source version Intermediate step Upgrade Guide

VIM 5.1.6 productive Upgrade to VIM 6.0 SP1 VIM Upgrade Guide 5.1.6 to 6.0(https://knowledge.opentext.com/knowledge/cs.dll/properties/21388817)

Second step:VIM upgrade from 6.0 SP1to 7.0

Installation Guide VIM 7.0,“Upgrading VIM” on page 56

Table 6-4: Exchange upgrades in 2 steps for other SAP versions

Source version Intermediate step Upgrade Guide

VIM 5.1.6 / 4.6C Upgrade to VIM 6.0 SP1 VIM Upgrade Guide 5.1.6 to 6.0(https://knowledge.opentext.com/knowledge/cs.dll/properties/21388817)

VIM 5.1.6 / 4.7 Upgrade to VIM 6.0 SP1 VIM Upgrade Guide 5.1.6 to 6.0(https://knowledge.opentext.com/knowledge/cs.dll/properties/21388817)

VIM 5.1.6 / ERP 5.0 Upgrade to VIM 6.0 SP1 VIM Upgrade Guide 5.1.6 to 6.0(https://knowledge.opentext.com/knowledge/cs.dll/properties/21388817)

VIM 5.2 / 4.6C Upgrade to VIM 6.0 SP1 VIM 6.0 SP1 Release Notes (https://knowledge.opentext.com/knowledge/cs.dll/properties/19224213)

VIM 5.2 / 4.7 Upgrade to VIM 6.0 SP1 VIM 6.0 SP1 Release Notes (https://knowledge.opentext.com/knowledge/cs.dll/properties/19224213)

VIM 5.2 / ERP 5.0 Upgrade to VIM 6.0 SP1 VIM 6.0 SP1 Release Notes (https://knowledge.opentext.com/knowledge/cs.dll/properties/19224213)

Second step in all cases:Exchange upgrade fromVIM 6.0 SP1

Installation Guide VIM 7.0,“Upgrading SAP ERP”on page 52

Chapter 6 Upgrading


https://knowledge.opentext.com/knowledge/cs.dll/properties/21388817































6.2 Handling Workflow Container InconsistenciesIn certain cases, workflow containers of open VIM workflows may get inconsistentas a result of an upgrade. This can happen when a new field is introduced into oneof VIM data structures and, by some reason, it must be introduced not at the end ofthe structure but in the middle. OpenText tries to avoid such changes, butsometimes they cannot be avoided.

Notes

• If possible, finish the processing of all currently open DP documents beforeupgrading the production system. Do not create new DP documents duringthe upgrade procedure.

• For more information about upgrading, see the document “FAQ on Upgradeto 7.0”, available in the Knowledge Center: https://knowledge.opentext.com/knowledge/cs.dll/Properties/38482369

Inconsistent data in workflow containers often results in short dumps. They happenwhen, after an upgrade, a user tries to open a work item that was created before theupgrade.

To solve the problem, the workflow containers can be processed by a specialprogram provided by SAP in OSS note 910573. The program requires that a newtable is created with the same structure as the table changed in the upgrade process,in the version that existed in the system before the upgrade. You can normally findthe old version using ABAP dictionary version management. However, to simplifythe solution of potential problems, OpenText recommends that you create that copybefore the upgrade is started.

The only VIM database table that is currently known to cause these problems istable /OPT/VIM_1HEAD. OpenText recommends that you create a copy (for examplewith the name ZZZ1HEAD) in transaction SE11. It is important that the table copy willnot reference any include or append structures. You can achieve this by performingthe following steps:

To expand includes:

1. Copy the table /OPT/VIM_1HEAD.

2. Without activating the copy, open it in change mode.

3. Set the pointer on each include line (.INCLUDE) that is still displayed, and, onthe Edit menu, click Include > Copy Components.

Normally, all fields will be expanded at once. After this, you can activate thetable.

6.2. Handling Workflow Container Inconsistencies


https://knowledge.opentext.com/knowledge/cs.dll/Properties/38482369

https://knowledge.opentext.com/knowledge/cs.dll/Properties/38482369

6.3 Upgrading SAP ERPThis section discusses the process to perform during an SAP ERP upgrade withregards to VIM.

When you have to upgrade your SAP ERP system and you already installed VIMusing packages, you have to use the specific VIM SAP ERP upgrade packages.

When you upgrade an SAP release to a higher release, the system automaticallyrecognizes that an SAP add-on is installed and requests the respective upgradepackage. This way the standard SAP ERP upgrade procedure also updates the VIMadd-ons to the relevant version.

The OpenText Vendor Invoice Management package is protected with a specificpassword. During upgrade, this password is requested by the SAP Add-OnInstallation Tool (SAINT). For the SAP ERP upgrade password, see “PasswordControl” on page 14.

Prerequisites

• Support Package Manager (transaction code SPAM) level 35• Make sure the profile parameter transport/systemtype is set to CUSTOMER, not

to SAP. If it is set to SAP, you will get object generation errors.• Apply OSS note 1082597: Not enough business functions activated in SFW5; this is

used for Switch Frame Work for activating the PO based invoice parkinginfrastructure.

• Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0s ASABAP

• For a list of available software components, check OSS note 1791715: SAP InvoiceManagement by OpenText 7.0

• The following components must be installed for SAP ECC 6.0 up to EHP7:



1 700 0013 SAPKB70013

2 701 0003 SAPKB70103

3 702 0003 SAPKB70203

4 higher -

• One of the following add-on components must be installed:

• OTEXVIM 604_700• OTEXVIM 603_640• OTEXVIM 602_620

Passwordcontrol

Chapter 6 Upgrading


• OTEXVIM 601_46C

To prepare the SAP ERP upgrade:

1. Inform all users about the scheduled downtime as early as possible.

2. Before you begin the upgrade, it is recommended to perform a complete backupor to take a snapshot of the SAP ERP system.

3. Save values from PO number lists and delivery note (DN) number lists inyour /OPT/VIM_1HEAD table.

If you want to keep the values for these fields, where the PO numbers and DNnumbers for a DP document were stored as a comma-separated list, you have touse a migration program. The migration program is part of VIM 6.0 SP6 andVIM 5.2 SP11.

If you are on a lower version, you have to install transport D89K904627 (for SAP4.6C: D81K903267). You find this transport on your installation CD.

Then run report /OPT/VIM_MIGRATE_PO_DN_LISTS to store PO_LIST andDN_LIST values in the new table /OPT/VIM_1PO_DN.

You get a log with the count of resulting entries in the table /OPT/VIM_1PO_DN.

To perform the SAP ERP upgrade:

1. Copy the respective SAPCAR file (*.SAR) from the product CD to the target SAPapplication server in the \usr\sap\trans folder. This is the parent folder of theDIR_EPS_ROOT folder.

Upgrade to ECC6.0 from SAPversion

File Source path Target path

SAP ECC 5.0SAP R/3 4.7SAP R/3 4.6C

OTEXVIM_EXCH_700_700.SAR

UPGR_ERP/DATA/ \usr\sap\trans\EPS


The resulting PAT file is extracted to the EPS\in folder relative to the path of theSAPCAR file.

3. Follow the standard SAP ERP system upgrade instructions.

During the prepare phase of the SAP ERP upgrade, the Upgrade Assistantshows you the existing VIM component that is installed.

4. Select the OTEXVIM component and other components if required.

Click the OK button to continue.

6.3. Upgrading SAP ERP


5. To include the OTEXVIM exchange package, select Upgrade with SAINT package.

Click the OK button to continue.

6. In the following screen, click the OK button to continue.

7. Continue with the SAP ERP upgrade process.

ImportantIn case of an SAP ERP upgrade, do not activate BC Sets, as described in“Activating Business Configuration Sets” on page 18. If you activate BCSets, all the configuration data is overwritten with OpenText baselineconfiguration data and all custom configuration changes are lost.

At the end of the upgrade you may see the following screen.

Chapter 6 Upgrading


When checking the LONGPOST.LOG, you may discover the following errorreferencing the VIM namespace.A2PESEEF_BADI 103 BAdI implementation "/OPT/VIM_CHECK_MIRO" must still be migrated2 EPU139 Postprocessing necessary when upgrade has been completed"SEEF_BADI""103"A2WESEEF_BADI 051 Migrate implementation "/OPT/VIM_CHECK_MIRO" using transaction SPAUExecute the upgrade report "COM_PRODUCT_UPGRADE"

In transaction SPAU, you may see the /OPT/VIM_CHECK_MIGO Business Add-Insreferenced for the VIM namespace.

If the two objects are green (see screenshot above), they are active andgenerated. This is okay and can be ignored.

6.3. Upgrading SAP ERP


Run the COM_PRODUCT_UPGRADE report using transaction SE38. This report isoutlined in the “SAP ERP Central Component 6.0 SR3 ABAP Upgrade Guide”section for Follow-up Activities, 6.22 Executing Conversion Programs for theProduct Master, p. 154.

If you have errors running this program, refer to SAP notes 970046 and 1055794.

To finish the SAP ERP upgrade:

1. After the upgrade, perform the installation verifying activities, as described in“Verifying Installation“ on page 39.

2. Test the entire VIM process like for a new VIM installation.

3. When you have successfully completed all tests, inform the OpenText ProjectManager.

With this information, we can keep our customer installation database up-to-date, which helps us providing faster technical support for you.

6.4 Upgrading VIMThis section discusses the process to perform an upgrade from VIM 5.2 to VIM 7.0and from VIM 6.0 to VIM 7.0.

The OpenText Vendor Invoice Management package is protected with a specificpassword. During VIM upgrade, this password is requested by the SAP Add-OnInstallation Tool (SAINT). For passwords for a VIM upgrade, see “PasswordControl” on page 14.

Prerequisites

General prerequisites

• Apply OSS note 1082597: Not enough business functions activated in SFW5;this is used for Switch Frame Work for activating the PO based invoiceparking infrastructure.

• Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0sAS ABAP

• Apply OSS note 1462364: Dependent structure has inconsistent runtimeobject after mass activation. This is specific to SAP ECC 6.0 system, up toEHP5.

• For a list of available software components, check OSS note 1791715: SAPInvoice Management by OpenText 7.0

• The following components must be installed:

ECC 6.0

Component SAP_BASISLevel: 700

Passwordcontrol

Chapter 6 Upgrading


• The following components must be installed for SAP ECC 6.0 up to EHP7:



1 700 0013 SAPKB70013

2 701 0003 SAPKB70103

3 702 0003 SAPKB70203

4 higher -

• Support Package Manager (transaction code SPAM) level 35• The following add-on component must be installed:

OTEXVIM 520_700 or OTEXVIM 604_700

VIM versionUpgrade to VIM 7.0 is supported with minimal versions of VIM 5.2 SP6 or VIM6.0 SP1. If you have a lower support package level within VIM 5.2 or VIM 6.0,you must upgrade to the required SP level first, and activate the BC setsdelivered with the SPs.

Direct upgrade from VIM 5.1.6 is not supported. You can upgrade from VIM5.1.6 to VIM 6.0 SP1 and then go on to VIM 7.0.

To check the version of VIM, open System > Status from the SAP menu andcheck the Component Version.

For more details, see “Verifying Installation“ on page 39. The followingscreenshots show system component information with the required minimumSP levels of OTEXVIM.

6.4. Upgrading VIM


Adjust SAINT tool settingsIn the settings of the SAINT tool, make sure that ABAP/Screen Generation is setto Always.

Chapter 6 Upgrading


To prepare the VIM upgrade:

1. Inform all users about the scheduled VIM downtime as early as possible.

Users must not perform any actions on the Accounts Payable module; thatmeans, the entire VIM processes must not be performed.

2. Before you begin the update, perform a complete backup or take a snapshot ofthe SAP ERP system.

3. Make sure the namespaces /OPT/, /ORS/, and /PTGWFI/ are modifiable:

a. Run the SE06 transaction.

b. Click System change option in the application tool bar.

c. In the Namespace/Name Range list, change the namespaces /OPT/, /ORS/,and /PTGWFI/ to Modifiable and save.

4. Save values from PO number lists and delivery note (DN) number lists inyour /OPT/VIM_1HEAD table.

If you want to keep the values for these fields, where the PO numbers and DNnumbers for a DP document were stored as a comma-separated list, you have touse a migration program. The migration program is part of VIM 6.0 SP6 andVIM 5.2 SP11.

If you are on a lower version, you have to install transport D89K904627. Youfind this transport on your installation CD.

Then run report /OPT/VIM_MIGRATE_PO_DN_LISTS to store PO_LIST andDN_LIST values in the new table /OPT/VIM_1PO_DN.

You get a log with the count of resulting entries in the table /OPT/VIM_1PO_DN.

To perform the VIM upgrade:

When you have to upgrade VIM and you already installed VIM using packages, youhave to use the specific VIM upgrade packages.

1. Copy the respective SAPCAR file (*.SAR) from the product CD to the target SAPapplication server in the \usr\sap\trans folder. This is the parent folder of theDIR_EPS_ROOT folder.

6.4. Upgrading VIM


SAP ERP system File Source path Target path

SAP ECC 6.0 OTEXVIM_UPGR_700_700.SAR

UPGR_VIM/DATA/ \usr\sap\trans\EPS




4. Continue the Add On process by selecting Add On OTEXVIM.

Click the Continue button.

5. When the Add Modification Adjustment Transports to the Queue message isdisplayed, click the No button to continue.

6. When you are prompted for the password, enter the password as provided in“Password Control” on page 14.


Chapter 6 Upgrading


7. Make sure that Start options is set to Start in dialog immediately forPreparation and Continue in Dialog immediately for Import 1, Import 2,and Clean Up.


A message is displayed, confirming the successful import.

8. Check in the SAINT tool if the package has been imported successfully with thenew release number. See “Verifying Installation“ on page 39 for specific releasenumber.

To finish the VIM upgrade:

1. If you need login languages other than English and German, install thelanguage packs for the languages you need. For more information, see“Language Packs” on page 38.

6.4. Upgrading VIM


2. Install the most recent VIM 7.0 Support Package (SP). You find the SPs in theKnowledge Center: https://knowledge.opentext.com/knowledge/cs.dll/Open/10151605. For further information, see the Release Notes of the respective SP.

3. After the upgrade, perform/verify all the post installation activities as describedin “Post Installation Activities After an Upgrade” on page 62.

ImportantDo not activate the BC Sets for first installation, as described in“Activating Business Configuration Sets” on page 18. If you activatethese BC Sets, all the configuration data is overwritten with OpenTextbaseline configuration data and all custom configuration changes arelost.

4. Test the entire VIM process like for a new VIM installation.

5. When you have successfully completed all tests, inform the OpenText ProjectManager.

With this information, we can keep our customer installation database up-to-date, which helps us providing faster technical support for you.

6.5 Post Installation Activities After an UpgradeTo ensure the integrity of the installed transports, you must perform and validatethe following procedures:

• “Activating Business Configuration Sets” on page 63• “Maintaining Number Ranges After Upgrade” on page 63• “Checking the BTE Handler Modules Configuration” on page 63• “Checking Status and Runtime Behavior of BAdIs for Invoice Processing”

on page 64• “Installing Transport with Layout Variant for IDH Admin Tool” on page 64• “Populating Invoice Transaction Field VORGANG for Credit Memos”

on page 65• “Removing Obsolete User Process Option 2742” on page 65

Chapter 6 Upgrading




6.5.1 Activating Business Configuration SetsNote: Check the tables in /OTEXVIM/VIM70_BASELINE_<xxx> (see thefollowing list) using the Compare button ( ) in the SCPR20 transaction, anddecide if it is appropriate to activate this BC Set. Save and export the log file toa local file. To keep the color information, use export format Rich textformat. Differences between existing tables and BC sets are marked in yellow.After activating the BC set you might want to set some customizing entriesback to the old values.

The business configuration sets (BC Sets) for post installation activities after anupgrade are the following:

/OTEXVIM/VIM70_BASELINE_52_60_DActivate this BC Set if your source system for the upgrade is VIM 5.2. If you getan activation error, ignore it.

/OTEXVIM/VIM70_BASELINE_LOWSP_DActivate this BC Set if your source system for the upgrade is lower than VIM 5.2SP8 or VIM 6.0 SP3 respectively. If you get an activation error, ignore it.

/OTEXVIM/VIM70_BASELINE_NEWFOR70Activate this BC Set in any case. You should not have activation errors here. Ifyou have activation errors, repeat the activation. If you still have activationerrors, you have to find out the reason. You can ignore activation errors like Nodata found for writing activation links for object <xxx>.

6.5.2 Maintaining Number Ranges After UpgradeFollow the procedures given in “Maintaining Number Ranges” on page 27 toconfigure the number range for the new number range object /OPT/REGID.

6.5.3 Checking the BTE Handler Modules ConfigurationIn VIM 7.0, all BTE handler modules are registered as partner modules. In earlierVIM version, the modules were registered as customer modules.

Check the following settings:

In the BF32 transaction, the 6 VIM events should be configured; see the followingscreenshot.

6.5. Post Installation Activities After an Upgrade


Check with the BF34 transaction, if these events occur in the customer section. If yes,remove them.

In the BF42 transaction, the VIM process RWBAPI01 should be configured; see thefollowing screenshot.

Check with the BF44 transaction, if this process occurs in the customer section. If yes,remove it.

6.5.4 Checking Status and Runtime Behavior of BAdIs forInvoice ProcessingUse transaction SE19 to check the runtime behavior of the BAdIs. The following arethe standard values:

BAdI Implementation Runtime behavior

/OPT/VIM_MIGO_ENH /OPT/VIM_CHECK_MIGO Implementation is called

/OPT/VIM_MIRO_ENH /OPT/VIM_CHECK_MIRO Implementation is called

/OPT/VIM_ENH_SPOT_MIRO

/OPT/CL_IM_VIM_BADI_MIRO Implementation is notcalled

To prevent the activation of BAdI /OPT/VIM_ENH_SPOT_MIRO, leave the PlannedStatus for Business Function /OPT/VIM_SFW_MIRO empty (in the SFW5 transaction).

6.5.5 Installing Transport with Layout Variant for IDH AdminToolThe layout provided in the baseline for the IDH Admin Tool is stored in table LTDX.Due to limitations of BC set technology, the entries are not correctly entered in thetable when the BC sets are activated. Therefore copy the transport QW3K900246 intothe transport directory and install the transport using STMS.

OpenText recommends setting the layout /IDH as default layout for the IDH AdminTool (transaction /OPT/VIM_7AX8; report /OPT/VIM_ICC_ADMIN_TOOL).

Chapter 6 Upgrading


6.5.6 Populating Invoice Transaction Field VORGANG forCredit MemosIn VIM 7.0, a new field VORGANG was introduced in the /OPT/VIM_1HEAD table. Thenew field gives room for the classification of invoice / credit memo / subsequentdebit / subsequent credit, which is used in PO invoices.

After an upgrade, the VORGANG field is empty for all invoices. To make its valueconsistent with the CREDIT_MEMO field, run the program /OPT/VIM_UPDATE_VORGANG_FOR_CM.

The program will set the VORGANG field to 2 for every document in the DP workflowwith CREDIT_MEMO flag selected.

6.5.7 Removing Obsolete User Process Option 2742In VIM 6.0, process option 2742 was used as a user process option, but it is notneeded anymore. In VIM 7.0, process option 2742 was reused and renamed to IDHTrigger.

This is not designed as a user process option but it still occurs in some process typesand must be removed.

To do this, run the program /OPT/VIM_PURGE_PROCESS_OPTIONS.

6.5. Post Installation Activities After an Upgrade


Chapter 7

Troubleshooting

7.1 FAQsThe following FAQs cover basic troubleshooting information.

Does VIM consist of any standard SAP objects/repairs?No

Does VIM consist of any Z objects?No

How do I check whether installation is successful?Refer to “Verifying Installation“ on page 39.

What is the namespace?SAP assigns name spaces for its partners; by doing so the changes to these objectsare protected.

Can I repair the OpenText objects?It is not recommended to repair OpenText objects. [email protected] before making any repairs; OpenText might havealready issued a patch for the intended repair and the same functionality can beachieved by using appropriate user exits.

There is an error when starting the workflow.Make sure the standard task is defined as a general task.


Part 3KPI Dashboard Installation

This part describes the installation and post installation activities needed for the“Key Performance Indicator” Dashboard KPI Dashboard. The KPI Dashboard is atool for managers showing VIM related process data at a glance in graphical charts.For further information, see section 25 “KPI Dashboard” in OpenText Vendor InvoiceManagement for SAP Solutions - Configuration Guide (VIM-CGD).

Notes

• The KPI Dashboard is an optional component.• If you are not using the KPI Dashboard, you can skip this part.

Part 3 KPI Dashboard Installation


Chapter 8

Installing the KPI Dashboard

The KPI Dashboard is installed together with the VIM Basis package.


Chapter 9

Post Installation Activities

The following activities are needed to configure the KPI Dashboard on your system.

9.1 Activating the SAP Web Dynpro ServiceThe settings in this section are necessary to activate the SAP Web Dynpro service.

Prerequisites

There are specific OpenText name spaces that have to be modifiable in order tochange the service settings. So first check with transaction SE03

Navigate to Transport Organizer Tool > Administration > Set System ChangeOption

Make sure, the Open Text Name space / Prefix /OPT and /ORS are set to Modifiable.After you have finished the customizing of services, change back the settings.


To activate the service:

1. To activate the Web Dynpro service on the SAP ERP system, run the SICFtransaction.

2. In Virtual Host, enter default_host and click Execute.

3. In the tree, select sap > bc > webdynpro.

Chapter 9 Post Installation Activities


4. Highlight vim_kpi_MAIN and, on the menu, click Service/Host > Activate.

5. Highlight vim_kpi_MAIN and double-click to change the service settings.

Continue with “To configure time out settings:“ on page 76.

9.1. Activating the SAP Web Dynpro Service


To configure time out settings:

1. Configure the Session Timeout to a reasonable time limit, for example 5minutes..

If a user has an open KPI Dashboard, does nothing for a couple of minutes andthen tries to change a filter or category, a timeout error occurs. As long as thetime without activity is shorter than the session timeout parameter, no error willoccur.

2. Save the changes and leave the service maintenance.

Error Handling

You can customize a few default pages for error handling in the Web Dynproservice.

Error pages are shown for defined reasons; for example, if the timeout is reached forthe web session. The default setting is to show SAP standard error pages.

You can change these settings for the following use cases:



• Logon Errors• Application Errors• Logoff Page• Not Accessible

9.1. Activating the SAP Web Dynpro Service


9.2 Setting the Connection for the SAP Web DynproServiceYou activate the SSL connection for Web Dynpro by configuring the SAP Web AS, asdescribed in the SAP help: http://help.sap.com/saphelp_nw04s/helpdata/en/65/6a563cef658a06e10000000a11405a/frameset.htm

Do not change the service settings described in “Activating the SAP Web DynproService” on page 73. Make sure that the SSL settings are not activated in the LogonData tab.



http://help.sap.com/saphelp_nw04s/helpdata/en/65/6a563cef658a06e10000000a11405a/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/65/6a563cef658a06e10000000a11405a/frameset.htm

Change the KPI constant DASHBOARD_START_URL to https://xxxxx:8443/xxxx. Seesection 25.4.10.5 “KPI Dashboard Start URL” in OpenText Vendor Invoice Managementfor SAP Solutions - Configuration Guide (VIM-CGD).

9.3 Setting Up the SAP NetWeaver Portal IntegrationUse Internet Explorer 8 (or higher) for setting up the SAP NetWeaver® Portalintegration for the KPI Dashboard on NetWeaver 7.0 and login to the SAPNetWeaver Portal as Administrator.

A System Object is needed to integrate the KPI Dashboard in the SAP NetWeaverPortal. The System Object is a set of connection properties to represent an external orSAP system (SAP R3, CRM, BW) used to retrieve data into portal iViews. If notexisting, you must create a System Object in the NetWeaver Portal.

9.3.1 PrerequisitesThis example shows the customizing for the connection to a specific ABAP® system.

To customize the connection to an ABAP system:

1. In the SAP NetWeaver Portal, navigate to System Administration > SystemConfiguration > System Landscape > Browse > Portal Content > Systemlandscape.

2. System Alias settings

In the Display drop down list, select System Aliases. The System Alias Editoris displayed.

Enter the Alias name: Generally it reads <SID>CLNT<CLIENTNO>; for example:BI7CLNT100.

Click the Add button and save.

3. Connector settings

In the Display drop down list, select Object, and then, in the PropertyCategory drop down list, select Connector.

Provide minimum connector properties for example. See the followingscreenshot for example values.

9.3. Setting Up the SAP NetWeaver Portal Integration


4. ITS settings

ITS settings are maintained for displaying SAP transactions in the portal as aniView.

In the Display drop down list, select Object, and then, in the PropertyCategory drop down list, select Internet Transaction Server (ITS).

Provide ITS properties as shown in the following screenshot.



The property values to enter can be read from the ABAP system usingtransactions SICF and SMICM.

For a detailed description how to set up the System Object in the Portal, seehttp://wiki.sdn.sap.com/wiki/display/EP/How+to+Create+System+Object+in+the+Portal+for+Connecting+to+SAP+backend+System.

9.3.2 Adding the Portal Component

To add the Portal component:

1. In the SAP NetWeaver Portal, navigate to Content Administration > PortalContent > Browse > Portal-Content.

2. Choose a folder or generate a new folder. To select the iView object, right-clickthe folder and select new > iView.

3. In the Display drop down list, select Object, and then, in the PropertyCategory drop down list, select Content - Web Dynpro.

Provide properties as shown in the following screenshot.

9.3. Setting Up the SAP NetWeaver Portal Integration


http://wiki.sdn.sap.com/wiki/display/EP/How+to+Create+System+Object+in+the+Portal+for+Connecting+to+SAP+backend+System

http://wiki.sdn.sap.com/wiki/display/EP/How+to+Create+System+Object+in+the+Portal+for+Connecting+to+SAP+backend+System

Check also other properties for design or layout, and customize them if needed.

4. To test the newly generated iView object, click the Preview button. If everythingis customized correctly, a separate window opens and shows the KPIDashboard content in the iView.



Part 4OpenText Approval Portal Installation

This part describes the installation of the OpenText Approval Portal component. TheApproval Portal is designed to work within SAP NetWeaver Application Server Java(NWAS) 7.0 or 7.3 or SAP NetWeaver Portal (NWP) 7.0 or 7.3.

With VIM 7.0 SP4 and higher, NWAS 7.4 and NWP 7.4 are also supported.

The Approval Portal can be deployed as a standalone application residing on NWASonly or as an application inside NWP using AppIntegrator iView. Install all thecomponents in a coordinated manner.

Notes

• The Approval Portal is an optional component.• If you are not using the Approval Portal, you can skip this part.• Please refer to section 12 “Administering the Approval Portal” in OpenText

Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-AGD) for administering and troubleshooting the Approval Portal.

• You might want to install multiple instances of the Approval Portal on thesame SAP NetWeaver Portal. In this case, contact OpenText CustomerSupport.

Part 4 OpenText Approval Portal Installation


Chapter 10


10.1 Installation PrerequisitesA complete installation and configuration of OpenText Vendor Invoice Managementfor SAP Solutions is needed for installing and testing the Approval Portal. Althoughit is possible to install the Approval Portal before the installation and configurationof the SAP ERP component, you will not be able to verify if the installation of theApproval Portal is completed and correct.

Server

Web Application ServerSAP NetWeaver Application Server Java (NWAS) 7.0 SP9 or above withSPNegoLoginModule and NWAS 7.3 SP3 or above. For SPNego configuration,see SAP Note 1488409.

With VIM 7.0 SP4 and higher, NWAS 7.4 SP3 or above is also supported.

SAP NetWeaver PortalSAP NetWeaver Portal (NWP) 7.0 SP9 or above and NWP 7.3 SP3 or above.

With VIM 7.0 SP4 and higher, NWP 7.4 SP3 or above is also supported.

Notes

• The requirement “SPx or above” does also refer to the EhP level.• For further information, see the SAP Note: 994791-SPNego Wizard.

The following list shows the supported resolution modes that have been tested inthe OpenText R&D lab. The resolution modes have been tested in all supportedbrowsers.

1. 1280 x 800 - Laptop view2. 1920 x 1080 - Laptop view3. 1680 x 1050 - Desktop view4. 1280 x 1024 - Desktop view

The following matrix shows the web browsers and versions that are supported bythe new interface of the Approval Portal, which is delivered since VIM 7.0 SP2. Thematrix is based on tests performed at OpenText R&D Lab. It considers accessibilityand usability aspects.

Note: The old interface of the Approval Portal supports only Internet Explorer7.0, 8.0, and 9.0.

RecommendedScreen

Resolution

Web browsers


With VIM 7.0 SP4 and above, the old interface of the Approval Portal alsosupports Internet Explorer 10.0 and 11.0.

ServerBrowser and Version

IE9 IE10 Firefox > 17 Chrome > 22 Safari > 5.0

NWAS 7.0

NWAS 7.3

NWAS 7.4(with VIM 7.0SP4)

NWP 7.0

NWP 7.3

NWP 7.4 (withVIM 7.0 SP4)

The Approval Portal supports Windows, Unix and other operating systemssupported by SAP.

There is no restriction which Windows or Unix versions or patch levels aresupported. Approval Portal supports all versions.

Note: The new Approval Portal has not been tested in Unix environment.

Aligned with SAP operating system support, see the SAP Product AvailabilityMatrix (PAM) for more details.

OpenText recommends implementing SSL (HTTPS) if security is a concern. BasicAuthentication in SPNego is using Base64 encryption which can be easily decrypted.See http://msdn.microsoft.com/en-us/library/aa292114(VS.71).aspx for furtherinformation.

Standard sizing requirements for NWAS or NWP 7.0 apply.

A SAP CPIC user in the SAP ERP server

The communication with the SAP ERP system is accomplished by using a CPIC userID. However, the Web user is recorded as the agent who approved an invoice, notthe CPIC user.

User typeCommunication Data (CPIC)

ProfileCreate a profile with the following authorization objects and add it to the CPICuser:

Operatingsystems

SSL

Sizing require-ments

SAP user



http://msdn.microsoft.com/en-us/library/aa292114(VS.71).aspx

Object: S_RFC

ActivityExecute (16)

Names of RFC to be protected/OPT/VIM_FG1A2, /ORS/*, /OPT/*, /ORS/SAPL000007_APPR_SCREEN, /PTGWFI/*, OPTB, ARFC, ERFC, RFC1, SDIFRUNTIME, SUNI, SYST, SYSU

RFC_TYPEFUGR (Function Group)

Object: S_CPIC

ActivityAccept, Initialize (37 and 51)

Name of an ABAP/4 FORM routineCPIC

Symbolic destination*

If you wish to narrow this down, examine table TXCOM and choose entryunder the SDEST field that represents the destination of the system you arecommunicating with.

Program Names with Search Help/ORS/*, /OPT/*, /PTGWFI/*

Object: S_DATASET (Authorization for file access)

ActivityRead, Write (33 and 34)

Filename* (physical file name)

Program Names with Search Help/ORS/*, /OPT/*, /PTGWFI/*

The following 2 authorization objects for the CPIC user are applicable for SAPERP 702 SP14 and higher and SAP NetWeaver Portal 702 SP15 and higher:

Object: S_RZL_ADM (Authorization object for R/3 system administration)

ActivityDisplay (03)

Object: S_WF_SUBST (Workflow: substitute rule)

ActivityDisplay (03)

Additional SAP Standard Profile needed: S_A.CPIC and S_A.USER

Note: If you are using an Archive Server to pull in images, you may needto assign additional roles. See the Archive Server Installation manual.

10.1. Installation Prerequisites


Example: OpenText Archive Server provides the following profiles that need to beassigned to the CPIC user to access images:

• S_AL_ADMLO (Display SAP ArchiveLink® administrator)• S_AL_ADMDE (Delete ArchiveLink administrator)

DefaultsDecimal notation should be 1,234,567.89.

Note: For SAP ERP systems with EHP5 or higher, one additional authorizationis required for the CPIC user.

S_WF_WI

Classification of tasks*

Activities12 (Resubmit work item)

Work item typeW – Dialog work item

10.2 Installation ComponentsBoth Software Component Archive (.sca) file and Software Deployment Archive(.sda) file are supplied; you can choose which format is suitable for your situation.Each file contains the following:

• SAP NetWeaver Application Server Java components• Java Enterprise archive (.ear file) - for the actual J2EE application

VIM 7.0 SPx installation packages for old and new interface

For all Support Packages of VIM 7.0 (SP2 and higher), the respective OpenTextVendor Invoice Management 7.0 Support Package folder in the KnowledgeCenter (accessible via https://knowledge.opentext.com/knowledge/cs.dll/Open/32893475) provides two installation packages of the VIM 7.0 SPx ApprovalPortal in the Web and Mobile Approval Component folder: one for the newuser interface (which is introduced with VIM 7.0 SP2), and one for the old userinterface.





10.3 System ArchitectureThis section explains the overall system architecture of the Approval Portal. There isone main component of the product:

• Java Application (.ear file) which is the Approval Portal application.

The Software Component Archive (.sca) file or Software Deployment Archive(.sda) file will be deployed using SAP Software Deployment Manager (SDM).

There are 2 ways to configure the Approval Portal application. It can be deployed:

• as a standalone J2EE application residing on NWAS only utilizing integratedauthentication

• as an application inside NWP using AppIntegrator iView

The following diagrams show the architecture for each scenario:

10.3. System Architecture


Figure 10-1: Approval Portal architecture with NWAS

The SAP help pages linked in the following discuss some of the communicationchannels between each component:

• Simple and Protected GSS API Negotiation Mechanism (SPNEGO) (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/4bd58c6c5e5f34e10000000a1553f6/frameset.htm)

• Network and Transport Layer Security (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/3a/7cddde33ff05cae10000000a128c20/frameset.htm)

• SAP Java Connector (JCO) (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/6f/1bd5c6a85b11d6b28500508b5d5211/content.htm)



http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/4bd58c6c5e5f34e10000000a1553f6/frameset.htm




http://help.sap.com/saphelp_nw70ehp1/helpdata/en/3a/7cddde33ff05cae10000000a128c20/frameset.htm



http://help.sap.com/saphelp_nw70ehp1/helpdata/en/6f/1bd5c6a85b11d6b28500508b5d5211/content.htm



Figure 10-2: Approval Portal architecture with NWP

10.3.1 SAP User RequirementsFor the SAP user, the following log in properties are required for the OpenTextApproval Portal:

Standalone J2EE application residing on NWAS only utilizing integratedauthentication

No need for SAP GUI Logon ID. Only network ID is required.

Application inside NWP using AppIntegrator iViewNo need for SAP GUI Logon ID. Only Portal ID is required.

Dual Stack installation (SAP ABAP and Java Stack) utilizing integratedauthentication

SAP GUI Logon ID required. Dual Stack forces to use SAP user managementbased on ABAP Stack.

10.3. System Architecture


Standalone J2EE application residing on NWAS with NWP utilizing integratedauthentication by accessing application directly without iView

No need for SAP GUI Logon ID; only network ID is required.



Chapter 11

Installing the Approval Portal

11.1 Preparing the InstallationTo prepare the installation, perform the following steps:

1. Deploy application specific files to serverTo gain access to the file system, sign on to the host server as a user withadministrator rights.Extract the files from opentext.zip from the delivery to a folder on the server.

ImportantOpenText recommends you to create and deploy to the folder usr/sap/<SID>/SYS/global/opentext/invoiceCfg. This is the default locationfor putting the application configuration file. If you deploy to anotherlocation, you will have to manually add a startup parameter in theConfig Tool to tell the application where to look for the configurationfiles. This will also require restarting the SAP NetWeaver ApplicationServer Java (NWAS). See Step 2 on page 94 for details.<SID> is the system ID of the NWAS. Example: T39.

Example: E:\usr\sap\T39\SYS\global\opentext\invoiceCfg

This folder is referenced as <Approval_Portal_installdir> in the following.The <Approval_Portal_installdir> folder contains the following files:

configuration.xmlcontaining all the configuration for the application

mobileconfiguration.xmlcontaining all the configuration for mobile support

RequestMappings.xmlOpenText strictly recommends not to modify this file. The Approval Portalapplication internally uses this file.

Lang_Support.propertiescontaining all the mapping of languages code; see section 12.3.2“Configuring Additional Languages” in OpenText Vendor InvoiceManagement for SAP Solutions - Administration Guide (VIM-AGD) for details.

Lang_DE.propertiescontaining all the text for the German language resource

Lang_EN.propertiescontaining all the text for the English language resource


Lang_ES.propertiescontaining all the text for the Spanish language resource

Lang_FR.propertiescontaining all the text for the French language resource

Lang_IT.propertiescontaining all the text for the Italian language resource

Lang_JA.propertiescontaining all the text for the Japanese language resource

Lang_NL.propertiescontaining all the text for the Dutch language resource

Lang_PT.propertiescontaining all the text for the Portuguese language resource

Lang_RU.propertiescontaining all the text for the Russian language resource

Lang_ZH.propertiescontaining all the text for the Chinese language resource

There might be more .properties files, depending on the package and therelease for additional languages. The language resource files can be changed.See section 12.3.1 “Changing Language Resources” in OpenText Vendor InvoiceManagement for SAP Solutions - Administration Guide (VIM-AGD) for details.

ImportantMake sure the <Approval_Portal_installdir> folder has:

• correct permissions for the J2EE application to write and read

• Full Control permission to the J2EE Engine service user (or toEveryone)

2. Optional: Invoke the J2EE Config Tool

ImportantThis step is only needed if you deploy the configuration files to alocation other than the folder usr/sap/<SID>/SYS/global/opentext/invoiceCfg.

If you deploy to another location than usr/sap/<SID>/SYS/global/opentext/invoiceCfg, you must add a startup parameter in theConfig Tool, manually, to tell the application where to look for theconfiguration files.

You find the Config Tool in the following directory: usr/sap/<SID>/<INSTANCE_NAME>/j2ee/configtool.

Chapter 11 Installing the Approval Portal


Notes

• SID is the system ID of the NWAS (example O15).• INSTANCE_NAME is the NWAS instance in the format of JCxx, wherexx is the instance number (example JC00).

The script file is:

• configtool.bat for Windows hosts

• configtool.sh for Unix hosts

a. Add the startup parameter to the Java parameters on the server: -Dcom.opentext.vim.portal.invoiceCfg=<Approval_Portal_installdir>.

Example: -Dcom.opentext.vim.portal.invoiceCfg=c:/opentext/invoiceCfg

b. Save the new parameter.

3. To apply the new startup parameter, restart the NWAS.

Restarting informs the server that the <Approval_Portal_installdir> foldercontains application specific information.

11.1. Preparing the Installation


11.2 Configuring the Administrator RoleImportantThis section is only needed if you are installing as a standalone J2EEapplication residing on NWAS only utilizing integrated authentication.

This section describes the installation activities to assign the administrator role to theuser for the Approval Portal application. As the Administrator, you must login tothe Administrator page to perform some application configuration and to performother administration tasks. See section 12 “Administering the Approval Portal” inOpenText Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-AGD) for additional information.

11.2.1 Configuring the Administrator Role for Access ThroughNWASThis section describes how to create a VIM administrator role and assign it to thedomain user through NWAS Visual Administrator. For a description of thenecessary steps with SAP NetWeaver 7.3 and 7.4, see “Configuring theAdministrator Role for Access Through NWAS for SAP NetWeaver 7.3 and 7.4”on page 99.

You must perform this configuration before deploying the .sca or .sda, to ensurethat the application recognizes the role.

To create the Administrator role:

1. Log in to J2EE Visual Administrator and navigate to Instance > Server >Services > Security Provider.

2. Click on the Edit button.



3. Click the Runtime tab > Policy Configurations tab > Security Roles tab.

4. To enable editing, click the Edit button.

5. Click the Add button.

6. In the Add Security Role dialog box, enter the role name:com.opentext.vim.portal.administrator.

Note: The role name is case-sensitive.

Click OK.

To assign the role to the domain administrator user:

1. Select the role you have newly created.

2. Click the Add button which is on the right hand side next to Users.

11.2. Configuring the Administrator Role


3. In the Choose Users or Groups dialog box, type the domain user to whom youwant to assign the administrator role.

4. Click on Search.

5. Select the user.

6. Click OK.

7. To change back to Read-only mode, click the Edit button.

To verify the configuration of the administrator role:

Note: Check this after you have deployed the .SCA or .SDA file, see“Deploying the Software Component Archive” on page 101.

• Navigate to http://<NWAS>:<NWASPORT>/vimportal/admin.



If you see a screen similar to the one above, you have configured theadministrator role successfully.

11.2.2 Configuring the Administrator Role for Access ThroughNWAS for SAP NetWeaver 7.3 and 7.4This configuration is mandatory if you have NetWeaver 7.3 or 7.4 Portal, but youwant to access the Portal application using a normal web browser. If you want tolaunch the Portal Application using NetWeaver 7.3 or 7.4 Portal, you can skip thissection.

To configure the administrator role for access through NWAS for SAPNetWeaver 7.3 and 7.4:

1. Log in to SAP NetWeaver Administrator and navigate to Configuration >Identity Management

11.2. Configuring the Administrator Role


2. Change Search Criteria to Role and click Create Role.

3. In Unique Name, enter com.opentext.vim.portal.administrator, and enteran optional Description.

4. Click the Assigned Users tab and perform a search. Select the user and clickAdd.

5. Save your settings.



11.3 Deploying the Software Component ArchiveDeploying the Software Component Archive comprises the following steps:

• “Connecting to the SAP Software Deployment Manager (SDM) for SAPNetWeaver 7.0” on page 101

• “Deploying the .sca File or .sda File” on page 102

• “Checking Correct Deployment” on page 103

• “Optional: Starting the Approval Portal J2EE Application Manually”on page 105

11.3.1 Connecting to the SAP Software Deployment Manager(SDM) for SAP NetWeaver 7.0

You deploy the Software Component Archive, using the SAP Software DeploymentManager (SDM).

Refer to the SAP help on SDM for more details on how to use SDM.

To connect to SDM:

1. To gain access to the file system, sign on to the host server as a user withadministrator rights.

2. Make sure the .sca (Software Component Archive) or .sda (SoftwareDeployment Archive) file is on a medium, for example, a CD drive, or a shareddirectory, accessible from the host server.

3. Connect to the SAP Software Deployment Manager (SDM):

You find SDM in the following directory: usr/sap/<SID>/<INSTANCE_NAME>/SDM/program.

Notes

• SID is the system ID of the NWAS (example O15).

• INSTANCE_NAME is the NWAS instance in the format of JCxx, wherexx is the instance number (example JC00).

The script file is:

• RemoteGui.bat for Windows hosts

• RemoteGui.sh for Unix hosts

11.3. Deploying the Software Component Archive


11.3.2 Deploying the .sca File or .sda FileIf there is a previous version of the Approval Portal, remove it before you continue.Refer to “Uninstalling the Approval Portal“ on page 143 for further information.

To deploy the .sca file or .sda file:

1. In SDM, click the Deployment tab.

2. Click the Add SCA/SDA icon ( ) to add the .sca or .sda file to thedeployment list.Which one to use depends on your requirements. Both of them will work.

3. In the Choose window, navigate to the IM_APPROVAL_PORTAL7_0.sca orIM_APPROVAL_PORTAL7_0.sda file.

Note: The filename might be different.

4. Click Choose.

5. Click Next to finish step 1 of 4 of deployment.

6. In step 2 of 4 of deployment, click Next to continue.

7. In step 3 of 4 of deployment, click Start Deployment to continue.

8. Wait until deployment is finished.



9. In step 4 of 4 of deployment, click Confirm to continue and finish deployment.

11.3.3 Checking Correct DeploymentTo check whether the Approval Portal is deployed correctly, perform the followingprocedure:

To check correct deployment of the Approval Portal:

1. In the SDM, click the SDM Repository tab and expand SAPJ2EEEngine.

IM_APPROVAL_PORTAL should be displayed under SAPJ2EEEngine. The versionnumber might be displayed, as well.

Note: If IM_APPROVAL_PORTAL is not displayed, use this Installation Guideto check if anything is wrong or redo the installation.

2. To check the J2EE application from NWAS, navigate to http://<NWAS>:<NWASPORT>/vimportal.

11.3. Deploying the Software Component Archive


You will see OpenText Approval error messages. This is correct as you have notdone any configuration yet.

3. Check the J2EE application:

Open the J2EE Visual Administrator.

a. Click on a server.b. Expand Services.c. Expand Deploy.

d. In the Deployed Components pane, expand sevlet_jsp.

opentext.com/IM_APPROVAL_PORTAL should be displayed.

Note: If opentext.com/IM_APPROVAL_PORTAL is not displayed, usethis Installation Guide to check if anything is wrong or redo theinstallation.



11.3.4 Optional: Starting the Approval Portal J2EE ApplicationManually

By deploying through SDM, the Approval Portal J2EE application will startautomatically. If the Approval Portal J2EE application doesn't, you can start itmanually.

To start the Approval Portal J2EE application manually:

1. Click on a server.

2. Expand Services.

3. Expand Deploy.

See screenshot in Step 3 on page 104.

4. In the Deployed Components pane, expand sevlet_jsp.

5. Click on opentext.com/IM_APPROVAL_PORTAL.

6. Click the Start Application button on the right.

7. Select the server(s) you want to start and click OK.

11.4 Deploying the Software Component Archive withSAP NetWeaver 7.3 and 7.4To deploy the Software Component Archive with SAP NetWeaver 7.3 and 7.4:

1. Make sure the .sca file is placed in D:\usr\sap\trans\EPS\in.

2. To start the Java Support Package Manager, navigate to usr/sap/<SID>/<INSTANCE_NAME>/j2ee/jspm

Notes

• SID is the system ID of the NWAS (example O15).

• INSTANCE_NAME is the NWAS instance in the format of JCxx, wherexx is the instance number (example JC00).

The script file is:

• go.bat for Windows hosts

• go.sh for Unix hosts

3. Enter user name and password.

11.4. Deploying the Software Component Archive with SAP NetWeaver 7.3 and 7.4


4. Click New Software Components, and then click Next.

If the component is already deployed, no applicable software component isfound.

If the component is not yet deployed, click Next to deploy the component.



5. Click Start.

11.4. Deploying the Software Component Archive with SAP NetWeaver 7.3 and 7.4


6. In the Completed screen, click Exit.



Chapter 12

Configuring SAP NetWeaver Portal Components

If you are deploying the Approval Portal on SAP NetWeaver Application ServerJava (NWAS) and the users are accessing the application through SAP NetWeaverPortal, you must configure the SAP NetWeaver Portal components.

For a description of the configuration with SAP NetWeaver 7.3 and 7.4, see“Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4”on page 115 and “Creating Roles for Users with SAP NetWeaver 7.3 and 7.4”on page 129.

Note: For information on how to change the title of the iView, page, workset,or role, refer to the SAP NetWeaver Portal Administration Guide from SAP.

As the SAP NetWeaver Portal administrator, you create the Appintegrator iView. Tomake the application available for SAP NetWeaver Portal users, you have toperform the following steps:

• “Creating AppIntegrator IViews for Users” on page 109

• “Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4”on page 115

• “Creating Roles for Users” on page 125

• “Creating Roles for Users with SAP NetWeaver 7.3 and 7.4” on page 129

• “Assigning Roles to SAP NetWeaver Portal Users” on page 132

• “Configuring IViews and Roles for the Administrator” on page 133

• “Administering the OpenText Approval Portal” on page 134

12.1 Creating AppIntegrator IViews for UsersConsult your corporate policy on the location and the naming conventions ofcreating iViews.

To create AppIntegrator iViews for users:

1. Login to SAP NetWeaver Portal as Administrator and expand Portal Content >Content Provided by Other Vendor.

2. Create a folder under End User Content or under another location, if wanted.


3. Right-click on the new folder and select New > iView.

Chapter 12 Configuring SAP NetWeaver Portal Components


4. In the iView wizard, click Portal Component – create an iView from a portalcomponent ... and click Next.

5. In Step 1: Portal Archive Selection, click com.sap.portal.appintegrator.sap andclick Next.

12.1. Creating AppIntegrator IViews for Users


6. In Step 2: Portal Component Selection, click Generic and click Next.

7. In Step 3: General Properties, enter the following parameters:

• iView Name (mandatory)

• iView ID (mandatory)

• iView ID Prefix



• Description

Select the Master Language (mandatory).

Click Next.

8. In Step 4: Summary, click Finish to finish the initial iView creation.

9. Click Open the object for editing and click OK.

12.1. Creating AppIntegrator IViews for Users


10. In Property Editor, scroll to the Entry Point line and click Yes.

Scroll to the HTTP Request Method line and select HTTP:GET.

Click Save.

11. In Property Editor, scroll to the URL Template line.

Enter the following value:

http://$host$:$port$/vimportal/?urlView=Y&PORTALUSER=<User.UserID>

Change host and port accordingly:



$host$NWAS server name where the Approval Portal J2EE application wasdeployed

$port$Port of that NWAS

Note: Do not change <User.UserID>.

12. Click Save and Close.

The creation of the AppIntegrator iView is now finished.

12.2 Creating AppIntegrator IViews for Users withSAP NetWeaver 7.3 and 7.4Consult your corporate policy on the location and the naming conventions ofcreating iViews.

To create AppIntegrator iViews for users with NetWeaver 7.3 and 7.4:

1. Login to SAP NetWeaver Portal as Administrator.

2. To create a new folder, navigate to Content Administration > Portal ContentManagement > Portal Content > Content Provided by SAP > End UserContent.

12.2. Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4


3. Right-click End User Content, point to New, and then click Folder.



4. On the New Folder tab, enter Folder Name and Folder ID Prefix (for example,com.opentext); then click Finish at the bottom of the page.

5. After creating the Approval Portal folder, navigate to Content Administration> Portal Content Management > Portal Content > Portal Applications



6. In Portal Applications, expand com.sap.portal.appintegrator.sap



7. Right-click the Generic template. In the context menu, click Copy.

8. Navigate to Portal Content > Content Provided by SAP > End User Content.

9. In the Approval Portal folder, paste the Generic iView as PCD Object. See thefollowing screenshot.



The wizard of the PCD Object opens.



10. Change the Object Name to Approval Portal Iview.

Click Next, then click Finish.

An iView is created.



11. To configure the newly created iView, right-click ApprovalPortalIview, thenclick Open > Properties.



12. On the Approval Portal Iview tab, click All.

13. From the Show Category list, select Content - Generic Launcher.



14. Configure the following parameters:

HTTP Request MethodHTTP GET

URL Templatehttp://<host name>:<port number>/vimportal/?urlView=Y&PORTALUSER=<User.UserID>

The URL is different for the Admin iView:

http://<host name>:<port number>/vimportal/admin?urlView=Y&PORTALUSER=<User.UserID>

Enter the following values:

<host name>Name of the NWAS where the Approval Portal J2EE application wasdeployed.

<port number>Port of that NWAS.

Note: Do not change <User.UserID>.

15. From the Show Category list, select Navigation.

To make the iView visible, select the Entry Point check box.



12.3 Creating Roles for UsersAfter creating a new AppIntegrator iView, you must create a role and add theAppIntegrator iView to the role.

To create roles for users:

1. In the SAP NetWeaver Portal, navigate to the folder you created in “CreatingAppIntegrator IViews for Users” on page 109.

2. Right-click on the folder, select New > Role.

12.3. Creating Roles for Users


3. In Step 1, enter Role Name, Role ID, Role ID Prefix and Description.

Select the Master Language.

Notes

• See also Step 7 on page 112 in “Creating AppIntegrator IViews forUsers” on page 109.

• Role ID Prefix is not mandatory. If you enter this parameter, you mustsearch by giving Role ID Prefix and Role Name when assigning the roleto the user.

4. Click Next.



5. Click Finish.

6. Click Open the object for editing and click OK.

12.3. Creating Roles for Users


7. In Property Editor, scroll to the Entry Point line and click Yes.

Click Save.

8. Select the AppIntegrator iView created in “Creating AppIntegrator IViews forUsers” on page 109, right-click the iView and select Add iView to Role > DeltaLink.

Click Save.

The AppIntegrator iView is added to the role.

9. Click Close.



12.4 Creating Roles for Users with SAP NetWeaver 7.3and 7.4After creating a new AppIntegrator iView, you must create a role and add theAppIntegrator iView to the role.

To create roles for users with SAP NetWeaver 7.3 and 7.4:

1. In the SAP NetWeaver Portal, navigate to the Approval Portal folder; see“Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4”on page 115.

2. Right-click on the folder, select New > Role > Freestyle Role.

12.4. Creating Roles for Users with SAP NetWeaver 7.3 and 7.4


3. Enter properties as shown in the screenshot above: Role Name, Role ID, RoleID Prefix and Description.

Select the Master Language.

Note: Role ID Prefix is not mandatory. If you enter this parameter, youmust search by giving Role ID Prefix and Role Name when assigning therole to the user.

4. Click Finish.



5. To edit the properties of the created role, click Properties.

6. Enter the Name (as shown in the screenshot) and select the Entry Point checkmark.

Click Save.

12.4. Creating Roles for Users with SAP NetWeaver 7.3 and 7.4


7. Select the AppIntegrator iView created in “Creating AppIntegrator IViews forUsers with SAP NetWeaver 7.3 and 7.4” on page 115, right-click the iView andselect Add iView to Role > Delta Link.

Click Save.

The AppIntegrator iView is added to the role.

8. Click Close.

12.5 Assigning Roles to SAP NetWeaver Portal UsersAfter creating AppIntegrator iViews and adding them to roles, you must assign theroles to the SAP NetWeaver Portal users.

To assign roles to SAP NetWeaver Portal users:

1. In the SAP NetWeaver Portal, click User Administration > IdentityManagement.

2. In the Search Criteria, enter the users or groups you want to assign to the newrole (created in “Creating Roles for Users” on page 125).

Click Go.

3. In the Details of User panel, click the Assigned Roles tab.

4. Click Modify.

5. In the Search Criteria field, search for the new role you created and click Go.

6. Select the new role and click Add.

You can see the role in the Assigned Roles tab.

7. Click Save.

The following screenshot shows a role being assigned to a demo coder.



12.6 Configuring IViews and Roles for theAdministratorConfiguring iViews and roles for the administrator is almost the same as for users.See sections for different NetWeaver versions above.

You can use Approval Admin for the iView Name and Approval Admin Role for therole.

The only difference from the user configuration is the URL template:

http://$host$:$port$/vimportal/admin?urlView=Y&PORTALUSER=<User.UserID>

See Step 11 on page 114 for details on the URL template for users.

12.6. Configuring IViews and Roles for the Administrator


Once you have finished the creation of the Administrator iView and the role, assignit to the appropriate administrators, as described in “Assigning Roles to SAPNetWeaver Portal Users” on page 132.

When you, as the administrator, navigate to the Approval Admin iView, it will looklike the following screenshot:

You have now finished the installation and configuration of the OpenText ApprovalPortal.

12.7 Administering the OpenText Approval PortalFor information on the administration of the Approval Portal, see section 12“Administering the Approval Portal” in OpenText Vendor Invoice Management for SAPSolutions - Administration Guide (VIM-AGD).



Chapter 13

Applying a New Patch

Note: Unlike the VIM SAP ERP component, the Approval Portal is a build andhas no dependencies of previous patches or support packages. You canuninstall the previous version and directly install the newest version withoutapplying the patches in between. However, the patch or build needs to matchto the VIM SAP ERP component. Approval Portal 7.0 will only work with theVIM 7.0 SAP ERP component.

New .sca file or .sda fileFollow the steps to undeploy the .sca or .sda file in “Uninstalling UsingSoftware Deployment Manager” on page 143, and then follow the steps todeploy the .sca file or .sda file in “Deploying the .sca File or .sda File”on page 102.

New <language>.properties filesExtract the new <language>.properties files from the media to<Approval_Portal_installdir> and perform the Reinitialize Application task. Seesection 12 “Administering the Approval Portal” in OpenText Vendor InvoiceManagement for SAP Solutions - Administration Guide (VIM-AGD) for more details.


Chapter 14

Upgrading the Approval Portal from PreviousVersions

You can upgrade the Approval Portal from version 5.2 to 7.0 and from version 6.0 to7.0.

Approval Portal 7.0 uses an additional xml file (RequestMappings.xml), which isnot available in Approval Portal 5.2 and 6.0. Therefore, if you want to upgrade fromApproval Portal 5.2 or 6.0, you must update the existing 5.2 or 6.0 installationdirectory with the 7.0 installation directory.

Make sure that all files mentioned in opentext.zip are deployed correctly.

You can reuse the original configuration.xml file as there are no changes; but it isbest to make a backup of the configuration.xml.

If you changed the language properties files from the previous version and wouldlike to reuse them in VIM 7.0, change the new language properties files manually.

To upgrade, perform the actions described in “Applying a New Patch“ on page 135.


Chapter 15

Troubleshooting

For information on troubleshooting the Approval Portal, see section 29.11“Troubleshooting” in OpenText Vendor Invoice Management for SAP Solutions -Administration Guide (VIM-AGD).


Chapter 16

Supporting Installation of the Standalone NWASPortal and Mobile Approval Portal on Unix or Linux

This chapter provides instructions how to enable the installation of the standaloneNWAS Portal and Mobile Approval Portal on Unix or Linux operating systems.

The Configuration tab of the Approval Portal Administration console provides aDomain input field to accept the authentication domain for users. The setting of thisfield is applied to all Approval Portal and Mobile Approval Portal users.

To support Unix or Linux operating systems, you must maintain the Domain fieldwith the same value, as maintained in the Windows Domain column in the COAtable. For details about the COA configuration, see section 5.5.1 “User Details View”in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).

Example: If the Windows Domain column in the COA table is not maintained for users,leave the Domain field in the Configuration tab of the Approval Portal Administrationconsole empty as well.


Chapter 17

Uninstalling the Approval Portal

To uninstall the Approval Portal, perform the following steps:

• “Uninstalling Using Software Deployment Manager” on page 143• “Uninstalling with SAP NetWeaver 7.3 and 7.4” on page 144• “Removing SAP NetWeaver Portal Components” on page 145• “Deleting Properties Files” on page 146• “Optional: Removing the Startup Parameter in the Config Tool” on page 146

17.1 Uninstalling Using Software DeploymentManagerThis section describes how to uninstall the .epa and .ear files from the SAPSoftware Deployment Manager (SDM) repository. For a description of uninstallingwith SAP NetWeaver 7.3 and 7.4, see “Uninstalling with SAP NetWeaver 7.3 and7.4” on page 144.

To uninstall files from the SDM repository:

1. Connect to the SAP Software Deployment Manager (SDM) in the host server:

You find SDM in the following directory: usr/sap/<SID>/<INSTANCE_NAME>/SDM/program.

Notes


The script file is:

• RemoteGui.bat for Windows hosts

• RemoteGui.sh for Unix hosts

Refer to the Software Deployment Manager Guide for more details on how touse SDM.

2. In SDM, click the Undeployment tab.

3. Find and click IM_APPROVAL_PORTAL.

4. Click Select.


5. Click Start Undeployment.

In Step 2 of 2, you see the progress.

6. To finish the undeployment, click Confirm.

opentext.com\IM_APPROVAL_PORTAL should no longer appear in the VisualAdministrator.

17.2 Uninstalling with SAP NetWeaver 7.3 and 7.4This section describes how to undeploy the Approval Portal with SAP NetWeaver7.3 and 7.4.

To undeploy the Approval Portal with SAP NetWeaver 7.3 and 7.4:

1. Navigate to D:\usr\sap\W73\J00\j2ee\console\ and run guiconsole.bat.

2. Enter user name and password.

3. In the J2EE Engine Console, type list_app to view the list of components thatare deployed.

4. To undeploy, run the following command:

undeploy name=IM_APPROVAL_PORTAL7_0 vendor=opentext.com

After undeployment, a success message is displayed.

Chapter 17 Uninstalling the Approval Portal


17.3 Removing SAP NetWeaver Portal ComponentsThis section describes how to remove iViews, pages, worksets and roles from theSAP NetWeaver Portal content.

Note: First, unassign the role if you already have assigned it to a user.

To remove SAP NetWeaver Portal components:

1. Login to the SAP NetWeaver Portal as SAP NetWeaver Portal Administrator.

2. Click Content Administration.

3. Expand Portal Content.

4. Navigate to the folder that was created in “Creating AppIntegrator IViews forUsers” on page 109.

17.3. Removing SAP NetWeaver Portal Components


Right-click the folder and click Delete.

5. In the Delete Confirmation page, click Finish.

The “OpenText Approval Portal” folder is now deleted.

17.4 Deleting Properties FilesAt this stage of the uninstallation process, delete the folder that contains theproperties files. The default folder name is usr/sap/<SID>/SYS/global/opentext/invoiceCfg, where <SID> is the system ID of the SAPNetWeaver Application Server Java (NWAS). See “Preparing the Installation”on page 93 for details on the properties files.

17.5 Optional: Removing the Startup Parameter in theConfig Tool

Note: This section is only relevant if you have added a startup parameter inthe Config Tool, see Step 2 on page 94 in “Preparing the Installation”on page 93.

Removing the startup parameter, using the J2EE Config Tool, finishes theuninstallation process.

To remove the startup parameter:

1. Invoke the J2EE Config Tool:

You find the Config Tool in the following directory: usr/sap/<SID>/<INSTANCE_NAME>/j2ee/configtool.

Notes


The script file is:

Chapter 17 Uninstalling the Approval Portal


• configtool.bat for Windows hosts

• configtool.sh for Unix hosts

2. Remove the startup parameter:

-Dcom.opentext.vim.portal.invoiceCfg=<Approval_Portal_installdir>.

Example: -Dcom.opentext.vim.portal.invoiceCfg=c:/opentext/invoiceCfg


4. Restart the NWAS to remove the startup parameter.

The uninstallation is now completed.

17.5. Optional: Removing the Startup Parameter in the Config Tool


Part 5Mobile Approval Portal Installation

This part describes the installation of the Mobile Approval Portal, which is anenhancement to the Invoice Approval. Users can approve their invoices, using amobile device, for example a Blackberry, an iPhone, or an iPad. The MobileApproval Portal is based on HTML5.

Note: The Mobile Approval Portal is an optional component. If you are notusing the Mobile Approval Portal, you can skip this part.

For information on the configuration of the Mobile Approval Portal, see section 13“Configuring the Mobile Approval Portal” in OpenText Vendor Invoice Managementfor SAP Solutions - Administration Guide (VIM-AGD).

Part 5 Mobile Approval Portal Installation


Chapter 18

Introduction to the Mobile Approval Portal

A mobile application (Mobile Approval Portal) is available as a new SAP mobilesolution for VIM. Using the Mobile Approval Portal, users can perform theirapproval tasks in a simple GUI, directly on their mobile device.

The Mobile Approval Portal component in VIM 7.0 is enhanced with the mobilecapabilities Sencha Touch. This enriches the look and feel on the supported mobileplatforms. For detailed information about Sencha Touch, see http://www.sencha.com/products/touch/features/.

The Mobile Approval Portal supports Windows, Unix and other operating systemssupported by SAP.

There is no restriction which Windows or Unix versions or patch levels aresupported. Mobile Approval Portal supports all versions. Aligned with SAPoperating system support, see the SAP Product Availability Matrix (PAM) for moredetails.

The following table shows which mobile operating systems, devices, and browsersare fully supported:

VIM 7.0 adds the new column Category which signifies Performance, Usability/Accessibility and Document Viewing aspects, ranked from A to C. A, B, and C arerankings from top to bottom on the mentioned aspects. These ranks are providedbased on testing in OpenText Mobile lab with real devices and simulators.

Mobile OperatingSystem

Device Browser Category

iOS (5.1.x or higher) iPad Safari (5.1.x or higher) A

iOS (5.1.x or higher) iPhone Safari (5.1.x or higher) A

BlackBerry (BB OS 10) BlackBerry BlackBerry OS 10browser

C

Android (4.0.x orhigher)

Any Android device[a] Chrome (23.0 or higher)and Supportedbrowsers

B

WindowsPhone (8 orhigher)

Any WindowsPhonedevice

Internet Explorermobile version (10 orhigher)

B

[a] In general, you can view the Mobile Approval Portal inside the browser on all kind of Android devices.Due to the diversity of physical Android devices, OpenText cannot guarantee 100% compatibility on allfunctionality that the Mobile Approval Portal offers.

Operatingsystems


http://www.sencha.com/products/touch/features/

http://www.sencha.com/products/touch/features/

Mobile Approval Portal users can display invoices using OpenText Imaging WebViewer. Web Viewer is a web application for displaying and printing documents inWeb-based scenarios and for appending comments to these documents. Thedocuments may be stored in OpenText Archive Server or other repositories.

The Web Viewer integration is completed for the invoice document and supports alldocuments supported by Web Viewer.

On the Mobile Browser without Web Viewer, it is not possible to render TIFFdocuments. JPG, PNG and GIF documents are supported to be shown in browser bydefault. To support PDF documents, a specific browser-plugin or a separate viewerapp is needed.

However, Web Viewer is able to display TIFF documents on the Mobile Browser onMobile Approval Portal.

Web Viewer is installed on a web server. It generates HTML pages containing thedocument to be displayed and sends them to the browser. The Web Viewer can beused by any leading application server configured appropriately.

Web Viewer supports documents from the following products:

• OpenText Archiving and Document Access for SAP Solutions• OpenText DocuLink for SAP Solutions

Limitations

• Web Viewer does not support MS Office documents.• For attachments, the Web Viewer integration is not implemented. Any attached

document, like PDF, JPEG, GIF or PNG, will be forced to open in a separatebrowser window by default.

Notes

• OpenText strongly recommends that you implement Web Viewer to displayimages on the Mobile Approval Portal.

• For further information about Web Viewer, see OpenText Imaging Web Viewer- Installation and Configuration Guide (CLWEBV-IGD).

Web Viewerintegration

Chapter 18 Introduction to the Mobile Approval Portal


Figure 18-1: HTML5 Mobile Approval Portal Architecture


Chapter 19

Authentication for the Mobile Approval Portal

This section describes the communication and authentication needed for the MobileApproval Portal.

The Mobile Approval Portal uses domain authentication. It can be accessed usingWiFi or VPN on the same network or on an external network.

To access from external network without WiFi or VPN, keep the Mobile ApprovalPortal URL in the DMZ and connect with Virtual Host. This requires IT help toconfigure the URL in the DMZ.

Note: For security reasons and also to grant stable access to the MobileApproval Portal, OpenText recommends that you use a VPN connection.

The detail authentication mechanism is the same as for the Approval Portal, forexample, which SSO mechanism is used. See “Preparing Installation“ on page 85


Chapter 20

Installing Web Viewer for the Mobile ApprovalPortal

OpenText Imaging Web Viewer can be integrated in the Mobile Approval Portal. Toensure security for the Web Viewer integration, OpenText recommends that youverify the “Use Signature” setting in /IXOS/OA_CUST_A with the followingprerequisites:

• OTEXBAS 10.0 SP2

• OpenText Imaging Web Viewer 10.2.0 Patch-004 (Patch = WEV-1020-004) orhigher.

Note: OpenText Imaging Web Viewer 10.2.0 SP1 = Patch-005,WEV-1020-005

• OpenText Archive Services Patch ASR-1021-007 or higher (as included inEnterprise Library 10.2.1 Patch Collection 1021_2012_04)

Note: See also the Release Notes of OpenText Archiving and Document Accessfor SAP Solutions 10.0 SP2.

Web Viewer version 10.5.0 will be supported with a later Support Package.

The Mobile Approval Portal supports Windows, Unix and other operating systemssupported by SAP. For the Web Viewer installation, see the appropriate section insection 3 “Installing Web Viewer” in OpenText Imaging Web Viewer - Installation andConfiguration Guide (CLWEBV-IGD).

To install Web Viewer 10.2.0, download the software from the following location:http://knowledge.opentext.com/knowledge/cs.dll/Open/19642255.

To apply patch 004 (or higher) for Web Viewer 10.2.0, download the software fromthe following location: https://knowledge.opentext.com/knowledge/cs.dll/Open/22422170

Notes

• OpenText recommends that you use the latest patch of the supported WebViewer software version.

• OpenText also recommends installing Web Viewer on a NetWeaver 7.3 or 7.4instance where Mobile Approval Portal is not running or on a supportedTomcat version. This approach improves the performance of viewing invoiceimages on Mobile devices.


http://knowledge.opentext.com/knowledge/cs.dll/Open/19642255



• OpenText also recommends installing Web Viewer on the same domain asthe Archive Server and SAP NetWeaver Application Server Java.

Chapter 20 Installing Web Viewer for the Mobile Approval Portal


Chapter 21

Installing the Mobile Approval Portal

Installing the Mobile Approval Portal differs depending on the application serveryou use:

• Standalone SAP NetWeaver Application Server Java (NWAS)• SAP NetWeaver Portal

21.1 Installing the Mobile Approval Portal onStandalone NWAS 7.0/7.3/7.4For a new standalone NWAS 7.0/7.3 (or 7.4, with VIM 7.0 SP4 and higher)installation, refer to “Preparing Installation“ on page 85. If the SAP standaloneNWAS 7.0/7.3 (or 7.4, with VIM 7.0 SP4 and higher) is already in place, skip thisstep.

The Mobile Approval Portal software component is packaged along with theApproval Portal component. The installation of the Mobile Approval Portal issimilar to Approval Portal. Refer to “Installing the Approval Portal“ on page 93.

21.2 Installing the Mobile Approval Portal on SAPNetWeaver Portal 7.0/7.3/7.4For a new SAP NetWeaver Portal 7.0/7.3 (or 7.4, with VIM 7.0 SP4 and higher)installation, refer to “Preparing Installation“ on page 85. If the SAP NetWeaverPortal 7.0/7.3 (or 7.4, with VIM 7.0 SP4 and higher) is already in place, skip this step.

The Mobile Approval Portal software component is packaged along with theApproval Portal component. The installation of the Mobile Approval Portal issimilar to Approval Portal. Refer to “Installing the Approval Portal“ on page 93.

21.2.1 PrerequisitesThe following versions are supported:

SAP NetWeaver Portal7.0 SP8 or higher

All higher support packages and enhancement packages of NetWeaver 7.0, 7.3,and 7.4

Approval Portal7.0


21.2.2 Scenario 1: Enabling Mobile Approval Portal forExisting Customers Running on SAP NetWeaver Portal1. Un-deploy the existing Approval Portal.

2. For SAP NetWeaver Portal 7.0/7.3/7.4 customers, deploy/configure the SPNegologin module.

Mobile Approval Portal uses SSO with the SPNego Login Module. Therefore, itis only supported on SAP standalone NWAS 7.0/7.3/7.4. If you are already onSAP NetWeaver Portal 7.0/7.3/7.4, and you want to have Mobile ApprovalPortal support, install the standalone NWAS (AS JAVA) component also on SAPNetWeaver Portal 7.0/7.3/7.4. This means, both AS JAVA and EP Core should beavailable on the NetWeaver instance.

Refer to “Installing the Mobile Approval Portal on Standalone NWAS7.0/7.3/7.4” on page 159 for specific SAP NetWeaver Portal versions.

3. Deploy the Approval Portal with the officially supported Support Package.

4. Access the Mobile Approval Portal URL in a supported smartphone / tablet.

21.2.3 Scenario 2: Enabling Mobile Approval Portal for NewCustomers1. For SAP NetWeaver Portal 7.0/7.3/7.4 customers, deploy/configure the SPNego

login module.

Refer to “Installing the Mobile Approval Portal on Standalone NWAS7.0/7.3/7.4” on page 159 for specific SAP NetWeaver Portal versions.

2. Deploy the Approval Portal with the officially supported Support Package.

3. Access the Mobile Approval Portal URL in a supported smartphone / tablet.

Chapter 21 Installing the Mobile Approval Portal


Part 6Vendor Invoice Management SAP CRM SAP

Shared Service Framework ComponentInstallation

This part describes the installation of the Vendor Invoice Management SAP CRMSAP Shared Service Framework component.

Part 6 Vendor Invoice Management SAP CRM SAPShared Service Framework Component Installation


Chapter 22


22.1 Password ControlThe OpenText Vendor Invoice Management package is protected with a specificpassword. During installation, this password is requested by the SAP Add-OnInstallation Tool (SAINT). For the VIM SAP CRM SAP Shared Service Frameworkinstallation package, the password is 316C596F6A.

22.2 Checking PrerequisitesThe following prerequisites must be fulfilled for the installation of the SAP SharedService Framework integration.


• In-depth knowledge of SAP administration tasks, in particular the SAP Add-OnInstallation Tool (SAINT) and CRM Add-On Installation


22.2.2 SAP CRM EHP1 PrerequisitesCheck the following prerequisites prior to installation:

• Support Package Manager (transaction code SPAM) level 38• For a list of available software components, check OSS note 1791715: SAP Invoice


The following components must be installed for SAP CRM 7.0 EHP1:

Component SAP_ABALevel: 702

Component BBPCRMLevel: 701


The following support packages must be installed:

SAPKA70203 (ABA), SAPKB70203 (BASIS)









The following support packages must be installed:

SAPKA73102 (ABA), SAPKB73102 (BASIS), SAPKU70202 (CRM)








The following support packages must be installed: SAPKB74003 (BASIS),SAPKA74003 (ABA), SAPKU71301 (CRM)



22.2.5 Activating Shared Service FrameworkIndependently from the EHP version, the following steps to activate the SharedService Framework are always required.

To activate Shared Service Framework using Switch Framework:

1. Run the SFW5 transaction.

2. Expand the ENTERPRISE_BUSINESS_FUNCTIONS node, select the PlannedStatus check box for business functions CRM_IC_CEBP & CRM_SHSVC andclick the Activate Changes icon.


On the product CD, the single PAT files are archived in SAPCAR files (extension*.SAR) that can be extracted using the SAPCAR command line tool.

22.2. Checking Prerequisites


Chapter 23


This chapter describes the installation of the Basis package of Vendor InvoiceManagement (VIM) on an SAP CRM application server.

The basic components are installed with the Basis package.



SAP CRM version

• SAP CRM 7.0 EHP1

• SAP CRM 7.0 EHP2: Additional step needed, see Step 3 on page 167

• SAP CRM 7.0 EHP3: Additional step needed, see Step 3 on page 167

FileOTVIMSSF_INST_VIM701_702.SAR

Source pathINST_CRM_700/DATA/

Target path\usr\sap\trans\EPS

2. Extract the SAPCAR file to the \usr\sap\trans\EPS\in folder with thefollowing command:

SAPCAR -xvf <name of SAPCAR file>

The resulting PAT file will be extracted to the EPS\in folder relative to the pathof the SAPCAR file.

3. Only if you install on SAP CRM 7.0 EHP2 or SAP CRM 7.0 EHP3:

An ACP file is necessary. The ACP file is available in SAP Marketplace asAttribute Change Package 01 for OTVIMSSF 701_702.

Extract the CSR0120031469_0080724.PAT file from theCSR0120031469_0080724.zip folder and copy it to the \usr\sap\trans\EPS\in folder.



Chapter 24


To put the SAP Shared Service Framework integration into operation, you mustperform the following post installation tasks:

• “Activating Business Configuration Sets in the CRM System” on page 169

• “Maintaining a Logical System for the CRM System in VIM” on page 173

• “Installing Support Packages 1 and 2” on page 173

24.1 Activating Business Configuration Sets in theCRM System

Notes

• For every client, you must activate new BC Sets after installing VIM 6.0CRM.

• You need the appropriate security authorization to run some of thetransactions.

You activate the BC Sets in the following steps:

1. Apply recommended user settings

2. Activate BC Set /OTVIMSSF/VIM60_SSF_CUSTOMIZING

Note: Check the tables in /OTVIMSSF/VIM60_SSF_CUSTOMIZING and decideif it is appropriate to activate this BC Set.

Activate the BC set in the Configuration client of the development system andcreate a transport from BC set activation, move the transport to the requiredsystems.

Do not activate the BC set in the production system. Create a customizationtransport in the development system configuration client by activating the BCset and move it to the desired systems.

To apply recommended user settings:


From the Utilities menu, click User Settings.


VIM 7.0 supports the following languages:

• Chinese

• Dutch

• English

• French

• German

• Hungarian

• Italian

• Japanese

• Portuguese

• Romanian

• Russian

• Spanish



New languages for VIM 7.0 are the following:

• Czech

• Polish

• Turkish

To select your applicable languages, select the respective check box in theManual Selection column.

2. Click the Maint. Transaction tab.

Apply the settings, as shown in the screenshot.

3. To copy the settings, click .

You are now ready to activate the BC set.

To activate BC Sets:


24.1. Activating Business Configuration Sets in the CRM System


2. Enter the BC set name /OTVIMSSF/VIM60_SSF_CUSTOMIZING and click theActivate button (highlighted in the screenshot.

Note: If you are prompted to create a new transport, follow your standardchange request process for tracking changes.

3. Apply the recommended settings, as shown in the screenshot.

4. Click the Activate button.

Tip: You can skip any warnings during the activation.

After successful BC Set activation, a message is displayed in the lower left of theSAP GUI: Activation ended with additional information.



24.2 Maintaining a Logical System for the CRMSystem in VIMTo integrate the VIM SAP CRM SAP Shared Service Framework component into theVIM SAP ERP component, you must maintain a logical system for the CRM systemin the backend ERP system (VIM SAP ERP component system). Support for SAPCRM SAP Shared Service Framework will only be activated if the logical system ofthe CRM is maintained. This setting generates the Service Requests button in thedashboards and the Create SR check box in the process type definition.

To maintain a logical system for the CRM system in the SAP ERP system:

1. In VIM, run the /N/OPT/SPRO transaction and navigate to the menu pathVendor Invoice Management > Cross Component Configuration > CRMIntegration > Maintain CRM Logical System.

2. Enter the logical system for the CRM system in the Constant Value field.


24.3 Installing Support Packages 1 and 2When you have finished the package installation, use the SPAM transaction to installthe Support Packages 1 and 2. See the instructions in Release Notes OpenTextVendor Invoice Management 6.0 CRM SSF SP1.pdf and Release Notes OpenTextVIM 60 CRM SSF SP2.pdf; available in the Knowledge Center: https://knowledge.opentext.com/knowledge/cs.dll/Open/19229480

24.2. Maintaining a Logical System for the CRM System in VIM




Chapter 25

Verifying Installation

Make sure that the OpenText Vendor Invoice Management CRM add-on is reflectedin the installed components.



2. Click next to Component version.


In the System: Component information dialog box, you should see theOTVIMSSF add-on component installed, with Release number 701_702 andpatch level 0002.

Chapter 25 Verifying Installation


Part 7Vendor Invoice Management SAPNetWeaver Business Warehouse

Component Installation

This part describes the installation of the Vendor Invoice Management SAPNetWeaver Business Warehouse (VIM BW) component.

Part 7 Vendor Invoice Management SAP NetWeaverBusiness Warehouse Component Installation


Chapter 26


26.1 Password ControlThe OpenText Vendor Invoice Management package is protected with a specificpassword. During installation, this password is requested by the SAP Add-OnInstallation Tool (SAINT). The following table shows the passwords for the VIM 7.0BW installation package:

SAP_BASIS Password

700 F17CB370FA

730 F17CB070FA

26.2 Checking PrerequisitesThe following prerequisites must be fulfilled for the installation of the VIM BWcomponent.

26.2.1 Required Knowledge

The following knowledge is required for the person dealing with the installation asdescribed in this document:



26.2.2 VIM 7.0 BW Prerequisites

Check the following prerequisites prior to installation:

• Support Package Manager (transaction code SPAM) level 39

• See OSS note 1791715: SAP Invoice Management by OpenText 7.0

• For SAP NetWeaver BW 7.3 only: Implement OSS note 1636155: 730SP6: Error‘RSTRAN 510’ while activating Transformation (if not yet in the system withSP6)

• The following components must be installed for SAP NetWeaver BW 7.x:


Table 26-1: SAP NetWeaver BW 7.0 / SAP NetWeaver BW 7.3 EHP1 / SAPNetWeaver BW 7.4

Option Component: SAP_BW Component: SAP_BASIS

Release Support Package Release Support Package

1 700 SAPKW70023 700 SAPKB70013

2 731 SAPKW73103 731 ----

3 740 ---- 740 ----

Table 26-2: SAP NetWeaver BW 7.3

Option Component: SAP_BW Component: SAP_BASIS


1 730 SAPKW73001 730 SAPKB73001

• The Add-On BI_CONT ‘Business Intelligence Content’ must be installed in asuitable version, for example:

• BI_CONT 705 for SAP NetWeaver BW 7.0• BI_CONT 736 for SAP NetWeaver BW 7.3• BI_CONT 747 for SAP NetWeaver BW 7.3 EHP1• BI_CONT 757 for SAP NetWeaver BW 7.4


On the product CD, the single PAT files are archived in SAPCAR files (extension*.SAR) that can be extracted using the SAPCAR command line tool.



Chapter 27


This chapter describes the installation of the Basis package of VIM on an SAPNetWeaver BW application server.

The basic components of VIM SAP NetWeaver BW are installed with the Basispackage.



SAP NetWeaver BW 7.0 / SAP NetWeaver BW 7.3 EHP1

FileOTVIMBW_INST_VIM700_700.SAR

Source pathINST_BW_700/DATA/


SAP NetWeaver BW 7.3

FileOTVIMBW_INST_VIM700_730.SAR

Source pathINST_BW_730/DATA/


2. Extract the SAPCAR file to the \usr\sap\trans\EPS\in folder with thefollowing command:

SAPCAR -xvf <name of SAPCAR file>


3. Call transaction SAINT (in client 000). You get an initial screen, which shows theinstalled components.

Click Start to add the VIM 7.0 BW component.


4. Click Start to see the screen that presents the packages ready to be installed.



5. Choose the package for component OTVIMBW. Carry out the import of thepackage as described in the respective SAP documentation.


Chapter 28

Verifying the Installation

Make sure that the VIM BW add-on is reflected in the installed components.





In the System: Component information dialog box, you should see the OTVIMBWadd-on component installed, with Release number 700.

Chapter 28 Verifying the Installation


Chapter 29

Upgrading SAP NetWeaver BW

The following upgrades are supported by exchange packages:

• Upgrade from SAP NetWeaver BW 7.0 to SAP NetWeaver BW 7.3

Source Path File Name Password

UPGR_BW_730/DATA/ OTVIMBW_EXCH_700_730.SAR F17CB076ED

• Upgrade from SAP NetWeaver BW 7.3 to SAP NetWeaver BW 7.3 EHP 1

Source Path File Name Password

UPGR_BW_731/DATA/ OTVIMBW_EXCH_700_731.SAR F17CB376ED

The following upgrade does not need an exchange package:

• Upgrade from SAP NetWeaver BW 7.0 to SAP NetWeaver BW 7.3 EHP 1


Part 8Vendor Invoice Management SAPNetWeaver Gateway Component

Installation

This part describes the installation of the Vendor Invoice Management SAPNetWeaver Gateway (VIM GW) component. The VIM GW component is needed torun the Supplier Self Service component, which is introduced with VIM 7.0 SP3.

Figure 4: Supplier Self Service architecture

Part 8 Vendor Invoice Management SAP NetWeaverGateway Component Installation


Chapter 30


30.1 Password ControlThe OpenText Vendor Invoice Management package is protected with a specificpassword. During installation, this password is requested by the SAP Add-OnInstallation Tool (SAINT). The following table shows the passwords for the VIM 7.0GW installation package:

SAP_BASIS Password

700 and compatible F17CB670FA

If you are asked for a SAP note number, use 1791715.

30.2 Checking PrerequisitesThe following prerequisites must be fulfilled for the installation of the VIM GWcomponent.

30.2.1 Required Knowledge

The following knowledge is required for the person dealing with the installation asdescribed in this document:



30.2.2 VIM 7.0 GW Prerequisites

Check the following prerequisites prior to installation:


• For general information on the installation of the SAP NetWeaver Gatewaycomponents, see http://help.sap.com/saphelp_gateway20sp06/helpdata/en/c3/424a2657aa4cf58df949578a56ba80/content.htm.

• The following components must be installed for SAP NetWeaver Gateway:


http://help.sap.com/saphelp_gateway20sp06/helpdata/en/c3/424a2657aa4cf58df949578a56ba80/content.htm

http://help.sap.com/saphelp_gateway20sp06/helpdata/en/c3/424a2657aa4cf58df949578a56ba80/content.htm

Table 30-1: SAP ERP 6.0 up to EHP7

Option Component:GW_CORE

Component: IW_FND Component: IW_BEP

Release

SupportPackage

Release

SupportPackage

Release

Support Package

1 200 SAPK-20004INGWCORE

250 SAPK-25004INIWFND

200 SAPK-20004INIWBEP

• Implement OSS note 1744864: Multiple Origin for Generated BOR/RFC Objectsdoes not work

Table 30-2: SAP ERP 6.0 EHP7

Option Component: SAP_GWFND Component: SAP_BASIS


1 740 SAPK-74004INSAPGWFND

740 SAPKB74002

Note: The VIM GW component is not yet released for SAP_BASIS 740 (EHP7).

30.2.3 Installation ToolOpenText Vendor Invoice Management uses the SAP Add-On Installation Tool(SAINT) for installation. SAINT uses single PAT files (extension *.PAT), whichintegrate several transport files; these collections are also called packages.

On the product CD, the single PAT files are archived in SAPCAR files (extension*.SAR), which can be extracted using the SAPCAR command line tool.

The SAR files can also be used directly in transaction SAINT.



Chapter 31


To install the OpenText VIM GW package:

1. Copy the respective SAPCAR file (OTVIMGW_INST_VIM700_700.SAR) from theKnowledge Center to a local folder.

2. Call the SAINT transaction (in client 000).

You get an initial screen, which shows the installed components.

3. On the menu, click Installation Package > Load packages > From Front Endand load file OTVIMGW_INST_VIM700_700.SAR.

4. To add the VIM 7.0 GW component, click Continue.

5. Choose the package for component OTVIMGW. Carry out the import of thepackage as described in the respective SAP documentation.


Chapter 32


Make sure that the VIM GW add-on is reflected in the installed components.




In the System: Component information dialog box, you should see the OTVIMGWadd-on component installed, with Release number 700.


Part 9Vendor Invoice Management Supplier Self

Service Component Installation

This part describes the installation of the Vendor Invoice Management Supplier SelfService component. The Supplier Self Service component is introduced with VIM 7.0SP3.

Part 9 Vendor Invoice Management Supplier SelfService Component Installation


Chapter 33


33.1 Installation PrerequisitesA complete installation and configuration of OpenText Vendor Invoice Managementfor SAP Solutions is needed for installing and testing the Supplier Self Service.Although it is possible to install the Supplier Self Service before the installation andconfiguration of the SAP ERP and Gateway component, you will not be able toverify if the installation of the Supplier Self Service is completed and correct.

SAP HANA Cloud Platform or any other Java-based application server (SP3restriction)

This section covers support and restrictions of Supplier Self Service in regards tooperating systems and web browsers.

• The Supplier Self Service web application does not support any mobile operatingsystems. It does not support any other operating systems than Windows.

Therefore, Mac/iOS, Linux, and Android operating systems are not supported.• For supported browsers, see https://sapui5.hana.ondemand.com/sdk/docs/guide/

BrowserSupport.html. See also OSS note 1716423: SAPUI5 Browser Support forMobile and Desktop Applications

• Some additional browser settings are necessary:

FirefoxYou must customize the language preferences: Go to Tools > Options, andclick the Content tab. In the Languages area, click Choose.

Add languages from the Select a language to add list. When performingan HTTP request, Firefox will send all the languages chosen with the Accept-Language header in the order of preference in which they are arranged in thelist.

Windows Internet Explorer 9The website might appear blank or might not be displayed correctly. In thiscase, set and use the Compatibility View on the menu bar of the browser:

• To use the Compatibility View, open the webpage in Internet Explorer,and then, on the Tools menu, click Compatibility View. If you do not seethe Tools menu, press ALT.

• To set the Compatibility View, on the Tools menu, click CompatibilityView settings. If you do not see the Tools menu, press ALT. In theCompatibility View Settings dialog box, enter the address of thewebpage, and then click Add.

Server

Operatingsystem and

browser support


https://sapui5.hana.ondemand.com/sdk/docs/guide/BrowserSupport.html

https://sapui5.hana.ondemand.com/sdk/docs/guide/BrowserSupport.html

The communication with the SAP NetWeaver Gateway system is accomplished byusing a Service user ID. Creation and assignment of the specific profile is describedin section 22.1.3 “Configuring Gateway Users” in OpenText Vendor InvoiceManagement for SAP Solutions - Configuration Guide (VIM-CGD).

33.2 Installation ComponentsA WAR (Web application ARchive) file is supplied. It is used to distribute a collectionof Java Servlets, JavaScript files, XML files, and other resources that togetherconstitute the Supplier Self Service web application.

33.3 System ArchitectureThis section explains the overall system architecture of the Supplier Self Service.There are a few ways to deploy and run the Supplier Self Service application. Thefollowing diagram shows the architecture for each scenario:

Figure 33-1: Supplier Self Service system architecture

Note: With VIM 7.0 SP3, only Option 1 is supported. It is described in thefollowing.

SAP user



Chapter 34

Installation on the SAP HANA Cloud

The SAP HANA Cloud Platform is an in-memory cloud platform based on openstandards. The platform is Java EE 6 Web Profile certified and provides a secure,scalable runtime environment with reusable platform services. Therefore, SupplierSelf Service can run on the SAP HANA Cloud Platform just like on any Java-basedapplication server.

Note: You need an SAP account for accessing the HANA Cloud.

34.1 Preparing the InstallationTo prepare the installation, you must deploy application specific files to the SAPHANA Cloud Server. You also need a Cloud connector as a separate servercomponent that has to be installed on premise.

34.2 Deploying the Application on the SAP HANACloud ServerYou deploy the application on the Cloud by using the SAP HANA Cloud Platformconsole client. You must deploy the vimsupplierselfservice package in the formof a WAR file. Deploying the Supplier Self Service application publishes it to the SAPHANA Cloud Platform. During deployment, you can define various specifics of thedeployed application using the deploy command optional parameters. For moreinformation, see https://help.hana.ondemand.com/help/frameset.htm?937db4fa204c456f9b7820f83bc87118.html.

Prerequisites

• You have downloaded and configured the SAP HANA Cloud Platform consoleclient. For more information, see https://help.hana.ondemand.com/help/frameset.htm?7613dee4711e1014839a8273b0e91070.html.

• Depending on your account type, deploy the application on the respectivelandscape. For more information, see https://help.hana.ondemand.com/help/frameset.htm?350356d1dc314d3199dca15bd2ab9b0e.html.

To deploy the application:

1. In the opened command line console, run the neo deploy command with theappropriate parameters. You can define the parameters of commands directly inthe command line, as in Example 34-1, “Deployment on the SAP HANA CloudServer” on page 202.

2. Enter your password if requested.


https://help.hana.ondemand.com/help/frameset.htm?937db4fa204c456f9b7820f83bc87118.html

https://help.hana.ondemand.com/help/frameset.htm?937db4fa204c456f9b7820f83bc87118.html

https://help.hana.ondemand.com/help/frameset.htm?7613dee4711e1014839a8273b0e91070.html

https://help.hana.ondemand.com/help/frameset.htm?7613dee4711e1014839a8273b0e91070.html

https://help.hana.ondemand.com/help/frameset.htm?350356d1dc314d3199dca15bd2ab9b0e.html

https://help.hana.ondemand.com/help/frameset.htm?350356d1dc314d3199dca15bd2ab9b0e.html

3. Press ENTER.

The deployment of your application starts.

4. If deployment fails, check if you have defined the parameters correctly.

Example 34-1: Deployment on the SAP HANA Cloud Server

neo deploy -- host <SAP HANA Cloud host> -- account <your account> --application vim3s -- source vimsupplierselfservice.war -- user <email oruser name>

Notes

• OpenText recommends entering the application name vim3s but you canchoose any other identifier you want.

• If the source file vimsupplierselfservice.war is located somewhere onyour system but not on the deployment folder you have to add the pathinformation to the filename.

• If you face any problems with the runtime environment, you can set thecustom parameter runtime-version manually, as described in https://help.hana.ondemand.com/help/frameset.htm?13afe5ca6e38485d8e6523f610c0ed29.html.

To make your deployed application available for requests, you must start it byrunning the neo start command or manage inside the SAP HANA Cloud cockpit.For more information, see section 22.2 “Customizing the HANA Cloud Server(Option)” in OpenText Vendor Invoice Management for SAP Solutions - ConfigurationGuide (VIM-CGD).

If you need more information about the SAP HANA Cloud Platform console client,see the online documentation: https://help.hana.ondemand.com/help/frameset.htm?46acebcd81384c9881f8ae7c5f3e3cac.html

34.3 Installing the SAP HANA Cloud ConnectorThe SAP HANA Cloud connector serves as the link between on-demandapplications on the SAP HANA Cloud Platform and existing on-premise systems.Using Cloud connector, you can configure the systems that are exposed to the SAPHANA Cloud Platform and control the resources available for the cloud applicationsin those systems. Thus, you can benefit from your existing assets without exposingthe whole internal landscape.

Note: The SAP HANA Cloud connector must not be used with products otherthan SAP HANA Cloud Platform.

Next steps

Chapter 34 Installation on the SAP HANA Cloud


https://help.hana.ondemand.com/help/frameset.htm?13afe5ca6e38485d8e6523f610c0ed29.html



https://help.hana.ondemand.com/help/frameset.htm?46acebcd81384c9881f8ae7c5f3e3cac.html

https://help.hana.ondemand.com/help/frameset.htm?46acebcd81384c9881f8ae7c5f3e3cac.html

The Cloud connector is a separate server component. It must be installed on premiseas described in the following online help: https://help.hana.ondemand.com/help/frameset.htm?e6c7616abb5710148cfcf3e75d96d596.html

34.3. Installing the SAP HANA Cloud Connector


https://help.hana.ondemand.com/help/frameset.htm?e6c7616abb5710148cfcf3e75d96d596.html

https://help.hana.ondemand.com/help/frameset.htm?e6c7616abb5710148cfcf3e75d96d596.html

Part 10Vendor Invoice Management Input Channel

for Ariba Network Integration for SAPBusiness Suite Installation

This part describes the installation of the Vendor Invoice Management input channelfor Ariba Network Integration for SAP Business Suite (VIM ARB).

Part 10 Vendor Invoice Management Input Channel forAriba Network Integration for SAP Business SuiteInstallation


Chapter 35


35.1 Password ControlThe OpenText Vendor Invoice Management package is protected with a specificpassword. During installation, this password is requested by the SAP Add-OnInstallation Tool (SAINT). The following table shows the passwords for the VIM 7.0ARB installation package:

SAP_BASIS Password

700 and compatible F17CB07598

35.2 Checking PrerequisitesThe following prerequisites must be fulfilled for the installation of the VIM ARBcomponent.




35.2.2 VIM 7.0 ARB PrerequisitesCheck the following prerequisites prior to installation:


• VIM 7.0 SP3 must be installed.

• The following components must be installed for Ariba Network Integration 1.0for SAP Business Suite:

Table 35-1: Ariba Network Integration 1.0 for SAP Business Suite

Option Component: ARBFNDI1 Component: ARBERPI1


1 100 600


• Implement OSS note 1935335: Mapping methods cannot be used from BAdIimplementations

35.2.3 Installation ToolOpenText Vendor Invoice Management uses the SAP Add-On Installation Tool(SAINT) for installation. SAINT uses single PAT files (extension *.PAT), whichintegrate several transport files; these collections are also called packages.

On the product CD, the single PAT files are archived in SAPCAR files (extension*.SAR), which can be extracted using the SAPCAR command line tool.

The SAR files can also be used directly in transaction SAINT.



Chapter 36


To install the OpenText VIM ARB package:

1. Copy the respective SAPCAR file (OTVIMARB_INST_VIM700_700.SAR) from theKnowledge Center to a local folder.

2. Call the SAINT transaction (in client 000).

You get an initial screen, which shows the installed components.

3. On the menu, click Installation Package > Load packages > From Front Endand load file OTVIMARB_INST_VIM700_700.SAR.

4. To add the VIM 7.0 ARB component, click Continue.

5. Choose the package for component OTVIMARB. Carry out the import of thepackage as described in the respective SAP documentation.


Chapter 37


37.1 Activating Business Configuration Sets for theOTVIMARB Component

Note: For every client, you must activate new BC sets after installing theOTVIMARB component.

To activate the BC sets:

1. Apply recommended user settings:

a. To access the Business Configuration Sets: Activation screen, run theSCPR20 transaction.

b. From the Utilities menu, click User Settings.c. To select your applicable languages, select the respective check box in the

Manual Selection column.

2. Activate BC set /OTVIMARB/700_CUSTOMIZING.

Activate the BC set in the Configuration client of the development system andcreate a transport from BC set activation, move the transport to the requiredsystems.

Do not activate the BC set in the production system. Create a customizationtransport in the development system configuration client by activating the BCset and move it to the desired systems.


Chapter 38


Make sure that the VIM ARB add-on is reflected in the installed components.




In the System: Component information dialog box, you should see theOTVIMARB add-on component installed, with Release number 700.


GlossaryAAK

See SAP Add-On Assembly Kit (AAK).

After Image

Technical option to realize an delta upload from the source systems into the SAPNetWeaver BW system. A data record loaded as After Image provides the statusof the record after it has been changed, or after data has been added.

Aging Report

Part of the Central Reporting infrastructure. The Aging Report reports about theaging of documents and work items in the current system.

AP processor

Accounts Payable personnel

Application Component Hierarchy

Hierarchy of folders to structure DataSources in SAP NetWeaver BW.

Approval chart of authority (COA)

The Approval chart of authority (COA) determines first approver and nextapprover for an invoice by combinations of Company Code (specific or range),Expense Type (marketing expense, utility), Cost Objects (G/L account, CostCenter), and HR objects (Position, Job code).

Approval Portal

VIM web interface for approving invoices.

Archive system

Computer system that enables storage, management and retrieval of archiveddata and documents

ArchiveLink document types

Document types that need to be customized for ArchiveLink

ArchiveLink

Service integrated in the SAP NetWeaver Application Server ABAP for linkingarchived documents and the application documents entered in the SAP ERPsystem


Authorization profiles

The SAP administrator assigns authorizations to the users that determine whichactions a user can perform in the SAP ERP system. These authorizations arestored in Authorization profiles.

Automation Report

Tool that provides data about automated and manual processing steps of VIMdocuments

BAdISee Business Add-Ins (BAdI).

BAPI®

SAP programming interface: Business Application Programming Interface

Baseline

Set of functionality with pre-defined configuration and the starting point toimplement VIM

BasisCubeSee InfoCube.

BDC ID

Business Data Communication ID. The BDC ID is used by the system to processan SAP transaction to create an SAP Document in user context.

Block

Situation where an invoice has a price or quantity variance that prevents invoicefrom posting

BTESee Business Transaction Event (BTE).

Business Add-Ins (BAdI)

Business Add-Ins (BAdI) is an SAP enhancement technique based on ABAPobjects. BAdI can be inserted into the SAP ERP system to accommodate userrequirements too specific to be included in the standard delivery.

Business rules

Rules that describe the operations, definitions and constraints that apply to anorganization

Business Transaction Event (BTE)

Event used for extending a Non PO invoice functionality to call a custom program

Glossary


Buyer

Person who is in charge of the PO. This role should have authorization to createand change the purchase order. This role is also responsible for negotiating andcommunicating with vendors.

Central Audit Report

Part of the Central Reporting infrastructure. The Central Audit Report is aslimmed VIM Analytics (VAN). The main difference to VAN is that the CentralAudit Report serves as a single point of access in a multiple backend scenario.

Central Reporting

Reporting infrastructure that provides several reports that enable you to measurecertain properties of VIM documents and their work items, in order to optimizeworking with VIM. Central Reporting comprises the following individual reports:Aging Report, Central Audit Report, Exception Analysis Report, Key Process AnalyticsReport, Productivity Report, and Summary Report.

Characteristic

Type of InfoObject in SAP NetWeaver BW that represents descriptions of fields,such as Vendor ID, Invoice Number, Unit of Measure, and Posting Date.

COASee Approval chart of authority (COA).

Coding

Coding allocates an invoice to G/L account and cost object if required.

Contract agent

Person who can create and modify SAP contracts.

Dashboard

User interface that organizes and presents information in a way that is easy toread. Users can also perform actions from the dashboard.

Data Transfer Process (DTP)

Object in SAP NetWeaver BW to transfer data from source objects to target objects

DataSource

Set of fields in SAP NetWeaver BW that provide the data for a business unit fordata transfer to the SAP NetWeaver BW system; technically, it contains an extractstructure and an extraction function module.

Glossary


DataStore Object (DSO)

Storage location for consolidated and cleansed data in SAP NetWeaver BW

DocuLink

OpenText DocuLink enables the archiving, management and retrieval of SAPCRM or SAP ERP documents from within the SAP infrastructure.

Document Processing (DP)

VIM component that captures invoice metadata including line items for PO andperforms preconfigured business rules

Document type

Type of document such as PO, Non PO, OCR, Non OCR

DPSee Document Processing (DP).

DSOSee DataStore Object (DSO).

DTPSee Data Transfer Process (DTP).

Duplicate analyzer

Person who is responsible to identify duplicate invoices

EDISee Electronic Data Interchange (EDI).

Electronic Data Interchange (EDI)

Method for transferring data between different application systems in the form ofmessages. SAP applications support EDI with messages sent in an SAPIntermediate Document (IDoc) format. VIM supports the creation of vendorinvoices through the EDI/IDoc interface.

Event Type Linkage

Error handling method. Event Type Linkage determines what the applicationshould do in case an error could not be handled.

Exception Analysis Report

Part of the Central Reporting infrastructure. The Exception Analysis Reportreports all work items with exceptions, grouped by exception, company code orvendor.

Glossary


Exception

Action that is not part of normal operations or standards

FISee Financial Accounting (FI).

Financial Accounting (FI)

SAP module for the Finance and Accounting department

IAPSee Invoice Approval (IAP).

ICCSee Invoice Capture Center (ICC).

IDocSee Intermediate Document (IDoc).

IESee Invoice Exception (IE).

Indexer

Person responsible for entering index data

Indexing

Process of entering or storing data into the system

InfoArea

Folder in SAP NetWeaver BW to organize InfoCubes, DataStore Objects, InfoObjects,and InfoObject Catalogs

InfoCube

Self-contained dataset in SAP NetWeaver BW, for example, of a business-orientedarea; an InfoCube is a quantity of relational tables arranged according to theenhanced star schema: A large fact table in the middle surrounded by severaldimension tables

InfoObject Catalog

Folder structure in SAP NetWeaver BW to organize InfoObjects

InfoObject

Smallest information unit in SAP NetWeaver BW. Key figures and Characteristicsare collectively called InfoObjects.

Glossary


InfoPackages

Object in SAP NetWeaver BW that specifies when and how to load data from agiven source system to the SAP NetWeaver BW system

InfoProvider

Object in SAP NetWeaver BW for which queries can be created or executed.InfoProviders are the objects or views that are relevant for reporting.

Information provider

Receiving role for option Refer for Information

Integrated Invoice Cockpit

VIM component that gathers and displays all VIM exceptions in one place. Userscan start the respective dashboard by processing a work item directly from theIntegrated Invoice Cockpit.

Intermediate Document (IDoc)

Standard SAP message document format for the EDI interface.

Invoice Approval (IAP)

VIM component that enables users to perform coding, approving and rejectinginvoices

Invoice approver

Person who approves invoices

Invoice Capture Center (ICC)

Optional VIM OCR component

Invoice characteristic

A value specific to each invoice (for example country) that allows flexibleprocessing in VIM. An invoice characteristic is determined during runtime anddepends on the corresponding index data of the document.

Invoice coder

Person who enters the accounting info on invoices to allocate the cost

Invoice Exception (IE)

VIM component that handles the exceptions that arise after an SAP invoice iscreated

Glossary


Invoice requester

Person who requested goods and services for Non PO invoices

Key Figure

Type of InfoObject in SAP NetWeaver BW that represents numeric values orquantities, such as Number of Invoices and Gross Invoice Amount.

Key Process Analytics Report

Part of the Central Reporting infrastructure. The Key Process Analytics Reportreports about a variety of key figures regarding the VIM process: It shows theaccumulated amounts of all documents in the DP workflow, in parked state andin posted state.

KPI Dashboard

Tool for managers showing VIM related process data at a glance in graphicalcharts.

LIVSee Logistic invoice (LIV).

Logistic invoice (LIV)

purchase order invoice

Materials Management (MM)

Materials management module of the SAP ERP software package. Materialsmanagement is used for procurement and inventory management.

MMSee Materials Management (MM).

Mobile Approval Portal

VIM component for approving invoices on mobile devices.

MultiProvider

Object in SAP NetWeaver BW that is based on InfoCube(s), DataStore Object(s),and/or InfoObject(s). A MultiProvider is used as a layer for the creation of end userqueries; the MultiProvider itself does not contain any data; rather, data resides inthe BasisCubes.

Namespace

Name range reserved by SAP for customer objects and SAP objects to make surethat objects are not overwritten by SAP objects during the import of corrections oran upgrade

Glossary


Non purchase order (Non PO)

Order that is not based on a PO

Non purchase order (Non PO) invoice (PIR)

Invoice based on a Non purchase order (Non PO)

Number range

Array of numbers that can be used for an object in the SAP ERP system

OCRSee Optical character recognition (OCR).

Optical character recognition (OCR)

Mechanical or electronic translation of images of handwritten, typewritten orprinted text (usually captured by a scanner) into machine-editable text

Park

Situation where an invoice is not posted and is waiting for further processing

Parked invoice document

Temporary document that the AP processor can change and post. SAP assigneddocument number becomes real number when posted.

Persistent Staging Area (PSA)

Data staging area in SAP NetWeaver BW. It allows to check data in anintermediate location before the data is sent to its destinations in SAP NetWeaverBW.

PIRSee Non purchase order (Non PO) invoice (PIR).

POSee Purchase order (PO).

Posted invoice document

Invoice that has already been posted in SAP ERP. Only free-form text fields canbe changed. Related documents such as POs or good receipts may be created orchanged to effect the invoice. If the document is not needed, it must be cancelled( PO invoice) or reversed ( non-PO invoice).

Price variance

Situation where the price on the invoice is different from the price in the purchaseorder

Glossary


Process Chain

Sequence of processes in SAP NetWeaver BW that are scheduled to wait in thebackground for an event; used to automate, visualize and monitor the processes.

Process options

Processing options for the user in the dashboard, such as Referral, Authorization,and Actions

Process type

Process type for a document. The process type determines the initial actor andvarious collaboration options available to the various actors during the processflow.

Productivity Report

Part of the Central Reporting infrastructure. The Productivity Report reportsabout the productivity of users/roles and the activities of users/roles.

PSASee Persistent Staging Area (PSA).

Purchase order (PO) invoice

Invoice based on a Purchase order (PO)

Purchase order (PO)

SAP module. PO indicates a document sent from a buyer to a seller. The purposeof the document is to order the delivery of goods or services.

Quantity variance

Situation where the quantity on the invoice is different from the quantity in thepurchase order

Receiver

Person who can create and reverse the goods receipt in SAP ERP

Requisitioner

Person who requested goods and services

Roles

Set of predefined roles for the SAP user

SAP Add-On Assembly Kit (AAK)

Standardized delivery procedure for software

Glossary


SAP Customer Relationship Management (SAP CRM)

SAP application that provides software for ticket systems, for example in theAccounts Payable department.

SAP NetWeaver Business Warehouse (SAP NetWeaver BW)

SAP application that allows to integrate, transform, and consolidate relevantbusiness information from productive SAP applications and external datasources.

SAP Shared Service Framework

SAP software that contains a rich set of tools to improve and automate SharedService Center operations.

SAP Supplier Relationship Management (SAP SRM)

SAP application that automates, simplifies, and accelerates procure-to-payprocesses for goods and services.

Scan operator

Person who scans the invoices into images (may not have a SAP ID)

Service approver

Person who approves a service entry

Service requisitioner

Person who enters a service entry

Summary Report

Part of the Central Reporting infrastructure. The Summary Report provides asummary of all documents processed through VIM.

Swimlane

Diagram representing a specific VIM process. A swimlane comprises the processdescription, roles, user interface and options of the process.

Tax expert

Person who advises on invoices that need tax audit. Normally tax departmentpersonnel.

Transformation (TRF)

Object in SAP NetWeaver BW to connect source objects to data targets; it allowsto consolidate, cleanse and integrate data

Glossary


TRFSee Transformation (TRF).

VANSee VIM Analytics (VAN).

Vendor Invoice Management (VIM)

Packaged business solution that solves a business problem – paying correctamount to vendors on-time and with the lowest cost. VIM delivers not technologybut best-practice business processes. VIM provides values to customers in processefficiency, visibility and compliance.

Vendor maintenance

Person who is responsible for creating and maintaining the vendor masterrecords

VIM Analytics (VAN)

VIM component that gives users a clear data report on their invoices in progress.VIM Analytics allows to track the documents routed through SAP workflows viaVIM.

VIM Workplace

Tool for VIM super users, which allows users to display lists of their work itemsthat meet a selection they have entered before. Users also can display work itemsof other users and of their team as a whole.

Workflow

SAP Business Workflows can be used to define business processes that are not yetmapped in the SAP ERP system.

Glossary


opentext vendor invoice management for sap solutions 7.0 - installation ....pdf

Documents

property of open text

vendor invoicemanagement

open text sa40 avenue

optional kpidashboard

sap business suite

opentext package

registered trademarks

product names