Diagnosis
In order to find the responsible employees for the correspondingsubscription values via table mapping or a static criteria rule thefield returning the employee keys should be compatible with the dataelement of the employee key.
Employee keys are 32-character identifiers (DDic table fieldSMOMITABT-SFAMITABT, data element SMO_GUID). The specified field has adifferent data type (see Technical Information and the Data Dictionaryfor more information).

System Response
The system cannot find complete employee keys in the specified fieldand therefore the Subscription Generator will not return the expectedlinks between criteria values and employees.
If there are other employee key fields defined in the mappinghierarchy, subscriptions for the employees found will be created.

Procedure
Check whether the subscription generator customizing makes sense. Checkwhether the employee key field indeed contains employee keys. In caseof an error or if you do not need the incompatible employee key field,it should be deleted, especially for performance reasons.
At the moment changes of the criteria rules are not supported. Thesubscription generator has to be recreated. Make sure that the criteriarules are correctly established. 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'.