SAP HANA Developer Guide - Get a Free Blog

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.
6.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.
100
P U B L I C
© 2012 SAP AG. All rights reserved.
SAP HANA Developer Guide
Setting Up the Analytic Model