Emea Consulting Localizations

Oracle® EMEA Consulting Localizations Cross-Countries LocalizationsUser GuideRelease 11.5.10.2Part No. E10522-01

March 2007

Oracle EMEA Consulting Localizations Cross-Countries Localizations User Guide, Release 11.5.10.2

Part No. E10522-01

Copyright © 2007, 2010, Oracle and/or its affiliates. All rights reserved.

Primary Author: Chandu Bellamkonda

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 RIGHTSPrograms, 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 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware 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.

iii

Contents

Send Us Your Comments

Preface

1 IntroductionForeword.................................................................................................................................... 1-1About this Localization Manual............................................................................................... 1-1User's Guides Related to This Consulting Localization...........................................................1-2Audience for this Manual ........................................................................................................ 1-2Installation................................................................................................................................. 1-2Consulting Localization Overview........................................................................................... 1-2

2 Reports and ProcessesCLE: ECE European Sales and Purchase Listing...................................................................... 2-1CLE: Account Analysis Report................................................................................................ 2-15CLE: Exchange Differences for AP Report..............................................................................2-24CLE: Exchange Differences for AR Report............................................................................. 2-29CLE: GL Unrealized Gain/loss Report.................................................................................... 2-34CLE: Intra-stat Report.............................................................................................................. 2-38CLE: Asset Accounting............................................................................................................ 2-47CLE: Prepayment Application.................................................................................................2-49CLE: Depreciation Rounding.................................................................................................. 2-51

3 Setting up Cross Country LocalizationsCLE: ECE European Sales / Purchase Listing Report................................................................3-1CLE: Intra-stat.......................................................................................................................... 3-28

iv

Index

v

Send Us Your Comments

Oracle EMEA Consulting Localizations Cross-Countries Localizations User Guide, Release 11.5.10.2Part No. E10522-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 andthe 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: [email protected]

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 officeand inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at www.oracle.com.

vii

Preface

Intended AudienceWelcome to Release 11.5.10.2 of the Oracle EMEA Consulting Localizations Cross-CountriesLocalizations User Guide.

This manual is a source of information about Czech, Slovakia and Turkey requirements and designed to provide useful guidance and assistance to:

• Consultants implementing Cross-Countries Consulting Localized components for 11i10 Oracle Applications

• Key user team of Oracle Applications

The Oracle EMEA Consulting Localizations (Cross-Countries Localization) guide assumes you have a basic understanding of core modules and the country specific localization requirement. If you have never used Oracle Applications, we suggest you to attend one or some of the Oracle Financial training classes available through Oracle Education Services

See Related Information Sources on page viii for more Oracle E-Business Suite product information.

Deaf/Hard of Hearing Access to Oracle Support ServicesTo reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.

viii

Documentation AccessibilityOur goal is to make Oracle products, services, and supporting documentation accessibleto all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access bythe disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in DocumentationScreen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in DocumentationThis documentation may contain links to Web sites of other companies or organizationsthat Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Structure1 Introduction2 Reports and Processes3 Setting up Cross Country Localizations

Related Information Sources

Do Not Use Database Tools to Modify Oracle E-Business Suite DataOracle 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

ix

Oracle E-Business Suite form can update many tables at once. But when you modify 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 whohas changed your information because SQL*Plus and other database tools do not keep arecord of changes.

Introduction 1-1

1Introduction

ForewordWelcome to the Release 11i of the Oracle® EMEA Consulting Localizations User Guide for Cross Countries Localizations. This user guide includes information to help you understand the following aspects of the Localization and to implement the Localization effectively for a customers.

Consulting Localizations Overview

Consulting Localizations Setup

Consulting Localization Reports

About this Localization ManualThe Oracle Applications-11i10 Czech Consulting localization User Reference Manual includes information you need to use Cross Countries Consulting Localization effectively. It is organized for easy access to detailed information about each of the following

CLE: AR ECE European Sales Listing (Oracle Receivables)

CLE: AR ECE European Purchase Listing (Oracle Payables)

CLE: Exchange Differences for AP Report (Oracle Payables)

CLE: Exchange Differences for AR Report (Oracle Receivables)

CLE: GL Unrealized Gain/loss Report (Oracle General Ledger)

CLE: Intrastat Report (Oracle Inventory)

CLE: Asset Accounting (Oracle Assets)

CLE: Prepayment Application (Oracle Receivables)

CLE: Depreciation Rounding (Oracle Assets)

1-2 Oracle EMEA Consulting Localizations Cross-Countries Localizations User Guide

This manual is to be referred in conjunction with Oracle Applications -11i10 Reference Manuals of the respective modules.

User's Guides Related to This Consulting LocalizationThis guide contains references to the following Oracle publications. Use the Release 11i versions of these guides unless otherwise specified.

Oracle General Ledger User's Guide

Oracle Payables User Guide

Oracle Receivables User Guide

Oracle Inventory User Guide

Oracle Assets User Guide

Audience for this Manual This manual is a source of information about Czech,Slovakia and Turkey requirements and designed to provide useful guidance and assistance to:

Consultants implementing Cross Countries Consulting Localized components for 11i10 Oracle Applications

Key user team of Oracle Applications

The Oracle EMEA Consulting Localizations (Cross Countries Localization) guide assumes you have a basic understanding of core modules and the country specific localization requirement. If you have never used Oracle Applications, we suggest you to attend one or some of the Oracle Financials training classes available through Oracle Education Services.

InstallationThis consulting localization is installed after the base install of Oracle e-Business Suite. The Cross Countries Localization patches to be applied are available for download fromMetalink. Please ensure the prerequisites are taken care before installing the patch, especially the product splicing for CLE (EMEA Consulting Localizations). Once the patches are installed, please ensure that the Post-installation steps are completed. These patches create Custom Descriptive Flexfield definitions for use to store the additional information; the user should not modify these forms at any time. The user needs 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.

Consulting Localization OverviewOracle® EMEA Consulting Localizations – Cross Countries Localization provides

Introduction 1-3

additional functionality to help customers from different countries in EMEA region to meet there legal and business requirements as a part of core Oracle Payables, Receivables, General Ledger, and Assets products. Cross Countries Consulting Localizations provides the functionality not available in core product but essential for a European customer. This User guide provides detail about setup and functionality of the following processes and reports.

CLE: AR ECE European Sales Listing (Oracle Receivables)

CLE: AR ECE European Purchasing Listing (Oracle Payables)

CLE: Exchange Differences for AP Report (Oracle Payables)

CLE: Exchange Differences for AR Report (Oracle Receivables)

CLE: GL Unrealized Gain/loss Report (Oracle General Ledger)

CLE: Intrastat Report (Oracle Inventory)

CLE: Asset Accounting (Oracle Assets)

CLE: Prepayment Application (Oracle Receivables)

CLE: Depreciation Rounding (Oracle Assets)

Reports and Processes 2-1

2Reports and Processes

CLE: ECE European Sales and Purchase ListingCLE: ECE European Sales Listing

The ECE EU Sales Listing lists all eligible sales transactions, totalized by Tax Identification Number of customer and Supply Code. Eligible transactions are those invoices for which:

The accounting for the invoice has been transferred to General Ledger.

The tax code for the transaction has been marked as an ESL transaction

Certain transactions viz. VAT prepayments need to be excluded from the ESL report. This is acheived using a LDFF on the Transaction Types. The LDFF "CLE: Additional Transation Type Information" needs to be explicitly set to 'No', to avoid reporting such transactions. All transaction types which are set to Null or Yes will continue to appear on the report.

The tax date is on or before end date of the reported period (quarter). Users should be able to run the ECE Sales Listing in preliminary mode to confirm the items to be reported, and in final mode to submit the report to the tax authorities. Once a transaction is printed on a final mode report, the transaction should not be printed on reports for subsequent reporting periods.

Users should be able to reprint a final mode report for a given reporting period, with exactly the same data on it. This includes transactions with tax dates in prior periods that were printed on the final mode report.

However, even if new transactions have been entered for the same reporting period since the final mode report was printed, these should not be displayed on the reprint report.

By contrast, new transactions entered between the preliminary and final mode runs of the report should indeed show up on the final report (as well as on subsequent reprints).


Pre-requisites

Users enter Tax Date in the AR Transaction Header GDF

Users enter Tax Date in the AP Invoice Header GDF

Users enter Tax Registration Number of customers on the address level (Bill to site use).If the program does not find sufficient information there, it should look for it at header level.

Users enter Tax Registration Number of suppliers on the site level. If the program does not find sufficient information there, it should look for it at header level.

Users can effectively differentiate transactions to be included by using VAT Tax Codes.

Users have entered first party domestic Tax Registration number in AR system Options,AP System Options, and also preferably at Legal Entity definition

User enters value for LDFF CLE: Transaction Type Information (set value for Include in ESL Report field)

Country codes

VAT Member State Code must be defined in Countries and Territories form for every EU member country. Only customers (and suppliers) from the countries with assigned VAT Member State Code are considered by ECE Sales and Purchases Listings. VAT Tax Codes.

The ECE_SUPPLY_CODE segment must be defined in AR Tax Codes GDF and AR Tax Codes GDF. The segment will use the flex value set based on the lookup codes table (lookup type ECE_SUPPLY_CODE).

AR and AP transactions that use tax codes marked in this GDF will be reported only. This requires new GDF at AR and AP Tax Code definition.

ESPL Reporting Calendar

The new ESPL Reporting Calendar with the Quarter period type must be defined. This calendar must be set up and designated at the set of books level.

