What is SPRO

S P R O as an acronym stands for SAP Project Reference Object. When you enter the transaction code SPRO on the command field of your SAP system, you’ll be directed automatically to the Customizing screen. On the customizing screen you’ll see all the customizing/configuration activities.

SPRO is use as short cut (transaction code) to access the IMG customizing screen. In the IMG customizing screen, you can display and access all the configuration activities to set-up SAP system to meet the specific needs and requirments of the client. It’s a single screen that provides a lot of flexibility in accessing the customizing transactions.

All the configuration  Setting for SAP R/3 Standard process will be done using the SPRO transaction Code.

As we have already discussed SAP is a table based configurable product, using the SPRO Transaction code you can change the configuration of the SAP.


SAP Landscapes


ASAP Implementation Methodology


Reason for SAP's Success

SAP Landscapes

Landscapes like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into 3 landscape DEV, QAS and PROD.

-  DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.
-  QAS may again have multiple clients for ex: 300- Integration Test, 700 to 710 Training.
-  PROD may have something like a 200 Production.

These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario. 

Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving every time. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example). 

You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients. 

But in the Testing client you can not even access SPRO  (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practiced in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory. 

The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.

Introduction to SAP

ASAP Implementation Methodology

ASAP methodology means nothing but standard process for implementation of SAP,  It consists of 5 phases.

Project preparation : consists of identifying team members and developing strategy as how to go. Look at the project scope document carefully it will tell you what SAP sub-modules in SAP you should be prepared for.It also Involves Project Plan preparation.

Business blueprint: Its the most Crucial phase in the entire project.

As is - Here you understand the existing business processes of the client . Your Business Process Owners collect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyze how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP.

Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes.

To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, there can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modeling you will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to wether a ABAP development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it.Here the as-is and to-be and gap analysis is explained. This is the document that you will be using to do your configuration in the realization phase. Make sure that you prepare the AS IS documentation and the TO BE Documentation and get it signed-Off from the customer. If both of these documents are not signed off then there will be definitely some problems when we proceed further for implementation.


Realization phase: The purpose of this phase is to implement all the business and process requirements based on the Business blueprint.
    Here you do the configuration in the development server (there are three clients -development,quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading data at this stage so you have more realistic data and your BDCs are tested.

Final Preperation and Cut Over activities
Once all modules unit testing is over then the configuration is trasported to the Quality server, where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in integration between various modules. Once all is okay from the QA server config is transported to the production server.
Go live preparation .  The collected master data is checked and the uploaded into production server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production server.

GO-Live and support:The Go-live milestone is itself is easy to achieve; a smooth and uneventful Go-live is another matter altogether. Preparation is the key, including attention to what-if scenarios related not only to the individual business processes deployed but also to the functioning of technology underpinning these business processes and preparation for ongoing support, including maintenance contracts and documented processes and procedures are essential.

Basic Screens in SAP

In this blog we will look into basic screen in the SAP. The screens are listed below.

1)      SAP Logon Screen,

2)      SAP Easy Access Screen

3)    Standard Report screen

SAP Logon Screen

The SAP R/3 System is a client server based system. The client concept enables the joint operation, in one system, of several enterprises that are independent of each other in business terms. During each user session you can only access the data of the client selected during the logon.

A client is, in organizational terms, an independent unit in the R/3 System. Each client has its own data environment and therefore its own master data and transaction data, assigned user master records and charts of accounts, and specific customizing parameters.

SAP systems are available in several languages. Use the Language input field to select the logon language for each session.

Multiple logons are always logged in the system beginning with Release 4.6. This is for security as well as licensing reasons. A warning message appears if the same user attempts to log on twice or more. This message offers three options:

• Continue with current logon and end any other logons in the system
• Continue with current logon without ending any other logons in the system (logged in system)
• Terminate current logon and the screen shot is as shown.

 

SAP Easy Access Screen

SAP Easy Access is the standard entry screen displayed after logon. Using the menu path Extras® Set start transaction you can select a transaction of your choice to be the default entry screen after logon.

You navigate through the system using a compact tree structure that you can adapt to your own specific requirements. Use the menu path Extras® Settings to change your view of the tree structure. You can use this to display technical names (transaction codes).

Enter a transaction code in the command field:

A transaction code (T-Code) is assigned to each function in R/3 (not each screen).

