Multiple Sales Transaction for Same Work Order

I am in the process of trying to create a store level report by department, catagory, and item of the moneys received in total by both deposit on work orders and on direct sales that are not work orders. We require a 100% deposit (of a single tender type) on work orders. I then need to break this deposit down by department, catagory and item. Then I must add that to the same break down for direct sales. Thereby getting a total of all moneys received during a specified period for the store across all registers.

So basically I am trying to figure out the data structure and organization of the transaction/order data and how they are related.

While doing this I have found, in our existing data, 11 work orders from last year that were invoiced twice on seperate registers using the same single deposit as the tender. One of those 11 sales transactions appears to have occured at exactly the same time on two different registers. The others are all within minutes/seconds of each other. I have looked in the journal batches to verify this and journaled receipts were found in their respective batches.

How is this possible? My assumption (love that word!) is that a work order can only be filled once and that a deposit on a work order can also only be used once during the sales transaction tending process. Can multiple people be working on processing the work order at the same time? If so, shouldn't there be something in place to prevent this from happening?

Our situation is that work orders get filled in groups. Work orders X thru Y are "picked" and prepared for shipping at the same time. At that point it is reported back to the office that they have been picked and are ready to be invoiced. At that point two people on different registers start recall the work orders and generate the respective invoice. Is it possible that both people got "in sync" with each other while processing? Is it possible that the system allows for the commital of the invoice without "knowing" that someone else is also process the invoice at that time? Shouldn't the system check the current status of a workorder prior to the commital of the invioce?

Did we just stumble in to a big logic hole?

Any info would be greatly appreciated.

Thanks, Terry

Reply to
PGC Developer
Loading thread data ...

==

So basically I am trying to figure out the data structure and organization of the transaction/order data and how they are related.

While doing this I have found, in our existing data, 11 work orders from last year that were invoiced twice on seperate registers using the same single deposit as the tender. One of those 11 sales transactions appears to have occured at exactly the same time on two different registers. The others are all within minutes/seconds of each other. I have looked in the journal batches to verify this and journaled receipts were found in their respective batches.

How is this possible? My assumption (love that word!) is that a work order can only be filled once and that a deposit on a work order can also only be used once during the sales transaction tending process. Can multiple people be working on processing the work order at the same time? If so, shouldn't there be something in place to prevent this from happening?

Our situation is that work orders get filled in groups. Work orders X thru Y are "picked" and prepared for shipping at the same time. At that point it is reported back to the office that they have been picked and are ready to be invoiced. At that point two people on different registers start recall the work orders and generate the respective invoice. Is it possible that both people got "in sync" with each other while processing? Is it possible that the system allows for the commital of the invoice without "knowing" that someone else is also process the invoice at that time? Shouldn't the system check the current status of a workorder prior to the commital of the invioce?

Did we just stumble in to a big logic hole?

Any info would be greatly appreciated.

Thanks, Terry

Reply to
cptsoft

Jeff,

Thanks for the reply.

With the report we are interested in only knowing the total by dept/catagory/item, but not by tender type. We are a state agency and need to report our revenue to our headquarters by a "revenue code" that is assigned to each dept. We are only concerned that the total tendered equals the grand total for the break down.

With what I have found so far while poking around the database, I will be using SQL user defined functions to:

  1. Draw out the details for open work orders from the orders tables for the reporting period.
  2. Draw out the details for sales not based on work orders from the transaction tables for the reporting period.
  3. Draw out details for sales based on work orders. This is more complicated since I will need to calculate the delta if the work order was placed prior to the processing of the sale. Otherwise the data from the transaction would be used.

I will then use a SQL user defined function to union all three sets of data together for a report showing the total money received during the reporting period, but not based on tender type. In this way they should be able to report all revenues received during the reporting period whether it is a day, week, or year. That's the plan so far. But you know what they say about plans!

Regarding the processing of work orders by multiple registers at the same time; how can I correct the data for the 11 work orders that I have identified? I would think that the inventory movement doubled. I would also think that the "redeemed deposits" might also be misstated. Can a custom key be created that the user could click prior to tendering the sale that would hit the database to determine if the work order was still open? While not the greatest solution, it might close the windows a little bit on the time frame that allows the problem to occur.

Any help, advise, or information would be greatly appreciated.

Thanks, Terry

"Jeff @ Check Po> Terry,

Reply to
PGC Developer

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.