Handbook System

Handbook
System Maintenance SCM

Mlnlycke Health Care MHC
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
3.4.3 liveCache Monitoring 11
3.4.4 liveCache 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
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 27
4.1.3 RFC wait times 28
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
Title
Date
Version
Change History
Version
Date
Changed by
Change
0.1
2004-08-25
Marta Birgisdottir
Firs draft
0.2
2004-08-31
Marta Birgisdottir
Update
0.3
2004-09-16
Marta Birgisdottir
Update after meeting between Capgemini AM and

IM.
0.4
2004-09-20
Marta Birgsdottir
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.1Document Purpose
The purpose of this document is to: Guide IM and AM in normal delivery,

actions to fulfil agreed SLAs
2.SMO: System Administration

2.1Questionnaire Topics / Session Content
Session Content
Description
Show Check
Introduction
Performance Management
System Management
Database Management
High Availability
Printing
Change Management
Security
APO
BW
CRM
SAP Technology Components
3.Advanced Planner and Optimizer (APO)

3.1APO Administration Responsible Persons
Responsible Person
Responsible Person
Company
Paul Forsner
Capgemini / IM
Anders strand
Capgemini / IM
Mikael Antonsson
Capgemini / AM
Michael Revensj
Capgemini / AM
System owner ?
MHC
3.1.1Install 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
Responsible
Frequency
Menu Path
Transaction
Check log
IM
Weekly
Tools| CCMS|Control/Monitoring|
OS07 | OS
Performance Menu|Operating system|
Collector
Remote|Activity|Goto|OS Collector
Via TNG
Tools | Control/Monitoring
RZ20
Using Alert
Monitor RZ20
IM
Daily
List of SAPNet notes

Topic
Notes
for Rel. <= 4.6 B

Install RFCOSCOL
202934
Using data collection agent SAPCCMSR
371023
Work Shop Note:

This RFCOSCOL have been installed by SCM installation project.
3.1.2Integration Models
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
Model
Logical System Application
Selected Data Transfer Method
of changings>
Work Shop note:

Link to document from Acando Frontec Integration model, responsible for that
are AM.
SMAP tasks
Task
Responsible
Frequency
Menu Path
Transaction
Check Integration
AM
Once in month / First
Logistics | Central
CFM4
Monday each month
Functions | Supply
Models
Chain Planning
Interface| Core
Interface APO |
Integration Model |
Display
Create Integration
AM
If necessary
Models
Logistics | Central
CFM1
Functions | Supply
Chain Planning
Interface| Core
Interface APO |
Integration Model |
Create
Activate Integration
AM
If necessary
Model
Logistics | Central
CFM2
Functions | Supply
Chain Planning
Interface| Core
Interface APO |
Integration Model |
Activate
Change Integration
Models
AM
If necessary
Logistics | Central
Functions | Supply
Chain Planning
Interface | Core
Interface APO|
Integration Model |
Change
CFM6
Task
Responsible
Frequency
Delete obsolete
AM
Have to start after
Integration Models
Check transfer
Menu Path
Report RIMODDEL
RIMODAC2 have finished

AM
When needed
CFC5 ( CFC9 as of
method
Backgound Jobs
PlugIn 2002.2 )
AM
Have to start after
RIMODGEN and
RCPTRAN4 have
RIMODAC2
finished
Activate Change
Transaction
AM
Pointers in general
SM37
This are done in MEP by
BD61
AF and are not needed in

SCP
Choose and adapt
AM
Message Types for
CIFMAT set in MEP, not
BD50
needed more in APO
transfering
Schedule data
AM
AF: veckovis i ny
CFP1, Report
transfer for Change
integrationsmodell genereras.
RCPTRAN4
Pointer Method
Fr att skicka ndringar p

