Author: Robert Metzker
Further discussion on this script should take place in this topic.
Author Notes:
club_dos.sql.zip (9.0 KB)
efashion_dos.sql.zip (1255.0 KB)
BOB Downloads (BOB member since 2003-05-05)
These scripts are helpful, thanks. I’m surprised i’m the first to report that
the scripts name the Year column in the aggregate tables as Year whereas eFashion universe has Yr in all objects.
the scripts name the ID columns in the aggregate tables as ID whereas eFashion has the objects set agg1_id and agg2_id.
agg_yr_qt table has column quarter whereas eFashion universe has the object defined as qtr.
In addition to these, i am getting many errors with my universe.
Does anyone have an Oracle compatible eFashion universe?
Update:
Looks like i may have an outdated version of eFashion? i asked a couple of friends and they seem to have the same version one as i do… Yet i found different columns (with ID and YEAR instead of agg1_id and Yr) in a BO presentation online. i would post a snapshot but can’t do so in Downloads…
twenty5 (BOB member since 2008-01-22)
I found a couple of issues when trying to populate the efashion table UNUSED_OUTLET_LOOKUP_FULL.
The issues are that :
-
the SHOP_NAME column as a varchar(30) was not big enough for the data in some of the INSERT lines (where max character length = 36). So I changed the create table table statement to be “SHOP_NAME varchar2(40)” rather than “SHOP_NAME varchar2(30)”.
-
Also there a couple of INSERT lines that need the apostrophe escaping in “St John’s”. i.e. change to “St John’'s”.
But then again, this is not used in the eFashion universe itself…
Darth Services 
(BOB member since 2007-11-20)