r12 implementation recommendations for germany (february 2010) e15627-01

8/19/2019 R12 Implementation Recommendations for Germany (February 2010) E15627-01

1/202

Oracle® E-Business Suite

Implementation Recommendations for Germany

Release 12

Part No. E15627-01

February 2010


2/202

Oracle E-Business Suite Implementation Recommendations for Germany, Release 12

Part No. E15627-01

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

Primary Author: Oracle Germany Consulting

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarksof their respective owners.

This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense 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. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou 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 behalfof 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. Governmentcustomers are "commercial computer software" or "commercial technical data" pursuant to the applicableFederal 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 theapplicable Government contract, and, to the extent applicable by the terms of the Government contract, theadditional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). OracleUSA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is notdeveloped or intended for use in any inherently dangerous applications, including applications which maycreate a risk of personal injury. If you use this software in dangerous applications, then you shall beresponsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use ofthis 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 servicesfrom third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim allwarranties of any kind with respect to third party content, products and services. Oracle Corporation and itsaffiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of thirdparty content, products or services.


3/202

iii

Contents

Send Us Your Comments

Preface

1 Introduction

Overview................................................................................................................................... 1-1

2 Setup Related Recommendations and Considerations

Introduction............................................................................................................................... 2-1

System Administration............................................................................................................. 2-1

General Ledger.......................................................................................................................... 2-2Ledger Architecture................................................................................................................... 2-3

MultiOrg Access Control.......................................................................................................... 2-5

Payables..................................................................................................................................... 2-9

Receivables.............................................................................................................................. 2-11

Banking Model........................................................................................................................ 2-16

Payments ................................................................................................................................. 2-28

Collections .............................................................................................................................. 2-35

Assets....................................................................................................................................... 2-36

EBusiness Tax ......................................................................................................................... 2-38

3 Process Related Recommendations and Considerations

Over All..................................................................................................................................... 3-1

General Ledger.......................................................................................................................... 3-1

Payables..................................................................................................................................... 3-4

Receivables................................................................................................................................ 3-5


4/202

iv

Cross Payables/Receivables...................................................................................................... 3-9

Payments..................................................................................................................................3-10

Assets....................................................................................................................................... 3-17

New Localizations R12............................................................................................................ 3-18

4 Audit Trail

Define Tables to be Audited.....................................................................................................4-1

Functional Setup......................................................................................................................4-11

Audit Trail Report .................................................................................................................. 4-12

5 Reconciliation Process

Cash Management..................................................................................................................... 5-1

Payables..................................................................................................................................... 5-4

Receivables.............................................................................................................................. 5-10

Assets....................................................................................................................................... 5-18General Ledger........................................................................................................................ 5-23

6 Reconciliation Reports

Cash Management..................................................................................................................... 6-1

Payables..................................................................................................................................... 6-5

Receivables.............................................................................................................................. 6-16

Assets....................................................................................................................................... 6-28

General Ledger........................................................................................................................ 6-57

VAT Reconciliation................................................................................................................. 6-71

Index


5/202

v

Send Us Your Comments

Oracle E-Business Suite Implementation Recommendations for Germany, Release 12

Part No. E15627-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 thedocument and if any concerns are already addressed. To do this, access the new Oracle E-Business SuiteRelease Online Documentation CD available on My Oracle Support and www.oracle.com. It contains themost 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 OracleSupport 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 atwww.oracle.com.


6/202


7/202

vii

Preface

Intended Audience

Welcome to Release 12 of the Oracle E-Business Suite Implementation Recommendations forGermany.

It is intended for a customer in Germany.

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

Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to callOracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle

technical issues and provide customer support according to the Oracle service requestprocess. Information about TRS is available athttp://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers isavailable at http://www.fcc.gov/cgb/dro/trsphonebk.html.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessibleto all users, including users that are disabled. To that end, our documentation includesfeatures that make information available to users of assistive technology. Thisdocumentation is available in HTML format, and contains markup to facilitate access by

the disabled community. Accessibility standards will continue to evolve over time, andOracle is actively engaged with other market-leading technology vendors to addresstechnical obstacles so that our documentation can be accessible to all of our customers.For more information, visit the Oracle Accessibility Program Web site athttp://www.oracle.com/accessibility/.


8/202

viii

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. Theconventions for writing code require that closing braces should appear on an otherwiseempty 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 organizationsthat Oracle does not own or control. Oracle neither evaluates nor makes anyrepresentations regarding the accessibility of these Web sites.

Structure1 Introduction

2 Setup Related Recommendations and Considerations

3 Process Related Recommendations and Considerations

4 Audit Trail

5 Reconciliation Process

6 Reconciliation Reports

Related Information Sources

This manual is to be referred in conjunction with Oracle Applications – R12 ReferenceManuals of the respective modules.

Integration Repository

The Oracle Integration Repository is a compilation of information about the serviceendpoints exposed by the Oracle E-Business Suite of applications. It provides acomplete catalog of Oracle E-Business Suite's business service interfaces. The tool letsusers easily discover and deploy the appropriate business service interface forintegration with any system, application, or business partner.

The Oracle Integration Repository is shipped as part of the E-Business Suite. As yourinstance is patched, the repository is automatically updated with content appropriatefor the precise revisions of interfaces in your environment.

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

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle DataBrowser, database triggers, or any other tool to modify Oracle E-Business Suite dataunless otherwise instructed.

Oracle provides powerful tools you can use to create, store, change, retrieve, and


9/202

ix

maintain information in an Oracle database. But if you use Oracle tools such asSQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity ofyour 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 anOracle 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, youmay 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 erroneousinformation and you risk unpredictable results throughout Oracle E-Business Suite.

When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suiteautomatically checks that your changes are valid. Oracle E-Business Suite also keepstrack of who changes information. If you enter information into database tables usingdatabase 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.


10/202


11/202

Introduction 1-1

1Introduction

Overview

When implementing Oracle E-Business Suite R12 in Germany there are several locallegal requirements and good business practices, which need to be taken intoconsideration when implementing the software.

This document reflects project results of current Oracle E-Business Suite R12implementations in Germany as well as findings during an Oracle internal project toachieve product certification for the financial modules of the suite.

The following four sections are covered by the document:

• Setup

• Process

• Audit Trail

• Reconciliation

Each of the four sections covers the most common Oracle E-Business Suite modules.The sections will give additional advice on the base and country-specific setup as wellas recommendations for daily business practice. Screen-shots are used to illustrate thetopics where appropriate.

The focus has been set on the following modules:

• General Ledger

• Payables

• Receivables

• Payments


12/202

1-2 Oracle E-Business Suite Implementation Recommendations for Germany

• Fixed Assets

• E-Business Tax

Oracle E-Business Suite Advanced Collections is also mentioned here, as much of theformer Receivables functionality has been moved to Advanced Collections.

