IBM BJ0NJML Integration Guide - Page 222

A Po Line., Maxvars.mxsysid.

Page 222 highlights

Conditions and Evaluations The following table lists the possible types of comparison fields that you can use in the field comparisons. Comparison of an alphanumeric source field is case sensitive. Field Integration control Use Compare the value in the specified field with the values in a list or value integration control. If a list control has multiple matching values, the evaluation is true. The true evaluation occurs only if the field value matches any one of the values in the list control. Value Example: Validate the STATUS of a purchase order. The current value in a STATUS field is WAPPR and the possible acceptable values that satisfy the condition are in a list control called POSEND. The values in POSEND are WAPPR, APPR, and CLOSE. If the evaluation type is EQUALS, the evaluation returns a true value. Compare the value in the specified field with a predefined value. This option is available for user-defined conditions. Regardless of the locale setting of the application server or the database, all decimal fields must use a period (.) as the decimal placeholder. Numbers to the left of the placeholder are not formatted. This format applies to inbound and outbound data. For example, $1,738,593.64 must be in the following format: 1738593.64. MAXVAR Example: A processing rule compares the value of the POLIN1 field with the value SPARE. If the evaluation type is EQUALS and the two values are the same, the evaluation returns a true value. Compare the value in the specified field with the value in a system control (a value in the MAXVARS database table). Boolean Comparison field Evaluate the OWNERSYSID on any enterprise service or publish channel to determine if it is the same as MAXVARS.MXSYSID. Compare the value in the specified field with a Boolean value (true or false). Compare the value in the specified field with another field in the same object. Object relationship, and field Example: Compare the GLDEBITACCT value and GLCREDITACCT value on a PO line or a journal entry to determine if they are equal. Compare the value in the specified field with a field in a different object. Example: Check the OWNERSYSID of inventory in the system for the item-storeroom values on a receipt line or a PO Line. 208 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

Conditions and Evaluations
208
Integration Guide
The following table lists the possible types of comparison fields that you can use
in the field comparisons. Comparison of an alphanumeric source field is case
sensitive.
Field
Use
Integration control
Compare the value in the specified field with the values
in a list or value integration control. If a list control has
multiple matching values, the evaluation is true. The true
evaluation occurs only if the field value matches any one
of the values in the list control.
Example
: Validate the STATUS of a purchase order. The
current value in a STATUS field is WAPPR and the
possible acceptable values that satisfy the condition are
in a list control called POSEND. The values in POSEND
are WAPPR, APPR, and CLOSE. If the evaluation type is
EQUALS, the evaluation returns a true value.
Value
Compare the value in the specified field with a
predefined value. This option is available for
user-defined conditions.
Regardless of the locale setting of the application server
or the database, all decimal fields must use a period (.) as
the decimal placeholder. Numbers to the left of the
placeholder are not formatted. This format applies to
inbound and outbound data. For example, $1,738,593.64
must be in the following format: 1738593.64.
Example
: A processing rule compares the value of the
POLIN1 field with the value SPARE. If the evaluation
type is EQUALS and the two values are the same, the
evaluation returns a true value.
MAXVAR
Compare the value in the specified field with the value in
a system control (a value in the MAXVARS database
table).
Evaluate the OWNERSYSID on any enterprise service or
publish channel to determine if it is the same as
MAXVARS.MXSYSID.
Boolean
Compare the value in the specified field with a Boolean
value (true or false).
Comparison field
Compare the value in the specified field with another
field in the same object.
Example
: Compare the GLDEBITACCT value and
GLCREDITACCT value on a PO line or a journal entry to
determine if they are equal.
Object
relationship, and
field
Compare the value in the specified field with a field in a
different object.
Example
: Check the OWNERSYSID of inventory in the
system for the item-storeroom values on a receipt line or
a PO Line.