Complex keys must be configured when the Object ID reference is not entirely contained within the requesting IDoc. When such keyword updates are sent, BIC has the capacity to assemble Object IDs from a combination of XPaths, SAP Queries, and Constants. Our example will be from the TOA01 table. In some Object ID a number will be followed by 20 spaces and then another number. Here is an example: 0090034060 000001442.
When a Object ID like this is found, multiple tables will need to be queried in order to obtain the correct Object ID. In this example, the first number is from the FIDCCP02/IDOC/E1FIKPF/XBLNR IDoc field, followed by 20 spaces. The second number is taken from the OPTARCNR column within the NAST table.
It is not recommended to configure a NAST query containing an OR statement because doing so can return inconsistent results. Instead, it is recommended to create multiple object keys.
To configure a complex key: