|
Joan, I have written some trigger programs over MAPICS files and have not had any problems with backups. At R6, there is a new option in CAS to store trigger information in MAPICS. My understanding is that when there is a file being upgraded, the PCM will use this database to remove and reload the trigger. If I am mistaken, then please let me know. I also read somewhere that it is a good practice (though I do not follow this just yet) to keep the trigger program in the same library as the file. If the file library is restored, so is the appropriate trigger program. I do not usually keep programs in AMFLIBx but this kinda makes sense. Eric A. Wolf ----- Original Message ----- From: "McCready, Joan" <Joan.McCready@xxxxxxxxxxxxxxx> To: "'MAPICS ERP System Discussion'" <mapics-l@xxxxxxxxxxxx> Sent: Thursday, February 27, 2003 7:36 AM Subject: Triggers (was: EPDM security) > Patrick, > > Since you mentioned trigger programs, I have a couple of questions for you > and the rest of the group. I'm beginning to look into writing some trigger > programs, both in Integrator/Browser and for plain-MAPICS updates. I know > I'd have to remove the triggers when applying updates and CUMe's, but I was > warned that trigger programs can also mess up your backups. (Both MAPICS and > AS/400 is what was implied to me) > > Are there problems with getting good backup files/tapes when you use > triggers? What kind of problems? Where can I go for more information? > > Thanks to all -- Joan > > Joan McCready, IS Manager phone: 636-479-4499 > MetalTek International fax: 636-479-3399 > The Carondelet Division www.metaltekint.com > 8600 Commercial Blvd > Pevely, MO 63070 > > > -----Original Message----- > From: Shrader, Patrick [mailto:pshrader@xxxxxxxx] > Sent: Thursday, February 27, 2003 8:52 AM > To: MAPICS ERP System Discussion > Subject: RE: EPDM security > > > We don't use EPDM here, but one option that you could explore does work for > us in other areas. Create a trigger program on the cost files/fields. This > program would verify to a database the approved cost "managers", and prevent > changes to this field if the user is not in this database. If the user isn't > authorized, simply replace the keyed value with the original. You would want > to use a before change trigger for this to work. > > I haven't done this in the client architecture, so I'd TEST and TEST again. > However, for green screen manipulation this approach would work. > > Patrick > > > -----Original Message----- > From: Sutton, Gary [mailto:Gary.Sutton@xxxxxxxxxxxxxx] > Sent: Thursday, February 27, 2003 9:28 AM > To: MAPICS ERP System Discussion > Subject: RE: EPDM security > > > The MAPICS security does not give you that level of granularity. Might want > to rethink the business process. > > Gary H. Sutton > > -----Original Message----- > From: Hans Koens [mailto:hkoens@xxxxxxxxxxxxxxxxx] > Sent: Thursday, February 27, 2003 6:19 AM > To: MAPICS ERP System Discussion > Subject: Re: EPDM security > > > That is correct ofcourse. > But as far as i can see there is no difference between cost fields for > security. The same user who can maintain current cost shouldn't be abble to > maintain standard cost and that is my problem. If was looking for seperate > security between current and standard cost. > > > > ----- Original Message ----- > From: "Sutton, Gary" <Gary.Sutton@xxxxxxxxxxxxxx> > To: "MAPICS ERP System Discussion" <mapics-l@xxxxxxxxxxxx> > Sent: Thursday, February 27, 2003 3:04 PM > Subject: RE: EPDM security > > > > Setup a group profile with the cost field update authority and assign > > the users responsible for setting up the new item to the group. Turn > > off the cost field authority for everyone else. If you limit access > > to the responsible personnel, who should have the authority to add new > > items and maintain existing items, cost control should be possible. > > > > Gary H. Sutton > > > > -----Original Message----- > > From: Hans Koens [mailto:hkoens@xxxxxxxxxxxxxxxxx] > > Sent: Thursday, February 27, 2003 2:50 AM > > To: MAPICS ERP System Discussion > > Subject: EPDM security > > > > > > I'm looking for a way to secure the standard cost field in EPDM > > (Standard material this level) It should be possible for a user to > > create an item including all the cost fields but when the item is > > already there the same user can't be allowed > to > > maintain the standard cost field.(Standard material this level) > > Current cost fields should still be maintainable by the same user. > > Standard cost can only be maintained by users with the correct user > rights. > > Is there a way to do this? > > > > > > > > > > > > > > Hans Koens > > Timesavers Int. B.V. > > Tel. +31 113 238911 > > Fax. +31 113 232003 > > E-mail hkoens@xxxxxxxxxxxxxxxxx > > Web http://www.timesaversint.com > > _______________________________________________ > > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To > > post a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, > > or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/mapics-l > > or email: MAPICS-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives at > > http://archive.midrange.com/mapics-l. > > _______________________________________________ > > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To > > post a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, > > or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/mapics-l > > or email: MAPICS-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives at > > http://archive.midrange.com/mapics-l. > > > > **************************************** > > This email has been scanned for viruses. > > Timesavers (Sandingmaster/Grindingmaster) > > Quality & Value Without Compromise > > **************************************** > > > > **************************************** > This email has been scanned for viruses. > Timesavers (Sandingmaster/Grindingmaster) > Quality & Value Without Compromise > **************************************** > _______________________________________________ > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a > message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change > list options, > visit: http://lists.midrange.com/mailman/listinfo/mapics-l > or email: MAPICS-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/mapics-l. > _______________________________________________ > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a > message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change > list options, > visit: http://lists.midrange.com/mailman/listinfo/mapics-l > or email: MAPICS-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/mapics-l. > _______________________________________________ > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a > message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change > list options, > visit: http://lists.midrange.com/mailman/listinfo/mapics-l > or email: MAPICS-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/mapics-l. > _______________________________________________ > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list > To post a message email: MAPICS-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/mapics-l > or email: MAPICS-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/mapics-l. >
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.