Hi folks! I'm trying to get the attributes of shipment activities in the VTTK, but when I link the VTTK through the VTTP in the Datamodel. I have the following error message "Not common table" Do you know how to handle this?
Best answer by Anonymous
Hi Matt, thanks for your reply.
The join we have is the following one:
VTTK -> VTTP(This one has an internal join with the VBFA) -> VBAP -> ACTIVITY_TABLE
If I want to make the relationship between these tables in a transformation, that works, but when I link these tables in the data model and try to create an OLAP table to get the attributes from the ACTIVITY_TABLE I the VTTK, Celonis shows the error "Not Common Table". I believe the reason for this is that Celonis only allows relations between tables in this way:
1:N -> 1:N -> 1:N or N:1 -> N:1 -N:1
and the relation we have is the following:
1:N -> N:1 -> 1:N
So I was thinking to create a single view with all internal tables that are necessary for the analysis inside a transformation, including the activity table.
You'll likely have to do a combination of Pullup functions and BIND(). We have something similar with VTTK to EKKO. It's something like
PU_FIRST(EKKO,PU_FIRST("EKPO",BIND("LIPS",PU_FIRST("LIKP",BIND("VTTP",[VTTK_FIELD])))))
So you might have to do something similar where you pullup and bind on the way through. Because you're combining parent-child table relationships across the data model
Can you provide a screenshot of what your Data Model looks like?
Can you provide a screenshot of what your Data Model looks like?
Hi Matt, thanks for your reply.
The join we have is the following one:
VTTK -> VTTP(This one has an internal join with the VBFA) -> VBAP -> ACTIVITY_TABLE
If I want to make the relationship between these tables in a transformation, that works, but when I link these tables in the data model and try to create an OLAP table to get the attributes from the ACTIVITY_TABLE I the VTTK, Celonis shows the error "Not Common Table". I believe the reason for this is that Celonis only allows relations between tables in this way:
1:N -> 1:N -> 1:N or N:1 -> N:1 -N:1
and the relation we have is the following:
1:N -> N:1 -> 1:N
So I was thinking to create a single view with all internal tables that are necessary for the analysis inside a transformation, including the activity table.
Hi Matt, thanks for your reply.
The join we have is the following one:
VTTK -> VTTP(This one has an internal join with the VBFA) -> VBAP -> ACTIVITY_TABLE
If I want to make the relationship between these tables in a transformation, that works, but when I link these tables in the data model and try to create an OLAP table to get the attributes from the ACTIVITY_TABLE I the VTTK, Celonis shows the error "Not Common Table". I believe the reason for this is that Celonis only allows relations between tables in this way:
1:N -> 1:N -> 1:N or N:1 -> N:1 -N:1
and the relation we have is the following:
1:N -> N:1 -> 1:N
So I was thinking to create a single view with all internal tables that are necessary for the analysis inside a transformation, including the activity table.
You'll likely have to do a combination of Pullup functions and BIND(). We have something similar with VTTK to EKKO. It's something like
PU_FIRST(EKKO,PU_FIRST("EKPO",BIND("LIPS",PU_FIRST("LIKP",BIND("VTTP",[VTTK_FIELD])))))
So you might have to do something similar where you pullup and bind on the way through. Because you're combining parent-child table relationships across the data model
Hi Matt, thanks for your reply.
The join we have is the following one:
VTTK -> VTTP(This one has an internal join with the VBFA) -> VBAP -> ACTIVITY_TABLE
If I want to make the relationship between these tables in a transformation, that works, but when I link these tables in the data model and try to create an OLAP table to get the attributes from the ACTIVITY_TABLE I the VTTK, Celonis shows the error "Not Common Table". I believe the reason for this is that Celonis only allows relations between tables in this way:
1:N -> 1:N -> 1:N or N:1 -> N:1 -N:1
and the relation we have is the following:
1:N -> N:1 -> 1:N
So I was thinking to create a single view with all internal tables that are necessary for the analysis inside a transformation, including the activity table.
Thanks Matt! that works
Login to the community
No account yet? Create an account
Login with SSO
Login with Saml2 Login with OpenIdConnectEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.