El impacto de la tecnología

This section discusses the process to perform an upgrade from VIM 5.2 to VIM 7.0 and from VIM 6.0 to VIM 7.0.

The OpenText Vendor Invoice Management package is protected with a specific password. During VIM upgrade, this password is requested by the SAP Add-On Installation Tool (SAINT). For passwords for a VIM upgrade, see “Password Control” 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 invoice parking infrastructure.

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

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

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

• The following components must be installed:

ECC 6.0

Component SAP_BASIS Level: 700

Password control

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

Option Component: SAP_BASIS

Release Level Support package

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 version

Upgrade to VIM 7.0 is supported with minimal versions of VIM 5.2 SP6 or VIM 6.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 sets delivered with the SPs.

Direct upgrade from VIM 5.1.6 is not supported. You can upgrade from VIM 5.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 and check the Component Version.

For more details, see “Verifying Installation“ on page 39. The following screenshots show system component information with the required minimum SP levels of ^OTEXVIM.

6.4. Upgrading VIM

Adjust SAINT tool settings

In the settings of the SAINT tool, make sure that ABAP/Screen Generation is set to Always.

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; that means, the entire VIM processes must not be performed.

2. Before you begin the update, perform a complete backup or take a snapshot of the 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 in your /OPT/VIM_1HEAD table.

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

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

Then run report /OPT/VIM_MIGRATE_PO_DN_LISTS to store PO_LIST and DN_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, you have to use the specific VIM upgrade packages.

1. Copy the respective SAPCAR file (*.SAR) from the product CD to the target SAP application server in the \usr\sap\trans folder. This is the parent folder of the DIR_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 2. Extract the ^SAPCAR file to the \usr\sap\trans\EPS\in folder with the

following command: SAPCAR -xvf <name of SAPCAR file>.

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

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

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 is displayed, 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.

Click the Continue button.

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

Click the Continue button.

A message is displayed, confirming the successful import.

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

To finish the VIM upgrade:

1. If you need login languages other than English and German, install the language 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 the Knowledge 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 described in “Post Installation Activities After an Upgrade” on page 62.

Important

Do not activate the BC Sets for first installation, as described in

“Activating Business Configuration Sets” on page 18. If you activate these BC Sets, all the configuration data is overwritten with OpenText baseline configuration data and all custom configuration changes are lost.

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

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

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