EMC ViewPoint for SAP (4.7) Purchasing Module Version 2.0 ......EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 EMC ViewPoint for SAP (4.7) Purchasing

EMC ViewPoint for SAP (4.7)Purchasing Module

Version 2.0

ADMINISTRATION MANUALP/N 300-002-928

REV A02

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

ii

Copyright © 2006 EMC Corporation. All rights reserved.Published February, 2006

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

EMC ViewPoint for SAP MM Module Administration Manual

Contents

Preface ............................................................................................................................. v

Chapter 1 Introducing the ViewPoint MM ModuleIntroduction ...................................................................................... 1-2ViewPoint Purchasing Module (MM)........................................... 1-3

Supplied menus ........................................................................ 1-3Basic information about the ViewPoint MM Module ......... 1-3

Chapter 2 Construction of the ViewPoint MM ModulePurchasing documents (non-unicode).......................................... 2-2

Procedure ................................................................................... 2-2Load program /PBS/CMMELDR3........................................ 2-5Initial load process.................................................................... 2-8Loading of administration table /PBS/CMMEIFILE........ 2-12Further load processes ........................................................... 2-14

Purchasing documents (unicode) ................................................ 2-18Load program /PBS/CMMELDR3_ADK .......................................................................................... 2-19Initial load process.................................................................. 2-23Loading of administration table /PBS/CMMEFILE......... 2-28Further load processes ........................................................... 2-31

Purchase requisitions..................................................................... 2-33Procedure ................................................................................. 2-33Load program /PBS/CMMBLDR3...................................... 2-35Initial load process.................................................................. 2-38Loading of administration table /PBS/CMMB_FILE ....... 2-40Further load processes ........................................................... 2-42

Purchasing info records ................................................................ 2-45

EMC ViewPoint for SAP MM Module Administration Manual iii

Contents

Procedure................................................................................. 2-45Load program /PBS/CMMILDR3....................................... 2-46Initial load process.................................................................. 2-49Loading of administration table /PBS/CMMI_FILE........ 2-51Further load processes ........................................................... 2-52

Accounting documents ................................................................. 2-55Procedure................................................................................. 2-55The load program /PBS/CMMRLDR3............................... 2-56First load run........................................................................... 2-59Loading the administration table /PBS/CMMR_FILE .... 2-60Further load runs.................................................................... 2-62

Disk space requirements............................................................... 2-64Use of several application servers............................................... 2-65

Chapter 3 Long-Term ArchivingIntroduction...................................................................................... 3-2Purchasing documents.................................................................... 3-3

Access to data transferred into external storage .................. 3-3Purchase requisitions ...................................................................... 3-5

Creation of secondary archives .............................................. 3-5Invoice documents........................................................................... 3-7

Creation of secondary archives .............................................. 3-7

Appendix A Additional MM InformationPurchasing documents .................................................................. A-2

Archive tools ............................................................................ A-2Additional tools ....................................................................... A-8

Purchase requisitions .................................................................... A-9Archive tools ............................................................................ A-9Additional tools ..................................................................... A-13

Purchasing info records .............................................................. A-14Archive tools .......................................................................... A-14Additional tools ..................................................................... A-17

Invoice documents ....................................................................... A-18Archive tools .......................................................................... A-18Additional tools ..................................................................... A-21

EMC ViewPoint for SAP MM Module Administration Manualiv

Preface

As part of an effort to improve and enhance the performance and capabilities of its product line, EMC from time to time releases revisions of its hardware and software. Therefore, some functions described in this manual may not be supported by all revisions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this manual, please contact your EMC representative.

ViewPointFunctionality

This document describes how to administer the various components that make up EMC ViewPoint for SAP Purchasing (MM) Module. EMC’s technology allows you to effectively manage your application data by providing the ability to define the access, retention, and service level requirements for any business transaction at each point in its lifecycle.

Audience This guide is part of the ViewPoint documentation set, and is intended for use by anyone administering the ViewPoint for SAP MM Module. It is assumed that the installer has a working knowledge of SAP Basis, and has the appropriate levels of responsibilities to perform the tasks described.

EMC ViewPoint for SAP MM Module Administration Manual v

vi

Preface

RelatedDocumentation

Be sure to review the EMC ViewPoint for SAP Release Notes for the most up-to-date information on product features.

The following list of related documents are available on the EMC ViewPoint for SAP Documentation CD that was delivered with your EMC ViewPoint SAP software CD.

Both the release notes and documentation CD can be found at:

http://Powerlink.EMC.com

Introductory� EMC ViewPoint for SAP Documentation CD

� EMC ViewPoint for SAP Release Notes

Installation� EMC ViewPoint for SAP Modules Installation Manual

� EMC ViewPoint for SAP Analyzer Plus Installation and User Manual

� EMC ViewPoint for SAP BW Analyzer Installation Manual

� EMC ViewPoint for SAP Construction and Maintenance Installation Manual

� EMC ViewPoint for SAP Fiscal Year Reporter Module Installation and User Manual

Miscellaneous� EMC ViewPoint for SAP Material Master Data, Batches, Special

Stocks, and BOMs Module Modification Manual

Administrative� EMC ViewPoint for SAP Controlling Line Items Module

Administration Manual

� EMC ViewPoint for SAP Financial Accounting and Material Documents Module Administration Manual

� EMC ViewPoint for SAP Purchasing Module Administration Manual

� EMC ViewPoint for SAP Sales and Distribution Module Administration Manual

� EMC ViewPoint for SAP Production Orders Module Administration Manual

� EMC ViewPoint for SAP Agency Business Module Administration Manual

� EMC ViewPoint for SAP Construction and Maintenance Module Administration Manual


Preface

� EMC ViewPoint for SAP Costing-Based Profitability Analysis Module Administration Manual

� EMC ViewPoint for SAP Master Data Changes Module Administration Manual

� EMC ViewPoint for SAP Data Retention Tool Module Administration Manual

� EMC ViewPoint for SAP Contract Account Documents Module Administration Manual

� EMC ViewPoint for SAP HR Archiving Objects Module Administration Manual

� EMC ViewPoint for SAP Material Ledger Documents Module Administration Manual

� EMC ViewPoint for SAP Material Master Data, Batches, Special Stocks, and BOMs Module Administration Manual

� EMC ViewPoint for SAP Controlling Orders Module Administration Manual

� EMC ViewPoint for SAP Profit Center Line Items Module Administration Manual

� EMC ViewPoint for SAP Plant Maintenance Module Administration Manual

� EMC ViewPoint for SAP Production Orders Module Administration Manual

� EMC ViewPoint for SAP Process Orders Module Administration Manual

� EMC ViewPoint for SAP Project Systems Module Administration Manual

� EMC ViewPoint for SAP Line Items Module Administration Manual

� EMC ViewPoint for SAP Special Ledger Module Administration Manual

� EMC ViewPoint for SAP Warehouse Management Module Administration Manual

� EMC ViewPoint for SAP Custom Module Administration Manual

User� EMC ViewPoint for SAP Analyzer Plus Installation and User Manual

� EMC ViewPoint for SAP Analyzer Lite Installation and User Manual

EMC ViewPoint for SAP MM Module Administration Manual vii

viii

Preface

� EMC ViewPoint for SAP Analyzer BW User Manual

� EMC ViewPoint for SAP Controlling Line Items Module User Manual

� EMC ViewPoint for SAP Financial Accounting and Material Documents Module User Manual

� EMC ViewPoint for SAP Purchasing Module User Manual

� EMC ViewPoint for SAP Sales and Distribution Module User Manual

� EMC ViewPoint for SAP Production Orders Module User Manual

� EMC ViewPoint for SAP Modules Utilities User Manual

� EMC ViewPoint for SAP Agency Business Module User Manual

� EMC ViewPoint for SAP Construction and Maintenance Module User Manual

� EMC ViewPoint for SAP Costing-Based Profitability Analysis Module User Manual

� EMC ViewPoint for SAP Master Data Changes Module User Manual

� EMC ViewPoint for SAP Contract Account Documents Module User Manual

� EMC ViewPoint for SAP HR Archiving Objects Module User Manual

� EMC ViewPoint for SAP Material Ledger Documents Module User Manual

� EMC ViewPoint for SAP Material Master Data, Batches, Special Stocks, and BOMs Module User Manual

� EMC ViewPoint for SAP Controlling Orders Module User Manual

� EMC ViewPoint for SAP Profit Center Line Items Module User Manual

� EMC ViewPoint for SAP Plant Maintenance Module User Manual

� EMC ViewPoint for SAP Production Orders Module User Manual

� EMC ViewPoint for SAP Process Orders Module User Manual

� EMC ViewPoint for SAP Project Systems Module User Manual

� EMC ViewPoint for SAP Special Ledger Module User Manual

� EMC ViewPoint for SAP Export Interface for Special Ledger Data User Manual

� EMC ViewPoint for SAP Warehouse Management Module User Manual


Preface

� EMC ViewPoint for SAP Fiscal Year Reporter Module Installation and User Manual

Conventions Used inThis Guide

EMC uses the following conventions for notes, cautions, warnings, and danger notices.

Note: A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment. The caution may apply to hardware or software.

WARNING

A warning contains information essential to avoid a hazard that can cause severe personal injury, death, or substantial property damage if you ignore the warning.

DANGER

A danger notice contains information essential to avoid a hazard that will cause severe personal injury, death, or substantial property damage if you ignore the message.

Typographical ConventionsEMC uses the following type style conventions in this guide:

bold • User actions (what the user clicks, presses, or selects)• Interface elements (button names, dialog box names)• Names of keys, commands, programs, scripts, applications,

utilities, processes, notifications, system calls, services, applications, and utilities in text

italic • Book titles• New terms in text• Emphasis in text

Courier • Prompts • System output • Filenames • Pathnames• URLs • Syntax when shown in command line or other examples

EMC ViewPoint for SAP MM Module Administration Manual ix

x

Preface

Where to Get Help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC WebSupport on Powerlink. To open a case on EMC WebSupport, you must be a WebSupport customer. Information about your site configuration and the circumstances under which the problem occurred is required.

Your Comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this guide to:

[email protected]

Courier, bold • User entry• Options in command-line syntax

Courier italic • Arguments in examples of command-line syntax• Variables in examples of screen or file output• Variables in pathnames

<> Angle brackets for parameter values (variables) supplied by user.

[] Square brackets for optional values.

