| Bill, this is Tom Malomo here and I think I have the answer for you:
There are 3 outstanding problems with the "RPTS" functionality as it applies
to Backlog:
1. The reports are including only scheduled backlog and are omitting
unscheduled backlog.
2. Since you used NOV-1988 for all 3 date parameters, the report should
have showed zeroes for December (as you stated).
The developers are aware of these problems and are in the process of
correcting them this very minute. We will post appropriate messages when
these fixes have been implemented.
3. This is a little more complicated...On the BK1 screen, the 96,216 units
that were reported represent quantities (scheduled and unscheduled) for
months prior to November, for November and December '88 and for all of
'89, '90 etc, as far out into the future as backlog goes.
Aside for the "report" bugs described above, the 96,216 units would still
not have been accounted for because of 1 other thing:
1. You were correct to use NOV-1988 as the pass date, but when you
used NOV-1988 as the beginning and ending execution date, the report
included only quantities scheduled for November - nothing prior to
November and nothing later than November. The best you could have
done was to use NOV-1988 as the beginning execution date and
OCT-1989 as the ending execution date - this covers a 12 month
period which is all that will fit on one line of the report. But
as you can see, you would still be missing those quantities that
are for months prior to November '88 or greater than OCT '89. This
means that we in FMIC need to revisit the Reports module as it
applies to Backlog and see how best to make the reports agree with
the BK1 screen. I have an idea about this, let me know what you
think of this:
Suppose you enter a pass date of NOV-1988, a beginning date of
NOV-1988 and an ending date of AUG-1989 (a period of 10 months).
Since we can fit 12 buckets on the report, we can make the first
bucket represent "prior to Nov" and the last bucket represent
"future"(scheduled or unscheduled greater than Aug-1989). The
other 10 buckets would be for NOV-1988 thru AUG-1989 respectively.
This way, the total quantity on the report would addd up to the
96,216 as reported by the BK1 screen. If you like this idea or
have a better idea, please let me know.
|
| Hi Tom,
I will try and add some more information for you and relate them
to each number that you talked about.
1. Thanks for the information that the backlog is only only
scheduled backlog in the RPTS functionality. BUT... The Scheduled
backlog should be at least 70K units for the VT320 and not
the 13+K units as stated on the report. I recognize that this is
an area that is being worked, but thought you might like to know
anyways.
2. Thanks for letting me know that you know about the date problems.
3. My purpose in getting the RPTS for backlog was to see the entire
backlog that would show all the part numbers and quantities that
make up that backlog. As a user I need this information to see any
changes that are needed in my supergroup for new part numbers
as well as any new products that may be manufactured by other
groups that are part of "lets say" the VT320 aggregate. My purpose
did not require that I would have to see what month each product
variant was scheduled in or unscheduled with a customer request
date. I currently use the DEC 10 total backlog that is frozen as
a total at the end of the month and then run the detail for that
total backlog. The current Total Backlog on the DEC 10 does not
break it out by months. You added some functionality that I did
not need that others might want however.
If I wanted to see that information, I would go to a SRC
report.
Your report idea that you mentioned would work for me ok. It must be
stated clearly for the user in the report however.
What would happen if the user left the beginning and exectution date
blank? Could then the system add up all total backlog (scheduled
and unscheduled) and report it as the November Pass data? This
is just another idea.
Regards,
Bill
|