Unable to store different qvds with same fields under different table label?

[User0]

I have few qvds for 2 different processes with same field names :
For example :
Process B01:
TableUser :UserId, Username , Email, ID
TableGroup: Groupname,GroupID
TableUGro:UserID,GroupID

Process B02:
TableUser :UserId, Username , Email, ID
TableGroup: Groupname,GroupID
TableUGro:UserID,GroupID

Process B03:
TableUser :UserId, Username , Email, ID
TableGroup: Groupname,GroupID
TableUGro:UserID,GroupID

While I am trying to load these qvds to store under different table lables , it is not working.
All the qvds are getting stored in the first table label .
Can you please help?

[cristianj23a]

Of course, just change the name of your QVD when using the STORE and make a DROP TABLE.

Process B01:
TableUser :UserId, Username , Email, ID
STORE SalesTable INTO [path/where/to/save/TableUser1.qvd] (qvd);
DROP TABLE TableUser

TableGroup: Groupname,GroupID
STORE SalesTable INTO [path/where/to/save/TableGroup1.qvd] (qvd);
DROP TABLE TableGroup

TableUGro:UserID,GroupID
STORE SalesTable INTO [path/where/to/save/TableUGro1.qvd] (qvd);
DROP TABLE TableUGro

Process B02:
TableUser :UserId, Username , Email, ID
STORE SalesTable INTO [path/where/to/save/TableUser2.qvd] (qvd);
DROP TABLE TableUser

TableGroup: Groupname,GroupID
STORE SalesTable INTO [path/where/to/save/TableGroup2.qvd] (qvd);
DROP TABLE TableGroup

TableUGro:UserID,GroupID
STORE SalesTable INTO [path/where/to/save/TableUGro2.qvd] (qvd);
DROP TABLE TableUGro

Process B03:
TableUser :UserId, Username , Email, ID
STORE SalesTable INTO [path/where/to/save/TableUser3.qvd] (qvd);
DROP TABLE TableUser

TableGroup: Groupname,GroupID
STORE SalesTable INTO [path/where/to/save/TableGroup3.qvd] (qvd);
DROP TABLE TableGroup

TableUGro:UserID,GroupID
STORE SalesTable INTO [path/where/to/save/TableUGro3.qvd] (qvd);
DROP TABLE TableUGro

[User0]

I am not trying to store the qvds , I am trying to have a table label for them, but all the qvds are coming under one process only .
Apologies , my question wording was not clear.

For example :

[p01_user]:

load * from 1.qvd

[p02_user]:

load * from 2.qvd

[p03_user]:

load * from 3.qvd

but in the data model there is only [p01_user] table with all the data. there is no [p02_user] or [p03_user].

[cristianj23a]

Surely since they have the same fields they are being concatenated automatically. To avoid that you should use NoConcatenate.

[p01_user]:

load * from 1.qvd

NoConcatenate

[p02_user]:

load * from 2.qvd

NoConcatenate

[p03_user]:

load * from 3.qvd

If you do that the tables are no longer concatenated, but doing that you will have synthetic keys because they have the same fields.

[marcus_sommer]

In many scenarios it's better not to split identically data-structures in different tables/files. Therefore I suggest to keep by your first approach - by adding an extra field Process with the appropriate B01/B02/B03 information to each load. With this information you will be able to differentiate between the sources within the script as well as within the UI as dimension/selection and/or set analysis condition.