Вы находитесь на странице: 1из 79

Oracle EMEA Add-on Localizations

User Guide for Romania Release 12.1


Part No. E05469-01

December, 2011

Oracle EMEA Add-on Localizations User Guide for Romania, Release 12.1 Part No. E05469-01 Copyright 2009, 2010, Oracle and/or its affiliates. All rights reserved. Primary Author: Kishore Kumar Yepuri

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software 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 this software 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.

Send Us Your Comments


Oracle EMEA Add-on Localizations User Guide for Romania, Release 12.1
Part No. E05469-01

Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document. Your feedback is important, and helps us to best meet your needs as a user of our products. For example: Are the implementation steps correct and complete? Did you understand the context of the procedures? Did you find any errors in the information? Does the structure of the information help you with your tasks? Do you need different information or graphics? If so, where, and in what format? Are the examples correct? Do you need more examples? If you find any errors or have any other suggestions for improvement, then please tell us your name, the name of the company who has licensed our products, the title and part number of the documentation and the chapter, section, and page number (if available). Note: Before sending us your comments, you might like to check that you have the latest version of the document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the most current Documentation Library plus all documents revised or released recently. Send your comments to us using the electronic mail address: appsdoc_us@oracle.com Please give your name, address, electronic mail address, and telephone number (optional). If you need assistance with Oracle software, then please contact your support representative or Oracle Support Services. If you require training or instruction in using Oracle software, then please contact your Oracle local office and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at www.oracle.com.

iii

Preface

Intended Audience
Welcome to Release 12.1 of the Oracle EMEA Add-on Localizations User Guide for Romania. This manual is a source of information about major requirements of Romania and is designed to provide useful guidance and assistance to: Consultants implementing Romanian Add-on Localizations components for R12.1 Oracle E-Business Suite Users of Oracle E-Business Suite The Oracle EMEA Add-on Localizations user's guide assumes you have good understanding of core modules and the country specific localization requirement. If you have never used Oracle E-Business Suite, we suggest you to attend one or more of the training classes available through Oracle University. See Related Information Sources on page vi for more Oracle E-Business Suite product information.

Deaf/Hard of Hearing Access to Oracle Support Services


To 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.

Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible

to 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 by the 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 Documentation


Screen 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 Documentation


This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Structure
1 Add-on Localizations Overview 2 Prerequisites 3 General Setup Steps 4 Statutory Accounting - Fiscal Book 5 Transaction Tax

Related Information Sources


Integration Repository
The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner. The Oracle Integration Repository is shipped as part of the E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.

vi

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


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

vii

1
Add-on Localizations Overview

Introduction
Oracle EMEA Add-on Localizations for Romania provide additional functionalities to help customers in Romania meet legal and business requirements. This user guide provides details about setup and functionality of the following programs and reports. This user guide is divided into two sections: 1. Statutory Accounting - Fiscal Book: CLE: INV Goods Received Note CLE: INV Transfer Note for Goods Report CLE: INV Consumption Bill Report CLE: INV Accounting Card Report CLE: AP Invoice Aging Report CLE: GL Trail Balances Report CLE: GL Trail Balance Report-Yearly 2. Transaction Tax: CLE: AR Sales Ledger Report CLE: AP Purchase Ledger Report Each report is explained in detail in the respective sections.

Add-on Localizations Overview

1-1

2
Prerequisites

Patches to be applied
Patches can be downloaded from MyOracle Support (Doc ID: 433874.1).

Assignment of Concurrent Programs to Request Groups


Request group setup is for providing access to the concurrent programs to the user responsibilities. Assign the following programs to request groups attached to the responsibility from which you want to access the functionality:

S. No. Program Name Module Template Code 1 CLE: INV Accounting Card Report 2 CLE: INV Consumption Bill Report 3 CLE: INV Transfer Note for Goods Report 4 CLE: INV Good Received Note 5 CLE: AP Invoice Aging Report 6 CLE: AP Purchasing Ledger Report EMEA Add-on Localizations EMEA Add-on Localizations EMEA Add-on Localizations EMEA Add-on Localizations EMEA Add-on Localizations EMEA Add-on Localizations CLE_F103_CB CLE_F104

CLE_F106

CLE_F105

CLE_F107

CLEF224APPVR

Prerequisites

2-1

S. No. Program Name Module Template Code 7 CLE: AR Sales Ledger Report 8 CLE: GL Trial Balance Report 9 CLE: GL Trial Balance Yearly EMEA Add-on Localizations EMEA Add-on Localizations EMEA Add-on Localizations CLEF223GLTBYB CLEF225ARSLR

CLEF223GLTB

2-2 Oracle EMEA Add-on Localizations User Guide for Romania

3
General Setup Steps

General Setup Steps

3-1

Localizations Descriptive Flexfields Setup


The patch installs the following Localizations Descriptive Flexfields:

1) Application: EMEA Add-on Localizations DFF Name: CLE_F220_GL_JE_LINE_EXT Title: CLE: Additional Info for Journal Lines Context Code: RO.Customer VAT

Segment Name CUSTOMER_NAME ORIGIN_OF_ACQUISITION Y

Displayed N Y

Required N

Valueset

CLE_F220_AR_CUSTOMERS CLE_F220_DELIVERY_LOCATION

2) Application: EMEA Add-on Localizations DFF Name: CLE_ZX_RATES_B_EXT Title: CLE: CLE: Additional Info on ZX Tax Rates Context Code: RO.VAT_RATE_DETAILS

Segment Name

Displayed

Required N N

Valueset

SUPPLIER_NAME Y N CLE_F220_AP_SUPP Y ORIGIN_OF_ACQUISITION Y

CLE_F220_AP_SUPPLIERS CLE_F220_DELIVERY_LOCATION

3) Application: EMEA Add-on Localizations DFF Name: CLE_AP_INVOICES_ALL_EXT Title: CLE: Additional Info On Invoices Context Code: RO.INCLUDE_IN_VAT_REGISTER

Segment Name Displayed Required Valueset INCLUDE Y AP_SRS_YES_NO_MAND

4) Application: EMEA Add-on Localizations DFF Name: CLE_F220_GL_JE_LINE_EXT Title: CLE: Additional Info On Journal Lines a) Context Code: RO.Customer VAT

Segment Name Displayed Required Valueset CUSTOMER_NAME ORIGIN_OF_ACQUISITION Y Y CLE_F220_AR_CUSTOMERS CLE_F220_DELIVERY_LOC

b) Context Code: RO.Supplier VAT


Segment Name Displayed Required Valueset Supplier Name ORIGIN_OF_ACQUISITION Y Y CLE_F220_AP_SUPPLIER CLE_F220_DELIVERY_LOC

5) Application: EMEA Add-on Localizations DFF Name: CLE_ZX_RATES_B_EXT Title: CLE: Additional Info On ZX Tax Rates Context Code: RO.VAT_RATE_DETAILS

Segment Name Displayed Required Valueset RATE_DETAILS APPLICABLE_TERRITORY INCLUDE Y Y Y CLE_F220_ZX_TAX_RATE_INFO CLE_F224_APPLICABLE_TERRITORY AP_SRS_YES_NO_MAND

6) Application: EMEA Add-on Localizations DFF Name: CLE_RA_CUSTOMER_TRX_EXT Title: CLE: Additional Info On Transaction Context Code: RO

Segment Name Displayed Required Valueset Include in VAT Register Y AP_SRS_YES_NO_OPT

Forms Personalization
The patch installs the following Forms Personalizations:

Form Form Name Block Function Name GLXJEENT_A GLXJEENT LINES CLE Localization DFF Form

OAF Personalization
The patch installs the following OAF Personalizations:

OAPage OARegion Item Prompt /oracle/apps/zx/taxco ntent/regime/webui/Z xTaxRatesViewPG Rate Periods Static Styled Text CLE: RO Tax Rate Info

General Setup Steps

3-3

4
Statutory Accounting - Fiscal Book

Introduction
The following reports are covered in 'Statutory Accounting Fiscal Book' section: CLE: INV Goods Received Note CLE: INV Transfer Note for Goods Report CLE: INV Consumption Bill Report CLE: INV Accounting Card Report CLE: AP Invoice Aging Report CLE: GL Trail Balances Report CLE: GL Trail Balance Report-Yearly