This document only gives additional advice on some specific implementation topics forGermany. Therefore it is strongly recommended also to refer to the existing Oraclestandard documentation e.g. Oracle Implementation and User Guides for furtherreference.


13/202

Setup Related Recommendations and Considerations 2-1

2Setup Related Recommendations and

Considerations

IntroductionAn IT-Governance framework should be implemented to control the followingprocedures:

• Definition of Roles and Responsibilities

• Assignment of Setup functions to Roles/Responsibilities

• Initiate Setup documentation

• Update Setup documentation

From an auditing perspective it is crucial, that all setup documentation is created andmaintained properly.

For additional information on how to monitor change of master data, please have a lookat the chapter Audit Trail.

The following section addresses some additional system administration and setuprecommendations, which should be taken into consideration when implementingOracle E-Business Suite in Germany.

System Administration

Changing APPS Password

Oracle Applications offers a function to access the data on the table level from theapplication by using Diagnostic/Examine from the menu bar.

In order to prevent users from changing table entries using this feature the password of


14/202


the "Apps" user should be changed from the standard value to a specific password.

This account should be used by the technical support group and/or databaseadministration only.

It is also recommended to set the profile option: "Utilities: Diagnostics" to No; this willrequire the user to enter a password.

Responsibilities

The Oracle E-Business suite offers the possibility to have individual user managementand individual responsibilities to restrict the access to the data a user can see, and to thefunctions a specific user has available. These responsibilities can be either attacheddirectly to a user, or to a role, which is than assigned to a user. When setting up usermanagement, the implementation team can choose to use either a seeded responsibilityor to create new responsibilities, which can be created to the individual needs. Withroles and responsibilities it is also possible to achieve a segregation of duties.

User Password Changes

The usage of passwords for all users should be set to "expires periodically" after a giventime period or after a defined number of accesses to the system.

Document Sequencing

Document sequencing must be setup. Create the document sequences for all OracleApplications modules that are implemented, and assign them to the appropriatedocument categories.

It is recommended to setup the document sequences as gapless.

Furthermore, it is recommended to renew the sequence definition and sequenceassignments on a fiscal year basis.

Set the profile option Sequential Numbering to "Always used" in order to be sure, thatno accounting entries are created without a document sequence number.

General Ledger

Accounting Sequencing

To ensure that gapless sequential numbering is assigned to journal entries the

accounting sequencing should be setup.Accounting sequencing is set up with the option "GL Period Close – GL Journal Entry".With accounting sequences, gapless numbering, and continued numbering can beachieved.

The initiation for the accounting sequence is done during the accounting event.


15/202


Accounting Sequence elements:

• Sequence definition

• Sequence assignments

should be renewed on a fiscal year basis.

Ledger Architecture

Ledgers

With Oracle E-Business Suite R12, a new ledger architecture has been introduced:

Ledgers can be defined as:

• Primary ledger

• Secondary ledger

• Reporting Ledger

In addition to a secondary ledger, a primary ledger can also have a reporting ledgerassigned.

The primary / secondary ledger architecture is often being used to accommodatedifferent Accounting Standards in parallel. (e.g. HGB and IFRS).

Reporting ledgers are used to reflect accounting in a different (reporting) currency.

Primary ledgers can be linked to one or more legal entities. For a Germanimplementation it is mandatory to have a 1:1 relationship between the defined legalentity and the corresponding primary ledger.

Ledger SetsIn R12, Ledger Sets is a new functionality to create a list of ledgers, which are using thesame:

• Accounting Flexfield

• Calendar


16/202


Ledger Sets can be used for different functions such as:• Journal entry

• Recurring journals

• Allocations

• Period close

• Reports

In addition a Data Access Set, with enhanced security options needs to be defined inorder to use Ledger Sets.


17/202


Ledger Sets are assigned to a user responsibility by the profile option: GL: Data AccessSet.

MultiOrg Access Control

Setup Overview

Oracle E-Business Suite R12 introduces the MultiOrg Access Control (MOAC) feature,which enables a user to enter transaction and master data for different operating units

without changing their responsibility.

Setting up or using MOAC is optional; the former MultiOrg access via separateresponsibilities is still in place and can continue to be used.

If centralized functions are required, for example a shared service center for Payables,the use of MOAC will provide the required functionality to do so.

Security Profile

A security profile is a list of operating units, which can be assigned on user orresponsibility level by using the appropriate profile option.


18/202


After defining your Security Profile (in HR),run the concurrent request:

• Security List Maintenance

to derive a complete list of your organizations when using MOAC.

Profile Options

The MOAC Architecture uses the following profile options, which can be set ondifferent levels (including user) :

• MO: Security Profile

Here the security profile is assigned

• MO: Default Operating

Unit If a security profile has been assigned containing more than one organization,the defaulting organization will be derived based on this profile option.

Accounting Setup Manager: Subledger Accounting OptionsRegarding the transfer of transactions from the Subledgers to the General Ledger, thereare three summarization options:

• No summarization

• Summarized by GL-Date Period


19/202


• Summarized by GL Period

In order to have a complete drill down from the General Ledger to the Subledger selectthe "No summarization" option.

It is also recommended to set the parameter "Post in GL" to "Yes" to get the process of

accounting completed at once.

This task has to be performed for every module within Financials, which is part of theimplementation.

Furthermore this setup is required to get complete General Ledger Journals. This alsofacilitates compliance with the regulation GDPdU

Accounting Setup Manager: Suspense AccountingIt is recommended not to setup Suspense Accounting. This will prevent users fromposting unbalanced journals.

Third Party Control Accounts

Restrict the access to certain Accounts for manual journal entries from the GeneralLedger responsibility in order to ensure that only a subledger application can enter

journals to these accounts and to simplify reconciliation. Third Party Control accountscould be:

• Liability account, used in AP for transactions

• Receivables Account, used in AR for transactions

• Asset Clearing Account


20/202


Web ADI Journal Entries

It is recommended to use the option "Automatically Submit Journal Import" due to thefact that the user who entered the transaction isn't necessarily the same person who

posted the journal entry into GL.Oracle considers Web ADI to be a Subledger. Consequently "Third Party ControlAccounts" can be used for transaction generation as well. If posting to Third PartyControl Accounts by Web ADI is not wanted this has to be secured by organizationalmeans.


21/202


Payables

Setup Payables Options (in extracts)

Payables System SetupIt is suggested to setup the following values using

(Resp) Payables (M) Setup/Options/ Payables System Setup

Description Value

Supplier Number Automatic

Type Numeric Terms

Date Basis Invoice

Payables Options - Discount

To setup this option Navigate to Payables Options, Tab: Accounting Options


22/202


Description Value

Discount Method System Account

Prorate Expense

Prorate Tax

There are three different discount methods available:

1. Prorate Tax

This option is used for creating a tax correction based on the discount taken, and tocredit the remaining discount amount to the "discount taken" account. In that case thereis no automatic transfer of reduced costs to Fixed Assets paid invoices available.

