SAP SAP CRM Flashcards

24 sample cards from the SAP CRM deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

1. What role do Adapter Objects and the Replication & Realignment (R&R) queues play in Middleware?

   Adapter Objects define which data (which tables/fields) is exchanged and how it is extracted/mapped for initial and delta loads. The Replication & Realignment (R&R) queues determine the recipients of data (e.g., which mobile clients get which data) based on subscriptions/publications, ensuring each site receives only relevant data.

2. What are qRFC inbound and outbound queues used for in CRM Middleware, and how are they monitored?

   qRFC (queued Remote Function Call) guarantees serialized, reliable delivery of BDocs between systems. Outbound queues (transaction SMQ1) and inbound queues (SMQ2) buffer messages; BDoc processing/errors are monitored via transaction SMW01 (and SMW02 for status overview).

3. What is the CRM WebClient UI and what technology underlies it?

   The CRM WebClient UI is the browser-based, role-based user interface introduced with CRM 2006s/2007. It is built on the BSP (Business Server Pages) framework using the WebClient UI Framework (MVC pattern with views, controllers, and the BOL/GenIL data layer).

4. Describe the MVC (Model-View-Controller) design of the CRM WebClient UI Framework.

   View: BSP page + view controller displaying context node data. Controller: handles events and navigation. Model: the BOL/GenIL layer providing business data. UI components contain views, view sets, windows, and context nodes bound to BOL entities; navigation is handled via the Navigation Bar and component interfaces (inbound/outbound plugs).

5. What is a Business Role in the CRM WebClient UI and what does it control?

   A Business Role is the central configuration object that defines a user's UI: which Navigation Bar profile, layout profile, technical profile, and authorization/PFCG role apply. It controls the work centers, logical links, and functions a user sees, tailoring the UI to a job function (e.g., Sales Professional, IC Agent).

6. What tools are used to adapt the CRM WebClient UI without heavy development?

   The UI Configuration Tool (BSP_WD_CMPWB / the config tool) for arranging fields, labels, and views per role/object; the Application Enhancement Tool (AET) for adding custom fields end-to-end; and the Design Layer for defining field-level attributes centrally across contexts.

7. What is the Application Enhancement Tool (AET) used for?

   AET is a WebClient UI tool that lets configurators add custom fields to business objects without ABAP coding. It automatically extends the database tables, BOL/GenIL model, UI, and (optionally) Middleware/BW replication for the new field, making end-to-end enhancement declarative.

8. What is the difference between the UI Configuration Tool and the Component Workbench (BSP_WD_CMPWB)?

   The UI Configuration Tool handles declarative, role-/object-specific layout of existing views (field placement, visibility, labels). The Component Workbench (BSP_WD_CMPWB) is the developer environment for creating/modifying UI components, views, context nodes, and enhancement sets (deeper, code-level changes).

9. What is SAP CRM Mobile / Mobile Sales and Mobile Service (the classic Mobile Application Studio scenario)?

   A framework for occasionally-connected field users (sales reps, service technicians) running a local client with a local database. Data is synchronized with the CRM server via CRM Middleware (mobile BDocs, R&R). Later offerings include SAP CRM Sales/Service on mobile devices and Fiori/Gateway-based mobile apps.

10. How does data synchronization work for the classic occasionally-connected CRM Mobile client?

    The mobile client holds a local database (e.g., Microsoft SQL Server). It connects periodically to the Communication Station/CRM server; changes are exchanged as mBDocs. The Replication & Realignment service determines which data each mobile site receives based on publications/subscriptions, and delta changes flow bidirectionally.

11. What is the difference between customizing/configuration and development (custom code) in SAP CRM?

    Customizing/Configuration uses SPRO/IMG settings, business roles, transaction types, and UI config to adapt standard functionality without ABAP (client-independent settings transported via requests). Development involves ABAP coding, BAdIs, enhancements, and custom UI components for requirements not met by configuration.

12. What is a Transaction Type in SAP CRM and where is it configured?

    A Transaction Type controls the properties and behavior of a One Order business transaction (e.g., which item categories, partner determination, status profile, and text schema apply). It defines the business context (Sales Order, Service Order, Lead, etc.) and is configured in the IMG (SPRO) under transaction/business processing.

13. What is an Item Category and how is it determined in SAP CRM?

    An Item Category controls how an item behaves within a transaction (pricing, delivery relevance, completion, etc.). It is determined automatically by a combination of Transaction Type + Item Category Group (from product master) + (optionally) item usage + higher-level item category, via the item category determination table.

14. How does Partner Determination work in SAP CRM?

    A Partner Determination Procedure, assigned to a transaction type/item category, defines which Partner Functions (e.g., Sold-To, Ship-To, Contact Person, Employee Responsible) are relevant and the access sequences/rules used to automatically find business partners for a transaction.

15. What is the Actions framework (Post-Processing Framework, PPF) in SAP CRM used for?

    The PPF (Actions) is a generic mechanism to trigger follow-up processing based on conditions: it can generate output (print/email/fax), create follow-up transactions, or call methods. Actions are defined in Action Profiles assigned to transaction types, with schedule and start conditions evaluated at runtime.

16. What is the Status Management framework (system vs. user statuses) in SAP CRM?

    Status Management controls the lifecycle of transactions/items. System statuses are set automatically by the system (e.g., Open, In Process, Completed). User statuses are defined in a Status Profile to model custom business states and can allow/forbid business transactions (Bus. Trans. Control).

17. What is the pricing engine used by SAP CRM, and how does it differ conceptually from ERP pricing?

    SAP CRM uses the Internet Pricing and Configurator (IPC), the Virtual Machine Container (VMC)-based pricing engine. It uses the condition technique (condition types, access sequences, condition tables, pricing procedures) analogous to ERP SD, but runs as a Java-based engine (AP/CPS) allowing real-time pricing in web and mobile scenarios.

18. Explain the condition technique used for pricing determination in SAP CRM.

    A Pricing Procedure lists condition types in sequence. Each condition type has an Access Sequence containing condition tables (accesses) checked in order; the first matching condition record supplies the value. This determines prices, discounts, surcharges, freight, and taxes for a transaction item.

19. What is SAP CRM Embedded Analytics / CRM Interactive Reporting?

    CRM Interactive Reporting provides out-of-the-box operational reports directly within the WebClient UI, drawing from CRM transactional data (with a lightweight, self-contained BI data store based on SAP BW technology embedded in the CRM system). It requires minimal setup for standard reports on sales, service, and marketing KPIs.

20. How does SAP CRM integrate with SAP BW (Business Warehouse) for analytics?

    CRM extracts data to SAP BW using standard DataSources (extractors) via the BW Service API / delta queue (RSA7). BW models the data in InfoProviders and BEx queries; results can be surfaced back in the CRM WebClient via BI reports/iViews. This supports strategic, cross-system, and historical analytics beyond embedded interactive reporting.

21. What is the difference between CRM Interactive (Embedded) Reporting and full SAP BW analytics?

    Interactive Reporting is operational, real-time-ish, embedded, and easy to set up for CRM-only data with limited history and volume. Full BW analytics offers strategic, high-volume, historical, multi-source data warehousing with complex modeling, planning, and cross-application reporting — at the cost of a separate BW system and greater implementation effort.

22. What implementation methodology does SAP recommend for CRM projects, and what are its phases?

    SAP ASAP (Accelerated SAP). Classic phases: 1) Project Preparation, 2) Business Blueprint, 3) Realization, 4) Final Preparation, and 5) Go-Live & Support (with Run/Operate). Newer SAP projects use SAP Activate (Prepare, Explore, Realize, Deploy, Run) with fit-to-standard workshops.

23. Name key performance optimization techniques for SAP CRM Middleware and system performance.

    Parallelize and monitor qRFC queues (SMQ1/SMQ2, MW block sizes), tune R&R queue processing and use appropriate block sizes for initial loads, archive/delete processed BDocs (SMW01), keep good database statistics/indexes, and schedule loads during off-peak. For UI, optimize WebClient component load, minimize round trips, and use table lazy-loading.

24. What performance/monitoring transactions and practices apply to the CRM WebClient UI and general CRM tuning?

    Use ST05 (SQL trace) and the ABAP runtime analysis (SAT/SE30) to find expensive DB accesses and code; ST22 for dumps; SM50/SM66 for work processes; and the WebClient UI trace tools. Best practices: reduce BOL/GenIL round trips, enable table pagination, cache read-only data, and right-size result-list row counts.

What this deck covers

SAP CRM flashcards FAQ