Você está na página 1de 8

Whats New in JDA Platform

Installation and Configuration changes

The installation directory structure has been changed


<install_dir>\config\bin\<application>
All documents is consolidated to
<install_dir>\config\doc
The data base directory for each application is located in
<install_dir>\config\database\<application>
All database scripts are located in
<install_dir>\config\database\setup
All JDA reporting models and template reports are installed to
<install_dir>\config\reports
The database instance creation scripts are located on the CD image so that
we can create the database instance before installation.
The environment name can be specified during installation (e.g. production,
test, development). The value specified during installation is appended to the
server startup script to customize the JDA service name, as well as displayed
in the header of the JDA application pages.
The installation now prompts for an ORACLE_HOME directory in order to
access the Oracle JDBC driver for database connections.
The installation now provides the option to perform the post installation tasks
automatically.
On windows we can deploy .NET Framework during installation if correct
version of the Microsoft .Net framework is installed on the server.
Additional options are provided to automatically configure and remove the
CIS services when the JDA Platform service is created on Windows.
The Common Infrastructure Services (CIS) component, which provides single
sign-on capabilities, now supports failover capabilities in case the primary
server goes down or is unavailable.

Migration
JDA Platform now supports a more seamless database migration from version
7.4.2 or higher to version 8.0. If migrating a database from version 7.4.2 or
higher, you can use one set of scripts to migrate the schema directly to
version 8.0 instead of migrating through each interim version. A similar set of
scripts is provided for JDA Monitor migration.

User Interface Changes


The navigation pane have been updated and enhanced

Graphical icons in the navigation pane now enable the Solution Navigation
and My Navigation folders to open when you mouse over the icons.
You can now click an icon to display a user-defined folder in the left-hand
side of the navigation pane for quicker access.
In the Manage Solution Navigation folder, you can now attach icons to a
folder to customize the look of the folder.
Multiple tabs can be opened within the JDA navigation pane. If you click on
the tab icon to the right of the page name in the navigation or directory, the
page will open in a new tab, as opposed to the existing tab. Note that not all
pages will support multiple instances of the same page being open.
Double-clicking on a tab will tile the open tabs so that you can re-arrange the
windows to display as you wish. A subsequent double-clicks of a tab title
returns the windows to the default tabbed view. Tabs can then be moved
within the JDA UI by dragging and dropping the tab.
Using related pages from one page to another will open the related page into
a new tab instead of replacing the window.
Clicking on the far left partial tab will provide a thumbnail view of the tabs.

Copy paste in VP grid


In current release v8.0, several new functions are introduced to copy and paste
data from Platform UI to Microsoft office supported tool such as Excel. To enable
this functionality, we need to first enable the programmatic clipboard access in
Internet Explorer. We can copy, cut, and paste the following using the familiar
operations of Microsoft Office that you know:

Single or multiple rows


Single or multiple columns
Range of cells in a grid

This new functionality helps us now to seamlessly copy and paste data directly from
application UI to supported worksheets reducing time and effort.

Security and user management changes

Management of users and their assignment of privileges in the system are


now handled in the User Manager page. The Security Manager no longer
contains a User tab. The Security Manager will continue to be used to
manage roles, enterprises, security filters, partnerships, and resources for
Foundation-based applications. For ABPP-based applications, role
management is handled in the User Security Manage Role page.
For new installations that create a new database, the default administrative
user is now System. For databases that are migrated, the System user will be
added. By default, this user will be given a role of HostAdmin.
All users must have a Foundation role assigned in order to log into the
system. A default role of Basic is provided that can be assigned to users for
login purposes. Additional roles and user groups can be assigned in order to
enable additional capabilities.
A new user import utility (userImport) is provided to bring users into the
system in bulk. For JDA Foundation-based applications, the csmImport utility
is no longer supported to import users, but continues to support bulk import
of Enterprises.
The user password encryption algorithm has been strengthened. As a part of
this change, all user passwords in the database must be reset if you are
authenticating against user passwords in the database. The utility
resetUserPassword is provided to reset all user passwords and email a
temporary password to users so that they can reset their passwords.
Alternatively, you can use the genPasswordHash utility to generate a
password for a particular user and replace the password in the database.

Release 8.0.0.0 of JDA Demand provides the following new


enhancements.
Major Enhancements
Measures:
The measures functionality has been introduced in Demand. Measures are
created to store and display time variant data values using any external data,
existing historical and forecast data, or any user computed logic. These
measures are used to enhance the forecast that drives the business planning.
For example, Sales Forecast measure is an estimate of all future sales
activity of a product.
Following are the measures types:
Stored Measures
Computed Measures

Pre-Defined Measures
Measures can be accessed in Demand Workbench and Demand Worksheet
UIs and Delete DFUs, Copy Measure data, Reconcile Forecast, Calculate
Model Processes.
The following new user interface and process have been added to support
this functionality:
Measure maintenance page: This page is used to manage stored,
computed, Pre-defined and Pre-defined draft measures and data
associated with them.
Copy measure process: This process copies the measure data from a
selected source measure to a selected target measure. The target
measure displays the same data as its source measure. When this
process is run, the calendars for the selected source and target
measure are compared and the copied data is saved according to the
one with maximum periodicity. This process is used for only DFU based
measures.