material i den aktiva
integrationsmodellen.Krning
gr frslagsvis lrdag morgon.
AF bestller av CAP
Reorganize Change
AM
Pointers
<weekly obsolete
change pointers
which are older than
14 days>Weekly after
Tools| ALE
BD22, Report
Administration|
RBDCPCLR
Services| Change
Pointers| Reorganize
RIMODDEL are finished

Check data transfer
IM, AM
Weekly - Mondays
CFP2
IM, AM
In case of error
/n/sapapo/cq
channels in R/3
Check data transfer
channels in APO
List of SAPNet Notes

Topic
Note Number
Generation and activation of integration models in batch
187455
Description of the delta logic or the program
533755
outdated
3.1.3liveCache preparation
Purpose
During liveCache preparation.
Procedure
Procedure for liveCache Preparation

Step Task
Responsible
Frequency
Menu Path
Transaction
1.
IM
Once
Tools | APO
LC 10 |Integration
(initial) *
Administration
| User data
Maintain password 'control' for DBM

user 'control'
liveCache/COM
Routinen |
Monitor |
Integration |
User data
2.
Maintain password 'sap' for liveCache IM
Once
Tools | APO
LC 10 |Integration
user 'SAPR3'
(initial) *
Administration
| User data
/ user SAP<LC-SID> if SCM 4.0 was
liveCache/COM
built up by a new installation
Routinen |
Monitor |
Integration |
User data
3.
Maintain
Once
Tools | APO
LC 10 |Integration
(initial) *
Administration
| Administration
in field 'Follow-up processing' of
liveCache/COM
report
section 'Initialize liveCache'
Routinen |
/SAPAPO/DELETE_LC_ANCHORS
IM
Monitor |
Integration |
Step Task
Responsible
Frequency
Menu Path
Transaction
Administration
report
4.
Flag checkbox 'Activate Alert

Monitoring'
IM
Once
Tools | APO
LC 10 |Integration
(initial) *
Administration
| Alert Monitoring
liveCache/COM
Routinen |
Monitor |
Integration |
Alert Monitoring
Work Shop note:

* Have to be done also when LiveCache are reinstalled or routine changed.
3.2BW 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 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
Note Number
Report SAP_ANALYZE_ALL_INFOCUBES
421795
BW 2.0 Oracle features
314719
BRCONNECT for Oracle
428212
Topic
Note Number
Increased memory consumption with Oracle 8
128221
Performance problems/ Overview of Notes
354080
Oracle DB Statistics for BW tables
129252
CBO: Weekly scheduling with SAPDBA
132861
CBO: Parallel generation of optimizer statistics
184513
CBO: Statistics creation on partioned tables
336325
3.3Software 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
Responsible
How To Do
Support Packages
Need to be updated
at regular basis
Patch
Responsible
How To Do
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
Work Shop note:

* AM are responsible to decide if we need this and tests after installation, IM
are responsible for installation of these.
3.4Monitoring
3.4.1Application 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
Responsible Frequency
Menu Path
Display
AM
Tools|APO Administration|Integration|Monitor| /n/SAPAPO/C3
Weekly
Transaction
Task
Application
Monday (after
Log in APO
forcast transfer)
Menu Path
Transaction
Application Log|Display Entries
System
Display
AM
Weekly
APO Administration|Monitor|Application Log|
CFG1 or Transaction CIF |
Application
Monday (after
Displa Entries
Monitoring| Application Log|
Log in R/3
forcast transfer)
Display Entries
Systems
Delete
AM / IM
Application
Log in APO
System
<once a day
entries known
entries older
as one week>
Tools|APO Administration|Monitor|Application /SAPAPO/C6, Background

Log|Delete Entries
job report
/SAPAPO/RDELLOG
Sunday night
Delete
AM / IM
Application
Log in R/3
Systems
<once a day
known entreis
older as one
week>
Logistic| central Function|Supply Chain
CFGD or Background job
Planning Interface|Monitoring|Application
report RDELALOG or CIF|
Log|CFGD - Delete Entries
Monitoring|Application Log|
Delete Entries
Sunday night
Customizing AM
of
Application
<Initialization
and if
necessary>
Tools| APO Administration| Integration|
/SAPAPO/C41
Monitor|Application Log|Switch on System

