Program to determine if any pending job labor transaction may have been created and then deleted rather than corrected and posted
Utility to find any pending job labor transaction may have been created and deleted
Solution ID = KB-365
Goal : Program to determine if any pending job labor transaction may have been created and then deleted rather than corrected and posted
Version = All Version
Module : SLMFG
Fact : Support Utility
Database : Progress, SQL
Fix
You can run the attached programs to help determine if any pending job labor transactions were perhaps created and then manually deleted rather than corrected and posted. When you move an item into inventory and the system encounters a problem which causes a pending job labor transaction to be created, the quantity is moved into inventory but none of the costing is done. One side affect is that the job finish material transaction will show a quantity but the unit cost and total posted fields (seen on material transaction reports) will all be zero. If you correct the problem and post the pending job labor transaction, the system will find and update the cost fields in the material transaction.However, it is not uncommon for users to delete the pending transactions rather than correct the problem and post them. If that is done, the costing is never done for that transaction and when the job is closed the the cost that should have been assigned to those pieces is moved out of WIP and written off to either inventory adjustment (actual costing) or routing variance (standard costing).
For Progress versions (SL6 and lower), the pend-labor.p utility will find all job finish material transactions which moved a quantity to inventory but which have no costs. It can also be used to find all job finish transactions for which a pending transaction may have been created for a specific job or item (though those can be found by running material transactions reports and looking for job finish transactions at zero cost). All tansactions found will be output to a file called pend-labor.out which should be created in your Syteline sessions Start In folder. The information output includes the transaction number and date, the item and job number, and whether or not a pending job labor transaction still exists for the material transaction.
For SQL versions (SL7 and higher), the pend_labor.sql script will find all job finish material transactions which moved a quantity to inventory but which have no costs.
Note It should be noted that the transactions found may or may not be the result of the pending transaction haveing been created and then deleted. While that is the most likely scenario, it is certainly possible that an item is correctly moved to stock from a job at zero cost. See solution related KB with keyword for the other reasons a item would be moved to inventory at zero cost.