| Vertical bar symbol for alternate selections. The bar means or.

... Ellipsis for nonessential information omitted from the example.


http://powerlink.emc.com

1Invisible Body Tag

This chapter includes these topics:

� Introduction ........................................................................................1-2� ViewPoint Purchasing Module (MM) .............................................1-3

Introducing theViewPoint MM Module

Introducing the ViewPoint MM Module 1-1

1-2

Introducing the ViewPoint MM Module

IntroductionThe ViewPoint modules are constructed in modular form and cover the application modules FI, SD, MM, CO, etc. with a special program package for exactly this application. You can easily see from the name which ViewPoint module belongs to which SAP module: FI, SD, MM, CO, etc. All ViewPoint modules have in common that they can be easily installed in the SAP R/3 system via the SAP transport utilities "tp" and "SAINT". Installation details of the ViewPoint modules are contained in the EMC ViewPoint for SAP Modules Installation Manual.

This administration manual was written to make construction and administration of the ViewPoint MM Module as easy as possible. At first, data archiving with transaction SARA is discussed; the second topic is the ViewPoint index construction from the SAP archive files.

The EMC ViewPoint for SAP Modules Utilities User Manual contains additional module information.



ViewPoint Purchasing Module (MM)

Supplied menus A global menu is supplied with the ViewPoint module for all products and utilities of the ViewPoint software suite, as well as a special menu for the ViewPoint MM Module.

For releases 3.0 to 4.5, the global menu is started via transaction /PBS/PBS. A button then appears where it is possible to start the menu. From 4.6 the global menu can be incorporated in and started from the activity groups (4.6B) or the roles (from 4.6C) respectively.

The menu for the ViewPoint MM Module can be started for releases 3.0 to 4.5 via transaction /PBS/CMM or from the global menu. From release 4.6 it can be started by integrating menu /PBS/CMM into the activity group (4.6B) or into the roles (from 4.6C) respectively.

All programs described in this manual are contained in the menu.

Basic information about the ViewPoint MM Module

The administrative task of the ViewPoint module is to construct and activate the ViewPoint archive and, in the event of problems, to analyze this archive with the tools supplied.

Construction and use of the ViewPoint MM Module requires successful data archiving with SAP tools and access to the archive file created this way.

ViewPoint Purchasing Module (MM) 1-3

1-4



2Invisible Body Tag

From Release SAP Enterprise it is now possible for ViewPoint modules to be used in a unicode system as well as a non-unicode system. In a unicode system Purchase Orders, i.e. Archiving objects MM_EKKO are no longer archived in ViewPoint format. Purchasing documents are now archived like Purchase requisitions and Purchasing info records in SAP ADK-format. Because of this change the Index generation and activation for long-term archiving has been redone. The correct procedure in a non-unicode system can be found in “Purchasing documents (non-unicode)” on page 2-2 and for a unicode system in “Purchasing documents (unicode)” on page 2-18.


� Purchasing documents (non-unicode) ............................................2-2� Purchasing documents (unicode) ..................................................2-18� Purchase requisitions.......................................................................2-33� Purchasing info records...................................................................2-45� Accounting documents ...................................................................2-55� Disk space requirements .................................................................2-64� Use of several application servers .................................................2-65

Construction of theViewPoint MM Module

Construction of the ViewPoint MM Module 2-1

2-2

Construction of the ViewPoint MM Module

Purchasing documents (non-unicode)

Procedure In order to archive purchasing documents, the SAP archiving tool is first used to remove the data from the R/3 database. The tool is started via the transaction SARA. The archiving is object-oriented. MM_EKKO is the archiving object for purchasing documents. The archived data is written by the SAP archiving program into sequential files outside the database.

The reorganized data can no longer be reloaded into the database and can only be evaluated sequentially. The reduced load that this results in for the R/3 database can be measured with the help of the ViewPoint Database Analyzer.

The generated SAP archives are written with the ViewPoint load program /PBS/CMMELDR3 into the ViewPoint MM Module. The load program reads the SAP archive files, summarizes the documents in a table, generates secondary indices and stores this data in compressed form on magnetic disks outside the database. After the archive has been constructed, you must define in the administration table or /PBS/CMMEIFILE the file path under which the ViewPoint archive can be found in the UNIX or Windows/NT file system.

Program /PBS/CMMESCAN can display the contents of the ViewPoint MM Module for purchasing.

The archived purchasing documents are thus available for online processing and can be evaluated easily via the ViewPoint transactions. The ViewPoint transactions correspond to the SAP transactions from a functional point of view, but can read and display both the resident data located in the R/3 database and also the archived data from the ViewPoint module.

As the data contained in the ViewPoint module can no longer be changed, a regular data backup of the archive is not necessary. The SAP archive file created during the next reorganization of the database can be added to the existing ViewPoint module using the load program PBS/CMMELDR3.



The load program is called up using the ViewPoint menu /PBS/CMM, or customer-specific menu, where the node archive of the ViewPoint menu is established, as shown in Figure 2-1, “Starting the load program for archived purchasing documents.”

Figure 2-1 Starting the load program for archived purchasing documents

Purchasing documents (non-unicode) 2-3

2-4


Figure 2-2 Construction of ViewPoint Modules

R/3 database before the archiving run

SAP archiving program

for the object MM_EKKO

SAP archive files for purchasing documents

PBS archive add on CMM (purchasing documents)

Load program of the PBS archive add on CMM

R/3 database after the

archiving run

PBS transactions read both archive data and resident data

The archive files of the purchasing documents can no longer be evaluated with SAP transactions.

Data of the PBS archive add on is kept on magnetic disks outside the database, evaluation via transactions possible

MM data in the R/3 database in transaprent tables

With the PBS archiving technique the archived data can be provided again quickly and easily in online processing.



Load program /PBS/CMMELDR3

/PBS/CMMELDR3 The ViewPoint MM Module enables you to keep purchasing documents from R/3 available online. To do this, you construct the ViewPoint MM Module from the SAP archive files using the load program /PBS/CMMELDR3. The selection screen of the load program /PBS/CMMRLDR3 with its delimitation options is illustrated in Figure 2-3, “Selection screen of load program /PBS/CMMELDR3.”

Figure 2-3 Selection screen of load program /PBS/CMMELDR3

In the following section we will explain the delimitation options and their effect when creating the ViewPoint MM Module.

� Select archive from

� Select automatically from

� Delete old run


2-6


Select SAP archive If the radio button ’Select archive from’ is active, a window is displayed when the request screen is confirmed, showing a list of the available SAP purchasing archives created on or after the specified date, as shown in Figure 2-4, “Proposed list of SAP MM archives for Purchasing documents loadable into MM Archive.”

Figure 2-4 Proposed list of SAP MM archives for Purchasing documents loadable into MM Archive

Now select those SAP MM archives MM_EKKO that you want to load into your ViewPoint MM Module.

In the automatic mode, all SAP purchasing archives that were created on or after the date specified are selected, without the list being displayed. SAP purchasing archives from this period that have already been loaded into the online archive are not selected.

Delete old run The parameter 'Delete old run' enables you to remove complete load runs from the ViewPoint MM Module. By pressing the 'run button', an overview window of all previous load runs pops up, from which you can select the run to be deleted, as shown in Figure 2-5, “Overview of previous runs.”

Figure 2-5 Overview of previous runs



� Process all documents

Process all documents If this radio button is active, the selected SAP archives are loaded completely into the ViewPoint module. The loading of the same SAP archive for the second time is prevented by an internal safety mechanism.

� Process sequential number range: from 1 up to 9.999.999

Number range In case of very large SAP archives, you may want to break up the load run into several smaller parts. To do this, the radio button ’Process sequential number range’ must be active and the appropriate interval limit set.

Note: By using this setting, the automatic recognition of duplicate SAP archive selection is switched off. Furthermore, in this case interval overlapping is not checked.

� Document date lower limit

Load from date This parameter determines which documents are transferred into the new archive. This is based on the purchase order date. Older purchase orders contained in the ViewPoint CMM Module or in the SAP document archive are not transferred.

� Release Information

When this radio button is selected, an important information for the ViewPoint customers, that have not only created ViewPoint indices under earlier releases, but have also copied the SAP documents into the ViewPoint directory, is displayed. This method is no longer supported by the meanwhile achieved reliability of standard archive access routines of the SAP AG.

� Path name for online archive CMM

Archive directory In this field you specify the directory in which the ViewPoint CMM Module is to be constructed. Please keep in mind that the path name should be no longer than 50 characters. It is important that this path is defined in the system. This path cannot be created by the load program.

If you use other ViewPoint modules besides MM, please provide a separate path for each archive.

File authorizations Please keep in mind when specifying the pathname under Unix, that the R/3 administrator <SID>adm is the owner of the indicated


2-8


directory and has read and write authorization. In the example of the directory /pbs/cmm, the activation of writing authorizations is carried out with the command chmod u+w /pbs/cmm. Should you wish to change the owner, please contact the system administrator.

Initial load process If all necessary information has been entered in the selection screen of the load report /PBS/CMMELDR3, the selection screen can be stored as selection variant for the initial construction of the ViewPoint module, and the report can be started as a background process.

Note: The ViewPoint MM Module must be setup per client.

During runtime, the program generates the ViewPoint module for purchasing documents from the archive data and transfers this into the specified file path. The program generates new directories and files for this, as shown in Figure 2-6, “Files of the ViewPoint MM Module after the initial construction.”

Note: We strongly recommend a data backup of the created files after each archive construction.

The files created by the operating system after the initial construction could be as follows:

[loew@pbs25] 15) pwd/pbs/ce/

[loew@pbs25] 16) ls *BELEGE:

0011E_STEUERUNG0011E_SUMMEN001CUC0000000010

BIB001:

0013E_STEUERUNG0013E_SUMMEN

0013E_ZCEFILE001E6000526053

001GEKKO6000526053==========F02=D= 001K0000001578000001

001M0000000000000000000001001UEINKBELEG60005260530001000001

001W60005260530002000002001Z00119961021

TEXTE:

001B0000000044

Figure 2-6 Files of the ViewPoint MM Module after the initial construction



Directories The load program creates two sub-directories in the archive master directory. In one sub-directory the documents are stored (in our example /pbs/ce/BELEGE/), in the second the indices to the documents (after the first run of the load program /pbs/ce/BIB001/). If the load program /PBS/CMMELDR3 is started a second time to load more documents into the ViewPoint module, they are added to the documents already existing in the path /pbs/ce/BELEGE/. The indices created for the added documents are merged with the already existing indices in /pbs/ce/BIB001/ and transferred together into the directory /pbs/ce/BIB002/. The directory /pbs/ce/BIB001/ is then deleted by the load program.

