KUMAVISION project

See also the following ChangeLogs

• KUMAVISION Core v26
• KUMAVISION base v26

26.2.3939.0 - 2025-07-03

Hotfix

• Bill-to customer of the sale-to Customer is not transfered into WBS-line (#14637, PSA-3209)
  Selecting a customer in a wbs-line doesn't fill the Bill-to customer on the wbs-line correct if this customer has a different bill-to customer.
• Field "distribution level" on the wbs-line is not updated correctly by changing the work package (#14641, PSA-3203)
  Rolling Planning - Change the work package on a wbs-line. The distribution level is now updated on the wbs-line by the new work package.
• Change work package in project ledger - missing resource unit error (#14642, PSA-3246)
  Some unit-problems in the "project ledger entry"-function "change work-package" have been solved.
• No automatic population of the project item consumption fields if budget lines are entered manually on sales order (#14662, PSA-3255)
  Process: Post project item consumption by a sales document - in some cases the necessary fields to this process are not filled.
• Project splitting lines - not for purchase receipt lines in invoices (#14700, PSA-3272)
  The functionality of splitting 1 purchase line into several project ledger entries by the "project splitt table" can not be used for a purchase receipt line which has been transfered into a purchase invoice. Because the project posting has been done by posting the receipt not by the invoice.
• Restore sales line texts by "restore the sales line" function (#14702, PSA-3275)
  Some improvements to the recreation of sales lines regarding the sales line texts.
• Filter in project ledger entry function "change budget line" (#14703, PSA-3269)
  The "Change Budget Line" function in the Project Ledger Entry (resources only) previously filtered the target budget line selection by Resource Type. We have now extended this filter to also include Resource Groups.
• Purchase splitting lines are not allowed in combination with purchase invoice entry (#14705, PSA-3270)
  The functionality of splitting 1 purchase line into several project ledger entries by the "project splitt table" can not be used for a purchase line with purchase invoice ledger entries. Because with purchase invoice ledger entries there is nothing to post for a project only some correction maybe.
• no resource receipt posting because of 0 division error caused by NON-Deductible VAT (#14739, PSA-3291)
  We need to adapt our extension for Non-Deductible VAT to align with recent changes introduced by Microsoft.
• Purchase Line with project splitting lines - check on wbs-line connection on purchase line (#14742, PSA-3261)
  Additional check in purchase project splitting lines: the project splitting must use a target wbs-line with the same work type used on the purchase line. Reasons are the units and the prices, they are used directly from the purchase line.
• Change start date on wbs-line to 0D (= no date) - this must not update the project (#14747, PSA-3285)
  When the starting date of a WBS line is changed, the project’s starting date can be automatically updated accordingly. However, this update will not occur if the starting date on the WBS line is removed (i.e., left blank).
• wbs-function "update payment plan" is not active (#14771, PSA-3305)
  In some cases the wbs-function "update payment plan" was not active.
• Technical Error by activating a wbs-version (#14772, PSA-3301)
  Technical Development Improvement
• delete project splitting entries by deleting the purchase line (#14800, PSA-3309)
  Deleting a purchase line must delete the purchase project splitting too.
• Delete purchase project splitt line after posting the receipt (#14804, PSA-3311)
  When posting a partial receipt on a purchase order, the associated project splitting must be removed. This ensures that a new project splitting can be defined for the next receipt posting, based on the updated quantities.
• Deactivate field "to do progress WBS" field (#14872, PSA-3201)
  On the wbs-line the field "to do progress WBS" will not be supported anymore. The calculation is deactivated, the field will be removed in some versions.
• project intercompany transfer - Dimension Integration of project setup is missing (#14885, PSA-3335)

Change

• change the numbering of the wbs-version number (#14277, PSA-3122)
  The WBS version number starts by default with 001. However, in the project setup, a new field allows you to define a different starting number—such as 0001—to provide greater flexibility. Defining a custom starting number is optional; if none is specified, the system will automatically begin with 001.
• Get Receiptline with different Non-Deductible VAT % (#14513, PSA-2265)
  A purchase order line includes multiple part receipts recorded on different dates. During this period, the non-deductible VAT percentage changed, resulting in varying VAT rates applied to each receipt. This variation must be accurately reflected during the invoicing process to ensure compliance and correct financial reporting.
• Connect sales opportunity to the project created by the sales document (#14576, PSA-3155)
  Each sales opportunity is associated with a sales quote. When a new project is initiated based on this quote or the corresponding sales order, it is likewise linked to the original opportunity.
• Calculation of the completion fields on project budget line (#14577, PSA-3191)
  The progress fields on the project budget line are now updated based on time ledger entries only if progress has been recorded in the time registration. If no progress is specified during time entry, the progress fields will remain unchanged.
• Add Call for Gantt Viewer on Job List and Job Scheduling (#14682, PSA-3257)
  grafical project gantt viewer can now be called by job list.
• work status in intercompany wbs-line - check on open IC-review (#14686, PSA-3250)
  A new validation has been introduced when changing the work status of a WBS line to "Open" or "In Progress": If the WBS line was transferred from an intercompany partner, the intercompany review must be completed first.
• CTC - Tooltips (#14695, PSA-3211)
  For more usability: Tooltipps on CTC Card are available now.
• time journal line - Tooltips (#14696, PSA-3220)
  For more usability: Tooltipps on time journal are available now.
• Duration in project template line (#14706, PSA-3215)
  On project template it is possible to define duration and starting offset on the wbs-line-level. If a new wbs is created from the template the start date of a new wbs-line can be calculated by the project start date + starting offset, for example: '+10' = the wbs-line starts 10 working days after the project starting date. The ending date of a new wbs-line can be calculated by the starting date of the wbs-line + the duration (in work days).
• Get Work package for selected G/L Journal lines (#14745, PSA-3226)
  In G/L Journal the function "get work package" is now available for some selected journal lines too.
• Add read permissions on some fields in resource table (#14767, PSA-3302)
  Technical Development Improvements
• Customer and Vendor open entry reports (ID 5025896+ 5025897) should skip project without any open entries. (#14770, PSA-3134)
  For improved usability, the two controlling reports—"Customer Open Entries" and "Vendor Open Entries"—now automatically exclude projects that have no open items.
• Create project shipment in project status quote (check the project setup) (#14779, PSA-3298)
  In project setup it is possible to define the usage posting of projects which are not in status order but in quote. The creating of a project shipment is now using this setup too.
• Insert Phase, Task, Step code fields into page KVSPSACreateJobShipmentFromPSP (5026229) (#14781, PSA-3297)
  The fields phase, task, step code are available now in the function "create project shipment"
• Test on number in purchase line by function call "get work package" (#14782, PSA-3223)
  The function "get work package" on purchase line can only be started if the field "No." on the purchase line is not BLANK.
• New function "project documents" on wbs-line (#14811, PSA-3266)
  A new function has been added to the WBS line that allows users to search for related documents—such as sales, purchase, internal, or service documents—that reference the selected WBS line.
• Internal Codes in time registration to classify the time ledger entries. (#14813, PSA-3268)
  The Internal Code for Time Registration is a new table that can be used in time registration processes—such as the CTC Card or the Project Time Journal—to classify time entries. The values in this table can be defined individually for each company, allowing for customized classifications. For example, it can be used to specify reasons for additional effort. The internal code is stored in the time ledger entries and is also transferred to the project journal.
• create purchase document from wbs: new option to extend existing purchase document (#14833, PSA-3264)
  A new option has been added to the WBS function "Create Purchase Document": "Extend Existing Order". This allows project budget lines to be transferred into an existing purchase quote or purchase order, enhancing flexibility in procurement processes.
• KVSPSAPSPResourcePlanning (5026063, List) in wbs with budget line (#14875, PSA-3321)
  The resource planning function is now available in the page "project incl. budget lines" too.
• Call "Distribution with budget line" from wbs page (#14877, PSA-3322)
  Rolling planning: Function "Distribution with budget line" in wbs-page available.
• Change error message of wbs-line end date check (#14879, PSA-3306)
  More user friendly error message by date changings on wbs-line regarding the budget lines.

26.2.3790.0 - 2025-06-11

Change

• change caption in page KUMAVISION Module setup (#14680, PSA-3252)

26.1.3777.0 - 2025-06-05

Hotfix

• Starting Date / Ending Date not updated in budget lines (#14242, PSA-3112)
  There is no automatic update of the start date / end date in the project budget line if the start date / end date is changed in the wbs-line. But there is a new check on the wbs-line. The start date in the wbs-line can not be changed after the start date of the corresponding budget lines. The end date of the wbs-line can not be changed bevor the end date of the budget lines.
• Error in opening dimensions from Payment Plans (#14361, PSA-3036)
  In some cases the dimension-Setup-ID of project invoice planning line can be 0. This causes an error by opening the dimension page. This has been fixed.
• Transfer new project or wbs-line dimension into payment plan (#14377, PSA-3161)
  New dimensions on project or wbs-line havn't been transfered into project payment plan, only the changing of existing dimensions.
• Assembly BOM in project with invoicing currency causes error (#14380, PSA-3080)
  Expanding an assembly BOM into a wbs-line (as budget lines) causes an error if the project has an invoicing currency.
• Auto budget line connection - don't use closed budget lines (#14445, PSA-3181)
  with the "auto budget line connection" (setting on the proejct setup) the usage posting on wbs-line level is automatically connected to a project budget line (of that wbs-line) if there is a suitable budget line is existing. This automatic must not use closed budget lines only the open one.
• project ledger entry transfer suggestion - Work type of the wbs-line has to be used (not from the work package) (#14451, PSA-3178)
  Function "project ledger entry transfer suggestion": In the second project journal line the work type of the selected target wbs-line has to be used (and not the one of the work package
• Main project dimension is not deleted from project if the project is deleted out of the main project (#14462, PSA-3173)
  If a project is connected to a main project, the "main project dimension" is transferred into the project. If the project was deleted from the main project this dimension was not deleted out of the project.
• Sales price finding in service documents (#14463, PSA-3171)
  In service documents the project365 sales price calculation method was not active.
• Necessary user permission for HR-Cockpit (#14501, PSA-3186)
  Some improvements regarding the permissions of the user using the HR-Cockpit.
• Rolling Planning: Handle planning periode if postings are not in the planning periode (#14507, PSA-3202)
  New message to the user by opening the rolling planning page if there is a usage posting outside of the planning range (start / end date of the wbs-line or budget line).
• Rolling planning - Qt. unassigned has negative qty. after distribution (#14579, PSA-3218)
  In some cases the "Qty. unassigned" was negative even if the qty has been assigned completely.
• Error message on activating a wbs-version (#14635, PSA-3225)
  Technical development improvement
• Change budget line in project ledger is not possible anymore if the setting "Allow Moving Job Ledger.." is FALSE (#14636, PSA-3248)
  There was a wrong check in the project-ledger-function "change budget line".
• create wbs by sales lines - error by "wbs-sales-budget-bloc" in combination with "resource budget autoAllocation" (#14646, PSA-3253)
  In combination of "automatic resource budget allocation" with "automatic sales budget bloc by order" there is an error if a new resource budget line is created from sales document.

Change

• Break time by work time with different settings (#13820, PSA-2914)
  Break time setting is no more only 1 list for all resources but several lists. With this you can define separate break time settings for different kind of resources. One of this break time setting must be defined as the default (in resource setup). Other break time settings can be defined on the resource card. On HR-Cockpit the break-time setup can be defined to resources too.
• Transfer sales season price from sales line into project price list by creating a project from sales document (#14234, PSA-3053)
  Process: "Create project and wbs by sales document": season prices (tiered prices) are now "saved" as project sales price. Example: There are sales prices in the price list like this: 1-9 pcs = 100,- / 10-99 =95,- / 100.. = 92,-. In the sales line is a quantity of 50, so the sales price in the sales line is 95. Creating the project + wbs + project sales price list will save this 95,- in the project sales price list without a minimum qty. because this sales price has to be used in every usage posting, even if there is only 1 item posted as a project-part-shipment.
• Transfer "Sell-to Customer" from wbs-begin-total into the work package line of that block (#14236, PSA-3056)
  Changing the "sell-to Customer" in a begin-total-block line (wbs-line) will transfer the new "sell-to Customer" into all corresponding wbs-lines of that block.
• new setting field to change the wbs-line on project ledger entry connected to a purchase ledger entry (#14248, PSA-2570)
  It was not possible to change a project ledger entry to another wbs-line (work package) or project task, if the project ledger entry was connected to a purchase invoice ledger (process: external resources posting time ledger, invoiced by a purchase invoice). With a new setting field (project setup) it is possible to decide if this is possible (3 options: No, within wbs-line, within project).
• fix sales price in wbs-line calculated by cost-factor (#14249, PSA-2964)
  sales prices on wbs-line which have been calculated by the field "cost factor" are now a kind of manual price and protected by the change of quantity or date. Only if the factor or the unit cost is changed the sales price is recalculated.
• Use job currency factor in usage posting (#14254, PSA-2909)
  Only for projects with invoice currency. With a new field on the project card "use invoice currency factor in usage" it is possible to decide if the invoice currency factor of the active wbs should be used by the usage posting. Default for new project = NO. Because of the wbs-currency factor has been used for usage posting in the past, the update routine (BC26.2) is setting the new field on the existing projects to YES. If the new field "use invoice currency factor in usage" is set to NO, the actual currency exchange rate is used.
• Color Legend in CTC-Card - missing Colours for absence (#14264, PSA-3005)
  On CTC-Card the colour setting table for the absence registration is visible as an info-box. This colours are used in the calender on CTC-Card to mark days of absence.
• create sales document function - change position of the step code filter on the request page (#14282, PSA-3126)
• Change "on cost filter" on "to invoice" information on role center (#14283, PSA-3136)
  The informations "to invoice" on the project365 role center "project lead" has a new filter. Project ledger entries with "invoicing typ" = "time&materials" + "package invoice" + "TE Flat Rate" are taken into account.
• Company name in project reports (#14284, PSA-3121)
  On internal reports (like controlling reports) the company is printed in the header. We are now using the company "Display name" in the project365 reports in the same way as BC-Standard.
• Create wbs by sales lines - set field "Transfer in Sales Doc" on wbs-line correct (#14313, PSA-3061)
• project item posting by sales document - flag in sales line is not set after creating project budget line from sales document (#14360, PSA-3048)
  process "project item posting by sales document": There was a GAP by the creation of a new project budget line (item) from a sales line (process "create project and wbs by sales document"). The necessary fields for the process "project item posting by sales document" were not set in the sales line after the budget line creation.
• Create wbs by sales lines - set field "Transfer in Sales Doc" on wbs-line correct (#14362, PSA-3061)
  Process "create project and wbs by sales document": The field "transfer in sales doc" of new wbs-lines created by a sales document must be in the correct option (depending of if the wbs-line is created directly by the sales line or the budget lines are in the sales lines).
• Transfer project invoicing fields from template to sales header to project (#14366, PSA-3032)
  The invoicing setup fileds (for the sales invoice attachment) are transfered from the project template into the sales document (quote, order) and then into the project. Regarding the process "create project and wbs by sales document".
• Insert new fields on sales line for the process "project item posting by sales document" on all sales sub pages (#14367, PSA-2974)
  In all sales document pages (quote, order, invoice, archive, posted ....) the fields for the process "project item posting by sales document" are available now.
• Open wbs from budget line card (#14387, PSA-3091)
  A "project budget line card" can be open from different sources. If this card was not openend from the project budget line page (but by a neutral position) it will be helpfull to open the corresponding wbs from the "project budget line card".
• Use item and resource translations by using project template in sales document (#14388, PSA-3129)
  Process "Create project and wbs by sales document": Transfer items and resources from project template into a sales document with a language code, the translation of the item / resource is used in the sales document line (if there is a translation existing, in the other case the description of the project template is used).
• E-Mail and phone from bill-to contact or bill-to address into sales header (#14390, PSA-3132)
  E-Mail and phone are transfered from bill-to contact or bill-to address into sales header.
• Attachment "posted invoice ledger entries" for posted credit memos (#14392, PSA-3137)
  Attachment "posted invoice ledger entries" are now available for posted credit memos too (and not only for posted invoices). The customer can check which positions (project ledger entries) have been send to the credit memo.
• change filtergroup on project and time entries called by posted CTC (#14396, PSA-3156)
  It is not possible to change the filter on project ledger entries and on time ledger entries if they are called by the CTC-Card. The users view is restricted to the entries connected to the CTC-Card.
• Ignore resource planning warning on resource (#14397, PSA-3160)
  In resource planning there is a capacity warning if the resource is planned with an overload. In some cases (dummy resources) this warning doesn't make sense. Now it is possible to setup a resource in the field "ignore resource planning warning". This is additional to the existing setup table "Overscheduling Setup".
• New wbs function to update the payment plan only for the current wbs-line (#14405, PSA-2656)
  On wbs the function "update payment plans" updates the payment plan for the whole project or for all wbs-lines (depending on the payment plan level). The new function "update payment plan (current line) updates the payment plan for the current wbs-line (only available by payment plan level = wbs-line).
• Order Quote Archive - missing project and wbs fields - Dimension Issues (#14413, PSA-3066)
  The order quote archive is completed by the project fields.
• project journal - new user filter related qty information fields (#14421, PSA-2593)
  Into the statistic in the bottom of the project journal a new quantity field was added "filtered quantity". By default this field has the same value as the Quantity field, but if the user sets some individual filters the filed "filtered quantity" shows the quantity of the filterd journal lines while the quantity field shows the original quantity of the non filtered total quantity.
• HR-Cockpit - Setting for auto deletion of the HR-Cockpit Data (#14433, PSA-3167)
  After the transfer function from HR-Cockpit into the corresponding tables (employee, resource ...) the user was asked if the HR-Cockpit record should be deleted or stay for a further processing. Now there is a new setup in the HR-Cockpit setup: "Delete HR-Cockpit" with this Options: always ask, always delete, don't delete.
• German Caption for "Project Bank Account Text" on "Sales & Receivables Setup" (#14437, PSA-3170)
  Some improvements on German Caption.
• Copy wbs description to sales line (setting) (#14443, PSA-3175)
  New setting in project setup "copy wbs description to sales line" to define wheter the wbs-line descripton (or project budget line description) should be transfered into a sales line during the function "get work package". The options are: always (with dialog), if default description exists (with dialog), never. The option "if default description exists (with dialog)" means: if there is no manual description in the sales line (the description of the item or resource is still in the sales line) the user will be asked if the description of the wbs / budget line has to be transfered into the sales line.
• Add Name in Pagetitle in hr cockpit card (#14444, PSA-3180)
  The employee name is now present on the HR-Cockpit-page-title.
• New setup in KUMAVISION Module Setup to deactivate Location on wbs (#14449, PSA-3184)
  New setup in KUMAVISION Module Setup to deactivate Location on wbs. If the location is deactivated on wbs, there will be no "Stock commitment" Calculation (more performance in wbs). In the next step (Version 26.3) the location fields and related functions will be hidden on the wbs.
• Location Code from project template to sales document (#14477, PSA-3158)
  Process: "Create project and wbs by sales document": Transfer location code from project template into sales line and in the next step into the project budget line. The location code priority is: 1) customer 2) project template 3) company setup
• Reservation from project budget line to production order line (#14491, PSA-3154)
  Creating a production order by project budget line function, will connect the budget line with the production order by a reservation entry. Posting the finished item on location the reservation changes to the item ledger entry.
• Create base Load - some improvements (#14497, PSA-3195)
  "Save values" in the "create base load" request page.
• copy wbs function: copy into the same project - confirm PTS-code changing (#14499, PSA-3189)
  Function "copy wbs": If this function is used within one project to copy from one version into another version, and one of the wbs-line-reference fields (Phase,task,step) is manually changed, the user will get a message about the risk this will cause.
• Improve Performance based on Telemetrie Data (#14516, PSA-3207)
  A lot of technical changings have been done to improve the performance of the wbs. We recommand to switch on the new Microsoft-BC-setting which disables the calculation of not visible flowfields.
• Third-party production - last operation to post the item on stock by purchase order including projec (#14553, PSA-3071)
  Now it is possible to post an purchase order connected to a production order and post the item into location including a project reservation and a project connection.
• Field Pause in page KVSPSAPost. ZDE-Card List (5026299, List) (#14606, PSA-3240)
  The field "pause" has been inserted into the posted ctc-list.
• Change english caption form premium type to surcharge (#14607, PSA-3208)
• English caption for the new field "Allow moving job ledger entry with purchase Invoice entries" (#14608, PSA-3233)
• change some english captions (#14609, PSA-3231)
• project journal - tooltips (#14634, PSA-3229)
• New function: Transfer Values from distribution entries (for wbs-line level distribution) (#14654, PSA-3213)
  Rolling Planning: The function "transfer from distribution" is now available for distribution on wbs-line-level.
• 2 flow fields for qty. assigned on wbs-line: one for the wbs-line distribution and one for the budge (#14655, PSA-3214)
  The flowfield on wbs-line "qty. allocated" has been changed to the allocation of the wbs-line level. A new flowfield has been added "Qty. allocated for Budget lines", for the allocation of the budget line level.

26.1.3615.0 - 2025-05-15

Change

• General performance and stability improvements.

26.1.3601.0 - 2025-05-14

Hotfix

• Recreation of purchase lines - project budget line ToDoNo. gets lost (#13959, PSA-3021)
  By changing some fields on purchase header the purchase lines are recreated automatically. The field "todo No." got lost in this case.
• sales invoice with prices including VAT-Flag - project ledger entry has wrong amount if line discount is set (#14114, PSA-3089)
  The sales amount on project ledger entry was wrong if the sales document was set in "prices including VAT" in combination with line discount.
• time journal line - cancel the selection of an other budget line deletes the existing budget line no. (#14121, PSA-3063)
• Transfer project budget line into another wbs-line - toDo-No. is getting lost in project ledger entries. (#14123, PSA-3069)
• ctc-cancel - problem with time comments by second cancelation (#14150, PSA-3094)
  The handling of the line comments has been fixed.
• time journal line - cancel the selection of an other budget line deletes the existing budget line no. (#14163, PSA-3063)
  This bug was only relevant on existing time journal lines with project budget line connection.
• System creates two sales quotes by filtering with phase (#14240, PSA-3111)
  WBS-Function "create sales document": Avoid an empty sales document by using the phase-/task-/step filters.
• Filter on no. in resource capacity / CTC time overview report, although other filter is set (#14244, PSA-3110)
  Filter handling has been fixed on CTC controlling report.
• In copy function the distribution calc formula are empty after copy into a new WBS Version (#14251, PSA-3124)
  Rolling planning: Copy wbs-function has been fixed.
• Non-deductible VAT for invoicing a purchase receipt (#14319, PSA-1328)
• Fields in Budget Lines are not updated by distribution (#14418, PSA-3117)
• Values in Distribution Matrix are not saved (#14419, PSA-3118)

Change

• Create wbs by sales lines - automatic resource budget allocation is not working (#13912, PSA-2958)
• Analyse Mode in page KVSPSAJobBudgetList (5026287, List) (#13952, PSA-3014)
  Now it is possible to set the page project budget list into analysis-mode.
• Define Default Bill-to Address on customer (#13968, PSA-2982)
  On Customer card it is possible to define alternative bill-to adresses. Now there is a field on the customer card to define one of them as the default-bill-to-adress. It it automatically used in sales documents (sales header) and on project card.
• Create purchase document from wbs: Split purchase document by location (#13980, PSA-3006)
  WBS-function "create purchase document": Now it is possible to splitt the purchase documents by location. This is helpfull if the locations have adress. With a new setting in project setup it is possible to define a default receive address type: Default - company address / Location address / project shipment address. This default is used in the wbs-function "create purchase document" and can be changed. If location address is used, the purchase documents will be splitt by the locations of the selected budget line.
• Avoid double reservation for project budget line if project shipment line has been created (#14013, PSA-3019)
  Reservation entries are transfered from project budget line into project shipment line. To avoid a double reservation on the project budget line after the creation of a project shipment line, there is a new field "project shipment reservation" on project budget line. If the user tries to create new reservations to the project budget line the project shipment reservation quantiy is used too.
• Create budget ledger allocation without resource capacity (#14025, PSA-3039)
  Now it is possible to create allocation to resource budget lines even if the resource has no defined resource capacity.
• Mandatory field check functions in page "change project" (#14056, PSA-3058)
  On the function page "change project" the mandatory field function is now supported.
• Review some english captions (#14068, PSA-3055)
• Service package resource in project budget line can now be changed into another service package resource. (#14087, PSA-3072)
  If a service package was inserted into a project wbs as a project budget line, it was not easy to change this project budget line in the number field (change the budget line to another service package). This has been fixed.
• don't use Qty. to Complete in project budget line if quantity = 0 (#14091, PSA-2998)
  It doesn't make sense to calculate the field remaining QTY if there is no QTY in the budget line.
• Some improvements in project evaluation row setup (#14093, PSA-2987)
  More useability in project evaluation row setup
• Save manual extended text by changing the customer on a project (#14095, PSA-3044)
  Manual extended text on a project are now marked as a manual text. Changing the project customer all extended texts on project card are deleted and replaced by the automatic text of the new customer, only the manual extended text will not be replaced.
• create a new HR-cockpit record for update mode without selection of an employee causes error (#14099, PSA-3004)
  More system stability on the HR-Cockpit
• enable the search function in page 5026287 KVSPSAJobbudgetList (#14108, PSA-2896)
  More usability in project journal by project budget line selection.
• Unit Price and Invoice Discounts: Change Validation (#14116, PSA-3082)
  Technical Development Improvement
• negative quantity in item tracking information on project shipment print (#14151, PSA-3052)
• Intercompany review - check "Default Budget Allocation Period" (#14152, PSA-3027)
  Transfer resource project budget lines into an other company (intercompany partner): It is necessary to have the same automatical resource allocation for project budget lines, This will be checked in the intercompany review function on the target project.
• Expand the project deletion testing by existing project evaluations (#14162, PSA-2979)
  Projects with existing evaluations (posted or unposted) can't be deleted.
• project task no validation in project journal line (#14182, PSA-3025)
  More usability in project journal: validation in "ToDo no" gets automatically the project-wbs-budgetLine-Connection (like in ctc-line).
• no Customer on budget line if there is a payment plan on the wbs-line (#14187, PSA-3086)
• create first price line for service package with starting date 0 (#14201, PSA-3000)
  The to ensure the first sales price and first cost are immediately valid the automatic price list line is created without a starting date.
• New Events for IC and Invoice Suggestion (#14203, PSA-3102)
  Technical development improvement
• Optimize Archive (#14205, PSA-3103)
• Add the function "Indent chart of accounts" into page project account list (#14219, PSA-3034)
• Add the function "Indent chart of accounts" into page project account list (#14230, PSA-3034)
  More usability.
• Dimensions on project template budget lines (#14231, PSA-3046)
  On project template default dimensions can be defined on project and on wbs-line level. Now this is possible on budget line level too.
• project financial reports - some improvements (#14233, PSA-3035)
  More usability.
• The combination of filters on 2 or 3 activity code fields in function "create sales document" must w (#14255, PSA-2975)
• New Event KVSPSAOnAfterModifyLinesGetActivity in Table KVSPSAJobTimeJournalLine for fuction GetActi (#14281, PSA-3100)
• Field "Period Unit Type" 2x in page KVSPSAPSPJobBudgetLineTemplate (5025902, List) (#14358, PSA-3059)
• The combination of filters on 2 or 3 activity code fields in function "create sales document" must work as an AND-statement (#14369, PSA-2975)
  The wbs function "create sales document" has 3 filters to select the wbs-lines by Phase, task and step code. These 3 filters are now working in a AND-combination. For example: Filter phase code "AAA" + Filter step Code "1122" transfer only the wbs-lines which have a phase Code AAA and a Step code 1122, both arguments must match.
• Task Code Table is not available by TelMe (Search) (#14379, PSA-3060)

26.0.3411.0 - 2025-04-15

Change

• General performance and stability improvements.

26.0.3404.0 - 2025-04-15

Hotfix

• create warehouse receive in purchase order - error message about missing project task no. (#14133, PSA-3009)
  This is a technical solution because of some changings in BC26-Standard.

Change

• Performance in WBS and Budget Lines (#12891, PSA-2345)
  
• Optimize Index - Use Number Seuqence in follwoing tables: "KVSPSA Job Account Entry", "KVSPSA Job Budget Entry", "KVSPSAJob Evaluation Entry", KVSPSAJobTimeLedgerEntry and KVSPSATimeBalanceEntry - gerneral Performance Optimization
• Replace KUMA HTML editor by the Microsoft Rich Text Editor (#13712, PSA-2908)
• Remove Forecast Module (#13782, PSA-2572)
• Remove Earnd Value Objects (#13783, PSA-2957)
• Posting Code is obsolated in KBA - remove project posting code (#13798, PSA-2944)
• Prevent Feature: Enable multiple users to post job ledger entries at the same time (#13859, PSA-2991)
  This feature can be set in later releases.
• GL/Account KVSKBADirectinSales & KVSKBADirectinPurchase (#14132, PSA-2392)
  In GL/Account the fields KVSKBADirectinSales & KVSKBADirectinPurchase does not exist anymore. Deleted all functions belongs to those fields.