3.1 SAP Implementation Blue Print

Project Name:	jaya Enterprise Limited (JEL).
Document Name:	Blue Print
Document ID:	NOVAR_BP_SD0001_1.0			Version:	1.0
Prepared by:	XXXX (Project Manager)	Contact No.	1234	Date:	05.11.01
Reviewed by:	XXXX (Systems Manager & Technical Controller)	Contact No.	4567	Date:	08.11.01
Approved by:	XXXX (Systems Manager)	Contact No.	4567	Date:	09.11.01
Released by:	XXXX(Project Manager)	Contact No.	1234	Date:	09.11.01

Revision History

Sr. No.	Version No.	Date of Revision	Section Number	Description of Change	Reason for Change	Change made by	reviewed by

SAP_IMPLEMENTATION_BLUE PRINT

Business Process Master List

(Enter the entire Master list of Enterprise structure definition, Mater Data definition, Business processes and the sub-processes Under Business Process Master List. From ASAP Q &A D.B. Pick up Level 3 as ‘Process’ and Level 4 as ’Sub-process’ that are identified in scope. If the process happens to be outside the Q&A DB then add the process and sub-process appropriately.)

Process Description	Sub-Process Description
Enterprise Structure-Logistics
	Maintain Plat
	Maintain Storage Location
	..
	..
	..
Enterprise Structure-FI	Maintain Company
	Maintain Company Code
	..
Enterprise Structure-Co
	MaintainOperating Concern
	Maintain Controlling Area
	..
	..
	..
Master Data
	Maintain Material Master
	Material List (BOM)
	..
	..
Number Ranges
	Define Number Ranges for Master Recipes
	Define number ranges for planned independent requirements
	..
	..
Procurement of Materials & External Services
	Purchase Requisition
	Purchasing
	Goods Receipt
	Service Entry Sheet
	Invoice Verification
Procurement via subcontracting

Business Process Questions (From Q&A Database of ASAP)

Module
Process
Sub Process / No
Description

(For each sub-process identified in scope, generate a MS Word document listing the relevant question for the processes in scope. If the need is felt to add or reduce the questions from the generated document, then necessary update can be done with a mutual consent of Core team and the consulting team. Use the Forma t of Business Blue Print (Header Footer) to fill this section. The option of answering the Q &A Database Questions is Project specific, as customer would have priority to decide how they want to see the Business Blue Print. The answers to questions shall form the basis for collection and filling the inputs from Customer in C.I. Template)

(

Q.1 How are the purchasing requisitions are created in the case of stock material, material for direct Consumption, External Services?

Ans:

Q.2 Will you use Pruchase requisition to trigger creation of contract or Scheduling Agreement (Outline agreement request)?

Ans:

Q.3 How many days it take, typically before a purchase requisition becomes a demand in a purchasing document given to a supplier? Please indicate processing time per Plant.

Ans:

Q.3 Will Purchase requisitions generated via material/article requirement planning be manually post-processed?

Ans.:

Business Process Details (C.I. Template of ASAP)

(Enter the C.I. Template for all the sub-processes identified in the Business Process Master list under this section. You may prepare individual document for each sub-process. It may not be possible to address each and every topic, But if there is no answer possible please write None or Not applicable so that it confirms that this point is not missed by oversight to address. )

Module
Process
Sub Process / No
Description

Sr No	Topics
1.1	Requirements & Expectations
	(Customer expectations as well as requirement from the Process in text form. The requirements may not be addressed existing process but the customer expects the solution. This would act as objective which would be tried to achieve by the team)

Sr No	Topics
2.1	Existing Process General Explanation
	(Brief Description/ Identification of The existing Process is to be entered by customer. This may not exactly fit the process addressed by SAP.)
2.2	Explanation of Existing Functions & Events
	(It is important for customer to describe existing process in detailed steps, so that it becomes easy to cross examine the mapping/modification of existing process in proposed SAP process being Blue Printed.)
2.3	Special Organizational Considerations
	(Please write special organization considerations in case if the existing process is being handled in a peculiar way, which would be important to address the proposed SAP Process.)

Sr No	Topics
3.1	Proposed Process General Explanation
	(Enter in Brief module/transaction addresses the proposed process. The brief explanation would help customer get familiarized with proposed SAP Process)
3.2	Explanation of Proposed Functions & Events
	(Explain in details the Process of Proposed steps to be carried in SAP. This would help customer understanding the activities happening during the process.)
3.3	Special Organizational Considerations
	(Enter how the special organization considerations specified during Existing Process Definition is responded to during the proposed SAP Process.)

Sr No	Topics
4.1	Changes Management Issues
	(Identify the issues expected during implementation of Proposed SAP Process in form of list which is agreed with in the team.)
4.2	Description of Improvements
	(Consulting team shall discuss the possible improvements with Core team of customer. The agreed improvements shall be described jointly by the implementation team i.e. the core team as well as consulting team. The responsibility for improvement shall be highlighted in this section. )

4.3	Description of Functional Deficits
	(In case if customer is loosing certain functionality due to the proposed solution, then such deficits shall be listed in this section)
4.4	Approaches for covering Functional Deficit
	(The approach agreed to cover the functional Deficit shallbe described in Details)

Sr No	Topics
5.1	Notes on Further Improvement
	(If certain Improvements are identified but cannot be implemented in the current scope of implementation then such and brief details of improvements shall be listed.)

Sr No	Topics
6.1	System configuration considerations
	(Details about the considerations e.g. logic or policy or naming convention agreed for the customizing values shall be clearly defined. It is desirable to enter the navigation path as well as transaction code where the customization needs to be done.)
6.2	File conversion considerations (Master data maintenance).
	(The brief description of method of master data conversion is entered in this section. If the master data is being interfaced for conversion with Legacy System, brief details of method shall be explained. The involvement of Technical consultant for recommendation can help improve better description of conversion method.)
6.3	Interface / Enhancements considerations
	(If it is noticed that SAP standard solution does not meet the customer expectation. IF the solution is possible using certain enhancement or interface then the brief description of solution in text and in language of Functional Consultant shall be entered in this section. This would form a basis to list of developments to be provided with solution. While discussing and formalizing technical development, it is recommended to list the development and create draft functional specification which would get released for development in the Realization phase.)
6.4	Reporting considerations
	(It is required to identify the reporting of data captured in the process. The path as well as brief details for SAP’s standard report should be provided. If the standard report does not meet the customer requirement then the workarounds (alternative reports), would be discussed with the core team. If the solution is only development of report then it would be identified in the list of Developments and Functional as well as technical specifications shall be created in the Realization Phase.)
6.5	Authorization considerations
	(In case certain developments are to be done are allowed to be processed or to be dynamically processed by only a few users, then a generic role shall be identified and mentioned in this section i.e. Buyer for a particular plant.)

Process signoff document

Module
Process
Sub Process
Description

Organizational Units	Consultant	Core Team Member
1. Kolshet
2. Turbhe
3. Kandla
4. Corporate