sap sd/mm archiving sheila schedlbauer program manager microsoft corporation session code: 107

SAP SD/MM ARCHIVING

Sheila SchedlbauerProgram ManagerMicrosoft Corporation

Session Code: 107

SAP ArchitectureArchive HistoryBuild a Successful Archive Run

•Project plan•Objects, Data extract & SARA•Metrics

Archive Again or UpgradeQ&A

Agenda

SAP Global Instance• Single database & 9 application servers• SQL Server 2000 & Windows Server 2003• Version 4.5B, Hot pack 57• Modules SD, MM, FI, CO, HR, AM, RE• 2000 named users in 68 countries• 39,000 worldwide users• Heavy EDI and web based usage • 99.9% availability

SAP Architecture

9696 9797 9898 9999

Large & Med Subsidiaries

Small & Med Subsidiaries

OEM Software

9595

Core Config

OEM H/W

Small & New Subsidiaries

Packaged Product, Etc.

0000

Archive Project Begins

Archive History

Phased Approach• IDOC (Monthly)

– Started July 99 (2 GB/month)

• FI (Yearly)– Started December 99 (50 GB/year)

• SD/MM (Yearly to quarterly basis)– Started September 00 (25 GB/quarter)

Archive History

Growth = 6 GB/WK Total, 2 GB/WK SDMM

Archive History

950

970

990

1010

1030

1050

1070

1090

9/1/02 10/1/02 11/1/02 12/1/02 1/1/03 2/1/03 3/1/03

DA

TA

BA

SE

GR

OW

TH

GB

1

SAP ArchitectureArchive HistoryBuild a Successful Archive Run

•Project plan•Objects, Data extract & SARA•Metrics


Agenda

Project Plan• Archive jobs can run for a long time!

– Per 600 MB file, VBAK = 12 hours write, 16 hours delete, typical 4 files/quarter

• Items to consider– Need 2 plans: Test and Production– Resources: 2 wks/qrtr testing, 2 wks/qrtr

executing– Preplanned system down times– Month end processing – system performance– Other projects– Contingency

Build a Successful Archive Run

• Areas of Coordination– Basis, Business, Finance

Small window in which archive jobs can run


Objects• MM_EKKO Purchasing documents• RV_LIKP Deliveries• MM_MATBEL Material documents• SD_VBAK Sales documents• SD_VBRK Billing documents• SD_COND Sales pricing records• ZZINVTABLE For billing related custom

tables• BALM SAP supplied delete

program


• One step archiving– Write and delete jobs run subsequently– SD_COND

• Two step archiving– Write and delete jobs run separately– ZZINVTABLE, MM_EKKO, MM_MATBEL,

RV_LIKP, SD_VBRK, SD_VBAK

• Simple delete– BALM


Data Warehous

e

ExcelReports

SAP R/3SQL 2000

Data Extract

Write

Extract

Delete


SARA• Technical Settings

– Archive file size = 600 MB– Commit counter set to 10– “Start automat.” not selected (except

SD_COND)– “Make index” selected – Files written and retained on a network share– 4.7 improvement – Interrupt settings, Data

archiving monitor


• Archiving Control– Residence time 365 days – SD_COND - expired validity date – Excluded specific business streams (9999)– SD_VBRK - “check account doc is cleared”

selected in the customization

• Variant Settings – Max # of records per table = 100 000

(SD_COND)– “Check FI document”

– “Check flow documents residence”


ZZINVTABLE – Custom object• Archive Write and Delete programs

– ADK Function modules– Documentation – SARA/Help, SE37– Specific requirements

• AOBJ– New Entry – create the object - ZZINVTABLE– Assign the programs to the object– Assign the tables to the object (ZINVHDR,

ZINVDET)

• SARA– Run the new object


BALM• OSS Note 0195157• Removes entries from tables related to

the flow of data between APO and SAP• Need to only keep one month of data• Run as a batch job on a weekly schedule• In 4.7 - Available as an object BC_SBAL


Metrics• 2 Metrics of interest

– Database recovery– Job performance


• Determine the tables to measure– Total = 340 tables for our objects– DB02 - to determine the largest 100 tables– SARA - to list the tables included in the

objects– Compare the DB02 results and the SARA

information– Pick header and detail pairs– 30 tables


ADR2 ADR5ADR

CADRCOM

CADRCT ADRV

CDCLS

CDHDR

EKKO

EKPO KONP LIKP

LIPS MKPFMSE

GNAST STXH STXL

VBAK VBAP VBEP VBFA VBKD VBPA

VBRK VBRPVBU

KVBUP

ZINVDET

ZINVHDR


• Measure the Database– DB02 - Run “updateusage” on selected archive

tables – Collect table size information and store the data

in a reporting database – Run delete jobs– Run “updateusage” again on archive tables– Collect post-delete table size information and

store in reporting database– Run delta report


SIZE (MB) ADRC

CDHDR LIPS MSEG NAST STXH VBAK

Before19816 45219 6468 9255 17342 7422 2642

After19013 44357 5481 8233 14912 6689 2252

Reclaimed 803 862 987 1022 2430 753 390

SIZE (MB) VBAP VBEP VBFA VBPA VBRK VBRP VBUK

Before17734 4971 20131 25955 3648 13986 3044

After16089 4223 18272 22427 3120 11973 2608

Reclaimed 1645 748 1859 3528 528 2013 436

Total Database Reclaimed = 23530 Megabytes (23.5 GB)


Object Job Hours Job Hours#

Files

Total MB

(compressed)

MM_EKKO Write 0.5 Delete 0.25 1 11

MM_MATBEL Write 0.75 Delete 2.25 1 165

RV_LIKP Write 5.75 Delete 6 1 575

SD_VBAK Write 22 Delete 45 4 2270

SD_VBRK Write 22 Delete 31 4 2129

SD_COND Write 0.5 Delete 0.5 2 81

ZZINVTABLE Write 14 Delete 0.15 1 88

TOTAL Write 66 Hrs Delete 85 Hrs 14 5319

ALLExtrac

t 13 Hrs

COMPLETE RUN = 164 Hrs (7 Days)


Metrics – 4.7 New Functionality• 4.7 offers new functionality

– Data Archiving Monitor– Display Statistics


Tcode: RZ20


• View across objects

• Progress of archive jobs

• Need for action

• Start time, run time, etc.


• Date

• Run time

• DB statistics

SAP ArchitectureArchive History Build a Successful Archive Run

Project PlanObjects, Data extract & SARAMetrics


Agenda

Review the Process• Keep a core team together (functional,

basis, business)• New business requirements• Performance improvements• Retest after hot pack applications

Archive Again or Upgrade

Some Challenges• SD_VBAK & SD_VBRK - Memory errors

preventing completion of write phase• MM_EKKO - Error in ABAP application

program in write phase - perform not found.• RV_LIKP – Custom read job for extract step

ends in ABAP error


OSS Notes• Check OSS regularly!• Best way to search for notes

– “SARA”, “AOBJ”– Error message– Object name (ex SD_VBAK or VBAK)– Program name (S3VBAKWR)– “archive”, “archiving”– Note 0102446 gives application areas for

each archive object


Use a project planRight balance between

performance and document flow integrity

Small data setReview the process regularly

Summary

Questions

Thank you for attending!

Please remember to complete and return

your evaluation form following this session.

Session Code:107

sap sd/mm archiving sheila schedlbauer program manager microsoft corporation session code: 107

Documents

successful archive

archive project

project plan archive

modules sd

days sd

vbrkbilling documents

matbelmaterial documents

vbaksales documents