Table of Contents

1. Background....................................................................................................3 1.1 Document Purpose....................................................................................3 2. SMO: System Administration......................................................................3 2.1 Questionnaire Topics / Session Content...................................................3 3. Advanced Planner and Optimizer (APO)...................................................4 3.1 APO Administration Responsible Persons...............................................4 3.1.1 Install RFCOSCOL...........................................................................4 3.1.2 Integration Models............................................................................4 3.1.3 liveCache preparation..........7 3.2 BW within APO.7 3.3 Software Maintenance.............8 3.4 Monitoring.........9 3.4.1 Application Log......................9 3.4.2 liveCache Message Log.....10 System Maintenance SCM 3.4.3 liveCache Monitoring........11 3.4.4 liveCache Mlnlycke Health Care MHC Data Volume Filling Level......12 3.4.5 liveCache Administration Log..................................................................................13 3.4.6 liveCache Heap...............................................................................13 3.4.7 Consistency Checks........................................................................14 3.5 liveCache Administration Tool...............................................................16 3.5.1 Define a liveCache Backup Medium..............................................17 3.5.2 SQL Studio......................................................................................17 3.5.3 Delete transactional simulations.....................................................18 3.6 Logging of liveCache 7.4........................................................................18 3.7 Backup....................................................................................................19 3.7.1 Backup liveCache 7.4.....................................................................19 3.8 Verify of liveCache.................................................................................19 3.9 Initialization of liveCache.......................................................................20 3.10 Recovery for liveCache 7.4..................................................................20 3.10.1 Recovery with liveCache 7.4 in case of a soft crash....................20 3.10.2 Recovery with liveCache 7.4 in case of a hard crash....................21 3.11 Consistency check.................................................................................21 3.12 Periodic Background Jobs....................................................................22

Handbook

3.13 List of important APO transactions......................................................23 4. qRFC.............................................................................................................26 4.1 General qRFC Settings...........................................................................26 4.1.1 Responsible Person in general........................................................26 4.1.2 qRFC Instance Parameter Settings..................................................26 4.1.3 RFC wait times................................................................................27 4.2 APO Monitoring of qRFC......................................................................28 4.2.1 Responsible Persons........................................................................28 4.2.2 APO-Monitoring qRFC Outbound Queues.....................................28 4.2.3 APO-Monitoring qRFC Inbound Queues.......................................29 4.2.4 APO qRFC Alert Monitor...............................................................30 4.2.5 R/3 System Integration Model Generation and Activation.............30 4.3 Relevant SAPNet Notes..........................................................................31

Attachments
Number 1 2 Title Date Version

Change History
Version 0.1 0.2 0.3 0.4 Date 2004-08-25 2004-08-31 2004-09-16 2004-09-20 Changed by Marta Birgisdottir Marta Birgisdottir Marta Birgisdottir Marta Birgsdottir Change Firs draft Update Update after meeting between Capgemini AM and IM. Update after input from Acando Frontec

Document Reviews and Audits

Date Name Position

Distribution
Company Name

1.

Background
This document describes the overall actions needed for maintenance of the SCM systems. It includes daily/weekly/monthly/initial actions needed by AM and IM within Capgemini. All actions is agreed together with the customer, and part of the maintenance agreement signed by MHC and Capgemini.

1.1

Document Purpose The purpose of this document is to: Guide IM and AM in normal delivery, actions to fulfil agreed SLAs

2.
2.1

SMO: System Administration

Questionnaire Topics / Session Content
SESSION CONTENT Description Introduction Performance Management System Management Database Management High Availability Printing Change Management Security APO BW CRM SAP Technology Components Show Check

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

4 / 31

3.
3.1

Advanced Planner and Optimizer (APO)

APO Administration Responsible Persons
RESPONSIBLE PERSON Responsible Person Paul Forsner Anders strand Mikael Antonsson Michael Revensj System owner ? Company Capgemini / IM Capgemini / IM Capgemini / AM Capgemini / AM MHC

3.1.1 Install RFCOSCOL Purpose For analyzing hardware and operating load on standalone liveCache and Optimizer we recommend to implement the SAPOSCOL on all standalone servers. Procedure

SMAP TASKS Task Check log Responsible IM Frequency Weekly Menu Path Tools| CCMS|Control/Monitoring| Performance Menu|Operating system| Remote|Activity|Goto|OS Collector Tools | Control/Monitoring Transaction OS07 | OS Collector Via TNG RZ20

Using Alert Monitor RZ20

IM

Daily

LIST OF SAPNET NOTES Topic for Rel. <= 4.6 B Install RFCOSCOL Using data collection agent SAPCCMSR Notes 202934 371023

Work Shop Note: This RFCOSCOL have been installed by SCM installation project.

3.1.2 Integration Models

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

5 / 31

Purpose <init and after customizing> Procedure It is important for system administrators to know which data how and how often will be transferred from R/3 System to APO System. In general it is recommended to have different Integration models for different data. You can choose between immediately and periodically transfer of data. This will be customized with help of transaction CFC5 ( CFC9 as of PlugIn 2002.2 ). Immediately transfer Check entries in table CIFMODGEN Check running of background jobs RIMODGEN and RIMODAC2 Periodically Transfer bases on ALE and Change Pointer Processing Check which Change Pointers are activated with help of BD52 Reorganize Change Pointer Table with help of transaction BD22

INTEGRATION MODELS Model Logical System Application Selected Data Transfer Method <Immediately, Change Pointers,no transfer of changings>

Work Shop note: Link to document from Acando Frontec Integration model, responsible for that are AM.
SMAP TASKS Task Check Integration Models Responsible AM Frequency Menu Path Transaction CFM4

