Fit- gap anlysis, as- is stusy, to- be process

hi,
can any one explain fit- gap anlysis, as- is stusy, to- be process with a business scenario
u can mail any info regarding this to [email protected]
regards
amulya

Hi Shinas,
You may refer to SAP EAF tutorials for this and also you may find this link helpful:
http://www.archives.gov/records-mgmt/initiatives/bpd-checklist.pdf
Hope this helps!!
Cheers,
Arafat

Similar Messages

What is fit gap analysis?

Hi
What is meant by FIT GAP analysis ? any example ,documents?
What is cut short methodology ?
Pls full points will be rewarded.
Send details at :[email protected]
Message was edited by:
chandrakanth nammi

HI , refer below reward if helps, sent the mail
Fit gap analysis as the name says it is not a complete upgrade doc. to fit in the gap between the new and existing system from which we are going to migrate to the new system we run an compare and document in the changes that need to be preformed in then new system.

Fit Gap Analysis

Hi, can anyone give me some real time scenarios of gaps in SAP HR?

Hi,
Gaps in business processes can be identified based on available system functionality. It depends on each customer how they would like to handle the Gaps. Some like to change their process to fit the system functionality and avoid custom developments, some handle the gaps by developing a custom solution with in the system.
Here's a simple example:
If business requirement says - employee should be able to request Sick leave only in increments of 0.5 days at a time in ESS, R/3 settings will allow to record absences less than a day, but does not restrict with any messages to request in increments of 0.5 days.
So, business can choose to tell employees to record only in 0.5 day increment by avoiding the custom validation development in ESS, or create a custom validation in the ESS application, restricting the employee to record only in increments of 0.5 days.
Thanks,

Can you provide some real time example of Fit Gap analysis .

Hi all,
Can you provide some real time example of Fit Gap analysis related to Functional.
Regards
Reddy

hi,
In my opinion and experience both functional and technical staff playkey roles in the fit-gap meetings and in the subsequent review of thefit-gap deliverable (which lists business requirements, fits, gaps, andalternatives to fill the gaps). Ideally the technical staff possessessignificant functional / business experience at least with that moduleso that he/she can help determine the cost/effort/technical scope if acustomization or interface is the preferred way to fill a particulargap. The fit-gap goes a long way in determining the overall scope ofthe implementation or upgrade project and is a critical success factor.It also needs to be completed very early in the project so thatresulting customizations and interfaces can be designed, created, andunit tested before the system test phase.
Thx,
waseem

Help on assets (FI-AA) reporting fit/gap

Hello,
I've a few reporting requirements on which I would appreciate your help to assess if is there any r/3 standard report or BI business content that can fit (or can be enhanced to fit) and deliver the info needed.
The reporting requirements are the following:
1- Costs of Sale assets Report: A report showing the costs incurred in selling an asset vs the asset costs and the sale proceeds.
2- Assets transferred into stock Report: Periodic report showing asset details & values having moved them from Fixed Assets into an inventory/stock environment.
3- Intercompany asset sale/purchase: Report showing asset that have been sold/purchased from one company to another company.
4- Asset status report: Report to show where the asset is and its status (ie AuC, in stock, capitalised, not depreciating etc).
5- Asset tracking report: Need a report that can list assets and all the tracking attributes eg serial number, location etc
I will appreciate all the help that you can provide (sap r/3 transaction or BI content technical name).
Kind regards,
Nuno

Hi
3) The standard reports under Day-to-Day Activities cover this. Just set the parameters to limit it to Intercompany Transaction types.
Kind regards

GAP Anlysis

What is GAP Analysis in ASAP Methodology???? I would appreciate if some one can explain it with a real time scenario.....

Hi
ASAP methodology is the standard implementation methodolgy suggested by SAP for the faster implementation of SAP projects.
It has 5 stages into it
1. Project preparation
2. Business Blueprint
3.Realisation
4.Final preparation
5. GO live and Support.
For more info look at the following:
http://www.geocities.com/rmtiwari/Resources/Management/ASAP_Links.html
Assign points if useful
Regards
Aravind

Very urgent-gap analysis -two examples

