Data Archiving Design Rev3

Data Archiving Design Document
No: Revision 2
Date: Wednesday, May 20, 2009
© 2008 Pt Devi Ratna
All rights are reserved. No part of this document may be photocopied, reproduced without prior consent of Pt Devi Ratna.
This document contains proprietary and confidential information. All data submitted to PT Golden Bird Metro is provided in reliance
upon its consent not to use or disclose any information contained herein except in the context of it business dealings with Pt Devi
Ratna.
Page 2 of 31
Content
1 Description of Project.......................................................................................................................5
2 Key Requirements.............................................................................................................................5
3 Functional Scope...............................................................................................................................6
3.1 Data Archiving with 6 standard archiving objects............................................................................6
3.2 Data Archiving of the 7 custom archiving objects for enhancement modules................................6
3.3 Document Archiving for billing documents (Enhancement module: BILLING)................................6
3.4 Project Schedule...............................................................................................................................6
4 System Analysis.................................................................................................................................6
4.1 Overview...........................................................................................................................................6
4.2 Concept of Archiving Objects...........................................................................................................6
4.3 Biggest Tables and the related Archiving Objects............................................................................6
4.4 Custom Archiving Objects.................................................................................................................6
4.5 Document Archiving from Billing Enhancement..............................................................................6
5 Recommendations............................................................................................................................6
5.1 Data Archiving...................................................................................................................................6
5.1.1 Archiving Objects..............................................................................................................................6
5.1.2 Residence Times...............................................................................................................................6
5.1.3 Standard Archiving Objects..............................................................................................................6
5.1.4 Custom Archiving Objects.................................................................................................................6
5.2 Document Archiving.........................................................................................................................6
Page 3 of 31
Purpose of this documentation is the analysis of the TPC and PCS SAP database and to
recommend a data archiving and management strategy with the goals of compliance and
database reduction in mind. In addition the design of one document archiving scenario is
detailed in this document.
Page 4 of 31
1 Description of Project
PTDR will implement a SAP data and document archiving solution for Blue Bird. We understand
the challenges the Blue Bird is facing in terms of keeping the SAP production database at a
healthy size.
PTDR’ has carried out an detailed database analysis for Blue Bird and believes that data
archiving with 6 standard and 7 non-standard objects will significantly reduce the database size
and reduce its future growth to keep it under control.
Bleu Bird can also expect improved performance and reduced backup times. Document
archiving will reduce the process of manual filing paper documents and at the same time enable
users to locate and display an electronic copy in the shortest time possible.
PTDR will also introduce one document archiving scenario for billing documents from the billing
enhancement
2 Key Requirements
The following key requirements have been identified as part of the initial database and system
review:
a) Significant reduction in the production database size
b) Control the future database growth
c) Archiving to be implemented for standard objects and enhancements modules (custom

tables).
d) Document archiving in general will be introduced at a later stage - however archiving of billing
documents from the billing enhancement will be implemented immediately.
e) Archiving in financial accounting, materials management and plant maintenance will initially
move the years 2004 to 2006 from the SAP database to the archive server. This
corresponds to a residence time were the actual financial year plus another two years
remain in the SAP database and older documents will be archived.
f) Blue Bird requested to archive data from the following enhancement modules:
 Billing for Voucher, Sales Order and Misc Charges

 Billing for Trucking (no longer required)
 Fuel Consumption
 Meter Reader
 Equipment Master Data (no longer required)
 COPA from Taxi Meter
 Driver Management: Loan
 Driver Management: Saving
Page 5 of 31
3 Functional Scope
Important Update: On Tuesday 19-May-2009 Bluebird requested to change the scope from 7
custom and 6 standard archiving objects to 6 custom and 7 standard archiving objects.
3.1 Data Archiving with 7 standard archiving objects
a) Archiving Process
Data archiving will be executed using SAP standard archiving functionality and archived
data will transferred via SAP ArchiveLink to the Opentext Archive Server for long term
storage. The scope includes the implementation of 7 standard data archiving objects.
b) Access to Standard Archiving Objects
Blue Bird users will be able to display standard archived documents with SAP standard
functionality such as
 Single document access (e.g. transaction FB03)

 Reports (e.g. in CO)
 Archive information system
