I am currently supporting a WIP application that creates the WIP job by using the wip_job_schedule_interface table. After the WIP Mass Load job runs, the job is created at the first operation. The user has requested if we can automate moving the job to the next operation, then the user would perform all subsequent moves. I am new to WIP, so I am trying to read up on the best way to do this.
So far, I have only found the WIP_MOVE_TXN_INTERFACE as a possibility. My thought would be that after the job is created, then use this interface table to do the move. Is this the best route, or can something be done during the intitial creation interface to accomplish this?
Yes, this is a good option.
Assume you have operations like 10, 20, 30, 40
and say users want you to complete operations 10 and 20 ...
You can also check with them why cant they perform a move transaction from 10-Queue to 40-Queue (instead of 30-Queue to 40-Queue)