ABAP REPORTS: 2012

SAP Basis Change and Transport System Pre Requirements

To set up your system landscape:
Ÿ

Install an R/3 System as a development system; the quality assurance and production R/3 Systems are not required at this stage. Create a transport directory at operating system level. This directory is required for the Transport Management System.If you have performed a database copy, initialize the Change and Transport Organizer (CTO) using Transaction SE06.Configure the system landscape using the Transport Management System (TMS) using Transaction STMS.

Transporting enables you to synchronize Customizing and development in multiple R/3 Systems through the transfer of changes from the development system to downstream systems. Transports along the transport route must occur in only one direction.Transporting requires a transport directory to enable R/3 Systems in the system landscape to store and access various data files, command files, and log files.Physically, changed objects in a three-system landscape are transported in three steps:

All objects in a change request that is to be released are exported – by being "copied" – from the database of the source system to the transport directory.

The objects are imported into the database of the quality assurance system. After testing and verification, the objects can be imported to the defined delivery systems.

Creating Trasport Directory

The global transport directory and all the necessary subdirectories are created during the installation of an R/3 System. Mount this directory using the operating system tools (nfs for UNIX; share for NT) for all systems within a system landscape or a transport group. The amount of disk space required depends on the amount of development work: estimate 10 MB for each customizer and developer. You will need additional space for client exports. The R/3 Parameter DIR_TRANS has to point to the path of the transport directory. For Unix, the default path is /usr/sap/trans. For Windows NT, the default path is \\$(SAPTRANSHOST)\sapmnt\trans and you must define the transport host with the alias SAPTRANSHOST on the domain name server.

The subdirectories required in the common transport directory include:

Ÿ bin: Configuration files for tp (TP_.PFL) and TMS (DOMAIN.CFG)
Ÿ data: Exported data
Ÿ olddata: Old exported data (to be archived or deleted)
Ÿ log: Transport logs, trace files, and statistics
Ÿ actlog: Action logs for all tasks and requests
Ÿ buffer: Transport buffer for the each system, indicating which transports are to be imported
Ÿ cofiles: Command or change request infrmation files that include information on the transport type, object classes, required import steps, and post-processing exit codes Ÿ sapnames: Information pertaining to transport requests for each SAP user Ÿ EPS: Download directory for advanced corrections and Support Packages
Ÿ tmp: Temporary data and log files

The Transport Management System (Transaction STMS) enables you to:

Ÿ Define an R/3 System's role within a system landscape or transport domain Ÿ Configure the transport routes using either a graphical editor or hierarchical editor Ÿ Configure the transport tool transport control program tp.Display the import queues of all R/3 Systems in the transport domain Ÿ Decide whether the quality assurance testing was successful in the QA System Ÿ Start the import of change requests in an import queue Ÿ Perform transports between R/3 Systems without a common transport directory Ÿ Handle transport proposals of developers

System Landscpae

With R/3 Release 4.0, SAP introduced the TMS and the concept of a transport domain (all R/3 Systems to be managed centrally using the TMS) and a transport group (all R/3 Systems that share the same transport directory and belong to the same transport domain).The term system landscape refers to the group of R/3 Systems normally comprising the development system, the quality assurance system, and the production system. A system landscape consists of all the R/3 Systems that share change requests for the purpose of maintaining consistent Customizing and development environments.A system landscape is usually synonymous with a transport domain. Having all R/3 Systems of the same system landscape in the same transport domain ensures consistent configuration and easy delivery of all change requests.

A transport domain may, however, contain more than one system landscape. For example, a company may have different system landscapes for each subsidiary. These R/3 implementations are very different and do not share change requests. To benefit from centralized configuration with the TMS, you can include both system landscapes in the same transport domain.

Strecture of TMS

The TMS supports several transport directories within a transport domain. The R/3 Systems with a common transport directory each form a transport group.Transports between different transport groups are supported by the TMS; transports between different transport domains are only supported by external systems.In most implementations of R/3, a customer only needs one transport domain and one transport group. If more than one transport directory is needed, additional transport groups are required.All R/3 Systems to be administered using the TMS belong to a transport domain. Within this transport domain, certain system settings such as the transport route settings are identical for all R/3 Systems. In order to have consistent settings, in the transport domain, one R/3 System (the domain controller) has the reference configuration, and all the other R/3 Systems in the transport domain receive copies of this reference configuration.

When setting up an R/3 System with the TMS, you include the R/3 System in an existing or new transport domain. All R/3 Systems in a transport domain must have unique system IDs, and may or may not share the
same transport directory.Within a transport domain, the TMS enables RFC communication between all R/3 Systems, for example, to distribute configuration changes or perform imports.Changes to the transport domain configuration are made in the domain controller, and then distributed to all R/3 Systems in the transport domain. Each time you make a change to the domain controller, a dialog box is displayed asking whether to distribute the change. You can distribute several changes at one time.

