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