You are on page 1of 7

Change Request

Developing IFRS Footnotes

Change Request # 01

Document Revision

Ver # Release Notes Author(s) Issue Date

0.1 Initial draft for discussion Adnan Malik 25th Oct 2018
0.2
0.3

531657210.docx July 11, 2021 Page 1


Change Request

CONTENTS

CHANGE REQUEST DETAILS.............................................................. 3

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

CHANGE IMPACT ANALYSIS....................................................................... 6


DOCUMENT APPROVAL ...........................................................................7

531657210.docx July 11, 2021 Page 2


Change Request

CHANGE REQUEST DETAILS

Change Request (to be filled by the person requesting change)


Change Request Title Date Requested by

Developing IFRS Footnotes 21st Oct 2018 Adnan Malik

Description of Change Required (Include impacted objectives, deliverables or any new


objectives and deliverables)

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:

i. Development of IFRS Footnotes

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.

4. Scope of Work/Proposed Solution


There are basically two approach to deliver the solutions as suggested below.

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

531657210.docx July 11, 2021 Page 3


Change Request

and schedule

5. Benefits for ARASCO


i. Automation of full reporting cycle in the system.
ii. Full integrated data implies more reliability on reporting.
iii. IFRS Compliance, IFRS report set will be available at BPC system.

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

MDSap will develop the following listed NOTES


IFRS Description Y/N
NOTE 5 5.2  Equity reconciliations to IFRS (continued)
NOTE 6 6.1 Financial risk factors
NOTE 7 7. Segment information
NOTE 8 8. Property and equipment.
NOTE 10 10. Investments accounted for using the equity method
NOTE 11 11. Biological assets
NOTE 12 12. Financial assets and financial liabilities.
NOTE 13 13. Inventories
NOTE 14 14. Prepaid expenses and other receivables
NOTE 15 15. Accrued government subsidies
NOTE 16 16. SHARE CAPITAL
NOTE 17 17. Statutory reserve
NOTE 18 18. Contractual reserve
NOTE 19 19.Employee benefits obligation
NOTE 20 20. Borrowings
NOTE 21 21. Accruals and other liabilities
NOTE 22 22. Zakat
NOTE 23 23.  Related-party transactions
NOTE 24 24. Contingent liabilities and contingent assets
NOTE 25 25. Commitments
NOTE 26 26. Revenue

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;

i. Provide the correct data which has to be extracted (Mapping to be given)


ii. Provide dedicated resource(s) as one business user
i. Provide Audited IFRS 2018 Provide the correct data which has to be extracted
(Mapping to be given)

531657210.docx July 11, 2021 Page 4


Change Request

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.

531657210.docx July 11, 2021 Page 5


Change Request

CHANGE IMPACT ANALYSIS

Change Impact Analysis & Evaluation (To be filled by the person requesting the change & may
require supporting documents)

Reason for the Change (Business or Technical Justification)


New requirements for the project as an addition to the scope.

Priority Urgent
Impact Of Not Making This Changes
IFRS Compliance (BS & PL) reports will not be available at Consolidation.

Impact On Project Requirement: Out of Scope

If ‘In Scope’, describe impact

Impact On Project Risk: No

If ‘Yes, describe

Impact On Project Schedule: No


If ‘Yes, describe

If there is Impact on Schedule , Enter new Project End Date :


Impact on Project Budget Projection:

This development will requires 30 man-days: BPC Consultant for 30 Man/Days @ $ 950 USD (man-day) =
28,500 USD – payable at invoicing.

Impact on Scope of Work No

531657210.docx July 11, 2021 Page 6


Change Request

DOCUMENT APPROVAL

Originated By:
Role Name Signature Date

Project Manager- ARASCO Faisal AlJarboa

Project Manager- MDSap Adnan Malik


ARASCO Planning Manager
ARASCO CFO

Project Sponsor Approval


Name Signature Date

531657210.docx July 11, 2021 Page 7

You might also like