How a Definition-Driven ERP Layers Company-Specific Customizations Over Shared Definitions

An ERP used out of the box is rare, since the same definitions ship to companies with very different needs, such as renaming a field or adding a validation check. The approach described places customization as a data layer over standard definitions, selected by a customization id stored on each company record. Only five of thirteen definition kinds can be customized, and two of them can never be changed through this layer. Customizations live in a separate folder per id, so companies sharing a group can point to the same id while others maintain their own. The layer addresses altering how an existing package behaves, while entirely new programs requested by a customer fall outside this mechanism.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.




Discussion (0)
Log in to join the discussion and vote.
Log in