RICEFW means Reports, Interface, Conversion, Enhancements, Forms and Workflow. It is applicable to all modules.

Development of these items will be dealt separately in large projects. A separate team will work on the development of programs, scripts etc. Reports - Development of customized reports in ABAP, Report Painter or BW Interface - Some business processes may be maintained in external systems. For example Payroll, Fixed Assets, Dispute management etc. These external activities may need postings in SAP. Interface programs are developed to automate the postings in SAP. Conversion - Conversion of Legacy data to loadable format into SAP. The process consists Extraction of legacy data from legacy systems, Transformation of data into loadable LSMW format and Loading the data into SAP. This activity is important and need accuracy. Hence, a separate team may be assigned for conversion alone. Enhancements - Generally in the case of large implementations a Global template Blue-print will be prepared and followed. If a plant or company code need additional configuration to meet their country specific or plant specific requirements, the template will be enhanced with new configurations. Forms - Development of layouts for Invoices, Account statements, Delivery notes etc Workflow - Development of approval flow logic in SAP. For example GL master data changes should follow specific approval process.

What is RICEFW ?
Mon, 09/06/2010 - 04:09 mac when you hear the term RICEF - you should think: customization / changes to std SAP. RICEFWs are used only when std SAP cannot do the work. Reports: SAP has tonz of standard reports (VA05, VA14L) that show you a lot of info. But when you need info that's NOT on a Std SAP report, you want to then create your own report. You talk to a developer / ABAP-er, and you give him the Table-Field specs for each column that you want to see on the report. You also tell him what your input selection criteria, are. Also give more details like - should this report auto-execute, should it be auto-emailed, should the output be a flat file or ALV format, etc. You will also suggest the Tcode for this new report. classic example: cut report. Interfaces: Assume SAP is being used in conjunction with some other non-SAP system, for ex: Manugistics. This means that these 2 systems have to talk. In real-time and without human intereference. that in turn, means that certain data and status values from SAP need to be accurately mapped to MANU, and vice-versa, and again, in real-time. To accomplish this, complex interface programs will be developed by the ABAP-ers, based on the specs given to them by the functional teams. These specs must be extra-specific. For example, "In MANU, when a freight movement is goods issued, do 3 things in SAP - change the status of the corresponding delivery to completed, show the carrier pick up time from MANU in SAP, and also, show the exact time of goods issue on the delivery, in a custom field". These interface programs bring data back and forth, and keep the business going. Conversions: When you are about to go live with SAP for the first time, all your data, history, records and functionality are in some other, legacy system. The functionality is imitated in SAP through configuration and/or customizations. However, you must still bring ALL the data, in the correct format, to SAP, right? If you have 10,000 customers, and 18,000 open sales orders and 1894 materials - are you going to do this by hand? No, you will use a conversion program. These are again custom programs. The developers will write 1 program (again, based on ur specs) each for customers, materials, sales orders, and so on. You will test these in Q and during Mock cutover. Each of these programs will ensure that their source record - in the legacy system - is mapped completely and exactly onto a corresponding target record in SAP. the customers conversion program, for example, will first read all the fields for a customer in the legacy system, then, in SAP, open XD01, and map each of those fields to its corresponding counterpart in SAP.

Enhancements: When you want SAP to do something that it doesnt do in std SAP, its a customization. But when you modify the way SAP does in std SAP, then thats an enhancement. For example, in Std SAP, when you save a sales order, SAP already populates the shipping type (from the ship to customer master), and the order's total weight. But when you want SAP to change the shipping type based on the order weight and not simply populate the shipping type from the ship to customer master, thats an enhancement. Because the values you are using are already in SAP - you are just using them differently. Forms: This is SAP Smartforms. Std SAP gives you readymade forms for Pick List and BOL. But lets say you want more fields displayed on these. You would then talk to a developer - they would show you your options. You will draw them a picture on a sheet of paper - saying that - in this section on the pick list, i want the ship to address displayed and here on the BOL, I want the bill to address displayed. The developer will then make these and show you, and you can then adjust things like the location of the box, the field length and the font size. the developers will use SmartForms to do all this.

