Saturday, February 27, 2010

SNAPSHOT

Oracle Financials Implementation Guide (R12)


  1. Criteria for Seperate Accounting Setup (Ledger)
    1. Chart of Accounts
    2. Currency
    3. Calendar
    4. Sub ledger Accounting Method
    5. Ledger Processing Options
    6. Need for Sequencing
    7. Need for Open/Close Periods separately
    8. Tax requirements
    9. Legal requirement to maintain a Ledger separately 

 

IFRS


    1. IFRS are issued by IASB       


SLA-Sub Ledger Accounting

    SAM-Sub Ledger Accounting Methods
        AAD-Application Accounting Definitions
            JLD-Journal Line Definitions 
                ADR-Account Derivation Rules
                    Mapping Sets

   Events
        Entity (AP_INVOICE, AP_PAYMENT)
            Class (INVOICE, CREDIT_MEMO, DEBIT_MEMO, etc)
                Type (INVOICE_VALIDATED, INVOICE_ADJUSTED, INVOICE_CANCELED)AD-Application Accounting Definitions 
        

E-Biz Tax

    Tax Authority - Government entity that regulates tax law, administers, or audits one or more taxes

        Tax Regime - The set of tax regulations that determine the treatment of one or more taxes administered by a tax authority  (Country, Operating Units (Party Name))

            Regime to Rate Flow-Tax - A distinct charge imposed through a fiscal or tax authority  (GL Accounts, tax type, Geography type, Parent geography)

                    Tax Jurisdiction - A geographical area where a tax is levied by a specific tax authority or where a specific tax rate applies

                        Tax Status - The taxable nature of a product or service in the context of a transaction for a tax type. Similar to the Tax code definitions in 11i

                      Tax Rate - The rate specified for a tax status in effect for a period of time. You can express the tax rate as a percentage or as a value per unit quantity (rate)

    


