Sl.

No

Activity

BW Steps

Person responsible
Basis

Basis Steps

Dependency

1.

System sanity check

Tcode YBIGMON used to check the sanity of the system

2.

Short dumps

Use Tcode ST22 and check for short dumps regularly during the day Use Tcode SM21 two times a day to check for system errors, warnings, user locks due to failed logon attempts from known users, and process messages Use Tcode SM50 / SM66 several times a day to check for stuck processes Use Tcode PRECSYS Displays the status of servers on the basis of SM12 information, information returned by each individual server and time of last job performed on each server

BW/Basis

3.

System log

Basis

4. DAILY

Workload

Basis

5.

Precal server status

Basis

ATS to reboot the servers if any of them are down

Basis 6. TREX search engine status Use Tcode RSODADMIN once before 8am to check the status of the TREX search engine status Inform ATS if the status of the TREX engine is down BW/Basis Inform ATS if the BIA server is down

7.

BIA status

Use Tcode RSDDBIAMON2 to check the status of the BIA

8.

IGS status

Use Tcode SIGS to check the Status of IGS engines per server

BW/Basis

Inform ATS if the IGS server is down

Sl.No

Activity

BW Steps

Person responsible
BW

Basis Steps

Dependency

9.

Data load monitoring

Use Tcodes RSMO / YV22 / YV23 to check for data loads

10. DAILY

Look at HD/INC calls

Take up the daily HD/INC calls

BW

11.

Attend change meeting

Communicate impacts to the team

BW

WEEKLY

12.

Analysis of precalculation jobs

Use Tcode RSBATCH to analyze failure and workload of precalculation server related jobs Perform pre and post mass transport activities

BW/Basis

13.

Mass transport support

BW/Basis

14.

Number range buffering

SID number range buffering

BW

To be automated ATS to run SQL monthly

15.
MONTHLY

Technical team meetings

Internal team meetings

BW

16.

Review of jobs on call-out

Add new, remove old, update of the documentation

BW

17.

REMSTATS

Check the cpu usage, memory utilization etc

Basis

Sl.No

Activity

BW Steps

Person responsible

Basis Steps

Dependency

OSS note review

18.

Review the OSS notes in SAP service market place and apply the useful ones to the BW system if it helps in increasing the efficiency of the system Run the report SAP_DROP_EMPTY_FPARTIT IONS to empty the F-table partitions

BW

Empty F-table partitions

BW

19.

20.

BW workload analysis & performance

Use Tcode ST03N for analysis and proposal for tuning

BW

Check broadcaster jobs

21.

Find 'test' jobs, jobs running twice or more a day, duplicate scheduling, liaise with users, analyze logs, etc.

BW

Sl.No

Activity

BW Steps

Person responsible
BW

Basis Steps

Dependency

22.

ODS secondary indexes

Check if the existing ones are used and create new ones to improve the performance Check regular deletion routines in place

23.

Data deletions

BW

REGULAR

24.

Superfluous (extra )batch jobs

1. Identify superfluous batch jobs and delete them. 2. Inform ECS to remove them from the schedule

BW

25.

Deletion of old queries/workbooks

Delete old workbooks and queries using reports RSZDELETE, YVUPD125 and YVUPD060 ( requires the consent of DSCM and key users) Check regular deletions are in place and set up deletions. Use the reports YVREP049, YVERP005 , YVUPD068 ,ZBWDELPSA and generic process chains

BW

26.

PSA sizes

BW

27.

Logs & traces

Check no unnecessary traces are recorded or any unnecessary logging is performed Transactions: ST01/ST05 RSECLOG_CL/RSECPROT BPS_TRACE

BW

Infocube compression

28.

Set up infocube compression where not in place

BW

29.

OSS message follow-up

Follow up the OSS messages

BW

30.

Slow update rules, transfer rules, etc

Identify wherever possible slow update/transfer rules and check with the designer to improve them.

BW

31.

Check, repair, coalesce indices

Use the reports YVREP012 ZSAPBWORA_INDEX_COAL ESCE YSAP_INFOCUBE_INDEXES_ REPAIR for checking/repairing the indices

BW/Basis

Sl.No

Activity

BW Steps

Person responsible

Basis Steps

Dependency

32.

Fiscal year change support

1.Users locked & batch stopped 2.Transports 3.Integrated forecast / Namahan Transmission / AIMS transmission 4.Prep (aggregates and BIA) 5.MD uploads/changes 6.Manual change run 7.Enable BW batch & unlock users 8.AIMS transmission / Integrated forecast / aggregates, BIA, etc

BW

From 6month s to Yearly

33

Peak season support

1.Avoid any action that impacts BW's performance and responsiveness unnecessarily 2.Try to move extra tasks to off-reporting hours 3.Let the team know about any extra jobs or nonstandard activities with significant impact on resources so that everyone knows what is going on should he/she receive questions from the users 4.Every designer to double check his/her area(s) of responsibility to guarantee availability 5.Any extra loads to be deleted from PSA a.s.a.p to not spoil valuable free space

BASIS

34

System refresh

BASIS

35

System upgrades

BW/BASIS

36

SAP GUI & components testing

Test the various functionalities of the new SAP GUI

BW/BASIS

37

Support pack testing

BW/BASIS

38

Early watch report review

Basis

39

Master data deletions Removal of superfluous infoproviders Identify the superfluous infoproviders and arrange for their deletion

BW

40

BW

41

InfoCube repartitioning

To be done in the future

BW

42

Request archiving

BW