Capítulo 2. Marco Teórico Referencial
2.2 Marco teórico
2.2.2 Espacios de aprendizaje
The 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 objects are protected.
Can I repair the OpenText objects?
It is not recommended to repair OpenText objects. Contact
[email protected] before making any repairs; OpenText might have already issued a patch for the intended repair and the same functionality can be achieved 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 3
KPI Dashboard Installation
This part describes the installation and post installation activities needed for the
“Key Performance Indicator” Dashboard KPI Dashboard. The KPI Dashboard is a tool for managers showing VIM related process data at a glance in graphical charts.
For further information, see section 25 “KPI Dashboard” in OpenText Vendor Invoice Management 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.
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 Service
The 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 to change the service settings. So first check with transaction SE03
Navigate to Transport Organizer Tool > Administration > Set System Change Option
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 SICF transaction.
2. In Virtual Host, enter default_host and click Execute.
3. In the tree, select sap > bc > webdynpro.
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 5 minutes..
If a user has an open KPI Dashboard, does nothing for a couple of minutes and then tries to change a filter or category, a timeout error occurs. As long as the time without activity is shorter than the session timeout parameter, no error will occur.
2. Save the changes and leave the service maintenance.
Error Handling
You can customize a few default pages for error handling in the Web Dynpro service.
Error pages are shown for defined reasons; for example, if the timeout is reached for the 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 Dynpro Service
You activate the SSL connection for Web Dynpro by configuring the SAP Web AS, as described 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 Dynpro Service” on page 73. Make sure that the SSL settings are not activated in the Logon Data tab.
Change the KPI constant DASHBOARD_START_URL to https://xxxxx:8443/xxxx. See section 25.4.10.5 “KPI Dashboard Start URL” in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
9.3 Setting Up the SAP NetWeaver Portal Integration
Use Internet Explorer 8 (or higher) for setting up the SAP NetWeaver® Portal integration for the KPI Dashboard on NetWeaver 7.0 and login to the SAP NetWeaver Portal as Administrator.
A System Object is needed to integrate the KPI Dashboard in the SAP NetWeaver Portal. The System Object is a set of connection properties to represent an external or SAP system (SAP R3, CRM, BW) used to retrieve data into portal iViews. If not existing, you must create a System Object in the NetWeaver Portal.
9.3.1 Prerequisites
This 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 > System Configuration > System Landscape > Browse > Portal Content > System landscape.
2. System Alias settings
In the Display drop down list, select System Aliases. The System Alias Editor is 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 Property Category drop down list, select Connector.
Provide minimum connector properties for example. See the following screenshot 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 an iView.
In the Display drop down list, select Object, and then, in the Property Category 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 using transactions SICF and SMICM.
For a detailed description how to set up the System Object in the Portal, see http://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 > Portal Content > Browse > Portal-Content.
2. Choose a folder or generate a new folder. To select the iView object, right-click the folder and select new > iView.
3. In the Display drop down list, select Object, and then, in the Property Category drop down list, select Content - Web Dynpro.
Provide properties as shown in the following screenshot.
9.3. Setting Up the SAP NetWeaver Portal Integration
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 everything is customized correctly, a separate window opens and shows the KPI
Dashboard content in the iView.
Part 4
OpenText Approval Portal Installation
This part describes the installation of the OpenText Approval Portal component. The Approval 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 NWAS only or as an application inside NWP using AppIntegrator iView. Install all the components 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 the same SAP NetWeaver Portal. In this case, contact OpenText Customer Support.
Chapter 10
Preparing Installation
10.1 Installation Prerequisites
A complete installation and configuration of OpenText Vendor Invoice Management for SAP Solutions is needed for installing and testing the Approval Portal. Although it is possible to install the Approval Portal before the installation and configuration of the SAP ERP component, you will not be able to verify if the installation of the Approval Portal is completed and correct.
Server
Web Application Server
SAP NetWeaver Application Server Java (NWAS) 7.0 SP9 or above with SPNegoLoginModule 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 Portal
SAP 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 in the OpenText R&D lab. The resolution modes have been tested in all supported browsers.
1. 1280 x 800 - Laptop view 2. 1920 x 1080 - Laptop view 3. 1680 x 1050 - Desktop view 4. 1280 x 1024 - Desktop view
The following matrix shows the web browsers and versions that are supported by the new interface of the Approval Portal, which is delivered since VIM 7.0 SP2. The matrix is based on tests performed at OpenText R&D Lab. It considers accessibility and usability aspects.
Note: The old interface of the Approval Portal supports only Internet Explorer 7.0, 8.0, and 9.0.
Recommended Screen Resolution
Web browsers
With VIM 7.0 SP4 and above, the old interface of the Approval Portal also supports Internet Explorer 10.0 and 11.0.
Server Browser and Version
IE9 IE10 Firefox > 17 Chrome > 22 Safari > 5.0 NWAS 7.0
The Approval Portal supports Windows, Unix and other operating systems supported by SAP.
There is no restriction which Windows or Unix versions or patch levels are supported. 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 Availability Matrix (PAM) for more details.
OpenText recommends implementing SSL (HTTPS) if security is a concern. Basic Authentication in SPNego is using Base64 encryption which can be easily decrypted.
See http://msdn.microsoft.com/en-us/library/aa292114(VS.71).aspx for further information.
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 user ID. However, the Web user is recorded as the agent who approved an invoice, not the CPIC user.
User type
Communication Data (CPIC) Profile
Create a profile with the following authorization objects and add it to the CPIC user:
Object: S_RFC Activity
Execute (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_TYPE
FUGR (Function Group) Object: S_CPIC
Activity
Accept, Initialize (37 and 51) Name of an ABAP/4 FORM routine
CPIC
Symbolic destination
*
If you wish to narrow this down, examine table TXCOM and choose entry under the SDEST field that represents the destination of the system you are communicating with.
Program Names with Search Help /ORS/*, /OPT/*, /PTGWFI/*
Object: S_DATASET (Authorization for file access) Activity
Read, 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 SAP ERP 702 SP14 and higher and SAP NetWeaver Portal 702 SP15 and higher:
Object: S_RZL_ADM (Authorization object for R/3 system administration) Activity
Display (03)
Object: S_WF_SUBST (Workflow: substitute rule) Activity
Display (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 need to assign additional roles. See the Archive Server Installation manual.
10.1. Installation Prerequisites
Example: OpenText Archive Server provides the following profiles that need to be assigned to the CPIC user to access images:
• S_AL_ADMLO (Display SAP ArchiveLink® administrator)
• S_AL_ADMDE (Delete ArchiveLink administrator) Defaults
Decimal notation should be 1,234,567.89.
Note: For SAP ERP systems with EHP5 or higher, one additional authorization is required for the CPIC user.
S_WF_WI
Classification of tasks
* Activities
12 (Resubmit work item) Work item type
W – Dialog work item
10.2 Installation Components
Both 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 OpenText Vendor Invoice Management 7.0 Support Package folder in the Knowledge Center (accessible via https://knowledge.opentext.com/knowledge/cs.dll/Open/
32893475) provides two installation packages of the VIM 7.0 SPx Approval Portal in the Web and Mobile Approval Component folder: one for the new user interface (which is introduced with VIM 7.0 SP2), and one for the old user interface.
10.3 System Architecture
This section explains the overall system architecture of the Approval Portal. There is one 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 integrated authentication
• 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 communication channels 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)
Figure 10-2: Approval Portal architecture with NWP
10.3.1 SAP User Requirements
For the SAP user, the following log in properties are required for the OpenText Approval Portal:
Standalone J2EE application residing on NWAS only utilizing integrated authentication
No need for SAP GUI Logon ID. Only network ID is required.
Application inside NWP using AppIntegrator iView
No need for SAP GUI Logon ID. Only Portal ID is required.
Dual Stack installation (SAP ABAP and Java Stack) utilizing integrated authentication
SAP GUI Logon ID required. Dual Stack forces to use SAP user management based on ABAP Stack.
10.3. System Architecture
Standalone J2EE application residing on NWAS with NWP utilizing integrated authentication 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 Installation
To prepare the installation, perform the following steps:
1. Deploy application specific files to server
To gain access to the file system, sign on to the host server as a user with administrator rights.
Extract the files from opentext.zip from the delivery to a folder on the server.
Important
OpenText recommends you to create and deploy to the folder usr/sap/
<SID>/SYS/global/opentext/invoiceCfg. This is the default location for putting the application configuration file. If you deploy to another location, you will have to manually add a startup parameter in the Config Tool to tell the application where to look for the configuration files. This will also require restarting the SAP NetWeaver Application Server 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.xml
containing all the configuration for the application mobileconfiguration.xml
containing all the configuration for mobile support RequestMappings.xml
OpenText strictly recommends not to modify this file. The Approval Portal application internally uses this file.
Lang_Support.properties
containing all the mapping of languages code; see section 12.3.2
“Configuring Additional Languages” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM-AGD) for details.
Lang_DE.properties
containing all the text for the German language resource Lang_EN.properties
containing all the text for the English language resource
Lang_ES.properties
containing all the text for the Spanish language resource Lang_FR.properties
containing all the text for the French language resource Lang_IT.properties
containing all the text for the Italian language resource Lang_JA.properties
containing all the text for the Japanese language resource Lang_NL.properties
containing all the text for the Dutch language resource Lang_PT.properties
containing all the text for the Portuguese language resource Lang_RU.properties
containing all the text for the Russian language resource Lang_ZH.properties
containing all the text for the Chinese language resource
There might be more .properties files, depending on the package and the release for additional languages. The language resource files can be changed.
See section 12.3.1 “Changing Language Resources” in OpenText Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-AGD) for details.
Important
Make 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 to Everyone)
2. Optional: Invoke the J2EE Config Tool Important
This step is only needed if you deploy the configuration files to a location 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 the Config Tool, manually, to tell the application where to look for the
configuration files.
You find the Config Tool in the following directory: usr/sap/<SID>/
<INSTANCE_NAME>/j2ee/configtool.
Notes
• SID is the system ID of the NWAS (example O15).
• INSTANCE_NAME is the NWAS instance in the format of JCxx, where xx 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_installd ir>.
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> folder contains application specific information.
11.1. Preparing the Installation
11.2 Configuring the Administrator Role
Important
This section is only needed if you are installing as a standalone J2EE application residing on NWAS only utilizing integrated authentication.
This section describes the installation activities to assign the administrator role to the user for the Approval Portal application. As the Administrator, you must login to the Administrator page to perform some application configuration and to perform other administration tasks. See section 12 “Administering the Approval Portal” in OpenText Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-AGD) for additional information.
11.2.1 Configuring the Administrator Role for Access Through NWAS
This section describes how to create a VIM administrator role and assign it to the domain user through NWAS Visual Administrator. For a description of the necessary steps with SAP NetWeaver 7.3 and 7.4, see “Configuring the
Administrator 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 ensure
You must perform this configuration before deploying the .sca or .sda, to ensure