Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-BM (Application Component) Batches⤷
VBDRV (Package) Batch Derivation
Basic Data
| Data Element | RBAND |
| Short Description | Derivation: Boolean selection rule AND |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | AND |
| Medium | 15 | AND |
| Long | 20 | AND |
| Heading | 3 | AND |
Documentation
Definition
Selection rule "logical AND" for determining values for several senders.
If you use this rule, you should also define which values the derivation is to interpret as TRUE and which as FALSE. If you do not do this, blank is interpreted as FALSE and every other value is interpreted as TRUE.
The result is determined as follows:
If all sending batches have the value that you stored as TRUE (or they are not blank), the result also receives the value that you stored for TRUE. (If you have not stored a value, the system uses 1 for numeric fields and "X" for alphanumeric fields in the result for the value TRUE).
If at least one sender attribute has a different value (or is blank), the result has the value that you stored for FALSE. (If you have not stored a value, the result is initialized).
Example
You have defined a characteristic with both possible values "OK" and "NOK". A batch is only evaluated as "OK" if all received batches have the value "OK". All received batches must be evaluated.
For this example, you have to set the selection rule "UND" with the value "OK" in the field TRUE, "NOK" in the field FALSE, and the 'Not empty indicator'.
History
| Last changed by/on | SAP | 19991110 |
| SAP Release Created in |