Goods Received Note Report


Requirement
Requirement is to print the "Goods Received Note" when goods are received into subinventory. The report "Goods Received Note" must be printed for each receipt from suppliers or transfer from another subinventory.

Solution Overview
Goods Received Note is a document to record details regarding goods received into subinventory. This is filled in for each receipt of goods delivered by suppliers or transferred from one inventory organization to another.

Statutory Accounting - Fiscal Book

4-1

Report Sample Layout

Prerequisites
Prerequisites before running Goods Received Note Report are as follows: Inventory organization should be present with costing enabled. Receipts should be present in the selected inventory organization. Cost Manager should be run for the inventory organization. Receipts should be created with destination as "Inventory".

How to Launch the Report


The report "Goods Received Note Report" is launched from the Standard Request Submission (SRS) window. It must have been previously added to the requests group of the used Responsibility. Navigation Path: Respective Responsibility>View>Requests>Submit New Request>Single Request. Select the report from the list of values and submit the report.

Report Parameters
The report parameters are:

4-2 Oracle EMEA Add-on Localizations User Guide for Romania

Parameter Required Description Inventory Organization Yes Select the inventory organization from the list of value. Subinventory Yes User can select the sub-inventory from the list of value corresponding to the selected inventory organization. Receipt Number Yes Select the Receipt Number from the list of value, corresponding to the respective subinventory. GRN Type Yes User can select either 'Warehouse' or 'Shop' from the list of value. The layout for this report changes based on this value. When the user selects the GRN Type as 'Warehouse', the report is displayed as per the GRN 14-3-1/A format, and if the user selects the GRN Type as 'Shop', the report is displayed as per GRN 14-3-1/aA format. The default value for this parameter is 'Warehouse'. Quantity Precision Yes Select the required format for quantity precision from the list of value for the report output. The valueset value from the 'INV: Dynamic Precision Option for Quantity on Reports' profile option displays in the list of value.

Statutory Accounting - Fiscal Book

4-3

Parameter Required Description Amount Precision Yes Select the required format for amount precision from the list of value for the report output. The valueset value from the 'INV: Dynamic Precision Option for Quantity on Reports' profile option displays in the list of value.

Report Headings
Report Title: Goods Received Note. Organization: Inventory organization. Document Number: Receipt number. Date : Receipt date, splited into day, month, year. Invoice number/Pack slip Number: Delivery document number of supplier.

With Vehicle No: Transport vehicle number. Delegate: Name of the person who performed the delivery.

Column Headings
Report prints rows sorted by Receipt Line Number Column Headings for GRN format 14-3-1/A: No: Receipt line number. Item description: Item description from the master item. UOM: Primary unit of measure for the inventory item. Quantity according to delivery documents: Quantity: Received quantity. Unit Price: Unit price for the inventory item. Amount: Total line amount (received quantity * unit price). Column Headings for GRN format GRN 14-3-1/aA: No: Receipt line number. Item description: Item description from the master item. UOM: Primary unit of measure for the inventory item. Quantity according to delivery documents.

4-4 Oracle EMEA Add-on Localizations User Guide for Romania

Quantity according to delivery documents: Quantity: Received quantity. Commercial increase per unit:

Quantity according to delivery documents.

Increase per unit cost. Increase total amount (Received Quantity *

Commercial increase total amount: Commercial Increase per Unit).

VAT per unit: VAT applicable per unit. Total VAT: Total VAT per item (Received Quantity * VAT per Unit). Unit sale price including VAT: Unit sale price including VAT.

Total sale value for item including VAT Total sale value for item including VAT: (Received Quantity * Unit Sale Price including VAT).

Transfer Note for Goods Report


Requirement
Business requirement is to print a report for the transfers of goods from one subinventory to another subinventory, which results in decrease of quantity in one subinventory and increase of quantity in another subinventory. Report must be printed for all the transactions.

Solution Overview
Transfer Note for Goods report can be printed for the following transactions: Subinventory Transfers using Subinventory form Move Order Issue using Move Order form The Transfer Note for Goods report displays the details of movement of an item from one subinventory to another, or between two locators within the same subinventory. The report displays both the quantity and monetary information.

Statutory Accounting - Fiscal Book

4-5

Report Sample Layout

Prerequisites
Inventory organization should be present with costing enabled. Material transactions should be created in the selected inventory organizations, in selected period. Cost Manager should be run for the inventory organization. Transfer Note for Goods should be run for each inventory organization. The assumptions for the report are: For each material transaction, there will be only one debit and one-credit records. Transactions do not result in negative on-hand balance. If they are negative on-hand balances, then the report will not print the transaction. Report prints rows, sorted in following order: By Receipt Line Number By Document Number

How to Launch the Report


The report "Transfer Note for Goods Report" is launched from the Standard Request Submission (SRS) window. It must have been previously added to the requests group of the Responsibility. The format of output is PDF. Navigation Path: Respective Responsibility>View>Requests>Submit New Request>Single Request. Select the report from the list of values and submit the report.

Report Parameters
The report parameters are:

4-6 Oracle EMEA Add-on Localizations User Guide for Romania

Parameter Required Description Inventory Organization Yes Select the inventory organization from the list of value. Subinventory Yes Select the sub-inventory from the list of value; corresponding to the previously selected inventory organization. Date From Yes Enter transaction "From Date" in the Field. Date To Yes Enter transaction "To Date" in the Field. Document Number No Select the Move Orders transacted from the list of value. Transaction Number No Select the Transaction Number for the subinventory transfers from the list of value.

Report Headings
Report Title: Transfer Note for Goods (i.e.<Parameter 1>). Report Sub-Title1: Organization Page: Number of current page of total number of pages. Date: Date and time on which the report is run. The date is in DD/MM/YY format and the time is in 24-hour format.

Column Headings
Document Number: Document Number present in MTL_MATERIAL_TRANSACTIONS table. Date: Transaction date. From subinventory: The subinventory from where the item is moved. To Subinventory: The subinventory of destination. No: Serial number. Item Description: Item description from Item Master Table. Code: Item code from Item Master Table. UOM: Unit of measure of the item.

Statutory Accounting - Fiscal Book

4-7

Quantity: Transferred quantity. Unit price: Unit price of the Item. Value: Value = Quantity * Unit price. From Locator: Locator from which the item has been transferred. To Locator: Locator to which the item has been transferred.

Consumption Bill Report


Requirement
Requirement is to have a report on the inventory consumption of each item in the inventory organization, which should also show the account and cost in functional currency for the transactions. All the transactions with selected Document number are reported.

Solution Overview
This report displays the list of items issued from stock for production or internal consumption (for each job, internal order) including price information. The Consumption Bill Report displays the materials, issued from stock for production or internal consumption. The report also displays the respective natural account segment, ordered quantity, issued quantity, unit price and the monetary value of each item, which has been issued from the inventory.

Report Sample Layout

Prerequisites
In order to run the report, user needs to ensure the following: Period must be open for the inventory organization for which the report is printed.

4-8 Oracle EMEA Add-on Localizations User Guide for Romania

Receipts must be present in the selected inventory organization. Cost Manager has been run for the inventory organization. Running the Cost Manager successfully costs all transactions. The assumptions for the report are: Inventory Transactions do not result in negative on-hand balances. If they are negative on-hand balances, then the report will not print the transaction. For each material transaction, there will be only one debit and one-credit records. Report prints rows, sorted in following order: By Document Number By Item

How to Launch the Report


The report "Consumption Bill Report" is launched from the Standard Request Submission (SRS) window. It must have been previously added to the requests group of the Responsibility." It is a XML report. A new template can be developed and attached based on customer requirements. The format of output should be in PDF. Navigation Path: Respective Responsibility>View>Requests>Submit New Request>Single Request. Select the report from the list of values and submit the report.

Report Parameters
The report parameters are:

Parameter Required Description

Inventory Organization Yes Select the inventory organization from the list of value.

Subinventory Yes User can select the sub-inventory from the list of value corresponding to the selected inventory organization.

Statutory Accounting - Fiscal Book

4-9

Parameter Required Description Date Yes Enter the transaction date in the field. Document Number Yes Select the document number from the list of value.

Report Headings
Report Title: Consumption Bill. Report Sub-Title1: Organization Name. Page: Number of current page of total number of pages.

Column Headings
Document Number: Transaction number Consumption Date: Material transaction date.

From Subinventory: Subinventory from where the item has been used. Serial No: Serial number. Item: Item code from inventory organization. Description: Item description of inventory. Debit: Debit account of the issued transaction (Only the natural account Segment). Credit: Credit account of the issued transaction (Only the natural account Segment). Ordered Quantity: Ordered quantity. UOM: Unit of measure of the item. Issued Quantity: Issued quantity. Unit price: Unit price of the Item. Value: Value = Issued Quantity * Unit price.

Inventory Accounting Card Report


Requirement
Requirement is to have a report on inventory movement details for the items as mentioned below:

4-10

Oracle EMEA Add-on Localizations User Guide for Romania

Output for specific inventory organization and subinventory. Output for period interval ("Date From" to "Date To"). Present the opening, closing, receipts, shipments and transfers for every transaction valued in functional currency.

Solution Overview
Report prints the on hand quantity, receipt and issues for the given period for an item.

Report Sample Layout

Prerequisites
In order to run the report, user needs to ensure the following: Period must be open for the inventory organization for which the report is printed. Receipts must be present in the selected inventory organization. Cost Manager has been run for the inventory organization. The report includes the following Assumptions: There will be only one debit and one credit record for each material transaction. Transactions do not result in negative on-hand balance. If they are negative on-hand balances, then the report will not print the transaction. Report prints rows sorted in following order:

Statutory Accounting - Fiscal Book

4-11

By Subinventory By Item Code

How to Launch the Report


The report "Inventory Accounting Card Report" is launched from the Standard Request Submission (SRS) window. It must have been previously added to the requests group of the Responsibility." The format of output should be in PDF. Navigation: Respective Responsibility>View>Requests>Submit New Request>Single Request. Select the report from the list of values and submit the report.

Report Parameters
The report parameters are:

Parameter Required Description Inventory Organization Yes Select the inventory organization from the list of value. Subinventory Yes User can select the sub-inventory from the list of value, corresponding to the respective inventory organization selected in the previous parameter. Inventory Item Yes Select the Item code from the list of value. Date From Yes Enter "Transaction From Date " in the field. Date To Yes Enter "Transaction To Date" in the field.

Report Headings
Report Title: Inventory Accounting Card. Report Sub-Title1: Organization (i.e. <Parameter 1>). Page: <Number of Current Page> of <Total Number of Pages>.

4-12

Oracle EMEA Add-on Localizations User Guide for Romania

Report Time: The time at which the report is run.

Column Headings
Item Code: Item code from inventory organization. Item Description: Description of inventory item. Document: Transaction Date Number: Document number Doc Type: Type of transaction Ordered Quantity UOM: Unit of measure of the item. Opening Balance Quantity: On hand quantity as of "From Date" parameter.

Entry Quantity: Received quantity from the material transactions during given period. Issue Quantity: Issued quantity from the material transactions during given period. Closing Balance Quantity: Closing balance quantity calculates on hand quantity of item for each transaction as sum of opening balance quantity and transaction quantity, calculated in primary unit of measure of item. Unit price/transaction layer: Unit price for transaction. Date and Signature

Invoice Aging Report


Requirement
The requirement is to have an invoices aging report for a particular liability account as of a particular date. It is required to populate the amounts due in the various aging buckets considering the specified date. If the "As On Date" is not specified, then the date of the day the report is run is considered.

Solution Overview
This report prints the supplier balances along with the invoices details belonging to the respective liability account on specified "As of Date" parameter. This report displays all the open invoices and balances for the supplier on "As of Date" parameter. This report can be run for the functional currency only. All the security rules attached to the responsibility are considered by the report.

Statutory Accounting - Fiscal Book

4-13

Report Sample Layout

Setup
Navigation Path: Go to related Payable Responsibility>Setup>Calendar>Ageing Periods

4-14

Oracle EMEA Add-on Localizations User Guide for Romania

Note: Report considers four periods only.

Liability Account Combinations must be defined in Account Aliases. Navigation Path: General Ledger Responsibility>Setup>Financials>Flex fields>Key>Aliases

Prerequisites
Enter some invoices with different payment terms, validate and account those. Submit the Invoice Aging Report to know the Aging of the Invoices. In order to run the report, user needs to ensure the following: Supplier invoices are created in Payables. The report includes the following assumptions: Liability accounts are defined at the Supplier Site level and default at each invoice level when the invoices are created for the supplier. Invoice Aging Buckets are defined in the respective Payables Responsibility.

How to Launch the Report


The report "Invoice Aging Report" is launched from the Standard Request Submission (SRS) window. It must have been previously added to the requests group of the Responsibility." It is a XML report. The format of report output should be in Oracle report format. Navigation Path: Respective Responsibility>View>Requests>Submit New

Statutory Accounting - Fiscal Book

4-15

Request>Single Request. Select the report from the list of values and submit the report.

Report Parameters
The report parameters are:

Parameter Required Description

Sort Invoices By Yes Sorting Order either by Invoice Type or By Trading Partner Include Invoice Detail Yes User can pick up the following value from the List Of Value.

Yes: Report output displays the details of the invoice along with remaining amount.

No: Only the remaining amount is displayed.

Include Site Detail Yes User can pick up the following value from the List of Value.

Yes: Report output displays the details of Supplier Site. No: Only the remaining amount is displayed.

Minimum Amount Due No All the invoices for which the remaining amount is above this value are printed in the report. Maximum Amount Due No All the invoices for which the remaining amount is below this value are printed in the report. Invoice Type No List of value displays all the Invoice types. User can pick up any of the value from the List of Value. The report output displays all the open invoices for the specific invoice type. If the user didn't select any value, the report considers all the Invoice Types.

4-16

Oracle EMEA Add-on Localizations User Guide for Romania

Parameter Required Description Trading Partner No User can select the supplier name from the list of values. If a value is not selected, then the report is run for all the suppliers. Aging Period Name Yes List of value displays the aging periods defined in the system. User should pick up any of the aging period name from the list of value. As Of Date No This parameter is a user enterable field. User can enter the date in this field. If the user doesn't enter any date, report considers the system date as default date. Liability Account No User needs to select the liability account combination for the list of values if the report has to run for a particular account. If the user doesn't give any value then report considers all the liability account for the operating unit.

Report Headings
Report Title: Invoice Aging Report. Page: Number of current page of Total number of pages. As-of-Date: User can insert any date prior to system date. Liability Account: Liability account for which user has submitted the report.

Column Headings
Liability Account: Liability account of the supplier invoice. Trading Partner: Name of the supplier. Invoice Number: Invoice number. Voucher Number: Document sequence number of the invoice. Due Date: Due date of the respective invoice. Days Due: Number of days due of the invoice calculated based on the 'As Of Date' parameter. %Open:% of unpaid amount of the invoice. Amount Remaining: Unpaid amount of the respective invoice.

Statutory Accounting - Fiscal Book

4-17

Aging Buckets (As per the Aging report selected in parameter "Aging Period Name"): Remaining payable amount is shown under different aging periods based on the aging period terms.

Trial Balance Report


Requirement
The requirement is to print the summary account balances for the natural account segment values that belong to the respective parent account and child account.

Solution Overview
The Trial Balance Report helps in the period end and year-end reconciliation process. This report has two layouts: 'Analytical' and 'Syntetical'. 'Analytical' displays all the natural account segment balances and 'Syntetical' displays all the parent account balances. This report displays opening balances, period activity balances, year-to-date balances and the closing balances for a given period. This report can be run for the functional currency or transaction currency for the Ledger. This report is sensitive to the respective security rule, attached to the responsibility.

4-18

Oracle EMEA Add-on Localizations User Guide for Romania

Report Sample Layout


Analytical

Syntetical

Setup
In order to run the report, user needs complete the following setups: 1. Required roll up groups to be setup. 2. Required summary templates to be set up in general ledger. 3. For the purpose of testing account values are taken in the distribution account of the invoices in payables, in transactions from receivables and manual journals in the General ledger Profile Options CLE: GL Trial Balance Child Template, CLE: GL Trial Balance Parent Template, CLE: GL Trial Balance Subparent Template CLE: GL Trial Balance Parent Rollup and CLE: GL Trial Balance Subparent Rollup are already defined in the application and having value at the site/responsibility level as the report covers 3 levels of relationship (child, parent and subparent). 4. The rollup groups assigned to Profile options CLE: GL Trial Balance Parent Rollup and CLE: GL Trial Balance Subparent Rollup should match with the rollups assigned to summary templates attached to CLE: GL Trial Balance Parent Template and CLE: GL Trial Balance Subparent Template. 5. Chart of Accounts includes parent accounts in the natural accounting segment, which are flagged as parent account.

4-19

Statutory Accounting - Fiscal Book

1. Define Rollup Groups

Below is the screenshot of the "Rollup Groups" defined in general ledger responsibility : Navigation Path: Setup>Financials>Flexfields>Key>Groups

2. Define Summary Templates

Below is the screenshot of the "Summary Templates" defined in general ledger responsibility: Navigation Path: Setup>Financials>Accounts>Summary

Parent Template can also be created in a similar way as above.

3. Define Profile Options

Below is the screenshot of the "Profile Options" assignment in system Administrator responsibility: Navigation Path: System Administrator >Profile > System

4. Rollup Groups assignment to Chart of Accounts.

The rollup group assignment to the natural accounts should be done based on the following logic: Report should allow summarizing balances and activities for all accounting code combinations, natural account segment value belongs to the range assigned to given parent account. For example, there are following values in the account segment:
Value 401-023 401-022 401-021 401-013 401-012 401-011 401-02 401-01 401 Description Liability - National Suppliers of goods Liability - National Suppliers of services Liability - National Sundry Suppliers Accruals on National Suppliers of goods Accruals on National Suppliers of services Accruals on National Sundry Suppliers Liability - National Suppliers without accruals Accruals on National Suppliers Liability - National Suppliers Parent (P) / Child (C) C C C C C C P P P

where

Where hierarchy is defined:

401 401-02 401-01

401-011

401-012

401-013

401-021

401-022

401-023

Report should allow getting summaries for 401 parent account (synthetic), which means summary of 401-01 and 401-02 (parent accounts). Summary for 401-01 means summary of all accounting code combination, where account value is one of child values: 401-011, 401-012, 401-013 and summary for 401-02 summary of all accounting code combination, where account segment value is one of 401-021, 401-022, 401-023. segment means child values:

4-22

Oracle EMEA Add-on Localizations User Guide for Romania

Levels and Rollup groups Parent accounts are grouped on levels in the hierarchy. Here is an example for the provided code:
Value 401 401-01 401-011 401-012 401-013 401-02 401-021 401-022 401-023 Parent Yes Yes No No No Yes No No No nivel 4 Group parinte nivel 4 Level

Below are the screenshots of the Rollup Groups assignment to Chart of Accounts in general ledger responsibility: Navigation Path: Setup>Financials>Flexfields>Key>Values Please Note: The assignments below are indicative and should be done based on the requirements of the user in a manner below and on the logic explained in the above extract.

Prerequisites: In order to run the report, user needs to ensure the following: All the journals are posted in the respective General Ledger responsibility Rollup Groups and Summary Templates setup completion as described in the setup section and attached at the respective natural account segment Value set. Respective values need to be attached at the following profile options described in the setup section. This report displays the summary account balances and activities for the natural account segment values that belong to the respective parent account and child account. This report has layouts: 'Analytical' and 'Syntetical'. 'Analytical' displays the entire natural account segment balances and 'Syntetical' displays all the parent account balances.

Report prints rows sorted in following order: By Natural Account Segment

How to Launch the Report


The report "CLE: Trial Balance Report" is launched from the Standard Request Submission (SRS) window. It must have been previously added to the concerned Request Group of General Ledger responsibility. It is a XML report. Navigation Path: Respective Responsibility>View>Requests>Submit New Request>Single Request. Select the report from the list of values and submit the report.

Report Parameters
The report parameters are:

Parameter Required Description Ledger Name Yes Select the ledger for which the report needs to be run. Period Name Yes User needs to select the respective period name for which the report needs to be run. Balancing Segment Yes Balancing segment values of Account key flex field for the ledger, which is retrieved from the "GL Ledger Name" profile option attached to the respective responsibility. Account From Yes User needs to select an account from the list of natural account segment values. Account To Yes User needs to select an account from the list of natural account segment values. Balance Type Yes User can select one of the following values:

Analytical: It displays all the natural account segment balances.

Syntetical: It displays all the parent account balances.

Statutory Accounting - Fiscal Book

4-23

Parameter Required Description Currency Yes It displays all enabled currency for the set of book.

Report Headings
Report Title: Analytical Trail Balance or Syntetical Trial Balance. Date: Date and time on which the report is run. The date is in DD/MM/YYYY format and the time is in 24-hour format. Page: Number of current page of total number of pages. Ledger Name: Ledger as given at parameter level. Period : Period as given at parameter level. Account from : As given at parameter level. Account To: As given at parameter level. Currency: Currency as per parameters.

Column Headings
Account Value: Natural account segment. Account Description: Account description. Beginning Balance: Debit/Credit: Net opening balance of the natural account segment value. PTD Activity: Debit/Credit: Net period-to-date balance of the natural account segment value. YTD Activity: Debit/Credit: Net year-to-date balance of the natural account segment value. Ending Balance: Debit/Credit: Net ending balance of the natural account segment value.

CLE: GL Trial Balance Report - Yearly


Requirement
To print the summary account balances and activities for the natural account segment

4-24

Oracle EMEA Add-on Localizations User Guide for Romania

values that belong to the respective parent account and child account with opening balances of the first period.

Solution Overview
This report prints the summary account balances and activities for the natural account segment values that belong to the respective parent account and child account. It prints beginning amounts of first period of the fiscal year. CLE: GL Trial Balance Report - Yearly helps in the period end and year-end reconciliation process. This report has 2 layouts: 'Analytical' and 'Syntetical'. 'Analytical' displays all the natural account segment balances and 'Syntetical' displays all the parent account balances. This report displays opening balances of the first period, current period activity balances, total amount balances of the current fiscal year and the closing balances for a given period. This report also can be run for the functional currency or transaction currency for the ledger. This report is sensitive to the respective security rule, attached to the responsibility.

Report Sample Output


Analytical:

Statutory Accounting - Fiscal Book

4-25

Syntetical:

Setup
Please follow the same setups for the Trial balance Yearly Report as done for Trial Balance Report.

Prerequisites
In order to run the report, user needs to ensure the following:

4-28

Oracle EMEA Add-on Localizations User Guide for Romania

1. 2.

All the journals are posted in the respective General Ledger responsibility Rollup groups and summary templates setup completion as described in the Setup section and attached at the respective natural account segment valueset. Respective values need to be attached at the following profile options described in the Setup section.

3.

This report displays the summary account balances and activities for the natural account segment values that belong to the respective parent account and child account. This report is having two layouts: 'Analytical' and 'Syntetical'. 'Analytical' displays all the natural account segment balances and 'Syntetical' displays all the parent account balances. Report prints rows sorted by the Natural Account Segment.

Report Parameters
Parameter Required Description Ledger Name Yes Select the ledger for which the report needs to be run. Currency Yes User need to select the code from the LOV displaying the list of currency code enabled for the selected ledger. Period Name Yes Users need to select the period name for which the reports need to be run. Balancing Segment Yes Balancing segment values of the ledger attached to the responsibility launching the report. Account From Yes Natural account should be selected from the LOV. Account To Yes Natural account should be selected from the LOV.

Statutory Accounting - Fiscal Book

4-29

Parameter Required Description Balance Type Yes User can select one of the following values:

Analytical: It displays all the natural account segment balances. Syntetical: It displays all the parent account balances.

How to Launch the Report


The report "CLE: GL Trial Balance Report - Yearly" is launched from the Standard Request Submission (SRS) window. It must have been previously added to the requests group of the used responsibility. Navigation Path: Respective Responsibility>View>Requests>Submit New Request>Single Request. Select the report from the list of values and run.

Report Heading
Report Title: Trial Balance Report-Yearly. Report Sub-Title1: Report Type (i.e. Synthetically or Analytical). Date: Date on which the report is run. The date is in DD/MM/YYYY format. Page: Number of current page of total number of pages. Ledger Name: Ledger given at parameter level. Balancing Segment: Balancing segment given at parameter level. Period: Period given at parameter level. Account from: Accounts given at parameter level. Account To: Accounts given at parameter level. Currency: Currency selected at parameter level.

Column Headings
Account Value: Natural account segment values. Account Description: Description of the natural account segment values. Beginning Balance: Debit/Credit: Beginning balances of the natural account segment

4-30

Oracle EMEA Add-on Localizations User Guide for Romania

value for the first period of the fiscal year. Current Period: Debit/Credit: Current period balance of the natural account segment value for the selected period of current fiscal year. Total Amounts: Debit/Credit: Current year-to-date balances of the natural account segment value of the current fiscal year. Ending Balance: Debit/Credit: Sum of the net begin balance and total amounts.

Statutory Accounting - Fiscal Book

4-31

5
Transaction Tax

Introduction
There are two "Transaction Tax" related Reports
1. 2.

CLE: AR Sales Ledger Report CLE: AP Purchase Ledger Report

Each Report is explained in detail below.

CLE: AR Sales Ledger Report


Requirement
The meaning of this report is to outline the realized sales and the tax (VAT) cashed in from those operations, which will be paid or compensated with the tax (VAT) due to the acquisitions. This legal report is used for: Additional journal for the registration selling material values or for carried services Document to record monthly collected VAT Document, which you control operations that you register to your accountancy. These transactions are recorded mainly in the Account Receivables module, but for special cases they can be introduced in General ledger module, in specific journals or in Account Payables.

Solution Component
The Sales Ledger Report (VAT Sales Register) is an internal document representing together with Purchasing Ledger report (VAT Purchasing Register) a basis for the Company VAT Report the document prepared for the fiscal authorities; in the same time the report offers visibility and control over the correct application of the Romanian tax law both for the internal control and for the Fiscal authority. The business processes feeding with data the Sales ledger report are transactions related to the customers that contain VAT. This report is intended for internal use, in order for the fiscal authority to compare it with the tax (VAT) deduction document.

Setups
The Report CLE: AR Sales Ledger Report has been created to generate the VAT report for Romania. By default all transactions will be reported in CLE: AR Sales Ledger Report. If the user due to requirements of law does not want to display a transaction in the report a LDFF has to be updated at Transaction Header level RO.INCLUDE_IN_VAT_REGISTER The AR transactions will not appear in the CLE: AR Sales Ledger Report if the CLE: Additional Info On Transaction LDFF with the context RO at transaction header level is chosen as No,else the transaction will appear in the CLE: AR Sales Ledger Report. Tax Rate The rate can be 5%,9%, 19%, 24%and 0. The tax Rates name should reflect the LDFF information that is being chosen for a particular Tax Rate. Based on the LDFF value specified at the Tax rate the data will be displayed in the report. Tax Status The Tax Status plays a key role for the data to be displayed in various columns of the report. While defining tax codes in R12 the user should ensure the correct Tax Status is chosen The Tax Status should be VAT for all Tax Rates with rate 5%, 9%, 19%,24%. VAT0% For All Exempt Operations tax rates the Tax Status should be EXEMPT. The rate will be zero in this case For All Non Taxable Operations the Tax Status should be NON_TAXABLE. The rate will be zero in this case.

Customer Site

Customer shipping site is a very important factor for data to be displayed in a column. It helps to confirm if the transaction is related to Intra-EU, Abroad or with in Romania. In case the shipping site is not entered for the transaction then the customer bill to site entered on the transaction is used for determining if the transaction is related to Intra-EU, Abroad or with in Romania.

LDFF at Tax Code definition level for considering in the Report

Based on the LDFF value specified at the Tax Code definitions the tax code will be evaluated for considering in the report. If the value is set, as Yes then the Tax Code will be considered for including the transactions in the report else will not be considered for the report.

LDFF at Tax Code definition level for determining the Territory Applicability

As Tax Codes are Territory based for ex-few Tax Codes are applicable to either Domestic or Abroad or Intra-EU or to all territories, it is essential to specify the Territory applicability while defining the Tax Codes. Based on the Territory value specified at the Tax Code definition level the data will accordingly appear in the report. For ex-Tax Type Code VAT with tax rate as 5% is applicable only for Domestic. Hence while defining the Tax Rate 5% with Tax Type code as VAT the user needs to specify the Territory as Domestic so that the data appears in the report accordingly.

Deduction Right

Based on whether the Transaction is with Deduction Right or with out deduction right, data will be displayed in various columns. The information for Deduction right need to be entered in the Localization DFF at Tax Rate Level in the context RO.VAT_RATE_DETAILS

EU Delivery

In Case of Goods delivered to EU which are exempt from Operations and are with Deductions Right then additional LDFF information has to be entered at Tax Rate Level while creating the tax rate to categorize it whether it is Exempt under Exempt Acc. with are.143 alin. (2) lit. a) & d) from fiscal code or Exempt Acc. with are.143 alin. (2) lit. Bb & c) from fiscal code . The information for this has to be entered in the Localization DFF at Tax Rate Level in the context RO.VAT_RATE_DETAILS.

Special Regime

Certain goods and services are applicable for special regime rate, in this case additional LDFF information has to be entered at Tax Rate Level to categorize it as Special Regime. a) Open Tax rate page and search for the VAT rates created.

b) Click on the Tax Rate Code and update CLE: RO Tax Rate Info LDFF.

c) Select an associated value for the vat rate that is being setup.

If any information mentioned above mismatches then the data will not appear at all or will not appear in the correct column of the CLE: AR Sales Ledger Report.

General Ledger

In case of entry of miscellaneous transactions in General Ledger pertaining to Accounts Receivable and which need to be displayed in the CLE: AR Sales Ledger Report, you need to enter the following additional information using the Localization DFF CLE RO VAT Information at Journal Line Level with the context RO.Customer VAT for the below segments Customer Name Origin of acquisition Whether the customer is based in EU, Romania or outside EU and Romania. Further the Tax should be set as Required at the Journal Header level. In addition to the above Enable Tax Journal Entry while doing Accounting Setup. Complete the set up for GL Tax Options.

Descriptive Flexfield Context and Value set Information Descriptive Flexfield Name CLE: Additional Info On Transaction (Accounts Receivable) LDFF CLE: Additional Info On ZX Tax Rates (EB Tax) LDFF Context Segments Values

RO

Include in VAT Register

Yes/No

RO.VAT_RATE_D RATE_DETAILS ETAILS

INCLUDE APPLICABLE_T ERRITORY

VAT0_DED VAT0_NO_DED EXEMPT_ART143_A&D EXEMPT_ART143_B&C EXEMPT_DED EXEMPT_NO_DED OFFSET_ART150_B&G OFFSET_ART160 VAT19_SPECIAL_ART1 52_1&2 OFFSET_STANDARD OFFSET_SERVICES Yes/No ABROAD ALL DOMESTIC DOMESTIC_ABROAD DOMESIC_INTRA-EU INTRA-EU

CLE: Additional Info for Journal Lines (In GL) LDFF

RO.Customer VAT

INTRA-EU_ABROAD CUSTOMER_NA Customer Name ME ORIGIN_OF_AC Domestic QUISITION Intra-EU Abroad

Profile Options

Enter information for the below Profile options at site level.


Profile MO: Security Profile GL: Ledger Name MO: Operating Unit Site Level Vision Romania Vision Romania Vision Romania User

USER Procedure