This requires new GDF at SOB definition. The ESPL Reporting calendar will be used as a parameter for EU Sales and Purchases Listings.

VAT Tax Date

Transactions are considered by the EU Sales and Purchases Listings based on the Tax Date specified at transaction header level.

Users enter the tax reporting date in the Tax Date global flex field in the Oracle PayablesInvoice Workbench or the Oracle Receivables Transactions window.

Preliminary and Final Listings

Before running the final ECE Sales or Purchases Listing for a given quarter, users can run it in preliminary mode as many times as they wish.

Running EU Sales or Purchases Listing in the final mode results in marking selected


transactions as 'Reported'.

This requires new GDF at AR Transactions Lines and

AP Invoices Distributions.

Corrections

When ECE Sales or Purchases Listing is running for a given quarter all transactions belonging to the previous reporting period not marked as 'Reported' are listed.

These transactions will be reported in separate section of the report (ECE European Sales or Purchases Listing).

The report does not follow corrections due to wrongly entered or changed

Tax registration number in the customer/supplier master.

Parameters

Parameter Required Default Value LOV

ESPL Reporting Period

Yes Preliminary Translatable values:

• Preliminary

• Final

• Reprint

Yes Earliest period for which final ECE SalesListing has not been run.

Preliminary & Final: Period names in the ESPL Reporting Calendar for which final ECE European Sales Listing has not been run.Reprint: Period names in the ESPL Reporting Calendar for which final ECE European Sales Listing has beenrun

Reporting Level Yes Summary Translatable Values:

• Summary

• Detail


Report Mode

If a user chooses Preliminary for this parameter, the report only includes transactions that have not yet been printed on a final report. If the user chooses Final for this parameter, the report only includes transactions that have not yet been printed on a final report. The report marks the transactions selected for this report with the chosen ESPL reporting period. If the user chooses Reprint for this parameter, only the ESPL Reporting Period parameter is needed. The report only includes transactions that were printed on the Final report for the chosen ESPL reporting period. Detail reporting level can be chosen only when the report is run in Preliminary or Reprint mode.

Reporting Period

Valid values are period names from the ESPL reporting calender designated for the current set of books. If the report is being run by preliminary or final mode(see previousparameter), LOV, should only include periods for which the ECE Sales Listing has not been run in final mode, ie., periods which do not exist in the ESL Reported GDF on AR.

Transaction Lines. Transactions selected for the report should include only those transactions with Tax Date on or before the last date of the selected period. If the report is being run in Reprint mode, LOV should only include periods for which the ECE SalesListing has been run in final mode, i.e. periods, which exist in the ESL Reported GDF onAR Transaction Lines. Transactions selected for the report are all transactions for which the Final ESL GDF matches the chosen period.

Reporting Level

Detailed level of the report can be chosen in Preliminary and Reprint run of the report. All transactions meeting given criteria are listed. The summary report prints only the Summary by Tax Registration Number and Supply code, and the Summary by Supply code sections. The detail option prints only the detailed section of the suggested layout. This option's layouts are presented in the following section

Reporting Heading

The report prints in the upper left corner

• VAT payer – The name of the set of books from Legal Entity organization's accounting information

Address 1-3 of the VAT payer – 1-3 lines of the address from Legal Entity organization's location

Postal code of the VAT payer – postal code from the address from Legal Entity organization's location City of the VAT payer – city from the address from Legal Entity organization's location

Tax Registration number of the VAT payer – VAT Registration Number from Legal Entity organization's accounting information

The report prints the Report Title, centered on the first line.

The report prints the Report Date in the upper right corner.


Reporting period, which is the quarter that the report is being run for.

The report prints the Current Page /Total Number of Pages on the second line, below the report date.

The report prints the following parameter values, starting from the fourth line. These are only printed on the first page of the report:

Report Mode

Reporting Level

The report prints the Functional Currency Code below the parameters

• ESL Reporting Period

The report prints transactions, which were not previously reported for each related period in separate section. The report prints the reporting period name (the name ofthe period from ESPL Reporting calendar). ESL periods are presented in reverse chronological order, starting from the ESL Reporting Period selected in the parameters. For each ESL period, a row is printed with the ESL period name.

Report Heading• Column Headings – Detailed section

Within each ESL reporting period the report orders journals by the following order

1. Country code

2. Tax Registration number

3. Supply code

4. Invoice number

5. Tax code

• Sequence number

The sequence number of the record listed

• Country Code

VAT Member State Code of the customer's country (from the customer site). ECE Sales Listing considers only transactions to customers from the countries with assigned VAT Member State Code.

• Tax Registration number

Tax Registration Number from the 'Bill to' site use of the customer


• Customer Name

The customer name

• Supply Code

The meaning of the supply code from the ECE Supply Code GDF on AR Tax Codes

• Invoice Number

Transaction's number from the transaction header. In detailed reporting level the report prints all transactions (sum of the transaction lines by tax codes) meeting given criteria

• Invoice Date

The effective date of the transaction

• GL Date

Tax Code

The GL Date of the transaction

• Tax Date

The Tax Date entered in the global flex field at the transaction header level.

• Tax Code

The tax code derived from the tax type line of the transaction. Tax codes are presented in alphanumerical order

• Taxable Amount

The taxable amount of the transaction, in functional currency. Debit items are displayedas a positive amount. Credit items are displayed as a negative amount. The taxable amount is a summary of the transaction lines with the same Tax code in a transaction.

Column Headings – Summary by Tax Registration Number and Supply Code Section

Based on the information collected in the detailed section, this part totals transaction by Tax Registration number and Supply code. Within each ESL reporting period the reportlists transactions in the following order:

1. Country Code

2. Tax Registration Number

3. Supply Code

• Sequence number



• Country Code

VAT Member State Code of the customer's country (from the customer site). ECE Sales Listing considers only transactions to customers from the countries with assigned VAT Member State Code.


Tax Registration Number from the 'Bill to' site use of the customer

• Number of Transactions

Number of valid transactions for the customer. The valid transactions are those for which:

• Tax Date specified at the transaction header level falls between start date and end date of the particular period

• Tax codes for the transaction lines have assigned a supply code in ECE Supply Code GDF on AR Tax Codes

The tax code must be derived from the tax type line of the transaction to enable usage oftax groups. Transactions are grouped by tax registration number and supply codes.

• Supply Code

The meaning of the supply code from the ECE Supply Code GDF on AR Tax Codes.

• Taxable Amount

The taxable amount of the transaction, in functional currency. Debit items are displayedas a positive amount. Credit items are displayed as a negative amount. The taxable amount is a summary of the transaction lines for a Tax Registration number, with the same supply codes in an ESL reporting period

• Column Headings – Summary by Supply Code Section

• This section lists transactions by supply code for each ESL Period. The section sorts and groups Taxable Amounts by Supply Code.

• Supply Code

The meaning of the supply code from the ECE Supply Code GDF on AR Tax Codes.

• Taxable Amount

The taxable amount of the transaction, in functional currency. Debit items are displayedas a positive amount. Credit items are displayed as a negative amount. The taxable amount is a summary of the transaction lines for a supply code within an ESL reporting period

Rules and Examples


• Amounts

The report shows totals of the transactions for each Tax registration number and Supplycode. Sales invoices and similar transactions are considered by the report as positive numbers. Credit memos and other credit transactions are considered as negative numbers. If a transaction is printed in any of the reports in Final Mode, then the same transaction cannot be included in any other report. On Reprint mode, only the transactions listed in Final mode report will be reprinted.

Layout: ECE European Sales Listing


CLE: ECE European Purchases Listing

Overview

Report ECE European Purchases Listing prints taxable transactions that have been posted to Oracle General Ledger from Oracle Payable. It is used to prepare quarterly reports for tax authorities in ECE countries.

• Parameters


Report Mode Yes Preliminary Translatable values:

• Preliminary

• Final

• Reprint


ESPL Reporting Period

Yes Earliest period for which final ECE Purchases Listing has not been run.

Preliminary & Final: Period names in the ESPL Reporting Calendar for which final ECE European Purchases Listing has not been run.Reprint:Period names in the ESPL Reporting Calendar for which final ECE European Purchases Listing has been run

Reporting Level Yes Summary Translatable Values:

• Summary

• Detail

The hidden parameter is ESPL Reporting calendar set up at the SOB level.

• Report Mode

If a user chooses Preliminary for this parameter, the report only includes transactions that have not yet been printed on a final report. If the user chooses Final for this parameter, the report only includes transactions that have not yet been printed on a final report. The report marks the transactions selected for this report with the chosen ESPL reporting period. If the user chooses Reprint for this parameter, only the ESPL Reporting Period parameter is needed. The report only includes transactions that were printed on the Final report for the chosen ESPL reporting period.

• Reporting Period

Valid values are period names from the ESPL reporting calendar designated for the current set of books. If the report is being run in Preliminary or Final mode (see previous parameter), LOV should only include periods for which the ECE Purchases Listing has not been run in final mode, i.e. periods which do not exist in the EPL Reported GDF on AP Invoice Distributions. Transactions selected for the report should include only those invoices with Tax Date on or before the last date of the selected period. If the report is being run in Reprint mode, LOV should only include periods for which the ECE Purchases Listing has been run in final mode, i.e. periods, which exist in the EPL Reported GDF on AP Invoice Distributions. Transactions selected for the reportare all transactions for which the Final EPL GDF matches the chosen period.

• Reporting level


