Setup
(EWI) Wine Setup
Functional Purpose: Centralized setup page for the entire Wine Base features. It enables users to define setup parameters, number series, routing, and batches required for the posting of wine treatment journals.
Main Fields:
| Field | Description |
|---|---|
| Wine App Enabled | Primary field used to enable or disable the entire app. This field must be enabled for all Wine Base functionalities to operate correctly. |
| Quantity Conversion Rounding Precision | Defines the quantity rounding precision used during conversions from the base unit of measure to liters/kg. Example: 1 = round to a whole number, 0.01 = round to 2 decimal places, 0.001 = round to 3 decimal places. |
| Wine Treatment Routing No. | Standard certified routing used as the template for all wine treatments. The routing must have the Certified status and contains the standard operations and routing steps required for processing. This field is mandatory to execute wine treatment operations. |
| Prod. Cost Work Center No. | Identifies the Work Center used to track and record production costs for treatment processes as additional operations. Required for posting. |
| Output Jnl. Template Name | Specifies the template used for posting the Output entries of items produced through treatment processes. Required. |
| Output Jnl. Batch Name | Specifies the batch used for posting the Output entries of items produced through treatment processes. Required. |
| Consumption Jnl. Template Name | Specifies the template used for posting the Consumption entries of items consumed by treatment processes. Required. |
| Consumption Jnl. Batch Name | Specifies the batch used for posting the Consumption entries of items consumed by treatment processes. Required. |
| Wine Treatment No. Series | Specifies the No. Series used to automatically generate Wine Treatment records. Required. |
Reason Code
Filling in the Reason Code field is very important for the Wine Suite applications. The standard Reason Codes table is extended by the EOS WINE app (EX080) with operational parameters for wine treatments, and by the EOS WINE SIAN app (EX083) with parameters used for ICQRF/SIAN electronic traceability.
1. Fields added by the EOS WINE (EX080)
| Field | Type | Functional use |
|—|—|
| Wine Treatment | Enables the reason code to be used in Wine Treatments. It acts as a filter: when creating and linking a treatment, only reason codes with this flag enabled can be selected. It is also the condition that makes the other Wine fields visible on the Reason Codes page. |
| Wine Treatment Multi Output | ndicates that the wine treatment generates multiple output products from the same source batch. When enabled, the treatment is created as a “Family” type order with a multi-output page. When disabled, a single-output treatment is created. |
| Wine Treatment No. Series | Specific number series assigned to wine treatments created using this reason code. It overrides the default number series defined in the Wine Setup. |
| Wine Treatment Routing No. | Production routing (certified routings only) proposed for treatments created with this reason code. It overrides the default routing defined in the Wine Setup. |
Operational use: Selecting the reason code in the New Wine Treatment page causes the system to automatically populate the number series and production routing, and determines whether to open the standard treatment page or the multi-output page.
2. Fields added by EOS WINE SIAN (EX083)
| Field | Functional Use |
|---|---|
| SIAN Operation Type Load | SIAN operation type (e.g., ARMC, IMBO, TAGL, SVIN, etc.) associated with load (positive) movements. When a positive movement is posted, it determines the operation used to update the SIAN register. |
| SIAN Operation Type Unload | Similar to the above, but for unload (negative) movements. It is also used as a filter in the operation product number lookups on treatment outputs/components. |
| SIAN Expiration Date Load | Expiration formula applied to the load operation. It calculates the expiration date of the SIAN register entry based on the posting date. |
| SIAN Expiration Date Unload | DateFormula. Same as above, but for the unload operation. |
| SIAN Enological Practice | Default enological practice (SIAN “Enological Practices” table). For receipt treatments/outputs (other than IMBO), it is propagated to the produced lot together with the practices inherited from the components, unless automation is disabled in the SIAN Setup. |
| Exemption Derogation | Exemption derogation code (SIAN “Derogation Obligation” table) reported in the SIAN register operation generated by the movement. |
| SIAN Skip Category Check | If enabled, skips the validation of allowed categories for the operation during transmission to the SIAN web service. |
| SIAN Expiration Date | Generic expiration field available on the Reason Codes page. In the current logic, the actual expiration date is managed by the dedicated Load/Unload expiration fields; therefore, this field acts as a residual/reference parameter. |
Convention Note (SIAN): the category check looks for a reason code whose code matches the operation name (e.g., reason code “IMBO”). On that reason code, the “SIAN Category Check” flag disables the validation. It is considered best practice to align reason code codes with the corresponding managed SIAN operation codes.
The SIAN Operation Type Load and the SIAN Operation Type Unload are identical for all wine treatment reason codes and for the bottling reason code (IMBO). The exceptions are the CASD (Purchase) and USSD (Sale) reason codes, where CASD must be set as the SIAN Operation Type Load and USSD as the SIAN Operation Type Unload (on both reason codes).
3. Setup Guidelines
- Enable “Wine App Enabled” in the Wine Setup to make the Wine/SIAN fields available and operational on reason codes.
- For each type of wine treatment, create a reason code with “Wine Treatment” = Yes and configure, where required, the number series, production routing, and multi-output flag.
- For SIAN traceability, configure at least the operation types (Receipt/Shipment) and, where applicable, the enological practice, exemption/derogation code, and expiration formulas.
- Pre-populate the SIAN “Enological Practices” and “Derogation Obligation” tables.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.