Unit 2: Planning in stories Flashcards
Leveraging SAP Analytics Cloud Functionality for Enterprise Planning (146 cards)
In SAP Analytics Cloud, what are versions primarily used for?
A. Storing historical data
B. Organising different user access levels
C. Organising, comparing, and maintaining actual, plan, and forecast data
D. Tracking software updates
C
In SAP Analytics Cloud, how are versions utilised for planning purposes?
A. Versions allow for storing only historical (actual) data.
B. They organise different user access levels for data manipulation.
C. Versions enable the creation of multiple plan iterations for future planning, each using a different version of data.
D. Versions are primarily used for tracking software updates.
C
How many versions do you need for historical (actual) data?
A. 2
B. 1
C. 10
D. Unlimited versions
B
You only need one version for historical (actual) data.
What happens when you change data in one version?
A. The changes affect all versions simultaneously.
B. Data modifications are restricted to read-only access.
C. The system prompts for confirmation before any changes are made.
D. Alterations in one version do not affect data in other versions.
D
How does Version Management enhance planning in SAP Analytics Cloud?
A. By limiting the creation of new versions for each forecast period.
B. By enabling the management of different versions and types of plans.
C. By merging forecasts with other types of plans like budgets and strategic plans.
D. By restricting access to specific plan types for certain users.
B
What is an example of how organizations can utilise Version Management in SAP Analytics Cloud?
A. Creating a single version for all types of plans.
B. Restricting access to plan types based on user roles.
C. Merging all plan types into one unified version.
D. Separating forecasts from other types of plans by creating a new version for each forecast period.
D
Other types of plans includes budgets and strategic plans.
In SAP Analytics Cloud, how are versions integrated when creating planning models?
A. Versions serve as a primary identifier for different users in planning models.
B. The actual version is automatically assigned as a system default in planning models.
C. Versions are created within stories and then linked to planning models.
D. Versions are not applicable in planning models within SAP Analytics Cloud.
B
What role does the “Version” dimension play in SAP Analytics Cloud planning models?
A. It acts as a filter to sort data by different versions of the plan.
B. Versions are created independently of planning models and stories.
C. The actual version is provided as a default, and additional versions are created during planning in stories.
D. Versions in planning models are solely managed by system administrators.
C
Additional versions are creating during planning stories.
What is the primary characteristic of private versions in SAP Analytics Cloud?
A. Maintained and visible only to the creator.
B. Visible only to system administrators.
C. Visible to all users.
D. Visible to specific user groups.
A
What can private versions be used for in SAP Analytics Cloud?
A. Sharing plan values with specific user groups.
B. Automatically updating plan values based on system changes.
C. Tracking historical changes in plan values.
D. Changing or simulating plan values without making the changes visible to anyone else.
D
How can a private version be transformed into a new public version in?
A. By utilising the “Publish As” option.
B. By selecting the “Share” option within the story.
C. Through manual conversion by system administrators.
D. Automatically upon creation.
A
When using the “Publish private data” option, what occurs in SAP Analytics Cloud?
A. Private version is deleted, and a new public version is created.
B. Data in the private version is copied to the original public version it was copied from initially.
C. Private version is converted into a read-only format.
D. Private version becomes inaccessible to anyone.
B
How is data editing handled in private versions?
A. Data edits require approval from system administrators.
B. Private versions allow read-only access, prohibiting data editing.
C. Edits in private versions are not automatically saved.
D. Edits in private versions are automatically saved without user intervention.
D
Can private versions be shared with other users?
A. Yes, they can be shared if necessary
B. No, private versions are strictly restricted to the creator
C. Yes, but only by system administrators
D. Yes, but only with specific user groups
A
How does SAP Analytics Cloud handle viewing private data?
A. Users can view their own private data from the planning model without the need to save or publish changes.
B. Private data changes must be saved and published manually.
C. Private data can only be viewed by system administrators.
D. Private data changes are automatically saved and published to the planning model.
A
Where are public versions maintained, and why are they published in SAP Analytics Cloud?
A. Public versions are maintained in planning models to restrict access, and they are published to enforce data integrity.
B. Public versions are maintained in data warehouses for archival purposes, and they are published to streamline data processing.
C. Public versions are maintained in stories, and they are published so that other planners can view the data.
D. Public versions are maintained in separate databases for security reasons, and they are published to ensure compliance with regulations.
C
How is access to data controlled in public versions within SAP Analytics Cloud?
A. By system administrators only
B. Through user-defined access levels
C. Access is unrestricted
D. Controlled by data privileges
D
What happens if changes to data in a story are not published before exiting in SAP Analytics Cloud?
A. Changes are automatically reverted
B. Users are prompted to publish changes
C. You’re prompted either to Revert all or Publish all changes.
D. Data changes are discarded
E. Data changes are retained in edit mode but not published
C
What happens if you leave a story without reverting or publishing the data?
A. Changes are automatically reverted
B. Users are prompted to publish changes
C. Data changes are discarded
D. Data changes are retained in edit mode but not published
D
Can there be multiple public Actual versions in a planning model in SAP Analytics Cloud?
A. Yes, there can be multiple public Actual versions
B. No, there can only be one public Actual version
C. Public versions are not applicable to Actual data
D. Public Actual versions must be created manually by administrators
B
What controls are available when leaving a story without publishing data changes in SAP Analytics Cloud?
A. Options to revert changes or publish them
B. Changes are automatically reverted
C. Data changes are published automatically
D. Data changes are discarded automatically
A
How can versions be managed in SAP Analytics Cloud?
A. Through the Version Control feature in the data settings.
B. Via the Version Management option in the story ribbon.
C. Versions are automatically managed by the system without user intervention.
D. Versions can only be managed by system administrators.
B
How can a private version be shared in SAP Analytics Cloud?
A. Navigate to Version Management, select “more”, and click “Share” to choose access permissions (Read Only or Read and Write).
B. Access the story ribbon, select “Share Version,” and specify read-only or read-write permissions.
C. Go to Data Settings, find the private version, and enable sharing options.
D. Private versions cannot be shared in SAP Analytics Cloud.
A