Create Integration Models

AM

Once in month / First Logistics | Central Monday each month Functions | Supply Chain Planning Interface| Core Interface APO | Integration Model | Display If necessary Logistics | Central Functions | Supply Chain Planning Interface| Core Interface APO | Integration Model | Create

CFM1

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
Task Activate Integration Model Responsible AM

6 / 31

Version 0.4
Frequency If necessary Menu Path Logistics | Central Functions | Supply Chain Planning Interface| Core Interface APO | Integration Model | Activate Logistics | Central Functions | Supply Chain Planning Interface | Core Interface APO| Integration Model | Change Transaction CFM2

Change Integration Models

AM

If necessary

CFM6

Delete obsolete Integration Models

AM

Check transfer method AM Backgound Jobs RIMODGEN and RIMODAC2 Activate Change Pointers in general AM

Have to start after RIMODAC2 have finished When needed Have to start after RCPTRAN4 have finished This are done in MEP by AF and are not needed in SCP CIFMAT set in MEP, not needed more in APO
AF: veckovis i ny integrationsmodell genereras. Fr att skicka ndringar p material i den aktiva integrationsmodellen. Krning gr frslagsvis lrdag morgon. AF bestller av CAP

Report RIMODDEL

CFC5 ( CFC9 as of PlugIn 2002.2 ) SM37

AM

BD61

Choose and adapt AM Message Types for transfering Schedule data transfer AM for Change Pointer Method

BD50

CFP1, Report RCPTRAN4

Reorganize Change Pointers

AM

Check data transfer channels in R/3 Check data transfer channels in APO LIST OF SAPNET NOTES Topic

IM, AM IM, AM

<weekly obsolete change pointers which are older than 14 days> Weekly after RIMODDEL are finished Weekly - Mondays In case of error

Tools| ALE Administration| Services| Change Pointers| Reorganize

BD22, Report RBDCPCLR

CFP2 /n/sapapo/cq

Note Number 187455 533755

Generation and activation of integration models in batch Description of the delta logic or the program outdated

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

7 / 31

3.1.3 liveCache preparation Purpose During liveCache preparation. Procedure

PROCEDURE FOR LIVECACHE PREPARATION Step Task 1. Responsible Frequency Menu Path Transaction LC 10 |Integration | User data

Maintain password 'control' for DBM IM user 'control'

2.

Maintain password 'sap' for liveCache user 'SAPR3' / user SAP<LC-SID> if SCM 4.0 was built up by a new installation

IM

3.

Maintain IM /SAPAPO/DELETE_LC_ANCHORS in field 'Follow-up processing' of section 'Initialize liveCache'

4.

Flag checkbox 'Activate Alert Monitoring'

IM

Once (initial) Tools | APO * Administration liveCache/COM Routinen | Monitor | Integration | User data Once (initial) Tools | APO * Administration liveCache/COM Routinen | Monitor | Integration | User data Once (initial) Tools | APO * Administration liveCache/COM Routinen | Monitor | Integration | Administration report Once (initial) Tools | APO * Administration liveCache/COM Routinen | Monitor | Integration | Alert Monitoring

LC 10 |Integration | User data

LC 10 |Integration | Administration report

LC 10 |Integration | Alert Monitoring

Work Shop note: * Have to be done also when LiveCache are reinstalled or routine changed. 3.2 BW within APO Purpose schedule job for running weekly Procedure Schedule a job with the report SAP_ANALYZE_ALL_INFOCUBES weekly with an initial sample size of 10%. All other tables not related directly to APO must be

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

8 / 31

analyzed by the SAPDBA weekly as well. It is important to finish the SAPDBA analysis before report SAP_ANALYZE_ALL_INFOCUBES starts. Before you perform a refresh, please consider the following: 1. After the initial historical load or load of a significant amount of data, the optimizer statistics must be recalculated. 2. For small data loads, you do not have to analyze every load. These small loads will have little impact on the optimizer statistics. Since BRCONNECT 6.10 Patchlevel 11 you can use also this tool if you use Oracle as APO DB.
RELEVANT SAPNET NOTES Topic Report SAP_ANALYZE_ALL_INFOCUBES BW 2.0 Oracle features BRCONNECT for Oracle Increased memory consumption with Oracle 8 Performance problems/ Overview of Notes Oracle DB Statistics for BW tables CBO: Weekly scheduling with SAPDBA CBO: Parallel generation of optimizer statistics CBO: Statistics creation on partioned tables Note Number 421795 314719 428212 128221 354080 129252 132861 184513 336325

3.3

Software Maintenance Purpose <regularly or if recommended> Procedure <Description of how to install a new Patch and who is responsible> 1. Support Packages 2. Database Patch 3. SAP Kernel Patch 4. COM Routine Patch 5. liveCache Kernel Patch 6. Optimizer Patch 7. Frontend - OCX-Patch 8. Frontend SAPGUI Patch

RESPONSIBILITIES Patch Support Packages Responsible * How To Do Need to be updated at regular basis

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
Patch Database Patch SAP Kernel Patch liveCache Interface library (dbadaslib) COM Routine Patch liveCache Kernel Patch Optimizer Patch Frontend OCX Patch Frontend SAPGUI Patch Plug in

9 / 31

Version 0.4
Responsible * * * * * * * * * How To Do

Work Shop note: * AM are responsible to decide if we need this and tests after installation, IM are responsible for installation of these. 3.4 Monitoring

3.4.1 Application Log Purpose regularly check delete once a day Procedure The following table lists the necessary actions. Please plan background job for deleting application log periodically once a day.

