You are on page 1of 1

Introduction

This Business Blue Print Document describes the following:


 Business requirements as given by the GRIL Key Users
 Suggestions by INDIA LLP. consultants wherever SAP ECC 6 are found to be useful to GRIL’s
business functionality
 To-Be Process on SAP ERP ECC 6 system suggested by BDO INDIA LLP. Consultants
 Comments whether the requirement can be realized on the SAP ERP ECC 6 system or not.
 Gaps which are at different stages of exploration

The following codes are given to each module that is within the scope of the agreement:

of To-Be Business
Status Description
Process
A-Possible Can be implemented on SAP ERP

B-Possible with workaround Can be implemented on SAP ERP through indirect means

C-Possible with ABAP Can be implemented on SAP ERP through ABAP/4 development

D-Possible with ABAP (But


Can be implemented on SAP ERP through ABAP/4 development but system performance may b
performance issue)

E-Not possible with out Major


Cannot be implemented on SAP ERP without major system modification
Modification
Possibility of implementation will be explored in the development environment. Cannot be confir
F-Open for exploration
this stage

G-Not possible Cannot be implemented on SAP ERP

Cannot be implemented because it is not part of the scope defined in the “Software Services Ag
H-Not in Scope
between BDO and GRIL

The To-Be business process realization is dependent on the following aspects:


 Scope of services described in the Software Services Agreement signed
 Scope of functionality described in the Software Services Agreement mentioned above.
 Capabilities and Limitations of SAP ERP
 As-Is Business Knowledge Transfer from GRIL Team members
 Business Requirements defined by the GRIL Team members