SAP Library - Find your answers

TSTC - SAP Transaction Codes

Edit, create, delete or adjust your database table

The database utility is the interface between the ABAP Dictionary and the relational database underlying the R/3 System.

This tools allows you to delete all the data in the tables.

You can call the database utility from the initial screen of the ABAP Dictionary with

Utilities -> Database utility (Transaction SE14).

You can use the database utility to edit all the database objects that are generated from objects of the ABAP Dictionary.

These are database tables that are generated from transparent tables or physical table pools or table clusters, indexes, database views and matchcode pooled tables or matchcode views.

If you want to use the database utility, you need authorization for authorization object

Question: How do I create an new auth group and assign a table to this group in S_TABU_DIS

Answer:
Tcode SUCU, The "group" does not have to exist but you can create one in SE54

If you want to exclude a table x from copying in client copy run report RSCCEXPT
Goto transaction SA38 , enter the report name and execute. You will see the output screen as

I need to copy table entries from client 000.
I have identified which entries I need to copy through running RPULCP00 but I don't know how to move the entries.

The simplest way is to go into the table through SM31
Then in your top row of buttons there should be one called 'utilities' from here select 'adjust',
Then select the client that you want to compare/copy from (you need to have an RFC destination set up).
This will then show you the contents of the table in both clients and identify the status of each record, they will fall into the following categories:
ML Differences, logon client entry
MR Differences, comparison client entry
L Entry only exists in logon client
R Entry only exists in comparison client
Identical entries
(M) Differences only in hidden fields

You should be able to scroll down the table, select the entries that you want to import, then hit the 'adjust' button, then hit the 'copy all' button, then back out with the green arrow, and save your table.

That should do the job.

Support packs are stored in tables PAT01 and PAT03.

Goto SE14

In the field "Obj.name" mention the table name and select "Tables", click on EDIT.

Select the "Delete Data" radio button and click on "Activate and Adjust Database"

Syntax error in SDCC, table inconsistency between ABAP Dictionary and the database, transport error 8 during the generation of ABAP Dictionary. When you call Transaction SDCC, a termination occurs due to a putative syntax error because a table is not known or active. When you check this with the ABAP dictionary (SE11), you notice, that the table is active or inactive, however it is not possible to activate it. The activation might terminate with the error message 'Inconsistency between ABAP Dictionary and database'. A check of the affected object also delivers this error.


Proceed as follows:

Log on as user DDIC
Call Transaction SE14
Enter the affected table name and
select EDIT
In the following screen, choose Table -> Reconstruct
Confirm the execution
Call Transaction SE11
Enter the affected table name
Display
Activate
If - after you chose EDIT -, the error message occurs that the table only exists on the database, you need to activate the source and the runtime object.

Call Transaction SE37:
-> Function module 'DD_TABL_ACTM' -> Single test
Under import parameter MODE, enter the number 12 and under TABNAME the corresponding table name
-> Execute (F8) -> Export parameter ACT_RESULT must be 0
Call Transaction SE14 again as described above.
-> Extras -> Database object -> Check,
as well as
-> Extras -> Runtime object -> Check
inconsistencies should no longer be contained.
If you cannot switch to the EDIT mode in Transaction SE14, which means no modifications are allowed in the customer system, then proceed as follows:

Call function module 'DD_TABL_ACTM' as described above.
Then call Transaction SE14 again and verify that the table has been activated.
As a result, this ensures that the SDCC can be executed.
The menu options in Transaction SE14 are
-> Extras -> Database object -> Check,
as well as
-> Extras -> Runtime object -> Check
inconsistencies should no longer be contained.
If this is not the case, open a CSN message under the BC-DWB-DIC-ED component.

Lock Transaction SM12:

The SAP system is equipped with a special lock mechanism the purpose of the lock mechanism is to prevent two transactions from changing the same data on the database simultaneously.
Locks are defined generically as "lock objects" in the Data Dictionary. Lock entries are usually set and deleted automatically when user programs access a data object and release it again.

The SAP lock mechanism is closely related to the Update Mechanism .

The documentation is divided into the following sections:

SAP Lock Concept: describes how the SAP lock works. You have to understand the concepts described here in order to use the SAP locks when you are programming applications. You can use different types of locks. The lock mode describes what type of lock it is.

S (shared Lock): Several users can access locked data at the same time in display mode. Requests from further shared locks are accepted, even if they are from different users. An exclusive lock set on an object that already has a shared lock will be rejected.

E(Exclusive): An exclusive lock protects the locked object against all types of locks from other transactions. Only the same lock owner can reset the lock .

Important Profile Parameters: A list of the profile parameters relevant for the lock concept.
enque/table_size: Size of the lock table managed by the enqueue server in the main memory. The lock table contains information on which locks are currently held by whom.

In this case, you should check whether the update server is functioning correctly, since the lock table can grow very fast if the update function stops. If no update problems exist, you can use this parameter to increase the size of the lock table.
The Computing Center Management System (CCMS) monitors the status of the lock table constantly and outputs warnings if the space available is not adequate.
Default value: 4096kb

rdisp/wp_no_enq: Number of enqueue work processes that are to run on this instance.
rdisp/enqname: Name of the application server that provides the enqueue service.

Managing Lock Entries: It describes lock management , which you use to display, check, and delete lock entries. This may be necessary if the SAP dispatcher, the operating system, or the network connection fails, and the dispatcher cannot delete lock entries. In this case, invalid lock entries remain effective and block access to the locked data when the system is restarted.

How to monitor a Lock entry:In SM12 check any lock entry older than 2 days, if any outdated entry check the corresponding User and check the user online or offline in AL08 and contact that User (you can get the User info from su01) and inform about the lock else if the user is offline release the table from lock by deleting the lock.

To edit the User Menu or SAP Menu of a particular user go through the follwing steps:-

Enter transaction code SM30 (Maintain Table Views) in your SAP command field and maintain USERS_SSM table. You would notice that no data maintained in this table during initial access. To maintain entries, click ‘New Entries’ button. Enter the individual username on the User Name field and select the USER Menu or SAP Menu ( As per the requirements)