Generally, you can assume the following: After run nnn of the load program /PBS/CMMELDR3, the sub-directories /BELEGE/ and /BIBnnn/ of the archive master directory are active.

Directory BELEG In the file 0011E_Summen, the control totals for index construction are provided for the load program. The file 0011E_Steuerung contains the information of the corresponding successfully completed run and the number from which the load program is to continue numbering the document clusters.

BIB directory In addition to general control information, secondary indices are also managed in the directory BIBnnn. The directory is provided with a sequential number (for example, BIB001) at the end. The files in the directory BIBnnn start with the 3-digit client number, followed by a letter that indicates the index involved. ’E’ means the document number indices, ’K’ the vendor indices, ’M’ the material indices, and ’O’ the accounting indices.

In the directory BIBnnn three management files are created. The files 0013E_Steuerung and 0013E_Summen are identical to the corresponding files in the directory BELEGE. The file 0013E_ZZEFILE contains the archive directory. This file is loaded with the ABAP/4 program /PBS/CMMEFILE into the database to enable an access to the archive files, described in “Further load processes” on page 2-14.

After the purchasing document archive has been generated successfully, the program /PBS/CMMELDR3 displays an archive selection statistic, as shown in Figure 2-7, ”Selection statistic /PBS/CMMELDR3,” on page 2-12.


2-10


This is run number 001

D O C U M E N T S T A T I S T I C

----------------------------------

Read purchase orders from acquisition: 195

Written purchase orders from acquisition: 195

Purch. order items from acquisition: 223

Written document cluster from stock: 0

Archived document cluster from stock: 0


Written document cluster from acquisition: 0

Written text cluster from stock: 0

Archived text cluster from stock: 0


Written text cluster from acquisition: 0

Exported document index cluster: 1

Exported vendor index cluster: 61

Exported vendor index cluster: 61

Exported material index cluster: 189

Exported purch. history cluster: 0

Exported purch. change cluster: 0



Exported text index cluster: 0

S E C O N D A R Y I N D E X S T A T I S T I C

------------------------------------------------

Acquis: Stock old: Stock new:

read archived written

--------------------------------------------------------------------------------------------

No. document indices : 195 0 0 195

No. text indices : 0 0 0 0

No. vendor indices : 223 0 0 223

No. material indices : 223 0 0 223

No. purch. ord. History : 0 0 0 0

No. purch. order changes : 0 0 0 0

------------

Delimitations

------------

ABARAUTO P 19900901

ABARCHIV P 19900901

ABDAT P 19870101

ALL_BEL P X

ANZ_BIS P 9999999

ANZ_VON P 1

ARCHLIST S 000155-001MM_EKKO

ARCHLIST S 000280-001MM_EKKO

ARCHNAME P

ARCHNUM S

AUTOMAT P


2-12


DELETE P X

ERDAT S

ER_EBELN S

ER_EKORG S

HANDLE P 0

INS_FLAG P

LOESCH P

LOETTBAN S

LOEZZBAN S

MANUELL P X

NOPOPUP P

NUR_BEL P

OBJ_OFF P 0

OLTEST P

PATH P /export/home/lautens/dummy

R2BAND P

XAR_BEL P

XAR_IND P X

Time statistic

-------------

Start of processing: 09:15:26

Start of sort: 09:15:34

End of sort: 09:15:34

End of processing: 09:15:34

ViewPoint CMM Module successfully constructed !

Figure 2-7 Selection statistic /PBS/CMMELDR3

Loading of administration table /PBS/CMMEIFILE

Having constructed the ViewPoint module with the load program /PBS/CMMELDR3, the administration table /PBS/CMMEIFILE must be loaded into the SAP R/3 system. This table contains the current directory tree of the online archive CMM.

The report /PBS/CMMEFILE is used to update the administration table. Table /PBS/CMMEIFILE describes the clear allocation between



the MM data in the ViewPoint CMM Module and the SAP R/3 system. The selection screen of the report is displayed in Figure 2-8, “Report /PBS/CMMEFILE for the loading of the administration records into the administration table /PBS/CMMEIFILE,”.

Enter as 'Path name of archive add on' the name of the current path into which the ViewPoint module files were previously transported by the load program /PBS/CMMELDR3. The parameter 'Test' must be qualified with SPACE.

If the parameter 'Test' is qualified, the administration records are imported, without them however being loaded into the SAP R/3 system. Figure 2-9, “Protocol load administration table,” shows the number of the imported data records.

Figure 2-8 Report /PBS/CMMEFILE for the loading of the administration records into the administration table /PBS/CMMEIFILE

Load file directory into database 1

------------------

Record type read

------------------

Number UE: 1

Number UK: 61

Number UM: 189

Number UR: 1

Number US: 1

ViewPoint CMM Module successfully activated

Figure 2-9 Protocol load administration table


2-14


Further load processes

Merge A ViewPoint module was created with the first load run, described in “Initial load process” on page 2-8. If more documents should now be added to the existing ViewPoint module, this is done in a similar way as described previously - by way of a merge run.

/PBS/CMMELDR3 When importing further SAP archive files you have to mark in the selection screen of the report /PBS/CMMELDR3 in the delimitation 'Select Archives' those SAP archive files that are to be merged with the existing online archive. If an SAP archive file was already loaded into the ViewPoint module during a previous run, the report recognizes this, and displays a warning message. Identical documents cannot exist more than once in the ViewPoint module.

The load program /PBS/CMMELDR3 should be started again as a batch process. A new ViewPoint archive is constructed from the existing ViewPoint module and the acquisition. Files that are no longer needed are deleted from the archive directory by the program /PBS/CMMELDR3.

A possible result of the merge run could be as shown in Figure 2-10, “Files of the ViewPoint MM Module after the merge,” (path name from the variant /export/home/lautens/dummy/):

lautens@sun45:/export/home/lautens/dummy 8% ls *

BELEGE:

0031E_STEUERUNG 0031E_SUMMEN 003SCMM_Lauf

BIB002:

0033E_STEUERUNG 003K0000000002000001

0033E_SUMMEN 003M0000000000000000000001

0033E_ZCEFILE 003R00119981019

003E5360005370

Figure 2-10 Files of the ViewPoint MM Module after the merge

A typical selection statistic after the merge run could be as shown in Figure 2-11, “Selection statistic of /PBS/CMMELDR3 after the merge run.”

This is run number 002



D O C U M E N T S T A T I S T I C

-----------------------------------



Purchasing item from acquisition: 222

Read document cluster from stock: 0

Archived document cluster from stock: 0


Written document cluster from acquisition: 0

Read text cluster from stock: 0

Archived text cluster from stock: 0


Written text cluster from acquisition: 0

Exported document index cluster: 2

Exported delivery index cluster: 61

Exported material index cluster: 189


2-16


Exported purch. ord. history cluster: 0

Exported purch. ord. change cluster: 0

Exported text index cluster: 0

S E C O N D A R Y I N D E X S T A T I S T I C

------------------------------------------------

Acquis. Stock old: Stock new:

read archived written

----------------------------------------------------------------------------------Number document indices : 194 195 0 389

Number text indices : 0 0 0 0

Number vendor indices : 222 223 0 445

Number material indices : 222 223 0 445

Number purch. ord. History: 0 0 0 0

Number purch. ord. Changes: 0 0 0 0

Figure 2-11 Selection statistic of /PBS/CMMELDR3 after the merge run

If all further load processes are completed, proceed as described in “Loading of administration table /PBS/CMMEIFILE” on page 2-12



by loading the administration table /PBS/CMMEIFILE into the SAP R/3 system via the report /PBS/CMMEFILE.


2-18


Purchasing documents (unicode)In order to archive purchase requisitions, the SAP archiving tool is first used to remove the data from the R/3 database. The tool is started via the transaction SARA. The archiving is object-oriented. MM_EKKO is the archiving object for the purchase requisitions. The SAP archiving program writes the archived data into sequential files outside the database.


The generated SAP archives are written into the ViewPoint CMM Module by the ViewPoint load program /PBS/CMMELDR3_ADK. The load program reads the SAP archive files and creates several secondary indices. In contrast to the purchasing documents, these are not stored in a ViewPoint-specific format but in the SAP ADK for-mat like the archived purchase requisitions.

The physical directory or the files in which this data is stored result from the logical path that was assigned to the archiving object /PBS/CMME via the transaction AOBJ. We supply the archiving object with the logical standard path ARCHIVE_DATA_FILE, which is also used for the original archiving object MM_EKKO. However, we recommend that a separate logical path is defined in archive object customizing for ViewPoint archiving objects.

Having constructed the secondary indices, the archived purchase requisitions are available for online processing and can be evaluated easily using the ViewPoint transactions. The ViewPoint transactions are identical to the SAP transactions from a functional point of view, but can read and display both the resident data located in the R/3 database and also the archived data from the ViewPoint module.

As the data contained in the ViewPoint module is no longer changed, a regular data back-up of the archive is not necessary. The SAP archive file created during the next reorganization of the database can be added to the existing ViewPoint module with the help of the load program /PBS/CMMELDR3_ADK.



The load program is called via ViewPoint menu /PBS/CMM or customer-specific menu, where the archive node of the ViewPoint menu is established, as shown in Figure 2-12, “Starting the load program for archived R/3 purchase requisitions.”

Figure 2-12 Starting the load program for archived R/3 purchase requisitions

Load program /PBS/CMMELDR3_ADK

/PBS/CMMELDR3_ADK The ViewPoint MM Module enables you to keep R/3 purchase requisitions available online. To do this, you use the load program /PBS/CMMELDR3_ADK to construct the ViewPoint CMM Module from the SAP archive files.

Purchasing documents (unicode) 2-19

2-20


The selection screen of the load program /PBS/CMMELDR3_ADK with its delimitations is displayed in Figure 2-13, “Selection screen of load program /PBS/CMMELDR3_ADK.”

Figure 2-13 Selection screen of load program /PBS/CMMELDR3_ADK

In the following section we will explain the delimitation options and their effect when loading the purchase requisitions into the ViewPoint MM Module.

� Select manually

� Select automatically

� Delete old run



