Tables play an important role in the way data within the SAP R/3 system is processed and generated. All application data in SAP gets stored in tables. This would include all financial information within SAP R/3. It is for this reason that auditing tables in SAP R/3 is so important. Important table parameters in SAP R/3 like table logs, critical tables, table contents, structural changes to tables need to be monitored and audited. Auditing tables in SAP can be undertaken by first looking at the process by which tables are managed and then going on to the technical aspects of the table or table parameters.

Both the above aspects are important to adequately secure tables in SAP. Simply speaking, technical table settings in SAP support laid down procedures for managing tables. Below, I am listing down some critical audit questions normally used when auditing tables in SAP R/3:

1. Is a formal procedure in place for creation of tables?

2. Is the procedure documented and circulated to all concerned personnel?

3. Are naming conventions used to distinguish, differentiate between tables?

4. Are authorization groups used to restrict access to tables?

5. Is logging enabled on critical tables?

Related Posts on SAP

Key Milestones in ERP Implementation
SAP Questions & Answers Database
Change Documents in SAP R/3
Breakpoints in SAP R/3