SAP Crystal Reports: Fundamentals of Report Design — Lesson 3: Record Selection, Group Selection, Parameters, Prompts, Subreports, and Drilldown

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing selection criteria and parameters.
• Perform and validate subreports, prompts, and drilldown navigation using reviewable system evidence.
• Evaluate the condition where report totals change unexpectedly because record selection, grouping, and formula evaluation occur at different stages and select proportionate corrective action.

Detailed Topics

• Record Selection applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Group Selection applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Parameters applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Prompts applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Subreports applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Drilldown applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces a reporting analyst building a reusable operational report that business users can filter, interpret, and distribute confidently. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the Crystal Reports design, test, and publication portfolio. It also tests the exception where report totals change unexpectedly because record selection, grouping, and formula evaluation occur at different stages.

Hands-On Exercise

Complete a controlled SAP exercise covering Record Selection, Group Selection, Parameters, Prompts, Subreports, and Drilldown and preserve the verified result in the Crystal Reports design, test, and publication portfolio.

1. Confirm scope, prerequisites, master data, roles, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, transactions, outputs, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, and handover actions.

Scenario Analysis

• Identify which object, rule, setting, or process step most strongly influences selection criteria and parameters.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the Crystal Reports design, test, and publication portfolio should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected SAP behavior first differs from the observed result. Check master data, configuration sequence, authorization, integration, status, and transaction evidence separately. Treat “report totals change unexpectedly because record selection, grouping, and formula evaluation occur at different stages” as a hypothesis until system settings, logs, documents, and outcomes confirm the cause.

Validation Checklist

• Required SAP structures, master data, roles, settings, and dependencies are present.
• The Crystal Reports design, test, and publication portfolio connects each conclusion to objective, reviewable evidence.
• Normal processing, the boundary condition, integration behavior, and exception were tested.
• Corrections, ownership, retest criteria, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Record Selection, Group Selection, Parameters, Prompts, Subreports, and Drilldown, explain the resulting SAP behavior, and defend the outcome through the Crystal Reports design, test, and publication portfolio.