Select SAP archive If the radio button ’Select manually’ is active, a window is displayed when the request screen is confirmed. This window displays a list of the available SAP purchasing archives created on or after the date you have specified, as shown in Figure 2-14, “Proposed list of SAP MM archives of Purchase requisitions loadable into MM archive.”

Figure 2-14 Proposed list of SAP MM archives of Purchase requisitions loadable into MM archive

Now select those SAP MM archives MM_EKKO that you want to load into your ViewPoint MM Module.

In the automatic mode, all SAP purchasing archives that were created on or after the date you have entered are selected, without the list being displayed. Purchase order archives of this period that have already been loaded into the ViewPoint module are not selected.


2-22


Delete old run The parameter ’Delete old run’ enables you to remove complete load runs from the ViewPoint MM Module. If you press the button Run, an overview of the runs that have previously been carried out is displayed, from which you can select the run to be deleted, as shown in Figure 2-15, “Overview of previous runs — run 2 canceled in run 4 — deletion selection made in runs 1, 3, and 5.”

Figure 2-15 Overview of previous runs — run 2 canceled in run 4 — deletion selection made in runs 1, 3, and 5


Process all documents If this radio button is active, the selected SAP archives are loaded completely into the ViewPoint module. Loading of the same SAP ar-chive a second time is prevented by an internal safety mechanism.

� Process sequential number interval from 1 to 9,999,999

Sequential interval In the case of very large SAP archives, you may want to break up the load run into several smaller parts. To do this, the radio button ’Process sequential number range’ must be active and the appropriate interval limit set.

� Create administration indices

Manage indices Setting this parameter results in the administration table /PBS/CMMEFILE being updated at the end of the actual load process. If you want to carry out several load processes one after another, this parameter should not be set until the last run. If this parameter was not set, or if the entries in the administration table /PBS/CMMEFILE were corrupted, you can construct the



administration indices separately at any time via the report /PBS/CMMEFILE_ADK.

� Delete previous run

Delete previous run If this parameter is set, it results in the data from the previous run being automatically deleted after the current load run has been completed successfully. In the implementation phase it is often advisable not to set this parameter, and to keep the previous run for safety reasons. Older runs can be deleted separately later on via the report /PBS/CMMEDELR_ADK.

Initial load process If all necessary information has been entered in the selection screen of the load report /PBS/CMMELDR3_ADK, the selection screen can be saved as a selection variant for the initial construction of the online archive, and the report can be started as background process.

Note: The ViewPoint MM Module must be constructed per client.

During run time, the program generates the ViewPoint module of purchase requisitions from the archive data. After the purchasing document archive has been generated successfully, the program /PBS/CMMELDR3_ADK displays an archive selection statistic, as shown in Figure 2-16, “Selection statistic of /PBS/CMMELDR3.”

Time statistic

-------------





Table statistic

------------------------------------------------------------------------------------

No. BANF read: 3

No. BANF processed 3

------------------------------------------------------------------------------------

Table records read


2-24


------------------------------------------------------------------------------------

EKKO 3

EKPO 15

EKBE 31

EKET 15

KONV 30

NAST 6

EKPA 4

EKKN 1

ESSR 1

ESKN 1

------------------------------------------------------------------------------------

Index read from stock

------------------------------------------------------------------------------------

SEKI AUFNR 3

SEKI BEDAT 60

SEKI BEDNR 5

SEKI EBELN 60

SEKI KOSTL 4

SEKI LBLNI 3

SEKI LIFNR 59

SEKI MATKL 195

SEKI MATNR 191

------------------------------------------------------------------------------------

Index written total

------------------------------------------------------------------------------------

SEKI AUFNR 4

SEKI BEDAT 63

SEKI BEDNR 5



SEKI EBELN 63

SEKI KOSTL 4

SEKI LBLNI 4

SEKI LIFNR 62

SEKI MATKL 210

SEKI MATNR 205

------------------------------------------------------------------------------------

Index table exported tables

------------------------------------------------------------------------------------

SEKI 9

Product. Mode: Statistics on Written Data Objects

--------------------------------------------------------------------------------

Archive File Key 028134-001/PBS/CMME

Number of Written Data Objects 18

Size of Archive File in MB 0,030

Proportion of Header Data in % 5,7

Occupied Database Space in MB 0,330

- Tables 0,003

- Indexes 0,002

- Structures 0,326

--------------------------------------------------------------------------------

| Type No. Description |


2-26


--------------------------------------------------------------------------------

| /PBS/CMMEHEAD 18 |

| /PBS/CMMELAUF 16 |

| /PBS/CMMELOG 877 |

| /PBS/CMMESEKI 620 |

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

Summary

Archiving Session Number 028134

Number of Written Data Objects 18

Size of Archiving Session in MB 0,030

Proportion of Header Data in % 5,7

Occupied Database Space in MB 0,330

- Tables 0,003

- Indexes 0,002

- Structures 0,326

--------------------------------------------------------------------------------

| Type No. Description |



--------------------------------------------------------------------------------

| /PBS/CMMEHEAD 18 |

| /PBS/CMMELAUF 16 |

| /PBS/CMMELOG 877 |

| /PBS/CMMESEKI 620 |

--------------------------------------------------------------------------------

11.01.2005 Generating program CMM (purchasing requisitions) 3

---------------------------------------------------------------------- Constr. PBS archive add on CMM/EBAN successfully compl!

Figure 2-16 Selection statistic of /PBS/CMMELDR3

Note: If the load program is terminated with the message ABAP/4 run time error

SYSTEM_NO_MORE_PAGING or EXTRACT_NO_MORE_PAGING

this is due to the insufficient size of the SAP paging.

1 - Via transaction SM04, Goto -> Memory an overview of the amount of memory being used for the roll and paging area by the active users and their transactions is displayed. Try to clarify whether it is not the current program but another program that requires so much memory.

2 - Use transaction DB11 to check in the current instance profile the parameters ’rdisp/ROLL_MAXFS’ and ’rdisp/PG_MAXFS’. The values stored there indicate the current block sizes for the roll or paging area (1=Block = 16 Kilobytes, 1 Kilo-byte = 1024 Bytes).

3 - As far as the system is concerned, compare the size of the common partition for the roll and paging areas with the values from transaction DB11. If the converted values do not correspond to the size of the partition, the parameters ’rdisp/ROLL_MAXFS’ and ’rdisp/PG_MAXFS’ have to be adjusted to the provided partition.


2-28


4 - Start your R/3 system again.

If the parameter was changed, the run has to be repeated after the data back-up of the ViewPoint module has been reloaded.

In addition, we should like to draw your attention to SAP Note No. 14779, which provides more information regarding the error described above.

Loading of administration table /PBS/CMMEFILE

By selecting the Index activation over the Menu "Archive’ Purchase Order’ Index activation" a pop-up displayed for selecting Old or New Data will appear, as shown in Figure 2-17, “Selection screen, old index - new index.”

Figure 2-17 Selection screen, old index - new index

R/2 data selection - Allows the user to activate a given non-unicode system Index into a unicode system Index. Further explanation for this selection can be found in “Loading of administration table /PBS/CMMEIFILE” on page 2-12 for non-unicode systems. In this case, it is not necessary to generate such new Indices.

R/3 data selection - Create an Index in a unicode system. This refers to all new newly generated Indices in a unicode system.



If in the generating program for Purchase Orders the checkbox "Create management Indices" is activated. All runs will then be automatically made with the proper selection.

The selection screen for activating unicode Indices with the program /PBS/CMMEFILE_ADK is shown in Figure 2-18, “Selection screen for generating archive indices.”

Figure 2-18 Selection screen for generating archive indices

Use last run selection Selecting this parameter causes a automatic activation of the last used run.

Select run manuallyselection

In the Testing or Implementing phases it is suggestive not to delete older load runs.

These run can be deleted at anytime later on when needed.

By selecting "Select run manually" the user can reactivate runs as needed. Figure 2-19, “Selection list for activating archived indices in a


2-30


selected run,” shows a selection list as given when selecting this function.

Figure 2-19 Selection list for activating archived indices in a selected run

A reactivation in this example can be made when selecting SAP-Run 027971. SAP-Run 027945 shows a active secondary archive which can not be selected here.

All other parameters have to do with secondary archives described in “Creation of secondary archives” on page 3-7.



A Protocol for a successful activation from the chosen Index run is shown in Figure 2-20, “Protocol from completed run.”

Figure 2-20 Protocol from completed run

Delete indicesselection

This parameter selection allows the user to delete the actual entries found in the Administration table, without having to activate another run.


Merge A ViewPoint module was created with the first load process (“Further load processes” on page 2-42). If you now want to load additional documents into the already existing ViewPoint module, this procedure is carried out in a similar way as described previously - by way of a merge run.

/PBS/CMMELDR3_ADK When importing further SAP archive files, those SAP archive files that are merged with the existing ViewPoint module should be


2-32


marked in the selection screen of the report /PBS/CMMELDR3_ADK. If an SAP archive file has already been loaded into the ViewPoint module during a previous run, this is recognized by the report and a warning message is displayed. Identical documents cannot exist more than once in the ViewPoint module.

The load program /PBS/CMMELDR3_ADK should be started again as a batch process. A new ViewPoint archive is constructed from the existing add on and the access. Archives from previous runs are deleted automatically if the option "Delete previous run" is selected. However, ViewPoint purchase requisition archives from earlier runs can be deleted separately later on via the report /PBS/CMMEDELR_ADK.



Purchase requisitions

Procedure In order to archive purchase requisitions, the SAP archiving tool is first used to remove the data from the R/3 database. The tool is started via the transaction SARA. The archiving is object-oriented. MM_EBAN is the archiving object for the purchase requisitions. The SAP archiving program writes the archived data into sequential files outside the database.


The generated SAP archives are written into the ViewPoint CMM Module by the ViewPoint load program /PBS/CMMBLDR3. The load program reads the SAP archive files and creates several secondary indices. In contrast to the purchasing documents, these are not stored in a ViewPoint-specific format but in the SAP ADK format like the archived purchase requisitions.

The physical directory or the files in which this data is stored result from the logical path that was assigned to the archiving object /PBS/CMMB via the transaction AOBJ. We supply the archiving object with the logical standard path ARCHIVE_DATA_FILE, which is also used for the original archiving object MM_EBAN. However, we recommend that a separate logical path is defined in archive object customizing for ViewPoint archiving objects.

