emc viewpoint for sap controlling line items module ... · pdf fileemc viewpoint for sap...

EMC ViewPoint for SAPControlling Line Items Module

Version 2.0

ADMINISTRATION MANUALP/N 300-002-924

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 CO Module Administration Manual

Contents

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

Chapter 1 Introducing ViewPoint for SAP CO ModuleIntroduction ...................................................................................... 1-2ViewPoint Controlling Line Items Module (CO) ........................ 1-3

CO basics.................................................................................... 1-3Hints for R/2 > R/3 migration ............................................... 1-4Supplied menus ........................................................................ 1-5

Chapter 2 CO ArchivingSAP data archiving .......................................................................... 2-2

The principle of CO line items archiving .............................. 2-2Preparing the archive ............................................................... 2-4Archiving of CO line items from the database ..................... 2-6

ViewPoint archiving with CO ........................................................ 2-9Initial load process.................................................................... 2-9Delete ViewPoint archives..................................................... 2-15Archive tool ............................................................................. 2-15Disk space and run times....................................................... 2-17Definition of the path ............................................................. 2-18Long term archiving concept ................................................ 2-18Summary of the archive setup .............................................. 2-20

Appendix A Additional CO InformationNaming convention ...................................................................... A-2Display variant in release 3.1 ...................................................... A-3Display transactions of CO .......................................................... A-6Integration of display transaction into user menus ................. A-8

EMC ViewPoint for SAP CO Module Administration Manual iii

Contents

ABAP/4 interfaces ......................................................................... A-9Archive access of the ViewPoint CO Module...................... A-9Adjustment of customer-specific programs/reports ......... A-9

Archive object/ViewPoint/CCOI ............................................. A-10Conversion of R/2 data from CCO/CCA archives ................ A-12

EMC ViewPoint for SAP CO 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 use the various components that make up EMC ViewPoint for SAP Controlling Line Items (CO) 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 using the ViewPoint for SAP CO 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 CO 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 CO 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 CO 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 Controlling Line Items Module (CO) ..........................1-3

Introducing ViewPointfor SAP CO Module

Introducing ViewPoint for SAP CO Module 1-1

1-2

Introducing ViewPoint for SAP CO 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 in the EMC ViewPoint for SAP Modules Installation Manual.

This administration manual was written to make construction and administration of the ViewPoint CO 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 has additional module information.



ViewPoint Controlling Line Items Module (CO)The EMC® ViewPoint Software Suite supplies the ViewPoint modules for the modules FI, SD, MM, and CO within a unified release strategy. This means for you, the ViewPoint customer, a facilitated management of the different ViewPoint module versions and an easier installation of updates and corrections. Each delivery contains a "Final Release" and, if necessary, a "Customer Patch" as described in the EMC ViewPoint for SAP Modules Installation Manual.

ViewPoint software has an own naming area from release 4.0. The objects described in this manual have names from this naming area exclusively. Customers using a SAP release 3.1 can find the objects of the ViewPoint naming area for release 3.1 in “Naming convention” on page A-2.

CO basics The ViewPoint CO Module is a package of ABAP/4 programs allowing the comfortable and quick display and evaluation of archived Controlling line items in the R/3 online system. All transactions displaying archived data are based on the SAP transactions. This guarantees that the users can work immediately with the archive transactions without special training. The ViewPoint CO Module supplied from SAP R/3 release 3.1H is the development of the ViewPoint CO Module/CA (for rel. 3.x), from version 2.0 disposing of a considerably extended functionality: Besides cost center line items, now all CO line items archived under the archiving object CO_ITEM (and all CO_line items archived with other archiving objects) can be transferred into and displayed in the ViewPoint archive. At present, these are the order line items, project line items as well as the CO line items for cost centers, business processes and sales documents. In addition to the actual line items, also the plan line items can be transferred into and displayed in the ViewPoint archive of the ViewPoint CO Module from release 4.0. Of course, the compatibility to the cost center line items archived with the archiving object CO_CCTR_EP remains.

With the help of the report/report interface you can call the ViewPoint line item reports from the different totals reports. Thus, you can display all line items belonging to a totals record from an extract, the database or the archive. In contrast to the original SAP line item reports, you can access during this process the line items from the database and the ViewPoint archive as described in the EMC ViewPoint for SAP Controlling Line Items Module User Manual.

ViewPoint Controlling Line Items Module (CO) 1-3

1-4


The ViewPoint CO Module administers the data transferred into the ViewPoint archive completely in the SAP ADK technique. This means: The secondary indices constructed for the ViewPoint archive, actually allowing the comfortable and quick access to the archived data, are created, stored and administered in analogy to the original SAP archiving technique. This function has improved handling and performance of construction and administration of the ViewPoint CO Module. The actual CO line items remain in the original SAP archive files. The ViewPoint index file of the ViewPoint archive contains a reference via which the line item you search for can be accessed immediately.

The precondition for the implementation of the ViewPoint CO Module is a correct SAP data archiving with transaction SARA. For the controlling line items the archiving objects CO_ITEM (controlling line items) and CO_CCTR_EP (only cost center line items) can be used.

For the implementation of the ViewPoint CO Module, EMC Professional Services recommends to archive the controlling line items using CO_ITEM.

Note: The archiving object CO_ITEM will be supplied by SAP only from release 4.0. To use the CO line item archiving also in the SAP release 3.1, first import the archiving object CO_ITEM. Please see the hints in the SAPNET (SAP Note Number 73152).

