Wednesday, 12 October 2011

SAP MM Introduction

We will Slowly move into the technical areas on SAP Rather than just having a look at the Generic Details about SAP. Now a Days there are some specialized modules available in SAP ERP to tackle the Specific Requirements of certain industries. We will First look at the MM(Material Management) Module in SAP. It is one of the biggest module in SAP.


This module mainly deals with the Procurement Process, Master Data (Material & Vendor Master), Inventory Management, Valuation of Material & Account Determination, Material Requirement Planning, Invoice Verification etc. This module is highly integrated with several modules in SAP.
SAP MM (Material Management) one the biggest functional module in SAP ERP. This module mainly deals with the Procurement Process, Master Data (Material & Vendor Master), Inventory Management, Valuation of Material & Account Determination, Material Requirement Planning, Invoice Verification etc. This module is highly integrated with several modules in SAP.
SAP Materials management (MM) covers all tasks within the supply chain, including consumption-based planning, planning, vendor evaluation and invoice verification. It also includes Inventory and Warehouse management to manage stock until usage dictates the cycle should begin again. Electronic Kan-ban/Just-in-Time delivery is supported.

Normal procurement process has the following steps:
  • Determination of requirement
  • Determination of source of supply
  • Vendor selection
  • Purchase order creation
  • Purchase order monitoring
  • Goods receipt
  • Invoice verification

Tuesday, 11 October 2011

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.

ERP - Why it is Required for an Organization

We have seen some thing about ERP and some thing About SAP which is the primary focus area of this Blog, But why all these ERP Softwares are required, Can't we manage all these activities with Custom developed softwares? 


The Answer for the above question lies in various Factors, they are 


Cost, 
  The Cost that involves in the Development of the new Custom software. While developing the software from the Scratch, you need to invest a lot in designing the process and then develop the code for the right from the scratch. Imagine the cost involved in all of them. Hence Organizations are increasingly adapt the ERP packages which are already built for the standard Business Process, you just need to implement them and customize the areas where there are some gap.


Best practice 
What are the key observation you see in any common enterprise is that they have many Business units and every second these departments exchange data and communicate with each other to achieve organizational goals collectively. It is clear that Communication and proper exchange of information helps better in achieving the goals of your organization. Every one is linked with each other for one or other needs say for eg. Sales exchange information with customers, sales provide information to marketing, marketing exchange communication with finance HR and so on. This is not just the basic case where the communication is internally, Exchange of information is with external customers also such as Share holders, creditors, vendors, etc. 


Adaptability with other vendors,
ERP allows you to introduce the latest technologies like Electronic Fund Transfer (EFT), Electronic Data Interchange (EDI), Internet, Intranet, Video conferencing, E-Commerce etc.

Most organizations across the world have realized that in a rapidly changing environment, it is impossible to create and maintain a custom designed software package which will cater to all their requirements and also be completely up-to-date. Realizing the requirement of user organizations some of the leading software companies have designed Enterprise Resource Planning software which will offer an integrated software solution to all the functions of an organization. 

Below is some of the major features of a basic ERP system which can help in one or the other ways.

ERP facilitates company-wide Integrated Information System covering all functional areas like Manufacturing, Selling and distribution, Payables, Receivables, Inventory, Accounts, Human resources, Purchases etc.,
It provides core corporate activities and increases customer service and thereby enhances the Corporate Image.
It provides a bridge between other departments to communicate and exchange data.
It not only communicates and exchange data between other departments but also helps across departments.
ERP helps for better Project Management.

It helps in eliminating most of the business problems like Material shortages, Productivity enhancements, Customer service, Cash Management, Inventory problems, Quality problems, Prompt delivery and so on
ERP not only addresses the current requirements of the company but also provides the opportunity of continually improving and refining business processes.
ERP provides business intelligence tools like Decision Support Systems (DSS), Executive Information System (EIS), Reporting, Data Mining and Early Warning Systems (Robots) for better decisions.

Components of ERP
• Sales and Marketing
• Master Scheduling
• Material Requirement Planning
• Capacity Requirement Planning
• Bill of Materials
• Purchasing
• Shop floor control
• Accounts Payable/Receivable
• Logistics
• Asset Management
• Financial Accounting

Service Oriented Architecture

SOA Concepts

Today, the concept of Service Oriented Architecture has become ubiquitous. Evidence from recent years establish that SOA is not just about hype, but a part of every major Business environment. The truth is, Service Oriented Architecture can be beneficial to Business only when it is utilized properly and when it is utilized to its potential. 

A Service-oriented Architecture is essentially a collection of services. these services communicate with each other. The communication can involve either simple data passing or it could involve two or more services co-ordinating some activity. Some means of connection services to each other is needed.

The technology of Web services is the most likely connection technology of service-oriented architectures. Web services essentially use XML to create a robust connection.

