Computing Center Management System (CCMS)#

Work Processes

Data Transfer

TemSe#

SAP Help
Parameter rspo/store_location controls where TemSe stores data from R/3 spool.
If not in "db", then it is generally stored under /usr/sap/<SYSTEM ID>/SYS/global/

SP11	Display TemSe objects
SP12	Managing TemSe objects

Every TemSe object consists of a header entry in table TST01 and the actual object. This can be stored in the file system (for example, job logs) or in table TST03 (for example, HR data).
NOTE: TemSe names must not contain a minus sign "-", see note 2057539 !

There are the following different TemSe objects.

AUDIT_*	Audit Informationssystem Datenexporte
BDCLG*	Batch Input Protokolle
DTA*	Datenträgeraustausch
HR*	Zwischendaten der Personalverwaltung
JOBLG*	Protokolle der Hintergrundverarbeitung
PK*	Pensionskasse Schweiz
SPOOL*	Daten zu Spool-Aufträgen
TEST*	Testdaten
TESTGRP*	benutzerübergreifende Testdaten
TESTOCL*	mandantenübergreifende Testdaten
TESTOWN*	persönliche Testdaten

r.RPUBVTA0	Download TemSe - PC/Server, SV-Beitragsnachweisung AT
r.RPUTSVD0	Content of TemSe
r.RSBTCDEL	Delete Job logs
r.RSTS0020	TemSe-Daten Konsistenzprüfung (= SP12 > Menu > TemSe-Datenablage > Konsistenzprüfung)
r.RSTS0030	TemSe-Objektüberprüfung
r.RSTS0022	Delete TemSe object
r.RPUTSR00	Löschen HR* Objekte (Note 98995) mit x.PE03>TEMSE (siehe Doku)

XRTAB errors
like XRTAB&2&128&TST03 = Datenbankfehler: TemSe->XRTAB(2)->128 bei Tabelle TST03 Schlüssel
is described in Note 67055

0	RT_READ_ONLY
1	RT_READ_FOR_UPDATE
2	RT_INSERT
3	RT_UPDATE
4	RT_DELETE

1	Sql error
2	Parameter error
4	internal error in rtab
8	memory alloc failed
16	output buffer too small
32	Table not found
64	key not found /no more recs
128	duplicate key

TSP*	=> Spool problem
TST*	=> TemSe problem

Jobs #

• Menu > System > Services > Jobs > ...
• SAP Menu > Tools > CCMS > Background Processing > ...
• Transactions:

RZ01	Gantt-chart Job Overview (Job Scheduling Monitor)
RZ03	Server Status & Alerts
RZ04	Setup
SM36	Define (Create) Job (Wizard is here also)
SM37	Job Overview + Maintenance (filter first via "Simple" or "Extended" Job Selection)
SM64	Triggering events manually
SMX	My Own Jobs
SPAD	Manage Spool/Print Devices
SPIC	Installationsprüfung Spool (4.7)
r.RSPO0055	Installationsprüfung Spool
r.RSPFPAR_SPOOL	Spool Parameters
SP01O	Spool-Steuerung
SP02	Anzeigen von Spool-Aufträgen
SPAT	Spooladministration (Test)
SPOV	Übersicht Spoolaufträge
RZ20	CCMS Monitor Sets (use "SAP CCMS Monitor Templates" > Background Processing > Ctrl+F10)
r.BTCTRNS1	Pause all jobs
r.BTCTRNS2	Activate all paused jobs again
r.BTCAUX10	Schedule job with special timing (not possible with SM36)

You can run

• internal and external jobs
• one or multiple steps
• generally runs sequentially and synchronously (only external program steps can run asynchronously)
• immediately or scheduled (in night)
• can also be triggered by one or more system or user event(s) (in opposite to a certain time)
• once or on a frequence.
• on other server (dedicated one, load balancing)
• no memory limit or time out
• need to be "Released" to allow execution (SM37)

Abap programs

• need variant for parameters (or specify in program)
• optionally declare executing user (profile)
• define output destination (spool, printer, mail)

Types

• ABAP program + Variant + Print and archiving parameters + Language
• External
  • External command + Type of operating system + (Parameters) + Target host system
  • External program + Parameters + Target host system

Scheduling Options

• with SM36
• with transaction SA38 (ABAP: Execute Program) and "Background"
• with transaction SE38 (the ABAP editor), Menu > Program > Execute > Background
• Through the background processing system’s own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
• Through an external interface.

Meta Data (Tables)

TBTCO	The job header table (job management data)
TBTCP	The job step table (individual processing steps in jobs)
TBTCS	The control table for the time-driven job scheduler
BTCEVTJOB	Jobs scheduled to wait for an event

Programming

