Re: EPDM Security for Costs

[michael.ellis@xxxxxxxxxxxxxxx]

I think I can shed some light on this subject.

To provide this level of field security, you must have MAPICS Integrator. 
The costing fields are secured by the Cross Application Tasks that control 
costing information.  Since they are already controlled by another task, 
you cannot place additional security on these fields.  This according to 
the MAPICS Support Center.  In my instance, I needed to secure the Unit 
Cost Default field on the Item Revision field to prevent users from 
placing a value in that field.  We were attempting to implement Item 
Balance costing and we wanted to ensure that no one placed a value in the 
Unit Cost Default field.  Since the constraint described above applied, I 
modified the attribute of the Unit Cost Default to allow a discrete domain 
with a single value of 0.  That solved my problem.

In your circumstance, I believe you will need to use the User Exits on the 
Item Revision object.  That exit must be written to prevent the user from 
maintaining the Std Mtl This Level field, while still allowing them to 
maintain the Current Material This Level.    If you have not used the User 
Exits yourself before, it can be a challenge to get started, but this is a 
sure-fire way to accomplish what you want.

I could help you with that effort, if you needed to pursue it further.

Michael G. Ellis
Information Systems International, Inc.
A Global ERP Consulting Firm
815-398-1670 x23
 
Choose ISI consultants to ensure consistently top quality implementation 
services at all levels of your organization.

"To enjoy the things we ought and to hate the things we ought has the 
greatest bearing on excellence of character. "
Aristotle, Nichomachean Ethics





mapics-l-request@xxxxxxxxxxxx
Sent by: mapics-l-bounces@xxxxxxxxxxxx
02/27/2003 08:10 AM
Please respond to mapics-l

 
        To:     mapics-l@xxxxxxxxxxxx
        cc: 
        Subject:        MAPICS-L Digest, Vol 1, Issue 508


Web   http://www.timesaversint.comFrom Gary.Sutton@xxxxxxxxxxxxxx Thu Feb 27 
07:53:58 2003
Received: from secure.goodmanmfg.com (secure.goodmanmfg.com 
[63.90.246.130])
                 by linux.midrange.com (8.12.5/8.12.5) with ESMTP id 
h1RDrsqj024376
                 for <mapics-l@xxxxxxxxxxxx>; Thu, 27 Feb 2003 07:53:57 
-0600
Received: from secure.goodmanmfg.com (root@xxxxxxxxx)
                 by secure.goodmanmfg.com with ESMTP id h1RE3Om03331
                 for <mapics-l@xxxxxxxxxxxx>; Thu, 27 Feb 2003 08:03:24 
-0600 (CST)
Received: from exch-hou.gmc (mail.goodmanmfg.com [10.10.2.5])
                 by secure.goodmanmfg.com with ESMTP id h1RE3O603327
                 for <mapics-l@xxxxxxxxxxxx>; Thu, 27 Feb 2003 08:03:24 
-0600 (CST)
Received: by mail.goodmanmfg.com with Internet Mail Service (5.5.2653.19)
                 id <FT2DGJ8J>; Thu, 27 Feb 2003 08:04:11 -0600
Message-ID: <8C7122012DB1D6119C38009027DE419602322469@xxxxxxxxxxxxxxxxxxx>
From: "Sutton, Gary" <Gary.Sutton@xxxxxxxxxxxxxx>
To: MAPICS ERP System Discussion <mapics-l@xxxxxxxxxxxx>
Date: Thu, 27 Feb 2003 08:04:02 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
                 charset="iso-8859-1"
X-MailScanner: Found to be clean
Subject: RE: EPDM security
X-BeenThere: mapics-l@xxxxxxxxxxxx
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: MAPICS ERP System Discussion <mapics-l@xxxxxxxxxxxx>
List-Id: MAPICS ERP System Discussion <mapics-l.midrange.com>
List-Unsubscribe: <http://lists.midrange.com/mailman/listinfo/mapics-l>,
                 <mailto:mapics-l-request@xxxxxxxxxxxx?subject=unsubscribe>
List-Archive: <http://archive.midrange.com/mapics-l>
List-Post: <mailto:mapics-l@xxxxxxxxxxxx>
List-Help: <mailto:mapics-l-request@xxxxxxxxxxxx?subject=help>
List-Subscribe: <http://lists.midrange.com/mailman/listinfo/mapics-l>,
                 <mailto:mapics-l-request@xxxxxxxxxxxx?subject=subscribe>

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
_______________________________________________