"How does SAP position SAP Data Warehouse Cloud in supporting business users?"
- A . Business users can maintain process chains from SAP BW/4HANA dataflows
- B . Business users can create agile models from different sources
- C . Business users can allocate system resources without IT involvement
- D . Business users can generate SQL code that is pushed to SAP BW/4HANA.
B
Explanation:
SAP Data Warehouse Cloud is a cloud-based data service that enables business users to create agile models from different sources and access data in real time. Business users can use the graphical user interface or the SQL editor to create data models, join data from various sources, and enrich data with business semantics. Business users can also use SAP Analytics Cloud to visualize and analyze data from SAP Data Warehouse Cloud. SAP Data Warehouse Cloud supports business users by providing self-service capabilities, pre-built business content, and flexible consumption options. References: 123
You want to run a BW query, but you only have partial authorization for the data selection.
What happens related to the BW query in this scenario?
- A . The BW query starts and shows an error message
- B . The BW query does not start running
- C . The BW query starts and the unautohorized values are
- D . The BW query starts and only the authorized data is displayed
D
Explanation:
In SAP BW/4HANA, the system’s authorization concept allows for selective data access. This means if a user only has partial authorization for a BW query, the query will still run, but it will only display the data for which the user has authorization. Unauthorized data will not be shown. So, even with partial authorization, the user can still see a subset of the data.
You create an SAP HANA HDI Calculation View.
What are some of the reasons to choose the data category Cube with Star Join instead of data category Dimension? Note: There are 3 correct answers to this question.
- A . Create restricted columns
- B . Provide default time characteristics
- C . Persist transactional data
- D . Combine master data and transactional data
- E . Aggregate measures as a sum
B,D,E
Explanation:
Creating restricted columns isn’t a specific reason to choose Cube with Star Join. Restricted columns can also be created in other data categories.
When choosing Cube with Star Join, you are provided with default time characteristics. This makes the Cube with Star Join particularly useful for time-dependent data analysis.
Persisting transactional data is a process of database operations, not specifically related to the choice between Cube with Star Join or Dimension.
Cube with Star Join combines master data and transactional data. The master data is typically stored in the dimensions of the star schema, and the transactional data is stored in the fact table at the center of the star schema.
Cube with Star Join can aggregate measures as a sum, which is important for analysis in many business scenarios.
Where can you automatically generate a process chain?
- A . Form a data flow objetc
- B . Within the process chain editor app
- C . from a streaming enable DataSource
- D . Within the process chain maintance
A
Explanation:
In SAP BW/4HANA, you can automatically generate a process chain from a data flow object. This helps to simplify the process of creating and maintaining process chains. The other options do not provide functionality for automatic generation of process chains.
What does a Composite Provider allow you to do in SAP BW/4HANA? Note: There are 3 correct Answers to this question.
- A . Combine Infoprovider using Join and Unions
- B . Join two ABAP CDS views
- C . Define new restricted key figures
- D . Create new calculated fields Integrate
- E . SAP HANA HDI calculation views.
A,D,E
Explanation:
Composite Provider allows you to combine InfoProviders using join and union operations in SAP BW/4HANA. This is one of the key features of a Composite Provider, allowing users to create complex models using multiple data sources.
Joining two ABAP CDS views is not a specific feature of a Composite Provider in SAP BW/4HANA. This can be done without a Composite Provider.
Defining new restricted key figures is a function of the BEx Query Designer, not of the Composite Provider.
Creating new calculated fields is another function of a Composite Provider. It allows users to extend their data model with calculated fields, based on existing ones.
Integrating SAP HANA HDI calculation views is also a function of a Composite Provider. This allows for more advanced modeling and analytical capabilities by utilizing HANA’s native calculation views.
You use InfoObject B as a display attribute for InfoObject A.
Which object properties prevent you from changing InfoObject B into a navigational attribute for InfoObject A? Note: There are 3 correct nswers to this question."
- A . High Cardinality is set in InfoObject B
- B . Attribute Only is set in InfoObject B
- C . Data Type "Character String" is set in InfoObject A
- D . Conversion Routine "ALPHA" is set in InfoObject A
- E . InfoObject B is defined as a Key Figure.
B,D,E
Explanation:
High Cardinality is a property that can be set on InfoObjects, but it doesn’t prevent the changing of a display attribute into a navigational attribute.
If "Attribute Only" is set for InfoObject B, it can’t be used as a navigational attribute. This setting restricts the InfoObject to only being used as an attribute.
The data type of InfoObject A doesn’t influence the ability to change InfoObject B into a navigational attribute.
If a conversion routine (like "ALPHA") is set in InfoObject A, it doesn’t directly prevent InfoObject B from being used as a navigational attribute, but it might cause inconsistencies in the data when used for navigation.
If InfoObject B is defined as a key figure, it can’t be used as a navigational attribute. Navigational attributes must be dimensions, not key figures.
In a DatStore object (advanced) of type Data Mart, which request-based deletion is possibel?
- A . The lastest not-yet-activated reques in the inbound table
- B . The lastest request in the active data table
- C . Any older activated reqeust in the inbound table
- D . The lastest request in the change log table
A
Explanation:
In a DataStore Object (advanced) of type Data Mart, only the latest not-yet-activated request in the inbound table can be deleted. Once a request has been activated and the data has been moved to the active data table or the change log table, it cannot be deleted on a request basis. Similarly, older activated requests in the inbound table cannot be deleted on a request basis.
Which SAP BW/4HANA objetcs can be used as sources of a data transfer process (DTP)? Note: There are 3 correct answers to this question.
- A . InfoSource
- B . Open Hub Destination
- C . DataStore Objetc (advanced)
- D . CompositeProvider
- E . SAP HANA Analysis Process
C,D,E
Explanation:
An InfoSource in SAP BW/4HANA can be used as a source in a Data Transfer Process (DTP). The DTP extracts data from the InfoSource and loads it into the target.
Open Hub Destination is a target object, not a source, in SAP BW/4HANA. It is used to distribute data to non-SAP data marts, analytical applications, and other applications.
A DataStore Object (advanced) can serve as a source in a DTP. It allows data to be updated flexibly from different sources and provides the data for reporting and analysis purposes.
A CompositeProvider can also be used as a source of a DTP. CompositeProviders allow you to combine data from several analytic indexes in a Union or Join operation.
SAP HANA Analysis Process is a method or process, not an object that can be used as a source in a DTP. It is used to execute data mining functions such as clustering, classification, and association.
You want to build an SAP HANA HDI calculation view of data category CUBE, but you get the "no measure defined" error. For the business requirement, a measure does not make sense.
Besides changing the data category to DIMENSION, what do you have to do?
- A . Switch from an aggregation node to a star join node
- B . Switch from an aggregation node to a projection node
- C . Switch form a projection node to an aggregation node
- D . Switch from a projection node to a star join node
B
Explanation:
In SAP HANA HDI Calculation views, if you’re creating a cube and there are no measures defined (which is mandatory for cubes), and you don’t want to switch to the Dimension data category, you can switch from an aggregation node (which requires at least one measure) to a projection node. A projection node doesn’t require a measure, so this will resolve the "no measure defined" error.
What is the purpose of an architecture overview model?
- A . To identify the user groups and required authorizations
- B . To automatically generate the LSA++ architecture
- C . To determine the sequence of projects
- D . To identify the required data sources.
D
Explanation:
An architecture overview model is used to identify the required data sources for an SAP BW/4HANA implementation. This includes determining where data is coming from, how it should be processed, and how it should be stored. It does not identify user groups, generate the LSA++ architecture automatically, or determine the sequence of projects.
When loading master data for a material, you want to look at the new values before they are released for reporting.
What could you do using modeling features? Note: There are 2 correct answers to this question.
- A . When you define the attributes of material, select the "Time Dependent" setting
- B . When you define the data transfer process, select the "Load records wit new key only" setting
- C . When you define the data transfer process, choose the "Set Manually" setting for "Overrall status of request"
- D . When you define the material characteristic, select the "Enhanced Master data update" setting
C,D
Explanation:
The "Time Dependent" setting doesn’t help you preview new values before they are released for reporting. This setting makes the attribute values time-dependent, not controlling their visibility.
The "Load records with new key only" setting in the data transfer process doesn’t enable previewing of new values. It only influences the loading of records with new keys.
The "Set Manually" setting for "Overall status of request" in the data transfer process allows the request to be manually set to a certain status, such as "hold", which can provide an opportunity to review the new values before they’re released.
The "Enhanced Master data update" setting in the material characteristic allows for an additional step before the master data is made available for reporting. This additional step can be used to review the new values before they’re released.
For which requirements do you suggest an SAP HANA modeling focus rather that an SAP BW/4HANA modeling focus?? Note: There are 2 correct answers to this question.
- A . Enhance existing SAP HANA content models
- B . Report on a harmonized set of master data
- C . Load snapshots or deltas from different sources on a periodic basis
- D . Leverage SQL in-house knowledge
A,D
Explanation:
When the requirement is to enhance existing SAP HANA content models, it would be more suitable to focus on SAP HANA modeling. This is because the existing models are already in HANA and can be modified directly using HANA tools.
Reporting on a harmonized set of master data is more related to BW/4HANA modeling as SAP BW/4HANA provides robust support for master data management.
Loading snapshots or deltas from different sources on a periodic basis is a task generally handled by ETL (Extract, Transform, Load) processes within BW/4HANA, so this is more of a BW/4HANA focus.
If you have SQL in-house knowledge, you would likely want to leverage this and therefore would focus on SAP HANA modeling, as HANA provides a SQL interface to its database.
Which tasks are part of the Business Blueprint and Data Model Definition phase in an SAP BW/4HANA project? Note: There are 3 correct answers to this question.
- A . Check the availability of data
- B . Specify necessary data conversion
- C . Implement transport routes and layers
- D . Monitor batch jobs and data volume
- E . Design the data layer concept
A,B,E
Explanation:
Checking the availability of data is a key task in the Business Blueprint and Data Model Definition phase. It’s important to ensure that all necessary data sources are available and accessible.
Specifying necessary data conversions is also a crucial task. This helps to ensure that the data from different sources can be effectively integrated and used within the data model.
Implementing transport routes and layers is part of the system setup and is usually handled during the project preparation phase rather than during the Business Blueprint and Data Model Definition phase.
Monitoring batch jobs and data volumes is more related to the operational phase of the system and is not typically part of the Business Blueprint and Data Model Definition phase.
Designing the data layer concept is a key task of the Business Blueprint and Data Model Definition phase. It helps define how data should be organized and structured within the system.
Which interface do you use to create a BW InfoObjet with access type "SAP HANA view!?
- A . BW moedling perspective in SAP HANA studio
- B . SAP HANA modeler perspective in SAP HANA studio
- C . Embedded SAP GUI in SAP HANA studio
- D . SAP Web IDE for SAP HANA
A
Explanation:
To create a BW InfoObject with access type "SAP HANA view", you would use the BW Modeling perspective in SAP HANA Studio. This perspective allows you to work with BW InfoObjects and other BW modeling entities, and it includes the ability to set the access type for InfoObjects to "SAP HANA view". The other interfaces are either focused on native HANA modeling (B and D) or general-purpose SAP tasks (C), and do not provide the specific BW modeling functionality needed for this task.
What are some of the prerequisites for using SAP S/4HANA ABAP CDS views for extraction into SAP BW/4HANA in an ODP context? Note: There are 2 correct answers to this question.
- A . An ODP source system with contest ODP_CDS must be created in SAP BW/4HANA
- B . The ABAP CDS views must be defined with the appropriate data extraction annotations
- C . THE ABAP CDS views must be released via program RODPS_OS_EXPOSE for BW extraction
- D . An Operational Data Provisioning Framework must be configured in SAP BW/4HANA
A,B
Explanation:
An ODP source system with context ODP_CDS must be created in SAP BW/4HANA. This allows the system to communicate with the source system using the Operational Data Provisioning (ODP) framework and to extract data from ABAP CDS views.
The ABAP CDS views must be defined with the appropriate data extraction annotations. These annotations define the technical attributes of the data source and allow it to be consumed in the ODP context.
While exposing CDS views for ODP extraction is required, as of my knowledge cut-off in September 2021, this is done through CDS view annotations and not through the program RODPS_OS_EXPOSE.
The Operational Data Provisioning Framework is inherently part of SAP BW/4HANA and doesn’t need to be separately configured for using ABAP CDS views for extraction. However, the specific ODP context (ODP_CDS in this case) must be set up in the BW source system, as mentioned in option A.
Which of the following are possible delta-specific field for a generic DataSource in SAP ERP? Note: There are 3 correct answers to this question.
- A . Record mode
- B . Calendar day
- C . Request ID
- D . Time stamp
- E . Numeric pointer
B,D,E
Explanation:
Record mode is not a delta-specific field. It is generally used for indicating the type of operation (like insert, delete, or update) on a record.
Calendar day can be used as a delta-specific field. Delta extraction can be based on the calendar day, for example, all records that have changed since the last extraction date.
Request ID is generally not used as a delta-specific field. It is typically used to identify a data load request.
Time stamp can be used as a delta-specific field. Similar to the calendar day, delta extraction can be based on a timestamp field, capturing all records that have changed since the last extraction timestamp.
Numeric pointer can also be used as a delta-specific field. It typically identifies a position in the application log of a source system from where data needs to be read for the delta load.
You would like to highlight the deviation from predefined threshold values for key figures actual revenue.
Which BW feature do you use?
- A . Structure
- B . Conditions
- C . Exceptions
- D . Calculated key figures
C
Explanation:
In SAP BW, you use Exceptions to highlight deviations from predefined threshold values for key figures. You can define exceptions in a query to specify particular criteria that the data in your query should meet. If the data meets these criteria, then it will be highlighted in a particular way, allowing you to easily identify any deviations from the expected values. Conditions are used to filter the results, while structures and calculated key figures are used to organize and perform calculations on the data, respectively.
You have created a custom characteristic with the technical name "COSTOBJ". Depending on the controlling area, you need to have different atribute values assigned.
How do you desing the model?
- A . Compound characteristic "COSTOBJ" with the characteristic for Controlling Area
- B . Compound the characteristic for Controlling Area with the characteristic "COSTOBJ"
- C . Define Controlling Areas as a navigation attribute for the characteristic "COSTOBJ"
- D . Define characteristic "COSTOBJ" as a navigation attribute for Controlling Area
A
Explanation:
Compounding is used in SAP BW when the values of an InfoObject are only unique in combination with the values of another InfoObject. In your scenario, the value of the characteristic "COSTOBJ" (cost object) is unique only in combination with the characteristic for Controlling Area. Hence, you would compound the characteristic "COSTOBJ" with the characteristic for Controlling Area. The order of compounding is important, therefore option B is not correct. Options C and D, which involve defining navigation attributes, are not appropriate because they are typically used for reporting purposes rather than ensuring uniqueness of values.
The Database Explorer in the Web IDE for SAP HANA proveides a data file improt wizard to create a table in SAP HANA from a flat file.
What are possible actions adter the system suggests the target structure?? Note: There are 3 correct answers to this question.
- A . Change the order of the fields in the target table
- B . Switch the table type between row store and column store
- C . Define sorting properties for a target table field
- D . Adjust the suggested data type of the target table fileds
- E . Map InfoObjetcs to fields in the target tavle
A,B,D
Explanation:
In the data file import wizard, you can change the order of the fields in the target table.
You can also switch the table type between row store and column store. This determines how the data will be stored in SAP HANA.
Defining sorting properties for a target table field is typically done as part of the data modeling process and is not available as an option in the data file import wizard.
You can adjust the suggested data type of the target table fields. The wizard usually suggests a data type based on the input data, but this can be manually adjusted if needed.
Mapping InfoObjects to fields in the target table is part of BW modeling and not typically part of the process of importing data into a table in SAP HANA using the data file import wizard.
What are the prerequisites for deleting master data (for example, cost centers) in SAP BW/4HANA? Note: There are 2 correct answers to this question.
- A . There must be no BW analysis authorizations defined thta use any of the cost centers
- B . There must be no transaction data referring to the cost centers
- C . There must be no hierarchy for the cost centers
- D . There must be no BW query that uses cost cenetr as a free characteristics.
B,C
Explanation:
BW analysis authorizations are not a constraint for deleting master data. They are used for controlling access to data during query execution.
There must be no transaction data referring to the cost centers. If there is transaction data in InfoProviders or DataStore objects that reference the cost centers, then you cannot delete these cost centers.
There must be no hierarchy for the cost centers. If there is a hierarchy defined on the cost centers, then these cost centers cannot be deleted.
The existence of a BW query that uses cost center as a free characteristic is also not a constraint for deleting master data. Queries are designed based on the InfoProvider structure and data. However, if master data is deleted, it might impact the output of the queries where those master data elements are used.
You created an Open ODS view of type Facts.
Which object type can you associate with a view field in the characteristics folder? Note: There are 2 correct answers to this question.
- A . Open ODS view of type Facts
- B . Calculation View of type Dimension
- C . Open ODS view of type Master Data
- D . InfoObjetc of type Characteristic
C,D
Explanation:
An Open ODS view of type Facts represents transaction data and is not suitable for associating with a field in the characteristics folder.
An Open ODS view of type Master Data can be associated with a view field in the characteristics folder of an Open ODS view of type Facts. The Master Data type Open ODS view provides attributes and texts for this association.
An InfoObject of type Characteristic can also be associated with a view field in the characteristics folder. InfoObjects are the smallest units in SAP BW and they can be directly associated with view fields.
A Calculation View of type Dimension is an SAP HANA specific object and is not typically used within an Open ODS view in BW/4HANA. It is used to join, filter, and aggregate data in the SAP HANA database.
Which external hierarchy properties can be changed in the query definition? Note: There are 3 correct answers to this question.
- A . Position of child nodes
- B . Expand to level
- C . Time dependency
- D . Sort direction
- E . Allow temporal hierarchy join
B,D,E
Explanation:
Expand to level: This determines the level up to which a hierarchy is initially expanded in a query output. You can change this property in the query definition.
Sort direction: This determines the order in which the hierarchy nodes are displayed in the query output. You can change this property in the query definition.
Allow temporal hierarchy join: This enables a time-dependent display of the hierarchy in a query output. You can change this property in the query definition.
Position of child nodes: This is defined at the hierarchy creation level and cannot be changed in the query definition.
Time dependency: This is a property of the hierarchy or the InfoObject itself and can’t be changed in the query definition.
You want build a web-based dashboard with interactive visualizations using Javascript.
Which SAP tool can you use to create this?
- A . SAP BusinessObjects
- B . Web Intelligence
- C . SAP Analytics Cloud analytics designer
- D . SAP Crystal Reports
- E . SAP Smart Business Cockpits
C
Explanation:
The SAP Analytics Cloud analytics designer is a powerful and flexible tool that allows you to create analytical applications and dashboards. It supports scripting (JavaScript) which allows the creation of complex, interactive and highly customised applications. This is most suitable for building a web-based dashboard with interactive visualizations using JavaScript.
SAP BusinessObjects is a suite of front-end applications that allow business users to view, sort and analyze business intelligence data.
Web Intelligence is a reporting tool in SAP BusinessObjects for creating ad-hoc reports and analysis.
SAP Crystal Reports is a business intelligence application, marketed to small and medium businesses by SAP. It is used to design and generate reports from a wide range of data sources.
SAP Smart Business Cockpits provide pre-configured dashboards for specific business scenarios, they are less customizable compared to the SAP Analytics Cloud analytics designer.
"Which SAP BW/4HANA objects support the feature of generating an external SAP HANA View?" Note: There are 2 correct answers to this question.
- A . Open ODS view
- B . Semantic group object
- C . Composite Provider
- D . BW query .
A,C
Explanation:
Open ODS View: An Open ODS view can generate an external SAP HANA view, which allows access to SAP HANA modeling features, and offers the ability to expose data for reporting purposes directly from the underlying SAP HANA database.
Composite Provider: A Composite Provider in SAP BW/4HANA can generate an external SAP HANA view. A Composite Provider is used to combine data from several InfoProviders using Join or Union operations, and the resulting dataset can be made available as an SAP HANA view.
Semantic group objects: This is not a valid SAP BW/4HANA object that supports external SAP HANA view generation.
BW Query: A BW Query can’t directly generate an external SAP HANA view, it’s rather used for data retrieval from InfoProviders.
You create a transformation from a DataSource to a DataMart Data Store object (advanced) All key figures are updated as Sum.
Which Delta methods indicate that the DataSource provides consistent information for this target? Note: There are 2 correct answers to this question.
- A . ABR
- B . ADD
- C . AIM
- D . AIE
B,D
Explanation:When the key figures are updated as sum in a transformation, the delta methods that would provide consistent information are "ADD" and "AIE".
ADD: The delta method "ADD" supports additive deltas, meaning that the data from the source is simply added to the existing data in the target.
AIE: The delta method "AIE" stands for "After-Image" in which case the most recent version of a record is always transferred during the delta update. The key figure values are overwritten in the target DataStore Object which should not be an issue if the source data is consistent.
ABR and C. AIM are not valid delta methods for SAP BW/4HANA.
What are some of the variable types n a BW query that can use the processing tupe SAP HANA Exit. Note: There are 2 correct answers to this question.
- A . Formula
- B . Text
- C . Charateristic value
- D . Hierarchy node
C,D
Explanation:
Characteristic Value: This variable type allows users to select one or more characteristic values for a specific characteristic.
Hierarchy Node: This variable type allows users to select one or more nodes of a hierarchy.
The processing type SAP HANA Exit lets you define the variable values in the SAP HANA database. This allows for flexibility and performance optimization because the calculation can be pushed down to the HANA database.
A and B. Text are not variable types that can use the processing type SAP HANA Exit.
What are some of advantages of using SAP BW/4HANA business content? Note: There are 2 correct answers to this question.
- A . Automatic generation of Analysis Authorizations during SAP BW/4HANA content activation
- B . Automatic content activation during installation of SAP BW/4HANA
- C . Accelerated SAP BW/4HANA implementation using ready-made models
- D . Ability to combine business content objects with custom-defined objects.
C,D
Explanation:
Accelerated SAP BW/4HANA implementation using ready-made models: SAP BW/4HANA business content provides pre-built models, reports, queries, and so on, which help in reducing the development time and thus accelerating the implementation process.
Ability to combine business content objects with custom-defined objects: SAP BW/4HANA business content is flexible and can be combined with custom objects to meet specific business needs.
A and B are not correct as they do not represent real advantages of using SAP BW/4HANA business content. The automatic generation of Analysis Authorizations or automatic content activation during installation are not standard features of SAP BW/4HANA business content.
"For InfoObject ADDRESS, the High Cardinality flag has been set. However, ADDRESS has an attribute CITY without the high Cardinality flag."
What is the effect on SID values in this scenario?
- A . SID values are not stored for InfoObject ADDRESS
- B . SID values are generated when data for infoObject ADDRESS is loadet
- C . SID values are generated when InfoObject CITY is activated
- D . SID values are generated when InfoObject ADDRESS is activated.
B
Explanation:
High Cardinality flag is used when an InfoObject can potentially have a large number of unique values (SIDs). Setting this flag changes the way these values are handled by the system. Specifically, for InfoObject with High Cardinality set, SID values are generated only when the data is loaded, not during activation. Therefore, the correct option is B. Other statements are not relevant to the scenario described.
In the Web IDE for SAP HANA workspace, you have imported a project including an HDB module with calculation views.
What do you need to do in the project sittings before you can successfully build the HDB module?
- A . Enter an organization
- B . Reset the project type
- C . Assign a space
- D . Define a package
C
Explanation:
In the SAP Web IDE for SAP HANA, before building an HDB module, you must assign a space to the project. Spaces are logical containers in the SAP Cloud Platform where applications and services run. They help to organize development, testing, and production environments. Therefore, option C is the correct answer.
What is required before you can integrate an HDI Calculation View (data category Dimension) into another HDI Calculation View (data category Cube with Star Join) of the same HDI container?"
- A . Create a synonym for the HDI Calculation View (data category Dimension).
- B . Build the design time file of the HDI Calculation View (data category Dimension) to generate a runtime object.
- C . Create a synonym for the HDI Calculation View (data category with Star Join).
- D . Build the runtime object of the HDI Calculation View (data category Cube with Star Join) to generate a design time file.
C
Explanation:
In the SAP Web IDE for SAP HANA, before building an HDB module, you must assign a space to the project. Spaces are logical containers in the SAP Cloud Platform where applications and services run. They help to organize development, testing, and production environments. Therefore, option C is the correct answer.