Software Logistics

12/5/2014

Data and Customizing

Client 200
Application
data
Customizing data

Client 300

User
Master
data

Application
data
Customizing data

User
Master
data

Cross-Client (Client-independent) Customizing

SAP Repository
Modifications
12/5/2014

Enhancements

Development
2

Client Data
Application
Transaction
data
Master
data

User
Master
data

Customizing data

12/5/2014

Clients and Systems

Client
200

Client
300

System

Clients and Systems separate and protect data

12/5/2014

Adaptation
Customizing

Client
Application
data
Customizing data

Development

User
Master
data

Cross-Client Customizing

Enhancements

Modification

12/5/2014

SAP Repository

Customizing

12/5/2014

Development
Add functionality using ABAP/4 programming
Frequently report generation
Requires a Developer Key
Can add objects (tables)
Begin with Y or Z
Append Structures
Add fields to any table

12/5/2014

Enhancements
User Exits
Defined places in ABAP
code where SAP
expects users may want
to perform additional
processing

12/5/2014

Include

Modifications
Not recommended
Can create problems with upgrades
Requires Change Registration Key
Changing a repository object delivered by SAP is
flagged as a repair
Source of future user exits
SAP, while not recommending modifications, does
provide tools to minimize the impact

12/5/2014

System Landscape
Development
System
000

066

Cust.

100

Unit
Test

200

Sandbox
Backup

DB

12/5/2014

QAS
System
000

066

Integ.
Testing

100

300

Training

300

400

Backup

400

DB

Production
System
000

066

Production 400

DB

10

Change Transport System

DEV

QAS

PRD

CUST

TEST

12/5/2014

SAND

QTST TRNG

QTST

11

Change Requests
Customizing changes
are transported as
change requests,
which are key to
managing system
changes
Change request can
be created
automatically during
customization

12/5/2014

12

Controlling Change Requests

Single biggest mistake in managing customizing and
development changes is the lack of clearly defined and
enforced transport processes and procedures. Good
transport processes and procedures:
Reduce the exposure of the production system to
problems caused by premature or incorrect
transports
Minimize the amount of manual intervention
required
Reduce e-mail communications and paperwork
required from the customizing team
12/5/2014

13

Controlling Change Requests

QA Approval Process
DEV

QAS

PRD

CUST

TEST

12/5/2014

SAND

QTST

TRNG

QTST

14

Controlling Change Requests

QA Approval Process
With the QA Approval process configured, change
requests placed in the transport directory for the
PRD system are flagged as inactive, and can only
be imported when all approval steps are processed.

12/5/2014

QA Approval can
only be performed
by designated users
with appropriate
authorizations.

DEV

QAS

PRD

15

Controlling Change Requests

Import Queues
When a change request is released, it is placed on
the import queue of the target system. There are
four methods of controlling the import of change
requests into the target system:

12/5/2014

Single Imports
Mass Imports
Import by Project
Transport Workflow

DEV

QAS

PRD

16

Controlling Change Requests

Single Imports
Change requests can be selected individually to be
imported into the target system
This is not a recommended approach
Increased administration
Selected transport requests may not constitute a
complete configuration modification
Requests must imported in
DEV
QAS
PRD
correct sequence

12/5/2014

17

Controlling Change Requests

Mass Imports
All change requests in the import queue are
imported into the target system
Requests are imported in the order they were
exported
A transport schedule can be established to help
maintain a consistent changes from developers
Example
Hourly imports into QAS
DEV
QAS
Weekly imports into PRD
Reduces administrator workload

12/5/2014

PRD

18

Controlling Change Requests

Mass Imports
Controlling Change Requests is primarily a
behavior issue. Developers can get in the habit of
releasing change requests before a completely
functioning change has been developed.
Mass Imports functions force developers to make
sure their change requests are ready to be released
before they are released.
DEV
QAS
PRD
Like making sure that your
chess move is correct before
removing your hand from the
chess piece
12/5/2014

19

Controlling Change Requests

Import by Project
Can filter to import only changes related to a
configuration project

DEV

12/5/2014

QAS

PRD

20

Key Points in Landscape

Management
No application data goes in customizing client in DEV
system
Like Accounting, you dont undo or delete transport
requests, you create correcting requestsmeans that
you have to manage the order of importing change
requests carefully

12/5/2014

21