1) Login into Oracle R12, Select Receivables responsibility and create a new Transaction in AR.

Enter The Invoice source. Select the Invoice Class; enter Invoice date and GL date. Enter the Customer Ship to site & Bill to Site and Click on Save Icon. 2) By default all transactions will be reported in CLE: AR Sales Ledger Report. If the user due to requirements of law does not want to display a transaction in the report, CLE: Additional Info On Transaction LDFF has to be updated at Transaction Header level by navigating to Actions CLE: Additional Info On Transaction.

3) If the transaction need not be reported in the VAT Register then select the context RO and choose No for Include in VAT Register Include segment.

4) Enter Line Information for the Transaction. Enter the Amount and then select the Tax code. Please ensure that proper judgment is taken while selecting the tax code based on the Site, Tax Status. Click on (B) Save

5) Complete the Transaction by clicking on (B) Complete. And post the Transaction to General Ledger following the posting procedure.

6) To generate CLE: AR Sales Ledger Report submit a standard single request and Select CLE: AR Sales Ledger Report.

Parameters for the request

Parameter

Required

Default Value

LOV

Customer Name GL Posting Status AR Transaction Status From Date To Date

No Yes Yes Requir ed Requir ed

Blank Posted Compl ete Blank Blank

LOV will display all the customers GL Posting Status Will have Posted, Un posted and ALL. AR Transaction Status will have Complete, In Complete and ALL LOV will display Calendar LOV will display Calendar

Customer Name - In case the report needs to be run for a single customer then select the customer from the LOV. GL Posting Status This Parameter is to include all Journals posted to GL or Unposted to GL or both Posted & Unposted (ALL). By default the parameter is Posted. In case the parameter is chosen as Posted then all the Journals Posted in General Ledger will appear in the report and in case the parameter is chosen as Not Posted then all the Journals, which are not yet posted, will appear in the report. AR Transaction Status This parameter will enable you to see AR transactions only completed or Incomplete or both complete and incomplete. By default the parameter is Complete. From date Select From date for E.g. beginning of the month 01-Jan-2008 To date Select To date for e.g. end of the month 31-Jan-2008

Click on (B) OK 7) To generate the Report in Romania, Click on (B) Language Settings and check the box for Romanian. To generate the report in American English then Click on (B) Language Settings and check the box for American English.

8) The default output for the report is PDF. To generate the output of the report in Excel, Click on (B) Options in SRS form and click on LOV in the Format and select Excel. Click on (B) Submit

9) The request will be submitted to view the output Click on (M) View and select Requests. Select the Request and Click on (B) View Output. Declaration Oracle is not responsible for any modifications that will be done by the users in the out put of this report in EXCEL format Below is a sample layout of the report in PDF format.

User Procedure for Entering Miscellaneous Transaction pertaining to Accounts Receivable in General Ledger

1) Select any Journal name and Category. The Journal name will be the document number in CLE: AR Sales Ledger Report. Click on LOV and select required for Tax field in the Journal Header. The TAX button will get activated. Enter Account line information and Amount Exclusive of Tax for the line for which tax is being calculated. Enter the other line Inclusive of Tax

4) Enter Tax Code, select the tax code with type OUTPUT. Output tax pertains to Accounts Receivable and Input tax pertains to Accounts Payable.

5) Click on the TAX Button and the journal will be saved, a new line will be created with the tax account and tax amount. 6) The Journal will be saved a new tax line will be created. The tax amount will be automatically calculated. The TAX button will now change to POST button

7) Select the saved Journal Line and Click on (M) Tools and select CLE: RO VAT Information. Select the context RO.Customer VAT

8) Enter information for Customer Name if any and Delivery Location (EU, DOMESTIC or OUTSIDE EU & ROMANIA)for transactions >> (B) OK and save.

9) Post the transaction to General Ledger and generate CLE: AR Sales Ledger Report. Submit a standard single request and Select CLE: AR Sales Ledger Report. Enter the information for the Parameters for the request.
Report Column Headings

0) Sl. No This is the Serial Number 1) Invoice Number - This is the Document Number, In case of AR transactions, this will be a transaction number and in case of General Ledger it will be the Journal Name 2) Invoice Date This is the Invoice Date of the transaction/in Case of GL this is the Journal creation date 3) Customer Name This is the customer name in Accounts Receivable, in General Ledger, the LDFF with the context RO.Customer VAT information need to be filled for customer name to appear in the report. In case of Transactions entered in Accounts Payable module with Offset taxes this will display the Supplier name for such Invoices. 4) Tax Registration Code The tax registration number of the customer will be displayed here. The Tax Payer ID entered for the customer will be displayed here. 5) Total (Tax Base+ Vat Value) - This is the sum total of the Tax Base and VAT value 6) Tax Base - This is the sum total of the line amounts for a particular Tax Code 7) Vat Value This is the sum total of tax amount for a particular Tax Code. 8) Territory This is to identify the Territory to which the Invoice belongs. The Territory is determined based on the Supplier Site entered on the Invoice Header. 9) Tax Code This displays the Tax Code applied to the Invoices. Only those Tax Codes to which the Include in Report segment is set to Yes are displayed here. 10) Description This displays the Description derived based on the combination of Territory, LDFF values and the Tax Codes.

The below table outlines the possible Descriptions based on the combination of Tax Type code, Territory and the LDFF values specified:
Territory based on Ship To Location and LDFF value specified at Tax Code level for Localization Descriptive Territory Flexfield values specified in Applicability Tax Rate definition
ABROAD INTRA EU DOMESTIC ABROAD ABROAD N/A N/A N/A Deduction Rights - YES Deduction Rights - NO Special Regime VAT_SPECIAL_ART152_1&2 N/A Deduction Right - YES DEduction Right - NO

TAX TYPE CODE


VAT VAT VAT VAT VAT

Description in the Report Output


Abroad VAT Taxable Operations Intra EU VAT Taxable Operations Domestic VAT Taxable Operations Abroad VAT Taxable Operations with Deduction Right Abroad VAT Taxable Operations with out Deduction Right

VAT

ABROAD

Abroad Goods and Services with Special Regime Non Taxable Operations Domestic Exempt Operations with Deduction Right Domestic Exempt Operations with out Deduction Right

NON TAXABLE DOMESTIC EXEMPT EXEMPT DOMESTIC DOMESTIC

EXEMPT

INTRA EU

EU Delivery - Exempt Acc. art.a) & d) Exempt Operations with EU Delivery Acc Art a & d EU Delivery - Exempt Acc. art.b) & c) Exempt Operations with EU Delivery Acc Art b & c

EXEMPT VAT with OFFSET code attached VAT with OFFSET code attached VAT with OFFSET code attached VAT with OFFSET code attached VAT with OFFSET code attached VAT with OFFSET code attached

INTRA EU

INTRA EU

OFFSET STANDARD

Intra EU Operations with OFFSET STANDARD

INTRA EU

OFFSET SERVICES

Intra EU Operations with OFFSET SERVICES

INTRA EU

OFFSET ART 150 B & G

Intra EU Operations with OFFSET ART 150 B & G

ABROAD

OFFSET ART 150 B & G

Abroad Operations with OFFSET ART 150 B & G

DOMESTIC

OFFSET ART 150 B & G

Domestic Operations with OFFSET ART 150 B & G

DOMESTIC

OFFSET ART 160

Domestic Operations with OFFSET ART 160

Summary Section of the Report

Tax Code The report will group the Tax Base and Vat Value by Tax Codes here. Territory - The report will group the Tax Base and Vat value by Territory here. Number of Documents The report will group the Invoices by Territory, Tax Code and Description and will display the Document count here. Total (Tax Base+ VAT value) - This is the sum total of the Tax Base and VAT value Tax Base- The report will group the Tax Base by Territory, Tax Code and Description and will display the sum total of Tax Base in this column. Vat Value - The report will group the Vat Value by Territory, Tax Code and Description and will display the sum total of Vat Value in this column. Description The report will group the Tax Base and the Vat value by Description here.

Report Output

The report output layout shall be as under-

Parameter Check and Error Handling

The parameters From Date and To Date are mandatory parameters. . In case the user does not provide the value and submits the report, then error should be handled as explained below

