Asyma E3 2012 - Securing assets and data - Robert Lavery
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Asyma E3 2012 - Securing assets and data - Robert Lavery

  • 270 views
Uploaded on

Asyma E3 2012

Asyma E3 2012

More in: Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
270
On Slideshare
270
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
1
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. How To Make Securing Assets & Data A Snap
  • 2. An Organization Needs To Secure Their Data Customers Banks Inventory Items Vendors
  • 3. 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. 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 onpermission settings.
  • 4. 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 restrictedbanks as the batch will not appear in the Batch List window. 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 caninclude this table in any Accpac reports to apply security control in Bank, AP or AR Reports.
  • 5. 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. 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.
  • 6. 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. 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. Youcan include this table in any Accpac reports to apply security control in AP Reports.
  • 7. 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: 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.
  • 8. 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 Noteentries for restricted vendors in AP & PO. 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. Youcan include this table in any Accpac reports to apply security control in AP Reports.
  • 9. 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, entriesfor 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. Youcan include this table in any Accpac reports to apply security control in AR, OE, IC Reports.
  • 10. Have a look
  • 11. Agenda