Labor records written from serialize PAPI call

[former_member735542]

We have a custom transaction that calls the serializeSFC PAPI. It appears that this is writing records to LABOR_LOG and LABOR_LOG_MEMBER. The CLOSURE_ACTIVITY column shows SPLIT/SERIALIZE for all these records. However, these are not showing up in the Supervisor Time Edit/Approval screen.

LABOR_LOG_MEMBER is, by far, the largest table in our database even though we don't have any LT calls in our PODs.

Version 15.4.0.9

[sergiy_katerinich · Accepted solution]

Hi!

I do not see such behavior in a local system. If there has been no LT tracking set up and used, then LABOR_LOG table is empty. And then Serialize from POD does not write anything to this table.

So, I suppose there was some LT activity previously on your site, and this is causing LT snapshots to be taken now on too. Or maybe you trigger Serialize PAPI with some fields causing LT actions.

Regards,

Sergiy