The following figure illustrates a basic service-oriented architecture. It shows a service consumer at the right sending a service request message to a service provider at the left. The service provider returns a response message to the service consumer. The request and subsequent response connections are defined in some way that is understandable to both the service consumer and service provider. How those connections are defined is explained in Web Services explained. A service provider can also be a service consumer.

 

Service Oriented Architecture is no longer a theory – it has moved into the realm of actual initiatives that can ensure that Businesses and investors receive high returns on their investments. It is vital to possess a keen understanding of various Service Oriented Architecture concepts in order to decide whether Service Oriented Architecture is suitable for your Business or not.

Why use Service Oriented Architecture?

Vast majority of Businesses working in the field of Information Technology have to justify their projects with a return on their investments. This puts Information Technology, as a field under enormous pressure. Information Technology must boast requirements that are increasingly responsive and flexible to the shifting needs of different Businesses.

Firms dealing with Information Technology must also be able to face the challenge of taking on an array of software systems that may or may not be compatible with one another. Moreover, Information Technology has to face demands to bring new commercial services to a much wider array of customers. Customers may access services through web interfaces, or may be part of a supply chain that needs to decrease the time and cost of manufacturing.

Thus, Information Technology companies are always on the look out for solutions that will help them meet the above demands – without having to spend a lot of money.

While Service Oriented Architecture may not solve all the problems posed by the increasingly complex realm of Information Technology, employing SOA tactics can bring a lot of benefits and rewards to a company. Typically, these benefits fit into one of the following three categories:

-Standardized interfaces and data models 
-Re-use 
-Composability

SOA Elements

Let us now take a look at some of the key features of Service Oriented Architecture. The best way to go about doing this is to break SOA down into its acrimonial elements. We’ll start with the last letter first: A for Architecture.

We will first examine architecture in reference to Service Oriented Architecture. Usually, in the realm of software, architecture tends to define the overall intercommunication and definition of different high level components. To put it simply, it is how a solution is broken down into logical units – and how they operate with one another. In a way, Service Oriented Architecture is representative of an approach to architecture that focuses on how services are defined and how they interact with one another.

Service Oriented Architecture is not something you can just go out and purchase. It is a set of architectural principles. While you might be able to directly purchase certain middle-ware that enables services and technologies, they alone do not constitute a Service Oriented Architecture.

Let us consider the SO part of SOA. Being service oriented basically means that you are employing an architecture that consists of a variety of services. This might sound familiar to those who have had some experience in the past with Object Oriented Design. In fact, Object Oriented Design and Service Oriented Architecture do have a lot of things in common.

By thinking in terms of services, you are effectively considering how to make your Business function so that it stands on its own. This approach is enabled via the use of Service Oriented Architecture. It takes into consideration the needs of both providers and consumers of services.

The providers of services offer functionality in the form of interfaces to the service capabilities they are providing. The consumer then accesses those capabilities. Such consumers may be an application or even another service provider. So, for instance, a checking account service may offer a functionality set that relates to a particular checking account. Such an account may offer the possibility to make deposits, withdrawals, create new accounts, and more. These capabilities, you may notice, are very particular to the context of a checking account service. We have not yet stated whether such a service might be provided by an ATM machine, a bank teller, or software.

A lot of people tend to believe that this definition of Service Oriented Architecture is merely the latest way to describe the functionality of applications. The fact is, a lot of applications in today’s day and age have already been built with an end user in mind. Thus, an application may encapsulate a group of several different tasks that are somehow related, yet also retain some degree of discretion.

Service Oriented Architecture distinguishes itself in that the consumer of certain application functionality may very well be another service or application.

Once these principles of architecture have been applied, you will find yourself with a lot of services that are able to interact as a means of providing a specific functionality set with benefits for your Business. This is when re-use comes into the game. You are now able to quickly build up another solution that will reuse a lot of these services while also providing additional services that the Business may require. Such services are woven into software system. In this scenario, they co-operate as a means of achieving Business objective, while possibly participating in some other systems that offer similar service capability for a possibly different end solution.

SOA vs. Other Architectures

Some observers claim that Service Oriented Architecture is merely another way that services and software can be sold. But SOA is a lot more than merely a buzz word. At the beginning, software was a set of code that ran somewhere on a large mainframe computer. This was where input was provided in the form of, say, punch cards.

As computer technology began to evolve, users would make use of simple text based terminals as a means of entering data, schedule jobs, etc. But software continued to grow larger. Rarely would other forms of software be relied upon to do these jobs.

Business logic steadily evolved over time so that much of the interface was moved to individual users’ desktops, while core Business logic and storage remained on a back room main computer. A lot of these applications still function in Businesses around the globe.

Sunday, 9 October 2011

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.