We used to do that here, but it became far too onerous to keep all the documentation up to date. Now, we only really document large config changes. We make note of things like:

• Functional area of the change (i.e. does it relate to receiving, picking, putaway, etc).
• Who requested the change?
• Who approved the change?
• What's the purpose of the change? I.e. what problem did we have that the change solves?
• Screenshots of any relevant UI screens or database snapshots from before and after the change.
• Any "weird" things about the change, which may relate to bugs in the system or things that are very specific to our own configuration. E.g. we bastardize the system a lot to get it to do things that it wasn't necessarily designed to do out-of-the-box, so if we've re-purposed a particular database field or something, we'd make note of that.

Depending on the scope of the change, we may also document what changes occurred within the database, i.e. "if we make this small change in this UI screen, what database tables get touched?"