Hi Jacob,
1)
Since you moved ZTREQ_CREATED to Event Type, you can directly add the TOR_TYPE here itself in
CT_TRACKPARAMETERS and you don't need pre-processing for this specific event.
Here is the code:
LS_par-EVTCNT = CT_TRACKINGHEADER-EVTCNT " shud be same as your ZTREQ_CREATED "evtcnt.
LS_par-PARTYP = 'C'
LS_par-PARAM_NAME = '<Yor Par Name >'.
LS_par-PARAM_INDEX = 1.
LS_par-action = 'C'. " Might not need it but check it try between S and C as actions.
append ls_par to CT_TRACKPARAMETERS .
2) Now you can remove your pre-processing config for this event code unless you have other functionality.
3) Yeah, you can have PARAMETER_CHANGE_NEW even if there are no changes to add. If there are no entries, no harm is done but very very little issue with the performance.
Let us know what kind of ST22 it is, if you haven't figured out.
Also, Were you able to resolve events not showing up in FU Execution but showing in FU EM?
Thanks,
Vishnu