please explain me with examples of gap analysis and how do you fill the gap
and also there are two movement types in schedule line cat , what is the purpose of two
early responders will be definitely rewarded
thanks & regards

GAP Analysis
A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print stage.
Cut Over Plans
Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.
Train Users
Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better. 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.
GAP Analysis
A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print stage
The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
Examples:
1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual property management and media advertising management functionality, respectively.
2. A leading Oral care product company wanted the promotion of free-goods where they wanted 'Buy one get 2 different products free'.
through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print stage.
Ex, The functionality that is not present in Standard SAP and adding it to suit the business requirements. In Credit memo request document type, creating Credit block automatically for those Credit memos above Rs 5000.
***reward if this helps**

Sample tamplates on Gap analysis and Resolution

Hi Gurus,
Can any one send me sample tamplates on Gap analysis and Resolution. My Email ID [email protected]
Thanks & Regards
Sasikanth.Ch

<b>mail sent reward if helps</b>
<b>GAP Analysis</b>
A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print stage.
Cut Over Plans
Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.
Train Users
Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better. 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.
GAP Analysis
A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print stage
The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
Examples:
1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual property management and media advertising management functionality, respectively.
2. A leading Oral care product company wanted the promotion of free-goods where they wanted 'Buy one get 2 different products free'.
2 gaps are,In customer master data the client requirement needs legacy customer number which can be solved with User exit.,
In sales order we need customer Phone number,We can use userexit
These 2 are gaps which we cant find in Standard SAP
1. if client want new field in customer master like nearest fire station ..
2. order will be uploaded directly with out va01. through BDC... bcoz lot of orders if they get daily, they can opt these...
Movement type 1 uses when a material have two movement types.. like example 101 and 261.. one is incomeing raw material and and going for production...
Message was edited by:
SHESAGIRI.G

Gap Analysis - Reg.

hi sap experts...
what is the fit gaps in sap, could you tell some fit gaps in sap please......
sai ram
Last warning: Respect the rules of the forum

Hi,
Gap analysis is the difference between AS-IS process and TO-BE process.
e.g. Cosultants should propose work arounds for this.
Rgds
Murali. N

* Information to All

