Asyma E3 2012 - Securing assets and data - Robert Lavery

11
How To Make Securing Assets & Data A Snap

description

Asyma E3 2012

Transcript of Asyma E3 2012 - Securing assets and data - Robert Lavery

Page 1: Asyma E3 2012 - Securing assets and data - Robert Lavery

How To Make Securing Assets & Data A Snap

Page 2: Asyma E3 2012 - Securing assets and data - Robert Lavery

An Organization Needs To Secure Their Data

Banks

Customers

Inventory Items Vendors

Page 3: Asyma E3 2012 - Securing assets and data - Robert Lavery

Norming Solutions that Secure Data

� Bank Security:

Control which users can see or use certain Banks based on permission settings.

� AR Security:

Control user access to Customers, Price Lists, AR Sales History, based on permission settings.

� AP Security:

Control user access to Vendors, AP Purchase History, based on permission settings.

� Inventory Security:

Control user access to IC items and locations, based on permission settings.Control user access to IC items and locations, based on permission settings.

� Purchase Security:

Control user access to Vendors, AP invoice/payment, purchase order and purchase history, based on vendor group permission settings.

�Sales Security:

Control user access to Customers, Price Lists, Order Entry, Sales History, based on permission settings.

Page 4: Asyma E3 2012 - Securing assets and data - Robert Lavery

Bank Security – Banking Access Restrictions� Bank Look Up, Inquiry and Transactions:

Users can’t look up restricted banks or perform inquiries on data and transactions in BS, AR & AP.

� Adding new Banks:

Users can add new banks within a restricted range but can’t view the new bank.

� Posting Batches:

Posting is limited to batches that do not contain restricted banks. Can’t view a batch with restricted banks as the batch will not appear in the Batch List window.

� Payment & Receipt Entry:� Payment & Receipt Entry:

Users can not enter or view payment or receipt entries for restricted banks in AP & AR.

�Import & Export of Bank Data:

Users can not import and export data for restricted banks.

�Apply Bank Restrictions in Bank, AP & AR Reports: (Sample - BK1410.RPT)

Bank Security maintains a bank permission table (BSUSERD) to define user access to banks. You can include this table in any Accpac reports to apply security control in Bank, AP or AR Reports.

Page 5: Asyma E3 2012 - Securing assets and data - Robert Lavery

AR Security – Customer Access Restrictions� Customer Look Up, Inquiry and Transactions:

Users can’t look up restricted customers or perform inquiries on data and transactions in AR.

� Adding new Customers:

Users can add new customers within a restricted range but can’t view the new customer.

� Posting Batches:

Posting is limited to batches that do not contain restricted customers.

� Invoice & Receipt Entry:

Users can not enter or view invoice or receipt entries for restricted customers in AR.Users can not enter or view invoice or receipt entries for restricted customers in AR.

� Import & Export of Customer Data:

Users can not import and export data for restricted customers.

�Apply Customer Restrictions in AR Reports: (Sample – ARCULT01.RPT)

AR Security maintains a customer permission table (AQUSERD) to define user access to customers. You can include this table in any Accpac reports to apply security control in AR Reports.

Page 6: Asyma E3 2012 - Securing assets and data - Robert Lavery

AP Security – Vendor Access Restrictions

� Vendor Look Up, Inquiry and Transactions:

Users can’t look up restricted vendors or perform inquiries on data and transactions in AP.

� Adding new Vendors:

Users can add new vendors within a restricted range but can’t view the new vendor.

� Posting Batches:

Posting is limited to batches that do not contain restricted vendors.

� Invoice & Payment Entry:

Users can not enter or view invoice or payment entries for restricted vendors in AP.Users can not enter or view invoice or payment entries for restricted vendors in AP.

� Import & Export of Vendor Data:

Users can not import and export data for restricted vendors.

�Apply Vendor Restrictions in AP Reports: (Sample – APCULT01.RPT)

APSecurity maintains a vendor permission table (VSUSERD) to define user access to vendors. You can include this table in any Accpac reports to apply security control in AP Reports.

Page 7: Asyma E3 2012 - Securing assets and data - Robert Lavery

Inventory Security – Item/Location Access Restrictions

� Item & Location Look Up, Inquiry and Transactions:

Users can’t look up restricted Items & Locations or perform inquiries on data and transactions in IC, OE & PO. Items can be restricted by Item, Category or Account Set. (Not simultaneously.)

� Adding new Items & Locations:

Users can add new Items/Locations within a restricted range but can’t view the new Items/Loc.

� IC Receipt, Shipment, Internal Usage, Adjustments, Transfers, Assemblies Entry:

Users can not enter or view any IC entries for restricted Items & Locations in IC.

� Import & Export of Item & Locations Data:� Import & Export of Item & Locations Data:

Users can not import and export data for restricted Items & Locations.

�Apply Item & Location Restrictions in IC Reports: (Sample – ICITMST1.RPT & ICLOC01.RPT)

IC Security maintains a Item/Location permission table (ISUSERDI) to define user access to Items/Locs. You can include this table in any Accpac reports to apply security control in IC Reports.

Page 8: Asyma E3 2012 - Securing assets and data - Robert Lavery

Purchase Security – Vendor Access Restrictions

� Vendor Look Up, Inquiry and Purchase History Transactions:

Users can’t look up restricted vendors or perform inquiries on data and transactions in AP & PO. Vendors can be restricted by Vendor, Vendor Group or Account Set. (Not simultaneously.)

� Adding new Vendors:

Users can add new vendors within a restricted range but can’t view the new vendor.

� Entry & Posting of PO Order, Receipt, Returns & PO/AP Invoice, Credit/Debit Note Batches:

Users can not enter, view and post PO Orders, Receipts, Returns, PO/AP invoice, Credit/Debit Note entries for restricted vendors in AP & PO.

� Import & Export of Vendor Data:� Import & Export of Vendor Data:

Users can not import and export data for restricted vendors.

�Can Control Which Users Can Access PO Requisition with Blank Vendor

�Apply Vendor Restrictions in AP Reports: (Sample – APVENLT01.RPT)

PO Security maintains a vendor permission table (PSUSERD) to define user access to vendors. You can include this table in any Accpac reports to apply security control in AP Reports.

Page 9: Asyma E3 2012 - Securing assets and data - Robert Lavery

Sales Security – Customer Access Restrictions

� Customer & Price List Look Up, Inquiry and Sales History Transactions:

Users can’t look up restricted customers & price lists or perform inquiries on transactions in AR & OE.

Customers can be restricted by Customer, Customer Group or Account Set. (Not simultaneously.)

� Adding new Customers & Price Lists:

Users can add new customers & price lists within a restricted range but can’t view the new customer & price list.

� Entry & Posting of OE Order, OE/IC Shipment, Credit/Debit Note & OE/AR Invoice, Batches:

Users can not enter, view and post OE Orders, Shipments, Credit/Debit Notes, OE/AR invoices, entries for restricted customers & price lists in AR, IC & OEfor restricted customers & price lists in AR, IC & OE

� Import & Export of Customer & Price List Data:

Users can not import and export data for restricted customers & price lists.

�Apply Customer & Price List Restrictions in AR/OE/IC Reports: (Sample – ARCULT01.RPT)

Sales Security maintains a customer/price list permission table (SSUSERDC) to define user access. You can include this table in any Accpac reports to apply security control in AR, OE, IC Reports.

Page 10: Asyma E3 2012 - Securing assets and data - Robert Lavery

Have a look

Page 11: Asyma E3 2012 - Securing assets and data - Robert Lavery

Agenda