SAP Tutorial - The Building Blocks

SAP Architecture

To be understood by you clearly, I have kept it simple. SAP has got three-tier architecture, as described below:
•    Presentation Layer
•    Application Layer
•    Database Layer

Presentation Layer – This is where you will be every day while working in SAP. It may be a desktop based graphical user interface or a web based UI. No Matter what the form, its work is to get you connected to the Application Layer and through that to underlying Database Layer.

Application Layer – These are programs which perform specific tasks or operations and are grouped together in the component area (eg Material Management, Sales and Distribution). It contains applications delivered by SAP AG as well as any Customized Program developed by your implementation Partner.

Database Layer – This is where the data is stored in form of table records. It is a relational database of your choice. SAP gives you freedom to choose the database platform.

Having described the SAP Architecture in a nutshell, now let us proceed towards doing the First Highly Critical Task of mapping the organization in SAP.  This is a very crucial activity and it should be completed as soon as possible. Basically you are creating your business’s organization structure from business process perspective. Each organization which is mapped in SAP is referred to by its ORGANISATION STRUCTURE IN SAP. 

This is the most basic Building Block on which you will later build and map all your business processes. Each Organization Structure (whether in real life or in SAP) has got certain basic Elements, so what we are required to do here is map the business’s building blocks into SAP at a higher level. Let’s go into detail with help of some examples.

In Business you have a company (having its registration number) for which you create Profit & Loss Statement and Draw a Balance Sheet at the end of Financial Year. So the company is a building block on the very top. Under this company you may have a Sales Department, Purchase Department, Production Department, and Accounts Department. Let us drill down further into Sales Department and may be you have different Channels of Sales, Different Brands which you manufacture or sell, and in order to reach your customer you have created a hierarchy of elements like a Sales Depot, A Sales Office, A Salesman etc. All of these are elements in your organisation’s business process map. Now if you are asked to create an organization structure for mapping in SAP, be overly cautious and described your organization in as much detail as possible from process perspective. It will help the consultants in drawing up an Organization Structure for you in SAP. Some of the elements used in SAP Organisation Structure are given below for your reference.

Organisation Structure in SAP


Some of key elements within SAP Organization Structure are listed below, please remember this is not an exhaustive list, it represents the most basic and required elements only.

  • Client – A Legally and organizationally independent Unit. This is the top most entity in SAP at which data can be recorded. It is a partition of data in database so you can multiple instances of same tables belonging to different Clients. When SAP is installed, 3 clients  are created in the database by default, these are 000, 001, and 066. These are client tables are populated by SAP with some basic configuration data which can be copied and altered to suit the business needs. Client 000 contains basic configuration settings, Client 001 has got some test data and Client 066 is used by SAP for early watch alerts of your systems.
  • Company – The Group Company, if any, where consolidation of different legal units is done.
  • Company Code - Lowest Legal Entity for which accounting is done.
  • Business Area – A Sub unit for which separate books of account may be needed
  • Profit Centres – Used for generating Profit Reports.
  • Cost Centres - To record expenses in proper heads for reporting purpose
  • Sales Organization – A hierarchical representation of your sales channels. In SAP, sales organization comprises of following sub-elements.
    • Distribution Channel – The avenues of sales eg, Distribution, Retail, Export, Institutional etc. This is a mandatory element.
    • Sales Division – This is basically the classification of goods sold at top level, it could be a brand or it could be product category, you have to choose carefully as the data entry in sales module and reporting will be dependent on this element. This too is a mandatory element.
    • Sales Offices – Optional Elements, primarily used for reporting. Use them if you have sales offices in different cities or geographies.
  • Sales Groups – Optional Element, here you can define different Group of Sales people, mainly used for reporting purpose.
  • Sales Area – Grouping of Sales Organization, Distribution channel and Division in such a way that you can control which channel can sell what. So it is basically a derived element which controls the type of sales that can be done a customer or a group of customers.
  • Plant – It is an operational unit within the company, it can be a manufacturing unit or it can be a warehouse.
  • Storage Locations – Logical Partitions within the plant where you can store materials. A plant can have multiple Storage Locations.
  • Purchasing Organization – it is a basic element which records all purchase transactions within SAP, a purchase organisation can cater to multiple sales organisations within the company.  For example you have 2 very distinct lines of sales businesses, one sells consumer products and the other sells cars, both of these sales lines belong to the same company and you have only one purchasing department which buys raw material as well as finished goods for both of these sales lines so in sap you will have one purchase organisation. Purchase organisation can be mapped to a client, or to plant or it could be a cross company entity
    • Purchasing Group – Key for a buyer or a group of buyers, who is/are responsible for certain purchasing activities. You can use it internally as the group responsible for the procurement of a material or a class of materials or if used externally, it is the medium through which contacts with the vendor are maintained.