MAINTANING APPLICATION LOG Task Responsibl Frequency e Weekly Monday (after forcast transfer) Weekly Monday (after forcast transfer) <once a day entries known entries older as one week> Sunday night Menu Path Tools|APO Administration|Integration| Monitor|Application Log|Display Entries Transaction /n/SAPAPO/C3

Display AM Application Log in APO System Display AM Application Log in R/3 Systems Delete AM / IM Application Log in APO System

APO Administration|Monitor|Application Log|Displa Entries

CFG1 or Transaction CIF | Monitoring| Application Log| Display Entries /SAPAPO/C6, Background job report /SAPAPO/RDELLOG

Tools|APO Administration|Monitor| Application Log|Delete Entries

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
Task Delete Application Log in R/3 Systems Responsibl Frequency e AM / IM <once a day known entreis older as one week> Sunday night <Initializatio n and if necessary>

10 / 31

Version 0.4
Menu Path Logistic| central Function|Supply Chain Planning Interface|Monitoring|Application Log|CFGD - Delete Entries Transaction CFGD or Background job report RDELALOG or CIF|Monitoring|Application Log|Delete Entries

Customizin g of Application Logging in APO System Customizin g of Application Logging in R/3 System Switch on Debugging Option in APO System Switch on Debugging Option in R/3 Systems

AM

Tools| APO Administration| Integration| Monitor|Application Log|Switch on System Logging

/SAPAPO/C41

AM

<Initializatio n and if necessary>

CFC2 or Transaction CIF| Monitoring|Settings|User Parameters

AM

AM

in special cases for analyzing application errors in special cases for analyzing application errors

/SAPAPO/C41

CFC2 or transaction CIF| Monitoring|Settings|User Parameters

3.4.2 liveCache Message Log Purpose Frequently or in emergency cases Procedure Every liveCache system message will stored in a log file called knldiag. You can check this file within the APO System with help of transaction LC10 | Problem Analysis | Messages | Kernel | Current. The knldiag file will be written wrap around. Pay attention that the knldiag file is renamed to knldiag.old during restart. For error analysis purpose it is important to save the knldiag file. On operating system level you will find the file in directory /sapdb/data/wrk/<SID>. In the case of a liveCache crash the knldiag and all other protocols will be moved into the directory specified in the parameter DIAG_HISTORY_PATH (liveCache 7.4) Another important log file is the knldiag.err. Every error is documented in this file. You can check this file also within APO System. In error cases it is important for analysis. It is located in the same directory like the knldiag file. In the case of a liveCache crash all message files and other important data needed for later analysis will be stored in a directory specified by the liveCache parameter DIAG_HISTORY_PATH.

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

11 / 31

Furthermore there exists the initialization protocol of liveCache. You have to check it after every initialization within APO System with help of transaction LC10. On Operating System Level you will find it in the directory /sapdb/<SID>/db as file lcinit.log. The following table lists the necessary actions.
SMAP TASK Task Check liveCache Initialization Protocol Responsible IM Frequency <after initialization> Menu Path Transaction LC10| liveCache: Monitoring| Problem Analysis| Logs | Operating LC10| liveCache: Monitoring| Problem Analysis| Messages | Kernel | Current LC10| liveCache: Monitoring| Problem Analysis| Messages | Kernel| Error

Check liveCache Kernel Log

IM

Check liveCache error log

IM, OS script every hour

Activate Kernel trace

IM

Tools| APO Administration| LiveCache/COM Routines| Monitor|liveCache: Monitoring| Problem Analysis| Logs | Operating <in error situation> Tools| APO Administration| Only when LiveCache/COM Routines| problem occurs Monitor|liveCache: Monitoring| Problem Analysis| Messages | Kernel Frequently, once Tools| APO Administration| every hour with LiveCache/COM Routines| script Monitor|liveCache: Monitoring| Problem Analysis| Messages | Kernel <only in coordination with SAP AG>

Work Shop note: SAP recommends to check LC10 every day by system administration (Capgemini, IM) 3.4.3 liveCache Monitoring Purpose Frequently Procedure For Monitoring liveCache issues you can use transaction LC10 in APO System. Database Manager DBMGUI on Operating System level The Database Manager consists of a server and a client part. The server part ( DBM server) is responsible for functionality. The client part consists of a graphical user interface, called the Database manager (DBMGUI), and a command line version, called the Database Manager (DBMCLI). Recommendation: Please do not use DBMGUI or DBMCLI for starting, stopping of liveCache. For recovery purposes use DBMGUI only for restoring Data Backup.

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

12 / 31

LIVECACHE

MONITORING TASKS Responsible IM, OS scripts Frequency <frequently> Every hours automaticly Menu Path Transaction LC10| liveCache:Monitoring| Problem Analysis| Messages| Kernel LC10| liveCache: Monitoring| Current Status| Memory Areas| Caches

Task System Error Messages

Data Cache IM, CCMS Utilization and Data Cache Hitrate

Check Data Volume filling level

IM, CCMS

Status, Size and number of Volumes,adding Volumes,Display Kernel parameters

IM, manually look

Check liveCache Initialization Protocol Check liveCache

IM

IM

Tools| APO Administration| LiveCache/COM Routines| liveCache:Monitoring| Problem Analysis| Messages| Kernel <frequently> Tools| APO Administration| Monitoring in LiveCache/COM Routines| CCMS. Critical liveCache: Monitoring| Current value 99,8. Send Status| Performance Overview e-mail before this value will overstep. <frequently> Tools| APO Administration| Monitoring in LiveCache/COM Routines| CCMS. Critiacal Current Status| Memory Areas | value 90%. Data Area <daily> Get the Tools| APO Administration| feeling about the LiveCache/COM Routines| database liveCache: Monitoring| trends. In the Configuration beginning 1/day after while 1/week. <after Tools| APO Administration| Initialization> LiveCache/COM Routines| liveCache: Monitoring| Problem Analysis| Logs| Operating <if necessary>

