Beruflich Dokumente
Kultur Dokumente
Administration Guide
This guide describes the technical and functional aspects of
administering OpenText Vendor Invoice Management 6.0.
VIM060000-AGD-EN-3
Table of Contents
Introduction ............................................................................... 9
1.1
1.2
1.2.1
1.2.2
1.2.3
1.3
1.4
1.5
Understanding VIM.................................................................. 15
2.1
2.2
2.3
2.4
Part 1
Administering VIM
19
Administration Tools............................................................... 21
3.1
Roles ........................................................................................ 29
5.1
7.1
7.2
8.1
8.2
VIM060000-AGD-EN-3
iii
Table of Contents
iv
10
10.1
10.2
11
11.1
11.2
11.3
12
13
Administering Workflows........................................................73
13.1
13.1.1
13.1.2
13.1.3
13.2
13.3
13.4
13.5
13.6
13.7
13.8
13.9
13.10
13.11
13.12
13.13
13.14
13.15
14
14.1
15
15.1
16
16.1
16.2
16.3
16.3.1
16.3.2
VIM060000-AGD-EN-3
Table of Contents
16.3.3
16.4
16.4.1
16.4.2
16.4.3
16.4.4
16.4.5
16.5
17
18
18.1
18.2
18.3
18.4
18.5
18.6
18.7
18.8
18.9
18.10
18.11
18.12
18.12.1
18.12.2
18.12.3
18.12.4
18.12.5
18.12.6
18.12.7
19
19.1
19.2
19.3
19.3.1
19.4
19.4.1
19.4.2
20
20.1
20.1.1
20.1.2
20.1.3
VIM060000-AGD-EN-3
Administration Guide
Table of Contents
vi
20.2
21
21.1
21.2
22
22.1
22.1.1
22.1.2
22.1.3
22.2
22.3
22.4
23
23.1
23.1.1
23.1.2
23.1.3
23.1.4
23.2
23.3
23.3.1
23.3.2
23.4
23.5
23.5.1
23.5.2
23.5.3
23.6
23.7
23.8
23.9
23.10
23.11
23.12
23.13
23.14
23.15
24
24.1
24.1.1
24.1.2
VIM060000-AGD-EN-3
Table of Contents
24.1.3
24.1.4
24.1.5
24.2
24.2.1
24.2.2
24.2.3
24.2.4
24.2.5
24.3
24.4
25
25.1
25.2
26
GLS
Glossary
239
IDX
Index
247
VIM060000-AGD-EN-3
Administration Guide
vii
Chapter 1
Introduction
1.1 About Vendor Invoice Management
VIM is an abbreviation for SAP Invoice Management by OpenText.
VIM solves a business problem - paying correct amount to vendors on time and
with the lowest cost.
VIM is an add-on to your SAP system, the majority of the functions and
processes run inside your SAP system.
VIM deals only with invoices that will be posted to SAP ERP.
VIM uses SAP technology: ABAP, Workflow, and SAP NetWeaver Portal.
VIM060000-AGD-EN-3
Chapter 1 Introduction
Automate the capture of paper invoices by using OCR to extract invoice data.
Document Processing
Invoice Approval
Approval Portal
10
VIM060000-AGD-EN-3
1.2
VIM Reporting: Use various reports to analyze the status of invoices in your
system.
Integrate VIM with the SAP CRM SSF component to create Service Requests
from VIM dashboards.
The product ISO image comprises the complete product CD-ROM in one *.iso
file. The product ISO image is available in the OpenText Knowledge Center. To
access the ISO image, select the product family page and then click the
Downloads link.
The documentation for all products and all supported versions is available in the
OpenText Knowledge Center. See the Release Notes for details and links. In the
Knowledge Center, select the product family page, and then click the
Documentation link. If the required product belongs to the OpenText Content
Server family, click the Content Server Module Documentation link and then
select the product from the list.
Note: You can find the latest information on manuals and online help files for
each product in the corresponding Release Notes. This includes the
identification codes of the current documentation.
VIM060000-AGD-EN-3
Administration Guide
11
Chapter 1 Introduction
1.2.3 Conventions
User interface
This format is used for elements in the graphical user interface (GUI), such as
buttons, names of icons, menu items, and fields.
Filenames, commands, and sample data
This format is used for file names, paths, URLs, and commands at the command
prompt. It is also used for example data, text to be entered in text boxes, and
other literals.
Note: If you copy command line examples from a PDF, be aware that PDFs
can contain hidden characters. OpenText recommends copying from the
HTML version of the document, if it is available.
KEY NAMES
Key names appear in ALL CAPS, for example:
Press CTRL+V.
<Variable name>
Angled brackets < > are used to denote a variable or placeholder. The user
replaces the brackets and the descriptive content with the appropriate value. For
example, <server_name> becomes serv01.
Internal cross-references
Click the cross-reference to go directly to the reference target in the current
document.
External cross-references
External cross-references are usually text references to other documents.
However, if a document is available in HTML format, for example, in the
Knowledge Center, external references may be active links to a specific section in
the referenced document.
Warnings, notes, and tips
Caution
Cautions help you avoid irreversible problems. Read this information
carefully and follow all instructions.
Important
Important notes help you avoid major problems.
Note: Notes provide additional information about a task.
Tip: Tips offer you quicker or easier ways of performing a task.
12
VIM060000-AGD-EN-3
1.3
Contact Information
Communities
Knowledge Center
Usage tips, help files, and best practices for customers and partners.
User groups and forums where you can ask questions of OpenText experts.
If you need additional assistance, you can find OpenText Corporate Support
Contacts at http://support.opentext.com/.
VIM060000-AGD-EN-3
Administration Guide
13
Chapter 1 Introduction
14
VIM060000-AGD-EN-3
Chapter 2
Understanding VIM
2.1 Delivery Model
As VIM is basically a scenario, its function may best be described as a problem
solution. It enables the flexible configuration of a company's payment workflow. To
this end, VIM is delivered with a so-called Baseline Configuration, a set of pre-defined
configurations that work out of the box. In conjunction with other OpenText
products such as OpenText Archive Server it is possible to realize comprehensive
solutions. Core Functions are the technical foundation of VIM: SAP screens,
functions, workflow templates, web pages, etc.
VIM060000-AGD-EN-3
15
16
VIM060000-AGD-EN-3
2.3
Process Swimlanes
VIM060000-AGD-EN-3
Administration Guide
17
18
VIM060000-AGD-EN-3
Part 1
Administering VIM
Chapter 3
Administration Tools
VIM provides the following tool that serves for administration purposes:
VIM060000-AGD-EN-3
21
Chapter 4
VIM060000-AGD-EN-3
23
Fiscal Year
fiscal year of the document that you want to clear
Program: /ORS/000007_LOCK_CLEANUP
Description: Releases invoice locks as set by Web approval workflow.
Suggested minimum frequency: Every 30 min.
Parameters: None
Program: /OPT/VIM_R1A_REMINDER
Description: Sends out VIM reminder emails for overdue items.
Suggested minimum frequency: Once a day
Parameters: Select Background Mode
Table /OPT/T852 defines the number of grace days.
Program: RSWWERRE
Description: Restarts work items that are in error status. This job reduces
workflow administration.
Suggested minimum frequency: As defined by the workflow configuration
Parameters: None
Program: /OPT/VIM_TRIGGER_HEADER_WF
Description: Triggers the LIV Header Level Workflow.
Suggested minimum frequency: Twice a day or more often, depending on the
requirements
Parameters: None
Program: /OPT/VR_A_AGGREGATION
Description: Runs the Aggregation Report for specific groups to update
reporting tables for Central Reporting. See Scheduling Batch Jobs for Central
Reporting on page 135 for details.
Suggested minimum frequency: Depending on specific groups and
requirements
Parameters: Use variants for specific groups.
Program: /OPT/CR_RERUN_RULES_JOB
Description: In the DP Goods Receipt Missing scenario of the Supplier
Relationship Management (SRM) scenario, this job will publish the events
PSS_Completed and ProcessCompletedExternally. These events will enable
the workflow to rerun business rules.
If the goods receipt is posted, rerunning the business rules will resolve the GR
Missing exception and continue with the next process.
If the maximum number of tries is exceeded, the work item will be sent to the
dialog user to be resolved manually.
24
VIM060000-AGD-EN-3
For Quantity and Price block scenarios, use the standard MRBR job and the
OpenText workflow clean up job to resolve work items which are in waiting
status.
Suggested minimum frequency: Every 4 hours
Parameters: Use variants for specific groups.
Program: /OPT/VR_UPDATE_FINISH_TIME
This is applicable only for customers who had VIM 5.2 earlier. New customers
can skip this job.
Prerequisite
The job /OPT/VR_UPDATE_FINISH_TIME needs the following prerequisite:
As the job act on the data stored in Central Reporting Tables, all data must
already be collected in Central Reporting Tables. Therefore, the
Aggregation Report /OPT/VR_A_AGGREGATION must have run with various
variants, see Administering Central Reporting on page 121 for details.
Description: Run this batch job only one time. It is part of the post installation
activities for work items that are already finished or completed in the SAP
system.
This job updates the finished time stamp for the work items in the Central
Reporting tables. Before introducing this job, the finish time stamp was not
updated.
For collecting aggregates, it is important to have the finished time stamp.
Do not run this job online but as a background job, if data volumes are huge for
work items. You can also process parallelly in background jobs: Split the work
item IDs into various ranges and use those ranges as job variants.
Once the time stamp of the older work items is updated, this job will no longer
be needed. For future work items, the regular aggregation report
/OPT/VR_A_AGGREGATION will update the finish time stamp by itself.
Suggested minimum frequency: Run only one time
Parameters: Use variants for work item ID ranges.
Program: /OPT/VAN_SYNC_JOB
Description: VIM tables /OPT/VIM_HD_DP, /OPT/VIM_HD_PO, /OPT/VIM_PO_WIH,
/OPT/VIM_HD_NPO, and /OPT/NPO_WIH are not correctly updated by VIM
workflows during the invoice process. The VIM Analytics (VAN) sync job
program updates the following fields of the VAN tables:
VIM060000-AGD-EN-3
Table
Field
Description
/OPT/VIM_HD_DP
CURR_AGENT
MULTIPLE_AGENTS
WI_STATUS
Administration Guide
25
Table
/OPT/VIM_HD_PO
/OPT/VIM_HD_NPO
/OPT/VIM_PO_WIH
/OPT/NPO_WIH
Field
Description
DOC_STATUS_CODE
TOTAL_AMOUNT
Gross amount
DOC_STATUS_CODE
DOCID
DP_DOCTYPE
DP document type
PARK_REASON
Parking reason
DOC_STATUS_CODE
DOCID
DP_DOCTYPE
DP document type
CURR_AGENT
MULTIPLE_AGENTS
WI_STATUS
CURR_ROLE
Current role
LAST_OPTION_TYP
LAST_OPTION_ID
CURR_AGENT
MULTIPLE_AGENTS
WI_STATUS
CURR_ROLE
Current role
LAST_OPTION_TYP
LAST_OPTION_ID
You can run the VAN Sync Job by executing the SA38 transaction with program
/OPT/VAN_SYNC_JOB or clicking the Sync button in the VAN application toolbar
for all selected entries in the list. By clicking the Sync button in VAN, all data of
the selected entries will be updated accordingly. You might need to refresh VAN
to get the updated data displayed.
The selection criteria in the Sync VAN Tables with SAP Data screen are
optional.
If the Include All check box is cleared, the following workflow and document
statuses are excluded for Non PO and PO invoice data selection:
26
Posted
Deleted
VIM060000-AGD-EN-3
Cancelled
Completed
Archived
VIM060000-AGD-EN-3
/OPT/VIM_RPT_SYNC_DP_TABLE
/OPT/VIM_RPT_SYNC_TABLES
/OPT/VIM_RPT_SYNC_TAB_NOLIMIT
Administration Guide
27
Chapter 5
Roles
The VIM role concept is comprehensively described in section 4 "Roles" in
OpenText Vendor Invoice Management - Configuration Guide (VIM-CGD) that covers
the following topic:
Defining roles
VIM060000-AGD-EN-3
29
Chapter 5 Roles
2.
Maintain the FAIL_SAFE user key types Fail Safe and Default Key for all roles,
using the following parameters:
Note: You only need to maintain one type, based on your requirements.
But it is a good practice to set up both types in case you change the
FAIL_SAFE type.
Agent Type
Select the agent type.
Agent Id
Select the agent Id.
30
VIM060000-AGD-EN-3
Chapter 6
VIM060000-AGD-EN-3
31
Chapter 7
Setting up a substitute
Adopting a substitution
To set up a substitute:
1.
To access SAP Business Workplace, execute the SBWP transaction or click Menu
> Business Workplace.
2.
From the menu, select Settings > Workflow settings > Maintain substitute.
VIM060000-AGD-EN-3
33
3.
34
In the Personal Substitutes screen, mark the name and click the Create
at the bottom of the screen.
substitute button
VIM060000-AGD-EN-3
7.1
4.
In the User screen, enter the SAP user id of the substitute. Click
to confirm.
5.
In the Detail Screen Substitution, insert the validity period. Make sure the
Substitution active check box is not selected.
6.
Click
to save changes.
VIM060000-AGD-EN-3
Administration Guide
35
7.
When the substitute is ready to work on the work items belonging to the substituted
person, he or she adopts the substitution and is then able to view and execute those
work items.
To adopt a substitution:
36
1.
To access SAP Business Workplace, execute the SBWP transaction or click Menu
> Business Workplace.
2.
From the menu, select Settings > Workflow settings > Adopt substitution.
VIM060000-AGD-EN-3
7.2
Select the substitution you want to activate by selecting the check box next to
the persons name.
Click
to confirm.
When you have finished working on the work items belonging to the substituted
person, you must end the substitution in order to view your own work items.
To end a substitution:
Click in the menu: Settings > Workflow settings > End substitution.
VIM060000-AGD-EN-3
Administration Guide
37
38
1.
2.
VIM060000-AGD-EN-3
7.2
3.
4.
To select the correct person from the list, double-click the entry.
VIM060000-AGD-EN-3
Administration Guide
39
40
5.
To designate a substitute for this person, select the Substitutes tab and click
Select a substitute.
6.
7.
To select the correct person from the list, double-click the entry.
to search.
VIM060000-AGD-EN-3
7.2
8.
Click
When the substitute accesses the approval page, he or she will be able to view
and approve invoices for the substituted person.
VIM060000-AGD-EN-3
Administration Guide
41
Chapter 8
VIM Analytics
Execute the MIR4 transaction (for PO invoices) or the FB03 transaction (for Non
PO invoices).
MIR4 transaction
FB03 transaction
VIM060000-AGD-EN-3
43
2.
Enter the invoice document number, the fiscal year (and the company code in
FB03) and click the Display doc button (press RETURN in FB03).
3.
44
VIM060000-AGD-EN-3
8.1
In the Process History panel, the statuses of one or more workflow processes
are displayed. Each process has a separate line. The processes can have one of
the following types:
4.
DP dashboard process
To display details of a process, click the View button at the beginning of the
line.
Approval process details
Click the
Click the
VIM060000-AGD-EN-3
Administration Guide
45
46
VIM060000-AGD-EN-3
8.2
2.
If you know the document number, enter it in the Document Number field.
Otherwise, search by any selection criteria.
3.
VIM060000-AGD-EN-3
Administration Guide
47
The report shows all applicable invoices, based on your selection criteria.
The Current Agent column indicates the current owner of the work item.
4.
48
To access the Unified Dashboard, select an invoice and click the Dashboard
button.
VIM060000-AGD-EN-3
Chapter 9
To access the Selection Report for Work Items, execute the SWI1 transaction.
VIM060000-AGD-EN-3
49
2.
WS00275269
WS00275260
WS00275254
WS00275252
WS00275264
WS00275266
Date created
Enter date range.
Time created
Enter time range.
Tip: You can save the selection criteria as a variant. From the menu, click
Goto > Variants > Save as variant.
3.
All VIM workflows that have been started during the specified interval are
displayed on the Work item selection screen.
50
VIM060000-AGD-EN-3
VIM060000-AGD-EN-3
Administration Guide
51
The St (Status) column indicates the status of each individual step of the
workflow:
Ready for processing
In process, but not completed
Completed
Error
Click the
icon next to a workflow step to display the agents who own this
work item (or possible or excluded agents).
5.
52
VIM060000-AGD-EN-3
In the Workflow Log (View with technical details), click the highlighted Error
field to display the error messages generated by the system.
If the error message shows the indicator Error or exception resolving role
<...>, role maintenance is required through the role maintenance transaction.
VIM060000-AGD-EN-3
Administration Guide
53
Chapter 10
To access the Selection Report for Work Items, execute the SWI1 transaction.
2.
VIM060000-AGD-EN-3
55
Status
ERROR
Task
Click the multiple selection button
WS00275269
WS00275260
WS00275254
WS00275252
WS00275264
WS00275266
Date created
Enter date range.
Time created
Enter time range.
Tip: You can save the selection criteria as a variant. From the menu, click
Goto > Variants > Save as variant.
3.
All VIM workflows with status Error that have been started during the specified
period are displayed on the Work item selection page.
4.
56
VIM060000-AGD-EN-3
5.
In the Workflow Log (View with technical details), click the highlighted Error
field to display the error messages generated by the system.
6.
VIM060000-AGD-EN-3
Administration Guide
57
The element ACTOR or Next Role indicates which role is causing the error. In
the example above, the error role is INFO_PROVIDER.
7.
58
To access the Workflow Restart After Error screen, execute the SWPR
transaction.
VIM060000-AGD-EN-3
2.
WS00275269
WS00275260
WS00275254
WS00275252
WS00275264
WS00275266
Tip: You can save the selection criteria as a variant. From the menu, click
Goto > Variants > Save as variant.
3.
4.
Select the workflow you want to restart and click the Restart workflow button.
VIM060000-AGD-EN-3
Administration Guide
59
If the workflow is restarted successfully, the entry in the Status column changes
from ERROR to STARTED.
60
VIM060000-AGD-EN-3
Chapter 11
VIM060000-AGD-EN-3
61
2.
US
ID
SAP user ID of the specific user
Select the option button To be processed by.
3.
62
VIM060000-AGD-EN-3
The report shows all SAP work items belonging to the user, regardless of
whether they are VIM work items or not.
VIM work items have the following task IDs:
TS00275278
DP Document Dashboard
TS00275267
PO Invoice Dashboard (Header WF)
TS00275262
PO Parked Invoice Dashboard
TS00275260
Non PO Invoice Dashboard
TS00275265
PO Invoice Dashboard (Line Level)
4.
Click the
VIM060000-AGD-EN-3
Administration Guide
63
With the work item IDs, you can assign the work items to a different user, see
Reassigning Open SAP Work Items to a Different User on page 64.
64
To access the Execute work items without agent check screen, execute the SWIA
transaction.
VIM060000-AGD-EN-3
2.
Enter the work item ID retrieved in Retrieving Open SAP Work Items of a
to execute.
Specific User on page 61 and click
Before you can reassign, you must be an owner of the work item.
3.
To own the work item, select it and click the Without check button in the
application tool bar.
This action leads you into either the VIM Dashboard or the DP Dashboard.
VIM060000-AGD-EN-3
Administration Guide
65
66
4.
Click
5.
Click the
6.
Click the
VIM060000-AGD-EN-3
7.
Enter the SAP user ID of the receiver of the work item and click
to execute.
2.
VIM060000-AGD-EN-3
Administration Guide
67
If the Invoice Data is known, enter the Company Code, the Document
Number, and the Fiscal Year for the invoice you want to reassign and click
to execute.
The system retrieves the current approver for this invoice and the rest of the
invoices waiting for his or her approval.
68
3.
4.
To show the details of the invoice, click the document number in the navigation
panel on the left-hand side.
VIM060000-AGD-EN-3
5.
6.
7.
VIM060000-AGD-EN-3
Administration Guide
69
70
VIM060000-AGD-EN-3
Chapter 12
2.
In the Invoice Lock Clean up program screen, enter the following information:
Invoice Type
Invoice Key
Enter the invoice key which is composed as follows:
Test Only
Select this check box and click
locked.
Tip: If you leave the Invoice Type and Invoice Key fields empty, all
currently locked invoices are displayed.
3.
VIM060000-AGD-EN-3
71
72
VIM060000-AGD-EN-3
Chapter 13
Administering Workflows
This chapter covers general activities for checking the system status of VIM:
Backup on page 80
You can conduct system performance checks using the SAP standard tools. The
SE30 transaction, for example, provides a runtime analysis of projects and
components.
You can use all the SAP standard logs and other infrastructure like the SM13 and
SM21 transactions for monitoring.
VIM060000-AGD-EN-3
73
The following sections describe how to use the SAP Standard CCMS functionality
for alert monitoring.
74
Monitor
Usage
Availability:
Selected Systems
Background
Processing
Buffers
The various SAP buffers, their hit rates, and swap rates
Change &
Transport System
Communications
Data Archiving
VIM060000-AGD-EN-3
Database
Dialog Overview
Enqueue
Entire System
Operating
System
Operating system data for any application servers and host systems
Security
Spool System
Spool system of the SAP system and the individual output servers
Syslog
System log broken down by application servers and individual topic areas
System Configuration
You can copy these monitors and change them. See the SAP online help for more
details:
http://help.sap.com/saphelp_nw70/helpdata/en/28/83493b6b82e908e10000000a1
1402f/content.htm.
To start a monitor, perform the following steps:
To start a CCMS templates based monitor:
1.
Execute the RZ20 transaction and select the menu option Extras > Activate
maintenance function.
In the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates
menu.
VIM060000-AGD-EN-3
Administration Guide
75
2.
76
VIM060000-AGD-EN-3
3.
4.
VIM060000-AGD-EN-3
Administration Guide
77
As CCMS is a standard monitoring tool from SAP, VIM does not require specific
values for the property thresholds. SAP basis needs to decide the level and to set
the thresholds for this.
To set threshold values:
a.
b.
button.
78
VIM060000-AGD-EN-3
monitor the activity and resources as the business processes are proceeding. For
activity monitoring purposes, see Frequently Used SAP Workflow Administration
Transactions on page 84.
2.
Select the required trace modes and click on the appropriate button under Trace
Requests to start the performance analysis.
VIM060000-AGD-EN-3
Administration Guide
79
SAP workflow logs are written for every activity of the process and therefore are
always available.
In addition to the standard system logs, you can use the SM21 transaction to check
system activities. See Frequently Used SAP Workflow Administration
Transactions on page 84 for transactions you can use for activity logging and
traces.
VIM also writes log to the standard system log infrastructure. See Working with
the Application Log on page 175 for details.
13.7 Backup
The configuration of VIM is stored inside SAP ERP, in the OpenText product tables.
A backup of the underlying SAP ERP system ensures the backup of the appropriate
configuration, runtime and persistent data. In addition, system transports store any
configuration changes that are made.
80
VIM060000-AGD-EN-3
2.
To schedule the Event Queue Job, execute the SWEQADM transaction. You
can set the frequency according to your requirement how often to update
the respective data.
The following event linkages can be turned on or off to enable or disable VIM
workflows:
Table 13-1: Event linkages for VIM workflows
Object type
FIPP
VIM060000-AGD-EN-3
Event
Receiver type
DELETED
SWW_WI_CREATE_VIA_EVENT
TS00275270
Administration Guide
Usage comments
Invoice Approval (IAP)
81
Object type
FIPP
BUS2081
BUS2081
BUS2081
/OPT/FIPP
/OPT/B2081
FIPP
FIPP
BUS2081
BUS2081
BUS2081
BUS2081
Event
Receiver type
POSTED
SWW_WI_CREATE_VIA_EVENT
TS00275270
DELETED
SWW_WI_CREATE_VIA_EVENT
TS00275270
POSTED
SWW_WI_CREATE_VIA_EVENT
TS00275270
POSTED
/OPT/BL_PO_BLK_RECEIVER
WS00275264
ZWFI_CREATED
/OPT/BL_NPO_PRK_RECEIVER
WS00275254
/PTGWFI/PIR_F_CHECKFM
ZWFI_PARKED
/OPT/BL_PO_PRK_RECEIVER
WS00275260
/PTGWFI/PRK_M_CHECKFM
DELETED
/OPT/VIM_RPT_RECEIVER_FM
POSTED
/OPT/VIM_RPT_RECEIVER_FM
DELETED
/OPT/VIM_RPT_PO_INV_RECEIVER
POSTED
/OPT/VIM_RPT_PO_INV_RECEIVER
RELEASED
/OPT/VIM_RPT_PO_INV_RECEIVER
CANCELLED
/OPT/VIM_RPT_PO_INV_RECEIVER
Usage comments
IAP
IAP
IAP
IE
VIM Analytics
(VAN)
VAN
VAN
VAN
VAN
VAN
82
To open the Event Type Linkages screen, execute the SWE2 transaction.
VIM060000-AGD-EN-3
2.
Create the event linkage entries shown in Table 13-1 (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 subsequent
systems.
VIM060000-AGD-EN-3
Administration Guide
83
Note: Repeat the procedure for all event linkage entries shown in Table 13-1.
To reassign open SAP work items to a different user, execute the SWIA
transaction. See the description in Reassigning Open SAP Work Items to a
Different User on page 64.
To display all work items (workflow template, dialog task, wait step,
background task) based on a custom selection, execute the SWI1 transaction. See
the description in Monitoring VIM Workflows on page 49.
To display or change event type linkages for VIM workflows, execute the SWE2
transaction. See the description in Linking Events for VIM Workflows on
page 81.
84
VIM060000-AGD-EN-3
2.
VIM060000-AGD-EN-3
button.
Administration Guide
85
3.
Amongst others, the Receiver function module and the status of the action is
displayed.
86
VIM060000-AGD-EN-3
Retrieve open work items belonging to a specific user. See Retrieving Open SAP
Work Items of a Specific User on page 61.
The following list shows all dialog standard tasks that can be used for SAP standard
reports:
TS00275278
DP Document Dashboard
TS00275267
PO Blocked Invoice Dashboard (Header WF)
TS00275265
PO Blocked Invoice Dashboard (Line Level)
TS00275262
PO Parked Invoice Dashboard
TS00275260
Non PO Parked Invoice Dashboard
TS00275253
Invoice awaiting web approval
Note: The web approval work items are always assigned to WF-BATCH
because the actual action is performed by the user on the web approval
page.
According to OSS 1227739, it is no longer possible to forward dialog work
items to a background user. You can apply the correction according to the
OSS note or the corresponding SAP Support Package. In function
SWW_WI_FORWARD, an additional check is applied to retrieve the user type
(dialog or background).
Solution: Work items that have to be executed by a non SAP user must be
assigned to a dialog user and not to WF-BATCH.
Correction instructions: Create a dummy user of type dialog user in the
SAP system. You do not have to assign specific authorizations to the user.
Then overwrite the existing default entry WF-BATCH for parameter
SAP_PROXY_ID (Product Code IAP) in table /PTGWFI/Z_CONST with the
dummy user, using the SM30 transaction.
For a list of workflow templates for the VIM process, see Monitoring VIM
Workflows on page 49.
VIM060000-AGD-EN-3
Administration Guide
87
SWWWIHEAD
SWW_CONT
SWW_CONTOB
SWIVOBJECT
Join SWW_CONTOB with SWWWIHEAD
SWELOG
SWWORGTASK
Agent assignment of work item. The agent assignment information for a particular work item is deleted once the work item is completed.
88
VIM060000-AGD-EN-3
Chapter 14
VIM060000-AGD-EN-3
89
Settings
New Posting Date
This field is mandatory.
Test mode (display invoices)
This check box is selected by default. The invoices resulted from the search
are only displayed.
There is no VIM functionality available in the test mode but you can add and
change the displayed fields, using the standard SAP layout button.
Exclude empty posting dates
Select this check box only in special cases where the posting date is not filled
and should not be updated.
Document options All ranges in this area are standard search criteria for DP
invoices.
2.
To execute the bulk change, clear the Test mode check box and click
A dialog box opens, asking for confirmation. In the dialog box, you still can
cancel the whole processing.
3.
90
VIM060000-AGD-EN-3
The bulk change also updates VIM Analytics and writes an entry in the process
logs.
VIM060000-AGD-EN-3
Administration Guide
91
Chapter 15
2.
3.
Click
VIM060000-AGD-EN-3
93
4.
94
In the Copy menus panel, click the From area menu button.
VIM060000-AGD-EN-3
5.
6.
Click
VIM060000-AGD-EN-3
Administration Guide
95
7.
Select all check boxes under Area menu and click the Add button at the bottom
of the dialog.
8.
9.
96
button.
VIM060000-AGD-EN-3
11. Enter appropriate values in the From and To field and click the Full
authorization button.
12. Click the
VIM060000-AGD-EN-3
Administration Guide
97
13. Expand all nodes and assign Display authorization to the needed Activity
icon next to the field.
fields. To define values for an Activity field, click the
14. To add Display authorization for all transaction starting with /OPT/, click the
Manually button in the application tool bar.
98
VIM060000-AGD-EN-3
15. In the Manual selection of authorizations dialog, enter S_TCODE in the topmost
to confirm.
Authorization object line and click
The new authorization object is displayed in the Change role: Authorizations
screen.
VIM060000-AGD-EN-3
Administration Guide
99
to save.
icon to return to the Change Roles main screen and open the User
21. Enter the early watch user or a different user that you want to assign to the
newly created Display VIM configuration role.
22. Save your settings.
100
VIM060000-AGD-EN-3
Users assigned to the new role are allowed to view the VIM configuration with
display only authorization.
VIM060000-AGD-EN-3
Administration Guide
101
Chapter 16
Find out all workflow work items for each current agent
Determine the due date for each work item using an SAP standard or
customized Function Module
Send an email or an SAP note to one or more selected current agents, to remind
them of due work items.
Note: The VIM Notifications functionality currently does not support the
Additional Role and the Notify Substitute features.
VIM060000-AGD-EN-3
103
The selection screen allows you to enter search criteria and process options. The
selection screen is divided into the following panels:
2.
Invoice Information
Document Process
Process Options
Recipient of Reminder
104
for search
VIM060000-AGD-EN-3
Company Code
Document Number
Fiscal Year
Line Item
Document ID: the number that was generated for the document during
the DP process
SAP User ID
OpenText User Id
Note: When adding user IDs as search criteria, the system does not
consider the substitutes for the user, if there are any.
3.
VIM060000-AGD-EN-3
Document Processing
PO Parked Invoices
PO Referred Invoices
Administration Guide
105
Mode
Select one of the process modes:
Test
The program generates a list of eligible work items for notification.
The program does not send the notifications. Users can select the
work items to send the notification.
Background
The program sends the notification to users and displays the work
items.
4.
Once you finished entering the search criteria and selecting the process options,
in the application tool bar to display the VIM Notifications List with
click
the search results.
106
VIM060000-AGD-EN-3
VIM060000-AGD-EN-3
Administration Guide
107
Filter: Select a report column in the list and click this button. The Filter
criteria dialog is displayed, allowing you to restrict the criteria in the
selected column without having to rerun the report with new search criteria.
Tip: Use
Layout: Click this button to select a saved layout. To change, save or manage layouts of the list, click the icon next to the Layout button.
108
The following list only covers columns whose meaning is not obvious.
VIM060000-AGD-EN-3
Column
Description
Current Agent
Process Type
Sub Process
Type
Sub Process Type for each process type, for example Approval Required
for Non PO Invoice Approval process type
Document
Number
Document ID
DP document ID
Vendor
Vendor number
Name 1
Vendor name
Inbox Days
Before Due
Due Date
First name
Last name
Responsible
Party
Receiver ID
ID
Work item ID
VIM060000-AGD-EN-3
Administration Guide
109
2.
To edit an existing notification, mark the respective line and click the
in the application tool bar. See the parameter description in step 3.
button
Note: You cannot change the Notification Scenario and the Sub Scenario
for an existing notification.
3.
To add a notification, click the New entries button in the application tool bar.
110
Document Processing
VIM060000-AGD-EN-3
PO Parked Invoices
PO Invoice Approvals
Sub Scenario
Select the notification sub scenario. Possible values depend on the selected
notification scenario.
Example:
Notification sub scenarios for the Non PO Parked Invoices notification
scenario:
Approval Required
Vendor Maintenance
All Scenarios
Role
Select the role for the notification. All users assigned to this role will receive
the notification.
Notify Substitutes
This feature is not supported at the moment.
Additional Role
This feature is not supported at the moment.
Inbox Days
Days Before Payment Due
Use these fields to decide if the reminder will be sent. The system calculates
the work item creating date plus the inbox days or the days before payment
is due. If the result is less or equal today's date, then a reminder will be sent.
Email Type
Select the notification type. At the moment, only Internet Email is
available.
Notification Text
Select the SAP text name to be used for the notification email body.
VIM060000-AGD-EN-3
Administration Guide
111
112
1.
2.
VIM060000-AGD-EN-3
Field name
You find the field names in structure /OPT/VIM_S1_REMINDER_DISPLAY.
Each field name represents a field in the VIM Notifications report.
Note: You cannot change this parameter in the Mail Configuration
screen.
Language
VIM supports the following languages:
German (DE)
English (EN)
Spanish (ES)
French (FR)
Italian (IT)
Japanese (JA)
Dutch (NL)
Portuguese (PT)
Russian (RU)
Chinese (ZH)
Notes:
Position
Specify the sequence of the fields in the email body.
Field Length
Specify the length of the field.
Text
Enter the title for each field in the respective language.
3.
VIM060000-AGD-EN-3
Administration Guide
113
2.
German (DE)
English (EN)
Spanish (ES)
French (FR)
Italian (IT)
Japanese (JA)
Dutch (NL)
Portuguese (PT)
Russian (RU)
Chinese (ZH)
Notes:
Mail Title
Enter the title of the notification email in the respective language(s).
3.
114
VIM060000-AGD-EN-3
2.
To exclude another user, click the New entries button in the application tool
bar.
3.
VIM060000-AGD-EN-3
Administration Guide
115
User Id
Enter the user ID to be excluded, corresponding to the selected user type.
Disable Notification
Mark this field with X to disable VIM Notifications emails.
Single Notification
Mark this field with X to have VIM Notifications emails sent only once per
work item instead of multiple times during the notification period.
Language Pref
Select the preferred language of the emails. VIM supports the following
languages:
German (DE)
English (EN)
Spanish (ES)
French (FR)
Italian (IT)
Japanese (JA)
Dutch (NL)
Portuguese (PT)
Russian (RU)
Chinese (ZH)
Note: Japanese and Chinese are supported only in SAP ECC 6.0.
4.
116
VIM060000-AGD-EN-3
2.
VIM060000-AGD-EN-3
German (DE)
English (EN)
Spanish (ES)
French (FR)
Italian (IT)
Japanese (JA)
Dutch (NL)
Portuguese (PT)
Administration Guide
117
Russian (RU)
Chinese (ZH)
Note: Japanese and Chinese are supported only in SAP ECC 6.0.
3.
Click
2.
4.
118
Click
VIM060000-AGD-EN-3
Chapter 17
VIM060000-AGD-EN-3
119
Chapter 18
Aggregation
Central Audit Report (see section 14 "Using the Central Audit Report" in
OpenText Vendor Invoice Management - User Guide (VIM-UGD))
Key Process Analytics Report (see section 16 "Using the Key Process Analytics
Report" in OpenText Vendor Invoice Management - User Guide (VIM-UGD))
Exception Analysis Report (see section 17 "Using the Exception Analysis Report"
in OpenText Vendor Invoice Management - User Guide (VIM-UGD))
Aging Report (see section 19 "Using the Aging Report" in OpenText Vendor
Invoice Management - User Guide (VIM-UGD))
License Report (see section 20 "Using the License Report" in OpenText Vendor
Invoice Management - User Guide (VIM-UGD))
To ensure good performance for the reports in Central Reporting, the data used for
the reports must be aggregated and saved in Reporting Data Tables. To achieve this
goal, the data is prepared in several different activities:
1.
The Collection Report, the User Master Report, and the Text Master Report get
master data and transaction data from their original tables and save the data in
the Source Data Tables. See Scheduling the Collection Report on page 132 for
details.
2.
The Aggregation Report selects data from the Source Data Tables (in different
logical systems, if required), aggregates, transforms and saves the data in the
Reporting Data Tables of the current system.
3.
The reports in Central Reporting are end user reports based on the content of
the Reporting Data Tables. For information about administration of Central Reporting, see the description in this chapter.
VIM060000-AGD-EN-3
121
Administration
steps
Maintaining logical systems and System Landscape Directory (SLD), see section
20.1 "Configuring the System Landscape Directory (SLD)" in OpenText Vendor
Invoice Management - Configuration Guide (VIM-CGD)
2.
3.
4.
5.
6.
Scheduling reports:
7.
Groups
Collection Report
Data in Source Data Tables changes during the use of VIM. Therefore, the
aggregation of data to the Reporting Data Tables must run regularly. OpenText
strongly recommends scheduling batch jobs for this purpose. For different tables,
the necessary frequency to update will differ considerably. For example, the SAP
Vendors Table will change much less frequently than the Workitem Agents Table.
For this reason, several default groups, comprising specific tables, are set up for the
aggregation:
Groups beginning with OTH* are used by the Central Audit Report only. The other
groups are used by the other central reports.
CUST_PREFL
Comprises Roles and Exception Mapping. This group is used to prefill the
customizing tables for roles and exceptions (see Maintaining Reporting Tables
on page 128) to ease customizing.
TRANSACT
MASTER
USER
122
VIM060000-AGD-EN-3
Scheduling the Aggregation Report for the following groups is only necessary in a
multiple backend system.
OTH_MASTER
OTH_DCHEAD
OTH_VMHEAD
OTH_AGENT
Recommended to run twice a day. The frequency can vary depending on business needs. Group ID OTH_AGENT replicates the data from table
/OPT/VT_WI_AGENT to the Central System. This data replication is useful for current agent display in the Central Audit Report.
Baseline groups
To display the groups that are delivered with Baseline, execute the /n/OPT/SPRO
transaction and follow LiveLink VIM - Configuration > Central Reporting >
Aggregation infrastructure > Aggregation report groups.
Note: OpenText strongly recommends not to change the Baseline groups.
VIM060000-AGD-EN-3
Administration Guide
123
Target data
tables
To display the Baseline target data tables that will be filled by the Aggregation
Report, execute the /n/OPT/SPRO transaction and follow LiveLink VIM Configuration > Central Reporting > Aggregation infrastructure > Aggregation
report target tables.
Target and source tables are displayed, depending on the Aggregation Group ID.
Note: OpenText strongly recommends not to change the Baseline target data
tables.
124
VIM060000-AGD-EN-3
To display the Aggregation report: Back end systems screen, execute the
/OPT/VIM_ABE transaction.
Alternatively, follow LiveLink VIM - Configuration > Central Reporting >
Aggregation infrastructure > Back end systems
2.
3.
Add all logical systems you want to use in the Aggregation Report.
Optional
Note: The wrapper function on the logical system returns the source table
content as an XML stream to the central system, because it is not possible
to hand over internal tables as generic types in RFC. If the fields Character
set and Byte order remain blank, the system default will be used. In case of
XML conversion problems during execution of the Aggregation Report,
you can specify the encoding to be used in these fields.
In this case, define the encoding, using the following fields:
Character set
Enter the character set, for example UTF-8.
Byte order
Enter the byte order, for example 1 if the character set uses big endian byte
ordering.
VIM060000-AGD-EN-3
Administration Guide
125
Note: For character sets and byte orders supported by SAP, see the SAP
documentation.
If you are not sure about the correct settings for your system, try the following:
a.
In the related back end system, call the SE37 transaction and execute
function module SYSTEM_CODEPAGE.
The codepage of the system is displayed.
b.
c.
Use the codepage number returned by the previous function module call
(for example 4103) as selection value for field CPCODEPAGE.
In the selected dataset, the field CPCOMMENT contains most often a
description of the character set it contains (for example ISO-8859-1 or UTF16BE).
126
1.
2.
VIM060000-AGD-EN-3
3.
4.
VIM060000-AGD-EN-3
Administration Guide
127
Invoke the Aggregation Report screen, see To run the Aggregation Report for
the CUST_PREFL group: on page 126.
2.
Enter the Group ID and configure the report for this group, according to your
needs. See step 3 on page 127.
3.
Click
4.
In the ABAP: Save as Variant screen, enter Variant name and Description and
save.
5.
to save as variant.
Role Maintenance: Define the roles to be used in the reports. See To maintain
roles for Central Reporting: on page 128.
Role Mapping Maintenance: Map roles from all the logical systems that have
been maintained for usage in the Aggregation Report. See To map roles from
several back end systems: on page 130.
Exception Mapping Maintenance: Map exceptions from all the logical systems
that have been maintained for usage in the Aggregation Report. See To map
exceptions for several back end systems: on page 131.
128
In the VIM Customizing IMG, select Central Reporting > Report Table
Maintenance > Role Definition and Mapping > Role Maintenance.
VIM060000-AGD-EN-3
2.
3.
In the VIM Customizing IMG, select Central Reporting > Report Table
Maintenance > Exception Definition and Mapping > Exception Definition
Maintenance.
VIM060000-AGD-EN-3
Administration Guide
129
2.
3.
Once you have run the Aggregation Report for the CUST_PREFL group, the
customizing tables for Role Mapping Maintenance and Exception Mapping
Maintenance are prefilled. To map roles/exceptions from several back end systems,
perform the following steps:
To map roles from several back end systems:
1.
130
In the VIM Customizing IMG, select Central Reporting > Report Table
Maintenance > Role Definition and Mapping > Role Mapping Maintenance.
VIM060000-AGD-EN-3
The columns Product Code, and Responsible Party have been prefilled
automatically.
2.
Assign the Role ID (as defined in To maintain roles for Central Reporting: on
page 128) to each responsible party (role) for specific product code.
3.
In the VIM Customizing IMG, select Central Reporting > Report Table
Maintenance > Exception Definition and Mapping > Exception Mapping
Maintenance.
VIM060000-AGD-EN-3
Administration Guide
131
The columns Exc. Type, and Exc.typeID (Exception Type ID) have been
prefilled automatically.
2.
132
VIM060000-AGD-EN-3
Scheduling
Cut-off date
The only mandatory selection criterion is Creation Date From. You must set this
date. It refers to the cut-off date, the work item creation date. Any invoices created
before this date are not considered in reporting. You can combine the Creation Date
From field with the Creation Time From field. If you also provide Creation Time
From, date and time together decide the cut-off time period.
Cut-off is important because Central Reporting is based on new workflow task
container elements and a new DP workflow template, created in VIM 5.2. You
cannot use data from VIM versions older than 5.2 for the reports. The cut-off time
period is used to filter out any data that belongs to older versions.
With a new installation, use the installation or go-live date for the Creation Date
From. With an upgrade, use the date of upgrading.
Do not maintain selection parameters other than Creation Date From and Creation
Time From.
Note: You can use the parameters Task and ID for testing purposes. The parameters refer to the workflow dialog task and the work item ID.
Table
/OPT/VT_JOB
The last run time of the Collection Report is stored in table /OPT/VT_JOB. At the first
time the Collection Report runs, table /OPT/VT_JOB is empty. Thereafter, the last run
time always gets updated in this table.
Note: If you select Test Mode, the data is not saved to source tables or any table. Even /OPT/VT_JOB will remain unchanged.
Once scheduled, this report always runs in delta mode. Only those work items and
documents are considered that have changed since the last run. Delta mode is
default and fixed. To change to full mode, you must clean table /OPT/VT_JOB.
VIM060000-AGD-EN-3
Administration Guide
133
134
VIM060000-AGD-EN-3
Multiple backend
In a single system scenario, the Central System is the same as the current system.
Schedule the Aggregation Report with all Group IDs, except the Group IDs that
start with OTH_*.
In a multiple backend system, schedule the Aggregation Report with all Group IDs,
including the Group IDs that start with OTH_*.
Collection Report
VIM060000-AGD-EN-3
Administration Guide
135
Aggregation Report
Most suited for this purpose are batch jobs. This section describes how to schedule a
batch job for the Aggregation Report. Scheduling batch jobs for the other reports is
similar. Keep in mind that the sequence of the jobs is important. Schedule Collection
Report, User Master Report, and Text Master Report before Aggregation Report.
After you have created variants of the Aggregation Report for the TRANSACT,
MASTER, and USER groups (see Creating Variants of the Aggregation Report for
Each Group on page 128), you can schedule one batch job with several steps or a
dedicated batch job for each variant. The procedure below shows how to schedule a
batch job for a single group.
Regarding the order of the other groups for the batch job, the job for the TRANSACT
group should be scheduled after MASTER and USER jobs. In a multiple backend
system, also schedule jobs for the Group IDs that start with OTH*. You have to
consider how often it is necessary to update the respective data and schedule the job
accordingly.
To schedule a batch job for the Aggregation Report:
136
1.
2.
3.
4.
VIM060000-AGD-EN-3
5.
By Date/Time or
After job
For Date/Time, click Period values and Restrictions to add date/time details.
6.
Click
7.
VIM060000-AGD-EN-3
to save.
Administration Guide
137
8.
In the ABAP program panel, enter the name /OPT/VR_A_AGGREGATION and the
variant you created before.
9.
Click
to save.
You might need to clean up the Central Reporting tables, for example to reload data
after fixing some issues. Whereas VIM Analytics bases on real time VIM tables,
Central Reports base on tables that are not real time. Collection Report, User Master
138
VIM060000-AGD-EN-3
Report, and Text Master Report pull information from real time VIM tables and
provide data to Source Data Tables. The Aggregation Report selects data from the
Source Data Tables and provides data to the Reporting Data Tables. As Source Data
Tables and Reporting Data Tables are not real time, these tables can be reloaded.
To run the cleanup report, execute the SA38 transaction with program
/OPT/VR_CLEAN_TABLES.
Report Tables
Select this check box to delete Reporting Data Tables.
Important
This will clean up all data in the end user Central Reports.
Source Tables
Select this check box to delete Source Data Tables.
This will not impact the end user Central Reports, except the Central Audit
Report.
You can define threshold values for an attention status and a critical status. If the
attention value is exceeded in a cell (or falls below it for the First Pass panel), the cell
is highlighted in orange. If the critical value is exceeded in a cell (or falls below it for
the First Pass panel), the cell is highlighted in red.
The following screenshot shows an example in the Total Liability panel:
VIM060000-AGD-EN-3
Administration Guide
139
To enter the WebFlow Constant Table where you maintain the constants,
execute the /n/OPT/VIM_KPA_CFG transaction.
Alternatively, in the VIM Customizing IMG, select Central Reporting >
Maintain Constants > Maintain Constants for Key Process Analytics.
140
VIM060000-AGD-EN-3
2.
where you must replace all <value> fields with a number, as follows:
Value 1 and 2 define the lower and upper threshold for the total number of First
Pass PO Invoices.
Value 3 and 4 define the lower and upper threshold for the total number of First
Pass NPO Invoices.
Value 5 and 6 define the lower and upper threshold for the total number of all
First Pass Invoices.
If the total number of First Pass invoices is lower than value 1/3/5, the respective
cell is marked red.
If the total number of First Pass invoices is greater or equal than value 1/3/5 but
lower than value 2/4/6, the respective cell is marked orange.
If any of the values is not maintained, the respective check is not done and the cell
will not be colored.
VIM060000-AGD-EN-3
Administration Guide
141
If the total number of First Pass PO Invoices is lower than 10,000, the respective cell
will be marked red.
If the total number of First Pass PO Invoices is greater or equal than 10,000 but lower
than 30,000, the respective cell will be marked orange.
If the total number of First Pass NPO Invoices is lower than 10,000, the respective
cell will be marked red.
If the total number of First Pass NPO Invoices is greater or equal than 10,000 but
lower than 30,000, the respective cell will be marked orange.
If the total number of all First Pass Invoices is lower than 20,000, the respective cell
will be marked red.
If the total number of all First Pass Invoices is greater or equal than 20,000 but lower
than 60,000, the respective cell will be marked orange.
142
VIM060000-AGD-EN-3
The total number of first pass invoices is checked against the thresholds for the All
Invoices line, only.
If the total number of all First Pass Invoices goes below 20,000, the respective cell
will be marked red.
If the total number of all First Pass Invoices is greater or equal than 20,000 but lower
than 60,000, the respective cell will be marked orange.
where you must replace all <value> fields with a percentage quotation, as follows:
Value 1 and 2 define the lower and upper threshold for the percentage of First
Pass PO Invoices.
Value 3 and 4 define the lower and upper threshold for the percentage of First
Pass NPO Invoices.
Value 5 and 6 define the lower and upper threshold for the percentage of all First
Pass Invoices.
If the percentage of First Pass invoices is lower than value 1/3/5, the respective cell
is marked red.
If the percentage of First Pass invoices is greater or equal than value 1/3/5 but
lower than value 2/4/6, the respective cell is marked orange.
VIM060000-AGD-EN-3
Administration Guide
143
If any of the values is not maintained, the respective check is not done and the cell
will not be colored.
Example 18-3: Constant KPA_TS_1STPASS_PERC
If the percentage of First Pass PO Invoices/First Pass NPO Invoices/all First Pass
Invoices goes below 0.1%, the respective cell will be marked red.
If the percentage of First Pass PO Invoices/First Pass NPO Invoices/all First Pass
Invoices is greater or equal than 0.1% but lower than 1%, the respective cell will be
marked orange.
where you must replace all <value> fields with data, as follows:
Value 2 and 3 define the lower and upper threshold for the amount of Blocked
Documents.
If the amount of Blocked Documents is greater than the lower threshold but smaller
or equal than the upper threshold, the respective cell is marked orange.
If the amount of Blocked Documents exceeds the upper threshold, the respective cell
is marked red.
144
VIM060000-AGD-EN-3
The currency value must be maintained if you want to use the threshold
functionality. If any of the other values is not maintained, the respective check is not
done and the cell will not be colored.
Example:
A Constant Value of USD;;20000 results in the following:
If the amount of Blocked Documents is greater than 20,000 USD, the respective cell
is marked red. The cell will never be marked orange because the respective value is
not maintained.
Example 18-4: Constant KPA_TS_LIAB_AMOUNT1
If the amount of Blocked Documents is greater than 10,000 USD but smaller or equal
than 20,000 USD, the respective cell is marked orange.
If the amount of Blocked Documents is greater than 20,000 USD, the respective cell
is marked red.
where you must replace all <value> fields with data, as follows:
Value 2 and 3 define the lower and upper threshold for the amount of Parked
Documents.
If the amount of Parked Documents is greater than the lower threshold but smaller
or equal than the upper threshold, the respective cell is marked orange.
VIM060000-AGD-EN-3
Administration Guide
145
If the amount of Parked Documents exceeds the upper threshold, the respective cell
is marked red.
The currency value must be maintained if you want to use the threshold
functionality. If any of the other values is not maintained, the respective check is not
done and the cell will not be colored.
Example:
A Constant Value of USD;;20000 results in the following:
If the amount of Parked Documents is greater than 20,000 USD, the respective cell is
marked red. The cell will never be marked orange because the respective value is
not maintained.
Example 18-5: Constant KPA_TS_LIAB_AMOUNT2
If the amount of Parked Documents is greater than 5,000 USD but smaller or equal
than 15,000 USD, the respective cell is marked orange.
If the amount of Parked Documents exceeds 15,000 USD, the respective cell is
marked red.
where you must replace all <value> fields with data, as follows:
146
Value 2 and 3 define the lower and upper threshold for the amount of PreProcess Documents.
VIM060000-AGD-EN-3
If the amount of Pre-Process Documents is greater than the lower threshold but
smaller or equal than the upper threshold, the respective cell is marked orange.
If the amount of Pre-Process Documents exceeds the upper threshold, the respective
cell is marked red.
The currency value must be maintained if you want to use the threshold
functionality. If any of the other values is not maintained, the respective check is not
done and the cell will not be colored.
Example:
A Constant Value of USD;;20000 results in the following:
If the amount of Pre-Process Documents is greater than 20,000 USD, the respective
cell is marked red. The cell will never be marked orange because the respective
value is not maintained.
Example 18-6: Constant KPA_TS_LIAB_AMOUNT3
If the amount of Pre-Process Documents is greater than 20,000 USD but smaller or
equal than 30,000 USD, the respective cell is marked orange.
If the amount of Pre-Process Documents exceeds 30,000 USD, the respective cell is
marked red.
VIM060000-AGD-EN-3
Administration Guide
147
<Value1>;<Value2>;<Value3>;<Value4>;<Value5>;<Value6>;<Value7>;<Value
8>
where you must replace all <value> fields with a number, as follows:
Value 1 and 2 define the lower and upper threshold for the total number of
processed PO Invoices.
Value 3 and 4 define the lower and upper threshold for the total number of PO
Invoices in process.
Value 5 and 6 define the lower and upper threshold for the total number of
processed NPO Invoices.
Value 7 and 8 define the lower and upper threshold for the total number of NPO
Invoices in process.
If the number of invoices is greater than the lower threshold but smaller or equal
than the upper threshold, the respective cell is marked orange.
If the number of invoices is greater than the upper threshold, the respective cell is
marked red.
If any of the values is not maintained, the respective check is not done and the cell
will not be colored.
Example 18-7: Constant KPA_TS_PROCDOCS_NO
148
VIM060000-AGD-EN-3
If the total number of NPO Invoices in Process exceeds 250,000, the respective cell is
marked red.
Value 1 and 2 define the lower and upper threshold for the percentage of
Processed PO Invoices.
Value 3 and 4 define the lower and upper threshold for the percentage of PO
Invoices in Process.
Value 5 and 6 define the lower and upper threshold for the percentage of
Processed NPO Invoices.
Value 7 and 8 define the lower and upper threshold for the percentage of NPO
Invoices in Process.
If the percentage of invoices is greater than the lower threshold but smaller or equal
than the upper threshold, the respective cell is marked orange.
If the percentage of invoices is greater than the upper threshold, the respective cell is
marked red.
If any of the values is not maintained, the respective check is not done and the cell
will not be colored.
Example 18-8: Constant KPA_TS_PROCDOCS_PERC
VIM060000-AGD-EN-3
Administration Guide
149
150
VIM060000-AGD-EN-3
Chapter 19
VIM060000-AGD-EN-3
151
2.
152
VIM060000-AGD-EN-3
VIM060000-AGD-EN-3
Administration Guide
153
Output to screen
This program runs in background and collects the vendor information. If the
program is running in the central system, it collects the vendor information from all
satellite systems using function module /OPT/DOWNLOAD_LY_DATA. The program
stores the vendor information in the central systems staging table (along with the
satellite systems logical system).
Table /OPT/VIM_STG_LIF contains the following information:
Vendor number
Company code
Bank details
Vendor address
154
VIM060000-AGD-EN-3
2.
VIM060000-AGD-EN-3
Administration Guide
155
156
VIM060000-AGD-EN-3
Output to screen
The sections Open only check and Vendor substitution appear only, when the
respective processing options have been selected in the selection screen.
Note: The number in section Order number table gives the remaining number
of PO entries that are written to the staging table. In the example, 342 order
numbers have been found, 48 have been removed due to the open only
check, and 294 have been written to the staging table for download.
VIM060000-AGD-EN-3
Administration Guide
157
ICC can call RFC1 as needed if ICC wants to initialize all records in the Vendor
staging table with SYN_FLAG = space.
2.
ICC then calls RFC2 and subsequently RFC3 in loop until RFC2 tells that all
records have been pulled, by passing COMPLETE = X as part of its export
parameter.
3.
As soon as ICC gathers the information that all records have been pulled, it
passes indicator COMPLETE = C to VIM via RFC3 and exits the loop.
ICC also stops the looping when an error occurs in RFC2, then ICC passes an
indicator COMPLETE = E to VIM via RFC3, and then exits.
RFC1
RFC2
T_DL_QUERY
158
VIM060000-AGD-EN-3
Output parameters
T_VENDOR
CURRENTUPDATE
Current timestamp
COMPLETE
Indicates whether all records have been successfully extracted and no more left
for extraction
The function module gets all the vendors which are loaded on or after the
timestamp LASTUPDATE and moves that data to the internal table T_VENDOR.
Populate the timestamp CURRENTUPDATE from current date and time.
RFC3
Passes indicator C as soon as ICC gathers the information that all records
have been pulled and then exits the call.
Passes indicator E when an error occurs in RFC2 for Vendor download and
exits the call.
Output parameters
None
Note: The Z Constant VEND_REC sets the maximum batch size for Vendor
download data. You can check this value by executing the SM30 transaction,
entering table /PTGWFI/Z_CONST, and checking value corresponding to product
code 005 and Z constant VEND_REC.
ICC can call RFC1 as needed if ICC wants to initialize all records in the Purchase
Order staging table (/OPT/VIM_STG_POH) with SYN_FLAG = space.
2.
ICC then calls RFC2 and subsequently RFC3 in loop until RFC2 tells that all
records have been pulled, by passing COMPLETE = X as part of its export
parameter.
3.
As soon as ICC gathers the information that all records have been pulled, it
passes indicator COMPLETE = C to VIM via RFC3 and exits the loop.
VIM060000-AGD-EN-3
Administration Guide
159
ICC also stops the looping when an error occurs in RFC2, then ICC passes an
indicator COMPLETE = E to VIM via RFC3, and then exits.
RFC1
RFC2
POSITIONS
T_DL_QUERY
Output parameters
T_DL_POHEAD
T_DL_POITEM
CURRENTUPDATE
Current timestamp
The function module gets all the purchase orders from tables /OPT/VIM_STG_POH
and /OPT/VIM_STG_POI, which are loaded on or after the timestamp LASTUPDATE
and moves that data to the internal tables T_DL_POHEAD and T_DL_POITEM.
Populate the timestamp CURRENTUPDATE from current date and time.
RFC3
Passes indicator C as soon as ICC gathers the information that all records
have been pulled and then exits the call.
160
VIM060000-AGD-EN-3
VIM060000-AGD-EN-3
Administration Guide
161
Chapter 20
VIM060000-AGD-EN-3
163
164
VIM060000-AGD-EN-3
The program maps the extracted data to VIM table fields and updates the
/OPT/VIM_1HEAD and /OPT/VIM_1ITEM tables. You maintain the ICC field
mapping using the /N/OPT/VIM_MAPV transaction.
b.
c.
The program maps the extracted data to VIM table fields and updates the
/OPT/VIM_1HEAD and /OPT/VIM_1ITEM tables. You maintain the ICC field
mapping using the /N/OPT/VIM_MAPV transaction.
b.
To invoke the selection screen of the ICC Admin Tool, execute the
/N/OPT/VIM_7AX8 transaction.
VIM060000-AGD-EN-3
Administration Guide
165
2.
In the Program to Monitor ICC data screen, enter the selection criteria:
DP document number
Archive Doctype
Document Type
Status
3.
166
button.
VIM060000-AGD-EN-3
In the ICC Admin Tool screen, the following action buttons are available in the
application tool bar:
Image
Select a DP document and click this button to display the archived image of
the document.
Discard Image
Select a DP document and click this button to set the document status to
Obsolete. DP documents with status Obsolete cannot be considered for
further processing.
Appln Log
Application Log. Select a DP document and click this button to display the
System log of the document.
Reset Count
Click this button to set the Extraction and Validation retries counts to zero. If
the document is in a Limit Reached status, it is set in the appropriate Ready
for status.
Change Status
Select a DP document and click this button to set the document to a required
status. The Possible statuses screen is displayed. Select the required status
from the list and confirm with .
Status Log
Select a DP document and click this button to display the Status log of the
Document.
VIM060000-AGD-EN-3
Administration Guide
167
DP Trigger
Select a DP document and click this button to invoke the DP Trigger
program, which will either set the DP document status to Ready for
Validation or trigger the workflow.
Vald Agents
Validation Agents. Select a DP document and click this button to display the
Validation Agents of the document.
168
VIM060000-AGD-EN-3
Chapter 21
21.1 Overview
The IDoc process comprises the following steps:
1.
2.
3.
Trigger workflow.
You can test the whole process using the WE19 transaction, where you supply the
IDoc and the processing function module.
To start the Test tool for IDoc processing, execute the WE19 transaction.
VIM060000-AGD-EN-3
169
170
2.
3.
Click the Inbound function module button in the application tool bar. The Test
inbound IDoc via a function module dialog box is displayed.
VIM060000-AGD-EN-3
4.
to
5.
To check the status of the created IDoc, execute the WE02 transaction.
6.
Enter the IDoc number of the new IDoc into the IDoc number field and click
VIM060000-AGD-EN-3
Administration Guide
171
172
1.
To access the Data Browser: Initial Screen, execute the SE16 transaction.
2.
VIM060000-AGD-EN-3
3.
Enter the IDoc number in the EDI_DOCNUM field of the selection screen and
in the application tool bar.
click
VIM060000-AGD-EN-3
Administration Guide
173
Chapter 22
Input parameters
OBJECTID
The Object ID is the currently processing document number, for example the DP
Document number, IDOC number, Work Item, or Financial Document number.
LOG_POINT
The log point is a unique identifier of the calling application or application area.
Using this value, you can identify the area that is generating the message.
VIM060000-AGD-EN-3
175
MESSAGE
176
1.
2.
To open, the Details view for a log point, double-click its line.
VIM060000-AGD-EN-3
In case the log level is not maintained at Log Point level, you can maintain it at
Object and Sub-object level.
3.
4.
VIM060000-AGD-EN-3
Administration Guide
177
Select the Object Vendor Invoice Management and double-click Sub-objects in the
navigation panel.
178
VIM060000-AGD-EN-3
Important logs
VIM060000-AGD-EN-3
Administration Guide
179
2.
Object
Sub-object
3.
Time restriction Specify a date and time range to display the messages
generated in a particular period.
4.
Log class Specify the log class of the messages you want to display.
5.
Click
180
VALUE(OBJECT_ATTRIBUTE) DEFAULT 0
VALUE(SUBOBJECT_ATTRIBUTE) DEFAULT 0
VALUE(EXTERNAL_NUMBER_ATTRIBUTE) DEFAULT 0
VALUE(DATE_FROM) LIKE BALHDR-ALDATE DEFAULT SY-DATUM
VALUE(TIME_FROM) LIKE BALHDR-ALTIME DEFAULT '000000'
VALUE(DATE_TO) LIKE BALHDR-ALDATE DEFAULT SY-DATUM
VALUE(TIME_TO) LIKE BALHDR-ALTIME DEFAULT SY-UZEIT
VALUE(TITLE_SELECTION_SCREEN) DEFAULT SPACE
VALUE(TITLE_LIST_SCREEN) DEFAULT SPACE
VALUE(COLUMN_SELECTION) LIKE BALDISP STRUCTURE
'11112221122
'
VALUE(SUPPRESS_SELECTION_DIALOG) DEFAULT SPACE
BALDISP DEFAULT
SY-DBCNT
VIM060000-AGD-EN-3
NO_AUTHORITY
*"
*"-----------------------------------------------------------------------
2.
OBJECT
SUBOBJECT
EXTERNAL_NUMBER
DATE_FROM
SUPPRESS_SELECTION_DIALOG: enter X.
Select the Object /OPT/VIM and double-click Sub-objects in the navigation panel.
Note: In the CRM system, custom configuration for application logging is not
available as it is in the ERP system.
VIM060000-AGD-EN-3
Administration Guide
181
Execute the SM30 transaction and open the maintenance view for table
/OPT/IT_LOG_CFGV.
2.
3.
4.
5.
182
VIM060000-AGD-EN-3
6.
VIM060000-AGD-EN-3
Administration Guide
183
Chapter 23
If you are not using the Approval Portal component, you can skip this
chapter.
VIM060000-AGD-EN-3
185
186
VIM060000-AGD-EN-3
Delete Connection
Delete a SAP connection.
Refresh All Connections
Refresh the connections after you made changes. Without the refresh, the
Approval Portal will continue to use existing connections.
Up Arrow
Move the connection priority up.
Down Arrow
Move the connection priority down.
Note: The first connection in the list is used as the default connection. The default connection determines the Invoice Lists User Preference. See section 6.2
"Working with the Personalize Screen" in OpenText Vendor Invoice Management
- User Guide (VIM-UGD) for more details.
Connection
Details
VIM060000-AGD-EN-3
Administration Guide
187
R/3 name
The R/3 name of the SAP system that is connected to.
Logon Group
The logon group of the SAP system that is connected to.
System number
The system number of the SAP system that is connected to.
You can perform the following actions:
Save
Save the SAP connections. If the connection is invalid, you will not be able to
save.
Test
Test the SAP connections. If the connection fails, it will return a failure message
to you.
188
VIM060000-AGD-EN-3
VIM060000-AGD-EN-3
Administration Guide
189
23.1.3 Configuration
Click the Configuration tab.
190
VIM060000-AGD-EN-3
(NWP) server with an AppIntegrator iView linked to the Approval Portal J2EE
application.
If the NWP is not in this list and a user tries to access it, the user will get a
message: Login Error- Authentication Failed.
WhiteList Configuration
Select this check box to enable the white list feature.
Add
Enter the DNS or IP of the NWP to be in the white list and click Add.
Reinitialize the application to get the new value.
Remove
Select an entry in the Portal Host(s) List and click Remove to remove the
entry from the list. Reinitialize the application to get the new value.
Save
Click this button to save the configuration.
23.1.4 Administration
The Administration tab allows you to perform Administration tasks on the
application. It also tells you the Version and the Build Date of the application.
Click the Administration tab.
Reinitialize Application
Click this button to reinitialize the application. This is necessary after you
changed the configuration or if you change the language resource files. See
Changing Language Resources on page 193 for more details.
VIM060000-AGD-EN-3
Administration Guide
191
Product Code
IAP
Constant
EXIT_SEARCH_HELP_FLT
Constant Value
/ORS/SEARCH_HELP_FIELDS_PREFIL
The interface of the custom function must be the same as the interface of the baseline
function /ORS/SEARCH_HELP_FIELDS_PREFIL:
FUNCTION /ORS/SEARCH_HELP_FIELDS_PREFIL.
*"--------------------------------------------------------------------*"*"Local Interface:
*" IMPORTING
*"
VALUE(SHLPNAME) TYPE SHLPNAME
*"
VALUE(INVOICE_HEADER) TYPE /ORS/INVOICE_HDR OPTIONAL
*"
VALUE(CURRENT_APPROVER) TYPE /ORS/UMOID OPTIONAL
*" TABLES
*"
RETURN STRUCTURE BAPIRET2 OPTIONAL
*"
FIELDLIST STRUCTURE /ORS/SEARCHHELP_FIELD_LIST
*"
ACCT_DATA STRUCTURE /ORS/INVOICE_ACCT_DATA OPTIONAL
*" EXCEPTIONS
*"
NOT_FOUND
*"---------------------------------------------------------------------
ENDFUNCTION.
This field is used to set the default value for the search field.
Display only
This field is an indicator that the search field value cannot be changed by the
user in the Approval Portal.
The custom function should fill these fields with appropriate values according to
your requirements.
192
VIM060000-AGD-EN-3
Important
Any changes made by the logic in the custom function module to the fields
other than Value and Display only will result in unexpected results or
errors.
2.
3.
word Flligkeitsdatum.
Java compiler and other Java tools can only process files which contain Latin-1
and/or Unicode-encoded characters (\u<XXXX> notation).
Example command: Java native2ascii -encoding UTF-8 "ori_utf-8-
Lang_DE.properties" Lang_DE.properties
Tip: You can also use any editor that can save as Unicode Enabled, for
example
http://en.sourceforge.jp/projects/propedit/downloads/11441/Properties
Editor.jar/
4.
VIM060000-AGD-EN-3
Administration Guide
193
English (EN)
German (DE)
Spanish (ES)
French (FR)
Italian (IT)
Japanese (JA)
Dutch (NL)
Portuguese (PT)
Russian (RU)
Chinese (ZH)
Note: Japanese and Chinese are supported only in SAP ECC 6.0.
This section describes the configuration to add another language than the
predefined. Therefore, you have to perform the following actions:
2.
3.
194
VIM060000-AGD-EN-3
Note: This entry is a SAP language key pair. Check the SAP help for a list
of language key pairs.
4.
2.
3.
4.
Open the new Lang_<XX>.properties file and translate the English strings into
the other language.
Convert non-ASCII characters to Unicode representative format, see step 3 on
page 193 in Changing Language Resources on page 193.
5.
Navigate to the application deployment directory, for example \usr\sap\<instance name>\<JC>\j2ee\cluster\server0\apps\com.opentext.vim.portal\VimPortalWeb\servlet_jsp\vimportal\root\styles, where
<JC> is the system number.
2.
3.
4.
VIM060000-AGD-EN-3
Administration Guide
195
You must include calendar popup strings in the new language to the calendar-
2.
3.
Append calendar strings to the file and translate the text into the new language;
see Example 23-1 for details.
Example 23-1: Adapting the calendar-en.js file
For Swedish, translate the week day names, the month names and the strings
Toggle first day of week, Prev. year (hold for menu), and so on.
Mind the SV for Swedish in the Calendar._<xxx> strings.
Calendar._DN_SV = new Array
("Sunday",
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday",
"Saturday",
"Sunday");
Calendar._MN_SV = new Array
("January",
"February",
"March",
"April",
"May",
"June",
"July",
"August",
"September",
"October",
"November",
"December");
Calendar._TT_SV["TOGGLE"] = "Toggle first day of week";
Calendar._TT_SV["PREV_YEAR"] = "Prev. year (hold for menu)";
Calendar._TT_SV["PREV_MONTH"] = "Prev. month (hold for menu)";
Calendar._TT_SV["GO_TODAY"] = "Go Today";
Calendar._TT_SV["NEXT_MONTH"] = "Next month (hold for menu)";
196
VIM060000-AGD-EN-3
4.
In Visual Admin, navigate to Instance > Server > Services > Deploy.
2.
Expand servlet_jsp.
3.
4.
5.
When the application is stopped, select it again and click Start Application.
6.
Click OK to confirm.
VIM060000-AGD-EN-3
Administration Guide
197
Important
To make the language change effective, the end user must clear the
browser cache.
198
1.
2.
3.
4.
5.
6.
VIM060000-AGD-EN-3
7.
Click Update.
8.
9.
VIM060000-AGD-EN-3
Administration Guide
199
2.
3.
4.
5.
Select the Severity level you need, click Save and select one of the following
options, according to your needs:
For more details, also consult the SAP Web Application Server Administration
Guide.
Log level Info is used to log the initial Servlet loading information and when an
RFC is called.
Log level Error is used to log in the exception blocks.
Logs are created under \applications\com\opentext\vim\portal in the log
directory in the WAS, for example
E:\usr\sap\T38\JC01\j2ee\cluster\server0\log\applications\com\opentex
t\vim\portal.
200
VIM060000-AGD-EN-3
The name of the log will be VimlapLog<Logindex>.log. These logs will contain all
application's Info log level. Up to 10 files will be created and will be reused.
To change the size and number of log files:
1.
2.
3.
4.
5.
VIM060000-AGD-EN-3
Administration Guide
201
6.
E:\usr\sap\T38\JC01\j2ee\cluster\server0\log\applications\com\opentex
t\vim\portal. The name of the trace will be VimIapTrace<Logindex>.trc. Up to
These trace files include the import, export parameters of functions, and the RFC the
application is calling. These trace files are useful to troubleshoot any error when
connecting and retrieving data from SAP ERP. Make sure that you turn the level
back to Info or Error in the production environment.
To determine that WAS writes the trace files to the location specified above instead
of defaultTrace.trc, you must perform the following setting.
202
VIM060000-AGD-EN-3
2.
3.
4.
VIM060000-AGD-EN-3
Administration Guide
203
5.
6.
7.
204
Select the required severity level from the Severity drop-down list.
VIM060000-AGD-EN-3
9.
VIM060000-AGD-EN-3
Administration Guide
205
2.
206
VIM060000-AGD-EN-3
For example
http://OPWAST38.optura.local:50100/GRMGHeartBeat/EntryPoint
3.
Configure HTTP:
Property name
url
Property value
http://<WAS>:<WASHOST>/vimportal/GRMGServlet
For example: http://opwast38:50100/vimportal/GRMGServlet
4.
Configure the Java Connector (JCo). You also must monitor the JCo connection
from Approval Portal to SAP.
VIM060000-AGD-EN-3
Administration Guide
207
While configuring a single JCo component, give the name as JCo1. If you need
to configure multiple SAP backend systems, increment the index suffix to JCo,
like JCo2, JCo3.
In the application, the list of components is read with the component name from
scenario. As the JCo component can be repeated multiple times, add an index
number to identify the specific component.
208
VIM060000-AGD-EN-3
5.
6.
VIM060000-AGD-EN-3
Administration Guide
209
7.
210
VIM060000-AGD-EN-3
propname: password
propvalue: the CPIC user password
propname: language
propvalue: the language
propname: apphost
propvalue: the application host
propname: sysnumber
propvalue: the system number
VIM060000-AGD-EN-3
Administration Guide
211
propname: group
propvalue: the group
http://help.sap.com/saphelp_nw70/helpdata/EN/cf/504a550ae6274495e2ce3
0d176f33b/content.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/34/60cdd0d3fdeb4cb8cbc4
eac681f961/content.htm
212
VIM060000-AGD-EN-3
Also backup a copy of the .sca or .sda file. If restoring is needed, do the following:
To perform a restore:
1.
2.
Redeploy the backup or the original delivery of the .sca or the .sda file. See
OpenText Vendor Invoice Management - Installation Guide (VIM-IGD).
Check in the Visual Admin if the application has been restarted and is running.
Login to the Administration page of the Approval Portal to see if all the
configurations are still correct.
Ask the end user to try to access the application to see if everything is working.
If a restore is needed, see Managing Backup and Restore on page 212 for
information how to restore.
VIM060000-AGD-EN-3
Administration Guide
213
23.14 Troubleshooting
The following issues can occur on the Approval Portal. See symptoms and solutions.
Issue #1: The user received an exception message
Symptom
The end user receives a message: Exception: Please consult with your
administrator
Solution
Review the logs and check for relevant information. Send the SAP WAS server
trace and the VIM trace to OpenText.
Issue #2: Not able to update the configuration
Symptom
You are not able to save the Configuration information to the
configuration.xml file
Solution
Make sure the <installDir>/invoiceCfg folder has write permission.
Issue #3: The invoice image is not working
Symptom
The user is not able to view the image and the SAP side is configured correctly.
Solution
Make sure the Image Display Type in the Configuration section of the
Administration page is configured correctly.
Issue #4: Some of the texts in other languages display in English only
Symptom
Some of the texts in other languages display in English only when user selects
other languages.
Solution
The language properties file for that language might not have the translation;
this might be due to the release date of the build. Change accordingly or contact
OpenText Customer Support to obtain the latest language properties files.
214
VIM060000-AGD-EN-3
23.15 Branding
23.15 Branding
You might need to change the logo of the Approval Portal. This section describes
how to do this.
Notes:
You must perform the same action when you are applying a new patch.
E:\usr\sap\T39\JC00\j2ee\cluster\server0\apps\com.opentext.vim.po
rtal\VimPortalWeb\servlet_jsp\vimportal\root\jsp\invoice
2.
3.
4.
src="<%=baseURLPathToImages%>banner_large_sap_vim_b24.png"
border="0"> with
background="<%=baseURLPathToImages%>banner_background.png".
E:\usr\sap\T39\JC00\j2ee\cluster\server0\apps\com.opentext.vim.po
rtal\VimPortalWeb\servlet_jsp\vimportal\root\images
2.
3.
4.
background="<%=baseURLPathToImages%>banner_background.png".
VIM060000-AGD-EN-3
Administration Guide
215
Chapter 24
For Non PO invoices parked using F-63, F-43, FB60, FV60, MR01, or MRHR,
transaction FBV4 must be used to change the posting manually.
For PO invoices created using MIRO or MIR7, transaction MIR4 must be used in a
change mode to change the posting manually.
This chapter provides two sections that explain the processing steps you must
perform for each of the above two types of documents.
Notes:
VIM060000-AGD-EN-3
217
next year. If the posting date has to be changed, use the FBV4 transaction to post it in
the new posting period.
At this stage, the runtime workflow instances based on this parked document will
be rendered unusable as the object key of the parked document is changed now. All
the OpenText application tables will be out of sync, as well.
218
VIM060000-AGD-EN-3
If custom extensions were implemented that store the SAP parked document
number, you have to make appropriate code corrections to avoid inconsistencies.
2.
You can run the report either in an online mode or scheduled as a batch job.
In the batch mode, all the parked documents that match the selection criteria
will be processed automatically without user intervention.
You must specify the new posting date so that all the documents will have
the posting dates modified to the new date. Make sure the posting period for
the new posting date is open.
VIM060000-AGD-EN-3
Administration Guide
219
If changing the posting date leads to no fiscal year change, use the month
end report.
The selection options Company Code and Fiscal Year are mandatory.
2.
220
You can run the report either in an online mode or scheduled as a batch job.
In the batch mode, all the parked documents that match the selection criteria
will be processed automatically without user intervention.
If changing the posting date leads to no fiscal year change, use the month
end report.
VIM060000-AGD-EN-3
VIM060000-AGD-EN-3
Administration Guide
221
At this stage, the workflows that are referencing to the original parked document
will have runtime errors because the original object is deleted by SAP.
222
VIM060000-AGD-EN-3
2.
You can run the report either in an online mode or scheduled as a batch job.
In the batch mode, all the parked documents that match the selection criteria
will be processed automatically without user intervention.
The selection options Company Code and Fiscal Year are mandatory.
You must specify the new posting date so that all the documents will have
the posting dates modified to the new date. Make sure the posting period for
the new posting date is open.
If changing the posting date leads to no fiscal year change, use the month
end report.
VIM060000-AGD-EN-3
Administration Guide
223
2.
You can run the report either in an online mode or scheduled as a batch job.
In the batch mode, all the parked documents that match the selection criteria
will be processed automatically without user intervention.
If changing the posting date leads to no fiscal year change, use the month
end report.
You can run the /OPT/VIM_MEND_PO transaction with certain filter if needed.
In dialog mode, you can restrict the output set by using the various selection
criteria available.
224
Make sure the logs and reports show the correct information.
The programs can be run in dialog mode to investigate any errors that might be
encountered.
VIM060000-AGD-EN-3
Keep the log for the program executions so that you will have a record of what
invoices were changed in case something goes wrong.
Depending on what is implemented at your site, you need to come up with a set of
scenarios to be tested.
The following is an example scenario you can be use for testing:
To test the year end procedure:
1.
2.
3.
4.
5.
Check to see if the approver gets a workitem to approve in the web portal or in
the SAPGUI, depending on how it is configured.
6.
7.
Access the approver's inbox and execute the workitem. You should notice that
the new fiscal year and possibly new document number is there in the details.
Make sure the comments are showing up properly.
8.
Run VIM Analytics and give the new document key. See if the result shows the
old document number in the details.
9.
Make sure the image can be displayed properly from FBV3 or any invoice
display transaction.
10. Check if the OpenText Dashboard (accessable from the Object Services menu
from invoice display transaction) shows the correct information for the new
invoice key.
VIM060000-AGD-EN-3
Administration Guide
225
You can use the log to check for a list of all documents that were processed
through year end processing.
226
VIM060000-AGD-EN-3
Chapter 25
This function module stores the ICC configuration data into SAP. Application
name is the key for configuration data; there will be different versions for the
application. One version of the application will be active at a time.
Every time ICC comes with new configuration data for any application, it stores
with new version number; the latest version will be set as the active version.
Each application will have more than one line of data.
T_DESCRIPTION
This function module returns the all active applications information. This gets
the application name, version and description from table /OPT/VIM_CFG_VER.
Output parameters:
T_CONFIG_LIST
VIM060000-AGD-EN-3
227
Output parameters:
T_CONFIG_DATA
T_DESCRIPTION
228
VIM060000-AGD-EN-3
2.
3.
VIM060000-AGD-EN-3
Administration Guide
229
4.
5.
In the Field Selection dialog box, select Application Name and Application
Version.
Click
230
VIM060000-AGD-EN-3
6.
Enter Application Name and Application Version you want to maintain, see
step 2 on page 229.
Click
All configuration line entries for the selected application and version are
displayed.
7.
Scroll downwards to make sure you have only lines for the correct Application
Name and Application Version.
8.
9.
10. For the final action, deleting the entry for the application version, execute the
SM30 transaction.
VIM060000-AGD-EN-3
Administration Guide
231
232
VIM060000-AGD-EN-3
VIM060000-AGD-EN-3
Administration Guide
233
Chapter 26
2.
Use the archiving object /OPT/DOC that is provided with VIM 5.2 SP1 to archive
the DP invoices.
3.
Follow the SAP standard archiving processes for the archive object /OPT/DOC.
The data from the following tables is archived:
/OPT/VIM_1HEAD
/OPT/VIM_1ITEM
/OPT/VIM_HD_DP
/OPT/VIM_HD_PO
/OPT/VIM_PO_WIH
/OPT/VIM_PO_WID
/OPT/VIM_HD_NPO
/OPT/VIM_NPO_WIH
VIM060000-AGD-EN-3
235
/OPT/VIM_NPO_WID
/OPT/VIM_1BDCLOG
/OPT/VIM_1LOG
/OPT/VIM_1OCRLOG
/OPT/VIM_8LOG
/ORS/STACK_HDR
/ORS/STACK_BODY
/ORS/INV_ADD
/ORS/INV_DATA
/ORS/APPR_LOG
/PTGWFI/M_PRKMTR
/PTGWFI/F_PIRMTR
/PTGWFI/F_BIRMTR
/PTGWFI/F_BIRMWI
/PTGWFI/F_DELINV
/PTGWFI/F_LIXMWI
/PTGWFI/F_LIXMTR
236
1.
2.
Use the archiving object /OPT/REP that is provided with VIM 5.2 SP1 to archive
the VIM Central Reporting information.
VIM060000-AGD-EN-3
3.
Follow the SAP standard archiving processes for the archive object /OPT/REP.
The data from the following tables is archived:
/OPT/VT_DOC_HEAD
/OPT/VT_WORKITEM
/OPT/VT_WI_ACTN
/OPT/VT_WI_STEPS
/OPT/VT_DOC_H
/OPT/VT_WI
/OPT/VT_WI_ACTV
VIM060000-AGD-EN-3
Administration Guide
237
Glossary
AAK
See: SAP Add-On Assembly Kit (AAK)
AP processor
Accounts Payable personnel
Approval chart of authority (COA)
The Approval chart of authority (COA) determines first approver and next
approver for an invoice by combinations of Company Code (specific or range),
Expense Type (marketing expense, utility), Cost Objects (G/L account, Cost
Center), and HR objects (Position, Job code).
Archive system
Computer system that enables storage, management and retrieval of archived
data and documents
ArchiveLink
Service integrated in the SAP Web Application Server for linking archived
documents and the application documents entered in the SAP system
ArchiveLink document types
Document types that need to be customized for ArchiveLink
Authorization profiles
The SAP administrator assigns authorizations to the users that determine which
actions a user can execute in the SAP system. These authorizations are stored in
Authorization profiles.
BAdI
See: Business Add-Ins (BAdI)
Baseline
Set of functionality with pre-defined configuration and the starting point to
implement VIM
VIM060000-AGD-EN-3
239
Glossary
BDC ID
Business Data Communication ID. The BDC ID is used by the system to process
an SAP transaction to create an SAP Document in user context.
Block
Situation where an invoice has a price or quantity variance that prevents invoice
from posting
BTE
See: Business Transaction Event (BTE)
Business Add-Ins (BAdI)
Business Add-Ins (BAdI) is a new SAP enhancement technique based on ABAP
objects. BAdI can be inserted into the SAP System to accommodate user
requirements too specific to be included in the standard delivery.
Business rules
Rules that describe the operations, definitions and constraints that apply to an
organization
Business Transaction Event (BTE)
Event used for extending a Non PO invoice functionality to call a custom program
Buyer
Person who is in charge of the PO. This role should have authorization to create
and change the purchase order. This role is also responsible for negotiating and
communicating with vendors.
COA
See: 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 to
read. Users can also perform actions from the dashboard.
DocuLink
OpenText DocuLink enables the archiving, management and retrieval of CRM or
ERP documents from within the SAP infrastructure.
240
VIM060000-AGD-EN-3
Glossary
VIM060000-AGD-EN-3
Administration Guide
241
Glossary
242
VIM060000-AGD-EN-3
Glossary
VIM060000-AGD-EN-3
Administration Guide
243
Glossary
244
VIM060000-AGD-EN-3
Glossary
VIM060000-AGD-EN-3
Administration Guide
245
Index
A
Activate role and exception mapping
Central Reporting 132
Activity monitoring 78
Adaptive computing 81
Additional languages
Approval Portal 194
Administration
activity monitoring 78
adaptive computing 81
alert monitoring 73
backup 80
CCMS templates 74
data archiving 80
DP invoices 89
DP processing 89
logs 79
registering CCMS agent 74
restart mechanism 81
SAP workflow administration transactions
84
SAP workflow tables 87
setting up central alert monitoring 74
Solution Manager Diagnostics 80
SWE2 transaction 84
SWEL transaction 84
SWI1 transaction 84
SWIA transaction 84
system availability 80
system performance analysis 79
traces 79
VIM configuration 80
work item analysis 86
workflows 73
Administration tools 21
VIM Customizing IMG 21
Aggregation Report
Central Reporting 135
creating variants 128
VIM060000-AGD-EN-3
247
Index
D
Data archiving 80
Delivery model 15
Document Processing
bulk change of posting date 89
Download programs
downloading in background 158
downloading PO data 154
downloading vendor database 151
function modules and RFCs 158
ICC integration 151
DP invoices
administration 89
DP processing
administration 89
Asynchronous interfaces
Approval Portal 213
Attachment support
Approval Portal 198
B
Backup 80
Approval Portal 212
Batch job
Central Reporting 135
Batch programs
ICC Dispatcher 163
Branding
Approval Portal 215
Bulk change of posting date
Document Processing 89
C
CCMS agent
registering 74
CCMS templates
monitoring 74
CD-ROM
Product ISO image 11
Central alert monitoring
setting up 74
Central Reporting 121
activate role and exception mapping 132
Aggregation Report 135
cleaning up tables 138
Collection Report 132
maintaining reporting tables 128
scheduling batch job 135
Text Master Report 134
User Master Report 134
Chart of Authority 31
Cleaning up tables
Central Reporting 138
Collection Report
Central Reporting 132
Configuring VIM Notifications 109
conventions 12
Creating variants
Aggregation Report 128
CRM system
application log 181
CUST_PREFL group
Aggregation Report 126
Customer Support 13
248
E
EDI support 169
IDoc process administration 169
Email formatting function module
VIM Notifications 118
Email options
VIM Notifications 109
Event linkage for VIM workflows 81
Excluding users
VIM Notifications 114
Extensions to VIM 18
F
FAIL_SAFE user key 29
H
High availability 14
Approval Portal 213
I
ICC Admin Tool
ICC Dispatcher 165
ICC application
deleting from SAP tables 228
ICC configuration data 227
RFCs 227
ICC Dispatcher 163
batch programs 163
ICC Admin Tool 165
IDoc process administration
EDI support 169
VIM060000-AGD-EN-3
Index
Invoice
workflow status 43
Invoice Approval
releasing invoice lock 71
Invoice lock
releasing 71
ISO image
Product ISO image 11
K
Key Process Analytics Report
thresholds maintenance 139
L
Language resources
Approval Portal 193
Load balancing
Approval Portal 213
Log
year end procedure 225
Log classification
application log 179
Log configuration for
vimIapTraceLogindex.trc
Approval Portal 203
Log files
Approval Portal 199
Log point
application log 176
Logs 79
M
Maintaining logical systems
Aggregation Report 124
Maintaining reporting tables
Central Reporting 128
Measuring performance
Approval Portal 205
Monitoring
Approval Portal 205
workflows 49
Month end procedure
Non PO based FI documents 217
parked documents 217
PO based documents 221
Multilingual support
Approval Portal 193
Multiple backend system 119
VIM060000-AGD-EN-3
N
Non PO based FI documents
month end procedure 217
year end procedure 217
Notification email body
VIM Notifications 112
Notification email title
VIM Notifications 113
Notification options
VIM Notifications 109
O
Object and Sub-object
application log 177
OpenText Online 13
P
Parked documents
month end procedure 217
year end procedure 217
Periodic tasks
Approval Portal 213
PO based documents
month end procedure 221
year end procedure 221
Process swimlanes 17
R
Reassigning Invoice Approval items
to a different user 67
Reassigning work items 61
retrieving work items of a specific user 61
to a different user 64
Releasing invoice lock
for Invoice Approval 71
Restart mechanism 81
Restore
Approval Portal 212
RFCs for the ICC configuration 227
Role error in a workflow 55
determining 55
restarting after fixing 58
Role for VIM configuration display 93
Roles 29
FAIL_SAFE user key 29
S
SAP early watch service 93
Administration Guide
249
Index
250
VIM060000-AGD-EN-3
Index
VIM060000-AGD-EN-3
Administration Guide
251