This is limited to the standard access functions offered by SAP for each archiving
object. Access to archived data via the above functions may be different for each
archiving object.
 Opentext Doculink
Opentext offers standard scenarios which enable users to conveniently locate and
display archived and online documents in an explorer-like view together with all
related objects.
Example: Search and display of archived and online materials documents with related
financial documents, material ledger documents and controlling documents or
purchase orders. (Please note that these standard scenarios might need to be
purchased at extra costs from Opentext depending on the license agreement.)
PTDR will implement a maximum of one Opentext standard scenario for each
standard archiving object.
3.2 Data Archiving of the 6 custom archiving objects for enhancement modules
Custom archiving objects will be created for data archiving in enhancement modules which
includes creation of custom archiving objects and write and delete programs for the same.
The implementation of 6 custom objects should be sufficient to reduce the overall database size
and improve performance. Additional custom objects can be implemented at a later stage.
Page 6 of 31
a) Archiving Process
PTDR will implement custom archiving objects and data archiving will be executed using SAP
standard archiving functionality. Archived data will transferred via SAP ArchiveLink to the
Opentext Archive Server for long term storage.
b) Access to Custom Archiving Objects
Display of data archived with these custom archive objects will be realized via Opentext
Doculink and archive information system.
3.3 Document Archiving for billing documents (Enhancement module: BILLING)
Implementation of 1 document archiving scenario for billing documents from the enhancement
module BILLING. Search and display for these documents will be realized via Opentext Doculink.
3.4 Project Schedule
The project plan for this project is as following:
Page 7 of 31
4 System Analysis
This section outlines the result of the detailed database analysis of the production database and
recommends the data archiving objects to be implemented according to the project scope.
4.1 Overview
The current used and free space of the database is as show below:
Description Size in KB Size in %

Total Database Size 1,002,792,568 100 %
Total Free Space 83,940,000 8%
Total Used Space 918,852,568 92 %
The database analysis compromised tables with a size larger than 1024 KB which in total sum up
to 80% of the used database space. Tables with a smaller size are either system tables or from
not activated modules and functions.
Description Size in KB Size in %

Total Used Space 918,852,568 100 %
Analyzed Space 735,255,552 80 %
Not Analyzed Space 183,597,016 20 %
4.2 Concept of Archiving Objects
Data archiving in SAP is defined by archiving objects. Archiving objects combine records from
several tables that belong together like a business object (e.g. financial document, sales order
and purchasing order). This ensures that records can be displayed from the archive in a
meaningful way.
Tables and their respective archiving object(s) can be determined using transaction DB15. One
table can belong to multiple archiving objects as some tables containing address or change log
data are shared by multiple business objects.
Some tables are not assigned to archiving objects because they are system tables or temporary
tables that may grow to a certain extend but the size be maintained with standard SAP
functionality (e.g. tables which belong to SAP spool).
Page 8 of 31
4.3 Biggest Tables and the related Archiving Objects
In order to achieve the goal to significantly reduce the database size the biggest archiving
objects should be prioritized for this project. Blue Bird may later introduce further archiving
objects if necessary.
Priority Archiving Object Description Size in KB %

