09122013 SGS SolutionReviewReport FICO

8/11/2019 09122013 SGS SolutionReviewReport FICO

http://slidepdf.com/reader/full/09122013-sgs-solutionreviewreport-fico 1/26

Design Review of SAP SolutionDetailed Report of Findings and Recommendations

SGS

Mohamed Anan / SAP MENANovember, 2013



© 2012 SAP AG. All rights reserved. 2Customer

Agenda

Review Approach

Risk Reporting Levels

Areas Reviewed

Interviews

Findings and Recommendations

Summary of Recommendations



Review Approach






Design Review of SAP Solut ionKey Components

Service is delivered by experienced SAP Reviewers

Agenda Meeting - Review of the agenda with the

Customer Sponsor and Customer Review Coordinator

to capture input to the QA process.

– The review examines the following solution areas in detail and

assigns a risk rating to each

o Business Process Design

o Application Designo Solution Architecture

Key Interviews - Discussions are conducted with

Customer and Partner Subject Matter Experts

Preliminary Findings are presented to the Customer

Sponsor at the end of the onsite interviews

Detailed Report is delivered to the customer after approximately 10 days




http://slidepdf.com/reader/full/09122013-sgs-solutionreviewreport-fico 7/26© 2012 SAP AG. All rights reserved. 7Customer

Design Review of SAP Solut ionRisk Reporting Levels

The Risk Level indicates the impact of a finding on a successful implementation (if

the design is left as is).

High

– Must be addressed before passing the current Quality Gate. It will impact a successful solution design if

left unchanged. Immediate investigation and follow up actions are required.

Medium

– Should be addressed before passing the following Quality Gate. You may continue the project with it,

but you are likely to experience numerous solution design related problems. Further investigation and

follow up actions are necessary.

Low

– Less critical. Try to fix the finding before next project phase starts if there are no other pressing issues.



Areas Reviewed



Design Review of SAP Solut ion Areas Reviewed

AreaName of assigned SAP

Reviewer

SAP ERP Finance and controlling Mohamed Anan



Interviews and Documents



Design Review of SAP Solut ionInterview Participants

Name Project Role Organization

Melhem, Mansour S. Acting Project Manager SGS

Abdullah AlQahtani Project Manager Java Gulf

Mr. Iehab budget manger SGS

Mr. nayf Revenue Accounting Manger SGS

Mr. ahmed bujunaid Financial Closing Accountant SGS

Mr. Osama Cash Journal Accountant SGS



Findings and

Recommendations



SAP FICOFinding 1

Data Migration

Risk Level:

Description of Finding:

– There is no profit center hierarchy

– There is no data migration sheets provided

Impact:

– The revenue cycle will not work properly without designing profit center hierarchy with its related profit

center master data

Recommendation:

– Design and create profit center hierarchy



SAP FICOFinding 2

End-User Training

Risk Level:


– Training that has been provided so far is focusing on the data entry process of different transactions,

however training on reporting has not been properly addressed.

Impact:

– User readiness to use SAP once live might be at risk, an overload on the bandwidth of support

resources might arise which might cause impacts on project timeline.

Recommendation:

– Training Manuals need to contain an elaborate explanation on the goals/usage of essential reports

within SAP, this will ensure users will have the ability extract and display the required reports on the

system minimizing the risk of overloading support resources once the system goes live.





SAP FICOFinding 4

Cash Journal

Risk Level:


– There is no cash journal available to be used

– Cash receipt and cash payment Printout form requires formatting and text content

Impact:

– The cash process is not working at all

Recommendation:

– Configure the cash journal according to SGS needs

– Enhance cash receipt forms




SAP FICOFinding 5

Revenue Cycle

Risk Level:


– The Revenue cycle is not designed and accordingly the revenue accountant still not using the system

and still depending on the manual system – Profit centers master data is not exist at all

Impacts

The final Financial reports will not include the revenues

Recommendation:

– Create profit center hierarchy with its related master data migration – Design the revenue cycle according to SGS requirements

– End user training need to be conducted for revenue cycle




SAP FICOFinding 6

Controlling

Risk Level:


– The different projects for SGS is not tracked properly from cost prospective

Impact:

– Missing detailed expenses and revenue reports per each project

Recommendation:

– Using the internal orders to trace the projects expenses and revenues




SAP FICOFinding 7

Period end closing/Year end closing

Risk Level:


– Foreign currency evaluation program is not implemented

– Period and year end reports are not issued from the system – Correspondence forms are not configured(account statement, balance confirmation, checks, financial

reports……)

Impact:

– The foreign currency indifferences still counted manually

– Period and year end reports is still issued manually

Recommendation:

– Configure the foreign currency program

– Enhance correspondence forms




Design Review of SAP Solut ionDashboard

Findings Risk Levels1 SAP ERP FICO- Data Migration Medium

2 SAP ERP FICO– End User Training Medium

3 SAP ERP MM – Funds management Medium

4 SAP ERP FICO – Cash Journal Medium

5 SAP ERP FICO – Revenue Accounting Cycle High

6 SAP ERP FICO - Controlling Medium

7 SAP ERP FICO –Period end closing / Year end Closing High



Summary of Recommendations




Design Review of SAP Solut ionSummary of Recommendations

Medium Risk findings:

Regular weekly or bi-weekly meetings need to be scheduled and attended by all

stakeholders from different FICO departments and Java Gulf SMEs, the objective of the

meeting is to synchronize on the latest status of the data available in the system,

furthermore to discuss and agree on an action plan on missing/un-entered data thusenabling smoother execution of FI process and reporting

A Cut-Off strategy needs to be in place with realistic and agreed upon dates, any

transactional data during cut-off period needs to be tracked, a SPOC from each department

needs to identified to consolidate and submit the delta once system is live.

Training Manuals need to contain an elaborate explanation on the goals/usage of essential

reports within SAP, this will ensure users will have the ability to extract and display the

required reports on the system minimizing the risk of overloading support resources once

the system goes live.




Design Review of SAP Solut ionConclusion

Issues/Risks have been identified and highlighted in this report

those need to be properly and swiftly addressed early enough to

avoid serious impacts during critical stages of the project.




Design Review of SAP Solut ionQuestions and Answers, Next steps and Wrap-up

Roundtable

Questions

Answers

Discussion

Next steps

Confirm agreement on next

steps (if any)

Wrap-up of meeting

The Solution review service is hereby completed without any further iterations /

repercussion on SAP, it is entirely up to SGS and the project team to take the

recommendations forward. All findings and recommendations of the report are based

on the information provided to SAP.



Thank you

Contact information:

Mohamed Anan

FICO Team Lead Consultant

SAP MENA

+201005156356



© 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose

without the express permission of SAP AG. The information contained herein may be

changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary

software components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,

System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power

Architecture, Power Systems, POW ER7, POWER6+, POWER6, POWER, PowerHA,

pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,

RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,

Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered

trademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin

are trademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C ®,World Wide Web Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,

Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry

Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App

World are trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,

Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,

Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are

trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, SAP HANA, and other SAP products and services mentioned herein as well

as their respective logos are trademarks or registered trademarks of SAP AG in Germany

and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal

Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services

mentioned herein as well as their respective logos are trademarks or registered trademarks

of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase

products and services mentioned herein as well as their respective logos are trademarks or

registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360° , and B2B 360° Services are registered trademarksof Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective

companies. Data contained in this document serves informational purposes only. National

product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be

reproduced, copied, or transmitted in any form or for any purpose without the express prior

written permission of SAP AG.