A REPORT

ON
JDA DEMAND TESTING ON ORACLE AND SQL SERVER
BY

V Sai Vivekanand Reddy 2016AAPS0170H

AT
JDA SOFTWARE SOLUTIONS, HYDERABAD
A Practice School-2 Station of
BIRLA INSTITUTE OF TECHNOLOGY & SCIENCE, PILANI
(DECEMBER, 2019)
 A REPORT
ON
JDA DEMAND TESTING ON ORACLE AND SQL SERVER

Name of the
Student ID No DISCIPLINE
V Sai Vivekanand Reddy 2016AAPS0170H B.E. Elec. & Comm. Eng

Prepared in partial fulfilment of the

Practice School-2

AT
JDA SOFTWARE SOLUTIONS, HYDERABAD

A Practice School-2 Station of

BIRLA INSTITUTE OF TECHNOLOGY &
SCIENCE, PILANI
(DECEMBER 2019)

BIRLA INSTITUTE OF TECHNOLOGY & SCIENCE,

PILANI(RAJASTHAN)
 Practice School Division

Station: JDA SOFTWARE SOLUTIONS Centre: HYD

Duration: From 13-07-19 To: 13-12-19

Date of Submission: 12-12-19

Title of the Project: JDA Demand 2019.1 Testing on Oracle and SQL server

ID No: Name(s) of the student: Discipline:

2016AAPS0170H V. Sai Vivekanand Reddy Electronics and Communication

Name(s) of the experts: Shanthi Mendu(Reporting Manager) , Venkat Bhompelli

and Sushma Panthadi

Name of PS Faculty: Channupati R. Prasanna

Project Area(s): Testing on JDA Demand Application 2019.1

Abstract: This report talks about the testing work done on JDA Demand
application on both Oracle and SQL servers on Different modules in the
application 2019.1 latest version and the things I have learnt about on working on
those modules

3
 ACKNOWLEDGEMENT

Our heartfelt gratitude to the PS Division at BITS PILANI for keeping PS-2
program as part of our curriculum and giving us this opportunity to experience the
professional side of the career that we are going to pursue.
Thanks to our mentor and Project leads, Shanthi Mendu, Venkat B. , Sushma
Panthadi, Venkatesh J. and for sparing their valuable time in guiding us through
the technical aspects and clearing our doubts at every stage of our technical
project.
We would like to express our special thanks of gratitude to Chennupati R.
Prasanna our PS-1 instructor who guided and supported us by giving necessary
feedback and pointers for our evaluation components and made sure we faced no
problems.

4
JDA SOFTWARE SOLUTIONS INTRODUCTION
JDA Software Group, Inc. is an American software and consultancy company (owned
by New Mountain Capital), providing supply chain management, manufacturing planning, retail
planning, store operations and collaborative category management solutions. Here, we focus on
Supply chain management as it’s our work.

Supply chain management in JDA is categorized as:

Category Management
One plan does not fit all, but how does a retailer scale operations to produce optimal
assortment and space plans for every selling location? The JDA Category Management SaaS
solutions help retailers and their collaborating vendors achieve scale and customer-centricity to
progress and achieve category sales goals. Combining sales history, market data, consumer
insights, and automation, retailers and manufacturers deliver effective plans that maximize
revenue and margin while creating satisfying shopping experiences.

Supply Chain Planning

Tightly coordinating global resources, materials, and assets in real-time to optimize the
delivery of goods and services to your customers is the ultimate balancing act. JDA’s Supply
Chain Planning can help you profitably address this supply chain complexity with our industry-
leading capabilities for demand and fulfillment, inventory optimization, network optimization,
order promising, factory planning and sequencing, and sales and operations planning.

Supply Chain Execution

