Re: Techniques to avoid modifications

Thanks for the great responses!

I'd like to avoid adding programs to the list of modified programs as
much as possible, even if it means jumping through some hoops as a
practice. It's already taking a long time to apply a CUM due to
modifications, with every little line of extra code needing to be
tracked, reapplied, and tested. Even with "perfect" documentation and
tools...well, you know. It all adds up. Is it just me that feels that
way about mods?

I assume the Mapics program would puke if I put a referential constraint
on the field and the data owner put in a bad value so I haven't looked
very far into that.

The MUI option is neat.

Interesting thought about putting it on the display file.

Thanks much!

Kathleen Kostuck

IT Contractor
Sub-Zero Wolf, Inc.


-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx
[mailto:mapics-l-bounces@xxxxxxxxxxxx] On Behalf Of
sjones@xxxxxxxxxxxxxx
Sent: Friday, November 16, 2007 7:59 AM
To: MAPICS ERP System Discussion
Subject: Re: [MAPICS-L] Techniques to avoid modifications

Kathleen:

Modifying the code is VERY SIMPLE in this situation, adding about 5
lines
of code to the program.

Try it, you will be surprised how easy it is ;)

Steve Jones
H-P Products, Inc




From:
"Trudie Cook" <Trudie.Cook@xxxxxxxxxxxxxxx>
To:
"MAPICS ERP System Discussion" <mapics-l@xxxxxxxxxxxx>
Date:
11/14/2007 06:01 PM
Subject:
Re: [MAPICS-L] Techniques to avoid modifications



Kathleen,

One thing you could do is put a trigger on the file. The trigger
program could validate the value. You can capture the before value and
validate the new value. If the new value was found to be invalid you
can just reverse the change.

Another thing you could try would be to add a MUI prompt to the field.

If there are just a few static codes you want to validate against.
Another trick that involved a very minimal modification, just add a
validation to the screen. No need to even recompile the RPG program.

Trudie Cook
MTD Products


-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx
[mailto:mapics-l-bounces@xxxxxxxxxxxx] On Behalf Of Kathleen Kostuck
Sent: Wednesday, November 14, 2007 5:39 PM
To: MAPICS ERP System Discussion
Subject: [MAPICS-L] Techniques to avoid modifications

Hi all,

I'm relatively new to Mapics so I'm really grateful that this list
exists and even gets posts!

I'm looking at the facility field shown in the Employee Master Maint.
Pgm (AMJFA). It doesn't appear to be used by anything else in Mapics so
we'd like to use it to group employees for labor reporting purposes. The
question is whether there is a way to validate the value entered into
the field without modifying the Mapics code. Anyone have any cool tricks
or techniques up their sleeve (possibly using an RI constraint?) to
avoid changing code or is modification inevitable?

To my knowledge, there aren't any user exits for this program.

TIA,

Kathleen Kostuck

IT Contractor
Sub-Zero Wolf, Inc.


The information contained in this E-mail message is intended
for the personal and confidential use of the designated
recipient(s) named above. This message and all communication
contained herein is privileged and confidential. If the reader
of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you
are hereby notified that you have received this E-mail message
in error, and that any review, dissemination, distribution or
copying of this message is strictly prohibited. If you have
received this message in error, please notify MTD PRODUCTS INC
immediately by calling (330) 225-2600.