Dear all,

Thanks for ideas.
By the way like Pendi's said how to use the exit point ? can you give the example ?
In other case we want call a program after the order is done, let say printing program, I already try by using exit01 for ORD701B then the program receive the parameter, it was done but the parameter we receipt only : program name, user id, exit point name and some blank fields. This is the first for us, can anybody tell us how ? we assume that the parameter which we received should contain some keys of ord700 (form ECH or ECL) which will be used by our add on program. Is my assumption right ? how it should be ?
Thank you for your help.


Regards,

Erwin




________________________________
From: "bpcs-l-request@xxxxxxxxxxxx" <bpcs-l-request@xxxxxxxxxxxx>
To: bpcs-l@xxxxxxxxxxxx
Sent: Saturday, May 5, 2012 12:00 AM
Subject: BPCS-L Digest, Vol 10, Issue 51
0
Send BPCS-L mailing list submissions to
    bpcs-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
    http://lists.midrange.com/mailman/listinfo/bpcs-l
or, via email, send a message with subject or body 'help' to
    bpcs-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
    bpcs-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of BPCS-L digest..."


*** NOTE: When replying to this digest message, PLEASE remove all text unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

  1. Security for protecting the field (ERWIN ADRIAN)
  2. Re: Security for protecting the field (Wynn, Christopher P.)
  3. Re: Security for protecting the field (Pendi)
  4. Re: Security for protecting the field (Al Mac Wow)


----------------------------------------------------------------------

message: 1
date: Thu, 3 May 2012 19:32:47 -0700 (PDT)
from: ERWIN ADRIAN <erwin107@xxxxxxxxx>
subject: [BPCS-L] Security for protecting the field

Dear All,

Currently we are in 8.3.4,? would you tell me more about ow to protect a field in LX ? can we create protection as we want rather than in sys603D3-01 ?
the real case is we want to protect the price field at ord700, we don't want somebody to change the field.

Thank you.


Regards,

Erwin

------------------------------

message: 2
date: Fri, 4 May 2012 09:37:18 -0500
from: "Wynn, Christopher P." <christopherwynn@xxxxxxxxxx>
subject: Re: [BPCS-L] Security for protecting the field

Hi Erwin,

We are running ERP LX 8.3.1 and looked into a similar modification.  We wanted to make the  price field a display only field in ORD700 for regular order lines as the system should price these.    SYS603 (8.3.1) cannot protect specific screen fields, only specific actions and function keys for a menu option.    We did not want to modify any LX screens or programs  so we added an exit point program to ORD701B.  This program edits the price for regular order lines (checks if it is zero  or was manually entered/overridden or does not match the price in the ESP file).    A supervisor is notified if a price exception occurs.    In PRMS this functionality was controlled by the order type code, there was an option if the price could be manually entered for regular line items,  a nice feature that would be welcomed in LX. 

Chris 

-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of ERWIN ADRIAN
Sent: Thursday, May 03, 2012 9:33 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Security for protecting the field

Dear All,

Currently we are in 8.3.4,? would you tell me more about ow to protect a field in LX ? can we create protection as we want rather than in sys603D3-01 ?
the real case is we want to protect the price field at ord700, we don't want somebody to change the field.

Thank you.


Regards,

Erwin
--
This is the BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l.



The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is legally privileged, confidential and exempt from disclosure. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender or the AB Mauri/Ohly Help Desk at Tel: 314-392-0800 x 1881 immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer. Thank you.


------------------------------

message: 3
date: Fri, 4 May 2012 22:09:18 +0700
from: Pendi <pendi@xxxxxxxxxxxx>
subject: Re: [BPCS-L] Security for protecting the field

Hi Chris,

May know how you the exit point, we have tried but the parameter from the program is blank.
We make new rpg with the 7 parameter, but the parameter is empty.

Regards,
Pendi.

Sent from my iPad

On 4 Mei 2012, at 21:37, "Wynn, Christopher P." <christopherwynn@xxxxxxxxxx> wrote:

Hi Erwin,

We are running ERP LX 8.3.1 and looked into a similar modification.  We wanted to make the  price field a display only field in ORD700 for regular order lines as the system should price these.    SYS603 (8.3.1) cannot protect specific screen fields, only specific actions and function keys for a menu option.    We did not want to modify any LX screens or programs  so we added an exit point program to ORD701B.  This program edits the price for regular order lines (checks if it is zero  or was manually entered/overridden or does not match the price in the ESP file).    A supervisor is notified if a price exception occurs.    In PRMS this functionality was controlled by the order type code, there was an option if the price could be manually entered for regular line items,  a nice feature that would be welcomed in LX. 

Chris 

-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of ERWIN ADRIAN
Sent: Thursday, May 03, 2012 9:33 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Security for protecting the field

Dear All,

Currently we are in 8.3.4,  would you tell me more about ow to protect a field in LX ? can we create protection as we want rather than in sys603D3-01 ?
the real case is we want to protect the price field at ord700, we don't want somebody to change the field.

Thank you.


Regards,

Erwin
--
This is the BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l.



The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is legally privileged, confidential and exempt from disclosure. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender or the AB Mauri/Ohly Help Desk at Tel: 314-392-0800 x 1881 immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer. Thank you.
--
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.


-------------------------------------------------------------------------------------------------------------------------------------------------------------------

This e-mail message and any attachments (if any)  are privileged and confidential information and is solely intended to be conveyed to the designated recipient(s).  If you are not the intended recipient of this e-mail, please notify the sender immediately by e-mail and permanently delete the message, including its attachment(s)  from your computer system. Any dissemination, distribution or copying the information contained  herein by unintended recipient is strictly prohibited. The sender does not guarantee the reliability of email communication is free of error or virus and  therefore you are advised to check attachment(s) for viruses before opening it. 





------------------------------

message: 4
date: Fri, 4 May 2012 11:32:05 -0500
from: "Al Mac Wow" <macwheel99@xxxxxxxxxx>
subject: Re: [BPCS-L] Security for protecting the field

Uncle Milt has software to monitor fields we want to protect, to tell us if
inappropriate changes are made, so
(a) they can be fixed
(b) we know who done it

Depending on version of BPCS, there is more than one place price can be
changed, perhaps inappropriately.

Al Mac (WOW) = Alister William Macintyre
via WOW WAY.com ISP
2012 April I had a serious PC melt down, from which I am still recovering
-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of ERWIN ADRIAN
Sent: Thursday, May 03, 2012 9:33 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Security for protecting the field

Dear All,

Currently we are in 8.3.4,? would you tell me more about ow to protect a
field in LX ? can we create protection as we want rather than in sys603D3-01
?
the real case is we want to protect the price field at ord700, we don't want
somebody to change the field.

Thank you.


Regards,

Erwin



------------------------------


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