With the need for innovation constantly accelerating, manufacturers, retailers and third-
party logistics companies must leverage the latest technologies such as the Internet of Things
(IoT), artificial intelligence (AI), machine learning (ML) and robotics for faster, more informed
cross-enterprise decision-making. This requires hyper-connected solutions that integrate
warehousing, labor and transportation into a seamless information and execution platform.
JDA’s SaaS-based Supply Chain Execution solutions provide the foundation to this platform -
reducing inventory levels and costs, improving customer service, enhancing decision-making and
providing more agile, profitable and responsive operations. With JDA, solving your inventory
planning, replenishment, transportation, warehouse operation and order fulfillment challenges
has never been easier.

Retail Planning
In today’s environment, retailers are faced with growing competition across channels.
Merchandisers perform large amounts of manual, repetitive tasks without an understanding of
history at a granular level which can identify missed business opportunities. A critical
component is being able to understand the internal and external factors that influence customer

5
demand. JDA’s Retail Planning suite of SaaS solutions aligns merchandise financial planning,
assortment, allocation and pricing with AI/ML forecasts so that retailers can meet their financial
goals and have better insight into their business on a store by store basis increasing profitability.

Store Operations
Changing customer preferences, new competitors, and growing sustainability needs are changing
all aspects of store execution. In particular, this has a direct impact on restaurants and convenience
stores. Store managers have to deal with the realities of increased demand for fresh and prepared food
items while also making sure they are reducing waste. JDA Store Operations is designed to intelligently
forecast customer demand throughout the day to help restaurants and C-stores maximize availability,
optimize their inventory, and support sustainability efforts by reducing waste. It is an easy to use, mobile
friendly, SaaS platform that can be rapidly adopted to address these challenges.

Workforce Management
Today’s workforce marketplace is more competitive than ever. Historically low
unemployment rates and workforce shortages mean organizations must optimize their workforce
to increase productivity and must focus on retaining and recruiting employees. To address these
challenges, organizations must have accurate forecasting and scheduling so they can align labor
when and where it is needed. JDA’s Workforce Management SaaS-based solutions provide
employees flexible scheduling options that keep employees engaged and labor management that
maximizes productivity and utilization while decreasing labor expenses.

Merchandise Operations
The role of retailer changes from day to day and is faster paced than ever. From
expanding into new markets to increasing e-commerce, opening stores, and keeping customers
happy, they must act at lightning speed to stay competitive. To maintain an edge, retailers must
focus on upgrading their technology and data to stay responsive and agile. Our Merchandise
Operations solutions provide the foundation for accurate, synchronized data with real-time
inventory updates and secure transactions. With visibility and flexibility, our solutions support
growth and control inventory costs throughout the most complex retail environments.

Service Industry Solutions

When you’re dealing with perishable inventory — like seats on trains, hotel rooms, hold
capacity or advertising space — you need to get the price exactly right, every time. Your offers
must be low enough to attract customers, but high enough to drive profitability. JDA's Pricing
and Revenue Management's advanced forecasting and optimization algorithms, plus data
analysis, help companies in the hospitality, travel, transportation and media industries make the
sale profitable. You’ll understand exactly what customers are looking for and deliver it reliably,
increasing your market share and brand strength.

6
 Understanding SCM: Supply chain management is the management of the flow
of goods and services and includes all processes that transform raw materials into final
products. It involves the active streamlining of a business's supply-side activities to
maximize customer value and gain a competitive advantage in the marketplace.

SCM represents an effort by suppliers to develop and implement supply chains that
are as efficient and economical as possible. Supply chains cover everything from
production to product development to the information systems needed to direct these
undertakings.

Supply chain management produces benefits such as new efficiencies, higher

profits, lower costs and increased collaboration. SCM enables companies to better manage
demand, carry the right amount of inventory, deal with disruptions, keep costs to a
minimum and meet customer demand in the most effective way possible. These SCM
benefits are achieved through choosing effective strategies and appropriate software to
manage the growing complexity of today's supply chains.

From here we see the modules worked upon:

Demand Workbench
The Demand Workbench is the primary interface for reviewing and modifying forecasts. It allows you to
review historical sales and future forecasts for individual DFUs. Various forecast types are displayed, as
well as events, causal factors, and overrides. It includes a graph and a grid to tune the forecast. The
various panels such as Model Statistics, DFU Attributes, and DFU Exception are used to review the
forecast. The graph and panels are collapsible and expandable.

