|"CKL Software GmbH"
|"Bewertung 365 / Valuation 365"
Partners and customers of CKL Software GmbH often need access to the source code of our applications for enhancement, testing, integration or problem solving purposes. To access the source code, follow these steps:
- Log in to the Partner Portal of CKL Software GmbH.
- Navigate to Products > CKL Apps and download the appropriate product package.
- Unzip the zip file and navigate to app > src in the product package folder.
You can customize the functionality of Valuation 365 by using some of the many different Event Publishers. CKL Software GmbH is constantly providing Event Publishers to make our apps as customizable as possible.
If you need additional events for your customization in Valuation 365 you can request them at firstname.lastname@example.org. Please submit the event request to us in the following form (example event request):
I need a new event in table “Service Contract Header” at “OnValidateTrigger” of field “Expiration Date”:
field(36; "Expiration Date"; Date)
Caption = 'Expiration Date';
IsHandled := false;
if IsHandled then
local procedure OnBeforeValidateExpirationDate(var ServiceContractHeader: Record "Service Contract Header"; var IsHandled: Boolean)
CREATION AND EXTENSIBILITY OF VALUATION CONDITIONS
Valuation 365 provides a set of predefined valuation conditions. If you have special valuation requirements that are not covered by the valuation conditions available in the product, you can easily create new valuation conditions. For this purpose, we provide you with an extension app. You can use this as the basis for creating an individual valuation rule.
It is important to verify that your environment is compatible with the hotfixes or updates being installed.
|CKL App Version
|Compatible BC Version
|Upgrade to Microsoft Dynamics 365 Business Central The module Valuation 365 was taken over with the set from Microsoft Dynamics 365 Business Central BC14 (Cumulative Update 09) C/AL-Code on Microsoft Dynamics 365 Business Central AL-Code.
|Consideration of freight costs in currency valuation rule For the valuation of item ledger entries according to the currency valuation rule, the associated freight costs were not taken into account up to now.
|Consideration of historical data in valuation rule leaving In the leaving valuation rule, the last output was not correctly deter-mined using the Item Historical Data table.
|Exception level in Leaving-Period valuation condition An exception level (code = 0) can be defined in the Leaving-Period valuation condition. This exception applies if no movements could be determined in the period under review. However, this level was always applied even if there were movements.
|Incorrect posting of valuation for individual value adjustment If no valuation condition is applicable for an item to be valuated, an item valuation plan entry is created with valuation type specific. If this line is now manually adjusted by individual value adjustment, the sys-tem creates a second line with valuation type specific. Both lines are marked as "valid". As a result, the values are not posted correctly.
|Various usability improvements The module has been made more user-friendly in several places. For example, the input of filters within the valuation conditions has been improved or the user is supported when creating a date formula.
|Details of incoming item ledger entries in item valuation plan entries Within the item valuation plan entries, further information regarding incoming item ledger entries was provided. Often it was not directly obvious why a certain valuation rule level was not applied (e.g. be-cause of an incoming item leger entry). The factbox now shows whether an incoming item was found.
|Upward compatibility for BC19 provided In order for the app to be compatible with BC19, various technical functionalities had to be adapted.
|Added some ToolTip The ToolTip property has been added to some Valuation 365 fields.
|Restructuring of the permission sets for Valuation 365 The Valuation 365 permission sets have been restructured and combined into one superordinate permission set "BEWERTUN 365 / VALUATION 365". Please remove the permission sets "VAL-JOURNAL, VAL-JOURNAL POST, VAL-SETUP, VAL-SUPER, VAL-VALUATION, VAL-VALUATIONTOGL" from the user and replace them with the permission set "BEWERTUNG 365 / VALUATION 365".
|Integration CKL Online Help in Valuation 365 App Links to the CKL Online Help have been added within the Valuation 365 app.
|Set Line as valid Value via Item Valuation Analysis Report An item valuation plan entry can now also be set directly as a valid value via the Item Valuation Analysis Reports. For this purpose, the editing of item valuation plan entries from the analysis view has been enabled.
|Posting (with impact to unit cost) of items with costing method average Previously, it was possible to post items with costing method average as revaluation (with impact to unit cost) via the Item Valuation Journal. This is now blocked. Items with costing method average should always be valued as a whole on item level and not individually on item ledger entry level. In Valuation 365, each individual item ledger entry is valued with a positive remaining quantity. Therefore, the standard Item Revaluation Journal must be used for items with the costing method average.
|Incorrect translation of various captions Translation into german was adjusted for several captions.
|Extension of the role accountant with valuation 365 activities The Accountant role has been extended. The basic valuation process of Valuation 365 has been presented. This is intended to improve the operation of Valuation 365.
|Creation and extensibility of Valuation Conditions Valuation 365 provides a set of predefined valuation conditions. If you have special valuation requirements that are not covered by the valuation conditions available in the product, you can easily create new valuation conditions. For this purpose, we provide you with an extension app. You can use this as the basis for creating an individual valuation rule.
|Upward compatibility for BC22 provided In order for the app to be compatible with BC22, various technical functionalities had to be adapted.
|Permissions for "Set Balance Posting Date" function Additional permissions have been granted to perform the "Set Balance Posting Date" function on the item valuation journal.
|ToolTips in Item Valuation Setup swapped In the Item Valuation Setup, the two ToolTips "Allow Posting of blocked items" and "Automatic Cost Posting" were interchanged.
|Conversion of some option fields to Enum For the extensibility of Valuation 365 some option fields have been changed to Enum.
|Error message "The record is already open" at Calculate Inventory Value If several levels of the type "Field Item Table" were defined within the valuation condition Lowest Value, the above mentioned error message appeared at Calculate Inventory Value.
|Upward compatibility for BC23 provided In order for the app to be compatible with BC23, various technical functionalities had to be adapted.
|Personal support available at www.ckl-software.de/en/