2. Prorate Expense

This option credits prorata all expense accounts and also makes corrections to the VAT.This option brings the reduced costs for Fixed Assets paid invoices to the MassAdditions for Fixed Assets if the accounting for the invoice lines is made to the FixedAssets interims account. There will be no specific accounting for discount taken.

3. System Account

This option credits all discounts to the system "discount taken" account. No automatedtax correction will be provided, when discount has been taken.

In a German implementation it is recommended to use one of the "Prorate"-options tocreate discount driven tax reduction. But the "Always Take Discount" option in thesupplier setup (Invoice Management) should not be enabled.

Payables Options – Currency

It is suggested to setup following values using

Payables Options, Tab: Currency

Description Value

Use Multiple Currencies Yes

Define the Accounts for

Realized Gains Account for Realized Gains

Realized Loss Account for Realized Loss


23/202


Rounding Account for Rounding

Payables Options – Invoices

It is suggested to setup the following values usingPayables Options, Tab: Invoices

Description Value

GL-Date Basis Invoice Date

Payables Options – Interest

It is suggested to setup following values using

Payables Options, Tab: Interests

Description Value

Allow Interest Invoices No

Payables Options – Payment

The Exclude Tax From Discount Calculation option specifies whether Payablessubtracts the tax amount from the invoice amount when it calculates the invoice

amount applicable to discount.

It is suggested not to enable this option.

Payables Options, Tab: Payments

Description Value

Exclude Tax from Discount Calculation No

Receivables

System Profile Options

To setup these options, navigate to System Profile Options within the SystemAdministrator Responsibility


24/202


These system profile options should be set up as follows:

Profile Option Value

AR: Application GL Default Later of Current date, Receipt and Invoice GL

date

Choose this value to use either the receipt GLdate or the invoice GL date, whichever is later,as the default GL date for your receiptapplications. This is the default value.

AR: Cash - Allow Actions Yes

AR: Change Customer on Transaction No

AR: Enable Journal Balance Check Yes

AR: GL Transfer Balance Test Yes

AR: Mask Bank Account Numbers Mask - First Four Digits Visible

AR: Override Adjustment Activity AccountOption

Yes

AR: Update Due Date Yes

AR: Use Invoice Accounting For Credit

Memos

Yes

HZ: Change Party Name No

System Options

To setup System Options navigate to System Options within the Receivables ManagerResponsibility

(Resp) Receivables (M) Setup/Options/ Reeivables System Options System Options, Tab:Accounting:

These receivables system options should be set up as follows:

Form Field Value


25/202


Automatic Journal Import Yes

Define Accounts for:

Realized Gains

Realized Losses

Tax

Cross Currency Rounding

Exchange rate gains account

Exchange rate losses account

Default tax account

Rounding errors during application of crosscurrency receipts account

Optionally define Accounts for:

Header Rounding

Unallocated Revenue

Important: Once header level rounding isactive, the setting cannot be turned off!

System Options, Tab: Transactions and Customers:

Form Field Value

Allow change to printed transactions No

Allow transaction deletion No

Allow payment of unrelated transactions Yes

Document number generation level When Completed

To be in accordance with German GDPdU regulations, the system option "Allowchanges to printed transactions" should be set to "No". If necessary, changes shouldalways be done by using credit memos, adjustments etc. rather than changing a printedtransaction.

Also, the system option "Allow transaction deletion" should be set to "No". This isnecessary to prevent gaps in the document sequence for Receivables transactions.Credit memos or adjustments are the tools to use to close (reverse) an unwantedtransaction. System Options, Tab: Miscellaneous:

System Options, Tab: Miscellaneous:

Form Field Value


26/202


Discount basis Application Rule Set Invoice amount

Require billing location for receipts Yes

Discount on partial payment Yes

Chargeback due date Open invoice due date

Source of territory None

Application Rule Set Prorate all

Setup VAT for adjustments when applying adjustments and discounts

Receivables Activities are required to make sure that correct VAT accounting entriesdue to adjustments and discounts are created automatically:

Receivable activities for adjustments (option 1)

Type Adjustment

GL Account Source Tax Code on Invoice

Tax Rate Source Code Invoice

Allocate the net portion using the Expense/Revenue accounts specified by the tax ratecode on the invoice. Distribute the tax amount to the tax accounts specified by the taxrate code on the invoice.

Receivable activities for adjustments (option 2)

Type Adjustment

GL Account Source Activity GL Account


Allocate the expense or revenue to the General Ledger account that is specified for thisReceivables Activity. Distribute the tax amount to the tax accounts specified by the taxrate code on the invoice.

Receivable Activities for Adjustments (option 3)


27/202


Type Adjustment

GL Account Source Revenue on Invoice


Allocate the expense or revenue net of any tax to the revenue account(s) specified on theinvoice. Distribute the tax amount to the tax accounts specified by the tax rate code onthe invoice.

Receivable Activities for Discount Type

Type Adjustment

GL Account Source Tax Code on Invoice


These Receivables Activities for earned and unearned discounts have to be referencedwhen defining receipt method accounts and will be used for account derivation whendiscounts are calculated during the receipt application process.

Therefore, the corresponding accounts have to be defined when the respective tax ratesare defined:


28/202


Customer setup considerations

The Value Added Tax identification number (Umsatzsteuer-Identifikations-Nummer:UID) in the Tax Profile on customer account level under "Tax Registrations" must bedefined. Select the tax regime code of the customer's home country and enter the UID.Set the Effective Date From and save.

Additionally set "Associated Fiscal classifications" under the Fiscal Classification Codeto "Registered" if the customer has a UID assigned.

Banking Model

Banking Setup - Overview

Since the release of Ebusiness Suite R12, banking setup is part of the TradingCommunity Architecture (TCA). Bank accounts can be defined as external and internal.

External bank accounts are part of the setup process within suppliers / customers in thecorresponding Payables / Receivables Financials application modules. Internal andexternal bank accounts setup prerequisites are:

• Banks

• Bank branches

Banks and bank branches are shared between legal entities, suppliers and customers.

Internal bank accounts need additional setup as:

• Detailed bank information


29/202


• Owner information and modules

• Detailed bank accounting information

• Payable documents setup.

The Cash Management module owns the internal bank accounts.

In order to perform payments, the following steps need to be performed:

• Setup an external bank account

• Assign an external bank account to a supplier

• Setup an internal bank account.

Define a bank

In order to define a bank, use the Cash Management responsibility and navigate to:(Resp) Cash Management (M) Setup/Banks

The "Manage Banks and Branches" page will be found here. When clicking the Bankstab, all necessary fields will be displayed to start with the bank definition:

Click on the "Create" button. On the next page additional bank information can beentered:


30/202


Country and bank name are mandatory fields.

After saving the information the bank address page will be shown. Bank address fieldsare not mandatory. Click "Finish" to complete bank definition.

