Transaction variant

This blog will explain how to create a transaction variant.

It will also give a list of how-to OSS notes that might help you for your situation.

Questions that will be answered in this blog are:

  • How to set up a transaction variant?
  • Where can I find the restrictions for transaction variants?
  • Where can I find how-to instructions for transaction variants?

Set up transaction variant

As example we will use SU3 transaction to maintain own user data. On the screen there is also a password reset button we want to remove:

To set up a transaction variant start transaction SHD0:

Enter in transaction code SU3 and in the variant name the Z name of the variant you want to create. Now hit the create button. Execute the transaction and go back to the popup screen. On the popup screen change the menu options and toggle the button to invisible:

The transaction variant is now created:

To assign a transaction code, don’t go to transaction SE93, but stay in the SHD0 transaction and select the menu option Goto / Create Variant Transaction:

Assign a ZSU3 as transaction code. Save the variant transaction and test it by entering the new ZSU3 transaction code:

The password reset button is gone in this variant.

SAP references

SAP blog on transaction variant: link.

SAP help file on transaction variant: link.
Restriction OSS note: 331360 – Transaction variants are not always possible.

OSS notes

How-to OSS notes:

Analysis of SYS_LOB* tables

When you are trying to manage your database size, you might see large SYS_LOB* tables on Oracle based systems.

Questions that will be answered in this blog are:

  • How can I find large SYS_LOB tables in my Oracle based SAP system?
  • How can I find the real table for the SYS_LOB?

Finding SYS_LOB table size

In DB02 select all segments larger than 1 GB with name SYS_LOB*:

Output might be like this:

On the tab Lobs you can see the table:

From SYS_LOB name to table

Next to the direct view in DB02 as shown above, OSS note 2142497 – What to do for large lobsegment on Oracle database? describes several ways of determining the translation from the SYS_LOB label to the real table.

You can use ST04 SQL query and fire this query: replace the SYS_LOB number from the one in your own system:

SELECT OWNER, TABLE_NAME, COLUMN_NAME FROM DBA_LOBS
WHERE 'SYS_LOB0007061918C00006$$' IN (SEGMENT_NAME, INDEX_NAME);

Or in ST04, you launch the DBA view for DBA_LOBS:

Result:

In this case table DMC_INDXCL is the source of the SYS_LOB. Knowing this it will easily lead you to OSS note 2704146 – How to delete data in DMC_INDXCL? – SLT for clean up.

Frequent SYS_LOB tables

Frequent SYS_LOB tables and solutions: