Академический Документы
Профессиональный Документы
Культура Документы
BUSINESS BLUEPRINT
SAP NetWeaver BW
DOCUMENT APPROVALS
Selman Al-Fares
AIG Project Sponsor
Ali Mezrawi
AIG Program Director
Mutahhar Khan
Wipro Delivery Manager
Hans Greeff
AIG Project Manager
Eswaran Krishnan
Wipro Project Manager
DOCUMENT CONTROL
Document Issue History
Revision History
Date Revision by Page No Revision Approved By Signature
Description
AIG-BBP-
BW-V1.0
Project Shaheen
TABLE OF CONTENTS
1 EXECUTIVE SUMMARY ................................ ................................ ................................ ............................ 7
1.1 BACKGROUND ................................ ................................ ................................ ................................ 7
1.2 AIG VISION ................................ ................................ ................................ ................................ ...... 7
1.3 ABOUT AIG SUBSIDIARIES................................ ................................ ................................ ................. 7
1.4 ENTERPRISE RESOURCE PLANNING OBJECTIVE ................................ ................................ ............................. 9
1.5 BUSINESS BLUEPRINT O VERVIEW................................ ................................ ................................ .............. 9
1.6 IMPLEMENTATION SCOPE - ERP ................................ ................................ ................................ ............. 10
1.6.1 Functional Scope - ERP ................................ ................................ ..... Error! Bookmark not defined.
1.7 SAP NET WEAVER BUSINESS W AREHOUSING: OVERVIEW ................................ ................................ ............ 11
1.7.1 Objective of Document ................................ ................................ ................................ .............. 11
1.7.2 SAP Net Weaver Business Intelligence : ................................ ................................ ....................... 11
1.7.3 Architecture SAP Net Weaver BW ................................ ................................ .............................. 11
1.7.4 BW Architecture: Enterprise BW Data Management ................................ ................................ .. 12
1.7.5 Enterprise Data Warehousing (EDW) Processes: ................................ ................................ ...... 14
2 ORGANISATION STRUCTU RE - ERP ........................................................................................................ 15
3 FUNCTIONAL SCOPE SAP NETWEAVER BW ......................................................................................... 16
3.1 IMPLEMENTATION SCOPE - SAP NETWEAVER BW ................................ ................................ ..................... 16
3.1 .1 Geographical Coverage - SAP NetWeaver BW ................................ ................................ ........ 16
3.1 .2 Functional Scope - SAP NetWeaver BW ................................ ................................ .................. 16
3.2 BW F UNCTIONALITY IN SCOPE ................................ ................................ ................................ ............... 18
8.1.1 EDW Processes ................................ ................................ ................................ .......................... 18
8.1.2 BW Suite / BEx Tools ................................ ................................ ................................ .................. 19
3.3 SOURCE SYSTEM ................................ ................................ ................................ ................................ 20
4 REPORTING REQUIREMEN T - STANDARD REPORTS ................................ ................................ ............... 21
4.1 KEY PROCESS INDICATORS ................................ ................................ ................................ .................... 21
4.2 FUNCTIONAL ACCOUNTING ................................ ................................ ................................ ................... 22
4.3 CONTROLLING ................................ ................................ ................................ ................................ ... 22
4.4 SALES & DISTRIBUTION................................ ................................ ................................ ........................ 22
4.5 MATERIAL MANAGEMENT ................................ ................................ ................................ .................... 22
4.6 PRODUCTION PLANNING ................................ ................................ ................................ ...................... 22
4.7 PLANT MAINTENANCE ................................ ................................ ................................ ......................... 22
4.8 QUALITY MANAGEMENT ................................ ................................ ................................ ...................... 22
4.9 PROJECT S YSTEM ................................ ................................ ................................ ............................... 23
4.10 ENVIRONMENTAL HEALTH & S AFETY ................................ ................................ ................................ ....... 23
4.11 HUMAN RESOURCES ................................ ................................ ................................ ........................... 23
5 REPORTIG REQUIREMENT CUSTOM REPORTS ................................ ................................ .................... 24
5.1 REPORTING REQUIREMENTS ................................ ................................ ................................ .................. 24
6 DETAILED DESIGN .................................................................................................................................. 25
6.1 INTRODUCTION ................................ ................................ ................................ ................................ .. 25
6.2 GENERAL CONSIDERATIONS ................................ ................................ ................................ .................. 25
6.2.1 Source System for Data ................................ ................................ ................................ ............. 25
6.2.2 Languages ................................ ................................ ................................ ................................ 25
6.2.3 Currency ................................ ................................ ................................ ................................ ... 25
6.2.4 Calendar ................................ ................................ ................................ ................................ ... 25
6.2.5 Data AvailaBWlity ................................ ................................ ................................ .................... 25
6.2.6 Architectural Principal ................................ ................................ ................................ .............. 25
6.2.7 The Key factors considered in Design ................................ ................................ ........................ 25
6.2.8 Layers in the Architecture ................................ ................................ ................................ ......... 26
6.3 SYSTEM LANDSCAPE................................ ................................ ................................ ............................ 26
Project Shaheen
1 EXECUTIVE SUMMARY
1.1 BACKGROUND
Astra Industrial Group (AIG) is one of the major industrial companies in Saudi Ara BWa which is
actively engaged in supporting the local economic development through value -added products that
are offered by its five industrial subsidiaries.
AIG was formed as a result of the reorganization of the Arab Company for Supply and Trading Co.
(ASTRA) industrial business where it merged its industrial companies to form a holding company. AIG
now owns five leading industrial companies that are active in Pharmaceutica l, Chemicals, Steel and
Engineering sectors.
1. Tabuk Pharmaceutical Manufacturing Company Ltd. ("TPMC")
2. Astra Polymer Compounding Company Limited ("Astra Polymers")
3. Astra Industrial Complex Company ltd for Fertilizer and Agrochemicals ("AstraChem")
4. International Building Systems Factory Company Limited ("IBSF")
5. Al-Enmaa Steel Company (Iraq)
AIG aims to reinforce and enhance its position as a leading industrial group in the Middle East and
North Africa (MENA) Region through improving the performance of existing businesses as well as
investing in new industrial ventures.
The Groups revenues and net income are organically derived from its subsidiaries, which are
generally considered as market leaders in their respective industries, and inorganically through
merger & acquisitions. All subsidiaries are headquartered in Saudi Ara BWa apart from the recent
acquisitioned company Al-Enmaa which is headquartered in Jordan and plant in Iraq. AIG have a
geographical reach in MENA region, Western Europe, and expanding their reach in Eastern Europe
and South East Asia.
Since its foundation in 1994, Tabuk is in the global branded generics pharmaceutical
industry, Headquartered in Riyadh, Saudi Ara BWa, with GMP facilities in Tabuk city, the
company has strong presence across the Middle East and North Africa (MENA), Central
Eastern Europe (CEE) and a promising outlook in Western Europe, Commonwealth of
Independent States (CIS) and the USA.
TABUK can manufacture oral as well as sterile cephalosporin anti BWotics. Additionally it has
another facility for the production of regular generic products.
Project Shaheen
One of TABUKs major assets is its Marketing, Sales and Distribution Network, which covers
all the MENA, CEE and CIS markets.
Astra Agricultural was established in 1988 to market and sell various agrochemicals,
fertilizers, and other agricultural inputs. It is curren tly the local agent and distributor of
many multinational companies in Saudi Ara BWa and the Middle East region. Headquartered
in Riyadh, the company is comprised of a well established local and regional network of sales
and distribution centers, as well as field demonstration and testing sites.
In 1996, after eight years of success, Astra Agricultural took a step towards further
integration and diversification by setting up its own state of the art plant " AstraChem", in
the Eastern Province of Saudi Ara BWa. The plant blends fertilizers, agrochemicals, and public
health insecticides, which are marketed and sold by Astra Agricultural in Saudi Ara BWa and
the Middle East.
Al-Enmae steel company is acquired by AIG in November 2009. It is basically a Steel Rolling
Mill and will be manufacturing rolled products and BWllets. The plant is still under
Project Shaheen
construction and located in Khor Al -Zubair in Basra, Iraq. It also has oxygen plant, water
treatment plant with RO system and fume de-dusting plant. The Head Office is located in
Jordan.
To implement SAP ERP 6.0 EHP4 standard business processes. Adhere to business basics and use SAP
as a model for best business practices. Integrate business processes and functions across the
organization. Improve AIG capacity to close its books quickly at the month end on a global and
consolidated basis.
The following SAP ERP 6.0 EHP4 Modules & SAP Ne t Weaver EHP2 is being implemented:
FI Financial Accounting
CO Controlling
SD Sales and Distribution
PP Production Planning & Control
MM Materials Management
QM Quality Management
PM Plant Maintenance
HR Human Resource
PS Project System
EHS Environmental Health & Safety
BW Business Warehousing
DMS Document Management System
ESS & MSS Employee Self Service & Manager Self Service
CRM Customer Relationship Management
EP Enterprise Portal
This document summarizes the findings of the Wipro Ara BWa Ltd consulting team, which conducted
requirement analysis of AIG for the SAP ERP 6.0 EHP4 systems. The information was gathered
through workshops and meetings conducted at the AI G plant with key users , Super Users, Business
Owners and personnel from Information Systems, as well as through reviews of business processes,
business procedures, documentation relevant reports, plant visit and standard operating
procedures (Interim and final).
Project Shaheen
The purpose of the analysis is to prepare & to move forward rapidly with the business process for
AIG in SAP ERP 6.0 EHP4 system. At the conclusion of the blueprint, Wipro Ara BWa Ltd consultants
will determine the SAP functionality required to run the AIG business respectively.
The Blueprint presents a summarized perspective of all functional business processes that will be
implemented. Blueprint document will serve - from this point forward the dual role of official project
scope as well as system acceptance criteria and the way SAP ERP 6.0 EHP4 will be configured for AIG.
The body of this document describes the organizational structure, master data and SAP ERP 6.0
EHP4 functional process flows to be rolled out at AIG. Certain key requirements are explicitly
identified and summarized to highlight their importance to AIG and to document the approach
proposed to meet the requirement.
One section of the report summarizes identified gaps and the solution proposed by the consultants
in SAP. There can be a gap which cannot be filled in that case AIG has to change its process according
to the standard practice.
The Blueprint reiterates the SAP ERP 6.0 EHP4 organizational structures that have been identified
and will serve as the basis for the initial conf iguration activities. The Wipro AraBWa Ltd team
believes that SAP ERP 6.0 EHP4 can accurately model AIG organizational requirements.
No significant configuration choices have been identified that will prevent the future
implementation of additional capa BWlities within the SAP ERP 6.0 EHP4 environment. The
information gathered and documented in the Blueprint is sufficient for the team to go forward into
the Realization phase. However, it is critical that both the Wipro and AIG team agree on the scope of
the project as presented in this document. Acceptance - by both teams - is required to move the
project into the next phase.
The Implementation scope includes the Geographical coverage details and the Functional Scope
The following SAP ERP 6.0 EHP4 Modules are being implemented:
FI Financial Accounting
CO Controlling
SD Sales and Distribution
PP Production Planning & Control
MM Materials Management
QM Quality Management
PM Plant Maintenance
HR Human Resource
PS Project System
Project Shaheen
The figure below defines what SAP believes are the key components of a BW system.
Performance Management
Provides all means to accelerate query performance, in particular the SAP Net Weaver BW
Accelerator.
Project Shaheen
SAP Enterprise
Structure AIG V3.0.doc
Project Shaheen
As per the project scope this system act a repor ting system for all entities in SAP ERP EHP4 system.
AIG Companies
Repetitive Manufacturing
FI Financial Accounting General Ledger Analysis
Asset Accounting Analysis
Accounts Payable Analysis
Accounts Receivable Analysis
CO Controlling Product Cost Controlling
Cost Center Accounting
Overhead Cost Orders
Profitability Analysis (COPA)
QM Quality Management Notification Analysis
Inspection Lot Analysis
PM Plant Maintenance PM Notification Analysis
Maintenance Orders Analysis
PS Project System Network Activity analysis
WBS Element Analysis
EHS Environmental Health & Safety Industrial Hygiene and Safety
Product Safety
HR Human Resource Organizational Management
Recruitment
Personnel Administration
Objective Setting and Assessments
Shared Services
Talent Management and Talent Development
Training and Event Management
Payroll
Compensation Management
Cross-Application Time Sheet
Personnel Development
Benefits
Enterprise Compensation Management
Learning Solution
Talent Development
Time Management
Project Shaheen
SAP NetWeaver Business Warehouse (BW) is an enterprise wide data warehouse solution that has
different Business Warehouse (BW) applications and tools are available to the organization. The B W
Team has considered the following requirements of the project including requirements such as BEx
Analyzer access to the end users.
Process Chains
A process chain is a sequence of processes that are scheduled to run in the background - (events
trigger processes) and are used to automate the complex processes that run in SAP BW. The BW
team will use process chains to centrally plan and control the dai ly data extraction, transformation
and loading of the Info Providers.
Transport Connector
The BW team will use the Transport Connector to assemble all the necessary metadata objects
required for transportation from the development environments to the tes t environments by using
the CTO tool (Change & Transport Organizer).
Business Content
Project Shaheen
SAP BW Business Content is an entire business model that contains all relevant metadata for use in
BW implementations. It includes metadata from all SAP standard application components.
When BW Business Content is installed, the following metadata objects are pre -configured, ready for
use:
1. Info Objects
2. Info Sources
3. Info Providers
4. Data Sources
5. Queries
6. Workbooks, etc.
Information Broadcasting
Information Broadcasting is accomplished by the BEx Broadcaster that provides all the functions
necessary to distribute queries, reports and analyses to end users and to the Enterprise Portal. In
addition, the BEx Broadcaster provides a wide range of functions such as alerting and the pre -
calculation of results. . Information Broadcasting is Seamless integration of BW capabilities with
Enterprise Portal, Collaboration and KM.
Project Shaheen
SAP ERP 6.0 EHP4 is the only source system considered for this SAP NetWeaver BW implementation
project.
Project Shaheen
As per the business discussions all standard reports in all modules will be activated. However we
would like to caution on the following:
1) Some of the BW Standard reports may give wrong / blank results due to the standard report
design itself and which is different due to the Business scenarios implemented in R/3.
2) The Business may get confused due to the results being different in R/3 and BW.
3) Data base size will increase which will limit the performance of the system.
4) Maintenance activates will increase by the above feature.
FI 51
FI-New Reports 58
CO 212
CO - New Reports 27
SD 86
MM 89
PP 80
QM 59
PM 41
Project Shaheen
PS 14
EHS
HCM 188
Total 905
4.3 Controlling
6 DETAILED DESIGN
6.1 Introduction
In the following section, a more detailed description of the overall design is given. It will zoom in on
the overall design and describe the content of several data elements.
In the content description, we will mention the objects that will be contained i n the DSO and cubes.
A DSO is meant for data aggregation and for detailed navigation, and it will contain more detailed
information than the cube. In general the DSO will consist of more objects than the related cube;
therefore not all information will be available in the cube. DSO is based on two dimensional whereas
an Info Cube is based on multidimensional model
6.2.2 Languages
All the analytical reporting requirements will be provided in English language only.
6.2.3 Currency
All currencies will be translated in the related currency(s) in the source system itself.
6.2.4 Calendar
All the reports will be accessed using only the CL IENT calendar / period and the CLIENT Year / period.
Specific reports will be available for quarterly and/or yearly.
Integrity: Single point of truth. As far as possible all redundant data extraction is removed. Standard
SAP extractors have been tailored to only bring required fields and any duplication of data fields
within extractors has been minimized.
Stability: Stability of the back end data model in terms of minimal extractions to serve the data
points, splitting of logical groups of data to minimize the data volume in one single flow. Building up
of the staging layer to get as is data is done.
Project Shaheen
Performance: Performance of data load and the reporting is considered while making the Data
model design and the Cube and Multi provider Dimension groupings. Use of ABAP routines is
minimized. Different options will be tried during the prototyping phase for better performance.
Supportability and Maintainability: The model is designed to keep the housekeeping jobs to the
minimum. The data flows are kept simple and only grouped logically.
Flexibility/Extensibility: The design (Customization objects) is made into four layers of which the
reporting layer will be only out of multi provider, for any future requirement which may need
additional data the relevant info provider can be plugged into the Multi provider.
AIG implementation only activates the SAP delivered Business content data flow.
Data extraction layer: Includes the Data sources, and transfer rules. This will ensure that only the
required fields are pulled into the information warehouse. Any cleansing of data or small
transformation will be done in this layer. At this point in the design there is only di rect mapping of
data fields.
Consolidation layer: The consolidation layer is designed to cater to the reporting requirements
since the reports cut across different functional sub groups this layer provides a single platform for
consolidating all the data in one single granularity.
Reporting layer: This layer consists of the Multi provider and the cubes, all the reports will be built
out of multi providers and hence the user can be given access only to the multi provider for creating
queries.
Following system landscape has been designed for BW system. SAP ECC and SAP BW are connected
through ALE (Application Lint Enabling) connections using Logical System Names. BW system has
only one client will connect to multiple ERP system clients.
To establish correct data loading procedure, BW development system will be connected to ECC
Development (Unit Testing client-Client: 203). BW Quality system will be connected ECC Quality
System (Client: 500) Similarly BW production system (Client: 900) will be connected to ECC
Production Client.
There will not be any mock production cutover for BW as the data base size for ECC will be very
small at the time of production cutover.
Project Shaheen
The picture depicts data flow only between first three lay ers. Queries and reports will be built on
Data Warehouse layer i.e. either on Data Store Objects (DSO) or on Info Cubes or on info objects
(which are converted as data provider).
As of SAP BW 7.0, a new object concept is available for Data Sources. It is used in conjunction with
the new concepts in data flow and process design (Data Source Transformation Info Source
(optional) Transformation Info provider).
In 3.x version of data flow concept (Data Source Transfer rule Info Source Update rule
Info provider) co-exist. Business Content Master Data & Transaction data objects are available in 3.x
Versions only.
In order to keep system ready for any kind of upgrade in future and considering SAP
recommendation, it was decided to use new conce pt of dataflow for Customization objects.
Additional activity of Data Source migration from 3.x Version to 7.0 will be taken up during source
system replication.
Business content in SAP BW is delivered with data source extractors that can be used in the daily ETL
activities. SAP extractors of SAP ECC master and transactional data use various update modes
Process Chains will be built and used for data loading in AIG BW implementation. Data loading will
schedule daily. BW reports will display data one day delay form the ERP system. Based on the report
requirement & importance will implement Real -Time data acquisition (RDA) if Standard Data
Extractors support.
Delta Update:
From go live onwards; SAP BW will perform delta updates on a daily basis that means any new or
changes to existing transactional documents in the SAP source systems will be extracted into the
appropriate Info Providers for reporting and analysis.
Full Update:
The master data characteristics (i.e. text descriptions, attributes and hierarchies for document types,
reason code categories etc will be performed using full updates. Once these master data objects are
configured in both source systems, they tend to be quite stable. For that reason, master data that
belongs in this update mode will be loaded once a week instead of daily.
Process Chains:
The process chains will be built in SAP BW that automates the complex daily ETL (extraction,
transformation and loading) processes for the BW system administrators.
In the production environment, critical master data and all transactional data extractions from the
source systems are currently assumed to be on a nightly basis. However some of the data where SAP
Extractors are not Delta enabled, data loading will be done using appropriate selection.
Project Shaheen
Master data facilitate navigation into reports. All the master data will be loaded into BW from ECC
system. No master data will be manually created within BW. This will ensure the data integrity
between ECC and BW system. Some of the important master data are mentioned below. This is only
an indicative list.
Material Master
Customer Master
Vendor Master
Profit Center
GL Accounts
Cost Center
Project Definition
WBS Element
Employee Master
Work Center
Equipment
Plant
Chart of Accounts Etc.
Profit Center
Cost Center
Network. Etc.
Hierarchies
Values of a master data element in a tree structure are called hierarchies. These hierarchies are
normally used for reporting purpose. These are also normally loaded from source s ystem. In
exceptional cases, it will be possible to create and edit hierarchies within BW system for facilitate
different reporting structures across business unit. This will be controlled through system
administrator. It will also be possible to provide c ontrolled access to business for editing, if the need
arise.
However, it will not be possible to enter a master data values in the hierarchy creation manually, it
need to be selected to possible values only. For example, while creating hierarchy for profi t centre,
one cannot enter GBPAPA301 manually. It has to be selected from the list of master data that are
Project Shaheen
already loaded from source system. This will ensure the data integrity between master data element
and hierarchy.
7 DATA MODELS
Following Modules Info Providers, respective Info Sources, Transformations/ Update Rules /Transfer
Rules and Data Sources will be installed from SAP Standard business content. All Standard Objects
are being activated in SAP BW for AIG.
AIG identified Data Models will create Process Chains (PC) for automatic data loading.
Following Info Providers (Info Cubes, DSO, Multi Provider etc) respective Info Sources and Data
Sources will be installed from business content as per the requirement.
7.1.1 FI : InfoProviders
7.2 Controlling
7.2.1 CO : InfoProviders
Following InfoProviders (InfoCubes, DSO, MultiProvider etc) respective InfoSouces and DataSources
will be installed from business content as per the requirement.
7.3.1 SD : InfoProviders
7.4.1 MM : InfoProviders
7.5.1 PP : InfoProviders
7.6.1 PM : InfoProviders
7.7.1 QM : InfoProviders
7.8.1 PS : InfoProviders
S. Extraction
Technical Name Description Frequency GAP
No Mode
1 0PS_CSH_WBS Payments on WBS Elements
2 0PS_DAT_MLS Dates Milestones
3 0PS_DAT_NAE Dates Network Operation
Element
4 0PS_DAT_NTW Network dates
5 0PS_DAT_NWA Dates Network Operation
6 0PS_DAT_PRJ Date Project
7 0PS_DAT_WBS WBS Element Dates
8 0PS_CSH_ORD Payments on Orders
7.10.1 HR : InfoProviders
BW_Master
DataSource List
Project Shaheen
8 NAMING CONVENTIONS
Objects unique to BW and not covered by other areas of SAP ECC are those used to define and
report on the contents of the BW. They have in common a naming convention comprised of two
parts: a Descriptive name and a Technical name. The following conventions apply to the
Technical name.
As a rule all BW Object Technical Names created by the project will begin with Y or Z. Objects
beginning with a Y are under development and test and can only be found in the Development of
BW. Once proven to the satisfaction of the project Y objects than re -named to with a Z objects in
Development and move to BW Quality than BW Production .
SAP provided Info Areas are pre-defined, but can be changed. Whenever possible, utilize the
delivered Info Areas. If a new area is needed, it should be named appropriately.
Up to 30 characters for the technical name and 60 for the description are pr ovided.
8.1.4 InfoObject
Info Objects are limited to nine characters. SAP has re -engineered the naming of fields to be more
like English. In the spirit of continuing this process, yet maintaining the customized identifier, all
new Info Objects will begin with the letter Z, and the remainder of the object name will be as
descriptive as possible. The naming convention is as follows:
The first consideration to be made is that the Info Cube is correctly placed within the appropriate
Info Area. In the case of extremely sensitive data, the cubes may reside in a separate Info Area
defined as Confidential. In all other cases, there are many Info Areas to use for cube assignments.
The technical name is restricted to nine characters as follows:
A DSO object serves to store consolidated and debugged transaction data on a document level
(atomic level). It describes a consolidated dataset from one or more Info Sources. This dataset can
be analyzed with a BEx Query or Info set Query.
8.1.13 Queries
Extract Structure is automatically generated when a Data source is created. But when
creating Data source based on function modules, we need to create customized extract
structure.
8.2.4 Views
ATTR-Attribute
TEXT-Infoobject Text
HIER-Hierarchy
TRAN-Transaction
Datasource
Description 20 <Module><Business FIAR_BWlling
Area>_<Free Text>
Project Shaheen
9 AUTHORIZATION MATRIX
AIG BW authorization matrix needs to be discussed with Business and prepared.
Based on AIG authorization Matrix all the identified BW standard reports will modify and
incorporate the identified Organization objects accordingly.
9.5 Authorization
All users, who want to display data from BW system in a report, will require analysis authorization.
This type of authorization is not based on the standard authorization concept of SAP. Instead, these
authorizations use their own concept that takes the features of reporting and analysis in BW into
consideration. Using the special authorization concept of BW for the display of report data, it will be
possible to protect especially critical data in a much better way.
It is important to note in this context that reporting analysis authorizations of BW system are not
connected to SAP ECC authorization. This means, a user can not have authorization for plant xxxx in
ECC but can have reporting analysis authorization in BW system for plant xxxx and vice-versa.
Project Shaheen
10 TESTING STRATEGY
Testing Phase Test cases Test system Project Phase Test requirements
Prepared and test
performed by
Unit Test Developer Development Realization Connectivity with ERP
Dev System Test data
covering all transactional
scenarios in ERP Dev
system.
User Business Process Quality User Connectivity with ERP
acceptance Owner / User Assurance acceptance Quality system to BW
test System Quality system. Test data
available in all the source
system Report layout
verification and data
validation.
Since we are activating all standard reports, gaps will be identified post business seeing the reports
in the system if any.