LC10| liveCache: Monitoring| Current Status| Memory Areas | Data Area LC10| liveCache: Monitoring| Current Status| Configuration

LC10| liveCache: Monitoring| Problem Analysis| Logs| Operating /SAPAPO/OM13

3.4.4 liveCache Data Volume Filling Level Purpose <frequently> Procedure Please check liveCache Data Volume Filling level carefully. Application errors may occur if the filling level is higher than 90%. The size of the liveCache Data Volumes should be al least 4* data cache size.

LIVECACHE

DATA VOLUME FILLING LEVEL Responsible IM Frequency <frequently> With CCMS, every hour. Critical value 90%. Menu Path Tools| APO Administration| LiveCache/COM Routines| liveCache: Monitoring| Current status| Memory Areas | Data Area Transaction LC10| liveCache: Monitoring| Current status| Memory Areas | Data Area

Task Check liveCache Data Volume Level

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
Task Add Data Volume Responsible IM

13 / 31

Version 0.4
Frequency <if necessary> Menu Path Tools| APO Administration| LiveCache/COM Routines| liveCache: Monitoring| Administration| Configuration| Volumes Transaction LC10| liveCache: Monitoring| Administration| Configuration| Volumes

3.4.5 liveCache Administration Log Purpose <Frequently> Procedure The reported actions are: - Changes in logmode of liveCache - Initializations - Recovery The table lists for each action the rows: start and end time, duration of an action, action, number of processed records for User, return code etc.
SMAP TASK Task Check history of liveCache Delete history of liveCache Responsible IM, Manually IM, batch jobb. Frequency <daily> in the evening CET <Monthly> batch jobb; Delete history 1/month. Delete data older than 3 month. Menu Path Transaction /n/sapapo/om11 /n/sapapo/om12

Work Shop note: Capgemini IM delete history 1/month. Delete data older than 3 month. 3.4.6 liveCache Heap Purpose <if necessary> Procedure For processing COM Routines liveCache uses Heap Memory. You have to limit this Heap Memory with help of liveCache parameter OMS_HEAP_LIMIT.

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

14 / 31

Determine the heap usage via LC10 | liveCache: Monitoring | Current Status | Memory Areas | Heap Usage . The sum SIZE value of the row size reflects the memory dynamically allocated for the liveCache heap from the operating system, which is not returned to the operating system until the liveCache stops. There has to be enough memory for heap , liveCache and perhaps other applications on this server. Pay attention if you use or plan to use AWE. A check of sizing could be useful. Maybe that it would be better to use a Unix (64 bit Operating) system. Pay attention if the sum of OMS_HEAP_LIMIT and Data Cache size is bigger than main memory of the liveCache server. With Windows there is a technical limit for process memory (3GB, even with AWE) You can check if there was COM Routine error in LC10| liveCache: Monitoring| Problem Analysis| Performance | OMS Monitor in tabstrip Entire View or by checking COM Traces.
MEMORY USAGE ON LIVECACHE SERVER Application Memory of Server Parameter OMS_HEAP_LIMIT How to evaluate Memory consumption in MB transaction OS07 if SAPOSCOL is installed for liveCache transaction LC10| liveCache: Monitoring| Only if COM routines are using Current Status| Configuration| Parameters | this much = High usage Current transaction LC10| liveCache: Monitoring| Check Heap_Usage = How Current Status|Memory Areas| Heap Usage much heap where used before last trun on/off on the server Task manager with Windows or Unix-specific tools

Reserved Heap Memory

Others

Work Shop note: Take a look at this transaction above to get a feeling about the system.
LIST OF SAPNET NOTES Topic Heap Memory Additional applications on the LiveCache server Initial parameterization of liveCache 7.4 Note Number 337445 392852 490958

3.4.7 Consistency Checks Purpose <Frequently and additionally after abnormal system events> Procedure Frequently check external consistency at least weekly down to daily if needed.
125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

15 / 31

After abnormal system events there may be inconsistencies - internal inconsistencies between APO DB and liveCache - external inconsistencies between the APO System and the dedicated systems. As a rule first check and restore internal and then check and restore external consistency.
SMAP TASK Task Responsible Frequency Initialisation and if there have been crash* Not relevant in MHC case Menu Path Transaction /SAPAPO/OM17

Check internal consistency AM / IM

For APO 3.0 only : Check internal consistency of resources Check internal consistency AM of DP data Repair DP data AM Check external consistency IM / AM

/SAPAPO/REST02

Report /SAPAPO/TS_LCM_CONS_CHECK_ALL Report /SAPAPO/TS_LCM_CONS_CHECK /SAPAPO/CCR or Report /sapapo/cif_deltareport3

Work Shop note: *If error occurs open OSS message immediately. **Application persons (Capgemini AM) are able to correct external inconsistency. System administrators (Capgemini IM) have to schedule deltareport3 weekly for example Sunday night and AM check this report as soon as possible Monday morning.

For additional information please use the best practice document Internal and External Consistency for SAP APO (3.x) / mySAP SCM (4.0), which can be found in service marketplace service.sap.com/scm -> Best Practices for Solution Management: mySAP SCM. Work Shop note:
Question arise which were the differences between the internal consistency check of transaction /sapapo/om17 and the report /SAPAPO/TS_LCM_CONS_CHECK_ALL. OM17 is only checking the table content between APO database and liveCache. The report also checks the anchors in the planning areas and the time series with the links in the liveCache on the character combinations.
LIST OF SAPNET NOTES Topic Description of consistency Checks Note Number 425825

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

