Oracle® Retail Allocation

Release Notes

Release 13.2.9

E73280-01

March 2016

Oracle Retail Allocation Release 13.2.9 is a patch release for Allocation 13.2.�

Allocation 13.2.9 includes selected defect fixes and enhancements for Allocation 13.2 code.� Oracle Customer Support investigates submitted issues assuming that all released� updates have been applied. It is the customer's decision when to apply a new release;� however, delays in applying updates can complicate the support process.

About Patch Releases

Oracle Retail patch releases are periodic releases that can include new defect fixes and� product enhancements.

Documentation for patch releases includes the following:

New and updated guides (for example, operations and user guides) that apply to the patch release level. See "Related Documentation" for a list of the documents published for Allocation 13.2.9.
Defect reports for new fixes and enhancements for the patch release.

See the Oracle Retail Allocation Installation Guide for Release 13.2.9 for instructions about how to apply the defect fixes and enhancements that you have not already installed.

Applying a Patch Release

Before applying the Allocation 13.2.9 patch release, be sure that:

Allocation 13.2 has been installed.
Patch release Allocation 13.2.8 has been applied.

Before applying the release over your files:

Note whether any modules have been customized. If so, the customizations must be reapplied to the new version of the module, or the fix may need to be applied to the custom version of the code.
Copy the original files to a different directory before you copy over them, in case you need to refer to them at a later date.

Back up data before running any script, because the scripts provided do not preserve data. See defect reports for details.

Check with your database administrator to determine whether your database should be analyzed after a script is run. In many cases, analysis of the database is necessary to take advantage of new or modified indexes intended to improve performance of the application.

Hardware and Software Requirements

See the Oracle Retail Allocation Installation Guide, Release 13.2.9 for information about the following:

Hardware and software requirements
Oracle Retail application software compatibility

Technical Enhancements

This section addresses the technical enhancements included in Oracle Retail Allocation Release 13.2.9.

Note:

The list below announces the addition of Oracle Retail support for the technology described. See the Oracle Retail Allocation Installation Guide requirements section for critical information, such as whether the enhancement below replaces previous versions or is supported in addition to already existing versions.

Database Server Support

Oracle Retail Allocation Release 13.2.9 is supported for use with the following database server:

Oracle Database Enterprise Edition 12cR1 (12.1.0.2)

Oracle Fusion Middleware

Oracle Retail Allocation Release 13.2.9 is supported for use with the following Oracle Fusion Middleware:

Oracle Access Manager (OAM) 11.1.2.3
Oracle HTTP Server (OHS) 11.1.1.9
Oracle Internet Directory (OID) 11.1.1.9
Oracle WebGate 11.1.2.3

Browser Support

Oracle Retail Allocation Release 13.2.9 is supported for use with the following browser:

Microsoft Internet Explorer 11
Mozilla Firefox ESR 31+

Defect Fixes and Documentation

A defect fix is a modification to the base Oracle Retail code (for example, a bug fix, a performance enhancement, or a functional enhancement). Each defect fix that is included in this patch has a corresponding defect report titled <defect-number>.PDF (for example, 1234567.PDF) that is posted to My Oracle Support at the following location: Oracle Retail Defect Document Listings (MOS ID:2021275.1).

In the same folder, the file named DEFECT MODULE XREF ALLOCATION 13.2.9.XLS lists every defect number and the modules and scripts that are included in the patch. Review each defect report carefully before implementing the defect fixes. Note that scripts do not preserve data. Make sure that all data is backed up before you run any script.

Noteworthy Defect Fixes

The following defect fixes are included in this release:

Defect Num8ber	Description
21671105	Unable to create a fashion allocation using size profile as a constraint. This enhancement fulfills the style/color demand at a store either using the store size profile data as a guide or enforces the allocation system to only fill the store demand if the size profile data associated with the store can be fully achieved across all eligible sizes, using an all or nothing logic. This prevents the stores from being allocated to sizes above and beyond its associated store size profile data in order to meet total store demand.
20815991	Support for fringe sizes in allocation - This logic allows you to allocate an item at the style/color level as long as at least one SKU under the style/color item passes the validation. A new property setting is added in Allocation which allows you to define whether: Option A - Allocation takes place for a fashion item only if the ranging as well as item/location status checks for a style/color item are satisfied at the parent item level as well as all the child items (current behavior); or Option B - Allocation takes place for a fashion item as long as the parent item and at least one of the child items are ranged and have a valid item/location status. The child items which are not ranged or do not have a valid item/location relationship are not considered while allocating the items.
22341143	Allocating two or more PO's with the same item on a single allocation causes the Final Allocated Quantity to be multiplied by the number of PO's.
22170526	An incorrect amount is allocated and displayed for Non-Sellable Complex Pack.
22068930	The maximum open cursors are set to 1000 and the calculation engine fails frequently with an exception.
21869355	The complex grouping of Location Trait and Location List is displays an error when they both have the same numerical ID.
21759643	The Minimum Quantity Limits do not adjust the Gross Need correctly when the inner and case values greater than 1.
21697851	Scheduled Allocations cannot be created in the Portuguese language.
21535575	Stock On Hand (SOH) and Future fulfillment (FF) do not display de-aggregated fashion item for user selection of hierarchy.
21493432	The allocation triggers are 100x slow as the allocation number is VARCHAR instead of a number.
21163723	The user selection option does not work correctly; It is receiving different values for Gross Need, Net Need, and SOH.
21090730	When you process the SOSTATUS or the ASNOUT, the system should not modify the allocation status (ALC_ALLOC.STATUS=3).
21086429	When the customer has different supplier pack sizes on same item for different suppliers, the allocation considers the each/inner/case size of the primary supplier.
18526453	When you create a Warehouse or Direct to Store PO from What-if the Pre Mark IND When you process the SOSTATUS or the ASNOUT, the system should not modify the allocation status (ALC_ALLOC.STATUS=3).
18418062	You can approve an allocation for a cancelled ASN.
17192848	You are redirected to the Allocation main page when you select the Remove on page Review Items button.
22468542	Cannot allocate to active items/locations if one or more item/locations are inactive.
22468596	Remove 'enforce store size profile' checkbox for what if allocations.
22467961	Toggle to group in the details screen location section does not display results.
22468256	'Enforce size profile' does not copy when copying an allocation.
22468707	'Enforce Store Size Profile' box becomes unchecked after initial calculation.