Define a bank branch

In order to define a bank branch use the Cash Management responsibility and navigateto:

(Resp) Cash Management (M) Setup/Banks

The "Manage Banks and Branches" page will be found here.

Navigate to the "Bank" tab and enter the previously defined bank (by name).

The page will show the Create Branch button.

Search for the bank defined in the previous section:

Click the "Create Branch" button to start the bank branch definition.

The following popup is displayed:


31/202


By pressing the "Continue" button the bank branch details form will be opened:

Enter the mandatory fields:

• Branch Name

Mandatory field. Branch names are only unique within the bank / bank branchcombination.

• Branch Number

In some countries this field is mandatory and a validation is done on the number beingentered (France, Switzerland). For German payment format this field must be entered

with the bank code (BLZ).• BIC Code

For using SEPA Payments the BIC Code is mandatory

• Branch Type


32/202


For using SEPA Payments the value SWIFT is required. For German standard paymentformat the value OTHER is correct.

After saving the information the bank branch address page will be shown. Bank branchaddress fields are not mandatory. Click finish to complete bank branch definition.

Create an internal bank account

Within Cash Management responsibility under navigate to:

(Resp) Cash Management (M) Setup/Banks

The "Manage Banks and Branches" page is displayed.

Clicking the "Bank Branch" tab and entering the previously defined bank branch (byname) will show the create account button.

The following form is shown:

Click the "Create" button, and the following information will be derived:

Click on "Continue", and the legal entity selector page opens up.


33/202


When the "Bank Account Owner" field is opened, the system will allow selection of alegal entity:

Select the relevant legal entity, which owns the bank account.

Note: If the legal entity cannot be derived, the cash managementsecurity wizard should be used in user management to create thecorrect grants for this setup activity.

Determine the purpose of the bank account. Typically in a Financials implementation,Payables and receivables are using the internal bank account.

Click on "Next".


34/202


Important: Note that the country of the bank determines the validationof the bank account number for many countries.

It is recommended to enable "Multiple Currencies Allowed", evenwhen it is currently intended to use only one currency. This will allowfor payments in foreign currency.

Account name: this name must be unique within the bank branch only.It can be up to 100 characters long.

If automatic bank statement sequencing in Cash Management is used, itis recommended to restrict the bank account name definition to amaximum 30 characters in length. It is also suggested that bank accountnames are uniquely defined within a ledger to derive correct bankaccount sequences. Be aware that bank account names are

case-sensitive.


35/202


• Check digits

For German payment formats this field can be left empty. For some other countries (e.g.France), this check digit field is mandatory, as it is a component of the total accountnumber (French RIB).

• IBAN code

For SEPA payments, the IBAN (International Bank Account Number) code is necessary.There is also a validation on this field. If it is planned to use SEPA in the future, it isrecommended to setup the IBAN number from the start.

Click "Save and Next".

General Controls/Cash Clearing

Cash clearing can be used to show payment transactions in transit on a differentaccount. If it is required to track clearing by Payment Document it is recommended touse Advanced Derivation Rules (Subledger Accounting).

There are many other options for the bank account, which affect the payment process;refer to the Cash Management manual for their explanations.

Click on "Save and Next" to continue.

Click on "Add Organization Access" and the following page is displayed:


36/202


Select the operating unit and "Continue".

The last step can be repeated to allow the usage of the bank account within severaloperating units within the same ledger.

After pressing "Finish", the bank account definition has been completed.

Manage Payment Documents

Within Cash Management responsibility under navigate: Setup>Bank Accounts

The "Manage Bank Accounts" page can be found. Executing a simple search to derivethe previously defined bank account will offer the "Manage Payment Documents"Button, which can be clicked after checking the relevant Bank account:

The Manage Payments Documents page opens:


37/202


Click on "Create".

Enter a name for the payment document:

Create a supplier bank account

Supplier bank accounts are defined during the setup of a supplier.

Within Payables responsibility navigate to: Suppliers / Entry and perform a search foran existing supplier.


38/202


Navigate to "Banking Details" from the menu at the left side of the screen.

Change the account assignment level to "Site", and click "Go"

Click on "Create".

Enter bank, bank branch and bank account details as follows:


39/202


Click "Apply".

After searching the supplier again the following details can be found within the bankaccount details form:

Create a Customer Bank Account

Creating a customer bank account can be done on account level as well as on site-levelwithin the functions offered on the "Payment Details"-Tab.

The form offers to define a complete new external bank account including a definitionof bank and bank branches.

If bank or bank and branch are already defined they can be selected, and a new bankaccount will be added to the customer.


40/202


To create the correct format, the direct debit bank instruction has to be set to the

appropriate value, which has been contractually agreed with the customer.

Payments

Payments Setup - Overview

Oracle E-Business Suite introduces with R12 a new Module: "Payments", whichinteracts with:

• Oracle Receivables

• Oracle Payables

• Oracle Cash Management

• Oracle Loans

Setup to be done can be divided in three areas:

• Shared Setup

• Funds Disbursement Setup


41/202


• Funds Capturing Setup

The majority of the objects are delivered as seeded values with the product. Thefollowing payments setup is focusing on the key elements and how to set them up.

Shared Payments Setup

Generic setup has to be done which is being used in both flows:

The necessary steps to perform payment functions are:

• Transmission Configuration

• Payment Systems

Transmission Configuration

There are several transmission mechanisms, which can be used:


42/202


Within the Transmission configuration the following setup is performed:

Payment Systems

German payment formats can be found in the "German Payment System" as well as inthe "Global Payment System".

To use a payment system, a payment system account needs to be set up.

The main payment formats can be found as seeded data:


43/202


Funds Disbursement Setup

Funds disbursement setup is used with the focus on outbound payments.

Funds disbursement setups:

Payment Methods

Payment methods such as "Electronic" and "Wire" can be found as pre-seeded data. Ifrequired new payment methods can be created and duplicated:

Payment Process

Profiles Payment process profiles are also seeded but can be customized or duplicatedfor specific usage:


44/202


Disbursement System Options

After defining the setups for funds disbursement, payments manager within thepayables function can be used to define detailed setups based on individualrequirements:


45/202


46/202


Profiles For a German implementation direct debit payment methods with the type"Lastschriftverfahren" and "Einzugsermächtigung" are key requirements.

A direct debit funds capturing profile can be found as seeded data for duplication:

Seeded Profiles cannot be used but they can be duplicated and tailored. The importantfield to be assigned in the duplicated versions is the transmission configuration.

Payee

The definition of a payee completes the funds capturing setup. Payees have to becreated including:

• Payment System and Payment System Account

• At least one Operating Unit Assignment

• Using multiple Operating Units would assume that they are all part of the sameledger

• Funds Capturing Process Profile


47/202


Collections

