Very generic naming of objects might cause clashes

[larshp]

code-pal has some objects with names that are very generic, like:
ycx_entry_not_found, y_alv_events, y_demo_failures

suggest introducing a naming scheme that reduces the possibility of name clashes in customer systems

[lucasborin]

Yeah, it would be good to have a default prefix on it all.

How about YPAL_ for the database, and Y_PAL_ for the ABAP?
(Y_PAL_IF_*)

Probably, it will require the renaming of the Checks:
Y_PAL_CHECK_<name>

And it will impact the current existing variants and profiles. Hm...

[larshp]

yea, and note that abaplint can help enforcing the naming pattern