28.01.2013 Views

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Remember: Schema mapping only applies to references from repository objects to catalog objects. It is<br />

not intended to be used for repository to repository references.<br />

Restriction: You need to map the references of script-based calculation views and procedures manually,<br />

that is, by changing the script.<br />

You can map several authoring schemas to the same physical schema. For example, content objects delivered by<br />

<strong>SAP</strong> refer to different authoring schemas, whereas in the customer system, all these authoring schemas are<br />

mapped to a single physical schema where the tables are replicated.<br />

Remember: The mapping between authoring and physical schema is stored in the configuration table<br />

“_SYS_BI”.”M_SCHEMA_MAPPING”<br />

Note:<br />

● In a system having no schema mapping, the authoring schema is filled 1:1 from the physical schema<br />

otherwise it would not be possible to change the default schema.<br />

● In a system if authoring schema mapping is found, it is checked that whether the current authoring<br />

schema is mapped to the current physical schema as follows: If yes, nothing is done. If not (including<br />

an empty authoring schema case), then the authoring schema is filled. With the backwards mapped<br />

authoring schema if there is a 1:1 mapping i.e. only one authoring schema was found. With this we<br />

simplify the mapping table in customer systems because even for enhancements the content schema<br />

is kept and no additional mapping must be introduced if the customer transports from development<br />

to production With the physical schema in case no or more than one authoring schemas are found.<br />

This indicates that the customer has changed the schema-dependent parts and that therefore his<br />

physical schema is stored also in the authoring schema.<br />

Example use case: Lets assume we have only <strong>SAP</strong>_ERP -> ERP in the mapping table and an analytic<br />

view having defaultSchema = <strong>SAP</strong>_ERP. Let's assume the customer changes the defaultSchema to<br />

CUS. Since CUS has no mapping the authoringSchema of the defaultSchema is set to CUS as well.<br />

Then the customer changes the defaultSchema back to ERP. A 1:1 mapping for ERP is found<br />

(<strong>SAP</strong>_ERP) and then the authoring schema is set back to <strong>SAP</strong>_ERP.<br />

1. In the Quick Launch tab page, choose Schema Mapping.<br />

2. Choose Add.<br />

3. Enter the authoring schema and physical schema that need to be mapped.<br />

4. Choose OK.<br />

<strong>SAP</strong> <strong>HANA</strong> <strong>Developer</strong> <strong>Guide</strong><br />

Setting Up the Analytic Model<br />

P U B L I C<br />

© 2012 <strong>SAP</strong> AG. All rights reserved. 101

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!