• Express: BP_JOBVARIANT_SCHEDULE, BP_JOBVARIANT_OVERVIEW
• Full: JOB_OPEN, JOB_SUBMIT, JOB_CLOSE

Execution on special server#

1. SE16 > TBTCS
2. Field EXECSERVER filled?

Track changes for job scheduling/deleting#

SCU3	List of logged tables + analysis, Table name: TBTCO
SE17	TBTCO > you can find last changed by(LASTCHNAME) when deletejob(DELANFREP) is 'x' (?)

or SPRO > Menü > Tools > Logging > ...

Activating Table Logging
SE11 > Menue > GoTo > Technical Settings > Select/Deselect Log Data Changes checkbox > Save + ACTIVATE (!)
or SE13
or SPRO > Menü > Tools > Logging > ...

r.RSTBPDEL	Clean up logging protocols with report
r.RSBTCDEL	Clean up jobs with report

Variants#

t.VARID	Variants Katalog
t.VARIT	Variants Description
t.VARIS	Variants for selections screen
t.VARI	Variants Values (Read raw data inf field CLUSTD with FM 'RS_VARIANT_CONTENTS')

• RELID = 'VB' => current storage (version 2)
• RELID = 'VA' => old variants (version 1)
• background jobs with dynamic variants are stored with "&"

Transport Variants#

1. SE38 > <report>
2. Springen - Varianten
3. Hilfsmittel - Transportauftrag
4. F8

Functions

RS_VARIANT_CONTENTS	Values of a variant returned in a table (OLD)
RS_VARIANT_CONTENTS_255	Values of a variant returned in a table (NEW!)
RS_VARIANT_EXISTS	Checks whether a variant exists for a report
RS_VARIANT_TEXT	Returns short description of variant
RS_VARIANT_VALUES_TECH_DATA	Reads variant parameters of a report

Reports

r.RSVCHECK	Rescue/Recover Variants (Veraltete/Obsolete)
r.RSVARDOC_NEW	Rescue/Recover Variants see note 2875966
r.RSADJUSTVARITABLES	Abgleich VARID, VARIT, VARI und VARIS
r.RSMATCHVVVV	Abstimmen VARID, VARIT, VARI, VARIS
r.RSDBSPVD	RSDBRUNT-Helfer: Varianten + Freie Abgrenzungen
r.RSTRANSP	Auswahl Report und Varianten für Transport
r.BTC_DELETE_ORPHANED_IVARIS	Löschen von "verwaisten" temporären Varianten (Note 1021775)
r.RSVARENT	Schutz von Varianten aufheben
fb.RS_COPY_SELECTION_SETS	Kopiert alle Varianten in allen Mandanten (und von einem Report zum anderen)

Selection variables in variants#

These variables are stored in client 00, e.g. are valid for all. To maintain use

x.STVARV	Maintain table TVARVC in current client
x.STVARVC	Maintain table TVARVC in client 000

Spool#

Delete spools#

Kategorie              Interner Kernel-Fehler
Laufzeitfehler         SPOOL_INTERNAL_ERROR
Anwendungskomponente   BC-ABA-LA
Nähere Beschreibung des Fehlers: "spool overflow "

RSPO0041	Löschen alter Spool-Aufträge
RSPO1041	Löschen alter Spool-Aufträge
RSPO0043	Spool-Daten-Konsistenzprüfung
RSPO1043	Spool-Daten-Konsistenzprüfung im Batch
Note 1422843

Archiving spools

For spool distribution (email) out of the job see Business Workplace

Spool Administration

Vergrößerung Spool-file#

siehe SAP note 48284 (mehr als 32000 Spoolaufträge im System anlegen, bei bsp. SPOOL_INTERNAL_ERROR)

r.RSPARAM:

rspo/spool_id/max_number	99000 Default max möglich Spoolnummer
rspo/spool_id/loopbreak	sollte ebenfalls auf 99000 stehen (default)
spo_num	Nummernkreis mit SNRO/SPO_NUM pflegen, erst auf Null setzen und dann auf den neuen gewünschten Wert hochsetzen (siehe Hinweis), Achtung: Im Mandanten 000 durchführen, in anderen Mandanten können andere Werte stehen

Aktueller Zustand:
RZ20 > SAP CCMS Monitor Templates > Spool System > System Wide > Spool > SpoolNumbers > UsedNumbers
SPAD > Volle Administration > Verwaltung > Übersicht Druckaufträge

Verweildauer#

rspo/req_lifetime

Systemparameter (r.rsparam) in Tagen

Parallel execution#

r.RPMREP00	HR: Scheduler für paralleles und verteiltes Reporting (works with RPCSVBD2) Note: all instances of the jobs need to run on the same server type (!). We had Unix and Linux instances with different character sets, if this report wants to merge the output from both of those it fails.
r.RPCSC000	Scheduler für Parallelabrechnung (works with RPCALCD0)