Eldorado Gold

SAP Continuous
Improvements:
ESTMA Data Collection

The better the question. The better the answer.

The better the world works.
1
 Agenda

1 Workshop Objectives

2 Process Area Overview & Leading Practice

3 Business Process Overview

4 Business Roles

5 Key Change Impacts

6 Next Steps

2
Workshop Objectives

1 Determine the end state business processes and business requirements

2 Validate process scenarios relevant for the business processes

3 Confirm Key Decision Points and Next Steps

4 Confirm security roles and key change impacts

3
Workshop Guiding Principles

1 EY will present the Best Practice flow and Leading Practices for the Process Area as a starting point

2 Eldorado will select workshop participants that can make key decisions for end state processes

3 Eldorado will actively participate to make sure business requirements, business scenarios and
integration points are accurately captured

4
Workshop Topic – Manage Pricing Structures – Week 1

# Workshop Topic Expected Workshop Outcomes

1 Chart of Accounts Management • Identify requirements and design components
• Review process flows
• Updated Solution backlog with user stories in all sites
2 Post FI Document

3 Print Journal Entry

4 Document Parking

5 Process G/L Recurring Document

6 Process Journal Entry Account Assginment Mode

5
L3 Business Definition and Scope

This workshop will cover the following Level 3 processes:

• Manage GL Accounts
• Process Journal Entry

This workshop will cover the following Level 4 processes:

– Chart of Account Management
– Post FI Document
– Print Journal Entry
– Document Parking
– Process G/L Recurring Document
– Process Journal Entry Account Assginment Mode

No further design workshop session is planned for the abowe L3 porcesses .

6
Key Design Decision Refresher

• Following Key Design Decisions were taken during the Analysis sessions: 
• 0L is leading ledger and it is IFRS ledger.
• There is only one parallel ledger and it is for statutory reporting.
• Turkish Uniform Chart of accounts list will be operating chart of accounts list. There will be only one new operating chart of accounts list
for all Tuprag Turkey company codes.
• CONN will remain as group chart of accounts list
• K4 Fiscal Year Variant (12 + 4 special period, 1st Jan-31 Dec) will be used
• A Tuprag Turkey specific FI document voucher will be printed, signden and archived for FI documnets
• Controlling area 3200 will be for all Tuprag Turkey Company codes
• Controlling are currency will be USD
• Document parking functionality will be used in some business transactions
• Recurring entry functionality will be used in some business processes
• Account assignment model functionality will be used in some business processes

7
Leading Practices/ Standard System Functionality

Company Code

The company code is the main organizational unit in financial accounting. Usually it represents a separate legal entity. For example, a
global pharmaceutical company may have a few different legal entities in the United States, which are registered as legally independent
companies: perhaps one that manufactures generic drugs, onethat is developing biotechnology medications, and one that is performing
testing for the pharmaceutical industry. It makes sense that each of these companies is set up as separate company code in SAP
S/4HANA. Then if those companies have a common parent company, it can be set up as a company in SAP. So normally there will be as
many company codes in the system as the organization has legal entities. The company code is the main unit for which a complete set of
financial statements can be generated. Every financial accounting document is posted per company code. Therefore, the company code
is the most fundamental organizational object in financial accounting and is very important to set up correctly to begin with.

8
Leading Practices/ Standard System Functionality

Company Code

Chart of Accts The chart of accounts defines the general ledger accounts
used and is maintained at a central (valid for all company codes) level and a
company code level.
Company Here you can enter the company to which the company code is
assigned. The company represents the parent legal entity for the company
code.
Credit Control Area This is used to perform credit management for the
company code. It manages the available credit limits for customers for the
company code.
Fiscal Year Variant This is the fiscal year variant used for this company code.
The fiscal year variant determines the periods and calendar assignments used
to post documents in financial accounting.
Pstng. period Variant The posting period variant in SAP determines which
periods are open and closed for postings. It provides a separate option to open
and close periods for various types of accounts (general ledger, customer,
vendor, assets, and so on). Here you specify the posting variant used for the
company code.
Field Status Variant The field status variant determines which fields are
required, optional, and suppressed when posting financial documents.
Inflation Method

