I'm modifying this report which has become very complex. My user has made me modify it lots of times since he always finds some calculation wrong.
It worked fine until he told me he rather prefered it grouped by article id (which was on a details section) instead of order number, which was Group#1.
I'm talking here about orders that create 1 or more shippers (depending on the existence). Sometimes, shippers aren't shipped complete because existence wasn't enough to complete the order. (I know this might sound familiar for many of you). I don't know the exact words in english but my report is trying to find all quantities of articles that were not shipped because:
1. There was no existence
2. Existence wasn't enough to complete picking list.
I have several columns and some are calculated based on the existent ones:
The layout is like this:
Qty Ordered/Qty on Shipper/Qty on Invoice/Qty on Shipper vs Qty Ordered/Qty on Invoice vs Qty Shipped
A tipical scenario for article X would be (on that order):
10 / 7 / 5 / 3 / 2
This means that a client ordered 10 units, a shipper was made for 7 units but the invoice turned out only for 5. So, 3 units were not on shippers and 2 units (that were on the shipper) did not made it to an invoice (ran out of existence).
Now, my report has to be grouped by Buyer, then by article and then by order and by shipper. So the buyers can see why they are running out of existence.
It has to be done this way so anyone (or me) can drill down on an article and see the order on which it was, and then, see the shippers generated by that order on which the article was.
I linked the tables on SQL server views so I could avoid retained orders, etc. and I have a view on which I have all the keys: OrderNbr, ShipperID, InvtID...
I started to have this problem when I did summaries: If I have an order that caused me a backorder, I might have two (or more) shippers for that order. When I print on my report, some records (based on the example) would look like:
article: X
order: 45 <- has 2 shippers
shipper: 89
details: 10 / 7 / 5 / 3 / 2
shipper: 98
details: 10 / 5 / 4 / 5 / 1
order: (summaries wrong) 20 / 12 / 8 / 3
order: 33 <- has 1 shipper
shipper: 89
details: 8 / 8 / 8 / 0 / 0
order: (summaries ok)
article (summaries)
summaries on case of first order should be like: 10 / - / 9 / - / -
I placed scores (-) because I'm all mixed up, stucked and I'm not sure how to deal with them anymore so they won't duplicate the quantities and be real so buyers can make decisions with the results.
Any ideas or supporting thoughts are welcome and thank you for taking the time to read all this stuff.
Magda
It worked fine until he told me he rather prefered it grouped by article id (which was on a details section) instead of order number, which was Group#1.
I'm talking here about orders that create 1 or more shippers (depending on the existence). Sometimes, shippers aren't shipped complete because existence wasn't enough to complete the order. (I know this might sound familiar for many of you). I don't know the exact words in english but my report is trying to find all quantities of articles that were not shipped because:
1. There was no existence
2. Existence wasn't enough to complete picking list.
I have several columns and some are calculated based on the existent ones:
The layout is like this:
Qty Ordered/Qty on Shipper/Qty on Invoice/Qty on Shipper vs Qty Ordered/Qty on Invoice vs Qty Shipped
A tipical scenario for article X would be (on that order):
10 / 7 / 5 / 3 / 2
This means that a client ordered 10 units, a shipper was made for 7 units but the invoice turned out only for 5. So, 3 units were not on shippers and 2 units (that were on the shipper) did not made it to an invoice (ran out of existence).
Now, my report has to be grouped by Buyer, then by article and then by order and by shipper. So the buyers can see why they are running out of existence.
It has to be done this way so anyone (or me) can drill down on an article and see the order on which it was, and then, see the shippers generated by that order on which the article was.
I linked the tables on SQL server views so I could avoid retained orders, etc. and I have a view on which I have all the keys: OrderNbr, ShipperID, InvtID...
I started to have this problem when I did summaries: If I have an order that caused me a backorder, I might have two (or more) shippers for that order. When I print on my report, some records (based on the example) would look like:
article: X
order: 45 <- has 2 shippers
shipper: 89
details: 10 / 7 / 5 / 3 / 2
shipper: 98
details: 10 / 5 / 4 / 5 / 1
order: (summaries wrong) 20 / 12 / 8 / 3
order: 33 <- has 1 shipper
shipper: 89
details: 8 / 8 / 8 / 0 / 0
order: (summaries ok)
article (summaries)
summaries on case of first order should be like: 10 / - / 9 / - / -
I placed scores (-) because I'm all mixed up, stucked and I'm not sure how to deal with them anymore so they won't duplicate the quantities and be real so buyers can make decisions with the results.
Any ideas or supporting thoughts are welcome and thank you for taking the time to read all this stuff.
Magda