With Oracle e-Business Suite R12, much of the AR Collections functionality is replaced by Advanced Collections functionality. Advanced Collections supports a number ofinnovative processes and concepts that are different from traditional collectionspractices. It's important to understand these concepts and to know how AdvancedCollections uses them. For additional information refer to the Oracle AdvancedCollections Implementation Guide and Oracle Advanced Collections User Guideavailable on OracleMetaLink.

Transactions

In Receivables, an invoice, debit memo, credit memo, chargeback, or bill receivable.Receivables maintains transaction tables which Advanced Collections accesses. Invoicescan include one or more payment schedules.

Delinquency

In Advanced Collections, this is a transaction that is overdue. The criteria used todetermine which transactions are delinquent are configurable. The seeded delinquencyconfiguration uses a payment schedule for which the dispute amount is less than thetotal amount overdue and the due date is prior to the current date to determinedelinquency. Delinquencies are identified from invoices, charge backs and debitmemos. Advanced Collections identifies delinquencies by running a 'delinquency statusdetermination' concurrent program and maintains this information in delinquencytables.

Collector's Work Queue

The Universal Work Queue provides a high-level list of all actionable work assigned to,or owned by, a collections agent. This work is automatically 'pushed' to the agent aspart of the automated collections management flow provided by Oracle AdvancedCollections.

Scoring Engines and Scoring Components


48/202


Scoring engines consist of one or more scoring components and they can be configuredto provide a score at the customer, account, and bill to level. Advanced Collections usesconfigurable scoring engines for two purposes: to determine whether a transaction isdelinquent and to determine the business value - or collections score - of customers.Collections scores are similar to a customer's credit score but they generally guide how

seriously the customer is treated during collection activities.Dunning Plan

The traditional method used to notify a delinquent customer about an unpaid balance.Advanced Collections provides the ability to send dunning letters via fax, e-mail orprinted letter. Additionally, Collections can use the customer's collections score and theoldest aged invoice to determine the content and delivery method of the dunningnotice. If payment is not made within a specified period of time, Advanced Collectionscan automatically assign a 'dunning callback' to a collector who will then see that actionon their Task node in the Collector Work Queue.

Collections Strategy

Compared to Dunning Plans, this collections method supports more complex means tocontact and manage customers about their receivables situation. Collections strategiesconsist of one or more work items, which are actions performed by either the system(send a reminder letter) or the collector (call this customer). Work items are timed to beexecuted serially. Strategies are based on collections scores so different strategies can beused for customers with 'good' or 'bad' value scores. Collections strategies can also beused to alert pre-delinquent customers about a pending payment. Unless a deployingorganization has no need to do anything more complex than simple dunning, the bestpractice recommendation is to use collections strategies. This allows for flexibility as theorganization changes in the future.

Assets

Setting up Asset Books

Allow Amortized Adjustments

Activate this option using the (Resp) FA Super User (M) Setup/ Asset System/ BookControls (Tab) Accounting Rules in order to ease the reconciliation of the depreciationamount (recalculating the depreciation).


49/202


Retirement Accounts

While setting up the accounts for the Retirement transaction in the Asset Book Form, itshould be considered to use different accounts per transaction. There is no need tosetup different accounts for "Gain" and "Loss". For the Retirement it is recommended touse a different Clearing Account than the Clearing Account used for Mass Additions.This helps with the reconciliation of the transactions in the GL.

Additional Asset Books

Often an additional Asset Book is being used to reflect country-specific legal

requirements. It is mandatory to link these additional Books to the appropriate Ledgers.For example, if the Primary Ledger is based on IFRS Accounting Standards, the linkedAsset Book has to reflect IFRS as well.

Optional: Security by book

If there should be a strict separation between the different books for the valuation ofassets, setup this feature to separate the data per Responsibility and per Asset book or


50/202


optionally for a number of Asset Books.

Setup at least one responsibility for each book in order to access assets stored in this book.

EBusiness Tax

Introduction / Remarks

It is common business practice in Germany to enter and post manual journals with taxesdirectly in the General Ledger instead of using the subledger modules.

The following setup will not share the tax statuses across Payables and Receivables. TaxStatus has been setup separately for Payables and Receivables. This has been achieved

by setting up specific Tax Rules.

E-Business Tax – Setup Regime to Rate flow - Overview

The applications module E-Business Tax is a rule-based engine, which empowers theuser to automatically derive the tax rates based on the transactions and parameters thathave been entered. For a complete setup of the E-Business Tax module please follow theRegime to Rate flow as shown in the following screen-shot with the 4 levels Regime,Tax, Status and Rate. In each step there are specific setups necessary.

For Germany taxes should be separated into input and output types:

Tax regimes

Set up tax regimes for the taxes in each country and geographic region where you do business and where a separate tax applies. A tax regime associates a common set ofdefault information, regulations, fiscal classifications and registrations to one or moretaxes with the same tax requirement.

The tax regime provides these functions:

• Groups similar taxes together.


51/202


• Designates the geography within which taxes apply.

• Defaults the settings and values you define to each tax in the regime.

• Contributes to the definition of configuration options and third party servicesubscriptions.

• Optionally provides a single registration for all taxes associated with the regime.

• Defines the use of fiscal classifications.

The common tax regime setup is one tax regime per country per tax type, with the taxrequirements administered by a government tax authority for the entire country.

The main region requires the following information:

Additional the Controls and Defaults are to be defined.

Taxes

Each separate tax in a tax regime includes records for the statuses, rates, and rules that

are used to calculate and report on the tax. E-Business Tax defaults tax informationfrom the tax regime to each tax that you create under a regime.

You can only enable a tax for use on transactions after you have completed all of therelated setup required. This is achieved by enabling the option: "Make Tax Available forTransactions" in the last step of your setup.


52/202


Additionally the Controls and Defaults are to be defined.

Status

A tax status is the taxable nature of a product in the context of a transaction and aspecific tax on the transaction. Every tax status in Oracle E-Business Tax is definedunder a tax and contains one or more tax rates.

For example, one tax can have separate tax statuses for standard, zero, exemption, andreduced rates. A zero rate tax status may have multiple zero rates associated with it inorder to handle different reporting requirements for zero rate usage, such as Intra EU,zero-rated products, or zero-rated exports.

You define a tax status under a tax and a configuration owner, and define all applicabletax rates and their effective periods under the tax status. The tax status controls thedefaulting of values to its tax rates.


53/202


In principal a tax status can be used for Payables and Receivables transactions.

Jurisdictions

A tax jurisdiction is a geographic region or tax zone where a specific tax authority levies

a tax. A tax jurisdiction specifies the association between a tax and a geographiclocation.

At transaction time E-Business Tax derives the jurisdiction or jurisdictions that apply toa transaction line based on the place of supply. The place of supply is the location where atransaction is determined to take place for a specific tax. E-Business Tax either uses adefault place of supply or derives a place of supply based on tax rules.

You must set up at least one tax jurisdiction for a tax before you can make the taxavailable on transactions.

