As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I was following the instruction from WF docs and built procedure calculating the FORECAST using MOVING AVEREGE method. The code is below:
DEFINE FILE CENTORD
PERIOD/I2 = MONTH;
END
TABLE FILE CENTORD
SUM
CENTORD.STOSEG.REGION
CENTORD.PINFO.QUANTITY
CENTORD.INVSEG.LINE_COGS
BY PERIOD
WHERE CENTORD.STOSEG.REGION EQ 'WEST';
ON PERIOD
RECAP MOVING_AVG/D12.2 = FORECAST(LINE_COGS, 1, 3, 'MOVAVE', 3);
ON TABLE SET PAGE-NUM NOLEAD
ON TABLE NOTOTAL
ON TABLE PCHOLD FORMAT HTML
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLE *
INCLUDE = endeflt,
$
ENDSTYLE
END
-EXIT
The result of first 2 occurrences I've got is different compare to result from WF docs. Outputfrom procedure:
MOVING_AVG: 1. 3829915.21 2. 6955250.36
In WF docs: 1. 4,775,124.00 2. 8,830,683.00
The rest of values are the same . Please help me to understand the issue.
Thanks.This message has been edited. Last edited by: Y&Y,
I found the way to get correct values after applying FORECAST function.... But I do not see the explanation for that: Removing the style from the code will bring correct generated Moving Averages. If anyone can point me to get the explanation for that- it's very appreciated.
To be more specific it appears to be all of the "border-*" syntax that is the cause but I can't explain why!! as it should have not have any impact upon the report at all?
Both in App studio and Dev Studio.
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
I've tested all methods in a FORECAST, and all of them behaved same way: generated wrong numbers when style is in the code and correct - without style.