9
Leading Practices/ Standard System Functionality

Chart of Accounts

The chart of accounts is a classification structure for the general ledger accounts used. There are three types of charts of accounts:

Operational chart of accounts The operational chart of accounts is the main chart of accounts, which is assigned to the company code.
It’s used to make postings in financial accounting.

Group chart of accounts The group chart of accounts links one or multiple operational general ledger account numbers to a group
account number. It’s used in the consolidation process.

Country chart of accounts This chart of accounts can be used on the country level to portray local requirements. It’s optional and can
be used for only some countries. When the country chart of accounts is assigned to the company code, you can assign an alternative
account number in the master record of the operational general ledger account.

10
Leading Practices/ Standard System Functionality

Chart of Accounts

Description The description of the chart of accounts, which should

indicate its use.

Maint. Language This is the main language under which the general
ledger accounts for the chart of accounts will be maintained. General
ledger accounts can have descriptions in other languages, but this is the
main language used in the country.

Length of G/L Account Number The length of the general ledger

account number. For example, a length of six would mean that account
numbers will be 100001, 100002, 100003, and so on. Commonly used
lengths are six or eight digits. Just make sure there are enough digits to
structure your accounts in logical account number ranges. For most
companies, six digits is enough.

Group Chart of Accts Here the operational chart of accounts is linked

with the group chart of accounts. Then in each account from the
operationa

11
Leading Practices/ Standard System Functionality

Chart of Accounts

Account Groups
Each account group is defined with an identifier entered in the Acct Group
column. In the From Acct and To Account columns the possible numbers
of the accounts are defined. From empty value to 999999 means that
accounts have to consist of numbers up to 999999. You can also define
more precise ranges, such as 100000 to 199999 for one group, 200000 to
299999 for another, and so on. It’s also possible to have accounts
consisting of letters, defined as ZZZZZZZZZZ.

12
Leading Practices/ Standard System Functionality

Ledger
A ledger is a central repository for accounting data.

Leading Ledger
You must designate one ledger as the leading ledger. In the standard system, the leading ledger is 0L. This ledger is updated in all company codes, that is, it's assigned to
all company codes.
 
Non Leading Ledger
Alongside the leading ledger, you can have other non-leading ledgers or extension ledgers. The non-leading ledgers are parallel ledgers to the leading ledger. They can be
based on a local accounting principle, for example. 

13
Leading Practices/ Standard System Functionality

Document Types

Document types in SAP serve to classify the various transactions posted in financial accounting. Each financial accounting document is assigned a document type, such
as vendor invoice, customer invoice, asset posting, and so on. The document types determine the numbers assigned to the documents, as well as many other important
configuration parameters, which we’ll now examine in detail..

. 

14
 Business Process Overview
FI General Settings
- There will be one controlling area for TR company codes (Controlling Area 3200).
- Controlling area currency is USD
- Kisladag, Ankara, Efemcukuru, Tarim, Export, Madalyon, SHK and Gayrimenkul company codes will be created
- Leading ledger (0L) is IFRS ledger, second ledger (Z1) is Statutory ledger
- All TR company codes have K4 fiscal year variant (12+4 Periods, 1st Jan-31st Dec) in all ledgers.
- Company code currency is 10 TRY for TR company codes.
- Second parallel currency is 30 USD. Exchange rate type M, real time conversion with Turkish central bank rate on translation
date.
- Document splitting will be activated on profit center level.

15
 Business Process Overview
Company Code

Company Field Status Operational Chart Posting Period Inflation Creditt

Description Company FM Area
Code Variant of Accounts List Variant Method Control Area
3201 Tuprag Metal AS 3201 Z032 0032 3201 TR01 #N/A #N/A
3202 Kisladag 3202 Z032 0032 3202 TR01 #N/A #N/A
3203 Efemcukuru 3203 Z032 0032 3203 TR01 #N/A #N/A
3204 Tuprag Tarim 3204 Z032 0032 3204 TR01 #N/A #N/A
3205 Tuprag Export 3205 Z032 0032 3205 TR01 #N/A #N/A
3206 Madalyon AS 3206 Z032 0032 3206 TR01 #N/A #N/A
3207 SHK AS 3207 Z032 0032 3207 TR01 #N/A #N/A
3208 Tuprag Gayrimenkul 3208 Z032 0032 3208 TR01 #N/A #N/A