You can access the assigned transaction code from any screen in the R/3 System.

You can find the transaction code for the function you are working in under the Status option of the System menu.

For example, to display SAP Abap Editor data, enter “/n” and the appropriate

Transaction code (in this case “/nse38”).

Combination to make the cursor move from one (input) field group to the next. Use TAB to move between fields within a group.

The standard SAP screen consists of following elements.

Command field: You can use the command field to go to applications directly by entering the transaction code. You can find the transaction code either in the SAP Easy Access menu tree (see next slide) or in the relevant application under System® Status.

Menu bar: The menus shown here depend on which application you are working in. These menus contain cascading menu options.

Standard toolbar: The icons in the system function bar are available on all R/3 screens. Any icons that you cannot use on a particular screen are dimmed. If you leave the cursor on an icon for a moment, a small flag will appear with the name (or function) of that icon. You will also see the corresponding function key. The application toolbar shows you which functions are available in the current application.

Title bar: The title bar displays your current position and activity in the system.

Check boxes: Checkboxes allow you to select several options simultaneously within a group.

Radio buttons: Radio buttons allow you to select one option only.

Status bar: The status bar displays information on the current system status, for example, warning and error messages.

A tab provides a clearer overview of several information screens.

Options: You can set your font size, list colors, and so on here.

Reasons for SAP's Success.

There might be several other reasons for SAP's success and Domination in the ERP market, this particular blogs are my views on SAP's tremendous success in the ERP Market.

1)  Track Record
  The first and foremost reason is their good track record for the support services that SAP has, there might be a lot of vendor who might be a new player in the market or even an existing large player. No one has a good track record like SAP. for the small players, there is no guaranty that they will survive for next 5 years. This is a key factor which influences the Corporates decision making. In fact corporates will never like to buy a solution offered by companies with less than 5 years of existence.

2) Focus and adaptability
As we all know that SAP's primary focus is on ERP and it does not have any other vested interest in other areas as Oracle has in Database and Microsoft has it in other range of products. Other important factor is that it can be implemented on most of the OS and Database systems available in the market.

3) SAP Strong Partnership
Over the years SAP has build a strong partnership space. who contributes heavily to the success of SAP's ERP product in many domains.

4) Truly Global and Process Centric Approach
SAP's design is truly Global, means, the SAP product can be implemented in any country seamlessly and it can be integrated with many other existing software landscape. Allows easier global integration (barriers of currency exchange rates, language, and culture can be bridged easily).

5)Reducing Redundancy
SAP's can able to maintain centralized information thus reducing the redundancy of the information that gets stored in the Databases.

There are many more advantages of using the SAP products, the above are few most important of them in my View.

Introduction To SAP

Introduction

     SAP is the number one among the several ERP Vendors in the World. SAP is the world's largest business software company. It operates in four geographic regions: EMEA (Europe, Middle East, Africa), AMERICA (United States and Canada), LAC (Latin America and Caribbean), and APJ (Asia Pacific and Japan), which represents Japan, Australia, India, and parts of Asia. In addition, SAP operates a network of 115 subsidiaries, and has R&D (Research & Development) facilities around the globe in Germany, India, the US, Canada, France, Brazil, Turkey, China, Hungary, Israel, Ireland and Bulgaria.

SAP focuses on six industry sectors: process industries, discrete industries, consumer industries, service industries, financial services, and public services. It offers more than 25 industry solution portfolios for large enterprises and more than 550 micro-vertical solutions for mid size companies and small businesses.

Who Founded SAP.

SAP was founded in June 1972 as Systemanalyse und Programmentwicklung ("System Analysis and Program Development") by five former IBM engineers in Mannheim, Baden-Württemberg (Dietmar Hopp, Klaus Tschira,Hans-Werner Hector, Hasso Plattner, and Claus Wellenreuther).

Products,

SAP's products focus on Enterprise Resource Planning (ERP). The company's main product is SAP ERP. The current version is SAP ERP 6.0 and is part of the SAP Business Suite. Its previous name was R/3. The "R" of SAP R/3 stood for real-time – even though it is not a real-time solution. The number 3 related to the 3-tier architecture: database, application server and client (SAP GUI). R/2, which ran on Mainframe architecture, was the predecessor of R/3.

SAP product are consider excellent but not perfect.  The main problems with software product is that it can never be perfect.

SAP ECC is one of five enterprise applications in Sap’s Business Suite. The other four applications are:

• Customer Relationship Management (CRM) – helps companies acquire and retain customers, gain marketing and customer insight
• Product Lifecycle Management (PLM) – helps manufacturers with product-related information
• Supply Chain Management (SCM) – helps companies with the process of resourcing its manufacturing and service processes
• Supplier Relationship Management (SRM) – enables companies to procure from suppliers

Advantages of SAP 

The main advantage of using SAP as your company ERP system is that SAP have a very high level of integration among its individual applications which guarantee consistency of data throughout the system and the company itself.


SAP is a table drive customization software.  It allows businesses to make rapid changes in their business requirements with a common set of programs.  User-exits are provided for business to add in additional source code.  Tools such as screen variants are provided to let you set fields attributes whether to hide, display and make them mandatory fields.


This is what makes ERP system and SAP in particular so flexible.  The table driven customization are driving the program functionality instead of those old fashioned hard-coded programs.  Therefore, new and changed business requirements can be quickly implemented and tested in the system.


Many other business application software have seen this table driven customization advantage and are now changing their application software based on this table customizing concept.


Architecture of SAP R/3  system
The SAP R/3 System architecture consists of three layers:  Presentation, Application, and Data Storage. The following diagram illustrates the function served by each layer and how the layers work together:

Presentation 

This is where users of the SAP R/3 System will submit input to the SAP R/3 System for the processing of business transactions. It is also where the output from these transactions appears as output fields, reports, tables and spread sheets.

On the desktop level, R/3 offers a user-friendly graphical interface called SAP GUI. The system also integrates alternative interfaces for optimum compliance with your requirements. This includes integrating common PC applications. Information exchange is also carried out through the Internet, Kiosk touch screen systems and telephone applications.

Application

 An application is a logically independent component residing at the host operating system level within the SAP R/3 client/server environment. This component is represented by an application server in the SAP R/3 network. After a user initiates a request at the presentation level, logic is invoked to service and process that information. The application logic modules can reside on one centralized host machine or be distributed over several physical host machines within a particular SAP R/3 network. Typically, the update and en queue processes reside on the database server in the application layer. In most cases, the message, spool and gateway processes will also reside on the database server.

The database server may also be referred to as the “central server”. On the application level, R/3 offers sophisticated mechanisms to optimally use high-performance system

resources. The system implements interconnections between various applications so that they are practical from a business perspective. R/3 closes the gap between the exacting concept of a business transaction and transactions from a data processing perspective.

Data Storage

 On the database level, R/3 exclusively uses relational database systems by various manufacturers. R/3 is able to utilize the most advanced features of each database vendor’s product. In other words, it is not constrained by the lack of features in any individual database engine. Instead, it is able to fully use a supplier-specific implementation without jeopardizing it’s own portability.

SAP Modules:

Complete SAP Modules:

1.    SAP Basis

1.1.           Security (BC - SEC)

1.2.           Application Link Enabling (ALE)

1.3.           Remote Function Calls (RFC)

1.4.           Object Linking and Embedding (OLE)

1.5.           Common Program Interface Communications (CPI-C)

1.6.           Electronic Data Interchange (EDI)

1.7.           Customizing (BC-CUS)

1.8.           ABAP Programming and Runtime Environment (BC - ABA)

1.9.           Client Server Technology (BC - CST)

1.10.       Network Integration (BC - NET)

1.11.       Basis Services/ Communication Interfaces (BC - SRV)

1.12.       Computing Center Management System (BC - CCM)

1.13.       Upgrade General (BC - UPG)

1.14.       Change and Transport System (BC - CTS)

1.15.       Operating System Platform(BC - OP)

1.16.       Database Interface, database platforms (BC - DB)

1.17.       Front End Services (BC - FES)

1.18.       ABAP Workbench (BC - DWB)

1.19.       Documentation and Translation Tools (BC - DOC)

1.20.       Controls and Control Framework (BC - CI) 

1.21.       Business Management (BC - BMT)

1.22.       Middleware (BC - MID)

1.23.       Computer Aided Test Tool (BC - CAT)

1.24.       Ready to Run R/3 (BC - BRR)

1.25.       Authorisations System Monitoring with CCMS Workload Alert Monitor

2.    ABAP/4 Programming

2.1             ABAP Workbench

2.2             Menu Painter

2.3             Screen Painter