In Appendix A, “Additional CO Information,” we discuss the SAP archiving of CO line items and cost accounting objects which can be transferred after the archiving with transaction SARA into the archive of the ViewPoint CO Module. Refer to the SAP documentation on archiving.

Hints for R/2 > R/3 migration

To support the R/2 > R/3 migration of controlling line items (KOEP data of record types 'C' and 'O'), for the ViewPoint CO Module the ViewPoint Migration Object ZZKE is available. With the help of ZZKE, controlling line items archived under R/2 and KOEP data from the resident R/2 database can be migrated into a sequential R/3 archive file. This R/3 archive file is completely analogue to the archive files of archiving object CO_ITEM created under R/3 with transaction SARA. The R/3 archive files which are created during the migration therefore can easily be transferred into an archive of the ViewPoint CO Module.



The precondition for using the ViewPoint Migration Object ZZKE is the installation of the SAP migration tool DMIG. The DMIG Customizing for the data transfer of KOEP data (R/2 database => R/3 database) must be completed. This is used as reference for the ViewPoint Migration Object ZZKE.

Please see the separate documentation (part D) for further details on how to use the ViewPoint Migration Object ZZKE which is contained in the delivery of the ViewPoint CO Module.

Supplied menus Together with the ViewPoint module a global menu is supplied for all products and utilities of ViewPoint software and a menu especially for the CO module. This menu can be called up to release 4.5 via the transaction /PBS/PBS (or ZPBS in 3.1). All programs described in this manual and the user transactions are contained in the menu.

From release 4.6 the navigation has completely changed due to the implementation of the SAP Easy Access technique. This has also its effects on the transactions in the environment of the ViewPoint modules.

The delivery of the ViewPoint CO Module contains range menus /PBS/PBS (main menu of the ViewPoint modules) and /PBS/CCO (menu of the ViewPoint CO Module). From these menus, you have to generate now activity groups (4.6B) respectively roles (from 4.6C) which then can be integrated into the user master. You can also create an activity group/role directly from the Easy Access menu, as shown in Figure 1-1, “SAP Easy Access menu.”

Figure 1-1 SAP Easy Access menu

You are free to choose the name of the activity group/role; the name can also be within the ViewPoint naming area. A ViewPoint range menu is then transferred by pressing the function key 'Transfer menus from range menus' by indicating the corresponding ViewPoint menu name. During the transfer, the system query for the resolution of the range menu is to be answered with 'yes'.

ViewPoint Controlling Line Items Module (CO) 1-5

1-6


The role/activity group created this way can now be integrated in the corresponding user master. We recommend to allocate global activity group/role /PBS/PBS to the administrators and the special function menu /PBS/CPP to the final users, as shown in Figure 1-2, “SAP Special Function menu.”

Figure 1-2 SAP Special Function menu

Please see the current SAP standard documentation for more details on the creation of activity groups/roles.


2Invisible Body Tag

This chapter includes these topics:

� SAP data archiving ............................................................................2-2� ViewPoint archiving with CO ..........................................................2-9

CO Archiving

CO Archiving 2-1

2-2

CO Archiving

SAP data archiving

The principle of CO line items archiving

For the archiving of CO line items from the SAP database the archiving objects CO_ITEM (Controlling line items) and CO_CCTR_EP (cost center line items) are used. Archiving via CO_CCTR_EP is object-oriented (including the corresponding totals records) while CO_ITEM archives cross-object all CO line items (without totals records) and deletes them in the database.

In principle, CO line items can also be archived (and deleted) by other (object oriented) archive objects like CO_COSTCTR, PP_ORDER, etc. The load program of the ViewPoint CO Module can extract CO line items which have been archived by such an object from the corresponding sequential archive files.

The SAP archiving program writes the CO line items to sequential files which can be accessed within the SAP file system. From release 4.0B these archive files can also be transferred into an external storage system (optical archive systems, HSM systems) via SAP ArchiveLink. For a later use of these archive files with the ViewPoint CO Module, these archive files need to be accessible via ArchiveLink (In the archive administration you can recognize the status "accessible via ArchiveLink" from a special flag).

When using the archiving object CO_ITEM with the present version of the ViewPoint CO Module you can use the archived CO line items of the following object types:

� ORD (orders)

� BPR (business process)

� CTR (cost centers)

� COB (cost object)

� NTW (network)

� WBS (WBS element)

� SDI (sales document item)

There are further object types besides the above mentioned ones, such as the object "Reconciliation object" (REO, AO). These object types are not processed by the ViewPoint display transactions. However, an index is constructed for these object types by the ViewPoint load program. To avoid that, we recommend to archive


CO Archiving

these objects separately with the archiving object CO_ITEM and do not process the archive runs with the ViewPoint load program.

When the setup of the ViewPoint archive has been completed, the CO line items can be displayed with the transactions of the ViewPoint CO Module as described in “ViewPoint archiving with CO” on page 2-9.

In the following we give a brief outline of the most important topics of CO line item archiving. Refer to the corresponding SAP documentations before you archive and delete CO line items from your database! Keep in mind that you cannot reload archived CO line items. They can only be evaluated sequentially with the SAP transactions.

In principle (see above) the ViewPoint CO Module can process CO line items from different SAP archiving objects. For the archiving of mass data EMC Professional Services recommends to use archiving object CO_ITEM. The compatibility of the ViewPoint CO Module with archiving object CO_CCTR_EP especially serves the integration of data which has been archived under previous SAP R/3 releases (3.x).

SAP data archiving 2-3

2-4

CO Archiving