16 / 31

3.5

liveCache Administration Tool Purpose <if necessary> Procedure There is a liveCache administration tool on operating system level called Database Manager (DBM). DBM works with Client/Server architecture. There are two user interfaces : - the graphical tool called DBMGUI, which is available on Windows Platforms only, - the command line oriented tool called DBMCLI.

After installing DBMGUI software on the frontend you can start DBMGUI. You can administer as much liveCache instances with one DBMGUI as you like. Every liveCache you want to administer has to be registered first. For that proceed as follows: 1. Start DBMGUI and choose in the menu Instance | Register instance ( Add .. as of DBMGUI 7.5 ) 2. Enter the name of the liveCache server and press Enter. You will get a list of all available liveCaches on this server. 3. Choose the liveCache instance . 4. Choose function Register 5. Enter a significant name for this liveCache. 6. Enter the name of the DBM user and his password. 7. Choose ok. The tool DBMCLI can be used from every frontend. The following table includes a list of useful DBMCLI commands.

DBMCLI OPTIONS Task show version show active tasks show tasks Storing DBM user data for DBMCLI using List of possible DBMCLI commands Option dbmcli -d <lC SID> -n <lChost> -u control,control show version dbmcli -d <lC SID> -n <lChost> -u control,control show active dbmcli -d <lC SID> -n <lChost> -u control,control show tasks dbmcli -d <lC SID> -n <lC host> -us control,control dbmcli -d <lc SID> -n <lC host>

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
Task Show DBROOT-Directory, liveCache Kernel versionand state execute an administration command Execute a SQL command Check AutoLog Status Switch On AutoLog Switch Off AutoLog Start liveCache Start liveCache to status Online (Warm) Stop or (Start) liveCache to status cold Stop liveCache to status offline

17 / 31

Version 0.4
Option dbmcli -d <lC SID> -n <lC host> db_enum dbmcli -d <lC SID> -n <lC host> -u <control user>, <password> <administration command> dbmcli -d <lC SID> -n <lC host> -uSQL <SQL userid,<password> sql_execute <SQL command> dbmcli -d <lC SID> -n <lC host> -u control,control autosave_show dbmcli -d <lC SID> -n <lC host> -u control,control autosave_start dbmcli -d <lC SID> -n <lC host> -u control,control autosave_stop dbmcli -d <lC SID> -n <lC host> -u control,control db_start dbmcli -d <lC SID> -n <lC host> -u control,control db_warm dbmcli -d <lC SID> -n <lC host> -u control,control db_cold dbmcli -d <lC SID> -n <lC host> -u control,control db_offline

3.5.1 Define a liveCache Backup Medium Purpose <if necessary> Procedure For defining a media call on your Windows client tool DBMGUI. 1) Choose from the menu of DBMGUI Instance | Configuration | Backup Media 2) Choose Media | New | Medium 3) Enter a significant media name 4) Enter the properties of this backup media. These are two steps. 5) Choose Extended for the next step. 6) Save the backup media. SAPNet Note 338903 describes how to configure using external backup tools with backint interface. Work Shop note: This are done in SCM installation project. Capgemini use external backup tool Legato for backup. 3.5.2 SQL Studio Purpose <once for configuration>

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

18 / 31

Procedure Please pay attention to notes 202344 and 386714. Work Shop note: SQL are not used in MHC SCM environment 3.5.3 Delete transactional simulations Purpose <frequently> Procedure For technical and business reasons it is recommended to schedule daily report /SAPAPO/OM_REORG_DAILY as described in SAPNet note 139558. For checking if there are old versions call transaction LC10 | liveCache: Monitor | Problem Analysis| Performance| OMS versions. There should be no versions older than 8 hours. Furthermore the report /SAPAPO/OM_DELETE_OLD_SIMSESS has to be scheduled every 30 minutes, see SAPNet Note 490992.

SMAP TASKS Task Schedule report /SAPAPO/OM_REORG_DAILY for background running Schedule report /SAPAPO/OM_DELETE_OLD_SIMSESS for background running Responsible IM Frequency Menu Path Transaction SM36 <daily> In the evening 03:00 <everey 30 minutes>

IM

SM36

3.6

Logging of liveCache 7.4 Purpose <configuration once > <check frequently> Background The size of Log Volumes is highly dependent of changing activity in liveCache. The default value is 2 GB. To avoid system standstill because of filled log Volume you should use AutoLog option which you can switch with help of DBMGUI. If Auto Log is switched on liveCache will automatically backup Log Volumes to predefined medium if a Log segment is filled up. By default Log Segment size is equal to 1/3 of Log size. This value should only be changed in contact with SAP AG.

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

19 / 31

3.7

Backup

3.7.1 Backup liveCache 7.4 Purpose <frequently>

Prcedure You can backup liveCache with help of DBMGUI. Before you can backup you have to define mediums as described above. The following tools are available: Report RSLVCBACKUP as of APO 3x, see SAPNote 455154 Transaction DB13C as of SCM 4x, see SAPNote 431508. There are different types of backups : Complete complete backup of data of liveCache Incremental incremental backup of changed data since last full backup of liveCache Log backup of Archive Log Area AutoLog after activation of this option there will be an automatic backup of every completed log segment. This option is recommended to avoid Log Full situations. 3.8 Verify of liveCache Purpose <after liveCache backup> Procedure Please follow the instructions in SAPNote 521870

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
SMAP TASK Task Verify of liveCache Responsible IM Frequency <Once per week during low system activity on test liveCache> In MHC case 1/month are enough

