What is ERP?
ERP stands for Enterprise Resource Planning.
Enterprise Resource Planning systems integrate all data and processes of an organization into unified system.
The key feature of an ERP system is it uses a single or unified database to store data for the various system modules.
Various Modules which comes under ERP are listed below: a.
Manufacturing b. Supply Chain c. Financials d. CRM e. Human Resources f. Warehouse management
What is SAP?
SAP stands for Systems Applications and Products in data processing.
SAP is the fourth largest software company in the world. It ranks after Microsoft,
IBM and Oracle.
SAP Head quarters are in Walldorf, Germany. SAP was founded in 1972 by five former IBM engineers.
SAP released SAP R/2 version initially. The architecture of R/2 system is
Mainframe architecture.
Later SAP R/3 is released which is different from R/2 architecture. R stands for
Real time. 3 stands for 3 tier architecture.
There are over 100,800 installations at more than 28,000 companies. SAP products are used by 12 million people in more than 120 countries
ASAP
ASAP stands for Accelerated SAP. Its purpose is to help design SAP implementation in the most efficient manner possible. Its goal is to effectively optimize time, people, quality and other resources, using a proven methodology to implementation.
ASAP focuses on tools and training, wrapped up in a five-phase process oriented road map for guiding implementation.
The road map is composed of five well-known consecutive phases:
• Phase 1 Project Preparation
• Phase 2 Business Blueprint
• Phase 3 Realization
• Phase 4 Final Preparation
• Phase 5 Go-Live and support
In today's post we will discuss the first phase.
Phase 1 : Project Preparation
Phase 1 initiates with a retrieval of information and resources. It is an important time to assemble the necessary components for the implementation. Some important milestones that need to be accomplished for phase 1 include
• Obtaining senior-level management/stakeholder support
• identifying clear project objectives
• architect an efficient decision-making process
• creating an environment suitable for change and re-engineering
• building a qualified and capable project team.
Senior level management support:
One of the most important milestones with phase 1 of ASAP is the full agreement and cooperation of the important company decision-makers - key stake holders and others. Their backing and support is crucial for a successful implementation.
Clear project objectives: be concise in defining what your objectives and expectations are for this venture.
Vague or unclear notions of what you hope to obtain with SAP will handicap the implementation process. Also make sure that your expectations are reasonable considering your company's resources. It is essential to have clearly defined

ideas, goals and project plans devised before moving forward.
An efficient decision making process:
One obstacle that often stalls implementation is a poorly constructed decision- making process. Before embarking on this venture, individuals need to be clearly identified. Decide now who is responsible for different decisions along the way.
From day one, the implementation decision makers and project leaders from each area must be aware of the onus placed on them to return good decisions quickly.
Environment suitable for change and re engineering:Your team must be willing to accept that, along with new SAP software, things are going to change, the business will change, and information technology enabling the business will change as well. By implementing SAP, you will essentially redesign your current practices to model more efficient or predefined best business practices as espoused by SAP. Resistance to this change will impede the progress of your implementation.
ASAP- Second Phase- Business Blueprint
SAP has defined a business blueprint phase to help extract pertinent information about your company that is necessary for implementation. These blueprints are in the form of questionnaires that are designed to probe for information that uncovers how your company does business. As such, they also serve to document the implementation. Each business blueprint document essentially outlines your future business processes and business requirements. The kinds of questions asked are germane to the particular business function, as seen in the following sample questions:
1) What information do you capture on a purchase order?
2) What information is required to complete a purchase order?
Accelerated SAP question and answer database:
The question and answer database (QADB) is a simple although aging tool designed to facilitate the creation and maintenance of your business blueprint.
This database stores the questions and the answers and serves as the heart of your blue print. Customers are provided with a customer input template for each application that collects the data. The question and answer format is standard across applications to facilitate easier use by the project team.
Issues database:
Another tool used in the blueprinting phase is the issues database. This database stores any open concerns and pending issues that relate to the implementation. Centrally storing this information assists in gathering and then managing issues to resolution, so that important matters do not fall through the cracks. You can then track the issues in database, assign them to team members, and update the database accordingly.
ASAP Phase- 3 - Realization:
With the completion of the business in phase 2, "functional" experts are now ready to begin configuring SAP. The Realization phase is broken in to two parts.
1) Your SAP consulting team helps you configure your baseline system, called the baseline configuration.
2) Your implementation project team fine-tunes that system to meet all your business and process requirements as part of the fine tuning configuration.
The initial configuration completed during the base line configuration is based on the information that you provided in your blueprint document. The remaining approximately 20% of your configuration that was not tackled during the baseline configuration is completed during the fine tuning configuration. Fine tuning usually deals with the exceptions that are not covered in baseline configuration. This final bit of tweaking represents the work necessary to fit your special needs.
Configuration Testing:
With the help of your SAP consulting team, you segregate your business processes into cycles of related business flows. The cycles serve as independent units that enable you to test specific parts of the business process. You can also work through configuring the SAP implementation guide (IMG). A tool used to

