4. Descripción general del modelo
4.2 Planeación de la implantación
4.3.3 Uso de los datos en la operación
You can set preferences for your Eclipse workspace to set up the default settings that the system uses whenever you log on.
1. Choose Window Preferences Modeler
Note
You can also set the preferences choosing Quick Launch Manage Preferences
2. Identify the required preference and perform the corresponding substeps from the table below:
Requirement Preference Substeps
To specify the structure of content packages in the Navigator view
Content Presentation Hierarchical - to view the package structure in a hierarchical manner such that, the child folder is inside the parent folder. Flat - to view all the packages at the same level for example, sap, sap.ecc, sap.ecc.ui.
Show Object Type Folders - to group together similar objects in a package such as attribute views in the Attribute View package.
To set the preferences for loading data using flat file
Data From Local File 1. Browse the location to save error log files for data load using flat files.
2. Enter the batch size for loading data. For example, if you specify 2000 and a file has records of
Requirement Preference Substeps
10000 rows the data load will happen in 5 batches.
3. Enter a decision maker count that will be used to propose data types based on the file. For example, enter 200 if you want the proposal to be made based on the 200 rows of file data.
To set the default value for the client that will be used while previewing model data
Default Model Parameters Select the client from the Default Client drop-down list.
To enforce various rules on objects
Note
Enforcing validation rules with severity “Error” are mandatory.
Validation Rules Select the required rules to be applied while performing object validation.
To determine the numbers of rows to be displayed in a page
Data Preview Select the maximum rows for data
preview as required.
To specify a location for job log files Logs 1. Expand the Logs node.
2. Select Job Log.
3. Browse the location where you want to save the job log files.
To enable logging the repository calls and specify location for repository log files
Logs 1. Expand the Logs node.
2. Select Job Log.
3. Select true from the drop-down list.
4. Browse the location where you want to save the repository log files.
To enable search for the attributes used in the views
Search Options Select Enable Search Attributes. .
To allow lower case alphabets for attribute view, analytic view, calculation view, procedure and analytic privilege names
Case Restriction Deselect the Model name in upper case checkbox.
Note
After changing the preferences make sure you choose Apply and OK.
7.1.2 Configuring the Import Server
In order to load data from external sources to SAP HANA you need to establish a connection with the server. To connect you need to provide the details of BusinessObjects Data Services repository and ODBC drivers. Once the connection is established you can import the tables definition and then load the data into table definitions.
1. In the Quick Launch tab page, choose Configure Import Server.
2. Enter the IP address of the server from which you want to import data.
3. Enter the repository name.
4. Enter the ODBC data source, and choose OK.
7.1.3 Importing Table Definitions
One of the ways to create tables to load source system data into SAP HANA is to import the table definitions from the source system.
You have configured the SAP HANA modeler for importing metadata using the Data Services infrastructure.
Use this procedure to import table definitions (metadata) from a source system to load source system data into SAP HANA. You can point to these table definitions for creating various content models such as attribute, analytic, and calculation views.
Based on your requirements, use one of the following approaches:
● Mass Import: To import all table definitions from a source system. For example, you can use this approach if this is a first import from the given source system.
● Selective Import: To import only selected table definitions from a source system. For example, you can use this approach if there are only few table definitions added or modified in the source system after your last import.
1. If you want to import all table definitions, do the following:
a) In the File menu, choose Import.
b) Expand the SAP HANA Content node.
c) Choose Mass Import of Metadata, and choose Next.
d) Select the target system where you want to import all the table definitions, and choose Next.
e) In the Connection Details dialog, enter the operating system user name and password of the target system.
f) Select the required source system, and choose Finish.
Note
If the required system is not available from the dropdown list, you need to contact your administrator.
2. If you want to import selective table definitions, do the following:
a) In the File menu, choose Import.
b) Expand the SAP HANA Content node.
c) Choose Selective Import of Metadata, and choose Next.
d) Select the target system where you want to import the table definitions, and choose Next.
e) Select the required source system.
Note
If the required system is not available from the dropdown list, you need to add the new source system using Manage Connections.
f) In the Type of Objects to Import field, select the required type, and choose Next.
g) Add the required objects (tables or extractors) that you want to import.
Note
If you want to add dependent tables of a selected table, select the required table in the Target panel, and choose Add Dependent Tables in the context menu.
h) Select the schema into which you want to import the metadata.
i) If you selected object type as extractor, select the package into which you want to place the corresponding objects.
j) Choose Next, then review and confirm the import by choosing Finish.
If the source object is a table or non V-type extractor, the system creates physical tables and stores them in the selected schema. However, if the source object is a V-Type extractor, the system creates content models and stores these models in the selected package, and the underlying physical tables in the schema.
7.1.3.1 Configuring Data Services for Metadata Import
Use this procedure to enable the SAP HANA modeler to import table definitions from the source system using the Data Services infrastructure.
1. Set the Passphrase
a) Log on to the Central Management Console of SAP BusinessObjects Enterprise (BOE).
b) Choose Manage Applications Data Services Application Settings .
c) In the Encryption Passphrase field, enter the passphrase that you have been using for the SAP HANA studio, and choose Save.
d) Restart the TOMCAT and BOE services.
2. Disable Session Security
a) Log on to the Data Services Management Console.
b) Choose Administrator.
c) In the Navigator view panel, choose Web Services.
d) Choose the Web Services Configuration tab page.
e) Select the Import_Repo_Object checkbox to save the connection details.
f) Select Disable Session Security from the dropdown menu, and choose Apply.
3. Creating a Data Source
a) Go to Start Control Panel Administrative Tools . b) Choose Data Sources (ODBC).
c) Choose the System DSN tab page, and choose Add.
d) Select HDBODBC from the driver list, and choose Finish.
e) Enter a name and description for the data source.
f) Enter server details.
Note
The format in which you need to enter details is <<host>:3<instance number>15>. For example, abc2012.wdf.sap.corp:30115.
g) Enter the required database details in the format, <<SID><instance number>>. For example, M4701.
h) Choose Connect.
7.1.3.2 Managing Source System Connections
Use this procedure to add or manage a source system connection that is required to import table definitions.
7.1.4 Loading Data into Tables
● If you are using the Load Controller or Sybase Replication Server infrastructure, make sure that you have imported all table definitions into the SAP HANA database. For more information, see Importing Table Definitions.
● If you are using the SLT component, the source system(s), target system and the target schema, are configured by the administrator during the installation.
Use this procedure to load data into your table definitions. Depending on your requirements, you can perform the following:
● Initial Load - to load all data from a source SAP ERP system into the SAP HANA database by using Load Controller or SAP Landscape Transformation (SLT). This is mostly applicable when you are loading data from the source for the first time.
● Data Replication - to keep the data of selected tables in the SAP HANA database up-to date with the source system tables by using SyBase Replication Server or SAP Landscape Transformation (SLT).
1. In the Quick Launch tab page, choose Data Provisioning.
2. If you are using SLT-based replication, choose Source.
3. Choose Load (for initial load) or Replicate (for data replication) as appropriate.
4. Select the required tables to load or replicate data in any of the following ways:
○ Search for the required tables.
1. Select the table from the list, and choose Add.
2. If you want to save the selected list of tables locally for future reference, select the Export selected tables checkbox, and specify the target location.
○ Load the list of tables from a local file as follows:
1. Choose Load from file.
2. Select the file that contains the required list of tables.
Note
The supported file type is .csv.
5. If you are using the load controller infrastructure, choose Next and enter the operating system user name and password.
6. Choose Finish.
7.1.4.1 Suspending and Resuming Data Load
If you are using SLT- based replication, you can choose to stop data replication temporarily for a selected list of tables, and later resume data load for these.
1. In the Quick Launch tab page, choose Data Provisioning.
2. Select the source system for which you want to suspend or resume data load.
3. Choose Suspend or Resume as required.
4. Select the tables, and choose Add.
5. Choose Finish.
7.1.4.2 Uploading Data from Flat Files
Use this procedure to upload data from flat files available in a client file system, to SAP HANA database.
● If the table schema corresponding to the file to be uploaded already exists in the SAP HANA database, the new data records are appended to the existing table.
● If the required table for loading the data does not exist in the SAP HANA database, create a table structure based on the flat file.
The application suggests the column names and data types for the new tables and allows you to edit them. The new table always has a 1:1 mapping between the file and table columns. The application does not allow you to overwrite any columns or change the data type of existing data. The supported file types are .csv, .xls, and .xlsx.
1. In the File menu, choose Import.
2. In the Select an import source section, expand the SAP HANA content node.
3. Select Data from Local File, and choose Next.
4. In the Target System section, select the target system to which you want to import the data using the flat file, and choose Next.
5. In the Define Import Properties page, browse and select the file containing the data you want to load.
6. If you have selected a CSV file, select a delimiter.
Note
A delimiter is used to determine columns and pick the correct data from them. In a csv file, the accepted delimiters are ',', ';' and ':'.
7. If you have selected an .xls or .xlsx file, select a worksheet.
8. If you want to load the data into a new table, select the New option and perform the following substeps:
a. Choose Next.
b. On the Manage Table Definition and Data Mapping screen, map the source and target columns.
Note
○ Only 1:1 column mapping is supported. You can also edit the table definition by changing the data types, renaming columns, adding or deleting the columns, and so on.
○ You can choose to map the source and target columns using the Auto Map option. If you choose the one to one option, then first column of the source is mapped to the first column at the target. If you choose the option Map by name, the source and target columns with the same name are mapped.
9. If you want to append the data to an existing table, select the Existing option and perform the following substeps:
a. Choose Next.
b. On the Manage Table Definition and Data Mapping screen, map the source and target columns.
10. If you want to provide a constant value for a column at the target, perform the following substeps:
a. Right-click the column.
b. From the context menu, choose Make As Constant.
c. In the Constant dialog box, enter a value, and choose OK.
Note
You can set a column to constant if it is not mapped to a source column.
11. To provide a default value for a column at the target, enter a value in the Default Value column.
12. Choose Finish.
7.1.5 Copying Content Delivered by SAP
You have the following privileges:
● REPO.READ for the source package.
● REPO.MAINTAIN_NATIVE_PACKAGES and REPO.EDIT_NATIVE_OBJECTS for the root package.
Use this functionality for one of the most common scenarios, that is, to copy the standard content shipped by SAP or an SAP partner to your local package to meet your modeling and reporting use cases. For example, from sap.ecc.fin to customer.ecc.fin.
Tip
We recommend you copy the content shipped by SAP or an SAP partner to your local package to avoid overwriting your changes during the subsequent import.
You can also use this procedure to copy objects, other than SAP-shipped in a package to other packages in the same system based on your business use case.
Caution
If you copy an object but not its dependent objects (if any), the copied object in the target package will have references to the dependent objects in the source package.
To copy the objects, you need to map the source root packages to the target root packages. You need to activate the copied objects in the target package to consume them for reporting purposes.
Restriction
For script-based calculation views and procedures, even if you copy the dependent objects, you need to change the script manually and adjust the dependent object references.
1. In the Quick Launch tab page, choose Mass Copy.
2. To create a mapping between the source package and the target package, perform the following substeps:
a) Choose Add.
b) Select a source package and a target package, and choose Next.
Tip
If you want to create more package mapping, select the source and target packages as required.
c) Select the required objects, and choose Add.
3. Choose Next to view the summary.
Tip
You can deselect an object to avoid copying it to the target package.
4. Choose Finish to confirm content copy.
7.1.6 Mapping the Authoring Schema to the Physical Schema
Schema mapping is done when the physical schema in the target system is not the same as the physical schema in the source system, usually in a transport scenario. The schema mapping is maintained via a mapping table.
You use this procedure to map the authoring schemas to the physical database schemas in the target system to access and deploy the transported objects.
A physical schema is the schema in which the tables are available. It may differ in the source and target systems.
An authoring schema (logical schema) is the physical database schema in the source system with which the content objects are created.
Content object definitions are stored in the repository, and contain references to the physical database schemas.
When you copy the content objects to a different system, for example, from an SAP system to a customer system, or between customer systems, the object definition still refers to the physical database schemas at the source. To resolve this, you use schema mapping.
Remember
Schema mapping only applies to references from repository objects to catalog objects. It is not intended to be used for repository to repository references.
Restriction
You need to map the references of script-based calculation views and procedures manually, that is, by changing the script.
You can map several authoring schemas to the same physical schema. For example, content objects delivered by SAP refer to different authoring schemas, whereas in the customer system, all these authoring schemas are mapped to a single physical schema where the tables are replicated.
Remember
The mapping between authoring and physical schema is stored in the configuration table
“_SYS_BI”.”M_SCHEMA_MAPPING”
Note
● In a system having no schema mapping, the authoring schema is filled 1:1 from the physical schema otherwise it would not be possible to change the default schema.
● In a system if authoring schema mapping is found, it is checked that whether the current authoring schema is mapped to the current physical schema as follows: If yes, nothing is done. If not (including an empty authoring schema case), then the authoring schema is filled. With the backwards mapped authoring schema if there is a 1:1 mapping i.e. only one authoring schema was found. With this we simplify the mapping table in customer systems because even for enhancements the content schema is kept and no additional mapping must be introduced if the customer transports from development to production With the physical schema in case no or more than one authoring schemas are found. This indicates that the customer has changed the schema-dependent parts and that therefore his physical schema is stored also in the authoring schema.
Example use case: Lets assume we have only SAP_ERP -> ERP in the mapping table and an analytic view having defaultSchema = SAP_ERP. Let's assume the customer changes the defaultSchema to CUS. Since CUS has no mapping the authoringSchema of the defaultSchema is set to CUS as well. Then the customer changes the defaultSchema back to ERP. A 1:1 mapping for ERP is found (SAP_ERP) and then the
authoring schema is set back to SAP_ERP.
1. In the Quick Launch tab page, choose Schema Mapping.
2. Choose Add.
3. Enter the authoring schema and physical schema that need to be mapped.
4. Choose OK.
Example
Consider a source system, SAP, with an information object, AV1. This refers to the table MARA in the SAP_ERP physical database schema. There is a target system, Customer, with the physical database schema EMEA.
After you import content, the object AV1 cannot be activated in the Customer system, since it still refers to SAP_ERP schema.
AV1 in the Customer system currently refers to SAP_ERP. To be able to activate the object, you need to modify the mapping of AV1 in the Customer system.
To do this, a mapping is created in the target system Customer between the authoring and physical schema as follows:
Authoring Schema Physical Schema
SAP_ERP EMEA
7.1.7 Generating Time Data
For modeling a business scenario that requires time dimension, you can populate time data in the default time-related tables present in _SYS_BI schema, for example while creating time attribute views. You can choose to
For modeling a business scenario that requires time dimension, you can populate time data in the default time-related tables present in _SYS_BI schema, for example while creating time attribute views. You can choose to