Introduction
SAP Analytics Cloud (SAC) provides powerful real-time analytics through BW Live connections. However, users frequently face access issues when opening BW Live stories in Microsoft Edge.
In most cases, these problems are not caused by BW or SAC models, but by:
- Browser security restrictions in Microsoft Edge
- Missing SAC or BW roles
- Incomplete user profile or license assignment
This guide focuses only on BW Live access issues in Microsoft Edge and how to resolve them.
- Common SAC Access Errors for BW Live Users
- Missing User Profile or Role (BW Live Context)
Typical message:
“Please contact your administrator to assign the required role.”
What it means:
- Your SAC user profile is not created, or
- Your SAC license is missing, or
- Required BW Live–related roles are not assigned
Without these, BW Live stories will not open, even if import models work.
Action:
- Confirm SAC license assignment
- Confirm BW Live access role with your administrator
- Browser Authorization Prompt in Microsoft Edge
What you see:
- Microsoft Edge asks for username and password when opening a BW Live story
What it means:
- User profile creation has started
- SAC license is not yet fully assigned
This issue is more visible in BW Live stories, because they require live authentication.
Action:
- Wait for license completion
- Check request status with the administrator
- Unauthorized Error Due to IDM Lock (BW Live)
Typical error:
- “Unauthorized”
- SAML2 authentication error
What it means:
- Your SAP user ID is locked in Identity Management (IDM)
- BW Live authentication fails immediately
Action:
- Contact administrator
- Request IDM unlock
- BW Live Connection Fails in Microsoft Edge
Typical symptoms:
- BW Live story opens but data does not load
- “Unable to connect to BW system”
- Blank tables or charts
Most common root cause in Edge:
- Third-party cookies are blocked
This issue affects BW Live only, not import models.
- Microsoft Edge Settings Required for BW Live
Third-Party Cookies (Critical for BW Live)
Microsoft Edge may automatically disable third-party cookies every 90 days.
When this happens:
- BW Live authentication fails
- SAC stories stop working suddenly
How to Enable Third-Party Cookies in Edge
- Open a BW Live SAC story in Microsoft Edge
- Look for the eye symbol in the browser address bar
- Click the eye symbol
- Enable third-party cookies for the SAC site
- Refresh the page
In most cases, BW Live data loads immediately.
- Pop-Ups and Redirects (BW Live Requirement)
BW Live uses pop-ups for:
- Authentication
- Variable prompts
If pop-ups are blocked, BW Live cannot complete login.
Edge Configuration
- Go to Edge Settings
- Open Cookies and Site Permissions
- Select Pop-ups and redirects
- Add your SAC tenant URL to Allow
Reload the BW Live story after this change.
- Role-Based Access for BW Live Data
If SAC opens but BW Live data fails:
Possible reason:
- Missing BW Live–specific role or view authorization
Action:
- Ask administrator to raise a GRC request
- Ensure both:
- SAC role
- BW Live / BW authorization role
are included
Checking GRC Request Status
- Open GRC Home
- Navigate to Search Requests
- Track approval and completion
Do not rely only on email updates.
- Confirmation That BW Live Access Is Ready
You will receive an email from the SAP Authorization Batch system when:
- SAC license is assigned
- User profile is created
- BW Live roles are active
After this, BW Live stories should open correctly in Microsoft Edge.
Final Tips for BW Live Users on Microsoft Edge
- This guide applies only to BW Live data
- Import models are usually not affected
- Microsoft Edge needs periodic cookie checks
- Pop-ups must be allowed
- Both SAC and BW roles are mandatory
Checking browser settings first can save hours of troubleshooting.
Conclusion
Most SAC access errors for BW Live users in Microsoft Edge are caused by browser security settings or missing roles, not by BW or SAC issues. With the right Edge configuration and proper role assignment, BW Live stories work reliably and smoothly.
Bluesky