assist you in configuring your SAP system in a step by step manner.
Knowledge Transfer:
As the configuration phase comes to a close, it becomes necessary for the
Project team to be self-sufficient in their knowledge of the configuration of your
SAP system. Knowledge transfer to the configuration team tasked with system maintenance (that is, maintenance of the business processes after Go-live) needs to be completed at this time.
In addition, the end users tasked with actually using the system for day-to-day business purposes must be trained.
ASAP Methodology - Phase 4 - Final Preparation:
As phase 3 merges into phase 4, you should find yourselves not only in the midst of SAP training, but also in the midst of rigorous functional and stress testing.
Phase 4 also concentrates on the fine tuning of your configuration before Go-live and more importantly, the migration of data from your old system or systems to
SAP.
Workload testing (including peak volume, daily load, and other forms of stress testing), and integration or functional testing are conducted to ensure the accuracy of your data and the stability of your SAP system. Because you should have begun testing back in phase 2, you do not have too far to go until Go-live. Now is an important time to perform preventative maintenance checks to ensure optimal performance at your SAP system.
At the conclusion of phase 4, take time to plan and document a Go-live strategy.
Preparation for Go-live means preparing for your end-users questions as they start actively working on the new SAP system.
ASAP - Phase 5 - 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.
Types of SAP Projects:
We can divide the SAP projects into three categories. They are
1) SAP Implementation Projects
2) SAP Support Projects
3) SAP Migration Projects
1) SAP Implementation Projects
In this type of projects, Customers are moving towards SAP software. Previously they might be using some other software.
2) SAP Support Projects
Once SAP project is implemented, it should be supported by the consultants in day-to-day business. In
Support projects, the support team helps the customer in day-to-day business.
3) SAP Migration Projects
As we see, SAP is continuously upgrading the R/3 software. Customers are moving from the older versions to new versions. When the customer decides to new version, it is called SAP
Migration Projects.
Now -a -days many customers are migrating from older versions like 4.5 or 4.6B,
4.6C to ECC 5.0 or ECC 6.0 versions.
Important transaction codes in ABAP

What is the use of Authorization Checks?
To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to authorization checks.
The following actions are subject to authorization checks that are performed before the start of a program or table maintenance and which the SAP applications cannot avoid:
· Starting SAP transactions (authorization object S_TCODE)
· starting reports (authorization object S_PROGRAM)
· Calling RFC function modules (authorization object S_RFC)
· Table maintenance with generic tools (S_TABU_DIS)
In coming posts, we will see how to add authorization checks for Reports and transactions.
Today we will discuss about table authorization checks.
Purpose of assigning authorization groups for tables:
You can assign authorization groups to tables to avoid users accessing tables using general access tools (such as transaction SE16). A user requires not only authorization to execute the tool, but must also have authorization to be permitted to access tables with the relevant group assignments. For this case, we deliver tables with predefined assignments to authorization groups. The assignments are defined in table TDDAT; the checked authorization object is S_TABU_DIS.
Now we will see how to assign/create authorization group for a table:
Go to SE54, Give the table name and choose authorization group and then click on create/change. You can create an authorization group.
Example:
You can assign a table to authorization group Z001. (Use transaction SM30 for table TDDAT) A user that wants to access this table must have authorization object S_TABU_DIS in his or her profile with the value
Z001 in the field DICBERCLS (authorization group for ABAP Dictionary objects).
Authorization Check:
In the earlier post, we came to know the importance of authorization check in real time environment. We know how to check authorization for table maintenance.
(Please refer earlier post).
Now we will see how to check authorization for Reports, Transactions, RFC function modules.
The following actions are subject to authorization checks that are performed before the start of a program or table maintenance and which the SAP applications cannot avoid:

Starting SAP transactions (authorization object S_TCODE)
starting reports

(authorization object S_PROGRAM)
Calling RFC function modules

(authorization object S_RFC)
Table maintenance with generic tools

(S_TABU_DIS)

The authorization objects S_TCODE, S_PROGRAM, S_RFC, and S_TABU_DIS are standard SAP provided.
Creating a new authorization object is not in the scope of ABAP developer. It will be taken care by SAP BASIS team.
To add authorization check to your program, you need to add the following code in your report. Imagine that you have created a transaction code for your report, then you should use the authorization object S_TCODE to check the authorization.
You can place the code in initialization event.
*Initialization
INITIALIZATION.
AUTHORITY-CHECK OBJECT 'S_TCODE'
ID 'TCD' FIELD 'ZEXAMPLE'.
IF sy-subrc <> 0. "Not Authorized
MESSAGE e003(ZZ) WITH 'TCD' 'ZEXAMPLE'.
ENDIF.
Here zexample is the transaction code created for the report.
OSS stands for On-line Service System.
What is the use of OSS?
In day-to day business customers who are using SAP software encounters problem or bugs with SAP software. To resolve the issues faced by customers
SAP has provided an on-line solution.
What? SAP software is having problems or bugs? Yes, any software product is not
100% pool-proof. SAP is continuously updating the versions for better performance and options.
Where can i access SAP OSS?
Log on to www.service.sap.com. Under the SAP Support Portal, click on SAP notes search.

Do i need user ID and password to enter into the OSS?
Yes, you need an User ID and Password to enter into the site. It will be provided by the BASIS Team in the Project. When they create SAP User ID, they will create
OSS notes ID also. You can also register individually in the site.
What is OSS Notes number?
After entering into SAP notes search, you can search for the problem using keyword appropriate for your problem. If you have specific OSS notes number with you, then you can directly enter the OSS notes number and you can see the Notes explanation.
How to apply OSS notes number?
Before applying OSS notes number into your SAP system. You need to check whether it is already implemented in your SAP system or not. If it is not implemented you can go ahead.
There are some OSS notes, which we should implement manually, that means we need to change the code in the programs/objects ourselves according to the steps mentioned in the problem.
I did not find any OSS notes appropriate for my problem or bug. What i have to do?
If the OSS notes displayed are not helpful to solve your problem. You can write to
SAP Service describing your problem. You problem will be answered by SAP
Support team.
How to apply OSS notes in my SAP system? What is the T-code and what are the steps.
In next post we will see it.
Attach T-Codes to Area Menu
We know how to create transaction codes. We can use the transaction code SE93
( Maintain Transaction).
Module pool programs/On-line programs must be attached to a transaction code to execute them.
Report programs (executable programs) can be executed directly without attaching them to the transaction codes.
But in real time, we do create custom transaction codes both for module pool programs/On-line programs and report programs.
Module pool programs and on-line programs are one and the same, where we do create screens using screen painter (SE51).
In real time business scenarios, after creating transaction codes, we need to attach them to Area Menu. End users can easily access the transaction codes if they are attached to Area Menu.
Area Menu is nothing but starting screen where in the left hand side we find menu.
The transaction code to maintain area menu is SE43. using SE43, we can attach our custom transaction codes to the area menu.
Please explore how to create nodes and sub nodes under menu using SE43.
Function Module:
What is a function module?

