Release Notes 1.2
- Soporte Techedge BPLUS ES
ID | Module | Description | Coments: IMPORTANT TO READ | Type |
|---|---|---|---|---|
1 | TBAI | Created new flows for self-billing. | Everything related to the new self-billing functionality is documented on the next page. | New functionality |
2 | TBAI | Including alarms in the product. | Everything related to the new alarm functionality is documented on the following pages: https://techedgespain.atlassian.net/wiki/spaces/BAE/pages/2756050959 https://techedgespain.atlassian.net/wiki/spaces/BAE/pages/2755985421 | New functionality |
3 | TBAI | Download and attachment reports | These reports are used for some self-billing flows https://techedgespain.atlassian.net/wiki/spaces/BTE/pages/2755559436 |
|
4 | TBAI | New BADIs created. | New badis are created for the XML download and upload reports of the self-invoice part at the /EDGE/TB_ESPOT_REPORTS extension point with the UPLOAD and DOWNLOAD methods, the reservation class for the BADIs is /EDGE/CL_BADI_TB_REPORTS_AUTO. Finally, two new methods are added to the BADI for creating records for LROE and TBAI /EDGE/BADI_TB_CREA at the /EDGE/TB_ESPOT_CREA extension point, these being DETERMINE_AUTO for creating self-invoice records and DETERMINE_PRIORITY to establish the priority of the configuration entries in LROE and TBAI record creation. More information about the product BADIs on the next page. | New functionality |
5 | TBAI | Rectifications SD. | The GET_RECTIFICATIVAS method of the class of the abstract class /EDGE/CL_TB_ABS_EXTRACTOR is changed to add the logic related to the rectifications that go by SD. | Improvement |
6 | TBAI | Total amount field in invoices issued without SG. | Fixed a bug where sometimes the total amount field in invoices issued without SG would show 3 decimal places instead of the 2 that it should show. | Correction |
7 | TBAI | Derecognition of issued without SG. | Corrected mapping bugs in the cancellation of invoices issued without SG in which the issue date was shown incorrectly. | Correction |
8 | LROE | Annotation fix now displays messages from the process. | New messages have been introduced when correcting annotations that are the following: The xxxxxxxxx annotation is not in a good state to correct. Cancellation correction is not allowed. The xxxxxxxxx annotation has been corrected. | Improvement |
9 | TBAI | Now a message is displayed in the log if the deletion of the repository test fails. | In step 30 there is a repository test where a file called 'test' is created to be deleted later. If the deletion fails, it is indicated in the log and the process stops since 2 entries in TOA01 cannot have the same electronic id. | Improvement |
10 | LROE | Batch error. | Fixed a bug where records were not being pulled out of batches properly. | Correction |
11 | TBAI | Total amount field in rectifications | The cases in which the total amount field in different rectifying invoices appeared with 3 or 1 decimal places when the correct thing is 2 decimal places have been corrected. | Correction |
12 | TBAI | Subchapter field in issued annotations table is now mandatory. | Fixed the /EDGE/VC_COPR001 view of transaction /EDGE/TC_TB_CV003 so that the subchapter field now appears as required. | Correction |
13 | TBAI | Now it is not allowed to create two identical entries differing only the subchapter. | In the /EDGE/VC_COPR001 view of the /EDGE/TC_TB_CV003 transaction for creating annotations, it is prevented from creating two lines that have the same value in the fields Chapter - Company - Document class - VAT indicator and accounting key and only differ in the value of the subchapter. | Correction |
14 | TBAI | Error in calculating the deductible fee. | The deductible fee was being calculated incorrectly and has been corrected. It was necessary to add the type of tax (KOTSL) corresponding to the Equivalence Surcharge (ASB) in the exclusions. | Correction |
15 | LROE | Error creating modifications of registrations with incorrect status. | NEW INVOICE New invoice sent with 1.1 and accepted status - Correction should not be allowed New invoice sent with 1.1 and incorrect status - It must be allowed to correct and generate a 1.2 registration New invoice sent with 1.2 and accepted status - It must be allowed to correct and create a 1.2 modification New invoice sent with 1.2 and incorrect status - It must be allowed to correct and create 1.2 discharge New invoice sent with 1.2 and accepted status with errors - It must be allowed to correct and create a 1.2 modification Annulment Corrections are not allowed on annulments | Correction |
16 | TBAI | Space in the field amount of the detail is not subject. | When correcting annotation and generating without SG, a space was generated in the field amount of the detail not subject. | Correction |
17 | TBAI | The TBAI validations are corrected to know if the SII is used or not. | The validation is corrected so that it does not only check if the configuration in TBAI goes by SII when it is only issued. | Correction |
18 | TBAI | Guipúzcoa unit amount field | An error has been corrected whereby the unit amount field for Guipúzcoa did not have 8 decimal places. | Correction |
Avvale 2024