SAP Analytics Cloud: Analytics Designer — Lesson 2: Scripting Language, Events, APIs, Global Variables, Functions, and Reusable Components

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing Analytics Designer scripting.
• Perform and validate events, APIs, and reusable functions using reviewable system evidence.
• Evaluate the condition where an analytic application displays stale or incorrect values because widget events, variable prompts, data refresh, and script scope execute in an unexpected sequence and select proportionate corrective action.

Detailed Topics

• Scripting Language applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Events applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• APIs applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Global Variables applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Functions applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Reusable Components applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces an analytics development team creating an interactive management application that combines guided analysis, planning, and workflow behavior. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the Analytics Designer application specification, script, and test portfolio. It also tests the exception where an analytic application displays stale or incorrect values because widget events, variable prompts, data refresh, and script scope execute in an unexpected sequence.

Hands-On Exercise

Complete a controlled SAP exercise covering Scripting Language, Events, APIs, Global Variables, Functions, and Reusable Components and preserve the verified result in the Analytics Designer application specification, script, and test 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 Analytics Designer scripting.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the Analytics Designer application specification, script, and test 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 “an analytic application displays stale or incorrect values because widget events, variable prompts, data refresh, and script scope execute in an unexpected sequence” 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 Analytics Designer application specification, script, and test 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 Scripting Language, Events, APIs, Global Variables, Functions, and Reusable Components, explain the resulting SAP behavior, and defend the outcome through the Analytics Designer application specification, script, and test portfolio.