Preparing the archive

Having started transaction SARA you can enter the archiving object name (here CO_ITEM or CO_CCTR_EP) you want to use for the data archiving from the database. Depending on the archiving object, partly different push buttons appear, as shown inFigure 2-1, “SARA initial screen for archiving object CO_ITEM.”

Figure 2-1 SARA initial screen for archiving object CO_ITEM


CO Archiving

By clicking on the button ’Customizing’, you can check and, if necessary, change the definitions which are entered as standard, as shown in Figure 2-2, “Selection screen for customizing options (CO_ITEM).”

Figure 2-2 Selection screen for customizing options (CO_ITEM)

In general, you do not need to change any archiving object specific customizing. However, the standard values should be checked. Normally, you also do not need to change the basis customizing.

For archiving object CO_ITEM, you only need to carry out application-specific adjustments: You need to update the residence time of the CO line items in the database via the corresponding menu point (see above). For the update of the residence times you can also use transaction SM30, table ARCU_COIT1.

The residence time which you have to define for each object type determines the minimum number of posting periods a CO line item has to remain in the database before it can be archived. When using the ViewPoint CO Module, this value can be very small, in theory even zero as the archived line items can be displayed/evaluated any time via the ViewPoint transactions.


2-6

CO Archiving

Please agree the value to be entered with your user department, as shown in Figure 2-3, “Entry of residence periods.”

Figure 2-3 Entry of residence periods

Archiving of CO line items from the database

Having completed (respectively checked) the customizing definitions, you can start the archiving of CO line items from the database. The archiving program should be started as background job via a selection variant which is updated by pressing the button Archiving under Actions of the entry dynpro of transaction SARA.

Using the archiving object CO_ITEM, you can archive those object types whose residence time and block size have been updated in the user-specific Customizing as shown in Figure 2-3, “Entry of residence periods,”. Keep in mind that with the ViewPoint CO Module (at present) the object types 'ORD' (orders), 'BPR' (business process), 'CTR' (cost centers), 'COB' (cost object), 'NTW' (network), 'WBS' (WBS element) and 'SDI' (sales document item) are processed. As the ViewPoint load program creates an index for all object types, we recommend to archive all further object types (e.g., the object reconciliation object (ABS; AO)) in separate archive runs.


CO Archiving

Within the ’Processing’ frame you can select the following processes via ’radio button’: only a test run for archiving, the archiving of CO line items (start deletion separately at a later time), or archiving and deletion. Please see the example variant for the archiving of CO line items with CO_ITEM in Figure 2-4, “Selection variant for the archiving with CO_ITEM.” Activate the function "Log per document" only in the test mode for a reasonable data volume.

Figure 2-4 Selection variant for the archiving with CO_ITEM

The procedure for the archiving of cost center line items using archiving object CO_CCTR_EP works principally the same way.


2-8

CO Archiving

By clicking on the button Management in the initial dynpro of transaction SARA an overview of the archive runs carried out and the corresponding SAP archive files can be displayed, as shown in Figure 2-5, “SAP archive administration: Archiving session overview.”

Figure 2-5 SAP archive administration: Archiving session overview


CO Archiving

ViewPoint archiving with COThe archive files of the ViewPoint CO Module are created by transaction /PBS/COIL. In this process, only the index data which refer to the complete data record in the original SAP archive files is stored in the ViewPoint-specific files. This avoids to keep redundant data and guarantees a quick setup of the ViewPoint archive. Furthermore, this offers the possibility to remove these SAP archive files into an optical archive (or HSM system) outside the SAP system via SAP ArchiveLink. Nevertheless, online data access is still possible via the ViewPoint CO Module.

The ViewPoint load program generates all necessary indices for the archived CO line items of the SAP archive file. Additionally, the location of the line item in the SAP archive file is stored in the ViewPoint index. This ViewPoint index data is not stored in the R/3 database but in a sequential file on magnetic disk in the SAP file system using the ADK (Archive Development Kit) technique of SAP AG. For this purpose, the ViewPoint load program uses the ViewPoint specific archiving object /PBS/CCOI, as shown in Figure 2-6, “Principle of the archive setup with CO.”

Figure 2-6 Principle of the archive setup with CO

Initial load process To start the archive setup process you start the load program via the CCOI main menu: Archive > Load archive (or start via transaction code /PBS/COIL).

Before starting the program or storing the selection variant, several delimitations have to be made. They are important for the setup and performance of the ViewPoint CCO Module. This is explained in

ViewPoint archiving with CO 2-9

2-10

CO Archiving

detail below. The selection screen is shown in Figure 2-6, “Principle of the archive setup with CO.”

Select archiving object: With this parameter you select the SAP archiving object whose archive files are to be processed. Archiving object CO_ITEM, recommended by ViewPoint, is entered as default selection.

Note: The archiving object CO_ITEM is supplied by SAP only from release 4.0. To use the CO line item archiving also in the SAP release 3.1, first import the archiving object CO_ITEM. Please see the hints in the SAPNET (SAP Note Number 73152). Select automatically: In the automatic mode, without displaying a list before, all available SAP archive files which have been created from the indicated date are selected. SAP archive files already processed in previous runs of the ViewPoint CO Module are not loaded again.

Select manually: If this button is active, a popup window is opened when clicking on the button SAP archives. In this window a list of the available SAP archives created from the indicated date is displayed as shown in Figure 2-7, “Selection screen of the load program.”

Figure 2-7 Selection screen of the load program


CO Archiving