Implement Financials


  1. Setup User/Responsibility

    1. Login to ‘System Administrator’ responsibility Using SYSADMIN/SYSADMIN

    2. Create a new User and attach required responsibilities & ‘System Administrator’ responsibility to the User.

    3. Log off and Log into System Administrator’s responsibility with the new User

    4. Setup the Profile Option ‘HR: USER TYPE’ to ‘HR USER’ for the new responsibility. Unless we do this we can not open any forms (Profiles>>System)

    5. Define Organizations (PO>>Setup>>Organizations>>Organizations)

      1. Create Location/s (Addresses) for Business Group

      2. Create Business Group and assign it at ……

      3. Create Operating Units, Inventory Organizations


  1. General Ledger Setup

    1. Switch to the GL responsibility and create following Flex fields and compile them (Keep the Dynamic Insertion option on)

      1. Accounting Flex field (Values Required)

      2. Job Flex Field (Value set Validation type should be ‘NONE’, so that values can be entered from the Screen)

      3. Position Flex field (Value set Validation type should be ‘NONE’)

      4. Stock Locators (a Future segment with out Value set will do)

      5. System Items (Values Required)

      6. Sales Orders (a Future segment with out Value set will do)

      7. Item Catalogs (a Future segment with out Value set will do)

      8. Account Aliases (a Future segment with out Value set will do)

      9. Item Categories (Value set Validation type should be ‘NONE’)

        1. Define one of the seeded Structures depending on the requirement (Normally ‘Item Category’)

        2. Create Category Codes (PO>>Setup>>Items>>Categories>>Category code)

        3. Create Category Sets (PO>>Setup>>Items>>Categories>>Category Sets)

        4. Assign Default Category set for ‘Purchasing’ and ‘Inventory’ (PO>>Setup>>Items>>Categories>>Default Category code)


    1. Define Set of Books

      1. Define Period types (e.g. Month, Quarter, Year )

      2. Define Calendar

      3. Define Currencies

      4. Define SOB


    1. Define Organizations (PO>>Setup>>Organizations>>Organizations)

      1. Create Location/s (Addresses) for LE/s

      2. Create Legal entity/s and enter ‘employer identification’ and ‘legal accounting’ from others

      3. Run ‘Replicate seed data’ report from the System Administrator’s Responsibility


    1. Setup System Profiles

      1. Switch to System Administrator and setup OU and SOB in profile options as follows.

        1. MO: operating unit (Default OU at site level is required. This can be overridden for each Responsibility)

        2. GL: set of books

        3. Folders: Allow customization (Yes/No)(USER lever only)

          1. (This is required only if we want to change (Show/Hide fields) the default view of the folder, for the reasons like assigning the sequence for the invoice type as manual, which requires entry of the Voucher Number manually which is hidden by default. In such case set up the above profile and select the fields to show/hide from the folders menu and save that view as default view, so that every time we open the screen we can see the modified view)

        4. Sequential Numbering: Always/Never/Partial

          1. (If we select ‘Always’, we have to define and assign Sequences for each Application, Category combination where ever mandatory. (GL>>Setup>>Financials>>Sequences)


    1. Value Security Setup

      1. Activate the Segment for the Security (GL>>Setup>>Financials>>Flex field>>Key>>Segment)

      2. Define Security rule for the Value set (GL>>Setup>>Financials>>Flex field>>Key>>Security>>Define)

      3. Assign the rule to responsibility


    1. Global Inter company System (GIS)

      1. Create Subsidiaries (GL>>Setup>>Inter company>>Subsidiaries)

      2. Create Transaction types (GL>>Setup>>Inter company>>Transaction types)

      3. Create Clearing account/s (GL>>Setup>>Inter company>>Clearing Accounts)

      4. Create Auto Accounting Rules if required (GL>>Setup>>Inter company>>Auto Accounting Rules)

      5. We have to run request “Program – Inter company Transfer ” to transfer the transaction to Sender/Receiver


  1. Purchasing Setup

    1. Switch to the ‘Purchasing Super User’ responsibility

    2. Define Organizations (Setup>>Organizations>>Organizations)

      1. Create Locations (Addresses) for OU/s, IO/s

      2. Create Operating unit/s and attach legal entity and sob to it

      3. Run ‘Replicate seed data’ report from the System Administrator’s Responsibility

      4. Create Inventory organization/s and enter accounting info, inventory info and receiving info from others


    1. Setup System Profiles

      1. Switch to System Administrator and setup OU and SOB in profile options as follows.

        1. MO: operating unit (for each Responsibility)

        2. GL: set of books

        3. PO: workflow process mode (background/online)

        4. Folders: Allow customization (Yes/No)(USER lever only)

          1. Note: This is required only if we want to change (Show/Hide fields) the default view of the folder, for the reasons like assigning the sequence for the invoice type as manual, which requires entry of the Voucher Number manually which is hidden by default. In such case set up the above profile and select the fields to show/hide from the folders menu and save that view as default view, so that every time we open the screen we can see the modified view


    1. Switch to the ‘Purchasing Super User’ responsibility and Choose SOB. System allows to choose SOB only once for an OU irrespective of the no of Responsibilities it is attached to (Setup>>Organizations>>SOB>>Choose)


    1. Define Default Category Sets

      1. Define a ‘Item Categories’ flex field with value set type as ‘Independent’

        1. Note: If the Item Category is single Segment Flex field, then we can create the Value set type as NONE

      2. Enter Value for the segments

      3. Create code combinations (PO>>SETUP>>ITEMS>>CATEGOIRES>>CATEGORY CODES)

      4. Define Category sets (PO>>SETUP>>ITEMS>>CATEGOIRES>>CATEGORY SETS)

      5. Define ‘Default Category Sets’ for various applications (PO>>SETUP>>ITEMS>>CATEGOIRES>>Default Category Sets)


    1. Setup Approval/Security Hierarchies

      1. Position hierarchies (Positions need to be Setup)

        1. Make sure to select ‘Business Group’ and enable the check box ‘use approval hierarchies’ on ‘human resources’ tab in ‘financial options’ (setup>organizations>financial options)

        2. Create Jobs. i.e., Buyer, Vice President, etc (setup>personal>jobs)

        3. Create Positions (a Sub category to Job). i.e., IT buyer, vice president marketing, etc and attach the Job to it. Set the Status to Active. The ‘Reporting to’ hierarchy will automatically get populated once this position is attached to a hierarchy (setup>personal>positions)

        4. Create Position hierarchies (setup>personal>position hierarchies)

              1. Enter Name of the Hierarchy, version, date and save it

              2. In the Position Block search for the Position for which you want to create Subordinates

              3. Save it and in the subordinates Block select the Positions which you want to be subordinates and save it.

        5. Create Approval groups and specify the ranges for the following. Approval Groups are OU Specific. (setup>approvals>approval groups)

              1. Document total (Mandatory for Blanket & Contract PO)

              2. Account range (Mandatory for Standard PO)

              3. Item category range

              4. Item range

              5. Location range

              6. Note: If the ‘Security Level’ is set to ‘Hierarchy’ then each Position in the Approval Hierarchy should be attached with a Approval group which has a Include of that Document type

        6. Associate combinations of Document type and Approval group to specific Positions on ‘Approval assignments’ (setup>approvals>approval assignments)

        7. Create employees and attach the Position to it in ‘More’ (Setup>Personnel>Employees)

        8. Run ‘Fill Employee Hierarchy’ request (PO>>view>>request)


      1. Employee/supervisor relationships (no position setup required)


    1. Create Employee/s. Attach the Buyer Employee/s to the Buyers list

    2. Switch to System Administrator and attach a buyer Employee to the User and switch back


    1. Define document types (setup>purchasing>document types)

    2. Security level

        1. Public: Everybody can see the Document

        2. Private: Only the owner can see

        3. Purchasing: Only Buyers can see

        4. Hierarchy: Everybody in the hierarchy can see (‘Security Hierarchy’ in ‘Control’ tab on Purchasing Options must to be entered)

      1. Access level

        1. Full

        2. View only

        3. Modify

      2. Setup default Hierarchy

        1. Note: If you do not define default hierarchy you have to manually select the hierarch at the time of submitting each PO. Hence this is mandatory

      3. Approval Options

        1. Owner can approve

        2. Approver can Modify

        3. Can change Forward –to

        4. Can change Forward – from

        5. Can change Approval hierarchy

        6. Disable


    1. Set up Purchasing, Receiving and Financial Options (Setup>>Organizations). Make sure you have entered the default Inventory organization on ‘Supplier-Purchasing’ tab

    2. We can Implement Organizational access by Responsibility (Inventory>>Setup>>Organizations>>Organization Access)

    3. Define UOM Class (Setup>>UOM>>Classes)

    4. Define Line types (Setup>>Purchasing>>Line types)


    1. Encumbrance

      1. Enable ‘Budgetary Control’ and define reserve account in the SOB definition (GL>>Financials>>Books>>Define)

      2. Enable Encumbrance in the Financial Options (PO>>Setup>>Organizations>>Financial Options)

      3. We have to run request ‘Program – Create Journals’ to create encumbrance journals


    1. Various types of Variances

      1. Purchase Price (PPV) – PO price and Standard Cost (IO>>Inventory Info)

      2. Invoice Price (IPV) – PO Price and Invoice Price (IO>>Inventory Info)


    1. Control Purchasing Periods (Open, Never Opened, Closed, Permanently Closed, Future)


Functional

a) Purchasing Process

      1. Enter Requisition (Internal, Purchase) (Requisitions> Requisitions)

      2. Tables Used