Jurisdiction Setup for Germany:

Tax Rates

Set up tax rates for the tax statuses and tax jurisdictions. For tax statuses, set up a taxrate record for each applicable tax rate that a tax status identifies. For tax jurisdictions,


54/202


set up tax rate records to identify the tax rate variations for a specific tax withindifferent tax jurisdictions. For example, a city sales tax for a state or province maycontain separate city tax jurisdictions, each with a specific rate for the same tax.

You can also define tax recovery rates to claim full or partial recovery of taxes paid.

You define tax rate codes and rate detail information per rate period. Rate periodsaccount for changes in tax rates over time. A tax rate code can also identify acorresponding General Ledger taxable journal entry.

Rate Details

Tax Accounts


55/202


Rules

The E-Business Tax determination process uses your tax configuration setup and thedetails on the transaction to determine:

• Which taxes apply to the transaction.

• How to calculate the tax amount for each tax that applies to the transaction.

With E-Business Tax rules there will be a tax determination model created to reflect thetax regulations of different tax regimes and the tax requirements of your business. Tocreate a simple tax model that makes use of default values without extensiveprocessing, or a complex tax model that considers each tax requirement related to a

transaction before making the final calculation.

During execution of the tax determination process, E-Business Tax evaluates, in order ofpriority, the tax rules that have defined against the tax configuration setup and thedetails on the transaction. If the first rule is successfully evaluated, the result associatedwith the rule is used. If not, the next rule is evaluated until either a successfulevaluation or default value is found.

The E-Business Tax determination process is organized into rule types. Each rule typeidentifies a particular step in the determination and calculation of taxes on transactions.

The tax line determination process uses the information of the transaction header andtransaction line to determine the tax lines.

The rule types and related processes used for tax line determination and tax calculationare:

1. Determine Place of Supply - Determines the location where a transaction isconsidered to have taken place for a specific tax.


56/202


2. Determine Tax Applicability - Determines the taxes that apply to a giventransaction.

3. Determine Tax Registration - Determines the party whose tax registration status isconsidered for an applicable tax on the transaction.

4. Determine Tax Status - Determines the tax status of each applicable tax on thetransaction.

5. Determine Tax Rate - Determines the tax rate for each applicable tax on thetransaction.

6. Determine Taxable Basis - Determines the amount upon which to apply the taxrate.

7. Calculate Tax Amounts - Calculates the tax amount for each applicable tax on thetransaction.

Example for Determine Tax Status:

Specific Rule Setup for Payable / Receivable Tax Separation

Party Tax Profile

Fiscal Classification Type has to include Sales Transaction and Purchase Transaction


57/202


Determine Tax Status in Tax Rules setup to restrict a tax status to be used only inpayables:

Bill To Party has to be set to Purchase Transactions.

Determine Tax Status in Tax Rules setup to restrict a tax status to be used only inReceivables:

Bill From Party has to be set to Sales Transaction.


58/202


59/202

Process Related Recommendations and Considerations 3-1

3Process Related Recommendations and

Considerations

Over AllThe following section will give some further recommendations on the several businessprocesses.

Patch Level

It is recommended to use latest available patch levels.

Subledger Accounting Method

There are several predefined Subledger Accounting Methods available. If the Subledger

Accounting Method being used is not a seeded one, it is recommended to document indetail all objects of the user-defined method.

General Ledger

Manual Journal entries with VAT

Postings on Tax accounts are only shown in the localized VAT reports, if they aregenerated by the standard feature for tax within the journal entry form.


60/202


Postings directly to the VAT-Account will not be shown in tax reporting because the taxcode is not referenced. .

Closing Periods within General Ledger

It is possible to close periods in General Ledger while there are still unposted journals.

An organizational process should be put in place, which ensures that all journals areposted before closing the period. It is not recommended to close a period permanentlyuntil after the auditors have completed the year-end certification.


61/202


Freeze Journals

Journal sources can be frozen and unfrozen. It is recommended not to unfreeze a journal source. Unfrozen journals can be modified or deleted. This could cause majorreconciliation issues.


62/202


Payables

Invoice GL-Date Mechanism

Entering the invoice header includes the field GL-Date and represents the liabilityaccounting. If this GL-Date is changed a warning-message is shown.

The GL-Date on invoice line level represents the expense accounting and is defaultedfrom the invoice header level. It is recommended to ensure that GL-Dates on line levelare accurate, because they impact the accounting.

Discount Invoices/Credit Memo fully applied

When invoices are reduced in full by applying a credit memo, it has to be ensured thatpayment terms and corresponding discounts are synchronized.

If payment terms are not in line with both documents, the remaining discount can be setto zero during the payment run.

Discount Partial Payments

When partially paying an invoice the system suggests the full discount amount to betaken based on the invoice information. A manual correction to the discount is needed,

to ensure correct documentation and accounting for this transaction.

Payable Options, Single Payment, Allow Pre-Date

Oracle standard functionality does not allow creation of a payment with a date that isearlier than the system date, unless the setup is extended to allow pre-date option in thepayable options form.


63/202


If the feature "allow pre-date" is going to be used, additional organizational measuresshould be defined to ensure the correctness of the payment date.

It is recommended that periods are closed at the month end to ensure the completenessof transactions

Supplier duplications

To prevent supplier duplications it is recommended to use naming conventions as wellas internal controls.

Internal control procedures should evaluate, if the supplier to be added exists already inthe system.

Supplier Bank Account Data

To ensure that suppliers bank account assignments are properly documented, it isrecommended to enable auditing. A report has to be created to show the content for thisaudit.

Receivables

Customer Duplications

To prevent customer duplications it is recommended to use naming conventions as wellas internal controls.

Internal control procedures should evaluate, if the customer to be added, exists alreadyin the system

Customer Bank Account Data

To ensure that customer bank account assignments are properly documented, it isrecommended to enable auditing. A report has to be created to show the content for thisaudit.

Customer Account Merge

With this function, the user can merge two customers into one remaining customer. Alltransactions owned by the original customer will be moved to the "new" customer.

Optionally, the original customer can be deleted after the merge has been run. It is not

recommended to set this option. If the user wants to use this option, it is suggested tohave audit trail function in place including customer master data.


64/202


Prepayments (ISTversteuerung von Anzahlungen)

In order to create the correct accounting in AR the following steps are recommended:

• Setup: Additional Transaction Type "Prepayment", with interims accounts forprepayments:


65/202


• Process (Step1): Enter the cash receipt

• Process (Step2): Enter the "prepayment invoice".

• Process (Step3): The final invoice will be entered as standard invoice, but with themanual entry of the "prepayment invoice"(+ tax) as a negative amount.

• Accounting of the final invoice must net off the interim accounting of the"prepayment invoice".

FreightFreight generation should be done based on Item, to calculate tax on top of the freightamount.