20 / 31

Version 0.4

Menu Path

Transaction Verify the backup once in month on a separate disk. Read note 521870 for further

LIST OF SAPNET NOTES Topic Consistency check (verify) of a liveCache Note Number 521870

Work Shop note: Verify the backup once in month on a separate disk. Read note 521870 for further information about this routine.

3.9

Initialization of liveCache Purpose After crash of liveCache only if no recovery is possible Procedure An initialization of the liveCache must be carried out only according to a recommendation and with help of SAP AG.

3.10

Recovery for liveCache 7.4

3.10.1 Recovery with liveCache 7.4 in case of a soft crash Purpose <after liveCache crash> Procedure For recovery purposes use DBMGUI and transaction LC10.

Step Stop data transfer from dedicated system Lock APO system against users

Task

Responsible IM IM

Comment OM17 OM17

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
Step Find out and solve the reason for the crash Start liveCache with LC10 Restart Data transfer Unlock APO user

21 / 31

Version 0.4
Task Responsible IM IM AM IM Comment OM17 OM17 OM17 OM17

3.10.2 Recovery with liveCache 7.4 in case of a hard crash Purpose <after liveCache crash> Procedure For recovery purposes use DBMGUI and transaction LC10.

SMAP TASKS Step Stop of data transfer from dedicated systems Lock APO System against users Start restore of data and log backups with help of DBMGUI in case of a disk crash Recovery of Logs or restore incremental backups Restart liveCache with help of transaction LC10 Unlock APO System Restart data transfer Task Responsible IM IM IM IM IM IM AM Comment OM17 OM17 OM17 OM17 OM17 OM17 OM17

3.11

Consistency check

Purpose Even after a recovery there could be internal and external inconsistencies in your System landscape. Procedure Before go live you have to start inconsistency checks based on SAPNote 425825. Work Shop note: Check the consistency after data load once at week.

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

22 / 31

3.12

Periodic Background Jobs Purpose <regularly> Procedure Use transaction SM36 for schedule background jobs.

BACKGROUND JOBS FOR MAINTENANCE OF APO SYSTEMS Function qRFC Outbound Alert Monitor qRFC Inbound Alert Monitor Delete Application Log Report /SAPAPO/RCIFQUEUECHECK /SAPAPO/RCIFINQUEUECKECK SBAL_DELETE Period Weekly Sunday night Weekly Sunday night weekly Follow SAP recommenda tion weekly Follow SAP recommenda tion daily - Follow SAP recommenda tion every 30 min System APO APO APO and R/3

Check consistency of Integration models (as of PI2002.1)

RCIFIMAX

R/3

Delete obsolete transactional simulations

/SAPAPO/OM_REORG_DAILY

APO

Delete obsolete transactional simulations without relations Delete obsolete Demand Job Logs older than 8 days

/ APO SAPAPO/OM_DELETE_OLD_SIMSESS /SAPAPO/TS_BATCH_LOGFILE Monthly APO last day in every month, Delete log 60 days and older

Work Shop note: Responsible to schedule this background jobs are AM. Capgemini AM and the SCM development project have to decide who will schedule this background jobs.

LIST OF SAPNET NOTES Topic R/3 Standard Jobs Demand Planning delete job logs Earlier deletion of hanging transactional simulations Scheduling report /SAPAPO/OM_REORG_DAILY Note Number 16083 512184 490992 139558

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

23 / 31

3.13

List of important APO transactions

IMPORTANT ADMINISTRATION TRANSACTIONS - R/3 SYSTEMS Topic Responsible Frequency <daily> Transaction; Menu Path Report qRFC Monitor outbound Definition and start of integration models, menu for qRFC monitor and application log qRFC stop selected outbound queue qRFC start selected outbound queue qRFC test and status of a selected outbound queue Display of all outgoing queues Customizing of Application Logging Display application log IM

<if necessary>

<if necessary> Weekly on Monday

SMQ1 CFM1, CFM6 or Logistic | Central Functions | Supply Chain Planning Interface | Integration Model SMQ1| Edit| Display selected RSTRFCQ1 queues| lock queues or stop immediately SMQ1|Edit | Display selected RSTRFCQ3 queues| restart or activate SMQ1 RSTRFCQ2

<if necessary> <once and if necessary> <daily>

CFS0 or CFS1 CFC6 or CIF|Monitoring| Settings| User parameters CFG1 or CIF| Monitoring| Application Log| Display entries CFGD or CIF|Monitoring| Application Log| Delete Entries CFC2 or CIF|Monitoring| Settings|User parameters SALE CFP2

Delete application log after checking Setting of Debugging Option Define and assign logical system to client Check data transfer channels

<daily>

RDELALOG

<if necessary> <in implementation phases> <frequently>

IMPORTANT ADMINISTRATION TRANSACTIONS - APO SYSTEM Topic qRFC Monitor outbound qRFC Stop selected Outbound queue qRFC Start selected Outbound queue qRFC test and status of a selected Outbound queue Responsible Frequency <daily> <if necessary> Transaction, Menu Path SMQ1 /SAPAPO/CQ SMQ1 Report

RSTRFCQ1

<if necessary>

SMQ1

RSTRFCQ3

IM

Weekly on Monday

RSTRFCQ2

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
Topic qRFC Alert monitor Display entries of application log Delete of Application log entries Customizing of Application logging Setting of Debugging Option in APO Check external consistency between APO and R/3 Systems Define and assign logical system to client Define Business system group Assign logical system to Business system group Define distribution scenario Generate/Delet e distribution definition Check data transfer channels Responsible Frequency <schedule for running every 15 minutes> Weekly only in R/3