We are now finished with describing the Building Blocks. In the Next Session I will give you example from one of my implementations.

Organization Structure Examples....
Read more »

SAP Tutorial - Background Material

Learning SAP


Background Material


Why this Blog? I have gone through many websites and blogs and found them to be too technical or having very little value. So I decided to write my own experience in my own way without going into too many technical details, hoping these ramblings would serve someone who is looking to roll out SAP. The Blog is for everyone, but it will be certainly more for those who are thinking of implementing SAP within their organization.

Comments and criticism are welcome from one and all.  I don’t claim to be an EXPERT in SAP as the SAP Universe is huge and I am a mere mortal human. So let’s begin….

I will keep this training Material simple yet powerful enough, for the beginner having no idea as to HOW SAP Works.
SAP is an ERP (Enterprise Resource Planning) software and much more as we will see later. The Software is one of most popular ERP software worldwide catering to business need of diverse businesses.
SAP is a composite Business Application having many components and each of those components may have several modules and each of those modules serve a specific business area.  The major components are called Financials (FI), Production (PP), Material Management (MM), Sales and Distribution (SD), Human Resources (HR) etc.
These components are connected to each other very well and that is why it is called an integrated ERP. The tight integration between components eliminates duplicity of data and also ensures that information comes from a single source resulting in better quality of decision making.
When an organisation takes the decision to roll-out or implement SAP within it, it has to first ask some questions as to why it is investing the time, money, and efforts. What are the business benefits that will be achieved by implementing SAP? How many of those benefits are quantifiable? What is the ROI and how it will be achieved? Do we have clear cut Business Processes Defined? Is there scope of further optimization of those processes during ERP Implementation? Do we have enough knowledge of business processes within the organization to take on this challenge? 

After getting answers to these above questions it still has to decide on the components that will be used by its users. For example, a manufacturing company may decide to use SD, PP, QM, MM, FI in the beginning. The component based structure of SAP allows you to use selective components and modules and when you think your foundation is strong, you systems are stabilised you can think about rolling out other components, business functions. The key to success here is a far sighted vision. The business should be able to visualize about its future position and alignment with SAP clearly so that there are no bottlenecks in future.

From my own experiences I can say that all complex business processes can be mapped in SAP ERP. Once you have the conviction and gathered enough knowledge about your business processes, take the bull by horns.
After taking the decision in favour of SAP, the next critical task is to find a good implementation partner / vendor who has got enough knowledge about your business domain and done some implementations in similar organisations.  It is the implementation partner / vendor who will ensure correct configuration of SAP ERP as per your business needs. The people deployed by ERP Implementation Partner or Vendor will work as Team with your business people and map all your requirements in SAP ERP.
So you will have to ensure that the people to be deployed by your selected implementation partner are up-to-the-mark and have decent knowledge of business processes similar to yours as well as good knowledge of SAP ERP Configuration.
Okay so you have finalised on SAP ERP, found the right implementation partner / vendor, the next task is creating the Hardware Infrastructure or Outsourcing it as the case may be. Selection of Servers for SAP ERP is very crucial and important as you won’t be able to change the infrastructure rapidly so my advice is plan well and plan the hardware for tomorrow as well.  There are tools available to help you in determining what kind of hardware you will need and we will describe them later. Also please note that most major hardware vendors may have SAP Certified server hardware which might fit your requirement with little customization. Involve your hardware vendor completely in creating the infrastructure for you.
Now you have all 3 entities ready, SAP ERP Software (licenses & Media), SAP ERP Implementation Partner, and Hardware for SAP.
Let’s now have a look at the next post  to understand how thing work in SAP World.

