The first one is server-responsibility profile hierarchy type. This hierarchy type can be used while defying Profile options and can be set at Site level, User level, or a new combination Server+Responsibility. This hierarchy type can be set in the profile option definition and cannot be changed later at the runtime. When using server+responsibility level both are considered as
a pair. Profile values can be set for combinations of a specific server with a specific responsibility, or for only a server or responsibility with a default for the other.

While processing a request the profile value is determined as follows:

1. User level value
2. Specific Server + Specific Responsibility value
3. Specific Responsibility + Default Server value
4. Specific Server + Default Responsibility value
5. Site level value

At top level the User level value overrides all other values. Once a profile has been defined to use the Server+Responsibility hierarchy type, values can be set at this level on the Define Profile Values page.

Second one is Profile categories that can be used to classify and group related profiles together. Once a Profile category is defined, it can be used to search for profiles by category when setting or viewing profiles values. Categories are also useful for finding related profiles, by looking for other profiles grouped in the same categories. Administrators can define as many categories as per the requirement , containing any profiles. Many profile categories are available as seeded data for the Administrators. Administrators are free to customize these categories to meet their requirements, or delete them entirely and replace with their own.

Next is the Value Set Definition form has added two additional features. One a new Usages button that shows everywhere a value set is used a Test button for Table Validated Value Sets that tests the value set for SQL errors . The Usage button opens another window which displays all descriptive flexfields, key flexfields, and concurrent programs referencing this value set. This information can be useful when a value set defintion has to be changed or deleted. 

Sometimes, when you create a payment in AP using foreign currency, you will get this message

APP-SQLAP-10020: Rate information is not available for this currency, date, and exchange rate type.
Enter rate information for this currency, date and exchange rate type in the Daily Rates window.

In Oracle R12, the payment can be committed even there is no rate available. However, this caused the accounting couldn’t be created which will be impacted to period close process.

So, you can do this step to handle missing exchange rate:

• Payments are created in the Payment Workbench with or without exchange rates based on the Payables options. If the exchange rate type is User, then the exchange rate must be given before the check can be created. If the exchange rate type is not User, and the required exchange rate entry check box has been checked, then the exchange rate must be available in the GL Daily Rates before the check can be created. However, if the exchange rate is not User and the required rates check box is not checked, a foreign currency check can be created without an exchange rate.

• Foreign currency payment created and maturity events should get accounted when the exchange rate fields are populated on the related checks and it should not be picked up by the accounting program when the exchange rate data is missing. In this case the AutoRate program should be run to populate the exchange rates.

• In the payment workbench form, maturity exchange date and maturity exchange rate fields should not be nullified when the user clicks on “Enter/Adjust Invoices” Button.

The conclusion is when you have missed the exchange rate in payment, just try the AutoRate in the concurrent program ([N] Other Concurrent, then click find and submit new request) to fill in the uncomplete payment information. This program will populate all payment which use foreign currency.

Oracle Reports

Fixed format reports delivered with the 11i release were built on this tool. This is the most used tool for reporting on Oracle E-Business Suite. Most customizations of available reports are built with this tool. Once customized the output of the report can be delivered in Excel, Word, Acrobat documents or text format.

Oracle Discoverer

is an intuitive tool for creating reports and performing on-line analysis. Discoverer uses the EUL (End User Layer), a metadata definition, which hides the complexity of the database from the end user and provides easy to use wizards for creating reports to suite individual needs. The flexibility of this tool allows the user to create  cross tab reports that perform like pivot tables in Excel.

Oracle XML Publisher 

is a new Oracle tool for reporting. It enables users to utilize a familiar desktop tool, like MS Word or MS Excel, to create and maintain their own report. At runtime, XML Publisher merges the custom templates with the concurrent request extracts data to generate output in PDF, HTML, RTF and EXCEL.

RXi Report: (Variable reports)

variable format reports delivered with the E-Business 11i. With this tool a user has the ability to print the same report with multiple layouts. The user can also choose which columns he requires on a particular report. This tool is most used on Oracle Financials Applications

FSG Reports: (Financial Statement Generator)

is a powerful report building tool for Oracle General Ledger. Some of benefits of using this tool are that a user can generate financial reports and schedule reports to run automatically. FSG Reports are available for the general ledger responsibility only and can be used to see key financial account balances.

Business Intelligence: System (BI)

is a set of tools to provide high level information for the managers (decision makers) to run their business such as the profitability of a particular business unit. The information this tool provides helps managers to take the right decision with the daily data that is uploaded on their systems.