Skip to Content
0
May 28, 2020 at 09:10 AM

Transaction BP Confusing Search on Blocking reasons

100 Views

Hello transaction BP experts

in recent project we encountered a strange issue when maitaining blocking reasons using different logon languages
e.g. English EN and German DE.

The search help shows different sets of possible values especially regarding cutomer owned blocking reasons like Y1...Y4, YI, YA.
If we enter - with logon language EN - values from the value set been displayed in search help and logon language German we receive an error message telling us that value is not allowed.

Technical Information about the search help display this

Search Help Name H_TVAST
Help type SH Search help
Binding Type Check table help

Details of that search help

Elementary Help H_TVAST
Short description Sales Order Type Blocks

Selection Method TVAST
Text Table -- E M P T Y --

We found the reason for that strage bebavior. In opposite to the table used in the tearch help (TVAST)
the Customizing table for Blocking Reasons is

Transparent Table TVASP
Short Description Sales Documents: Blocking Reasons
with fields

MANDT MANDT CLNT Client
AUFSP AUFSP CHAR Indicator for Order Block
AUART AUART CHAR Sales Document Type

The table TVAST seems to be the text table of TVASP.
But that is not defined in the DDIC.
Message
Table TVASP does not have a text table
Message no. E2238
is displayed in SE11 for table TVASP when we use menue function
Goto | Text Table

So this facts lead into serveral questions:
- Why is that like this?
- Does it rearly make sense to have different value sets depending
on the logon languge of the user working on a buisiness case?
- Which economically or business reasons explain that behavior?
- Or is it simply a bug?

We are higly interested in your answers.

Best Regards

Stephan Weber