JDA Demand 360 Module


The JDA Demand 360 module (with the main view of module is Demand
Worksheet) has been introduced in Demand. This is a licensable module and
does not come automatically with Demand. The Demand Worksheet is a pivot
table that enables us to view, review, and edit the measure data,
corresponding to the selected facet and its hierarchy levels. This worksheet
helps us to configure the historical and forecast measure data. We can apply
locks to editable data cells to disable any change in its data value. The data
in the pivot table can be aggregated and disaggregated across the
hierarchical levels. When there are locks applied during disaggregation, the
change in the data values is distributed among the unlocked child and parent
cells of the hierarchy.
The following system properties have been added to the Demand Worksheet:

WorksheetDFUSearchLimit: Specifies the maximum number of


DFUs that can be included in DFU search in Demand Worksheet.
WorksheetMeasureLimit: Specifies the maximum number of
measures that can be selected from available measures list in the
Demand Worksheet Properties page.
WorksheetComputedMeasureLimite: Specifies the maximum
number of computed measures that can be selected from available
measures list in Demand Worksheet Properties Page.

Attach rates enhancements: Multi-Level Attach Rates and


Normalization
The attach rates functionality has been enhanced to include the multiple level
attach rates and normalization concepts. There can be multiple source and
target DFUs in the product assembly. The target DFU of one relation can be a
source DFU for other relation. And the source DFU can be a target DFU for
other relation.

Negative Override Warning


The override functionality in demand is now enhanced to provide the warning
message when the override value is greater than the total history, resulting
in negative base history. The warning message is displayed on the following
pages:

Demand Workbench History and Forecast Tab, Create Override on


Graph.
Decision Support Workbench History and forecast grid, Save
manager.
Override Manager.

Demand Management Report


The reports functionality has been introduced in Demand to help you
understand and analyze the behavioral trend and performance of the
forecast. These are read-only reports and built using JDA Reporting. These
reports are displayed only when JDA Reporting is also installed on the JDA
Platform.

Move History process Enhancements


The Move History process now allows you to select the type of history to be
moved. The existing Move All option is renamed as Available History Range.
Along with StartDate only and Startdate and Duration options, this process is
enhanced with three additional UI options Replace Entire History, Available
History Dates only, and Add to Existing History.

Calculate Model Enhancements


The following changes have been made to the Calculate Model process:

Calculate Model based upon HistStart Date instead of 1st history value.
Separation of CalcModel_PurgeAll option for values prior to
DemandPostDate.
Exception to alert unstable regression model.

Exception Graph Extensions / alignment of graph options from DSW


The Exception Graph page and Exception Graph panels in the Demand
Workbench have been enhanced to include four graphs that were available
only in the Decision Support Workbench.

Release 8.0.0.0 of JDA Fulfillment provides the following new


enhancements.
Dynamic Allocation
This feature identifies the supplies that are available to be distributed to
stores and decide how the supplies are to be allocated to each store.
Dynamic Allocation is divided into two components, need and allocation. The
following workbenches and processes help us to achieve this business
requirement.

Replenishment Dashboard features and MDAP support


Replenishment Dashboard supports display name feature for the SKU, SKU
Projections and related columns used in the user interface. The dashboard
also supports scenario feature. Using this feature, we can see the SKU
Projections data in the Grid and Graphical format in an aggregated format for
the Dashboard SKUs.
Dashboard supports in-memory model for large retail volume of data using
MDAP feature. We can use Dashboard to work on a large volume data to
resolve business issues.

StatSS time-phase Customer Service Levels

This feature supports the calculations of Statistical Safety Stock Quantity and
Safety Stock Coverage for time-phased Customer Service Levels (CSL).

Pack Rounding
This feature provides additional flexibility in rounding replenishments created
by the Calculate Plan process. This feature, along with existing lot sizing with
respect to Min/IncDRPQty, allows you to round up and round down the
replenishments to the defined convenience ship rounding quantities.

Retain safety stock in Demand Reduction


When the RetainSSinDmdReduction property is enabled, the Calculate Plan
process provides visibility into the non-ignorable safety stock component of a
distribution demand, working in parallel with the Demand Reduction feature.

Time-phased Order Optimization in Plan Analysis


Several new columns have been added to the SKUProjStatic table to allow us
to view time-phased Order Optimization results within Plan Analysis. These
columns work together to allow us to view how the projected orders are
affecting the projected on-hand.

Sourcing at Arrive Date in Order Optimization


Prior to release 8.0, Order Optimization considered the effectivity of Sourcing
rows active based on OrderPlaceDate. Order Optimization has been changed
to consider Sourcing rows active based on the ArrivDate rather than the
OrderPlaceDate.

Perishable Planning and MaxWasteFactor; Include safety stock in


waste reduction, ignore demands that cannot be met on time, and
continue planning.
Forward Buy based on a price increase
Order Optimization can now consider a forward buy based on comparing the
current price with the future price entered in the DealSKU table. This allows
you to make an investment in inventory at the lower price.

Você também pode gostar