hi all.
SAP Tickets - What Is That?
Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error.
The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the right solution in right time.This is the job of the support consultant.
The issues or the tickets(problems) which are arised is taken care of on priority basis by the support team consultants.
The work process in support projects are given below for your reference.
1. The customer or the end user logs a call through any tool or by mail (RADIX).
2. Each one of the support team is a part of support group.
3. Whenever a customer logs a call he /she has to mention to which work group (by name).
4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None)
5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR(Transport Request through the basis admin)
6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process.
These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client.
An example:
Tickets in SD can be considered as the problems which the end user or the employee in the company faces while working on R/3. Tickets usually occur during the implementation or after the implementation of the project. There can be numerous problems which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.
To begin with, we should give "TICKET" to you for not knowing it.
Here is an eg of a ticket raise:
End user is not able to
1. Create Sales order for a customer from a New plant, since shipping point determination is not happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING).
He raises a ticket and the priority is set in one of the below:
1. Low 2. Medium 3. High.
Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.
You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.
Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support.
What Is Maintaining SLA - Service Level Agreement
What is maintaining SLA in production support?
SLA is an abbreviation for "Service Level Agreement". It means to have guaranteed reaction or resolving times for incidents (= trouble tickets).
For instance you could have defined the following SLA levels For example:
Gold: Reaction time = 30 minutes, resolving time = 4 hours
Silver: Reaction time = 4 hours, resolving time = 24 hours
SLAs normally are part of a contract between a customer and a service provider.
Or in details description:
SLA are Service Level Agreements to resolve the tickets by the market. SLA means Service Level agreement. It is the service agreement between a Company and a service provider. For example an IT Organization providing support of SAP / other software / hardware has a agreement. This can be for example categorized based on criticality of the incident. High priority incident has to be resolved on 10 hours. Medium priority incident has a 3 days time to resolve etc
SLA's are nothing but Service level agreements.
These are defined in project preparation phase and client would have made an agreement with the company for the level of service. The SLA's are applicable in Production as well as maintanence support projects. For example: if your company follows a ticketing process(a ticket is nothing but an environment contains complete description of the problem which contains Short description, problem, customer contact details, sreen shots of the error etxc.,) and for each ticket there will be a severity for example business critical issues or problems may be treated as high or top severitie's. In those case your company or your team has to deliver the solution to the customer in agreed time limit or otherwise you might end up missing SLA's.
SLA's has two important time specifications
1. IPRT --- initial problem response time --- this is nothing but time taken to respond to the problem.
2. PRT --- Problem response time -
this is nothing but time taken to solve the issue or problem.
Both IPRT and PRT will be different for different severitie's.
What Are Functional Specification in SAP?
To speak at macro level that is at projet manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.
The Functional Specification describes the features of the desired functinality.. It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.
The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.
b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
Let me throw some light on documentation which is prepared before and in a project:
1) Templates
2) Heat Analysis -
3) Fit Gap or Gap Analysis
4) Business Process Design
5) Business Process Model
6) Business Change & Impact
7) Configuration Design, which is just 5 % of Total SAP- have different names -
8) Future Impact & Change Assessement
9) Functional Design (Module Wise)
10) Risk Assessement
11) Process Metrics and Many More-- Which has impact on Business and its work flow
Note * This documents are preapared in Vanilla SAP Standards -- Things differ from one implementation to another, and it always depends on the type of business which is opting for SAP
Role of a mySAP Functional Consultant
What are the differences between a functional and business consultant?
The difference between Functional consultant and Business consultant are as follows:
1) A funcitonal consultant is able to configure the system unlike business consultant.
2) Functional consultant know more about business process unlike Business consultant.
3) A business consultant will bring business process knowledge and provide it to functional consultant who in turn used this knowledge to configure the system.
4) Functional consultant has more configuration knolwledge then Business consultant.          *-- Rocky
The responsibilities of a support consultant are:
- Primarily responsible for Handling tickets and application support to the endusers
- When an issue comes diagnose, analyse and solve the issue
- Responsible for any enhancements
- Writing functional specs and interacting with Abapers to develop any user exits
- Training the end users and preparing end user training material                            *-- Sistla
For those who wished to know the role of a functional consultant. Below is one view:
A functional consultant evaluates the demands in talking with the customer's representatives, transforms the essence into an abstract and algorithmic business model. Hence, he identifies the use cases and transforms them into logical and technical views.
Then the main task starts: customizing the respective business area and making sure the system reacts in the manner according to the constraints of the requested use case.
The consultant documents the settings and prepares proper guidelines that allow other consultants to do further changes or repairs with due efforts.
The consultant takes care that proper training is given to the users and that the system is usable, performing appropriately and the business flow is complete and correct.
During go live he assists the technical staff by testing the behaviour of the system.
After go live he guarantees that the procedures remain usable and consistent in real live situation and proposes enhancements.
The main duty of a consultant is to transfer external know-how to the client. It is not manpower that counts but intelligence, understanding of processes, a feeling for defects and general a common sense
Role of SAP Consultant In Testing
1. What is the role of SD Consultant in Testing while implementing the project?
2. What is Unit testing and Integration Testing?
Testing : the core team members along with endusers will test whether the postings done in SAP is resulting as per the requirements of the organisation. They will test whether the output documents such as purchase order, invoice document are printed in the required format and showing the correct data.
Unit testing is refer to the module which are going to implement. SD, MM, FICO etc. there will be test script based on that testing will be performed.
Integration testing will be cross the modules. MM-SD-FICO for example. Integration testing is also called SIT ( System integration testing)
Testing mathologies and types: there are 6 types of testings:
1. Unit Testing
2. System Testing
3. System Integration security Testing
4. Performance Testing
5. User Acceptance testing
6. Regression Testing
Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice.
Whrereas System testing you will be testing the full cycle with it's integration, and you will be testing using test cases which give a full cyclic test from order to invoice.
Security testing you will be testing different roles and functionalities and will check and signoff.
Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second. Usually it is done using software.
Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. This will be done on each phase of testing.
User Acceptance Testing: Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases.
We use different software during testing. Most commonly use are
Test Director: which is used to record requirement, preparing test plan and then recording the progress. We will be incorporating defects that are coming during these testings using different test cases.
Mercury Load Runner: is used for performance testing. This is an automatic tool.
What does the following terms means :
- Technical Unit Testing
- Functional Unit Testing
- IntegrationTesting
- Volume Testing
- Parallel Testing?
Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program. A successful test only proves the developed code works and that it performed the process as as designed.
Functional Unit Testing= Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result.
IntegrationTesting= Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas.
Volume Testing= testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized.
Parallel Testing= Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared.
I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several.
What kind of testings that are carried out in testing server?
1. Individual Testing ( Individually which we've created)
2. Regressive Testing ( Entire Process)
3. Integration Testing ( Along with other integrated modules)
The 3 types of testing is as follows:-
1. Unit testing (where an individual process relevant to a SD or MM etc is tested)
2. Integration testing (where a process is tested that cuts across all areas of SAP).
3. Stress testing (where lots of transactions are run to see if the system can handle the data)
Roles and Responsibilities of End Users
What is the Difference between Consultant & End users?
SAP consultant role is to build the system, changes & modification/updation in currently installed SAP system for the end users.
SAP End user only use the SAP system just to fetch some info, or to create new thing. So a end user is just using the final product which it is meant for and consultnat design the product/updation and modification.
The roles and responsibilities of end users is working in easy access menu they will not have authorizations of using img settings if they get doubt they will send query to the implemented company and just entering day to day transactions.
Roles and Responsibilities of End User:
Using the software at the end or after the implementation is an End User.
In sap HR , we do come across entire Org Management creation by an end user after the Personnel strucutre is created. OM objects like creation of Org Unit means functional area or dpt , creation Job and Position and its occupancy is with in the limits of an enduser. Initiallly the OM is created by sap consultant . In course of time a new department has appeared in the company of the client .. this has to be created by the enduser rather than depending up on the implementor... similarly new job and position..like this small things are always done by the enduser.
The entire work of OM is purely depends upon the enduser.
After from this running periodical payroll and Ensuring of the Time schedules ( Work Schedules) of each employee is done from sap easy access by an enduser and the show run of payroll everymonth is by the enduser only. Like this lot of roles are there for an end user.
Whatever the problems come across during the enduser utilisation of sap ...that will reach as ticket to the support team
What Are SAP End User Manual
It is the same for every other modules although here I reference it mainly for SAP HR.
1) You should understand which targeted group for the end-user training is for. Do they have any computer background or not.
2) In what way they are going to make use of the manuals supplied to them during the course of training.
Let us focus on how to prepare manuals:
In the client side , End Users are not permanent. If they get any better job outside they will resign and go out. Even if you train them well, again the end-user team disappears after some time. That is why implementing company( Client ) expects SAP Consultants to prepare documents which are self explanatory (even to a layman in SAP) and study themselves and use the sap easy access very comfortably.
Hence we should prepare a document which explains the following things comfortably:
A) All the buttons and Screens we have in sap and its importance for an end-user.
B) All the transaction codes used by end user.
C) The STEP by STEP usage methodology with screen shots and explanatory foot notes for each Transaction code.
D) Prepare a book a table and columns which should have the following information:
- Sl.NO.
- Transaction Code
- Navigation path
- Use of the Code
- Expected Result
- Achieved Result
- Remarks/Any Comment
E) Highlight the common troubles during the usage of SAP by an end- user and give the solutions (ready to use)
These problems you can come across while giving the in house training for the end-users. You just place them at one place and publish it for their usage in future for any of their new joinees as an end-user.
F) Every consultant is aware that the entire Organsiational Management is with end user only. Means consultant should train the end user in entire OM.
G) We should inform the importance of info types and usage for our purposes at expert mode, PA30, PA40 etc.,
H) Each field in the international infotypes should be explained very clearly and ensure that they are comfortable with the fields of infotypes which have been configured for their company.
For example : info type 0001 Org Assignment insists about the three structures of the HR. We should explain each sub field like Emp Group, Emp Sub Group, Personnel Area and Sub Area and its importance and relevance to their company so as to understand while processing them from the end- user point of view .
When an employee is hired into the company , now the end-user in a position to understand which employee group and subgroup, Personnel Area And Sub Area etc., should allotted..
Like this whatever comes across in SAP Easy Access should be insisted through the training of end users.
I) Demo, exercises and solutions should be provided in the manuals.
J) Glossary of terms and expansion of Acronyms, Abbreviations should be given. Like this each consultant should focus on end user training and prepare the documents.
Mini SAP System Requirement and How to Get it
Mini SAP System Requirement
The system Requirements are :
General Requirements
Operating System:
Windows 2000 (Service Pack2 or higher);
Windows XP (Home or Professional);
Windows NT
Linux
Internet Explorer 5.01 or higher
At least 192 MB RAM (recommended to have 256 MB of RAM)
At least 512 MB paging file
At least 3.2 GB disk space (recommended to have 6 GB hard disk drive space)
(120 MB DB software, 2.9 GB SAP data, 100 MB SAP GUI + temporary free space for the installation)
The file C:\WINNT\system32\drivers\etc\services (Windows 2000) or
C:\Windows\system\32\drivers\etc\services (Windows XP) must not include an entry for port 3600.
A possible entry can be excluded by using the symbol '#'.
No SAPDB must be installed on your PC.
The hostname of the PC must not be longer than 13 characters.
The Network must be configured for installation and
the MS Loopback Adapter must be configured when you start the system without a network connection!
Special Requirements for Installations on Windows XP
In the file C:\Windows\system\32\drivers\etc\hosts the current IP address and the host name must be defined as
<IP address><Host name>
Open the network connectivity definition with start->control panel->network connections for defining the network connection. Select ->extended-> allow other users in network. Activate new configurations.
Select remote desktop within extended configuration menu.
Successfully Implementing SAP
Implementing a package can be a traumatic affair for both the customer and the vendor.   Get it wrong and the vendor may get paid late or have to resort to lawyers to get paid and tarnish their reputation.   For the company the new package may not work the way they expected, be late or cost a more than budgeted for and take management will take their eye off running their business.
Recently a client asked me what I would consider to be the five most important things one should consider before embarking on an implementation.   This isn't a simple question, although there are many factors to think about after some consideration for me the top five are way ahead of the others.
My top five factors to consider would be:
1. Set up a Project Board,
2. Secure the resources,
3. Complete the GAP Analysis,
4. Have detailed Cut Over Plans,
5. Train the users.
Taking each one in turn:
The Project Board
The correct set up and operation of the Project Board in my view is major factor in the success failure of the project.   The Project Board will consist of the stakeholders, key users and the vendor.   The Project Board is part of the governance of the project.   The Project Board will meet regularly to ensure that the project plans are created and being executed as planned, moves from stage to stage with all the deliverables being signed off is resourced properly.
The Resources
Three types of resources are absolutely necessary -- end users, change team and technicians.
Early involvement by the end users is absolutely necessary, as they will be the ones living with the system for hopefully many years to come.   They will want to feel involved in its implementation.   Buy in from the end users of the system is absolutely essential if the system is to have a long and stable life in any organisation.
The Change Team will identify the gaps between the package and the business requirements, re-engineer some of the businesses process to cope with the package, train the users to ensure implementations is smooth as possible into the business.
The Technical Team will prepare the systems environment for the package, apply any software fixes from the vendor, implement the software in the best way possible for the organisation set up and tune the software for the particular technical environment.
GAP Analysis
A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do.   For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print stage.
Cut Over Plans
Detailed plans need to be developed for cutting over from the old system(s) to the new.   Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.
Train Users
Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced.   Therefore the more effort you put into helping the users master the system early the better.
Explain Cutover Activities/Strategies in SAP FI.
Cutover Activities or Master Data Uploading Strategies Depending upon the when we are going live. As per that, you have to give the information to your core team. If you goling live at the middle you have to upload the all P&L Account items and B/S Items. If you going live at the financial year start, you have to only Upload the B/S Items. Activities for Golive:
1.   G/L Master Upload Thru BDC or LSMW (TC-Fs00 and extended one co code to another company code Fs01)
2.   Vendor Master Upload Thru BDC Or LSMW (Will be Taken Care By MM)
3.   Customer Master Upload Thru BDC or LSMW (Will be Taken Care By SD)
4.   Asset Master Upload(Thru As90)
5.   Cost Element Master Upload
6.   Cost Center Master Upload
7.   Profit Center Master Upload
8.   G/L Balances Thru F-02
10. Vendor Balances thru F-43
11. Customer Balances thru F-22
12. Customer Advances thru f-29
13. Vendor Advances thryu F-48
Before uploading Vendor Balances you have to take care of WHT(TDS) Information.
Difference between the User Exit & Gap analysis.
Both are quiet a different and has a small relation.
User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench.   its not new functionality which we are trying to build in sap but its slight enhancement within the same code.
Gap analysis is start point of Realization and once blue print is finished we have to find the realization of sap system for client requirment and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system.   *-- V. Sridhar
What is roll out of SAP Project?
As per dictionary, Rollout means Inauguration or initial exhibition of a new product.
As per SAP specific definition, rollout is the strategy for international SAP implementation. Rollout strategy normally include the following
- Whether to implement SAP simultaneously (also known as big-bang) in all the countries, or
- Go live in sequence of phased manner
- Or to go for the combination of both (phased manner implementation for some of the countries and big-bang for others).
Rollout strategy is the most important decision that a client can make during SAP implementation. Normally, steering committee decides the rollout strategy.
ALL THE BEST

