Sap 582k3
This document was ed by and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this report form. Report r6l17
Overview 4q3b3c
& View Sap as PDF for free.
More details 26j3b
- Words: 3,429
- Pages: 15
NORTHERN INDIA ENGINEERING COLLEGE
[ D TO GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY, DELHI]
Assignment of Information system management IN PARTIAL FULLFILLMENT OF MASTER OF BUSINESS ISTRATION ( MBA )3rd SEMESTER 2013 -2015 SUBMITTED BY
SUBMITTED TO
POOJA ARORA MRS.SHUCHI SRIVASTAVA PRIYA TALWAR MANISHA GAUTAM SHALINI SINGH PRERNA ARORA
1.Introduction The research report is all about Sap. SAP SE (Systems Applications Products Societas Europaea) is a European multinational software corporation that makes enterprise software to manage business operations and customer relations. In this report we take the example of Team Lease pvt. Ltd. This project shows that how Sap is useful in this company, how it makes work easy and how it benefits the organization. Research can be descriptive or explanatory. In a descriptive study the study should be on an existing systems prevailing conditions of the topic under Research. In exploratory study the objective is to explore the area of study, by introducing new augments to the existing system and draw inferences and projections. the project should be valuable for an organization and be capable for implementation by the organisation. !he study should highlight in application in day to day functioning or in a specific area.
2.SAP SAP SE (Systems Applications Products Societas Europaea) is a European multinational software corporation that makes enterprise software to manage business operations and customer relations. Headquartered in Walldorf, Baden-Württemberg, , with regional offices around the world.[3] The company's best-known software products are its enterprise resource planning application systems and management (SAP ERP), its enterprise data warehouse product – SAP Business Warehouse (SAP BW),
SAP Business Objects software, and most recently, Sybase mobile products and the in-memory computing appliance SAP HANA. SAP is one of the largest software companies in the world. 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 realtime. The number 3 related to the 3-tier architecture: database, application server andclient (SAPgui). R/2, which ran on a Mainframe architecture, was the predecessor of R/3. Before R/2 came System RF, later dubbed R/1. SAP ERP 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
2.2 Concepts As a SAP beginner, you need a basic understanding of business processes, SAP acronyms and project concepts. I first learned about SAP and ERP’s (Enterprise Resource Planning systems) while in school at Grand Valley State University. The SAP Alliance business program included a mandatory ERP course. Before fumbling through SAP transactions, we were given a framework of common business processes. For example, to understand how to process an invoice, you must first understand the purpose of invoices and where this step fits in the overall order to cash process. We also needed some
key SAP and project to get a foundational understanding of what’s involved in a SAP project and the key components of the system. 2.2.1. Business Processes: If you have little or no exposure to a functional area, you first want to start with understanding the business processes that flow through SAP. Also keep in mind that most processes are crossfunctional and go end-to-end, meaning they through many departments in an organization. Even if you are in a technical role, you need a general understanding of what business drivers are behind your role. Michael Management courses provide a functional understanding as you learn about SAP. You may also find it valuable to invest in business/or SAP textbooks specific to your functional area. As you dive in to SAP, to always focus on how technology drives the business. Focusing on streamlining business processes can avoid creating unnecessarily complex technical design and avoid creating waste in the system. 2.2.2. SAP Acronyms: Secondly, understanding SAP acronyms and how you fit in the overall SAP project is important in quickly providing value. As a beginner, you’re probably finding the world of SAP to be filled with intimidating acronyms. Before you get too overwhelmed, realize that there is probably only a subset of acronyms and that will actually be relevant to your role in SAP. As you meet people in your project or organization, you can start to build a mental list of which areas you will integrate with and hone in on those and acronyms. To start, I recommend you check out Michael Management’s course SAP100 Essential SAP Skills. It’s the perfect course to feel comfortable with basic SAP concepts and . I’ve also found many websites that feature a list of SAP acronyms that you can use as reference. This wiki on SAP’s community network may be helpful: http://wiki.sdn.sap.com/wiki/display/HOME/SAP+Acronyms. Finall y, I recommend following SAP news to learn more about the SAP you hear. SAP’s community network is an active community of SAP customers and partners and its one of the best resources to learn about functional modules, SAP trends, and news. Keep in mind that it takes experience and your own research to feel comfortable with SAP acronyms.
Here are some common acronyms that every beginner will hear: Functional & Technical Modules: FI (Finance), CO (Controlling), SD (Sales & Distribution), MM (Materials Management), HR (Human Resources), BI (Business Intelligence), BW (Business Warehousing), PM (Plant Maintenance), QM (Quality Management), LE (Logistics Execution),
FSCM (Financial Supply Chain Management), PP (Production Planning), CRM (Customer Relationship Management), SEC (Security), Basis (Business Application Software Integration System) SAP Technical Acronyms: ABAP (Advances Business Application Programming), ALE (Application Link Enabling), ALV (SAP List Viewer), BAPI (Business Application Programming Interface), BEx (Business Explorer), BAdI (Business Add In), CATT (Computer Aided Test Tool), GUI (Graphical Interface), HTML (Hyper Text Markup Language), IMG (Implementation Guide), EDI (Electronic Data Interchange) LSMW (Legacy System Migration Workbench), OLE (Object Linking and Embedding), OSS (Online System), R/3 (Real Time 3 Tier), RFC (Remote Function Call), SOLMAN (Solution Manager), WD (Web Dynpro), SPRO (SAP Project Reference Object). 2.2.3. SAP Project Concepts: Finally, every beginner should understand basic SAP project concepts like the phases and roles people involved in a SAP implementation. Let’s begin with SAP deployment phases. ASAP, Accelerated SAP, is the standard implementation approach that is used on every SAP implementation. The approach consists of 5 phases: Project Prep, Business Blueprint, Realization, Final Prep, and Go Live & . Each phase includes important milestones that allow the project to continue to the next phase. A successful project has clear ‘exit’ and ‘entrance’ criteria that must be fulfilled for the project to move to the next phase. These criteria are reviewed by project management and key stakeholders to assess the projects performance. In the project preparation phase, project goals, scope and timeline are defined by project stakeholders and project management. In the blueprint phase, current business processes are documented and then redesigned to fit in SAP. Any requirement or process that does not fit using standard SAP functionality is documented as ‘gap’. This is a key part of the blueprint phase called ‘Fit/Gap Analysis’. In the realization phase, all requirements are configured in the system and the system is testing using integrated scenarios. Integration testing is cross-functional testing used to identify ‘defects’ or issues in the system that need to be resolved. In final preparation, testing is completed, training is delivered, and cutover steps are performed. Cutover involves all the steps necessary to go from the old, legacy system to SAP.
Finally, Go Live and occurs when s begin to perform their job in SAP and the project team monitors and s s. If you are fortunate enough to a project in the beginning phases, you may have a better understanding of how a project moves from project preparation, to blueprint, to realization, to final preparation, and in to go live and . Realistically, most resources are brought in to a project as things ramp up in the blueprint and realization phases. Next, it’s key to understand who is involved in a SAP implementation to understand where you fit in. At the top level, you have corporate executives that are deemed project stakeholders. It is their job to oversee the project from a high level and ensure it fulfills the defined goals and objectives. Below stakeholders is the project management which is more hands on in overseeing the project and closely monitors each functional and technical area of the project. Project management helps mitigate risks and issues, delivers project messaging, and keeps the project within the timeline and budget. Heading up each functional and technical team is a team lead. Team leads oversee team and communicate status, risks, and issues to project management. Functional team configure the system to meet business requirements and write functional specifications for customized needs. Technical team work in a variety of roles: security, ABAP development, data conversion, Basis, etc. By focusing in on these 3 concepts, I hope you can quickly come up on the SAP learning curve and provide value on your project. If you enjoyed this blog, you may be interested in my book, The Essential SAP Career Guide. It is a comprehensive guide to starting your career and covers job search tips, key skills for your first job, and how to choose consulting vs. industry positions.
3.An Implementation of SAP Once a company decides to buy SAP, a consulting company is being hired for the implementation. The consulting company analyze the business process of the company and prepare a blueprint. Sometimes the business process is reengineered (BPR) to accommodate SAP's functionalities. The second step is installation of SAP and setting up three clients namely development client, test client and production clients.
In the development client the SAP functional and development group start configuring the SAP based on the blueprint. Once it is completely configured, it is being transported to test client for testing using real time data. Once testing is successful, the configuration is being transported to production client to be used by real-time s. So this process makes SAP more reliable and robust in production. Preparation Before Implementing SAP SAP R/3 implementation is generally a key project for any organization. It is necessary to do preparation before implementation. Many organizations speak of "transferring technology." But what does that mean? Transfer technology involves transfer of the system which includes the
hardware software people processes information organization structure synchronization function and behavior. It becomes obvious that the transfer of any part of the system, without the rest of it, does not transfer technology. In our context, the software SAP/3 is
being changed. In most of the cases the hardware needs to be changed. The people need training to operate SAP system. But unfortunately, many organizations fail to understand that they need to change their processes. SAP is a package & it contains many best practices suitable to almost each industry. The designer (configuring the system) must design the system keeping the objective of the business objective in mind. The should be prepared to change it’s processes and ensure that the objective of the processes is met. This should be done without or minimum distortion of the processes designed by SAP. This is a big challenge to the designer as well as . It should noted that the representative involved in the system design should be empowered for low level BPR decisions. Also the information stored in the system will be in different form than the legacy system. The must be prepared & trained for the changed. The major challenge is behavioral change. Implementation of SAP R/3 system changes relationship of different persons, it gives/denies access to information which was not available/available to the person, it changes processes and control functions. This all gives behavioral issues. To get best out of SAP, these issues must be addressed before implementation. SAP R/3 re-engineers many processes and the fear of downsizing and loosing job hinders free acceptance of SAP in many organizations. This fear hinders free communication between the end-s and SAP system designer. The communication is a vital element in successful implementation of SAP R/3. This issue of 'Fear Of Downsizing' must be addressed before starting implementation project. ASAP Implementation Methodology Any enterprise application software has to cover a broad spectrum of functionality, yet to be configured enough to meet specific requirements. SAP achieves this by ASAP methodology & R/3 Business Engineer. AcceleratedSAP (ASAP) is SAP’s standard implementation methodology. It contains the Roap, a step-by step guide that incorporates experience from many years of implementing SAP. Quality checks are incorporated at end of each phase to ensure quality of deliverables and monitor critical success factors.
ASAP is delivered as a PC based package, so that an implementation project can begin prior to having an SAP R/3 system installed ASAP Tools ASAP Roap ASAP and Business Engineer have compatibility with many third party modeling tools and packages like MS Excel etc Creating the Business Blueprint for Implementation Projects Purpose To create a Business Blueprint during the implementation of mySAP.com solution to document the business processes in an enterprise, and to decide which processes should realize in SAP system. The use of Business Blueprint in the Solution Manager during the realization phase (configuration and testing) should continue. It needs to reuse the project structure created in the Business Blueprint phase, to configure and generate test plans. One can also display, change and enhance project documentation created during the Business Blueprint phase, during configuration. Prerequisites You want to implement a mySAP.com solution. You have completed the Project Preparation: you have defined an implementation project and a system landscape in the project istration of the SAP Solution Manager. Process Flow Create a Blueprint structure, using predefined substructures. Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains. Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements.
Create the project documentation and save it in the Business Blueprint. Assign transactions to process steps. This specifies which transactions in the system correspond to the process steps in your enterprise. Print the Business Blueprint document. When the Business Blueprint is complete, you can start to set up the development system landscape. Result You have created your Business Blueprint and set up your development system landscape. You can reuse the Business Blueprint and the project structure to configure and test your business processes
Business Blueprint Use This function documents the business processes in your company that you want to implement in the system. In a Business Blueprint for Projects, you create a project structure in which relevant business scenarios, business processes and process steps are organized in a hierarchical structure. You can also create project documentation and assign it to individual scenarios, processes or process steps. You then assign transactions to each process step, to specify how your business processes should run in your SAP Systems. The Business Blueprint is a detailed description of your business processes and system requirements. You can print it out. Integration You can continue to use the project documentation and the project structure that you create during the Business Blueprint, in the configuration and test organization phases.
• When you configure your business processes, the system displays the Business Blueprint project structure. You can use the Business Blueprint project structure as a point of reference during configuration. • You can also display and edit the project documentation from the Business Blueprint phase, during configuration. • You base all test plans that you create during test organization, on the Business Blueprint project structure. The transactions that you assign to process steps in the Business Blueprint are put in test plans during test plan generation, and run as function tests to test the transactions. Prerequisites You have created a project of type implementation, template, or upgrade, in the project istration. Features Scope of the transaction Business Bueprint Function Tab Create a project structure Structure
Display the following documentation: • Documentation delivered by SAP, e.g. scenario descriptions • Documentats from templates, e.g. from template projects To be able to edit general documentation, copy it to the Project Documentation tab. General Documentation Assign documents to structure elements Create, Change, documents Project Documentation Input istration data, e.g. project status, team assigned, planned and actual resources istration
Assign transactions and programs to structure elements Transactions Create, Display and Edit messages Messages Display and Create a process graphic Create a process graphic Graphic
Where-used list: • Use in project • Use in other projects • Go to use by double-click • General Documentation • Project Documentation • Transactions
General Functions Function Navigation Change the sequence, hide or show tabs Settings ® -Specific Translate project structure
Activities 1. Create a Blueprint structure in the Structure tab, using predefined substructures. 2. Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains.
3. Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements. 4. Create project documentation to save in the Business Blueprint, in the Project Documentation tab. 5. Assign transactions to process steps in the Transactions tab. This specifies which transactions in the system correspond to the process steps in your enterprise. 6. Print the Business Blueprint document. 7. When the Business Blueprint is complete, you can start to set up the development system landscape. Result You have specified a Business Blueprint. You can reuse the Business Blueprint and the project structure to configure and test your business processes.
Business Blueprint Definition A Business Blueprint documents the business process requirements of a company. In collaborative business processes, several companies are involved. Use The Business Blueprint gives you a general idea of how your business processes could be mapped in one or more SAP Systems. The Business Blueprint documents in detail the scope of business scenarios, business processes, process steps, and the requirements of a mySAP.com solution implementation.
Structure A Business Blueprint compises the following structure elements in a hierarchy: • Organizational units • Master data • Business scenarios • Business processes • Process steps You assign content, for example, project documentation, Business Configuration Sets, or transactions to individual structure elements, in the SAP Solution Manager. You can also create structure elements for organizational units and master data, below a business scenario. You only use these structure elements if the organizational units and master data are only relevant to the business process above them in the structure.
4.CONCLUSION While the tendency is to view upgrades as a necessary evil in the enterprise software market, the reality is that upgrades can be an important part of a company's overall competitive profile. This happens ideally in the case of a functional upgrade, though it can also be the case with a technical upgrade that unleashes a capability, such as Unicode , that in turn helps open up new markets and opportunities. Helpful contents on SAP HR to assist those ing the SAP Human Resource Management Modules.
The SAP HR module enables companies to effectively manage information about the people in their organization. It is integrated with other SAP modules and external systems.
From the Organization Management perspective, companies can model a business hierarchy, the relationships of employees to various business units and the reporting structure among employees.
The Personnel istration (PA) sub module helps employers to track employee master data, work schedules, salary and benefits information.
The Personnel Development (PD) functionality focuses on employees' skills, qualifications and career plans.
Finally, the Time Evaluation and Payroll sub modules process attendance and absences, gross salary and tax calculations, and payments to employees and third party vendors. Hence, in my suggestions SAP HR is an important aspect for an organization.
5.ACKNOWLEDGEMENTS We would like to thank our ISM Lecturer, Mrs. SHUCHI SRIVASTAVA for her contributions,insights and . References http://en.wikipedia.org/wiki/SAP_SE http://scn.sap.com/community/uac/blog/2013/04/26/3-concepts-for-sapbeginners http://scn.sap.com/thread785683
[ D TO GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY, DELHI]
Assignment of Information system management IN PARTIAL FULLFILLMENT OF MASTER OF BUSINESS ISTRATION ( MBA )3rd SEMESTER 2013 -2015 SUBMITTED BY
SUBMITTED TO
POOJA ARORA MRS.SHUCHI SRIVASTAVA PRIYA TALWAR MANISHA GAUTAM SHALINI SINGH PRERNA ARORA
1.Introduction The research report is all about Sap. SAP SE (Systems Applications Products Societas Europaea) is a European multinational software corporation that makes enterprise software to manage business operations and customer relations. In this report we take the example of Team Lease pvt. Ltd. This project shows that how Sap is useful in this company, how it makes work easy and how it benefits the organization. Research can be descriptive or explanatory. In a descriptive study the study should be on an existing systems prevailing conditions of the topic under Research. In exploratory study the objective is to explore the area of study, by introducing new augments to the existing system and draw inferences and projections. the project should be valuable for an organization and be capable for implementation by the organisation. !he study should highlight in application in day to day functioning or in a specific area.
2.SAP SAP SE (Systems Applications Products Societas Europaea) is a European multinational software corporation that makes enterprise software to manage business operations and customer relations. Headquartered in Walldorf, Baden-Württemberg, , with regional offices around the world.[3] The company's best-known software products are its enterprise resource planning application systems and management (SAP ERP), its enterprise data warehouse product – SAP Business Warehouse (SAP BW),
SAP Business Objects software, and most recently, Sybase mobile products and the in-memory computing appliance SAP HANA. SAP is one of the largest software companies in the world. 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 realtime. The number 3 related to the 3-tier architecture: database, application server andclient (SAPgui). R/2, which ran on a Mainframe architecture, was the predecessor of R/3. Before R/2 came System RF, later dubbed R/1. SAP ERP 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
2.2 Concepts As a SAP beginner, you need a basic understanding of business processes, SAP acronyms and project concepts. I first learned about SAP and ERP’s (Enterprise Resource Planning systems) while in school at Grand Valley State University. The SAP Alliance business program included a mandatory ERP course. Before fumbling through SAP transactions, we were given a framework of common business processes. For example, to understand how to process an invoice, you must first understand the purpose of invoices and where this step fits in the overall order to cash process. We also needed some
key SAP and project to get a foundational understanding of what’s involved in a SAP project and the key components of the system. 2.2.1. Business Processes: If you have little or no exposure to a functional area, you first want to start with understanding the business processes that flow through SAP. Also keep in mind that most processes are crossfunctional and go end-to-end, meaning they through many departments in an organization. Even if you are in a technical role, you need a general understanding of what business drivers are behind your role. Michael Management courses provide a functional understanding as you learn about SAP. You may also find it valuable to invest in business/or SAP textbooks specific to your functional area. As you dive in to SAP, to always focus on how technology drives the business. Focusing on streamlining business processes can avoid creating unnecessarily complex technical design and avoid creating waste in the system. 2.2.2. SAP Acronyms: Secondly, understanding SAP acronyms and how you fit in the overall SAP project is important in quickly providing value. As a beginner, you’re probably finding the world of SAP to be filled with intimidating acronyms. Before you get too overwhelmed, realize that there is probably only a subset of acronyms and that will actually be relevant to your role in SAP. As you meet people in your project or organization, you can start to build a mental list of which areas you will integrate with and hone in on those and acronyms. To start, I recommend you check out Michael Management’s course SAP100 Essential SAP Skills. It’s the perfect course to feel comfortable with basic SAP concepts and . I’ve also found many websites that feature a list of SAP acronyms that you can use as reference. This wiki on SAP’s community network may be helpful: http://wiki.sdn.sap.com/wiki/display/HOME/SAP+Acronyms. Finall y, I recommend following SAP news to learn more about the SAP you hear. SAP’s community network is an active community of SAP customers and partners and its one of the best resources to learn about functional modules, SAP trends, and news. Keep in mind that it takes experience and your own research to feel comfortable with SAP acronyms.
Here are some common acronyms that every beginner will hear: Functional & Technical Modules: FI (Finance), CO (Controlling), SD (Sales & Distribution), MM (Materials Management), HR (Human Resources), BI (Business Intelligence), BW (Business Warehousing), PM (Plant Maintenance), QM (Quality Management), LE (Logistics Execution),
FSCM (Financial Supply Chain Management), PP (Production Planning), CRM (Customer Relationship Management), SEC (Security), Basis (Business Application Software Integration System) SAP Technical Acronyms: ABAP (Advances Business Application Programming), ALE (Application Link Enabling), ALV (SAP List Viewer), BAPI (Business Application Programming Interface), BEx (Business Explorer), BAdI (Business Add In), CATT (Computer Aided Test Tool), GUI (Graphical Interface), HTML (Hyper Text Markup Language), IMG (Implementation Guide), EDI (Electronic Data Interchange) LSMW (Legacy System Migration Workbench), OLE (Object Linking and Embedding), OSS (Online System), R/3 (Real Time 3 Tier), RFC (Remote Function Call), SOLMAN (Solution Manager), WD (Web Dynpro), SPRO (SAP Project Reference Object). 2.2.3. SAP Project Concepts: Finally, every beginner should understand basic SAP project concepts like the phases and roles people involved in a SAP implementation. Let’s begin with SAP deployment phases. ASAP, Accelerated SAP, is the standard implementation approach that is used on every SAP implementation. The approach consists of 5 phases: Project Prep, Business Blueprint, Realization, Final Prep, and Go Live & . Each phase includes important milestones that allow the project to continue to the next phase. A successful project has clear ‘exit’ and ‘entrance’ criteria that must be fulfilled for the project to move to the next phase. These criteria are reviewed by project management and key stakeholders to assess the projects performance. In the project preparation phase, project goals, scope and timeline are defined by project stakeholders and project management. In the blueprint phase, current business processes are documented and then redesigned to fit in SAP. Any requirement or process that does not fit using standard SAP functionality is documented as ‘gap’. This is a key part of the blueprint phase called ‘Fit/Gap Analysis’. In the realization phase, all requirements are configured in the system and the system is testing using integrated scenarios. Integration testing is cross-functional testing used to identify ‘defects’ or issues in the system that need to be resolved. In final preparation, testing is completed, training is delivered, and cutover steps are performed. Cutover involves all the steps necessary to go from the old, legacy system to SAP.
Finally, Go Live and occurs when s begin to perform their job in SAP and the project team monitors and s s. If you are fortunate enough to a project in the beginning phases, you may have a better understanding of how a project moves from project preparation, to blueprint, to realization, to final preparation, and in to go live and . Realistically, most resources are brought in to a project as things ramp up in the blueprint and realization phases. Next, it’s key to understand who is involved in a SAP implementation to understand where you fit in. At the top level, you have corporate executives that are deemed project stakeholders. It is their job to oversee the project from a high level and ensure it fulfills the defined goals and objectives. Below stakeholders is the project management which is more hands on in overseeing the project and closely monitors each functional and technical area of the project. Project management helps mitigate risks and issues, delivers project messaging, and keeps the project within the timeline and budget. Heading up each functional and technical team is a team lead. Team leads oversee team and communicate status, risks, and issues to project management. Functional team configure the system to meet business requirements and write functional specifications for customized needs. Technical team work in a variety of roles: security, ABAP development, data conversion, Basis, etc. By focusing in on these 3 concepts, I hope you can quickly come up on the SAP learning curve and provide value on your project. If you enjoyed this blog, you may be interested in my book, The Essential SAP Career Guide. It is a comprehensive guide to starting your career and covers job search tips, key skills for your first job, and how to choose consulting vs. industry positions.
3.An Implementation of SAP Once a company decides to buy SAP, a consulting company is being hired for the implementation. The consulting company analyze the business process of the company and prepare a blueprint. Sometimes the business process is reengineered (BPR) to accommodate SAP's functionalities. The second step is installation of SAP and setting up three clients namely development client, test client and production clients.
In the development client the SAP functional and development group start configuring the SAP based on the blueprint. Once it is completely configured, it is being transported to test client for testing using real time data. Once testing is successful, the configuration is being transported to production client to be used by real-time s. So this process makes SAP more reliable and robust in production. Preparation Before Implementing SAP SAP R/3 implementation is generally a key project for any organization. It is necessary to do preparation before implementation. Many organizations speak of "transferring technology." But what does that mean? Transfer technology involves transfer of the system which includes the
hardware software people processes information organization structure synchronization function and behavior. It becomes obvious that the transfer of any part of the system, without the rest of it, does not transfer technology. In our context, the software SAP/3 is
being changed. In most of the cases the hardware needs to be changed. The people need training to operate SAP system. But unfortunately, many organizations fail to understand that they need to change their processes. SAP is a package & it contains many best practices suitable to almost each industry. The designer (configuring the system) must design the system keeping the objective of the business objective in mind. The should be prepared to change it’s processes and ensure that the objective of the processes is met. This should be done without or minimum distortion of the processes designed by SAP. This is a big challenge to the designer as well as . It should noted that the representative involved in the system design should be empowered for low level BPR decisions. Also the information stored in the system will be in different form than the legacy system. The must be prepared & trained for the changed. The major challenge is behavioral change. Implementation of SAP R/3 system changes relationship of different persons, it gives/denies access to information which was not available/available to the person, it changes processes and control functions. This all gives behavioral issues. To get best out of SAP, these issues must be addressed before implementation. SAP R/3 re-engineers many processes and the fear of downsizing and loosing job hinders free acceptance of SAP in many organizations. This fear hinders free communication between the end-s and SAP system designer. The communication is a vital element in successful implementation of SAP R/3. This issue of 'Fear Of Downsizing' must be addressed before starting implementation project. ASAP Implementation Methodology Any enterprise application software has to cover a broad spectrum of functionality, yet to be configured enough to meet specific requirements. SAP achieves this by ASAP methodology & R/3 Business Engineer. AcceleratedSAP (ASAP) is SAP’s standard implementation methodology. It contains the Roap, a step-by step guide that incorporates experience from many years of implementing SAP. Quality checks are incorporated at end of each phase to ensure quality of deliverables and monitor critical success factors.
ASAP is delivered as a PC based package, so that an implementation project can begin prior to having an SAP R/3 system installed ASAP Tools ASAP Roap ASAP and Business Engineer have compatibility with many third party modeling tools and packages like MS Excel etc Creating the Business Blueprint for Implementation Projects Purpose To create a Business Blueprint during the implementation of mySAP.com solution to document the business processes in an enterprise, and to decide which processes should realize in SAP system. The use of Business Blueprint in the Solution Manager during the realization phase (configuration and testing) should continue. It needs to reuse the project structure created in the Business Blueprint phase, to configure and generate test plans. One can also display, change and enhance project documentation created during the Business Blueprint phase, during configuration. Prerequisites You want to implement a mySAP.com solution. You have completed the Project Preparation: you have defined an implementation project and a system landscape in the project istration of the SAP Solution Manager. Process Flow Create a Blueprint structure, using predefined substructures. Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains. Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements.
Create the project documentation and save it in the Business Blueprint. Assign transactions to process steps. This specifies which transactions in the system correspond to the process steps in your enterprise. Print the Business Blueprint document. When the Business Blueprint is complete, you can start to set up the development system landscape. Result You have created your Business Blueprint and set up your development system landscape. You can reuse the Business Blueprint and the project structure to configure and test your business processes
Business Blueprint Use This function documents the business processes in your company that you want to implement in the system. In a Business Blueprint for Projects, you create a project structure in which relevant business scenarios, business processes and process steps are organized in a hierarchical structure. You can also create project documentation and assign it to individual scenarios, processes or process steps. You then assign transactions to each process step, to specify how your business processes should run in your SAP Systems. The Business Blueprint is a detailed description of your business processes and system requirements. You can print it out. Integration You can continue to use the project documentation and the project structure that you create during the Business Blueprint, in the configuration and test organization phases.
• When you configure your business processes, the system displays the Business Blueprint project structure. You can use the Business Blueprint project structure as a point of reference during configuration. • You can also display and edit the project documentation from the Business Blueprint phase, during configuration. • You base all test plans that you create during test organization, on the Business Blueprint project structure. The transactions that you assign to process steps in the Business Blueprint are put in test plans during test plan generation, and run as function tests to test the transactions. Prerequisites You have created a project of type implementation, template, or upgrade, in the project istration. Features Scope of the transaction Business Bueprint Function Tab Create a project structure Structure
Display the following documentation: • Documentation delivered by SAP, e.g. scenario descriptions • Documentats from templates, e.g. from template projects To be able to edit general documentation, copy it to the Project Documentation tab. General Documentation Assign documents to structure elements Create, Change, documents Project Documentation Input istration data, e.g. project status, team assigned, planned and actual resources istration
Assign transactions and programs to structure elements Transactions Create, Display and Edit messages Messages Display and Create a process graphic Create a process graphic Graphic
Where-used list: • Use in project • Use in other projects • Go to use by double-click • General Documentation • Project Documentation • Transactions
General Functions Function Navigation Change the sequence, hide or show tabs Settings ® -Specific Translate project structure
Activities 1. Create a Blueprint structure in the Structure tab, using predefined substructures. 2. Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains.
3. Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements. 4. Create project documentation to save in the Business Blueprint, in the Project Documentation tab. 5. Assign transactions to process steps in the Transactions tab. This specifies which transactions in the system correspond to the process steps in your enterprise. 6. Print the Business Blueprint document. 7. When the Business Blueprint is complete, you can start to set up the development system landscape. Result You have specified a Business Blueprint. You can reuse the Business Blueprint and the project structure to configure and test your business processes.
Business Blueprint Definition A Business Blueprint documents the business process requirements of a company. In collaborative business processes, several companies are involved. Use The Business Blueprint gives you a general idea of how your business processes could be mapped in one or more SAP Systems. The Business Blueprint documents in detail the scope of business scenarios, business processes, process steps, and the requirements of a mySAP.com solution implementation.
Structure A Business Blueprint compises the following structure elements in a hierarchy: • Organizational units • Master data • Business scenarios • Business processes • Process steps You assign content, for example, project documentation, Business Configuration Sets, or transactions to individual structure elements, in the SAP Solution Manager. You can also create structure elements for organizational units and master data, below a business scenario. You only use these structure elements if the organizational units and master data are only relevant to the business process above them in the structure.
4.CONCLUSION While the tendency is to view upgrades as a necessary evil in the enterprise software market, the reality is that upgrades can be an important part of a company's overall competitive profile. This happens ideally in the case of a functional upgrade, though it can also be the case with a technical upgrade that unleashes a capability, such as Unicode , that in turn helps open up new markets and opportunities. Helpful contents on SAP HR to assist those ing the SAP Human Resource Management Modules.
The SAP HR module enables companies to effectively manage information about the people in their organization. It is integrated with other SAP modules and external systems.
From the Organization Management perspective, companies can model a business hierarchy, the relationships of employees to various business units and the reporting structure among employees.
The Personnel istration (PA) sub module helps employers to track employee master data, work schedules, salary and benefits information.
The Personnel Development (PD) functionality focuses on employees' skills, qualifications and career plans.
Finally, the Time Evaluation and Payroll sub modules process attendance and absences, gross salary and tax calculations, and payments to employees and third party vendors. Hence, in my suggestions SAP HR is an important aspect for an organization.
5.ACKNOWLEDGEMENTS We would like to thank our ISM Lecturer, Mrs. SHUCHI SRIVASTAVA for her contributions,insights and . References http://en.wikipedia.org/wiki/SAP_SE http://scn.sap.com/community/uac/blog/2013/04/26/3-concepts-for-sapbeginners http://scn.sap.com/thread785683
Related Documents 171j1w
Sap 582k3
April 2022 0
Sap 582k3
June 2020 3
Sap 582k3
February 2023 0
Sap 582k3
August 2020 0
Sap 582k3
April 2020 47