How to determine/prove in SAP that a T-Code edits an SAP table?

[Former Member]

Hello,

Can someone help me with these two questions. I'm not an expert in SAP and I do not have access as a Basis Administrator (so I don't have access to SM30, SE11, etc.). I'm an Auditor. Here are my two questions:

1. Is there a way to prove or that I can look or interpret in SAP (via tables configurations in SE16, SE80, SE84 or SE93) to determine/verify/prove if a T-Code can edit a particular table? For example, T-Codes OVTP and VOFA, I believe can edit/maintain table TVFK. BUT How can I show that those two T-Codes in fact modify that table?

2. Is there a way that I can go look at a table and identify which T-Codes have the ability to edit that table. For example, table T169G; is there a way to know which T-Codes can add/edit/modify the tolerances in that table (T169G).

Thank-you in advance. I'm not an expert and my access to SAP is not Basis. However I can use those T-Codes and if some one can point to me the steps to get that information above I can follow those.

GPB

[Former Member]

Hello Colleen,

Thanks for the answer. Let me follow-up with specific results. By the way, I do have access to SE93. But please explain how would I use SE93 to determine if a T-Code can update a table?

Here are specific examples, using your suggestion of the TSCTP table.

1. For tables T169G and T169L: I go to table TSTCP and input *T169G* or *T169L* in the 'Parameter' field. The system returns the "Notable entries found for specified key." Does that mean that there are no T-codes that can edit those two tables?

2. For table TVFK, I type *TVFK* again in the parameter filed and the system returns the following 13 results. I don't know how to interpret the results. I only "knew" that T-Codes OVTP and VOFA where the ones used to edit table TVFK. But with the 13 results I don't know how to interpret what the system returns.

Can you please provide some help?

[Colleen]

Hi Greg

For some situations, you can identify if a specific transaction does update a table. This would apply to parameter transaction definitions in SE93 that skip initial screen for SM30, SM31 and SM34. If you don't have SE93 access but do have SE16 then you can look at the TSTCP table to see if there is a paramter definition. Most of these scenarios are going to be configuration tables or small master data tables.

For example if table T169G has a transaction code then go to SE16 table TSTCP and search in the string for *T169G* to see if any transactions appear. However, if a view has been created (combination of tables) then you would need to look for the view.

For other transactions, it really depends on the program and within the program the logic. Unfortunately, there won't be a straight rule. You could look at a code scan to search for a table and it might find the function module that triggers the update. Alternatively, run an SQL trace on user executing a transaction to see what tables are hit.

All of this would require an elevated level of access.

It might be easier to give specific examples that you are trying to track down or talk to an ABAP developer for advise.