24 / 31

Version 0.4
Transaction, Menu Path /SAPAPO/CW or Tools|APO Administration|Integration| Monitor|qRFC Alert /SAPAPO/C3 or Tools| APO Administration| Integration| monitor| Application Log| Display Entries Report / SAPAPO/RCIFQUEUECHEC K

<daily as background job> <Initialization and if necessary> <in case of error analyzing> <after detection of application errors, after recovery> <for initialization> <for initialization> <for initialization>

/SAPAPO/RDELLOG

/SAPAPO/C41 or Tools| APO Administration| Integration| Monitor| Application Log| Switch on System Logging /SAPAPO/C4 or Tools| APO Administration| Integration| Monitor| Application Log| Switch on System Logging /SAPAPO/CCR /SAPAPO/cif_deltareport3

SALE

/SAPAPO/C1

/SAPAPO/C2

<for initialization> <for initialization>

/SAPAPO/CP1

/SAPAPO/CP2

/SAPAPO/CQ

IMPORTANT ADMINISTRATION TRANSACTIONS - APO LIVECACHE Topic Responsible Frequency <if necessary> Transaction, Menu Path LC10| liveCache: Monitoring Report liveCache Administratio n (Starting, stopping, initialization)

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
Topic liveCache configuration such as parameters, Volumes Checking processes and Memory Managemen t Checking Version of COM routines Maintain liveCache connections Checking liveCache Connection, status, COM Routines Check internal consistency between APO DB and liveCache Delete anchor tables, copying master data back into live cache during initialization Display COM Trace file Maintain COM Trace level liveCache Data Browser Responsible Frequency <if necessary>

25 / 31

Version 0.4
Transaction, Menu Path LC10| liveCache: Monitoring| Current Status| Configuration Report

<daily> on Mondays

LC10| liveCache: Console

<if necessary>

/sapapo/OM13

<if necessary> <after installation, upgrade, Support Packages, Troubleshooti ng> <after detection of errors, after recovery>

LC10| lIntegration

/SAPAPO/OM13

<Integration Administrator>

TOOLS| APO Administration| / liveCache/COM Routines| SAPAPO/OM_LC_DB_SYNC_PREP Tools| liveCache ARE Consistency Check or /SAPAPO/OM17 LC10| liveCache< Create/Change or Delete Connection| liveCache Initialization| Processing /SAPAPO/delete_lc_anchors

<is to be maintained in the initialization procedure of liveCache, table DBCON> <if necessary>

<if necessary>

TOOLS|APO Administration| LiveCache/COM-Routines| Tools|Display Trace File or /SAPAPO/OM01 TOOLS|APO Administration| LiveCache/COM-Routines| Tools|Change Trace Level or /SAPAPO/OM02 TOOLS|APO Administration| LiveCache/COM-Routines| Tools|Data Browser or /SAPAPO/OM16

IMPORTANT ADMINISTRATION TRANSACTIONS - APO OPTIMIZER Topic Optimizer log Responsible Frequency <frequently such as weekly> Transation, Menu Path /SAPAPO/OPT11 Report

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
Topic Display user list on optimizers Display optimizer versions Display processes Maintain master data for optimization server Responsible

26 / 31

Version 0.4
Frequency <if necessary> <if necessary> <if necessary> <for initialization> Transation, Menu Path /SAPAPO/OPT03 /SAPAPO/OPT09 /SAPAPO/OPT12 SPRO|SAP Reference IMG| APO Implement Guide| Advanc Pl. a.Opti.|Basic Settings|Optimization| Basic Functions| Maintain Master Data for Parallel Optimization SPRO|SAP Reference IMG| APO Impl. Guide|Advanc Pl. a.Opti.|Basic Settings| Optimization|Basic Functions|Maintain Parameter for Parallel Optimization SPRO|SAP Reference IMG| APO Implement Guide| Advanc Pl. a.Opti.|Basic Settings|Optimization| Basic Functions| Maintain Global Settings or /SAPAPO/COPT00 SM59 Report

Maintain Parameter for Parallel Optimization

<for initialization>

Switch on checking of optimizer server availability

<if necessary>

Defining and Checking Optimizer RFC destinations

4.
4.1

qRFC
General qRFC Settings

4.1.1 Responsible Person in general

RESPONSIBLE PERSON Responsible Person Mikael Antonsson Paul Forsner ? Company Capgemini Capgemini MHC

4.1.2 qRFC Instance Parameter Settings Purpose After reconfiguring and regularly Procedure

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

27 / 31

The following table gives you some hints for gateway parameter settings. They are to maintain for every instance which is used by qRFC.

IMPORTANT GATEWAY PARAMETER Parameter gw/max_conn Meaning maximum number of allowd connections to a gateway of an instance maximum Swap Space of CPIC requests on gateway for R/3 >=4.6D maximum number of allowed CPIC connections to gateway for R/3 < 4.6D maximum number of connections to an application server maximium number of RFC connections in relation to rdisp/max_comm_entries in percent maximum number of dialog work processes, which are allowd to use for RFC in relation to sum of work processes number of workprocesses which are not allowd for sending RFC requests maximum number of allowd connection to an instance Default Value 100 Recommendation at least 1000 could be increased until 2000 25000000

gw/max_overflow_size

gw/max_shm_req

400

rdisp/max_comm_entries

2000

rdisp/rfc_max_comm_entries

90

rdisp/rfc_max_own_used_wp

75

rdisp/rfc_min_wait_dia_wp

at least 3*

rdisp/tm_max_no

2000