Please select the SAP archive of archiving object CO_ITEM respectively a certain SAP archive file for which you want to generate the indices with the ViewPoint CO Module. Loading the same SAP archive several times is prevented by internal security mechanisms, as shown in Figure 2-8, “Archive selection for archiving object CO_ITEM.”

Figure 2-8 Archive selection for archiving object CO_ITEM

Process all line items: If this selection is active, the selected SAP archives are loaded completely into the ViewPoint CO Module.

Process sequential interval: In case of huge SAP archive runs it may be necessary to split the load run into several portions. In this case, the select button 'Process sequential number interval' needs to be activated and corresponding interval delimitations have to be qualified: Please select the number of CO line items, which shall be loaded into the ViewPoint archive in the present run. In case the delimitations of the first run are from '1' to 'n', the second run must begin with 'n+1'. If you perform several runs with the load program, a certain load run always has to start with the CO line item following the last CO line item of the previous run! The total number of CO line items belonging to a specific SAP archive file can be determined from the log file of the SAP archive run.

After successfully creating the ViewPoint archive for the archived CO line items, transaction /PBS/COIL exports an archive selection statistic as protocol.


2-12

CO Archiving

Note: The archive construction of the ViewPoint CO Module must be carried out for each client separately. After finishing the ViewPoint archive setup, you should backup all newly created ViewPoint archive files.

If you want to separate the ViewPoint archive files from the SAP archive files, you can use transaction ’FILE’ to change the path name for the ViewPoint archive data of archiving object /PBS/CCOI. You can also use the ’Customizing’ button for the ViewPoint archiving object /PBS/CCOI in the initial dynpro of transaction SARA to reach the maintenance of path and file names for the ViewPoint archive index.

Complete theadministration table

After the load program has been finished, the key entries of the ViewPoint archive data cluster have to be copied to an administration table so that the data can be accessed from the online mode. This is a kind of table of contents for the archive data. This administration data is stored in database table /PBS/ARCH_IDX. The space required in the database is only about 0.5% of the space of the archive file on the magnetic disk.

These index entries are generated by transaction /PBS/COIA. Start this program via the ABAP Workbench (SE38) or from the CO main menu:

ViewPoint CO Archive Module > Archive > Activate Archive.

After starting the program, a selection list appears showing the successfully completed archive runs of the ViewPoint CO Module which have not been entered yet in table /PBS/ARCH_IDX. Now you can select the archive runs you want to access again from the SAP online system.


CO Archiving

After the program run, the entries made in table /PBS/ARCH_IDX are displayed in a protocol list as shown in, as shown inFigure 2-9, “Entries in administration table /PBS/ARCH_IDX.”

Figure 2-9 Entries in administration table /PBS/ARCH_IDX


2-14

CO Archiving

Archive management Finally, you can check the created ViewPoint archive files via the CO menu point: Archive > Manage archive. If all steps mentioned before have been carried out correctly, the status displays (’lights’) should all be green as shown in Figure 2-10, “Administration information on the ViewPoint archive files.”.

Figure 2-10 Administration information on the ViewPoint archive files

You can now access the data of the ViewPoint CO Module via the ViewPoint online transactions (and example utilities)

Further loadprocesses

When loading SAP archive runs into the archive of the ViewPoint CO Module, the ViewPoint data of the current run is no longer merged to the data of the previous archive runs. Due to the secondary indices used by ViewPoint a sufficient performance is guaranteed during the online access to the archive data. This technique enables an improved run time when setting up the archive of the ViewPoint CCO Module. Thus, the archive setup of additional runs of the ViewPoint CCO


CO Archiving

Module is completely identical to the initial run as described in “Initial load process” on page 2-9.

Delete ViewPoint archives

If necessary, the ViewPoint archives of the ViewPoint CO Module created with the load program can be deleted again. During this process, transaction /PBS/COID removes the files of the ViewPoint archives and correlated entries from database tables ADMI_RUN, ADMI_FILES and /PBS/ARCH_IDX.

For the deletion of an ViewPoint archive run please start program /PBS/COID from the menu:

ViewPoint CCO Archive Module > Archive > Delete archive

The ViewPoint archive run to be deleted is selected from a list (multiple selection possible). The result of the deletion process is then shown in a list protocol, as shown in Figure 2-11, “Protocol for the deletion of a ViewPoint archive run.”

Figure 2-11 Protocol for the deletion of a ViewPoint archive run

Archive tool A useful tool for the control or administration of the ViewPoint CO Module is the "Archive tool". This program allows a (technical) view into the data archived with the ViewPoint CO Module. You can display the contents of the secondary indices, the references to the CO line items themselves as well as the administration information of the


2-16

CO Archiving

ViewPoint CO Module. In a basic list, the header entries of the ’ViewPoint data cluster’ used for the storage and - by selecting different header entries, the corresponding detailed information are displayed. The load protocols of all ViewPoint archive runs of the load program can be displayed via select option ’Document statistics’. Start the archive tool from the CO main menu: CCO > Archive > Archive tool (display).

The archive tool can be started directly via transaction code /PBS/COIS. To select the requested data quantity in an easily comprehensible way, you can limit the maximum number of data clusters to be displayed or enter (a part of) the ViewPoint key field on the selection screen as shown in Figure 2-12, “Delimitations of the archive tool.”

Figure 2-12 Delimitations of the archive tool

The following example shows the access to ViewPoint data cluster containing cost center line items. In addition to the selection delimitations mentioned before, the basic list and the detailed display


CO Archiving

