122clegrfinug February 2016

Oracle® EMEA Add-on Localizations
Financials User Guide for Greece

Release 12.2
Part No. E49770-01
February 2016
Oracle EMEA Add-on Localizations Financials User Guide for Greece, Release 12.2
Part No. E49770-01
Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved.
Primary Author: Shanmugapriya Chandrakumar, Vijaya Gosala, Venkat Subramony and Priyanka Malhotra
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of
their respective owners.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of
the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable
Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication,
disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the
applicable Government contract, and, to the extent applicable by the terms of the Government contract, the
additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle
USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It
is not developed or intended for use in any inherently dangerous applications, including applications that may
create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be
responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.
Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or
hardware in dangerous applications.
This software and documentation may provide access to or information on content, products and services from
third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third party content, products and services. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third
party content, products or services.
Contents
Send Us Your Comments
Preface
1 Add-on Localizations Overview

Greek Add-on Localizations ................................................................................................................ 1-1
Components ............................................................................................................................................1-1
Solution Overview ................................................................................................................................ 1-2
2 General Setup
Assignment of Concurrent Programs/Concurrent Program Sets to Request Groups .................. 2-1
Functions to Menus............................................................................................................................... 2-2
Global Descriptive Flexfields.............................................................................................................. 2-5
Localization Descriptive Flexfields .................................................................................................... 2-6
Form Personalizations .......................................................................................................................... 2-7
OA Page Personalizations .................................................................................................................... 2-8
3 Statutory Trial Balance File

Requirement .......................................................................................................................................... 3-1
Report Output ........................................................................................................................................3-2
Setup Steps ............................................................................................................................................ 3-2
Functionality ...........................................................................................................................................3-3
Prerequisites .......................................................................................................................................... 3-7
User Procedure .......................................................................................................................................3-7
How to Launch the Report ................................................................................................................... 3-7
iii
Report Parameters ................................................................................................................................ 3-8
File Description ..................................................................................................................................... 3-9
Column Description ............................................................................................................................. 3-9
Limitations ............................................................................................................................................. 3-9
4 VAT- Greek Tax Audit Report

Requirement........................................................................................................................................... 4-1
Solution Overview ............................................................................................................................... 4-1
Report Output ........................................................................................................................................ 4-2
Setup Steps ............................................................................................................................................. 4-3
Functionality .......................................................................................................................................... 4-4
Prerequisites........................................................................................................................................... 4-5
User Procedure....................................................................................................................................... 4-6
Report Headings .................................................................................................................................... 4-8
Column Headings ................................................................................................................................. 4-9
Limitations ........................................................................................................................................... 4-12
5 Trial Balance with Unposted Transactions

Requirement........................................................................................................................................... 5-1
Report Output ........................................................................................................................................ 5-2
Setup Steps ............................................................................................................................................. 5-3
Functionality .......................................................................................................................................... 5-4
Prerequisites........................................................................................................................................... 5-5
User Procedure....................................................................................................................................... 5-5
Report Headings .................................................................................................................................... 5-7
Column Headings ................................................................................................................................. 5-8
Limitations ............................................................................................................................................. 5-9
6 Greek Bills Receivables Receipt Report

Requirement........................................................................................................................................... 6-1
Report Output ........................................................................................................................................ 6-2
Setup Steps ............................................................................................................................................. 6-2
Functionality .......................................................................................................................................... 6-3
Prerequisites........................................................................................................................................... 6-4
User Procedure....................................................................................................................................... 6-4
iv
Report Parameters ................................................................................................................................. 6-4
Report Headings ................................................................................................................................... 6-6
Column Headings ..................................................................................................................................6-6
Limitations ............................................................................................................................................. 6-7
7 Greek Withholding Tax Letter

Requirement .......................................................................................................................................... 7-1
Report Output ........................................................................................................................................7-2
Setup Steps ............................................................................................................................................ 7-4
Functionality ...........................................................................................................................................7-5
Prerequisites .......................................................................................................................................... 7-7
User Procedure .......................................................................................................................................7-8
Report Parameters ................................................................................................................................. 7-8
Report Headings ................................................................................................................................. 7-10
Column Headings ............................................................................................................................... 7-10
Limitations ........................................................................................................................................... 7-13
8 Turnover Reporting
Requirement .......................................................................................................................................... 8-1
Generic Setup Steps.............................................................................................................................. .8-2
Report Output from Fiscal Year 2014 ............................................................................................... ..8-18
Setup of Exchange Rates ................................................................................................................... ..8-20
Setup of Expense Report Functionality ............................................................................................ ..8-22
Setup of Global Descriptive Flefields .............................................................................................. ..8-25
Setup of Relative Value-Sets .............................................................................................................. ..8-32
Functionality from Fiscal Year 2014 ................................................................................................. ..8-37
User procedure from Fiscal Year 2014 ............................................................................................ ..8-41
CLE MYF Output Page 2013, Errors & Warnings ........................................................................... ..8-42
9 AP/AR Guarantee Processing

Requirement .......................................................................................................................................... 9-1
Report Output ........................................................................................................................................9-2
Prerequisites .......................................................................................................................................... 9-2
Solution Components ............................................................................................................................ 9-3
v
CLE: Letters of Guarantee Types Form .............................................................................................. 9-3
CLE: Letters of Guarantee Master File ............................................................................................... 9-7
CLE: Letters of Guarantee Transaction Form ...................................................................................9-11
CLE: Letters of Guarantee Inquiry Form ......................................................................................... 9-16
CLE: Letters of Guarantee Analytical Report .................................................................................. 9-20
10 GENERAL GL JOURNAL
Solution Overview .............................................................................................................................. 10-1
Output ................................................................................................................................................... 10-2
Setup Steps ......................................................................................................................................... 10-2
Functionality ........................................................................................................................................ 10-3
User Procedure .................................................................................................................................... 10-6
Report Parameters .............................................................................................................................. 10-9
Report Headings .................................................................................................................................. 10-12
Column Headings ............................................................................................................................... 10-13
Limitations ........................................................................................................................................... 10-14
Index
vi
Send Us Your Comments
Oracle EMEA Add-on Localizations Financials User Guide for Greece, Release 12.2
Part No. E49770-01
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?

• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and the
chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com

Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
vii
Preface
Intended Audience
Welcome to Release 12.2 of the Oracle EMEA Add-on Localizations Financials User Guide for
Greece.
This guide is a source of information about requirements of Greek Add-on Localizations
and is designed to provide useful guidance and assistance to:
• Consultants implementing Greek Add-on Localizations components for R12.2
Oracle E-Business Suite
• Users of Oracle E-Business Suite
This user guide includes information to help you understand the following aspects of the
Add-on Localization and to implement the Add-on Localization effectively:
• Overview
• Process Flow
• Functionality
• Prerequisites
• Setup
The Greece Add-on Localizations user guide assumes that you have good
understanding of core modules and the country specific localization requirement. If you
have never used Oracle e-Business Suite, we suggest you to attend one or more Oracle
Financials training classes available through Oracle University.
About this Add-on Localizations Manual

This Financials User Guide includes information you need to use Greek Add-on
ix
Localizations functionality effectively. It is organized for easy access to detailed
information about each of the following features:
• Greek Statutory Trial Balance File
• Greek Tax Audit Report
• Greek Trial Balance with Unposted Transactions
• Greek Bills Receivables Receipt Report
• Greek Withholding Tax Letter Report
• Greek Turnover Reporting
• Letters of Guarantee
• Greek General GL Journal
This manual is to be referred in conjunction with user guides of the respective modules for
Oracle E-Business Suite R12.2.
Installation
This Add-on Localizations is installed after the base install of Oracle e-Business Suite.
The Greece Add-on Localizations patch to be applied is available for download from
MyOracle Support (Doc ID: 438527.1). Please ensure the prerequisites are taken care
before installing the patch, especially the product splicing for CLE (Add-on
Localizations). Once the patches are installed, please ensure that the Post-installation
steps are completed. These patches create Add-on Localizations Descriptive Flexfield
definitions to store the additional information. You should not modify these forms at
any time. You need to fill the required values in the Descriptive Flexfields. The
Descriptive Flexfields specified in this manual can be accessed by additional Menu
extension on related forms.
See Related Information Sources on page xi for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/
Structure
1 Add-on Localizations Overview
2 General Setup
3 Statutory Trial Balance File
x
4 VAT- Greek Tax Audit Report
5 Trial Balance with Unposted Transactions
6 Greek Bills Receivables Receipt Report
7 Greek Withholding Tax Letter
8 Turnover Reporting
9 AP/AR Guarantee Processing
10 GENERAL GL JOURNAL
Related Information Sources

This guide contains references to the following Oracle publications. Use the Release 12.2
versions of these guides, unless otherwise specified:
• Oracle General Ledger User Guide, Release 12.2
• Oracle E-Business Tax User Guide, Release 12.2
• Oracle Payables User Guide, Release 12.2
• Oracle Receivables User Guide, Release 12.2
• Oracle Financials for Europe User Guide, Release 12.2
Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the E-Business Suite. As your
instance is patched, the repository is automatically updated with content appropriate for
the precise revisions of interfaces in your environment.
Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle E-Business Suite data
unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of
your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an
Oracle E-Business Suite form can update many tables at once. But when you modify
xi
Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you
may change a row in one table without making corresponding changes in related tables.
If your tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite
automatically checks that your changes are valid. Oracle E-Business Suite also keeps
track of who changes information. If you enter information into database tables using
database tools, you may store invalid information. You also lose the ability to track who
has changed your information because SQL*Plus and other database tools do not keep a
record of changes.
xii
1
Add-on Localizations Overview
Greek Add-on Localizations

Oracle® Add-on Localizations for Greece provides additional functionalities for Oracle E-
Business Suite to help customers meet legal and common business requirements. This user
guide provides details about setups and functionalities of the following features, forms,
reports and programs:
Components
Serial Number Feature Components
1 CLE: Greek Statutory Trial Balance File
2 CLE: Greek Tax Audit Report
3 CLE: Greek Trial Balance with Unposted Transactions Report
4 CLE: Greek Bills Receivables Receipt Report
5 CLE: Greek Withholding Tax Letter Report
6 CLE: Greek Turnover Reporting
7 CLE: Letters of Guarantee
8 CLE: General GL Journal
Add-on Localizations Overview 1-1

Solution Overview
1. Greek Statutory Trial Balance File

The Greek Statutory Trial Balance report/file is run for each company with a specific
VAT registration number. The report displays only actual balances. Budgeted and
encumbrance balances are not included. The report displays balances without year-end
closing entries and optionally includes beginning balances. Whenever the report is
requested for a balancing segment, the output is created for the balancing
segment/company mapped with a VAT number. If the report is requested without
balancing segment, then the output is created for all balancing segments/companies with
their respective VAT numbers summarized by natural account.
2. Greek Tax Audit Report

Greek Tax Audit Report is used by companies to report to the Greek tax authorities all
the incoming and outgoing tax balances along with the Tax Codes and Tax Accounts.
The report displays the incoming and outgoing tax balances with tax codes, account
code, debit/credit amounts of the transactions and descriptions. The report gives details
about the transactions in Accounts Payables and Accounts Receivables, which are
posted to General Ledger, and specific only to those GL Accounts, which have tax codes
belonging to Greece VAT type and also reported to the Greece tax authority. The report
displays calculated tax, real tax, and also the variance between the calculated and real
tax. It also displays totals of the transactions and tax code amounts.
3. Greek Trial Balance with Unposted Transactions

This Trial Balance displays both posted and unposted journals. The Carry forward
balances from the previous year, previous period balances and the current period
balances for the specific General Ledger data access set are displayed in the report for the
respective accounts. All parent account levels for the respective account codes entered in
the journal are displayed in the report.
4. Greek Bills Receivable Receipt Report

The solution serves as a Receipt or delivery note for all the Bills Receivables given by a
customer on a particular date in order to settle the account. The report produces a
sequence number each time when the report is run. This Header Sequence Number or
PIN Number groups together the Bills Receivables with respect to the particular
customer. The output file contains the customer's address data, due date, transaction
type, transaction number, drawee bank of the Bills Receivable, Bills Receivable amount
and total amount. Only the Bills Receivables with the status of "Pending Remittance"
are displayed in the report.
1-2 Oracle EMEA Add-on Localizations Financials User Guide for Greece
5. Greek Withholding Tax Letter
The withholding tax letter is run to provide the details of the tax withheld against
invoices for a supplier, along with the details of the invoices subject to withholding tax,
which are applied to both partially and fully paid invoices during the calendar year.
Prior to running the Greek withholding tax letter, the user needs to run the "AP
Withholding Tax Extract" request to select the data. The details of fiscal company, VAT
number, tax office, tax Area, company activity, and register number are extracted from the
legal entity profiles. However, the tax file number and electronic file number are obtained
from a Localization Descriptive Flexfield set at the legal entity level. The legal entity
represents the fiscal company.
6. Greek Turnover Reporting

MYF (Customer/Supplier Turnover Report) is a Greek statutory requirement. It
provides summarized information on the turnover of customers and suppliers during a
calendar year. The report must be submitted annually to the Greek tax authorities. The
report should categorize customers and the suppliers by the AFM (Tax registration
number).
Apart from the turnover amounts, specific identification information must be included for
each customer/supplier. This consists of the AFM (Tax Registration Number),
Profession and HQ address. Some information must also be included about the
reporting legal entity.
These requirements are satisfied by

Set up Global Descriptive Flexfields
• CLE: MYF setup OAF page
• CLE: MYF output Page
• CLE: Process MYF Concurrent Request
Output generated as Text files in a fixed formats:

• Supplier /customer List Positive Balances - File Format Report (IL01 file)
• Supplier /customer List Negative Balances - File Format Report (IL01.PIS file)
7. Letters of Guarantee Solution

This is a solution to capture, maintain and follow up the status of the guarantee letter
and also to create the respective accounting entry. It supports viewing and running
reports about Guarantee letters received and issued by the company. A guarantee letter
can be for a defined period with a specific expiration date or can be without any
expiration date. This information is captured in the Guarantee Letter Master File.
Add-on Localizations Overview 1-3

8. General GL Journal
The solution consists of a report for the journals to be displayed on the basis of
Reporting Sequence names for each period, and also for the Third party information to
be displayed. In the existing solution, the carried forwarded balances to normal periods
(non-adjustment) periods, are working fine, whereas for Adjustment periods they are
not working. Hence, an enhancement on the existing Global Journals and Third Party
Report (Daily journal book report) is required, which should show the carried forward
balances for the adjustment periods (year opening/closing), and also should include
Year to Date Carried Forward Balances by the REPORTING SEQUENCE NAME.
2
General Setup
Assignment of Concurrent Programs/Concurrent Program Sets to Request

Groups
Request Group setup provides access to the Concurrent Program/Concurrent Program
Set to the user responsibilities. Assign the following program/set to the request group
attached to the responsibility from which you want to access the functionality.
Reports
Program Name Oracle E-Business Suite
CLE: Greek Statutory Trial EMEA Add-on Localizations

Balance File
CLE: Greek Tax Audit Report EMEA Add-on Localizations
CLE: Greek Trial Balance with EMEA Add-on Localizations

Unposted Transactions
Report
CLE: Greek Bills Receivables EMEA Add-on Localizations

Receipt Report
CLE: Greek Withholding Tax EMEA Add-on Localizations

Letter Report
CLE: Greek Turnover EMEA Add-on Localizations

Reporting
General Setup 2-1

Program Name Oracle E-Business Suite
CLE: Letters of Guarantee EMEA Add-on Localizations
Request Set Definition

N/A
Functions to Menus
Add Functions to Menu

The user needs to add functions to menu manually.
Menu : AP_NAVIGATE_GUI12
Function: CLE Greece Turnover Reporting
Prompt: Greece Turnover Reporting
Function: 'JEGRLERAP - Supplier Turnover Exclusion Rules'

Prompt: Greek Localizations
Function: CLE: Guarantee Types
Prompt: CLE: Letters of Guarantee Types
Function: CLE: Guarantee Letters
Prompt: CLE: Guarantee Letters Master File
General Setup 2-3

Function: CLE: Guarantee Letters Transactions
Prompt: CLE: Guarantee Transactions
Function: CLE: Guarantee Letters Inquiry
Prompt: CLE: Guarantee Letters Inquiry
Global Descriptive Flexfields
The patch installs the following Global Descriptive Flexfields:
Application: Regional Localizations
DFF Name: JG_PO_VENDORS

Title: Required to Submit/Not
Context Code: JE JE.GR.APXVDMVD.SUPPLIER
Segment Name Displayed Required Valueset
(Y/N) (Y/N)
JE_GR_MYFREQ_YE Y N Yes_No
S_NO

DFF Name: JG_PO_VENDORS
Title: MYF Reportable
Context Code: JE JE.GR.APXVDMVD.SUPPLIER
General Setup 2-5

(Y/N) (Y/N)
JE_GR_MYFREP_YES Y N Yes_No
_NO

DFF Name: JG_HZ_CUST_ACCOUNTS
Title: Required to Submit/Not
Context Code: JE.GR.ARXCUDCI.CUSTOMER
(Y/N) (Y/N)
S_NO

DFF Name: JG_HZ_CUST_ACCOUNTS
Title: MYF Reportable

Context Code: JE.GR.ARXCUDCI.CUSTOMER
(Y/N) (Y/N)
S_NO
Localization Descriptive Flexfields

The patch installs the following Localization Descriptive Flexfields:
Application: EMEA Add-on Localizations

Localization DFF Name: CLE_RA_CUSTOMER_TRX_EXT
Localization Title: CLE: Additional Transaction Information
Context Code: GR.SEQUENCE
(Y/N) (Y/N)
CLE_SEQUENCE Y N AR_SRS_NULL_NU
M
Localization DFF Name: CLECLE_XLE_ENT_PRFLS_EXT

Localization Title: CLE: Additional Legal Entity Information
Context Code: GR
(Y/N) (Y/N)
CLE_TAXFILENUMB Y N None
ER
CLE_ELECTRONICFI Y N None
LENUMBER

Localization DFF Name: CLE_AP_SUPPLIER_SITES_EXT
Localization Title: CLE: Additional Supplier Sites Information

Context Code: GR
(Y/N) (Y/N)
CLE_VATREGISTRA Y N CLE_F289
TIONOFFICE _TAX_OFFICE
Form Personalizations
The patch installs the following Forms Personalizations:
General Setup 2-7

Form Form Name Block Function Name
Bills Receivables ARBRMAIN RMAI_HEADER CLE Localization DFF

