SACS21: SAP Analytics Cloud: Story Design — Lesson 3: Input Controls, Filters, Navigation, Bookmarks, and Presentations

Learning Objectives

• Explain how Input Controls, Filters, Navigation, Bookmarks, and Presentations supports clear governed analytics stories.
• Complete the workflow and produce a reviewable story interaction and navigation register.
• Evaluate the condition where a bookmark restores obsolete filters and misleads the presenter and select a supported response.

Detailed Topics

• input controls: business purpose, responsible roles, and SAP objects that establish the operating scope.
• story filters: configuration choices, master-data dependencies, and determination logic shaping the result.
• page navigation: transaction flow, status behavior, integration effects, and reviewable operational evidence.
• bookmarks and presentations: control points, exception paths, testing needs, and release criteria protecting the outcome.

Instructor Demonstration

The guided walkthrough connects input controls, story filters, page navigation, bookmarks and presentations to the intended business outcome and control evidence. Learners see the expected SAP behavior, what belongs in story interaction and navigation register, and how to respond when a bookmark restores obsolete filters and misleads the presenter.

Hands-On Exercise

Complete a controlled activity covering input controls, story filters, page navigation, bookmarks and presentations and preserve the result in story interaction and navigation register.

1. Define the expected business outcome and the SAP objects that should produce it.
2. Perform the lesson scenario, retaining before-and-after evidence for every material decision.
3. Test the exception without altering unrelated settings or data, then explain the first failure point.
4. Apply proportionate remediation and complete a focused regression check before approval.

Scenario Analysis

• Which SAP object, rule, record, or process step most strongly influences Input Controls, Filters, Navigation, Bookmarks, and Presentations?
• What evidence separates configuration, data, authorization, integration, and timing causes in this scenario?
• How should the story interaction and navigation register be approved, retained, monitored, and updated after handover?

Troubleshooting Guidance

Start at the earliest point where expected behavior differs from the observed result. Review process sequence, relevant data, configuration, authorization, integration, and timing as separate hypotheses. Treat “a bookmark restores obsolete filters and misleads the presenter” as unconfirmed until settings, documents, logs, reports, and focused retesting support the cause.

Validation Checklist

• Required roles, structures, data, settings, and dependencies for Input Controls, Filters, Navigation, Bookmarks, and Presentations are present.
• The story interaction and navigation register links each conclusion to objective and reviewable SAP evidence.
• Normal processing, the stated exception, integration behavior, and access boundaries were tested.
• Corrections, retest criteria, ownership, monitoring, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Input Controls, Filters, Navigation, Bookmarks, and Presentations, explain the resulting SAP behavior, and defend the outcome through story interaction and navigation register.