Development
| AppInfo | Detail |
|---|---|
| "AppId" | "4be2e50d-be5e-48cc-9a33-650bdc76d0f1" |
| "Publisher" | "CKL Software GmbH" |
| "Name" | "Bewertung 365 / Valuation 365" |
SOURCE CODE
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.
EVENTS
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 support@ckl-software.de. 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';
trigger OnValidate()
var
IsHandled: Boolean;
begin
IsHandled := false;
OnBeforeValidateExpirationDate(Rec, IsHandled);
if IsHandled then
exit;
end;
}
New Event:
[IntegrationEvent(false, false)]
local procedure OnBeforeValidateExpirationDate(var ServiceContractHeader: Record "Service Contract Header"; var IsHandled: Boolean)
begin
end;
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.
CHANGELOG
It is important to verify that your environment is compatible with the hotfixes or updates being installed.
| CKL App Version | Compatible BC Version | Description |
|---|---|---|
| 11.0.0.0 | From BC24.0 | Upward compatibility for BC27 provided In order for the app to be compatible with BC27, various technical functionalities had to be adapted. |
| 8.0.11.0 | From BC21.0 | Extension of the Valuation Condition Setup Wizard to include the Range Procedure, Leaving Procedure, Lowest Value Principle, Range Procedure by periods and Leaving Procedure by periods Extension of the Valuation Condition Setup Wizard to include the Range Procedure, Leaving Procedure, Lowest Value Principle, Range Procedure by periods and Leaving Procedure by periods. |
| 8.0.10.0 | From BC21.0 | Provision of API pages The following API pages were provided in Valuation 365: Page 5447640 Item Valuation Entry, Page 5447641 Item Valuation Plan Entry, Page 5447642 Valuation General Posting Setup, Page 5447643 Valuation Inventory Posting Setup. |
| 8.0.9.0 | From BC21.0 | Provision of additional event publishers for valuation condition range Additional event publishers have been made available in codeunit 5447562. |
| 8.0.8.0 | From BC21.0 | Item Ledger Entry Type Filter for lowest value type “Average cost price” Various levels/types can be created within the “Lowest value” valuation rule. For the lowest value type “Average Cost”, the defined item ledger entry type filter was not taken into account in the calculation. |
| 8.0.7.0 | From BC21.0 | Valuation Condition Simulation added A valuation condition simulation has been added within the valuation conditions. This allows the valuation of a specific item to be simulated in advance using a valuation condition. In addition, the values determined in the standard report “Inventory Valuation” are displayed for comparison purposes. |
| 8.0.6.0 | From BC21.0 | Provision of additional event publishers for valuation condition currency Additional event publishers have been made available in codeunit 5447562. |
| 8.0.5.0 | From BC21.0 | Valuation Condition Setup Wizard The Valuation Condition Setup Wizard can be used to define basic setup parameters for a valuation condition. The setup fields of the valuation condition are described in more detail and can be defined step by step. In addition, a valuation level and item valuation condition can be defined. The valuation condition can then be individually changed and expanded. |
| 8.0.4.0 | From BC21.0 | Provision of additional event publishers for the transfer of item valuation entries to financial accounting Additional event publishers have been made available in codeunit 5447602. |
| 8.0.3.0 | From BC21.0 | Post only Valid Value The new field “Post only Valid Value” in the item valuation setup allows only valid item valuation plan entries to be posted. This switch should only be set if there are performance problems due to the large number of entries to be processed within Valuation 365. The posting process is changed so that only item valuation plan entries that are defined as “valid value” are posted. This limits the traceability of past valuations but can speed up the posting process in Valuation 365. |
| 8.0.3.0 | From BC21.0 | Set Unit Cost (Specific) per Item In the Item Valuation Journal, it is now possible to set a unit cost (specific) for the entire item in the journal. This means that a specific unit cost can be defined quickly and easily for certain items across several journal rows. |
| 8.0.3.0 | From BC21.0 | Item Filter in Item Valuation Conditions In the item valuation conditions, you can determine which items should be taken into account for the valuation. Previously, a specific item could be defined, or all items could be taken into account. With the new item filter option, several items and item ranges can now be entered. |
| 8.0.2.0 | From BC21.0 | Additional field "Valuation 365 Cost Calc. Type" in the Item Valuation Setup With the additional field "Valuation 365 Cost Calc. Type" in the Item Valuation Setup, you can define how the valuations for item ledger entries are to be calculated. Initially, the calculation is carried out according to the settings in the field "Average Cost Calc. Type" in the Inventory Setup. If this field is to be overridden, an option can be selected in the field "Valuation 365 Cost Calc. Type”. |
| 8.0.1.0 | From BC21.0 | Location filter in item valuation conditions The location filter option can be selected within the item valuation conditions. This allows you to define whether the valuation rule should only be applied to certain locations. In certain constellations, the location filter was not taken into account during the valuation run. |
| 8.0.0.0 | From BC21.0 | Upward compatibility for BC23 provided In order for the app to be compatible with BC23, various technical functionalities had to be adapted. |
| 6.0.4.0 | From BC19.0 | 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. |
| 6.0.3.0 | From BC19.0 | Conversion of some option fields to Enum For the extensibility of Valuation 365 some option fields have been changed to Enum. |
| 6.0.2.0 | From BC19.0 | 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. |
| 6.0.1.0 | From BC19.0 | 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. |
| 6.0.0.0 | From BC19.0 | Upward compatibility for BC22 provided In order for the app to be compatible with BC22, various technical functionalities had to be adapted. |
| 2.0.13.0 | From BC15.0 | 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. |
| 2.0.12.0 | From BC15.0 | 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. |
| 2.0.11.0 | From BC15.0 | Incorrect translation of various captions Translation into german was adjusted for several captions. |
| 2.0.10.0 | From BC15.0 | 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. |
| 2.0.9.0 | From BC15.0 | 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. |
| 2.0.9.0 | From BC15.0 | Integration CKL Online Help in Valuation 365 App Links to the CKL Online Help have been added within the Valuation 365 app. |
| 2.0.8.0 | From BC15.0 | 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". |
| 2.0.8.0 | From BC15.0 | Added some ToolTip The ToolTip property has been added to some Valuation 365 fields. |
| 2.0.7.0 | From BC15.0 | Upward compatibility for BC19 provided In order for the app to be compatible with BC19, various technical functionalities had to be adapted. |
| 2.0.6.0 | From BC15.0 | 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. |
| 2.0.5.0 | From BC15.0 | 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. |
| 2.0.4.0 | From BC15.0 | 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. |
| 2.0.4.0 | From BC15.0 | 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. |
| 2.0.3.0 | From BC15.0 | 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. |
| 2.0.2.0 | From BC15.0 | 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. |
| 2.0.1.0 | From BC15.0 | 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. |
|
|---|
| Personal support available at www.ckl-software.de/en/ |