You are on page 1of 18

Maventic Innovative Solutions Pvt. Ltd.

Your Trusted Advisor

Maventic : A Presentation

Internal and Confidential

Agenda

Agenda
SAP System Landscape Transport Routes Transport Request Access Rights (Developer Key, Access Key)

SAP System Landscape

SAP System Landscape

Agenda
Used In Initial Phase of Project for configuration / customization as per company Business Process

Normally has 3 Clients


Customizing Development Testing

Changes to code and Customizing Basic Testing Rarely contains any realistic Business data

SAP System Landscape

Normally has 2 Clients


Testing Training

Changes to code and Customizing are moved from Dev Contains some amount of realistic Business data

Live Version Of System Changes to code and Customizing are moved from Quality after rigorous testing Contains real time Business data

SAP Transport Route

All SAP change is associated with Transport Request Ex. Table Definition, Source Code, etc. Transport Requests are released into Transport Directory The changes exported from one system may be imported into another system in minutes, weeks or even months

SAP Transport Route


Typical Representation of How changes move through a SAP Landscape

More Accurate representation of How changes move through a simple Landscape

SAP Transport Route

The Target SAP system reads the data files from the transport directory Runs a series of special programs that implement the changes within the importing system May affect All clients Particular Clients A series of Return Codes is provided by SAP as the outcome of the import

SAP Transport Route

Once Released a transport cannot be added or changed The new Transport Request may contain only a part of complex object Transports must be imported in sequence

SAP Transport Request

Transaction Code: SE01, SE09, SE10 Changes to Customizing settings are recorded in Customizing requests Workbench requests record changes made to ABAP Workbench objects Transports of copies allow you to transport (sub-)objects in an object list into any other SAP System you want Creates two different kind of files Data Files Co Files

SAP Transport Request


Requests and tasks allow objects from the Repository or Customizing to be managed within an SAP System or transported between different SAP Systems. Change requests: Transportable change request For recording changes to Repository objects and transporting them to other SAP Systems. Local change requests For recording changes to Repository objects within an SAP System. Customizing request For recording changes to Customizing settings and transporting them, if necessary, to other SAP Systems or clients. Tasks: Correction For recording changes to Repository objects if they are carried out in the object's original system Customizing settings Repair For recording changes to Repository objects if they are not carried out in the object's original system

Request/Task
Requests and tasks allow objects from the Repository or Customizing to be managed within an SAP System or transported between different SAP Systems. Change requests: Transportable change request For recording changes to Repository objects and transporting them to other SAP Systems. Local change requests For recording changes to Repository objects within an SAP System. Customizing request For recording changes to Customizing settings and transporting them, if necessary, to other SAP Systems or clients. Tasks: Correction For recording changes to

Repair For recording changes to Repository objects if they are not carried out in the object's original system

Repository objects if they are carried out in the object's original system Customizing settings

SAP Transport Request


Transaction Code: STMS

SAP Transport Request

SAP Provides With Different Return Codes


Return code: 0 Return code: 4 Return code: 8 Return code: 12 & Greater Transport successful Warnings occurred Transport carried out with errors The transport was terminated

SAP Transport Route

Some Useful Hints:


Data in Tables are Not Transported RFC Destination is Not Transported If we have use a RFCDEST then we should not hard code it in program but read it from a table Number ranges

Developer & Access Keys

Needs to be a registered user on SAP Net (http://service.sap.com/sscr) Developer Key: Required for development of Custom Objects Access Key: Required for changing SAP standard Objects

Developer & Access Keys

Developer Key Stored in Table DEVACCESS Access Key Stored in Table ADIRACCESS Other Information Required: Installation Number of the server SAP License Hardware Key System ID SAP Version System Number Operation System / Database Object Directory Entry ( Only For Access Key)

THANK YOU