Tuesday, 29 March 2016

Continuous Business Engineering

In today’s fast-moving, ever-changing business climate, companies are in a constant state of flux and their mission-critical applications must adapt and evolve at the same speed. If software cannot grow with the needs of a company, the company will quickly find itself in a straight jacket.

Furthermore, an ERP application needs to let you move forward fast, knowing that you can roll back changes without downtime.

An enterprise's organizational structure and the corresponding R/3 implementation created using the Business Engineer are not "set in concrete", they can be modified at any time. Examples of possible changes, which can be made rapidly include the following:
  • Addition or removal of entities within the organization structure (for example, business units, production plants, warehouses, etc.)
  • Introduction of new staff, promotion, reallocation of work tasks, and maintenance of authorization profiles
  • Changes to the reporting or cost/profit center structure
  • New and concurrent currencies
  • Accommodation of changed legal requirements (for example, new tax rates, new employment legislation)
  • Activation or deactivation of R/3 functions
  • Optimization of business processes
  • Support for new and multiple versions of R/3
In addition, SAP offers a range of services if you want support for some of these changes, for example, conversion services to support mergers and acquisitions. Standard Euro services are a further example of the available services.


AcceleratedSAP and R/3 Business Engineer take the hassle out of implementation procedures and change management. Modifications can be made at any time, and the compatibility of changes can be verified with other configuration decisions, thus supporting their smooth, trouble-free introduction into the productive system.

Available Tools for SAP implementation

An implementation project requires a lot of careful thought beforehand. We need to think about what we want to accomplish, the optimum sequence, and the business cases that are best suited to our needs. But SAP has already done a lot of the thinking for you and packaged its findings in the following tools. They are then described in more detail in the following chapters organized according to the corresponding

Accelerated SAP phases.

Accelerated SAP (ASAP): A comprehensive solution for the introduction of the R/3 System in your enterprise. ASAP and most of its tools can be used independently of an R/3 installation.

The tools available for Accelerated SAP are:

·    The Project Estimator, an internal SAP tool which enables SAP consultants to accurately gauge the required resources, the costs and the time frame of implementation. The Project Estimator takes into account the project scope and several project and risk factors.

·      The Concept Check Tool, a tool enabling carry out quality checks on the project preparation, technical infrastructure and R/3 configuration settings. This is done mainly during the first two implementation phases of the R/3 project. In this way you are alerted to potential data volume and configuration conflicts that could lead to performance issues if not addressed.

·    The Implementation Assistant: The ASAP navigation tool that accompanies you through the five phases of implementation down to the task level. It includes a description and a detailed "how-to" for each task in the Roadmap. Along with that, many tools, templates and documents are hyperlinked to the task.

 The Implementation Assistant contains the following elements:

ASAP Implementation Roadmap and Project Plan. The Roadmap contains the five phases, from which you can drill down into work packages, activities and tasks. The Project Plan contains three components, a budget plan, a resource plan and a work plan.
The ASAP Roadmap is the successor of the R/3-based Procedure Model, which was used until Rel. 3.1 in R/3 implementation projects.

Knowledge Corner, containing tips and tricks for configuration from consultants, detailed documentation on SAP’s implementation services, information on technical tools, as well as simplification guidebooks and R/3 Customizing wizards.
Question and Answer Database (Q&Adb). Using the R/3 Reference Model structure, the Q&Adb is used to assist in gathering requirements for business processes, conversions, reports, interfaces, enhancements and authorizations. The database provides useful questionnaires to help you define the process needs and also serves as a repository for all this information. Since it is a database, it allows for flexible reporting. The business requirements generated from the Q&Adb are collectively known as the Business Blueprint.Business 

Process Master List, to manage configuration, testing and the creation of end user documentation. The Business Process Master List is linked to pre-written Business Process Procedures (BPPs), detailled end-user documentation for R/3 transactions.

Issues Database: supporting project management, this database supports the entering, monitoring and managing of issues that come up during the project.

R/3 Business Engineer: The implementation tools for the high-quality configuration of the R/3 System are:

R/3 Reference Model: Comprehensive graphical process flows describing the R/3 functionality from different points of view. It contains scenarios, processes and functions, as well as components. The R/3 Reference Model can be viewed using SAP's Business Navigator and the Business Navigator Web, or using third-party modeling tools available from modeling partners.

Implementation Guide (IMG): Used to configure all system parameters for the business processes in R/3. It contains project management functionality and a menu-driven view of all R/3 Customizing activities. Every activity can be documented in detail, and responsibilities and statuses can be assigned.

Preconfigured systems:

  • Preconfigured US and Canadian clients: Provides a head start on baseline configuration. It includes a preconfigured US/Canadian chart of accounts, print forms, account determination, units of measure, etc. The predefined test sequences that are included can be a starting point for integration testing.
  • Preconfigured industry systems: A number of complete preconfigured clients consisting of an industry-specific model and preconfigured business processes for the needs of a particular industry in R/3 are available. For more information on preconfigured systems, see the description of Phase 2, Business Blueprint

Change and Transport System

Change and Transport System


The CTS is the central tool for managing changes to customizing and repository data that we make in the IMG or ABAP workbench.A Tansport request can be either customizing request or ABAP workbench request.




ABAP workbench request.


An ABAP workbench request can be created by ABAP workbench tool. Any changes or objects we develop through ABAP workbench are stored in Repository tables of SAP database.


As an ABAP developer will be working with ABAP workbench and thus you create work bench requests.

Customizing request



A customizing request can be created by the customizing tool IMG.


A functional consultant works with configuration tool IMG (SAP Implementation Guide) T-code SPRO, thus creating customizing requests.

Transport organizer: Transation Code SE10

Transport organizer is the tool provided by SAP which records and documents all changes to objects in the repository and customizing. The transaction code for transport organizer is SE10 or SE09.

Transport organizer is fully integrated with ABAP workbench and customizing tool IMG. That means you can navigate in both directions from transport organizer to ABAP workbench and reverse also.

Development class:

Development classes are used to group similar work objects that are being developed in a project.
While creating development class we must assign it to the transport layer.
All the objects assigned to that development class can be transported according to the routes defined in the transport layer.

Defining transport layer and routes is SAP BASIS administrator job. The transport layer defines transport 
route between the systems included in system landscape.

The development classes are themselves objects in the ABAP workbench.

Change Request:
Information source in the transport organizer that records and manages all changes made to repository
objects and customizing settings during a development project.
Task:
A task is assigned to a change request.

It is the information carrier in the transport organizer for entering and managing all changes to repository
objects and customizing settings performed by employees within a development project.