Detailed level of the report can be chosen in Preliminary and Reprint run of the report. All transactions meeting given criteria are listed. The summary report prints only the Summary by Tax Registration Number and Supply code, and the Summary by Supply code sections. The detail option prints only the detailed section of the suggested layout. This option's layouts are presented in the following section.

Report Heading

The report prints in the upper left corner:

Name of the VAT payer – The name of the set of books from Legal Entity organization's accounting information

Address 1-3 of the VAT payer – 1-3 lines of the address from Legal Entity organization's location

Postal code of the VAT payer – postal code from the address from Legal Entity organization's location

City of the VAT payer – city from the address from Legal Entity organization's location

Tax Registration number of the VAT payer – VAT Registration Number from Legal Entity organization's accounting information

The report prints the Report Title, centered on the first line.

The report prints the Report Date in the upper right corner.

Reporting period, which is the quarter that the report is being run for.

The report prints the Current Page / Total Number of Pages on the second line, below the report date.

The report prints the following parameter values, starting from the fourth line. These are only printed on the first page of the report.

Report Mode

Reporting Level

The report prints the functional currency code below the parameters.

Row Heading

EPL Reporting Period

The report prints transactions, which were not previously reported for each related period in separate section. The report prints the reporting period name (the name of the period from ESPL Reporting calendar). EPL periods are presented in reverse chronological order, starting from the EPL Reporting Period selected in the parameters. For each EPL period, a row is printed with the EPL period name.

• Column Headings – Detailed section

Within each EPL reporting period the report orders journals by the following order

• Country code



• Supply code

• Invoice number

• Tax code

• Sequence number

The sequence number of the record listed.

• Country Code

VAT Member State Code of the supplier's country (from the supplier site). ECE Purchases Listing considers only invoices from suppliers from the countries with assigned VAT Member State Code.


Tax Registration Number from the site of the supplier

• Supplier Name

The supplier name

• Supply Code

The meaning of the supply code from the ECE Supply Code GDF on AP Tax Codes.

• Invoice Number

Invoice number from the invoice header. In detailed reporting level the report prints all transactions (sum of the transaction lines by tax codes) meeting given criteria.

• Invoice Date

The date of the invoice.

• GL Date

The GL Date of the transaction

• Tax Date

The Tax Date entered in the global flex field at the invoice header level

• Tax Code

The tax code derived from the distribution line. Tax codes are presented in alphanumerical order

• Taxable Amount


The taxable amount of the transaction, in functional currency. Standard invoices and similar transactions are displayed as a positive amount. Credit memos and other credit transactions are displayed as a negative amount. The taxable amount is a summary of the transaction lines with the same Tax code in a transaction.

• Column Headings – Summary by Tax Registration Number and Supply Code Section

Based on the information collected in the detailed section, this part totals transaction by Tax Registration number and Supply code. Within each EPL reporting period the reportlists transactions in the following order:

• 1. Country Code

• 2. Tax Registration Number

3. Supply Code

• Sequence number


• Country Code

VAT Member State Code of the supplier's country (from the supplier site). ECE Purchases Listing considers only transactions to suppliers from the countries with assigned VAT Member State Code


Tax Registration Number from the site of the supplier.

• Number of Transactions

Number of valid transactions for the supplier. The valid transactions are those for which:

• Tax Date specified at the invoice header level falls between start date and end date of the particular period.

• Tax codes for the transaction lines have assigned a supply code in ECE Supply Code GDF on AP Tax Codes. Transactions are grouped by tax registration number and supply codes

• Supply Code

The 'meaning' of the supply code from ECE Supply Code GDF on AP Tax Codes.

• Taxable Amount

Taxable amount of transaction (in functional currency). Standard invoices and similar transactions are displayed as a positive amount. Credit memos and other credit


transactions are displayed as a negative amount. The taxable amount is a summary of the distribution lines for a Tax Registration number, with the same supply codes in an ESL reporting period.

• Column Headings – Summary by Supply Code Section

This section lists transactions by supply code for each EPL Period. The section sorts and groups Taxable Amounts by Supply Code.

• Supply Code

The 'meaning' of supply code from the ECE Supply Code GDF on AP Tax Codes.

• Taxable Amount

The taxable amount of the transaction, in functional currency. Standard invoices and similar transactions are displayed as a positive amount. Credit memos and other credit transactions are displayed as a negative amount. The taxable amount is a summary of the distribution lines for a supply code within an EPL reporting period. Layout as givenbelow

Layout


CLE: Account Analysis ReportThis is a single report and three layouts

If the Territory profile is Czech, the Detailed Account Analysis report (CZ-39), has to be displayed

If the Territory profile is Turkey, the parameter field that gives an option to the user to choose between Account Analysis Report (TR-04) and Sub-ledger Report (TR-05) shouldbe given. By default the parameter form should show Account Analysis Report (TR-04)

The Parameter form displays the parameters required for all the three reports. Depending on the Territory and an additional parameter field which gives the user to choose between TR-04 and TR-05 reports, the required parameter fields should get enabled and the user should not be able to enter any information into the fields which are not required

The Detailed Account Analysis report (CZ-39) created in General Ledger module, whichin a substantial manner expands the display options of accounting transactions details required for Czech Legislation

The Account Analysis Report (TR-04), lists all journal entries (for the date range selectedat report submission) in the required order, grouping them under 3-digit summary accounts. Beginning balances and balances at the end of each accounting period in the selected range are provided at 3-digit summary account level.

The Sub-ledger Report (TR-05) lists all opening/closing balances of accounts in a selected account/date range along with all journal entry lines that affect this range.

The following information is listed for each journal line: Journal date, Journal category, Document Sequence Number, Account, Account description, Journal line description and debit/credit amount. A running total is also provided.

Parameters

Detailed Account Analysis Report (CZ-39)


Parameter Description Required Default Value LOV

Accounting flexfield from

Initial value of accounting flexfield

Yes KFF of current set of books

Accounting flexfield to

Initial value of accounting flexfield

Yes KFF of current set of books

Period from Accounting period from date

Yes List of open periods

Period to Accounting period to date

Yes List of open periods

From GL date From General Ledger date.

No

To GL date To General Ledger date.

No

Report currency Functional currency or STAT currency (or Set of Books MRC currency).

Yes Functional currency

List of Currencies

Entered currency Transaction currency

No List of Currencies

Amount from Minimum amount in functional currency

No

Amount to Maximum amount in functional currency

No

Supplier Supplier's name No Suppliers List

Customer Customer's name

No Customers List


Source Transaction source.

No A (Actual) Transaction Source (Actual/Budget/Encumbrance)

Category Transaction category

No Transaction Category

Sort by Sorting mode (by date or amount). By datewill be set as a default in ascending order).

No Date Date / Amount

No. of records In case of ordering by amount it is convenient to seta number of displayed records

No

Account Analysis Report (Kebir Defteri)


Balancing Segment value

First 3 digits of Natural AccountSegment

No

Start Date Beginning of the date range

No

End Date Ending of the date rangE

No

Subledger Report (Muavin)



Currency Code Currency Code No

Balance Type Balance Type No

Budget or Encumbrance Name

For Budget and Encumbrance balance types

No

Budget or Encumbrance Name

For Budget and Encumbrance balance types

No

Starting Period Accounting period from date

No

Ending Period Accounting period to date

No

Accounting Flex field Range

Accounting Flexfield Range

No KFF of current set of books

Order by Criteria Order by Criteria- Natural Account segment, Balancing segment, Source in the ascending order of EffectiveDate, Category Name, Batch Name, Journal Name and Journal Line No.

No Natural AccountSegment, Balancing Segment, Source

Report Heading

Detailed Account Analysis A part of the heading is also a list of all parameters entered in accord with a subsection "Report parameters".

Set of Books name

Set of Books name followed by a functional currency (in brackets).

Report date

DD – MM - YYYY

Page


The report prints the Current Page / Total Number of Pages

Accounting flexfield from

Initial accounting flexfield.

Accounting flexfield to

Final accounting flexfield.

Report currency

Report currency (local or STAT).

Entered currency

Entered currency of transaction.

Period from-to

Initial-end period.

From-to GL date

Scope of GL dates.

Source

Transaction source.

Category

Transaction category.

Account

Account segment value.

Initial balance

Initial account balance, i.e. a summation of initial balances of all Accounting flexfields containing a given account.

Turnover Credit per period

Account turnover, i.e. a summation of credit turnovers of all Accounting flexfields containing a given account.

Turnover Debit per period

Account turnover, i.e. a summation of debit turnovers of all Accounting flexfields containing a given account.

Final balance

Final account balance, i.e. a summation of final balances of all Accounting flexfields containing a given account.

Column Headings

On every new page a column heading should be listed below a page heading.


GL date

General Ledger date.

Journal No.

Number of a General Ledger Journal.

Source

Transaction source.

Category

Transaction category.

Supplier/Customer

Supplier or customer name.

Invoice No.

Invoice number. In case of a supplier invoice it is a number assigned by a supplier (usually used as a variable symbol). In case of a customer invoice it is an invoice number (from a field "Number" on the form for entering of transactions).

Internal No.

In case of the activation of numbering an internal document number will be listed. In case of supplier invoices it is an internal number generated after the selection of a document category (i.e. invoice type). In case of customer invoices list a number from a field "Document number" on the form for entering of transactions.

Invoice date

Date of the issue of invoice.

Currency

Transaction currency.

Functional Amount Credit

Credit transaction amount converted into the functional currency.

Functional Amount Debit.

Debit transaction amount converted into the functional currency.

