--- title: "Authorization Issues When Reading Tables" slug: "how-to-fix-sap-authorization-issues-when-reading-tables" updated: 2021-12-30T15:19:27Z published: 2021-12-30T15:19:27Z --- > ## Documentation Index > Fetch the complete documentation index at: https://success.panaya.com/llms.txt > Use this file to discover all available pages before exploring further. # Authorization Issues When Reading Tables Once you complete extracting your [Custom Code](/v1/docs/how-to-extract-and-upload-your-custom-code), you may encounter**authorization issues** in the final **[Job Log](/v1/docs/how-to-retrieve-the-sm37-job-log-for-panaya-support)**. These issues can be related to the Production RFC user or the user running the extraction. **Examples of a Job Log Authorization Issue** - RFC_READ_TABLE of [TABLE_NAME]. Error: NOT_AUTHORIZED - RFC_READ_TABLE of E070. Error: NOT_AUTHORIZED - ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1640090231048.png) **How to solve this?** You will need to define/update the Authorization Group for Object S_TABU_DIS to the Production RFC user, as described in [this article](/v1/docs/authorizations-required-for-the-code-extraction-rfc-user)  **How do I know which Authorization Group to add?** 1. Run transaction **SE11**(ABAP Dictionary: Initial Screen) 2. Type the **Database Table****name (1)** 3. Select **Display (2)** ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1640090239291.png) 4. In the upper menu, select **Utilities (1)**and then **Table Maintenance Generator (2)** ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1640090247474.png) 5. Take note of the **Authorization Group** ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1640090260453.png) 6. If this Authorization Group is not mentioned in [this article](/v1/docs/authorizations-required-for-the-code-extraction-rfc-user), for Object S_TABU_DIS, you will need to add it to the RFC user definition 7. Run the extractor