Logging
Logging in
APO
System
<Initialization
and if
necessary>
CFC2 or Transaction CIF|
AM
in special
cases for
analyzing
application
errors
/SAPAPO/C41
AM
in special
cases for
CFC2 or transaction CIF|
Customizing AM
of
Application
Monitoring|Settings|User
Parameters
Logging in
R/3 System
Switch on
Debugging
Option in
APO
System
Switch on
Debugging
Monitoring|Settings|User
Task
Menu Path
analyzing
application
errors
Option in
R/3 Systems
Transaction
Parameters
3.4.2liveCache 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.
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
Responsible
Frequency
Menu Path
Transaction
Check liveCache
IM
<after
initialization>
Tools| APO Administration|
LC10| liveCache:
LiveCache/COM Routines|
Monitoring|
Monitor|liveCache: Monitoring|
Problem Analysis|
Problem Analysis| Logs |
Logs | Operating
Initialization
Protocol
Task
Responsible
Frequency
Menu Path
Transaction
Operating
Check liveCache
IM
Kernel Log
<in error
situation> Only
LC10| liveCache:
Monitoring|
when problem
Problem Analysis|
occurs
Problem Analysis| Messages |
Messages | Kernel
Kernel
| Current
Check liveCache
IM, OS script
Frequently, once
LC10| liveCache:
error log
every hour
every hour with
Monitoring|
script
Problem Analysis|
Problem Analysis| Messages |
Messages | Kernel|
Kernel
Error
Activate Kernel
IM
trace
<only in
coordination
with SAP AG>
Work Shop note:

SAP recommends to check LC10 every day by system administration
(Capgemini, IM)
3.4.3liveCache 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.
liveCache Monitoring Tasks

Task
Menu Path
Transaction
System Error
IM, OS
<frequently> Every
LC10|
Messages
scripts
hours automaticly
liveCache:Monitoring|
liveCache:Monitoring| Problem
Problem Analysis|
Analysis| Messages| Kernel
Messages| Kernel
<frequently> Monitoring
LC10| liveCache:
Utilization and
in CCMS. Critical value
Monitoring| Current
Data Cache
99,8. Send e-mail before
liveCache: Monitoring| Current
Status| Memory
Hitrate
this value will overstep.
Status| Performance Overview
Areas| Caches
Data Cache
IM, CCMS
<frequently> Monitoring
LC10| liveCache:
Volume filling
in CCMS. Critiacal value
Monitoring| Current
level
90%.
Current Status| Memory Areas | Status| Memory Areas
Check Data
IM, CCMS
Data Area
| Data Area
Status, Size and
IM, manually
<daily> Get the feeling
LC10| liveCache:
number of
look
about the database
Monitoring| Current
Volumes,adding
trends. In the beginning
liveCache: Monitoring|
Status| Configuration
Volumes,Display
1/day after while 1/week.
Configuration
<after Initialization>
Kernel
parameters
Check liveCache IM
LC10| liveCache:
Initialization
Monitoring| Problem
Protocol
liveCache: Monitoring| Problem Analysis| Logs|

Analysis| Logs| Operating
Check liveCache IM
<if necessary>
Operating
/SAPAPO/OM13
3.4.4liveCache 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

Task
Check liveCache
IM
Data Volume Level
Menu Path
Transaction
<frequently>With
LC10| liveCache:
CCMS, every hour.
Monitoring| Current
Critical value 90%.
liveCache: Monitoring| Current
status| Memory
status| Memory Areas | Data
Areas | Data Area
Area
Add Data Volume
IM
<if necessary>
LC10| liveCache:
Monitoring|
liveCache: Monitoring|
Administration|
Administration| Configuration|
Configuration|
Volumes
Volumes
3.4.5liveCache 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
Responsible
Frequency
Check history of liveCache
IM, Manually
<daily> in the
Menu Path
Transaction
/n/sapapo/om11
evening CET
Delete history of liveCache
IM, batch jobb.
<Monthly> batch
jobb; Delete history
1/month. Delete
data older than 3
month.
/n/sapapo/om12
Work Shop note:

Capgemini IM delete history 1/month. Delete data older than 3 month.
3.4.6liveCache 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.
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
How to evaluate
Memory of Server
transaction OS07 if SAPOSCOL is installed for
Memory consumption in MB
liveCache
Parameter OMS_HEAP_LIMIT transaction LC10| liveCache: Monitoring|
Current Status| Configuration| Parameters |
Only if COM routines are using

this much = High usage
Current
Reserved Heap Memory
transaction LC10| liveCache: Monitoring|

Current Status|Memory Areas| Heap Usage
Check Heap_Usage = How

much heap where used before
Application
How to evaluate
Memory consumption in MB
last trun on/off on the server
Others
Task manager with Windows or Unix-specific

tools
Work Shop note:

Take a look at this transaction above to get a feeling about the system.
Topic
Note Number
Heap Memory
337445
Additional applications on the LiveCache server
392852
Initial parameterization of liveCache 7.4
490958
3.4.7Consistency Checks
Purpose
<Frequently and additionally after abnormal system events>
Procedure
Frequently check external consistency at least weekly down to daily if needed.
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
Check internal consistency AM / IM
Frequency
Initialisation
and if there
have been
Menu
Path
Transaction
/SAPAPO/OM17
Task
Responsible
Frequency
Menu
Path
Transaction
crash*
For APO 3.0 only :
/SAPAPO/REST02
Report
Check internal consistency

of resources
Check internal consistency AM
of DP data
/SAPAPO/TS_LCM_CONS_CHECK_ALL
Repair DP data
AM
Report /SAPAPO/TS_LCM_CONS_CHECK
Check external
IM / AM
Not relevant
/SAPAPO/CCR or Report
in MHC
/sapapo/cif_deltareport3
consistency
case
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.
Topic
Description of consistency Checks
Note Number
425825
3.5liveCache 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
Option
show version
dbmcli -d <lC SID> -n <lChost> -u control,control show

version
show active tasks

active
Task
Option
show tasks

tasks
Storing DBM user data for DBMCLI using
dbmcli -d <lC SID> -n <lC host> -us control,control
List of possible DBMCLI commands
dbmcli -d <lc SID> -n <lC host>
Show DBROOT-Directory, liveCache Kernel
dbmcli -d <lC SID> -n <lC host> db_enum
versionand state
execute an administration command
dbmcli -d <lC SID> -n <lC host> -u <control user>,

<password> <administration command>
Execute a SQL command
dbmcli -d <lC SID> -n <lC host> -uSQL <SQL

userid,<password> sql_execute <SQL command>
Check AutoLog Status
dbmcli -d <lC SID> -n <lC host> -u control,control

autosave_show
Switch On AutoLog

autosave_start
Switch Off AutoLog

autosave_stop
Start liveCache

db_start
Start liveCache to status Online (Warm)

db_warm
Stop or (Start) liveCache to status cold

db_cold
Stop liveCache to status offline

db_offline
3.5.1Define 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.2SQL Studio
Purpose
<once for configuration>
Procedure
Please pay attention to notes 202344 and 386714.
Work Shop note:
SQL are not used in MHC SCM environment
3.5.3Delete 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
IM
Schedule report
/SAPAPO/OM_DELETE_OLD_SIMSESS
for background running
IM
<daily> In the
Menu
Path
Transaction
SM36
SM36
evening 03:00
<everey 30
minutes>
3.6Logging 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.
3.7Backup
3.7.1Backup 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.8Verify of liveCache
Purpose
<after liveCache backup>
Procedure
Please follow the instructions in SAPNote 521870
SMAP Task
Task
Responsible
Verify of liveCache IM
Frequency
Menu Path Transaction
<Once per week during low system