Workflow: SAP uses a std mechanism, workflow, to inform people, when certain trigger things happen in SAP. for example: whenever an order with a delivery block is created, a particular CSR, who handles delivery blocks, gets an email in their SAP inbox. This is NOT their regular email inbox. This is in their SAP inbox, Tcode: SBWP. Once they see the message there, they can double click on it and it will take them to that sales order in change / VA02 mode. Once the CSR does whatever is required to release the delivery block, saves the order and clicks the back button they will be taken back to the SBWP screen - when they hit refresh, that entry will dissapear from the list. But keep in mind that none of this is std SAP - a workflow consultant has to come in, and define: which users will get emails when what actions occur in SAP.

Business Blueprint

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 administration.
Features Scope of the Business Blueprint Transaction

Function

Tab

Create a project structure Display the following documentation:

Structure

Documentation delivered by SAP, e.g. scenario descriptions Documents 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, Upload user documents Input administration data, e.g. project status, team members assigned, planned and actual resources Assign transactions and programs to structure elements Create, Display and Edit issues und messages Display and Create a process graphic Where-used list:

General Documentation in template projects Project Documentation in all project types

Administration Transactions Issues/Messages Graphics

Use in user project Use in other projects Go to use by double-click

General Functions

General Documentation Project Documentation Transactions

Function Change the sequence, hide or show tabs Translate project structure For further information about translating document names for URLs, in your project, see Translating a Template Create/print a Business Blueprint document Assign document authorization
Activities

Navigation Settings User-Specific

Goto

Translation

Business Blueprint Create Blueprint Document Assign authorizations in the Role (PFCG) and User Maintenance.

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 in Projects

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 an SAP 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.
Integration The Business Blueprint is the prerequisite in the Solution Manager for configuration and test organization:

Configuration:

You configure your business processes with reference to the Business Blueprint project structure. You can also display and edit the project documentation from the Business Blueprint phase. Test Organization:

You base all test plans that you create during test organization, on the Business Blueprint project structure. The transactions which you assign in Business Blueprint process steps, are put in test plans when you generate them. You can run these transactions as function tests, to test the transactions.

ASAP Roadmap
Use
The ASAP Roadmap provides the methodology for implementing and continuously optimizing your SAP System. It divides the implementation process into five phases and offers detailed Project Plans to assist you (in Microsoft Project format). The documentation stored at each level of the Roadmap tree structure contains recommendations on implementing your SAP System and links to helpful tools and accelerators.

Purpose
When you install the Implementation Assistant you can choose from several Roadmap types and flavors. Roadmap types Implementation Roadmap flavors R/3 System (Continuous Improvement) BW

APO Business-to-Business Procurement Global ASAP Upgrade R/3 System R/3 System

In your implementation project (Roadmap type: Implementation), you can bring together several Roadmap flavors in one Roadmap. The Implementation Assistant also helps you to implement a combination of software implementation projects.

Features
The implementation of your SAP System covers the following phases: 1. Project Preparation In this phase you plan your project and lay the foundations for successful implementation. It is at this stage that you make the strategic decisions crucial to your project: o o o o Define your project goals and objectives Clarify the scope of your implementation Define your project schedule, budget plan, and implementation sequence Establish the project organization and relevant committees and assign resources

2. Business Blueprint
In this phase you create a blueprint using the Question & Answer database (Q&Adb), which documents your enterprises requirements and establishes how your business processes and organizational structure are to be represented in the SAP System. You also refine the original project goals and objectives and revise the overall project schedule in this phase. 3. Realization In this phase, you configure the requirements contained in the Business Blueprint. Baseline configuration (major scope) is followed by final configuration (remaining scope), which can consist of up to four cycles. Other key focal areas of this phase are conducting integration tests and drawing up end user documentation. 4. Final Preparation In this phase you complete your preparations, including testing, end user training, system management, and cutover activities. You also need to resolve all open issues in this phase. At this stage you need to ensure that all the prerequisites for your system to go live have been fulfilled. 5. Go Live & Support In this phase you move from a pre-production environment to the live system. The most important elements include setting up production support, monitoring system transactions, and optimizing overall system performance.