Total Analyzed Space 735,255,552
Total Analyzed Space not covered by Archiving Objects 84,649,984
Total Analyzed Space covered by recommened Archiving Objects
650,605,568 100 %
(Database Growth)
1 PM_ORDER Plant Maintenance 97,011,917
2 COPA1_BB00 Profitability Analysis 94,791,680
3 MM_ACCTIT MM Interface Postings to FI *1
56,910,848
4 FI_DOCUMNT Financial Documents 52,049,920
5 EC_PCA_ITM Profit Center Accounting 47,594,496
Custom Archiving
6 Objects Custom Modules *2
39,293,952
7 PM_QMEL Maintenance Notifications 37,007,360
8 PM_IMRG Measurement Documents 31,997,952
Tables will be archived with 1-
Incl. Multiple Objects 13 112,004,506
Total Analyzed Space covered by further Archiving Objects (Database
568,662,631 87 %
Growth)
9 MM_MATBEL Material Documents 23,271,424
10 BC_SBAL Delete Logs 17,828,864
11 CO Multiple Controlling 10,890,035
12 CO_ML_IDX Material Ledger Index Data 2,230,272
Incl. Multiple Objects Tables not included in 1-13 27,722,342
Total Analyzed Space covered by Archiving Objects (Database Growth)
81,942,937 13 %
not in scope
*1
Archiving MM subsequent posting data (generate in background). Please note that this is
purely background data and no transaction exists to display those records.
*2
Please refer to 4.4 for information about custom archiving objects and sizes.
The above calculations show that with the selected (highlighted above in green)
standardarchiving objects plus 7 custom archiving objects Blue Bird will be in control of around
87 % of the tables with transactional data. How much can be initially archived depends on the
document distribution by year for each archiving object.
Please note that the above figures are approximate values.
Page 9 of 31
4.4 Custom Archiving Objects
Custom archiving objects need to be created for the archiving of custom tables in SAP. Blue Bird
intends to archive the following 7 custom archiving objects and the related tables:
Archiving
No Description Size in KB %
Object
1 ZZ_BILL Billing for Voucher, Sales Order and Misc. Charges 7,141,376 16 %
2 ZZ_FLEH Fuel Consumption 12,751,872 29 %
3 ZZ_ARGO Meter Reader 9,394,176 21 %
5 ZZ_COPA COPA from Taxi Meter 6,098,944 14 %
6 ZZ_DMLOAN Driver Management: Loans 3,364,864 8%
7 ZZ_DMSAVE Driver Management: Savings 5,053,440 12 %
Total for all Objects 43,804,672 100%
Please note that the difference in the totals of this table (43,804,672) and the table in chapter
4.3 (37,007,360) derives from different approaches. While the table in chapter 4.3 only
considers 80% of the used space this table considers all tables related to the custom archiving
objects and is therefore more precise.
4.5 Document Archiving from Billing Enhancement
The following is a scanned sample of the document to be archived as outgoing document. The
relevant billing information is printed by SAPScript on a form in several copies. One copy will be
stored automatically on the archive server whenever a document is printed.
Page 10 of 31
5 Recommendations
This chapter proposes a data and document archiving solution according to the project scope:
5.1 Data Archiving
5.1.1 Archiving Objects
Priority Archiving Object Description

1 PM_ORDER Plant Maintenance
2 COPA1_BB00 Profitability Analysis
3 MM_ACCTIT MM Interface Postings to FI
4 FI_DOCUMNT Financial Documents
5 EC_PCA_ITM Profit Center Accounting
6 PM_QMEL Maintenance Notifications
7 PM_IMRG Measurement Documents
8 ZZ_BILL Billing for Voucher, Sales Order and Misc Charges
9 ZZ_FLEH Fuel Consumption
10 ZZ_ARGO Meter Reader
11 ZZ_COPA COPA from Taxi Meter
12 ZZ_DMLOAN Driver Management: Loans
13 ZZ_DMSAVE Driver Management: Savings
5.1.2 Residence Times
Residence time is the time a certain document (record) is remaining in the SAP R/3 database
before it is archived.
5.1.2.1 Recommendation for Residence Times
As a recommendation Bluebird should leave documents from the current fincancial year plus
another two years on the database. Bluebird may also opt for a shorter residence time but
should in any case leave the current plus another complete year in the database. Residence
times need to be discussed between management, IT and functional departments.
It might be easier or users if a common residence time is decided throuout the company.
Page 11 of 31
5.1.2.2 Document Distribution
The following tables show the document distribution for the archiving objects. How much
records can be initially removed the database to the storage system depends on the document
distribution.
Number of records in % highlighted in green could be archived with a residence time of current
plus another 2 years.
Archiving Object PM_ORDER

Year Number of Documents in % Accumulated % of Total
2004 3% 3%
2005 11 % 14 %
2006 22 % 36 %
2007 27 % 63 %
2008 28 % 91 %
2009 9% 100 %
Archiving Object COPA1_BB00

2004 10 % 10 %
2005 21 % 31 %
2006 19 % 50 %
2007 20 % 70 %
2008 24 % 94 %
2009 6% 100 %
Archiving Object MM_ACCTIT

2004 8% 8%
2005 20 % 28 %
2006 21 % 49 %
2007 21 % 70 %
2008 22 % 92 %
2009 8% 100 %
Archiving Object FI_DOCUMNT

