- SAP BA implementation require a
lot of technical expertise (BW/BI -advance level expertise on BW workbench,
TOOL BI, ETL,LSMW, PI Interface communication (flat file, XML, BAPI or
direct PSO or consuming real time front office operative data) so that reconciliation
or any mismatches can be identified or ensured that implementation / design
with exception / error testing is
fit for the purpose
- Integration architect role- critical as like any ERP implementation
from technical aspects of the solution implementation
Collaborative
approach that includes Architecture, Finance, IT and operational experts, agreed
– this is case of any solution in the ERP landscape –
- Foremost
& important role” in SAP BA implementation is the Finance Accountants (SMEs)
who understand IFRS –IAS disclosure / reporting reqs - not a high level but as low as individual
transaction level, expert can
review blueprints, input to testing, develop sample data cases/ strategy (which
I believe is the heart (back bone of the SAP BA testing)
- Data management itself is critical for successful implementation
and for ROI, that’s why SAP BA has archiving concepts in BA – this facilitate
correct – predictable analytics - I don’t think need for quality data can be ignored for pre-implementation
- correct raw data mining & controlling thought-out
the testing life cycle for recognition,
registration, valuation & classification and again derecognition, imbrutement from existing posting,
- We
do understand a single
distinction of the data (FT, BT) from its life cycle can change the
expected accounting behaviors / results - You will agree – IFRS is changing e.g. recent
changes in the IAS 36 for “Impairment of Assets”
made industry more vigilant with solutions
such as SAP BA
I also observed some time necessary
resource / talent lack on the implementation (technical or functional) as SAP
BA is bit new in industry compare to FICO - Some time SAP BA creates a very large number of “account
combinations” and journal lines from the transaction on the given period end (KDV-
EoD)- Number of values in each segment, composition of the extended accounting etc-
idea is to ensure accounts covered in
the transaction do not relate to the same sub ledger - otherwise the
transaction becomes an intra-ledger transfer – this is a good feature of
solution like SAP BA, but as someone like SME not being available on the project,
this good feature was modified in one
small implementation then reverted after
almost 4 months discussion …
In
many organizations, BA had become not only the system for financials AFI and
regulatory reporting, but also a system for operational management, planning
tool and reporting to internal performance with SAP BPC etc . Hence, if any of
the SAP BA project oriented organization lacked a strong talent for project
accounting and management – It must be looked a resource rather SAP BA
solution..
Compiling daily data for profit and loss or balance sheet reporting, determine appropriate accounting treatment (eg under IAS39) - Period end related analyses / procedure from accounting perspective -
projects must been ready for surprises and new lessons learnt.
As my career in QA and testing, I believe SAP implementation
scenarios is the easiest one provided right recourses are doing right job…
#Individual must be strong in both accounting for
financial instruments (IFRS -GAPP) and the mechanics in Bank Analyzer/BW
required to address the client’s reporting and disclosure requirements
Data sourcing and reporting teams to ensure a
cohesive end-to-end solution. Be a Package Solution Consultant SAP BA project. One
must not just solving IT problems but understands and works with finance …
A good read, thanks Rajesh.
ReplyDelete