AS-IS study and TO-Be requirements

[Former Member]

Hi All,

Can any one explain the following items used in implementation project using ASAP Methodology.

1. AS-IS Study.

2. To- Be Requirements.

Thanks in advance,

Regards,

Vamsi.

[Former Member · Accepted solution]

Dear Vamsi,

AS IS:

This work is of a functional consultant.It involves understanding the complete functionality of the system.

It involves detailed understanding of how the HR department is functioning because based on that only you would provide a solution to them. Like suppose you are implementing SAP HR module for them then in the AS-IS and TO-BE phase, you need to prepare all the documents of the process flow (you can prepare them in word). Like suppose you are implementing for PA then you need to identify how many personnel areas you need to make, how many subareas you will make, employee groups, subgroups, based on what you are classifying them? This all will come in the master data document which has to be approved from the client whoever he is .

Like if the current system is on mainframe or for some specific applications like for recruitment the system is on mainframes and the client wants to keep that system as well then interfaces need to be identified which will be there because you will have to upload the data to sap system using bdc.

Like this for every process there will be a document.Even for actions like:

- Hiring

- Newly Hire

- Termination

- Transfer

- Layoff etc

You will have to see what all actions your client wants, like if there is an action transfer which is run for employee what all will be the reasons you will be configuring for that action. This will be told by the client which can come out after a series of meetings and after discussions you will have to come out with the document that these will be action types. These will be the action reasons, these will be the action codes for that. This will be in the TO BE process document.

After this phase is over complete configuration can be done.

Actually AS-IS process in summary involves a :

1) Series of meeting with the client.

2) Gathering complete information about the existing system.

3) Preparation of the blue print documents describing the complete AS-IS process ,i mean the existing system.

4) Flow charts should be included in the as-is blue print process flow document describing the complete process.

5) After this is finished u have to give the TO-BE process structure that will be implemented in SAP.

6) After that there will be some things which cannot be implemented in SAP so the gaps are to be identfied.

7) These gaps are to be documented in white paper for the client.

It is a lenghty process but not so difficult only the thing is that the functionality is to be understood properly.

TO BE involves how the existing process are mapped with Standard SAP.

This will lead to GAP Analysis.

A small search on SDN SD forum will help you to answer your query.

I will suggest you to visit http://sap-img.com/sap-sd.htm. It will give you the overview of SAP SD module.

Moreover there is a separate section of FAQs with answers which will help you in great deal.

Hope this helps you.

Do award points if you found them useful.

Regards,

Rakesh

[Former Member]

Thanks a lot

[Former Member]

My pleasure

[Former Member]

Hi Vamsi some more info on your question,

As-Is Analysis is done during the Blueprint phase of SAP project (or for any Enterprise Solution implementation).

These are carried out jointly by Package Solution Consultants, Business Process Consultants (Business Analysts) and End-user / Subject Matter Experts from client side, typically in the form of Workshop discussions/meetings.

During the As-Is Process Mapping the existing business processes are documented as they are in place (hence As-Is). Typically Swim-lane diagrams are used to map the different actions performed by the different business roles for a given business process. For example - Sales Order Management process will have Customer, Customer Service Representative and Sales Manager as three roles in the Swim-lane Diagram.

Next comes the To-Be process - here you come up with the business process as it should be after the solution implementation. This will incoporate the best practices from comparable industries for more efficient way of running the business.

Reward if helpful

Regards

Abhishek Swarup

[Former Member]

>

> Hi All,

>

> Can any one explain the following items used in implementation project using ASAP Methodology.

>

> 1. AS-IS Study.

>

> 2. To- Be Requirements.

>

> Thanks in advance,

>

> Regards,

>

> Vamsi.

Hi Vamsi,

1. AS-IS: In this we analyse the existing business and the current state, the way current processes are taking place, is reffered to as AS-IS process.

2. TO-BE: As you are implementing SAP you have a desired state of business you would like to improvise certain processes revamp others add a few delete a few other and hence you have in mind a desired business state after implementation of SAP this staet is reffered to as TO-BE.

The requirements to reach to TO-BE from AS-IS requires GAP analysis.

Hope it helps.

Post for furthur clarification

Regards

Abhishek Swarup