According to Oracle documentation3, when you need to set up a calendar for the year Apr-XX to Mar-YY where YY is the following year, and you would like the periods to be named according to the year they fall in, you should choose Fiscal Year as the format. A Fiscal Year format enables you to define periods based on fiscal years that span two calendar years. Therefore, option A is correct. Option B is incorrect because a Calendar Year format defines periods based on calendar years that start on January 1st and end on December 31st. Option C is incorrect because a Period format defines periods based on any number of days or weeks. Option D is incorrect because a Year format defines periods based on calendar years that start on any month other than January and end on any month other than December.

To add a global branding logo and more predefined transactional attributes to the journal approval email notification, you should copy (or customize) and edit the layout template and the data model. The layout template is a file that defines the appearance and content of the notification, such as text, images, tables, or charts. The data model is a file that defines the data sources and queries that provide data for the notification, such as predefined transactional attributes. You can copy (or customize) and edit the layout template and the data model using Oracle Analytics Publisher reports. You do not need to copy (or customize) and edit the output type, as this is a setting that determines the format of the notification output, such as HTML or PDF. You do not need to copy (or customize) and edit the style template, as this is a file that defines the styles and formatting of the notification elements, such as fonts, colors, or margins. You do not need to copy (or customize) and edit the sub template, as this is a file that contains reusable content or logic that can be referenced by multiple layout templates. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Configure Workflow Approvals and Notifications 12

According to Oracle documentation1, a more automated approach to reconcile intercompany payables and receivables accounts is to run the Intercompany Reconciliation report, which shows pairs of intercompany receivables and payables accounts that are out of balance. This report is automatically generated when you run the Prepare Intercompany Reconciliation Information process. You can drill down on the report to view the balances by source and by journal lines. Therefore, option D is correct. Option A is incorrect because Oracle Hyperion Close Manager is not a tool for reconciling intercompany account balances. Option B is incorrect because you don’t need to manually reconcile your intercompany account balances in Financials Cloud. Option C is incorrect because the BI Publisher reports called Intercompany Transaction Summary and Account Details are not designed to reconcile intercompany balances. Option E is incorrect because creating a query using Oracle Transactional Business Intelligence (OTBI) is not a more automated approach to reconcile intercompany payables and receivables accounts.