The standard freight calculation delivered in the AR Workbench by pressing the freight button should not be used, because it does not create tax on the freight.


66/202


Optionally, the freight button can be disabled by unchecking the allow freight option inthe transaction types definition.

Invoice Printing

It is recommended to use the standard invoice printing process.

If using the online button in the invoice workbench it must be ensured byorganizational measures that the data will not be changed anymore.


67/202


Alternatively the print button can be excluded from the responsibility:

Receipt Overapplication

If the overapplication feature is used, organizational measures should be in place toensure the correct application of the receipts.

Cross Payables/Receivables

AP/AR-Netting

Based on netting agreements, netting batches can be generated for netting of liabilitiesand receivables within the trading partners defined in the netting agreement.

Netting agreements can be defined even if the trading partners are not the same legalentity. Therefore it has to be ensured that netting agreements includes only thosetrading partners, which are in line with legislation to net off transactions.

Local legal requirements determine which single transactions can be netted. So, it is

suggested to setup netting batch creation with a manual review step, before finallyapproving and generating the netting transactions.

Refunds

Since the introduction of Oracle Payments in R12 the refund feature can be used to paycredit memos to a customer. This function will create a refund invoice in Payables,


68/202


69/202


Templates

Templates can be setup to be used during the payment process request during thepayment run. Within the template definition a lot of information can be defaulted or left

blank to be entered during the payment process request. Key elements to design atemplate are the following:

• Payment selection criteria

: Pay Groups, Legal Entities, Organizations, Payment Method, etc.

• Payment attributes:

Bank Account, Payment Document, Payment Process Profile, and Exchange Rateetc.

• Process Automation Options

• Validation Failure Results

• Additional Information

It is recommended to design a template with process automation options, whichenables the user to intervene in the payment process.

Within the template tab the payment request can be started as a single payment requestor a repeating request can be scheduled.


70/202


Payment Process Requests

By creating the single payment request the payment process is going to be started.

Preceded values based on the template definition are offered and can be changed.Mandatory fields have to be completed at this stage.

Based on the process automation options the payment process request can be reviewed,edited and finally submitted:


71/202


The "Payment Dashboard" indicates the actual status of the payment process request:

Scrolling down in the completed payment process request will enable all information:

Click on "Payment Process Request" .


72/202


Within the concurrent requests form, the formatting request has been created.

The following output files are created:

Selected Payments Schedules Report


73/202


Format Payment Instructions

The output is the bank file:

Payment File Accompanying Letter


74/202


Fund Capturing

Creating a direct debit run (Lastschriftlauf/Einzugsermächtigung) would consist fromthe following steps:

• Create automatic receipt batch (Receivables Manager)

• Create remittance batch (Receivables Manager)

• Create settlement batch (Funds Capturing Process Manager)

In the last step the following outputs will be delivered:

• File for funds capturing (Local File System)

• Receipt of Payment Notification (Optional)

• Accompanying Letter to authorize the bank

Before running the new step "Create Settlement", it is recommended to check whetherauthorized transactions are available in payments. These can be found in the"Authorizations" tab on the funds capturing process manager home page:


75/202


Transactions which are found here, are transmitted by the remittance batch procedure:

The create settlement process can be started from the standard view -> request form ordirectly on the Funds Capturing Process Manager Homepage.

Assets

Asset Numbering

If the option to use "automatic numbering" is activated in FA, all assets will have agapless number. But, it is possible to enter an alphanumeric number, which will lead toa "non-gapless" sequence.

Users should take measures to endure that this is not happening

Depreciation calculation according to § 7 II Einkommenssteuergesetz (EStG)

In the standard environment, there is no depreciation method defined which followsthe regulations of § 7 II EStG.

Formulas or table-based depreciation methods can be used to achieve the regulations ofthis requirement.

Unplanned Depreciation and Cost Adjustments

In order to enter unplanned depreciation and cost adjustments, and to calculate thecorrect depreciation, activate the feature "Amortize Adjustments".

Then the Assets Net Book value will be recalculated based on the assets remaining life

and the depreciation method.

Adding Costs to an existing Asset

It is possible to show added costs to an existing asset (AHK Erhöhung), in theAddition-Column of the Asset Summary Report if the best practice will used to add anadditional asset. To have a link between both assets the sequence might be changed(e.g. Asset number 100a for this additional asset). It is important to also check the


76/202


remaining life of this asset.

Changing seeded asset details

It is recommended to add Assets only by using the Mass Addition interface withinvoices coming from Accounts Payable.

If assets are added manually, change important asset details such as Useful Life orDepreciation method. This information is defaulted by the selected Asset Category.

The user should also make sure, that this information is not changed during the processof adding assets.

Localized "Asset Summary Report (Germany)"

The local requirements of §268 (2) HGB can be achieved with the Asset SummaryReport (Germany), with the following column headings Original Asset, Additions,Retirements, Changes Of Accounts, Cost Adjustments, Accumulated Depreciation,Depreciation Expense, NBV Ending Period and NBV Beginning Period.

New Localizations R12

There are several localizations available for Oracle's customers. These should help ourcustomers to manage their business. These localizations are fully supported and can befound in Metalink (search for "EMEA Add-On Localizations")

In order to complete the certification successfully, the following localizations wereinstalled.

VAT Reporting There are four reports available, which help the user to reconcile their VAT.

CLE: Journal Details Report

This localization is using the accounting sequence number, and supports thereconciliation process


77/202

Audit Trail 4-1

4Audit Trail

Define Tables to be Audited

The following tables have to be audited. In the event that you have extended thestandard EBS functionality, these extensions should also be audited if they extend ormodify information that is used to create or derive accounting information.

GL

GL Period (Periodenstatus)

TABLE COLUMNS

GL_PERIOD_STATUSES APPLICATION_ID (PK)

CLOSING_STATUS

PERIOD_NAME (PK)

SET_OF_BOOKS_ID (PK)

Accounting Flexfield (Kontoflexfelddetails)

TABLE COLUMNS

FND_FLEX_VALUES_TL FLEX_VALUE_ID (PK)LANGUAGE (PK)

DESCRIPTION

FLEX_VALUE_MEANING


78/202


Exchange Rates (Wechselkursänderungen)

TABLE COLUMNS

GL_DAILY_RATES FROM_CURRENCY (PK)

TO_CURRENCY (PK)

CONVERSION_DATE (PK)

CONVERSION_TYPE (PK)

CONVERSION_RATE

Ledger/Ledger Set Changes (Ledger/Ledgerset Änderungen)

TABLE COLUMNS

GL_LEDGERS LEDGER_ID (PK)

NAME

SHORT_NAME

DESCRIPTION

LEDGER_CATEGORY_CODE

OBJECT_TYPE_CODE

COMPLETION_STATUS_CODE

CHART_OF_ACCOUNTS_ID

CURRENCY_CODE

PERIOD_SET_NAME