Having constructed the secondary indices, the archived purchase requisitions are available for online processing and can be evaluated easily using the ViewPoint transactions. The ViewPoint transactions are identical to the SAP transactions from a functional point of view, but can read and display both the resident data located in the R/3 database and also the archived data from the ViewPoint module.

As the data contained in the ViewPoint module is no longer changed, a regular data backup of the archive is not necessary. The SAP archive file created during the next reorganization of the database can be added to the existing ViewPoint module with the help of the load program /PBS/CMMBLDR3.

Purchase requisitions 2-33

2-34


The load program is called via ViewPoint menu /PBS/CMM or customer-specific menu, where the archive node of the ViewPoint menu is established, as shown in Figure 2-21, “Starting load program for archived R/3 purchase requisitions.”

Figure 2-21 Starting load program for archived R/3 purchase requisitions



Load program /PBS/CMMBLDR3

/PBS/CMMBLDR3 The ViewPoint MM Module enables you to keep R/3 purchase requisitions available online. To do this, you use the load program /PBS/CMMBLDR3 to construct the ViewPoint MM Module from the SAP archive files. The selection screen of the load program /PBS/CMMBLDR3 with its delimitations is displayed in Figure 2-22, “Selection screen of load program /PBS/CMMBLDR3.”

Figure 2-22 Selection screen of load program /PBS/CMMBLDR3

In the following section we will explain the delimitation options and their effect when loading the purchase requisitions into the ViewPoint MM Module.

� Select manually


� Delete old run


2-36


Select SAP archive If the radio button ’Select manually’ is active, a window is displayed when the request screen is confirmed. This window displays a list of the available SAP purchasing archives created on or after the date you have specified, as shown in Figure 2-23, “Proposed list of SAP MM archives of purchase requisitions loadable into ViewPoint MM archive.”

Figure 2-23 Proposed list of SAP MM archives of purchase requisitions loadable into ViewPoint MM archive

Now select those SAP MM archives MM_EBAN that you want to load into your ViewPoint MM Module.

In the automatic mode, all SAP purchasing archives that were created on or after the date you have entered are selected, without the list being displayed. Purchase requisition archives of this period that have already been loaded into the ViewPoint module are not selected.



Delete old run The parameter ’Delete old run’ enables you to remove complete load runs from the ViewPoint MM Module. If you press the button Run, an overview of the runs that have previously been carried out is displayed, from which you can select the run to be deleted, as shown in Figure 2-24, “Overview of previous runs — runs 2, 4, and 5 reset in runs 3, 6, and 7 — runs 1 and 8 selectable for deletion.”

Figure 2-24 Overview of previous runs — runs 2, 4, and 5 reset in runs 3, 6, and 7 — runs 1 and 8 selectable for deletion


Process all documents If this radio button is active, the selected SAP archives are loaded completely into the ViewPoint module. Loading of the same SAP archive a second time is prevented by an internal safety mechanism.

� Process sequential number interval

Sequential interval In the case of very large SAP archives, you may want to break up the load run into several smaller parts. To do this, the radio button ’Process sequential number range’ must be active and the appropriate interval limit set.

� Create administration indices

Manage indices Setting this parameter results in the administration table /PBS/CMMB_FILE being updated at the end of the actual load process. If you want to carry out several load processes one after another, this parameter should not be set until the last run. If this parameter was not set, or if the entries in the administration table /PBS/CMMB_FILE were corrupted, you can construct the administration indices separately at any time via the report /PBS/CMMBFILE or the menu point Archive > Purchase Requisitions > Construct Admin.Table respectively.



2-38


Delete previous run If this parameter is set, it results in the data from the previous run being automatically deleted after the current load run has been completed successfully. In the implementation phase it is often advisable not to set this parameter, and to keep the previous run for safety reasons. Older runs can be deleted separately later on via the report /PBS/CMMBDELR or via the menu point Archive > Purchase Requisitions > Additional Tools > Complete deletion of the generation runs respectively.

Initial load process If all necessary information has been entered in the selection screen of the load report /PBS/CMMBLDR3, the selection screen can be saved as a selection variant for the initial construction of the online archive, and the report can be started as background process.

Note: The ViewPoint MM Module must be constructed per client.

During run time, the program generates the ViewPoint module of purchase requisitions from the archive data.

After the purchasing document archive has been generated successfully, the program /PBS/CMMELDR3 displays an archive selection statistic, as shown in Figure 2-25, “Selection statistic of /PBS/CMMBLDR3.”

Time Statistic





Table Statistic

No. BANF read: 1.580

No. BANF processed: 1.580

Table Records Read

EBANR 1.580



EBAN 1.580

EBKN 27

Index read from stock

Index written totally

EBAN BANFN 1.580

EBAN BEDNR 1.580

EBKN KOSTL 27

Index Table Exported Tables

EBAN 4

EBKN 1

Statistic of the Archived Objects

Archive file: 000870-001/PBS/CMMB Number of objects: 7

Figure 2-25 Selection statistic of /PBS/CMMBLDR3

Attention If the load program is terminated with the message ABAP/4 run time error

SYSTEM_NO_MORE_PAGING or EXTRACT_NO_MORE_PAGING

this is due to the insufficient size of the SAP paging.

1. Via transaction SM04, Goto > Memory an overview of the amount of memory being used for the roll and paging area by the active users and their transactions is displayed. Try to clarify whether it is not the current program but another program that requires so much memory.


2-40


2. Use transaction DB11 to check in the current instance profile the parameters ’rdisp/ROLL_MAXFS’ and ’rdisp/PG_MAXFS’. The values stored there indicate the current block sizes for the roll or paging area (1=Block = 16 Kilobytes, 1 Kilo-byte = 1024 Bytes).

3. As far as the system is concerned, compare the size of the common partition for the roll and paging areas with the values from transaction DB11. If the converted values do not correspond to the size of the partition, the parameters ’rdisp/ROLL_MAXFS’ and ’rdisp/PG_MAXFS’ have to be adjusted to the provided partition.

4. Start your R/3 system again.

If the parameter was changed, the run has to be repeated after the data backup of the ViewPoint module has been reloaded.

In addition, we should like to draw your attention to SAP Note No. 14779, which provides more information regarding the error described above.

Loading of administration table /PBS/CMMB_FILE

If the option "Create administration indices" was not active during construction of the purchase requisition archive, these can be created separately at any time via the report /PBS/CMMBFILE or the menu path Archive > Purchase Requisitions > Activate index respectively.



The corresponding selection screen is shown in Figure 2-26, “Selection screen for construction of administration indices.”

Figure 2-26 Selection screen for construction of administration indices

Use last run If this radio button is active, the last run is automatically used for the creation of the indices.

Select run manually Especially in the implementation and test phase, it may be useful not to delete older load runs but to keep them for a while. You can activate an earlier run and construct the corresponding administration indices at any time via the parameter "Select run manually". Figure 2-26, “Selection screen for construction of administration indices,” shows a selection list as displayed after starting in the manual mode.

Figure 2-27 Selection list for construction of administration indices for certain load run


2-42


In this example, SAP run 014325 could be reactivated. SAP run 014331 is active as secondary archive and can no longer be used. All further parameters are connected with the creation of secondary archives and are explained in “Creation of secondary archives” on page 3-5.

After creation of the administration indices a protocol is displayed, as shown in Figure 2-28, “Protocol of creation of administration table.”

Figure 2-28 Protocol of creation of administration table

Activate main archive This parameter enables you to delete the current entries in the administration table without having to activate the indices for another load run at the same time.


Merge A ViewPoint module was created with the first load process, as described in “Initial load process” on page 2-23. If you now want to load additional documents into the already existing ViewPoint module, this procedure is carried out in a similar way as described previously - by way of a merge run.

/PBS/CMMBLDR3 When importing further SAP archive files, those SAP archive files that are merged with the existing ViewPoint module should be marked in the selection screen of the report /PBS/CMMBLDR3 in the delimitation 'Select Archives.' If an SAP archive file has already been



loaded into the ViewPoint module during a previous run, this is recognized by the report and a warning message is displayed. Identical documents cannot exist more than once in the ViewPoint module.

The load program /PBS/CMMBLDR3 should be started again as a batch process. A new ViewPoint archive is constructed from the existing add on and the access. Archives from previous runs are deleted automatically if the option "Delete previous run" is selected. However, ViewPoint purchase requisition archives from earlier runs can be deleted separately later on via the report /PBS/CMMBDELR.

If all load processes are finished, the administration table /PBS/CMMBFILE must be loaded into the SAP R/3 system with report /PBS/CMMBFILE. In case the button "Create administration indices" is set, this procedure is unnecessary.

Figure 2-29, “Selection statistic of /PBS/CMMBLDR3 after merge run,” shows a typical selection statistic after a merge run.

Time Statistic





Table Statistic

Number BANF read: 200

Number BANF processed: 200

Table Records read

EBANR 200

EBAN 200

EBKN 23

Index Written from stock


2-44


EBAN BANFN 1.580

EBAN BEDNR 1.580

EBKN KOSTL 27

Index Written total

EBAN BANFN 1.780

EBAN BEDNR 1.780

EBKN KOSTL 50

Index Written total

EBAN BANFN 1.780

EBAN BEDNR 1.780

EBKN KOSTL 50

Index Table Exported Tables

EBAN 4

EBKN 1

Statistic of Archived Objects

Archive file: 000872-001/PBS/CMMB Number of objects: 8

Size in MB: 0,172

Figure 2-29 Selection statistic of /PBS/CMMBLDR3 after merge run



Purchasing info records

Procedure In order to archive purchasing info records, the SAP archiving tool is first used to remove the data from the R/3 database. The tool is called via transaction SARA. The archiving is object oriented, MM_EINA being the archiving object for the purchasing info records. The SAP archiving program writes the archived data into sequential files outside the database.

The reorganized data can no longer be reloaded into the database and can only be evaluated sequentially. The reduced load that this results in for the R/3 database can be measured using the ViewPoint Database Analyzer.

The generated SAP archives are written into the ViewPoint MM Module using the ViewPoint load program /PBS/CMMILDR3. The load program reads the SAP archive files and creates several secondary indices. In contrast to the purchasing documents, they are not stored in a ViewPoint format but in the SAP-specific ADK format, the same as the purchasing info records themselves.