After your system has gone live, you can use a separate Roadmap with six work packages, in order to optimize your SAP System continuously. These phases are the main milestones for your SAP System implementation project. Each phase has:

Work packages, which consist of activities, for which project teams are responsible. Activities, which consist of tasks, which are processed by one or more team members. Tasks, which are carried out by a project team member. You can also access the How-to sections and accelerators at this level.

An IISO 9001 Company

ENTERPRISE RESOURCE PLANNING

The competitive environment in the Internet Economy brings renewed focus on the need to implement an Enterprise Resource Planning (ERP) solution. The increasing use of the web as the enabler of B2B and B2C E-Commerce places greater stress on the strength of the fulfillment systems. Opus enables the Adoptive Enterprise with highly customized functionality for ERP and integration with the Supply Chain, HRMS, E-Procurement, ECommerce and CRM applications. Opus provides the comprehensive approach and services for implementing ERP solutions using latest product suites from leading ebusiness solution providers like SAP. Business Challenge In the present day environment with the continuous changes in customer preferences the organizations are expected to respond promptly to the changed needs for survival and sustained growth. To address these situations it is essential for all the enterprises to improve their operational efficiency and optimize the use of their resources with the support of an online and efficient information system. SAP as an Enterprise Solution exactly addresses these requirements. Opus. Role Opus participates as an implementation partner, working in the Team SAP mode and employing SAP's patented ASAP methodology. The key role is in the design of functional specifications, and development of RICE (Reports, Interfaces, Customizations, and Extensions) components apart from the transfer of knowledge to the core team and the end users of the client. Our services Opus. main strength lies in SAP implementation. Opus has also a

strategic alliance with Siemens Information Systems Limited, India for implementing SAP. Opus was involved in a number of successful SAP project implementations for organizations such as Beckman Inc., Kraft Foods Inc., Berkley Networks., Molex Inc., etc, all based in the United States. The list of domestic projects is equally impressive and includes organizations such as ONGC, Gujarat Narmada Valley Fertilizer Corporation, Mohan Breweries and Distilleries Limited, the first Liquor Company in India to go in for SAP, Eicher, Nagarjuna Fertilizers & Chemicals Ltd., Dr. Reddy.s Laboratories Ltd. etc. Some of these implementations were carried out in association with our business partners Siemens Information Systems Limited, India.

An ISO 9001 Company

w w w .. o p u ss a ss ii a .. c om

--

--

SAP Services
Adoptive Enterprise consists of end-to-end solutions in ERP including strategic planning, visioning, and implementation and post implementation services. We offer following services . Pre Implementation Services: Business Process Study Planning towards an ERP Implementation Gap & Fitment Analysis Migration Study Supply Chain Opportunity assessment Project Scoping & Sizing Implementation Services: Turnkey Implementation Project Management Functional Consulting ABAP/4 Programming BASIS Support Enhancement/Development of add on Applications Data/Customization Migration Version Upgrades Post Implementation Services: Trouble-Shooting Fine Tuning of Configuration & Programs Ongoing user Education & Corporate Training Enhancements & Rollout Migration to new releases Maintenance 24 X 7 support Opus has a wide range of competencies - from consulting to SAP implementation to system integration. Careful nurturing of these competencies has lead to the building up of a comprehensive knowledge repository containing technical and business data. Along with our associates, we are able to dip into this large well of knowledge to be able to

deliver high quality, high value solutions. Multi-skilled Teams In our SAP division, we aim to reach this goal by having teams with multi-skill compositions that complement each other. Again the teams bring to the table sets of technical skills that complement each other completely. We are thus able to draw upon our internal skills to provide value to the customer.

An ISO 9001 Company

w w w .. o p u ss a ss ii a .. c om

--

--

