During your implementation, you set a value for each Receivables user profile option to specify how Receivables controls access to and processes data. Receivables lets you govern the behavior of many of the windows that use profile options.
Profile options can be set at the following levels:
Site: This is the lowest profile level. Site level profile option values affect the way all applications run at a given site.
Application: These profile option values affect the way a given application runs.
Responsibility: These profile option values affect the way applications run for all users of a given responsibility.
User: These profile option values affect the way applications run for a specific application user. The values you enter for options at the User level supersede the values that your system administrator has entered for you for these options.
Each of these user profile options affect the behavior of Receivables in different contexts. In Receivables, operations that profile options can affect include receipt application, the entry of adjustments, the creation and remittance of automatic receipts and taxes, and posting to your general ledger.
You may also have additional user profile options on your system that are specific to applications other than Receivables.
To change profile options at the Site, Application, or Responsibility level, choose the System Administrator responsibility, then navigate to the Personal Profile Values window. Query the Profile Name field to display the profile options with their current settings, make your changes, then save your work.
You can change profile options at the user level in the Personal Profile Values window. To do this, navigate to the Personal Profile Values window, query the profile option to change, enter a new User Value, then save your work.
Generally, your system administrator sets and updates profile values at each level.
Important: For any changes that you make to profile options to take effect, you must either exit, and then reenter Receivables, or switch responsibilities.
Overview of Setting User Profiles, Oracle Applications System Administrator's Guide - Maintenance
This section lists each Receivables profile option. For each user profile option, we give a brief overview of how Receivables uses that profile, and tell you at which level you can set or update it.
The following profile options affect the operation of Receivables, but are not "owned" by Receivables:
MO: Operating Unit: Assign this profile option to an application responsibility to provide a user with this responsibility access to one operating unit.
MO: Security Profile: Assign this profile option to an application responsibility to provide a user with this responsibility access to multiple operating units.
MO: Default Operating Unit: Use this profile option to specify a default operating unit from the list of operating units assigned to your application responsibility through the MO: Operating Unit or MO: Security Profile profile option.
Note: If the MO: Operating Unit is set or you are assigned only one operating unit in the MO: Security Profile profile option, then the single operating unit becomes your default operating unit.
For more information, see: Oracle Applications Multiple Organizations Implementation Guide.
Indicate Attachments: This profile option lets you turn off the indication of attachments when querying records in Receivables. Setting this profile option to No can increase system performance. For more information, see the Oracle Applications System Administrator's Guide - Maintenance.
This table indicates whether you can view or update profile options and at which levels your system administrator can update these profile options: the user, responsibility, application, or site levels.
A Required profile option requires you to provide a value. An Optional profile option already provides a default value which you can change.
The key for this table is:
Update - You can update the profile option
View Only - You can view the profile option, but cannot change it
No Access - You cannot view or change the profile option value
|Profile Option||Value||Default||User Access||System Admin Access: User||System Admin Access: Resp.||System Admin Access: App.||System Admin Access: Site|
|Tax: Allow Ad Hoc Tax Changes||Optional||No default||View Only||Update||Update||Update||Update|
|Tax: Allow Manual Tax Lines||Optional||No default||View Only||Update||Update||Update||Update|
|Tax: Allow Override of Customer Exemptions||Optional||No default||View Only||Update||Update||Update||Update|
|Tax: Allow Override of Tax Code||Optional||No default||View Only||Update||Update||Update||Update|
|Tax: Inventory Item for Freight (This profile option affects Receivables but is owned by another application)||Required||No default||View Only||Update||Update||Update||Update|
|Tax: Invoice Freight as Revenue (This profile option affects Receivables but is owned by another application)||Optional||No default||View Only||Update||Update||Update||Update|
|Tax: Lease Management Installed||Optional||No default||Update||Update||Update||Update||Update|
|Tax Taxware: Service Indicator||Optional||No default||View Only||View Only||Update||Update||Update|
|Tax Taxware: Tax Selection||Optional||No default||View Only||View Only||Update||Update||Update|
|Tax Taxware: Tax Type||Optional||No default||View Only||View Only||Update||Update||Update|
|Tax Taxware: Use Nexpro||Optional||No default||View Only||View Only||Update||Update||Update|
|Tax: Use Tax PL/SQL Vendor||Optional||No default||View Only||Update||Update||Update||Update|
|Tax: Use Tax Vendor||Optional||No default||View Only||View Only||Update||Update||Update|
|Tax Vertex: Case Sensitive||Optional||No default||View Only||View Only||No Access||No Access||Update|
|Tax Vertex: Secondary Taxes||Optional||No default||View Only||View Only||Update||Update||Update|
|AR: Allow Overapplication in Lockbox||Required||No||View Only||View Only||Update||Update||Update|
|AR: Allow Update of Existing Sales Credits||Required||Yes||Update||Update||Update||Update||Update|
|AR: Always Default Transaction Balance for Applications||Optional||No default||Update||Update||Update||Update||Update|
|AR: Application GL Date Default||Optional||Later of Receipt GL Date and Invoice GL Date||View Only||No Access||Update||Update||Update|
|AR: AutoInvoice Gather Statistics||Optional||No default||Update||Update||Update||Update||Update|
|AR: Bank Directory Source||Optional||No default||No Access||Update||Update||Update||Update|
|AR: Bank Directory URL||Optional||No default||No Access||No Access||No Access||No Access||Update|
|AR: Bills Receivable Batch Source||Optional||No default||Update||Update||No Access||No Access||No Access|
|AR: BPA Details Access Enabled||Optional||No||View Only||Update||Update||Update||Update|
|AR: BPA Print Output Directory||Required||No default||View Only||Update||Update||Update||Update|
|AR: Cash - Allow Actions||Required||Yes||View Only||Update||Update||Update||Update|
|AR: Change Customer on Transaction||Optional||Yes||View Only||Update||Update||Update||Update|
|AR: Commit Between Validations in Lockbox||Optional||No default||Update||No Access||Update||Update||Update|
|AR: Create Bank Charges||Optional||Yes||Update||View Only||Update||Update||Update|
|AR: Customer Text Last Successful Run||Optional||No default||No Access||No Access||No Access||No Access||Visible|
|AR: Customers - Enter Alternate Fields||Optional||Yes||View Only||No Access||Update||Update||Update|
|AR: Debug Level for Lockbox / PostBatch||Required||3||Update||Update||Update||Update||Update|
|AR: Default Exchange Rate Type||Required||No default||View Only||View Only||Update||Update||Update|
|AR: Default Open Receipts for Application||Optional||No||Update||Update||Update||Update||Update|
|AR: Deposit Offset Account Source||Optional||Auto-Accounting||No Access||No Access||Update||Update||Update|
|AR: Disable Receivable Activity Balancing Segment Substitution||Optional||No||No Access||Update||Update||Update||Update|
|AR: Enable SQL Trace||Optional||No default||Update||Update||No Access||No Access||No Access|
|AR: Enable Debug Message Output||Optional||No default||Update||Update||No Access||No Access||No Access|
|AR: Factor/Endorse Bills Receivable without Recourse||Optional||No||View Only||Update||Update||Update||Update|
|AR: GL Transfer Balance Test||Optional||Yes||View Only||Update||Update||Update||Update|
|AR: Include Receipts at Risk in Customer Balance||Required||No default||Update||Update||Update||Update||Update|
|AR: Invoices with Unconfirmed Receipts||Optional||No default||View Only||Update||Update||Update||Update|
|AR: Item Flexfield Mode||Optional||Concatenated Segment Entry||Update||Update||Update||Update||Update|
|AR: Lockbox and QuickCash Gather Statistics||Optional||Yes||Update||Update||Update||Update||Update|
|AR: Maximum Lines Per AutoInvoice Worker||Optional||No default||View Only||No Access||Update||Update||Update|
|AR: Override Adjustment Activity Account Option||Optional||Yes||View Only||Update||Update||Update||Update|
|AR: Receipt Batch Source||Optional||No default||Update||Update||Update||Update||Update|
|AR: Require Adjustment Reason||Optional||No||Update||Update||Update||Update||Update|
|AR: Require Receipt Method on Remittance Batch||Optional||No||View Only||View Only||Update||Update||Update|
|AR: Sort Customer Reports by Alternate Fields||Required||No default||View Only||No Access||Update||Update||Update|
|AR: Transaction Batch Source||Optional||No default||Update||Update||Update||Update||Update|
|AR: Update Due Date||Required||Yes||View Only||Update||Update||Update||Update|
|AR: Use Invoice Accounting For Credit Memos||Optional||Yes||View Only||Update||Update||Update||Update|
|AR: Use Oracle Approvals Management in Credit Memo Workflow||Optional||No||View Only||No Access||No Access||No Access||Update|
|AR: Use Parallel Hints||Optional||No||Update||Update||Update||Update||Update|
|AR: Use Statement, Dunning, and Late Charges Site Profiles||Optional||No||No Access||No Access||Update||Update||Update|
|HZ: Change Party Name||Optional||Yes||View Only||Update||Update||Update||Update|
|HZ: Internal Party||Optional||No default||Update||Update||Update||Update||Update|
|HZ: Name/Address Backwards Compatibility||Optional||Yes||Update||Update||Update||Update||Update|
|HZ: Show Only Active Addresses||Optional||No default||Update||Update||Update||Update||Update|
|Oracle Exchange Database Link||Optional||No default||No Access||View Only||View Only||View Only||Update|
|Default Country (This profile option affects Receivables but is owned by another application)||Required||No default||Update||Update||Update||Update||Update|
|Enable Transaction Code||Optional||No||No Access||Update||Update||Update||Update|
|Journals: Display Inverse Rate (This profile option affects Receivables but is owned by another application)||Optional||No||Update||Update||Update||Update||Update|
|OM: Item Flexfield (This profile option affects Receivables but is owned by another application)||Required||No default||View Only||No Access||No Access||No Access||Update|
|Sequential Numbering (This profile option affects Receivables but is owned by another application)||Optional||Not Used||Update||No Access||Update||Update||Update|
This profile option lets you choose whether to allow modifications of rates and amounts assigned to tax codes in the Transactions window in Receivables by setting the profile option to Yes. You must have defined tax codes in the Tax Codes and Rates window and set Ad Hoc to Yes. A null value is equivalent to No.
This profile option determines whether to allow entering of unapproved exemptions in Receivables by setting the profile option to No. This profile option controls access to the Tax Handling field in the Lines window when entering transactions. You use the Tax Handling field to indicate how Receivables handles exemptions for each transaction line.
You can also use this profile option to control whether you allow sales tax systems to automatically create unapproved sales tax exemptions during invoice entry. A null value is equivalent to No.
This profile option lets you choose whether to allow overriding of a system-derived tax code during order or invoice entry by setting the profile option to Yes. If you override a system derived tax code, Receivables will use the rate and amount assigned to the new tax code to determine the tax for the transaction.
Use this profile if you have set Tax: Invoice Freight as Revenue to Yes (so that freight can be taxed) and you need to control the rate of tax applied to freight. You can do this by defining an inventory item of User Type Freight and setting this option to your new inventory item. When Order Management identifies this inventory item, it uses the Tax Codes (or Groups) assigned to it or Item Exceptions to control the applicable tax rates and accounting for the freight service. On the printed invoice, the description of the freight line will be derived from the inventory item that you defined, rather than the default description 'Freight'.
If you are using Oracle Order Management, this profile option determines how Order Management imports freight amounts to Receivables when you run the Receivables Interface program. Use this profile if you require freight amounts to be taxed by setting the profile option to Yes. If this option is Yes, Order Management will create a line item of type Line on the invoice for the freight amount identified on the Ship Confirm window, so that it can be taxed. When Receivables prints the invoice, this amount will be printed as the last invoice line with the description of Freight.
If the Taxware Sales/Use Tax System is your tax vendor, set this profile option to define your service indicator. Taxware uses the service indicator to identify the taxability in jurisdictions where the taxability differs according to the service indicator. Choose Service, Rental, or Non-service. A null value is equivalent to Non-service. See: Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System Implementation Guide.
If the Taxware Sales/Use Tax System is your tax vendor, define this profile option to control whether jurisdiction-level jurisdiction codes should be used when calculating taxes. Choose Tax Only to calculate tax based on the ship-to address. Choose Jurisdiction and Tax to calculate tax based on the ship-to, ship-from, point of order acceptance, and point of order origin information. A null value is equivalent to Jurisdiction and Tax. See: Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System Implementation Guide.
If the Taxware Sales/Use Tax System is your tax vendor, define this profile option to identify the default tax type for transactions that are passed to Taxware from Receivables. Taxware uses the tax type to determine how to calculate tax in jurisdictions in which tax calculations are different depending on the tax type. Choose Sales, Service, or Use. A null value is equivalent to Sales. See: Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System Implementation Guide.
This profile option determines whether you use Nexpro, a function of the Taxware Sales/Use Tax System. Choose Yes if Taxware is your tax vendor. A null value is equivalent to No. See: Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System Implementation Guide.
This profile option determines the tax vendor to use in a multiple organization environment when multiple tax vendors are installed. Choose either Taxware or Vertex. The default value is Null. See: Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System Implementation Guide.
This profile option lets your system administrator control which users can call an installed third party application for tax calculations. This profile option is required in multiple organization installations in which one set of executables is shared across many different tax compliance requirements. Choose Yes to indicate that a user can call a third party application to calculate tax. A null value for this profile option is equivalent to No.
If Vertex Quantum is your tax vendor, this profile option determines whether tax calculation queries to the Vertex Tax Decision Maker (TDM) are case sensitive. If you do not use Vertex Quantum, Receivables ignores this profile option. See: Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System Implementation Guide.
If Vertex Quantum is your tax vendor, this profile option indicates whether secondary taxes should be returned to Oracle Receivables by setting it to Use Secondary Taxes. A null value is equivalent to Use Secondary Taxes. If you do not use Vertex Quantum, Receivables ignores this profile option. See: Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System Implementation Guide.
This profile option controls how AutoLockbox handles receipts when the payment amount is greater than the balance due for a transaction. When a payment exceeds the balance due, AutoLockbox closes the transaction and leaves a negative balance due for the item if both of the following are true:
AR: Allow Overapplication in Lockbox is set to Yes; and
the open debit item's transaction type has Allow Overapplication set to Yes
If either of these conditions are false, AutoLockbox applies only enough to close the transaction and leaves the remaining receipt amount unapplied.
This profile option determines the default amount applied value that displays in the Applications window, whether you enter applications directly or by using the Search and Apply feature. The default value includes discount amounts, where applicable.
If you set the profile option to Yes, then the default amount applied is the remaining transaction amount.
If you set the profile option to No, or if a null value exists, then the following defaulting rule is applied:
If the unapplied receipt amount is greater than or equal to the transaction, then the default amount applied is the remaining transaction amount.
If the unapplied receipt amount is less than the remaining transaction amount, then the default amount applied is the unapplied receipt amount.
If the unapplied receipt amount is negative, then the default amount applied is the remaining transaction amount (to prevent the negative unapplied amount from increasing).
Later of Receipt GL date and Invoice GL date: Choose this value to use either the receipt GL date or the invoice GL date, whichever is later, as the default GL date for your receipt applications. This is the default value.
Later of Receipt GL date, Invoice GL date, and Current date: Choose this value to use the receipt GL date, the invoice GL date, or the current date, whichever is later, as the default GL date for your receipt applications.
If the value for this profile option is set to Yes, or is null, AutoInvoice analyzes the interface tables and gathers statistics.
If the value is set to No, AutoInvoice does not analyze the interface tables.
This profile option is used by iReceivables for bank account transfer payments that make use of the Automated Clearing House (ACH) network. The profile option provides iReceivables with access to the E-Payment routing directory through the Federal Reserve Financial Services web site, a local file downloaded from this web site, or both. iReceivables uses the E-Payment routing directory to derive the name of the bank or financial institution from the routing number that a customer enters to pay an invoice using an ACH bank account transfer.
This profile option is used by iReceivables to identify the URL in Oracle iReceivables that will host the Federal Reserve Financial Services web site. This profile option is set when the AR: Bank Directory Source profile option is set to Web Services or Web Service First then Local.
This profile option determines the default bills receivable transaction batch source to use for bills receivable transactions. Enter a bills receivable batch source that you previously defined to default to the Bills Receivable window and the Bills Receivable Transaction Batches window.
This profile option determines the level of information internal users and customers can access online presented by Oracle Bill Presentment Architecture. If set to Yes, the user can access the details page of an online bill by clicking an active hyperlink in the Item Description column of the Lines and Tax table to view detail billing information from supplementary data sources. If set to No, no hyperlink is displayed and users cannot access a details page for billing detail.
This profile option identifies the output directory for invoice PDF files generated by the invoice batch print program submitted in Oracle Bill Presentment Architecture or Oracle Receivables. It also stores PDF files generated by the Print Preview feature of Interactive Preview when the user selects one or more invoices to print.
This profile option determines whether Receivables lets you create item level actions in the Applications window while you apply receipts. Valid item level actions include adjustments to your debit items or the creation of chargebacks for specific debit items.
If set to Yes, Receivables displays the Chargebacks or Adjustments window and lets you create chargebacks and adjustments when you choose either Chargebacks or Adjustments in the Applications window.
Note: You cannot update the customer bill-to or ship-to information if the transaction is a chargeback, has activity against it, or has been posted, even if this profile option is set to Yes.
This profile option determines whether the AutoLockbox program will commit (save) after validating each record in a Lockbox transmission. If you set this profile option to No, AutoLockbox will only commit after validating all of the records in the transmission.
Other operations that this profile can affect include the following:
This profile option stores the last successful run date of the customer text data creation and indexing process. You must run the customer text data creation and indexing process to acquire good search results in the Text tabbed region of the Find/Enter Customers window.
This profile option controls whether users can enter information in the Alternate Name field in the Customers and Customer Addresses windows. This field lets you enter a phonetic representation of a customer name. Alternate names are used primarily in Japan to enter and sort customer information using Kana characters.
Receivables also uses this information when you choose Customer Name Sort as a parameter when printing certain Receivables reports (for example, the Customer Listing - Detail or Summary report). Refer to the AR: Sort Customer Reports by Alternate Fields profile option in this section.
Enter one of the following values to indicate how extensive the debugging information saved to the log file will be:
0 - Save only the most severe messages and errors (default setting).
1 - Save messages that indicate entering and exiting various functions.
2 - Save any useful and informative messages.
3 - Save all other debug messages, including printing values of several important variables.
Corporate Exchange Rate - An exchange rate you define to standardize rates for your company. This rate is usually a standard market rate determined by senior financial management for use throughout the organization.
Spot Exchange Rate - An exchange rate you enter to perform a conversion based on the rate on a specific date.
User Specified Rate - An exchange rate you specify when entering a foreign currency transaction.
Note: If using the Automatic Receipts and Remittances Creation programs to pay foreign currency transactions, then set this profile option to a value other than User.
See: Scheduling the Automatic Receipts Creation program, Oracle Receivables User Guide and Scheduling the Automatic Remittances Creation Program, Oracle Receivables User Guide.
Use this profile option to indicate whether or not the following items should always be selected:
Include Open Receipts box in the Receipt Applications window (Tools menu)
Open Receipts box in the Search and Apply window
This profile option indicates which accounting source to use for a deposit's offset account. Receivables can use either AutoAccounting or the deposit's transaction type as the accounting source for the offset account.
This profile option lets you disable balancing segment substitution for receivable activities. This profile option does not affect the gain, loss, and rounding accounts that you define at the system options level.
If you set this profile option to Yes, then you must define a suspense account in the event that your activities and original transactions do not post to the same balancing segment value.
This profile option affects these activities:
Discounts (earned and unearned)
Activity applications, such as receipt write-off activity, short term debt, and claims investigation
Use this profile option to activate SQL Trace, a program that creates a log file of each SQL procedure performed while executing Oracle Receivables functions. If this profile option is enabled and a SQL-related error occurs, Oracle Applications developers and your system administrator can use the log file the program creates to identify the cause.
If set to Yes, show bind variable name the SQL Trace is enabled and only the names of bind variable in each SQL statement is displayed.
If set to Yes, show bind variable value the SQL Trace is enabled and the values of bind variable in each SQL statement is displayed. This option may be more useful as the program shows the actual value used during statement execution, rather than just the bind variable name.
If set to No, SQL Trace is disabled.
Accept the default setting of No for optimum performance during normal day-to-day processing.
Use this profile option to help resolve errors that can occur when generating iReceivables pages, such as web pages that appear with missing fields or data that displays incorrectly. This profile option activates a debugging program that inserts comments into your HTML source files to help your system administrator determine the cause of any errors.
This profile option determines whether you can create factored remittances or endorsements without recourse. The profile option controls this by allowing users to uncheck the With Recourse box in the Remittances window and the Transaction Batches window.
Available values are:
Yes: Receivables will reject unbalanced debits and credits before posting to the general ledger. These rejected unbalanced debits and credits will be listed in the Unposted Items Report which runs automatically during the posting program.
No: Receivables will not reject unbalanced debits and credits before posting to general ledger.
This profile option controls whether Receivables displays items at risk and includes them when calculating customer account balances in the Account Details window. Set this option to No if you do not want to view items at risk in this window or include them when calculating the balance due.
Available values are:
Always Pop a Flexfield Window: The item flexfield always pops up as you navigate through the field.
Concatenated Segment Entry: The item flexfield never pops up as you navigate through the field. Instead, you can type the item flexfield information directly into the field.
No Window for a Single Segment Flexfield: The item flexfield will only pop if it has more than one segment enabled.
Important: The value you specify for this profile option at the user level takes precedence over the value that is set for this profile option by the system administrator at the site, application, responsibility, or user level.
This profile option lets you choose whether Lockbox or QuickCash analyzes the interface or interim tables or not.
This profile option lets you choose whether you can override the default adjustment account when entering or updating manual adjustments and when updating automatic adjustments. These changes must be made before posting to the general ledger.
Note: Overriding the adjustment account pertains only to adjustments whose receivable activity's GL account source is Activity. If the GL account source is not Activity, then the default adjustment account cannot be changed, regardless of this profile option setting.
Only Receipt sources with a Receipt Source Type of Manual will be displayed in the list of values.
Use this profile option to control whether a reason is required when entering manual adjustments. If you set this option to Yes, then Receivables requires a reason whenever a manual adjustment is made.
This profile option controls whether Receivables will sort information using the value of the Alternate Name field in the Customers window when you run certain reports. To use this option, the AR: Customers - Enter Alternate Fields profile option must also be set to Yes.
Reports that can use this option include: the Customer Profiles Report, Receipt History Report, Applied Receipts Register, Unapplied and Unresolved Receipts Register, Automatic Receipts Awaiting Confirmation, Print Statements, Transaction Register, and the Customer Listing Detail and Summary reports.
This profile option determines the default invoice source that will appear in the Batch field of the Transaction and Credit Memo windows. Receivables only displays batch sources with a Transaction Source Type of Manual in the list of values for this option.
The value you specify for this profile option at the user level in this window takes precedence over the value set for this profile option by the system administrator at the site, application, responsibility, or user level.
Available values are:
Yes: Receivables lets you update the due date of a debit item to any date that is greater than the transaction date of this item. If you change the due date of your debit item, Receivables does not update the terms of this item.
No: Receivables prevents you from updating the due dates of debit items.
Use this profile option to select whether to use parallel hints while running the remittance program.
If set to Yes: The Generate Late Charges program uses the late charge policy specified on the account site with a Late Charges business purpose.
If set to No: The Generate Late Charges program uses the late charge policy specified on the billing site.
This profile option lets you enter the name of the database link between Oracle Exchange and Receivables when they are on two separate database instances. Set this profile option in Receivables after you create the database link to Exchange. You must set this profile option if you want to integrate your Exchange billing data with Receivables.
Please refer to the Oracle Exchange and Oracle Sourcing System Operator Implementation Guide, Release 6.2.2 and above, for complete information on the Oracle Exchange Billing integration with Receivables.
The following Oracle Trading Community Architecture profile options affect the operation of Oracle Receivables.
Set to Yes to preserve backwards compatibility by continuing to use AR address formatting.
Set to No to use TCA address formatting.
These profile options are for Customer Interface or Customer Merge:
HZ: Audit Customer Account Merge, Oracle Trading Community Architecture Administration Guide
HZ: Gather Table Stats, Oracle Trading Community Architecture Administration Guide
HZ: Location Updatable, Oracle Trading Community Architecture Administration Guide
HZ: Number of Workers Used by Customer Interface, Oracle Trading Community Architecture Administration Guide
Set these profile options to enable the Dun & Bradstreet integration with Receivables:
HZ: D&B Password
HZ: D&B User Name
HZ: D&B URL
HZ: Web Server Proxy Host Name
HZ: Web Server Proxy Password
HZ: Web Server Proxy Port
HZ: Web Server Proxy User Name
Profile Options and Profile Option Categories Overview, Oracle Trading Community Architecture Administration Guide
Because some Oracle Applications products have overlapping functions, the following Oracle Order Management profile options also affects the operation of Receivables, even if you have not installed Oracle Order Management.
If set to Yes, then the commitment balance includes reserved amounts.
If set to No, then Receivables assumes that no amounts were reserved in Order Management.
This profile option is visible and updatable at the site level.
Order Management Profile Options, Oracle Order Management Implementation Manual
Because some Oracle Applications products have overlapping functions, the following Oracle General Ledger profile option also affects the operation of Receivables, even if you have not installed Oracle General Ledger.
Use this profile option to determine how you enter and display conversion rates in the Oracle Order Management Enter Sales Orders and Returns windows, and the Oracle Receivables Receipts and Applications windows.
If set to Yes, you can enter and display conversion rates in the functional-to-foreign format; that is, the rate by which you multiply the functional amount to determine the foreign amount.
If set to No, you can enter and display conversion rates in the foreign-to-functional format; that is, the rate by which you multiply the foreign amount to determine the functional amount.
Note: In Receivables, this profile option also affects how the exchange rate appears in the Exchange Rate pop-up window when you choose a Rate Type of either Corporate or Spot. See: Defining Conversion Rate Types, Oracle General Ledger User's Guide.
Use this profile option to control whether a user can derive an exchange rate between an EMU and Non-EMU currency, based on the floating exchange rate between the euro and the Non-EMU currency. The user derives the exchange rate while entering both transactions and period rates.
Background: All NCUs have a fixed exchange rate with the euro. Floating rates exist only between NCU and Non-NCU. By setting this profile option to No, a user can enter a transaction involving an NCU and Non-NCU, choose User as the Rate Type in the Exchange Rates window, and enter the current exchange rate between the euro and the Non-NCU. Oracle General Ledger calculates a rate between the NCU and Non NCU for your transaction.
If set to Yes, you cannot derive an exchange rate between an NCU and Non-NCU.
If set to No, you can derive an exchange rate between an NCU and Non-NCU.
See: Foreign Currency Transactions, Oracle Receivables User Guide.
Use this profile option to enter transaction codes when entering journal entries. These transaction codes create additional budgetary or proprietary journal entries automatically during posting. You must also enable budgetary control for your ledger.
If set to Yes, you can enter a transaction code in windows that allow it in public sector installations of Oracle Payables, Oracle Receivables, Oracle Purchasing, and Oracle General Ledger.
If set to No, you are unable to create additional account pairs for your journal entries and you will not be able to use transaction codes in AutoLockbox.
This profile option is also used to enable transaction code functionality in AutoLockbox. AutoLockbox uses transaction codes to manage receivables accounting in a manner that is consistent with federal regulations. This feature is available only in public sector installations.
Setting General Ledger Profile Options, Oracle General Ledger Reference Guide
This section lists each profile option in Oracle Application Object Library, which are available to every Oracle Application. For each profile option, we give a brief overview of how Oracle Application Object Library uses the profile's setting.
Setting this profile option to Yes ensures that the Oracle Workflow data used to generate accounting flexfield code combinations using the Account Generator is purged after the Account Generator has completed.
This profile option should always be set to Yes unless you are debugging the Account Generator; in this case, we recommend that you set it to No temporarily at the user level. Running the Account Generator with this profile option set to No fills up the workflow tables and can slow system performance.
The concurrent managers run your requests according to the priority and start time specified for each.
Changing this value does not affect requests you have already submitted.
Setting the profile to Yes allows your concurrent requests and reports to be automatically placed on hold. To take requests off hold:
Navigate to the Concurrent Requests Summary window to select a request
Select the Request Control tabbed region
Uncheck the Hold check box
Setting the profile to User means only the user who submitted a request may:
view the completed report output for that request online;
view the diagnostic log file for that request online;
reprint a completed report, if the Concurrent: Save Output profile option is set to Yes.
If a user changes responsibilities, the reports and log files available for online review do not change, but are still determined by the user who submitted the concurrent requests.
Setting the profile option to Responsibility means access to reports and diagnostic log files is based on the responsibility the user is currently using. In this case, for any requests submitted from their current responsibility, any user may:
view the completed report output for a request online;
view the diagnostic log file for a request online;
reprint a completed report, if the Concurrent: Save Output profile option is set to Yes.
If a user changes responsibilities, the reports and log files available for online review change to match the user's current responsibility. Users can always see the output and log files from reports they personally submitted, but may also see reports and log files submitted by any user from the current responsibility.
Changing this value does not affect requests that you have already submitted.
Requests normally run according to start time on a “first-submitted, first-run" basis. Priority overrides request start time. A higher priority request starts before an earlier request.
Priorities range from 1 (highest) to 99 (lowest). The standard default value is 50.
You can set the date and time that your requests are available to start running:
If the start date and time is at or before the current date and time, requests are available to run immediately.
If you want to start a request in the future, for example, at 3:45 pm on June 12, 1998, you enter 12-JUN-98 15:45:00 as the profile option value.
You must include both a date and a time.
Changing this value does not affect requests that you have already submitted.
Users can see and update this profile option.
You can save your request outputs in a standard file format.
The default setting saves request outputs in standard file format.
Some concurrent requests do not generate an output file.
If your request output is saved, you can reprint a request. This is useful when requests complete with an Error status. For example, the request runs successfully, but a printer malfunctions.
Changing this value does not affect requests that you have already submitted.
Concurrent programs are incompatible if simultaneously accessing the same database tables incorrectly affects the values each program retrieves.
When concurrent programs are defined as incompatible with one another, they cannot run at the same time.
Setting it to Yes prevents your requests from running concurrently. Requests run sequentially in the order they are submitted.
Setting it to No means your requests can run concurrently when their concurrent programs are compatible.
Changing this value does not affect requests you have already submitted.
Normally, currency numbers are right-justified.
Each currency has its own precision value that is the number of digits displayed to the right of a decimal point. For U.S. dollars the precision default is 2, so an example display is 345.70.
Set Mixed Currency Precision to be equal to or greater than the maximum precision value of the currencies you are displaying. For example, if you are reporting on rows displaying U.S. dollars (precision = 2), Japanese yen (precision = 0), and Bahraini dinar (precision = 3), set Mixed Currency Precision = 3.
Angle brackets < > < xxx > Trailing hyphen - xxx -
If you run Oracle Applications in character mode, you can also use:
Parentheses ( ) ( xxx ) Square Brackets [ ] [ xxx ]
If you use the negative number formats of (xxx) or [xxx] in the GUI version of Oracle Applications, your negative numbers appear as <xxx>.
This is the only format available for positive numbers in the GUI version of Oracle Applications. If you use the character mode positive number formats of +xxx or xxx+, your positive numbers appear as xxx in the GUI windows.
If your currency amount does not fit within the field window, the thousands separator does not display.
This is the default source for the Country field for all address regions and is used by the Flexible Address Formats feature, the Flexible Bank Structures feature, and the Tax Registration Number and Taxpayer ID validation routines.
This profile can be set to any valid country listed in the Maintain Countries and Territories window and can be set to a different value for each user.
If the Default Country profile option is not defined, Receivables uses the value of the Default Country field in the System Options window as the default when you enter addresses.
The Flexible Bank Structure, Tax Registration Number, and Taxpayer ID validation routines are only performed for customers and banks in the home Country. If the current transaction does not have a Country value, the Default Country profile value is used to determine whether validation is required. If the Default Country profile is not defined, validation will not be performed.
Setting it to Yes means after entering a valid value in a segment you automatically move to the next segment.
Setting it to No means after entering a valid value in a segment you must press [Return] to go to the next segment.
If set to Not Enabled, Shorthand Entry is not available for any flexfields for this user, regardless of whether shorthand aliases are defined.
If set to New Entries Only, Shorthand Entry is available for entering new records in most foreign key windows. It is not available for combinations windows, updating existing records, or entering queries.
If set to Query and New Entry, Shorthand Entry is available for entering new records or for entering queries. It is not available for updating existing records.
If set to All Entries, Shorthand Entry is available for entering new records or updating old records. It is not available for entering queries.
If set to Always, Shorthand Entry is available for inserting, updating, or querying flexfields for which shorthand aliases are defined.
You can override this by selecting Flexfields: Show Full Value, which displays the full flexfield window with the cursor resting on the last segment.
You should set Maximum Page Length to a value appropriate for the paper size your printer uses.
The default value of 58 accommodates A4 type paper in landscape mode.
If your printer uses 8 1/2" by 11" size paper, you can set Maximum Page Length to 66.
Both menus have the same sequence of menu choices for each application function.
If set to Yes, you see a DecisionPoint window when a message explanation is available.
If set to No, you do not see a DecisionPoint window when a message explanation is available. You acknowledge messages by pressing any key.
Occasionally, an application may share another application's messages. The Message: Shared Application profile option lets you identify another application whose error messages can be referenced.
When you select AutoReduction: PowerSkip you can reduce a list of values to only those starting with a character(s) you specify, and your cursor automatically skips to the next differing character.
For example, if you had a long list of quarterly reports, two starting with the letter z (ZDept CF1 and ZDept CF2), when you type the letter z the list of values list is reduced to two values, and the cursor automatically skips to the last character. You then type 1 or 2 to select a report.
In the example above, with AutoReduction set to Normal, you must type all the characters if you want to use the AutoReduction feature to select one of the reports.
Use QuickPick: AutoReduction to help reduce list of value lists to a single choice. Then with QuickPick: AutoSelect you can, for example:
Specify the first character(s) of the choice you want
If only one value begins with the character(s), AutoSelect automatically selects the correct choice, closes the pop-up window, and enters the value.
To enter a QuickPick value when AutoSelect is set to No, you must press [Return] after selecting the value.
Sequential Numbering assigns numbers to documents that you create in Oracle financial products. For example, when you are in a window that creates invoices, each invoice document can be numbered sequentially.
Sequential numbering provides a method of checking whether documents have been posted or lost.
Not all windows within an application can be selected to support sequential numbering.
Sequential Numbering has the following profile option settings:
Always Used: You may not enter a document if no sequence exists for it.
Not Used: You may always enter a document.
Partially Used: You will be warned, but not prevented from entering a document, when no sequence exists.
This profile option is visible and updatable at the site, application, and responsibility levels, as described in the table below.
Note: The ability to set the Sequential Numbering profile option at the responsibility level was added for the Multiple Organizations Support feature. We recommend setting this option at either the site or application level unless you are implementing this feature.
The internal name for this profile option is UNIQUE: SEQ_NUMBERS.
If any concurrent requests failed since your last session.
How many times someone tried to log on to Oracle Applications with your user name, but an incorrect password.
When the default printer identified in your user profile is unregistered or not specified.
Profile Options in Oracle Application Object Library, Oracle Applications System Administrator's Guide - Maintenance