The physical directory or the files in which this data is stored, can be derived from the logical path that was assigned to archiving object /PBS/CMMI via transaction AOBJ. The archiving object is supplied with the logical standard path ARCHIVE_DATA_FILE, which is also used for archiving object MM_EINA. However, we recommend that you define a separate logical path for each ViewPoint archiving object in the archiving object customizing.

Having constructed the secondary indices, the archived purchasing info records are available for online processing and can be easily evaluated with the ViewPoint transactions. The functionality of the ViewPoint transactions is identical to the functionality of the SAP transactions. However, they can read and display not only the resident data in the R/3 database but also the archived data from the ViewPoint module.

As the data in the ViewPoint module can no longer be changed, a regular data backup of the archive is not necessary. The SAP archive file created during the next reorganization of the database can be added to the existing ViewPoint module via load program /PBS/CMMILDR3.

Purchasing info records 2-45

2-46


You can call the load program via ViewPoint menu /PBS/CMM or customer-specific menu, where the node archive of the ViewPoint menu can be established, as shown in Figure 2-30, “Starting the load program for archived R\3 purchasing info records.”

Figure 2-30 Starting the load program for archived R\3 purchasing info records

Load program /PBS/CMMILDR3

/PBS/CMMILDR3 The ViewPoint MM Module enables you to keep R/3 purchasing info records available for online processing. To do this, you use load program /PBS/CMMILDR3 to construct the ViewPoint MM Module



from the SAP archive files. The selection screen of load program /PBS/CMMILDR3.

In the following section, we explain the delimitations and their effects when loading the purchasing info records into the ViewPoint MM Module, as shown in Figure 2-31, “Selection screen of load program /PBS/CMMILDR3.”

� Select manually


� Delete old run

Figure 2-31 Selection screen of load program /PBS/CMMILDR3

Select SAP archive If the radio button 'Select manually' is active, a window is displayed when the request screen is confirmed, showing a list of the available SAP purchasing archives that were created on or after the specified date.

Now select those SAP MM archives MM_EINA that you want to load into your ViewPoint MM Module. In the automatic mode, all SAP purchasing archives that were created on or after the date specified


2-48


are selected, without the list being displayed. Purchasing info records from this period that have already been loaded into the ViewPoint archiving module are not selected.

Delete old run The parameter ’Delete old run’ deletes complete load runs from the ViewPoint MM Module. When you press the Run pushbutton, an overview of all previous runs is displayed, from which you can select the run to be deleted, as shown in Figure 2-32, “List of those SAP MM archives of purchasing info records loadable into MM.”

Figure 2-32 List of those SAP MM archives of purchasing info records loadable into MM

Figure 2-33 Overview of runs realized — run 9 selectable for deletion


Process all documents If this radio button is active, the selected SAP archives are loaded completely into the ViewPoint module. Loading the same SAP archive a second time is prevented by an internal safety mechanism.


Sequential interval In the case of very large SAP archives, it is sometimes advisable to break up the load run into several smaller parts. In this case, the radio



button ’Process sequential number interval’ must be active and the appropriate interval limits set.

Administration indices Setting this parameter results in the administration table /PBS/CMMII_FILE being updated after the actual load run has been completed. If you want to perform several load runs in succession, you should only set this parameter for the last run. If this parameter was not set, or if the entries in the administration table /PBS/CMMI_FILE were corrupted, you can construct the administration indices separately at any time later on using the report /PBS/CMMIFILE, or the menu path Archive > Purchasing info records > Activate index.

� Delete run

Delete Run Setting this parameter results in the data from the previous run being deleted automatically after successful completion of the current load run. In the implementation phase it is often advisable not to set this parameter and to keep the run for safety reasons. Older runs can be deleted separately later on using the report /PBS/CMMIDELR or via the menu path Archive > Purchasing info records > Additional Tools > Complete deletion of the generation runs.

Initial load process If all necessary information has been entered in the selection screen of load report /PBS/CMMILDR3, the selection screen can be saved as a selection variant for the initial construction of the online archive and the report can be started as a background process.

Note: The ViewPoint MM Module must be constructed separately per client.

During run time, the program generates the ViewPoint module of purchasing info records from the archive data.


2-50


After successful generation of the purchasing info record archive, program /PBS/CMMILDR3 displays an archive selection statistic, as shown in Figure 2-34, “Selection statistic of /PBS/CMMILDR3.”

Figure 2-34 Selection statistic of /PBS/CMMILDR3



Loading of administration table /PBS/CMMI_FILE

If the button "Create administration indices" was not active during construction of the purchasing info record archive, these indices can be created separately at any time via report /PBS/CMMIFILE or the menu path Archive > Purchasing Info Records > Activate index.

Figure 2-35, “Selection screen for construction of administration indices,” shows the selection screen for this procedure.


Use last run If this parameter is active, results in the last run automatically being used for the creation of the indices.

Select run manually Especially during the implementation and test phase it can be useful not to delete older load runs, but to keep them for a while. You can use the parameter "Select run" to activate an earlier run at any time and construct the corresponding administration indices. Figure 2-36, “Selection list for construction of administration indices of any load run,” shows a selection list displayed after starting in the manual mode.

Figure 2-36 Selection list for construction of administration indices of any load run


2-52


After the successful construction of the administration indices a protocol is displayed, as shown in Figure 2-37, “Construction protocol of an administration table.”

Figure 2-37 Construction protocol of an administration table

Delete indices This parameter enables you to delete the current indices without having to activate indices for another load run at the same time.


Merge With the first load process, a ViewPoint module was created, as described in “Initial load process” on page 2-38. If you now want to load additional documents into the already existing ViewPoint module stock, please proceed with a merge run as described previously.

/PBS/CMMILDR3 When importing additional SAP archive files you have to mark in the selection screen of report /PBS/CMMILDR3 in the delimitation option 'Select archives' those SAP archive files that you want to merge with the existing ViewPoint module. If an SAP archive files



has already been loaded into the ViewPoint module during a previous run, the report recognizes this and displays a warning message. It is not possible for identical documents to exist several times in the ViewPoint module.

Load program /PBS/CMMILDR3 should be started again as a batch process. A new ViewPoint archive is constructed from the existing add on and the new documents. Archives from earlier runs are automatically deleted if the radio button "Delete previous run" is active. ViewPoint purchasing info record archives from earlier runs can, however, also be deleted separately at a later data via report /PBS/CMMIDELR.

If all further load processes have been completed, administration table /PBS/CMMIFILE should be loaded, into the SAP R/3 system using report /PBS/CMMIFILE as described in “Loading of administration table /PBS/CMMB_FILE” on page 2-40.


2-54


This step is not necessary if you had activated the option "Create administration indices" during the last run. Figure 2-38, “Selection statistic of /PBS/CMMILDR3 after merge run,” shows a typical selection statistic after a merge run.

Figure 2-38 Selection statistic of /PBS/CMMILDR3 after merge run



Accounting documents

Procedure In order to archive accounting documents, the SAP archiving tool is first used to remove the data from the R/3 database. The tool is called up using the transaction SARA. The archiving is object-oriented. MM_REBEL is the archiving object for the accounting documents. The archived data is written into sequential files outside the database by the SAP archiving program.

The reorganized data can no longer be loaded back into the database and can only be evaluated sequentially. The reduced load that this results in for the R/3 database can be measured with the help of the ViewPoint Database Analyzer.

The generated SAP archives are written into the ViewPoint CMM Module using the ViewPoint load program /PBS/CMMRLDR3. The load program reads the SAP archive files and generates various secondary indices. In contrast to the purchasing documents, these are not stored in a ViewPoint-specific form, but instead, in an SAP-specific ADK format like the archived accounting documents themselves.

The physical directory and/or the files in which this data is located, results from the logical path that was assigned to the archiving object /PBS/CMMR using transaction AOBJ. The archiving object is delivered with the logical standard path ARCHIVE_DATA_FILE, which is also used for the original archiving object MM_REBEL. However, we recommend that you define a separate logical path for ViewPoint archiving objects in archiving object customizing.

After construction of the secondary indices, online processing options are available for the archived accounting documents and they can easily be evaluated using the ViewPoint transactions. The ViewPoint transactions correspond to the SAP transactions from a functional point of view, but can read and display both the resident data located in the R/3 database and also the archived data from the ViewPoint module.

Because the data that is located in the ViewPoint module can no longer be changed, a regular data backup of the archive is not necessary. The SAP archive file that is generated during the next reorganization of the database can be added to the existing ViewPoint archive module using the load program /PBS/CMMRLDR3. The call of the load program is effected via ViewPoint menu /PBS/CMM or

Accounting documents 2-55

2-56


customer-specific menu, where the node archive of the ViewPoint menu was integrated, as shown in Figure 2-39, “Starting load program for archived R/3 accounting documents.”

Figure 2-39 Starting load program for archived R/3 accounting documents

The load program /PBS/CMMRLDR3

/PBS/CMMRLDR3 The ViewPoint CMM Module enables you to keep accounting documents from R/3 available online. To do this, you construct the ViewPoint CMM Module from the SAP archive files using the load program /PBS/CMMRLDR3. The selection screen of the load



program /PBS/CMMRLDR3 with its delimitation options is illustrated in Figure 2-40, “Selection screen of load program /PBS/CMMRLDR3.”

Figure 2-40 Selection screen of load program /PBS/CMMRLDR3

In the following section we will explain the delimitation options and their effect when loading the account documents into the ViewPoint MM Module.

� Select manually


� Delete old run


2-58


Select SAP archive If the radio button ’Select manually’ is active, a dialog window is displayed when the request screen is confirmed, displaying a list of available SAP account documents that were created on or after the date that was specified, as shown in Figure 2-41, “Proposed List of SAP MM archives of account documents loadable into MM archive.”

Figure 2-41 Proposed List of SAP MM archives of account documents loadable into MM archive

Now select those SAP MM archives of MM_Rebel that you want to load into your ViewPoint CMM Module. In automatic mode, all SAP purchasing archives are selected that were created on or after the date that was specified here, without the list of all SAP purchasing archives being displayed. Account archives from this period that have already been loaded into the archive are not selected when doing this.

Delete old run The parameter 'Delete old run' enables you to remove complete load runs from the ViewPoint MM Module. When you press the Run pushbutton, an overview of all previous runs is displayed, in which you can then select the run that is to be deleted, as shown in Figure 2-42, “Overview of previous runs — run 3 selectable for deletion.”

Figure 2-42 Overview of previous runs — run 3 selectable for deletion