Demand Workbench page: Single model/edit (use interactive

graph)
Use this page to review and fine-tune the forecasts. The page includes a graph, a grid, and panels to tune
the forecast. The graph and panels are collapsible and expandable. The Show Graph option above the grid
displays the graph and the Hide icon available at the top right corner of the graph hides it. Panels are
divided into left and right panes. You can configure the display of panels and their width and height using
the setting in the Demand Workbench Properties page: Page Setup tab. You can set maximum three
panels for the left pane and maximum four panels for the top pane. By default, the Hierarchy Panel is
always displayed in the left pane. When the panels are in collasible mode, the respective icons for the
configured panels are displayed in panes. When the panes are in collasible mode and you select the icon,
that particular panel is displayed as a floating window.

7
The tabs are displayed in the grid according to the setting in the Demand Workbench Properties page:
Page Setup tab and the model being used.
The GoTo dialog box displays all the DFUs which belong to the selected level in the hierarchy.
The default search for a particular instance of Demand Workbench can be configured in the Demand
Workbench Properties page: General tab.
The Workbench can be presented in an edit or view mode, single or multi-model mode, and interactive or
non-interactive graph mode. For information on these various modes, see Other views. Additionally, you
can specify whether you want to work with published (Fcst table) or draft (FcstDraft table) data.

Demand Workbench page: Multi-model

Use the Demand Workbench Multi-model view to review and evaluate the forecasts. The page includes a
graph, a grid, and the hierarchy panel to review the forecast. The graph and panel are collapsible and
expandable. The Show Graph option above the grid displays the graph and the Hide icon available at the
top right corner of the graph hides it. The hierarchy panel is always displayed in the left pane by default.
When this panel is in collapsible mode, the hierarchy icon is displayed in the pane. When the pane is in
collapsible mode and you select the icon, the panel is displayed as a floating window.
Only the History and Forecast tab is available in the multi-model mode.
The GoTo dialog box displays all the DFUs which belong to the selected level in the hierarchy.
The default search for a particular instance of Demand Workbench can be configured in the Demand
Workbench Properties page: General tab.
In Demand Workbench Multi-model view, the following measures are displayed in different colors on the
graph:

● Total forecast
● Base forecast
● Override
● Fitted history

The naming convention in the graph legend is as follows:

● After demand post date: <HistStream>_<Model> - <Forecast Type>

● Before demand post date: <HistStream> - <Forecast Type>

Fitted history is displayed as: <HistStream>_<Model> - Fitted History

The Workbench can be presented in an edit or view mode, single or multi-model mode, and interactive or
non-interactive graph mode. For information on these various modes, see Other views. In addition, you
can specify whether you want to work with published (Fcst table) or draft (FcstDraft table) data.

8
DFU Information dialog box
This dialog box contains the information that is displayed in the Demand Workbench grid. You can move
this dialog box to view the grid information while the graph is displayed.
You can display this dialog box in two ways. If you click on the interactive graph, this dialog box
displays the information for the date you clicked. If you select the DFU Information from the Demand
Workbench Action menu, you can select a date on this dialog box for the information you want to view.
You can configure the fields to be displayed in this dialog box using the setting in the Demand
Workbench Properties page: Data tab.

DFU Exceptions dialog box

Use this page to view exception messages encountered while running one of the Demand processes from
the DFUException table.

Demand Workbench Properties page: General tab

Use this page to indicate whether the data for DFU Model can be edited and to define the data displayed
there.

Demand Workbench Properties page: Page Setup

tab
Use this page to define the tabs and panels displayed in the Demand Workbench.

Demand Workbench Properties page: Data tab

Use this tab to select the data that is displayed in the History and Forecast Grid, Graph, DFU Information
dialog box, or Year Over Year Grid. The display options, which are applicable for the graph, have Series
Properties option to set.