Man, thanks a lot! I appreciate this.
You think you could do me a favor? I listen to a lot of DCI songs (for those of you who don't know what that is, don't worry about it), anyways, DCI shows are average 0-2 mins. Could you give me the formula that you use for this so I can calculate it's

Document for "AS IS"

Hi collegues. Can somebody give an example of "as is" report about the state of the enterprise, which is performed before the Blueprint creation.

Hi Dmitriy Usov
AS IS document is prepared by collecting the information from the Business Users / End users of client side from the Respective process owners like ( OM,PA,PD,Payroll etc) Departments.
This report gives the base inputs on the current business process followed by the clients and from this document you can go into fit gap anaylsis between the "AS IS" process and SAP HR product functionality and come out with the final Design for the process (i.e Blueprint).
"AS IS " templates will differ for each client engagement based on the assignment they are carrying out.
Thanks
Gautham.

Technical Requirements for SD in ECC 6.0

Hi All,
I need to document the technical requirements in ECC 6.0 implementation for SD Module.Kindly revert back with helpful answers.
Thanks,
Faisal

As per my understanding you require information on what Technical document might be required to be prepared by SD Consultant. If my understanding is correct, in that case we require to prepare Functional Specs for the enhncement & development required in the project.
Functional Specs:
To speak at macro level that is at project manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhere organizations combine these two documents into a single document.
The Functional Specification describes the features of the desired functionality. It describes the product's features as seen by the stake holders, and contains the technical information and the data needed for the design and development.
The Functional Specification defines what the functionality will be of a particular area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step that is technical development process.
b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
At the consultant level the functional specs are prepared by functional consultants on any functionality for the purpose of getting the same functionality designed by the technical people as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
Let me throw some light on documentation which is prepared before and in a project:
1) Templates
2) Heat Analysis -
3) Fit Gap or Gap Analysis
4) Business Process Design
5) Business Process Model
6) Business Change & Impact
7) Configuration Design, which is just 5 % of Total SAP- have different names -
8) Future Impact & Change Assessment
9) Functional Design (Module Wise)
10) Risk Assessment
11) Process Metrics and Many More-- Which has impact on Business and its work flow
Regards,
Rajesh Banka

