SAP Learning Journey

Translating Event Content

Objectives
After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Understand how event content can be translated

Translation of Event Content

"Now that we have our content built in our event, I wanted to ask, do you have any non-English speakers that will be participating in the auction?"

"I do not for this laptop auction, but I will need to know how to do this for our future, global auctions. Can you show me the process?"

"To put it plainly, translations need to be added manually. Project Owners key in a lot of information in the base language which does not get translated automatically. You will need to enter the translation to the content that you build and the field entries for each language."

How to Translate Event Content?

Prerequisites

To be able to add or modify translations in the sourcing event, you must be a member of the Translator group.

Context

Translating event content in additional languages enables participants and team members from different locales to view translations in their preferred languages.

Procedure

  1. To enter translations for field values, click the Translations link associated field.

    To add translations to the event title, click on the title. Then click the Translations link associated with it.

    • On the resultant popup, you can see the field value in the base language and placeholders for translations in additional languages. Enter the translations in the placeholders for the languages of your choice.

      Note: You don't have to enter translations for all available languages.

    • Save your changes.
  2. To translate content, select Translate under the Actions menu once the content is created in the base language. Within the Content Translation page, choose the Translate Language in the drop-down that you wish to translate to. You will need to manually add translations for the empty boxes, and revise the prepopulated text boxes.

Considerations

  1. Translated event content is available only if translations are added in the language selected by users as their default locale preference.
    1. To verify the language settings, users can select the profile icon and go to Preferences ＞ Change default locale and currency.
    2. If translations aren't available in their preferred language, information is shown in the base language of the sourcing event.
  2. Translations can be added at the template level or the event level.
    • Example:

      If a template selected for a sourcing event has translations available in the preferred language of a user working on the event, the user is able to see the translated content in the event.

  3. Material master data retrieved from an external system is not translatable and shown read-only.

For a demonstration on event translations, watch this video.

Event Summary

"We have reached the final step of the event creation. The Summary step allows you to review all event settings, project header field values, and overall outline before publishing your event."

If errors are present within the event settings, a warning message is displayed at the top of the page, and the Publish button is grayed out. Event owners can return to any of the event creation steps and correct the error.

"I want to change the title of my event. I see under the Actions menu that there is an option to edit the overview page with the header fields. I want to go back and change the title and add more specifics and description."

Step 1: Edit Overview

Go to Actions ＞ Edit Overview.

Step 2: Change Values

You can edit fields such as Event Title and Description, Region and Commodity, or you can change your mind about the event being a test. There are, however, values that can not be changed after event creation. Among these: the template the event is based on, event type and base language.

Step 3: Validate Changes

Select OK to validate your changes and return to theSummary page.

Log in to track your progress & complete quizzes