Process all documents If this radio button is active, all selected SAP archives are loaded completely into the ViewPoint module. Loading of the same SAP archive a second time is prevented by an internal safety mechanism.




Number interval In the case of very large SAP archives, you may want to break up the load run into several smaller parts. To do this, the radio button ’Process sequential number range’ must be active and the appropriate interval limit set.

Administration indices Setting this parameter results in the administration table /PBS/CMMR_FILE being updated after the actual load run has taken place. If you want to perform several load runs in succession, you should first set this parameter for the last run. If this parameter was not set, or if the entries in the administration table /PBS/CMMR_FILE were corrupted, you can construct the administration indices separately at any time using the report /PBS/CMMRFILE or the menu path Archive > Account documents > Admin. table.


Delete previous run Setting this parameter results in the data of the previous run being deleted automatically after the current run has completed successfully. During the implementation phase, it seems to be reasonable to not set this parameter, and to store the previous run as a safety precaution. Old runs can then be deleted separately later on using the report /PBS/CMMRDELR or via the menu path Archive > Account documents > Delete run.

First load run Once you have made all necessary entries in the selection screen of the load report /PBS/CMMRLDR3, the selection screen can be saved as a selection variant for the initial construction of the online archive, and the report can be started as a background process.

Note: The ViewPoint MM Module must be setup per client.

During runtime, the program generates the billing documents from the archive data of the ViewPoint module.

After the archive for the billing document records has been generated successfully, the program /PBS/CMMRLDR3 displays an archive


2-60


selection statistic, as shown in Figure 2-43, “Selection statistic of /PBS/CMMRLDR3.”

Figure 2-43 Selection statistic of /PBS/CMMRLDR3

Loading the administration table /PBS/CMMR_FILE

If the checkbox "Generate administration indices" was not active when the billing document archive was being constructed, these can be generated separately via the report /PBS/CMMRFILE or via the menu path Archive > Account documents > Activate index.



The selection screen for this transaction is illustrated Figure 2-44, “Selection screen for construction of administration indices.”


Use last run Setting this parameter results in the last run that was performed being used for generation of the indices.

Select run manually In the implementation and test phases it is sometimes advisable to not delete the former load runs, but instead to keep them. By using the parameter "Select run manually", you can reactivate an earlier run at any time and construct the corresponding administration indices. Figure 2-45, “Selection list for construction of administration indices for load run,” shows the selection list that is displayed after starting in manual mode.

Figure 2-45 Selection list for construction of administration indices for load run


2-62


After the administration indices have constructed successfully, a protocol is displayed, as shown in Figure 2-46, “Log for construction of administration table.”

Figure 2-46 Log for construction of administration table

Delete indices This parameter enables you to delete the current indices without having to activate indices belonging to another load run.

Further load runs

Merge A ViewPoint archive was generated with the first load run, as described in “Initial load process” on page 2-49. If further documents should now be loaded into the existing ViewPoint module content, this is done in a similar way as previously described - by way of a merge run.

/PBS/CMMRLDR3 When adding further SAP archive files, the files that are to be merged with the existing ViewPoint module have to be selected in the selection screen of the report /PBS/CMMRLDR3 in the delimitation 'Select archive.’ If an SAP archive file was already loaded in a previous run of the ViewPoint module, this is recognized by the



report and a warning message is displayed. Identical documents may not exist several times within the ViewPoint module.

The load program /PBS/CMMRLDR3 should be started again as a batch process. A new ViewPoint archive is constructed from the existing ViewPoint module and the access. Archives from previous runs are deleted automatically if the checkbox "Delete previous run" is active. ViewPoint purchasing info records from previous runs can, however, be deleted later on using the report /PBS/CMMRDELR. If all further load runs have been completed, the administration table /PBS/CMMRFILE should be loaded into the SAP R/3 System using report /PBS/CMMRFILE. This step can be omitted if the checkbox "Generate administration indices" was active during the last run.

Figure 2-47, “Selection statistic of /PBS/CMMRLDR3 after merge run,” shows a typical selection statistic after a merge run.

Figure 2-47 Selection statistic of /PBS/CMMRLDR3 after merge run


2-64


Disk space requirementsThe ViewPoint module for purchasing documents is constructed in database-independent file systems. The system administrator’s task here is to reserve free memory capacity for construction of the archive. A file path has to be created for the reserved disk space, which can be used by the ViewPoint archive programs. In addition, a read/write authorization on this file path restricted exclusively to the supplied ViewPoint programs is advisable.

The disk space capacity to be provided depends on the number of documents that are to be kept in the archive. For each purchase order (including secondary index) a capacity of about 500 bytes should be calculated.



Use of several application serversIn larger R/3 systems, the database and the R/3 applications normally run on different servers, known as the database server and the application server respectively. Often it is advisable to use several application servers for the performance reasons. However, as the ViewPoint module for purchasing documents is constructed in file systems independent of the database, all application servers must have direct access to these file systems. It is the system administrator’s task to organize the application servers in such a way that the file systems of the ViewPoint module can always be reached via the same path. Under Unix, NFS (Network File System) provides an elegant solution. The following example of a three-level R/3 client/server architecture illustrates how to proceed in this case. The system should consist of one database server and one application server (and several presentation servers), whereby the ViewPoint module is created on the database server. You should then proceed as follows:

The file systems containing the ViewPoint module must first be released on the database server using the command share. The following command (syntax of Sun/Solaris) releases, for example, the file system /pbs/cmm:

share -F nfs /pbs/cmm .

The released file systems can then be mounted on the file system of the application server. A precondition for this is that the directories used as mount point already exist. The following example of a command mounts the released file system /pbs/cmm of the database server sun20 at the mount point /archiv/cmm:

mount -F nfs sun20:/pbs/cmm /archiv/cmm .

Please keep in mind that in case of several application servers, the same mount point is used for each of them, as only one single path can be assigned to the ViewPoint module (in this case, for example, /archiv/cmm).

Note: The server containing the data of the ViewPoint module must also be an NFS server so that application servers can access the NFS server as NFS clients.

Use of several application servers 2-65

2-66


Under Windows NT - if NFS has not been installed - the local drive of the database server, where the ViewPoint module is contained, must be released. A more detailed explanation is provided later.


3Invisible Body Tag


� Introduction ........................................................................................3-2� Purchasing documents ......................................................................3-3� Purchase requisitions.........................................................................3-5� Invoice documents .............................................................................3-7

Long-Term Archiving

Long-Term Archiving 3-1

3-2

Long-Term Archiving

IntroductionWe recommend to make a new directory in which the data is loaded at regular intervals (e.g., for each calendar year) in order to prevent an extremely increase in data in the directory of the archive add on. On the one hand, when doing this you can reduce the run time of the load run, as the time which is needed for the merging of the indices depends on the amount of indices already available. On the other hand, parts of the archive can be stored on other media such as tapes. So you are able to reduce the disk space which is permanently needed. If the data is required again in the SAP system, you only have to reload the directory, to enter the path in the control table and to update a management table. In that way the information stored outside are available online again. Both the transactions and the customer programs adapted to the ViewPoint module take both data sources into account.


Long-Term Archiving

Purchasing documents

Access to data transferred into external storage

If data transferred into an external storage system should be available online again, in case it was transferred to other media such as a tape, it has to be reloaded in a directory on the hard disk. The name of the directory does not matter. Furthermore, the management table has to be filled for this directory via Archive > Purchasing documents > Additional tools > Long-term archive > Activate additional archive paths (program name /PBS/CMM_FILE_OT).

The following selection screen is displayed in Figure 3-1, “Activate removal of paths.”

Figure 3-1 Activate removal of paths

� Update path table for removal

Update path table forremoval

The menu option "Update path table" assigns path numbers for removed directories in a control table.

� Activate paths

Activate paths After pressing this button, you can select one or more files for removal, which can be set active in the displayed table. The entries selected will be activated after starting the program. "Active" means that the necessary management entries are loaded from the directories into a database table. After termination the directories are

Purchasing documents 3-3

3-4

Long-Term Archiving

available in the archive add on which have the status "active" in the path table. Using the archive tool /PBS/CMMESCAN and entering the path number manually, you can test if it was terminated successfully.

� Deactivate paths

Deactivate paths This button allows you to select one or more files for removal which should be deactivated in the displayed table (Only those paths can be selected which have an "x" in column "active"). The selected directories are deleted from the database table.

Note: Activate the corresponding button and select "activate" or "deactivate" before pressing the selection button.


Long-Term Archiving


Creation of secondary archives

If the run time is no longer bearable, e.g. it takes more than 10 hours, you can transfer the current active ViewPoint archive for purchase requisitions into a so-called secondary archive with program /PBS/CMMBFILE and start the construction of a new main archive in the next load run. Figure 3-2, “Selection screen for construction of management indices,” displays the structure of the selection screen.

Figure 3-2 Selection screen for construction of management indices

The current main archive and all active secondary archives are considered in the read accesses. As the ViewPoint archives for purchase requisitions are stored in the ADK format, you can transfer older secondary archives, which are no longer accessed very often, in an optical archive.

Transform intosecondary archive

If you select this parameter, the current main archive will be deactivated and at the same time activated as secondary archive.


3-6

Long-Term Archiving

Activate/deactivatesecondary archives

These two parameters enable you to activate or deactivate inactive ViewPoint archives for purchase requisitions as secondary archives. An overview on the available ViewPoint archives for purchase requisitions is displayed by pressing button "Select list". You can select ViewPoint archives which can be activated and those which are deactivated, as shown in Figure 3-3, “Selection list for activating secondary archives.”

Figure 3-3 Selection list for activating secondary archives


Long-Term Archiving

Invoice documents

Creation of secondary archives

If the runtime reached a certain extent (e.g., > 10 h), you can transform the now active ViewPoint archive for accounting documents into a so called secondary archive with the program /PBS/CMMRFILE and start the creation of the new main archive in the next load run. Figure 3-4, “Selection screen for creation of administration indices,” displays the creation of the selection screen.

Figure 3-4 Selection screen for creation of administration indices

The current main archive as well as all current secondary archives are always considered. As the ViewPoint archives for purchase requisitions are archived in the ADK format, you can transfer older secondary archives, that are not so often accessed, in an optical archive.

Transform tosecondary archives

Qualifying this parameter means the deactivation of the current main archive and activation as secondary archive at the same time.

Invoice documents 3-7

3-8

Long-Term Archiving

Activate/deactivatesecondary archives

These two parameters enable to activate or deactivate inactive ViewPoint archives for accounting documents as secondary archives. You receive an overview of the existing ViewPoint archives for invoice documents via button "Select list". Activatable or deactivatable ViewPoint archives are provided with a clickable checkbox, as shown in Figure 3-5, “Selection list for activation of secondary indices.”

Figure 3-5 Selection list for activation of secondary indices


AInvisible Body Tag

This appendix includes these topics:

� Purchasing documents .....................................................................A-2� Purchase requisitions........................................................................A-9� Purchasing info records..................................................................A-14� Invoice documents ..........................................................................A-18

Additional MMInformation

Additional MM Information A-1

A-2

Additional MM Information

Purchasing documents

Archive tools The program /PBS/CMMESCAN is available for displaying the ViewPoint CMM Module for archived purchase orders which can be called via the menu archive tool. Figure A-1, “Selection screen archive tool,”displays the selection screen of the /PBS/CMMESCAN.

Figure A-1 Selection screen archive tool

The statistics of the current and of all previous load runs can be displayed with button log tables in the selection screen /PBS/CMMESCAN. All documents for a specific index can be displayed in the ViewPoint archive.

Figure A-2, “Selection screen of /PBS/CMMESCAN,” displays the vendor number.

Figure A-2 Selection screen of /PBS/CMMESCAN



Figure A-3, “Display of vendors and number of appropriate documents,” displays the documents for a specific vendor number.

Figure A-3 Display of vendors and number of appropriate documents

Purchasing documents A-3

A-4


The tables archived for a document, as shown in Figure A-4, “Display of purchase orders for specific vendor,” can be displayed by a double click.

Figure A-4 Display of purchase orders for specific vendor



And their contents, as shown in Figure A-5, “Display of tables for specific document number,” can be displayed by a double click.

Figure A-5 Display of tables for specific document number


A-6


Figure A-6 Segment of table EKKO for archived purchasing document

Read from secondaryarchive

If the option "Read from secondary archive" is activated, a specific ViewPoint Module whose content should be displayed can be selected, as shown in Figure A-7, “Selection of ViewPoint Module.”

Figure A-7 Selection of ViewPoint Module



According to this selection, the selected secondary archive is displayed in the query screen, as shown in Figure A-8, “Selection screen after selecting first secondary archive.”

Figure A-8 Selection screen after selecting first secondary archive


A-8


Additional tools Under menu option ’Additional Tools’, as shown in Figure A-9, “Additional tools,” the following analyses are available in addition to the long-term archive.

Figure A-9 Additional tools

Purchase requisitionsreading example

In this menu option you will find report /PBS/CMMITEST, which is reading exemplarily the tables EINA and EINE via all available indices in archive add on CMM. We tried to structure the source code as good as possible; its study for possible proprietary developments in purchasing is helpful.

Fast display This menu option is reading only the ViewPoint indices and the fields within, without branching to the proper purchase requisitions in the SAP archive. A list is displayed, from where you can branch to the individual display. For search of a specific archived purchase requisition, where only the vendor is known, the utilization of this functionality is faster than the utilization of the standard list display.

Complete deletion ofgeneration runs

This menu option allows to delete completely active as well as inactive ViewPoint index archives for purchase requisitions. During the test phase the function can help to restore an initial status. The report should be used with caution in the productive area. In case a ViewPoint index archive was deleted by mistake (main archive or secondary archive), it must be created anew.




Archive tools For display of the ViewPoint MM Module of archived purchase requisitions the program /PBS/CMMBSCAN is available, which can be called via menu option, as shown in Figure A-10, “Menu option archive tools.”

Figure A-10 Menu option archive tools

Figure A-11, “Selection screen of archive tool for purchase requisitions — /PBS/CMMBSCAN,” displays the selection screen of /PBS/CMMBSCAN.

Figure A-11 Selection screen of archive tool for purchase requisitions — /PBS/CMMBSCAN

Purchase requisitions A-9

A-10


If the parameter Read from secondary archive is active, a secondary archive can be selected via the selection list (Figure A-12, “Selection screen of secondary archive /PBS/CMMBSCAN,”), thus only data of this secondary archive for purchase requisitions is displayed, as shown in Figure A-13, “Selection screen after selection of secondary archive 1.” If this parameter is inactive, only data from the main archive for purchase requisitions is displayed.

Figure A-12 Selection screen of secondary archive /PBS/CMMBSCAN

Figure A-13 Selection screen after selection of secondary archive 1



The statistics of the current and of all previous load runs can be displayed with the button log tables in the selection screen /PBS/CMMBSCAN. All purchase requisitions for a specific index can be displayed in the ViewPoint archive. Figure A-14, “Archive files for purchase requisition number index (PuReNo index),” displays the archive files for the Purchase requisition number index (PuReNo index) and Figure A-15, “Archive files for PuReNo index,” displays the list of the archived purchase requisitions of this archive file.

Figure A-14 Archive files for purchase requisition number index (PuReNo index)

Figure A-15 Archive files for PuReNo index


A-12


The archived purchase order tables, as shown in Figure A-16, “Archived Purchase Order tables,” and the respective table contents, as shown in Figure A-17, “Contents of table EBAN,” can be displayed via double-click.

Figure A-16 Archived Purchase Order tables

Figure A-17 Contents of table EBAN



Additional tools Under menu option ’Additional Tools’, as shown in Figure A-18, “Menu option additional tools,” the following analysis options are available.

Figure A-18 Menu option additional tools


In this menu option you will find report /PBS/CMMBTEST, which is reading exemplarily the tables EBANR, EBAN und EBKN via all available indices in archive add on CMM. We tried to structure the source code as good as possible, that it's study for possible proprietary developments in purchasing is helpful.

Fast display This menu option is reading only the ViewPoint indices and the fields within, without branching to the proper purchase requisition in the SAP archive. A list is displayed, from where you can branch to the individual display. Für search of a specific archived purchase requisition, where only the requisition note number is known, the utilization of this functionality is faster than the utilization of the standard list display.

Delete completelygeneration run



A-14


Purchasing info records

Archive tools The program /PBS/CMMISCAN which can be called by the menu option archive tool, as shown in Figure A-19, “Menu option archive tools,” provides the screen of the archived ViewPoint purchasing info records.


Figure A-20, “Selection screen of /PBS/CMMISCAN,” displays the selection screen of /PBS/CMMISCAN for purchasing info records.

Figure A-20 Selection screen of /PBS/CMMISCAN

The statistics of the current and of all previous load runs can be displayed with the button log tables in the selection screen /PBS/CMMISCAN.



All purchasing info records for a specific index can be displayed in the ViewPoint archive. Figure A-21, “Access archived Purchasing info records via vendor index,” displays archived records via the vendor index.

Figure A-21 Access archived Purchasing info records via vendor index

Figure A-22 List of vendor indices

Purchasing info records A-15

A-16


Figure A-23 Archived info record tables

The tables of an archived purchase info record, as shown in Figure A-23, “Archived info record tables,” and its contents, as shown in Figure A-24, “Segment of table EINE for change document of purchasing info record,” can be displayed via double click.

Figure A-24 Segment of table EINE for change document of purchasing info record



Additional tools Under menu option ’Additional Tools,’ as shown in Figure A-25, “Menu option additional tools,” the following analyses are available.



In this menu option you will find report /PBS/CMMITEST, which is reading exemplarily the tables EINA and EINE via all available indices in archive add on CMM. We tried to structure the source code as good as possible, that it's study for possible proprietary developments in purchasing is helpful.

Fast display This menu option is reading only the ViewPoint indices and the fields within, without branching to the proper purchase requisition in the SAP archive. A list is displayed, from where you can branch to the individual display. For search of a specific archived purchase requisition, where only the vendor is known, the utilization of this functionality is faster than the utilization of the standard list display.



Purchasing info records A-17

A-18


Invoice documents

Archive tools The program /PBS/CMMRSCAN which can be called via the menu option archive tool, as shown in Figure A-26, “Menu option archive tools,” is available for display of the ViewPoint MM Archive Module archived logistic invoice documents.


Figure A-27, “Selection screen after selection of secondary archive 1,” displays the selection screen of /PBS/CMMRSCAN for invoice documents.

Figure A-27 Selection screen after selection of secondary archive 1



If the parameter Read from secondary archive is active, a secondary archive can be selected via Selection list, as shown in Figure A-27, ”Selection screen after selection of secondary archive 1,” on page A-18. Only data of this secondary archive for invoice documents is displayed, as shown in Figure A-28, “Selection screen of secondary archive /PBS/CMMRSCAN.” If this parameter is not active, data from the main menu is displayed for invoice documents.

Figure A-28 Selection screen of secondary archive /PBS/CMMRSCAN

The statistics of the current and of all previous load runs can be displayed with the button log tables in the selection screen /PBS/CMMRSCAN. All invoice documents for a specific index can be displayed in the ViewPoint archive. Figure A-29, “Archive files for vendor index,” displays the archive files for the vendor index and displays invoice documents for a specific vendor number.

Figure A-29 Archive files for vendor index

Invoice documents A-19

A-20


Figure A-30 List of vendor indices

The archived accounting document tables, as shown in Figure A-31, “Tables for invoice document,” and the table contents, as shown in Figure A-32, ”Segment of contents of table RBKP of invoice document,” on page A-21 are displayed via double-click.

Figure A-31 Tables for invoice document



Figure A-32 Segment of contents of table RBKP of invoice document

Additional tools Under the menu option ’Additional Tools,’ as shown in Figure A-33, “Menu option additional tools,” the following analyses are available.


Invoice documentsreading example

In this menu option you will find report /PBS/CMMRTEST, which is reading exemplarily the tables RBKP and RSEG via all indices available in the archive add on CMM. We tried to structure the source code as good as possible, that it's study for possible proprietary developments in purchasing is helpful.

Invoice documents A-21

A-22


Fast display This menu option is reading only the ViewPoint indices and the fields within, without branching to the proper invoice documents in the SAP archive. A list is displayed, from where you can branch to the individual display. For search of a specific archived invoice document, where only the vendor is known, the utilization of this functionality is faster than the utilization of the standard list display.


This menu option allows to delete completely active as well as inactive ViewPoint index archives for invoice documents. During the test phase the function can help to restore an initial status. The report should be used with caution in the productive area. In case a ViewPoint index archive was deleted by mistake (main archive or secondary archive, it must be created anew.