9
Demand Workbench: History and Forecast tab
In the Demand Workbench edit mode, use the History and Forecast tab to review history and forecast
data and to apply forecast locks and overrides to individual DFUs. Overrides can be applied to both
history and forecast data. Locks can be applied to forecast data. Locked forecasts are fixed forecast
quantities that override all other forecast types. This tab can also be used to review existing DFU
overrides and locks.
To apply an override with a different calendar, use the Override Manager page.

Demand Workbench: Mask History tab

In the Demand Workbench edit mode, use the Mask History tab to select specific time periods to mask
and to save masks to be reused later. The Mask History tab contains a row for each time period within
the data range selected in the Demand Workbench. A DFU can have only one attached mask and must use
the Fourier, MLR, or AVS-Graves algorithm.

Add Locks and Overrides dialog box

Use this dialog box to apply forecast locks or overrides over a specific range of time periods.

Delete Locks and Overrides dialog box

Use this dialog box to remove locks or overrides from multiple time periods.

Lock Forecast dialog box

Use this dialog box to confirm the data entered through the interactive graph for a forecast lock.

Demand Workbench: Target tab

In the Demand Workbench edit mode, use the Target tab to attach target profiles to this DFU.

10
Demand Workbench: Lifecycles/External Factors tab
(Lewandowski)
Use this tab to attach a lifecycle or an external factor to a single DFU.

Demand Workbench: Mean Values tab

Use this tab to create, delete, edit, and copy mean value modifications for Lewandowski, AVS-Graves,
and Moving Average models.

Demand Workbench: Data Driven Events tab

Use the Data Driven Events tab to create, edit, copy, link, and delete data-driven events for
Lewandowski models.

Copy Data Driven Events dialog box

Use this dialog box to copy a DDE to the same DFU or to another DFU.

Link Data Driven Events dialog box

Use this dialog box to link one DDE to another. All linked DDEs become children of this DDE. If you
delete the parent DDE, all linked instances of this DDE are also deleted.

Multiple Data Driven Events dialog box

If you select to edit or copy a data driven event using the interactive graph and there are multiple events
applied to the same time period, use this dialog box to select the DDE you want to use.

11
Demand Workbench: Seasonality tab
Use this tab to enter or modify starting values that are seasonal impact indicators for the DFU. DFUs must
use the AVS-Graves, Holt-Winters, Lewandowski, Moving Average, Profile Based Forecasting, or the
Short Lifecycle algorithm.

Demand Workbench: Year over year tab

This tab allows you to view, compare, and analyze several years of data in single-model mode.

The total number of columns displayed on the Year over Year tab is always equal to the periodicity of
the calendar even if the actual number of periods in a year differ from the periodicity. In this case, the
extra periods are rolled to the next bucket and the short periods receive the quantity from the following
periods.

Adjusting the Statistical forecast

During the forecasting cycle, you create a statistical model reflecting normal product demand based on
historical data. However, this base forecast is affected by planned marketing strategies, competitive
events, or occasional one-time occurrences. To more accurately predict future demand, you must add this
judgment information to the statistical forecast to create a net forecast.
The feature you will use to add this information depends on the type of event creating the demand change:

● Override the statistical forecast: Add overrides to the calculated forecast to account for
occurrences that do not reflect the true demand patterns.
● Lock the statistical forecast: Lock the statistical forecast if you do not want the forecast values to
change during specific periods of time.
● Add causal factors to MLR models: Add causal factors to MLR models to account for events or
activities that can affect the demand patterns.
● Work with targets: Apply a target to a forecast to indicate a specific amount of volume you want
to sell over a specific period of time. Targets are valuable tools to use when you want to create a
forecast for a fixed quantity product.
● Add market activities using Market Manager: Using JDA Market Manager, add marketing events,
such as sales and promotions, to the forecasts.
● Use data driven events with Lewandowski models: Add data driven events to Lewandowski
models if you want the system to automatically calculate the impact an event had on the forecast.
● Assign external factors to Lewandowski models: Assign external factors to Lewandowski DFUs
to account for events or activities that can affect the demand pattern.

Overrides, locked forecast impacts, target impacts, data driven events, and marketing events are stored as
a different forecast type in the Fcst or FcstDraft table. For more information, see Forecast types.

12
Another way to adjust the forecast is by aggregating and reconciling forecast data. This functionality is
similar to the way you can adjust history by allocating demand to specific DFU Models. For more
information, see Introduce and Discontinue products.

Adjusting the forecast is the fifth step in the Demand planning process.

Figure: Demand Planning Process - Adjust the Statistical Forecast

Override the statistical forecast

You can apply overrides to the forecast to account for one-time events that are increased or decreased the
forecast in a manner that you do not expect to occur regularly. You can apply overrides to historical or
forecast data. Applying historical overrides removes the event impact from the statistical forecast.
Forecast override can be applied at a DFU or aggregate level. If you enter data at the aggregate level, it
can be filtered down to the DFU Model level. However, entering overrides does have its limitations.
Specifically, the actual results cannot be tracked against forecast overrides and the adjustments cannot be
named and identified; therefore, the effect of multiple overrides on the same DFU Model cannot be
distinguished from one to another and they cannot be tracked in the future.

Apply overrides to locks and targets

You can apply forecast overrides to locked or targeted periods using the Demand Workbench. In the case
of locked periods, the Type 3 forecast (impact of lock) is adjusted by the amount of the override so that
the total forecast quantity stays the same. In the case of targeted periods, the Type 9 forecast (impact of
target) is reduced by the amount of the override so that the total forecast quantity stays the same. The
target is then reallocated

13
Dashboard
Dashboard is an intuitive user interface that graphically represents the current status of business, along
with the historical trends, to enable improvement through a defined workflow. It helps in quick decision
making in a day in the life of a demand planner.

contains information about the Persona-based, non-in-memory Dashboard. Please seeCollaborative

workflow of Demand and ACT (ESP) for information on the in-memory Dashboard that enables the
collaborative planning workflows between Demand Worksheet and ESP (ACT).

Dashboard consists of goal and summary gadgets to view business performance and to analyze the
workflow related to manage forecast accuracy respectively. The supply chain metrics such as forecast
accuracy and forecast bias are displayed as goal gadgets, whereas information for aggregate analysis and
lag analysis are displayed as summary gadgets. The summary gadgets can be drilled down for a detailed
analysis of the defined workflow through which a planner may take corrective action to improve the
performance of underperforming DFUs.
Dashboard allows you to include the DmdUnit Description, DmdGroup Description, and Loc
Description columns in the Available Columns list on the Edit Properties: Analysis Grid dialog box. You
can select the required description columns to view them in the grid. If you select any of the description
columns, the corresponding DmdUnit,DmdGroup, and Loc columns are not displayed in the grid.
The granularity of information in Dashboard can be presented at the DFU level, and aggregated at the
hierarchy level.
You can configure Dashboard as the home page so that it provides you an overview of the defined metrics
when you log into the application. It also helps you to work with the defined workflow.
Dashboard consists of the following panes and pages containing information to support a business
process:

● Hierarchy: Consists of a hierarchy tree that is built on a selected hierarchy.

● Goals: Consists of goal gadgets displaying the trend of a metric, actual value, and deviation from
company goals.
● Manage Forecast Accuracy: Consists of summary gadgets displaying an overview of aggregate
and lag analysis.
● Manage Forecast Accuracy analysis page: Consists of analysis gadgets displaying detailed
information about a selected group using the following panes:
○ Graph: Consists of gadgets displaying the aggregate analysis, lag analysis, and revenue
forecast of the sub-groups of a selected data point.
○ Details: Displays detailed DFU data of a selected data point in a grid format.

