Professional Documents
Culture Documents
Change Request # 01
Document Revision
0.1 Initial draft for discussion Adnan Malik 25th Oct 2018
0.2
0.3
CONTENTS
1. EXECUTIVE SUMMARY.......................................................................3
2. CURRENT SITUATION..........................................................................3
3. REQUIREMENTS...................................................................................3
4. SCOPE OF WORK/PROPOSED SOLUTION.............................................3
5. BENEFITS FOR ARASCO....................................................................4
6. MDSAP’S RESPONSIBILITIES..............................................................4
7. CUSTOMER RESPONSIBILITIES............................................................4
8. PROPOSAL ASSUMPTIONS...................................................................5
1. Executive Summary
This Change Request comes as a response to ARASCO’s requirements during
Realization stage of BPC Project where we revised business requirements, this change
request will serve the following objectives:
2. Current Situation
ARASCO will not be able to view footnotes once BPC is live. They will be able to view
the Consolidate Balance sheet and Profit and Loss Account but without footnotes.
3. Requirements
To develop IFRS Notes so that the Footnotes will be available for Arasco’s usage for
statutory and management reporting purposes.
1. Manual Process; Input Templates will be provided for each note. The user has
to punch the data accordingly.
2. Automation Process; There is no user intervention based on the data
availability and mapping data will populate automatically.
As per the current business system situation, since there is no proper mapping
information available in the source system (i.e. Data is available but unable to capture
the way BPC / BW is required), MDSap preference will be to go with option 1, which
will provide maximum benefit to the project and enable us to put our experience to
ARASCO’s benefit.
This change request will emphasize this option and provide impact on project cost
and schedule
6. MDSap’s Responsibilities
MDSap will develop and test this functionality in the Development System (PCD), upon the
satisfied results the programs will be transported to Production System through QAE landscape
as usual
7. Customer Responsibilities
Customer has to assign a contact person(s); who has IFRS & SAP FI/CO knowledge for any
clarifications and testing in the QA system when required by the consultants. After transporting
the programs into Production System it is customers’ responsibility to execute these process. In
addition customer is also responsible for/to;
ii. Customer has to provide the source of each notes ( foot notes )
iii. If the source is ECC system, business has to do the necessary configuration set ups
at the ECC side in order to automate the Fixed assets movements (transaction types
in ECC FI ) schedules (Notes, Ex. Note 8 and 9)
iv. The content of every note has to be properly identified in the source with unique
tracking code according to the business process. If any case business has to fails to
track unique identification while making the positing at the ECC side, In the BPC
side manually post in the input template.
v. In every Note, Business has to provide the proper mapping information against to
each line item of the note content. Ex: Whether it may be GL Code / Transaction
Type / movement type /
vi. Unless there is proper mapping provided by the business, BPC system con not make
the system automate. ( Exceptional clause where there is a business process issue
to unable to provide in the system level will make it manual for those notes)
vii. According to the field availability, necessary settings will be done at BPC side as well
as BW side. If any filed need to be activated based on the requirement, the BW
team should be activate required filed in the table level to fetch the data.
viii. Business has to confirm and finalize the audited certified notes list to BPC Team. At
the same time if any listed notes are not required or not in the part of the business
scope should be mentioned clearly by the business.
8. Proposal Assumptions
i. For the data which is not yet available in the ECC system will be entered into BPC
manually
ii. Required data such as Trade Partner and Movement details are ready and available
in the system (In a nutshell, the data available in SAP ECC should be moved to BPC
automatically and data which is not available is subject to manual data entry in
BPC)
iii. All uploading will have to loaded the data manually or through flat file interface
where mapping is done as been done in BPC.
Change Impact Analysis & Evaluation (To be filled by the person requesting the change & may
require supporting documents)
Priority Urgent
Impact Of Not Making This Changes
IFRS Compliance (BS & PL) reports will not be available at Consolidation.
If ‘Yes, describe
This development will requires 30 man-days: BPC Consultant for 30 Man/Days @ $ 950 USD (man-day) =
28,500 USD – payable at invoicing.
DOCUMENT APPROVAL
Originated By:
Role Name Signature Date