So there’s a lot of information missing here to help you. The basics of table fields are:
form A contains a table field and a key that is used for data relationship and filtering of data
form B contains the data that will populate the table field and the key from form A
the qualification of the table field uses A.key=B.key to filter the data (you can also sort the data and select the columns from from B)
thus when you refresh the table field the data is there on form A
so now if you want the user to create the relationship data that is stored in form B then the standard practice is to provide a button which opens a dialog that allows them to add and remove items from/form B. When the dialog is closed you’ll have an action that refreshes the table and shows the data from form B, in The table field on form A.
if you need further help you’ll need to supply more information such As where the source data is, who or how is it entered and related, what the key is and maybe even what they will do with it.
Users enter their requests in the HPD: Help Desk form, there they must select the cause of the claim, the value that the company must reimburse and the name of the person authorizing the payment.
You can create custom form to store this additional reimbursement related information. Create character field for Cause of the claim and attach menu to it. You can configure menu values in 'SYS:Menu Items' form. Have a button and new activelink to add the these additional values to backend custom form. Create table field and point it to this custom form. (qualification would be Incident number = Incident Number).
You can just use the resolution categories for this Which are out of the box and configurable. I don’t see a need for anything custom from your statements So far.