SAP Services
SAP STAFFING SERVICES Opus provides high caliber SAP consulting services. Our staff has been focusing on SAP implementation and allied services for over 6 years. Outstanding Consultants SAP professionals with minimum ONE SAP R/3 implementation experience Related industry experience Modular integration expertise with knowledge of more than one application module Both technical and functional expertise. We staff all SAP requirements, and we meet the need for specialized skills in SAP Reporting and SAP Information Systems, Interfacing SAP and external systems and SAP /Internet Interfacing Focusing on Results We assemble small teams of consultants who are highly skilled Small teams support and train internal staff throughout the analysis of needs and implementation of solutions Decisions are made quickly and solutions are streamlined, making the system less complex. The Best of Both Worlds Opus maintains a healthy mix of permanent employees and a database of pre-qualified independent consultants. This allows us to offer the advantages of project based consulting and the flexibility of contract staffing. Advantages include: Stable, reliable core of highly qualified consultants Strong management support that invests in our consultants through training and support Ability to respond quickly and with the precise skill set needed Ability to draw on a large pool of talent

An ISO 9001 Company

w w w .. o p u ss a ss ii a .. c om

--

--

SAP Services
APPROACH AND IMPLEMENTATION METHODOLOGY Project Approach Framework Any ERP implementation requires unambiguous and comprehensive analysis of the existing system. Furthermore, the magnitude and complexities associated, requires a

well-defined systems approach to take into account various issues related to business, technology, operations, bottlenecks and constraints. Keeping in view the above technical and socio-technical issues, Opus has formulated a 3-tier approach to execute the proposed assignment. Initial discussions will be held with the Senior Management to understand the Vision of the company, Long Term goals, Corporate/Functional Objectives and the MIS requirements. If this is readily available, it will be adopted by incorporating changes, if any. Intensive workshops will be conducted with the Functional Heads to understand the Short Term and Long Term Planning Procedures, Supply Chain Logistics and the Reporting Requirements, and lastly Interaction will be carried out with the Functional Users or Core Team to study, finalize and assign the roles and responsibilities, day-today transactions and functional efficiencies. During these interactions a special effort will be made to bring out the relevant Change Management Issues related to SAP implementation. To critically look at the Change Management issues and for addressing the business readiness it is essential to clearly understand the Business Processes Hence it is necessary to focus on business process mapping, identifying bottlenecks and streamlining process relevant to ensuring successful technology fitment and absorption. The Business Process modeling will be carried out to study and analyze all the Business Processes in three levels. PROJECT APPROACH FRAMEWORK DIAGRAM
Project Approach Levels Diagram

Strategic Decision Processes & EIS Marketing Manufacturing Materials Personnel & HRD Enabling Processes and MIS Supply Chain Management Processes

An ISO 9001 Company

w w w .. o p u ss a ss ii a .. c om

--

--

SAP Services
Implementation Methodology The Methodology for SAP implementation encompasses a sound theoretical foundation, which lays emphasis on the alignment of Information Systems with the organizational objectives and priorities. Opus appreciates that to carry out an SAP implementation effectively and speedily it is essential to have a detailed understanding of the existing Business Processes, Systems and Procedures. Examining critically the effectiveness of the existing system by in depth

analysis, the root causes of various inherent bottlenecks and drawback of the present organizational structure, system and procedures, roles, responsibilities and accountabilities of individual groups, etc. if any for reengineering and mapping into SAP. Opus follows ASAP Methodology, an SAP. patented implementation methodology for a quick and quality implementation. However, to reduce any duplication of effort Opus will critically consider the preparedness of THE CLIENT in all areas and suitably modify ASAP project management for meeting target date for Go-live. Opus will critically evaluate all possible parallel activities to deploy resources from THE CLIENT and Opus to complete implementation as per the agreed schedules. ASAP implementation methodology is broadly classified into five major phases. This includes Project Preparation, Business Blueprint, Realization, Final Preparation and Golive & Support. This methodology follows a Roadmap, which portrays project structure and provides a detailed description of work packages, activities and tasks for each phase of the implementation project.
Compre hensive Analysis of Existing Systems Gathe ring Information abo ut Corporat e Vision, Long Term Goals & MIS requirements