Roll out requirements of SAP in European countries

Dear All,
We are in the process of rolling out SAP to our client's European business units based on our US based global template. Is there any documented procedural steps one must follow so that we do not miss any of the statutory/Legal requirements and some country specific functionality (config, reports etc) ?
We are presently looking for the countries Po, Hu, Be, Ru, Sp, It & UK. We are currently looking at country specific best practices baseline packages in Sap services Marketplace but if anyone can provide an exhaustive list of activities based on their past implementations, it'll be very much helpful.
Warm regards,
Kingsuk Mukherjee

a common requirement in all countries of the European union is Intrastat trade reporting.
And even it is common in EU countries, it can slightly vary from country to country, and Italy the most complicated in this regard.
For Russia you should implement the country version
for Belgium there is special OSS note "how to setup Belgium company code"
(and an umbrella is needed in Belgium, not a legal requirement, but a personal. I never had a worse whether anywhere else than the year I worked in Belgium)
You should do you fit/gap analysis on site to see whats missing.
It is always surprising especially if you have 2 companies in one country, they have different "legal" requirments. Just had it today. we are merging SAP systems, and both systems have a company in Italy.

Structure of Sales Organization?

Structure of Sales Organization?
What is Tolerance Group?
What is the format of Business Blue Print?
When do we require the functional Specifications?