activity on test liveCache> In MHC case
Verify the
1/month are enough
in month on a
backup once
separate disk.
Read note
521870 for
further

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.9Initialization 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.10Recovery for liveCache 7.4
3.10.1Recovery with liveCache 7.4 in case of a soft crash
Purpose
<after liveCache crash>
Procedure
For recovery purposes use DBMGUI and transaction LC10.
Step
Task
Responsible
Comment
Stop data transfer from dedicated system
IM
OM17
Lock APO system against users
IM
OM17
Find out and solve the reason for the crash
IM
OM17
Start liveCache with LC10
IM
OM17
Restart Data transfer
AM
OM17
Unlock APO user
IM
OM17
3.10.2Recovery 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
Task
Responsible
Comment
Stop of data transfer from dedicated systems
IM
OM17
Lock APO System against users
IM
OM17
Start restore of data and log backups with help of DBMGUI

in case of a disk crash
IM
OM17
Recovery of Logs or restore incremental backups
IM
OM17
Restart liveCache with help of transaction LC10
IM
OM17
Unlock APO System
IM
OM17
Restart data transfer
AM
OM17
3.11Consistency 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.
3.12Periodic Background Jobs
Purpose
<regularly>
Procedure
Use transaction SM36 for schedule background jobs.
Background Jobs for Maintenance of APO Systems

Function
Report
Period
System
qRFC Outbound Alert /SAPAPO/RCIFQUEUECHECK

Monitor
Weekly
APO
qRFC Inbound Alert

Monitor
/SAPAPO/RCIFINQUEUECKECK
Weekly
Delete Application
Log
SBAL_DELETE
Sunday night
APO
Sunday night
weekly
APO and
Follow SAP
R/3
recommendation
Check consistency of RCIFIMAX

Integration models (as
of PI2002.1)
weekly -
Delete obsolete
transactional
simulations
/SAPAPO/OM_REORG_DAILY
daily - Follow
Delete obsolete
transactional
simulations without
relations
/SAPAPO/OM_DELETE_OLD_SIMSESS every 30 min
APO
Delete obsolete
Demand Job Logs
older than 8 days
/SAPAPO/TS_BATCH_LOGFILE
APO
R/3
Follow SAP
recommendation
APO
SAP
recommendation
Monthly last
day in every
month, Delete
Function
Report
Period
System
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.

Topic
Note Number
R/3 Standard Jobs
16083
Demand Planning delete job logs
512184
Earlier deletion of hanging transactional simulations
490992
Scheduling report /SAPAPO/OM_REORG_DAILY
139558
3.13List of important APO transactions

Important Administration Transactions - R/3 Systems
Topic
Responsible
Frequency
Transaction; Menu Path
qRFC Monitor outbound
<daily>
SMQ1
Definition and start of
CFM1, CFM6 or Logistic |
integration models,
Central Functions | Supply
menu for qRFC monitor
Chain Planning Interface |
and application log
Integration Model
qRFC stop selected

outbound queue
<if necessary>
SMQ1| Edit| Display selected

queues| lock queues or stop
immediately
Report
RSTRFCQ1
Topic
Responsible
Frequency
Transaction; Menu Path
Report
qRFC start selected
<if necessary>
SMQ1|Edit | Display selected
RSTRFCQ3
outbound queue
queues| restart or activate
qRFC test and status of IM
Weekly on Monday
SMQ1
<if necessary>
CFS0 or CFS1
<once and if
necessary>
CFC6 or CIF|Monitoring|
<daily>
CFG1 or CIF| Monitoring|
RSTRFCQ2
a selected outbound
queue
Display of all outgoing
queues
Customizing of
Application Logging
Display application log
Settings| User parameters
Application Log| Display

entries
Delete application log
<daily>
CFGD or CIF|Monitoring|
after checking
RDELALOG
Application Log| Delete