Transactions Form
OA Page Personalizations
The OA Page Personalisations are handled automatically by patch:
OA Perso ID Com Destination Prompt View Instance

Page nalize ment URL
Name s
Legal Identi AddL Addit OA.jsp?OAFunc CLE GeneralUpdateVO

Entity ficatio egalD ional =CLE_F220_PG Additional
Mana n etails Legal &pExtendedPag Legal Entity
ger Infor Entity e=/oracle/apps/x Information
Updat matio Infor le/legalsystem/l
e page n matio egalentity/webu
n i/LegalEntity
DetailsPG&pLe
galEntityId={@L
egalEntityId}&p
EntityPartyId={
@PartyId}&retai
nAM=Y&pExte
ndedTable=
CLE_XLE_ENT
_PRFLS_EXT&p
ConnectString=
DFF_ID1={@Leg
alEntityId}&pC
ountry=COUNT
RY=fnd_
profile.value
('JGZZ_COUN
TRY_CODE')
OA Perso ID Com Destination Prompt View Instance
Page nalize ment URL
Name s
Tax ZxSu VatRe Vat OA.jsp?OAFunc CLE: MaintainSupAcctSitesV

Mana ppSite gistrat Regist =CLE_F220_PG Additional O
gers TaxD ionOff ration &pExtendedPag Tax
Third etTabl ice Office e=/oracle/apps/z Information
Party eRN x/taxcontent/reg
Site istration/webui/
Updat ZxPartyTaxP
e page rofilesUpdateP
G&retainAM=Y
&pExtendedTab
le=CLE_AP_SU
PPLIER_SITES_
EXT&pConnect
String=DFF_
ID1={@VendorSi
teId}&pCountry
=COUNTRY=fn
d_profile.value('
JGZZ_COUNT
RY_CODE')
General Setup 2-9

3
Statutory Trial Balance File
Requirement
According to Greece Statutory requirements, the Statutory Trial Balance file must be
submitted to the tax authorities annually. The Statutory Trial Balance report needs to be
submitted to the tax authorities within nine months from the completion the fiscal year.
The report is to be produced for each company (one legal entity, one VAT registration
number) once a year.
Solution Overview
The Greek Statutory Trial Balance report/file is run for each company with a specific
VAT registration number. The report displays only actual balances. Budgeted and
encumbrance balances are not included. The report displays balances without year-end
closing entries and optionally includes beginning balances. Whenever the report is
requested for a balancing segment, the output is created for the balancing
segment/company mapped with a VAT number. But, if the report is requested without
balancing segment, then the output is created for all balancing segments/companies with
their respective VAT numbers summarized by natural account.
Statutory Trial Balance File 3-1

Report Output
Setup Steps
The following table lists the setup steps and reference to their location within Oracle E-
Business Suite. After you log on to Oracle E-Business Suite, complete these steps to
implement Greek Statutory Trial Balance File.
Note: The sequence indicated for the setup checklist applies only to the
relevant steps to be considered in implementing the Greek Statutory
Trial Balance File. For each module installed, consult the manuals for
that particular module to determine the sequence of setup steps.
Step Number Setup Step Step Type Oracle E-Business

Suite
1 Apply Greece Add-on Required System Administrator

Localization Patch
Suite
2 Assign the CLE: Required System Administrator

Greek Statutory Trial
Balance File to the
corresponding
request group of the
responsibility from
which the report
needs to be run.
Functionality
• The primary functionality of the report is to display the accounts defined in the
Greek Chart of Books (COB) for which balances exist along with the respective
parent level accounts.
• Accounts included in the Trial Balance are accounts with 1,2,3 and 4 (optional)
levels.
The balances of the accounts represented in the Trial Balance are grouped and
displayed as explained below:
Account Groups 1,3,4 and 5 Account sub-group 54 Account Groups 2,6,7 and 8
Only first and second level All account levels are All account levels are
accounts are included included included. 2 and 7 groups
optionally belong to the bank
sector and the report displays
the first three levels for these
accounts.

Account Groups 1,3,4 and 5 Account Groups 2,6,7,8, and 54
For example, a journal has been entered for For example, the journal is entered for the
the amount of 15000 for account code: 110000. account code: 54001900 and for account group
In this case, since the account with account 2. In this case, as the account belongs to the
code 110000 belongs to account group 1, only group 54, all the 4 levels of accounts are
parent accounts for the first and second level displayed. Hence, the first level parent
are displayed. So, the parent levels of TRB11 (TRB54), second level parent (TRB54.00), third
(First level) and TRB11.00 (Second level) are level parent (TRB54.00.19) and the fourth level
displayed. parent (TRB54.00.19.00) accounts are
displayed.
Rules defined for natural accounts according to requirements of Greek COB for
Statutory Trial Balance report:
Level 1 Level 2 Level 3 Level 4
Mandatory level, 2 Mandatory level, 4 Mandatory level, 6 Levels 4 and up are

digits fixed length digits fixed length digits fixed length not mandatory and
with predefined with predefined with predefined without predefined
values according to values according to values, could be a number of digits or
Greek COB Greek COB child account values
according to Greek
COB
Natural account example of the required structure according to Greek COB
Account 10000000 Account 100000 Account 1000 Account 10
Level 4 child Level 3 parent Level 2 parent Level 1 parent
Used in GL entries Group of 10000000 - Group of 100000 - Group of 1000 - 1099

10000099 carries total 100099 carries total carries total balances
balances of these balances of these of these accounts
accounts accounts
Natural Accounts (child Parent Level 3 Parent Level 2 Parent Level 1

level)
10000000 100000 1000 10
Natural Accounts (child Parent Level 3 Parent Level 2 Parent Level 1
level)
10000001 100000 1000 10
10000002 100000 1000 10
60000000 600000 6000 60
60000001 600000 6000 60
60000002 600000 6000 60
61000000 610000 6100 61
62300000 623000 6230 62
Groups/Levels of Accounts included in the Trial balance:
Group Subgroup Exception Included Level/Levels

Included
10(0) Yes First and Second

Account Levels
1 Yes First and Second

Account Levels
2 Bank Sector Yes All the Account

Levels

Account Levels

Account Levels
5 Subgroup 54 Yes First and Second

Account Levels
5 54 Yes All the Account

Levels

Group Subgroup Exception Included Level/Levels
Included
6 Yes All the Account

Levels
7 Bank Sector Yes All the Account

Levels
8 All the Account

Levels
9 No
HDR: Header section, which contains the VAT registration number and period. The "
Header" section is a single line in the file, but however in the case of reporting for
multiple VAT registration numbers then it will occur once for each VAT registration
number and date.
• VAT Registration Number: VAT Registration Number, which is assigned to the
legal entity/ company. Assigning the balancing segment to the legal entity does this.
Each legal entity is represented as a company and the balancing segment is mapped
to the ledger.
• Period: GL Period for which the CLE: Greek Statutory Trial Balance File is run.
TRB: Trial Balance section, which refers to the account balance and contains the account
code, account description, and account balances with positive and negative signs
respectively for debit and credit account balances.
Statutory Trial Balance Report consists of three columns. The first and the second
column show the account code, account description sorted firstly by account group
(ascending) and secondly by account level (ascending).
The account codes are sorted in the following order: 0 (10), 1, 2, and 3,4,5,6,7,8. The third
column includes the account balance with a negative sign for credit balances and
positive sign for debit balances.
This report displays only actual balances. Budgeted and encumbrance balances are not
included. The report displays balances without year-end closing entries and optionally
includes beginning balances. Hence, in order to not display year-end closing entries, the
report should be run for the last period before last adjusting period, which is used for
closing entries only.
Whenever the report is requested for a balancing segment, one output is created for the
balancing segment/VAT number. Whenever the report is requested without balancing
segment, one output is created for all balancing segments/VAT number summarized by
natural account. According to Greek Code of Books the Account segments for 1st, 2nd
and 3rd level are predefined and obligatory for all companies.
The grouping depends on the first character of the first level of the accounting segment
and the subgroup on the first two characters of the accounting segment.
The report displays all natural accounts from 01 to 89.
The report can be run for the secondary ledger as well and the account balances are
displayed in the currency associated with the secondary ledger.
Prerequisites
• The standard setups in General Ledger must exist.
• The Greek Accounting Flexfield Structure must be defined as per the requirements,
where the user defines the account codes as per the Greece Code of Books. The
Account segments for 1st, 2nd and 3rd level are predefined and mandatory for all
companies, and hence have to be defined. The Grouping depends on the first
character of the first level of the Accounting segment and the sub group on the first
two characters of the Accounting segment.
• The accounting calendar must be defined with 14 periods including two adjustment
periods, where the last adjustment period is the closing period.
• A VAT registration number must be created for the legal entity and balancing
segment, which is assigned to the legal entity.
User Procedure
Create some GL journals
• Refer to Oracle General Ledger User Guide to enter journals for certain accounts.
Post the Journals

• Refer to Oracle General Ledger User Guide to enter post the journals, which have
been created.
How to Launch the Report

Run CLE: Greek Statutory Trial Balance Report and File
• Navigate to Standard Request Submission From.
• Select "CLE: Greek Statutory Trial Balance File".

• Enter the parameters.
• Submit the Request.
Report Parameters
Serial Parameter Mandator Description
Number y
1 Ledger Name Yes Select the primary/secondary ledger from

LOV. Default is primary ledger, but user
may run this report for any ledger. The user
can also select the ledger from the ledger
sets.
2 Period Yes Select from LOV the period up to which the

report needs to be run. All "open", "closed",
and "future enterable" GL periods are
shown in the LOV.
3 Accounts From Yes Select the start account range from LOV.
Even if the user enters all the range of the
accounts, the accounts starting with 9 are
omitted.
4 Accounts To Yes Select the end accounts range from LOV.
5 Balancing Segment Yes Select the value for the balancing segment,
belonging to the legal entity, which has a
unique VAT registration number from LOV.
If more than one balancing segment has
same VAT number, then this report runs for
each balancing segment separately.
6 Currency Yes This report displays balances in functional

currency for the ledger selected. However,
the user can select any other currency also
in this parameter. All enabled currencies are
shown in this LOV.
In this case, the report will only display the

transactions entered in the selected
currency.
7 Zero Beginning of No If yes, then the accounts with beginning
Serial Parameter Mandator Description
Number y
year Balances balance as zero are printed in the report.
8 Account Delimiter Yes Dot is the default delimiter. Dot is used as

delimiter to separate the accounts level.
Note: To generate the e-text report

format, click on "Options" Button after
entering the parameters and change the
format of the report to E-Text and click
OK.
File Description
• VAT Number: VAT registration number, assigned to the legal entity and balancing
segment.
• Period: Period for which the CLE: Greek Statutory Trial Balance File is run.
Column Description
• Account Code: Account codes prefixed with TRB and segregated by accounts
delimiter (.). All levels of the accounts are also displayed in case of Account Groups
2,54,6,7, and 8.
• Account Description: The full description of the accounts.
• Amount (with positive or negative signs): The respective account balances are
displayed with positive sign for debit balance and negative sign for credit balances.
Limitations
• The report is specific to the Greek COB (Chart of Books), which contains different
levels and groups.
• The report is balancing segment specific, as only one unique VAT registration
number can be assigned to the balancing segment.

4
VAT- Greek Tax Audit Report
Requirement
Companies must submit a VAT report to tax authorities including all the incoming and
outgoing tax balances. The required information can be provided as a report with a
specific layout or uploaded through Tax Authority Network. Due date is the end of the
quarter for companies with A&B class Books of Records and monthly at the 20th of the
next month for companies with C class Books of Records.
Solution Overview
Greek Tax Audit Report is used by the companies to report to the Greek tax authorities
all the incoming and outgoing tax balances along with the Tax Codes and Tax Accounts.
The report displays the incoming and outgoing tax balances with tax codes, account
code, debit/credit amounts of the transactions and descriptions. The report gives details
about the transactions in Accounts Payables and Accounts Receivables, which are
posted to General Ledger, and specific only to those GL Accounts, which have tax codes
belonging to Greece VAT type and also reported to the Greece tax authority. The report
displays calculated tax, real tax, and also the variance between the calculated and real
tax. It also displays totals of the transactions and tax code amounts.
VAT- Greek Tax Audit Report 4-1

Report Output
Setup Steps
Business Suite. After you logon to Oracle E-Business Suite, complete these steps to
implement Greek Tax Audit Report.
relevant steps to be considered in implementing the Greek Tax Audit
Report. For each module installed, consult the manuals for that module to
determine the sequence of setup steps.

Suite

Localization Patch

Suite

Greek Tax Audit
Report to the
corresponding
Request Group of the
responsibility from
which the report
needs to be run.
Functionality
The primary functionality of the report is to display all incoming and outgoing tax
balances with tax codes and accounts. The report gives the details of the invoices in
Accounts Payables and Accounts Receivables for which tax codes are assigned.
The report displays calculated tax, Real Tax, and also the variance between the
calculated and real tax.
Real Tax refers to the manual over-ride of the calculated tax amount, which is on the
Invoice, by the user. To do this, enter the control amount for the 'Item Line' Type
against the invoice amount. Then, validate the invoice, create accounting for it and
transfer the entries to General Ledger.
Only accounted transactions from AP and AR, which have been transferred to GL and
posted, are displayed in the report. The manual GL journals, which are posted, will be
displayed as well.
The report layout differs based on the "Group By" and "Detailed" parameters.
The four layouts for the report are:

1. Detailed Transactions per Tax Code
2. Summary Transactions per Tax Code
3. Transaction by General Ledger Account (Detailed)
4. Transactions by General Ledger Account (Summary)
In the report layout detailed transactions per tax code, account totals and totals of tax
code are displayed.
Only tax code totals are displayed in case of summary transactions per tax code. The
totals are summarized according to tax codes.
The accounted invoices in AP and AR are displayed at both the tax code level and
account level (Both Detailed and Summary). Likewise, accounted invoices are displayed
both at tax code level and accounts level (Both Detailed and Summary) even for GL
manual journals, but the manual SLA journal entries, which are accounted and
transferred to General Ledger, are only displayed at the Account level, as no tax codes are
assigned to it (Both Detailed and Summary).
When accounted Invoices in AP and AR are transferred to General Ledger, the
accounting entries can either be posted or these can remain unposted. If the "Submitted to
GL" parameter is given as "All", then the report selects all journal entries including posted
and unposted. If it is given as "Posted", then only posted entries in General
Ledger are selected. Similarly, when the parameter is given as "Unposted", then only
Unposted Journals are considered from General Ledger.
In case of Accounts Payables invoices or Accounts Receivables invoices with multiple
invoice lines, if different tax rate codes are assigned to each line, then based on the tax
code assigned, the report segregates each line and displays all the four layouts at both
tax code level and account level. Hence, each line's details are displayed separately in
the report, sorted by tax codes and transaction date in descending order.
Manual subledger journal entries from Accounts Payables and Accounts Receivables
which are assigned the accounting class of 'Tax' for the tax account (VAT) are also
displayed in the report. These journals must be accounted and transferred to General
Ledger.
If the user enters a wrong period range in the "GL Start Date" and "GL End Date"
parameters, then the report displays "NO DATA FOUND".
The CLE: Format Greek Tax Audit report runs automatically, once the user submits the
Greek Tax Audit report for the type of output format selected.
Prerequisites
• The following profile options must be enabled and set to 'Yes'.
• eBTax: Allow Ad Hoc Tax Changes
• eBTax: Allow Manual Tax Lines
• eBTax: Allow Override of Tax Classification Code
• eBTax: Read/Write Access to GCO Data
• The concurrent program must be registered with the Application eBTax in

E-Business Suite Release 12.2.
• The standard setups in eBTax such as tax regime, taxes, tax rates, tax jurisdiction,
tax statuses, tax rules must exist. The tax codes must be made available for
transactions in the Subledger modules.
• If any of the prerequisites, which need to be completed before running the report, is
not done, then in that case the report does not display any data.

User Procedure
Create an Accounts Payables Invoice and assign Tax code
• Refer to Oracle Payables User Guide to create AP invoices and assign a tax rate code
to it.
Create an Accounts Receivables Invoice and assign Tax code

• Refer to Oracle Receivables User Guide to create an AR Invoice and assign tax rate
code to it. Once the invoice is completed, the calculated tax amount is displayed.
Create Manual Journal with Tax Rate Code

• Refer to Oracle General Ledger User Guide to create a manual General Ledger
Journal and assign tax code to it. The respective calculated tax line is created
automatically once the journal is saved.

Run CLE: Greek Tax Audit Report
• Navigate to Standard Request Submission From in Tax Managers responsibility.
• Select "CLE: Greek Tax Audit Report".
• Submit the request.
Report Parameters
Parameter Mandatory Description
Ledger Yes Select the Primary/Secondary Ledger from LOV,

which belongs to the data access set assigned.
Default is primary ledger, but user may run this
report for any ledger.
Group By Yes This parameter contains the list of values 'Tax' and
'Account'. No default value.
Detailed No This parameter contains the list of values 'Yes' and

'No'. This determines whether the report is
displayed at the Detailed or Summary level. No
default value. If the user leaves the parameter blank
then the Detailed report will be run.
When report runs at detailed level, both tax code

totals and account totals are displayed, but only tax
code totals are displayed for the transactions for
summary level.
GL Start Date Yes Enter the GL Start date for which the report needs to
run.
GL End Date Yes Enter the GL End date for which the report needs to
run.
From Tax Code No The LOV displays all the tax rate codes, which are
enabled. This depicts the start tax rate code from
which the report will run. If the user does not select
any value here, then the report will run for all tax rate
codes. No default value.
To Tax Code No The LOV displays all the tax rate codes, which are
enabled. The User selects the end tax rate code up
to, which the report needs to run. No default value.
When From and To Tax Code parameters are left

blank, then the report runs for all the tax codes.
Account Segment No The LOV displays the list of account codes. Here the
Low User selects the start account range for which the
report needs to run. No default value.
Account Segment No The LOV displays the list of account codes. Here the
High User selects the end account range up to which the
report needs to run. No default value.
Submitted to GL Yes The list of values displays 'All', 'Posted' and

'Unposted' values Here the User User selects the
posting status. The default value is 'Posted'.
Output Type Yes The list of values displays the 'RPT' and 'XLS' values
to determine whether the output is in report format

or excel. Default value is RPT.
Delimiter Yes There is only one default value (semicolon), which is

the delimiter displayed in the report.
The purpose of the delimiter is to segregate the

columns in Excel output.
Note: To run the report in the Excel format,

select the Output Type parameter as 'XLS'.
Report Headings
Report Title: Greek Tax Audit Report
Period: Period for which the CLE: Greek Tax Audit Report is run.
Sub-section report title: Specifies the layouts of the report which are:
1. Detailed Transactions per Tax Code

2. Summary Transactions per Tax Code
3. Transaction by General Ledger Account (Detailed)

4. Transactions by General Ledger Account (Summary)
Group By: Group by 'Tax' or 'Account' which is given as the parameter for the report.
Detail By: Detailed by set to 'Yes' or 'No', which determines whether the report is run at
the detail/summary level.
Period from: Start date for which the CLE: Greek Tax Audit Report is run.
Period to: End date for which the CLE: Greek Tax Audit Report is run.
Tax Code Range from: The From Tax Code entered at the parameter level, which
determines the tax code range for which the report runs.
Tax Code Range to: The To Tax Code entered at the parameter level, which determines
the tax code range up to which the report runs.
Account Range from: The General Ledger High Account range, given at the parameter
level for which the report runs, is displayed.
Account Range to: The General Ledger Low Account range, given at the parameter
level for which the report runs, is displayed.
Posting Status: Posting status of 'All', 'Posted', or 'Unposted', given at the parameter
level is displayed.
Output Type: Output format for the report whether Report format or Excel format.
Request Identifier: This is a part of the report information. This is an identification
number to identify the request.
User Name: The user name of the instance.
Responsibility: The responsibility from which the report is run.
Application: The application from which the report is run.
Time of Request: The time of the report submission.
Currency Code: The currency code for which the report is run (Ledger currency).
Printer: If a default printer is used for a print of the report.
Resubmission Interval: Any interval to the resubmission of the report.
Number of Copies: Number of copies of the report.

Print Style: The print style of the report.
Column Headings
Detailed Transactions per Tax Code
• Tax Code
• Tax Rate
• Tax code Description
• Account
• Description
• Date
• Invoice Number
• Invoice Description
• Debit
• Credit
• Amount
• Net Amount

• Calculated Tax
• Real Tax
• Difference between Calculated Tax and Real Tax
Summary Transactions per Tax Code

• Tax Code
• Tax Rate
• Tax code Description
• Account
• Description
• Debit
• Credit
• Amount
• Net Amount
• Calculated Tax
• Real Tax
• Difference between Calculated Tax and Real Tax
Transaction by General Ledger Account (Detailed)

• Invoice Type
• Invoice Number - The invoice or the journal number
• Day
• Month
• Year
• Account
• Tax Code
• Debit
• Credit
• Amount
• Description
Transaction by General Ledger Account (Summary):

• Invoice Type
• Invoice Number - The invoice or the journal number
• Day
• Month
• Year
• Account
• Tax Code
• Debit
• Credit
• Amount
• Description
When the report is submitted two requests are run:

• CLE: Greek Tax Audit Report
• CLE: Format Greek Tax Audit Report Output
When the User runs the CLE: Greek Tax Audit Report, the CLE: Format Greek Tax
Audit Report is automatically run, where the User can verify the output of the Report.
In case, the CLE: Greek Tax Audit report errors out, then the CLE: Format Greek Tax
Audit Report does not run.
The request "Format Greek Tax Audit Report" contains the required output.
Totals/Report Totals
• Totals by Tax Code are reported when group by is " Tax Code".
• Totals by Account are reported when group by is "Tax Code" and "Detailed" is Yes.

Limitations
• When the User runs the report for a specific GL Start Date and End Date, the
manual subledger Journal entries in both AP and AR, which fall within the GL
dates entered, will also be selected.
However, these Manual subledger journals cannot be run at the tax code level, but
only at the Account level. Hence this is one of the limitations.
• The User cannot enter real tax for a manual General Ledger Journal. Hence, the
report can't display the real tax value for any manual General Ledger Journal.
5
Trial Balance with Unposted Transactions
Requirement
The Greek Trial Balance with Unposted Transactions must be available on a daily and
routine basis whenever the tax authorities and auditors visit the company for auditing.
The report also provides a means for effective reconciliation.
Solution Overview
The Greek Trial Balance with Unposted Transactions gives the ability to print both
posted and unposted journals. The Carry forward balances from the previous year,
previous period balances and the current period balances for the specific General
Ledger data access set are displayed in the report for the respective accounts. All parent
account levels for the respective account codes entered in the journal are displayed in
the report.
Trial Balance with Unposted Transactions 5-1

Report Output
Setup Steps
implement Greek Trial Balance with Unposted Transactions.
relevant steps to be considered in implementing the Greek Trial
Balance with Unposted Transactions. For each module installed,
consult the manuals for that module to determine the sequence of setup
steps.

Suite
1 Apply Greece Add-on Prerequisite System Administrator

Localization Patch

Suite

Greek Trial Balance
with Unposted
Transactions to the
corresponding
responsibility from
which the report
needs to be run.
Functionality
• The Solution is a Trial balance displaying both Unposted and Posted journals.
• The beginning balances from the previous year, previous period balances and the
current period balances are displayed in the report for the respective accounts.
• All parent account levels for the respective account code, entered in the journal are
displayed in the report.
• The Total Debit must be balanced with the Total Credit column.
• When transactions in subledgers such as AP/AR are accounted and transferred to

General Ledger, the respective posted and unposted entries are displayed in the
report.
• The report can be run for any ledger, belonging to the data access set or ledger set
and it runs for the balancing segment (company) selected.
• It can also run for the balance types of Actual, budget or encumbrance.
• There can be a restriction, on the basis of posted / unposted journals. If there is no

restriction, then all journals will be displayed irrespective of posted or unposted.
• Sorting is by the account codes in the ascending order with the respective parent
account levels.
• The file format of the report does not include the totals of carried forward, brought
forward and the grand totals; these are available in the printed report format only.
• The totals of all the nine columns in the report, which are, [Beginning Balance debit,
Beginning Balance credit, Prior Period Activity debit and credit, the current period
debit and credit, the totals of debits and credits and the column for balance (debit -
credit)], are calculated and displayed in the report.
• The line at the end of the page with the page's total has the label "Carried Forward".
All the previous page totals are displayed in the next page with the label "Brought
Forward". This is shown at the beginning of each page, commencing from the
second page onwards. The entire report's totals are displayed at the end of the last
page under the label "Grand Totals".
Prerequisites
• The standard setups in General Ledger must exist.
• The profile options GL: Data Access Set and GL Ledger Name must be set by the
user at the responsibility level. The Ledger/ Data access set created is assigned to
this profile option. Hence, when the report is run for the particular ledger or data
access set.
• The Account Codes must be defined as per Greece Statutory Requirements. The
parent to child mapping and the four levels of accounts must exist.
User Procedure
• Create some GL journals and do not post them.
Refer to Oracle General Ledger User Guide to enter journals for certain accounts,
but leave them as unposted.
• Create some journals and post them.
Refer to Oracle General Ledger User Guide to create some journals for certain
accounts and post them.
• Run CLE: Greek Trial Balance with Unposted Transactions for the unposted and
posted journals.
• Select "CLE: Greek Trial Balance with Unposted Transactions".
Note: Click on "Options" Button after entering the parameters and change the
format of the report to Excel, HTML, PDF, or RTF. The default format is "PDF".

Report Parameters
Ledger/Ledger Set Yes Select the Ledger or the Ledger set for
which the report needs to run. Default is
primary ledger, but you may run this report
for any ledger belonging to the GL Data access
set or Ledger Set.
Balancing Segment Yes The list of values shows all the Balancing
segments with respect to the Chart of
accounts ID. The report runs for the
balancing segment (company) selected.
Accounts From Yes Select from the list of values the start
account from which the report needs to run.
Accounts To Yes Select from the list of values the end

account up to which the report needs to
run.
Fiscal Year Yes Select the fiscal year for which the report
needs to run. Report runs only for that
particular fiscal year.
GL Date From Yes Enter the GL date from which the report
starts running. The GL date is in
DD-MMM-YY format. The fiscal year
chosen and the GL date must be in sync. If
not, an error message is displayed.
GL Date To Yes Enter the GL Date up to which the report

can run. The GL date is in DD-MMM-YY
format.
Exclude period No Selects from list of values the period, which

is to be excluded in the report (generally in
case of closing period). The LOV contains all
GL periods including adjustment
periods and closed periods.
Exclude JE Source No Select the journal source, which is to be

excluded in the report.
Exclude JE Category No Select the journal category, which is to be

excluded in the report.
Currency No Select the currency for which the report

needs to run.
Balance Type Yes Select the balance type for which the report
needs to run.
Posting Status Yes Select the posting status of the journals,

which can be 'All', 'Posted', or 'Unposted'.
Balance Transferred Yes Select 'Yes' or 'No', which determines if

only the trial balance selects only the
journals whose balances, have been
transferred.
Hide Zero Balances Yes Select 'Yes' or 'No', which determines if the
accounts with zero balances, are to be
hidden or included.
Hide Untransacted Yes Select 'Yes' or 'No', which determines if the

Accounts accounts with no transactions are to be
hidden or included.
Account Delimiter Yes Enter any symbol (;,-,&,etc) and the report
displays that symbol as the delimiter.
Layout Yes Select either 'File' or 'Report' from the list of

values. The layout of "FILE" is without page
breaks, carried forward and brought
forward and report totals.
Report Headings
Headers section contents depends upon the chosen parameters:
Report Title: Greek Trial Balance with Unposted Transaction.
Ledger/Ledger Set: Ledger name, which is given in the parameter for which the report

runs.
Accounts: Accounts, which are included in the report based on the accounting range
High and Low entered by the user.
Company: Balancing segment for which the report runs, given by the user in the
parameter "Balancing Segment".
Fiscal Year: Fiscal year for which the report runs.

GL Dates: GL (From/To) dates mentioned by the user in the parameters. (Fiscal year
and GL dates must be in sync).
Exclude Period: Period, which is excluded usually referring to the period involving the
closing entries.
Exclude Category: Category, which is excluded usually referring to the period
involving the closing entries.
Exclude Source: Journal source to be excluded, entered by the user in the parameter "
Exclude Source".
Currency: Currency, which is selected by the user at the parameter level.
Balance Type: Actual, Budget, Encumbrance Balance types, whichever the user selected in
the parameter.
Posting Status: Posting status of the journals (Posted, Unposted or All), whichever the
user selects.
Balance Transferred: Whether balances are transferred to GL or not based on 'Yes' or
'No' selected by the user.
Hide Untransacted Accounts: When the value is selected as YES, accounts, which do
not have any transactions, are not shown.
Hide Zero Balance Accounts: When the value is selected as YES, accounts with no
transactions are not shown.
Account Delimiter: The chosen account level Delimiter (.) - default is full stop, which is at
the parameter level.
Layout: The chosen layout (File or Report).
Column Headings
Account: The codes of all accounts with transactions during the fiscal year, falling
within the GL From and To dates including accounts having amounts carried forward
from the previous year.
Description: The description of every account for which the report runs with
transactions during the fiscal year including accounts having amounts carried forward
Beginning Balance / Debit: The sum of debit amounts per account carried forward
Beginning Balance / Credit: The sum of credit amounts per account carried forward
Prior Period Activity/Debit: The sum of debit amounts per account from the beginning of
the fiscal year till the current period, excluding the current period amounts, but
including amounts carried forward from the previous year.
Prior Period Activity / Credit: The sum of credit amounts per account from the
beginning of the fiscal year till the current period, excluding the current periods
amounts, but including amounts carried forward from the previous year.
Period Activity / Debit: The sum of debit amounts per account concerning the current
period alone.
Period Activity / Credit: The sum of credit amounts per account concerning the current
period alone.
Year-To-Date Balance / Debit: The sum of debit amounts per account from the
beginning of the fiscal year till the end of the current period including the current
periods amounts and amounts carried forward from the previous year.
Year-To-Date Balance / Credit: The sum of credit amounts per account from the
beginning of the fiscal year till the end of the current period including the current
periods amounts and amounts carried forward from the previous year.
Net Balance [Debit - Credit]: Negative sign [Total Debit - Total Credit] is displayed for
credit balances.
TOTALS:
• The totals of all the nine columns in the report - [Brought forward debit, brought
forward credit, previous periods debit and credit, the current period debit and
credit, the totals of debits and credits and the column for balance (debit - credit)],
are calculated. The line at the end of the page with the page's total has the label "
Carried Forward".
• All the previous page totals are displayed in the next page with the label "Brought
Forward". This is shown at the beginning of each page, commencing from the
second page onwards.
Last Page Totals:
The entire report's totals are displayed at the end of the last page under the label "Grand
Totals".
Limitations
• This report only runs for a particular fiscal year.

• The Greek flexfield structure contains different account levels and groups. Unless
these account levels and groups are given by the user in the flexfield structure, the
report cannot be submitted. The report will error out in such a case.
6
Greek Bills Receivables Receipt Report
Requirement
When a Bills Receivable is given to the company by a customer as future dated
payment, a receipt must be printed and signed by both parties to prove that the
customer's payment is accepted and approved by the company. The report must
include all the Bills Receivables received by the customer on that particular day. The
receipt must include customer address and all Bills Receivables data. A sequence
number must be created and linked to each Bills Receivable for reference, which must be
printed initially and also whenever the report is reprinted.
Solution Overview
The solution serves as a Receipt or delivery note for all the Bills Receivables given by a
customer on a particular date in order to settle the account. The report produces a
sequence number each time when the report is run. This Header Sequence Number or
PIN Number groups together the Bills Receivables with respect to the particular
customer. The output file contains the customer's address data, due date, transaction
and total amount. Only the Bills Receivables with the status of "Pending Remittance"
are displayed in the report.
Greek Bills Receivables Receipt Report 6-1

Report Output
Setup Steps
Business Suite. After you log on to Oracle E-Business Suite, complete these steps to
implement Greek Bills Receivables Receipt Report.
relevant steps to be considered in implementing the Greek Bills
Receivables Receipt Report. For each module installed, consult the
manuals for that module to determine the sequence of setup steps.

Suite

Localization Patch

Greek Bills
Receivables Receipt
Report to the request
group associated with
the responsibility.
The Localization Descriptive Flexfield for CLE: Sequence Number for Bills Receivables is
enabled in the Bills Receivables Transactions form, wherein when the user runs the report,
the user has to return and query the Bills Receivable (BR) transaction, and click on Actions--
> CLE: Sequence number for Bills Receivables in order to view the sequence number for the
Bills Receivable transaction.
Functionality
The primary functionality of the report is to display the receipts for all the Bills
Receivables presented by the customer to settle his account, on a particular transaction
date. The report includes customer address and all the Bills Receivables information.
Only the Bills Receivables with status of "Pending Remittance" needs to be displayed in
the report.
A sequence number is created and linked to each Bills Receivable for reference. This
sequence must be printed initially and whenever the report is reprinted. The first time the
report is executed for the customer on a specific date the report produces a sequence
number for all the bills included. This Header Sequence Number or PIN Number
groups the Bills Receivables of that customer. In case the same customer delivers more Bills
Receivables later, but for the same date, then a new report with a new sequence is produced
which refers to the new set of Bills Receivable.
The report can be executed any number of times for the same customer and date, when he
delivered Bills Receivables as a payment to settle the account. When the user prints the
same report subsequently, he/she has to reprint it. If the user sets the parameter " Reprint"
to 'No' and tries to print the same report again, the report shows NO DATA. For the same
transaction date, if the user enters more transactions and prints the same report, then the
header sequence number becomes the next successive number to the header sequence
number previously printed.
The report heading includes the Fiscal company information (legal entity). The legal
entity details such as Company Activity and Address are taken from the legal entity
profiles. The output file contains the customer's address data, due date, transaction
and total amount of each report sequence number. "CLE: Sequence Number for Bills
Receivables" Localization Descriptive Flexfield is used in order to assign the Header
Sequence Number. The Localization Descriptive Flexfield is given in the Bills
Receivables Transaction form. Every time the report is run, the incremental (next
consecutive) number gets generated automatically and is stored in the Localization
Descriptive Flexfield. This Localization Descriptive Flexfield is not an enterable field,
but a display only field, which displays the Header Sequence Number, retrieved by the
report output.
The Report only runs for the functional currency. The report is run at customer site
level, and can run for multiple customer sites.

Prerequisites
• The standard setups in Accounts Receivables must exist.
• The Bills Receivables with respect to the particular customers must be created and
assigned to the corresponding customer transactions.
• The Localization Descriptive Flexfield for CLE: Sequence Number for Bills
Receivables must be enabled in the Bills Receivables Transactions form.
User Procedure
Create an AR transaction (invoice) and complete it
• Refer to Oracle Receivables User Guide to create AR transactions and complete

them.
Create a Bills Receivables transaction (with status "pending remittance")

• Refer to Oracle Receivables User Guide to create a Bills Receivable transaction and
assign an AR invoice to the Bills Receivable.

• Run CLE: Greek Bills Receivables Receipt Report from a Receivables responsibility.
• Navigate to Standard Request Submission form in Receivables Responsibility.
• Select "CLE: Greek Bills Receivables Receipt Report".
Note: To run the report in PDF format, select the parameter Output Type as 'PDF',
and then click on the Options button. In the Format LOV, select PDF, and then click
OK.
Report Parameters
Serial Parameter Mandatory Description
Number
1 Organization Yes Select the organization for which the

report needs to run. The organization
is the Operating Unit. The LOV
contains all the Operating Units as
per the MO: Security Profile set.
2 Legal Entity Yes Select the legal entity for which the
report needs to run. This parameter is
context based on the organization
chosen by the user. The legal entity
parameter is used to retrieve the
company name and VAT number on
the report header.
3 Customer Yes Select the customer's name for which

the report needs to run. List of
customer's names is displayed. No
default value. If the customer has
multiple sites, the report displays the
Bills Receivables for all the sites of
the customer and belonging to the
organization selected by the user at
the parameter level.
4 Transaction Date Yes Enter the Transaction date for which

the report needs to run. Report
displays all Bills Receivables, which
belongs to the particular customer
and the respective transaction dates.
5 Reprint Yes The List of values contains values

'Yes' and 'No'. The option of 'Reprint'
is available to the report, when the
report is already run for a customer
and transaction date. But, if the user
wants to run it once again, then the
Reprint parameter needs to be set to
'Yes', only then the report is printed,
otherwise no details is displayed in
the report.

Report Headings
Fiscal Company: Legal entity name.
Company activity: Legal entity - company activity.
Address: Address of the legal entity.
City Zip: Zip code of legal entity city.

VAT number: VAT registration number of the legal entity.
Tax Office: Issuing tax authority of the Legal entity.

Sequence Number: Header sequence number of the report for the Bills Receivables
transactions.
Report Title: Bills Receivables Delivery Note.
Customer Account: Account Number of the customer for which the Bills Receivables is
promised.
Customer Name: Customer name, which is the drawee of the Bills Receivables.
Customer Address (from the primary bill to site): Customer address, which is given in
the primary bill to site address, entered at the time the customer is created.
City: The city, which has been mentioned in the customer address (Bill to site address).
Customer VAT Registration Number: The VAT registration number, which has been
given under the Tax profile details if the customer to which the particular VAT
Registration number has been assigned.
Receipt Date: Date at which the Bills Receivables Delivery Note is being produced.
Column Headings
Line sequence (number): Line Sequence Number for the Bills Receivables pertaining to
the customer.
Maturity Date (date): Maturity/Expiration Date of the Bills Receivables.
Type: Transaction Type of the Bills Receivable is displayed.
Bills Receivable Number (char): Number of the respective Bills Receivable.
Drawee Bank (char): The respective Bank (remittance) of the drawee, on whom the
Bills Receivables is drawn.
Bills Receivable amount (number): Amount of the Bills Receivable.
Deliverer: Signature of the deliverer (customer), on whom the Bills Receivable is
drawn.
Receiver: Signature of the receiver (company), on whose favor the Bills Receivable is
given by the customer.
• The Total (column) for all the Bills Receivables in a specific report are given at the
end report (same sequence number) under the Bills Receivables Amounts column.
Limitations
• Report can be run only for a specific transaction date.
• The report cannot be run for multiple customers at the same time.

7
Greek Withholding Tax Letter
Requirement
The Greek Withholding Tax Letter is a requirement to provide the details of the Tax
withheld against invoices for a supplier, along with the details of the invoices, for which
withholding tax has been generated. It is printed to assess the obligation of the
company to deposit the withheld tax from the suppliers to the tax authorities. Four
different layouts of letters are required. The first type is used for the Letters sent to the tax
authorities and the other three types refer to the tax withheld from freelancers,
contractors and board of directors.
Solution Overview
The withholding tax letter is run to provide the details of the tax withheld against
invoices for a supplier, along with the details of the invoices are subject to withholding
tax, which are applied to both partially and fully paid invoices during the calendar
year.
Prior to running the Greek withholding tax letter, the user needs to run the "AP
Withholding Tax Extract" request to select the data. The details of fiscal company, VAT
number, tax office, tax Area, company activity, and register number are extracted from the
legal entity profiles. However, the tax file number and electronic file number are obtained
from a Localization Descriptive Flexfield set at the legal entity level. The legal entity
represents the fiscal company.
Greek Withholding Tax Letter 7-1

Report Output
Header
Layout 1
Layout 2
Layout 3

Layout 4
Setup Steps
implement Greek Withholding Tax Letter.
relevant steps to be considered in implementing the Greek Withholding
Tax Letter. For each module installed, consult the manuals for that
module to determine the sequence of setup steps.

Suite

Localization Patch
2 Assign the Greek Required System Administrator

Withholding Tax
Letter to the
corresponding
responsibility from
which the report
needs to be run.
Suite
3 Set Localization Optional Legal Entity Manager

Descriptive Flexfield
at Legal entity update
page for Electronic
file number and Tax
file number.
4 Set Localization Optional Accounts Payables

Descriptive Flexfield
at Supplier sites page
for VAT registration
office.
Localization Descriptive Flexfield at Legal entity update page for Electronic file
number and Tax file number:
Navigation Path:
Legal Entity Manager--> Legal Entity Configurator -->Query for country "Greece" and
click on "Go" button.
Click on "View details" for the specific legal entity the user wants, legal type: "Legal
Entity". Click on the "Update" button in the General tab. Click on "CLE: Additional Legal
Entity Information". Select context value as "GR". Enter "Tax File Number" and "
Electronic File Number" and click on the Save button.
Localization Descriptive Flexfield at Supplier sites page for VAT registration office:
Navigation Path:
Accounts Payables -->Suppliers -->Entry -->Click on the "Organization" tab.
Under Tax and financial information section, click on "Additional tax details". Choose
context value: "GR". Enter VAT registration office: "Greece". Click on the Save button.
Functionality
The primary functionality of the report is to print a Withholding Tax Letter that
certifies:
• The total amount of withholding tax applied to invoices that are either partially or
fully paid during the calendar year.
• The total net amount of invoices on which withholding tax is applied.
• The invoice date and official legal sequence number of each invoice on which tax is

withheld during the calendar year.
The four different layouts of Letters that require four different Withholding Tax Groups
are:
• Layout sent to Contractors/Third parties
• Layout sent to Freelancers
• Layout sent to Board of directors.
• Layout sent to Tax Authorities
Before running the Greek withholding tax letter, the user needs to run the "AP
Withholding Tax Extract" request to select the data. It is user responsibility to run the "
AP Withholding Tax Extract" for dates within the calendar year that is required for the
report. The details of fiscal company, VAT number, tax office, tax area, company
activity, and register number are extracted from LE profiles. However, the tax file
number and electronic file number are obtained from a Localization Descriptive
Flexfield set at the legal entity level. The withholding invoice is created at invoice
validation time.
The Report selects only invoices in Functional currency.
Only validated and accounted invoices are displayed by the report.
The name and telephone number details of the employee given in parameter are printed on
the report.
Payable amount refers to the amount paid to the supplier, and taxable amount refers to the
basis amount of withholding tax calculation. For example: For an AP invoice
number 222, the payment Amount is 970 Euros and Taxable Amount is 1000 Euros. In this
case the Withheld tax will be 30 Euro.
There are no validations at the parameter level for the four layouts. The user is
responsible for selecting the correct Withholding Tax Group and tax code as
parameters.
All the suppliers under the selected category receive withholding tax letters based on the
layout selected by the user.
The tax codes are not displayed in any of the layouts. However, all layouts include tax
rates, tax descriptions and amounts. The country code appears on the report, next to the
supplier address for all the layouts. There is a page break for each supplier in the report.
At the end of the report for all layouts, Assessment, Issuer, Certifier, and Title of
Certifier are shown.
The layout of letter sent to tax authorities requires an official certification about the total
amount of tax withheld from each supplier. The following fields are required:
• Suppliers name and address.
• The name of the country.
• The rate of the withholding tax.
• The numbers and dates of invoices.
• The total net amount.
The layout of letter sent to contractors, freelancers and board of directors includes the
following fields:
1. The suppliers name, address, VAT registration number and supplier's tax authority.
2. The total amount of the withheld tax.
3. The total net amount of the supplier's invoices.
Prerequisites
• Only accounted Accounts Payables invoices with withholding taxes applied are
displayed in the report. Unless the invoices are accounted, it is not displayed in the
report.
• The setups related to withholding tax need to be done/enabled to run this report
successfully.
• The withholding tax feature is to be enabled at the Supplier Site level, so that those
are defaulted to those supplier's invoices. The automatic withholding tax lines for the
invoice must be created (withholding tax line) upon validating the Invoice. And also
the Withholding Tax invoices with type "Withholding Tax" must be created
automatically once the Invoice has been validated.
• These withholding tax invoices must be validated and accounted in order to be

displayed in the report. Refer to Oracle Payables User Guide and verify once the
invoice is validated, the automatic withholding tax line for the invoice is created
(withholding tax line).
• Prior to running the Greek Withholding Tax Letter, the standard Withholding Tax
Extract needs to be run for the particular supplier/all suppliers using the date
ranges within the calendar year.
• The Localization Descriptive Flexfields for the fields "Electronic file number" and "
Tax file number" must be enabled at the Legal entity update page in Legal Entity
Manager.
• The Localization Descriptive Flexfield at the Supplier Sites page for VAT
registration office has to be enabled.

User Procedure
Create standard Payables Invoices with witholding tax
• Refer to Oracle Payables User Guide to create standard invoices using withholding
tax assigned to the respective suppliers. Validate and create accounting entries for
these Invoices, and then transfer the entries to General Ledger.
Run Standard Withholding Tax Extract
• Refer to Oracle Payables User Guide to run the standard "Withholding Tax Extract"
for all suppliers /a particular supplier using date ranges within the calendar year
and then run the withholding tax letter for that request ID.

• Run CLE: Greek Withholding Tax Letter Report from Payables responsibility.
• Navigate to Standard Request Submission form in Payables responsibility.
• Select "CLE: Greek Withholding Tax Letter".

Note: To run the report in PDF format, select the parameter Output Type as 'PDF',
and then click on the Options button. In the LOV format, select PDF, and then click
OK.
Report Parameters

Number
1 Request ID Yes Select the request ID, which is

automatically generated, once the
AP: Withholding Tax Extract is
run.
2 Legal Entity Yes Select the legal entity for which

the report needs to run.
Number
3 Certifier Yes Enter the certifier's name, who

sends the Withholding Tax Letter to
the tax authorities on behalf of the
fiscal company.
4 Title of Certifier Yes Enter the title of the certifier, who

sends the Withholding Tax Letter to
the tax authorities.
5 Layout Yes Select the Layouts of the report,

which are as follows:
• Layout sent to
Contractors/Third parties
• Layout sent to Freelancers
• Layout sent to Board of

directors
• Layout sent to Tax

Authorities
6 Withholding Tax No The LOV contains the list of

Group withholding tax groups. The user
selects the tax group for which the
report runs. No default value.
7 Withholding Tax No This LOV contains the list of

withholding tax which is context
based on the Withholding Tax
Group LOV. Based on the
Withholding tax group selected,
the withholding taxes relevant to
the tax group are displayed. No
default value.
9 Employee No This LOV contains the list of all

employees belonging to the
Business Group. The user can
select a particular employee, and
then run the report. The employee
name/telephone is displayed in

Number
the report header, if selected. No

default value.
Report Headings
Report Title: Greek Withholding Tax Letter
Organization Name: Legal entity name (Fiscal Company) for which the report is run.
The legal entity details are extracted from the LE profiles.
City and Zip: City and zip code of the fiscal company (Legal Entity).
Current date: Current system date for which the report is being run.
Registration Number: Registration Number (APMAE Code) of the legal entity, which is
selected from LE profile (Legal Entity Manager).
Address Line: Registered address of the legal entity.
Employee name: Employee name is displayed in the report header based on the
employee selected at the parameter level by the user.
Employee telephone: The telephone number of the employee is displayed based on the
employee selected by the user at the parameter level.
Tax office: Tax office of the legal entity (fiscal company) is displayed.
Tax area: Tax area of the legal entity (fiscal company) is displayed
Vat Number: VAT registration number is selected from the legal entity profile. The
VAT registration number belonging to a particular legal entity's establishment is
displayed.
Tax File number / Electronic Tax File Number: The tax file number/electronic file
number is extracted from Localization Descriptive Flexfield, set at the legal entity level.
Country: The country of the legal entity is displayed in this field.
Column Headings
Layout 1 and Layout 2
• Assessment
• We assess to Supplier name
• Supplier address line
• Supplier city and zip
• Supplier country
• VAT registration number
• VAT registration office
• Payments from Date from to Date to
• Invoice- Payable total
• Invoice currency code
• Invoice- Amount total
• Withholding Tax rate - Percentage
• Withholding tax description
• Total withholding tax amount
• According to article 58 paragraph 1,case B' K.N. 2238/94. The withheld tax amount
was reimbursed to &CP_COMPANY_TAX_Office. The document is issued for tax
use according article 83 paragraph 2 K.N. 2238/94
• Sincerely
• Sender Name
• Sender Title
Layout 3
• Assessment
• We assess to - Supplier Name
• Supplier Address Line
• Supplier city and zip
• VAT Registration Number
• VAT Registration Office
• Supplier Country
• During the calendar year (current year) the following payments were received:

• Board of Directors repayments - Total amount
• Invoice currency code
• Withholding Tax code - Withholding tax amount
• Taxable Income - Taxable Amount
• Remaining amount - [Board of director repayments - Withholding tax amount -

Taxable Income]
• The above taxes were withheld according article 54 paragraph 4 of 2238/94 and
have been reimbursed to Company Tax Office. The document is issued for tax use
according article 83 of K.N 2238/94 paragraph 2.
• Sincerely
• Sender Name
• Sender Title
Layout 4
• To Tax Office
• Subject: Withholding Tax Assessment
• We kindly ask to provide us with a withholding tax assessment for services

delivered by company, Supplier Name, Supplier Address Line and Supplier
Country according to article 13 par. 5 of N. 2238/94 and contract of avoiding double
taxation between Country Name and Supplier Country.
• The taxable amount withheld Withholding Tax rate (percentage) from the following
invoices of Supplier Name:
• Invoice Date
• Invoice Number
• And concerning the amount Invoice Currency code Total Payable Amount (in
words) that was reimbursed as shown in the attached documents.
• Certifier
• Issuer
• Sender Name
• Sender Title
Limitations
• When the User runs the report, in the parameters section he will be able to mention
the report layout name. This layout name will not be visible in the Report output
anywhere, and hence this is a limitation.
• The User enters the values for the parameters "certifier" and "title of certifier" at the
parameter level. These values appear as only Signatures in the report output, and
have no other effect other than this.

8
Turnover Reporting
Requirement
There are many changes in the legislature of 2014 for the Turnover report in Greece. The
requirement has changed from annual to monthly and especially for the transitional fiscal
year of 2014, to quarterly extracts, to be reported to the tax authorities. The file to be
submitted is no longer a specialized txt file but an xml file that can only be submitted
through a special portal of the Tax authorities. It summarizes purchases and
sales from specific suppliers and customers and also depicts gross figures for retail and
other expenses and revenues . The Greek requirement has undergone changes
with respect to reporting the turnover to 'Public sector companies'. From Fiscal year
2008, turnover to Public sector companies need not be reported separately. The existing
flag though, present at the master files of Suppliers and Customers will be used by the
new functionality to indicate that the relative third party should be included in the
turnover report (thus the default value, along with existing records should be changed
to ‘Y’ for Yes. Certain turnover is also excluded by defining turnover exclusion rules.
Supplier / customer types, invoice / transaction types and/or invoice / transaction
distribution line types are defined and consequently excluded from the Account
Payables and Account Receivables turnover reporting in the exclusion rules. This
information must be gathered at the end of each period and be submitted to the tax
authorities in a predefined XML file, by the end of the next period.
• All partners (customers/suppliers including public sector) are analytically reported.

• There is no longer any value limit for expenses and revenues to be excluded from
the turnover report.
• All retail transactions that are covered by simple retail-receipts and not by Invoices,
will be grouped in single amounts for : Other Expenses.
Solution Overview
MYF (Customer/Supplier Turnover Report) is a Greek statutory requirement. It
provides summarized information on the turnover of customers and suppliers during a
calendar year. Undere the new law voted in 2014, the report should be submitted to the Greek tax
authorities every quarter for fiscal year 2014 and monthly from fiscal year 2015 and on. Later
Turnover Reporting 8-1

amendments to the law however have pushed for full disclosure of fiscal 2104 by jan 20, 2016 and
full disclosure of fiscal 2015 for Sep 30, 2016. There is currently no information on the financial
information of fiscal 2016. The report should categorize customers and the suppliers by the AFM
(Tax registration number).
Apart from the turnover amounts, specific identification information must be included for each
customer/supplier. This consists of the AFM (Tax Registration Number), that is defined at the third
party level for verification purposes. All other personal information, like occupation, address, etc
are no longer needed in the report.
Some information must also be included about the reporting legal entity. This information is
defined on the specialized MYF Setup screen.
Other elements of this solution include :
Global Descriptive Flexfields:
CLE: MYF setup OAF page

CLE: MYF XML Output (The new output Formto be used from 2014 onward)
CLE: Import External Data

CLE: Turnover Report XML (The new concurrent process for periodic data collection).
Turnover Output to XML (CLE: Turnover Report XML Output) that generates the XML
file output to be submitted to the Tax authorities.
Generic Setup Steps

The following table lists the setup steps and reference to their location within Oracle E-Business
Suite. After you logon to Oracle E-Business Suite, complete these steps to implement CLE: Greece
Turnover Reporting.
Note: The sequence indicated for the setup checklist applies only to the relevant
steps to be considered in implementing the CLE: Greece Turnover Reporting. For
each module installed, consult the manuals for that module to determine the
sequence of setup steps.

Suite

Localization Patch
2 Assign the “ CLE: Required System Administrator
Turnover Report
XML”, “CLE:
Turnover Report
XML Output”
and“CLE_F118_G
ENLOAD,” to the
desired
request group
associated with the
responsibility.
3 Assign the CLE_F118 Required Application Developer

_MYF_XML, CLE:
Import External Data
and Expense Types
Turnover Report
Parameters form
Functions, to the
Desired menus.
Log on to MyOracle Support. Download and install the Greek Add-on Localization patch. The
patch creates the components of the Greek Turnover Report Installation of:
CLE: Greece Turnover Reporting - Menu
The above Menu contains:
CLE: MYF XML Output
Here the user should add the CLE: Import External Turnover Data and CLE_F118_MYF_XML, pages
with relative prompts.
The user should also add the Expense Types Turnvover Report Parameters, function (without a prompt)
To the relative AR and / or AP menu where the CLE: Greece Turnover Reporting –submenu will be
Assigned to.
Turnover Report Concurrent requests
Assign the following concurrent requests to the request group associated with the
responsibility from where turnover reporting will be managed and run:.
CLE: Turnover Report XML,
CLE: Turnover Report XML Output and
CLE_F118_GENLOAD

The CLE: Greece Turnover Reporting –submenu is available once the patch has been downloaded
and applied successfully. The user can attach these menus as submenus to the respective menus,
attached to the Accounts Payables and Accounts Receivables responsibilities.
Add the sub-menu:
Switch to System Administrator responsibility, and then navigate to: - Application

-->Menu Illustrations: Navigation Path: Application -->Menu.
Query for the Menu
Add Prompt Greece Turnover Reporting. Submenu CLE: Greece Turnover Reporting to
the main menu of Accounts Payables (and /or Receivables). Enable the check box 'Grant'.
Add the Expense Types turnover Report parameters, function without a prompt to the same
main menu of Accounts payables (and/ or Receivables). Enable the check box ‘Grant’
From the System Administrator responsibility, navigate to: - Application

-->Menu Illustrations: Navigation Path: Application -->Menu.
Query for the Menu: CLE_F118_TRNVR_RPT
The submenu CLE_F118_TRNVR_RPT with the CLE MYF setup and CLE MYF Output forms
has already been created by the patch.
Add Prompt CLE: Import External Data. Add Function: CLE: Import External Turnover
Data. Enable the check box 'Grant'.
Add Prompt CLE: MYF XML Output. Add function : CLE_F118_MYF_XML. Enable the
check box 'Grant'.
Add the new forms on the Turnover Submenu:
Add the Turnover Report Concurrent requests

CLE_F118_GENLOAD (Statutory Turnover reporting) Concurrent Program
CLE_F118_GENLOAD Concurrent request is registered under EMEA Localizations. The

name of the program: CLE_F118_GENLOAD.
The short name of the program: CLE_F118_GENLOAD.
This is used to upload and process a tab delimited file with transactional data stored in
external systems.
CLE: Turnover Report XML (Statutory Turnover reporting) Concurrent Program
CLE: Turnover Report XML, concurrent request is registered under EMEA

Localizations. The name of the program: CLE: Turnover Report XML.
The short name of the program: CLE_F118_TRNOVR_RPT_XML
This is used to collect and process the monthly transaction data from AP and AR to present it
to the user.
CLE: Turnover Report XML Output (Statutory Turnover reporting) Concurrent Program
CLE: Turnover Report XML Output, concurrent request is registered under EMEA
Localizations. The name of the program: CLE: Turnover Report XML Output.
The short name of the program: CLE_F118_MYF_XML_OUT
This is used to produce the required output XML file with all the relative data that will be
Submitted on a periodic (monthly) basis to the special portal available by the Greek Ministry
Of Finance. After repeated delays, the current status is for the 2014 fiscal year data to be
submitted by January 20, 2016 and the 2015 fiscal year data by September 30, 2016. There has
been no clarification as to the whereabouts of monthly or quarterly reports for 2016 fiscal year
data at the moment. On every quarterly submission, the user should stll submit
three monthly XML files.
To access these requests from the relative responsibility, attach these request to the
request group attached to the required responsibility.

Illustrations for the first concurrent request:
Switch to System Administrator responsibility and then navigate to Security-->
Responsibility--> Define --> Query for Accounts Payables Vision Operations
Responsibility and make a note of request group name.
Navigation Path: Security --> Responsibility--> Request Query for group and the
application to which the request is required to be added.
Query for Accounts Receivables Vision Operations responsibility and make a note of
request group name.
Navigation Path: Security --> Responsibility--> Request Query for Group and the
application to which the request is required to be added.
The patch installs the Functions / OA Pages. The user needs to attach the menu to the
respective responsibilities and check the existence of the same.
This OAF page is designed as a search page with a 'Create New' and 'Update' buttons.
The page has been divided into three sections. The first section consists of the fields that
form a part of the search: Company Name, Registered Name and Tax Registration
Number.
The search page uses three values for search:
• LE Name
• Registered Name
• VAT Registration Number
A blind search gets all the legal entities for which the MYF set up has been done. There is
an Update button against each legal entity. There is also 'Create New Setup' button to
create MYF set-up for new legal entity.
On updation / create new set up buttons the fields are user updatable.
The first section of the page consists of the following information:
• Company Registered name
• Legal entity
• Tax registration number
• Tax Officer ID
• File Number
• Address
• Telephone / Fax numbers

• E-mail
• City
• Zip code
The second section of the page consists the following information:

• The path to capture output file.
• The minimum invoice/transaction amount.
The second section of the page consists the following information:

• Accounts Payable Tab
• Accounts Receivables Tab
Under each Tab there are following sections:

Turnover exclusion rules: Select from LOV. The AP and AR turnover rules are to be set up from
Greek standard localization menu. This tab is used to call the AR and AP
turnover exclusion rules, which are already defined to call while running the CLE:
Process MYF concurrent request.
Exclusion clause: SQL commands in addition to the setup can be defined under this
section.
Profession field: Customer profession is selected from SIC code defined at customer
header.
Supplier profession information is selected from 'Standard Industry Class' defined at supplier
header level.
There is also provision to specify the transaction amount limit. MYF selects only those
transactions over and the minimum amount specified in the form.
Additional Setup (“Setup MYF” OA Page):
Specify AR/AP exclusion rules. The MYF allows you to completely exclude for AR: certain
Customer Classes, certain system-defined transaction types, and certain system-defined Line
Types. For AP: certain Vendor Types, system-defined invoice types, and system-defined
distribution line types. of your choice (i.e. Prepayments, Expense Reports, etc).
AR Functionality:
To use this functionality, use Greek AR Localizations (standard functionality) to set up an

exclusion rule that excludes your AR selections, then use Greek AP Localizations (standard
functionality) to set up an exclusion rule that excludes your AP selections. Specify these rules in
Setup MYF form.
In order to use this functionality, first you need to have included the above mentioned forms in
the respective responsibilities for Greek AR and Greek AP.
From responsibility : System Administrator
Application > Menu > Query for Menu used by Receivables Responsibility for Greece:
Add Prompt : ‘AR Exclusion Rules’ and Function : Customer Turnover Exclusion Rules.
AP Functionality:
Do the same for AP. Query for Menu used by Payables Responsibility for Greece:
Add Prompt : ‘AP Exclusion Rules’ and Function : Supplier Turnover Exclusion Rules.

After assigning these forms to the respective responsibilities the user defines the objects to be
excluded from the Turnover report.
For Receivables:
For Payables:
Please notice that what is shown as the Group Type is the meaning of the available value and
not the lookup type:
These exclusion rules are used in the following MYF setup screen as mentioned also in the
12.2 CLEGRFINUG section 8-7.

Query for the relative legal Entity and select Update :
In the relative TAB for receivables the user should select the respective Exclusion rule defined
above.
Likewise, for the Payables Exclusions, the user will need to assign the Payables Exclusion rules
to the proper TAB and appropriate field:
Additional exclusions can be added by using SQL clauses in the “Exclusion Clause” windows
for AR and AP.
An example of a possible and a little complicated SQL filter to be inserted in the relevant box for
AR additional exclusions of the MYF setup form is the following:
ra_cust_trx_types_all.name = 'Acquis Con Inv' or

ra_cust_trx_types_all.name = 'Acquis Edu Inv' or
ra_cust_trx_types_all.name = 'Acquis HW Sup Inv' or
ra_cust_trx_types_all.name = 'Acquis Sup Inv' or
ra_cust_trx_types_all.name = 'Acquisition Deferred' or
ra_cust_trx_types_all.name = 'Complex Order' or
ra_cust_trx_types_all.name = 'I/C IN Lic Trans' or
ra_cust_trx_types_all.name = 'I/C IN Sup Trans' or
ra_cust_trx_types_all.name = 'PA Inv Mig' or
ra_cust_trx_types_all.name = 'Revenue Adj. Inv' or
ra_cust_trx_types_all.name = 'Acquis Sup CM' or
ra_cust_trx_types_all.name = 'I/C Credit Memo'
In case the user wants to use the descriptions and not the names of these transaction types, in the
above code you could change the NAME with DESCRIPTION and using the descriptions of
these transactions.
CLE: Turnover Report XML (from 2014) Concurrent Request
The following process, describes the necessary steps and functionality of the Turnover
program to be used from January 1st 2014.
The patch installs the concurrent program and its executable. The user needs to check the
existence of the same.
The objective of this concurrent program is to segregate the customer turnover, suppliers turnover
into positive and negative balances, collect all the relative other expenses amounts, collect any
possible retail and /or petty cash receipts, and transmit the report outcome into the new output form
created for usage from 2014 onward, the CLE: MYF XML Output page.

Output Page. As mentioned above, this process and form pages will only be in effect until
the submission of the relative data for fiscal year 2013. These are not being used for the
transactional data of fiscal year 2014.
Parameter Mandatory Default Value LOV
Legal Entity Y Alphabetical order List of Values
From Period Y Latest Open period on List of Values

Relative calendar.
To Period Y Latest Open period on List of Values

Relative calendar
From Date N None Date Format
To Date N None Date Format
To begin, run the "CLE: Turnover Report XML" concurrent request. When running the ΜΥF:
• Specify the legal entity for which the report is run. Select the value from the list of
values.
• Specify desired period. The program allows for multiple period selection (from –
to) but the end result is always monthly based. In other words, even if the program
runs from period Jan -2014 to Mar-2014, if there are transactions under the same tax
registration number in all three periods, there will be three different lines created in
the output screen, one for each period.
• An extra filetr is provided to run the program for specific days within the
monthly period. This is only necessary in the case of sequencial reporting of the
turnover report.
CLE: MYF XML Output Page

The patch installs the Functions and Forms. The user needs to attach the menu with
these existing functions to the respective responsibilities.
This page captures the output from the concurrent request ‘CLE: Turnover Report XML’. Upon
completion of the request, navigate to the CLE: MYF XML Output page.
Important: Each time the " CLE: Turnover Report XML " concurrent request
is run for a given period, MYF data is deleted for that period and rebuilt.
Correct data in application / system and rerun the process as many times to
get the accurate result.
Manual corrections are no longer possible in the CLE: MYF XML output
Page.
• The user selects the Legal Entity and the period (periods) for which he/she wishes to
inspect the financial transactions. There are additional filters like the source of these
transactions (ERP, Import,etc), XML Section (grouped by Tax Reg Nmb, or other expenses,
etc), Subledger (AP, AR). There is also an option to select the lines with errors (or not).
• The information provided in the output form includes the source of the entries, the
subledger, the third party tax registration number and name, the number of transactions,
the sum of these transactions, the type (credit or normal-debit), and the XML section.
• For each Tax registration number, there can be two lines per period. One includes all the
positive transactions (Invoices), and one includes all the negative (Credit Memos, etc).
This is also a change from the previous functionality that checked only balances.
• When the XML section has the value of Other expenses, there is no need for a tax
registration number to be provided. The same is true when the value on the XML section is
Grouped Cash Register. In the later case, the cash registration number should have been
provided in the relative transactions and is present on the output screen as well.
• If there is an error for a specific line, the Error checkbox at the end of each line is checked.
• The user can review all the entries that are included in the amount presented in a specific
line by double-clicking on the field at the beginning of the line.
By double clicking again on the first field of any line of the detailed transactions, a new window
opens with error messages (if there is an error).
• When all the checks have been completed, the user can extract the final file by clicking on
'Create File' button at the top of the page. This will initiate the execution of the “CLE:
Turnover Report XML Output” concurrent request that will result to the required XML file
For the information shown on the Output screen.

Attention: The export file will present the information seen on the output form. The
user must use the selection filters to isolate the relative period to be submitted to the
tax authorities.
Report Output from 2014:

The required output will have an XML form as this provided in the example below. The user can
Use this XML as a source to create additional internal templates and reports:
Setup of Exchange Rates
Under the new legislature, the tax authorities provide the user with the ability to enter transactions
in a foreign currency in the relative subledgers. These transactions will be translated to a specific
exchange rate that needs to be setup and for which the user needs to provide a monthly rate,
just for the sake of the turnover report, with effective date the first of each period.
In order to setup the required rate the user needs to Navigate to :

Payables > Setup > Currency > Rates > Types
And define a new conversion type with the name : ‘GR_MYF’
The description can be anything that makes sence to the user. Eg: ‘Monthly exchange rate for
Turnover report’.
As mentioned above, the user needs to define a rate per period with effective date the first
of each month, that will be used to translate all the foreign currency transactions of that month
to the country currency (EURO).
In order to define the required rate values the user needs to Navigate to :
Payables > Setup > Currency > Rates > Daily
And define a new rate for conversion type ‘GR_MYF’ for the first day of every period for
Which there are transactions in foreign exchange.
The user enters only the Entered to Accounting currency ratio and the application creates the
Reverse one.
When this setup is available, without any other action from the user, the application will
translate any foreign currency transaction to that of the ledger currency when the ‘CLE: Turnover
Report XML’ process is run. The user can check on the entered currency amounts and their
translated amounts per invoice by double-clicking on the first field of the line in the Output page.

Setup of Expense Report Functionality
Under the new legislature, the tax authorities require that even small amounts that are not
charged against the tax registration number of a third party, they need to be included as lumb
sums in the new report. The ERP application offers the user the ability to enter employee
expense reports that are then transformed into regular AP transactions.
The Turnover localization allows for the pre-definition of the treatment of each expense type
in the expense reports, so that when the AP invoices are created, each item-line will have a
relative indication that would specify how the new turnover report will treat that line’s amount.
In order to define how the application will treat each expense item, the user needs to setup an
Expense report template to be used by its employees. The user needs to Navigate to :
Payables > Setup > Invoice > Expense Report Templates
For each expense item line the user needs to identify the type of expense this item belongs to,
and to which XML section this expense item will be accounted in.
The user selects one Expense item line and then from the Tools Menu at the Application
Toolbar, selects : ‘CLE: Greece Turnover Report Parameters’
In the parameters windw that opens, the user must identify for the specific expense item,
what will be the XML section that this item will be accounted in. The choises are the same
as the ones used for the AP and AR transactions but for the expense reports only the
following have a logical effect on the expenses:
MYF Excluded: This amount will be excluded from the turnover report
Grouped Expenses: This amount will be listed by the employee’s Tax reg.Nmb.
Othe Expenses: This amount will be accounted in the Other expenses
Sum amount in the Turnover report.
In order for this template to be available for usage from i-expense as well, it is important to
check the relative checkbox when this is defined.
It must be noted that as it will be clear in the example that follows, when an
expense report is processed and transformed into an AP transaction, this will be in the name
of the employee that has entered the expense report. For expenses like Hotel accommodations
that will need to be entered again as AP Invoices in the system in the name of the
Corporation itself, the expense item line better be identified as MYF Exclude. Mini bar
Expenses on the other hand can be entered as Other Expenses.
A user of the application, when he or she is also declared as an employee, can enter a
Payables’ transaction of the type Expense report. The user needs to Navigate to :
Payables > Invoices > Entry > Expense Reports
The user needs to select the Template that was setup before and list the items relative to the
respective expense report. By selecting the expense type each line belongs to, the application
identifies the XML section where this amount will be accounted to. Once all expense lines have
been entered, the user must press the ‘ALL Verified” button at the bottom right corner of the
page. Once everything is verified, the user (or the person responsible) runs the concurrent
report “ Expense Report Export” that transforms the expense reports to AP transactions.
In the AP transaction created, the Item type expenses at line level have kept the definitions
and the expense types of the original expense reports.
Setup of Global Descriptive Flexfields

The Global Descriptive Flexfields are explained below:
Supplier / Customer additional Information GDF
Included in MYF/Not
In order for a customer/supplier to be considered for the turnover report, the first segment of the
Global Descriptive Flexfield on the customers and the suppliers needs to include a
global_attribute1 with a user-prompt of " Included in MYF" and a valueset of Yes_No.
Required to Submit/Not
If a customer/supplier is MYF reportable, the tax authorities validate Tax Registration Number
while processing MYF file.
If a customer/supplier is not liable (farmer, casually employed etc. as these occupations are not
liable for MYF submission), the tax registration number is not validated by the tax authorities
while processing the MYF file.
To achieve this functionality, extend the Global Descriptive Flexfield on the customers and the
suppliers to include a global_attribute2 with a user-prompt of " Required to Submit" and a
valueset of Yes_No. A value of null or 'Y' is considered as required to submit while a value of 'N'
is considered as Non-Required.
This classification does not affect whether a customer/supplier is included in the MYF or not.
Instead, it is an independent characterization of the customer/supplier that affects how the
information provided gets validated by the tax authorities

Applicatio Descriptiv Display Context Segment Attribute
n Short e Flexfield Name field
Name (OA page) values
Regional JG_PO_VE Include in JE.GR.APX JE_GR_PSC Global_attribute 1

Localizatio NDORS MYF/Not VDMVD.S _YES_NO
ns UPPLIER
Regional JG_PO_VE Required to JE.GR.APX JE_GR_MYFRE Global_attribute 2

Localizatio NDORS Submit/Not VDMVD.S Q_YES_NO
ns UPPLIER
Regional JG_PO_VE MYF JE.GR.APX JE_GR_MYFREP Global_attribute 3
Localizatio NDORS Reportable VDMVD.S _YES_NO
ns UPPLIER
Regional JG_HZ_CU Include in JE.GR. ARX JE_GR_PSC Global_attribute 1

Localizatio ST_ACCO MYF/Not CUDCI.CU _YES_NO
Ns UNTS STOMER
Regional JG_HZ_CU Required to JE.GR.ARX JE_GR_MYFRE Global_attribute 2
Localizatio ST_ACCO Submit/Not CUDCI.CU Q_YES_NO
ns UNTS STOMER
Regional JG_HZ_CU MYF JE.GR.ARX JE_GR_MYFREP Global_attribute 3
Localizatio ST_ACCO Reportable CUDCI.CU _YES_NO
ns UNTS STOMER
MYF Reportable
Extend the Globalization Descriptive Flexfield on the Customers and the Suppliers to include an
optional global_attribute3 with a user-prompt of "MYF Reportable" and a valueset of Yes_No. A
value of 'Y' causes the MYF to use that customer's/supplier's name, profession, address, and
other information reportable information.
For example, when multiple customers exist in AR with the same tax registration number, the
user must have a way to specify which the MYF needs to use to report the name, profession,
address, and liable/not liable information. This value is mostly relevant for the up to 2013 yearly
type of turnover report, but the logic was kept for the newer version as well, even though it is not
presented on the report.
Creation of Context based Global Descriptive Flexfields
Supplier level Global Descriptive Flexfields

• Query for Global Descriptive Flexfield: JG_PO_VENDORS.
• Insert Context Field values.
• Code: JE.GR.APXVDMVD.SUPPLIERS.
• Name: Greece Supplier information.
• Description: Greek Suppliers Information.
• Enable the segment vales.
• Enable the context.
• Freeze and compile the flexfield.
Enter segment values as below:
Number Name Window Prompt Column Valueset
10 JE_GR_PSC MYF Submit Global_Attribute_1 Yes_No

_YES_NO
20 JE_GR_MYFREQ MYF Required Global_Attribute_2 Yes_No

_YES_No
30 JE_GR_MYFREP MYF Reportable Global_Attribute_3 Yes_No

_YES_NO
Customer level Globalization Descriptive Flexfields
• Query for Globalization Descriptive Flexfield: JG_HZ_CUST_ACCOUNTS.
• Insert Context Field values.
• Code: JE.GR.ARXCUDCI.CUSTOMERS
• Name: Greek Customers Information.
• Description: Greek Customers Information.
• Enable the segment vales.
• Enable the context.
• Freeze and compile the Flexfield.

Enter segment values as below:
Number Name Window Prompt Column Valueset
10 JE_GR_PSC MYF Submit Global_Attribute_1 Yes_No

_YES_NO
20 JE_GR_MYFREQ MYF Required Global_Attribute_2 Yes_No

_YES_No
30 JE_GR_MYFREP MYF Reportable Global_Attribute_3 Yes_No

_YES_NO
Supplier / Customer transaction additional Information GDF
The patch will also setup the following Global Descriptive Flexfields that the user should
verify they are present and in effect:
Transaction Type for Turnover Reporting

In order to identify the way each transaction will be depicted in the new Turnover report, the
following GDF have been included in the patch and need to be completed by the user during
Transaction entry. The logic being used in Receivables and Payables is the same but there are
certain differences due to the different needs of each subledger. For the Receivable transactions,

the GDF being used is the JG_RA_CUSTOMER_TRX, and apart from the Item type definition that
can take the values described below, there is one more segment being used when the transaction
refers to Retail transactions that have been entered through a specific registered Cash Desk. In that
case, when the item type is “groupedCashRegisters” the user must identify the cash registered
number for the amount to populate the proper field in the report. It is important that the Cash
register number segment is defined on the Global_attribute3 column.
The item values available and their uses are:

Excluded : MYF Excluded transaction
groupedCashRegisters: Retail transactions being transferred in the ERP that have a
specific Cash register as a source. A second segment needs to
be filled with the registered number of the cash machine.
groupedExpenses: Regular AP Invoices and CM enetered against valid third
parties, to be grouped by Third party Tax Reg Nmb.
groupedRevenues: Regular AR Invoices and CM enetered against valid third
parties, to be grouped by Third party Tax Reg Nmb.
OtherExpenses: Other Expense related transactions that will be summed
together in an expense pull amount rather than be analized
by third party id. This includes expense and petty cash receipts.
RevenueInvoices To be used when the user wants to submit the transactional
invoices one by one and not to let the application group them
together.
On the payable transactions, the same classification is being made making use of the JG_AP_
_INVOICES Global Descriptive Flexfield. On the payables side there is no cash register segment
to be defined, but the application uses an additional Global descriptive flexfield that allows the
user to classify the expense items of an invoice on a line to line basis. This is used to cover the
expense report functionlaity as well as the differenc in classification of expense items, to be
addressed under the original issuer’s tax registration number, or to be summed as other expenses.
The GDF described above is the JG_AP_INVOICE_LINES and it should also be created by
the patch, along with the relative JG_AP_EXPENSE_REPORT_LINES, used to identify the
treatment of the different expense types in the expense report functionality:

The main segment defined in all these GDFs is the Item Type in Global_attribute1 with the
Value set : CLE_F118_XML_SECTIONS
Setup of Value Sets Required by the Turnover Solution

The required value sets for the new functionlaity to be operational are included in the patch.
For reference, verification and maintenance purposes, these are defined below:
Responsibility: System Administrator

Path: Application / Validation / Set
The value sets being used by the Turnover report functionality are the :
CLE_F118_XML_SECTIONS
CLE_F118_SOURCES
CLE_F118_SUBLEDGERS
The next Value set has dependent values on the CLE_F118_SOURCES as seen below.

For reference, verification and maintenance purposes, the values on these value sets as
these are defined from the patch are listed below:
Responsibility: System Administrator

Path: Application / Validation / Values
It must be noted that the user needs to add possible additional Sources (like IMPORT) and their
Relevant subledger dependent values.

Set-up Turnover exclusion Rules
To access the function to set the turnover rules, following functions are to be included
in the Accounts Payables and Accounts Receivables responsibility.
Turnover Function User Type Applications Applications

Exclusion Function
Name
Supplier JEGRLERAP Supplier Form Greek European

Turnover Turnover Localizations
Exclusion Exclusion
Rules Rules
Customer JEGRLERAR Customer Form Greek European

Turnover Turnover Localizations
Exclusion Exclusion
Rules Rules
Include the Function 'JEGRLERAP - Supplier Turnover Exclusion Rules' to the Accounts
Payables responsibility menu.
Include the Function 'JEGRLERAR - Customer Turnover Exclusion Rules' to the Accounts
Receivables responsibility menu.
Illustration:
Navigation Path: Application --> Menu
Assumptions
• The entire solution is based on legal entity being used as top most reporting entity.
• Setup of Accounts Receivables.
• Setup of Accounts Payables.
• Specification of AR and AP exclusion Rules. To use this functionality, use Greek AR

and AP Localizations (Standard functionality) to set up AR and AP turnover
exclusions.
• The Globalization Descriptive Flexfields as explained are created and enabled.
• The related Value sets are created, along with the respective values and enabled.
These Globalization Descriptive Flexfields are required set up as the functionality for
the Turnover reporting from 2014 onward, is based on these Globalization Descriptive
Flexfields And their proper usage by the end users.
Functionality from Fiscal year 2014.

The Customer/Supplier Turnover Report from January 1st 2014, provides summarized
information on the turnover of customers and suppliers during a calendar year on a
monthly basis. In order to satisfy the new requirements, the updated MYF solution as
mentioned in the solution overview, consists of three concurrent requests, three pages, a
trigger and some specific descriptive flexfields and value sets that have been identified
above.
Certain turnover is excluded by defining turnover exclusion rules. Supplier /
customer types, invoice / transaction types and/or invoice / transaction distribution line
types are defined and consequently excluded from the Accounts Payables and Accounts
Receivables turnover reporting in the exclusion rules. This functionality is retained from the
existing solution in effect till the fiscal year 2013 and has also been described above.
Create customer and supplier with Tax registration number set at the third party site
level, while profession is no longer required. Global descriptive flex fields set for supplier
and customer to identify whether turnover is ‘MYF included’ –ex Public Sector Comp.
Report , 'MYF reportable' and 'Required to Submit'. . Under the new functionality the first
segment is very important as it identifies which third party will be included in the
turnover report and the second segment is important for the Suppliers as it identifies who
is obligated to also file a turnover report for cross examination by the tax authorities. If
the value is ‘Yes’ or Null the supplier is obligated (value ‘0’ in the XML), if it is ‘No’ the
supplier is not obligated to file (value ‘1’ in the XML output file).
It is important to set up the Tax registration number at the third party site level through the
Tax manager responsibility in order for the application to execute a tax registration number
verification.

To set this up, the user after the supplier or customer has been created in the respective
subledger, he/she must Navigate to :
Responsibility: Tax Manager

Path: Parties / Party Tax Profile
The user should execute a query with the name of the relative third party with Party type
set as Third Party Site. Then the user should click on the Update Tax profile (or Create if
there is no Party Site created from the subledger)
In the screen where the Party Site details are defined, the Tax Registarion Type must be
defined as ‘VAT’ , the Tax Registration Number is set with an ‘EL’ or ‘GR’ prefix or simply the
nine digit number. The Set as default checkbox is irrelevant. If there is no Third party Tax
Profile created (Migrated Data) then and only then the process will pick the tax registration
number from the Default Registration number field of the Third party Site, which in that case
will have to be set up for VAT and Greece. Click on the SAVE and /or APPLY button.
The user should make sure that once the site information for this site has been saved, the
default Reporting country is set to Greece.
After all is set, the user can enter AP transactions with the expense type set at the header
or line level. The application checks first if there is an expense type at line level and if not
then it checks the header. If no expense type has been defined, the application considers
this transaction as ‘MYF excluded.’
The user can also enter AR transactions, identifying only at header level the XML section
under which, this revenue will be classified. For Retail transactions that have been
imported in the system, the user must identify the relative transaction as ‘Grouped Cash
Registered’ and also identify the Cash register number as this has been registered in the
tax authorities.
The invoices will be reported based on transaction dates, under AFM (Tax registration
number) defined as mentioned above. All the transaction dates falling in the calendar
month selected for the report, based on legal entity, will be selected for the reporting and
they will be classified in different sections of the XML report based on the values set on
each transaction or AP transaction line. The positive and negative transactions are

grouped by AFM (Tax registration number), so that for each AFM, for each monthly
period there can be 2 lines defined in the output screen and the final report. One for
positive transactions (eg. Invoices) and one for all the negative transactions (eg. Credit
memos).
Apart from the transactions entered through the ERP application, the system supports the
import of additional transactions through a peripheral system. The user needs to prepare
a tab delimited file with specific format and then use the relative “CLE: Import External
Data” Page to import these transactions and also consider them when the Turnover
process will run. The user clicks on the ‘Import New File’ button and a HTML page opens
where the user indicates the exact file (full path) that will be imported. The file then
appears in the Import data screen and is imported in the system.
An example of an import Tab Delimited file is the following :
When executing the Concurrent CLE: Turnover Report XML, the application selects the
Transactions for AP and AR that are eligible to be included in the report and based on the
query selection for presentation on the screen, the user creates the export XML file by
clicking on the Create file button. Meanwhile, while on the screen, the data can be queried
by using any column value as a filter and also they can be exported to Excel by means of
the Form toolbar function of Export.
Common User Procedure from 2014 on
• Enter AR and AP transactions
• Run CLE: Turnover Report XML concurrent program
• View the output in CLE: MYF XML Output Page.
• ΜΥF output file is valid only if the concurrent request completes successfully.
• Errors and warnings may occur primarily due to ΑΦΜ issues but these will be identified
in the Output page .
• Choose the Legal entity and the relative period from the respective fields and press ‘FIND’.
Since all XML export files are being submitted monthly (even during the transitional 2014,
the report is due every quarter but is submitted month by month).
• The output from CLE: Turnover Report XML is viewed here. The output is listed in columns
form grouped by period and tax registration number (AFM).
• You may NOT edit the data in this page (update, insert, delete).
• The first field is used as a button, where the user can double-click and enter on a detail screen
of the relative transactions forming up this line’s amount.
• If there are errors in a line, the Error checkbox will be checked and the user can review these
errors by clicking the first button to see the detailed transactions and then again double-clicking
on the specific transaction that also has the Error checkbox checked. Then there is a window
with the relative error message.
• Important Note: Each time you run the "CLE : Turnover Report XML" concurrent request for a
given period, MYF data is deleted for that period and rebuilt.
• Extract your final files by clicking on Create File button at the top of the page. Your
process will issue a warning message if there are lines with errors.

• The Create file button executes a concurrent request whose output is the required XML output
file that will be submitted to the Ministry’s portal. For the quarterly submissions of
fiscal year 2014, the users must prepare 3 XML files, one for each monthly period of the quarter.
This means that the CLE: Turnover Report XML process can run once for the whole quarter must
with periods set From Ian 2014 to Mar 2014, but in order to prepare the XML files, the user
query each monthly period separately on the output screen and create a file for each period.
• Extract your final files by clicking on Create File button at the top of the page. Your
process will issue a warning message if there are lines with errors.
CLE: MYF output Page - ERRORS and Warnings

The following error / warning messages are possible during the process:
Warning: Trading partner ΑΦΜ and Tax Registration Number are more than 9 digits long.
Action: Query up the Trading Partner reported on this line and update its tax registration
number.
Error: This ΑΦM is invalid. Action: Query up the Trading Partner using the ΑΦΜ
reported on this line and update the tax registration number(s) to a valid value.
Error: There is no ΑΦM Action: Query up the Third Party reported on this line and update its tax
registration number.
Error: No tax registration number is visible in the XML Output Form. Please check if there is a
valid Tax Registration line for the relative Third Party Site with the required qualifications (VAT,
GR, Valid Greek Tax registration number).
9
AP/AR Guarantee Processing
Requirement
It is a common business practice to issue and receive Guarantee Letters in Greece.
Letters of Guarantee are issued to provide the beneficiary with financial security. Bank
issues any type of bank guarantees requested by applicants and undertakes the
responsibility for applicant's failure in fulfillment of an obligation, or payment of a debt.
System must support the following activities:
• Creation of new guarantee types.
• Capturing Guarantee Letter details.
• Performing all Guarantee Letter related transactions like increase / decrease / return
or liquidate the guarantee.
• Viewing the guarantee information in a single Form.
• Ability to take reports which display the required information for a guarantee.
• Creation of accounting entries for all the transactions and transfer the same to the
Books of Accounts.
Solution Overview
This is a solution to capture, maintain and follow up the status of the guarantee letter
and also to create the respective accounting entry. It supports viewing and running
reports about Guarantee letters received and issued by the company. A guarantee letter
can be for a defined period with a specific expiration date or can be without any
expiration date. This information is captured in the Guarantee Letter Master File.
AP/AR Guarantee Processing 9-1

Report Output
Prerequisites
Installation
• CLE: Letters of Guarantee Types
• CLE: Letters of Guarantee Master File
• CLE: Letters of Guarantee Transactions
• CLE: Letters of Guarantee Inquiry
• CLE: Letters of Guarantee Report
Post Installation Setup
• Successful application of the patch creates the CLE_F291_GUARANTEES menu.
• This menu can be included to any standard AP or AR menus, thereby the guarantee
functionality can be accessed from the standard AP or AR responsibility.
• If the requirement is to access the guarantee solution through a separate

responsibility, then a new responsibility and a request group needs to be created.
This new responsibility can be created under AP or AR responsibility.
• Add the concurrent program - CLE: Greek Letters of Guarantee to the request
group attached to the AP or AR responsibility.
• It is mandatory to assign the Profile Option: MO Security Profile to the
responsibility from which guarantee functionality has to be accessed.
Solution Components
Letters of Guarantee solution can be classified into three broad processes:
1. Set Up
CLE: Letters of Guarantee Types Form: This form is used to define new guarantee
types. System allows the user to define different Guarantee Types based on their
requirement. While defining guarantee type key information like letter type, ledger
name, accounting information are captured. The Letters of Guarantee Type defines
whether our company issued it and it is given to a customer, supplier or other, or a
customer, supplier or other received it from our company.
2. Transactions
CLE: Letters of Guarantee Master File form: This form is used to enter the information
about the Letters of Guarantee received or issued. This form captures critical
information like the letter number, bearer category, name of the supplier / customer, site
information and the amount of guarantee.
CLE: Letters of Guarantee Transactions form: This form is used to perform transactions on
an existing Letters of Guarantee. Most of the information in this form defaults from earlier
forms based on the letter number selected except for the transaction related
information like transaction type, transaction date, transaction amount and GL date, which
need to be entered by the user while creating the transaction.
3. Inquiry and Reporting
CLE: Letters of Guarantee Inquiry form: This is a View -only form and is used to query
information about Letters of Guarantee. System provides a drill down feature wherein
all the transactions for a particular letter can be viewed by clicking the Transaction
Details button.
CLE: Letters of Guarantee Report displays all information about Letters of Guarantee in the
prescribed format. This report can be run for a bearer category, or a particular letter or a
range of letters or on the basis of the issue date of letter.
CLE: Letters of Guarantee Types Form
Functionality
• CLE Letters of Guarantee Types form is used to define new guarantee types.
• A Guarantee type is specific to a ledger.

• The Value assigned in the field 'letters type' decides whether this letter type is used
for receipt or issue of Letters of Guarantee.
• Uniqueness of the Letters of Guarantee type is maintained at the combination of

ledger, letter type and code.
• A Letters of Guarantee type can be end-dated by entering a date in the "Effective

Date To" field. An end-dated letter type is not available in the list of value for
selection in the subsequent forms.
• "Takes Part in Credit Check" check box is for information only. No specific logic has
been built in this solution to include this in the credit check process in Order
Management.
• While defining the letters of guarantee type user needs to enter the account code
combination, which is used for the guarantee account and also the offset accounting
combination.
• Whenever a transaction is created one side of the accounting entry is guarantee

account and the other side is offset account. For any type of transaction performed
against a guarantee, an accounting entry is created and transferred to General
Ledger. Accounting entries created during the transaction performed with this
guarantee type is transferred to the ledger selected in this form
• Accounting entries in the General Ledger are created with the journal source and
category selected in this form.
User Procedure
Ledger - This is a mandatory field. Values available for selection in this LOV are the
Primary Ledgers, which are assigned to the operating units included in the MO Security
Profile attached to the responsibility.
Effective Date To: This is an optional field and this is used to end date a Letter Type. An
end dated letter type is not available for selection in the subsequent forms after that
date.
Validation for this Field:

• Date: Date entered in this field must be equal to or greater than the system date
thereby system ensures that a letter type cannot be end dated with a date earlier
than the system date.
• Code: This is a mandatory and free-text field to capture the letter type code.
• Letter Type: This is a mandatory field and there are two possible values: Receive
and Issue. Default value is Receive. Value selected in this field decides whether this
letter type is used for a Receipt type or Issue type Letters of Guarantee.
• Description: This is a mandatory and free-text field to capture the letter type code
description.
• Takes Part in Credit Check: This is an optional check box.

• Account Code Combination for the Guarantee Account: This is a mandatory field
and the values in the list of value is defaulted from the Chart of Account assigned to
the ledger selected in the Ledger field.
Validations for this Field:

• The list of values for natural account displays only those accounts, which are not
marked as a parent account and accounts for which Allow Posting flag is enabled in the
accounting flexfield.
• System checks for violation of cross validation rules defined, if any. If the selected
account code combination violates the cross validation, rule system prompts the
error message defined in the cross validation rule and the transaction cannot be
completed.
Debit or Credit of Guarantee Account Per Transaction Type - This set up decides
whether the guarantee account is debited or credited for each transaction type.
• Deliver to Beneficiary
• Return to Beneficiary
• Amount Reduction
• Amount Increase
• Liquidation

Debit or Credit indicates whether the guarantee account is debited or credited for a
particular transaction type. This is a user enterable field and there is no control or check
from the system to check the correctness of debit or credit selected for each transaction
type. The responsibility for the correct setup and creation of accounting entries lies with the
person doing the setup. The only validation available is that the system will not
allow saving the letter Type. If all the values are selected as either debit or credit,
system expects there must be at least one value in the opposite Side.
Account Code Combination for the Offset Account - This is a mandatory field and the
values in the list of value is defaulted from the Chart of Account assigned to the ledger
selected in the Ledger field.
• In the accounting flexfield the list of values for natural account displays only those
accounts, which are not marked as a Parent Account, and accounts for which Allow
Posting Flag is enabled.
• System checks for violation of cross validation rules defined, if any. If the selected
account code combination violates the cross validation rule, system prompts the
error message defined in the cross validation rule and the transaction cannot be
completed.
Journal Source - Journal entries created for the transactions performed with Journal
Source guarantee type is created with this journal source.
Journal Category - Journal entries created for the transactions performed with Journal
Category guarantee type is created with this journal.
Exceptions
Exception Exception Message
If the combination of ledger, code and letter A code already exists for the combination of
type are already existing and the user tries to ledger, letter type and code. Please enter a
create with the same combination. unique name.
If a date earlier than the system date is entered Effective date must not be earlier than the
in the "Effective Date To" field type. system date.
If all the values are selected as either debit or Please correct the debit / credit Information.
credit, system expects there must be at least
one value in the opposite side (either one
credit or one debit).
CLE: Letters of Guarantee Master File
Functionality
CLE: Letters of Guarantee Master File Form is used to enter the information about the
Letters of Guarantee received or letter issued by the organization. An organization can
receive Letters of Guarantee from a supplier, or customer /or others. An organization can
issue Letters of Guarantee to a supplier, or customer / or others
• Letter - A letter of guarantee is a letter of credit opened in a bank, which holds in
reserve the amount of the guarantee on a specific account till the maturity date of
the guarantee.
• Check - The guarantee check is an actual check given to the beneficiary, which
remains in the possession of the beneficiary until it is returned to the bearer or till it
gets liquidated.
• Bearer category / Issued To: Any one of these two fields becomes mandatory based
on the letter type selected in the letter description field. Possible values in the

Bearer Category field are Bearer Supplier, Bearer Customer and Others. Similarly,
values in the "Issued To" field are Supplier, Customer and Others.
• Non-functional Currency - If a non-functional currency is selected, a field amount

in Euro gets displayed and this is a mandatory field, user needs to enter the
converted amount in Euro in this field.
• Expiration date - Letters of Guarantee can have an expiration date, if the letter has
an expiration date and the same is captured in the "Expiration Date" field, or if the
letter has no expiration date the "Never Expires" check Box is ticked. By enabling
this check box, the "Expiration Date" field becomes optional.
• If the Letter status is "Not Used", then all the fields in this form can be updated. If
the letter status is "Open", then only Comments, Expiration Date and Never Expires
fields can be updated. If the letter status is "Closed", then none of the fields can be
updated.
• Letters of Guarantee's statuses:
Letters of Guarantee Status Description
Not Used This is the "Initial" status of a letter.
Open Changes to OPEN as soon as it is delivered to

the beneficiary.
Close When the guarantee is returned to bearer or

gets liquidated.
User Procedure
Operating Unit - This is a mandatory field and the list of value contains all the
operating units attached to the MO Security Profile. Security Profile value is derived
from the Profile Option: MO Security Profile attached to the responsibility.
Issuer - This is a mandatory field and the list of value contains all the banks defined in
the system. The list of value contains both internal and external banks.
Branch - This is a mandatory field and the list of value contains all the branches defined for
the bank selected in the earlier field is available for selection.
Letter Description - This is a mandatory field and the list of value contains all the active
letter types defined in the system.
Letter Types, which are end dated, are not available for selection after the end date.
Letter Body - This is a mandatory field and the list of value contains two values: "Letter"
and "Check".
Bearer Category - Behavior of this field is dependent on the value selected in the Letter
Description field. If a letter type defined as a Receive has been selected, then this field
becomes mandatory. The list of value has three values - Bearer Customer, Bearer
Supplier and Bearer Other.
Issued To - Behavior of this field is dependent on the value selected in the Letter
Description field. If a letter type defined as Issue has been selected, then this field
becomes mandatory. The list of value has three values - Customer, Supplier and Other.

Customer Number - This field becomes mandatory if the "Value Bearer Customer" or "
Customer" is selected in the fields "Bearer Category" and "Issued To" respectively. List of
value contains the entire customers having an Active site in the operating unit
selected. List of value displays both Customer Code and Name.
Customer Name - This field becomes mandatory if the "Value Bearer Customer" or "
Customer" is selected in the fields "Bearer Category" and "Issued To" respectively. List
of value contains the entire customers having an Active site in the operating unit
selected.
Customer Site - This field becomes mandatory, if the "Value Bearer Customer" or "
Customer "is selected in the fields "Bearer Category" and Issued To respectively. List of
value contains all the Active sites for the customer selected.
Supplier Number - This field becomes mandatory, if the "Value Bearer Supplier" or "
Supplier" is selected in the fields "Bearer Category" and "Issued To" respectively. List of
value contains all the suppliers having an Active site in the operating unit selected. List of
value displays both Supplier Code and Name.
Supplier Name - This field becomes mandatory, if the "Value Bearer Supplier" or
Supplier is selected in the fields Bearer Category and Issued To respectively. List of
value contains all the suppliers having an Active site in the Operating Unit selected.
Supplier Site - This field becomes mandatory, if the "Value Bearer Supplier" or "Supplier " is
selected in the fields "Bearer Category" and "Issued To" respectively. List of value contains
all the Active sites for the supplier selected.
Other - This field becomes mandatory, if the "Value Bearer Other" or "Other" is selected
in the fields "Bearer Category" and "Issued To" respectively. This is a free text field.
Letter Number - This is a mandatory field and accepts numerical and alphanumeric
values.
Validations for this field are:

Date of Issue - This is a mandatory field and captures the date of issue of the letter.
Currency - This is a mandatory field and captures the currency of the letter.
Amount - This is a mandatory field and captures the amount of the letter.
Amount in Euro - If the currency selected in the currency Field is other than EUR, this
field gets displayed. This is a mandatory field. User needs to enter the converted
amount in Euro in this field.
Never Expires & Expiration Date - The Letters of Guarantee can have an expiration
date. If the letters have an expiration date, the same is captured in the Expiration Date
field. If the letter has no expiration date, the check Box 'Never Expires " is ticked. By
ticking this check box, the Expiration Date field becomes optional.
Purpose - This field allows the user to capture in short the reason for this guarantee
document. For example: for the guarantee of the Project XXXX's good completion.
Comments - This field allows the user to capture any comments even on a later day
from the date of creation, on any situations and details that may have risen for the
specific guarantee instrument.
Exceptions
If Letter Number and Bearer are already This combination of Bearer Category and
existing and the user is trying to enter the Letter Number already exists. Please enter a
same record. unique combination.
If the Letter Issue Date is greater than the Issue date must not be greater than the
Effective To Date of the Letter Type. Effective To Date of the Letter Type.
If the expiration date entered is less than the Expiration date must be greater than issue
letter issue date. date.
CLE: Letters of Guarantee Transaction Form
Functionality
CLE: Letters of Guarantee Transactions form is used to perform transaction on an
existing Letters of Guarantee. Most of the information in this form defaults from earlier
forms when a Letters of Guarantee is selected. Transaction related information like
Transaction Type, Transaction Date, Transaction Amount and GL Date are entered while
entering the transaction.
There are five possible transaction types that can be performed on a Letters of
Guarantee:
Transaction Type What should be the Letter What will be the Letter
Status Before the Status After the Transaction
Transaction is Made is Made
Receipt from bearer / Deliver Not Used Open

to Beneficiary
Amount Increase Open Open
Amount reduction Open Open

Transaction Type What should be the Letter What will be the Letter
Status Before the Status After the Transaction
Transaction is Made is Made
Return to Beneficiary Open Closed
Liquidation Open Closed
• Amount - Original amount of the Guarantee.
• Open Amount - Latest Open amount field gets updated after every transaction
done with this Letters of Guarantee
• Transaction Amount - Amount of the current transaction
• Amount in Euro - This field becomes mandatory for all transactions where in the
currency of the letter is not EURO in such cases user has to enter the converted
amount in EURO in this field.
• Cancel Transaction functionality is used to rectify any errors occurred while

entering a transaction
• Letter with "Closed" status is not available in the list of value for the letter number
field as no transactions can be performed against these letters.
User Procedure
Letter Number - This is a mandatory field. List of value contains all the letters, which
are in "Open" and "Not Used" status.
Cancelled - This checkbox is enabled, once a Transaction has been cancelled and
successfully transferred to General Ledger. All the fields are non-updateable for a
cancelled transaction.
Letter Type- This is a non-updateable field and value defaults based on the letter
number selected.
Letter Body - This is a non-updateable field and value defaults based on letter number
selected.
Issuer Name- This is a non-updateable field and value defaults based on the letter
number selected.
Branch-This is a non-updateable field and value defaults based on the letter number
selected.
Bearer - This is a non-updateable field and value defaults based on the letter number
selected.
Date of Issue - This is a non-updateable field and value defaults based on the letter
number selected.
Expiration Date - This is a non-updateable field and value defaults based on the letter
number selected.
Amount - This is a non-updateable field and value defaults based on the letter number

selected.
Open Amount - This is a non-updateable field and value defaults based on the letter
number selected.
Status - This field displays the existing status of the letter selected. This is a
non-updateable field and value defaults based on the letter number selected.
Transaction Type - This is a mandatory field and the list of value contains the following
values:
• Receipt from bearer / Deliver to Beneficiary
• Amount Increase
• Amount Reduction
• Return to Beneficiary
• Liquidation
Transaction Date - This is a mandatory field and system ensures that the transaction
date is the same as or greater than the date of issue of the letter.
Transaction Amount - This is the field where the transaction amount is entered or
defaulted based on the transaction type.
Transaction Type Selected Transaction Amount Field
Receipt from bearer / Deliver to Beneficiary Open amount defaults as the transaction
amount.
Amount Increase This is a mandatory field and the user has to

enter the transaction amount.
Amount Reduction This is a mandatory field and the user has to

enter the transaction amount.
Return to Beneficiary Open amount defaults as the transaction

amount.
Liquidation Open amount defaults as the transaction

amount.
GL Date - This is a mandatory field and system validates that the GL Period for the date
selected is in Open status.
Debit Account - This is a non-updatable field and value defaults based on the letter
number selected.
Credit Account - This is a non-updateable field and value defaults based on the letter
number selected.
Update General Ledger: Clicking this button executes the creation and transfer of
accounting entries to General Ledger. The following actions are performed:
• Creates a journal entry based on the accounting information derived from the
guarantee type.
• This executes the Journal Import program. Journal entry is created using the journal
batch source and journal category attached in the Letter Type Definition form.
• Journals are created in EURO currency. Only the transactions for ledgers with
EURO as functional currency are selected.
• Journal is in Unposted status, user needs to query these journals and post in
General Ledger.
• Creation of the Journal entry cannot be undone.
• GL Update Flag: Once the Update General Ledger has been completed, the check
box "Update GL" gets ticked. This indicates whether the transaction is accounted or
not.
• Cancel Transaction: This button is available only for those transactions, which have
been updated to General Ledger. Clicking this button executes the creation and
transfer of accounting entries to General Ledger.
• Whenever a transaction is cancelled, a new Reversal Journal is created.
• This process executes the Journal Import Program. Journal entry is created using
the journal batch source and journal category attached in the Letter Type Definition
Form.
• Reversal Journals is created in EURO Currency.
• While creating the reversal journal change Sign method is used whereby Debit /
Credit side of the account is the same as the original transaction journal, but the
sign of the amount is changed.
• Journal is in Unposted status, user needs to query these journals and post in
General Ledger.
• Journal entry cannot be created.
Below-mentioned naming convention is followed while creating the journal entries in

General Ledger:
Journal Batch Name - 'Letters of Guarantee'||Letter number||', '||GUARANTEE

TRANSACTION NAME||
Journal Batch Description = "Journal Import || Journal Source|| Request ID
Journal Name
• For New Transactions: 'Guarantee ' (Guarantee Number) (GL Category) (Currency)
• For Cancelled Transactions: Cancel of Guarantee (Guarantee number) (GL

Category) (Currency)
Journal Description - (Transaction Type) (Bearer Category) (Bearer Name)
Journal Line Description - (Transaction Type) (Bearer Category) (Bearer Name)
Exceptions
Transaction date is less than date of issue Transaction date must be greater or equal of
issue date.
Transaction date entered by the user is not in There is no open GL period for this
Open GL Period. transaction date.
The GL Date entered by the user is not in There is no open GL period for this GL date.
Open GL Period.
When there is a problem transferring to GL Error during transfer to GL process.

using Journal Import through the form.
A problem in canceling transaction. Error during cancellation process.
The Transaction / GL Date is earlier than the GL Date must not be earlier than the Letter
Letter Issue Date. issue date.
The user tries to perform a transaction with an With this status, selected Transaction type
Invalid status for that Transaction Type. cannot be performed.
CLE: Letters of Guarantee Inquiry Form
Functionality
• Letter Number
• Takes part in the Credit Check process
• Status
• Operating Unit
• Issuer
• Letter type
• Letter Body
• Issued To
• Bearer Category
• Customer Number
• Customer Name
• Site
• Supplier Number
• Site
• Other
• Issue Date
• Amount
• Currency
• Amount in Euro
• Open Amount in Euro
• Indefinite Time
• Expiration Date

User Procedure
By clicking at "Transaction Details", a new form opens, which displays the details of all the
transactions performed for that Letter.

CLE: Letters of Guarantee Analytical Report
Functionality
Objective of this report is to display the information about Letters of Guarantee.
The report is a part of Standard Request Submission (SRS). This report is added to the
request group attached to the responsibility to which the Guarantee Menus are added.
This report can be run for a specific bearer category, range of letters, range of suppliers or
customers or a specific date range.
Data under the Financial Statement region is displayed only after the accounting and
transferring of data to general ledger.
Report Parameters
Operating Unit No Select the organization for which the report runs. The
list of values contains the organizations, belonging to
the MO: Security Profile.
Third Party Category Yes The list of values contains:
• Bearer Customer
• Bearer Supplier
• Bearer Other
• Issued to Customer
• Issued to Supplier
• Issued to Other
From Third Party No Values available for selection in the list of value is
dependent on the value selected in the Third Party
Category parameter.
To Third Party No Values available for selection in the list of value is

dependent on the value selected in the Third Party
Category parameter.
Issue Date From No The Letter issue date is entered in this parameter.
Issue Date To No The Letter issue date is entered in this parameter.
From Letter Number No The list of values is dependent on the value selected in
the third party category parameter. If "Bearer Customer
" is selected in the Third Party Category parameter,
then all Letters of Guarantee received from customers
are available in the List of value for selection. This
parameter is enabled only after value is selected for the
" From Third Party" and "To Third Party" parameter.
Letter numbers, which belong to the selected third
party, are listed in the LOV.

To Letter Number No The list of values is dependent on the value selected in

the Third Party Category parameter. If "Bearer
Customer" is selected in the "Third Party Category"
Parameter, then all Letters of Guarantee received from
customers is available in the list of value for selection.
This parameter is enabled only after value is selected for
the Parameter " From Third Party" and "To Third Party".
Letter numbers, which belong to the selected third party,
are listed in the LOV.
Report Headings
Report heading is "Letters of Guarantee's Analytical Statement". This is printed in all the
Pages.
Column Headings
Trader - Name of the Trader.
Site - Site / Location details.
Letter Number - Letter Number.

Issuer-Name of the Bank, which has issued the Letters of Guarantee.
Date of Issue- Date on which the Letters of Guarantee was issued.
Expiration Date-Letter Expiration Date.
Letter Body- Letter Body.

Letter Description-Description of the letter.
Purpose-Purpose.
Original Amount-Original amount of the letter.
Open Amount (EUR)- Latest Updated amount i.e. Original Amount and the impact of all
the Transactions happened on that Letter.
Transaction Type-Type of Transaction Performed.
Transaction Date-Transaction Date
Transaction Amount- Transaction Amount .

Sort Condition
The report is sorted by trader's category (Bearer Customer/Supplier/other/Ourselves),

and then by Trader's Name (Alphabetically).
Totals/Report Totals.
• Category Total - Total of the original amount and total of the open amount of the
Guarantee.
• Guarantee's Nominal Value -Original amount of the guarantee.
• Guarantee's Open Amount - Latest updated amount of the guarantee.
• Total- Total of the amount displayed along with the account code combination.
Summary Section
The report displays the accounting information, debit and credit amount under the Sub
Heading Financial Statement for all accounted guarantee transactions.

10
GENERAL GL JOURNAL
Requirement
The requirements are as follows:
• To display carri ed forward balances on the basis of the Reporting sequence

names.
• The adjustment periods’ carried forward balances also need to be handl ed in
the report in the sam e way as it is handled for the non -adjustment periods.
The requi rem ent is to build the CLE: General GL Journal as it is developed i n
standard (Regional Localizations), where in for a particular peri od and GL date,
and for the respecti ve account code combi nations, the entered and accounted
debit, credit balancesare displ ayed, and the balances are carried forward on the
basis of accounting sequencenumber and name. In addition, the solution is
required to display the year to date carried forward balances by Reporti ng
Sequence Name and also to show the carried forward balances adjustment peri
ods as well.
Solution Overview
The solution is a report, where the journals are displ ayed on the basis of
Reporting Sequence Names for each period, and also for the third party
information. An enhancem ent on the existing global journals and thi rd party
report (Daily Journal Book Report) is done to show the carried forward bal ances
for the adjustment peri ods (year opening/closing). It also includes year todate
carried forward bal ances by the Reporting Sequence Names.
Output
Along with report parameters in the header information, the following

information will be displayed:
Setup Steps
Note: The sequence i ndicated for the setup checklist applies only to the relevant steps
to be considered in implementi ng the CLE: General GL Journal. For each module
installed, consult the manuals for that module to determi ne the sequence of setup
steps. The section below gi ves overview of the setups required for CLE: General GL
Journal.
Step Setup Step Step Type Oracle E-Business Suite

Number
1 Apply Greece Add - on Required System Administrator
Localization on Patch
2 Assign the CLE: General GL Required System Administrator

Journal to the corresponding
Request Group of the
responsibility from which the
report needs to be run.
(Mandatory).
Functionality
Primary functionality of the report is to handle an enhancement of di spl aying the
carried forward balances on the basis of the Reporting Sequence Names and also
displaying the carri ed forward balances for the adj ustment periods as well. Hence, the
CLE: General GL Journal (Daily Journal Book report) shows the carried forward
balances for the adj ustment periods (year opening/closing), and also includes year to
date carri ed forward balances by the Reporting Sequence Names.
This report is not submitted on a date basis to tax authorities. However, duri ng a tax
audit it is requir ed to be pri nted for any specifi ed periods. This report is avail able
upon request and pri nted by the 15th day of the foll owi ng month for the m onth that
is requested.
The Reporting Sequence Nam e is linked with the journal categori es (Journal sources as
well ). This is done at the Accounting Setup M anager level, and is linked to the GL
sequencing context and S LA sequencing context. The balances are carried forward
from one peri od to the next period withi n each legal sequence nam e either these
periods are regular or adj usting or mixed (regular and adjusting) for the sequence.
The carried forward bal ances (Y TD) are displ ayed on the basis of the Reporting
Sequence Name as follows:
Period Reporting Carried Period Ending

Number Sequence Forward Balance
Balance
1 SEQ1 0 400
2 SEQ2 0 2000
3 SEQ3 2000 1500
4 SEQ4 400 100
In this case the carri ed fwd bal ance for both period 1 and 2 is 0 since these are the
starting bal ances for SEQ1 and SEQ2. The period 4 has carried forward bal ance (400)
from the ending balanc e from Period 1 (400). Similarly, for Period 3 has carried
forward balance (2000) from the endi ng balanc e from Peri od 2 (2000). At the end of
the report for the specific reporting sequence the Endi ng Report Total = Carried Fwd
Balanc e + PTD m ovement.
The CLE: General GL Journal looks like this after handli ng the carried forward balance
reporting sequence wise:
CLE: Ge neral Daily Journal

GL Journal Book
Current Carried PTD Amount Total Report From To Sequence
Forward Carried Sequence Number
Balance Forward Number
0.00 285,478,299.72 285,478,299.72 1 2
0.00 24,974,861.93 24,974,861.93 1 3158
24,974,861.93 23,076,912.98 48,051,774.91 3159 6317
48,051,774.91 130,679,158.13 178,730,933.04 6318 9489
178,730,933.04 35,927,571.48 214,658,504.52 9490 12630
214,658,504.52 43,966,300.43 258,624,804.95 12631 16136
258,624,804.95 75,858,763.26 334,483,568.21 16137 20187
334,483,568.21 47,150,165.58 381,633,733.79 20188 23762
381,633,733.79 21,172,288.46 402,806,022.25 23763 26206
402,806,022.25 52,398,280.61 455,204,302.86 26207 31246
455,204,302.86 23,341,352.20 478,545,655.06 31247 34551
478,545,655.06 30,520,347.55 509,066,002.61 34552 38549
509,066,002.61 65,272,874.70 574,338,877.31 38550 42791
285,478,299.72 615,616,945.49 901,095,245.21 3 628
The key consideration is that the user will run this report for a particular reporting
sequence and a particular peri od, at a time, and also the report is run for either
Adjustment/Non-adj ustment periods.
The report can be sorted on any order, at the discretion of the us er, but the default
sorting for the report ed sequenc e is by the GL date, accounti ng sequenc e nam e,
accounting sequence number, journal source, bal ance type, batch name, and batch
date.
Every journal in SLA and GL m ust have a uni que gapl ess Reporting Sequence Num
ber. More that one di fferent reporting sequence are created and linked to the respecti
ve journal categories for Non -adjustment periods and adjustment peri od’s respecti
vely or even mixed non-adj ustment and adjustment peri ods.
The SLA reporting sequences and GL reporting sequences are created for adjustment
/non-adj ustment journals (these adj ustments could be in Subl edger or GL) coul d be
segregated adj ustment periods/non -adj ustment periods. Hence, for each fiscal year,
more than one new reporting sequences need to be set -up i n both GL sequencing
context and SLA sequencing cont ext.
Separate sequences depending on company legal reporting requi rem ents are defined.
There coul d be separate book -sequence for “analytical” journals, non - “analytical”
journals and openi ng -closing journals. Adjusting and non-adjusting
peri ods could be included in the same sequenc e and carri ed forward balanc es are
based on reporting sequence and period sequence.
The user can create invoices in Accounts Payables and Accounts Recei vables, and then
can run the Create Accounting program from the res pecti ve m odul es, and transfer
the entri es to General Ledger and post them. The reporting sequences will be
generated using the SLA sequencing context defi ned.
Journals are created for di fferent code com binations for both adj ustment and non-
adjustment peri ods and are posted.
Prerequisites
The standard setups in General Ledger should exist. The GL and SLA Reporting
Sequences setups should exist.
User Procedure
Create GL Sequencing Context Reporting Sequences
• Refer to Oracle General Ledger User Gui de to create uni que gapl ess reporting
sequence numbers for the GL accounting entri es. More than one di fferent
reporting sequence is created and linked to the respecti ve journal categori es for
non- adjustment peri ods and adj ustment periods respecti vely or even mix of
both Non adjustment and adjustment peri ods.
• The user needs to create two separate cal endars one with 15 fiscal periods and
one with 14 fiscal peri ods. These calendars are used for three di fferent scenarios.
The description of the calendar creation and sequence setup is gi ven as follows:
Case A:
• 1st openi ng, 14th settlements, 15th closing are adj usting periods
• 2nd to 13th non-adjusting periods representing calendar mont hs.
• Natural accounts beginning with “9” are called analytical ledger accounts
• Natural accounts NOT beginning with “9” are called general ledger accounts
Rem ark: It is illegal to mix in the same journal natural accounts beginning with “9”
and not.
• 1st sequence for report called “opening closing journal book” where 1st , 15th
adjusting peri ods journals included
• 2nd sequence for report called “j ournal book” where 2nd to 14th (1 adj + 12 non -adj
)
peri ods journals are included of natural accounts NOT beginning with “9”.
• 3rd sequence for report called “analytical book” where 2nd to 14t h (1 adj + 12 non -
adj) peri ods journals are included of natural accounts beginning with “9”.
Case B:
• 1st openi ng, 14th closing are adjusting periods

• Natural accounts NOT beginning with “9” are called general ledger accounts
Rem ark: It is illegal to mix in the same journal natur al accounts beginning with “9”
and not.
• 2nd sequence for report called “j ournal book” where 2nd to 14th period (1 adj + 12
non-adj) journ als are included of natural accounts NOT beginning with “9”.
• 3rd sequence for report called “analytical book” where 2nd to 13t h non adjusting peri
ods journals are included of natural accounts beginning with “9”.
Case C:
• 1st openi ng, 14th closing are adjusting periods

Natural accounts NOT beginning with “9” are called general ledger accounts
Rem ark: It is illegal to mix in the same journal natural accounts beginning with “9”
and not.
• 2nd sequence for report called “j ournal book” where 2nd to 14th period (1 adj + 12
non-adj) journals are included of natural accounts NOT beginning with “9”. . For this
scenario there is no Analytical Accounting.
Create GL and SLA Reporting Sequences
Create GL and SLA reporting sequences separately for the respecti ve p eri ods irrel
evantly of the period type.
Create manual journals in General Ledger
Create journals in General ledger for di fferent account code combinations and di fferent
sequences.
Post the General Ledger Journals
Post all the manually created journals in General Ledger for the respecti ve sequences
and peri ods.
Clo se the General ledger periods
Close all the respecti ve General Ledger peri ods for which the journals have been
created. This is the poi nt where the reporti ng sequenc es are generat ed for the GL
journals. “Peri ods - Cl ose Peri od” and “Creat e Reporting Sequence Number”, both
these requests are kicked off, and reporting sequences are generated for the journals.
Run CL E: General GL Journal Report
• Navigate to Standard Request Submission F rom, in General Ledger Responsibility.
• Select “CLE: General GL Journal Report”.
• E nter the param eters and submit the request.

Report Parameters
Parameter Required Description
Ledger Yes Select the ledger (l edger name) and the report c an be run for
any ledger. (Possibl e to run the report for l edger sets, data
access sets as well).
Legal No Select the legal entity (legal entity name) for which the report
Entity shoul d run. The list of values for the legal entity is dependent
on the led ger nam e chosen.
Journal Entry
Yes This parameter displays all the available journal entry sources
Source for which the report shoul d run. The journals source LOV
contains “All ” as one value.
Show Yes This is an option whether to sho w the adjustment peri ods in
Adjustment the report or not.
Periods
Period Yes Select the start period from which the report shoul d run.
From
Period To Yes This parameter defaults to the same val ue as the peri od from
val ue, but it is the user's discretion to change the peri od to
value. This indicates the period up to which the report can run.
GL Date Yes This parameter autom atically defaults with the “Peri od from ”
From parameter value. For exam ple: If period from is selected as
“Jan-09”, the GL date from parameter val ue becomes “01 - Jan-
2009”. This indicates the start GL date from which the report
needs to run.
GL Date To Yes This parameter autom atically defaults with the “Peri od To”
parameter value. For exam ple: If period to is selected as “Dec -
09”, ”, the GL date to parameter val ue becomes “31 - Dec-
2009”. This indicates the end GL date till which the report
needs to run.
Accounting Yes Select the “Accounting Fl exfiel d From” account code

Flexfield combinati ons. This represents the low values for the accounts
From from which the report needs to start runni ng.
Accounting Yes Select the “Accounting Fl exfiel d To” account code combinati
Flexfield To ons. This represents the High val ues for the accounts, up to
which the report needs to run.
The list of values for this param eter dis plays the journal
Process No
Category categori es from which user can select the journal categori es
for which the report needs to run.
Event Class No Select the event class from XLA, which is relevant to the
particular journal.
Select the document sequenc e nam e for which the report

Document No
Sequence needs to run. If this paramet er is selected, then the report
Name runs for the specific docum ent sequenc e alone.
Select the accounting sequence name for which the report

Accounting No
Sequence needs to run. The list of val ues contains all the accounting
Name sequence names for the ledger.
The list of values contai ns val ues “Yes and “No”. User
Posting No
Status canselect whether the report needs to display only posted
journals or unposted journals.
The list of values contai n 3 values “Adjustment ”, “All”,

Accounting Yes
Period and “Normal ”. User can select whet her journals from Adj
Type usting Accounting Peri ods alone are to be displayed, or
Journals from both norm al and Adjustment accounting
peri ods or Journals from normal accounting periods only.
The list of values contai ns “Yes” and “No”. User can sel
Include No
Year to ect whet her the report needs to include the year to dat e
Date carri ed forward balances or not.
Carried
Forward
The list of values contai ns “Draft”, “Final” and “Invali d”.
Journal No
Entry The report runs based on this Journal entry status. The
Status reporting sequence param eter and adjustment peri od
parameters are dependent to this parameter as the
Reporting sequences are generated only when the GL
period is closed, whic h means the GL entries are posted
and accounting posted flag is final.
LOV contains the list of values of all the available

Reporting No
Sequence reporting sequence names (acti ve). User can select the
Name partic ular report sequence name for which the report
needs to run.
LOV contains all the segments in the accounting flex field

First No
Flexfield structure. User can select the first flex fiel d segment, which
Segment is displayed in the report.
Used
LOV contains all the segments in the accounting flex field
Second No
Flexfield structure, except the one chosen as the first fl exfiel d
Segment segment. User can select the second flex field segment,
Used which is displayed in the report.
LOV contains the all the segments in the accounting fl
Third No
Flexfield exfiel d structure, except the ones chosen as the first and
Segment second flexfi eld segments. User can select the third fl exfi
Used eld segment, which is displayed in the report.
LOV contains the val ues “Accounting Sequenc e Nam

First Report Yes
e”,“Accounting Sequence Num ber”, “Balance Type”,
Sort “Batch Date”, “Batch Nam e”, “GL Date”, and “Journal
Source”. User can select the first report Sort based on
which the report should be sorted. By default the report
sorts fi rst on the GL date.
LOV contains the val ues other than the first report sort
Second Yes
previously selected. User can select the second report sort
Report Sort based on which the report shoul d be sorted. By default the
report sorts on the accounting sequence name.
LOV contains the val ues other than the first and second
Third Yes
report sorts previ ously selected. User can sel ect the third
Report Sort report sort based on which the report should be sorted. By
default the report sorts on the Accounti ng Sequence
Num ber.
LOV contains the val ues other than the first, second and
Fourth Yes
third report sorts previously selected. User can select the
Report Sort fourth report sort based on which the report shoul d be
sorted. By default the report sorts on t he Journal Source.
LOV contains the val ues other than the first, second, third,
Fifth Yes
and fourth report sorts previously selected. User can select
Report Sort the fi fth report sort based on which the report should be
sorted. By default the report sorts on the Balance type.
Sixth Yes
fourth and fi fth report sorts previously selected. User can
Report Sort select the sixth report sort based on which the report
should
be sorted. By default the report sorts on the Batch Nam e.
Seventh Yes
fourth, fi fth and sixth report sorts previously selected.
Report Sort User can select the seventh report sort based on which the
report should be sorted. By default the report sorts on the
Batch
Date.
User enterable fiel d, wherei n user can enter the name, if

Created By No
necessary which shoul d be displ ayed in the report.
LOV contains two val ues “Yes” and “No”. You can specify
Group By Yes
whet her the report needs to be grouped by the peri od or
not.
User-ent erable field, wherei n user can enter the journal

Batch name No
batch nam e for which the report shoul d run.
User-ent erable field, wherei n user can enter the accounti ng

Accounting No sequence number from which the report shoul d start
Sequence running.
Number
From
User-ent erable field, wherei n user can enter the accounti ng
Accounting No
Sequence sequence number up to which the report shoul d run.
Number To
User-ent erable field, wherei n user can enter the document

Document No
Sequence sequence number from which the report shoul d start to
Number run.
From
User-ent erable field, wherei n user can enter the document

Document No sequence number up to which the report shoul d run.
Sequence
Number To
User-ent erable fields, where user can enter the creation date
Creation No from val ue.
Date From
User-ent erable fields, wherein user can enter the creation date
Creation No to value.
Date To
User-ent erable field, wherei n user can enter the entered

Entered No currency value. The report restricts the output to this entered
Currency currency alone.
Report Headings
All param eter val ues are displaye d:
Report Title: General GL Journal.
Period from to period to: For Period from – Peri od to.
Page: Current page/Last page.
Legal Entity: Legal Entity nam e gi ven at the parameter level.

Column Headings
Period Name: The period nam e for which the report runs.
GL Date: GL date for which the report is run.
Reporting Sequence Name: Reporting Sequenc e Nam e for the peri od. Reporting .
Sequence Number: Reporting Sequence Num ber for the peri od. Line: Line Number.
Account: The i ndi vidual accounts pertaini ng to the GL dates and Reporting Sequence.
Account De scription : Account descri ptions for the accounts displayed.
Line Descrip tion: Journal Line description
Third Party Number: Thi rd party num ber is retri eved from the Table
XLA_AW_LINES., based on the party type code. The thi rd party could be either a
suppli er/customer.
Third Party Name: Thi rd party name is retri eved from the Table XLA_AW_LINES.,
based on the party type code.
Third Party Currency: The currency used by the thi rd party.
Entered Debit: Entered debit amount in the journal.
Entered Credit: Ent ered credit am ount in the journal.
Accounted Debit: Accounted debit amount in the journal.
Accounted Credit: Accounted credit amount in the journal.

Totals/ Report Total s
o Each page has brought forward bal ance at the top of the page foll owed by the
carried forward balance at the end of the page.
o The page total is displayed before the carri ed forward bal ance, which is the total of
the accounted debits and accounted credit amounts.
o Carried forward bal ance is calculated as “Brought Forward Bal ance + Page
Totals = Carri ed F orward Balance”.
o Adjustment carried forwar d colum n displays the total adjustment carried forward
balance for the particular page.
Jo urn al Total:
o The total of the j ournal i.e the total of the entered debits, entered credits,
accounted debits, and accounted credits.
Perio d End total (Base d on end -G L date ):
o The totals of the period end (end-GL date), alone not the entire period.
Perio d Total:
o The totals of the entire period.
Rep ort Total:
This is the grand total, which is the entire report total, which is the summation of the period
totals.
Limitations
This report might take a lot of run time, if there is a large vol ume of data.
• It is at the user's discretion to run the report indi vi dually for adjustment/non -
adjustment peri ods separately.
• Only if the reporting sequence name is gi ven at the parameter level (optional
parameter), the report runs for the gi ven reporting sequence only, else the report by
default runs for all reporting sequences for the particular periods gi ven at the parameter
level.

122clegrfinug February 2016

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

122clegrfinug February 2016

Uploaded by

Copyright:

Available Formats

Oracle® EMEA Add-on Localizations

Financials User Guide for Greece

Part No. E49770-01

U.S. GOVERNMENT RIGHTS

Send Us Your Comments

1 Add-on Localizations Overview

3 Statutory Trial Balance File

4 VAT- Greek Tax Audit Report

5 Trial Balance with Unposted Transactions

6 Greek Bills Receivables Receipt Report

7 Greek Withholding Tax Letter

9 AP/AR Guarantee Processing

• Are the implementation steps correct and complete?

Send your comments to us using the electronic mail address: appsdoc_us@oracle.com

• Users of Oracle E-Business Suite

About this Add-on Localizations Manual

• Greek Tax Audit Report

• Greek Trial Balance with Unposted Transactions

• Greek Bills Receivables Receipt Report

• Greek Withholding Tax Letter Report

• Greek Turnover Reporting

• Greek General GL Journal

Related Information Sources

• Oracle E-Business Tax User Guide, Release 12.2

• Oracle Payables User Guide, Release 12.2

• Oracle Receivables User Guide, Release 12.2

• Oracle Financials for Europe User Guide, Release 12.2

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Greek Add-on Localizations

Serial Number Feature Components

1 CLE: Greek Statutory Trial Balance File

2 CLE: Greek Tax Audit Report

3 CLE: Greek Trial Balance with Unposted Transactions Report

4 CLE: Greek Bills Receivables Receipt Report

5 CLE: Greek Withholding Tax Letter Report

6 CLE: Greek Turnover Reporting

7 CLE: Letters of Guarantee

8 CLE: General GL Journal

Add-on Localizations Overview 1-1

1. Greek Statutory Trial Balance File

2. Greek Tax Audit Report

3. Greek Trial Balance with Unposted Transactions

4. Greek Bills Receivable Receipt Report

6. Greek Turnover Reporting

These requirements are satisfied by

• CLE: MYF setup OAF page

• CLE: MYF output Page

• CLE: Process MYF Concurrent Request

Output generated as Text files in a fixed formats:

7. Letters of Guarantee Solution

Add-on Localizations Overview 1-3

Assignment of Concurrent Programs/Concurrent Program Sets to Request

Program Name Oracle E-Business Suite

CLE: Greek Statutory Trial EMEA Add-on Localizations

CLE: Greek Tax Audit Report EMEA Add-on Localizations

CLE: Greek Trial Balance with EMEA Add-on Localizations

CLE: Greek Bills Receivables EMEA Add-on Localizations

CLE: Greek Withholding Tax EMEA Add-on Localizations

CLE: Greek Turnover EMEA Add-on Localizations

General Setup 2-1

CLE: Letters of Guarantee EMEA Add-on Localizations

Request Set Definition

Add Functions to Menu

Function: CLE Greece Turnover Reporting