Main changes performed for version V2.0:
On September 27, 2019, the NAV has released a new version 2.0 of the API document, which determines the refactoring of the existing system, the expansion of the services offered and the replacement of the SHA-512 algorithm by the SHA3-512 algorithm. These changes imply that for version 2.0 there will be a new "endpoint" service and changes in the XML tags.
These changes do not impact the data report of version 1.1 and will only be considered if the requestVersion > 1.1 and the request is sent to the new endpoint v2.
The top level of the invoice includes the serial number and the date of issue.
The label lineExpressionIndicator is mandatory.
Change in pattern for PostalCodeType.
The number of characters allowed for the lineDescription label is defined as 512.
There is a new enum value for "ProductCodeCategoryType": TESZOR and now allows a length of 6 characters.
The number of characters allowed for the productCodeOwnValue label is defined as 255.
The "invoiceData" node is renamed to "invoiceDetail".
The "invoiceDeliveryDate" tag is mandatory.
Two new indicators are added to the invoice contents: "smallBusinessIndicator" & "periodicalSettlement".
There is a new optional indicator that allows you to describe the nature of the product or service within the invoice lines.
The elements "modificationIssueDate", "modificationTimestamp" and "lastModificationReference" have been removed. The modification date of outgoing invoices must be reported in the element "invoiceIssueDate". In addition, a new element "modificationIndex" is created which describes the logical sequence of changes to invoices.
Code added for corrective invoices "STORNO".
List of improvements EI Hungry V2.0 | |||
|---|---|---|---|
Nº | Type | Description | Comments |
1 | Improvement | Update to the new 2.0 agency format | |
2 | New functionality | Change status button | Change to status 1000 - Invoicing process started if the invoice is in status 1040 - Waiting Invoice response from MW or change to status 1058 - Corrected invoice if the invoice is in status 1052 - Invoice rejected. |
3 | New functionality | Modifications allowed | Sending modification invoices are allowed. |
4 | New functionality | Modification / creation of status | Modification of status 1043: Invoice response received correctly. When the asynchronous response of the shipment comes in, the invoice will go to this status and that's when you can call the change of status (query). If this response does not enter or enters in error, it will remain in status 1040 or 1042 and will not call the change of status since step 50 does not accept these two statuss. (This was not working like this before). Creation of the statuss: 1054 - XML Transformation for Query executed correctly. 1055 - Error transforming data to XML for Query. for step 50 (transformation for sending query). |
5 | New functionality | New status for invoice status RECEIVED | A new status to reflect responses with RECEIVED status and to allow access to step 50 and a new status request to be sent. 1059 Received invoice. |
6 | Correction | Access to SAP document display for objects of type VBRK. | |
7 | New functionality | Column to identify type of operation | This allows to identify whether the invoice is a creation 1 (CREATE), modification 2 (MODIFY) or cancel 3 (STORNO). |
8 | New functionality | Stores sending NAV XML attachment. | |
9 | Improvement | The "View XML", "View Response" buttons show an error if several invoices are selected at once | |
10 | Improvement | The response XML is stored only if an error occurs in the response. That is, if there is an "ERROR" in the status block. | |
11 | Improvement | Mapping modification |
were not displayed correctly in the XML. |
12 | New functionality | Stores warnings of accepted invoices | When an accepted invoice arrives (DONE status) sometimes warnings arrive. Store these warnings in the tables of the "View response log" button to be able to visualise them. |
13 | New functionality | Technical annulments | To be able to use this new functionality a new web service needs to be configured. This new service needs to have an endpoint configured. You can use this guide to help you to do it: Middleware communication |
14 | Improvement | Added Object type column to the ALV | |
15 | Improvement | New mappings added for SD documents | |