2004 10 % 10 %
2005 13 % 23 %
2006 18 % 41 %
2007 24 % 65 %
2008 26 % 92 %
2009 8% 100 %
Page 12 of 31
Archiving Object EC_PCA_ITM
2004 6% 6%
2005 21 % 27 %
2006 24 % 51 %
2007 21 % 72 %
2008 21 % 93 %
2009 7% 100 %
Archiving Object PM_QMEL

2004 5% 5%
2005 13 % 18 %
2006 21 % 39 %
2007 26 % 65 %
2008 26 % 91 %
2009 9% 9%
Archiving Object PM_IMRG

2004
2005
2006
Data not available at time of analysis.
2007
2008
2009
Archiving Object Billing for Voucher, Sales Order and Misc. Charges
2004 5% 5%
2005 13 % 18 %
2006 16 % 34 %
2007 25 % 59 %
2008 30 % 89 %
2009 11 % 100 %
Archiving Object Fuel Consumption

2004 8% 8%
2005 6% 14 %
2006 3% 17 %
2007 3% 20 %
2008 52 % 72 %
2009 28 % 100 %
Archiving Object Meter Reader
Page 13 of 31
2004 9% 9%
2005 19 % 28 %
2006 18 % 46 %
2007 21 % 67 %
2008 24 % 91 %
2009 9% 100 %
Archiving Object Equipment Master Data

2004 6% 6%
2005 15 % 21 %
2006 19 % 40 %
2007 23 % 63 %
2008 26 % 89 %
2009 11 % 100 %
Archiving Object COPA from Taxi Meter

2004 9% 9%
2005 19 % 28 %
2006 18 % 46 %
2007 21 % 67 %
2008 24 % 91 %
2009 9% 100 %
Archiving Object Driver Management: Loans

2004 10 % 10 %
2005 19 % 29 %
2006 17 % 46 %
2007 20 % 66 %
2008 24 % 90 %
2009 10 % 100 %
Archiving Object Driver Management: Savings

2004 9% 9%
2005 19 % 28 %
2006 18 % 46 %
2007 21 % 67 %
2008 24 % 91 %
2009 9% 100 %
Page 14 of 31
5.1.3 Access to Archived Data
The following gives an overview how users can access archived data. How access is realized is
different for each archiving object.
5.1.3.1 Single Document Access
We are talking about single document access when the display of archived data is realized with
the same transaction as for online data or in a similar way. Example is transaction FB03 which
can display archived and online data. This access method is only available for a selected number
of archiving objects.
5.1.3.2 Reports
A selected number of reports, for example in financial accounting and controlling, can read from
online and archive or from either online or archive.
5.1.3.3 Print Lists
In case a certain report does not read from archive and the information is lost after archiving
then a sapshot of this report can be archived in form of a print list prior to archiving. This report
can be displayed in its original form at any time later.
5.1.3.4 Opentext Doculink
Doculink gives users access to documents in an explorer like form. Doculink can display online
and offline records side by side. In addition archived (paper) documents can be displayed as
well. Below find an example to illustrate access with Doculink.
Page 15 of 31
5.1.4 Standard Archiving Objects
5.1.4.1 PM_ORDER
5.1.4.1.1 Description
Archiving object PM_ORDER archives plant maintenance and service orders.
5.1.4.1.2 Checks during Archiving
Documents must meet the following criteria before they can be archived:
 Document must have status “Business completed” (CLSD).

Note: The status business completion (CLSD) can only be set if no more PO commitments
exists (open PO) and the final invoice indicator is set in the related PO’s. According to SAP
standard procedures the indicator is to be set by the user when the LIV is created or
manually in the PO.
 All orders which are part of a network or hierarchy must be archivable before a single
order of that network or hierarchy can be archived
 Related PO’s must be archived before the PM order can be archived.
 PM orders must be archived before the related PR’s can be archived.
 Requested quantity not yet completely ordered
 Purchase order for this requisition item has not yet been invoiced.
 The closed indicator in the purchasing requisition will allow for archiving even the
requested quantity is not converted into a purchase order in full.
 Inspection lots must be completed.