PO_REQUISITION_LINES_ALL

PO_REQ_DISTRIBUTIONS_ALL

      1. Request for quotation (bid, catalog, standard)

      2. Enter quotations

      3. Quotation analysis

      4. Enter/Generate/Release Purchase Order

      5. Enter PO (Blanket, Contract, Planned, Standard )

      6. Enter PO Lines (Expense, Goods, IGC contract commitment, Outside processing)

      7. Click on Shipments and enter the info then

      8. Click on Distributions and check the info if correct else enter/ Modify the info

      9. Tables Used

PO_HEADERS_ALL

PO_LINES_ALL

PO_LINE_LOCATIONS_ALL

PO_LINE_DISTRIBUTIONS_ALL

      1. Approve it

      2. Receive Goods/Services (3 way matching)

RCV_SHIPMENT_HEADERS_V

      1. Inspect (4 way matching)


    b) Reconciliation


  1. Accounts Payable Setup

    1. Switch to System Administrator and create a Payables Responsibility and attach appropriate Payable Menu

    2. Setup Following Profiles for the responsibility (SA>>Profiles>>System)

      1. MO: operating unit

      2. GL: set of books

      3. Folders: Allow customization (Yes/No)(USER lever only)

Note: This is required only if we want to change (Show/Hide fields) the default view of the folder, for the reasons like assigning the sequence for the invoice type as manual, which requires entry of the Voucher Number manually which is hidden by default. In such case set up the above profile and select the fields to show/hide from the folders menu and save that view as default view, so that every time we open the screen we can see the modified view

      1. Sequential Numbering: Always/Never/Partial

