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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Related Links<br />

○ In the text boxes Version, Support Package Version, and Patch Version enter integer values only; the<br />

combined values define the version of the delivery unit that is currently being developed. For<br />

example, enter Version = 1, Support Package Version = 3, and Patch Version = 17 to specify that the<br />

current version of your delivery unit is 1.3.17. The version number is transported to other systems<br />

with every DU transport.<br />

Note: The numbers you enter here refer to the application component that you are<br />

developing; the numbers do not refer to the patch or service-pack level deployed on the <strong>SAP</strong><br />

<strong>HANA</strong> server.<br />

○ The PPMS ID is the product ID used by the <strong>SAP</strong> Product and Production Management System<br />

(PPMS).<br />

Note: Customers and partners should leave the PPMS ID text box empty.<br />

Maintaining the Delivery-Unit Vendor ID [page 35]<br />

In <strong>SAP</strong> <strong>HANA</strong>, the vendor ID is used primarily to define the identity of the company developing a software<br />

component that they plan to ship for use with <strong>SAP</strong> <strong>HANA</strong>. If you want to create a delivery unit, it is a<br />

prerequisite to maintain a vendor ID in your system.<br />

<strong>SAP</strong> <strong>HANA</strong> Delivery Unit Naming Conventions [page 36]<br />

In <strong>SAP</strong> <strong>HANA</strong>, conventions and guidelines exist for the naming of delivery units (DU). The delivery unit is the<br />

vehicle that lifecycle management (LCM) uses to ship one or more software components from <strong>SAP</strong> (or a<br />

partner) to a customer. The DU is also the container you use to transport application content in your system<br />

landscape.<br />

4.2 Using <strong>SAP</strong> <strong>HANA</strong> Projects<br />

Projects group together all the artifacts you need for a specific part of the application-development environment.<br />

Before you can start the application-development workflow, you must create a project, which you use to group<br />

together all your application-related artifacts. However, before you create a project, you must create a repository<br />

workspace, which enables you to synchronize changes in local files with changes in the repository. As part of the<br />

project-creation process, you perform the following tasks:<br />

1. Create a development workspace.<br />

The workspace is the link between the <strong>SAP</strong> <strong>HANA</strong> repository and your local filesystem, where you work on<br />

project-related objects.<br />

2. Create a project.<br />

Create a new project for a particular application or package; you can use the project to collect in a convenient<br />

place all your application-related artifacts.<br />

3. Share a project.<br />

Sharing a project enables you to ensure that changes you make to project-related files are visible to other<br />

team members and applications. Shared projects are available for import by other members of the<br />

application-development team.<br />

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

Setting Up Your Application<br />

P U B L I C<br />

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

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

Saved successfully!

Ooh no, something went wrong!