Summary for Non-Technical Readers

RZP now has another concrete codebook working: cost and revenue accounts. This is not just a list of values on the screen, but a working view where users can edit definitions, open record detail, search, and launch help at the right place in the application.

Codebooks like this are part of everyday work in an ERP system. That is exactly why they matter for the migration. The new application has to do more than move the data; it also has to preserve the way users work with that data.

The current demo confirms that the RZP conversion continues to move from static form display toward genuinely usable functions. Details will still be refined, but the practical flow of working with the codebook is already visible.

What the Demo Shows

The video shows the working codebook of cost and revenue account definitions. The user works with a list of records, can edit values in it, and can move into the detail of a selected item. The record detail is not only a passive preview; it is another place where the data can be edited.

The demo also includes search. This is essential in codebooks, because users usually do not want to browse the full list. They need to quickly find a specific definition and check or adjust its settings.

Another important element is context-sensitive help. The application opens the help file directly on the relevant page, so the user does not get only generic documentation, but help tied to the specific part of RZP they are currently using.

The cost and revenue accounts codebook in RZP: definition editing, record detail, search, and context-sensitive help.

Why It Matters

Codebooks often look like a simple part of a system, but in practice they combine several kinds of behavior at once: list work, editing, validation, record detail, search, and integration with help. If the migrated modules are to be usable in real work, these small everyday scenarios have to work reliably.

For RZP, this is another confirmation that the new version is not becoming only a visual copy of the original application. It is gaining parts that already perform concrete tasks and move closer to the user's everyday work in the original system.

Home