Process Order Change Event - Type linkage under condition (check function module)

[openrico]

Dear professionals,

When I create/change a process order an event is supposed to trigger a receiver type via type linkage (TA SWETYPV).
Therefore i put object type CL_CO_WF_PROCESS_ORDER into the table with event change and create. That is working fine so far. The event is thrown and therefore the type linkage is triggert.

But my requirement is that the change event type linkage is only triggered when a special condition takes place. So I have implemented a function module (Z_CHECK_PROC_ORD_CHANGE_EV) and entered it into "check function module".

In this function module I have to check if the actual finish date of the process order was set by the user. If no, the exception is thrown.
I have debugged the process and at this time, when the check function module is called, the database tables are not updated yet. So neither a functionmodule nor the database gives me the data which was entered prior.
Although a user enters the actual finish date in the process order, the function module raises the exception because it cant see those updates yet.
Sadly I have no access to the entered gui data aswell.

Has anyone had this problem or knows how I achieve my requirement? Maybe there is a user exit/bte or something else in the process order change process that I can use.

Thank you very much!
Greetings
Enrico

[Sandra_Rossi]

When the event CREATED or CHANGED is triggered, it should be theoretically after the database tables are updated. You should investigate why "the database tables are not updated yet" because it's abnormal, or give context about what happens when the event is triggered so that people can help.

[openrico]

Hallo Sandra,

thanks for you answer. This is exactly what I thought too... But when I've debugged the program, a commit is called only after the check function module is called.

For further Informations:

In the check function module I want to check either the field GLTRI in table AFKO or field LTRMI in table AFPO. Both fields are empty at the time the check is called. But direct after the function module, a commit is called from SAP and the tables are updated and both fields have the value, the user has entered prior in transaction COR2.