Month end jobs - CEA and Inventory close

Here is a URL destination that addresses BPCS archiving:

http://www.unbeatenpathintl.com/locksmith_bpcs.htm

The product is Locksmith ... another Bells & Whistles
software enhancement for BPCS. Locksmith will cut the
time needed for executing month-end jobs if you have
substantial numbers of older records in your files.

Archiving is a much better idea than purging, especially
if you have:

Sarbanes-Oxley --  http://www.unbeatenpathintl.com/pcaob/source/1.html

                                ...... or .....

21 CFR part 11 --  http://www.unbeatenpathintl.com/FDA21CFR11/source/1.html

compliance issues.

Warm regards,
Milt Habeck
Unbeaten Path
www.unbeatenpathintl.com
mhabeck@xxxxxxxxxx





----- Original Message ----- 
From: Clare Holtham
To: SSA's BPCS ERP System
Sent: Thursday, June 24, 2004 2:33 AM
Subject: Re: Month end jobs - CEA and Inventory close


Steve,

Have you thought about using the BPCS Archiving? This would remove a lot of
the older records to a separate BPCS environment where your users could
still look at them if necessary, and month-end (and daily transaction
processing) would run a whole lot quicker too.
You could also investigate creating appropriate indexes for month-end. That
usually gives about a 40% improvement at least.
And finally, are you running month-end in the batch pool or where? SQL runs
differently based on how much memory is available in the pool it runs in.
Does closing all the other subsystems and running it in *Base make any
difference??
Some of the files that get really huge and need archiving are things like
CMF (Cost Master) and ZPD (printing), and these are accessed many times
(multiplier is number of records in primary files) during such processing.

Hope this helps,

Clare

Clare Holtham
Director, Small Blue Ltd - Archiving for BPCS
Web: www.smallblue.co.uk
IBM Certified AS/400 Systems Professional
E-Mail: Clare.Holtham@xxxxxxxxxxxxxx



  ----- Original Message ----- 
  From: Steve Segerstrom
  To: bpcs-l@xxxxxxxxxxxx
  Cc: Russell Koenig ; Gerard Tilton
  Sent: Wednesday, June 23, 2004 11:38 PM
  Subject: Month end jobs - CEA and Inventory close


  We are bpcs 6.02 heavily modified.
  I am toying with the idea of running CEA concurrently with the month end
inventory jobs. By cea I mean that we are running batch posting (CLDI501 BTP
posting) for cost of goods sold, daily postings. It takes about 2.5 hours to
get through all of the posting jobs at which time I run my inventory close
and then all of the inventory reports. Takes another 6+ hours.
  So - I am going to copy the files I need for the inventory reports - they
are all read only and go ahead and bring up bpcs. I could come up another 2
hours earlier if I could run my inventory close and then bring up bpcs while
cea runs in the background. I am having a tough time believing that posting
transactions to the GL would have an impact on ITH ILI IWI files and that
they would pick up additional activity after bpcs is brought up. Am I being
stupid, playing with fire, or onto something?


  > From: owner-bpcs-l@xxxxxxxxxxxx
  > Sent: Thursday, April 29, 1999 10:26 PM
  > To: BPCS-L@xxxxxxxxxxxx
  > Subject: RE: Month-End Close
  >
  >
  > Period End Close Programs for 6.0.02(mm):
  >
  > FOR900    Purge and Roll History
  > FOR910    Update Current Demand
  > FOR915    Update Current Orders
  > FOR920    Update Current Forecast
  > FOR930    Load Item / Warehouse from Basis
  > JIT900         Production History Purge
  > DRP500    Distribution Requirements Planning
  > MRP500    Master Production Schedule Generation
  > MRP600    Material Requirements Planning Generation
  > CAP600    Capacity Requirements Generation
  > CAP160    Reload Bill of Resources
  > CAP500    Rough Cut Capacity Planning
  > CAP900    Capacity Weekend
  > CST120    Overhead Cost Input
  > CST510    Overhead Allocation
  > CST910    Labor Ticket Post
  > SFC900         Shop Order Close (if Costing NOT installed)
  > CST900    Shop Costing Post / Close
  > PRF900    Period end Close
  > SFC905         Labor Ticket Save
  > PUR900    Purchasing Period-End
  > ACP900    Accounts Payable Period-End
  > ACR900    A/R Period End Close
  > INV920         Inventory Transaction Subsystem Post
  > INV900         Inventory Period-End
  > INV972         Reset On Hand Balances
  > INV973         Delete Warehouse (IWI Records With No Inventory
  > SFC990         File Reset & Clean Up
  > ORD990    File Reset & Clean Up
  > SYS990    Clear/Reset Lot/Location Allocations
  > INV971         Reset On Order and Allocated Amounts
  > CEAGTB    CEA Period Close
  >
  > Year End Close Programs
  >
  > FOR940    List Seasonality History Factors
  > FOR950    Update Seasonality History Factors
  > JIT900         Production History Purge
  > CAP910    Capacity Year End
  > ACR910    A/R Year End (if INV is NOT installed)
  > INV910         Inventory Year End
  > INV660         Clear Physical Inventory
  > INV620         Print Inventory Tags
  > PUR910    Purchasing Year End
  > ACP920    1099 Report
  > ACP910    A/P Year End
  > FXA900         Fixed Assets Year-End Processing
  > FXA910         Mid-Quarter Convention (If mandated by FXA900)
  > FXA920         Year-End Roll and Close - Fixed Assets
  > CEAGDS    CEA Transfer Opening Balances
  > PRF900    Period End Close
  >
  > The above are all of the BPCS close programs for the release I am on.
  >  I do not run all of the above. I only run the packages I
  > have installed.
  > I hope this will be of some help.
  >
  > The above order is the BPCS run order supplied by the Helpline.
  >
  > Sincerely,
  >
  > Chris Ertz
  > Software Development Manager
  > American Metal Products