SAP SRM/EBP & Cognos BI Enterprise Technology Quiz

Framework Manager allows importing metadata from multiple data sources into a single model, enabling reporting across heterogeneous databases and systems. This is a key feature for enterprise data warehousing where data comes from various sources. The model can combine tables from different databases, defining relationships and joins across data source boundaries.

Cognos Analysis Studio is designed for analyzing multi-dimensional data models (OLAP cubes), allowing users to explore data across multiple dimensions like time, geography, and product categories. It is not used for Framework Manager analysis (A), runtime macro filtering (B), or analyzing purely relational models (D). The tool specializes in OLAP and business intelligence analysis.

The statement claims 'We can't cancel/Reverse Good receipt from Portal' and the answer is False, meaning we CAN cancel/reverse Good Receipt from the Portal. In SAP SRM/EBP (Enterprise Buyer Portal) or supplier portals, goods receipts can typically be reversed or cancelled through the portal interface, subject to authorization and business rules. The ability exists, making the original statement incorrect.

In reverse catalog or limit shopping cart scenarios in SAP SRM, a dummy price of 1 (nominal value) is entered. This allows the system to validate and process the document. The actual price is later adjusted or determined based on the vendor invoice or confirmation.

Shopping cart approval levels in SAP SRM are determined by three key characteristics: T-class (transaction class), Plant, and Value. The T-class defines the transaction type (e.g., direct material, indirect material), the Plant represents the organizational unit, and the Value determines the monetary threshold for approval workflows. Options A and B incorrectly include company code or purchase group instead of T-class, while D includes purchase group which is not a determining factor for approval levels.

The SAP SRM/EBP system landscape for Kraft includes four systems: RGD, RGT, KTF, and KPE. These represent different instances in the landscape (likely Development, Test, and Production environments across different regions). Option A omits RGT, option B omits RGD, and option C incorrectly lists EAD/EAQ which are not valid Kraft SRM landscape identifiers.

In the classic SAP SRM scenario, the Related Documents section of a shopping cart shows the follow-on documents created during the procurement process: Purchase Requisition (PR), Purchase Order (PO), Reservation, Goods Receipt (GR), and Invoice. Option B incorrectly includes Contract (which is a standalone document, not a follow-on), option C adds Shipment, and option D adds Inbound Delivery - these are not typically shown in Related Documents for a shopping cart.

MDM stands for Master Data Management, which is a methodology and technology for managing an organization's critical data to ensure consistency, accuracy, and stewardship. In SAP environments, MDM is used to maintain consistent master data across systems. Options A, B, and C incorrectly suggest MDM stands for variations of Manager or is specific to Material - it's a broader concept covering all master data domains.

In custom SAP system templates (such as those used by Kraft/AP), ZVEN is configured specifically as the account group for external vendors. ZEMP is typically used for employees, and ZRED is for other specific internal or custom categories, making ZVEN the correct choice.

Kraft uses EBP (Enterprise Buyer Professional) specifically for purchasing Indirect Material & Services (IM&S) and Spares. Direct Materials and Commodities typically follow different procurement processes (often through core ERP/MRP systems), and Milk is not relevant in this SAP context. Option A (Direct Material) and B (Commodity) are incorrect as they use different procurement channels at Kraft.

Shopping cart value approval in SAP SRM is NOT multilevel - it follows a single-level approval workflow based on the value thresholds and other characteristics. The approval is determined once based on the T-class, Plant, and Value characteristics, and doesn't require multiple levels of approval escalation. Therefore, the statement is False.

In SAP SRM (EBP), sensitivity approvers are only triggered under specific conditions, such as when a shopping cart contains sensitive materials, restricted categories, or exceeds predefined value thresholds. They are not globally required for every single shopping cart created in the system, making the statement false.

The statement is false. SAP SRM EBP Purchase Order workflow approvals are typically linked to the total value of the document, not to the duration of the agreement or individual item line values. The system evaluates document-level values against authorized approval limits.

WBS (Work Breakdown Structure) element approval is not globally mandatory for all shopping carts. A shopping cart only requires WBS approval if it is cost-assigned to a WBS element; carts using cost centers or other account assignments bypass this step, making the statement false.

Table ZMMPUR_BBPPGRP maps SRM shopping cart attributes to determine backend SAP ECC purchasing groups. ZMMPUR_HIERVAL handles approval hierarchies, and ZMMPUR_LXAPP handles approval values, leaving ZMMPUR_BBPPGRP as the correct table for purchasing group determination.

In Kraft's SAP landscape, the KTF environment functions as the common SRM system connected to multiple ECC backends (like EAR and EAS). The other environments listed (KDJ, RDT, KPE) serve distinct, non-shared roles in the testing or production landscape.

In Kraft's custom SAP SRM workflow configuration, ZMMPUR_HIERVAL is the specific custom table designed to store hierarchy-based approval limit values for contracts. ZMMPUR_LXAPP is typically reserved for shopping carts, and ZMMPUR_BBPPGRP is used for purchasing group mapping.

Shopping cart approvers in SAP SRM are determined using two key characteristics: Plant and T-classes (transaction classes). The Plant identifies the organizational location, while T-classes categorize the transaction type (e.g., direct material, indirect material). These two characteristics together determine the appropriate approval agent/workflow. Options A, B, and D incorrectly suggest other characteristics that are not the primary determinants for SC approvers.