Entered amount Credit.

Credit transaction amount entered in the original currency. Entered amount Debit Debittransaction amount entered in the original currency.

Section

A section contains a record of transactions per accounting flexfield.

Subsections

A subsection contains all transactions for a chosen account value.


Summation levels

At the end of each section there will be a summation for transactions of a given accounting flexfield for a functional currency and Credit and Debit account balances. Atthe end of each subsection there will be a total summation for all transactions of a given accounting flexfield for a functional currency and Credit and Debit account balances.

Sorting

Main sorting will be determined by a parameter value in "Sort by", which can take on two values – Date and Amount. Date in ascending order is set as a default (i.e. entered value Date).

In case Amount is entered, data will be sorted in a descending order by the amounts expressed in a functional currency.Additional sorting within the main sorting is by a GLJournal number.

Layout


Report Header

Set of Books Name

Report Title

Date/Time Report was run

Page Number/Number of Pages

Summary Account

First 3 digits of the Natural Account (Summary Account)

Beginning Debit/Credit Balance for the summary account and date range

Accounting Period

Accounting Period Sequence (e.g 1 for January, 12 for December)

Debit/Credit Balances as at the end of accounting period

Journal Line

Date of Journal Record

Journal Document Sequence Number assigned for Legal Reporting

(all journals are assigned sequence numbers in the order of date, category and journal number)

Journal Category

Journal Document Sequence Number (System generated at journal entry)

Accounting Flex field

Accounting Flex field Description


Journal Description

Debit Amount

Credit Amount

Total Criteria

Period Total Debit

Period Total Credit

Order criteria

First 3 digits of the Natural Account Segment

Journal Effective Date

Document Sequence Number (assigned for Legal Reporting)

Journal Category

Document Sequence Number (System assigned)

Natural Account Segment

Report is listed in the following order:

OTHER REPORTS

Report Header

Set of Books Name

Report Title

Date/Time Report was run

Page Number/Number of Pages

Currency Code

Accounting Flexfield Range

Balance Type

Account Level

Accounting Flex field/Accounting Flex field Description

Balance Brought Forward as at start of the date range (Debit/Credit/Net(*))

Balance as at the end of the date range (Debit/Credit/Net(*))

Totals for transactions in the date range (Debit/Credit) (*) Debits – Credits

Journal Line Level

Date of Journal Record

Journal Category

Journal Document Sequence Number (System generated at journal entry)


Journal Description

Debit Amount

Credit Amount

Running Net (*) Amount

Total Criteria

Totals are provided at following levels:

Accounting Flexfield

Report

Order Criteria

Report is listed in the following order

Order By entered as parameter (Natural Account segment, Balancing segment, Source)

Journal Effective Date

Journal Category Name

Journal Batch Name

Journal Name

Journal Line Number

CLE: Exchange Differences for AP ReportThe revaluations process in the Oracle General Ledger creates journals for unrealized exchange gains/losses. There is legal requirement for disclosure of revaluation result by the list of open items affected by the revaluation; theirs initial exchange rate, revaluation exchange rate and revaluation difference (gains or losses).

Exchange rate differences on open items, according to the statutory accounting requirements, should be confirmed with list of such open items, where should be indicated: Supplier, invoice #, Internal Invoice #, date, Original Invoice rate, exchange rate, amount original, in foreign currency - open (unpaid) amount, in functional currency – open (unpaid) amounts with exchange rate at the beginning and closing of the period, for which calculation of exchange gains / losses is processed. Same procedure is followed for outstanding advances paid /received, as their unapplied amount are open items too.

Parameters

No. Parameter Required Default Value

LOV


1 Operation Unit N None LOV of all operation units of current set of books. If not filled, the report select data from all Operating units.

2 Revaluation Period

Y None These are GL Periods for selecting open invoices. The user can select the period for which he wants to run the report.

3 Currency N Blank LOV of enabled currencies without functional currency of current set of books. If not filled, the report select data for all currencies.

4 Rate Type Y None LOV of 1) Daily Rate Type fromLOV and this rate nameis defined by user in advance and 2) Period RateType

5 Daily Rate Type N None If user selects "Daily" in Rate Type Parameter, then all the Daily rates available in GL_DAILY_RATES. This is disabled if the user selects "Period" in Rate Type Parameter.

6 Daily Rate Date N Yes FND_STANDARD_DATE for selecting rate value..

7 Account From Y Blank Lowest account combination for determining range of accounts to be processed in report. Key Accounting FlexField should be provided tochoose combination. Security rules defined for current responsibility to be strictly applied for display values in LOV for every segment. Parameter Form should allow user to enter values


8 Account To Y Blank Default – copy of previous Parameter 5 combination. Highest account combination for determining range of accounts to be processed in report. Should be validated with rule: the value should be equal or greater than relevant value in the previous parameter("Account From:").Key Accounting FlexField should beprovided to choose combination. Security rules defined for current responsibility to be strictly applied for display values in LOV for every segment. Parameter Form should allow user to enter values not presented in the LOV (to be able use range limits

9 Grouping Level Y "Account" User should choose from a list of options:

• "2- digit account" – grouping by first two digits of the natural account segment value;

• "3- digit account" – grouping by first three digits of the natural account segment value;

10 Including invoicesin functional currency

N Blank We need this parameter to be able to reconcile GL balance in funcional currency to this report balancesIf there is enter YES the invoices in funcional currency are included

Report Heading (Operation Unit)

Set of Books Name

Operation Unit Name

Currency Rate type


Daily Rate Type

Daily Rate Date

Account from

Account to

Grouping level

Include Invoices in Functional Currency

Current system date, time

Page Number

Report Headings (Account frame)

Account

Account Number

Supplier

Supplier Name

Type

Invoice Type (Standard, Debit Memo, Credit Memo, Prepayment, etc). Rows for Prepayments should be flagged with asterisk (*) in beginning of the row

Invoice Number

If sequence is used, then sequence #, else – invoice / payment (for prepayments) number

Internal Invoice

No DOC_SEQUENCE_VALUE for the above invoice number

Date

Invoice Date

Currency

Invoice Currency Code

Original Invoice Rate

Exchange rate considered in the Invoice / Prepayments at Account Level

Balance amount in Entered currency DR, CR

Open item balance amount in foreign currency as of Revaluation date (Parameter). DR and CR amounts are printed in separated columns. Account for Prepayment invoices should be taken from distribution row (rows with tax are not subject for revaluation, only prepayment rows). In case when prepayment invoice is paid, includes tax rows and partially applied, the amount to be printed – proportional part of un-applied value for prepayment row. For example: paid prepayment invoice for $1,200.-00 includes: prepayment row with $1,000.-00 and VAT row for $200.-00, Available (un-applied) amount is $600.-00. In the report for this invoice should be printed basis for revaluation


of $1000 x ($600 / $1200) = $500.

Balance amount in Functional currency, Original rate DR, CR

Revaluation rate DR, CR Two pairs of DR and CR columns should be calculated with relevant exchange rates for the printed ORIGINAL AMOUNT: (1) Original Rate- invoice original rate for all invoices excluding Prepayment, for last one – calculated rate of prepayment distribution row; Prepayment, for last one – calculated rate of prepayment distribution row; (2) Revaluation Rate - period end rate for Closing Rate Date. Calculated amount. DR, CR are printed in separated columns and summarized separately too.

Historical Exchange Differences (LOSSES, GAINS, Net balance)

Calculated column values. Calculation algorithm: it is difference between relevant (DR and CR) columns for Selected Daily or Period Rate and Original (CR By Selected Daily or Period Rate – CR Original or DR By Selected Daily or Period Rate – DR Original for detailed rows); Positive result (greater zero) for CR differences and negative result for DR differences should be printed in the Losses column for detailed rows as a positive value. Positive result (greater zero) for DR differences and negative result CR differences and net balance should be printed in the Gains column for detailed rows as a positive value.

Totals (Supplier)

Summaries for every Supplier should be summarized for every CR and DR columns separately for all currencies, and functional currency as grand total for supplier

Totals (Account)

Summaries for every Account should be summarized for every CR and DR columns separately for all currencies, and functional currency as grand total for Account

Total (Operation Unit)

Summaries for every Operation Unit and Report Total should be summarized for every CR and DR columns separately for all currencies and functional currency as grand total for Report. The revaluation rate considered for the report should be mentioned in the Parenthesis for each currency.

Layout


CLE: Exchange Differences for AR ReportThe revaluations process in the Oracle General Ledger creates journals for unrealized exchange gains/losses. There is legal requirement for disclosure of revaluation result by the list of open items affected by the revaluation; theirs initial exchange rate, revaluation exchange rate and revaluation difference (gains or losses). Exchange rate differences on open items, according to the statutory accounting requirements, should be confirmed with list of such open items, where should be indicated: Customer, invoice #, Internal Invoice #, date, Original Invoice rate, exchange rate, amount original,


in foreign currency - open (unpaid) amount, in functional currency – open (unpaid) amounts with exchange rate at the beginning and closing of the period, for which calculation of exchange gains / losses is processed.

Parameters

No. Parameter Required Default Value

LOV

1 Operation Unit

No None LOV of all operation units of current set of books. If not filled , the report select data from all Operating units.

2 Revaluation Period

Yes None These are GL Periods for selecting open invoices. The user can select the period for which he wants to run the report.

3 Currency No Blank LOV of enabled currencies without functional currency of current set of books. Ifnot filled , the report select data for all currencies.

4 Rate Type Yes None LOV of 1) Daily Rate Type from LOV and this rate nameis defined by user in advance and 2) Period RateType.

