EWM VAS - how come the strange DB model, with client-number in DB tables (/1OM/VASOVASH100) ?

[joachimrees1]

I am working with (S/4HANA) EWM VAS (Value Added Services) and am a little stunned by the data model. I have a few question, but try to keep to the "ask only one Question per Question rule".

The VAS table on DB-level are generated on client level.

So for the VAS-Header, in client 100, you'd have to look at table /1OM/VASOVASH100 , and in in client 125 at you would have to look at /1OM/VASOVASH125 .

This can be by dynamically providing the table to the select, and something like this:

    CONCATENATE '/1OM/VASOVASH' sy-mandt INTO DATA(vas_header).
    CONCATENATE '/1OM/VASOVASA' sy-mandt INTO DATA(vas_activity).
    CONCATENATE '/1OM/VASOVASI' sy-mandt INTO DATA(vas_item).

Question:

Why was this modeled this way? (What thougths have been put into it, what upsides does it have ?)

[joachimrees1]

I know, a direct db select is probably not the right thing to do - I am asking for that here: https://answers.sap.com/questions/13587171/ewm-vas-value-added-services-how-to-read-a-vas-ord.html

Nevertheless, I think the desire to understand a design decition is valid!

[joachimrees1]

Not important, but I am still courious about this!

Context:

>Fact: EWM VAS-Header, in client 100, you'd have to look at table /1OM/VASOVASH100 , and in in client 125 at you would have to look at /1OM/VASOVASH125 .

>Question: Why was this modeled this way? (What thougths have been put into it, what upsides does it have ?)