An Oracle White Paper
April 2012
Introduced in Release 6.0
E29318-01
Available Unit of Measure Management
Applications: GSM
Focus Area: Ingredients, Packaging, Printed Packaging, Formulation, and Trade
We have found the need to limit the units of measure (UOM) available for a specific raw material. This impacts both formulation and integration to host system use cases.
Users now have the ability to configure the system to explicitly state the units of measure raw material specifications are to be consumed in when they are used in Formulation Specifications. In conjunction with this new configuration option, users can add and qualify unit of measure data on raw material specifications (Ingredients, Packaging and Printed Packaging specifications). They can define the base UOM as well as all of the other available UOMs that can be used for each specification.
When the system is set to manage UOM data explicitly, the UOM data that has been added to the raw material specification will be available in the bill of material UOM drop down inside a formulation specification. When the system is set to not have UOM data explicitly managed, the UOM data that has been added to the raw material will be added to the standard list of UOMs that are present today.
1. On the Summary tab of a raw material, i.e. ING, PKG, PPKG, a new section has been added called Spec Available UOM.
2. The user can select the UOM category appropriate for the material. In the example below we will select Mass.
Figure 1. Select UOM Category
3. Once the UOM Category is established the user selects the UOMs that can be used to describe the material. The Base UOM is used to define the custom UOM in UOM Conversions section.
Figure 2. Select Base UOM
4. The Additional UOMs field allows the user to select additional UOMs that are valid for the material. These represent UOMs that do not need additional conversions defined, i.e. if the base is “LB” then the system can automatically calculate “KG”.
Figure 3. Additional UOM
selection
Figure 4. Additional UOM presentation
5.
Custom UOMs are described in the UOM Conversions
section. In this example a UOM called “10BG” represents 10 lbs.
Figure 5. UOM Conversions section
6. In addition custom UOMs can be presented referencing equivalent numbers.
Figure 6. Custom UOM
Custom UOMs are managed in ADMN/Global/UOM. Each entry is added to the “Other” category and is presented to specifications based on status.
Figure 7. Custom UOMs managed in ADMN
Once custom UOMs are defined on a given raw material they will be available for use when populating a formulation or trade specification. In the examples below we present the ingredient we created above being connected to a formulation specification with both.
Example #1: Ingredient being attached to a formulation specification with explicit UOMs configured on. Note, in this example only the UOMs identified on the ingredient are available.
Figure 8. Explicit UOMs configured on
Configuration Example:
<add key="GSM.AvailableUOMs.Explicit.Enabled" value="true" configDescription="only use the UOMs defined AvailableUOMs only for consumption"/>
Example #2: The same formulation specification described in example #1 with Explicit UOMs configured off. Note, in this example the custom UOM is added to the standard list of UOMs.
Figure 9. Explicit UOMs configured off
Configuration Example:
<add key="GSM.AvailableUOMs.Explicit.Enabled" value="false" configDescription="only use the UOMs defined AvailableUOMs only for consumption"/>
|
|
Available Unit of
Measure Management Oracle Corporation Worldwide Inquiries: 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. |