are shown in Figure 2-13, “Selection screen — basic and detailed list of archive tool for CO with key field.”

Figure 2-13 Selection screen — basic and detailed list of archive tool for CO with key field

Originally, the archive tool was developed for ViewPoint-internal service and problem support. Due to its technical function, it has become an efficient tool for the experienced basis administrator.

Disk space and run times

The ViewPoint CO Module is constructed in sequential files (flat files) in file systems independent of the R/3 database as described in “Archive tool” on page 2-15. It is now the system administrator's task to reserve free disk space for the flat files of the secondary indices of the ViewPoint archive.

The necessary disk space depends on the amount of CO line items to be transferred into the ViewPoint archive. For each CO line item you should calculate a capacity of about 30 to 50 bytes.

Performance and run time during the construction of the secondary indices of the ViewPoint CO Module strongly depend on the efficiency of your system and the data volume to be processed. For


2-18

CO Archiving

example: To generate the secondary indices of the ViewPoint archive for 100.000 CO line items, a run time of less than 5 minutes is required on two 300 MHz CPUs.

Definition of the path

Archiving objects The ViewPoint CO Module contains a load program that is assigned to an archiving object. Logical data paths are assigned to each archiving object via the SAP customizing. These logical data paths represent a physical data path.

The ViewPoint CO Module contains the following archiving object:

4.6C: /PBS/CCOI ViewPoint CO Module

Maintenance viatransaction SARA

The Customizing settings of the ViewPoint archive objects can be modified via the transaction SARA:

> SARA > Customizing > Technical Settings

Long term archiving concept

For many users it is important, for example, for fiscal reasons, to keep the CO line items archived in the ViewPoint CO Module available in the online mode for a long period of time (for example, for more than five years). If additionally the data volume is very large, the complete data volume archived in the ViewPoint CO Module can increase so much that a good performance of the online accesses to the ViewPoint archive is no longer possible, even in the case of an efficient system.

To reduce the data volume which is accessed in the online operation, the user may wish to occasionally "switch off" one or more archive runs of the ViewPoint CO Module from online access, without deleting the actual ViewPoint archives. As the indices of the different archive runs are not merged in the ViewPoint CO Module, this wish can be easily fulfilled by the utilities of the ViewPoint CO Module: Only the entries in the administration table referring to a certain ViewPoint archive run of the ViewPoint CO Module have to be deleted to exclude this specific archive run from online access. This process can easily be reversed again: you only have to add the entries of the administration tables for the (existing) ViewPoint archive runs again.

As long as the "switched off" ViewPoint archive runs (ViewPoint indices and original SAP archive files) are not used, they can be


CO Archiving

archived on any medium. The easiest way is to transfer them into an optical archive or a HSM system via SAP ArchiveLink. If needed again, they can be easily reloaded from such systems.

To switch off certain ViewPoint archive runs, you proceed as follows:

Start menu option: Archive > Deactivate Archive from the main menu /PBS/CCOI

Select those ViewPoint archive runs of the ViewPoint CO Module that you want to exclude from online access from option "File list". Before carrying out this step, we recommend to use the archive tool (display) of CCO and write down the corresponding SAP archive files from the run protocols, in case you want to transfer the SAP archive files and the ViewPoint indices of the ViewPoint CO Module to a separate storage medium afterwards. Now start the program with your selection, a shown in Figure 2-14, “Selection screen to deactivate ViewPoint archive runs.”

Figure 2-14 Selection screen to deactivate ViewPoint archive runs

To enable online access to the ViewPoint archive runs of CO, which have been "switched off" again, simply start program "Complete Admin.Table" from the ViewPoint Archive menu of the ViewPoint CO Module. Before doing this, you only have to ensure that the ViewPoint index file and the corresponding SAP archive file have been transferred into the original file directory again.


2-20

CO Archiving

Summary of the archive setup

Below the most important steps of the archive construction of the ViewPoint CO Module are summarized:

� SAP archiving: preparation, customizing, realization: A correct SAP archiving must be carried out for the CO line items to be transferred into the archive of the ViewPoint CO Module.

� Preparation of the ViewPoint CO Module: Reserve sufficient disk space in the file system. Option: Define a special file directory for the integration of the ViewPoint archive data (secondary indices) via customizing functions.

� Setup of the ViewPoint archive (secondary indices) of the ViewPoint CO Module for the required SAP archive files with ViewPoint load program (CCO menu: Archive > Load archive)

� After all load runs have been finished: complete administration table /PBS/ARCH_IDX. (CCO menu: Archive > Activate archive)

� Use the archive tool to check the CO line items transferred into the ViewPoint CO Module (CCO menu: Archive > Archive tool)

The archive construction of the ViewPoint CO Module is finished. The user can now access the data for display and evaluation in the ONLINE operation.


AInvisible Body Tag

This appendix includes these topics:

� Naming convention ..........................................................................A-2� Display variant in release 3.1 ..........................................................A-3� Display transactions of CO..............................................................A-6� Integration of display transaction into user menus .....................A-8� ABAP/4 interfaces ............................................................................A-9� Archive object/ViewPoint/CCOI.................................................A-10� Conversion of R/2 data from CCO/CCA archives ...................A-12

Additional COInformation

Additional CO Information A-1

A-2

Additional CO Information

Naming conventionAs described at the beginning, all objects in this manual have names from the ViewPoint naming area. In Table A-1, “ViewPoint object naming,” the objects of the ViewPoint naming area are confronted with the objects for the release 3.1.

Table A-1 ViewPoint object naming