Note: If Blue Bird chooses to archived maintenance notifications with archiving object
PM_QMEL then historical maintenance orders cannot be created as a condition of PM_QMEL
archiving. Display functionality with transactions IW33. IW63, IW39 is not possible and display is
possible only with archive information system in similar form as IW33 but reduced functionality.
Note: The archiving program for plant maintenance orders also archives the related purchase
requisitions. These purchase requisitions are therefore not selected by the archiving program for
object MM_EBAN.
Note: Some of the conditions may not apply to Blue Bird if PR’s are not created directly from the
PM_ORDER.
Important: PM Order Type SO not to be archived.
5.1.4.1.3 Seletion Criteria for Archiving
The following are the recommended selection parameters:
 Change Date
 Planning Plant (if required)
 Order Type: Exclude SO
Page 16 of 31
5.1.4.1.4 Access to Archived Documents
Archived documents can be displayed with the following transactions:
Display a single document:
Transaction Description Functionality

IW33 Display Maintenance Order Online & Archived
IW63 Display Historical Maintenance Order Archived only
IW39 Display Order List Online & Archived
ALO1 Document Relationship Browser Not available
SARI Archiving Information Structure Archived only
J6NY Opentext Doculink Explorer Not Available
Page 17 of 31
5.1.4.2 COPA1_BB00
Archiving object COPA1_BB00 archives records from profitability analysis.
There are no specific checks for the archiving of line items beside the residence time or specific
selections in the archiving program variant.
 Fiscal Year and Period

 Company Code (if required)
 Controlling Area (if required)

ALO1 Document Relationship Browser Online & Archived
SARI Archiving Information Structure Archived only
J6NY Opentext Doculink Explorer Not available
Reports:

KE24 PA: Actual line items Online & Archived
KE25 PA: Plan line items Online & Archived
KE30 PA: Profitability report Online & Archived
Page 18 of 31
5.1.4.3 MM_ACCTIT
The archiving object MM_ACCIT is used to archive Materials Management (MM) subsequent
posting data. Postings made in the Inventory Management (MM-IM) and Invoice Verification
(MM-IV) application components update Accounting-relevant information in tables ACCTHD,
ACCTIT, and ACCTCR. Records updated in these tables are only background interface data and
there is no transaction or report to display them.
There are no specific checks for the archiving of line items beside the residence time or specific
selections in the archiving program variant.


SARI Archiving Information Structure Archived Only
Reports:

Not available Not available Not available
Page 19 of 31
5.1.4.4 FI_DOCUMNT
Archiving object FI_DOCUMNT archives financial documents.
 The document must not contain any open items. The system can only archive documents
containing cleared items or those not managed on an open item basis.
 Documents with withholding tax must meet country-specific retention requirements.
 Sample, recurring and parked documents cannot be archived.


FB03 Financial Documents Online & Archived
FBL5N Customer line items Online & Archived
FBL3N G/L account line items Online & Archived
FBL1N Vendor line items Online & Archived
ALO1 Document Relationship Browser Online & Archived
J6NY Opentext Doculink Explorer Online & Archived
Reports:

S_ALR_87009826 Compact doc. Journal Online & Archived
S_ALR_87009828 Line item journal Online & Archived
Page 20 of 31
5.1.4.5 EC_PCA_ITM
Archiving object EC_PCA_ITM archives line item records from profit center accounting. Totals
will not be archived.
When Profit Center Accounting is active, additional line items and totals records are created for
each profit-related transaction posted in the R/3 System. Consequently, Profit Center
Accounting is not complete for a period until all the profit-related transactions for the period
have been posted. SAP recommends that you wait until this is the case before archiving the
profit center transaction data for the period. However, there are no checks for this during
archiving.

 Record Type (Plan/Actual will be archived separately)
 Controlling Area (if required)

Reports:

