An Oracle White Paper

April 2012

Introduced in Release 6.0

E29322-01

GSM Edible Portion

# Overview

Applications: GSM

Focus Area: Ingredients and Formulation

The idea behind edible portion is that not all material can be consumed. If not all materials can be consumed then not all materials contribute equally when combining materials together to make new materials. Therefore theoretical rollups are calculated based on the edible amount.

# The Basics

Let’s look at a simple example. In example A we have an item where both ingredients are 100% edible, represented by column C. Therefore when we roll up the Total Fat per 100g we need to consider the contribution that each ingredient provides. Ing 1 and 2 contribute equally because their input amount, column B, and their edible portion, column C are the same. By blending the two ingredients into a new output we end up with 7.5g of Fat per 100g.

Figure 1. Example A

Now let’s change the scenario. In example B Ing 1 is now only 25% edible. It might represent meat on the bone or another item where very little of the total weigh is edible. In this example you will notice that the edible ratio, column E, for both items change. This indicates that Ing 2 is providing a majority of the edible material. Therefore the Fat per 100g for Ing 2 has a greater impact on the output. In this case the combined material output has 6g of Fat per 100g.

Figure 2. Example B

### Additional Notes

- We do not believe it will be appropriate for most customers to use edible portion. By default the GSM.EdiblePortion.Enabled configuration is set to “false” or off. Therefore if you choose to use it you will need to change the value to “true”. This configuration is found in the BaseFeatureConfig and can be copied to the CustomerFeatureConfig.

- If you enable the functionality and choose not to use edible portion for one or many items then the edible portion for these items should be marked as 1 or 100%.

- For items impacted by edible portion we have also determined that users often need to adjust the label’s serving size. Users will need to perform this work on the Nutrient Profile using a combination of serving size and custom data in order to generate proper panel data.

GSM Edible Portion March 2012 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 oracle.com | Copyright © 2012, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. 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. UNIX is a registered trademark licensed through X/Open Company, Ltd. 1010