Release Notes 1.3
- Soporte Techedge BPLUS ES
ID | Module | Description | Coments: IMPORTANT TO READ | Type |
|---|---|---|---|---|
1 | TBAI | Clients have been added to the tax tables by customer and by supplier.
| The client field has been added to the following tables:
| Improve |
2 | TBAI | Error with LROE checkbox in reprocessing transaction
| When a record is not created in the LROE monitor, it was not marked as a LROE error in the reprocessing report. In addition, a new condition has been added to prevent empty lines from appearing in the log. The name of the columns of the checkbox has been changed, now it is called Log TBAI and Log LROE. | Correction |
3 | TBAI | Translations | Translations of data elements as well as text elements of message types and reports into English have been carried out. | Correction |
4 | TBAI | Entries have been added in the self-billing configuration table (/EDGE/TC_TB_REGL).
| Entries have been added in the combination Recipient/own in flow 3.3.1, when the TO's/Supplier's farm is not HFB because it was not indicated that the Customer's farm should be analysed. In fact, the Client's finances must always be analysed. The entries added are as follows: 
| Correction |
5 | TBAI | GOS menu: Three ABAP classes are provided that perform the logic in the GOS menu to access the TBAI, LROE and alarm monitors respectively. | Information for the creation of the GOS menu:https://techedgespain.atlassian.net/wiki/spaces/BTE/pages/2794488036
| New functionality |
6 | TBAI | Creation of a new status 6343 Invoice accepted without SG
| The status 6343 has been created and will be updated in TBAI and LROE when an LROE issued with subchapter 1.1 is rejected, subsequently corrected and finally sent successfully to the county council with subchapter 1.2. | Improve |
7 | TBAI | Change in the mapping of the Grouping to the company code instead of by parameter of the table /EDGE/TC_TB_017.
| The Grouping is now mapped to the value of the company code being sent. Example: If the company code is BAI1 the grouping field will be sent to the TCI with BAI1 instead of the mapping from the /EDGE/TC_TB_017 table. The values of the common fields of this table have been updated. TBAI / LROE common parameter configuration (including middleware parameterization) | Correction |
8 | TBAI | Modification of the internal table DATA_TO_MAP
| The GET_DATA method of the /EDGE/CL_TB_ABS_EXTRACTOR class GET_DATA has been modified to improve the performance of the application. | Performance improvement |
9 | TBAI | New Authorisation Objects.
| Authorisation objects and user permissions are adapted. https://techedgespain.atlassian.net/wiki/spaces/BTE/pages/2747629572 | New functionality |
10 | TBAI | The API class /EDGE/CL_TB_LROE_API is modified to be customer extensible. | This section details the modifications to the class: TBAI / LROE common parameter configuration (including middleware parameterization) | Correction |
11 | TBAI | Extension of the BADI "Invoice detail" to obtain the issuer of the invoice in one of its entries.
| GET_EMISOR_FACTURA method has been created in the BAdI /EDGE/BADI_TB_TBAI_DET_FACT for the sender block within the subject block. The logic is the same but a BAdI method is added to make it easier to modify the logic per customer. https://techedgespain.atlassian.net/wiki/spaces/BTE/pages/2755788911 | Improve |
12 | TBAI | New report for TBAI process continuity.
| A new report has been created to avoid invoice chaining number errors. This link details the new functionality: https://techedgespain.atlassian.net/wiki/spaces/BTE/pages/2794782721 | New functionality |
13 | LROE | Remove repeated exceptional processing statuses
| The repeated statuses that appeared in the exceptional processing popup have been removed, as well as the correct translation of the statuses. | Correction |
14 | TBAI | New CHANGE_CREATION method of BAdi /EDGE/BADI_TB_CREA
| This method has default implementation, read documentation https://techedgespain.atlassian.net/wiki/spaces/BTE/pages/2755788894 | Improve |
15 | TBAI | Modification of the TBAI monitor | Invoices are now sorted by e-invoice ID in descending order. | Improve |
16 | TBAI | SII cancellations and rectifications from 2022 onwards
| Cancellations and rectifications that were sent to the SII before TBAI went into production will have to be sent to the SII. Even if entries have been generated in the exception table for the creation of annotations or TBAI records, if it is detected that the cancellation or rectification created corresponds to a registration prior to the exceptional date, the system will create the entry in the SII cockpit. Point 9 of the FAQs - https://techedgespain.atlassian.net/wiki/spaces/BTE/pages/2646245377 | New functionality |
17 | TBAI | Invoices are sent to the Álava regional agency. | Delivery service to Álava available. | New functionality |
18 | TBAI | Correction of the calculation of the total amount of the invoice detail lines coming from SD. | Fixed an error in the calculation of the total amount when invoices came from SD. | Correction |
19 | TBAI | Correction of operation date mapping | The transaction date mapping is corrected.
| Correction |
20 | TBAI | Correction of the mapping of the field "invoice number" for issued invoices. | If the BKPF of the invoice has the field XBLNR filled, it will paint the invoice number as XBLNR, otherwise it will paint it with the BELNR. | Correction |
21 | TBAI | Change in the logic of the mapping of the field "invoice series".
| The logic has been adapted. There are two invoice series fields:
| Correction |
22 | TBAI | Correction of the mapping of the block 'SubstituteAmountRectificationAmount'. | The mapping of the block "SubstitutiveRectificationAmount" is corrected and adapted to the agency's validations. | Correction |
Avvale 2024