Hierarchy
⤷ BC-CTS-LAN (Application Component) Language Transport
⤷ STRALAN (Package) Language Transport with tp/R3trans
Basic Data
Data Element | LANGUNPACK |
Short Description | Flag - Unpack Packages |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BOOLEAN | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
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 | Unpack |
Medium | 15 | Unpack Package |
Long | 20 | Unpack Package |
Heading | 10 | Unpack |
Documentation
Definition
This flag indicates whether you want the language packages to be unpacked during the import or not.
If this flag is not set (default), the system checks whether the data files for the transport requests in the package are already in the transport directory when it unpacks the package file. If so, they are not unpacked again and this step is skipped. A data file is only unpacked from the package if the system cannot find it in the transport directory.
This reduces the import time for language packages, since packages being imported into multiple systems in the same transport domain only need to be unpacked for the import into the first system in the domain. This option makes sure that unpacked files are used for the other systems in the domain. It also makes sure that any imports running for other systems do not terminate due to opened data files being changed or opened again.
If you set this flag, the transport files needed for the import are always unpacked from the package file before the import. This is not normally necessary.
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in | 46D |