14
Hierarchy
The Hierarchy pane consists of a hierarchy tree built on the hierarchy selected from the drop-down list
available in the Hierarchy pane. Only the DFU based hierarchies defined in Hierarchy Manager are
displayed in the drop-down list. For more information on Hierarchy Manager, see the JDA Platform
OnLine Expert.
By default, the All node is selected. You can expand and select any level within the hierarchy tree to view
the data that belongs to that level of the hierarchy in the gadgets.
If you select a different hierarchy than the default and click Save, the newly selected hierarchy is saved as
the default hierarchy. For more information, see Manage Users tab.
You can minimize the Hierarchy pane by clicking Collapse

Manage Forecast Accuracy

The Manage Forecast Accuracy pane consists of gadgets that enable you to view and compare the
performance of categories in different lags.

Edit properties
You can select a calendar, specify the number of periods, and select a metric to calculate forecast
accuracy. The calendar and number of periods specified on this page are considered by the following
gadgets:

● Forecast Accuracy
● Forecast Bias
● Aggregate Analysis
● Lag Analysis
● Revenue Forecast (available on the Manage Forecast Accuracy analysis page)
1. Click Properties from the gadget's toolbar. The Edit Properties: Manage Forecast Accuracy
dialog box is displayed.
2. Select a value from the Calendar drop-down list.
Note: Only demand calendars are displayed in the drop-down list.
3. Enter the number of periods from the Periods field for which the data is displayed.
Note: By default, 6 is selected.
For example, if the selected calendar is DmdWeek and the selected period is 4, the data is
calculated for the past four weeks from the current date. The calculated data is then displayed in
the graph.
4. Select a value from the Metric drop-down list to calculate forecast accuracy. The available
options are: Weighted MAPE, MAPE, and ABSPCTTOTERROR.

The metrics are calculated as follows:

Weighted MAPE: Weighted MAPE is calculated by weighing forecast errors in each bucket, where
weights are assigned to each error based on the sales volume, revenue, or profit of a product.

15
Weighted MAPE is calculated as follows:
[Σ|(TotHist-TotFcst/TotHist)|*W]/ΣW

MAPE: MAPE is calculated by adding the forecast errors in each forecast bucket.
MAPE is calculated as follows
([Σ|(Hist(n)-Fcst(n)/Hist(n))|]/N)*100 (number of Buckets) n=1,2…N

ABSPCTTOTERROR: Absolute percent of the error in the total forecast for the period is calculated as
follows:
(|TotHist- TotFcst |/TotHist)*100

Aggregate Analysis
The Aggregate Analysis gadget displays the revenue of a selected hierarchy level, based on the Group
By value selected in the Edit Properties: Aggregate Analysis dialog box, for the specified periods. The X-
axis displays the number of units sold and the Y-axis displays the forecast accuracy. The number of units
sold corresponds to the total history of the DFUs in the selected period. The revenue is calculated by
multiplying DFUEffPrice:EffPrice and FcstPerfStatic:TotHist. The revenue is displayed in the form of
bubbles. The bigger the bubble size, the greater is the revenue. The number of bubbles is displayed as per
the value selected in the Group By drop-down list in the Edit Properties: Aggregate Analysis dialog box.
When you place the mouse pointer on a bubble in the graph, the revenue is displayed as a tooltip.
The goal for a selected hierarchy level is displayed as a green horizontal line in the graph. The bubbles
above the goal line are displayed in green. The bubbles below the goal line are displayed in green, yellow,
or red based on the following logic:

1. Calculate a weighted distance value using the following formula:

Distance for a bubble Bn=100*(Sum(Revenue(Bn)-
Revenue(Bn)/Sum(Revenue(Bn))
where n=1,2, ….N (all bubbles' revenues with forecast accuracy less than the goal)
2. Calculate Tolerance Level + 10% and Tolerance Level + 20% of the minimum Distance.
3. Revenue bubbles with Distance less than Tolerance Level+10% are displayed in red.
4. Revenue bubbles with Distance in between Tolerance Level + 10% and Tolerance Level+ 20%
are displayed in yellow.
5. Revenue bubbles with Distance greater than Tolerance Levels + 20% are displayed in green.

If you select the All node in the Hierarchy pane, revenue is displayed for all the sub-nodes in the
hierarchy.
You can select the required lag from the Lag drop-down list on the gadget. The graph is refreshed and the
data is displayed according to the selected lag.
The gadget helps you to review the group having more revenue and take corrective action.
If you click a bubble in the graph, the Manage Forecast Accuracy analysis page is displayed with the
gadgets that provide more detail for the selected group.
Example for bubble coloring
Suppose there are five brands with revenue and accuracy values as follows:

16
 Forecast
Brand accuracy Revenue ($)
(%)

A 70 1200

B 65 1300

C 90 5000

D 80 1000

E 75 350

Accuracy goal is defined as 85% in Dashboard Manager.

Since accuracy of C is 90%, which is above 85%, it will be displayed in green irrespective of the revenue
value.
For remaining bubbles (A, B, D, E): Total revenue = (1200+ 1300+1000+350) = $3850.
The distance value is calculated as follows:

● A: 100*((3850-1200)/3850) = 68.8%
● B: 100*((3850-1300)/3850) = 66.2%
● D: 100*((3850-1000)/3850) = 74.02%
● E: 100*((3850-350)/3850) = 90.9%

Minimum distance percentage is 66.2%.

Tolerance Level + 10% = 66.1 * 1.1 = 72.7%
Tolerance Level + 20% = 66.1 * 1.2 = 79.3%
The color of bubbles will be as follows:

● Bubble1 (A) will be displayed in red as 68.8 is less than 72.7 and 79.3.
● Bubble2 (B) will be displayed in red as 66.2 is less than 72.7 and 79.3.
● Bubble 4 (D) will be displayed in yellow as 74.02 is between 72.7 and 79.3
● Bubble 5 (E) will be in green color as 90.9 is greater than 72.7 and 79.3.

Edit properties
You can modify the display of data in the Aggregate Analysis gadget by specifying the data and display
options.

1. Click Properties from the gadget's toolbar. The Edit Properties: Aggregate Analysis dialog box is
displayed.

17
 2. To rename the gadget, enter a value in the Name field.
Note: If a name is not specified in the Name field, the default gadget name is derived from the
Group by option. For example, if you group the data by brand, the gadget name is Brand
Analysis.
3. The Data Options area displays or allows you to:
● KPI: The metric used to calculate the forecast accuracy.
● Lag: Select the default lag used to display data in the graph.
4. The Display Options area displays or allows you to:
● Graph Type: The type of graph.
● UOM: The unit of measure for the data displayed in the graph.
● Group By: Select a value by which the data is grouped and displayed in the graph. The
drop-down list is populated according to the group-by options defined on the Manage
Gadgets tab in Dashboard Manager.
Note: If you remove a group-by option from the Manage Gadgets tab in Dashboard
Manager, the change is not reflected in the gadget. You must select a different group-by
option from the gadget properties to see the latest changes.
● Display Graph Values: Select this check box to display the tooltip on the graph when
you place the mouse pointer over a data point.

Lag Analysis
The Lag Analysis gadget displays the performance of groups in the specified lags of a selected hierarchy
level for a specified period. The X-axis displays the group name and the Y-axis displays the forecast
accuracy when UOM is Accuracy and total forecast when UOM is Unit.
If you select the All node in the Hierarchy pane, the comparison of lags is displayed for all groups in the
node.
The gadget helps you to compare the performance of groups with actual sales or forecast accuracy in
different lags.
If you click a data point in the graph, the Manage Forecast Accuracy analysis page is displayed with the
gadgets that provide more detail for the selected group.

Edit properties
You can modify the display of data in the Lag Analysis gadget by specifying the data and display options.

1. Click Properties from the gadget's toolbar. The Edit Properties: Lag Analysis dialog box is
displayed.
2. To rename the gadget, enter a value in the Name field.
Note: By default, a name is displayed for the gadget.
3. The Data Options area displays or allows you to:
● KPI: The metric used to calculate the forecast accuracy.
● Lags: Enter the lags to be used to display data in the graph.
● UOM: Select one of the following options to compare the lags:
○ Accuracy: Compare the lags with respect to forecast accuracy.

18
 ○Unit: Compare the lags with respect to total forecast. When you select Unit, a
sales column is added to the graph, which indicates the actual sale for a group.
4. The Display Options area displays or allows you to:
● Graph Type: The type of graph.
● UOM: The unit of measure for the data displayed in the graph.
● Group By: Select a value by which the data is grouped and displayed in the graph. The
drop-down list is populated according to the group-by options defined on the Manage
Gadgets tab in Dashboard Manager.
Note: If you remove a group-by option from the Manage Gadgets tab in Dashboard
Manager, the change is not reflected in the gadget. You must select a different group-by
option from the gadget properties to see the latest changes.
● Display Graph Values: Select this check box to display the tooltip on the graph when
you place the mouse pointer over a data point.

DFU Maintenance page

Use the DFU Maintenance page to add DFU Models, copy DFU Models, delete DFU Models, delete
DFUs, and merge history for multiple DFU Models.
Below are it’s functionalities:

19
Add DFU Model, Dmd Unit, Location, Dmd group
page
Use the Add DFU Model page to add new DFU Models to the database. From this page, you can access
additional pages to map the newly created DFUs to other DFUs or SKUs, or to associate an MLR DFU
Model with causal factors.
Use the Add Demand Unit dialog box to enter a new demand unit in the DmdUnit table. If you select
additional columns from the DmdUnit table on the DFU Maintenance Properties page: Grid Data tab,
those columns also are displayed on this page

DFU to SKU Map page

Use the DFU to SKU Map page to map the new DFU to one or more SKUs. You can map a single DFU
Model to multiple SKUs by entering each SKU in the upper portion of the page and clicking Save. The
new mapping is displayed in the bottom of the page. Repeat the process to add additional DFU to SKU
maps.

Demand Pegging page

Use the Demand Pegging page to review and edit historical and forecasted attach rates and dependent
demand of the target DFU in relation to the individual source DFUs. If any of the relation has the static
value, this value is displayed in the attach rate column and the target dependent demand is calculated
dynamically and displayed. It is calculated as:
For single-level relationships, Target Dependent Demand = Source Independent Demand * Static Value
For multiple-level relationships, Target Dependent Demand = Source Total Demand * Static Value
Where Source Total Demand is the total of its independent demand and the summation of dependent
demand with respect to all its parent sources.
The Demand Pegging page search is based on the target DFU. You can navigate from Demand Pegging to
Demand Workbench and vice versa using the Related Navigation link.

If there is no source DFU associated with the target DFU that has been included in a search, the following
message is displayed: ‘No source DFU found’.

20
Merge Forecast process
Use this page to merge the forecast that exists in the Compressed Data Storage (CDS) tables to the Fcst
and the FcstDraft table. The Merge Forecast process is used as a part of the Compressed Data Storage
functionality. For more information, see the JDA Supply Chain Planning and Optimization Installation/
Administration Guide.

Move History process

Use this page to move the history from the Hist table or the stored or computed measures data to the
Compressed Data Storage (CDS) tables. The Move History process is used as a part of the Compressed
Data Storage functionality. For more information, see the JDA Supply Chain Planning and Optimization
Installation/Administration Guide.

You can move only the history data or measure data (stored or computed) at a time

Reconcile Forecast process

Use the Reconcile Forecast process to reconcile forecasts allocated by one or more maps. The Reconcile
Forecast process keeps forecast totals synchronized between levels of the DFU hierarchy. Forecasts can
be reconciled from the upper level to the lower level, as well as the lower level to the upper level. In
addition, you can specify the type of forecast data you want to reconcile.

Creating an issue for the error in JIRA and

closing the issues after it’s been resolved
Finding errors in executing the cases through:

 Manually

 Toad for oracle server

 SSMS for sql server

**** THE END ****

21
22