Exception Condition

Status

Post Process

Error Message

Value for parameter From Date not entered

Message should be displayed.

User should choose the value from the LOV. Program should not be submitted. User should choose the value from the LOV. Program should not be submitted.

Please enter a value for the parameter or segment From Date.

Value for paramter To Date not entered

Message should be displayed.

Please enter a value for the parameter or segment To Date.

Assumptions

This request is created for Oracle E-business Suite Version Release 12.0.0. The EB tax setup is completed in R12 & GL Tax Options have been set. It is assumed all the required setups are done. The CLE: Additional Info On Transaction LDFF with the Context RO and the segment Include in VAT Register is implemented at AR Transaction Header level. The Localization DFF CLE: Additional ZX Rates Information is implemented at Tax Rate level in EB-Tax The Localization DFF CLE: Additional Info for Journal Lines is implemented at GL Journal Line Level To Cancel/reverse an Invoice a credit memo should be raised and applied instead of using Invoice delete. Tax Status and Tax rate, Site address & DFF information are critical for the data to appear in the correct column of the report. In case of GL Tax journal if the user wants to enter data for multiple customers then one journal should be created for each customer.

CLE: AP Purchasing Ledger Report


Requirement
The meaning of this report is to outline the operations, with the tax (VAT) paid due to the acquisitions. These transactions are recorded mainly in the Accounts Payable module, but for special cases they can be introduced in General ledger module, in specific journals. This legal report is used for: Additional journal for the registration selling material values or for carried services Document to record monthly paid VAT Document, which you control operations that you register to your accountancy.

Solution Component
The business processes feeding with data the CLE: AP Purchasing ledger report are transactions related to the suppliers that contain VAT. This report is intended for internal use, in order for the fiscal authority to compare it with the tax (VAT) deduction document.

Setup
The Report CLE: AP Purchasing Ledger Report has been created to generate the VAT report for Romania. The data in the report will be displayed in various columns is based on the below Information. By default all transactions will be reported in CLE: AP Purchasing Ledger Report. If the user due to requirements of law does not want to display a transaction in the report the GDFF with Context RO.INCLUDE_IN_VAT_REGISTER has to be updated at AP Invoice Header level to No. RO.INCLUDE_IN_VAT_REGISTER : The AP Invoice will not appear in the CLE: purchasing Ledger Report if the LDFF of Actions CLE: Additional Info On Invoices with Context RO.INCLUDE_IN_VAT_REGISTER at transaction header level is chosen as NO for the segment INCLUDE, else the transaction will appear in the CLE: AP Purchasing Ledger Report. Tax Rate The rate can be 5%, 9%, 19%,24%, 19% with Offset Tax,24% with Offset Tax and 0. The tax Rates name should reflect the LDFF information that is being chosen for a particular Tax Rate. Tax Status The Tax Status plays a key role for the data to be displayed in various columns of the report. While defining tax codes in R12 the user should ensure the correct Tax Status is chosen The Tax Status should be VAT for all Tax Rates with rate 5%,9%, 19%,24%,24% with Offset Tax and 19% with Offset Tax. For All Exempt Operations tax rates the Tax Status should be EXEMPT. The rate will be zero in this case For All Non Taxable Operations the Tax Status should be NON_TAXABLE. The rate will be zero in this case. For transactions with mandatory VAT payment a VAT rate has to be chosen and then should be offset by offset-VAT rate. Set up offset tax rate with Tax Status offset and with tax rate (19%/-24%) and attach the offset tax rate to a Tax rate with the Status as VAT. Hence for this purpose two tax rates for ART150 B&G and for ART160 should be defined with rate percentage as 19%/24% and the offset tax rate with rate percentage as 19%/-24% should be assigned to the above 2 tax rates.

Offset VAT

Based on whether the Transaction is applicable for Art150. B&G or Art160 the data for Goods and Services with Mandatory VAT Payment will be displayed in the report. Further in case of transaction with Standard Offset the data will be displayed in the Taxable Intra-EU goods column of the report. All this information will be derived based on the value chosen for the LDFF CLE: RO Tax Rate Info while defining the Tax Rate.

LDFF setup at Tax Rate level for considering in the report

Based on the LDFF value specified for the Segment Include in Report at the Tax Rate level the same will be evaluated for considering in the report.

LDFF setup at Tax Rate Level to determine the Territory Applicability

As Tax Codes are Territory based for ex-few Tax Codes are applicable to either Domestic or Abroad or Intra-EU or to all territories, it is essential to specify the Territory applicablity while defining the Tax Rates. Based on the Territory value specified at the Tax Rate definition level the data will accordingly appear in the report

LDFF setup at Tax Rate level

Based on the values specified in the LDFF at Tax Rates the data will be displayed in various columns of the report.

Supplier Site

Supplier site entered on the transaction is a very important factor for data to be displayed in a column. It helps to determine if the transaction is related to Intra-EU, Abroad or with in Romania.

General Ledger

In case of entry of miscellaneous transactions in general Ledger pertaining to Accounts Payable and which need to be displayed in the CLE: AP Purchasing Ledger Report, you need to enter the following additional information using the Localization DFF CLE: RO VAT Information at Journal Line Level using the context RO.Supplier VAT. Supplier Name
In addition to the above -

Enable tax Journal Entry while doing Accounting Setup for the Ledger. Complete the set up for GL Tax Options

Origin of acquisition Whether the Supplier is based in EU, Romania or outside EU and Romania. Further the Tax should be set as Required at the Journal Header level. In addition to the above Enable tax Journal Entry while doing Accounting Setup for the Ledger. Complete the set up for GL Tax Options
Descriptive Flexfield Context and Value set Information
Descriptive Flexfield Name
Context Segments Values

CLE: Additional Info On Invoices LDFF CLE: Additional Info for Journal Lines (In GL) LDFF

RO.INCLUDE_IN_VAT_ REGISTER RO.Supplier VAT

INCLUDE

Yes/No

Supplier Name ORIGIN_OF _ACQUISIT ION

Supplier Name

Domestic Intra-EU Abroad

CLE: Additional Info On ZX Tax Rates (EB Tax) LDFF

RO.VAT_RATE_DETAIL S

RATE_DET AILS

VAT0_DED

VAT0_NO_DED EXEMPT_ART143_A&D EXEMPT_ART143_B&C EXEMPT_DED EXEMPT_NO_DED OFFSET_ART150_B&G OFFSET_SERVICES OFFSET_STANDARD OFFSET_ART160 VAT19_SPECIAL_ART152_1&2 INCLUDE APPLICAB LE_TERRIT ORY Yes/No ABROAD ALL DOMESTIC DOMESTIC_ABROAD DOMESIC_INTRA-EU INTRA-EU INTRA-EU_ABROAD

Profile Options

Enter information for the below Profile options at site level.


Profile MO: Security Profile GL: Ledger Name MO: Operating Unit Site Level Vision Romania Vision Romania Vision Romania User

USER Procedure 1) Login into Oracle R12, Select Payables responsibility and Create a new Standard Invoice in AP. Enter the Supplier Name/Number, Supplier Site, Invoice Date, Invoice Number, Invoice Currency and Invoice Amount and press Save Icon.

2) By default all transactions will be reported in CLE: AP Purchasing Ledger Report. If the user due to requirements of law does not want to display a transaction in the report the LDFF of Actions CLE: Additional Info On Invoices with Context RO.INCLUDE_IN_VAT_REGISTER at transaction header level has to be updated to NO for the segment INCLUDE.

3) Select No for the Segment Include to exclude this transaction from the report. Click on (B) Ok. 4) Click on the Lines tab and enter the Line Amount, Tax Classification code and Press Save icon >> Click on (B) Tax Details

5) Click on (B) Tax Details to modify or update Tax rate information >> Press (B) OK.

6) In the Lines Tab click on (B) Distributions and enter invoice distribution information & Press Save Icon

7) Validate the Invoice and Post the transaction to General Ledger.

The Invoice status will be Validated and Accounted