Entries
Setting of Debugging
<if necessary>
Option
CFC2 or CIF|Monitoring|
Settings|User parameters
Define and assign
<in
implementation
phases>
SALE
<frequently>
CFP2
logical system to client
Check data transfer

channels
Important Administration Transactions - APO System

Topic
Transaction, Menu Path
qRFC Monitor
SMQ1
<daily>
outbound
qRFC Stop
selected
Report
/SAPAPO/CQ
<if
SMQ1
RSTRFCQ1
Topic
Report
SMQ1
RSTRFCQ3
necessary>
Outbound queue
qRFC Start
<if
necessary>
IM
Weekly on
selected
Outbound queue
qRFC test and
status of a
RSTRFCQ2
Monday
selected
Outbound queue
qRFC Alert
monitor
Display entries
of application
<schedule for
running every
15 minutes>
/SAPAPO/CW or Tools|APO
Weekly only in
/SAPAPO/C3 or Tools| APO
R/3
Administration| Integration| monitor|
log
Delete of
Alert
Application Log| Display Entries
<daily as
background
job>
<Initialization
and if
necessary>
Application log
entries
Customizing of
/SAPAPO/RCIFQUEUECHECK
Administration|Integration|Monitor|qRFC
Application
logging
/SAPAPO/RDELLOG

Administration| Integration| Monitor|
Application Log| Switch on System
Logging
Setting of
Debugging
Option in APO
<in case of
error
analyzing>

Administration| Integration| Monitor|
Application Log| Switch on System
Logging
Check external
consistency
between APO
and R/3
Systems
<after
detection of
application
errors, after
recovery>
/SAPAPO/CCR
/SAPAPO/cif_deltareport3
Topic
Define and
<for
initialization>
SALE
<for
initialization>
/SAPAPO/C1
<for
initialization>
/SAPAPO/C2
<for
initialization>
/SAPAPO/CP1
<for
initialization>
/SAPAPO/CP2
/SAPAPO/CQ
assign logical
Report
system to client
Define Business
system group
Assign logical
system to
Business system
group
Define
distribution
scenario
Generate/Delete
distribution
definition
Check data
transfer
channels
Important Administration Transactions - APO liveCache

Topic
Responsible
Frequency
liveCache
<if necessary>
LC10| liveCache: Monitoring
<if necessary>
LC10| liveCache: Monitoring|
Administration
(Starting,
stopping,
initialization)
liveCache
configuration
such as
parameters,
Volumes
Current Status| Configuration
Report
Topic
Responsible
Frequency
Checking
<daily> on
LC10| liveCache: Console
processes
Mondays
Report
and Memory
Management
Checking
<if necessary>
/sapapo/OM13
<if necessary>
LC10| lIntegration
<after
installation,
upgrade, Support
Packages,
Troubleshooting>
Version of
COM routines
Maintain
liveCache
connections
Checking
liveCache
Connection,
status, COM
Routines
Check internal
consistency
between APO
<Integration
<after detection
Administrator> of errors, after
recovery>
DB and
/SAPAPO/OM13
TOOLS| APO Administration|
/SAPAPO/OM_LC_DB_SYNC_P
liveCache/COM Routines| Tools|

liveCache Consistency Check or
/SAPAPO/OM17
liveCache
Delete anchor
tables,
copying
master data
back into live
cache during
<is to be
maintained in the
initialization
procedure of
liveCache, table
DBCON>
LC10| liveCache<
<if necessary>
TOOLS|APO Administration|
Create/Change or Delete
Connection| liveCache
Initialization| Processing
initialization
Display COM
Trace file
LiveCache/COM-Routines|
Tools|Display Trace File or
/SAPAPO/OM01
Maintain COM
Trace level
<if necessary>
Tools|Change Trace Level or
/SAPAPO/OM02
/SAPAPO/delete_lc_anchors
Topic
Responsible
Frequency
liveCache
Data Browser
Report
Tools|Data Browser or
/SAPAPO/OM16
Important Administration Transactions - APO Optimizer

