Diagnosis
The naming of event &SYST-MSGV1& in SAP namespace does not correspond toconventions.

System Response
The event cannot be created.

Procedure
The description of an event can only contain uppercase letters, numbersand underscores. Select the name of the event as follows:
Events that should be used for function modules in the process of aBilling Engine Application begin with the name of the object, althoughan underscore can fill up to the first three spaces. One space followsfor the layer, finally three characters for describing the method. Useconsecutive numbering for the last space, beginning with 0. If more thanten events per method are required, replace the number in the last spacewith a letter. Events in TOP templates contain the string 'TOP' from thefourth to the seventh space.
Example: BD_OADD0, PRLPPST0, DL_OGL_A
Events that should be used in reports also begin with the object,followed by an 'R', an identifier for the report, and consecutivenumbering analogous to the conventions for function modules.
Example: DL_RPRC1, BD_RTRFA
Events that should be used in methods for classes, are described in thesame way as events in reports, only using the identifier 'C' (for class)after the object.
Example: BD_CBSP0
Events in service wrappers begin with an underscore, followed by theidentifier for the service (with possibly an underscore for up to threespaces). Finally, as in the case of function modules, a three-digitidentifier and a character/letter for consecutive numbering is added.Specification of a layer is not required.
Example: _PRCDMP1, _ACCM2H0
Events in subscriptions that are not assigned to a service begin withtwo underscores.