Object Release 3.1 Release 4.x Description

Arch.object ZZCCOI /PBS/CCOI Archiving object CO

Menu ZPBS /PBS/MAIN Menu of the ViewPoint modules

Menu YPBS /PBS/PBS Button to start the ViewPoint menu

Menu ZZCI /PBS/CCOI Menu of the ViewPoint CO Module

Transaction ZCIL /PBS/COIL Load archive

Transaction ZCIA /PBS/COIA Activate archive

Transaction ZCIS /PBS/COIS Archive tool

Transaction ZCIB /PBS/COIB Deactivate archive

Transaction ZCID /PBS/COID Delete archive

Transaction ZCIM /PBS/COIM Manage archive

Transaction YCON /PBS/UTIL_CONVERT Conversion tool



Display variant in release 3.1The ViewPoint display transactions in the SAP release 3.1 can use all display variants of the SAP display transactions to display selected data. To use the variants for the first time, they have to be generated for the ViewPoint display transactions. This is carried out automatically when starting the variant with the ViewPoint display transaction. The ViewPoint display transaction has to be started again after the defined cancellation.

Besides, it is possible to generate all display variants together. Start the ViewPoint display variant maintenance program to which you want to generate the display variants: CCO main menu (ZZCI), menu point "environment", as shown in Figure A-1, “Update display variants for ViewPoint transactions.”

Figure A-1 Update display variants for ViewPoint transactions

To generate the display variants, e.g., the transaction YSB1, you proceed as follows: Start the list variant maintenance for YSB1. Now select in the following menu the menu point environment > generation. Mark all display variants you want in the displayed list and save the selection.

Display variant in release 3.1 A-3

A-4


The display variants are now generated, as shown in Figure A-2, “Generate display variants for ViewPoint transactions.”

Figure A-2 Generate display variants for ViewPoint transactions

The creation and modification of display variants is also done via the ViewPoint display variant maintenance program. How you can add the ViewPoint archive indicator to a display variant is described in the following. Start the corresponding maintenance transaction as described above. In the following dynpro press the button display variants and then select a display variant.



Now you can enter the field PBS_STAR (designation: archive) in any digit of the variant you want. Finally save and generate the display variant, as shown in Figure A-3, “Enter ViewPoint archive indicator.”

Figure A-3 Enter ViewPoint archive indicator

Display variant in release 3.1 A-5

A-6


Display transactions of COFrom version 2.1 of the ViewPoint CO Module, the display transactions shown below are available. The ViewPoint transactions can display and evaluate CO line items from operative tables of the SAP database as well as archived documents via the ViewPoint CO Module. For your convenience, we listed the ViewPoint transaction codes together with the corresponding SAP transactions. The EMC ViewPoint for SAP Controlling Line Items Module User Manual describes the application programs and transactions listed in Table A-2, “ViewPoint CO 3.1 transactions,” and Table A-3, “ViewPoint CO 4.0, 4.5, and 4.6 transactions.”

Table A-2 ViewPoint CO 3.1 transactions

ViewPoint 3.1 SAP Transaction description

YB13 KB13 Display of reposting of primary costs

YB23 KB23 Display allocation of activities

YB33 KB33 Display statistical operating figures

YB43 KB43 Display reposting of revenues

YB53 KB53 Display entry of activities

YB63 KB63 Display reposting of CO line items

YALR KALR Reconciliation ledger: CO line items

YSB1 KSB1 Cost centers: Actual line items

YOB1 KOB1 Order: Actual line items

YJ74 CJ74 Projects: Actual line items

YPB1 CPB1 Business processes line item actual

YKCS KKCS Cost object line item actual

YSB5 KSB5 Cost accounting documents actual costs



Table A-3 ViewPoint CO 4.0, 4.5, and 4.6 transactions

ViewPoint 4.0, 4.5 From ViewPoint 4.6 SAP Transaction description

/PBS/KB13 /PBS/KB13N KB13, KB13N Display reposting of primary costs

/PBS/KB43 /PBS/KB43N KB43, KB43N Display reposting of revenues

/PBS/KB63 /PBS/KB63 KB63 Display reposting of CO line items

/PBS/KB66 KB66 Display indir. acty. allocation reposting

/PBS/KB16N KB16N Display manual allocation

/PBS/KB23 /PBS/KB23N KB23, KB23N Display direct activity allocation

/PBS/KB53 /PBS/KB53N KB53, KB53N Display posting of activities

/PBS/KB33 /PBS/KB33N KB33, KB33N Display statistical key figures

/PBS/KALR /PBS/KALR KALR Reconciliation ledger: CO line items

/PBS/KSB1 /PBS/KSB1 KSB1 Cost centers: Actual line items

/PBS/KSBP /PBS/KSBP KSBP Cost centers: Plan line items

/PBS/KOB1 /PBS/KOB1 KOB1 Orders: Actual line items

/PBS/KOBP /PBS/KOBP KOBP Orders: Plan line items

/PBS/CJI3 /PBS/CJI3 CJI3 Projects: Actual items

/PBS/CJI4 /PBS/CJI4 CJI4 Projects: Plan line items

/PBS/CPB1 /PBS/CPB1 CPB1 Business processes: Actual line items

/PBS/CPBP /PBS/CPBP CPBP Business processes: Plan line items

/PBS/KKCS /PBS/KKCS KKCS Cost object: Actual line items

/PBS/KKCP /PBS/KKCP KKCP Cost object: Plan line items

/PBS/KVBI /PBS/KVBI KVBI Sales documents: line items actual