Hi Farhan,
The Structure of Sales Org, differs from client to client. Its purely client specific.
But normally the structure containes, Sales Org, Distribution Channel, Division, Sales Group and Sales Office.
Tolerance groups:
Tolerance groups represent amounts or percentages by which receivables may be underpaid or overpaid.
Amounts and percentage values for tolerances relating to underpayments and overpayments of receivables are defined in a tolerance group.
Business Blue Print;
Business Blue print is understanding the clinets business completley. While we are implementing SAP to any client, first we have to understand their business completely so that we can map accordingly in SAP system. So, after understanding their business, we will prepare a document called as Busines Blue print. While is nothing but AS Is study.
Functional Specification:
To speak at macro level that is at projet manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.
The Functional Specification describes the features of the desired functinality.. It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.
The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.
b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
Let me throw some light on documentation which is prepared before and in a project:
1) Templates
2) Heat Analysis -
3) Fit Gap or Gap Analysis
4) Business Process Design
5) Business Process Model
6) Business Change & Impact
7) Configuration Design, which is just 5 % of Total SAP- have different names -
8) Future Impact & Change Assessement
9) Functional Design (Module Wise)
10) Risk Assessement
11) Process Metrics and Many More-- Which has impact on Business and its work flow
Hope this is helpful.
REWARD IF HELPFUL.
Regards,
Praveen

