I no longer have BPCS/400 access, but worked on it for 25 years, so a lot
still sticks in my head.
I still have one of the GL cheat sheets I created for our auditors.
There will be files unique to versions of BPCS.  We never used CEF file on
405CD but there were a lot of empty files created in BPCS setup, not needed
by our tailoring.

GL Journal entries, from shipping invoicing and other transactions, were
assembled in 405CD from a combination of "regular" BPCS files:
*	IIC item class master file provided GL accounts for various kinds of
products and actions.  I don't know if standard BPCS, or just how we set it
up, but 2 letters defined regular product classes and 2 digits defined
non-part# actions, such as billing a customer for overtime or special
tooling charges, non-standard delivery, or a credit memo without specifying
*	ITE transaction effect file had rules for every kind of inventory
action, which feeds ITH inventory history, including where in GL is to get
the transactions, from perspective of Journal prefix, which has to be
pre-defined in GL, where that pre-definition identifies how much detail vs.
summary is to be used when the transactions land there.  We had transactions
which were deliberately invisible from GL.
*	ZPA system parameters, and miscellaneous BPCS Business Rules
Tailoring file, has some miscellaneous reason codes based on which kind of
sub-system module action triggered the customer order or other actions, when
the reason codes of inventory transactions don't apply.
*	IWM warehouse master file had which GL profit center any given
transaction was to go into.  Customer service could over-rule this, and
sometimes messed up when a different facility was to do repairs, or
inter-company drop ship involved.
*	CMF cost master file provided cost of shipping inventory
*	Customer order had pricing info, which could have come from a
variety of systems, including item list price, various discount pricing
*	There were some other nuances.
*	Since GL transaction codes "assembled" from different files,
sometimes we got invalid "new" combinations, which had not yet been setup in
GL, and sometimes the finance dept clerks had trouble reconciling this.

We had auditors and finance personnel who denied themselves BPCS education,
so they were forever asking where this or that $ came from in "regular"
BPCS, so I created a modified version of the GL trial balance, which used
the codes in GL Journal transactions, which point at invoices, orders, etc.
to provide expanded info on which customers vendors etc. were the reasons
for the various transactions.

Alister Wm Macintyre (Al Mac)
Linked In https://www.linkedin.com/in/almacintyre  
-----Original Message-----
From: BPCS-L [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of Tim Knoebel
Sent: Monday, May 18, 2015 9:52 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] BPCS 6.1 - Switch from Pick Confirm to Ship Confirm

Thanks Alister, for your write-up.  I had worked with BPCS 405cd a long time
ago and seem to think this issue was easier to handle in 405cd than in 6.1.
Did CEF (Session Manager) exist in 405cd?  I don't recall using it there;
here it seems to muddy the waters quite a bit.  Finance took full control of
CEF and set everything up in it before I started here.  I have not run
across where the G/L accounts are assigned to the individual transactions in
what I call "regular" BPCS.  Maybe in CEF somewhere?

Best regards,

Timothy J Knoebel, Sr.  iSeries/BPCS Administrator

-----Original Message-----
From: BPCS-L [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of Alister Wm
Macintyre (Wow)
Sent: Friday, May 15, 2015 13:03
To: 'BPCS ERP System'
Subject: Re: [BPCS-L] BPCS 6.1 - Switch from Pick Confirm to Ship Confirm

I am now retired from 405 CD,  no longer have BPCS access, writing from
memory.  Plus I recognize some 405CD solutions don't translate well to 6.1.

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-2021 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.