Professional Documents
Culture Documents
Author:
Version
1.0
Table of Contents
GL Setup Steps ......................................................................................................................................................................................................................................... 3 GL Profile Options .................................................................................................................................................................................................................................... 5 AP Setup Steps ......................................................................................................................................................................................................................................... 7 AP Lookups ........................................................................................................................................................................................................................................... 9 AP Profile Options .................................................................................................................................................................................................................................. 10 AR Setup Steps ....................................................................................................................................................................................................................................... 11 AR Profile Options .................................................................................................................................................................................................................................. 17 FA Setup Steps ....................................................................................................................................................................................................................................... 19 FA Profile Options .................................................................................................................................................................................................................................. 20 Payments Setup Steps............................................................................................................................................................................................................................ 21 Payments Profile Options ...................................................................................................................................................................................................................... 22 E-Tax Setup Steps ................................................................................................................................................................................................................................... 23 E-Tax Profile Options.............................................................................................................................................................................................................................. 25 Subledger Accounting Profile Options ................................................................................................................................................................................................... 26 WebAdi Accounting Profile Options ...................................................................................................................................................................................................... 27
Page 2 of 27
GL Setup Steps
GL # 1 2 3 Required
Required Optional Optional
Step
Define CoA. Define Cross-validation Rules to Prevent Certain Account Combinations From Being Created. Define A CoA Mapping to Map Two or More Charts of Accounts. the CoA Mapping Is Used By Accounting Setup Manager to Complete the Setup Steps for Secondary Ledgers, and It Is Used By the Global Consolidation System (gcs) to Consolidate Data Between Ledgers. Define Descriptive Flexfields Define Accounting Period Types. Define Accounting Calendar. Review the Calendar Validation Report to Note Common Setup Errors. Define A Transaction Calendar and Valid Business Days for That Calendar. if to Use Average Balance Processing. Enable Currency of the Ledger Define Conversion Rate Types and Conversion Rates, Such As Daily Rates and Historical Rates. Define Additional Journal Entry Sources. if You Have Enabled Average Balance Processing, Specify an Effective Date Rule for Each Journal Source You Define. Define Additional Journal Categories. Define Journal Reversal Criteria. Define an Accounting Setup Using Accounting Setup Manager to Combine Legal Entities, Ledgers, Reporting Currencies, Subledger Accounting Methods, and Other Setup Information. Before You Can Enter Transactions and Journal Entries to Ledgers, You Must Complete the Ledger Options for All Ledgers Assigned to an Accounting Setup and the Accounting Setup Status Must Be Complete. Define Ledger Sets to Group Ledgers That Share the Same CoA and Accounting Calendar/period Type Combination to Take Advantage of Processing Efficiencies, Such As Opening and Closing Periods Across Ledgers In A Ledger Set. Define Data Access Sets to Secure Read and Write Access to Ledgers, Balancing Segment Values, and Management Segment Values for One or More Ledgers. Assign A Ledger to the Profile Option Gl Ledger Name for Each oracle Subledger. This Profile Option Controls the Ledger CoA That Each Subledger Will Use for Transaction Processing. Assign A Data Access Set to the Profile Option Gl: Data Access Set for Each General Ledger Responsibility. Define Definition Access Sets and Assign them to Responsibilities. Once Definitions Are Secured, Definition Access Sets Can Be Assigned to Responsibilities. Define Account Combinations That Can Be Used for Data Entry if Dynamic Insertion Is Not Enabled for Coa Structure. Define and Assign Document Sequences Define Employees. Setup Journal Approval.
Reference
Common Applications Common Applications Common Applications
4 5 6 7
Common Applications Common Applications Common Applications Common Applications Common Applications Common Financials GL GL GL GL
14 Optional 15 Optional 16 Required 17 Required 18 Optional 19 Optional 20 Required 21 Optional 22 Optional Page 3 of 27
GL
Step
Define One or More of the Following Optional Accounts: 1. Suspense Accounts. 2. Statistical Units of Measure. Define Transaction Codes if You Use Public Sector General Ledger. Create Summary Accounts Set Up Automatic Tax Calculation if You Do Not Have oracle Receivables and oracle Payables Installed. Define Automatic Posting Criteria. Define Encumbrance Types. Setup Budgets. if to Enable Budgetary Control, Define One or More Budgetary Control Groups. Define Security Rules. Set General Ledger Profile Options. Open an Accounting Period. Set Up the Global Consolidation System (gcs).
Reference
GL
24 25 26 27 28 29 30 31 32 33 34
Optional Optional Optional Optional Optional Optional Optional Optional Required Required Optional
GL GL GL GL GL GL GL GL GL GL GL
Page 4 of 27
GL Profile Options
# 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 GL Profile Options
Budgetary Control Group Daily Rates Window: Enforce Inverse Relationship During Entry Enter Journals: Validate Reference Date FSG: Accounting Flexfield FSG: Allow Portrait Print Style FSG: Enforce Segment Value Security FSG: Expand Parent Value FSG: Message Detail GL: Archive Journal Import Data GL: AutoAllocation Rollback Allowed GL: Data Access Set GL: Debug Mode GL: Income Statement Accounts Revaluation Rule GL: Journal Review Required GL: Launch AutoReverse After Open Period GL: Number of Accounts In Memory GL: Number of Formulas to Validate for each MassAlloca tion Batch GL: Number of Formulas to Validate for each Recurring Journal Batch GL: Number of Purge Workers GL: Number of Records to Process at Once GL: Owners Equity Translation Rule GL Account Analysis Report: Enable Segment Value Security on Beginning/ Ending Balances GL AHM: Allow User to Modify Hierarchy GL AutoAllocation: Continue to Next Step if No Journal Created GL Consolidation: Preserve Journal Batching GL Consolidation: Preserve Journal Effective Date GL Consolidation: Cross Instance Workflow Notification Contact GL Consolidation: Separate Rows for Debit and Credit Account Balances in Consolidation Journal GL Daily Rates: Cross Rates Override GL Journal Import: Separate Journals by Accounting Date GL: Ledger ID GL: Ledger Name
Value
No default No No Account No No No Minimal No Yes No default No YTD No Yes 2500 5 5 No 1000 PTD No No No No No No default No User Entered Rate Overrides No System Defined No default
Required
Required
Page 5 of 27
Value
No default No 0 No Yes 3 5000 5000 PTD No No No No default No No Go Up Mgt Chain No No Yes
Page 6 of 27
AP Setup Steps
AP # 1 2 3 4 5 6 7 8
Applications Setup Steps Required Required Optional Optional Required Required Required Required
Step
Create application user sign-ons and passwords. Define Chart of Accounts. Enable Currencies to be used. Define Foreign Currency Exchange Rate Types, and enter Daily rates. Define Accounting Period Types and Accounting Calendar Periods. Define a Ledger Set the SET_OF_BOOKS_ID profile option to Updateable. Set the GL: Data Access Set profile option. - If not using multi-org feature, set the option for the Oracle Payables application. - If using multi-org feature, set the option for each unique combination of organization and responsibility. Define Descriptive Flexfields. Enter Locations. Define Employee Lookups. If Oracle Human Resources installed, Enter employees. If Oracle Inventory or Oracle Purchasing is installed, Define at least one Inventory Organization before defining Financials Options. Implement Sequential Voucher Numbering. Set Up Taxes. Update Country and Territory information, and assign flexible address formats. Implement Budgetary Control in General Ledger.
Performed for
SysAdmin GL GL GL GL GL Application Developer SysAdmin
9 10 11 12 1 2 3 4 5
Optional Required Optional Conditionally Required Financials Setup Steps: Conditionally Required Optional Required Optional Optional Payables Setup Steps Required Required Required Optional Conditionally Required Required Required Required Required with Defaults
1 2 3 4 5 6 7 8 9
Install or upgrade Payables. Choose Primary Ledger. Assign Ledger to a responsibility. Set profile options. Assign Reporting Ledger Define Financials Options. Define Payables System Setup Options. Define Payables Options. Define Payables Lookups.
each installation each organization SysAdmin SysAdmin each organization each organization each organization each installation
Page 7 of 27
Step
Required with Defaults Required with Defaults Required Required Optional Conditionally Required Optional Optional Optional Required with Defaults Optional Optional Optional Optional Required Optional Optional Required Conditionally Required Optional Optional Conditionally Required Conditionally Required Define Purchasing Lookups. Define Payment Programs. Define Payment Terms. Define Banks, bank transmission details, and bank accounts Define Special Calendars Define Suppliers and Supplier Sites. Define Distribution Sets. Define Request Sets. Define Matching Tolerances for purchase orders. Define Invoice Hold and Release names. Define Payment Interest Rates If to use Automatic Interest Calculation. Define Expense Reports Templates if to use Payables or Oracle Internet Expenses to enter employee expense reports. Define Payment Formats. Define the format for the Invoice Aging Report. Set up Print Styles and Drivers for the Supplier Mailing Labels Report. Set up Credit Card programs if to use credit cards or procurement cards. If to use the Invoice Approval Workflow to automate approval process then enable the feature and set up the workflow. Open Payables Accounting Period. Define Tax Authority type suppliers if to use automatic withholding tax. This is a must before defining tax codes and tax groups. Define Tax Codes and Withholding Tax Groups if to use automatic withholding tax. Define Withholding Tax Certificates and Exceptions. Define Reporting Entity(ies) for income tax reporting. (Required with Defaults) Define additional United States 1099 income tax regions.
Performed for
each installation each installation each installation each organization each installation each organization each organization each installation each organization each installation each installation each installation each installation each installation each installation each installation each installation each installation each installation each organization each organization each organization each installation
Page 8 of 27
AP Lookups
Purchasing Lookups - FOB. Supplier default for all new purchase orders. - Freight Terms. Supplier default for all new purchase orders. - Minority Group. Supplier classification for reporting purposes. - Pay Group. Groups invoices in payment batches. - Supplier Type. Supplier classification for reporting purposes. You enter this value in the Type field of the Classification region of the Suppliers window. This value cannot exceed 25 characters or you will not be able to see it in the Suppliers window. Payables Lookups - AWT Certificate Types. Define withholding tax certificates. Payables predefines the Standard lookup name. - AWT Rate Types. Define Withholding Tax type tax codes. Payables predefines the following: Certificate, Exception, Penalty, and Standard lookup names. Important: Oracle Payables uses only the Standard AWT Rate Type. If to use an AWT Rate Type other than Standard, customize Automatic Withholding Tax to perform special behavior based on the AWT Rate Type. - Bank Branch Type. Payables predefines the following Bank Branch values that you enter in the Banks window: ABA, CHIPS, OTHER, SWIFT. - Card Brand. Used in the Credit Card Programs window. Payables includes four card brands: American Express, Diner's Club, MasterCard, and Visa. - Disbursement Type. Used upon defining payment documents in the Manage Payment Documents page accessed from the Banks Accounts page. Payables predefines three disbursement type values: Combined, Computer Generated, and Recorded. - Don't Pay Reason. Used in the Modify Payment Batch window when you remove all invoices for a supplier site from a payment batch. - EDI Payment Format. Payables predefines the following lookup names: CCD, CCP, CTP, CTX, PPD, PPP. - EDI Payment Method. Payables predefines the following lookup names: ACH, BACS, BOP, FEW, FWT, SWT, ZZZ. - EDI Remittance Method. Payables predefines the following lookup names: Do not route, EDI to Third party, EDI to payee, EDI to payee's bank, EDI to payer's bank. - EDI Transaction Handling. Payables predefines the following lookup names: C, D, I, U, Z. - Source. Used when you enter the source of invoices you want to import. - Tax Type. Used to define tax codes. Payables uses four predefined tax type values: Sales, Use, Offset, and Withholding Tax.
Page 9 of 27
AP Profile Options
# 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 AP Profile Options
Profile Options in Payables AP: Notification Recipient E-mail AP: Use Invoice Batch Controls AP: Show Finally Closed POs Profile Options in General Ledger Budgetary Control Group Journals: Display Inverse Rate Currency: Allow Direct EMU/Non-EMU User Rates. Enable Transaction Codes GL: Create Interfund Entries Profile Options for Multiple Organization Support MO: Default Operating Unit MO: Operating Unit MO: Security Profile Profile Options in Projects PA: Allow Override of PA Distributions in AP/PO PA: Default Expenditure Item Date for Supplier Cost Profile Options in Application Object Library AuditTrail: Activate Default Country Folders: Allow Customization Sequential Numbering Printer. Chargeable Subcontracting Enabled JMF: Enable Chargeable Subcontracting
Value
Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional No default No default No (for new installations); Yes (for upgrades ) No default No default No No default No default No default No default No default Yes No default
Required Required
Enabled Enabled
Page 10 of 27
AR Setup Steps
AR # 1 2 3 Required Step
Required Required Optional Define Ledgers Decide How to Use the Account Generator Define Transaction Flexfield Structure
Performed for
each installation each ledger each installation If you use AutoInvoice to import information from an external system and create transactions in Oracle Receivables, define Transaction Flexfields to uniquely identify these transactions. Because Transaction Flexfields are unique, you can also use them to link and reference other transaction lines. If you are not using AutoInvoice, proceed to the next step.
4 5 6 7
Optional
Define Descriptive Flexfields (System Items and Territory flexfields Define Organizations Define AutoCash Rule Sets Define Receivables Lookups
each installation
Optional
each installation
9 10 11
Optional
Define Invoice Line Ordering Rules Define Grouping Rules Define Application Rule Sets
each installation
Optional Optional
used when applying receipts imported using AutoLockbox to open debit items. used throughout the application to provide validated default values and list of values choices. You can add or update these to customize your list of values and speed data entry. Demand classes are categories you can use to segregate scheduled demand and supply into groups, so that you can track and consume the groups independently. You can then assign demand classes to customers in the Customers windows. specify how you want to order and number transaction lines after AutoInvoice groups them into invoices, debit memos, and credit memos. indicate how you want to group transaction lines imported by AutoInvoice. control how Receivables reduces the balance due for your open debit items when you apply payments using either the Applications window or Post QuickCash
If you skip this step, Receivables uses the rule set Line First - Tax After as the default. This rule set first applies the payment to the line amount and then applies the remaining amount to any associated tax.
12
Required
determine accounting flexfields, whether you use header or line-level rounding, and control the default operation of the AutoInvoice and Automatic Receipt programs.
Page 11 of 27
Required Step
Optional Define Flexible Address Formats Maintain Countries and Territories Define Payment Terms
Performed for
each installation To enter customer, supplier, bank, check, and remit-to addresses in country-specific formats, set up flexible address formats. Use the address style field to assign address styles to countries if you want to use the Flexible Address Formats feature. to determine the payment schedule and discount information for customer invoices, debit memos, and deposits. You can also define proxima payment terms to pay regular expenses such as telephone bills and credit card bills that occur on the same day each month and create split payment terms for invoice installments that have different due dates. To maintain transactions and account balances in multiple currencies, assign your reporting ledger to your primary ledger. This enables you to generate reports in each of your reporting currencies. Create revenue recognition schedules for your invoices.
Optional
each installation
Required
each installation
If you skip this step, Receivables uses 30 NET as the default. This payment term indicates that payment is due within 30 days.
16
Optional
If you are not using Multiple Reporting Currencies (MRC) functionality, skip this step. Important: If you have an accounting period type that is not Month and you use AutoInvoice with Oracle Order Management, you should update the Period field for the predefined IMMEDIATE accounting rule to the same period as your accounting period type.
17
Optional
each installation
18
Required
19
Required
Define AutoAccounting
to control the recording of accounting information for these periods. Receivables uses the status of these accounting periods to control transaction entry and journal entry creation to your general ledger. to specify the general ledger accounts for transactions that you enter manually or import using AutoInvoice. AutoAccounting uses this information to create the default revenue, receivable, freight, tax, unearned revenue, unbilled receivable, bills receivable accounts, and AutoInvoice clearing (suspense) accounts.
20
Optional
Page 12 of 27
Required Step
Optional Set Up Multi-Fund Accounts Receivable
Performed for
Oracle provides default seeded account derivation rules and journal entry descriptions. Attach seeded application accounting definitions (AAD) to a new subledger application method. You can create new account derivation rules and journal descriptions. In cases where multi-fund accounts receivable (MFAR) account pairs are needed, you can create mapping sets. Oracle does not provide default mapping sets for multifund accounts receivable. If you set up Oracle Receivables to create accounting entries when receipts are cleared in Oracle Cash Management, then you must set the AR: Activate Multi Fund Accounting Extract profile option to Yes for MFAR. assigned to invoices, debit memos, commitments, credit memos, on-account credits, and bills receivable. used to control transaction and transaction batch numbering, provide default transaction types for transactions in batch, and to select validation options for imported transactions. Receivables provides predefined transaction sources: MANUAL-OTHER, DM Reversal, and Chargeback.
22
Required
23 24
Required Required
each operating unit each installation Collectors can use the Collections windows and Receivables collection reports to keep apprised of a customer's past due items. Receivables provides a predefined collector called DEFAULT. Approval limits affect the Adjustments, Submit AutoAdjustments, and Approve Adjustments windows as well as the Credit Memo Request Workflow. to use a predefined revenue distribution set with noninvoice related receipts.
25 26 27 28 29
Required
each installation
Define Remittance Banks Distribution Sets Define Receivables Activities Define Receipt Programs
each operating unit each operating unit each operating unit each installation
used to send paper and electronic documents to your customers and remittance banks.
If you skip this step, Receivables uses the Automatic Receipt print program 'Print Created Receipts' (ARXAPFRC.rdf).
Page 13 of 27
Required Step
Required Define Receipt Classes
Performed for
each installation specify whether receipts are created manually or automatically. For manual receipts, you can specify whether to automatically remit it to the bank and/or clear your accounts. For automatic receipts, you can specify a remittance and clearance method, and whether receipts using this class require confirmation. to account for your receipt entries and applications and to determine a customer's remittance bank information. to provide default values for the receipt class, receipt method, and remittance bank account for receipts in a batch. Receipt Sources also determine whether the numbering for receipts in a batch is automatic or manual. to review and report on open receivables based on the number of days each item is past due. to control when you create customer statements. to customize the content of customer statements. Standard messages automatically print on the bottom of your statements. Use the Print Statements window to assign statement messages and submit statements for printing. If you defined a Territory Flexfield and want to create customized reports based on territory information, define Territory Flexfield combinations. You can assign Territory Flexfields to salespersons, invoices, and customer business purposes. to allocate sales credits to invoices, debit memos, and commitments. If you do not want to assign sales credits for a transaction, you can enter No Sales Credit. If AutoAccounting depends on salesperson, Receivables uses the general ledger accounts that you enter for each salesperson along with your AutoAccounting rules to determine the default revenue, freight, and receivable accounts for transactions.
31 32
Required Required
33 34 35
36
Optional
Define Territories
each installation
37
Required
Define Salespersons
38 39
Required Required
Define System Profile Options Define Customer Profile Classes Define Customers
each installation each installation to categorize customers based on credit, payment terms, statement cycle, automatic receipt, late charge, dunning, and invoicing information. If you skip this step, Receivables uses the profile class DEFAULT.
40
Required
each installation
Page 14 of 27
Required Step
Optional Define Remit-To Addresses
Performed for
Define remit-to addresses for each installation. For each operating unit, associate each remit-to address with a state and country. to inform your customers where to send payments. Associate each remit-to address with one or more state, country, and postal code combinations. For example, if you want your customers in California and Nevada to send their payments to a specific address, enter the remit-to address and associate the states CA and NV with this address. Remit-to addresses are assigned based on the bill-to address on the transaction. It is a good idea to set up a default remit-to address, even if you have other remit-to addresses defined, because Receivables can use this address if the bill-to location on the transaction is not covered by any other remit-to address assignment. This may happen, for example, when you create transactions for a new customer.
42
Optional
each installation
43 44
Optional Optional
45
Optional
each installation
46
Optional
each installation
to enable customers to apply receipts to related customer transactions. To restrict receipt application to only related customers, define relationships between your customers and set the system option Allow Payment of Unrelated Invoices to No. Receivables lets you define one way and reciprocal relationships between your customers. If you want to provide one party with access to another party's accounts and transactions, then define party paying relationships. You use Oracle Trading Community Architecture Relationship Manager to define party paying relationships. To import receipts from a bank file using AutoLockbox If to use AutoLockbox to import receipts, Transmission formats specify how data in lockbox bank file is organized so it can be successfully imported into the Receivables interface tables. to define and update groups of units of measure with similar characteristics (for example, Volume or Length). A class consists of a base unit of measure and other assigned units of measure. Use this window to define the base unit of measure for each class. to define one or more units of measure. Each item that you define in Receivables must have a primary unit of measure that you will have defined in this window. to enter predefined lines for debit memos, on-account credits, and invoices. When you define standard memo lines, you can specify whether a line is for charges, freight, line, or tax. Receivables also lets you define one
47
Optional
Page 15 of 27
Required Step
Performed for
chargeback and one debit memo reversal line.
48
Optional
49 50
Required Optional
51
Optional
Define categories and sequences for each installation. Assign sequences to categories for each ledger.
to apply receipts to transactions in different currencies, set up Receivables for cross currency receipts. To do this, define a cross currency rounding account in the System Options window, and define a suspense account in Oracle General Ledger. Oracle Receivables uses Oracle E-Business Tax as its tax engine. Oracle E-Business Tax provides a tax vendor extension that integrates external tax calculation programs with Oracle Applications. This extension performs complex tax calculations to create and store tax data. You can implement either the Taxware Sales/Use Tax System or Vertex Q-Series with Oracle Receivables. By assigning unique numbers to documents, you can account for each transaction you enter and the document that accompanies it.
52
Optional
53
Optional
to print a single bill that includes all of a customer's transactions for the billing period and any balance carried forward from the previous billing period. This lets you send one consolidated bill to a customer, instead of a separate invoice for each transaction. calculate late charges against past due debit items for each customer, account, or site.
Page 16 of 27
AR Profile Options
# 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 AR Profile Options
Tax: Allow Ad Hoc Tax Changes Tax: Allow Manual Tax Lines Tax: Allow Override of Customer Exemptions Tax: Allow Override of Tax Code Tax: Debug File Directory Tax: Debug Flag Tax: Inventory Item for Freight (This profile option affects Receivables but is owned by another application) Tax: Invoice Freight as Revenue (This profile option affects Receivables but is owned by another application) Tax: Lease Management Installed Tax Taxware: Service Indicator Tax Taxware: Tax Selection Tax Taxware: Tax Type Tax Taxware: Use Nexpro Tax: Use Tax PL/SQL Vendor Tax: Use Tax Vendor Tax Vertex: Case Sensitive Tax Vertex: Secondary Taxes AR: Allow Overapplication in Lockbox AR: Allow Update of Existing Sales Credits AR: Always Default Transaction Balance for Applications AR: Application GL Date Default Optional Later of Receipt GL Date and Invoice GL Date AR: AutoInvoice Gather Statistics AR: Bank Directory Source Access AR: Bank Directory URL AR: Bills Receivable Batch Source AR: BPA Details Access Enabled AR: BPA Print Output Directory AR: Cash - Allow Actions AR: Change Customer on Transaction AR: Commit Between Validations in Lockbox AR: Create Bank Charges AR: Customer Text Last Successful Run AR: Customers - Enter Alternate Fields AR: Debug Level for Lockbox / PostBatch
Value
No default No No Account No No No Minimal No Yes No default No YTD No Yes 2500 5 5 No 1000 PTD No No No No No No default No User Entered Rate Overrides No System Defined No default No default No
Page 17 of 27
Value
0 No Yes 3 5000 5000 PTD No No No Concatenated Segment Entry No No Go Up Mgt Chain No No Yes Optional
Page 18 of 27
FA Setup Steps
FA # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 Step
Required Optional Optional Optional Optional Optional Optional Required with defaults Required with defaults Optional Optional Required Required Required Required Required Optional Required with defaults Required Required Optional Required Required with defaults Optional Optional Required Optional Required Optional Optional Optional Optional Optional Define Ledgers Define Unit of Measure Classes Define Units of Measure Define Employees Define Descriptive Flexfields Set Up Oracle Subledger Accounting Decide How to Use the Account Generator Define Additional Journal Entry Sources Define Additional Journal Entry Categories Define Supplier and Employee Numbering Schemes Define Suppliers Define Asset Key Flexfield Define Asset Category Flexfield Define Location Flexfield Define System Controls Define Locations Define Asset Keys Define Standard Asset Descriptions and Other QuickCode Values Define Fiscal Years Define Calendars Set Up Security by Book Define Book Controls Define Additional Depreciation Methods and Rates Define Depreciation Ceilings Define Investment Tax Credits Define Prorate and Retirement Conventions Define Price Indexes Define Asset Categories Define Distribution Sets Enter Leases Define Warranties Set Profile Options Define Asset Insurance
Performed for
once per installation. once for each Inventory organization. once for each Inventory organization. once for each business group only once per installation once for each ledger. once for each (entity) i.e. organization operating unit, business group, or legal entity. once for each operating unit. once for each operating unit. once for each operating unit. once for each operating unit. only once per installation only once per installation only once per installation once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger. once per ledger.
Page 19 of 27
FA Profile Options
# 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 24 25 26 27 28 28 28 FA Profile Options
Account Generation FA: Custom Generate CCID FA: Generate Depreciation Expense Accounts FA: Generate Asset Level Account FA: Generate Book Level Accounts FA: Generate Category Level Accounts FA: Use Workflow Account Generation Archive and Purge Category FA: Archive Table Sizing Factor Concurrent Processing Category FA: Mass Copy All Cost Adjustments FA: Number of Parallel Requests Debug Category FA: Print Debug Depreciation Category FA: Annual Rounding FA: Deprn Single FA: Enable Depreciation Override FA: Use Threshold Desktop Integration Category FADI: Create Asset Privileges FADI: Physical Inventory Privileges Payables Integration Category FA: Default DPIS to Invoice Date Performance Category FA: Batch Size FA: Cache Sizing Factor FA: Maximum Projection Extent FA: Print Timing Diagnostics Security Category FA: Security Profile Setup Category FA: Allow Swiss Special Assets FA: Tax Asset Type Category Segment for Japanese Depreciable Assets Tax Report
Value
No No default No default No default No default Yes 100 KB No 1 No Always No No default No default Entry, Upload, Submit Entry, Upload, Submit, Adjust No 200 25 No default No default No default No default No default
Page 20 of 27
Shared Setup Tasks for Funds Capture and Funds Disbursement Optional Set Up Payment Function Access Optional Set Up Function Security Setup Checklist for E-Business Suite Products required Set up internal bank accounts and related payment documents required Set up bill-to location and operating units conditionally required Set up external bank accounts required Set up a tax reporting entity conditionally required Define conversion rates Setup Checklist for Shared Oracle Payments Setup Tasks required Creating Oracle Payments Users optional Set Up System Security Options conditionally required Set Up or Updating Oracle XML Publisher Templates for Payment Formats or Reporting Formats. conditionally required Set Up Formats Set Up Validations optional conditionally required conditionally required conditionally required optional optional required Set Up Transmission Configurations Configuring Tunneling Set Up Payment Systems Configuring Oracle Payments Sample Servlet Set Up SSL Security for Payment System Servlet Communication Configuring the XML Framework
1 2
1 2 3 4 5 6 7 8 9 10 11
Application Object Library Payments Oracle XML Publisher Payments Payments Payments Payments Payments Payments Payments Payments
12 13 14 15 16 17 18
Setup Tasks for Funds Disbursement required Set up third party payees and suppliers and supplier sites. conditionally required Set up VAT reporting. conditionally required Set Up Funds Disbursement Payment Methods optional Set Up Payment Method Defaulting Rules optional Set Up Bank Instruction Codes optional Set Up Delivery Channel Codes optional Set Up Payment Reason Codes required Set Up Payment Process Profiles required Set Up Disbursement System Options
iSupplier Oracle Financials Payments Payments Payments Payments Payments Payments Payments
Page 21 of 27
Step
Performed for
19 20 21 22 23 24
Configuring the ECApp Servlet Set Up Funds Capture Payment Methods Set Up Funds Capture Process Profiles Set Up First Party Payees Set Up Credit Card Brands Loading Risky Instruments
Value
No Default No default No default No Default No default No default No default No default No default No default No default No default No USD
Update
Site Level Site Level Site Level Site Level Site Level Site Level Site Level Site Level Site Level Site Level Site Level Site Level Site Level All levels
Page 22 of 27
Oracle EBS R12 Financials Configurations Summary E-Tax # 35 Optional 36 Optional 37 Optional 38 Optional 39 Optional 40 Optional 41 Optional 42 Optional 43 Optional 44 Optional 45 Optional 46 Optional 47 Optional 48 Optional 49 Optional 50 Optional 51 Optional 52 Optional 53 Optional 54 Optional 55 Optional 56 Optional
Step
Create Product Classification Create Product Intended Use Classification Create Party Classification Create Transaction Classification Create Transaction Business Categories Create Document Classification Create User Defined Transaction Classification Create Country Defaults Create Exceptions Create Tax Rules Complete First Party Legal Entity Party Tax Profile Create First Party Legal Establishment Party Tax Profiles Create Party Tax Profiles for Third Parties Find Customers Find Suppliers Create Configuration Owner Tax Options Create Application Tax Options Provider Service Details Create Provider Service Mapping Create Provider Service Extensions Simulate Transactions Make Tax Available on Transactions
Page 24 of 27
Value
Yes Yes Yes Yes No default Freight Charge No Yes Non-S ervice Jurisdiction and Tax No Yes
Page 25 of 27
No No
Must be set to No and should NEVER be changed. Otherwise, the link between SLA and GL will be broken, so GL no longer knows which journals came from SLA. This may cause problems with inquiry and drilldown on these journals in the future. This option is set to Yes only in cases where GL is on a separate instance than SLA.
SLA: Display Timestamp on Trace SLA: Enable Data Access Set Security in Subledger SLA: Enable Diagnostics SLA: Enable PL/SQL Profiler SLA: Enable SQL Trace SLA: Enable SRS Log/Output SLA: Enable Subledger Transaction Security in GL
No No No No No Yes No
Controls whether the drilldown to SLA will enforce the transaction security of the application owning the Transaction. For example, if one drills down to Payables, he will only be able to see Journals for transactions belonging to operating units to which he has access (based on your MO: Security Profile.) Thus drilldown can be restricted to the Operating Units to which the responsibility has access. In case the GL responsibility does not have access to a particular Operating Unit, the Drilldown will not show any data.
SLA: Enable Trace SLA: Flush Trace File SLA: INITIAL DATE FOR HISTORICAL UPGRADE SLA: Oracle Forms Trace Mode SLA: SRS Trace Mode SLA: Setup User Mode (INTERNAL use only, do not ship) SLA: Trace File Override Directory SLA: Trace File Override Filename SLA: Trace Level SLA: Trace Timeout
No No File Tracer
100 600
Page 26 of 27
Page 27 of 27