What is the best way to store a client-independent program parameter?

Viewed 293

I need to store a list of transactions where my user exit wouldn't run. This list would preferably be client-independent (user exit needs same behaviour across clients). Using a database table may be overkill for a simple list ? Variants has been suggested but the client-independent table for variants is obsolete.

Thank you for your suggestions.

1 Answers

Just if you don't want to create a new table, ECC has a special transaction for that task: STVARV/STVARVC.

Defining and maintaining Selection Variables

It serves for creating and maintaining business-specific variants, variables, transactional parameters and so on.

After the release 6.40 changes have been introduced (notes 1994216, 770084, 557314 ) that made TVARV obsolete and left only client-specific TVARVC, however this shouldn't make you frustrated.

Though you cannot use TVARVC tcode for maintaining records, nothings prevents you from bypassing this stupid limitation and create entries in TVARV manually, this table is client-independent.

Also, client-specific TVARVC table has CLIE_INDEP field that probably serves for the similar purpose

enter image description here

however I didn't test if this flag functions properly, it is up to you.

Related