Enterprise Technology Fundamentals: Lotus Notes, SAP Retail, and Data Warehousing

Order count is clearly a measure/fact (numeric aggregate being analyzed). Team size is a dimension - it's a descriptive attribute of the teams processing orders, used to group or filter the order counts. In dimensional modeling, measures are the numeric values we analyze (facts), while dimensions are the context descriptors (who, what, where, when) we analyze across.

This is false. While measures are typically numeric, not all numerical fields are measures. A measure must be aggregatable and meaningful for analysis - e.g., a numeric ID or phone number is numeric but is a dimension attribute, not a measure. Conversely, all measures in a properly designed business model are numeric (since they represent quantifiable metrics), but the reverse isn't true. The statement creates an incorrect bidirectional implication.

A degenerate dimension is a dimension attribute that has no dimensions of its own (like order number or invoice number) and is therefore stored directly in the fact table rather than in a separate dimension table. Options A and B correctly define this - it's an attribute that qualifies as dimension but is stored in the fact table for efficiency. Option C is incorrect because degenerate dimensions typically have no surrogate keys (they use natural keys). Option D is incorrect - values are generated outside the fact (from source transactions).

Total automation is never achievable in enterprise systems - SAP IS Retail improves and streamlines processes but requires human oversight and intervention. The other options (increased sales, improved flow, lower costs, flexibility) are realistic benefits.

A TCODE (transaction code) serves to call a SAP screen and acts as a direct shortcut to that screen, bypassing menu navigation. It does not directly enter order details, call menu paths, or serve no purpose.

MM41 is the standard SAP IS Retail transaction code for creating articles (master data for products). VA01 is for sales orders, VL31N for deliveries, and MM42 is for modifying existing articles.

ME21N is the standard SAP transaction code used to create a Purchase Order. VL01N is for outbound deliveries, ME29N is for releasing purchase orders, and ME9F is for message output.

VA01 is the standard SAP transaction code used to create a Sales Order. VA21 is for creating inquiries/quotations, while VL10 and VL02 relate to delivery processing.

SAP IS Retail has three article categories: Single (individual products), Generic (grouped similar products like different colors), and Structured (products with variants like size/color combinations). Unstructured is not a valid category.

2-step pricing in SAP IS Retail means setting a base price at the Distribution Center (DC) and then adding store-specific markup at retail locations. This differs from cost-plus or adding markup twice.

Pricing strategies in SAP IS Retail include competitor pricing (A), markdown pricing (B), and market basket pricing (E). Customer and vendor pricing are standard pricing conditions rather than retail-specific pricing strategies.

Loyalty Management is typically part of SAP CRM, not SAP IS Retail. The other options (Assortment, Sales Price Calculation, Promotion Management, Allocation) are core IS Retail processes for retail operations.

The retail process flow involves all key actors in the supply chain, including vendors, customers, distribution centers, stores, and consumers. Therefore, 'All of the above' is correct.

In SAP IS Retail, a site is defined as an organizational unit that can be either a store (A) or a distribution center (B). Plot and Warehouse are not standard site types in this context.

A purchasing group in SAP represents a buyer or a group of buyers who are responsible for certain purchasing activities. It does not represent vendors, administrators, or pickers.

In SAP, a Sales Area is defined as the combination of Sales Organization + Distribution Channel (+ Division as the third component, though Org + Channel is the core definition used in most contexts).

Subsequent activities to trigger a promotion in SAP IS Retail include activating prices (A), generating/editing the promotion allocation table (B), announcing the promotion (C), and determining sources of supply (E). Planning (D) is an initial step, not a subsequent trigger activity.

When experiencing email reception issues in Lotus Notes, the status bar displays error messages, connection status, and troubleshooting information that can help identify the root cause.