Cognos BI and SAP ERP Fundamentals

In SAP vendor/customer master data, multiple account groups can share the same number range, but each account group can only be assigned one number range. Each account group must use either internal or external numbering, not both simultaneously. Option B is false because number ranges can be reused across groups. Option E is false because an account group cannot have dual numbering systems.

A single customer master can have different reconciliation accounts and payment terms across company codes because each company code maintains its own company code segment data. However, the customer code (number) remains the same across company codes. Option A is incorrect because customer codes are shared, not different. Option D is incorrect because the COA segment is not mandatory for customer master creation.

Cognos 8 uses web-based architecture with centralized server components. Users access it through browsers without installing client software, making it zero-footprint on client machines.

Event Studio (formerly Event Management Service) is designed for event lifecycle management - creating, managing, and monitoring event-based tasks and alerts. Report Studio is for reports, Query Studio for ad-hoc queries, Metric Studio for scorecards.

Cognos Connection is the web portal providing unified access to all Cognos studios. It's the single entry point for accessing Report Studio, Query Studio, Analysis Studio, Event Studio, and other Cognos components.

In Cognos 8 three-tier architecture, the Applications tier contains the Cognos BI server components including dispatchers (handle requests) and Content Manager (manages content store). Web tier is for web servers, Data tier for databases.

The Content Store is a database storing Cognos metadata - report specs, packages, models, security settings, data source connections, and portal configuration. It does NOT store actual business data from source databases.

Framework Manager is a Windows-based client application for creating and managing metadata models (packages). It must be installed locally, unlike web-based tools like Cognos Connection.

Prompts in Cognos can be used in all listed contexts - parameter maps (for dynamic substitution), session parameters (like user info), stored procedure arguments (for parameterized queries), and expressions including filters, calculations, and data model relationships.

In Report Studio and similar BI tools, a security filter applied to a specific query subject controls data access at the query level, which is referred to as data security. Object security would apply to entire objects like reports or models, while package security applies to entire packages. Data security is the most granular level.

Dimensions organize information from the LOWEST level of granularity (most detailed, like individual dates or products) to the HIGHEST level (most aggregated, like years or product categories). The statement claims the reverse order, making it false.

The Explorer Bar in Report Studio contains the Page Explorer (for navigating report pages), Query Explorer (for working with queries), and Condition Explorer (for managing conditional variables and formatting). Work Area Explorer is not a standard component.

Report Studio can create list reports, crosstabs (maps), charts, and repeater reports among others. 'View' is not a standard report type in Report Studio - it's more commonly a database concept or a different tool's feature.

In dimensional reporting, a slicer is a dimensional filter that excludes specific dimension members from measure rollups and calculations. Unlike regular filters that just hide data, slicers affect the actual aggregation behavior. A 'dicer' is not a standard term in this context.

The Insertable Objects pane in Report Studio contains the Model tab (showing available model items), Query Item tab (specific query items), and Toolbox tab (built-in functions and operators). Properties is typically a separate pane, not a tab within Insertable Objects.

When measure dimensions and regular dimensions are organized into clusters in Framework Manager, this grouping is referred to as a Star Schema Group. This follows the dimensional modeling pattern where fact tables (measures) are surrounded by dimension tables in a star pattern. Snowflake is a different, more normalized pattern.

In SAP BW and data warehousing contexts, source systems include SAP R/3 systems (source transaction data), SAP BW itself (as a source to other BW systems or downstream systems), flat files (for batch data loading), and external systems (via various interfaces). All listed options are valid source system types, making 'All the above' the correct answer.

All three options (SAP, BANN, JD Edwards) are major ERP (Enterprise Resource Planning) systems used by organizations to manage business processes. The question asks for types of ERP systems, and since all listed options are valid ERP solutions, the correct answer is All the above.

In SAP ABAP, sequential files processed on the application server are indeed referred to as datasets. This terminology is consistent with SAP's file handling conventions where datasets represent physical files used for sequential input/output operations in ABAP programs.