Understanding EUR Product Specifications

EUR product specifications represent a group of target attributes that you define for a blend lot at a specific wine status. The purpose of setting up EUR product specifications is to provide the ability to define target values for various lot attributes that you want the blend lot that is associated with the EUR to achieve as it moves through the blend process. Having defined the target value for a specification, you can perform a validation on the blend lot that compares the defined target value with the actual value of the lot attribute that is returned by a named calculation. When you validate specifications, the system evaluates whether the value that is returned by the named calculation conforms to the specification according to the specified rule.

The following table lists the lot attributes for which you can set up specifications and the tables from which the named calculations return values:

Attribute	Table
Material type Instructed attributes	Blend Lot Master (F31B31)
Composition	Lot Composition (F31B311)
Quality test	Test Results (F3711)
Ownership	Lot Owners (F31B315)
Style	Lot Style (F31B314)
EUR	Lot EUR (F31B316)
Accumulated additives	Lot Accumulated Additives (F31B318)
Cost	Blend Lot Costs (F31B31C)

To define EUR product specifications, you first set up generic specifications with the following information:

• Named calculation

• Target value

• Rule type

• Validation type

Each specification can encompass more than one named calculation. You enter a named calculation to obtain an actual value for comparison with the target value that you specify. You can select only named calculations that were previously defined using the Named Calculations program (P31B109).Depending on the data type of the value that is returned by the named calculation, which can be a numeric, string, character, or date value, only the corresponding target value field is available for data entry. For example, if the return value of the named calculation is a string value, you can enter a target value only in the Target String field.

The specification compares the target value that you enter with the value that is returned by the named calculation return value based on a set of rules that define possible relationships between return and target values The following table lists the available rules and their application to the different data types:

Rule	Character	String	Date	Numeric
Equal to	Valid	Valid	Valid	Valid
Not equal to	Valid	Valid	Valid	Valid
Greater than	NA	NA	Valid	Valid
Greater than or equal to	NA	NA	Valid	Valid
Less than	NA	NA	Valid	Valid
Less than or equal to	NA	NA	Valid	Valid

These hard-coded rules are stored in the Named Calculation Rule UDC table (31B/RR). The special handling codes determine what the valid rules are. Rules with a special handling code of 1 apply only to specifications with named calculations that return strings. Rules with a special handling code of 1 or 2 apply to specifications with named calculations that return numeric values. Rules without special handling codes do not apply to specifications.

After you specify the target value, named calculation, and rule, you must determine what kind of validation you want the system to perform against the specification. You can set up the specification so that the system issues an error message if the validation shows the return value to be out of specification.

Quality results are stored as strings, but you can set up a numeric comparison rule for quality results that you have defined as numeric. When the system validates the specification, the system uses a numeric rule to determine the extent to which the quality results conform to the specification. As an example, the following table establishes the range from 5.0 to 5.5 as an acceptable pH value range. The third specification points to the ideal value of 5.3. Thus, the returned value falls into the acceptable range, but falls short of the ideal target value.

Returned Value	Rule	Target Value	Result
5.2	Less than	5.5	In specification
5.2	Greater than	5.0	In specification
5.2	Equal to	5.3	Out of specification

The named calculations that are based on the F31B31 table support validations of instructed attributes, as well as survey gain or loss, and operational gain or loss, and yield.

After you have created a generic specification, it is available to be attached to an EUR definition. You can attach specifications to different combinations of EURs and wine statuses.