Approach at the TOP Level Approach at the Level of Functional Heads Conducting Workshops to understand:
Short Te rm & Long Term Planning Processes Supply Chain Logistics MIS Requirements

Approach at the Level of Functional or Core Team Users Study and Finalize the:
Assignment of Roles & Responsibilities Day to Day Transactions Functional Efficiencies

An ISO 9001 Company

w w w .. o p u ss a ss ii a .. c om

--

--

SAP Services

Following is a detailed description and deliverables associated with each phase:

I. Project Preparation
The purpose of this phase is to provide initial planning and preparation for the Project. Although each project has its own unique objectives, scope and priorities, the steps in the phase one, help identify and plan the primary focus areas to be considered. As we prepare for implementation, there are important issues we must address at the beginning of the project, including: 1. Defining project goals and objectives, 2. Clarifying the scope of implementation, 3. Defining implementation strategy, 4. Defining the overall project schedule and implementation sequence, 5. Establishing the project organization and committees, and 6. Assigning resources. Deliverables 1. Initial Project Plan, 2. Project Procedures, 3. Technical requirements, and 4. Project Kickoff.

An ISO 9001 Company

w w w .. o p u ss a ss ii a .. c om

--

--

SAP Services
II. Business Blueprint and Process simplification
The purpose of this phase is to create the Business Blue print, which is a detailed documentation of the simplified business process, which will cover all the processes documented in the AS IS phase. Opus will mainly refer the standard Process of SAP. With this basic platform, we achieve a common understanding of how the company intends to run its business using the system. During this phase technical team releases the technical blue print for the hardware. Deliverables 1. Refine the original project goals and objectives, 2. Define the baseline scope, 3. Refine the overall project schedule, 4. Develop System Environment and technical blue print, 5. Business Organization Structure, and 6. Business Process Document.

III. Realization
The purpose of this phase is to implement business and process requirements based on the Business Blueprint. The objectives are final implementation in the system, an overall test, and the release of the system for productive (live) operation. The system is configured in two work packages, namely Baseline (major scope), and Final (remaining scope). Multiple module tests and the integration tests are carried out during this phase. Deliverables 1. System Management,

2. 3. 4. 5. 6.

Final Configuration and Confirmation of the system, Creation of layout sets, Establish Authorization Concept and Profiles, Final Integration Test report, and End user documentation and Training Material.

IV. Final Preparation

The purpose of this phase is to complete the final preparation, including testing, user training, system management and cut over activities, to finalize the readiness to go live. This final preparation phase also serves to resolve all crucial open issues. Data collection and Data loading activity is done during this phase. Users are also trained during this phase. On successful completion of this phase, one is ready to run the business on the productive system. Deliverables 1. User Training, 2. System Management, 3. Detailed Project Planning for going live, 4. Cut Over plan, and 5. Data loading.

An ISO 9001 Company

w w w .. o p u ss a ss ii a .. c om

--

--

SAP Services
V. Go live and support
The purpose of this phase is to move from a pre-production environment to a live productive operation. After loading the closing balances in the system it is handed over to users for productive use. We must set up a support organization for users, not just for the initial critical days of your productive operations but also to provide long term support. During this phase, users have many questions. There must be a solid user support organization easily accessible to all users. This phase is also used to monitor system transactions and to optimize overall system performance. Deliverables 1. Production Support Procedures, and 2. Project Conclusion As part of methodology Opus likes to ensure the following Change management procedures and training followed. This needs to be done with active user participation from the client ERP is not an IT tool but it is a business solution. It cuts across all business functions. Hence it brings a change for every one performing the processes covered by ERP. If the change is not communicated to the users properly it may develop a resistance, which can be detrimental to the project.

CHANGE MANAGEMENT DURING SAP IMPLEMENTATION:

Change Management is one of the most critical success factors in SAP implementation This phase shall begin along with the commencement of the implementation project.