/PBS/KSB5 /PBS/KSB5 KSB5 Controlling documents: Actual costs

/PBS/KABP /PBS/KABP KABP Controlling documents: Plan costs

Display transactions of CO A-7

A-8


Integration of display transaction into user menusThe ViewPoint transactions of the ViewPoint CO Module can be called via the ViewPoint transaction code or can be integrated into the corresponding SAP menus, e.g., KSMN (cost center accounting):

Tools > ABAP Workbench > Development > Other tools > Area menus > Menu KSMN (corresponds to transaction SE43).

If you do not want to modify the standard menus, the area menu can also be copied under another name, for example, beginning with ’Z’.

ViewPoint area menus (from SAP release 4.6: activity menus) are not only available for the ViewPoint modules in general (/PBS/MAIN) but also for the ViewPoint CO Module (/PBS/CCOI).



ABAP/4 interfaces

Archive access of the ViewPoint CO Module

All access routines to the ViewPoint archive indices of the ViewPoint CO Module are contained in ABAP/4 program /PBS/CCOIREAD. Please see the utilities of the ViewPoint CO Module, e.g., /PBS/CCOIU00x, x = 1 to 6. to see, how these routines can be used as described in “Display variant in release 3.1” on page A-3.

Adjustment of customer-specific programs/reports

To adjust customer-specific programs and reports to the archive accesses of the ViewPoint modules, ViewPoint offers support via a special conversion utility: Program /PBS/UTIL_CONVERT automatically adds the necessary access routines to the ABAP/4 programs, in order to display and evaluate archived data which has been transferred into an archive of a ViewPoint module. For this purpose, the ViewPoint archive accesses are added to the "SELECT" commands of the programs. You can also start this conversion utility from the main menu of the ViewPoint module as shown in Figure A-4, “Result protocol of the conversion utility.”

Figure A-4 Result protocol of the conversion utility

ViewPoint main menu (/PBS/MAIN) > Utilities > General tools > Conversion select statement

The functionality of the ViewPoint conversion tools has recently been improved and extended. The new version comes with a separate manual which explains the properties and usability of the ViewPoint conversion tool in detail.

ABAP/4 interfaces A-9

A-10


Archive object/ViewPoint/CCOITo store the index data of the ViewPoint CO Module an own archiving object was created with ADK (Archive Development Kit) means. Normally, these archiving objects remove data from the SAP database during an archiving respectively deletion run. The archive indices necessary for the quick access to the CO line items stored in the SAP archive files are now created with the help of archiving object /PBS/CCOI of the ViewPoint CO Module. Of course, a deletion run and a reloading of the data is not useful for this object; therefore the program does not contain such a function. The different data structures belonging to archiving object /PBS/CCOI are summarized in Figure A-5, “Table of the data structures of object ZZCCOI,” and Figure A-6, ”Table of the data structures of object /PBS/CCOI,” on page A-11.

Table V_ARC_DEF Date 07.01.01 Object ZZCCOI

Rec. Father seg. Segment Description0010 ZZCI_IK ViewPoint CCO Module Index Head0020 ZZCI_IK ZZCI_ITEM PBS Index CO_ITEM (Shrt text + Object)0030 ZZCI_IK ZZCI_BK PBS Index COBK (key)0040 ZZCI_IK ZZCI_BK_O PBS Index COBK (original document)0050 ZZCI_IK ZZCI_EJ PBS Index COEJ (key)0060 ZZCI_IK ZZCI_EJ_1 PBS Index COEJ (totals database)0070 ZZCI_IK ZZCI_EJL PBS Index COEJL (key)0080 ZZCI_IK ZZCI_EJL_1 PBS Index COEJL (totals database)0090 ZZCI_IK ZZCI_EJR PBS Index COEJR (key)0095 ZZCI_IK ZZCI_EJR_1 PBS Index COEJR (totals database)0100 ZZCI_IK ZZCI_EJT PBS Index COEJT (key)0105 ZZCI_IK ZZCI_EJT_1 PBS Index COEJT (totals database)0110 ZZCI_IK ZZCI_EP PBS Index COEP (key)0120 ZZCI_IK ZZCI_EP_1 PBS Index COEP (totals database)0125 ZZCI_IK ZZCI_EP_2 PBS Index COEP (cost type)0130 ZZCI_IK ZZCI_EPB PBS Index COEPB (key)0140 ZZCI_IK ZZCI_EPB_1 PBS Index COEPB (totals database)0150 ZZCI_IK ZZCI_EPL PBS Index COEPL (key)0160 ZZCI_IK ZZCI_EPL_1 PBS Index COEPL (totals database)0170 ZZCI_IK ZZCI_EPR PBS Index COEPR (key)0180 ZZCI_IK ZZCI_EPR_1 PBS Index COEPR (totals database)0190 ZZCI_IK ZZCI_EPT PBS Index COEPT (key)0200 ZZCI_IK ZZCI_EPT_1 PBS Index COEPT (totals database)0250 ZZCI_IK ZZCI_TEXT PBS CCOI Protocol texts

Figure A-5 Table of the data structures of object ZZCCOI



Table V_ARC_DEF Date 07.12.99 Object /PBS/CCOI

