Al,

We're on V3 and I must admit to not really trusting the figures you have 
described.  In all reporting that we do here, we total all data from the lines 
and ignore header and master files.  V4 was a bit more stable than the version 
that we are on so there may be some mileage in verifying the 'B' transactions 
against YTD sales, etc.  If everything was okay, then there wouldn't be the 
need for the reorg programs.

Ian

-----Original Message-----
From: Al Mac [mailto:macwheel99@xxxxxxxxxxx]
Sent: 21 May 2003 04:54
To: BPCS Users Discussion Group
Cc: Tim Armstrong; Jerry Cooper
Subject: Sales YTD Totals 405 CD


I have been asked for some new reports, with such elements as average 
week's sales totals (average in a year of sales) by customer, and perhaps 
later by other criteria.
Looking at the Last Month, 2 months ago etc. data, I am also wondering if 
that data could go into like CAP bar graph format to see when recurring 
customer volumes peak each year.

I am trying to puzzle out the significance of what is in some files I not 
mess with very often, such as SSD SSH RCM SIL
We not using all of BPCS 405 CD, just: ACP ACR BIL BOM CAP CST DRP GLD INV 
JIT MPS MRP ORD PUR SFC

I can see that some YTD fields are THIS FISCAL since End_Year
e.g. SAL300 for a customer looks to me like LAST YEAR is total of 2002 thru 
April so it is like THIS YEAR is total of 2003 thru April, then when we run 
INV900 it will put MTD into this year YTD, use bucket 12 for May 2002 into 
LAST YEAR YTD, so we continue to compare same months, then drop of bucket 
12, move all buckets to the next higher one, and replace bucket 01 with the 
MTD figures.  I think that is kind of cool.

But what I am looking for is if any of the YEAR totals is really total of 
year ago through last end of month.  I could then divide that by 52 (# 
weeks in a year) to get AVERAGE WEEK of sales in the last year to compare 
to another report I already created that shows total sales for the most 
recent week, through whatever date it is run (date math = last 7 days of 
SIL records).  If there is no such field (YEAR = cumulative since a year 
ago) then I will have to sum a year's stuff another way.

SSD has cust/item break down whole company (no facility handle) with MTD 
YTD fields and the 01-12 buckets
SSH has cust/item and I can get facility from warehouse, but it does not 
have the 01-12 buckets
RCM has cust only MTD YTD 01-12 and the PRIOR YEAR total, which is where I 
assume SAL300 is getting it
SIL has detail lines billed, going back one year, pricing not cost of sales 
... if I wanted total for a month, calendar month would be much easier than 
fiscal
ITH_B has cost side but no customer #, although I can get that from cust 
orders still open (not a pretty picture) but I not want to mess with ITH 
(such a humongous file)

So basically if I not know of a file with reliable perpetual YEAR total by 
customer, I will be adding buckets 01-12 to get year sales total.
I also had a hard time figuring out where this stuff is documented.

-
Al Macintyre
BPCS/400 Computer Janitor at http://www.globalwiretechnologies.com/
See Al at http://www.ryze.com/go/Al9Mac
Emergency notification (homeland, weather, etc.) http://www.emergencyemail.org/
Find BPCS Documentation Suppliers 
http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.