Re: GJ novice learns fast -- BPCS-L


This response relates to the e-mail sent by Al Macintyre regarding the G/L 
Journal Posting problems experienced with 405 CD V4R3 mixed mode and the 
first end-month fiscal for year 00.

**********************************************

Al:

There have been several excellent responses to your e-mail questions.  Here 
are a few additional suggestions, some of which relate specifically to your 
V405 CD environment:

1.  To make tracking of the Journal Batches that correspond to your Inventory 
Transactions easier, you should consider using a unique Journal Source Code 
for each Transaction Effect Code that posts to G/L.  You might want to use 
the Transaction Code itself as the Journal Source Code in order to have a 
more direct association.  Just be sure that you do NOT duplicate an existing 
BPCS reserved Journal Source from other application areas (e.g. BL, AR, AP, 
etc.).

This method will also reduce the number of Batch Numbers used with a single 
Journal Source Code (i.e. within IN).

2.  In order to reduce the number of Journal Batches that BPCS creates, you 
may want to remove the Location (TLOCT) as one of the Level Breaks that 
forces an increment of the Journal Batch Number in INV920.  Please refer to 
the OPNQRYF statement for ITH in INV920C.

The Warehouse (TWHS) controls the Company and the Location (TLOCT) controls 
the G/L Profit Center which is retrieved from the Location (ILM) File.  
However, there is NO need to create a new Batch Number each time that the 
Location (i.e. P/C) changes.  A Journal Batch can have multiple P/C's within 
it.

In addition to removing the TLOCT from the OPNQRYF statement, you would also 
need to remove the statement in INV920 that sets CNTLVL to "Y" if the 
Location changes.

Combined with Point 1, this method will produce one Journal Batch per 
Transaction Code per day, assuming that you do NOT run INV920 multiple times 
in a day.

3.  You mentioned that there were small batches of Journal Transactions that 
could NOT post because they already had a GJH entry for them.  This condition 
could occur if you happen to run Subsystem Post (GLD540) at the same time 
that INV920 (or any other program that writes records to GJW) is running.  
GLD540 will pick up the transactions in GJW and begin the post process to 
GJH/GJD.  However, the other program(s) are still adding transactions to GJW 
with the same Batch Number.  These additional transactions will NOT be 
processed until you run GLD540 again.  As a result, when GLD540 is run again, 
the Batch Number will already be in existence and the GJW records will NOT 
post.

Be sure to carefully control when GLD540 is run.


Please feel free to contact me directly if you have any further questions 
about my suggestions.

Hope that this helps.

Les Mittman, CPIM

BSI Consulting, Inc.
Highland Park, IL
(847) 831-9388
(847) 831-9389 (fax)
+---
| 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
+---