All TR company codes will have same field status variant (the code may be ‘Z032’ area code of TR)
All TR company codes will use same operational CoA. Canada’s CoA is ‘0010’ The code of TR CoA can be ‘0032’.
Every company code will have its owen posting period variant.
Inflation accounting will be active for TR company codes and TR01 will be inf. Method for all company codes.
FM area and credit control area will be empty

16
 Business Process Overview
Chart of Accounts List
TR Chart of Accounts list code can be ‘0090’
Length of Group
Chart of
Accounts Description
Maintenance G/L Chart of Length is 8
Language Account Accounts
List Maintenance language is TR
Number List
Group chart of accounts list is CONN??
0032 Tuprag Turkey Chart Of Accounts List TR 8 GCOA
GCOA Eldorado Group CoA TR 5 

CoA Acc Group Description Nr From NR To Account groups

0090 10 Dönen Varlıklar 10000000 19999999
0090 20 Duran Varlıklar 20000000 29999999 GL Account groups have been defined in parallel to TR accounting principles and TR
0090 30 Kısa Vadeli Borçlar 30000000 39999999 financial statement nodes.
0090 40 Uzun Vadeli Borçlar 40000000 49999999
0090 50 Özkaynaklar 50000000 59999999
0090 60 Gelir Tablosu Hesapları 60000000 69999999
0090 70 Departman Gider Hesapları 70000000 79999999
0090 80 Serbest Hesaplar 80000000 89999999
0090 90 Nazım Hesaplar 90000000 99999999

17
Manage GL Accounts

R-1-1-1 Manage GL Accounts

START
Requester

1. Prepare create/update
request and submit it for
approval

3. Request additional
information
Yes
Approver

7. Validate data in the

END
system

Any additional
2. Review the request
information needed?

No
MDM Analyst*

4. Create/Change GL Does it require SAP 6. Send out confirmation

Account in the system Configuration update?
No email to validate data

*This activity will be performed by the requester/requester¶s team if MDM Analyst is not available
Yes
SAP Analyst

5. Update SAP
Configuration

18
Process Journal Entry

R-1-1-2 Process Journal Entry

START

1. Gather Supporting 4. Reopen Parked

Documentation Document Yes
GL Accountant

(FBV2)

JE Document 10. Delete Parked

needs to be No Document
fixed? (FBV0)
2. Enter Journal
Entry (JE) 5. Attach
Document in SAP Supporting
(FV50/ Documentation if
ZFI_DOCUMENT_P needed or update
ARK) the document

3. Save Document 6. Save Parked

as Parked Document as
(Document Park or Completed
F8) (FBV2)
GL Approving Manager

9. Contact GL
No
Accountant to Fix
7. Manager Checks
completed Is JE accurate to
document Approve? END
FBV0

8. Approve and Post

Yes JE Document
(FBV0)

19
Process Manage Requisitions
User L3 Business Priority User Story Title User Story
Story ID Process
1 Medium

20
Integration Points

# Integration point Team(s) Integration Point Description

1 No Integration

21
Change Impacts

L3 Business Change Current State Future State Impacted Change Change

Process Impact Stakeholders Impact Impact
Category Severity
(Process, (Low,
People, Tech, Medium,
Org. High)
Structure)

1 In current state There will be one All Process Medium

all company single chart of
Manage GL codes have its accounts list
Accounts own chart of assigned to all TR
accounts list. company codes

22
Review and Update Business Roles

# Business Role Description

1 Demand Unit Manager Demand Unit Manager will approve purchase requisitions.

23
Key Next Steps

24
Parking Lot Items

25
User to Business Role Mapping

• This is hierarchy of user access:

User John Smith

Demand Unit
Job Role Manager

Approve
Task Roles PRs

Transaction
Fiori – My Approve
Mass
Approve
Inbox PRs ME54N
Codes PRs ME55N

26