Topic
Responsible
Frequency
Transation, Menu Path
Optimizer log
<frequently such as
weekly>
/SAPAPO/OPT11
Display user list on
<if necessary>
/SAPAPO/OPT03
Display optimizer versions
<if necessary>
/SAPAPO/OPT09
Display processes
<if necessary>
/SAPAPO/OPT12
Maintain master data for
<for initialization>
SPRO|SAP Reference IMG|
optimizers
optimization server
APO Implement Guide|

Advanc Pl. a.Opti.|Basic
Settings|Optimization| Basic
Functions| Maintain Master
Data for Parallel
Optimization
Maintain Parameter for
<for initialization>
Parallel Optimization

APO Impl. Guide|Advanc Pl.
a.Opti.|Basic Settings|
Optimization|Basic
Functions|Maintain
Parameter for Parallel
Optimization
Switch on checking of
<if necessary>
Report
Topic
Responsible
Frequency
optimizer server availability
Transation, Menu Path
Report
APO Implement Guide|

Advanc Pl. a.Opti.|Basic
Settings|Optimization| Basic
Functions| Maintain Global
Settings or
/SAPAPO/COPT00
Defining and Checking
SM59
Optimizer RFC destinations
4.qRFC
4.1General qRFC Settings
4.1.1Responsible Person in general
Responsible Person
Responsible Person
Company
Mikael Antonsson
Capgemini
Paul Forsner
Capgemini
MHC
4.1.2qRFC Instance Parameter Settings
Purpose
After reconfiguring and regularly
Procedure
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
Meaning
Default
Value
Recommendation
gw/max_conn
maximum number of
allowd connections to a
gateway of an instance
at least 1000 could be

increased until 2000
gw/max_overflow_size
maximum Swap Space of

CPIC requests on
gateway for R/3 >=4.6D
25000000
gw/max_shm_req
maximum number of
allowed CPIC
connections to gateway
for R/3 < 4.6D
400
rdisp/max_comm_entries
maximum number of
connections to an
application server
100
2000
rdisp/rfc_max_comm_entries maximium number of

90
RFC connections in
relation to
rdisp/max_comm_entries
in percent
rdisp/rfc_max_own_used_wp maximum number of

dialog work processes,
which are allowd to use
for RFC in relation to
sum of work processes
75
rdisp/rfc_min_wait_dia_wp
number of workprocesses 1
which are not allowd for
sending RFC requests
at least 3*
rdisp/tm_max_no
maximum number of
allowd connection to an
instance
2000

Topic
Note Number
Parameters for qRFC
384971
Optimal parameters for qRFC
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.3RFC wait times
Purpose
<frequently>
Procedure
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
Responsible
Frequency
Check high wait times in RFC
IM
Weekly Wednesday
4.2APO Monitoring of qRFC
Menu Path
Transaction
ST03 or ST03N
4.2.1Responsible Persons
Responsible Person
Responsible Person
Company
Mikael Antonsson
Capgemini
Paul Forsner
Capgemini
MHC
4.2.2APO-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.
SMAP tasks
Task
Responsible
Frequency
Menu Path
Transaction
Checking APO qRFC
IM
Weekly
Tools | APO Administration |
SMQ1
APO and R/3
before FC-
Monitor | qRFC Monitor
Outbound Queues
transfer jobs.
Exact time not
decided
(should be
friday)
Stopping selected Outbound
IM/AM
Queues
Starting selected Outbound
queues
IM/AM
<if
necessary>
<if
necessary>
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.3APO-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
Responsible
Frequency
Menu Path
Checking APO qRFC Inbound Queues
IM - APO
Weekly before
Transaction
SMQ2
FC-transfer jobs.
Exact time not
decided (should
be friday)
Stopping selected Inbound Queues
IM/AM
<if
necessary>
SMQ2
Starting selected Inbound queues
IM/AM
<if
necessary>
SMQ2
Customize QIN Scheduler
AM
<if
necessary>
SMQR
List of SAPNet notes

