The two options that allow access to the BI Catalog for creating an Oracle Transactional Business Intelligence analysis are Reports and Analytics and Enterprise Performance Management Workspace. Reports and Analytics is a tool that allows users to access, create, edit, and share reports and analyses using data from various sources, including Oracle Transactional Business Intelligence. Users can access Reports and Analytics from various pages in Oracle Fusion Applications or from Oracle Fusion Cloud Service Console. Enterprise Performance Management Workspace is a tool that allows users to access, create, edit, and share reports and analyses using data from various sources, including Oracle Transactional Business Intelligence. Users can access Enterprise Performance Management Workspace from Oracle Fusion Cloud Service Console or from a web browser. Universal Content Management Workspace is not an option that allows access to the BI Catalog for creating an Oracle Transactional Business Intelligence analysis, as this is a tool that allows users to manage documents and other digital content in Oracle Fusion Applications. Business Process Management Workspace is not an option that allows access to the BI Catalog for creating an Oracle Transactional Business Intelligence analysis, as this is a tool that allows users to monitor and manage business processes in Oracle Fusion Applications. Scheduled Processes is not an option that allows access to the BI Catalog for creating an Oracle Transactional Business Intelligence analysis, as this is a tool that allows users to submit, monitor, and manage scheduled processes in Oracle Fusion Applications. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Use Oracle Transactional Business Intelligence (OTBI) 12

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

"A chart of accounts segment is a component of the account combination. Each segment has a value set attached to it to provide formatting and validation of the set of values used with that segment." The qualifiers are used to identify the segments for reporting and processing purposes2. In this case, the company segment should be the primary balancing segment, which is used to balance journal entries and create trial balances. The department segment should be the cost center segment, which is used to track costs by organizational units. The natural account segment should be the natural account segment, which is used to classify transactions by account type. The intercompany segment should be the intercompany segment, which is used to identify transactions between different legal entities or business units.

he two true statements regarding intercompany accounting for Financials Cloud, Projects, Inventory, and SCM are that Intercompany Balancing Rules are defined centrally and applied across Financials and Projects, and that each product has its own Intercompany Accounting feature that needs to be configured separately. Intercompany Balancing Rules are defined in General Ledger Cloud and are used to balance cross-ledger intercompany journals between Financials and Projects. Each product also has its own Intercompany Accounting feature that enables intercompany transactions within the product or across products. For example, Payables and Receivables have Intercompany Invoicing, Projects has Intercompany Billing and Capitalization, Inventory has Intercompany Transfer Pricing, and SCM has Intercompany Drop Shipments. Intercompany balancing rules in General Ledger do not need to be mapped with the intercompany configuration in each product, as they are independent of each other. In Financials Cloud, Intercompany Balancing Rules are not used to balance both cross-ledger allocation journals and single-ledger journals, as they are only used to balance cross-ledger journals. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Configure and Process Intercompany 12