Business Blue Print Document

Business Blue Print Document (To-Be)

Process ID: BBP_FI_005_Posting Period Variant

Process Name: POSTING PERIOD VARIANT

Document Change History:

Version Date of Change Author Summary of Change
Draft 22.05.2013 Dhruma D. Vora Initial
Under 05.09.2013 Dhruma D. Vora Incorporated review comments with
Review User Champions
Final 05.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?
 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.)

Page 1 of 5
 Business Blue Print Document

Business Event Summary

Process: FI _ POSTING POSTING PERIODS VARIANT
PERIODS VARIANT
Sub- POSTING PERIODS POSTING PERIODS VARIANT
Process: VARIANT
Event You can specify which company codes are open for
Description:
posting in a posting period variant. Posting period
variants are cross-company code and you have to
assign them to your company codes. The posting
periods are then opened and closed simultaneously for
all company codes via the posting period variants. If the
posting control is to be done separately for each
company code, separate posting period variant needs to
be created for each of the company codes.

To-Be processes

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.
System
Activity /
No. Activity / Task Description Transactio
Task Name
n
01 Posting You can specify which company codes are open for posting OBBO
periods in a posting period variant. Posting period variants are cross-
variant company code and you have to assign them to your
company codes. The posting periods are then opened and
closed simultaneously for all company codes via the posting
period variants.
Working with posting period variants is recommended if you
are responsible for a large number of company codes. Since
you only have to open and close the posting period once for
the variant, your work is considerably reduced.

02 Account type The opening and closing of posting periods by account type. OB52
This means that for a specific posting period, postings can be
permitted to customer accounts, but not to vendor accounts.
For each posting period that should be open, you must
always specify at least account type + (valid for all account
types). You can exercise more detailed control by specifying
further account types.
Using the minimum entry, when you enter the posting date in
the document header, the system checks whether the
posting period determined in the posting period variant can
be posted to. Thereafter, as soon as you enter an account
number, in a second step, the system checks whether the
posting period is permitted for the account specified.

Page 2 of 5
 Business Blue Print Document

03 Accounts The opening and closing of posting periods by account OB52

Interval intervals. This means that you only open a posting period for
posting to specific G/L accounts.
Account intervals are used exclusively with G/L accounts. If
you want to open sub ledger accounts, you have to enter the
corresponding reconciliation account and the account type
During the closing operations, you can use the reconciliation
accounts to close customer and vendor accounts before G/L
accounts, for example. Ex: this allows you to prevent further
postings to these accounts after you have confirmed the
balances with your customers and vendors.
04 Open and Open and closing posting periods in your fiscal year variants. OB52
Closing You can open and close these posting periods for posting. As
periods many periods as you require can be open for posting
simultaneously.
Usually, only the current posting period is open for posting,
all other posting periods are closed. At the end of this posting
period, the period is closed, and the next posting period is
opened.
Special periods can be open for closing postings during the
period-end closing.
Posting Period variant CPLA –
Separate posting period variants will be created for different
company codes.

05 Authorization Authorization group can be created for postings that can be SPRO
group for made by selected users in special period.
Special
Period

Page 3 of 5
 Business Blue Print Document

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
02

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

Page 4 of 5
 Business Blue Print Document

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.)

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 5 of 5