Much of the reasons why someone might want to look up "B" transactions is duplicated in other files.
ESH ESL at time of shipping,
SIL SIH at time of billing.

Some of these files are stored by BPCS to infinity, and need evaluation how long do you really need to store that data, then make arrangements to purge that which is older than you need.

We often have multiple customer order lines on same customer / item that get shipped out together, resulting in multiple "B" transactions reflecting pieces of the same actual shipment, and most of our users want to view total quantity sent same date, not how it was organized prior to shipment or which ECL lines it came off of. Thus most of our shipping history inquiries are not looking at ITH file.

Al Macintyre
BPCS/400 Computer Janitor at

We process many "B" transactions for the same customer / product / date. We
have been dealing with this sequence number problem for some time for our
fastest moving items. I am thinking about writing a program that would
replace all ITH "B" transaction records older that a set number of days with
summary records where one record represents all such transactions for the
same customer, product, date. For anything older than 60 or 90 days we
really don't need detail information -- just the ability to identify when
some abnormal movement took place.
once the unconsolidated records are replaced by the summary records it is
easy to resequence the file and update the sequence number field in the IIM.
(In fact, we do that part already as part of our purge routine.)

Mark Bazer
Director, Information Systems
Dyno Merchandise
Pompano Beach, FL

Al Macintyre
BPCS/400 Computer Janitor at
See Al at
Emergency notification (homeland, weather, etc.)
Find BPCS Documentation Suppliers

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