Re: Inventory history -- BPCS-L

> From: MDamon@agrilinkfoods.com (Damon, Mitch)
>  
>  Does anyone know if there is any place in BPCS where the period starting
>  inventory history is stored?
>  
>  Mitch Damon, CPIM

We just had a similar situation & initially the players were confused as to 
what exactly was going on.

Our scenario is that we SOMETIMES have SOME people working on a Saturday & 
our End-Month-Fiscal USUALLY gets completed on a Friday night, so that the 
Fiscal Calendar for the month just ended is now closed, in GLD105 or SYS800 I 
believe, as part of the EOM check list.

The accounting manager sends reminder messages to people ... This Friday is 
END OF MONTH ... Please tell me Friday when your departments & facilities are 
finished with all work for the day week & month ... and the reason he is 
doing this of course is that he can get started on Friday & month end reports 
for particular applications while people are still working on other 
applications ... but then some people do not check the Fiscal calendar & 
realize that the following Saturday & Sunday are also included within our 
calendar & wiped out as a valid date for transactions during the process of 
EOM.

They sometimes show up on the weekend & try to do their work & not realize or 
forget that the weekend of a fiscal EOM EOY or physical is different than 
that of any other weekend for the processing of transactions.  They get an 
error message on those inventory transactions that also go to the GLD ... do 
INV355 & select first transaction, look at bottom of screen with GLD info, 
then roll forwards through the transactions with your eyes glued to that part 
of the screen ... it may be that you have some inventory transactions that do 
not go into the GLD.

The CFO just sent everyone a reminder that if people need to work on this 
Saturday, since it is EOM weekend, instead of dating the work they do as June 
30, it needs to be dated as if it occurred Monday July 2.  I followed up 
behind him with instructions how to accomplish that with minimum keystrokes.

Get to a command line.
Key in CHGJOB DATE(070201) & enter.
Return to BPCS Menu & notice that it is operating at the OLD date.
Get into INV300 & notice that anything you run from the Menu thinks that 
today's date is what you entered at the command line ... this should apply to 
the default date of any transactions you enter from that session side only, 
until you sign off or do a different CHGJOB DATE using mmddyy format

I consider this to be a termporary expedient to tide over the people who end 
up working the weekend of an EOM.  Normally all our transactions are to be 
dated the day they got keyed in.  I do not want to be encouraging use of this 
date mucking outside this scenario.  For security reasons a lot of our people 
do not have command line authority.

My plan is to create a CL which embodies this from a menu option but also 
adds a safety verification to permit the date change to only be a few days 
off ... in other words it is acceptable to make the date yesterday or the 
next date in the shop calendar, but it is not acceptable to make a keying 
error & get a date that is months away.

You might also check the workings of your shop calendar & the DRP calendar.

For MRP & CAP planning purposes, we define weekends as not being production 
days, so the math comes out right on when raw materials to be delivered & 
when production must start to meet promises to customers.  But then we end up 
working overtime on weekends & entering transactions on dates that the 
calendar thinks are not correct working dates.

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)


+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---