1

Transport Strategy
2012/1/18

Change History
Date

Brief Description of Change

Name

2011/10/18

Initial version Create

H.Takahashi

2012/02/14

Add a difference transport rule from 2012/03/05

Y.Inoue

2012/8/24

Add the rule for Vietnam rollout

Y.Inoue

2013/1/18

Add a difference transport rule after Go-Live

Y.Inoue

INDEX

1. Purpose of Document
2. Basic Policy
2.1. What is Transport?
2.2. Assumption
2.3. Basic Policy for Transport Operation

3. Transport Management Policy

3.1. Transport Procedure
3.2. Unit of Transport Request
3.3. Client Roll for DEV Environment
3.4. Client Strategy/Transport Route

1. Purpose of Document

1. Purpose of Document
Purpose of Document
A basic policy of the transport management for the global rollout project is provided.
It aims to clarify "Method and procedure of transportation" and to persist the transport
management

Scope of Document
Member
System

SGST Project Member

ECC

2. Basic Policy
2.1. What is Transport?
2.2. Assumption
2.3. Basic Policy for Transport Operation

2.1. What is Transport?

What is Transport?
It is a Process to deliver Add-on Objects and Customize Objects created/modified at DEV system
for another system (QAS/PRD)
Development System
(DEV)

Add-on Object

Customize

SAP
SAP
Standard Standard
Object
Config

Quality Assurance System

(QAS)

Export/
Export/
Import
Import
by
bySTMS
STMS

Add-on Object

Customize

SAP
SAP
Standard Standard
Object
Config

Export/
Export/
Import
Import
by
bySTMS
STMS

Production System
(PRD)

Add-on Object
Customize

SAP
SAP
Standard Standard
Object
Config

System Landscape
What is Transport Request (=TR)?
Administrative information that system recognizes when change is transported or is copied to
another Client. One transport request includes one or more change requests.
Development, correction, and temporary correction are recorded in the task. (It is a concept of
one lower layer of the transport request.)
The repository object taken into the request can be edited only by the request. (locked)

2.2. Assumption

When a basic policy of transport is set up, the following system landscape are
required.
SAP System Landscape is Development (DEV) /Quality Assurance (QAS) / Production (PRD).
The Development system is assumed to be a single instance for the future roll out. The standard
template objects and the rollout objects in each country are uniformly managed.
The Production System/Quality Assurance System are assumed to be a single instance for present
roll out. The future, the examination is separately done according to the condition of the country
(system, time difference, and society's infrastructure, etc.).
It is assumed that it advances it by single instance single client as a basic policy of the instance
client composition.

Development
(DEV)

Quality Assurance
(QAS)

Production
(PRD)

Shared Development

This time

Future

The multi instance will be examined

if it needs in the future.

2.3. Basic Policy for Transport Operation

Purpose of transport management

To transport the development object that completes the tests to the Production System having the
corresponding with each objects.

Point of transport management

1) Make the mechanism that the transportation error is not caused.
The transporting order of the object is managed.
The object that has been tested is transported.
2) Make the mechanism that the inconsistency between systems is discovered.
The confirmation is executed at each transport result.
The difference confirmation between systems is executed.

Basic Policy (=Strategy to achieve the above-mentioned management point)

Transport Procedure
The operation flow to keep consistency without omission is established.
Unit of Transport Request
The rule at each TR acquisition is decided, and the transport method corresponding to the
project timing is established.
Client Roll for DEV Environment
To use the transport management function of ERP, Client roll for DEV environment is defined.
Client Strategy / Transport Route
To use the transport management function of ERP, Client strategy plan and transport route is
defined.

10

3. Basic Policy
3.1. Transport Procedure
3.2. Unit of Transport Request
3.3. Client Roll for DEV Environment
3.4. Client Strategy / Transport Route

3.1 Transport Procedure

11

As a precondition of the transport execution, receive the approval by PMIC for the object .
NEC
Developer
Development

Execute
Release TR

Add-on
Add-on

NEC
Appl. Member

Execute
Acceptance Test

NEC
Appl. LD/PMO

Confirm
Acceptance Test

Indicate
Release TR

PMIC

Automatic
Transport

Approve
Acceptance Test

Config
Config

Application
Transport

TR List

Approve
Transport

TR List

Confirm
Transport Result

Execute
Transport

TR List

The next phase consideration (Fixes it by QAS construction)

Transport Request List (TR List) format with description item
Confirmation method of Transport result
Application method of automatic transport : Service time (Regular time/emergency), Application
method (Calling/Charge)

3.2 Unit of Transport Request (1/4)

12

Initial Transport
At the initial transport for QAS system construction, The transport request is acquired for the following

unit, and put up each object.

As Automatic transport has the option of regular time, execute the initial transport at the Night
time.
Object

Unit of TR

Object ID

Add on Object (*)

1 in PJ

PKG

Customize Object (include data)

1 in PJ

CTT

SAP Note

1 in SAP Note

NTE

Basis Customize

1 in Object

BLC

* Example of Transport Error : This case is finished to 2011/08

If the dictionary object has not been transported before the transportation of the Add-on program, the error occurs.
The order of the object is kept by managing in one package, and assuming the batch transport.

3.2 Unit of Transport Request (2/4)

13

Difference Transport ( Before Go-Live )

