SAPIM516 Administration Guide
SAPIM516 Administration Guide
5.1.6
Administration Guide
Table of Contents
1 Overview .........................................................................................................................................5
1.1 VIM Delivery Model................................................................................................................................... 6
1.2 VIM Components ...................................................................................................................................... 7
1.3 Software Change Management ................................................................................................................ 9
2 VIM Customizing IMG Dashboard...............................................................................................10
3 VIM Installation Check program .................................................................................................11
4 List of Open Text VIM Workflow Batch Jobs.............................................................................13
5 How to Maintain VIM Roles? .......................................................................................................14
5.1 Roles Overview....................................................................................................................................... 14
5.2 Template Maintenance ........................................................................................................................... 15
5.3 Role Maintenance ................................................................................................................................... 18
5.4 Simple Maintenance ............................................................................................................................... 20
5.5 Expert Mode for Org Maintenance.......................................................................................................... 21
5.6 Fail_Safe Maintenance ........................................................................................................................... 23
6 Chart of Authority Maintenance User Guide .............................................................................26
6.1 Purpose................................................................................................................................................... 26
6.2 Audience ................................................................................................................................................. 26
6.3 Prerequisites ........................................................................................................................................... 26
6.4 How to get there?.................................................................................................................................... 26
6.4.1 Approver Details tab ........................................................................................................................ 27
6.4.2 COA Details tab ............................................................................................................................... 28
6.4.3 Coder Details tab ............................................................................................................................. 30
7 How to Set up Substitute (back-up) for Workflow Process? ...................................................31
7.1 How to Set Up Substitution for SAP Inbox? ........................................................................................... 31
7.1.1 Set Up a Substitute.......................................................................................................................... 31
7.1.2 Adopt Substitution............................................................................................................................ 33
7.2 Workflow Administrator: How to Set Up Substitute for Other Users to Approve Invoice?...................... 36
8 How to Determine the Workflow Status of an Invoice? ............................................................40
8.1 PO Invoice: Display VIM WF status via MIR4 Transaction..................................................................... 40
8.2 Non-PO Parked Invoice: Display VIM Workflow Status through FB03................................................... 42
8.3 Logistic Invoice Exceptions: Displaying VIM Workflow Status through VIM Analytics ........................... 44
9 How to Monitor VIM Workflow? ..................................................................................................47
10 How to Solve Error Workflow with “Role” error? .....................................................................50
10.1 How to determine if a Workflow has “Role” Error? ................................................................................. 50
10.2 How to Restart Workflow in “Error” Status?............................................................................................ 52
11 How to Reassign Work Item Belong to Other User? ................................................................54
11.1 How to Retrieve Open SAP Work Items Belong to a Specific User? ..................................................... 54
11.2 How to Reassign Open SAP Work Items to a Different User in SAP?................................................... 57
11.3 How to Reassign Approval Invoice Items? ............................................................................................. 60
12 How to Release Invoice Lock for Invoice Approval?................................................................63
13 Workflow Administration.............................................................................................................65
3 Administration Guide
Open Text Vendor Invoice Management 5.1.6
4 Administration Guide
Open Text Vendor Invoice Management 5.1.6
1 Overview
The purpose of this document is to provide help for workflow administrator for maintaining Vendor
Invoice Management (VIM). Topic includes:
1. List of Open Text VIM Workflow Batch Jobs
2. VIM Role Maintenance – set up user id’s per roles
3. Set up approvers for non-PO invoice approval
4. Set up Substitution
5. VIM Workflow monitoring
6. Restarting VIM Workflow with error
7. Reassign VIM work items belong to other users
8. Release non-PO invoice locks
9. Some SAP Workflow highlights
5 Administration Guide
Open Text Vendor Invoice Management 5.1.6
6 Administration Guide
Open Text Vendor Invoice Management 5.1.6
7 Administration Guide
Open Text Vendor Invoice Management 5.1.6
z Document Processing
Capture invoice metadata including line items for PO
Handle suspected duplicated invoices
Collaborate with others
z Invoice Approval
List invoices to be approved
Approve and code the invoice
z VIM Analytics:
Overview of the invoices in progress
Unified dashboard
z Exception Handling (Invoice Exception)
Handle the exceptions that arise after a SAP invoice is created
z Vendor Self Service
This is an optional .NET component
Allows vendors to check the status of their purchase orders, invoices, good receipts and payments
The actual scenarios implemented at a particular site might be different based on the customer needs. The
following graphic shows the product as can be installed on a system landscape.
8 Administration Guide
Open Text Vendor Invoice Management 5.1.6
9 Administration Guide
Open Text Vendor Invoice Management 5.1.6
10 Administration Guide
Open Text Vendor Invoice Management 5.1.6
11 Administration Guide
Open Text Vendor Invoice Management 5.1.6
The icon indicates successful installation; the icon indicates that further activity is required.
If required, click on the icon to complete the respective activity with an SAP transaction.
Tip: With a standard installation, every item should be marked with an icon.
12 Administration Guide
4 List of Open Text VIM Workflow Batch Jobs
The following jobs should be scheduled accordingly.
Role Definition:
Roles are defined by product codes
- There are 3 main product codes
005 – DP based roles
LIX – LIV based product codes
‧ (both for PO parking and PO blocking workflows)
PIR – Non-PO parking workflows
VSS – VSS based roles (VSS is an optional component)
Every assignment is based on the product code/role combination
Role Resolution:
Role Resolution determines which workitem is sent to whom
Role Resolution is defined via Template:
- Template contains the options that control how role is resolved
- Template is considered configuration
- Use /OPT/CP_9CX2 to create or modify
- Three types are
Key determination
Functional module
HR structure
Types of Template:
Key determination (Static)
- Combination of columns
- Depends on the business object attributes
- Example: company code, scan location and plant define AP Processor role
Function Module (Dynamic)
- Set of custom functions that extend baseline functions
- Example: Buyer is PO creator FM extracts from PO
SAP HR org structure
- Always send to the structure such as a position or work center
- Example: Tax Experts are users attached to a single work center
Template Id: Template Name without any spaces and special characters.
Description: template description.
Agent Id: the agent ID and this is only when Org Unit is selected for Type.
Function Module: the function module when Function Module is selected for Type.
Type: Template can be of 3 types.
1) Function Module Based: The role is resolved based on the function module. The example interface is
shown below. ACTOR_TAB will return the selected actors
2) Org Unit: If you want to maintain role based on org unit this option can be used.
3) Key Determination Based: If you choose Key Determination Based, you need to select Template Fields.
Based on these fields the role will be resolved. Allow ranges will be used to maintain range values.
The following is for Template Fields.
Template fields – Ref Table and field will give field label and technical properties
Field ID: the field ID
Search Help Name: Maintain search help for field
Allow Ranges: Allows ranges
Allow Wildcard: Allows wild character * for every thing.
Template Field Maintenance:
You will also need to maintain template field for each field. Select Template ID and double click on Template Field
in the left panel.
Product Code: maintain relevant Open Text product code.
Object Type: maintain work item business object Type.
Attribute: technical attribute of business object attribute.
To maintain for product relevant templates, you can activate and deactivate. At any given point of time you can have
only one active template for product role. If you deactivate it, it is going to delete all the existing entries for the role /
org configuration in table /ptgwfi/w_org.
Product Code: the product code such as DP, LIX, PIR
Responsible Party: the person who is responsible
Role Function Module: the function module for the role
Key Determination flag: use this if you are maintain key determination
Object Type: this is based on the workflow
The following is a screen that has Template Type of Key Determination.
The following is a screen that has Template Type of Org Unit.
The following is a screen that has Template Type of Function Module.
Expert mode allows you to maintain multiple entries in fast way and also allows you to maintain complex range of
conditions.
6.1 Purpose
Chart of Authority is required in Open Text Invoice Approvals process to allow users to approve Non PO / PO
Invoices. The Users (Approvers) could be different with different limits of approvals for different combinations or
different Org Data. This could sometimes be very complex. This tool provides one stop interface for maintaining
all the combinations of Approvers, Approval Limits and Coders for the Invoice Approval Process.
6.2 Audience
Functional users responsible for maintaining Chart of Authority for Invoice Approvals who are aware of
organizational objects involved in Invoice Approval process.
6.3 Prerequisites
Org Units allowed in Approval process are maintained. This can be maintained in transaction code SM30 for
Table/View /OPT/BL_T401V.
Fields Required for Approval User Data are maintained. This can be maintained in transaction SM30 for Table/View
/OPT/BL_T402V.
o Click on button to create new Approver
o Maintain required entries
o Save
• To copy existing user
o Select an existing user
o Click on button to copy existing user
o Make changes to data
o Save
• To delete existing user
o Select an existing user
o Click on to mark user for deletion
o If user already exists in the system, the user will only be marked for deletion as there could be some
approval data for the user
o If the user is just created, the user will be deleted permanently
• To create multiple users
o Click on to insert 5 users
o Maintain required entries for each user
o Save
6.4.2 COA Details tab
• This tab lists the allowed approval limits for user per org data combination.
o UserObjID Id: the Open Text User Id.
o Amount: the approving amount that user is allowed to approve.
o Currency: the currency.
o Company Code: the Company Code.
o Cost Center: the Cost Center.
o WBS Element: the WBS Element.
NOTE: Same user cannot have different approval limits for the same combination of org units in the
same currency. However the user can have different approval limits in different currencies for the same
combination of org units.
Example:
If User1 is authorized for approving invoices up to $1000 for any Company Code/Cost
Center/WBS Element combination, entries are:
• User Id
• Amount 1000
• Currency USD
• Company Code *
• Cost Center *
• WBS Element *
• To create new entries
o Click on to create new approval limits for users
o Maintain required entries
o Save
6.4.3 Coder Details tab
• This tab lists the coders determined by the system for a combination of org data.
o Coder: the name of the coder for this combination
o Counter: not modifiable
o Default: if this is person is always a coder
o Requestor: the person who the invoice belongs to
o Company Code: the company code
Example:
o For Company Code 1000 if the system needs to determine User1 always as a coder, mark that entry as
default
• Create New Entries
o Click on button to create new entries
o Maintain User data
o Save
7.1.1 Set Up a Substitute
Each person can designate more than one user as substitute.
7.1.2 Adopt Substitution
When the substitute is ready to work on the work item belong to the substituted person, he can “adopt substitution”
and will then be able to view/execute those work items.
to confirm.
Example: Yvonne is a substitute for Wayne to approve invoice when Wayne goes on vacation. However, Wayne has
not designated Yvonne as his substitute in the system. Wayne is on vacation and there are invoices waiting for
approval.
The VIM workflow administrator can execute the following steps to set Yvonne up as Wayne’s substitute so that
Yvonne can approve the invoices.
Note: When a substitute approves an invoice, the audit trail will show that “XXXX approves on behalf of YYYY”.
For non-PO parked invoices, use one of the following means to display invoice status:
1) Transaction FB03 Æ Service for ObjectÆ Workflow Æ Open Text Dashboard
2) Transaction /OPT/VIM_ANALYTICS Æ VIM Analytics
1. Transaction: MIR4
Enter invoice number and click
“Display doc”.
8.2 Non-PO Parked Invoice: Display VIM Workflow Status through FB03
Steps Screen Print
2. WS00275260 – parked PO invoice workflow (from the time a PO invoice is parked until the invoice is
posted or deleted).
3. WS00275254 – non-PO parked invoice workflow (from the time a non-PO invoice is parked until the
invoice is posted or deleted).
4. WS00275252 – web approval of parked invoice (from the time an invoice is sent for web approval action
until approval is completed or invoice is fully rejected).
5. WS00275264 – Blocked PO invoice workflow (from the time a PO invoice is blocked for payment until it
is released or cancelled)
6. WS00275266 – Blocked PO invoice header level action workflow (from the time that a blocked invoice is
authorized for header level action until the action is completed or when AP sends back).
Type: F
Task: WS00275255
WS00275260
WS00275254
WS00275252
WS00275264
WS00275266
Acceptable Statuses:
1) STARTED Æ In progress
2) COMPLETED or
CANCELLED Æ
completed workflow
Æ Completed
Type: F
Status: Error
Task: WS00275255
WS00275260
WS00275254
WS00275252
WS00275264
WS00275266
Task: WS00275255
WS00275260
WS00275254
WS00275252
WS00275264
WS00275266
11.1 How to Retrieve Open SAP Work Items Belong to a Specific User?
Open work items belong to a specific user can be found through SAP standard Workload Analysis report. Each work
item will have a “Work Item ID” which is a unique number identifier for a work item.
2. Enter:
Type Æ “US”
11.2 How to Reassign Open SAP Work Items to a Different User in SAP?
Once work item id’s are identified, they can be reassigned through SAP standard transaction SWIA titled Execute
Work Item Without Agent Check.
Notes: If the reassignment is permanent due to an organizational change, please ensure Org Maintenance set ups are
completed prior to reassigning the work item in the following steps.
clicking on .
to confirm.
1. Transaction code:
/ORS/UMREASSIGNED
to complete the
reassignment action.
1. Transaction code:
/ORS/RELEASE_LOCK
13 Workflow Administration
This section describes some of the general activities that are useful for an administrator in checking the systems status
of the product.
13.1.1 Central Monitoring setup
The product is completely embedded inside SAP ERP system and hence the entire general alert monitoring
infrastructure can be used for check for health of the system and application.
VIM does not need a separate CEN system to monitor. You should use the existing CEN system that is connected to
the SAP ERP system on which VIM is installed to monitor VIM. For configuring CEN please refer the SAP online
help as referred below.
http://help.sap.com/saphelp_nw70/helpdata/EN/9d/df1241c738f423e10000000a155106/frameset.htm
13.1.2 Registering CCMS Agent
This product is an ABAP Add-On and all the functionality is embedded into the SAP ERP ABAP system. The Standard CCMS
Agent SAPCCM4X can be used. If the underlying SAP ERP system is already registered into CEN then nothing new needs to be
registered. Please refer to the following SAP online help link for registering CCMS Agent.
http://help.sap.com/saphelp_nw70/helpdata/EN/ca/118110ff542640b7c86b570cc61ae3/frameset.htm
13.1.3 Configure CCMS Templates
• Configure SAP CCMS monitor using transaction RZ20
Procedure:
Go to transaction RZ20 and Activate Maintenance function from Extras Menu
Expand SAP CCMS Monitor Templates menu.
Double click and activate MTE by selecting check box
Double click on the line item to see details
Select the line and choose properties to get other settings like methods used and threshold values set etc.
You can use the following SAP CCMS Monitor Templates monitor sets
Monitor Usage
Availability and Performance Availability monitoring of selected systems and
Overview Monitor their application servers
Background Processing Background processing of the SAP systems and
their application servers
Buffers The various SAP buffers, their hit rates, and swap
rates
Change & Transport System Transports for a system
Communications Data transfers (SAPconnect, SAP Gateway,
Application Link Enabling, LDAP, RFC)
Data Archiving Monitored data archiving sessions
Database Database (such as table status, performance,
backups, data consistency)
1. Start the Alert Monitor using transaction RZ20 or choose CCMS → Control/Monitoring → Alert Monitor.
2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.
3. Start the desired monitor from the list by double-clicking it.
You can copy these monitors and make desired change. Please refer to SAP online help for more details. URL for the
Alert monitor online help has been provided below:
http://help.sap.com/saphelp_nw70/helpdata/en/28/83493b6b82e908e10000000a11402f/content.htm
VIM product does not require any specific values for the property thresholds for various monitoring templates. The
threshold values need to be arrived at by taking all the system landscape and functional considerations.
Setting threshold values for the nodes can be done as follows:
1. Go to transaction code RZ20 and expand the menu and double click on desired monitor set.
2. You can setup threshold values for the nodes by double clicking the node and click on display change button
3. Enter the desired values and save.
13.2 Activity Monitoring
The product used SAP Workflow engine to realize the process orchestration of the business processes. The Workflow
run time and administration tools can be effectively used to monitor the activity and resources as the business
processes are proceeding. Please refer to section 13.13 for using workflow administrator transaction for activity
monitor.
The performance analysis of the customer system can be done using standard ABAP tool set as the ABAP based
components of VIM reside inside SAP ERP system.
Procedure:
Go to transaction ST05.
choose Trace options and trace function for Performance analysis.
ABAP components of VIM use SAP workflow engine for realizing business process orchestration. Hence, traces can
be activated and used to checking specific sets of activities as part of problem analysis. SAP workflow logs are written
for every activity of process and hence are available all along. In addition to this standard system logs through SM21
can be used to check system activities. Please refer to section 13.13 for using workflow administrator transaction for
activity logging and traces.
Once this add‐on is installed on a customer system all the information should be accessible through Solution Manager
Tools for an administrator to perform root‐cause analysis. No separate external logs are generated during the product
use.
Configuration of the product is done through product specific IMG provided and documented in Configuration
guide.
13.7 Backup
Since the product configuration is store inside SAP ERP in Open Text product tables, the backup of the underlying
SAP ERP system would ensure the backup of the appropriate configuration, runtime and persistent data. In addition,
system transports would store any configuration changes that are made.
Archiving of old data can be done using SAP archiving objects WORKITEM, BKPF and others. Removal of any such
data should be done after careful consideration of the business requirements about data availability. Specially, since
the business objects in scope of these processes are financial in nature, local regulations needs to be adhered to in
making such decisions. It is generally recommended that any such initiatives are conducted in as a part of an overall
data archiving initiative.
In general any workflows that go into error status can be restarted after making appropriate configuration or
run‐time data changes. There are no other asynchronous interfaces for the product.
Note: /OPT/VPR is for VSS which is an optional component. Please set up this only if VSS is implemented.
13.12.1 How to Enable/Disable VIM Workflow?
1) Transaction Code: SWE2
Find one of the above event linkage entries and double-click on the entry.
2) Change the “Linkage activated” box to enable (box is checked) or disable (box is unchecked) the
workflow.
Note: For parked invoice solution, you might also want to activate/deactivate BADI and BTE.
Note: Depending on the SAP version, the following screens might look different on your system.
Use the selection screen to restrict the data to given date range and specific tasks described in
Section 13.14 and choose execute.
Select the desired work item and choose execute.
2. Work item log (SWI1): display all work items (workflow template, dialog task, wait step, background
task) based on selection
Procedure:
Go to transaction SWI1.
Use the selection screen to restrict the values and click on execute.
3. Event log (SWEL): display lists of event published during a specific duration
Procedure:
Go to transaction SWEL
You can notice what is receiver Function module and status of the action.
4. Event linkage (SWE2): display/change events linkage for workflow
Go to transaction SWE2
Check for type linkage active for OpenText Object Types mentioned in section 13.12
13.14 Work item Analysis (Report)
You can access the following transactions by going to:
Tools Æ Business Workflow Æ Development Æ Reporting Æ Work Item Analysis
Here is a list of all dialog standard tasks that can be used for SAP standard reports:
Workflow Description
WS00275255 Document Process Workflow (from receiving the scanned
invoice info until the invoice is parked/posted or the
document is marked as obsolete or duplicates)
WS00275260 parked PO invoice workflow (from the time a PO invoice is
parked until the invoice is posted or deleted)
WS00275254 non-PO parked invoice workflow (from the time a non-PO
invoice is parked until the invoice is posted or deleted)
WS00275252 web approval of parked invoice (from the time an invoice
is sent for web approval action until approval is completed
or invoice is fully rejected)
WS00275264 Blocked PO invoice workflow (from the time a PO invoice
is blocked for payment until it is released or cancelled)
WS00275266 Blocked PO invoice header level action workflow (from the
time that a blocked invoice is authorized for header level
action until the action is completed or when AP sends
back)
WS00275251 Vendor Self Service: an optional component
SAP ERP system, this solution follows standard early watch practices. Client dependent configuration data of
VIM is not visible in early watch client and also normally early watch client is locked against any configuration
changes. It is also possible for the administrator to create role to view configuration with display only
authorization as described below:
Note: Depending on the SAP version, the following screens might look different on your system.
Select “ From area menu” button
Enter /OPT/VIM area menu in the area menu field and choose enter
Save
Expand all and give display authorization only in activity field. use to open the activity field.
Add display authorization for all transaction starting with /OPT/ by inserting manually.
Go to the user tab and enter early watch user or user with display VIM profile.
15 Reminder/Notifications program
The Open Text Vendor Invoice Management Reminder has been developed to:
• find out all workflow work items for each current agent
• collect related information for each work item into a list
• determine Due Date for each work item using SAP standard or customized Function Module
• display the list for all current agents and the end‐user of this reporter can send internet email or SAP
notes to selected current agent(s) to “reminder” him/her there are “Due” work items based on
configurable data (Online mode)
• send internet email or SAP notes to each current agent to “reminder” him/her there are “Due” work
items based on configuration data (BACKGROUND mode)
This guide is intended to give instructions on the usage of the Reminder both from an end‐user perspective.
From the user perspective, the guide includes a description of each of the following:
• The main selection screen and its options
• Explanation of the data reported
• User interactions
• Configuration data
The main VIM Reminder program is started via transaction code “/OPT/REMINDER”. This program will be
typically scheduled as a batch job so that the relevant agents get notifications of reminders regularly.
All functions of the VIM Reminder are controlled via a common selection screen. This screen appears below.
This panel allows you to enter your search criteria and the panel is divided into the following sections:
• Invoice Information
• Document Process
• Workitem Date Range
• Mail Configuration
• Process Options
15.2.1 Invoice Information
This section allows you to enter search criteria for the invoice.
• Company Code: Organizational unit within financial accounting.
• Document Number: Accounting document number of the invoice.
• Fiscal Year: Fiscal year that the invoice was blocked or parked.
• Line: Item The document line of this invoice.
15.2.2 Document Process
This section allows you to enter search criteria for Document Processing information.
• Document ID: the number that was generated for the document during the Open Text Document
Processing.
15.2.3 Workitem Date Range
This section allows you to enter search criteria for work item information.
• Workitem Creation Date: Creation Date of Work Item
15.2.4 Mail Configuration
This section allows you to enter configuration data for mail/note.
• Mail Title: specify title for mail/note
15.2.5 Process Options
This section allows you to enter processing options. There are two parts in this group:
• Scenario: specify document type
• Mode: specify process mode
This part of processing options sections allows you to check document type
• Document Process WFs: include DP work items
• PO Block Invoices – Head: include PO Block Invoice head work items
• PO Block Invoices – Line: include PO Block Invoice line work items
• PO Parked Invoices WFs: include PO Parked invoice work items
• NPO Parked Invoices WFs: include NPO Parked invoice work items
• Approval PO Invoices: include approval PO invoice work items
• Approval Non PO Invoices: include approval Non PO invoice work items
This section describes the display of the report results that are available in running the Reminder.
Clicking this will send internet email/SAP note to selected current agent.
Clicking this will call SAP transaction SCOT
The following are the available columns in the ALV Grid output.
Column Description
Current Agent Current agent who owns items
Process Type Type of the document (DP, PO/NPO doc…)
Sub Process Type Sub Process Type for each process Type
Company Company Code
Document number SAP Document number
Fiscal year Fiscal year
Document ID The Document Processing document ID
Vendor Vendor Number
Name 1 Vendor name
Total Amount Total amount
Doc Currency Doc Currency
Inbox Days Days the WI in the inbox
Before Due Days before due date
Due Date Document Due Date
First Name First name of current agent
Last Name Last name of current agent
Responsible Party Responsible Role
Receiver ID Email Address of current agent
ID Workitem ID
AAK
AP processor
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
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
Baseline
Set of functionality with pre-defined configuration and the starting point to implement
VIM
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
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
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
Coding
Contract agent
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
Open Text DocuLink enables the archiving, management and retrieval of CRM or ERP
documents from within the SAP infrastructure.
VIM component that captures invoice metadata including line items for PO and performs
preconfigured business rules
Document type
DP
Duplicate analyzer
Error handling method. Event Type Linkage determines what the application should do in
case an error could not be handled.
Exception
FI
IE
Indexer
Indexing
Information provider
Invoice Approval
VIM component that enables users to perform coding, approving and rejecting invoices
Invoice approver
Invoice coder
Person who enters the accounting info on invoices to allocate the cost
VIM component that handles the exceptions that arise after a SAP invoice is created
Invoice requester
LIV
Materials Management
SAP MM is the materials management module of the SAP ERP software package.
Materials management is used for procurement and inventory management.
MM
(MM)
Namespace
Name range reserved by SAP for customer objects and SAP objects to make sure that
objects are not overwritten by SAP objects during the import of corrections or an upgrade
Number range
Array of numbers that can be used for an object in the SAP system
OCR
Park
Situation where an invoice is not posted and is waiting for further processing
Temporary document that the AP processor can change and post. SAP assigned document
number becomes real number when posted.
PIR
PO
Invoice that has already been posted in SAP. Only free-form text fields can be changed.
Related documents such as POs or good receipts may be created or changed to effect the
invoice. If the document is not needed, it must be cancelled ( PO invoice) or reversed (
non-PO invoice).
Price variance
Situation where the price on the invoice is different from the price in the purchase order
Process options
Processing options for the user in the dashboard, such as Referral, Authorization, and
Actions
Process type
Process type for a document. The process type determines the initial actor and various
collaboration options available to the various actors during the process flow.
SAP module. PO indicates a document sent from a buyer to a seller. The purpose of the
document is to order the delivery of goods or services.
Quantity variance
Situation where the quantity on the invoice is different from the quantity in the purchase
order
Receiver
Person who can create and reverse the goods receipt in SAP
Requisitioner
Roles
Scan operator
Person who scans the invoices into images (may not have a SAP ID)
Service approver
Service requisitioner
Swimlane
Tax expert
Person who advises on invoices that need tax audit. Normally tax department personnel.
VAN
Packaged business solution that solves a business problem – paying correct amount to
vendors on-time and with the lowest cost. VIM delivers not technology but best-practice
business processes. VIM provides values to customers in process efficiency, visibility and
compliance.
Vendor maintenance
Person who is responsible for creating and maintaining the vendor master records
Optional web-based VIM component that allows vendors to track their own POs, goods
receipts, payments and the status of invoices.
VIM
VIM component that gives users a clear data report on their invoices in progress. VIM
Analytics allows to track the documents routed through SAP workflows via VIM.
VSS
Workflow
SAP business workflows can be used to define business processes that are not yet mapped
in the R/3 system.