Hierarchy
⤷
⤷
Basic Data
| Data Element | WLANGU |
| Short Description | Requested Language for Business Events of Specified Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SPRAS | |
| Data Type | LANG | Language key |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | T002 |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Language |
| Medium | 15 | Language |
| Long | 20 | Language |
| Heading | 2 | Ln |
Documentation
Definition
Desired language for business events of the business event type entered.
Supplementary Documentation - WLANGU 3000
Use
This refers to the language in which the business events of the required business event type is held.
Procedure
Example
Dependencies
Supplementary Documentation - WLANGU 7000
Use
During bookings, cancellations and rebookings (Transactions PP12, PP13 and PP19):
The field is both an input as well as an output field, depending on how the user enters the required business event:
- by specifying the business event type ID, the business event
language and the required start date and the required start date
-> Business event language is input field
- by directly specifying a business event ID
-> If it is a valid business event ID, the respective business event language of the system is shown
-> Business event language is output field
During pre-bookings (Transaction PP15): Language in which the attendee wants to attend business events of the required type.
This language is stored during pre-booking, the attendee is prebooked on the business event type "in the language".
Procedure
Example
Dependencies
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |