Hi La-Qa,
if you need to maintain these records on a regular basis, you could use Web Screen Painter to create a new list form and detail form for the zcr_module table, and add an entry to the Administration menu tree (e.g. under 'Service Desk / Application Data / Codes') so that you can add / edit records as needed.
Best practice when creating a reference table is to include an 'active' indicator (often labelled 'delete_flag' - look at a table such as 'crs' in WSP to see how to implement that), so that you can deactivate records that you don't want any more. Deleting a record from a reference table risks leaving a broken link from the table that references it, with the possibility that a SQL join against the reference table will give a misleading answer at some time in the future.
SQL is not the ideal way to add reference table data, as a new record inserted using SQL will not be given the next 'id' value automatically, whereas pdm_load '-i' and a detail form will both handle that for you. But SQL can sometimes be useful, e.g. for a bulk update. After updating a table with SQL, run 'pdm_cache_refresh -t <table name>' to update SDM's cached values, or restart the Service Desk Manager service.
To sum up, you have (at least) three options for maintaining your reference table - pdm_load, list and detail forms and
SQL - and SQL is usually the last preference.
Regards,
James