IBM BJ0NJML Integration Guide - Page 274

Default Processing for Translatable Columns, Language Tables

Page 274 highlights

Default Processing for Translatable Columns Default Processing for Translatable Columns When you log in, you can choose a language code other than the base language for the system. In any application, you can then enter language-specific values for columns that are designated as translatable. By default, outbound transactions contain the applicable column values in the language that is associated with the login session. The language values display whether the transaction is initiated by an application or the Data Export feature. For example, if the base language of your system is English, you can log in as a French user and update an item record with a French description. The outbound message contains the item description in French, even when the description also exists in English, or a third language. Language Tables If a database table contains translatable columns, the database contains a corresponding table called L_tablename, for example, ITEM and L_ITEM. The L_tablename table stores the non-base language values for every translated column except the long description. Long descriptions in all languages are in the LONGDESCRIPTION table. To include translated values in the output XML, include the L_tablename and LONGDESCRIPTION objects in the applicable object structures. Provide the base language values as a service input to object structures that have the L_tablename as part of their object definition. Your service input must be in the core object, and all other languages must be in the additional language enabled object. For example, when English is the base language, the ITEM table contains the English description of an item and the L_ITEM table contains the French and German descriptions of that item. The LONGDESCRIPTION table contains the English, French, and German long descriptions. When you add the L_tablename object to an object structure, assign the same value to the transLanguage and baseLanguage attributes. Otherwise, the base language values are not available and are processed for the multilanguageenabled fields. 260 Integration Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330

Default Processing for Translatable Columns
260
Integration Guide
Default Processing for Translatable Columns
When you log in, you can choose a language code other than the base language
for the system. In any application, you can then enter language-specific values for
columns that are designated as translatable.
By default, outbound transactions contain the applicable column values in the
language that is associated with the login session. The language values display
whether the transaction is initiated by an application or the Data Export feature.
For example, if the base language of your system is English, you can log in as a
French user and update an item record with a French description. The outbound
message contains the item description in French, even when the description also
exists in English, or a third language.
Language Tables
If a database table contains translatable columns, the database contains a
corresponding table called L_tablename, for example, ITEM and L_ITEM. The
L_tablename table stores the non-base language values for every translated
column except the long description. Long descriptions in all languages are in the
LONGDESCRIPTION table.
To include translated values in the output XML, include the L_tablename and
LONGDESCRIPTION objects in the applicable object structures.
Provide the base language values as a service input to object structures that have
the L_tablename as part of their object definition. Your service input must be in
the core object, and all other languages must be in the additional language
enabled object.
For example, when English is the base language, the ITEM table contains the
English description of an item and the L_ITEM table contains the French and
German descriptions of that item. The LONGDESCRIPTION table contains the
English, French, and German long descriptions.
When you add the L_tablename object to an object structure, assign the same
value to the transLanguage and baseLanguage attributes. Otherwise, the base
language values are not available and are processed for the multilanguage-
enabled fields.