Dear all,
I am wondering about the meaning of the above setting in the EH type customizing. This is not taken into account in Event Message Processing (because the EVM Extension Table to be used is derived from the mapping profile in this case) - so what is it used for?
Thanks, Michael
Hi Michael,
as i remember this is needed for querying data. Otherwise it would not be known which EVM Extension table name is needed to query the data. Therefore it must be guaranteed that you have one EVM Extension assigned to your EH Type. Otherwise querying in the way it is done from the BAPis would not be possible.
Best regards,
Steffen
Hi Steffen,
thanks for your quick answer! So if I have several event messages which have been processed for the same EH, but using different EVM extension tables (which is perfectly possible, because the EVM extension table depends on the tracking ID codeset used in the event message), I would get problems in querying event handlers using fields of the extension tables which are not in the EH type customizing. Apart from that, I don't have to expect any other problems.
Is my understanding correct?
Regards, Michael
Hi Michael,
you should only use one EVM Extension table per EH Type. I'm not sure if you can display the extension entries if you have different tables. Especially in the table view i expect problems. But i have never tried this.
Best solution is to add all fields you need to one table.
Best regards,
Steffen