Diagnosis
For a dynamic mapping criteria rule for a subscription generatorentries defining the dynamic mapping have to be established. For adynamic mapping criteria rule you have to provide:

• at least two tables you want to define the dynamic mapping for


• the mapping conditions between the tables


• in the first table the field from which the criteria value should be
read

• in any of the linked tables fields from which to read the keys of
responsible employees. Employee keys can be read from more than onetable in the defined table hierarchy. For performance reasons it isrecommended to include as few tables as possible.

• optionally, for any table in the hierarchy: static where conditions on
table fields
In the table mapping for the given criteria field (see TechnicalInformation) no field for the employee key value has been specified inthe last table in the table mapping hierarchy. The last table in thetable mapping may be unnecessary.

System Response
There is an unnecessary table at the end of the mapping hierarchy. Thisis not an error (if at another place employee keys are returned).However, the design used is unsuitable for performance reasons.

Procedure
Try to keep the table mapping as short as possible. If the last entryis unnecessary you should consider to remove it.
At the moment changes of the criteria rules are not supported. Thesubscription generator has to be recreated. Make sure to set up thedynamic table mapping correctly. For more information refer to thedocumentation.
Always create and test subscription generators on your test system. Ifeverything works correctly, transport the generator to the targetsystems.
After creation, transport (if necessary), and activation of the newsubscription generator on the target client, the invalid subscriptiongenerator can be set to status 'To Be Deleted'.