5 Daily Rate Type

No None If user selects "Daily" in Rate Type Parameter, then all the Daily rates available in GL_DAILY_RATES. This is disabled if theuser selects "Period" in Rate Type Parameter.

6 Daily Rate Date

No Yes FND_STANDARD_DATE for selecting rate value.

7 Account From

Yes Blank Lowest account combination for determining range of accounts to be processed in report. Key Accounting FlexField should be provided to choose combination. Security rules defined for current responsibility to be strictly applied for display values in LOV for every segment.Parameter Form should allow user to enter values not presented in the LOV (to be able use range limits


8 Account To

Yes Blank Default – copy of previous Parameter 5 combination. Highest account combination for determining range of accounts to be processed in report. Should be validated with rule: the value should be equal or greater than relevant value in the previous parameter ("Account From:").Key Accounting FlexField should be provided to choose combination. Security rules defined for current responsibility to be strictly applied for display values in LOV for every segment. Parameter Form should allow user to enter values not presented in the LOV (to be able use range limits

9 Grouping Level

Yes "Account" User should choose from a list of options

• · "2-digit account" – grouping by first two digits of the natural account segment value;

• · "3-digit account" – grouping by first three digits of the natural account segment value;

• · "4-digit account" – grouping by first four digits of the natural account segment value;

• · "Account" – grouping by the natural account segment value;

• · "Combination" - grouping by the combination of Key Accounting Flexfield

10 Including invoices infunctional currency

No Blank We need this parameter to be able to reconcile GL balance in functional currency to this report balances If there is enter YES the invoices in functional currency are included

Report Heading

Set of Books name

Operating Unit name

Revaluation period


Currency

Rate Type

Daily Rate Type

Daily Rate Date

Account from

Account to

Grouping level

Include Invoices in Functional Currency

Current system date, time

Page number

Account

Account number

Customer

Customer name

Type

Invoice Type (Standard, Debit Memo, Credit Memo, Prepayment, etc). Rows for Prepayments are flagged with asterisk (*) in beginning of the row.

Invoice Number

Invoice Number

Internal Invoice No

DOC_SEQUENCE_VALUE for the above invoice number.

Date

Invoice Date

Currency

Invoice Currency Code

Original Invoice rate

Exchange rate considered in the Invoice / Prepayments at Account Level

Balance amount in ENTERED currency DR, CR

Open item balance amount in foreign currency as of Revaluation date (Parameter). DR and CR amounts are printed in separated columns. Account for Prepayment invoices should be taken from distribution row (rows with tax are not subject for revaluation, only prepayment rows). In case when prepayment inovice is paid, includes tax rows and partially applied, the amount to be printed – proportional part of un-applied value for prepayment row. For example: paid prepayment invoice for $1,200.-00 includes:


prepayment row with $1,000.-00 and VAT row for $200.-00. Available (un-applied) amount is $600.-00. In the report for this invoice should be printed basis for revaluation of: $1000 x ($600 / $1200) = $500.

Balance amount in FUNCTIONAL currency Original rate DR, CR; Revaluation rate DR, CR

Two pairs of DR and CR columns are calculated with relevant exchange rates for the printed ORIGINAL AMOUNT: Original- invoice original rate for all invoices excluding Prepayment, for last one – calculated rate of prepayment distribution row Revaluation Rate - period end rate for Closing Rate Date. Calculated amount DR, CR should be printed in separated columns and summarized separately too.

Historical Exchange Differences (LOSSES, GAINS, Net balance)

Calculated column values. Calculation algorithm: it is difference between relevant (DR and CR) columns for

Selected Daily or Period Rate and Original

(CR By Selected Daily or Period Rate – CR Original or DR By Selected Daily or Period Rate – DR Original for detailed rows)

Positive result (greater zero) for CR differences and negative result for DR differences should be printed in the Losses column for detailed rows as a positive value.

Positive result (greater zero) for DR differences and negative result CR differences and net balance should be printed in the Gains column for detailed rows as a positive value.

Totals (Customer)

Summaries for every Customer should be summarized for every CR and DR columns separately for all currencies, and functional currency as grand total for supplier

Totals (Account)

Summaries for every Account should be summarized for every CR and DR columns separately for all currencies, and functional currency as grand total for Account

Total (Operating Unit)

Summaries for every Operation Unit and Report Total should be summarized for every CR and DR columns separately for all currencies , and functional currency as grand total for Report. The revaluation rate considered for the report should be mentioned in the Parenthesis for each currency.

Layout


CLE: GL Unrealized Gain/loss ReportThis reports presents information on revaluation of transactions recorded in foreign currencies and having open balance in account code combinations as at the date of revaluation.

The report presents conversion rate applied at the time of recording the original transaction, and the rate applied as at the date of report run, resulting difference amount due to difference between the conversion rates applied on transaction date and report period revaluation date.

It is an accounting practice to revalue the GL Account balances available in foreign currencies into functional currency at each period end. This functionality is available in General Ledger.

Resulting difference (due to difference in conversion rate as on date of recording the transaction and period end) is charged to appropriate account code combinations assigned for this purpose. Hence the difference, either profit or loss, will become part ofreports made from General Ledger.

In some countries, Tax Rules provide not to include such profit/ loss made due to difference (fluctuation) in conversion rates of foreign currency into functional currency, which is not realized, while computing profit/ loss for tax purposes.

• Rules and Examples

This report has to be submitted after completing revaluation process in General Ledger, and posting the resulting journal. Conversion rates applied for this report are equal to conversion rates used by revaluation journal.

If a currency is selected as a parameter while submitting the report, then all transactions


recorded in all selected account code combinations, in that currency and which have open balances at the end of the period be reported in the report.

If parameter 'All' is selected as a parameter for currency, while submitting the report, then all transactions in all foreign currencies of all selected account code combinations which have open balances at the end of the period be reported in the report.

In case any account carrying opening balance, the balance has to be printed in the reportas a first row of transactions of the period along with conversion rate applied on that amount, followed by other transactions of the period.

In case any account carrying the opening balance as closing balance (without any transactions during that period), same rule to be applied, how any journal line is treatedfor presenting in this report. In this case only one row appears in transaction section of the report

Parameters


Currency Yes All Excluding functional currency, all currencies used in GLSet of Books attached to GL Responsibility through which this report is being submitted and an additional value 'All'

Accounting Flexfield From

Yes Blank All segment values for Set of Books attached to the GL Responsibility through which this report is being submitted; Filed also be able to accept values from '0' or from'z'


Accounting Flexfield To

Yes Blank All segment values for Set of Books attached to the GL Responsibility through which this report is being submitted; Filed also be able to accept values from '0' or from'z'

Period Yes Latest GL period, for which revaluation journal is posted in GL

All GL periods in which revaluation journal is posted, used by Set of Books attached to the GL Responsibility through which this report is being submitted

Report Heading

Report Title

Unrealized Gain/loss Report GL' should appear in centre of the report on top at line 1.

Report sub title

'For period : parameter period' appear on second line

Report Heading

Account From: Parameter – Accounting Flexfield from Account To : Parameter – Accounting Flexfield to Currency : Parameter – Currency The above three lines are left aligned.

Date

System date and time when the report was printed.

Page

Sequential Page Number / as of total page count.

Column Headings

Source Source of transaction

Category category of transaction

Journal Title description from transaction journal

Date Posted journal effective date (HEADER_EFFECTIVE_DATE).


Journal Amount

In Foreign Currency

amount of journal row in specified currency. Positive value – credit side of journal, negative value – debit side of journal.

In Functional Currency amount of journal row in functional currency . Positive value – credit side of journal, negative value – debit side of journal. Exchange Rate historical journal exchange rate

Revaluation in Functional Currency (Amount in Foreign Currency multiplied by Currency conversion rate applied while revaluation ) – Amount in functional currency of the row. Positive value – profit from entry revaluation, negative value – loss from entry revaluation.

Row

Opening balance of period is to be presented in one row. Each journal line created during the period is printed in one row. Revaluation Amount charged to the account also is printed as last row for that account flex flied and for the currency.

Summary Section

Totals of Journal Amount in Foreign Currency and in Functional Currency, Revaluationin functional Currency is to be presented for each Currency in one row. At end of journals related to one currency, a row of totals is to be printed. After printing totals row, foreign currency name and conversion rate applied for revaluation should be printed as a row. Description as to how to print this row is shown in layout of the report. In the same row, total for Revaluation in functional Currency column has to be printed. After completing all rows related to an account flex field, total for Revaluation in functional Currency column has to be printed. (See layout) After completing all account flex fields, Grand Total is to be printed for Revaluation in functional Currency column (See layout) The records are to be sorted in the order of: Account code combination, Currency, Journal Source, Journal Category, Journal effective date, JournalHeader id, Journal Line id.

Lay out


CLE: Intra-stat ReportOverview

This report will give the inventory movement details of all the transactions occurred in the EU. This excludes the miscellaneous inventory transactions.


Parameters


Legal Entity Yes Blank The legal entity defined in the movement statistics parameter Set up will be shown in the LOV.the entity for which we want the statistics to be captured, will be selected.

Economic Zone Yes Blank The Economic Zone defined in the movement statistics parameter Set up will be shown in the LOV.

Usage Type Yes Blank Internal, if the movement of goods iswithin the economic zone, external is the movement is across the EZ.

Statistical Type Yes Blank The intrastat parameter needs to bechosen. This value will be defaulted.

Movement Type Yes Blank Arrival, Arrival Adjustment, Dispatch, Dispatch adjustments.

Period Name Yes Blank The Legal entity SOB calendar period.

Report Option Yes Blank Summary/ Official; Detail report


Currency Yes Blank The currency populates from the Legal entity parameter,the base currency for the legal entity SOB will be picked

Conversion Yes Blank The currency conversion rate

Report Status No Blank The applicable report status for the official report; the LOV will have only one value 'Frozen'.

Report Heading –Detail Report

This report will display all the movement statistics transactions in a period as per the movement status. The report will be sort by the Movement statistics ID, in the ascending order.

Report title

CLE Movement Type Movement Statistics Detail. Requested by: Name of person, who runs the requestReport Parameters Displays all the parameters entered during the report submission.

Report Information

Displays the following information

Report ID

Application

Responsibility

Time of Request

Page number

Period:

Period entered as a report parameter

Column heading

In case the report extends to the next page, the following header data would be repeated: Report name ' Movement Statistics Detail/Summary/Official report.

Legal entity


Set of Books

Reporting Currency

Standard UOM

Report Date

Page number

Parent Movement Num/ Commodity Code/ Description/ Inventory Item/ Item Description/Inventory Org

Parent Movement Num: the movement ID number generated while running the processor.

Commodity Code: the commodity code of the item.

Description: Commodity code description

Inventory Item: Inventory Item code

Item Description: Inventory Item description

Inventory Org: the inventory Org associated with the Item.

Transaction Date/ Trader Type/ Trader Name/Trader number/ Trader Site/ Item Cost

Transaction Date: Date on which the transaction occurred.

Trader Type: the type of trader, whether a supplier or a customer.

Trader Name: the name of the supplier/customer

Trader number: The Supplier/customer number.

Trader Site: the supplier/customer site at which the transaction occurred.

Item Cost: cost of the item in the transaction

Source Type/ Source Number/ Source Line/ Invoice/ Invoice Line/ Release Number

Source Type: describes the source of the transaction, the following transactions will be captured

Sales order

Purchase order

Customer Return

Internal order

Inventory Transactions (Inter company transfers)

Return to supplier

OPM Sales Order

OPM receipt

OPM Inventory Move


OPM Inventory Transfer

OPM return to supplier

OPM customer return

OPM Immediate Inventory Transfer

OPM journaled Inventory Transfer

Source Number:The PO/SO /RMA number. This is the source document number.

Source Line: the source doc line number

Invoice: the invoice number associated with the transaction

Invoice Line: The line number of the invoice

Invoice Release number: the release number of the invoice

Quantity / Transaction/ Primary/Alternate

Quantity: the quantity of item transacted in primary and alternate UOM. Quantity in additional UOM (when required, this is based on UOM and item category in MovementStatistics Parameters)

Exchange Rate/ Source Value/ Outside Value/ Invoice Value/ Transaction Value/ Statistical Value

Exchange Rate: The rate of exchange if the transaction is in foreign currency.

Source Value: The amount in the source document.

Transaction Currency/Weight/ Outside Code

Transaction Currency: The currency in which the transaction occurred. Weight: weight of the goods in the transaction.

Dispatch Country/ Arrival Country/ Origin Country/ Shipment Number/ Shipment Line

Dispatch Country: the country from which the goods are dispatched.

Arrival Country: the destination country for the goods.

Origin Country: the country of origin of the goods.

Shipment number and Line of the goods shipped

Transition Nature/ Delivery Terms/ Transport/ Area/ Port/ Type

Transaction Nature: Seeded values for the transaction type. It specifies if the transactionis a RTV, SO, PO RMA etc.

Delivery Terms: The delivery terms of the transaction

Transport: The transport mode of the transaction

Area: Area will default from destination/dispatch sub-inventory – movement statistics processor should populate this field


Report Totals

The totals for each record status and the complete report total has to be shown

Report footing

The report will conclude with -End of Report- on Last page of Report. No footer for each page.

Lay Out

Report Heading –Summary Report

The Summary report will show only the records in the 'Open', 'verified' and 'Frozen' status. The report will be sort by the Movement statistics ID, in the ascending order. Page break for every four records.

Report title

CLE Movement Type Movement Summary Report. Requested by: Name of person, whoruns the request

Report Parameters

Displays all the parameters entered during the report submission.

Report Information

Displays the following information:

Report ID

Application


Responsibility

Time of Request

Page number

Period:

Period entered as a report parameter

Column heading

Report /Edit/item number

Report – Sequence number for the report in a given declaration month, in which the item was declared Edit - Sequence number for adjustment report in a given declaration month, in which the item was declared Item number –Position of the item in the report; where item was declared in given month. These fields will be empty in case of the Summary report and an additional column will display the serial numbers.

Commodity Code

The Commodity code associated with the item.

Goods Description

Description of the goods in the transaction

Country of destination/dispatch

Country of destination: the destination country for the goods Country of dispatch: The country from which the goods were dispatched.

Country of origin

The country of origin of the goods.

Total weight in kg

The weight of the all the goods in the transactions

Quantity in additional units of measurement

The quantity will be shown in additional UOM.

Transaction code

The type of transaction associated with the line. A SO, PO etc.

Delivery terms

The delivery terms associated with the transaction

Transport type

The transport type associated with the transaction

Movement amount in SK

The movement amount in the SK currency.

Report Totals


NA

Layout

Report Heading – Summary Report

The Summary report will show only the records in the 'Open', 'verified' and 'Frozen' status. The report will be sort by the Movement statistics ID, in the ascending order. Page break for every four records.

Report title

CLE Movement Type Movement Summary Report

Requested by: Name of person, who runs the request.

Report Parameters

Displays all the parameters entered during the report submission.

Report Information

Displays the following information

Report ID

Application

Responsibility

Time of Request

Page number

Period:

Period entered as a report parameter.


Column heading

Report /Edit/ item number

Report – Sequence number for the report in a given declaration month, in which the item was declared Edit - Sequence number for adjustment report in a given declaration month, in which the item was declared Item number –Position of the item in the report; where item was declared in given month. These fields will be empty in case of the Summary report and an additional column will display the serial numbers.

Commodity Code

The Commodity code associated with the item.

Goods Description

Description of the goods in the transaction.

Country of destination/dispatch

Country of destination: the destination country for the goods.

Country of dispatch: The country from which the goods were dispatched.

Country of Origin

The country of origin of the goods.

Total weight in kg

The weight of the all the goods in the transactions

Quantity in additional units of measurement.

The quantity will be shown in additional UOM.

Transaction code

The type of transaction associated with the line. A SO, PO etc.

Delivery terms

The delivery terms associated with the transaction.

Transport type

The transport type associated with the transaction.

Movement amount in SK.

The movement amount in the SK currency.

Report Totals

NA

Report footing

The report will conclude with -End of Report- on Last page of Report. No footer for each page.

Layout


Rules and Examples

Rounding rules

Rounding rules in summary/official report – as per the law requirement, following give details about rounding rules implied during creation of official report:

Movement value – final value should be rounded up to whole numbers.

Item weight value - The total weight is given in whole kg, rounded down when < 0.5 kg, rounded up when > 0.5 kg. Weight under 1 kg = 1 kg. For items without weight, weight = 0 kg will be entered.

Alternative quantity value and UOM - Quantity in alternative UOM must be rounded up to whole numbers For items without a mandatory weight reporting in additional units of measurement, the system will enter 0 (zero)

CLE: Asset AccountingAs per standard procedure, while accounting the asset retirement the system derives the expense account based on initial values set at the level of asset book. The system does not derive the expense account according to the retirement type. Retirement of Assets needs to generate account combination, using a natural account that is linked to Retirement type.

Lookup

Lookup type by name "RETIREMENT" with description "RETIREMENT TYPES" is available in Fixed Assets. The same can be seen at: Setup>Asset System >Quick codes.


DFF -Descriptive Flexfield

A DFF is created and enabled which has to be used while creating values for above referred quick code "RETIREMENT TYPE". The DFF be made as a mandatory DFF.

Example: Value: Theft Description: Retirement due to theft of asset Disable date: Blank DFF Value for Natural Account: 5320

[Note: It is assumed that 5320 is natural account defined in associated GL Set of Books and requirement is to use this account while creating accounting for retirement when retirement type 'Theft' is used]

While retirement of Assets, user has to select the retirement type appearing in form under 'Retirement Details' block, at item 'Retirement Type'. List of Values will consist ofall the values created and available at Quick code "RETIREMENT". At present functionality, this field is not a mandatory filed. User can continue the work, without selecting any value for the field 'Retirement type'. In case the user does'nt enter the DFF values for the retirement type, the accounting program will pick up the values from book controls.

Pre-requisites

Values for Quick code "RETIREMENT" are to be provided

Set Of book to be attached against a quick code

Natural Account to be assigned to each value provided at "RETIREMENT"

Custom profile option: CLE : Asset Accounting to be set to 'Yes'

While retirement of asset, user has to select retirement type.

After running the depreciation program

User has to run CLEF023 Create Journal Entries program

Process Flow

1. Perform the pre-requisites as described above.

2. Query the assets that need to be retired.

3. Select the retirement type which has the DFF setup at the time of retiring.

4. Submit Run Depreciation program for the period in which the asset is retired withoutselecting the check box for Close Period.

5. Submit the CLEF023 : FA Create Journal Entries program with Import Journals parameter set to Yes.

6. Review the log file of the CLE program when the Journal Import request ends in a warning, for detailed error messages.

7. Correct the issues described in the log file of the CLE program.

8. Run Rollback Journal Entries.

9. Run Rollback Depreciation.


10. Submit Run Depreication program again by selecting the Close Period check box as no more issues were identified.

11. Submit the CLEF023 : FA Create Journal Entries program. Now the import would besuccessful.

CLE: Prepayment ApplicationIt is a common business practice to receive Deposits from customers. As a regular business process, such deposits will be adjusted against invoices created for regular sales. Standard functionality provides the same.

Standard functionality available at present, allows adjusting deposits with invoices. While adjustment, system considers whole amount of deposit. System will not check whether amount on such deposit is received or not.

As there is no validation on deposit, whether amount is received on that deposit or not, while adjusting, there exists a possibility that, invoices may get adjusted with deposits, on which no amount has been received.

This is resulting in showing an invoice as fully paid, though amount has not been received for the same. In such case, invoice shows as fully paid as the invoice is already adjusted towards deposit.

To have better credit control, and to have the records to represent a true status on invoice payments, it is required to validate the deposit while adjusting with invoices.

Validation should provide a check to allow the adjustment on deposits, where amount on such deposit is already received. System should not allow adjusting with a deposit, ifamount on such deposit is not received. In case of a part amount received on deposit, system should allow adjusting the deposit with invoices, only to the extent of amount received on that deposit. Amount received on deposit includes receipts applied to the deposit and also credit notes applied to the deposit.

Profile Option

One profile option 'CLE_F066_USE_PAID_DEPOSITS' is available. This profile will have values of 'Yes' and 'No'. If this profile is set to yes, then this solution is available. If this profile is set to 'No' this solution will not be available, though patch is applied

Alert

An alert is created to track apply deposit. Whenever user completes: Transactionsà Transactions, From Menu bar, go to Actions and Click on Apply Deposit, select deposit number, and click on 'OK 'button, the alert is activated.

Setup steps for Alert are provided in Annexure B.


Alert activates a script to replace amounts by limiting the deposit amount to amount received on such deposit (including Credit Memos applied to such deposit)

If amount applied to invoice from the deposit is less than or equal to amount received (including CM), then no changes are made to amounts applied by standard functionality.

If amount applied to invoice from the deposit is more than the amount received (including CM), then all the amounts applied by standard functionality will be replacedby amounts restricted to received amount (including CM) on such deposit.

If no amount is received on a deposit, and/or no credit notes were adjusted with such deposit, and such deposit is applied to an invoice,such deposit is not available in LOV


to apply.

In case of part amount is received on a deposit (including CM), application of deposit will be restricted to the amount received on such deposit.

All applications, receipts adjusted/ applied on deposit till then will be considered to determine, the received amounts, and available for application amounts. Alert require some extra time to complete updation of amounts. User required to requerry the transaction, to see the changes made by alert.

User Interactions

User should keep in mind that deposits, for which amount is already received is only allowed to adjust with invoices.

Application of deposit is limited to amount received on that deposit. (Standard functionality is -application of deposit is limited to deposit amount)

When amount is received against a deposit, user should apply that receipt with the deposit, before proceeding for adjusting the deposit with invoices. When invoice has earlier date than deposit, it is possible to apply deposit to invoice by changing Effective date of deposit to invoice (or earlier) date.

CLE: Depreciation RoundingExisting Standard functionality allow to run Depreciation program which calculates the depreciation amount which is rounded off to the decimal precision set at GL Set of Books Currency. (Asset Book (corporate and Tax) are mapped to GL Set of Books).

The solution is needed which maps to specific Slovakia and CZ business and accountingrequirements.

The "CLE: Depreciation Rounding Program" performs rounding off when we have enabled DFF.

The solution addresses to generate journals from FA modules in whole numbers while accounting for depreciation and retirement. Wherever a journal is got created with non whole number (excluding during last period of an asset), based on rounding rule described in this solution, the number will get converted into a whole number.

The concurrent program "CLE: Depreciation Rounding Program" runs Depreciation, calculate gains and losses, Rounding off and functions Journal Entry Reserve Ledger Report or Tax Reserve Ledger Report Based on the type of the book.

The rounding off depreciation program will be submitted which rounds off the calculated depreciation and other resulting journal amounts created by standard program, relating to Current period.

DFF is set at Book Control level. Setup>Asset System>Book Control>

CLE FA Book Controls Extension.Rounding Off Field is selected as YES to enable and NO to disable rounding off Function. The Rounding off should occur for only those assets, which are created under the Asset books where the DFF "Allow Rounding Off"


(FA_BOOK_CONTORLS.ATTRIBUTE1) is set to yes. As the functionality is based on DFF, hence DFF are mandatory

For Depreciation to get rounded off,

Depreciation reserve (FA_DEPRN_SUMMARY.DEPRN_RESERVE) < Asset cost (FA_BOOKS.COST) or FA_BOOKS.RETIREMENT_PENDING_FLAG is YES

Logic followed for rounding off amount

If the Calculated Depreciation amount is positive then it is rounded off to next highest number. Ex: - If the calculated Depreciation is say, 5.345, then it is updated to next highest number, which is 6. Here, Rounding Difference amount =6-5.345=0.655

If the calculated Depreciation amount is negative or else 0, then it is rounded off to previous lowest number. Ex: - if the Calculated Depreciation is say (-5.345), then it is updated to –6. Here, the Rounding Difference amount =-6-(-5.345)=-0.655

Rounding Off (in corporate books and tax books)

If the current period = last period of Asset

Then no update is proposed, all journals will be created as per standard functionality for depreciation and retirement.

If the current period <> last period of Asset

Depreciation amount = Depreciation + Rounding Difference. YTD Depreciation = YTD Depreciation + Rounding Difference Amount. Depreciation reserve = Depreciation reserve + Rounding Difference Amount.

If the Asset is retired, then update should be made to FA_ADJUSTMENTS.ADJUSTMENT_AMOUNT.

If FA_ADJUSTMENT.SOURCE_CODE_TYPE = RETIREMENT AND FA_ADJUSTMENT.ADJUSTMENT_TYPE = RESERVE FA_ADJUSTMENT.adjustment_amount = adjustment_amount + Rounding difference

The rounding difference should also be adjusted against NBV_RETIRED and GAIN_LOSS_AMOUNT.

DFF Details

Application: Fixed Assets

Navigation: Setup>Asset System>Book Control>Actions>CLE FA Book Controls Extension

Base Table: FA_BOOK_CONTROLS

Segment Name

Prompt Column Size Value Set Context


Round Write Off

Allow Rounding Off

Attribute 1 3 Yes_No Global Data Elements

Parameters


Asset Book Y Blank All asset books available for the responsibility through which, the program is being accessed

Period Y Current Period in Asset Book

DFF Y No No, Yes

This is part of a request set. When this program "CLE: Depreciation rounding program" is submitted,

Following requests are called: -

Depreciation Run

Calculate Gains and Losses

CLE: Depreciation Rounding Program

Journal Entry Reserve Ledger Report or Tax Reserve Ledger Report Based on the type of the book

Setting up Cross Country Localizations 3-1

3Setting up Cross Country Localizations

CLE: ECE European Sales / Purchase Listing ReportGDF Setup

Set up required at General Ledger

GDF at Set of Book

Select GDF

• Responsibility : General Ledger

Navigation : Setup>Financials>Flexfields>Descriptive Flexfield>Segments

Query on Title : JG_GL_SETS_OF_BOOKS


uncheck 'Freeze flexfiled definitions'


Go to segments of CZ

Keep cursor on 'JE.CZ.GLXSTBKS.BOOKS'

Click on 'segments'

Add a row

Number : 30

Name : Tax Calander

Window Prompt : Tax Calander

Column : Global Attribute4

Value set : CE_FC_CALENDAR

Save your work


Close the form

Freeze flexfield definiation : check the box at Freeze flexfield definiation

Compile : Click on compile button

Attach Tax calander at GL SET OF BOOKS

Open SOB definition form

Responsibility : General ledger, Czech

Navigation : Setup>Financials>Books>Define

Query on 'Set of Books" : Vision Czech


Attach Tax Calander at GDF

Click on GDF '( )'

Vat Reporting calander : JEBE_ESL (this attribute is not used for R2)

Vat Register Sequencing: Document (this attribute is not used for R2)

Tax Calander : JEBE_ESL


Click on OK; Save your work

SET UP in RECEIVABLES

GDF for Supply code

Responsibility : Receivables

Navigation : Setup>Financials>flexfields>descrirptive>Segments

Query on : Title : JG_AR_VAT_TAX

Uncheck on 'freeze flexfield definiation'


GO for a new record (click on + at top)

Code : JE.CZ.ARXSUVAT.SUPPLY_CODE

Name : Supply code information

Description: Supply code information


click on segments

Add a row

Number : 10

Name : Supply code

Window Prompt : Supply code

Column : Global Attribute 20

Value set : CLE_F020_ECE_SUPPLY_CODE

Save your work


Close the form

Click on Freeze flexfiled definiation

Click on compile button

• Creation of Tax Codes and assign supply code


Navigation : Setup> Tax> Codes

Tab : Rates

Tax Code : ECE0

Tax Rate :10

Tab : Effective:

Effective from : 1-Apr-1980

Tab : More

Go to extreme right and click at GDF under '( )'

Context value : Supply code information

Supply code : 0


Save your work.

Create rows for other tax codes and select GDF values

• Assign VAT Member State Code


Navigation : Setup à System à Countries

Query on country/territory : 'Czech Republic'


VAT Member State Code : CZ


Save your work.

• SET UP IN PAYABLES

• Create GDF for supply code

Responsibility : Payables

Navigation : Setup>Flexfield>Descriptive>Segments

1 Query on Title

2 JG_AP_TAX_CODES


• Unfreeze definition

Un check freeze flexfield definition


• Add a new row to context field values

Code : JE.CZ.APXTADTC.SUPPLY_CODE

Name : Supply code information

Description : Supply code information


• Add segment values

Click on segments

Add a row

Number : 10

Name : Supply code

Window prompt : Supply code

Column : Global attribute20

Value set : CLE_F020_ECE_SUPPLY_CODE


Save your work

Freeze flexfield definition : check the box

Compile : click on compile button

Create tax codes & assign supply code


Navigation : Setup>Tax>Codes

Create new tax code

Tax code : ECE

Tax type : VAT

Rate : 10

Effective from : 1-Apr-1980

GL Account :


Assign Supply code

Click on GDF under '( )'


click on OK

Save your work

Create other tax codes in similar way

• Vat Number set up


Responsibility Navigation : Setup>System> Organizations> Organizations


Query on Organization

As an example 'Vision Hungary' is used


Go to Legal Entity

Click on 'others' button

Select 'Legal Entity Accounting'


Click on the line appearing with Legal Accounting Information

Fill up Vat Registration Number information


Set up required at Receivables

GDF at Transaction Types

Select GDF

Responsibility: Receivables

Navigation: Setup>Financials>Flexfields>Descriptive Flexfield>Segments

Query on Title: CLE: Additional Transaction Type Information


Uncheck 'Freeze flexfiled definitions'


Go to segments of CZ

Keep cursor on 'CZ'

Click on 'Segments'


Add a row

Number: 1 Name: INC_TRANS_TYPE

Window Prompt: Include In ESL Report

Column: Global Attribute1

Value set: Yes_No

Save your work

Close the form

Freeze flexfield definition: check the box at Freeze flexfield definiation

Compile: Click on compile button

Setup the LDFF for Transaction Type that needs to be excluded.

Go to Transaction Type setup


Go To Actions – CLE: Transaction Type Information


Select Context Value: CZ

Set Include in ESL Report: No


CLE: Intra-statSETUP : Movement Statistics Personalization of form

Step 1->Responsibility->Inventory -> Find Movement Statistics screen -> Find ->Detail


Step 2-> Detail screen -> Detail Button


Movement Statistics Detail Form


Step 3-> Help->Diagnostics->Custom Code -> Personalization

(For the first time after log in will ask for the Password As shown in the next screen )


Step 4->Password : <***> -> ok


Step 5-> Fill the values as mentioned below the screen shot


Seq: 91

Description: CLEF087_MVT_INVOICE_DATE

Enable flag should be checked

Click on the Condition Tab

Trigger Event: WHEN-NEW-RECORD-INSTANCE

Trigger object: MOVEMENTS

Condition: -

MOVEMENTS.INVOICE_DATE IS NOT NULL

and :MOVEMENTS.MOVEMENT_STATUS_MEANING ='Open' OR

MOVEMENTS.MOVEMENT_STATUS_MEANING='Verified'

Processing Mode : Both

Context Level -: Responsibility

Value -: The responsibility name in which the user in logged in

Step 6->Click on the Actions Tab


Seq -: 20

Type -: Property

Language -: All

Enable flag should be checked

Object Type -: Item

Target Object -: MOVEMENTS.INVOICE_DATE

Property Name -: VALUE

Value -: :MOVEMENTS.TRANSATION_DATE

Step 7-> Go to next line


Seq -: 21

Type -: Built-in

Language: - All Enable flag should be checked

Builtin Type: - DO_KEY

Argument COMMIT_FORM

Save the form.

Close all the forms.

SETUP: Intrastat

SET UP IN PAYABLES

Create GDF for Tax date


Navigation : Setup >Flexfield >Descriptive >Segments

Query on Title : JG_AP_INVOICES


Unfreeze definition

uncheck freeze flexfield definition


Add a new row to context field values

Code : JE.CZ.APXINWKB.INVOICE_INFO

Name : Additional Invoice Information

Description : Additional Invoice Information


Add segment values

Click on segments

Add a row

Number : 1

Name : TAX_DATE

Window prompt : Tax Date


Value set : FND_STANDARD_DATE


Save your work

Freeze flexfield definition : check the box

Compile : click on compile button

SET UP IN RECEIVABLES

Create GDF for Tax date


Navigation : Setup >Flexfield >Descriptive >Segments

Query on Title : JG_RA_CUSTOMER_TRX


Unfreeze definition

uncheck freeze flexfield definition


Add a new row to context field values

Code : JE.US.ARXTWMAI.TAX_DATE

Name : Additional Invoice Information

Description : Slovak Additional Information


Add segment values

Click on segments

Add a row

Number : 10

Name : Tax Date

Window prompt : Tax Date


Value set : Date


ITEM 'CATEGORY SET' SET UP:

The Intrastat functionality has to collect only transactions, which involve the physical movement of the items.

The Service items, expense items, etc should not be collected.

This requirement is met by defining a category set exclusively for the items that need to be reflected in the movement statistics and assign this category set in the movement statistics parameters.

Defining Category Set

Navigate to

Inventory >Set upàItems>Categories>Category set

Enter the name of the category, which will be exclusively used for intrastat transactions.

Enter the description

Enter the category flexfield structure applicable

Specify the level at which this will be controlled

Enter the categories that come under this category set and enter the default category.


Assign this category set to the items that need to be reflected in the movmeent statistics

Navigate to Inventory>Items>Master Items

Query the item which is the intrastat item


Go to 'Tools' window bar and click 'Assign Categories'

Assign the Category set defined earlier

Save the work

INTRASTAT ECONOMIC ZONE SET UP

The Economic zone defintion is one of the major set ups for the Intrastat (Movement Statistics) functionality

The transaction is picked based on the countries in the economic zone.

Any transaction involving the physical movement of the items between the countries in the Economic zone will be considered in the movement statitistics.

Movement of items within the countries in the economic zone will be termed as 'Internal' transaction; that is 'Intrastat'. Movement of items involving a economic zone country any other country will be termed 'Extrastat'.

SET UP:

Navigate to Inventory >Set up>Transaction>Movement Statistics>Economic Zone

Enter a code for the Economic zone

Enter the name of the economic zone and the description

Enter the countries which will be included in the defined economic zone.


Save the Economic zone definition.

MOVEMENT STATISTICS PARAMETER SET UP

This is a mandatory set up for the movement statistics functionality.

This is specific to a legal entity and works at the legal entity level.

Navigate to inventory >Set up>Transaction>Movement Statistics>Parameters.


Select the legal entity for which we have to define the movement statistics parameters.

Enter the economic zone defined earlier


Click the Statistical type usage button

Enter the usage type, Statistical type.

In the period set, enter the calander for the intrastat transactions,.this is the GL calender and any GL calender can be assigned here

In the category set field, enter the category set defined exclusively for the Intrastat transactions.


Save the entry.

This completes the set up for the Intrastat functionality

SET UP FOR STATISTICAL PROCEDURE Call out program

Statistical procedure is a field in the movement statistics form and is not populated by the standard processor

We need to use a call out program for populating this field.

The following set up's have to be made for the statistical procedure.

Statistical procedure values are a look up called 'MVT_STATISTICAL_TYPE' in the application developer.

We have to first define the item cross referrence type of 'Intrastat'

We have to assign the intrastat items to this type.

The cross reference 'Value' that we define in the Item cross reference will be used in the statistical procedure look up.

We have to add the same ' Value' of the intrastat item cross reference as one of the valuesin the 'MVT_STATISTICAL_TYPE' look

This will be populated in the 'Statistical procedure' field in the movement statistics.

Define cross reference type


Assign the intrastat item to this cross reference


This value define as the cross reference would be used in the look up again

Define 'MVT_STATISTICAL_TYPE' look up.

Reader's Comment Form

Cross-Countries Localizations User Guide

Oracle welcomes your comments and suggestions on the quality and usefulness of this


publication. Your input is an important part of the information we use for revision.

• Did you find any errors?

• Is the information clearly presented?

• Do you need more information? If so, where?

• Are the examples correct? Do you need more examples?

• What features did you like most about this manual? What did you like least about it?

If you find any errors or have any other suggestions for improvement, please indicate the topic, chapter, and page number below:

Please send your comments by logging a Service Request using http://metalink.oracle.com If you would like a reply, please give your name, email id, address, and telephone number below:

Thank you for helping us improves our documentation

Index-1

Index

SymbolsCLE: Account Analysis Report, 2-15

AAbout this Localization Manual , 1-1Audience for this Manual, 1-2

CCLE: Asset Accounting, 2-47CLE: Depreciation Rounding, 2-51CLE: ECE European Sales / Purchase Listing Report, 3-1CLE: ECE European Sales and Purchase Listing, 2-1CLE: Exchange Differences for AP Report, 2-24CLE: Exchange Differences for AR Report, 2-29CLE: GL Unrealized Gain/loss Report, 2-34CLE: Intra-stat, 3-28CLE: Intra-stat Report, 2-38Consulting Localization Overview, 1-2

FForeword, 1-1

IInstallation, 1-2

UUser's Guides Related to This Consulting Localization, 1-2

Emea Consulting Localizations

Documents

Transcript of Emea Consulting Localizations