BUSINESS PROCESS REENGINEERING: (BPR)

Implementing an ERP system does not necessarily mean redefining an

organization's business processes. It (ERP System) can be used to enhance
and optimize the existing business process; however, an outright re-
engineering might be needed in some cases.

What is Business Process Re-engineering (BPR)?

Business Process Re-engineering simply implies eliminating tasks that does

not add value to a business process while reorganization the value adding
tasks. It can also be perceived as a restructuring of redundant dependent
tasks or work order. It involves a re-thinking and consequently a re-
moulding. In appreciating this concept, it is expedient to view a process as a
"chain of tasks". The truth is that in a typical business process, you can have
some redundant tasks that if not present does not really have any impact.
Such tasks can be eliminated thus streamlining business process.

During ERP implementation, before a business process can be re-

engineered, excellent understanding of the defective process is key. This is
why it is important to first carry out a critical and objective business process
definition and analysis before system design. At this juncture, it is important
to state that when restructuring a business process, adherence to best
practices is encouraged. This allows the client to be able to leverage the
redefined business process externally and not only internally

For business process reengineering to be successful and consequently, ERP

implementation, the buy-in of the end users must be achieved. Often times,
I've heard people say "this is how we have been doing it and we like it that
way". It is important to convince the process owners why a re-engineering is
needed. And the only way to do this is to make the user uncomfortable with
his hitherto work methodology. As a matter of fact, setting up of an in-house
restructuring team will help to foster users conviction within the
organization. The members of the team should cut across all process owners.
Conclusively, the benefits of BPR are enormous. They include the following,
but not limited to

1. Business process is streamlined.

2. Business process is optimized and more efficient.
3. Strict controls can be enforced and monitored.
4. Best practices can be adhered to.
5. Time and cost saving as a result of eliminated redundant tasks

STEERING COMMITTEE:

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.

CUTOVER PLAN:

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.

What is meant by cut off date?

Lets says the SAP system has been completely configured according
to the requirement of the client and is now ready to use. At this stage
the client now needs to migrate from the Old system (Legacy system)
to the new SAP system.
The migration from the old system to the new system is known as cut
off date. The old system is switched off and the new SAP system is
switched on. The data is migrated from the old system to SAP. The
existing data and the all the new transactions will henceforth be
entered in the new SAP system.

CUTOVER (CUT OFF) ACTIVITIES:

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 ARE going 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 thru F-48

BIG BANG IMPLEMENTATION

Implementation all modules in all locations at a time.

PHASED IMPLEMENATION

In the beginning implementing some modules-once the modules are

stabilized go for the balance modules

What is the difference between upgrade project and end to end

project.
Upgrade Project is a project where in SAP is already in place and it is
the version upgrade from a lower end to a higher version.
End to End project is a project where SAP is implemented for the first
time.
What are the types of testing in SAP? As a functional consultant What
type of testing are performed
a) Integration Testing: This test makes sure that
Organization Business processes working together with
other business processes.

b) Functional testing: This test makes sure that

Configuration data working as per the specifications.

c) Unit Testing: This test makes sure that Individual

parts of the program are working properly.

d) Regression testing: This test makes sure that any

new code added to the program does not have adverse
impact on already existed functionality.

What is P to P Process refers in SAP?

P to P refers to the Procure to Pay cycle.
The cycle is as follows;
Step 1: Purchase Requisition, A department of the company wants to buy a piece of
equipment e.g. a printer, a PR is created specifying the type of printer which is required and
the PR is submitted for approval.
Step 2: Request for quotation. The Procurement department creates a request for quotation
inviting suppliers to quote the price at which they can deliver the printer.
Step 3: Purchase Order. The replies are analyzed, a supplier is selected and a Purchase order is
created.
Step 4: Goods Receipt created when the printer is received
Step 5:Invoice Receipt. the supplier of the printer submits its invoice
Step 6: Payment
b)

USER ACCEPTANCE TESTING(UAT)

When we test any particular document with the user and if it is ok
immediately we have to take the signature on the document, which is signed
off and can be forwarded to the immediate boss. There are some steps to be
followed when we go for user acceptance testing.

SAP SOLUTION MANAGER:

The SAP Solution Manager is the platform that integrates all content, tools and
methodologies for the technical implementation and operation of mySAP.com e-
business solutions. It helps customers to manage their entire mySAP.com
solution landscape, including interfaces to third-party systems with a focus on
core business processes. The SAP Solution Manager consists of an operations
area for ordering and performing services, a solution monitoring section and a
support area for activities such as SAP Note search and automatic
implementation.

The SAP Solution Manager integrates in one platform:

System monitoring (real time)

Business process monitoring (real time)

Service level management (SLM Reporting)
Access to Best Practices for mySAP.com (service procedures /
documents)

Proactive and predictive services for optimization and maintenance over

the entire
lifecycle (Feasibility >> Integration >> GoingLive >> EarlyWatch >>
Conversion >> Upgrade)

Support desk with integrated messaging for user support (full range help desk
functionality with ongoing integration into mySAP Customer Relationship
Management (mySAP CRM) and a defined interface to SAP Support)

Remote support (desktop application sharing and service data transfer)