Buyer Security

 3 Replies
 0 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
riegerj
Veteran Member
Posts: 44
Veteran Member
    We are trying to find a way to keep buyers from keying POs to any other buyer code except their own.  We found a lawson KB article that says you can add PROC LEVEL BUYER-CODE to your security.cfg and maintain it through LAUA but that concept seems very labor intensive to me.  We would have to create a security class for every user!  We are instead considering a user exit that will stop them if the buyer code is not theirs.  Has anyone tried doing this in security or any other way?  Can you share any pitfalls or tips?  Thanks!
    Roger French
    Veteran Member
    Posts: 549
    Veteran Member
      You should consider using LSF9 security. I've done all kinds of buyer security scenarios in the past, and you can write a rule or rules to do what you want in yours.
      riegerj
      Veteran Member
      Posts: 44
      Veteran Member
        Thanks Roger but moving those users to portal isn't an option right now. They will be the last to switch over and we will need to bring in design studio so we can make it functional for them.
        xxxxxttysfh
        Veteran Member
        Posts: 62
        Veteran Member

          Can anyone give us Tips on how to achieve this