GL_LEDGER_SET_NORM_ASSIGN LEDGER_ID (PK)

LEDGER_SET_ID (PK)

START_DATE

STATUS_CODE

AP

AP Period (Periodenstatus)


79/202

Audit Trail 4-3

TABLE COLUMNS


CLOSING_STATUS

PERIOD_NAME (PK)


Supplier Header & Site Information (Lieferantenheader und –site Informationen)

TABLE COLUMNS

HZ_PARTIES PARTY_ID (PK)

PARTY_NAME

PARTY_NUMBER

PARTY_TYPE

PERSON_IDENTIFIER

PERSON_FIRST_NAME

PERSON_LAST_NAME

HZ_PARTY_SITES PARTY_SITE_ID (PK)

LOCATION_IDREGION

PARTY_SITE_NUMBER

PARTY_SITE_NAME

PARTY_ID

Supplier Bank Account Data (Bankdaten)

TABLE COLUMNS


80/202


IBY_EXT_BANK_ACCOUNTS EXT_BANK_ACCOUNT_ID (PK)

BANK_ACCOUNT_NAME

BANK_ACCOUNT_NUM

BANK_ACCOUNT_TYPE

BANK_ID

BRANCH_ID

AR

AR Period (Periodenstatus)

TABLE COLUMNS


CLOSING_STATUS

PERIOD_NAME (PK)


AR System Parameters (Debitorenoptionen)

TABLE COLUMNS

AR_SYSTEM_PARAMETERS_ALL ORG_ID (PK)

SET_OF_BOOKS_ID

ACCOUNTING_METHOD

RUN_GL_JOURNAL_IMPORT_FLAG

CER_SPLIT_AMOUNT

CER_DSO_DAYS

POSTING_DAYS_PER_CYCLE

INVOICE_DELETION_FLAG

GENERATE_CUSTOMER_NUMBER

Customer Header & Site Information (Kundenheader und –site Informationen)


81/202

Audit Trail 4-5

TABLE COLUMNS

HZ_PARTIES PARTY_ID (PK)

PARTY_NAME

PARTY_NUMBER

PARTY_TYPE

PERSON_IDENTIFIER

PERSON_FIRST_NAME

PERSON_LAST_NAME

HZ_PARTY_SITES PARTY_SITE_ID (PK)

LOCATION_ID

REGION

PARTY_SITE_NUMBER

PARTY_SITE_NAME

Customer Bank Account Data (Bankdaten)

TABLE COLUMNS

IBY_EXT_BANK_ACCOUNTS EXT_BANK_ACCOUNT_ID (PK)BANK_ACCOUNT_NAME

BANK_ACCOUNT_NUM

BANK_ACCOUNT_TYPE

BANK_ID

BRANCH_ID

Party Merge

TABLE COLUMNS


82/202


HZ_MERGE_PARTIES BATCH_PARTY_ID (PK)

BATCH_ID

FROM_PARTY_ID

TO_PARTY_ID

MERGE_STATUS

Account Merge

TABLE COLUMNS

RA_CUSTOMER_MERGE_HEADERS CUSTOMER_MERGE_HEADER_ID(PK)

CUSTOMER_ID

MERGE_REASON_CODE

MERGE_FAIL_MSG

FA

Asset Book Setup (Afa Buch Setup)

TABLE COLUMNS

FA_BOOK_CONTROLS BOOK_TYPE_CODE (PK)

BOOK_CLASS

AMORTIZE_FLAG

INITIAL_DATE

LAST_DEPRN_RUN_DATE

SET_OF_BOOKS_ID

DEPRN_CALENDAR

Asset Categories Setup (Anlagegruppensetup)

TABLE COLUMNS


83/202

Audit Trail 4-7

FA_CATEGORIES_TL CATEGORY_ID (PK)

LANGUAGE

DESCRIPTION

Depreciation Methods of an Asset (Abschreibungsmethoden einer Anlage)

TABLE COLUMNS

FA_METHODS METHOD_CODE (PK)

METHOD_ID (PK)

NAME

DEPRN_BASIS_RULE

DEPRN_BASIS_FORMULA

DEPRN_BASIS_RULE_ID

Asset Prorate Convention Rules

TABLE COLUMNS

FA_CONVENTION_TYPES PRORATE_CONVENTION_CODE (PK)

DESCRIPTION

CREATION_DATE

FA_CONVENTIONS PRORATE_CONVENTION_CODE (PK)START_DATE (PK)

PRORATE_DATE

Assets and Asset books

TABLE COLUMNS


84/202


FA_BOOKS BOOK_TYPE_CODE

ASSET_ID,

DATE_EFFECTIVE

LIFE_IN_MONTHS

DEPRN_START_DATE

DEPRN_METHOD_CODE

LIFE_IN_MONTHS

ADJUSTED_COST

ORIGINAL_COST

PRORATE_CONVENTION_CODE

PRORATE_DATE

CAPITALIZE_FLAG

DEPRECIATE_FLAG

LAST_UPDATE_DATE

LAST_UPDATED_BY

DATE_INEFFECTIVE

RETIREMENT_ID

RECOVERABLE_COST

LAST_UPDATE_LOGIN

Assets and Asset Description

TABLE COLUMNS


85/202

Audit Trail 4-9

FA_ADDITIONS_TL ASSET_ID

LANGUAGE

DESCRIPTION

LAST_UPDATE_DATE

LAST_UPDATED_BY

CREATED_BY

CREATION_DATE

Assets, Asset numbers, Asset Categories

TABLE COLUMNS


86/202


FA_ADDITIONS ASSET_ID

ASSET_NUMBER

ASSET_KEY_CCID

CURRENT_UNITS

ASSET_TYPE

ASSET_CATEGORY_ID

PARENT_ASSET_ID

SERIAL_NUMBER

MODEL_NUMBER

IN_USE_FLAG

OWNED_LEASED

NEW_USED

ATTRIBUTE_CATEGORY_CODE

CONTEXT

LEASE_ID

INVENTORIAL

LAST_UPDATE_DATE

LAST_UPDATED_BY

CREATED_BY

CREATION_DATE

LAST_UPDATE_LOGIN

Assets – Asset Distributions

TABLE COLUMNS


87/202

Audit Trail 4-11

FA_DISTRIBUTION_HISTORY DISTRIBUTION_ID

BOOK_TYPE_CODE

ASSET_IDUNITS_ASSIGNED

DATE_EFFECTIVE

CODE_COMBINATION_ID

LOCATION_ID

LAST_UPDATE_DATE

LAST_UPDATED_BY

DATE_INEFFECTIVE

ASSIGNED_TORETIREMENT_ID

TRANSACTION_HEADER_ID_OUT

LAST_UPDATE_LOGIN

Functional Setup

Configure the Profile Options

Profile option 'Sign-On: Audit Level' set to 'FORM'

Profile Option 'Audit Trail: Activate' set to 'YES'

Enabl