8) To generate CLE: AP Purchasing Ledger Report submit a standard single request and Select CLE: AP Purchasing Ledger Report. Select the appropriate parameter for Operating Unit Field & Enter the information for the parameters
Parameters for the request

Parameter

Required

Default Value

LOV

Period Posted Parameter Vendor Name

Yes Yes No

NULL Posted NULL

All Open & Closed periods GL Posting Status Will have Posted, Un posted and ALL. List of All Suppliers

Period select the period from list of value, the Lov will show all period that are open and closed for the Payables module. Posted Parameter This Parameter is to Include all posted or unposted transactions or ALL Transactions. By default the parameter is Posted. If the parameter is chosen as un-posted then all Invoices that are not accounted and Journals that are not posted will appear in the report. If the parameter is chosen as posted then all Invoices that are accounted and Journals that are posted will appear in the report. Vendor Name The Vendor name parameter should list all the suppliers. In case the user wants to run the report for a specific supplier then the specific supplier can be chosen as a parameter.

9) To print the report in Romanian or American English languages click on (B) Language settings and check the box beside the Language name.

10) To generate the output of the report in Excel format click on LOV for Format column and select Excel. Press (B) OK & (B) submit to submit the request.

Declaration - We are not responsible for any modifications that will be done by the users in the out put of this report in EXCEL format. Below is a sample layout of the report in English

User Procedure for Entering Miscellaneous Transaction pertaining to Accounts Payable in General Ledger 1. Select any Journal name and Category. The Journal name will be the document number in CLE: AP Purchasing Ledger Report. Click on LOV and select required for Tax field in the JE Header. The TAX button will get activated. 2. Enter Account line information and Amount Exclusive of TAX for the line for which tax is being calculated. Enter the other line Inclusive of VAT.

3. Enter Tax Code; select the tax code with type INPUT. Output tax pertains to AR and Input tax pertains to AP.

4. Click on the TAX Button and the journal will be saved, a new line will be created with the tax account and tax amount. 5. The Journal will be saved a new tax line will be created. The tax amount will be automatically calculated. The TAX button will now change to POST button

6. Select the saved Journal Line and Click on (M) Tools and select CLE: RO VAT Information. Select the context RO.Supplier VAT

7. Enter Information for Supplier Name, Select Origin Of acquisitions in order to confirm whether the supplier site is based in Romania, EU or Non-EU Click on (B) OK >> Click on (B) Save >> Post the Journal

8. Post the transaction to GL. 9. Submit a standard single request and Select CLE: AP Purchasing Ledger Report. Enter the information for the Parameters for the request. Report Column Headings 0) No This is the Serial Number 1) Document Number - This is the Document Number, In case of AP transactions, this will be a transaction number & In case of GL it will be the Journal Name 2) Date This is the Invoice Date of the transaction and in Case of GL this is the Journal creation date 3) Supplier (Name) This is the Supplier name in AP, in GL the LDFF RO VAT Information need to be filled for supplier name to appear in the report. 4) Tax Registration Code The tax registration number of the Supplier will be displayed here. 5) Prepayment This is the Prepayment number applied to the Invoice. In Case of prepayments the prepayment Invoice will appear in the report as a normal invoice, once the prepayment Invoice is applied to a standard Invoice then the prepayment invoice number and the prepayment amount will appear in the prepayment column beside the Invoice to which it has been applied. Further, for the Standard Invoice, the amounts will appear for the remaining amounts (the balance amounts after reducing the prepayment applied amounts) in the respective columns of the report.

6) Prepayment Amount The prepayment Amount column displays the prepayment amount applied to the Invoice. 7) Total (Tax Base +Vat Value) This is the sum total of the Tax Base and VAT value 8) Tax Base - This is the sum total of the line amounts for a particular Tax Code 9) Vat Value This is the sum total of tax amount for a particluar Tax Code. 10) Territory This is to identify the Territory to which the Invoice belongs. The Territory is determined based on the Supplier Site entered on the Invoice Header. 11) Tax Code This displays the Tax Code applied to the Invoices. Only those Tax Codes to which the Include in Report segment is set to Yes are displayed here. 12) Description This displays the Description derived based on the combination of Territory, LDFF values and the Tax Codes. The below table outlines the possible Descriptions based on the combination of Tax Type code, Territory and the LDFF values specified
Tax Type Code Territory based on Supplier Site entered on Transactions LDFF Values specified at Tax Code definition level for Offset detail Description in the Report Output

VAT VAT VAT

DOMESTIC ABROAD

N/A N/A OFFSET STANDARD OFFSET SERVICES OFFSET_ART160

Domestic VAT Taxes Abroad VAT Taxes

INTRA EU VAT INTRA EU VAT VAT DOMESTIC VAT INTRA EU VAT ABROAD EXEMPT EXEMPT EXEMPT NON TAXABLE VAT INTRA EU DOMESTIC ABROAD INTRA EU INTRA EU DOMESTIC

Intra-EU Offset Standard

Intra-EU Offset Services Domestic Article 160

OFFSET_ARTICLE 150 B&G Domestic Article 150 B&G OFFSET_ARTICLE 150 B&G Intra-EU Article 150 B&G OFFSET_ARTICLE 150 B&G Abroad Article 150 B&G N/A N/A N/A N/A N/A Intra-EU Exempt Taxes Domestic Exempt Taxes Abroad Exempt Taxes Intra-EU Non Taxable Taxes Intra-EU VAT Taxes

Summary Section of the Report Tax Code The report will group the Tax Base and Vat Value by Tax Codes here. Territory - The report will group the Tax Base and Vat value by Territory here. Number of Documents The report will group the Invoices by Territory, Tax Code and Description and will display the Document count here. Total (Tax Base+ VAT value) - This is the sum total of the Tax Base and VAT value Tax Base- The report will group the Tax Base by Territory, Tax Code and Description and will display the sum total of Tax Base in this column. Vat Value - The report will group the Vat Value by Territory, Tax Code and Description and will display the sum total of Vat Value in this column. Description The report will group the Tax Base and the Vat value by Description here.

Report Output The report output layout shall be as under-

Parameter Check & Error Handling (1) The parameter Period and Posted Parameter are mandatory parameters. . In case the user does not provide the value and submits the report, then error will be handled as explained below

Exception Condition

Status

Post Process

Error Message

Value for parameter Period not entered Value for parameter Posted not entered

Message should be displayed.

Message should be displayed.

User should choose the value from the LOV. Program cannot be submitted. User should choose the value from the LOV. Program cannot be submitted.

Please enter a value for the parameter or segment Period Name.

Please enter a value for the parameter or segment Posted Parameter

Assumptions This request is created for Oracle E-business Suite Version Release 12.0.0. The EB tax setup is completed in R12 & GL Tax Options have been set. It is assumed all the required setups are done. The INVOICE GDFF CLE: Include In VAT Register is implemented at AP Invoice Header. The Localization DFF CLE: RO VAT Information is implemented at GL Journal Line Level To Cancel an AP Invoice a credit memo should be raised and applied instead of using Invoice Cancel Function. Tax Status and Tax rate, Site address & DFF information are critical for the data to appear in the correct column of the report. In case of GL Tax journal if the user wants to enter data for multiple suppliers then one journal should be created for each supplier

Index

A
Add-on Localizations Overview, 1-1 Assignment of Concurrent Programs to Request Groups, 2-1

P
Patches to be applied, 2-1 Prerequisites, 2-1

S C
CLE: AP Purchasing Ledger Report, 5-21 CLE: AR Sales Ledger Report, 5-1 CLE: GL Trial Balance Report - Yearly, 4-24 CLE: Trial Balance Report, 4-18 Consumption Bill Report, 4-8 Statutory Accounting - Fiscal Book, 4-1

T
Transaction Tax, 5-1 Transfer Note for Goods Report, 4-5

F
Forms Personalization, 3-3

G
General Setup Steps, 3-1 Global Descriptive Flexfields setup, 3-1 Goods Received Note Report, 4-1

I
Inventory Accounting Card Report, 4-10 Invoice Aging Report, 4-13

L
Localizations Descriptive Flexfields Setup, 3-2

O
OAF Personalization, 3-3

Index-1