Topic
Note Number
Activate Inbound Queues
416475
Configuration of QIN Scheduler
369007
Topic
Note Number
Inbound Queues for Automotive
430725
SCM Queuemanager
419178
4.2.4APO qRFC Alert Monitor
Purpose
Regularly
Procedure
SMAP task
Task
Responsible
Frequency
Menu Path
Transaction
Maintain variant for report
AM
<once during
implementation
and if
necessary>
ABAP Workbench|
SE38
<running period
15 min>
CCMS| Jobs|
SM36,
Definition
/sapapo/cw
Schedule background job for report IM

/SAPAPO/RCIFINQUEUECHECK
<running period
15 min>
Check protocols of this background AM
Weekly - Mondays
Schedule background job for report IM
job
Development|
ABAP Editor|
Variant create
SM36
CCMS| Jobs|
SM37
Maintenance
4.2.5R/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 used.
Please maintain a list of all relevant Integration Models and their data in your
dedicated R/3 Systems.
SMAP tasks
Task
Responsible
Frequency
Menu Path
Transaction
In R/3 System: Check

Integration Models
AM
Logistics | Central CFM1, CFM2

Functions | Supply
Chain Planning
Interface | Core
Interface
Advanced Planner
and Optimizer |
Integr

period of scheduled
job: RIMODGEN
AM
SE16, Table TBTCP,

look for different
variant of scheduled
report RIMODGEN,
or transaction SM37

period of scheduled
job: RIMODAC2
AM
SE16, Table TBTCP,

look for different
variant of scheduled
report RIMODGEN,
or transaction SM37
In R/3 System:
Customizing of
transfering of data
changes
AM
CFC5 ( CFC9 as of
PlugIn 2002.2 )
4.3Relevant SAPNet Notes

Relevant SAPNet Notes
Topic
Queue status in SMQ1, SMQ2 and table ARFCRSTATE
Note Number
378903

Handbook System

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

Handbook System

Uploaded by

Copyright:

Available Formats

Handbook

System Maintenance SCM

3.10.1 Recovery with liveCache 7.4 in case of a soft crash 20

Update after meeting between Capgemini AM and

Update after input from Acando Frontec

Document Reviews and Audits

The purpose of this document is to: Guide IM and AM in normal delivery,

2.SMO: System Administration

SAP Technology Components

3.Advanced Planner and Optimizer (APO)

Performance Menu|Operating system|

List of SAPNet notes

for Rel. <= 4.6 B

Using data collection agent SAPCCMSR

Work Shop Note:

Logical System Application

Selected Data Transfer Method

<Immediately, Change Pointers,no transfer

Logical System Application

Selected Data Transfer Method

Work Shop note:

Once in month / First

Monday each month

Have to start after

RIMODAC2 have finished

Have to start after

This are done in MEP by

AF and are not needed in

Choose and adapt

Message Types for

CIFMAT set in MEP, not

needed more in APO

transfer for Change

Fr att skicka ndringar p

RIMODDEL are finished

List of SAPNet Notes

Generation and activation of integration models in batch

Description of the delta logic or the program

Procedure for liveCache Preparation

Maintain password 'control' for DBM

Maintain password 'sap' for liveCache IM

/ user SAP<LC-SID> if SCM 4.0 was

built up by a new installation

in field 'Follow-up processing' of

section 'Initialize liveCache'

Flag checkbox 'Activate Alert

Work Shop note:

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

SAP Kernel Patch

liveCache Interface library (dbadaslib)

COM Routine Patch

liveCache Kernel Patch

Frontend OCX Patch

Frontend SAPGUI Patch

Work Shop note:

Maintaning Application Log

Tools|APO Administration|Integration|Monitor| /n/SAPAPO/C3