Advance Payment#

24.7.1091.0 - 2024-11-05#

Hotfix

Apply payment - missing / incorrect Advance Chain No. in General Ledger Entries (#12503, AZ-247)
When apply the payment, the system now searches for the correct Advance Chain No. This means that it is also correct when apply several Advance Chains with one payments.
Can not create new advance invoice in cum. Advance Chain (#12613, AZ-252)
The logic with the setting “Cum. cancels prev. Inv.” has been revised.

Change

New Events for Documents exists check for Advance Chain (#11966, AZ-216)
New events have been provided.
Missing rendering for e-mail layout in report 70260236 Sales - Closing invoice (#12191, AZ-207)
The report has been converted to the new rendering logic and the standard e-mail layout has been stored.
Vendor Posting Group Card Advance Payment Fields (#12194, AZ-231)
The fields "Receiv. Account Advance" and "Receiv. Unreal. Advance" have been displayed in the Vendor and Customer Posting Group Cards.

Hotfix

Correction Advance Job Ledger Entries Foreign Currency (#11901, AZ-167)
The net amount is now transferred to the advance project entry in the closing invoice, no longer the total amount.
Transfer the transaction number in the Advance Project Ledger Entries (#11976, AZ-220)
In purchasing, the transaction no. was not transferred to the Advance Project Ledger Entries. The event responsible for this has been corrected.
Correction Advance Chain Statistics (#12045, AZ-166)
A unnecessary foreign currency entry has been removed from the statistics.

Change

Change Enums, with more than 30 characters (#11135, AZ-193)
To avoid problems with MS specifications later on, the enums with more than 30 characters were replaced with enums with less than 30 characters. (Enum KVSADVAdvancePlanningEntryStatus -> Enum KVSADVPlanningEntryStatus, Enum KVSADVAutomaticallyCreateCreditMemoForClosInv -> Enum KVSADVAutoCreateCrMemoForClInv, Enum KVSADVDocumentsExistForAdvanceChain -> KVSADVDocExistForAdvanceChain)
Suppression Notification Message Assign Security Deposits (#11988, AZ-175)
The notifications about Assign Security Deposits (AZ-151) have been revised so that they do not appear in automatic processes.

Hotfix

Error when adding cumulated Advance Planning Entries to existing invoice (#8104, AZ-142)
When cumulative advance planning is enabled and an Advance Invoice is created manually (not by Advance Planning Chart but by manually creating the invoice header and then assigning the Advance Planning Entries) an error occured. This has been fixed. The invoice date is now a mandatory field so as not to break the calculation for cumulative advance planings lines.
Advance posted Invoice contains unposted closing credit memo no. (#11654, AZ-205)
If the posted closing credit note no. is available when the invoice is posted, it will be entered. Otherwise it is updated when the closing credit note is posted.

Change

Delete code for automatic creation of the test suite due to problems with BC25 (#11580, AZ-211)
The old functionality has been deleted for compatibility reasons.
Linked advance chain in sales line / purchase line cannot be deleted (#11668, AZ-204)
If the field "KVSADVAdv. Plans on Line-Level" is not set in the document header, a linked advance chain can now also be deleted in the lines.

Hotfix

Incorrect error message when posting down payment invoices on the subject of retention. (#11368, AZ-201)
The check whether Security Desposits exist has been optimized.
Standard code change from 24.2.20227.21402 causes error when unapply entries with foreign currencies. (#11456, AZ-208)
Due to a code change by MS, a commit occurs when unapply entries with foreign currencies. This commit is now prevented.
Word layout cannot be edited at report 70260236 Sales - Closing Invoice (#11470, AZ-206)
Due to artifacts from older versions, the layout could not be read in again as a user-defined layout. The irritating artifacts have been removed.

Change

Conversion of number series management to new logic (#10589, AZ-174)
The changes made by MS for the number series have been adopted.

Hotfix

Advance Chain No. linked to several orders (#11222, AZ-191)
If orders run quickly through the system and the Advance Chains are created automatically when the order is created and no postings are made on the Advance Chain, the Advance Chain is deleted and the no. is used again for the next one. This is now being prevented.
For advance chain that are linked to both the project and the order, the link to the project or order can no longer be removed (#11270, AZ-187)
The linked advance chain in the order can now be deleted. If all conditions for the project are met, the Advance Chain can now also be removed again.
Error message on status change in the project (#11286, AZ-196)
When the status was changed in the project, the same tests were run as when the advance chain was deleted from the project. This has been changed.

Hotfix

Unapply Vendor Ledger Entries with Non Deductible VAT: Amounts at Job Legeder Entry wrong (#10916, AZ-179)
Due to a sign error, the amounts in the project ledger were incorrect when unaply a payment with non-deductible VAT.
Wrong error message "Order amount exceeded" when using Non-Deductible VAT (#10955, AZ-156)
Due to the inclusion of non-deductible VAT in the net amount, the message “Order amount exceeded” was triggered incorrectly. The net amount is now adjusted for the vat amount.

Change

Inconsistencies in the overpayment credit note (#10626, AZ-131)
The calculation of the overpayment amount was adjusted. The feedback from the system has also been optimized.
Allow merge customer and vendor with advance payments (#10727, AZ-132)
Problems with merging customers and vendors have been fixed.
Add Adv. Job Ledger Entries in Tell me (#11002, AZ-190)
This page has been added to Tell me.

Change

Change

BC24: Delete obsolete objects, functions and events (#8645, AZ-168)
Obsolete objects, functions and events have been deleted for BC24.
BC 24 Restore Archive projects with Advance Job Ledger Entries not allow (#10559, AZ-172)
The new archive project is supported. In some cases, a restore is prevented to avoid corrupt data.
BC 24 Project settlement against multiple Customers (#10584, AZ-171)
We allow the standard multiple customers for the projects. It is then mandatory to work with advance chains on job tasks.