2.4             Data Dictionary

2.5             SAP Script

2.6             Business Workflow (BC - WF)

2.7             ALE

2.8             EDI

2.9             Business Connector

2.10         Business Server Pages

2.11         Internet Application Server

2.12         Mercator Report Painter

2.13         ALV reporting

2.14         Report writer

2.15         Dialog Programming

2.16         Repository Information System

2.17         ABAP 00

2.18         IDOCS

2.19         LSMW

2.20         Smartforms

2.21         EBP

2.22         ASAP methodology

2.23         ABAP Query

3.    SAP FI (Financial Accounting)

3.1.           General Ledger Accounting (FI - GL)

3.2.           Special Ledger (FI - SL)

3.3.           Extended Ledger

3.4.           Accounts Payable (FI- AP)

3.5.           Accounts Receivable (FI - AR)

3.6.           Asset Accounting (FI - AA)

3.7.           Bank Accounting

3.8.           Funds Management (FI - FM)

3.9.           Travel Management (FI-TM)

3.10.       Consolidation

4.    SAP CO (Controlling)

4.1.           Cost Centre Accounting (CO - CCA)

4.2.           Overhead Cost Controlling (CO - OM)

4.3.           Activity Based Coding (CO - ABC)

4.4.           Product Cost Controlling (CO - PC)

4.5.           Profitability Analysis (CO - PA)

4.6.           Material Ledger (CO - ML)

5.    SAP EC (Enterprise Controlling)

5.1.           Consolidation (EC - CS)

5.2.           Executive Information System (EC-EIS)

5.3.           Profit Center Accounting (EC - PCA)

5.4.           Business Planning and Budgeting

6.    SAP TR (Treasury)

6.1.           Cash Management (TR - CM)

6.2.           Loans Management (TR - LM)

6.3.           Market Risk Management (TR - MRM)

6.4.           Treasury Management (TR - TM)

6.5.           Funds Management (TR - FM)

6.6.           Information System

7.    SAP IM (Investment Management)

7.1.           Investment Programmes

7.2.           Investment Measures (orders/products)

7.3.           Corporation Wide Budgeting

7.4.           Appropriation Requests

7.5.           Automatic Settlement of Fixed Assets

7.6.           Depreciation Forecast

7.7.           Information System

8.    SAP HR (Human Resource)

8.1.           Recruitment

8.2.           Personnel Administration

8.3.           Benefits Administration

8.4.           Compensation Management

8.5.           Personnel Development

8.6.           Organizational Management

8.7.           Travel Management

8.8.           Training and Events Management

8.9.           Personnel Planning

8.10.       Time Management

8.11.       Incentive

8.12.       Wages

8.13.       Workflow

8.14.       Payroll

8.15.       Internet Scenarios

8.16.       Information System

9.    SAP SD (Sales and Distribution)

9.1.           Master Data

9.2.           Sales

9.3.           Sales Support

9.4.           Sales Information System

9.5.           Billing

9.6.           Special Business Transactions

9.7.           Shipping

9.8.           Transportation

9.9.           Credit Control

9.10.       QM in SD

9.11.       Internet

9.12.       Foreign Trade

9.13.       Electronic Data Interchange

10.           SAP Logistics Information System

10.1.       Purchasing Information System

10.2.       Sales Information System

10.3.       Inventory Controlling

10.4.       Retail Information System

10.5.       Production Planning and Control Information System

10.6.       Plant Maintenance Information System

10.7.       Project Information System

11.           SAP MM (Materials Management)

11.1.       Purchasing

11.2.       Invoice Verification

11.3.       Logistics (General)

11.4.       Logistics Information System

11.5.       Inventory Management

11.6.       Inventory / Valuations

11.7.       Materials Planning

11.8.       Workflow

11.9.       External Services Management

11.10.  QM in MM

11.11.  Warehouse Management

12.           SAP PM (Plant Maintenance)

12.1.       Preventative Maintenance

12.2.       Maintenance Order Management

12.3.       Maintenance Projects

12.4.       Service Management

12.5.       Maintenance Planning

12.6.       Equipment and Technical Objects

12.7.       Structuring Technical Systems

12.8.       PM Processing

12.9.       Work Clearance Management

12.10.  Internet Scenarios

12.11.  Customising

12.12.  Information System

13.           SAP PP (Production Planning)

13.1.       Make to Order (CR)

