Forecast Roll-Over Script across multiple years
Hello Experts,
I currently have the below Script and Prompt but it only works for one Fiscal year and I need help changing it so that it can be used across multiple years, my issue is below:
If I have project TEST and it started in 2013.011 and ends in 2014.004, I have forecast values for all periods so when I run the script I'm prompted to "select forecast year" and "select forecast version based on previous period"
So when I run from 2013.11 (forecast version P11) to 2013.12 (forecast version P12) that works fine but it's not working to roll-over from 2013.012 to 2014.001
Any help is much appreciated.
Thx,
Shane
*****SCRIPT*****
//%CATEGORY_SET% - contains P9, STARTMNTH = 10, PREVFC=P8
*SELECT(%SM%,"[STARTMNTH]",F_CATEGORY,"[ID]='%F_CATEGORY_SET%')
//$YY$ - contain planning year selected by user from DM combobox
*SELECT(%FCSTMNTH%,"[ID]",TIME,"[ID]>'$YY$.%SM%' AND [YEAR]='$YY$' AND [CALC]='N'")
*SELECT(%ACTMNTH%,"[ID]",TIME,"[ID]<'$YY$.%SM%' AND [YEAR]='$YY$' AND [CALC]='N'")
*SELECT(%PF%,"[PREVFCST]",F_CATEGORY,"[ID]='%F_CATEGORY_SET%')
//To copy FORECAST XX we use
*XDIM_MEMBERSET F_CATEGORY=%PF%
*XDIM_MEMBERSET TIME=$YY$.%SM%,%FCSTMNTH%
*WHEN F_CATEGORY
*IS *
*REC(EXPRESSION=%VALUE%,F_CATEGORY=%F_CATEGORY_SET%)
*ENDWHEN
//To copy ACTUAL we use
*XDIM_MEMBERSET F_CATEGORY=ACTUAL
*XDIM_MEMBERSET TIME=%ACTMNTH%
*WHEN F_CATEGORY
*IS *
*REC(EXPRESSION=%VALUE%,F_CATEGORY=%F_CATEGORY_SET%)
*ENDWHEN
*****PROMPT*****
PROMPT(MESSAGE,"Create Forecast Based on Previous")
PROMPT(COMBOBOX,%YY%,"Select Forecast Year:",0,,{2014,2015,2016,2017,2018})
PROMPT(SELECTINPUT,%SELECTION%,,"Select the Forecast Version:","F_CATEGORY")
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SUSER,%USER%)
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SAPPSET,%APPSET%)
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SAPP,%APP%)
INFO(%EQU%,=)
INFO(%TAB%,;)
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,TAB,%TAB%)
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,EQU,%EQU%)
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SELECTION,%SELECTION%)
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,LOGICFILENAME,FORECAST.LGF)
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,REPLACEPARAM,YY%EQU%%YY%)
OK - I'll try explain this another way, I have 2 records for "ACTUALS" in 2013 (this is DEV system)
1st record - Project A-000001 / 2013.010 for $2000
2nd record - Project A-000036 / 2013.012 for $5000
Prompts
PARAM - YY=2013
DATA REGION - F_CATEGORY=P12
Here's the Script:
//%CATEGORY_SET% - contains P9, STARTMNTH = 10, PREVFC=P8
*SELECT(%SM%,"[STARTMNTH]",F_CATEGORY,"[ID]='%F_CATEGORY_SET%')
//$YY$ - contain planning year selected by user from DM combobox
*SELECT(%FCSTMNTH%,"[ID]",TIME,"[ID]>'$YY$.%SM%' AND [CALC]='N'")
*SELECT(%ACTMNTH%,"[ID]",TIME,"[ID]<'$YY$.%SM%' AND [YEAR]='$YY$' AND [CALC]='N'")
*SELECT(%PF%,"[PREVFCST]",F_CATEGORY,"[ID]='%F_CATEGORY_SET%')
//To copy FORECAST XX we use
*XDIM_MEMBERSET F_CATEGORY=%PF%
*XDIM_MEMBERSET TIME=$YY$.%SM%,%FCSTMNTH%
*WHEN F_CATEGORY
*IS *
*REC(EXPRESSION=%VALUE%,F_CATEGORY=%F_CATEGORY_SET%)
*ENDWHEN
//To copy ACTUAL we use
*XDIM_MEMBERSET F_CATEGORY=ACTUAL
*XDIM_MEMBERSET TIME=%ACTMNTH%
*WHEN F_CATEGORY
*IS *
*REC(EXPRESSION=%VALUE%,F_CATEGORY=%F_CATEGORY_SET%)
*ENDWHEN
RESULT
PLS note that there is only 1 record for "ACTUAL" and that's the 1st record - Project A-000001 / 2013.010 for $2000
2nd record - Project A-000036 / 2013.012 for $5000 is MISSING
LGX:
*XDIM_MEMBERSET F_CATEGORY=P11
*XDIM_MEMBERSET TIME=2013.012,2014.001,2014.002,2014.003,2014.004,2014.005,2014.006,2014.007,2014.008,2014.009,2014.010,2014.011,2014.012,2015.001,2015.002,2015.003,2015.004,2015.005,2015.006,2015.007,2015.008,2015.009,2015.010,2015.011,2015.012,2016.001,2016.002,2016.003,2016.004,2016.005,2016.006,2016.007,2016.008,2016.009,2016.010,2016.011,2016.012,2017.001,2017.002,2017.003,2017.004,2017.005,2017.006,2017.007,2017.008,2017.009,2017.010,2017.011,2017.012,2018.001,2018.002,2018.003,2018.004,2018.005,2018.006,2018.007,2018.008,2018.009,2018.010,2018.011,2018.012,2019.001,2019.002,2019.003,2019.004,2019.005,2019.006,2019.007,2019.008,2019.009,2019.010,2019.011,2019.012,2020.001,2020.002,2020.003,2020.004,2020.005,2020.006,2020.007,2020.008,2020.009,2020.010,2020.011,2020.012
*WHEN F_CATEGORY
*IS *
*REC(EXPRESSION=%VALUE%,F_CATEGORY=P12)
*ENDWHEN
*XDIM_MEMBERSET F_CATEGORY=ACTUAL
*XDIM_MEMBERSET TIME=2013.001,2013.002,2013.003,2013.004,2013.005,2013.006,2013.007,2013.008,2013.009,2013.010,2013.011
*WHEN F_CATEGORY
*IS *
*REC(EXPRESSION=%VALUE%,F_CATEGORY=P12)
*ENDWHEN
LOG:
LOG BEGIN TIME:2014-03-14 09:36:23
FILE:\ROOT\WEBFOLDERS\F_COUNCIL \ADMINAPP\Forecasting\TEST.LGF
USER:096655
APPSET:F_COUNCIL
APPLICATION:Forecasting
[INFO] GET_DIM_LIST(): I_APPL_ID="Forecasting", #dimensions=8
F_CATEGORY,F_ENTITY,F_PERSON,F_PROJECT,F_SECTION,F_WBSE,MEASURES,TIME
#dim_memberset=2
F_CATEGORY:P11,1 in total.
TIME:2013.012,2014.001,2014.002,2014.003,2014.004,...85 in total.
REC :%VALUE%
CALCULATION BEGIN:
QUERY PROCESSING DATA
QUERY TIME : 1235.46 ms. 285 RECORDS QUERIED OUT.
QUERY REFERENCE DATA
CALCULATION TIME IN TOTAL :672.78 ms.
285 RECORDS ARE GENERATED.
CALCULATION END.
ENDWHEN ACCUMULATION: 285 RECORDS ARE GENERATED.
DATA TO WRITE BACK:
F_CATEGORY F_ENTITY F_PERSON F_PROJECT F_SECTION F_WBSE TIME SIGNEDDATA
P12 4000 000000 A-000036 000 A-000036.1.01 2013.012 103.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.001 104.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.002 105.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.003 106.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.004 107.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.005 108.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.006 109.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.007 110.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.008 111.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.009 112.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.010 113.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.011 114.00
P12 4000 000000 A-000036 000 A-000036.1.01 2014.012 115.00
P12 4000 000000 A-000036 000 A-000036.1.01 2015.001 116.00
P12 4000 000000 A-000036 000 A-000036.1.01 2015.002 117.00
P12 4000 000000 A-000036 000 A-000036.1.01 2015.003 118.00
P12 4000 000000 A-000036 000 A-000036.1.01 2015.004 119.00
P12 4000 000000 A-000036 000 A-000036.1.01 2015.005 120.00
P12 4000 000000 A-000036 000 A-000036.1.01 2015.006 121.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2013.012 235.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.001 236.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.002 237.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.003 238.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.004 239.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.005 240.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.006 241.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.007 242.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.008 243.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.009 244.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.010 245.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.011 246.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2014.012 247.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2015.001 248.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2015.002 249.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2015.003 250.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2015.004 251.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2015.005 252.00
P12 4000 000000 A-000036 000 A-000036.1.01.01 2015.006 253.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2013.012 344.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.001 345.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.002 346.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.003 347.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.004 348.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.005 349.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.006 350.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.007 351.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.008 352.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.009 353.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.010 354.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.011 355.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.012 356.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.001 357.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.002 358.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.003 359.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.004 360.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.005 361.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.006 362.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2013.012 494.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.001 495.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.002 496.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.003 497.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.004 498.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.005 499.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.006 500.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.007 501.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.008 502.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.009 503.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.010 504.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.011 505.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.012 506.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.001 507.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.002 508.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.003 509.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.004 510.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.005 511.00
P12 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.006 512.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2013.012 573.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.001 574.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.002 575.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.003 576.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.004 577.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.005 578.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.006 579.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.007 580.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.008 581.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.009 582.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.010 583.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.011 584.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2014.012 585.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2015.001 586.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2015.002 587.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2015.003 588.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2015.004 589.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2015.005 590.00
P12 4000 000000 A-000036 000 A-000036.1.01.02 2015.006 591.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2013.012 663.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.001 664.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.002 665.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.003 666.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.004 667.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.005 668.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.006 669.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.007 670.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.008 671.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.009 672.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.010 673.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.011 674.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.012 675.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.001 676.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.002 677.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.003 678.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.004 679.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.005 680.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.006 404.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2013.012 765.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.001 766.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.002 767.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.003 768.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.004 769.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.005 770.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.006 771.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.007 772.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.008 773.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.009 774.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.010 775.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.011 776.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.012 777.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.001 778.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.002 779.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.003 780.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.004 781.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.005 782.00
P12 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.006 493.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2013.012 430.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.001 431.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.002 432.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.003 433.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.004 434.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.005 435.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.006 436.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.007 437.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.008 438.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.009 439.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.010 440.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.011 441.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2014.012 442.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2015.001 443.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2015.002 444.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2015.003 445.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2015.004 446.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2015.005 447.00
P12 4000 000000 A-000036 000 A-000036.1.01.03 2015.006 448.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2013.012 584.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.001 585.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.002 586.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.003 587.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.004 588.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.005 589.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.006 590.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.007 591.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.008 592.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.009 593.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.010 594.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.011 595.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.012 596.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.001 597.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.002 598.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.003 599.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.004 600.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.005 601.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.006 602.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2013.012 606.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.001 607.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.002 608.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.003 609.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.004 610.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.005 611.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.006 612.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.007 613.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.008 614.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.009 615.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.010 616.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.011 617.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.012 618.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.001 619.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.002 620.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.003 621.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.004 622.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.005 623.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.006 624.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2013.012 824.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.001 825.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.002 826.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.003 827.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.004 828.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.005 829.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.006 830.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.007 831.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.008 832.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.009 833.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.010 834.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.011 835.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.012 836.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.001 837.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.002 838.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.003 839.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.004 840.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.005 841.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.006 842.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2013.012 125.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.001 126.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.002 127.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.003 128.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.004 129.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.005 130.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.006 131.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.007 132.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.008 133.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.009 134.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.010 135.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.011 136.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.012 137.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2015.001 138.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2015.002 139.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2015.003 140.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2015.004 141.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2015.005 142.00
P12 4000 000000 A-000036 000 A-000036.1.01.03.04 2015.006 143.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2013.012 407.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.001 408.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.002 409.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.003 410.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.004 411.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.005 412.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.006 413.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.007 414.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.008 415.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.009 416.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.010 417.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.011 418.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2014.012 419.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2015.001 420.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2015.002 421.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2015.003 422.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2015.004 423.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2015.005 424.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.01 2015.006 425.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2013.012 606.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.001 607.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.002 608.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.003 609.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.004 610.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.005 611.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.006 612.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.007 613.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.008 614.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.009 615.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.010 616.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.011 617.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2014.012 618.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2015.001 619.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2015.002 620.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2015.003 621.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2015.004 622.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2015.005 623.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.02 2015.006 624.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2013.012 726.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.001 727.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.002 728.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.003 729.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.004 730.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.005 731.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.006 732.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.007 733.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.008 734.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.009 735.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.010 736.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.011 737.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2014.012 738.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2015.001 739.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2015.002 740.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2015.003 741.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2015.004 742.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2015.005 743.00
P12 4000 000000 A-000036 000 A-000036.1.01.05.03 2015.006 744.00
285 RECORDS HAVE BEEN WRITTEN BACK.
WRITING TIME :543.97 ms.
[INFO] GET_DIM_LIST(): I_APPL_ID="Forecasting", #dimensions=8
F_CATEGORY,F_ENTITY,F_PERSON,F_PROJECT,F_SECTION,F_WBSE,MEASURES,TIME
#dim_memberset=2
F_CATEGORY:ACTUAL,1 in total.
TIME:2013.001,2013.002,2013.003,2013.004,2013.005,...11 in total.
REC :%VALUE%
CALCULATION BEGIN:
QUERY PROCESSING DATA
QUERY TIME : 1019.73 ms. 1 RECORDS QUERIED OUT.
QUERY REFERENCE DATA
CALCULATION TIME IN TOTAL :140.35 ms.
1 RECORDS ARE GENERATED.
CALCULATION END.
ENDWHEN ACCUMULATION: 1 RECORDS ARE GENERATED.
DATA TO WRITE BACK:
F_CATEGORY F_ENTITY F_PERSON F_PROJECT F_SECTION F_WBSE TIME SIGNEDDATA
P12 4000 000000 A-000001 000 A-000001.1.01 2013.010 2000.00
1 RECORDS HAVE BEEN WRITTEN BACK.
WRITING TIME :480.96 ms.
SCRIPT RUNNING TIME IN TOTAL:5.07 s.
LOG END TIME:2014-03-14 09:36:28
Prompts
PARAM - YY=2014
DATA REGION - F_CATEGORY=P1
RESULT
PLS NOTE - The 2nd record "ACTUAL" - Project A-000036 / 2013.012 for $5000 is MISSING
LGX:
*XDIM_MEMBERSET F_CATEGORY=P12
*XDIM_MEMBERSET TIME=2014.001,2014.002,2014.003,2014.004,2014.005,2014.006,2014.007,2014.008,2014.009,2014.010,2014.011,2014.012,2015.001,2015.002,2015.003,2015.004,2015.005,2015.006,2015.007,2015.008,2015.009,2015.010,2015.011,2015.012,2016.001,2016.002,2016.003,2016.004,2016.005,2016.006,2016.007,2016.008,2016.009,2016.010,2016.011,2016.012,2017.001,2017.002,2017.003,2017.004,2017.005,2017.006,2017.007,2017.008,2017.009,2017.010,2017.011,2017.012,2018.001,2018.002,2018.003,2018.004,2018.005,2018.006,2018.007,2018.008,2018.009,2018.010,2018.011,2018.012,2019.001,2019.002,2019.003,2019.004,2019.005,2019.006,2019.007,2019.008,2019.009,2019.010,2019.011,2019.012,2020.001,2020.002,2020.003,2020.004,2020.005,2020.006,2020.007,2020.008,2020.009,2020.010,2020.011,2020.012
*WHEN F_CATEGORY
*IS *
*REC(EXPRESSION=%VALUE%,F_CATEGORY=P1)
*ENDWHEN
*XDIM_MEMBERSET F_CATEGORY=ACTUAL
*XDIM_MEMBERSET TIME=
*WHEN F_CATEGORY
*IS *
*REC(EXPRESSION=%VALUE%,F_CATEGORY=P1)
*ENDWHEN
LOG:
LOG BEGIN TIME:2014-03-14 09:40:55
FILE:\ROOT\WEBFOLDERS\F_COUNCIL \ADMINAPP\Forecasting\TEST.LGF
USER:096655
APPSET:F_COUNCIL
APPLICATION:Forecasting
[INFO] GET_DIM_LIST(): I_APPL_ID="Forecasting", #dimensions=8
F_CATEGORY,F_ENTITY,F_PERSON,F_PROJECT,F_SECTION,F_WBSE,MEASURES,TIME
#dim_memberset=2
F_CATEGORY:P12,1 in total.
TIME:2014.001,2014.002,2014.003,2014.004,2014.005,...84 in total.
REC :%VALUE%
CALCULATION BEGIN:
QUERY PROCESSING DATA
QUERY TIME : 1342.07 ms. 270 RECORDS QUERIED OUT.
QUERY REFERENCE DATA
CALCULATION TIME IN TOTAL :716.94 ms.
270 RECORDS ARE GENERATED.
CALCULATION END.
ENDWHEN ACCUMULATION: 270 RECORDS ARE GENERATED.
DATA TO WRITE BACK:
F_CATEGORY F_ENTITY F_PERSON F_PROJECT F_SECTION F_WBSE TIME SIGNEDDATA
P1 4000 000000 A-000036 000 A-000036.1.01 2014.001 104.00
P1 4000 000000 A-000036 000 A-000036.1.01 2014.002 105.00
P1 4000 000000 A-000036 000 A-000036.1.01 2014.003 106.00
P1 4000 000000 A-000036 000 A-000036.1.01 2014.004 107.00
P1 4000 000000 A-000036 000 A-000036.1.01 2014.005 108.00
P1 4000 000000 A-000036 000 A-000036.1.01 2014.006 109.00
P1 4000 000000 A-000036 000 A-000036.1.01 2014.007 110.00
P1 4000 000000 A-000036 000 A-000036.1.01 2014.008 111.00
P1 4000 000000 A-000036 000 A-000036.1.01 2014.009 112.00
P1 4000 000000 A-000036 000 A-000036.1.01 2014.010 113.00
P1 4000 000000 A-000036 000 A-000036.1.01 2014.011 114.00
P1 4000 000000 A-000036 000 A-000036.1.01 2014.012 115.00
P1 4000 000000 A-000036 000 A-000036.1.01 2015.001 116.00
P1 4000 000000 A-000036 000 A-000036.1.01 2015.002 117.00
P1 4000 000000 A-000036 000 A-000036.1.01 2015.003 118.00
P1 4000 000000 A-000036 000 A-000036.1.01 2015.004 119.00
P1 4000 000000 A-000036 000 A-000036.1.01 2015.005 120.00
P1 4000 000000 A-000036 000 A-000036.1.01 2015.006 121.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.001 236.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.002 237.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.003 238.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.004 239.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.005 240.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.006 241.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.007 242.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.008 243.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.009 244.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.010 245.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.011 246.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2014.012 247.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2015.001 248.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2015.002 249.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2015.003 250.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2015.004 251.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2015.005 252.00
P1 4000 000000 A-000036 000 A-000036.1.01.01 2015.006 253.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.001 345.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.002 346.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.003 347.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.004 348.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.005 349.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.006 350.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.007 351.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.008 352.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.009 353.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.010 354.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.011 355.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2014.012 356.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.001 357.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.002 358.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.003 359.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.004 360.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.005 361.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.01 2015.006 362.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.001 495.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.002 496.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.003 497.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.004 498.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.005 499.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.006 500.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.007 501.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.008 502.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.009 503.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.010 504.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.011 505.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2014.012 506.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.001 507.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.002 508.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.003 509.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.004 510.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.005 511.00
P1 4000 000000 A-000036 000 A-000036.1.01.01.02 2015.006 512.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.001 574.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.002 575.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.003 576.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.004 577.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.005 578.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.006 579.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.007 580.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.008 581.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.009 582.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.010 583.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.011 584.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2014.012 585.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2015.001 586.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2015.002 587.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2015.003 588.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2015.004 589.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2015.005 590.00
P1 4000 000000 A-000036 000 A-000036.1.01.02 2015.006 591.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.001 664.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.002 665.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.003 666.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.004 667.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.005 668.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.006 669.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.007 670.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.008 671.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.009 672.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.010 673.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.011 674.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2014.012 675.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.001 676.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.002 677.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.003 678.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.004 679.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.005 680.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.01 2015.006 404.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.001 766.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.002 767.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.003 768.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.004 769.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.005 770.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.006 771.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.007 772.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.008 773.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.009 774.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.010 775.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.011 776.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2014.012 777.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.001 778.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.002 779.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.003 780.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.004 781.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.005 782.00
P1 4000 000000 A-000036 000 A-000036.1.01.02.02 2015.006 493.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.001 431.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.002 432.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.003 433.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.004 434.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.005 435.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.006 436.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.007 437.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.008 438.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.009 439.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.010 440.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.011 441.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2014.012 442.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2015.001 443.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2015.002 444.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2015.003 445.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2015.004 446.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2015.005 447.00
P1 4000 000000 A-000036 000 A-000036.1.01.03 2015.006 448.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.001 585.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.002 586.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.003 587.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.004 588.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.005 589.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.006 590.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.007 591.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.008 592.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.009 593.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.010 594.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.011 595.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2014.012 596.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.001 597.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.002 598.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.003 599.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.004 600.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.005 601.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.01 2015.006 602.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.001 607.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.002 608.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.003 609.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.004 610.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.005 611.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.006 612.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.007 613.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.008 614.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.009 615.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.010 616.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.011 617.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2014.012 618.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.001 619.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.002 620.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.003 621.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.004 622.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.005 623.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.02 2015.006 624.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.001 825.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.002 826.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.003 827.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.004 828.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.005 829.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.006 830.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.007 831.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.008 832.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.009 833.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.010 834.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.011 835.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2014.012 836.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.001 837.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.002 838.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.003 839.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.004 840.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.005 841.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.03 2015.006 842.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.001 126.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.002 127.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.003 128.00
P1 4000 000000 A-000036 000 A-000036.1.01.03.04 2014.004
Similar Messages
-
how to delete forecast entries with zero current and original qty from a particular forecast set which span across multiple forecasts
Hi,
There is no way to delete those records selectively from front end.
The best possible way is to delete the records from MRP_FORECAST_DATES tables from backend.
Hope that helps!!
Regards,
Mohan Balaji
NOTE: Please mark the post as Helpful or Answered if the update has really helped you. This would also bring the thread to logical conclusion and will be helpful for the viewers. -
I want to create a Forecast report that shows the Current Month ( I have a subtitution variable set for this) and the the next 3 months out. I can a relative member function to set the next 3 months but if the Month is Dec how can I change the year to show Jan 2004 instead of 2003? Can I set it dynamically in the report or can I create a new dimension in Essbase with a formula? Any help would be great I'm fairly new to Essbase.
Unfortunately that did not post the way I typed it.Basically if you are in Excel your Row 1 column heading is your members from your Year dimension, your Row 2 column heading is your members from your Month Dimension, then your Measures would be your row headings. Sorry if I made this more confusing than it needed to be. If you want to send me an email, I will send you an Excel sheet showing what I [email protected]
-
Calculating values across multiple years
Hi,
I have a stored procedure that has 10 rows for each of the last 10 years and about 25 columns for various different values for each given year.
I need to create a report that shows all the values (columns) for only year 3, year 7, and year 10. My problem is, I have a formula that calculates the value for year 3 that requires information from year 1, and 2. The formula for year 7 requires information from year 4, 5, and 6 and so on.
I plan to use a crosstab but how can I use values from previous years into the year I am printing in a cross tab?
Can anyone provide any help?
Thanks,
Zack H.Carl,
This is a very plausible way of doing it.
However, I was thinking more along the lines of storing the values of each field in an array for each year and then call up whatever value I wanted from the array into my calculation. For instance, the stored procedure returns 10 rows x 25 columns = or 250 field values. I wanted to create an array say numbervar array_year1, array_year2 and so on.
Then, in my calculation, I can call up whatever value I wanted like array_year2[5]/array_year1[5].
Can this approach be acheived?
Any help would be appreciated.
Thanks again,
Zack -
Parameters spaning across multiple years.
Hi,
Can you help me regarding the parameters in Discoverer.
The requirement is as follows.
I have Four parameters .......
Parameter 1:Start Year
Parameter 2:Starting Month
Parameter 3:Ending Year
Parameter 4:Ending Month
For EX:
If values are as follows
Parameter 1:2006
Parameter 2:JULY
Parameter 3:2008
Parameter 4:FEB
Now the report should display the data ranging from JULY 2006 to FEB 2008.
Thanks in Advance.
Regards
SridharCreate a calculation called get_start_date as
to_date(:parameter_2||:parameter_1, 'MONYYYY')Create a second calculation called get_end_date as
last_day(to_date(:parameter_4||:parameter_3, 'MONYYYY'))Then create a condition like
report_date BETWEEN get_start_date AND get_end_date -
Sharing scripts across multiple computers
Hi,
I'm currently working on customizing Bridge (ie. custom file info panel, start-up scripts), but I would like to share the changes I make with a group of users.
So far, what I've been doing is modifying a start-up script or custom panel, and then sending it to each person, and telling them where on their system to put the file. It would be much easier to have a shared instance of the file, so I could just modify that file directly. Is this possible? (We all have access to a shared drive, but I can't figure out how to get something on that drive to be detected by Bridge)Wayne,
I'm pretty sure there is no way to redirect Bridge and File Info to look elsewhere for custom panels.
One thing you might consider doing is publishing the shared panels on a web or FTP server on your intranet or on the internet. You could then use the JavaScript web and ftp access tools to write a script that would synchronize the panels in the local folder with panels on the server.
-David Franzen
Adobe Bridge Quality Engineer
Adobe Systems, Inc. -
Spread Data Over Multiple Months & Years with Data from Multiple Years
Hello Everyone,
I have a complex calculation for spreading values over several months spanning mulitle years. Because we have a 36 month rolling Forecast, a more sophisticated calc is required as opposed to hard coding months or years.
Heres the description:
Users enter the following data,
FY11 BegBalance Number of BOD Members 10
BOD Options Vesting Months 20
BOD Options Accounting Value 10
BOD Options- Number of Shares 100
BOD Grant Month Aug
FY12 BegBalance Number of BOD Members 5
BOD Options Vesting Months 10
BOD Options Accounting Value 5
BOD Options- Number of Shares 200
BOD Grant Month Oct
FY13 BegBalance Number of BOD Members 20
BOD Options Vesting Months 8
BOD Options Accounting Value 20
BOD Options- Number of Shares 100
BOD Grant Month Feb
Based on the above;
"BOD Stock" is calculated as following/month=Number of BOD Members*BOD Options Accounting Value*BOD Options- Number of Shares/ BOD Options Vesting Months
Start month for the above is based on "BOD Grant Month". So, for instance considering data for FY11:
The total "BOD Stock" value is $10000 (originating from FY11) with start month of AUG in FY11 and the number of months to spread over is 20 months. So, essentially the "BOD Stock" per month (originating from FY11) is $500 starting from AUG FY11 to Mar FY13.
Similarly, the total "BOD Stock" value is $5000 (originating from FY12) with start month of OCT in FY12 and the number of months to spread over is 10 months. So, essentially the "BOD Stock" per month (originating from FY12) is $500 starting from OCT FY12 to JUL FY13.
The challange I am facing is because of the number of months to spread. Because I have data to spread from multiple years and each year's data spills into the following years, each year should accumulate data from prior years. For instance;
FY11 should include only FY11
FY12 should include FY11 and FY12
FY13 should include FY11, FY12 and FY13.
Could anyone suggest a smarter way to do this without writting code for each year, maybe using @MDALLOCATE function? The following shows how data should be spread and accumulated.
BegBalance Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Period
FY11 Number of BOD Members 10 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Options Vesting Months 20 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Options Accounting Value 10 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Options- Number of Shares 100 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Grant Month Aug #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Stock 10000 #mi #mi #mi #mi #mi #mi #mi 500 500 500 500 500 #mi
FY12 Number of BOD Members 5 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Options Vesting Months 10 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Options Accounting Value 5 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Options- Number of Shares 200 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Grant Month Oct #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Stock 5000 500 500 500 500 500 500 500 500 500 1000 1000 1000 #mi
FY13 Number of BOD Members 20 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Options Vesting Months 8 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Options Accounting Value 20 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Options- Number of Shares 100 #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Grant Month Feb #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi #mi
BOD Stock 40000 1000 6000 6000 5500 5500 5500 5500 5000 5000 #mi #mi #mi #mi
Appreciate your inputs!
Edited by: user10678366 on Oct 12, 2010 3:21 PMWhy not use substitution variables for Years? you could have something like &Year1, &Year2, &Year3
Cheers -
Year Over Year Comparison for Multiple Years
I have a business request where the client is asking for a year over year percentage comparison for multiple years
So for example
Applications
2015 5
2014 10
2013 22
So in year 2015 we can see that applications is currently down (5-50/10 - [New-Old/Old] by -50% compared to year prior
In year 2014 we are down -55%
Ultimately I wanted to display the following
Applications
2015 -50%
2014 -55%
2013
I have an idea of how to do this for a single year, where a presentation variable is fed in then I can just do this year minus previous year.
I was wondering, how can I do this calculation or presentation in OBIEE? Can this be done within answers? Or does something need to be done in the RPD?As long as your model is correctly done with a time hierarchy you can just use the time series function AGO to get the value of previous year.
So in the formula you can calculating your delta in % comparing the current year amount and the previous one.
You can do it in the analysis directly, but if you will often need to access "previous year measures" would be a good idea to add it in the RPD so you don't need to write the formula every single time. -
Script to remotely find IE version across multiple PC's
Hoping someone can help...I'm very new to Powershell and it seems very powerful, but I'm having trouble to execute commands across multiple pc's. I can use powershell to find the IE version on my local machine, but I'd like to be able to pull from
a TXT file (list of PC's) the IE Version and export it to CSV format
If anyone has any idea, I'm up for testing.
Thank YouPost you script and the error messages.
¯\_(ツ)_/¯ -
How to execute sql scripts from Powershell across multiple databases
Re: How to execute sql scripts from Powershell across multiple databases
I have an tsql script that I want to run across a list of databases. How is the best way to do this in Powershell? Thanks.My example below, using just the SMO and not breaking up the batches, the ExecuteWithResults give the following error when the .sql file contains a GO. My script files are as simple as a DECLARE and then a GO.
WARNING: SQL Script Failed
The object of type "Microsoft.PowerShell.Commands.Internal.Format.FormatStartData" is not valid or not in the correct sequence. This is likely caused by a user-specified "format-list" comm
and which is conflicting with the default formatting.
+ CategoryInfo : InvalidData: (:) [out-lineoutput], InvalidOperationException
+ FullyQualifiedErrorId : ConsoleLineOutputOutOfSequencePacket,Microsoft.PowerShell.Commands.OutLineOutputCommand
Also, when executing from the ISE, is there a way to force the ISE to release the files. I am having to close the ISE and reopen my script every time I want to make a testing change to the .sql file.
[reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo")
$scriptspath = "C:\temp\psExecuteSQLScripts\scripts"
$SQLServer = "fidevc10"
$SQLDB = "Bank03"
# Create SMO Server Object
$Server = New-Object ('Microsoft.SQLServer.Management.Smo.Server') $SQLServer
# Get SMO DB Object
$db = $Server.Databases[$SQLDB]
# Load All SQL Scripts in Directory
$scripts = Get-ChildItem -Path (Join-Path $scriptspath "*") -Include "*.sql" -Recurse
# Loop through each script and execute
foreach ($SQLScript in $scripts)
$fullpath = $SQLScript.FullName
# Read the Script File into Powershell Memory
$reader = New-Object System.IO.StreamReader($fullpath)
$script = $reader.ReadToEnd()
# Execute SQL
Write-Host "Executing $SQLScript on $SQLDB...."
try
$ds = $db.ExecuteWithResults($script)
Foreach ($t in $ds.Tables)
Foreach ($r in $t.Rows)
Foreach ($c in $t.Columns)
Write-Host $c.ColumnName "=" $r.Item($c)
Write-Host "Complete"
catch [Exception]
Write-Warning "SQL Script Failed"
echo $_.Exception|format-list -force
Write-Host " " -BackgroundColor DarkCyan -
Multiple roll over/out + attachMC = wrong coordinates of attached mc
First the code:
att = function (prev,nex,coox,alf) {
attachMovie (nex, nex, _root.getNextHighestDepth());
nex=eval(nex);
nex._x = coox;
nex._y = 160;
prev._alpha = alf;
att(LetP,"LetP",80,100);
LetP.onRollOver=function () {
att(LetP, "LetPi", 80, 0);
LetP.onRollOut=function () {
att (0,"LetPj",80,0);
removeMovieClip ("LetPi");
setTimeout(remPj, 10000);
remPj=function() {
removeMovieClip ("LetPj");
LetP._alpha = 100;
When I set mouse over first MC ("LetP") it starts second MC ("LetPi"). When I remove mouse from this area, LetPi is replaced with LetPj, which disappear after a while revealing LetP.
Problem starts when I do this:
mouse over the mc, then mouse out, then over again, and then out
- result of this operation is that the LetPj appears where it should (that is x=80 and y=160), but it also appears in upper - left corner of the screen (x=0 and y=about 10,sometimes less).
And untill the additional mc (the one at x=0) disappear the main mcs (those at x=80) act chaotically on roll over/out events.
Is there a reason why it acts like this?No
The example I geve was just for one letter, it was letter "P". That's why every mc in code I've written above has the same coordinates (x,y). I got other letters, every one of them works with the same mechanism as "P". But other letters have different coordinates. I want every letter to animate independently.
Every letter has 3 versions. For "P" it is "LetP", "LetPi" and "LetPj".
For example letter "R" has instances of "LetR", "LetRi" and "LetRj". Letter "O" has instances of "LetO", "LetOi" and "LetOj". And so on....with more letters.
I gave an example just for letter "P" so I'd know what to do with other letters
My first post in this thread was a function, which was supposed to work for all the letters. And it might've been not very understandable function (I have sometimes trouble with figuring it out ) But it works as I intended to. Code in my second post is easier to understand, but it has the same effect as code in the first post.
Both versions of this code (my fist post, and my second post) works simmilar. But both of them have simmilar 'side effects' - instance of "LetPj" appears at the upper left corner of stege. And this side effect was not in my intentions
I was interested in the reason why this instance of "LetPj" (or "LetRj" or "LetOj"...and so on) appears where it shouldn't be.
Is that the explanation you were hoping for? -
Sharing an iTunes Library across multiple user account and a network.
Sharing an iTunes Music Library across multiple user accounts.
Hello Everybody!
Firstly, this was designed to be run in Mac OS X 10.4 Tiger. It will not work with earlier versions of Mac OS X! Sorry.
Here's a handy tip for keeping your hard drive neat and tidy, it also saves space, what in effect will be done is an iTunes music library will be shared amongst multiple users on the same machine. There are advantages and disadvantages to using this method.
• Firstly I think it might be worthwhile to state the advantages and disadvantages to using this approach.
The advantages include:
- Space will be saved, as no duplicate files will occur.
- The administrator will be able to have complete control over the content of the iTunes library, this may be useful for restricting the content of the Library; particularly for example if computer is being used at and education institution, business or any other sort of institution where things such as explicit content would be less favorable.
- The machine will not be slowed by the fact that every user has lots of files.
The disadvantages to this system include.
- The fact that the account storing the music will have to be logged in, and iTunes will have to be active in that account.
- If the account housing the music is not active then nobody can use the iTunes library.
- There is a certain degree of risk present when an administrator account must be continually active.
- Fast User Switching must be enabled.
Overview:
A central account controls all music on the machine/network, this is achieved by storing iTunes files in a public location as opposed to in the user's directory. In effect the system will give all users across the machine/network access to the same music/files without the possibility of files 'doubling up' because two different users like the same types of music. This approach saves valuable disk space in this regard and may therefore prove to be useful in some situations.
This is a hearty process to undertake, so only follow this tutorial if you're willing to go all the way to the end of it.
Process:
Step 1:
Firstly, we need to organize the host library, I tidied mine up, removing excess playlists, random files, things like that. this will make thing a bit easier in the later stages of this process.
Once the library is tidied up, move the entire "iTunes" folder from your Home directory to the "//localhost" directory (The Macintosh HD) and ensure that files are on the same level as the "Applications", "Users", "Library" and "System" directories; this will ensure that the files in the library are available to all users on the machine (this also works for networks)
Optionally you can set the ownership of the folder to the 'administrator' account (the user who will be hosting the library.), you may also like to set the permissions of 'you can' to "Read & Write" (assuming that you are doing this through the user who will host the library); secondly you should set the "Owner" to the administrator who will be hosting the library and set their "access" to "Read & Write" (this will ensure that the administrator has full access to the folder). The final part of this step involves setting access for the "Others" tab to "Read Only" this will ensure that the other users can view but not modify the contents on the folder.
Overview:
So far we have done the following steps:
1. Organized the host library.
2. Placed the iTunes directory into a 'public' directory so that other users may use it. (this step is essential if you plan on sharing the library across multiple accounts on the same machine. NOTE: this step is only necessary if you are wanting to share you library across multiple accounts on the same machine, if you simply want to share the music across a network, use the iTunes sharing facility.
3. set ownership and permissions for the iTunes music folder.
Step 2:
Currently the administrator is the only user who can use this library, however we will address this soon. In this step we will enable iTunes music sharing in the administrator's account, this will enable other users to access the files in the library.
If you are not logged in as the administrator, do so; secondly, open iTunes and select "Preferences" from the "iTunes" menu, now click the "Sharing" tab, if "share my library on my local network" is not checked, the radio buttons below this will now become active, you may choose to share the entire libraries contents, or share only selected content.
Sharing only selected content may be useful if their is explicit content in the library and minors use the network or machine that the library is connected to.
If you have selected "share entire library" go to Step 3, if you have selected share "share selected playlists" read on.
After clicking "share selected playlists" you must then select the playlists that you intend to share across your accounts and network. Once you have finished selecting the playlists, click "OK" to save the settings.
Overview:
In this step we:
1. Enabled iTunes sharing in the administrator's account, now, users on the local network may access the iTunes library, however, users on the same machine may not.
Step 3:
Now we will enable users on the same machine to access the library on the machine. This is achieved by logging in as each user, opening iTunes, opening iTunes preferences, and clicking "look for shared music". now all users on the machine may also access the library that the administrator controls.
This in effect will mean that the user will not need to use their user library, it will be provided to them via a pseudo network connection.
As a secondary measure, I have chosen to write a generic login script that will move any content from the user's "Music/iTunes/iTunes Music" directory to the trash and then empties the user's trash.
This is done through the use of an Automator Application: this application does the following actions.
1. Uses the "Finder" action "Get Specified Finder Items"
1a. The user's "~/Music/iTunes/iTunes Music" folder
2. Uses the "Finder" action "Get Folder Contents"
3. Uses the "Finder" action "Move to Trash"
4. Uses the "Automator" action "Run AppleScript"
4a. with the following:
on run {input, parameters}
tell application "Finder"
empty trash
end tell
return input
end run
IMPORTANT: Once the script is adapted to the user account it must be set as a login item. in order to keep the script out of the way i have placed it in the user's "Library" directory, in "Application Support" under "iTunes".
Overview:
Here we:
1. Enabled iTunes sharing in the user accounts on the host machine, in effect allowing all users of the machine to view a single iTunes library.
2. (Optional) I have created a login application that will remove any content that has been added to user iTunes libraries, this in effect stops other users of the machine from adding music and files to iTunes.
Step 4:
If it is not already enabled, open system preferences and enable Fast User Switching in Accounts Options.
Summary:
We have shared a single iTunes library across multiple user account, while still allowing for network sharing. This method is designed to save space on machines, particularly those with smaller hard drives.
I hope that this hint proves to be helpful and I hope everybody will give me feedback on my process.
regards,
Pete.
iBook G4; 60GB Hard Drive, 512MB RAM, Airport Extreme Mac OS X (10.4.6) iWork & iLife '06, Adobe CS2, Final Cut Pro. Anything and Everything!!!how to share music between different accounts on a single computer
-
Nokia E71 Calendar Memos across multiple days
Hello,
I recently got a German Nokia E71
(E71-1 Software Version: 100.07.76 08-06-2008).
I noticed a strange behavior of the calendar:
When I create a memo that goes across multiple days (lets say 10 days or 14 days) In Month view the memo is shown correctly for the set time. Also when synchronizing with MS Outlook the memo is shown correctly on the PC.
But when you open the Memo directly (open day view, select the memo and press the center of the nav-key) then the memo is displayed to last one day longer than originally specified.
For example I created a memo that should end on the 11th of September (actually it starts in August so maybe spanning the Month barrier may also cause the problem) but it is shown to end on September 12th when I open it. Although it is shown correctly in Month view (shown on 11-Sept, not shown on 12-sept).
Maybe you have similar experiences?
Or an explanation for that behavior?
Thanks and regards,
SebastianI think I'm experiencing the same thing, Sebastian.
Phone: E71 bough from 3 in the UK ~20months ago.
Firmware: 100.07.76 08-06-2008 RM-346 E71-1 (241.02)
Here's how it happens:
Step 1) I create a memo on the calendar with the phone.
Step 2) I do an Ovi sync over the air (i.e. there is no use of the PC Suite or Microsoft Outlook going on).
Step 3) Some (but not all) of my single day memos are spread over two (2) days.
How it should look when correct: http://tinyurl.com/ovi-cal-memo-right
How it actually looks when wrong: http://tinyurl.com/ovi-cal-memo-wrong
As you can see in the 'wrong' example, instead of memos showing up as lasting for 1 day duration it's apparently "23 hours, 59 minutes" in duration, and ends on 18/07/2011. And yet it's spread over the 18th and 19th on the month view. The correct date (as entered and displayed on my phone) is actually the 19th! The same goes for all those other 'wrong 2-day memos': they should all only be shown on the second of the two day bar that's visible in month view.
At the moment, for some unknown reason, the problem seems confined to April-October of this year (and subsequent and prior years) and dates are stretched back by a day so they appear on the web version of the Ovi calendar as lasting for two (2) days instead of one (1). But I think that the problem has been more widespread and across-the-board in the past, and it may have put dates forward by an aditional day (although I can't be sure on that.
Thankfully, all these memos remain as correct on the phone and seem to be unaffected by the sync.
When it first happened I made an attempt to correct the Ovi Web Calendar memo sync problem before (thinking it was a once only bug) by going through all the Ovi calendar entries on the web interface and tidying things up that way. But I'm not prepared to go through all that hassle again.
It's a real niggle, to say the least.
What can be done?
Thanks for any help.
Attachments:
ovi-cal-memo-right.jpg 155 KB
ovi-cal-memo-wrong.jpg 159 KB -
Embedding same images across multiple components, best practices?
Hi Guys,
Once again a great forum.
I have a fairly large dashboard application, built from many
components, from an obvious maintenance point of view this is
preferred.
To keep the look and feel the same across each component I
reuse a lot of the icons, this icons have 3 states, disabled,
normal and hot(rollover)
The mouse roll over and roll out are the same for each set of
icons. At the moment I have each component embed each icon and
repeat the functions.
This is not the optimum way to do this so I'm looking on best
practices. Should I build a separate action script package with all
the embedded images and roll over/out functions. Then import that
in to each component. But then I will embedded ALL the images in
each component. Should I embed all the images in the main container
app, then when flex sees the same image in a compoent will it not
embedded again or will it embed the images again..
In the example below 4 of the components have the same
refresh icon and roll/over states. So this code is repeated (bad
practice) in all 4. Moving to separate action-script package will
make maintenance easier, but as stated above will just one copy get
embedded for the entire app, or will 4 copies get embedded ?
[Embed(source="images/refresh_24.png")]
[Bindable]
private var refreshIcon:Class;
[Embed(source="images/refresh_24_hot.png")]
[Bindable]
private var refreshIconHot:Class;
[Embed(source="images/refresh_24_dis.png")]
[Bindable]
private var refreshIconDis:Class;
private function rollOverRefresh(event:Event):void {
if (event.target.source != refreshIconDis )
{event.target.source = refreshIconHot;}
private function rollOutRefresh(event:Event):void {
If (event.target.source != refreshIconDis )
{event.target.source = refreshIcon;}
}Flex is able to collate those Embeds so they are only
included once IIRC.
While it may seem like bad practice to include it in each
component, it really isn't, from a code reusability standpoint. But
you could probably continue on that path and create a custom
component <mycontrols:RefreshButton> that has the the embeds
in one place for you.
You could probably also do something similar with style very
easily:
.MyButton {
overSkin="@Embed(source='../assets/orb_over_skin.gif')"
upSkin="@Embed(source='../assets/orb_up_skin.gif')"
downSkin="@Embed(source='../assets/orb_down_skin.gif')"/>
Then apply that style to your button.
You could also put the button into a single SWF file in Flash
and include it that way to reduce the number of embeds. I never
include PNG, JPG, GIF, etc files directly, always SWF as you get
better compression that way IMO. Plus I just find it gives me
greater flexibility...if I want to animate my skins in the future
(button that gleams for instance), I already have SWF's in my code
so no need to change anything out but the SWF. -
Fixed Image roll over question....
I am putting the finishing touches on my photography business site (www.colbybrownphotography.com) and came across an interesting problem. Instead of using iWEB's photo gallery pages (which I can't stand) I decided to set up my page as an art portfolio with an "art gallery" feel to it. The photos in my "home" section are set up as links so when I roll over them they list where they are redirecting you, but in my actually gallery they are fixed images. Is there any ability to add roll over text to those photos where I could possible talk about the particular photo that the mouse scrolls over? I knew I would be limited when I decided to use iWeb to put together my site but I have been surprised lately with at least a few of the ideas I figured would be out of its technical reach. Thanks in advance.
ColbyThere's also this +Tooltip DHTML Library+. At the following link, mouseover the image there...
http://www.walterzorn.com/tooltip/tooltip_e.htm
...I don't know how easy these scripts are to incorporate into an iWeb site using +HTML Snippets+, but if you get them working, please post back here explaining how you did it.
The following thumbnail viewer is beyond what you were asking for, but anyway, click on the examples here and watch the captions drop down...
http://vikjavev.no/highslide/
Maybe you are looking for
-
Hi My database is running on solaris 10. database verrison is 10.2.0.3.0 when connecting ot db after databases get started. it throws error ORA-00205: error in identifying control file, check alert log for more info and when I checked in alert log fi
-
Idoc to soap sync without bpm. is it possible? Helping me..
Hi Experts, i have a small clarification Idoc to soap sync interface in sap pi 7.0. i created IDoc to Soap sync using BPM but some times the signals are stuck due to load issue in swpr, while reprocess those signals all going successfully to the rece
-
Ever since we got CS6 here at work, we've had nothing but issues. This is not an upgrade, it is a clean install on a brand new iMac 10.8.5. Today starts a new set of issues. Indesign crashes about 2 or 3 times just for the fun of it, then this aftern
-
HT1414 How do u update ipad2 iOS?
I think i have 4.2 ios although its listed in settings as a version. No other reference for operating system that i can find. How do u update the iOS in ipad2?
-
HT4993 Cannot connect to home wifi
I have the iphone 4S and I'm really getting tired of not being able to connect to my home wifi. My husband has the Samsung Galaxy S3 and has no problems whatsoever. I bought this phone for that specific reason amongst others but this is getting ridiu