Note: If we select ‘Always’, we have to define and assign Sequences for each Application, Category combination where ever mandatory. (GL>>Setup>>Financials>>Sequences)

      1. Use Invoice Batch Control: Site level Default is ‘No’


    1. Switch to the ‘Payable Manager’ responsibility and Choose SOB. System allows to choose SOB only once for an OU irrespective of the no of Responsibilities it is attached to (Setup>> SOB>>Choose)

    2. Define Pay terms

    3. Create Lookup Codes

      1. Pay Group (Purchasing)


    1. Setup Financial Options (If not already Setup)

    2. Setup Payables Options

      1. Automatic Offset


    1. Tax Setup

      1. Create Tax types if required. (AP>>Setup>>Lookup>>TAX_TYPE)

      2. Create required Tax Codes (AP>>Setup>>Tax>>Tax codes)

      3. Create Tax Groups for combinations of Tax codes

      4. Setup Tax in Financial Options ‘Tax’ tab


    1. Define Payment Terms

    2. Define Sequence/s and assign them to the different Categories (GL>>Setup>>Financials>>Sequences)

    3. Develop new Check format as required and attach it to Program (AP>>Setup>>Payment>>Programs)

    4. Define Banks, Check books, etc. Make sure to check the ‘Pooled Account’ box if you want to enabled ‘Automatic offset’ functionality for payments. (AP>>Setup>>Payments>>Banks)

    5. Approval Setup

      1. Switch to ‘AME Application Administrator’ responsibility

      2. Define attributes

      3. Define Conditions

      4. Define Approval Groups

      5. Define Rules

      6. Test the rules created


    1. Control Payable Periods (AP>>Accounting)


Functional

a) Invoice types

  1. Standard

  2. Credit memo

  3. Debit memo

  4. Expense report

  5. Po default *

  6. Quick match *

  7. Mixed *

  8. Prepayment

  9. Recurring invoice

* On saving system will the change the type to standard

For speed entry invoice gateway can be used (no validation occurs)


  1. Payment methods

      1. Checks

      2. EFT


c) Payment types

  1. Manual

  2. Quick

  3. Refund



d) GL transfer procedure

  1. Validate (from actions)

  2. Create accounting entries (from actions)

  3. Payables transfer to general ledger (request)

  4. Run journal import (request)

  5. And post

e) Payment entry (amount)

i) Invoice – positive