S_ALR_87009712 Profit Center List: Plan/Actual Online & Archived
S_ALR_87013340 Profit Center Group: Plan/Actual/Variance Online & Archived
S_ALR_87009726 Profit Center Group: Plan/Actual/Variance by Origin Online & Archived
S_ALR_87009734 Profit Center Group: Plan/Plan/Variance Online & Archived
S_ALR_87009717 Profit center Group: Quarterly Comparison of Actual Data Online & Archived
S_ALR_87013342 Profit Center: Statistical Key Figures Online & Archived
KE5Z Profit Center: Actual Line Items Online & Archived
KE5Y Profit Center: Plan Line Items Online & Archived
S_ALR_87013343 Profit Center: Receivables Online & Archived
S_ALR_87013344 Profit Center: Payables Online & Archived
Page 21 of 31
S_ALR_87013345 Profit Centers: Customers Online & Archived
S_ALR_87013346 Profit Centers: Vendors Online & Archived
S_ALR_87013347 Profit Centers: Assets Online & Archived
S_ALR_87013348 Profit Centers: Materials Online & Archived
S_ALR_98013349 Profit Center: Average Balance Year to Date/Accounts Online & Archived
S_ALR_98013350 Profit Center: Average Balance Year to Date/Profit Center Online & Archived
S_ALR_98013351 Profit Center: Average Balance by Period/Account Online & Archived
S_ALR_98013352 Profit Center: Average Balance by Period/Profit Center Online & Archived
S_P99_41000117 PCA Actual Data: Transfer to SAP EIS Online & Archived
S_P99_41000118 PCA Plan Data: Transfer to SAP-EIS Online & Archived
Page 22 of 31
5.1.4.6 PM_QMEL
Archiving object PM_QMEL archives maintenance notifications in the plant maintenance

component.
 The deletion lag must be set in the notification.

 As soon as a maintenance notification is used in a maintenance order, the system status
MARC (Flagged for archiving) can be set. However, the system only archives the
maintenance notification if the maintenance order and the historical order have already
been deleted.
Note: If Blue Bird chooses to archived maintenance notifications with archiving object
PM_QMEL then historical maintenance orders cannot be created as a condition of PM_QMEL
archiving. Display functionality with transactions IW33. IW63, IW39 is not possible and display is
possible only with archive information system in similar form as IW33 but reduced functionality.
 Notification number
 Equipment number
 Functional location
Please note that when the plant maintenance order is business completed the related
notification is also completed. The notification must be completed as a condition for archiving.
Therefore the above selection can be left empty so all archivable notification will be selected
automatically.

SARI Archiving Information Structure in simple table form only Archived Only
Page 23 of 31
5.1.4.7 PM_IMRG
Archiving object PM_IMRG archives measurement documents in the plant maintenance

component.
 You can only delete complete measurement document areas, this means, from the first
measurement document entered until a key date. You cannot archive and delete individual
measurement documents.
 At least one measurement document is usually retained when archiving. This is the latest
non-canceled measurement document. However, in the following cases, more than one
measurement document is retained:
 If there are canceled measurement documents after the latest measurement

document, then the latest measurement document and all subsequent canceled
measurement documents are retained.
 If there are several measurement documents with the same entry date and the same
(exact to the second) entry time, then all of the “latest” measurement documents
are retained. This can occur, for example, when you enter test data.
 Measuring Point
 Until Measuring Time

IK41 List and single document display in the same for as online Archived Only
Page 24 of 31
5.1.5 Custom Archiving Objects
5.1.5.1 Billing for Voucher, Sales Order and Misc Charges
Custom archiving for enhancement module/function “Billing for Voucher, Sales Order and Misc
Charges”.
 The record must have been posted to financial accounting. Check for flag ZTBILL.
Documents can be selected for archived by the following parameters:
 Billing Date
 Billing Number
5.1.5.1.4 Tables to be archived
The following tables will be archived with this object:
 ZTBILL (Header table)

 ZTCVCLS
 ZTCVEXP
 ZTCVTMP
 ZTMCTRH
 ZTMCTRD
 ZTSODATA
 ZTSODATAORG
 ZTBILLDET

J6NY Opentext Doculink Explorer in table like form Online & Archive
Print Lists Archive available reports before data archiving Archive Only
Page 25 of 31
5.1.5.2 Fuel Consumption
Custom archiving for enhancement module/function “Fuel Consumption”.
 Bluebird has not given any criteria yet, however this can be specified during the
implementation phase of this project.
 Financial Year
 Document Number
 ZTFLEH (Header table)

 ZTFLED

Page 26 of 31
5.1.5.3 Meter Reader
Custom archiving for enhancement module/function “Meter Reader”.
 Date
 Document Number
 ZTTXNARGO (Header table, standalone)

Page 27 of 31
5.1.5.4 Profitablility Analysis from Taxi Meter
Custom archiving for enhancement module/function “Profitablility Analysis fromTaxi Meter”.
 Date
 Document Number
 ZTICOPAMTR (Header table, standalone)