LIST OF SAPNET NOTES Topic Parameters for qRFC Optimal parameters for qRFC Note Number 384971 384077

Work Shop note: Implement this parameter settings above. *Value of workprcesses on R/3 system that will always be free for R/3 users. 4.1.3 RFC wait times Purpose <frequently> Procedure

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

28 / 31

Call transaction ST03 or ST03N to check if there are high wait times in tasktype RFC. High wait times for RFC or dialog task indicate that not enough work processes are available so that online users have to wait for free dialog work processes or that not enough work processes are available for RFC interfaces. In this cases it might be necessary no change the RFC parameter configuration or to add dialog work processes to the instance if possible. High wait times for tasktype RFC indicate a work process bottleneck. This could be resolved by reconfiguring the RFC resource parameters, adding more dialog work processes to the instance if possible or redistributing the RFC load to other instances or other times of the day.

SMAP TASK Task Check high wait times in RFC Responsible IM Frequency Weekly Wednesday Menu Path Transaction ST03 or ST03N

4.2

APO Monitoring of qRFC

4.2.1 Responsible Persons

RESPONSIBLE PERSON Responsible Person Mikael Antonsson Paul Forsner ? Company Capgemini Capgemini MHC

4.2.2 APO-Monitoring qRFC Outbound Queues Purpose Frequently and if there are problems in data transfer to external systems. Procedure Check qRFC Outbound Queue in APO System and R/3 Systems.

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
SMAP TASKS Task Checking APO qRFC Outbound Queues Responsible IM APO and R/3 Frequency Weekly before FCtransfer jobs. Exact time not decided (should be friday) <if necessary> <if necessary> Menu Path

29 / 31

Version 0.4

Transaction SMQ1

Tools | APO Administration | Monitor | qRFC Monitor

Stopping selected Outbound Queues Starting selected Outbound queues

IM/AM IM/AM

Tools | APO Administration | Monitor | qRFC Monitor Tools | APO Administration | Monitor | qRFC Monitor

SMQ1 SMQ1

If there more than one integration model there may be different qRFC Queues. You will identify APO queues by the naming convention. The name is starting with CF*. 4.2.3 APO-Monitoring qRFC Inbound Queues Purpose <initialization> Procedure As of PlugIn 2001.1 and APO Support Package 14 you can activate Inbound Queues. For registration of Inbound Queues use transaction SMQR. Default setting are: Maxtime 5 maxtime in seconds Nretry 30 number of retrys of scheduler Tdelay 300 delay between two tries

SMAP TASK Task Checking APO qRFC Inbound Queues Responsible IM - APO Frequency Weekly before FC-transfer jobs. Exact time not decided (should be friday) <if necessary> <if necessary> <if necessary> Menu Path Transaction SMQ2

Stopping selected Inbound Queues Starting selected Inbound queues Customize QIN Scheduler

IM/AM IM/AM AM

SMQ2 SMQ2 SMQR

LIST OF SAPNET NOTES Topic Activate Inbound Queues Note Number 416475

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20
Topic Configuration of QIN Scheduler Inbound Queues for Automotive SCM Queuemanager

30 / 31

Version 0.4
Note Number 369007 430725 419178

4.2.4 APO qRFC Alert Monitor Purpose Regularly Procedure

SMAP TASK Task Maintain variant for report /SAPAPO/RCIFQUEUECHECK Responsible Frequency AM <once during implementation and if necessary> <running period 15 min> <running period 15 min> Menu Path ABAP Workbench| Development| ABAP Editor| Variant create CCMS| Jobs| Definition Transaction SE38

Schedule background job for report /SAPAPO/RCIFQUEUECHECK Schedule background job for report /SAPAPO/RCIFINQUEUECHEC K Check protocols of this background job

IM

SM36, /sapapo/cw SM36

IM

AM

Weekly - Mondays

CCMS| Jobs| Maintenance

SM37

4.2.5 R/3 System Integration Model Generation and Activation Purpose <checking> Procedure For performance and administration handling reasons it is recommended to define separated integration models for master and transaction data. Therefore customer should have more than one integration model. Incremental data transfer of master data is basically controlled with the transaction CFC5 ( CFC9 as of PlugIn 2002.2 ). This transaction defines whether changes to material masters, customers and vendors are transferred to APO system immediately (in real-time, directly when updating data in the R/3 system), periodically or not at all. Depending on the amount of changes, the immediate data transfer may impact the performance of the system, so in many cases the periodic data transfer is preferred. However, settings for ALE change pointers must also be maintained if this method is

125224302.doc

System Maintenance SCM Mlnlycke Health Care MHC

2004-09-20 Version 0.4

31 / 31

used. Please maintain a list of all relevant Integration Models and their data in your dedicated R/3 Systems.

SMAP TASKS Task In R/3 System: Check Integration Models Responsible AM Frequency Menu Path Transaction

In R/3 System: Check period of scheduled job: RIMODGEN

AM

In R/3 System: Check period of scheduled job: RIMODAC2

AM

In R/3 System: AM Customizing of transfering of data changes

Logistics | Central CFM1, CFM2 Functions | Supply Chain Planning Interface | Core Interface Advanced Planner and Optimizer | Integr SE16, Table TBTCP, look for different variant of scheduled report RIMODGEN, or transaction SM37 SE16, Table TBTCP, look for different variant of scheduled report RIMODGEN, or transaction SM37 CFC5 ( CFC9 as of PlugIn 2002.2 )

4.3

Relevant SAPNet Notes

RELEVANT SAPNET NOTES Topic Queue status in SMQ1, SMQ2 and table ARFCRSTATE Note Number 378903

125224302.doc