SAP Architecture.....
Read more »

SAP Table Maintenance Display

SAP Table Maintenance Display

In previous tutorial, you’ve learned how to create table maintenance generator by using TCODE SE54, today you will learn how to create the table display that utilizes TCODE SM30 to maintain the table values.
1. Execute TCODE SE93.
Enter the TCODE name, start with Z or Y.
Choose “Transaction with parameters (Parameter transaction).
Click “OK”

Read more »

Table Maintenance Generator in SAP

Table Maintenance Generator in SAP

Today I want to teach you how to create table maintenance generator in SAP, if you never heard about table maintenance generator, it’s actually used to maintain table values by using TCODE SE54 and after you create the table maintenance then you can display the values by using SM30.
Follow these steps to create table maintenance generator.
1. Execute TCODE SE54.
2. Enter the table name. Select “Generated Objects.” Click Create.
Read more »

Table Relationship In SAP

Table Relationship In SAP

Today I want to teach you how to find SAP table relationships, this is very useful for functional analyst to make a good program specification and also it can help ABAPer to look at the table relationships also.
The TCODE we’ll be using is SE11.
1. EXECUTE TCODE SE11 and enter the table name that you want to look at the relationship, in this tutorial I want to see table relationships between table EQUZ and ILOA, so I just type in the EQUZ table name and click on the display button.
Read more »

Convert Number To words Using ABAP

Convert Number To words Using ABAP  

Today I want to share some ABAP code samples that you can use to convert numbers or amount into words using SPELL_AMOUNT function module.
Here’s the ABAP Sample code:
data:
lw_spell LIKE spell,
saywords(150),
lv_text TYPE ltext,
p_amt TYPE eban-preis,
p_amt2(15),
p_waers type eban-waers.

START-OF-SELECTION.
p_amt = ‘123450′.
p_waers = ‘USD’.

SELECT SINGLE ktext INTO lv_text
FROM tcurt
WHERE spras = sy-langu
AND waers = p_waers.

TRANSLATE lv_text to UPPER CASE.
CALL FUNCTION ‘SPELL_AMOUNT’
EXPORTING
amount   = p_amt
currency = p_waers
filler   = ‘ ’
language = sy-langu
IMPORTING
in_words = lw_spell.

DATA: lv_cent TYPE spell.
lw_spell-decimal = lw_spell-decimal / 10.
IF lw_spell-decimal IS NOT INITIAL.
CALL FUNCTION ‘SPELL_AMOUNT’
EXPORTING
amount   = lw_spell-decimal
*        currency = lw_vbak-waerk
filler   = ‘ ’
language = sy-langu
IMPORTING
in_words = lv_cent.
ENDIF.

IF NOT lv_cent-word IS INITIAL.
CONCATENATE lw_spell-word ‘AND’ lv_cent-word ‘CENTS’
lv_text INTO saywords
SEPARATED BY space.
ELSE.
CONCATENATE lw_spell-word  lv_text INTO saywords
SEPARATED BY space.
ENDIF.
WRITE p_amt to p_amt2 CURRENCY p_waers.

WRITE:/ p_amt2, saywords.
“end code
Run the program and you will see the number has been converted into words.
18-0ct-10-01
Run the program


Read more »

How To Maintain Long Text Object in SAP

How To Maintain Long Text Object in SAP

Long Text has many usages in SAP, in this text object we can put on information such as names, job position without have to create any tables or user exits.
To read the information in the long text object, we’re can use the “READ_TEXT” function, You can check here to find out how to read from the text object.
The TCODE you can use to maintain long text object in SAP is SO10. Using this tcode you can edit or just display the value of the long text object.

After you execute the TCODE, you need to enter, TEXT NAME, TEXT ID and LANGUAGE. Click Display or Change To maintain the long text values.
Read more »

Stay Updated