This involves Change Management workshops to be conducted at various stages of the SAP implementation. The stages are as given below: 1. Early hiccups stage . Whenever the ERP package is finalized, 2. As is study phase, 3. Business blueprint stage, and 4. Final preparation stage. Change management workshops for Operating level: Participants . Clerical staff, supervisors, accounting officers, MRP controllers, other officers, etc. The workshops and training classes will address the following . 1. Need for change, 2. SAP overview, 3. Advantages of process simplification, 4. SAP advantages to the organization, 5. Training in Microsoft Office, and 6. New processes in SAP and the advantages.

An ISO 9001 Company

w w w .. o p u ss a ss ii a .. c om

--

10

--

SAP Services
Change management workshops for middle managers The workshops for the Middle management will address . 1. Need of change in the current market scenario, 2. SAP overview, 3. Advantages of the integration, 4. Changes that SAP will bring in the job role and the organization structure, 5. Pace of the change in the market, 6. Advantages to the organization, 7. Role of the middle management in the SAP implementation, and 8. Use of on line data for the decision-making.
Change management workshops for Top management

The workshops for the top management will address . 1. Advantages of the integration to the organization 2. SAP overview, 3. Changes that SAP will bring in the job roll and the organization structure, 4. Security of data and transactions offered by SAP, 5. Use of online database for decision-making. Opus. Advantage Opus offers complete assurance on each of the following critical success factors in a SAP implementation Total knowledge to the Clients Ramp-up capability in SAP related resources Reliable methodology for capture of the system landscape Strong execution capability Minimum downtime Ready combination of tools and methodologies.

Interview Question and Answers on SAP SD

1.What are the responsibilities of a functional consultant in an implementation project? a) Responsibilities in implemention project - Preparing the functional specification documents. - Review and approval of functional specifications. - Designing a road map and setting approval from client. - Changing existing configuration whenever needed. - Setting up configuration for new enhancements. - Handling basic issues of MM module. b)Responsibilities in support project - Handling customization, configuration, and enhancement related issues - Handling tickets on Day to Day basis - Monitoring S&D reports on daily basis required by clients - Preparing functional specification documents - Preparing end user training Documents 2.What are the responsibilities of a technical consultant in an implementation project?

Preparation of techinical specifications, getting apporvals from functional consultant and PM,assitance to functioal consultant. 3.What are the main and sub modules in SAP? MM,FICO,PP,ABAP 4.What is ERP and SAP?and why inplementing SAP in an organization? Explain the special features of SAP over other ERPs? SAP is an ERP package. SAP can be fit it any language. It is used to get exact data with a fraction of section which will be use fully for management to take correct decision in a short span of time. Using of sap means there is no need to maintain the middle management in the organization because the CEO of the company is able to direct the executives direcltly with the system. SAP is able to integrate all functional organizational units togethere and retrieve exact data needed by management. Therefore, investing on middle management will become less. and the user will be able to acess instance reports using the logistic informaion systems in SAP. 5.Explain the business flow of an implementation project? - Project prepration - Business blue prints - Fit gap analysis - Realization - Golive - Support 6.Explain breifly about your role in current/previous project? (If you have one) Team member 7.Explain your functional experience prior to SAP? For this yo will give explanation depends of your previous experience. 8.Can you explain the modern technologies in SAP? Do you use this in your current project? I think the ans is APO, BW, CRM, if its wrong pls guide me any body. 9.Explain the terms "AS IS" and "FIT GAP ANALYSIS"? Business blue print stage is called as is process. Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There

should be a gap. So by filling this gap, we make configuration with the help of these documents. This is called as fit gap analysis. In this stage, we should analysis the gap between as is and is as process 10.What are the responsibilities of "CORE TEAM" and "FUNCTIONAL TEAM" in an implementation? Core Team are the power users who are selected for the SAP implementation. The Functional Team gather the initial implementation requirement from these core team users who will be the bridge between the SAP Functional Team and their department users with the expert work knowledge.