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.

4. Download translated text to the <strong>SAP</strong> <strong>HANA</strong> repository<br />

13.5.1 <strong>SAP</strong> <strong>HANA</strong> Delivery-Unit Translation Details<br />

The <strong>SAP</strong> <strong>HANA</strong> repository includes features for translating package-related metadata texts. If you plan to<br />

translate the contents of the new delivery unit you create, you must maintain translation details.<br />

Translation details provide a brief overview of the type and current status of the text objects to be translated, for<br />

example, by specifying the technical area of the new delivery unit and indicating the current status of translation<br />

texts.<br />

Note: Translation text can include the following elements: UI strings (menus, dialog titles), error<br />

messages, and documentation, amongst other things. Package names and descriptions are also relevant<br />

for translation purposes as are the names and descriptions of database views, tables, columns, and so on.<br />

To make things easier for the translation team, you should maintain the following metadata for translation<br />

purposes; the metadata must be maintained at the package level:<br />

● Terminology domain (mandatory)<br />

The technical/product area with which your delivery unit (application) is associated, for example: AC<br />

(Accounting General), FI (Financial Accounting), or PP (Production Planning and Control). This enables<br />

translator teams to assign work to the most suitable experts, and allows the translators to make use of<br />

existing terminology databases. The terminology domain is used by <strong>SAP</strong> internal translation systems.<br />

● Text collection (mandatory)<br />

The name space for the text objects in the translation system. Technically, you can use any value, but the<br />

text-collection name space is similar to the package namespace used in <strong>SAP</strong> <strong>HANA</strong>, for example:<br />

"sap.hana.xs.docs". The value assigned to the Text collection field is used by <strong>SAP</strong> internal translation systems.<br />

● Hint<br />

An optional field that customers and partners can use to pass on notes concerning the text objects tagged for<br />

translation.<br />

● Text status<br />

An optional field that customers and partners can use to pass on information indicating the current stage in<br />

the translation-review process of the text objects, for example: "New", "In review", "Reviewed", "Approved",<br />

"Published", and so on.<br />

13.5.2 Maintaining Translation Details<br />

Translation details provide a brief overview of the type and current status of the text objects to be translated, for<br />

example, by specifying the technical area of the new delivery unit and indicating the current status of translation<br />

texts.<br />

If you plan to translate the contents of a delivery unit, you must maintain translation details. You can maintain the<br />

translation details when you create a new delivery unit or for existing delivery units. It is mandatory to maintain<br />

the following translation-related details:<br />

● Terminology domain<br />

The technical/product area with which your delivery unit (application) is associated, for example: AC<br />

(Accounting General), FI, or PP.<br />

● Text collection<br />

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

Implementing Lifecycle Management<br />

P U B L I C<br />

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

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

Saved successfully!

Ooh no, something went wrong!