Crystal 2011 prompts on adhoc reports dont show up in BOBJ 4.0

Hi All,
I have two issues with crystal report 2011 via BI launch pad BOBJ 4.0
1. We created crystal reports 2011 on Bex query with some filters and promots and schedule the reports but when we try to open the report and referesh through BI launch pad in BOBJ 4.0 , it does not show any prompts associates with it. Note that report is published and scheduled.
But when I save the same report on my local network drive and open it, all the associated promots shows up.
I am sure it is not crystal report interface issue or BOBJ application it self or may be some kind of authorization but considering the fact that we can see the propmpts when report is saved locally on te network drive..
2. We have created a project and addedd multiple reports in Crystal reports 2011 and then published and scheduled it. We schedule the reports to go to users via email in excel format but it sends only one report (one attachment) per email, I like to send multiple attachments in one email. How could I achieve this.
Your help and advice will be appreciated.
Regards
MD

Hi,
1. i'd recommend having a seperate BW for BI4 purposes. If anything, it makes management of integration TRANSPORTs much easier, given that you can only have 1 version active..
(yes, although there's no SAP IK Kit, transports are still imported into backend)
2. OLAP BAPI access is still there in BI4.0, namely for the CR 2011 tool with BW MDX Driver , and for Webi documents using the legacy Universe Design Tool OLAP.unv file.
the new OLAP data access driver for SAP in BI4.0 is the BW's BI Consumer Service (BICS API). The function modules for this are generally called: BICS_PROV_GET*
3. No hurdle at all. You can migrate your content as-is without fear of change. that's principally why the CR 2011 client is there for the 4.0 RTC - for adoption and onboarding. That legacy CR client technology is wholy unchanged, apart from .xlsx support and a 'read only' save mode.
the Crystal for Enterprise product is still playing catch up. It hasn't got all (any) of the direct drivers you would expect from crystal, but it can consume the new .unx common semantic layer and the BICS jco driver (neither of which the CR2011 product can)
... as of 4.1 (Q1 2012) the fit-gap in features is answered. i.e. they've all been fwd ported.
i hope this helps
Regards,
H

Fit- gap anlysis, as- is stusy, to- be process

Similar Messages

Maybe you are looking for