Setting up TMS

Before you can work with the TMS, you must configure the TMS on all R/3 Systems in your system landscape.To configure the TMS:

ŸConfigure the transport domain

Assign R/3 Systems to the transport domain, and specify one R/3 System as the transport domain controller.
Ÿ

Configure transport routes

The transport routes are used to define both the target system in which you want to consolidate change requests, and the R/3 Systems to which change requests are delivered after verification and testing.

ŸConfigure Quality Assurance (QA) Procedure

Define a QA system, where the decision is made whether objects may be further transported to the production system.After setting up the TMS, use the TMS tools to check and monitor TMS configuration. The transport domain and transport groups define which R/3 Systems are managed by the TMS and which systems share the same transport directory. Transport routes define how change requests are transported and thus strictly reflect the system landscape implementation process.

The transport domain contains all R/3 Systems whose transports are to be administrated jointly. One of these R/3 Systems is chosen as the transport domain controller. Since all activities relevant to the entire transport domain, such as configuring transport routes or RFC connections, can only be carried out on the domain controller, the R/3 System selected to be the domain controller should have:

ŸHigh availability
ŸA high level of security
ŸA high level of maintenance

The domain controller is normally configured on a production system or a quality assurance system.The system load on the R/3 System that is chosen as the domain controller is low, and only increases for a short period when the TMS configuration is changed.

logistics introduction

SAP Basis Software Logistics Introduction

Software logistics gives procedures for improvement and Customizing which enable you to keep order among all the R/three Systems and purchasers in your system landscape.Development and Customizing, quality assurance testing, and production work are performed in completely different clinets in one or more R/3 Systems. Three R/3 Techniques are really useful, to allow you to:

Take a look at the transport of modifications from one system to another earlier than transporting these modifications to the manufacturing system.
Create cross-consumer changes in order to not affect the manufacturing atmosphere without earlier testing. Note that, while most Customizing work is shopper-particular, all Repository objects and international settings are cross-client.
Keep away from development occurring within the production system - for causes of safety, system load, and the need to take a glance at any change without endangering the manufacturing environment.

R/3 knowledge may be divided into two classes:

. Consumer-specific knowledge is information affecting only one consumer, resembling user grasp and software data.
. Cross-consumer knowledge is information affecting the entire system surroundings, reminiscent of cross-client Customizing knowledge and all Repository objects.

The ABAP Dictionary is a knowledge dictionary that is part of the ABAP Repository:

. Each bit of ABAP Dictionary information is entered solely as quickly as and is then accessible anywhere within the system at any time. The ABAP Dictionary robotically provides all new or modified information, thus providing current runtime objects and guaranteeing data consistency and security.
. The R/3 runtime atmosphere consists of all ABAP packages required throughout R/three execution. The ABAP interpreters in the runtime surroundings don't use the original of an ABAP program. Slightly, they use a replica generated once only during runtime (early binding). Runtime objects, such as packages and screens, are routinely regenerated (late binding) when a time stamp comparison between the object and the ABAP Dictionary detects a difference.
. This combination of early binding and late binding ensures that the active integration of ABAP Dictionary data doesn't have an effect on system-large performance. All efficiency-critical info is saved within the runtime objects and is at all times kept up-to-date.

Client

A client is a self-contained unit in commercial, organizational, and technical terms, with its own user grasp knowledge and set of desk key ranges.Data from totally different shoppers is kept separate on the R/3 kernel level. SQL statements executed by an software use the clinet number within the the place-clause. Although a table might contain knowledge from several completely different clients, the the place-clause limits entry to specific clients. n Examples of client-specific data embody:

. Consumer grasp information - comparable to parameters, authorization, consumer groups
. Customizing knowledge - corresponding to organizational units, assignments, and doc types
. Application data - such as business transaction information, and materials grasp information

The SAP shopper concept can combine a quantity of corporations or subsidiaries in a single R/3 client by utilizing firm codes and the SAP authorization concept.

. Firm codes outline the smallest corporate organizational units for which a whole self contained set of accounts might be drawn up for external reporting.
. The SAP authorization idea permits the mum or dad company to entry all subsidiaries for report functions, whereas subsidiary-specific knowledge is protected towards access from different subsidiaries through company code definition.

Standard Client Roles

The standard client roles fulfill the optimum minimal necessities of your R/3 System:

. Client CUST is the central Customizing client the place complete adaptation of R/three to customer specific wants takes place. All modifications performed in this client are recorded so they can be provided to the other purchasers utilizing the Transport Administration System.
. Client QTST is used to test and confirm the new Customizing settings within the application.. Shopper PROD is the client for production actions, that's, where your organization's business is carried out. Customizing changes imported into this shopper have to be first examined rigorously within the QTST shopper with a view to ensure that production operation is free of disruption.

To realize the full benefit of a 3 system landscape, every critical shopper should have a separate R/3 System.

Extra shoppers inside a system landscape might include:

. A sandbox client for experimenting with transactions and settings
. A take a glance at client so that Customizing adjustments could be verified towards pattern data
. A end-consumer training surroundings

Additional consumer roles might be applied in keeping with customer-specific needs.

Goals System Panorama

To take care of information security, defend utility information through the use of the consumer idea, which separates information in protecting with purchasers, and the authorization concept, which separates information inside one client according to user.As nicely as, it's greatest to strictly separate the environments for improvement, high quality assurance, and manufacturing, because:

. If data is lost, a consumer can solely be rebuilt consistently if test master data and Customizing information are held in separate data environments.
. The performance of the manufacturing client shouldn't be affected by development and check actions within the other clients.
. Modifications to Repository objects are client-independent, and immediately have an impact on the run time environment. Subsequently, modifications must be tested before being transported to the production system.
. In the event you had only one system, no further development would be attainable after manufacturing had started. Adjustments to Repository objects could probably be made only when manufacturing operations were stopped for growth and testing.

A two-system panorama isn't optimal because growth and high quality assurance testing each occur in the development system. Since no separate quality assurance system is on the market, all objects transported to the consolidation system immediately change into part of the production system.

To make sure easy manufacturing operation, an R/3 System landscape ought to comprise the three R/3 Methods, the standard purchasers, and any required additional clients. A 3-system landscape is the beneficial R/three System landscape and meets the wants of most customers:

. Growth takes place within the improvement system. Changed objects are then released to the high quality assurance system.
. In the quality assurance system, new developments can be tested without affecting the manufacturing environment. A quality assurance system allows you to combine improvement efforts and to test the validity and consistency of transported objects before shifting the objects into production.
. All objects imported into the quality assurance system will additionally be delivered to one or more manufacturing systems.

The three system landscape is also a foundation for performing an R/three Release upgrade. R/3 Systems in the identical system panorama require distinctive system names.

Transporting

Greater than 800 enterprise course of chains with their related functions are characterize within the R/3 System. During implementation of those process chains, the different characteristics of the usual options needed for various branches of business and firm varieties, together with multiple languages and nationwide particularities, are realized by Customizing. Customizing changes are required for all implementations of R/3. New performance past that offered by SAP may be realized utilizing the event instruments of the ABAP Workbench.

Though Customizing and development, the R/3 System might be adapted to modified business processes even after set up, and in productive operation. To make sure consistency, Customizing
and development are distributed to other purchasers within the same R/3 System and to different R/3 Systems.Transporting is the process by which modifications are distributed inside a system landscape.

Tools for managing modifications

R/3 gives the instruments required for the creation, documentation, and distribution of adjustments within a system landscape. To arrange the system landscape so that it supports the management, verification,and testing of all adjustments:

. A single shopper is really useful for all Customizing work. Set consumer change choices appropriately before utilizing your clients.
. A single R/3 system (the development system) is really useful for all improvement work. Set the system change choices appropriately.
. To create and assign appropriate person authorizations to developers and customizers, use the pattern profiles included in R/3. These authorizations control whether or not a consumer can create, modify, or launch change tasks and requests.
. Record and document all adjustments to a client or system.

The greatest way during which R/3 allows service and assist is amongst the decisive elements for a stable manufacturing environment. SAP supplies a comprehensive concept for service and help, together with advance corrections, and the On-line Correction Help (OCS), which gives Help Packages and other patches.

In R/3 Release 4.0, SAP has launched the Change and Transport System (CTS), comprising the following instruments:

. The Change and Transport Organizer (CTO) supplies functions for organizing software growth projects. It is designed to support projects of all sizes, whether or not they're carried out centrally or in a distributed environment.
. The Transport Management System (TMS) organizes, monitors, and performs transports for all R/3 Systems inside a system landscape. As nicely as, TMS is used to configure and handle the organising of R/3 Systems and transport routes within a system landscape.
. Operating system transport tools are executables that talk with the R/3 System, the database, and information generated throughout the export process.

Erp Installation CONCETPS

SAP AND ABAP TOPICS

SAP Basis Change and Transport System Pre Requirements

SAP Basis Software Logistics Introduction