ii) Credit memo – negative

  1. Debit memo – negative

  2. Refund – negative


  1. There is netting report available between suppliers and customers, but to make it work properly the following 3 should be same.

  1. Name

  2. Currency

  3. Tax Code

g) Automatic payment processing

  1. Select

  2. Modify

  3. Format & print

  4. Confirm


h) Important tables

A. Customer master tables

D. Tables updated for auto pmt before confirm

1. PO_VENDORS

1. AP_INVOICE_SELECTION_CRITERIA

2. PO_VENDOR_SITES

2. AP_SELECTED_INVOICES

B. Invoice tables

3. AP_SELECTED_INVOICES_CHECKS

5. AP_BACHES

E. Tables updated for auto pmt after confirm

6. AP_INVOICES

9. AP_CHECKS

7. AP_INVOICE_DISTRIBUTIONS

10. AP_INVOICE_PAYMENTS

8. AP_PAYMENT_SCHEDULES

F. AP to GL transfer tables

C. For employee expenses

1. AP_ACCOUNTING_EVENTS_ALL

3. AP_EXPENSE_REPORT_HEADERS

2. AP_AE_HEADERS_ALL

4. AP_EXPENSE_REPORT_LINES

3. AP_AE_LINES_ALL

  1. GL transfer program uses 2 PL/SQL procedures named as APCCENG and APGLTRANS. APACCENG program looks for new transactions in the AP_SELECTED_INVOICE_CHECKS (for payments) and AP_INVOICES, AP_INVOICE_DISTRIBUTIONS (for invoices). Any new transactions found will be inserted to f tables. The GL_TRANSFER_FLAG in AP_AE_HEADERS_ALL will have y, n or e values to represent its status. APGLTRANS program picks up line from the AP_AE_LINES_ALL table where flag=n and inserts them in to GL_INTERFACE table


  1. Reconciliation

  1. AP: Accounts Payable Trial Balance

      1. GL: Posted Invoice Register

      2. GL: Posted Payment Register


  1. Important notes

  1. If ‘Allow Adjustments to Paid Invoices’ option is ON—

  1. If Invoice is not accounted and not paid we can make changes to distributions

  2. If Invoice is accounted but not paid then we have to reverse the Distributions to make changes

  3. If ‘Allow Adjustments to Paid Invoices’ option is OFF—


  1. Accounts Receivable Setup

    1. Switch to Administrator and create a AR Responsibility and attach appropriate Menu

    2. Set up the following Profiles

      1. MO: Operating Unit

      2. GL Set of Books

      3. AR: Transaction Batch Source (Optional, Default Batch Source on Transaction entry form)

      4. Tax: Allow Override of Tax Code

      5. DQM Match Rule for Online Duplicate Identification (Optional)

    3. Switch to new Responsibility and Setup the System Options (AR>>Setup>>System>>System Options)

    4. Define Transaction Sources (AR>>Setup>>Transactions>>Sources)

    5. Define Transaction types (AR>>Setup>>Transactions>>Transaction Types)

    6. Define Auto Accounting (AR>>Setup>>Transactions>>Auto Accounting)

    7. Define Remit to Addresses (AR>>ctrl L>>remit) (required only when enabled in system Options)

    8. Define Tax Codes (AR>>Setup>>Tax)

    9. Define Payment terms (AR>>Setup>>Transactions>>Payment terms)

    10. Define Banks (AR>>Setup>>Receipts>>Banks)

Note: AP needs to be setup (Choose Books) for the OU to define Banks

    1. Define Receipt Activities (AR>>Setup>>Receipt>> Receipt Activities)

    2. Define Receipt Classes (AR>>Setup>>Receipt>>Receipt Classes)

    3. Define Receipt (Batch) Sources (AR>>Setup>>Receipt>>Receipt Sources)

    4. Define Lock Boxes (AR>>Setup>>Receipt>>Lockboxes>>Lockboxes)

    5. Important tables

