Business Blue Print Document

Business Blue Print Document

Process ID: BBP_FI_007_Customer Vendor Communication

Process Name: Vendor/Customer Communication

Document Change History:

Version Date of Change Author Summary of Change
Draft 10.06.2013 Dhruma D. Vora Initial
Under 16.09.2013 Dhruma D. Vora Incorporated review comments with
Review User Champions
Final 16.09.2013 Dhruma D. Vora Final Version

Checklist
Business Event Description
 Are the Business Considerations and “To-Be” event descriptions complete?
 Are the descriptions clearly written? (Free of jargon, logically organized etc.)

Business Process Flow

 Have standard symbols been used?
 Do the flows reference appropriate manual and system points?
 Are the flows at an appropriate level of detail?

Other
 Have all interface and reporting points been identified?
 Have all development items been identified and documented?
 Have differences between current and To-Be processes documented?
 Have all issues been logged in the issues log? Cross Referenced in this document? Attached to
this document? (functional, technical, conversion, development, change management)
 Have all the gaps been documented?
 Has the business process been verified with User Requirement Documents?
 Have all high-level conversion considerations been documented?
 Has the application architecture been updated to reflect interfaces?
 Have all referenced items been noted and attached where appropriate? (Spreadsheets,
Functional information papers, etc.)

Business Event Summary

Process: Vendor/Customer Communication
Sub- Vendor/Customer Communication
Process:
Event This functionality controls the output of correspondence
Description: requests by calling up the print reports on a company code
basis for the individual correspondence requests. After
processing the correspondence requests are deleted.
The program is usually scheduled as a job once a day so that
the correspondence requests that have accumulated in the
meantime can be output.

To-Be processes
a. Vendor/Customer Communication
Page 1 of 4
 Business Blue Print Document

TO-BE: Proposed Business Process Description

Document future To-Be process based on system requirements. Note which tasks are system vs. manual
transaction. Also cross-reference the number of each task to the number of step in the process flow diagram.
No. Activity / Task Name Activity / Task Description System Transaction
01 Correspondence Request This functionality controls the output of correspondence F.61
for Customer requests by calling up the print reports on a company
code basis for the individual correspondence requests.
After processing the correspondence requests are
deleted.
The program is usually scheduled as a job once a day so
that the correspondence requests that have accumulated
in the meantime can be output.
02 Vendor Balance This function allows you to generate letters to your F.18
Confirmation vendors for the purpose of checking payables. The
program offers you the following:
 balance confirmation

Note: Any changes to Format will be considered as

development
03 Debit Note/Credit Note for  In case of price correction or quantity differences, N.A.
Price Correction and Qty credit/debit note will be raised.
Correction  If the invoice is booked through invoice
verification in MM module, then the credit/debit
note is issued through a MM credit/debit note

 Similarly, if the credit/debit note is for an invoice

through SD module, the credit/debit note is
issued through SD module
 Credit Note / Debit note can also be created for
those invoices which are raised through FI
directly.

Process Flow Diagram:

(To-Be)
(As-Is)

TO-BE: Development Items

Record development objects. Specify their type (I = Interface, R = Report, E = Enhancement, C =
Conversion, F = Form, W = Workflow) and priority (1 = Mandatory, 2 = Workaround required if not
implemented, 3 = Optional) required. Also cross-reference the number of each task to the number of
step in the process flow diagram.
No. Type Description Priority Ref. To-be Step(s)
01 Balance Confirmation Letter
02 Debit Note

Page 2 of 4
 Business Blue Print Document

TO-BE: Identified Business Work Practice Change

Document the identified business work practice changes to the As-Is process ( Nature of Changes would
be S- System; R – Roles, P- Policies)

Sr. Area Nature of Current Practice in SAP

No Change Practice

TO-BE: Pain Points and Associated Business Impacts

Document the identified Pain Points in the As-Is process and their resolution

Sr. Pain Points Business Resolution Comments

No Impact

As-Is Document Referenced

Document the list of As-Is documents referred in this To-Be process

Sr. As-Is Document No As-Is process Name

No

TO-BE: Identified Business Impacts

Document identified impacts to the business. Specify impact category (OG = Organisation, OP =
Operation, CU = Customer, OT = others) the level of criticality based on depth of business impact or size
of gap (H = High priority issue or benefit to address, M = Medium sized gap/ impact, L = Lower priority to
address).
*Note: This should take into consideration the Work Practice Change from the As-Is to the To-
Be
No. Description Impact Category Impact Level Mitigation

TO-BE: Identified Regulatory Impacts

Document identified regulatory Impacts to the business. Specify as H – High; M – Medium; L – Low. If the
process has no regulatory impact mark as none.
*Note: This should take into consideration the Work Practice Change from the As-Is to the To-
Be
No Description/Potential Failure Probability of Severity of Overall Mitigation
Occurrence Impact Impact
None

Additional Documents Referenced

Enter the location for all other documents which are referenced here. Enter the full path of the file. Enter
a brief one line description about what the document contains. (E.g. Business Blueprint, Process Flows,
Development Inventory, Issue Logs, etc.)

Page 3 of 4
 Business Blue Print Document

This BBP document is signed off based on following assurance:

1. Accenture will provide appropriate solution to meet the requirement as described in the ‘TO BE’
and the relevant ‘FIT GAP’ document.
2. Any change should be mutually agreed upon by both Cipla & Accenture and will be recorded as
an addendum to the BBP document.

Sign Off

Sign-off
Please sign and Date. Name Signature Date
Process Owner V.S.Mani

Core Team Member Ramnath

Vaibhav Vaidhya

Sandeep Narang

Datta Sharma

Pravin Mungekar

Functional Consultant Dhruma D. Vora

Quality Assurance Pravin Bhatkulkar

Page 4 of 4