Broadly speaking Function module is one modularization technique.
The different modularization techniques available are
1) Include programs
2) Macros
3) Function Modules
4) Subroutines
5) Methods
What is the use of modularization?
1) Improves readability. That means, easy to read
2) Re-usability, the procedures can be used in other programs as well
3) Encapsulation of data
4) Reduces code redundancy, i.e. Avoids duplication of code
How to create Function Module?
We can create function modules by using function builder. The transaction code for function builder is SE37.
Is it necessary to attach the function module to a function group?
Yes, every function module must be attached to a function group. That means function group acts as a container. A single function group may contain one or more function modules which are logically related.
How many types of function modules are there?
There are two types of function modules
–
1) Normal
2) Remote (RFC)
How RFC function module differs from normal function module?
RFC stands for remote function call. As the name itself reveals, this function module can be called remotely by using RFC destination. Here remote means, external system, it may be a SAP system or Non-SAP system like Java system.
What are the advantages of function modules?
As we discussed above, it is one of the modularization techniques which helps code re-usability. We can handle exceptions using function modules.
How to know whether a given function module is normal or RFC function module?
1) Go to SE37.
2) Enter the name of the function module you are provided.
3) Click on DISPLAY
4) Choose Attributes tab
5) Under this tab, you can see Processing Type block.
6) If remote-enabled module is checked, then it is RFC otherwise normal function module.
How many types of RFCs are there?
There are five types of RFCs-
1) Synchronous RFC
2) Asynchronous RFC
3) Transactional RFC
4) Queued RFC
5) Parallel RFC
Synchronous RFC:
It is the very common method used in real business scenarios. Both the client and server must be available in this type of RFC.
The advantage is that you can get the result immediately, which means the RFC function module gives result or output immediately.
The syntax is
CALL FUNCTION <function module name> DESTINATION <RFC destination name>
In next post we will discuss all other RFC types.

Table Maintenance Generator
In this Post, we will discuss what is table maintenance generator?What is the use of it?
As all of you know, we can create database tables in SAP using transaction code
SE11. A table can be manipulated by a program or manually.
When creating table, you will find a check box 'Table maintenance allowed'. If we check that option, we can manually enter entries using SE16 or table maintenance generator screen.
SE16 is for data browser.
How to create table maintenance generator?
Go to SE11, give the table name and click on change. Then Go to utilities--> Table maintenance generator.
In the table maintenance generator screen, we should give Authorization Group,
Function Group name (Function Group name can be same as table name),
Maintenance type can be one step or two step, usually we will create with one step. we should give maintenance screen number. After clicking on create button, a table maintenance generator will be created.
To check it go to SM30 . In SM30, we find display, Maintain options.
We can view the table contents by choosing Display and we can create table entries by choosing Maintain.
Why we have to go for Table maintenance generator, when we can edit the table by SE16 or SE11, utilities->create entries?
Answer.
In the production system, end-users will not be having access to transaction codes like SE11 and SE16. Developers will not be having access to many transaction codes including the above two.
To view the contents of the database table, we will use SE16n in Production system. Please find out the difference between SE16 and SE16n.
All these authorizations will be maintained by BASIS team, by creating access profiles.
So in order to edit or create the contents of a database table, we should go for table maintenance generator. In real time, authorizations will be maintained in production system. (even in development and Test systems to some extent).
There is an audit like Sarbanes-Oxley Act for American clients, where every thing will be audited by government agency. To know more about SOX, use the links on the right hand side of this page.
The second reason is, we can edit or create multiple entries at a time, using table maintenance generator.
Apart from that we have options like 'Enter conditions' in table maintenance screen SM30. Please try to find out the use of those, by creating an example.
Table Maintenance generator: Difference between one step and two steps.
While creating table maintenance generator, we find below options:
1) When we choose one step, we have to give the screen number in Overview
Screen field.
2) When we choose two step, we have to give both overview screen number and single screen number.
You can give any number for screen. Don’t give 1000 screen number. As this number is reserved for selection screen.
When we choose two step, two screens will be created for table maintenance. For single step only one screen will be created.

When we choose two step, table maintenance will work as follows
Go to SM30, give the table name for which you have created table maintenance-
Overview screen will be displayed. To create entri es, when you click on ‘new entries’. Another screen will be displayed, where you give input and save. You can enter one record at a time.
When we choose single step, table maintenance will work as follows:
Go to SM30; give table name for which you have created table maintenance-
Overview screen will be displayed; To create entries click on ‘new entries’, you can enter the records on the same screen. You can enter multiple records at a time.
We use single step generally, as it is user friendly.
To completely understand the difference and above points please do exercise by creating table maintenance generator in both ways (using single step and two step).