13.2.       Make to Order (PIR)

13.3.       Repetitive Manufacturing

13.4.       PP for Process Industries (PP - PI)

13.5.       PP - Processes

13.6.       Sales and Operations Planning

13.7.       Capacity requirements

13.8.       Master Planning

13.9.       KANBAN

13.10.  Production Orders

13.11.  Product Cost Planning

13.12.  Plant Data Collection

13.13.  Assembly Orders

13.14.  Information System

14.           SAP QM - Quality Management

14.1.       Planning

14.2.       Inspections

14.3.       Notifications

14.4.       Control

14.5.       Certificates

14.6.       Test Equipment Management

14.7.       QM-IS

15.           SAP BW (Business Warehousing)

15.1.       Data Warehousing

15.2.       BI Suite - Business Explorer

15.3.       BI Platform

15.4.       ODS Structures

15.5.       Development Technologies

15.6.       Info Cube

15.7.       Design Build

16.           SAP CS (Customer Service)

16.1.       Service Processing

16.2.       Controlling

16.3.       Service Contracts

16.4.       Workflow in Customer Service

17.           SAP SMB

17.1.       SAP SMB

18.           SAP CA (Cross Application Components)

18.1.       SAP Business Workflow

18.2.       Application Link Enabling (ALE)

19.           SAP PS (Project Systems)

19.1.       Basic Data

19.2.       Operational Structures

19.3.       Project Planning

19.4.       Approval

19.5.       Information System

19.6.       Project Execution and Integration

19.7.       Work Breakdown Structure

20.           mySAP SRM (Supplier Relationship Management)

20.1.       Self Service Procurement

20.2.       Service Procurement

20.3.       Plan Driven Procurement

20.4.       Spend Analysis

20.5.       Strategic Sourcing

20.6.       Catalogue Content Management

21.           mySAP SEM

21.1.       Business Consolidation (SEM-BCS)

21.2.       Business Information Collection (SEM-BIC)

21.3.       Business Planning and Simulation (BW-BPS)

21.4.       Corporate Performance Monitor (SEM-CPM)

21.5.       Stakeholder Relationship Management (SEM-SRM)

22.           mySAP CRM (Customer Relationship Management)

22.1.       CRM Enterprise

22.2.       Field Applications

22.3.       Interaction Center

22.4.       E-Commerce

22.5.       Channel Management

22.6.       Industry Specific CRM

23.           mySAP Product Life Cycle Management

23.1.       Document Management

23.2.       Engineering Change Management

23.3.       Enterprise Content Management

23.4.       Classification

23.5.       Basic Data for Process Manufacturing

24.           SAP SCM (SAP Supply Chain Management)

24.1.       SCM Process and Business Scenarios

24.2.       SAP Forecasting and Replenishment

24.3.       SAP Advance Planning and Optimization (SAP - APO)

24.4.       SAP Inventory Collaboration Hub (SAP - OCH)

24.5.       SAP Event Management (SAP - EM)

24.6.       SCM Basis

25.           SAP Netweaver

25.1.       SAP Masterdata Management

25.2.       Information Integration

25.3.       Portal Content

25.4.       Process Integration

25.5.       Knowledge Management

25.6.       Life Cycle Management

25.7.       SAP Business Intelligence

25.8.       SAP Visual Composer

25.9.       People Integration

25.10.  Application Platform

25.11.  SAP Web Application Server

25.12.  SAP Business Information Warehouse

25.13.  SAP Solution Manager

25.14.  SAP Enterprise Portal

25.15.  SAP Mobile Engine

25.16.  Security

26.           SAP IS (Industry Solutions) / SAP for Industries

SAP has the following industries specific solutions:

26.1.       Aerospace & Defence

26.2.       Consumer Products

26.3.       Defence & Security

26.4.       Retail

26.5.       Insurance

26.6.       Mill Products

26.7.       Higher Education & Research

26.8.       Industrial Machinery & Components

26.9.       Logistics Service Providers

26.10.  Automotive

26.11.  Chemicals

26.12.  Pharmaceuticals

26.13.  Banking

26.14.  Telecoms

26.15.  Life Sciences

26.16.  Mining

26.17.  Public Sector

26.18.  Service Provider

26.19.  Media

26.20.  Healthcare

26.21.  Oil & Gas

26.22.  Utilities

26.23.  Postal Services