1. RA_CUSTOMER_TRX_ALL

Transaction headers

2. RA_CUSTOMER_TRX_LINES_ALL

Transaction Lines

3. RA_CUST_TRX_LINE_GL_DIST_ALL

Transaction Line Distributions

4. AR_PAYMENT_SCHEDULES_ALL

Payment Schedules

5. RA_CUST_TRX_TYPES_ALL

Transaction types

6. RA_ACCOUNT_DEFAULTS_ALL

Auto Accounting

7. RA_ACCOUNT_DEFAULT_SEGMENTS

Auto Accounting

8. AR_CASH_RECEIPTS_ALL

All Cash receipts are logged into this table

9. AR_DISTRIBUTIONS_ALL

This table stores the accounting distributions for cash receipts, miscellaneous receipts, adjustments, credit memo applications, cash receipt applications, and bills receivable transactions.

10. AR_CASH_RECEIPTS_HISTORY_ALL

The status field for that row tells you which step the receipt has reached

11. AR_RECEIVABLE_APPLICATIONS_ALL

This table stores all accounting entries for cash and credit memo applications

12. AR_MISC_CASH_DISTRIBUTIONS_ALL

This table stores all accounting entries for miscellaneous cash applications.

13. AR_RECEIPT_CLASSES

Receipt classes determine whether the receipt belonging to this class are created manually or automatically, and whether the receipts go through the different steps in a receipt’s life-cycle

14. AR_RECEIPT_METHODS

This table stores information about Payment

Methods, receipt attributes that you define and assign to Receipt Classes to account for receipts and their applications

15. AR_RECEIPT_METHOD_ACCOUNTS_ALL

For each receipt method, each bank account that can handle this Payment Method is defined as a row in this table

16. RA_INTERFACE_LINES_ALL

Invoice Interface table



  1. Cash Management Setup

    1. Switch to System Administrator and create a Cash Management Responsibility and attach appropriate Menu

    2. Setup Following Profiles for the responsibility (SA>>Profiles>>System)

      1. MO: operating unit

      2. GL: set of books

    3. Setup System Options

    4. Create Document Categories and Sequences for each Account (Bank) Name and assign them

    5. Define Bank Codes if you want to use Automatic Reconciliation feature. This is mapping of bank specific transaction codes to Oracle APPS transactions i.e., Payments, Receipts, Journals etc.


Functional

    1. Manual Bank Statement (Bank Reconciliation>>Bank Statements)

      1. Enter Bank account details and click on lines and enter lines. After entering the line click on Available and select the corresponding Payment/Receipt/Journal for that bank statement line and click Reconcile

      2. Alternatively on the Bank statement window click on Available button and select the Payment/ Receipt/Journal and click on Reconcile. This will automatically inserts a reconciled line in the Bank Statement

      3. Bank Statement Interface (Bank Reconciliation>>Bank Statement Interface)

        1. Place the text file from the bank on the designated path in the Unix box and run the request ‘Bank Statement Loader ’to upload the file data into Bank statement Interface table

        2. Run ‘Bank statement Import’ request to create the bank Statement from the interface table


      1. Automatic reconciliation (Request>>Automatic Reconciliation)

Statement Interface tables

Statement Tables

1. CE_STMT_INT_TMP


2. CE_STATEMENT_HEADERS_INT_ALL

1. CE_STATEMENT_HEADERS

3. CE_STATEMENT_LINES_INTERFACE

2. CE_STATEMENT_LINES


  1. Fixed Assets Setup

    1. Switch to Administrator and create a FA Responsibility and attach appropriate Menu

    2. Setup the following flex fields (FA>>Setup>>Financials>>Flex fields>>Key>>Segments)

      1. Category flex filed

      2. Location flex field

      3. Asset Key flex field


    1. Setup System Controls (FA>>Setup>>Asset System>>System Controls)

    2. Define Fiscal Years (FA>>Setup>>Asset System>>Fiscal Years)

    3. Define Calendars (FA>>Setup>>Asset System>>Calendars)

