| Oracle® Retail Brand Compliance Management Cloud Service Release Notes Release 18.1 F18532-03 |
|
 Previous |
| Oracle® Retail Brand Compliance Management Cloud Service Release Notes Release 18.1 F18532-03 |
|
Previous |
Release Notes
Release 18.1
F18532-03
November 2019
This document highlights the major changes for Release 18.1 of Oracle Retail Brand Compliance Management Cloud Service.
Oracle Retail Brand Compliance Management Cloud Service is an application designed to meet all aspects of sourcing, developing, and protecting retailer brands. The application provides solutions for product development, compliance, quality, and traceability. It is designed specifically for retail, food service, and manufacturing businesses to develop and protect their brands, manage their suppliers, and ensure full end-to-end product lifecycle management.
Oracle Retail Brand Compliance Management Cloud Service is composed of the following modules:
Library enables the issue, receipt, and acceptance of policies, guidelines, and key working documents.
Product supports the development of products and production specifications.
Project supports the development of project briefs, plans, and workflow management.
Supplier enables the identification, selection, and approval of suppliers.
Reports - reporting tool for reporting across the system, using standard templates and custom reports.
Oracle Retail Brand Compliance Management Cloud Service is hosted in the Oracle Retail Cloud with the security features inherent to Oracle technology and a robust data center classification, providing significant uptime. The Oracle Cloud team is responsible for installing, monitoring, patching, and upgrading retail software.
Included in the service is continuous technical support, access to software feature enhancements, hardware upgrades, and disaster recovery. The Cloud Service model helps to free customer IT resources from the need to perform these tasks, giving retailers greater business agility to respond to changing technologies and to perform more value-added tasks focused on business processes and innovation.
Oracle Retail Software Cloud Service is acquired exclusively through a subscription service (SaaS) model. This shifts funding from a capital investment in software to an operational expense. Subscription-based pricing for retail applications offers flexibility and cost effectiveness.
The following technology is supported:
The following web browsers are supported:
|
Note: Oracle Retail assumes that the retailer has ensured its Operating System has been patched with all applicable Windows updates. |
Microsoft Internet Explorer 11
Mozilla Firefox ESR 60+
Google Chrome (Desktop) 73+
|
Note: Where new fields, User Interface (UI) changes, or glossary entries are introduced as part of a change, the portal owner may need to apply their own translations of the core system text. |
The following functional enhancements are included in this release:
Retailers often collect product specifications from their suppliers for items that are used as raw materials within products that the retailer manufactures themselves, such as in-store bakery goods. The Combined Specifications feature allows retailers to compile their own finished product specifications by combining sections from existing raw materials specifications that have been created by suppliers. Effectively a scratchpad facility forming the raw material data into the finished product specification, the key features are:
The facility is enabled or disabled by a system parameter.
New glossaries provide configurable rules for combining specification sections.
Provides the option to create a specification by combining sections from other existing specifications.
Can also combine sections into an existing specification.
A wizard guides the user through the process of combining specification sections.
Sections that can be combined are Recipe/Formulation, Nutrition, and Dietary & Allergy/Additional Product Info.
Applies to all specification types other than Produce, but can only combine specifications of the same type.
A percentage breakdown is entered to apportion the recipe and nutrient values in the finished product.
The raw material recipes are combined into the finished product recipe as compounds.
Dietary & Allergy/Additional Product Info data is the worst case of the combined data, based on configurable rules.
The feature is available to both supplier and retailer users, subject to access rights.
Combined specifications must be unlocked before editing. Details of their source can be viewed.
The finished product specification is progressed through the usual workflow stages.
A post-upgrade task will be to enable or disable the feature (the default is for it to be enabled) and set up the contents of the glossaries, either manually or using the glossary import option.
A new combine option appears in the specification creation wizard for all specification types other than Produce. Additional steps in the wizard guide the user through selecting the specifications and sections.
A new specification action appears for combining sections into an existing specification.
When sections are combined into a specification, the contents of the new Recipe/Formulation, Nutrition, and Dietary & Allergy/Additional Product Info sections are automatically populated based on the selected sections.
New options appear in Specification list views (Extract Source Specifications and Extract Specifications Where Used in the Actions menu) to extract details of combined specification usage to spreadsheet.
New batch jobs and notification emails are introduced for the creation of combined specifications.
New configuration options appear in the Admin area for Combine Question Rules and Combined Specification Nutrients glossaries, plus a new parameter in the Dietary & Allergy Declarations glossary and a new system parameter.
For in-store products, it may be necessary for the retailer to create their own Supplier and Site accounts.
The introduction of specific nutrition legislation rules for Canada, based on the current US legislation, plus various enhancements that are applicable to the US and Canada legislations:
To accommodate the new Dual format panel where both nutrient value and daily value percentage must be declared, the option to configure which values are declared on-pack is enabled for US and Canada legislations.
An Amount Prepared column heading field is added to the specification, and the current As Prepared Values option in the Nutrition Panel glossary is renamed Use Dual Format.
The Dual panel is used for Supplement products, with declaration of both Per Serving and As Prepared values.
The order of the Servings per Container and Serving Size statements in the declaration panel is reversed (US only).
The declaration of Calories, Calories from Fat, and Calories from Saturated Fat now show blank if the nutrient has no daily value (instead of referencing a footnote).
Nutrient amounts for vitamins and minerals are declared in addition to their daily value percentages.
An option to include a disclaimer statement with the declaration panel, stating that the output is not intended to be an exact representation of the on-pack nutrition declaration. Where used, the disclaimer will appear as part of the panel within the Pack Copy file, reports, and Specification APIs.
A decision has been made to move away from presenting nutrition declaration data with any graphical formatting, in order to avoid giving the impression that it is a representation of the packaging or label design. This is initially just applied to the US and Canadian legislations.
New installations will include the core Nutrition Panels and related glossaries for US and Canada (including the new Dual panel).
|
Note: In 2016, the US FDA published a final rule under the Food, Drug & Cosmetic (FD&C) Act, which amends the Nutrition labeling regulations for packaged foods and dietary supplements. Most of these changes can be achieved through the configuration capabilities of Brand Compliance, however the enhancements described above are necessary.Canadian authorities have drafted proposals for changes to their Nutrition labels (which are different to the US amendments), but these are not yet finalized, and so are not included in these enhancements. |
The Canada legislation becomes available for use, but must be configured as appropriate to the retailer's specific requirements.
The Nutrition Panels and related glossaries must be manually uploaded as part of the upgrade project. Manual configuration will be necessary, including the new Dual panel and setting a default value for the Amount Prepared panel heading text. The As Prepared Values option is renamed Use Dual Format.
The option to select which panels are to be declared becomes available in the Nutrition Panel glossary. Existing panels should be checked that columns have not inadvertently been selected to be declared, now that the feature is enabled for US and Canada legislations.
The US requirement to include nutrient value as well as the daily value percentage for vitamins and minerals can be achieved by editing the Nutrient Panel glossary record and removing the US Vitamin header from the Nutrients list, so that all nutrients appear within the US Main section header. It may be necessary to create a new version of the panel.
If the disclaimer text is to be output to the panel, configuration setup is necessary to enable it and set the disclaimer text.
Existing installations will have the nutrition declaration formats replaced with the new simple table style. Existing specifications that have already have a US panel generated will retain the original format until the specification is next edited at a draft status, in which case it will become necessary to regenerate the declaration panel before the specification can be progressed. The upgrade process will automatically set the Declaration Refresh Required flag.
Newly-generated panels will have the order of Servings per Container and Serving Size values reversed (US only).
Calories, Calories from Fat, and Calories from Saturated Fat will show blank in the panel if there is no percentage daily value.
|
Note: The existing dual functionality can be utilized to provide the required dual columns in the data entry table. However, the following columns need to be included in the columns to be declared in the Nutrition Panel configuration:
Special consideration is required for installations that currently use US legislation for the Canada market. This will be dealt with by providing guidance if/when an upgrade project is initiated, on how to transition from the current Canadian/US legislation to the new Canadian legislation - which may be by naming them Canadian Old and Canadian New. |
Nutrient Targets were originally introduced to comply with Salt Target requirements in the UK, hence the Brand Compliance functionality was limited to a single nutrient. Changing market requirements mean that Salt is no longer the only nutrient of concern, with focus now also on nutrients such as Sugar and Fat.
The existing Nutrient Targets facility is enhanced to provide the capability of configuring target criteria (per legislation) for any number of nutrients, and to allow for both maximum and minimum target values.
When a specification's Nutrition declaration panel is generated, any targets are updated with an indication of whether the target was achieved or not, and whether it was a maximum or minimum target. If a target is not achieved, it will result in a warning or terminal error based on the configured rules.
Nutrient Targets are only enabled in Food specifications; they are not used in Produce or BWS specifications.
Where used, the target details will appear as part of the panel within the Pack Copy file, reports, and Specification APIs.
A system parameter allows the configuration of which legislations will use nutrient targets.
The Nutrient Targets glossary record is changed to allow for multiple nutrients to be selected, with separate tables for maximum and minimum targets. Existing installations will have their glossary entries converted to the new format as part of the upgrade process.
The Food specification's Nutrition section is changed to cater for multiple minimum and/or maximum targets.
When an existing Food specification that uses targets is next edited at a draft status, if the Nutrient Target configuration has been changed, such as to use additional nutrients, it will be necessary to regenerate the declaration panel (including targets) before the specification can be progressed further.
A manual post-upgrade task will be required to reconfigure the default Exempt category (or similar), to ensure the minimum and maximum target tables do not contain any entries.
A manual post-upgrade task will be required to check for any usage of the Columns to be Declared option in US legislation specifications, that is, where it was previously selectable but had no effect. This is necessary to avoid the possibility of a declaration having been erroneously selected, which would now come into effect, as the option is being enabled for all legislations.
If using the US Dual Panel, ensure the Nutrition Panel configurations include the following columns to be declared:
| Column | Preset by Default |
|---|---|
| Per Serving | Yes |
| %Reference Intake Per Serving | Yes |
| %Reference Intake Per Serving As Prepared | Yes |
The calculation of Energy values is extended to include the automatic calculation of nutrient values for Salt and Other Fats.
The rules for which nutrients are calculated (and any conversion factors) are configurable. Configuration provides more flexibility in identifying the nutrients used in the calculations, however it is initially limited to Energy, Salt, and Other Fats.
The default setting is for Energy to be calculated for all legislations except US and Canada; Salt to be calculated for EU only; and Other Fats to be calculated for Mexico only.
The calculations can be used within Food, Produce, and BWS specifications, but only to the Full nutrition formats, not to the Lite format. The values in the data entry table of the specification's Nutrition section are automatically calculated in accordance with the configuration settings, and become read-only.
The Energy calculation is as per the current calculation; Equivalent Salt is calculated by multiplying Sodium by the configured factor; Other Fats is calculated as Fat less Saturated Fat.
Options become available in the Nutrient Calculations configuration record to enable calculations per legislation for Energy, Salt, and Other Fats.
Values in the data entry table of the specification's Nutrition section become automatically calculated and read-only if the nutrient is configured to be calculated.
A manual post-upgrade task will be necessary to set the Nutrition Calculation configuration to enable/disable the Energy, Salt, and Other Fats calculations as required.
|
Note: The Salt calculation is enabled by default for EU legislations, with the Salt Factor parameter being set to 2.5.If the automatic calculation of salt from sodium is not required, the option must be disabled. If enabled, the Salt calculation assumes the unit of measure of the salt and sodium nutrients are both grams (g). If the sodium unit of measure is milligrams (mg), the conversion factor parameter must be set to 0.0025 instead of 2.5. For example: Sodium 0.5g x 2.5 = Salt 1.25g Sodium 500mg x 0.0025 = Salt 1.25g |
A new Nutrient Type field appears in the Nutrient glossary record, which must be set for the nutrients to be automatically calculated. It may be necessary to create a new version of the nutrient.
The enhancement results in a change to the structure of the XML returned by the Specification REST API. Previously, a single nutrient target category could be selected per Nutrition section (typically Salt). The enhancement now allows targets for multiple nutrients per Nutrition section. The XML structure within the specificationSectionFoodNutritionSection segment therefore now contains a specificationFoodStandardCategoryDetail element for each target category, instead of a single foodStandardCategory element. The specificationFoodStandardCategoryDetail element contains nutrient and targetAchieved elements to identify the nutrient and whether it achieved its target.
Support for product nutritional information legislation is introduced for the following countries:
South Africa
Mexico
Chile
Argentina
Brazil
Japan
India
The new legislations are based on the current EU legislation; in addition, the Mexico legislation has specific Front of Pack nutrition labeling capabilities for declaring certain nutrient values as calories, along with Energy per Pack total amount.
The suite of Brand Compliance Management Cloud Service APIs is extended to allow for the retrieval of Scorecards, using standard REST web service technology. Details of how to call the web service can be found in the Oracle Retail Brand Compliance Management Cloud Service Implementation Guide.
To support the integration of Scorecards with external systems, Scorecards are now each assigned a unique business key identifier.
Options are available in the External Systems section of the Admin area to grant external systems access to the new Scorecards API.
A unique ID business key field is added to the Scorecard record. The IDs are also shown in certain list views.
|
Note: The new API initially only provides the ability to retrieve (GET) data. |
The suite of Brand Compliance Management Cloud Service APIs is extended to allow for the retrieval of Project and their associated Activities, using standard REST web service technology. Details of how to call the web services can be found in the Oracle Retail Brand Compliance Management Cloud Service Implementation Guide.
To support the integration of Projects and Activities with external systems, Activities are now each assigned a unique business key identifier (Projects already have a business key).
Options are available in the External Systems section of the Admin area to grant external systems access to the new Projects and Activities APIs.
A unique ID business key field is added to the Project Activity record. The IDs are also shown in certain list views.
|
Note: The new API initially only provides the ability to retrieve (GET) data. |
The Attachments API is extended to allow retailers to retrieve file attachments held on the Scorecard, Project, and Activity records. Details of how to call the web services can be found in the Oracle Retail Brand Compliance Management Cloud Service Implementation Guide.
To use the Attachments API, an External System record will need to be configured and assigned the appropriate Endpoint and Service
|
Note: The API provides the ability to retrieve (GET) attachment data for Scorecards, Projects, and Activities, in addition to the current service for Report Outputs. |
The following improvements are included in this release:
Various enhancements have been made to the Brand Compliance Application Program Interfaces (APIs), to support the new features, and for general improvements:
The new Audit/Visit Code is added to the GET method of the Audits REST API.
Various other improvements for filters, wildcard searching, and error logging in the REST APIs.
It is not necessary to make changes to existing calls to the APIs, unless the new features are to be utilized.
Additional fields are made available for use in email templates:
The email templates PROJECT1 and PROJECT2 that notify users as a Project or Activity progresses through its workflow stages have fields available to identify the project and any associated suppliers, sites, and contacts.
The email templates ADVISEPACKCOPY and SPEC4 that notify users of the progression of Pack Copy files have the Pack Copy Version added.
The email templates REGISTER EMAIL PASSWORD, REG1, REG2 REG3, and REG4 that notify users about account registration have their content revised, including addition of the names and email addresses of the person who created the account.
The additional attributes are not included by default in the email templates, but are available to be added if required, in which case the system administrator must edit the relevant Notification Email templates.
A new system parameter provides a permissions configuration option to set whether the Benchmark fields in the Product Record may be edited by supplier users as well as retailer users. If the parameter is set, both retailer users and supplier users who have access rights to edit a Product Record will also have the ability to edit the Benchmark fields; otherwise the Benchmark fields are restricted to retailer users only.
The new system parameter will need to be set by an administrator with Oracle Authorized User access rights.
The Pack Copy file format is changed to include the Certificate Type and Main Product Title fields, and to show the Main Product Title at the top of the first page.
All fields are included when a Product Record is copied, except Benchmarks and Barcodes.
Emails to suppliers notifying them that they have been assigned a Produce specification are now sent with the recipients being Bcc'd rather than Cc'd.
New columns appear in the Global Change options for Products, Projects, and Sites.
For more information, see the following documents in the Oracle Retail Brand Compliance Management Cloud Service Release 18.1 documentation set:
Oracle Retail Brand Compliance Management Cloud Service Administration Guide
Oracle Retail Brand Compliance Management Cloud Service Implementation Guide
Oracle Retail Brand Compliance Management Cloud Service User Guide
Oracle Retail Brand Compliance Management Cloud Service Product User Guide
Oracle Retail Brand Compliance Management Cloud Service Project User Guide
Oracle Retail Brand Compliance Management Cloud Service Reports User Guide
Oracle Retail Brand Compliance Management Cloud Service Supplier User Guide
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Retail Brand Compliance Management Cloud Service Release Notes, Release 18.1
F18532-03
Copyright © 2019, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.
Value-Added Reseller (VAR) Language
Oracle Retail VAR Applications
The following restrictions and provisions only apply to the programs referred to in this section and licensed to you. You acknowledge that the programs may contain third party software (VAR applications) licensed to Oracle. Depending upon your product and its version number, the VAR applications may include:
(i) the MicroStrategy Components developed and licensed by MicroStrategy Services Corporation (MicroStrategy) of McLean, Virginia to Oracle and imbedded in the MicroStrategy for Oracle Retail Data Warehouse and MicroStrategy for Oracle Retail Planning & Optimization applications.
(ii) the Wavelink component developed and licensed by Wavelink Corporation (Wavelink) of Kirkland, Washington, to Oracle and imbedded in Oracle Retail Mobile Store Inventory Management.
(iii) the software component known as Access Via™ licensed by Access Via of Seattle, Washington, and imbedded in Oracle Retail Signs and Oracle Retail Labels and Tags.
(iv) the software component known as Adobe Flex™ licensed by Adobe Systems Incorporated of San Jose, California, and imbedded in Oracle Retail Promotion Planning & Optimization application.
You acknowledge and confirm that Oracle grants you use of only the object code of the VAR Applications. Oracle will not deliver source code to the VAR Applications to you. Notwithstanding any other term or condition of the agreement and this ordering document, you shall not cause or permit alteration of any VAR Applications. For purposes of this section, "alteration" refers to all alterations, translations, upgrades, enhancements, customizations or modifications of all or any portion of the VAR Applications including all reconfigurations, reassembly or reverse assembly, re-engineering or reverse engineering and recompilations or reverse compilations of the VAR Applications or any derivatives of the VAR Applications. You acknowledge that it shall be a breach of the agreement to utilize the relationship, and/or confidential information of the VAR Applications for purposes of competitive discovery.
The VAR Applications contain trade secrets of Oracle and Oracle's licensors and Customer shall not attempt, cause, or permit the alteration, decompilation, reverse engineering, disassembly or other reduction of the VAR Applications to a human perceivable form. Oracle reserves the right to replace, with functional equivalent software, any of the VAR Applications in future releases of the applicable program.