Page 28 of 31
5.1.5.5 Driver Management: Loans
Custom archiving for enhancement module/function “Driver Management: Loans”.
 Document Year
 Document Number
 ZTTRHTH (Header table, standalone)

 ZTSLHT

Page 29 of 31
5.1.5.6 Driver Management: Savings
Custom archiving for enhancement module/function “Driver Management: Savings”.
 Document Year
 Document Number
 ZTTRTBH (Header table, standalone)

 ZTSLTB

Page 30 of 31
5.2 Document Archiving
The below illustration describes the document archiving solution in the “Billing” enhancement
module:
1. Initially the empty form without any data is archived with a form ID to the archive server.
2. Each time the document is printed a copy is archived to the archive server and the current
form ID is assigned to it.
3. When the user wants to display the archived document he searches for the document in
Opentext Doculink for SAP. When the document is found in SAP a simple doubleclick will
open the Opentext Viewer and the document is displayed. The viewer will overlay the
archived data and form automatically.
4. The archived document can be re-printed from the Opentext viewer.
5. Whenever a new form revision is created it needs to be scanned and archived with
Opentext forms management for SAP. A new form ID will be assigned. New documents will
be assigned to this form while older documents will be displayed with the previous form.
Page 31 of 31

Data Archiving Design Rev3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Archiving Design Rev3

Uploaded by

Copyright:

Available Formats

Data Archiving Design Document

3.1 Data Archiving with 6 standard archiving objects............................................................................6

3.3 Document Archiving for billing documents (Enhancement module: BILLING)................................6

3.4 Project Schedule...............................................................................................................................6

4.2 Concept of Archiving Objects...........................................................................................................6

4.3 Biggest Tables and the related Archiving Objects............................................................................6

4.4 Custom Archiving Objects.................................................................................................................6

4.5 Document Archiving from Billing Enhancement..............................................................................6

5.1 Data Archiving...................................................................................................................................6

5.1.1 Archiving Objects..............................................................................................................................6

5.1.2 Residence Times...............................................................................................................................6

5.1.3 Standard Archiving Objects..............................................................................................................6

5.1.4 Custom Archiving Objects.................................................................................................................6

5.2 Document Archiving.........................................................................................................................6

a) Significant reduction in the production database size

b) Control the future database growth

c) Archiving to be implemented for standard objects and enhancements modules (custom

 Billing for Voucher, Sales Order and Misc Charges

3.1 Data Archiving with 7 standard archiving objects

b) Access to Standard Archiving Objects

 Single document access (e.g. transaction FB03)

b) Access to Custom Archiving Objects

3.3 Document Archiving for billing documents (Enhancement module: BILLING)

3.4 Project Schedule

The project plan for this project is as following:

Description Size in KB Size in %

Description Size in KB Size in %

4.2 Concept of Archiving Objects

Priority Archiving Object Description Size in KB %

Please note that the above figures are approximate values.

4.5 Document Archiving from Billing Enhancement

5.1 Data Archiving

5.1.1 Archiving Objects

Priority Archiving Object Description

5.1.2 Residence Times

5.1.2.1 Recommendation for Residence Times

Archiving Object PM_ORDER

Archiving Object COPA1_BB00

Archiving Object MM_ACCTIT

Archiving Object FI_DOCUMNT

Archiving Object PM_QMEL

Archiving Object PM_IMRG

Archiving Object Fuel Consumption

Archiving Object Meter Reader

Archiving Object Equipment Master Data

Archiving Object COPA from Taxi Meter

Archiving Object Driver Management: Loans

Archiving Object Driver Management: Savings

5.1.3.1 Single Document Access

5.1.3.3 Print Lists

5.1.3.4 Opentext Doculink

Archiving object PM_ORDER archives plant maintenance and service orders.

5.1.4.1.2 Checks during Archiving

 Document must have status “Business completed” (CLSD).

Important: PM Order Type SO not to be archived.

5.1.4.1.3 Seletion Criteria for Archiving

The following are the recommended selection parameters:

Archived documents can be displayed with the following transactions:

Display a single document:

Transaction Description Functionality

Archiving object COPA1_BB00 archives records from profitability analysis.

5.1.4.2.2 Checks during Archiving

5.1.4.2.3 Seletion Criteria for Archiving

The following are the recommended selection parameters: