55118-A: Creating Reports with SAP Crystal Reports for Developers with Visual Studio — Lesson 2: Fields, Groups, Summaries, Formulas, Running Totals, Parameters, and Conditional Formatting

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing report calculations and parameter design.
• Perform and validate groups, formulas, totals, and formatting using reviewable system evidence.
• Evaluate the condition where a report works in the designer but fails in the application because runtime versions, database logon, parameter binding, and deployment dependencies differ and select proportionate corrective action.

Detailed Topics

• Fields applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Groups applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Summaries applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Formulas applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Running Totals applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Parameters applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Conditional Formatting applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces a .NET development team embedding parameterized operational reports into a secure business application. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the 55118-A report design, application integration, and deployment portfolio. It also tests the exception where a report works in the designer but fails in the application because runtime versions, database logon, parameter binding, and deployment dependencies differ.

Hands-On Exercise

Complete a controlled SAP exercise covering Fields, Groups, Summaries, Formulas, Running Totals, Parameters, and Conditional Formatting and preserve the verified result in the 55118-A report design, application integration, and deployment 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 report calculations and parameter design.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the 55118-A report design, application integration, and deployment 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 “a report works in the designer but fails in the application because runtime versions, database logon, parameter binding, and deployment dependencies differ” 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 55118-A report design, application integration, and deployment 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 Fields, Groups, Summaries, Formulas, Running Totals, Parameters, and Conditional Formatting, explain the resulting SAP behavior, and defend the outcome through the 55118-A report design, application integration, and deployment portfolio.