SPOOL WORK PROCESS

1️⃣ What is a Spool Work Process in SAP?

 It’s a special type of work process dedicated to output management (printing,
faxing, emailing).
 Unlike dialog work processes that interact with users or update work processes that
commit DB changes, the spool work process is concerned only with taking prepared
output and sending it to printers or output devices.

2️⃣ Printing Process in SAP — Step by Step

Step 1 – User triggers output (Dialog WP)

 You run a report, print an invoice, or generate a purchase order.

 The dialog work process:
o Formats the document in device-independent format.
o Creates a spool request in SAP.
o Saves it in TemSe (Temporary Sequential Object) storage.

📌 TemSe = SAP’s “parking lot” for output before it goes to the printer.

 Can be stored in DB table TST03 or in the file system (depending on config).

 Directory info is in TST01.

Step 2 – Spool WP picks it up

 The spool work process continuously checks TemSe for pending spool requests.
 When it finds one, it:
o Reads the TemSe data.
o Converts it to a device-specific format (e.g., PCL, PostScript, PDF) using the
printer’s device type settings.

Step 3 – Send to Host Spooler

 The formatted output is sent to the OS-level spooler (Windows Print Spooler, UNIX
lp/lpr, etc.).
 From there, it’s sent to the physical printer.

Step 4 – Printer prints

  The OS spooler sends the job to the printer.
 Printer prints it.
 SAP updates the spool request status to “completed” (green).

3️⃣ Temporary Sequential Object (TemSe)

 Purpose: Acts as a temporary storage location for spool requests until processed.
 Why needed: Printing might not be immediate — spool requests wait in TemSe until
the spool WP picks them.
 Storage options:
1. Database – easier to back up but can bloat DB.
2. File system – faster but needs filesystem space management.

5️⃣ Lock Mechanism & Spool

 If the document is locked by another process/user:

o You cannot print or update it until lock is released.
o Status in SM13 (Update Requests) may remain pending until lock clears.

Temp sequential object updated through dialog wp ye smjh nhi aaya

TRANSPORT MANAGEMENT SYSTEM

The Transport Management System (TMS) in SAP is a tool used to manage, control, and transport
changes (customizing, developments, etc.) across the different SAP systems in your landscape —
typically DEV ➝ QA ➝ PROD.

IN IMPLEMENTATION WE DO 4 THINGS

CUSTOMIZING CONFIGURATION SETTINGS 2 TYPES CLIENT SPECIFIC AND CROSS CLIENT

MODIFICATION make changes to a standard sap delivered program change source code

ENHANCEMENT add some extra code to existing code or adding some additional functionality

DEVELOPMENT creating new program or a table or a screen that is not there in the programs
provided by sap ex sjobrepo created

We move these 5 things client specific cross client modifcstion enhancement deveopment from
DEV -> QA -> PRD NOT ENTIRE REPOSITORY DATA bec std sap soft is installed on both dev and qa
prd so almost everything is same except changes that we have done so we move these chsnges

There is no app data in bith dev and qa so to test in qa we use CATT AND ECATT to generate
dummy data
rfc is used for client copy and client has data so why use tms

Let’s clarify this confusion: RFC is indeed used during client copy, and clients contain data, so you’re
asking:

"If we can copy client data using RFC, why do we need TMS?"

The answer lies in understanding that RFC and TMS serve entirely different purposes in SAP.

✅ What is RFC used for?

🔹 Primary Purpose: Communication and Function Calls between SAP Systems

 During remote client copy, RFC is used to transfer application data and master data (like
customers, vendors, materials) from one client/system to another.
 It’s like a data-level duplication.
 It does not transport configuration code, programs, or developments.

✅ What is TMS used for?

🔹 Primary Purpose: Transporting Customizations, Configurations, and Developments

 TMS moves:
o Custom ABAP programs
o Configuration settings
o Smartforms, Reports
o Custom Tables, Objects, etc.
 It ensures changes are moved in a controlled, versioned, and trackable way from DEV ➝ QA
➝ PROD.
SE06 standard installation then hit post installation activity then these three functionalities will
be activated

And at the same time it will generate an initial transport id DEVK900002

From another change it will create another tansport req say DEVK90004 these are transport req

Se09 workbench organizer if you do any cross client changes , modification enhancement
developemnt it will be recorded by workbench organiser as a transport request

SE10 customizing organiser If you do any client specific customizing it will be recorded by
customizing organiser as at transport organiser

SE01 transport organiser to manage both workbench and customizing transport requests.

A Transport Request (TR) record and store changes

is used to record and store changes made in the system — like code, configuration, or customization
— so those changes can be moved to other systems (e.g., from Development → Quality →
Production).

Each tr has a uniques tr no Ex: DEVK900002

TRANSPORT DIRECTORY It is a shared file system that is accessible by all systems (DEV, QA, PRD) in
the SAP landscape.

/usr/sap/trans/

Bin configuration file for tp and tms

Buffer contains list of TRs ready to be imported per system

tmp Temporary files created during transport

log contains logs of transport imports/exports

data  Stores the data files of released transport requests.

 File Naming Format: R<request number>.<SID>

👉 Example: R900123.DEV
 Contents: Actual data (objects, programs, customizing) to be imported into other systems.

Cofiles Cofiles are control files of a transport request . They contain metadata about the
transport request — like object list, transport type, source/target system info, and order of
execution

What is tp transport tool program

it is a command-line tool used in SAP to control the import and export of transport requests
between SAP systems

TRANSPORT DOMAIN

It is a group of sap systems that are managed together

TRANSPORT GROUP

A Transport Group is a set of SAP systems that share the same transport directory

3. Transport Domain Controller (TDC)

📌 Definition:

The Transport Domain Controller is the main SAP system in a transport domain that:

 Manages all TMS configurations

 Controls transport routes
 Manages system roles (DEV, QA, PRD)
 Is the only system where TMS configuration changes can be made

📋 Key Responsibilities:

 Define transport routes

 Create/configure other systems in the domain
 Generate configuration files (TMSADM, TP_DOMAIN_<SID>.PFL)
 Maintain the import buffers

🧠 Think of it as:

The “admin” system of the entire transport landscape.