(Note: Period Names should be same as GL period Names)

    1. Define Prorate Conventions (FA>>Setup>>Asset System>>Prorate Conventions)

    2. Create Locations (FA>>Setup>>Asset System>>Locations)

    3. Create Asset Keys (FA>>Setup>>Asset System>>Asset Keys)

    4. Define Depreciation Methods (FA>>Setup>>Depreciation>>Methods)

    5. Create Books (FA>>Setup>>Asset System>>Book Controls)

    6. Create Asset Categories for all the Books Created (FA>>Setup>>Asset System>>Asset Categories)


Functional

    1. Asset types

      1. Capitalized (Can be Depreciated)

      2. CIP (Will not be Depreciated)

      3. Expense (Can not be Depreciated)

      4. Group Asset


    1. Five Major functionalities of Oracle Assets

      1. Asset Additions

        1. Quick Addition

        2. Detail Addition

        3. Mass Additions (Asset Interface)


      1. Assets Adjustments

        1. Change the Depreciation Method

        2. Change the Life

        3. Reclassify (Change in Category)

        4. Change in financial info like cost, depreciation and Amortization etc.

        5. Revaluation


      1. Asset Transfers

        1. Between Ledger accounts

        2. Locations

        3. Employees


      1. Asset Retirements

        1. Retire assets fully or partially, by units or cost, and in the current or previous accounting periods. You can retire an asset from any depreciation book without affecting other books.

        2. Reinstate Retired Assets


      1. Depreciation

        1. Run Depreciation

        2. Project Depreciation

        3. Rollback Depreciation


    1. Important Tables

1. FA_BOOK_CONTROLS

Definition of Asset Books

2. FA_CATEGORIES_B

Asset Category Flex field info

3. FA_CATEGORY_BOOKS

Default Accounting info for each category

4. FA_CATEGORY_BOOK_DEFAULTS

Default Depreciation info for each category

5. FA_MASS_ADDITIONS

Asset Interface Table

6. FA_ADDITIONS_B

Asset Master Table

7. FA_TRANSACTION_HEADERS

Transaction info of an Asset

8. FA_BOOKS

This table contains all the info of each asset required to calculate Depreciation. A record will be inserted every time a new asset is created or Modified

9. FA_ASSET_HISTORY

This is an audit table. Any change to any asset will insert a new record here and end dates the earlier one

10. FA_DISTRIBUTION_HISTORY

Contains the info about the employee, location accounting

11. FA_DEPRN_PERIODS

Open period

12. FA_DEPRN_DETAILS

Contains all info regarding Depreciation and related info like YTD, Reserve, Bonus Depreciation etc.


    1. Setup Security by Book

      1. Create Assets organizations and attach the Book/s

The description needs to be changed (add space)

      1. Create Organization Hierarchy (FA>>Setup>>Security>>Organization>>Hierarchy)

      2. Create Security Profiles (FA>>Setup>>Security>>Security)

      3. Run the Security List Maintenance program

      4. Setup FA: Security Profile


    1. Migration Strategy

      1. Following minimum info to be collected

        1. Asset Description

        2. Location flex field info

        3. Category flex field info

        4. Units

        5. Total Cost

        6. YTD Depreciation

        7. ITD Accumulated Depreciation

        8. Depreciation Expense Account

        9. Date Placed in Service

        10. Clearing (Migration) Account --Optional



      1. Collect the date with the above minimum info

      2. Upload it thru ADI with Option Post checked

      3. Important notes

        1. Depreciation and Accumulated Depreciation balances should be taken to their respective accounts in the trial balance upload

        2. Asset Cost balances should be taken to either Asset clearing/Migration accounts. The same account should be entered in asset upload sheet (Point 10 above)





No comments:

Post a Comment