Skip to content

KUMAVISION trade#

25.1.2601.0 - 2024-11-26#

Hotfix

  • Error executing Batch Job 5157136 KVSTRDReduceSingleShptOrderQty (#12683, TRD-658)
    In the reduction of quantities for Sales Orders marked as 'Single Shipment per Order', an error occurred during the validation of quantities in the Item Charge Assignments of the Alloy Surcharge line. This error has been resolved with this ticket.
  • Sales Return Order for Partial Quantities generates Duplicate Alloy Surcharge Line (#12714, TRD-661)
    The field KVSTRDAlloySurchAttachToLineNo is now correctly transferred to the Return Order or Credit Memo lines from the posted document line. As a result, duplicate alloy surcharge lines will no longer be created during quantity validation. Additionally, the document type 'Return Order' has been removed from the update routine for rebuilding alloy surcharge lines. This ensures that the price is not recalculated but remains unchanged.
  • Creating Sales or Purchase Order from Blanket Order for two Items with Alloy Surcharge (#12715, TRD-660)
    Currently, an error occurs when creating an order from a blanket sales order or a purchase order from a blanket purchase order if more than one item with alloy surcharges exists. With the implementation of this ticket, this error will be resolved.
  • Sales Orders can't be released if "Check Pos. Nos. on Sales Lines" in Sales Setup is set to "Check" (#12765, TRD-631)
    Sales & Receivables Setup: If the 'Check Pos. Nos. on Sales Lines' field is set to 'Check,' the system should verify whether the 'Enable Minimum Order Value' field is set to 'Yes.' If this is the case, a notification will be displayed to inform the user that this combination is not recommended. The reason is that the minimum order value is only calculated upon release of a sales order, which prevents the manual assignment of a position number before release.

Change

  • Special Order and Drop Shipment: Description in Purch. Order Line must match to Vendor Language Code (#12646, TRD-649)
    When a Drop Shipment or Special Order is created from a Sales Order, the description from the sales line is carried over to the purchase line if no appropriate translation exists for the item or item variant based on the vendors language code. However, the system should use the predefined description of the item or item variant, as the description in the sales line may already have been translated according to the customers language code. As a result of this ticket's implementation, the description for drop shipments or special orders will now consistently be sourced from the item or item variant whenever no language code is specified for the purchase, but a language code is present in the Sales Order
  • Implement "Post and Send" for Periodic Invoicing (#12696, TRD-659)
    The "Post and Send" functionality has been introduced for Periodic Invoicing. A new field, "Send Email", has been added to the "Periodic Invoicing Setup" and the "Periodic Invoicing" report. In the report, this field is pre-populated by default with the value defined in the setup. If "Send Email" is set to ‘Yes,’ the system will trigger email dispatch at the end of the Periodic Invoicing process. This is done based on the Document Sending Profile configured for the customer on the General tab of the customer card. This enhancement aligns the periodic invoicing process with the existing functionality for manually posting and sending invoices.
  • Check in Table Item-User-Location due to unfavorable primary key (#12754, TRD-657)
    A check has been added to the table’s records to identify entries with identical item numbers and no assigned user. Additionally, all checks are now executed not only when inserting a record but also when modifying a record.
  • Alloy Surcharge: Implement support for partial deliveries in Purchases (#12804, TRD-639)
    Enhance the purchase process to support partial deliveries for alloy surcharges. This implementation requires the 'Auto Post Non-Invt. via Whse.' field in the purchase setup to be set to 'None' for the adjustments to take effect. Additionally, a notification will now be displayed if the 'Auto Post Non-Invt. via Whse.' field is set to 'Attached/Assigned,' advising that this configuration should not be used in conjunction with alloy surcharges. As part of this enhancement, it is now possible to adjust the quantity of Sales & Purchase alloy surcharge lines after a partial delivery or shipment has been posted. Furthermore, if a price for the alloy surcharge line already exists, no additional pricing calculation will be triggered, ensuring consistency in pricing. Lastly, during the validation of quantities, alloy surcharge lines are no longer removed and recreated. This prevents the unintended resetting of the "Quantity Shipped"/"Quantity Received" and "Quantity Invoiced" fields, which could occur in such scenarios. Furthermore, if the "Auto Post Non-Invt. via Whse." field is set to "Attached/Assigned", the logic for synchronizing partial quantities is not executed. However, during posting, the system still verifies whether the quantities between item lines and alloy surcharge lines are identical. If discrepancies are detected, an error message is displayed. This behavior has now been adjusted so that the quantity verification will only be performed if the "Auto Post Non-Invt. via Whse." field is not set to "Attached/Assigned". This adjustment has been implemented for both the purchase and sales processes.

25.1.2560.0 - 2024-11-11#

Hotfix

  • Outgoing Check for Inventory Multiple should only be performed for Sales (#12611, TRD-646)
    It is now checked whether the origin of the Warehouse Shipment Line is "Sales Order." If this is the case, the logic surrounding the "Inventory Multiple" field is executed. Additionally, the event "KVSTRDOnBeforeIsValidWarehouseShipmentLineSourceDocument" has been provided, allowing for the override of this new check. The option value "Outbound" in the "Inventory Multiple Check" field within "Inventory Setup" has been renamed to "Sales Outbound." The validation and functionality related to rounding up or down the quantity concerning the "Inventory Multiple" field are now also available for Sales Invoices.

Change

  • Page "Variant Quick Entry" shows blocked variants (Purchase, Sales, Transfer) (#12489, TRD-636)
    The "Variant Quick Entry" page currently displays variants that are marked as blocked (e.g. for Purchase, Sales, or Transfer), leading to errors when attempting to process these variants. To resolve this, the "Variant Quick Entry" page will be updated to filter out variants where the "Blocked" field is set to 'Yes', ensuring that only unblocked variants are shown and processed correctly.
  • Event Request: Implement event in "CalculateSurchargePrice" in codeunit KVSTRDAlloySurchargeMgt (#12644, TRD-650)
    Added event: KVSTRDOnAfterGetStartingAndEndingDateForSurchargePrice(var SourceType: Integer; var SourceNo: Code[20]; var ItemNo: Code[20]; var VariantCode: Code[10]; var QtyPerUnitOfMeasure: Decimal; var AlloySurchargeCode: Code[20]; var ValuationDate: Date; var CurrencyCode: Code[10]; var CurrencyFactor: Decimal; var PriceStartingDate: Date; var PriceEndingDate: Date)
  • Event Request: Implement event in "CopyDemandPlanningLinesToDemandForecast" in codeunit KVSTRDDemand (#12645, TRD-651)
    Added event: KVSTRDOnBeforeInsertProductionForecastEntry(var ProductionForecastEntry: Record "Production Forecast Entry"; var DemandPlanningLine: Record KVSTRDDemandPlanningLine)
  • Extensibility Request: Make codeunit "KVSTRD Item Replacement Mgt." and several procedures external available (#12706, TRD-662)

25.1.2546.0 - 2024-11-07#

Change

  • Use "DataTransfer" for upgrade routines (#12632, TRD-648)

25.1.2537.0 - 2024-11-05#

Change

  • Use "DataTransfer" for upgrade routines (#12632, TRD-648)

25.0.2501.0 - 2024-10-24#

Hotfix

  • Item Life Cycle: Wrong error thrown at posting of pick document (#12472, TRD-635)
    When posting a pick document all lines will be checked against their related Item Life Cycle, also including lines which are not getting shipped or invoiced. The check against the Item Life Cycle should only be done against lines which are getting shipped or invoiced, all other lines should be excluded from the check as they are not involved in the posting routine.

Change

  • Alloy Surcharge: Implement support for partial shipments in Sales (#12295, TRD-575)
    Enhance the sales process to support partial shipments for alloy surcharges. This implementation requires the 'Auto Post Non-Invt. via Whse.' field in the sales setup to be set to 'None' for the adjustments to take effect. Additionally, a notification will now be displayed if the 'Auto Post Non-Invt. via Whse.' field is set to 'Attached/Assigned,' advising that this configuration should not be used in conjunction with alloy surcharges.

25.0.2471.0 - 2024-10-16#

Hotfix

  • Wrong check on "Purchase Blocked" for Item with Replenishment System = 'Prod. Order' (#12303, TRD-620)
  • Position numbering executed irrespective from Setup (#12358, TRD-623)
    When releasing a sales order, position numbering is executed even if automatic position numbering is disabled in the Sales & Receivables Setup (field: Check Pos. Nos. on Sales Lines). This occurs whenever freight costs or a minimum order value surcharge are added, causing all lines to be renumbered. The expected behavior is that position numbers should only be assigned if the setting for automatic position numbering is enabled in the Sales & Receivables Setup.
  • Enter Items to Service Item Worksheet in service quotes (#12382, TRD-626)
    When adding items to the Service Item Worksheet in service quotes, an error message appears stating that this action is only permitted for documents of type "Order." This error occurs when the "Copy Item Purchasing Code" option is enabled in the Service Setup. However, it is necessary to be able to enter items in service quotes for estimation purposes. With this update, the "Purchase Code" field will no longer be automatically populated in the service line of a service quote based on the corresponding setting in the Service Setup. Instead, it will only be set during order creation. As the validation of the purchase code determines the fields “Direct Shipment” or “Special Order,” these fields will also only be populated on the order side.
  • Rename from Demand Planning Calc. Schedule Header not possible (#12430, TRD-633)
    When changing the code of the Demand Planning Calc. Schedule a confirmation dialog appears two times which leads eventually to an error after confirming the dialogs. To prevent this issue renaming of the record should not be allowed anymore.

Change

    • Necessary Changes + Migrations in Service Archive / Simplified Planning and Multiple VAT per (#11850, TRD-588)
  • Implement functionality for transferring Alloy Surcharge Code to return order, archive and posted do (#12268, TRD-614)
    Implementation of functionality to transfer the Alloy Surcharge Code into posted documents (credit memo, invoice, shipment) as well as archive and reclamation documents. This enables traceability of alloy surcharges in later evaluations. Adjustments affect the following tables: Sales Line Archive (5108), Sales Shipment Line (111), Sales Credit Memo Line (115), Return Receipt Line (6661), and Sales Invoice Line (1113), including the field 'KVSTRDAlloySurchAttachToLineNo'. Additonally the field "KVSTRDAlloySurchAttachToLineNo" will automatically set to zero in Sales Lines of Return Orders and Credit Memos which are retrieved from posted shipments or invoices to prevent further conflicts with the alloy surcharge logic.
  • Extensibility request: Add event in AlloySurchargeMgt (#12281, TRD-618)
    Added event: KVSTRDOnGetStartingAndEndingDateForSurchargePriceForOtherAlloySurchargeCalcType(AlloySurchargeCalcType: Enum KVSTRDAlloySurchargeCalcType; ValuationDate: Date; var StartingDate: Date; var EndingDate: Date)
  • Toggling visibilities of calendar week fields: Set "SaveRecord" to false in CurrPage.Update (#12320, TRD-621)
    When determining the visibility of calendar week fields in document lines, a CurrPage.Update is executed with the parameter SaveRecord set to 'true' (default), which can potentially cause issues in customer applications. Since no record modifications are needed, the parameter should be passed as 'false' to prevent unintended changes. Therefore the code has been updated from: "CurrPage.Update()" to "CurrPage.Update(false)".