Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have the following problem:
- In my datamodel, two tables are linked, I'll name them >>Delivery_plan<< and >>SO_table<<.
- The two are linked by four fields: Item_no, freighttype, customer and DueDate, all of which are present in both tables.
- The table >>SO_table<< has a fifth dimension, however - one order (made up of those four fields) has many different box_IDs
=> several lines of the >>SO_table<< are thus linked to just one line in the >>Delivery_plan<<.
=> Thus far, that is good and well and correct.
- All the items in the >>SO_table<< have not yet been shipped to the customer, however.
- I want to also display the items which have been shipped, so I have a second instance of the >>SO_table<<;
- This >>SO_table_shipped<< is linked to the >>Delivery_plan<< by the same four fields, that works
- However, it also has a fifth dimension, a nr. of box_IDs, just like the first.
<=> Every box_ID must be unique, so the IDs of the shipped >>SO_table_shipped<< naturally don't match those of the first instance.
=> So all I can do is display the total volume that has been shipped for this >>Delivery_plan_key<< in every line.
I have already aggregated that >>SO_table_shipped<< and made a sum of the quantity, so I now have a small table with the four keyfields and a total volume that is linked to my >>Delivery_plan<<.
The issue is only this: The diagram actually has five dimensions, but I can link by only four as I have just explained - so I need to ignore the fifth dimension, which is the box_ID - only, in my aggregated >>SO_table_shipped<<, I don't have the box_ID anymore.
Can I do that using Set_analysis?
Thanks a lot!
Best regards,
DataNibbler
OK,
I think this is done now.
It got still a bit more complicated along the way because another element of my key varies in time as I found out, so I could connect this to the delivery_plan by only a three-part key.
Well, now I have about the info I wanted - not quite as precise as I could have wished for, but I guess it's the best that can be done.
Best regards,
DataNibbler
OK,
I think this is done now.
It got still a bit more complicated along the way because another element of my key varies in time as I found out, so I could connect this to the delivery_plan by only a three-part key.
Well, now I have about the info I wanted - not quite as precise as I could have wished for, but I guess it's the best that can be done.
Best regards,
DataNibbler