|
What I have seen so far on the postings is that there does not appear to be a way within vanilla BPCS to do this. With programming help I can do most anything whether it is populating GBH/GBL or creating a separate concatenated field through a trigger program for macro-able events to avoid BTP. George, I like you have seen this before but it really hasn't been a big issue because we have either been in multiple libraries or have a very centralized accounting department that they wanted a single book. I also have not submitted an E-BMR. What I would like to see SSA do is carry the subsystem event determination reason code forward as a key for the event setup. That way simply doing a macro-able event on warehouse would allow you to have multiple events with the same event id, same subsystem origin, but different reason codes, therefore different ledgers, book, etc. Thanks, Mark ---------- > From: George Sagen <gsagen@primesourcetech.com> > To: BPCS-L@midrange.com > Subject: RE: Subsystem Event Determination > Date: Tuesday, July 27, 1999 11:02 PM > > Hi Mark. > > Wow. What a pain. SSA could make life a lot easier if the facility code was > somehow macroable in every line of every model. I've had other clients > request this too, but have never asked for an E-BMR. > > Do they require the data to be live or just current periodically? Do they > need it in detail by facility or just the summarized result? The reason I > ask is that maybe you can write a report/query that: > > 1. Grabs the GLH records with an inventory subsystem origin and for a > defined period. > 2. Link through the GXR to the ITH records and get the facility code for > each GLH line. > 3. Group the GLH records by facility code then account and post the > summarized activity to the facility inventory accounts. > 4. Summarize the original GLH's by account and create a reversing entry with > one line per account affected. > > If you want to get fancy, you can have a programmer write the query and dump > the resulting records into GBH/GBL and post them through BTP. This would > avoid writing code that touches the BPCS source and still force all the > glorious BPCS validation. > > Messy, but it might work. > > Best wishes, > > Geo. > > > > George Sagen > BPCS Application Consultant > gsagen@primesourcetech.com <mailto:gsagen@primesourcetech.com> > http://www.primesourcetech.com > > PrimeSource Technologies, L.L.C. > 7373 East Doubletree Ranch Road > Suite 150 > Scottsdale, AZ 85258 > (801)360-6360 Direct & VM > > > . -----Original Message----- > . From: uucp@Uucp1.mcs.net [mailto:uucp@Uucp1.mcs.net]On Behalf Of Mark > . Seaton > . Sent: Tuesday, July 27, 1999 5:27 AM > . To: bpcs-l@midrange.com > . Subject: Subsystem Event Determination +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.