Special Case: Table Lookup in Table VBKD 
Special Case: Table Lookup in Table VBKD
When you define a table lookup for the table VBKD (Sales document: Business data), data does not have to be present for every item in the sales document. If the item data is no different than the header data, the system does not store it in the item as well. In this case, you can find the valid values in the header data, which is stored in table VBKD under the item number "000000".
Thus, if you want to read characteristic values from VBKD, you always need to define two table lookups.
You want the system to read the field KDGRP (customer group) from table VBKD and enter the value contained there in the temporary field GLOBAL USERTEMP1, so that you can use the customer group to derive other characteristics.
To achieve this, you need to create the following two steps:
Step |
Derivation type |
1 |
Table lookup in table VBKD using the key KAUFN and KDPOS; |
2 |
Table lookup in table VBKD using the key KAUFN and KDPOS. For KDPOS, you define field attributes stating that the constant "000000" should be used here. Then copy KDGRP to GLOBAL USERTEMP1. |
This rule causes the system to first try to read the item data. But since this information is not stored explicitly, the field GLOBAL USERTEMP1 remains blank. Then the system carries out step 2, which reads the header data.
If you have used the field GLOBAL USERTEMP1 for other purposes earlier in the strategy, be sure to clear its content first.