Rec. Father seg. Segment Description0010 /PBS/CCOI_IK ViewPoint CCO Module Index Head0020 /PBS/CCOI_IK /PBS/CCOI_ITEM PBS Index CO_ITEM (Shrt text + Object)0030 /PBS/CCOI_IK /PBS/CCOI_COBK PBS Index COBK (key)0040 /PBS/CCOI_IK /PBS/CCOI_COBK_O PBS Index COBK (original doc.)0050 /PBS/CCOI_IK /PBS/CCOI_COEJ PBS Index COEJ (key)0060 /PBS/CCOI_IK /PBS/CCOI_COEJ_1 PBS Index COEJ (totals database)0070 /PBS/CCOI_IK /PBS/CCOI_COEJL PBS Index COEJL (key)0080 /PBS/CCOI_IK /PBS/CCOI_COEJL_1 PBS Index COEJL (totals database)0090 /PBS/CCOI_IK /PBS/CCOI_COEJR PBS Index COEJR (key)0095 /PBS/CCOI_IK /PBS/CCOI_COEJR_1 PBS Index COEJR (totals database)0100 /PBS/CCOI_IK /PBS/CCOI_COEJT PBS Index COEJT (key)0105 /PBS/CCOI_IK /PBS/CCOI_COEJT_1 PBS Index COEJT (totals database)0110 /PBS/CCOI_IK /PBS/CCOI_COEP PBS Index COEP (key)0120 /PBS/CCOI_IK /PBS/CCOI_COEP_1 PBS Index COEP (totals database)0130 /PBS/CCOI_IK /PBS/CCOI_COEPB PBS Index COEPB (key)0140 /PBS/CCOI_IK /PBS/CCOI_COEPB_1 PBS Index COEPB (totals database)0150 /PBS/CCOI_IK /PBS/CCOI_COEPL PBS Index COEPL (key)0160 /PBS/CCOI_IK /PBS/CCOI_COEPL_1 PBS Index COEPL (totals database)0170 /PBS/CCOI_IK /PBS/CCOI_COEPR PBS Index COEPR (key)0180 /PBS/CCOI_IK /PBS/CCOI_COEPR_1 PBS Index COEPR (totals database)0190 /PBS/CCOI_IK /PBS/CCOI_COEPT PBS Index COEPT (key)0200 /PBS/CCOI_IK /PBS/CCOI_COEPT_1 PBS Index COEPT (totals database)0210 /PBS/CCOI_IK /PBS/CCOI_EBII PBS INDEX EBII (key+rest)0220 /PBS/CCOI_IK /PBS/CCOI_EBII_1 PBS INDEX EBII (SD Doc. number)0250 /PBS/CCOI_IK /PBS/CCOI_TEXT PBS CCOI protocol texts

Figure A-6 Table of the data structures of object /PBS/CCOI

Archive object/ViewPoint/CCOI A-11

A-12


Conversion of R/2 data from CCO/CCA archivesIf archived CO line items have been migrated from SAP R/2 (release 4.3 or 5.0) into SAP R/3 (release 3.x) with the ViewPoint CO Module/CA before the implementation of ViewPoint CO Module (from 4.0B), you can migrate this data with the help of program /PBS/CCOIUMSL into release 4.x. Then you can continue to use and display this data with ViewPoint CO Module. In the ViewPoint CO Module/CA for R/3 release 3.x, the data was stored in a ViewPoint-specific format which does not correspond to the ADK standard.

All data archived in SAP R/3 can directly be processed for the construction of a ViewPoint archive (/PBS/CCOILOAD) with the ViewPoint CO Module. But, R/2 archive data, which were migrated into a former CO/CA archive in SAP release 3.x must be converted into a format which can be read by load program /PBS/CCOILOAD. Program /PBS/CCOIUMSL creates archive files corresponding to the data format of archiving object CO_ITEM from the migrated R/2 data being stored in a ViewPoint archive CO/CA of SAP release 3.x. Then, these archive files can be processed with transaction /PBS/COIL as described in “Initial load process” on page 2-9. Call conversion program /PBS/CCOIUMSL via the main menu of CCO:

ViewPoint archive > ViewPoint utilities CCOI > Conversion program R/2 data CCO/CCA > CO_ITEM



According to your delimitations on the selection screen as shown in Figure A-7, “Selection screen of conversion program for migrated KOEP data,” the conversion program accesses an existing ViewPoint archive created under release 3.0/3.1 with the ViewPoint CO Module/CA.

Figure A-7 Selection screen of conversion program for migrated KOEP data

EMC Professional Services recommends to convert the data step by step into the corresponding archive files of archiving object CO_ITEM depending on the size of the old CCO/CCA archive (monthly, quarterly or yearly).

The following preconditions must be fulfilled for the implementation of conversion program /PBS/CCOIUMSL:

� The file path to the existing ViewPoint archive CCO/CCA under 3.x has to be accessible from the current system (file path is described in your SAP CCO/CCA manual).

� Online access to the archived data of CCO/CCA was made possible by running program /PBS/CCOCFILE (in analogy to ZZCKFILE of ViewPoint CO Module/CCA, in your SAP CCO/CCA user manual). Program /PBS/CCOCFILE is called via the CCO main menu: ViewPoint archive > ViewPoint utilities CCOI > Load admin. table for R/2 data conversion (/PBS/CCOCFILE)

Conversion of R/2 data from CCO/CCA archives A-13

A-14


Having completed the conversion run, program /PBS/CCOIUMSL displays a protocol of the archived CO line items, as shown in Figure A-8, “Protocol of the conversion program for migrated KOEP data.”

Figure A-8 Protocol of the conversion program for migrated KOEP data

After the successful conversion of the old data, the ViewPoint CO Module/CCA for release 3.x which is no longer needed can now be deleted.
