MarkView for SAP - Addressing some performance issues

Applies To

• ERP System: SAP
• MarkView Version: All Versions

Behavior

• Depending on your usage trends and data volume, you may see some performance issues in MarkView for SAP and/or 'Low Memory' warnings reported in SAP related to MarkView. These can be addressed by adding the appropriate indexes to facilitate the queries MarkView executes on the ERP data.

Resolution

Functional Context - MarkView Viewer Performance / Get Invoice Info
Applies to: All MarkView Versions
Table: BKPF
Fields (in order): MANDT, BLDAT, BUDAT, BVORG

Steps to create this index:

1. Go to transaction SE11 and input table BKPF in the Database Table field
2. Click the Display button
3. Click on the "Indexes..." button
4. On the "Indices for Table BKPF" dialog window, click on the "Create Index" button
5. On the Create Index dialog window enter a name for the Index
6. Click Ok, you may receive a warning - this is ok, click through
7. You will receive a Customer Modif: Different Original and Logon languages pop up - Click on the "Maintain in orig. lang" button.
8. In the short description enter a description for the index
9. Enter the fields in the following order:
   1. MANDT
   2. BLDAT
   3. BUDAT
   4. BVORG
10. Save and activate the Index
11. In order to propagate the Index to the database you must next click on Utilities -> Database Utility
12. In the "Execute database operation" box on the "ABAP Dictionary: Utility for Database Indexes" window, make sure the Direct radio button is selected and then click on the "Create database index" button. WARNING: For customers with a large volume, you may wish to do this during downtime because the operation locks the table and can take some time.
13. Index created, process complete.

The other indexes detailed below can be implemented using similar steps to those outlined above. (Example steps are Oracle database specific - For others, refer to SAP documentation for adding indexes)

Functional Context - MarkView Express Performance / Get Invoice Info
Applies to: MarkView 6.0 to 6.5
Table: BSAK
Fields (in order): MANDT, BUKRS, AUGBL, AUGDT

Functional Context - Web Inquiry
Applies to: MarkView 6.0 to 6.5
Table: LFA1
Field: NAME1

Functional Context - Web Inquiry
Applies to: All MarkView Versions
Table: REGUH
Fields (in order): VBLNR, LIFNR

Functional Context - Web Inquiry
Applies to: MarkView 6.0 to 6.5
Table: BSAK
Fields (in order): MANDT, BUKRS, LIFNR

Functional Context - Advisor (both Cold Sync and Hot Sync), Also used in Electronic Invoice Rendering (EIR)
Applies to: All MarkView Versions
Table: EDIDS
Fields (in order): MANDT, STATUS, CREDAT, STAPA1, STAPA2, STAPA3

Functional Context - Advisor (Cold Sync)
Applies to: All MarkView Versions
Table: RBKP
Fields (in order): XBLNR, LIFNR, BUKRS

Functional Context - MarkView Express Performance / Web Inbox
Applies to: MarkView 6.0 to 6.5
Table: BSAK
Fields (in order): MANDT, BUKRS, GJAHR, BELNR

Functional Context – Receipt Matching - MVAP_RECEIPTS_MV
Applies to: MarkView 8.1 and higher
Table: RSEG
Fields (in order): MANDT, EBELN, EBELP

Note: Some SAP implementations may already include an index on these fields. If that index exists in your environment and is switched on there is no need to create a new custom index.

Keywords: preformance