1b.app
Link copied -

OS - NP created two TTNs

At the "Generate TTN" stage, according to the process logs https://rivcont.info/2464767/, one TTN was formed - 20450443381515
In the NP office and according to the logs https://rivcont.info/admin/logs/showall/ajax/?file=novaposhta-scansheet-2021-09-... two TTNs are visible 20450443380889, 20450443381515
1. (TTN who signed up in boxing)
2. (TTN which should not be)
See what's the problem?
Boxing generates two requests for the formation of TTN ?
Or NP gives two TTN? (in this case, please provide examples of request and response / what needs to be written in support of the IR)
Thanks
Original question is available on version: ru

Answers:

Сусяк Ігор
Integrator.com.ua
Personal license
1. Do you create TTNs manually? todі ymovіrno pressed 2 times
2. to fence in the integration of NP /admin/shop/integrations/novaposhta-integration-1/control/ check the box "Prohibit the re-creation of a TTN if there is an already created"
3. better TTN vipisuvati deyu, it is possible for the procedure.
21.09.2021, 14:25
Original comment available on version: ru


Susyak Igor
Integrator
Employee
Integrator.com.ua wrote:
1. Do you create TTNs manually? todі ymovіrno pressed 2 times
2. to fence in the integration of NP /admin/shop/integrations/novaposhta-integration-1/control/ check the box "Prohibit the re-creation of a TTN if there is an already created"
3. better TTN vipisuvati deyu, it is possible for the procedure.

- TTN is formed automatically by the action on the stage.
- If we pressed the button twice, two TTHs would be recorded in the process logs, but only one is displayed there.
- "Prohibit the re-creation of a waybill if there is an already created one" is not necessary, because there are situations where we re-create an invoice in the process
- there was a similar problem before, then it was due to the fact that the new mail gave two TTN
21.09.2021, 14:29
Original comment available on version: ru

Сусяк Ігор
Integrator.com.ua
Personal license

- "Prohibit the re-creation of a waybill if there is an already created one" is not necessary, because there are situations where we re-create an invoice in the process

I think scho tsya tick all virishit - friend ttn not happen. and as it is necessary - you see the real ttn and create a new one.
21.09.2021, 15:22
Original comment available on version: ru


Susyak Igor
Integrator
Employee
Integrator.com.ua wrote:

- "Prohibit the re-creation of a waybill if there is an already created one" is not necessary, because there are situations where we re-create an invoice in the process

I think scho tsya tick all virishit - friend ttn not happen. and as it is necessary - you see the real ttn and create a new one.

Thanks
Let's try with the setting "Prohibit the re-creation of a TTN in the presence of an already created one", it will slightly change the responsibilities of managers)
If it happens again, I'll create a new topic.
21.09.2021, 15:34
Original comment available on version: ru


Vysokos Nikolai Alexandrovich
Client wrote:
In the office of the NP and according to the logs https://rivcont.info/admin/logs/showall/ajax/?file=novaposhta-scansheet-2021-09-... you can see two TTN

There were 2 requests to the IR for the formation of TTN at [2021-09-21 12:00:20] and at [2021-09-21 12:01:04]
Your TTN is formed by an action and there are various actions that allow the process to move 2-3 statuses forward. Most likely, during the first transition to the status, an error was generated, the invoice number was not registered. in case of an error, the changes were rolled back, but the request to the NP had already been sent and the TTN was created. And when you re-transition, there was no longer an error and the process successfully switched to the desired status and the delivery invoice is present
Perhaps you should put the creation of ttn after actions that could give an error
21.09.2021, 15:46
Original comment available on version: ru


Maria
OneBox production
Employee wrote:

Vysokos Nikolai Alexandrovich
Client wrote:
In the office of the NP and according to the logs https://rivcont.info/admin/logs/showall/ajax/?file=novaposhta-scansheet-2021-09-... you can see two TTN

There were 2 requests to the IR for the formation of TTN at [2021-09-21 12:00:20] and at [2021-09-21 12:01:04]
Your TTN is formed by an action and there are various actions that allow the process to move 2-3 statuses forward. Most likely, during the first transition to the status, an error was generated, the invoice number was not registered. in case of an error, the changes were rolled back, but the request to the NP had already been sent and the TTN was created. And when you re-transition, there was no longer an error and the process successfully switched to the desired status and the delivery invoice is present
Perhaps you should put the creation of ttn after actions that could give an error

Okay, let's analyze what can give errors
Thanks
21.09.2021, 16:16
Original comment available on version: ru

Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter. Log in and comment