After the QAS environment is constructed, the Transport Request is acquired for the following unit
and transport is executed individually.
Because the correction of the individual program is the main, the batch transport is not enforceable.
It is necessary to request to have considered the order when transportation was applied.
Object

Unit of TR

Object ID

SAP Note

1 in SAP Note

NTE

Domain, Data Element

1 in PJ

DET

Authority Object

1 in PJ

AUO

Authority Role

1 in Object

AUR

Structure

1 in Object

TBS

Table Data Type

1 in Object

TBD

Table

1 in Object

TBL

View

1 in Object

VIW

Search Help

1 in Object

SHP

Lock Object

1 in Object

LOT

Baseline Customize

1 in Object

BLC

Customize

1 in Object

CUT

Customize Data (Table Data)

(Include the Number Range Data)

1 in Object

CUD

Function Module, Include

(Class/Method, BAdi)

1 in Object

COM

Program

1 in Object

PGM

Variant

1 in Object

VAT

3.2 Unit of Transport Request (3/4)

14

Difference Transport ( After Go-Live )

After Go-Live, we create the transport number by unit of Change request number or Issue number.
When we transport this the TR, all modified objects are transported.
"Workbench objects" and "Customizing objects" are created each transport request.
If you want to separate to some transport numbers in one change request, you must control transport order and contents.

Object

Unit of TR

Object ID

* Workbench

1 in CR Number or Issue Number

WORK

* Customize

1 in CR Number or Issue Number

CUST

3.2 Unit of Transport Request (4/4)

15

Description of Transport Request

The objects in the transport request and the order of the transport requests is made visible.
DEL:[Object Attribute]:[ReleaseTiming]-[ChangeRequestNumber]-[ModuleID]:[ObjectID]:<Explanation>
Example:
G0:GBL-CR1234-BC:NTE:SAP note.1234 for ABAP program error
ZI:R01-CR5678-FI:PGM:Modification of common program for India
ZV:R02-P00001-WORK:CUT:Do not update the Variant Variables

DEL:ZI:R01-CR1234-CO:NTE:SAP note.1234 for ABAP Temporary development

Sign

Value

Description

Delete Sign

DEL

Add it in case of Temporary or Deletable TR

Object Attribute

G0

Global object case

Z+ Country ID
ZI : India (APIN)
ZV: Vietnam (PAPVN)

Local object case

Release Timing

GBL : Template Timing

R01-99 : Roll Out Timing
R01: India (APIN)
R02:Vietnam (PAPVN)
R03: Malaysia (MB) & Singapore (SA)
R04: PAPFMY (MD)
R05: PAPMOSH (CE)
R06: PAPRDTH (TC)

According to the roll out timing

Change Request
Number

Change Request: CR + 0001-9999

Issue Number: P00001 P99999

CR Number *"XXXX when there is no CR number

Module ID

FI/CO/SD/MM/PP/BC

Module ID is described (Refer to the Naming Rule).

Object ID

See 3.2 Unit of Transport Request

Explanation

Explanation of TR

* In English

3.3 Client Roll for DEV Environment

16

Client composition and definition

Client in the DEV System is as follows. Execute development with an appropriate client.
Client

Sys
tem
199
ERP DEV System

200

100

Sandbox
Client

Customizing
Client

Development
Client

Role

Setting

A prior verification and

the prototype setting are
executed.

Customize

CL Dep. Changes
CL Indep. No Changes

Repository

CL Indep. No Changes

A formal customizing is
executed, and the
content is transported to
another client.

Customize

CL Dep. Changes
CL Indep. Changes

Repository

CL Indep No Changes

Development/unit
test/receipt/variant
acquisition is executed.

Customize

CL Dep. No Changes
CL Indep. Changes

Repository

CL Indep. Changes

Data
Input
Possible

Impossible

Possible

Transport to other Client (SCC1) of Customize (Client dependent) Object

Enables to transport Customize object from Customizing Client to Development Client.

Timing of Creation of Development Client

Separately, applies after Customizing situation and Development start are adjusted.
Assume 1Week to the application for client creating for the BASIS team.

The next phase consideration

Client strategy : Fix the client composition and roll (Test and Training, etc) for QAS System / PRD
System.
( Described in Client Strategy / Transport Route at this time)

3.4 Client Strategy / Transport Route

Updated

17

Client Strategy
Client composition is Single Instance and Single client.
Customize Master CL in DEV System is implemented all company customizing. Customize Copy CL in QAS System is
copied from Customize Master CL and is assumed to be source CL for the Test.

Transport route (Client Specific Customize)

The SAP customize is implemented on Customize Master Client on TGD.
The TR of Client Specific Customize is transported to all client on QAS.

Transport route (Client In-depend Development)

The Add-on Object is developed on Development/UT Client on TGD.
The TR of Client In-depend Development is transported to Customize Copy client on QAS.
(We can use same Add-on Object on other clients)
DEV
A/B/C
Comp.

Client
Depend

PRD

QAS

200 Customize Master

300 Customize Copy

A/B/C
Comp.

301 QA

100 Dev/UT

500 Production (A/B/C)

304 UAT

Client
In-depend

200 Customize Master

100 Dev/UT (Maintenance)

300 Customize Copy

A/B/C
Comp.

301 QA
304 UAT

A/B/C
Comp.

500 Production (A/B/C)