Datasets:
pismacx
/
ai_assistant

Dataset card Data Studio Files Community
Unnamed: 0
int64
0
999
0
stringlengths
258
77k
600
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8432\n\n### Instruction:\nPlease close both contracts below :\r\n\r\nItem : HCL\r\n\r\nPO-10/05/2019/RMP\r\nPO-4/06/2021/RMP\r\n\r\nComment user :\r\n\r\n I receive notifications when I want to close it, which I follow up, but then I receive new notifications. ( canceling Call offs etx )\r\n\r\n \n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'10/05 ma element na 0 kg jeden :ZaN_GIDTyp=960 AND ZaN_GIDFirma=1015303 AND ZaN_GIDNumer=612!image-2023-01-30-17-53-33-485.png!\'", "Comment 3: \'na ipor jest wyprodukowane nawet wiecej : !image-2023-01-30-17-54-48-144.png!TrN_GIDTyp=1490 AND TrN_GIDFirma=1015303 AND TrN_GIDNumer=32615\'", "Comment 4: \'2 różne magnumery na zaelem:select * from cdn.ZamElem where zae_gidnumer=612\'", "Comment 5: \'select * from cdn.ZamElem where zae_gidnumer=612select * from cdn.TraElem where tre_gidnumer=32615select * from cdn.tranag where trn_gidnumer=32615select * from cdn.ZamNag where ZaN_GIDNumer=612select * from cdn.traselem where trs_gidnumer=32615select * from cdn.Magazyny where mag_gidnumer in (2,8)\'", "Comment 6: \'zamowienie z czerwca 2021 pdobnieZaN_GIDTyp=960 AND ZaN_GIDFirma=1015303 AND ZaN_GIDNumer=12395select cdn.NazwaObiektu(trn_gidtyp,trn_gidnumer,1,2)", \'Comment 7: * from cdn.tranag where TrN_ZaNNumer=12395select cdn.NazwaObiektu(trn_gidtyp,trn_gidnumer,1,2)\', "Comment 8: * from cdn.tranag where TrN_ZaNNumer=612\'", "Comment 9: \'Hello for the orderPO-10/05/2019/RMP there is and POri document for more then 20250 kg", \'Comment 10: it seems like the second position on order made some problems\', \'Comment 11: also it is very old order- maybe something were done unsually.The pori isPORI-27/05/2019/VIMP - so from what I can see this should be set to executed as the correct status.Did you wish to change it status\', "Comment 12: did you need more changes for that PO and related elements send us informations.!image-2023-01-30-17-53-33-485.png!\'", "Comment 13: \'AboutPO-4/06/2021/RMP it is only confirmed ( with no realated POR", "Comment 14: nor PORI)did you wish to close it or to cancel it?After closing the order will get the status closed confirmed.What notification the operator got? Did it blocked him from operation?!image-2023-01-30-18-47-02-106.png!\'", "Comment 15: \'The contracts are indeed old and need to be closed / deleted.I can’t change it.I don’t exactly know the reasons why but they need to be closed in anyway. Met vriendelijke groeten", "Comment 16: with kind regardsFrank BoersmaSupport Inkoop en Logistiek !image-2!\'", "Comment 17: \'Hello,Requested POs are closed now. Please", "Comment 18: verify if this status is fine for you and if we can close this task.Regards\'", "Comment 19: \'I have asked the user for a conformation \'", "Comment 20: \'Waiting for your feedback then.Regards\'", "Comment 21: \'Hi,Any feedback?Regards\'", "Comment 22: \'Hi,Any feedback?Regards\'", "Comment 23: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
601
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8431\n\n### Instruction:\nChainge main, target and payer customer off SO-76/10/2022/V and ESI-3/11/2022/vexp from 7727 to 0674\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Dear,According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task.RegardsAgnieszka Januszewska\'", "Comment 3: \'see also DGS-8466\'", "Comment 4: \'Hi,We are closing this task as a duplicate toDGS-8466,Regards\']"]\nRelated Issues:\n[]\n\n### End'}
602
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8430\n\n### Instruction:\nArtikel 704956 has been exported to Intens, unfortunately I don\'t see this in Intens (New Items)\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Hello,There is a New Item Card in \\\'MAS NL\\\' sector with code = \\\'704956\\\' has been sent from Milas on 20.01.2023.Someone should parametrized this item and decide for which sectors item should be created from New Item Card document. Then item will be able to choose in Intense in this sector/sectors.!image-2023-01-30-16-15-54-887.png!!image-2023-01-30-16-17-24-349.png!Regards"\', "Comment 3: \'Could we close the task?\'", "Comment 4: \'Confirmed that can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
603
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8429\n\n### Instruction:\nThese messages ara show in quarantaine screen in DHP. \r\nQuestion : Where can we see the interval off time for wich items will be show in this screen because there is a great variation in the interval\r\nSome item will be correct for more then half a year\r\nThere will be differences between items with the same therm.\r\n\n\n### Response:\n["Comment 1: [\'!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'zgodnie z rozmową. \'", "Comment 4: \'Is there anything known about the status of this issue?\']"]\nRelated Issues:\n[]\n\n### End'}
604
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8428\n\n### Instruction:\nFields on Tech Results tab on Financial Statement document:\r\n * Total value of first loader\xa0\r\n * Total value of all loader\r\n\r\nshould be changed and calculated with all item codes instead of \'SLAC\' item like it is right now.\r\n\r\n\xa0\r\n\r\n*How it is:*\r\n\r\n(Sum of net values from invoices (PI and SI) related to Slaughtery reports (without invoices from Reversed Slaughtery Reports) with item code = \'SLAC\')\r\n\r\nminus\r\n\r\n(Sum of net values from invoices (PI and SI) related to Slaughtery reports (without invoices from Reversed Slaughtery Reports) with item code = \'AFKK\')\r\n\r\n\xa0\r\n\r\n*How it should be:*\r\n\r\n(Sum of net values from invoices (PI and SI) related to Slaughtery reports (without invoices from Reversed Slaughtery Reports) with item code != \'AFKK\')\r\n\r\nminus\r\n\r\n(Sum of net values from invoices (PI and SI) related to Slaughtery reports (without invoices from Reversed Slaughtery Reports) with item code = \'AFKK\')\r\n\r\n\xa0\r\n\r\nDue to this change also values for other calculations will change:\r\n * Feed profit\r\n * Average price delivered broilers per kg\r\n\r\n!image-2023-01-30-16-09-14-749.png!\r\n\r\nexample - FS-M/0219, ID= 79562 on IBIP_DH_TEST\n\n### Response:\n[\'Comment 1: ["[[email protected]]we have been changed calculations on Technial Results for Total value of first loaders. These changes have impact on fields Total value of all loaders and Feed profit. We also changed Average price delivered calulation because it\\\'s related with Total value of first/all loaders calculation.You can feel free to test it on test environment for MAS NL and MAS BE. I\\\'m waiting for your feedback.Best regards\', \'Comment 2: Grzegorz"\', \'Comment 3: \\\'There is still something not good in the "Voerwinst"(Feed profit).It should be 217.146,90 - 140.972,02 - 25.257,54 = 50.917,34 !image!\\\'\', \'Comment 4: \\\'Two other changes from the business:* Change “Doorgroei na 1e keer uitladen (g/d)” to "Doorgroei (g/d)"* Make this 0 decimals instead of 2\\\'\', \'Comment 5: "Please verify now and recalcualte technical results\', \'Comment 6: there should be value for Feed profit =50917.35 on document FS and also on printout.Before my change this value 1185,02 was as positive\', \'Comment 7: but it should be with negative sign. I\\\'ve changed this value for -1185,02 and also add vat and gross value for this line.!image-2023-02-02-13-45-04-522.png!"\', \'Comment 8: \\\'Two other changes from the business: * Change “Doorgroei na 1e keer uitladen (g/d)” to "Doorgroei (g/d)" * Make this 0 decimals instead of 2DONE :)\\\'\', "Comment 9: \'[[email protected]]could you verify it?After confirmation we can move also these changes on production environment.\'", "Comment 10: \'Verified.\'", "Comment 11: \'[[email protected]]do przeniesienia na prod\'", "Comment 12: \'[[email protected]]przeniesione na prod.\'", "Comment 13: \'[[email protected]],modification for technical resultscalculations have been adjusted in prod environment.You can feel free to test it.Best regards,Grzegorz\'", "Comment 14: \'Can be closed.\']"]\nRelated Issues:\n[\'DGS-8053\', \'DGS-8215\']\n\n### End'}
605
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8427\n\n### Instruction:\nFor Abma 000105 - this is a free contract - we can not open a new round, see error below. \n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Its fixed now on test and production database", "Comment 3: you can test it on test database.\'", "Comment 4: \'Dodano dodatkowy warunek na wykonanie akcji przy free farmer kontrakcie\'", "Comment 5: \'Still same error", "Comment 6: I can not create the new round\'", \'Comment 7: "Can you check it now i don\\\'t get this error now."\', "Comment 8: \'Still can not open round. Now only this error. !image-1!\'", "Comment 9: \'Ogólnie z free farmer contractu nie możemy wykonać tej akcjiakcja jest stworzona dla dokumentu CF", \'Comment 10: już przy pierwszym kroku szuka dokumentuów z ddf_id CF\', "Comment 11: akcja jest całkowicie nie przystosowana do dokumentu ffc\'", "Comment 12: \'Can you please check this again", "Comment 13: it is urgent\'", \'Comment 14: "Hello Dirco,We\\\'re verifying this topic\', "Comment 15: because it looks like in the system it\'s not well prepared creating Round and Feed sale from \'Free Farmer Contract\'.We need to investigate it little more.Is it possible to create \'Contract farmer\' from this \'Free farmer contract\' which you need right now?We don\'t want to stop you with work", \'Comment 16: then we want to find some temporary solution.This functionality works well from Contract Farmer\', \'Comment 17: but from Free Farmer Contract it looks different in our configuration\', \'Comment 18: due to this it will take more time to review it.Regards"\', "Comment 19: \'Comment at mail Tomasz: I still can not create the next round \'", "Comment 20: \'Hello Dirco,Please verify right now that is it correct and you can generate properly Round from Free Contract Farmer.Regards\'", "Comment 21: \'Yes it is fixed now. This can be closed", "Comment 22: thanks. \']"]\nRelated Issues:\n[]\n\n### End'}
606
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8426\n\n### Instruction:\nPlease help to check VT-1669/1/23 in Nghe An Plant ( 0432) .\r\nItem BPEY000731 can\'t released to stock with reson "Serial number already exists" ( it has the same serial number as item BPEY00419).\r\nWhy is there no warning when user recording a duplicate serial number ? User still can complete WO and close VT?\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "{code:java}SELECT [SerialNumber] ,[InternalSerialNumber]\\\\t ,* FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] where SerialNumber=\\\'30012023PO1249TH2\\\' select * from dbo.Items where id in(\\\'D03E04FB-01A1-4AB3-ADD1-A58575C860AC\\\',\\\'68BE024E-3115-4964-A5B8-295114645D6D\\\'){code} !screenshot-1! brakuje w stock:VT ma 22 elementy !screenshot-2! !image-2023-01-30-14-12-48-772!"\', "Comment 4: \'Hello as for correction the VT you can edit the delivery that is already in stock and then send the message with the error again. !screenshot-3! And yes", "Comment 5: there should be a warning.Were there other cases like this?\'", "Comment 6: \'1 question before you can close the ticket: Serial can edit or not if that already for using?\'", \'Comment 7: "Where it is already used because I don\\\'t see that initial<> current quanitity? There is only a restriction on the uniqueness of the entry.Regards"\', "Comment 8: \'HI Piotr GaczorekYou can close this ticket. Thanks u.\']"]\nRelated Issues:\n[]\n\n### End'}
607
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8425\n\n### Instruction:\nI will write an e-mail for this topic.\r\n\r\n\r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'{color:black}Hi,{color} {color:black}{color} {color:black}Can you help us with the following?{color} {color:black}Customer 100725 shows in FS-N/0023 ID88499 These post:{color}{color:black}{color} !image001!{color:black}{color}{color:black}{color} {color:black}When we go to Excel our Slaughtery is out of the overview (see Excel){color}{color:black}{color} !image002!{color:black}{color}{color:black}{color} {color:black}{color} {color:black}How can this be?{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image003!{color:blue}{color}{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | |{color:blue}{color} !image004!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} | |{color:blue}{color} !image006!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image007!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | [^FS Trenning (geen slacht).xlsx] _(24 kB)_\'", \'Comment 3: "Hello,I see that is an issue because we\\\'re showing documents PI when Reference is filled. On these 2 documentsPI-FNN/2022/0379,PI-FNN/2022/0380 this field is empty.Why this field is empty? Is there any reason why this field is empty?!image-2023-01-30-12-04-35-753.png!That\\\'s why it\\\'s not visible on this list (at summary \\\'Total Slaughtery\\\' we\\\'re showing invoices when \\\'Supplier\\\' (not referecne) is filled\', "Comment 4: so in this case it\'s ok and values from invoices are summed).For this case filling field \'Reference\' will resolve issue", \'Comment 5: however there are some inaccuracies here between Round and Financial statement which we can also adjust.Please inform us about \\\'Reference\\\' on PI invoices.!image-2023-01-30-12-04-21-628.png!"\', "Comment 6: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Something went wrong with this migration.{color} {color:black}Invoices should be:{color} {color:black}Leading doc a regular sale{color} {color:black}Purchase a registered purchase.{color} {color:black}{color} {color:black}I asked Mitch if he could change these postings", \'Comment 7: but he can not.{color} {color:black}Could you please make the change?{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* maandag 30 januari 2023 12:14 *Aan:* Jong\', "Comment 8: Christine de <[email protected]> *Onderwerp:* DGS-8425 FS 100725 Trenning incomplete | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | !image006-1!!image007-1!!image006!!image007!\'", \'Comment 9: "Hi Christine,We can change some data if it\\\'s not correct\', \'Comment 10: but what data should we change? Like on screens?!image-2023-01-31-13-28-02-948.png!!image-2023-01-31-13-25-32-220.png!"\', "Comment 11: \'{color:black}Yes perfect Damian{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* dinsdag 31 januari 2023 13:30 *Aan:* Jong", "Comment 12: Christine de <[email protected]> *Onderwerp:* DGS-8425 FS 100725 Trenning incomplete | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | !image006-2!!image007-2!!image006!!image007!\'", "Comment 13: \'Now it is like on screens below.PI-RTN/2022/0148 - PI Registration (on my earlier screen I made mistake and mark as Regular)- reference is filledSI-RLN/2022/0310 - SI RegularNow only PI Registration is on the Round and Financial StatementPlease verify that everything is correct.Regards!image-2023-01-31-14-52-35-950.png!!image-2023-01-31-14-48-26-232.png!\'", "Comment 14: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}We miss these ones. Could you also change these to registration?{color} {color:black}ID 35452{color}{color:black}{color} !image001!{color:black}{color}{color:black}{color} {color:black}SI ID 36376{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* dinsdag 31 januari 2023 15:01 *Aan:* Jong", "Comment 15: Christine de <[email protected]> *Onderwerp:* DGS-8425 FS 100725 Trenning incomplete | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | !image001-1!!image007-3!!image008!!image007!\'", "Comment 16: \'Hi Christine,SI ID 36376 - changed to Regular!image-2023-02-01-09-18-20-068.png!PI35452 - Registration and filled Reference!image-2023-02-01-09-22-18-336.png!Please verify that is correct.Regards\'", "Comment 17: \'{color:black}Goodmorning,{color} {color:black}{color} {color:black}Thanks Damian! Now FS is complete{color} {color:black}😊{color}{color:black}{color} {color:black}Have a good day.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* woensdag 1 februari 2023 09:25 *Aan:* Jong", "Comment 18: Christine de <[email protected]> *Onderwerp:* DGS-8425 FS 100725 Trenning incomplete | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | !image006-3!!image007-4!!image006!!image007!\']"]\nRelated Issues:\n[\'DGS-8437\']\n\n### End'}
608
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8424\n\n### Instruction:\nOn customer 816755 we are not able to open a new round. It seems that the contract is closed.\r\n816755/0069/0001\r\nOn 016755 contract 0057 can be closed.\r\n\r\nThanks for your action.\r\n\r\n\r\n\r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Hello,Contract Farmer CF-N/0069 now is in \\\'Draft\\\' status in your Inbox\', \'Comment 3: you should be able to process it and then Create new Round.Contract FarmerCF-N/0057 has been closed.Please verify that is correct."\', "Comment 4: \'Sorry I forgot to reply. You can resolve this as done.\']"]\nRelated Issues:\n[]\n\n### End'}
609
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8423\n\n### Instruction:\nWe want to delete conversion documents from the round of An de Stegge but we can\'t find the documents in documents. Please could you tell us how we can delete this documents?\n\n### Response:\n["Comment 1: [\'!An de Stegge documentnr.PNG|thumbnail!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hello,Please try to clear this field \\\'From\\\' on ribbon and you should be able to find these documents.!image-2023-01-30-09-47-23-364.png!Regards"\', "Comment 4: \'Could we close the task?\'", "Comment 5: \'Yes\']"]\nRelated Issues:\n[]\n\n### End'}
610
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8422\n\n### Instruction:\nPlease help to check this case and solving in Can Tho Plant -0437\r\nOn canceled of Production lot report with stock unit status In progress . \r\n** PLR 44372140123005 and 4372200123005\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Dla lota4372200123005!image-2023-02-01-08-45-42-916.png!errory:!image-2023-02-01-08-44-25-864.png!!image-2023-02-01-08-45-00-565.png!!image-2023-02-01-08-45-00-565! !image-2023-02-01-08-45-42-916!\'", "Comment 4: \'LOT4372200123005!image-2023-02-01-08-47-35-682.png!!image-2023-02-01-08-47-55-209.png!\'", "Comment 5: \'!image-2023-02-01-09-10-10-118.png!\'", "Comment 6: \'Dear Hardy,You can do inventory for those two stock units. Or we can correct them under database. Please", \'Comment 7: let us know what is better for you.For duplicated PLRs (I guess this was the reason for cancelling them\', "Comment 8: I have asked in DGS-8329 if you agree to raise RCA task).Regards\'", \'Comment 9: "{code:java}--UPDATE D--SET Status = 2\', \'Comment 10: Quantity = 0\', \'Comment 11: ExpiryDate = GETDATE()select *FROM DHPlantStockBusinessLogicMain.dbo.Deliveries DLEFT JOIN DHPlantStockBusinessLogicMain.dbo.StockUnits S ON S.DeliveryId = D.IdWHERE D.SourceDocumentId IN (\\\'B85005E1-F436-427F-95CF-DA74DD5F25F5\\\',\\\'A867C990-3B57-4896-803A-68D29937439F\\\')--UPDATE S--SET Quantity=0,Quantityonhand = 0,logisticstatus=8select *FROM DHPlantStockBusinessLogicMain.dbo.Deliveries DLEFT JOIN DHPlantStockBusinessLogicMain.dbo.StockUnits S ON S.DeliveryId = D.IdWHERE D.SourceDocumentId IN (\\\'B85005E1-F436-427F-95CF-DA74DD5F25F5\\\',\\\'A867C990-3B57-4896-803A-68D29937439F\\\'){code}"\', "Comment 12: \'please correct under DB and i have answer in DGS-8329\'", "Comment 13: \'Stock Units are corrected. Please", "Comment 14: verify.Regards\'", "Comment 15: \'W Prod i w Stock PLRy mają różne ID!image-2023-02-03-10-53-26-923.png!\'", "Comment 16: \'Hi Piotr Gaczorek .You can close the ticket .\'", "Comment 17: \'Hi leksandra Przybyłek.You can close the ticket .\']"]\nRelated Issues:\n[\'DGS-8330\', \'DGS-8329\']\n\n### End'}
611
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8421\n\n### Instruction:\nSql Nightrun job on DHVD01AP53 stopped for the second time. Linked server 10.111.4.5 can\'t be reached, see screenshot. Perhaps this has something to do with the Microsoft interruption last Thursday? Perhaps someone can take a look. Thanks in advance. Nightrun didn\'t run Thursday to Friday and Friday to Saturday night. As the interruption @Microsoft happened on Thursday it seems logical but i could be wrong. \n\n### Response:\n["Comment 1: [\'!DHVD01AP53.JPG|thumbnail!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Thanks", \'Comment 4: but last night the sync did run again. It is kind of strange and also sometimes but worrying that it isn\\\\\\\'t running. Also the error message is something i can\\\\\\\'t explain. 01/29/2023 02:11:12,BMadmin_Interfacing (night run) Azure,Error,12,DHVD01AP53,BMadmin_Interfacing (night run) Azure,e2 - NutrientDescriptions,,Executed as user: HEUS\\\\\\\\sa_sqld01ap53. TCP Provider: The semaphore timeout period has expired. [SQLSTATE 07008] (Error 121) OLE DB provider "SQLNCLI11" for linked server "10.111.4.5" returned message "Communication link failure". [SQLSTATE 01000] (Error 7412). The step failed.,00:53:44,16,7412,,,,001/27/2023 02:12:18,BMadmin_Interfacing (night run) Azure,Error,12,DHVD01AP53,BMadmin_Interfacing (night run) Azure,e2 - NutrientDescriptions,,Executed as user: HEUS\\\\\\\\sa_sqld01ap53. Cannot get the current row value of column "[10.111.4.5].[BestmixSyncDB].[dbo].[NutrientDescriptions].Language" from OLE DB provider "SQLNCLI11" for linked server "10.111.4.5". [COLUMN_NAME= Language STATUS=Unknown DBBINDSTATUS] [SQLSTATE 42000] (Error 7341) OLE DB provider "SQLNCLI11" for linked server "10.111.4.5" returned message "Multiple-step OLE DB operation generated errors. Check each OLE DB status value<c/> if available. No work was done.". [SQLSTATE 01000] (Error 7412). The step failed.,01:54:03,16,7412,,,,0Do we need to send these messages to you in the first place? \\\'\', "Comment 5: \'Dear Rob,We have discussed your case. We think you should contactMebrate or your IT to solve this case.Regards\'", "Comment 6: \'Ok", "Comment 7: i will discuss this internally. Thanks. \'", "Comment 8: \'Shall we leave this task open or can we close it?Regards\'", "Comment 9: \'Goodmorning", "Comment 10: you can close this task. Thanks!\'", "Comment 11: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}
612
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8420\n\n### Instruction:\nWe have several documents confirmed on DHP but they are not integrating to DHC. \r\n0851250123005\r\n0851250123014\r\n0851250123015\r\n0853250123001\r\n0851250123011\r\nCould you please fix it? It\'s urgent, we are waiting to invoice.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Please werify if SQL server works. I\\\'m not able to expand databases!image-2023-01-27-20-24-11-876.png!Also i\\\'m not able to log on to server:!image-2023-01-27-20-27-59-454.png!"\', "Comment 3: \'!image-2023-01-27-20-33-02-599.png!\'", "Comment 4: \'Please", "Comment 5: try this password Kotr@2023\'", "Comment 6: \'!image!\'", \'Comment 7: \\\'2023-01-27 16:59:47 (15de5d19-7ce1-4538-964d-eb22444b4e3e/Plant.DHC.Integration/BR-1-SV-VM0604/15144/5) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type "Plant.Stock.BusinessLogic.DomainAbstractions.Deliveries.DeliveryCreatedEvent"\', \'Comment 8: retry no -1Kotrak.Integration.IntegrationPluginCommon.Interfaces.ConnectionBrokenException: An error occurred while sending the request. ---> System.ServiceModel.CommunicationException: An error occurred while sending the request. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.. ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host. --- End of inner exception stack trace --- at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error\', \'Comment 9: CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token) at System.Net.Http.HttpConnection.<CheckUsabilityOnScavenge>g__ReadAheadWithZeroByteReadAsync|45_0() at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request\', \'Comment 10: Boolean async\', \'Comment 11: CancellationToken cancellationToken) --- End of inner exception stack trace --- at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request\', \'Comment 12: Boolean async\', \'Comment 13: CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request\', \'Comment 14: Boolean async\', \'Comment 15: Boolean doRequestAuth\', \'Comment 16: CancellationToken cancellationToken) at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request\', \'Comment 17: Boolean async\', \'Comment 18: CancellationToken cancellationToken) at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request\', \'Comment 19: Boolean async\', \'Comment 20: CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request\', \'Comment 21: HttpCompletionOption completionOption\', \'Comment 22: CancellationTokenSource cts\', \'Comment 23: Boolean disposeCts\', \'Comment 24: CancellationTokenSource pendingRequestsCts\', \'Comment 25: CancellationToken originalCancellationToken) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpClientRequestChannel.HttpClientChannelAsyncRequest.SendRequestAsync(Message message\', \'Comment 26: TimeoutHelper timeoutHelper) --- End of inner exception stack trace --- at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(HttpRequestException requestException\', \'Comment 27: HttpRequestMessage request\', \'Comment 28: HttpAbortReason abortReason) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpClientRequestChannel.HttpClientChannelAsyncRequest.SendRequestAsync(Message message\', \'Comment 29: TimeoutHelper timeoutHelper) at System.ServiceModel.Channels.RequestChannel.RequestAsync(Message message\', \'Comment 30: TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.RequestAsyncInternal(Message message\', \'Comment 31: TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message\', \'Comment 32: TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message\', \'Comment 33: TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action\', \'Comment 34: Boolean oneway\', \'Comment 35: ProxyOperationRuntime operation\', \'Comment 36: Object[] ins\', \'Comment 37: Object[] outs\', \'Comment 38: TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(MethodCall methodCall\', \'Comment 39: ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(MethodInfo targetMethod\', \'Comment 40: Object[] args) at generatedProxy_1.PushDeliveries(Package`1 ) at Plant.Integration.DhcService.Communication.BasePushService`1.PushPackage(IDhcService dhcService\', \'Comment 41: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 40 --- End of inner exception stack trace --- at Plant.Integration.DhcService.Communication.BasePushService`1.PushPackage(IDhcService dhcService\', \'Comment 42: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 40 at Plant.Integration.DhcService.Communication.BasePushService`1.CallService(IDhcService dhcService\', "Comment 43: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 62 at Plant.Integration.DhcService.Application.PushDataFilter`1.Process(PackageIntegrationState input) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\PushDataFilter.cs:line 26 at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input) at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input) at Kotrak.Integration.Pipeline.Pipeline`1.Excecute(T input) at Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler`1.Handle(TEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Infrastructure\\\\\\\\Handlers\\\\\\\\BaseInboundMessageHandler.cs:line 49 at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message)\'", "Comment 44: \'Monikanow can you access?\'", "Comment 45: \'Yes I have. during analysis\'", "Comment 46: \'Have you made any changes inSQL server firewall settings or another network settings?\'", \'Comment 47: "I checked with Ludemila and no\', \'Comment 48: we didn\\\'t changed nothing."\', "Comment 49: \'Can I restart the DHP servers?\'", "Comment 50: \'Yes please make restart.\'", "Comment 51: \'done\'", "Comment 52: \'could you check integration now?\'", "Comment 53: \'yes . I will let you know\'", "Comment 54: \'Now the production are in DHC. Do you know why we had this problem?\'", "Comment 55: \'There was problem with connect into DHP SQL server from server 10.55.64.12. Now it works. This was incydentally problem restart helps.!image-2023-01-27-22-18-00-964.png!\']"]\nRelated Issues:\n[]\n\n### End'}
613
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8419\n\n### Instruction:\nProszę o sprawdzenie, czemu dokument nie chce się prawidłowo zaksięgować, przypisane zostały właściwe konta 505-02-01-03 i 505-02-01-08 do nowych MPK-ów;\r\nPoniżej dekretacja:\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Przy próbie księgowania nie otrzymaliśmy żadnego komunikatu błędu. Wycofaliśmy dekretację.Proszę o sprawdzenie i informację", "Comment 4: jaki błąd pojawia się u Pani przy dekretacji.Pozdrawiam!image-2023-01-27-17-55-51-009.png!\'", "Comment 5: \'Została właśnie przeprowadzona ponowna próba i przeszło bez problemuDziękujeTask do zamkniecia\']"]\nRelated Issues:\n[]\n\n### End'}
614
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8418\n\n### Instruction:\nHi,\r\n\r\nIs it possible to add transport cost to Internal Orders (IOs)\r\n\r\nIf possible how ?\r\nif not what options do we have.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hi SamuelThere is no functionality for adding costs on internal order in the system.We can add an attribute in which we enter the value of the transport cost just for information purposes", \'Comment 3: but this cost will not increase the value of the goods in stock.Regards\', "Comment 4: Beata\'", "Comment 5: \'Many Thanks Kindly Close the Ticket\']"]\nRelated Issues:\n[]\n\n### End'}
615
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8417\n\n### Instruction:\nDear Jira service Desk\r\nWe have a stalk unit of Fry Meal (9004 ) = 501kg but we couldn`t process it on dispatch for a customer to sell it. keeps saying missing stalk . \r\nWe only needed 75 kg to dispatch when there is already 501kg available on system . \r\nHope someone will help us figure out a solution.\r\nThanks always \r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Thanks very much !\'", "Comment 4: \'Dear Gemechis,This item is expired. You can edit delivery and change the date.Regards!image-2023-01-27-16-38-22-420.png!\'", "Comment 5: \'Hello Dear Yes that was a solution ; I edited the expiry date as suggested and Sales dispatch was successful. Thanks very much Problem solved !!image001!\'", "Comment 6: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}
616
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8416\n\n### Instruction:\nKD has order 217/23/KLR showing in production but are unable to produce off of it as the order element is not appearing \n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'BulkProductID was missing", "Comment 4: Item was resent from DHC,Please check. !screenshot-1! \'", "Comment 5: \'thank you", "Comment 6: task can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
617
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8415\n\n### Instruction:\nHello, can you please remove AD \xa0AW967242 from DHC, this one is no longer Active\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hi Thomas,Additional Technology has been removed.Regards\'", "Comment 3: \'Thanks", "Comment 4: ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
618
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8414\n\n### Instruction:\nserver is: 10.84.1.22\r\nC:\\CA contains the latest one\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'proszę o przekazanie do działu dev", "Comment 4: będzie to rozliczane w ramach wsparcia integracji z MS D365\'", "Comment 5: \'certyfikat podmieniony\'", "Comment 6: \'Please check should be working now", "Comment 7: resolved by developers.\'", "Comment 8: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. Regards\']"]\nRelated Issues:\n[]\n\n### End'}
619
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8413\n\n### Instruction:\nGood evening,\r\n\r\nI have got a problem with item code 116270 for plant Maasbracht.\r\nThe recipe is not available on DHC.\r\n\r\nPlease could you help me, out production needs this one.\r\n\r\nKind regards\r\n\r\nGerard Geerts\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hello Monika,did you find a course of this problem?Regards,Gerard\'", "Comment 3: \'no still analysis\'", "Comment 4: \'Oké! Thanks for a reaction sofar.\'", "Comment 5: \'Reason is full queuesThere is missing DHH item in dhC Service database. Then should be sent information about recipe. We will monitoring list of queue and when it will decrease recipe should appear in DHP!image-2023-01-26-22-35-23-984.png!\'", "Comment 6: \'Hello Monika,This problem could we found it by ourselves by analysis and after that resolve it?Thanks for your support.Kind regards,Gerard\'", "Comment 7: \'For item116270 recipes version 22 and 23 should be in plant now. please verify\'", "Comment 8: \'Hello Gerard", "Comment 9: regarding message queues you can verify with BP here for DHCService whether messages are being processed. !screenshot-1! \']"]\nRelated Issues:\n[]\n\n### End'}
620
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8412\n\n### Instruction:\nKindly remove these documents form buffer as they are inconsequential and preventing the closing of the month\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: \\\'Why don\\\\\\\'t you untick "To buffer" and save this document?!image-2023-01-26-17-33-56-290.png!What should happen next with those PORC documents? Should they be executed or cancelled?Regards!image-2023-01-26-17-33-56-290!\\\'\', "Comment 4: \'!image-1!\'", "Comment 5: \'This is what happens when i try that\'", "Comment 6: \'Hi,Just to confirm:Corrected document is POR-73/21/MAG issued on the 22nd of February", \'Comment 7: 2021 and it has correction under PORC-129/21!image-2023-01-30-08-14-37-231.png!!image-2023-01-30-08-18-47-738.png!PORC-129/21 is issued on the 30th of April 2021 (quantity)!image-2023-01-30-08-17-54-700.png!!image-2023-01-30-08-18-15-937.png!PORC-350/21 was issued on 14th of June 2021 (value\', "Comment 8: but issued first due to gid number)!image-2023-01-30-08-21-50-513.png!!image-2023-01-30-08-22-16-744.png!\'", \'Comment 9: "Hi,We have analised all clipped documents. PORC-129 has been issue incorrect. In our opinion\', \'Comment 10: the best option would be to remove PORC-129 (as it is in buffer\', \'Comment 11: you can delete it here:!image-2023-01-30-09-23-22-114.png|width=831,height=342! )and issue this correction document again. But please\', \'Comment 12: mind this correction will correct current stock.I would like you to clarify one more thing: how document from 2021 interrupts closing months in 2023? Didn\\\'t it interrupted closing month in 2022? Do you receive any error?Regards"\', \'Comment 13: "{color:#212121}First of all i have tried deleting and it doesn\\\'t delete\', \'Comment 14: and we are now closing all our months\', \'Comment 15: we haven\\\'t closed months before this is the first time that is why this issue is now coming up. You can try deleting it and see if it will delete. It wont.{color} ----"\', "Comment 16: \'PORC-129 has been deleted. Now you need to generate correction document again.The issue was caused that first correction PORC-350 was done to element and the next correction PORC-129 was done to PORC-350 (header)", \'Comment 17: not to element.Please4\', "Comment 18: check and let us know if you can proceed further.Regards\'", "Comment 19: \'Trza było ustawić TrN_SpiTyp = 0{code:java}update n set TrN_SpiTyp=0 from cdn.tranag n where trn_gidnumer = 269472{code}\'", "Comment 20: \'you removed just one. i want all removed please\'", "Comment 21: \'Hello,Regarding documents:!image-2023-02-01-07-54-36-429.png!shall we delete them or remove from buffer? I have chnaged clipper type on those documents so you can also remove them by yourself.Regards\'", "Comment 22: \'okay let me remove them and see if they move\'", "Comment 23: \'Sure", "Comment 24: waiting for your feedback then.\'", "Comment 25: \'it works kindly close\'", "Comment 26: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}
621
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8411\n\n### Instruction:\nRecipe 3620.025 v. 15 and 16 are not synchronized to DHP\n\n### Response:\n[\'Comment 1: ["In DHH one ingredient is rounded up to quantity 0this 3014014 - quantity 0 in kg and quantity % 0,0000377 but DHH rounds up to 4 digitsThe recipe\\\'s ingredient cannot have 0 quantity\', \'Comment 2: That is why it is not synchronized to DHPVersion 15 and 16 have the same problemSerge needs to send the recipe again with a slightly bigger quantity - on 14 it was 0,0001The quantity needs to be discussed with Serge. In case You need more then 4 digits then we would have to make the change globally in DHHBest regards\', \'Comment 3: Marta"\', "Comment 4: \'!image!\']"]\nRelated Issues:\n[]\n\n### End'}
622
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8410\n\n### Instruction:\nIntakes are not being sent from DHP to DHC.\r\nAn example we have more intakes that are not synchronized to DHC at all.\r\n\r\nFor example, we have ASN-104/01/2023 and ASN-105/01/2023. Which are identical but one isn’t in DHC and the other one is. \r\n\r\nASN-104/01-23 is done in Vt-381/01/23 and ASN-105/01/2023 is done in VT-380/1/23. Both are closed around the same time. \r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!!image-3!!image-4!!image-5!!image-6!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: " !screenshot-1! {code:java}2023-01-26 14:20:02,688 [5] ERROR Evolution.DHCService.Client.PushServiceOrchestrator [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSC25-JOB1\\\\\\\\Evolution.DHCService.Client\\\\\\\\Evolution.DHCService.Client\\\\\\\\PushServiceOrchestrator.cs:41] - Synchronization error. Service PushVehicleTickets is unable to synchronize2023-01-26 14:20:02,689 [5] ERROR Evolution.DHCService.Client.PushServiceOrchestrator [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSC25-JOB1\\\\\\\\Evolution.DHCService.Client\\\\\\\\Evolution.DHCService.Client\\\\\\\\PushServiceOrchestrator.cs:42] - Evolution.DHCService.Client.Exceptions.TransmissionException: Cannot connect to server ---> System.ServiceModel.CommunicationException: There was an error while trying to serialize parameter http://tempuri.org/:package. The InnerException message was \\\'Enum value \\\'16388\\\' is invalid for type \\\'Evolution.DHCService.Contracts.DeliveryStatus\\\' and cannot be serialized. Ensure that the necessary enum values are present and are marked with EnumMemberAttribute attribute if the type has DataContractAttribute attribute.\\\'. Please see InnerException for more details. ---> System.Runtime.Serialization.SerializationException: Enum value \\\'16388\\\' is invalid for type \\\'Evolution.DHCService.Contracts.DeliveryStatus\\\' and cannot be serialized. Ensure that the necessary enum values are present and are marked with EnumMemberAttribute attribute if the type has DataContractAttribute attribute. at System.Runtime.Serialization.EnumDataContract.WriteEnumValue(XmlWriterDelegator writer\', \'Comment 4: Object value) at System.Runtime.Serialization.EnumDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter\', \'Comment 5: Object obj\', \'Comment 6: XmlObjectSerializerWriteContext context) at System.Runtime.Serialization.XmlObjectSerializerWriteContext.WriteDataContractValue(DataContract dataContract\', \'Comment 7: XmlWriterDelegator xmlWriter\', \'Comment 8: Object obj\', \'Comment 9: RuntimeTypeHandle declaredTypeHandle){code} !screenshot-2! "\', "Comment 10: \'Jest jedna taka dostawa z oczekującym VT{code:java}SELECT * FROM [DHP_NL_PROD].[dbo].[Delivery] where Del_Status=16388 and del_vteid in(SELECT [Vex_VtEId] FROM [DHP_NL_PROD].[dbo].[VehicleTicketExport] where Vex_Ticket is not null){code}del_id=268651\'", "Comment 11: \'{code:java}SELECT *--update d--set del_status=4 FROM [DHP_NL_PROD].[dbo].[Delivery] d where Del_Status=16388 and del_vteid in(SELECT [Vex_VtEId] FROM [DHP_NL_PROD].[dbo].[VehicleTicketExport] where Vex_Ticket is not null){code}{code:java}\\\\t UPDATE R\\\\t SET RGM_STATUS=4 FROM [DHP_NL_PROD].[dbo].[RegisterMappings] R WHERE RgM_DelId IN(268651){code}DEL_ID=268445{code:java}UPDATE RSET RgM_Status=4 FROM [DHP_NL_PROD].[dbo].[RegisterMappings] R WHERE RgM_DelId IN( SELECT Del_ID--update d--set del_status=4 FROM [DHP_NL_PROD].[dbo].[Delivery] d where del_vteid in(SELECT [Vex_VtEId] FROM [DHP_NL_PROD].[dbo].[VehicleTicketExport] where Vex_Ticket is not null)) AND RgM_Status<>4{code}{code:java}select d.del_id", "Comment 12: d.Del_Status --update d--set d.Del_Status=4from dbo.VehicleTicketElementRelease r--inner join dbo.RegisterMappings m on m.rgm_id = r.VeW_RgMIdinner join dbo.Delivery d on d.del_id = r.VeW_DelIdwhere r.VeW_VtEId in (SELECT [Vex_VtEId] FROM [DHP_NL_PROD].[dbo].[VehicleTicketExport] where Vex_Ticket is not null) --and m.RgM_Status <> 4 and d.Del_Status <> 4{code}{code:java}268587update r set RgM_Status=4 FROM [DHP_NL_PROD].[dbo].[RegisterMappings] r where RgM_DelId in(select distinct d.del_id--update d--set d.Del_Status=4from dbo.VehicleTicketElementRelease r--inner join dbo.RegisterMappings m on m.rgm_id = r.VeW_RgMIdinner join dbo.Delivery d on d.del_id = r.VeW_DelIdwhere r.VeW_VtEId in (SELECT [Vex_VtEId] FROM [DHP_NL_PROD].[dbo].[VehicleTicketExport] where Vex_Ticket is not null)) and RgM_Status=16388{code}\'", "Comment 13: \'Currently VTs should be synchronized,the reason was wrong status for deliveries.Please check.\'", "Comment 14: \'What was the status?To what status is it changed?\'", "Comment 15: \'The status of Delivery was changed to Delivery Finished.Please", "Comment 16: let us know if it is working fine no for you and we can close this task.Regards\'", "Comment 17: \'What is the reason this went to “wrong status” There is no diference with other VT in DHP\'", "Comment 18: \' Wrong status in DHC in Shipping notices?\'", "Comment 19: \'Hello", "Comment 20: more precisely delivery status from the dhp level - as an ID that is not synchronized to DHC.\'", "Comment 21: \'[[email protected]]potrzebujemy na RCA i 8h na analize.\'", "Comment 22: \'RCA will be created but developers need 8 working hours for analysis. Please accept.\'", "Comment 23: \'There will be costs for this investigation?\'", "Comment 24: \'Yes. The costs will be on your side unless it happens it is an application bug", "Comment 25: but it seems to be not for now.\'", "Comment 26: \'Hello", \'Comment 27: RCA has been created DGS-8619\', "Comment 28: but developers need 8 working hours for analysis.We are closing this task.Regards\']"]\nRelated Issues:\n[\'DGS-8619\']\n\n### End'}
623
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8409\n\n### Instruction:\nI can not delete PI 0645 ID 88376. \r\n\r\nThis is after deleting SI 940. Can you fix this? See error below. Please inform Richard and Nancy also. \n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hello,This Purchase Invoice is on Saldo to Pay\', \'Comment 4: that\\\'s why it\\\'s not possible to delete it from Intense.Firstly Purchase Invoice should be deleted from Saldo to Pay document and then it will be possible to deletePI 0645 ID 88376Please verify and check that is possible.Regards"\', "Comment 5: \'Thanks", "Comment 6: please close this one\']"]\nRelated Issues:\n[]\n\n### End'}
624
{'prompt': "Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8408\n\n### Instruction:\nMeeting on Client request \n\n### Response:\n['Comment 1: []']\nRelated Issues:\n[]\n\n### End"}
625
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8407\n\n### Instruction:\nHi,\r\nWe have some Job Orders with missing cost of some raw materials (example JO 154/23/tema)\r\n\r\nHow do we fixed them and how do we ensure they don happen again.\r\n\r\nAlso all the cost are the same is there a reason ?\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!screenshot-1!PLR: 0722200123007!image-2023-01-26-18-16-53-078.png!!image-2023-01-26-18-17-21-294.png!\'", \'Comment 4: "Po godzinie stworzenia PLR czyli 11:36{code:java}2023-01-20 11:35:59,853 [14] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution finished2023-01-20 11:35:59,884 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution finished2023-01-20 11:35:59,884 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution started2023-01-20 11:35:59,916 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution finished2023-01-20 11:35:59,916 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.WarehouseMovements.WarehouseMovementProcessor [(null)] - WarehouseMovementProcessor execution started2023-01-20 11:35:59,947 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.WarehouseMovements.WarehouseMovementProcessor [(null)] - WarehouseMovementProcessor execution finished2023-01-20 11:36:14,932 [14] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 5836922023-01-20 11:36:15,026 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Bussines Partner Vendor Item Code message from trigger - 992023-01-20 11:36:15,026 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Bussines Partner Vendor Item Code data downloaded - 992023-01-20 11:36:15,026 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Sending Bussines Partner Vendor Item Code message - Evolution.ErpIntegrator.CdnXL.Interfaces.Dictionaries.BusinessPartners.XLBusinessPartnerItemCode2023-01-20 11:36:15,042 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - ItemBusinessPartnerCodeChange Message mapping... (ID=ID - -99)2023-01-20 11:36:15,042 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - ItemBusinessPartnerCodeChange Message mapped... (ID=ID - -99)2023-01-20 11:36:15,042 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - ItemBusinessPartnerCodeChange Message sent... (ID=ID - -99)2023-01-20 11:36:15,932 [14] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 5836922023-01-20 11:36:23,307 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Order message from trigger - ID - 265332023-01-20 11:36:23,369 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Order data downloaded - SO-256/23/ATMK2023-01-20 11:36:23,369 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Sending Order message - SO-256/23/ATMK2023-01-20 11:36:23,369 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapping.... (Firma:1339393 - TYP:960/NUMER:26533/LP:0\', \'Comment 5: SO-256/23/ATMK)2023-01-20 11:36:23,400 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapped (Firma:1339393 - TYP:960/NUMER:26533/LP:0\', \'Comment 6: SO-256/23/ATMK)2023-01-20 11:36:23,400 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message send (Firma:1339393 - TYP:960/NUMER:26533/LP:0\', \'Comment 7: SO-256/23/ATMK)2023-01-20 11:36:28,400 [10] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution started2023-01-20 11:36:28,822 [10] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-598/12/2022/AC [Id: eb447291-b547-440d-8692-03c7b93d34e7]2023-01-20 11:36:28,822 [10] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-20 11:36:28,853 [10] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-20 11:36:28,932 [14] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution started2023-01-20 11:36:28,978 [14] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL transaction created\', \'Comment 8: token ID - 75-4l-kPc1ORJNhISD]L^M5---.>CM--2023-01-20 11:36:29,010 [14] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: f7fa08ba-027e-456b-9c21-edf094e7d3d2 (1101011 - 29960.000000)2023-01-20 11:36:29,088 [14] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Found 0 WMR- () for order IO-3879/222023-01-20 11:36:29,103 [14] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL transaction rollbacked\', "Comment 9: token ID - 75-4l-kPc1ORJNhISD]L^M5---.>CM--2023-01-20 11:36:29,103 [14] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-01-20 11:36:29,103 [14] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-01-20 11:36:29,119 [14] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Can\'t find WMR- document to map to WMR+Evolution.ErpIntegrator.ERP.Interfaces.Exceptions.WarehouseMovementReleaseNotMappedException: Can\'t find WMR- document to map to WMR+ at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.MapWarehouseMovementRelease(VehicleTicket vehicleTicket", \'Comment 10: InternalOrder internalOrder\', \'Comment 11: WarehouseMovementReceipt warehouseMovementReceipt) at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.OnExecute(VehicleTicket vehicleTicket)2023-01-20 11:36:29,150 [14] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution finished2023-01-20 11:36:29,150 [10] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-261/1/2023/AC [Id: c8d31e77-918c-40ee-b1a6-0870c1913538]2023-01-20 11:36:29,150 [10] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-20 11:36:29,182 [10] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-20 11:36:29,307 [15] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution started2023-01-20 11:36:29,338 [15] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL transaction created\', \'Comment 12: token ID - YZ8I-b`ET1ShDdNkEeUDf-5---/VH=--2023-01-20 11:36:29,385 [15] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: f805aed1-6403-4e89-9b0d-b3d1129ebaf3 (1002200 - 9000.000000)2023-01-20 11:36:29,447 [15] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Found 0 WMR- () for order IO-82/232023-01-20 11:36:29,447 [15] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-01-20 11:36:29,463 [15] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-01-20 11:36:29,463 [15] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL transaction rollbacked\', "Comment 13: token ID - YZ8I-b`ET1ShDdNkEeUDf-5---/VH=--2023-01-20 11:36:29,478 [15] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Can\'t find WMR- document to map to WMR+Evolution.ErpIntegrator.ERP.Interfaces.Exceptions.WarehouseMovementReleaseNotMappedException: Can\'t find WMR- document to map to WMR+ at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.MapWarehouseMovementRelease(VehicleTicket vehicleTicket", \'Comment 14: InternalOrder internalOrder\', \'Comment 15: WarehouseMovementReceipt warehouseMovementReceipt) at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.OnExecute(VehicleTicket vehicleTicket){code}"\', \'Comment 16: "Hi,Probably JO was reopened\', "Comment 17: questioned itam was added (but lack of price hasn\'t been noticed) and documents of internal release were generated. To solve this case", \'Comment 18: you can use function Settlinig Job Order - the price has been corrected. Closin JO also should correct the price of additionally added item.Regards!image-2023-01-30-10-00-24-610.png!"\', "Comment 19: \'Thank you.It worked Kindly close the ticket\'", "Comment 20: \'Thank you\'", "Comment 21: \'Hi", "Comment 22: have a JO with the same issue but the procedure would not work for this.\'", "Comment 23: \'Kindly open and let us resolve it JO 238/23/TEMA\'", "Comment 24: \'Hi,Please", "Comment 25: create new task for this issue. Thank you in advance.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
626
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8406\n\n### Instruction:\nPlease help to check PLR 4361170123050 in Hai Phong Plant ( 0436) .\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Według historii !screenshot-1! zostało przyjęte 975kg\', \'Comment 4: potem wydane x2 i przyjęta różnica - JORDYN:{code:java}SELECT [Created] ,[Event] ,[EventType] ,[UserName] FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits] where AggregateId=\\\'0EC7F20D-41CA-49C6-A835-9C06D4ED072A\\\' order by created{code} !screenshot-2! !screenshot-3! !screenshot-4! !image-2023-01-26-07-49-38-211!"\', "Comment 5: \'A delivery for PLR was created", "Comment 6: then issued for the following releases:-518,089kg-95,238kgThen operator JORDYN made another intake in relation to this delivery(created from this PLR) for 613,327.You can see it here !screenshot-5! \'", "Comment 7: \'May you help more specific steps how to do that?if as your motioned below", "Comment 8: we will Pre-produce that and make user avoid mistake\'", "Comment 9: \'Hello", "Comment 10: in reference to the answer additional changes have been made in the application version 8.3 that should prevent this type of situations.\'", "Comment 11: \'Hi Piotr GaczorekYou can closed this ticket. Thank u .\']"]\nRelated Issues:\n[]\n\n### End'}
627
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8405\n\n### Instruction:\nWe have 2 sales order duplicated on DHC. We notice the status was not updated to DHP, so we sent again the sale order, but now we have 2 lines for the same SO. \r\nOVE-052063\r\nOVE-028066\r\nCould you check why sytem duplicated the SO and didn\'t updated the version?\r\n\r\nThank you\r\n\r\n\r\n\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'sorry", \'Comment 3: I added wrong\', \'Comment 4: not update the version\', "Comment 5: but update the sales order status.\'", "Comment 6: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 7: \'Różnica w mapowaniu dla ErpIDCompany !screenshot-1! !screenshot-2! \'", "Comment 8: \'Hello", \'Comment 9: orders have now CompanyID\', "Comment 10: looks like currently a field is sent from ERP - have there been any changes? !screenshot-4! these two orders previously had ERPidcompany=10!image-2023-01-26-13-54-33-498!\'", \'Comment 11: "Hello Piotr,these orders were created more than a year ago\', \'Comment 12: so maybe yes\', \'Comment 13: we had some integration update. Could you fix the status because if integration changed we can\\\'t update?OVE-052063 CancelledOVE-028066 Executed"\', "Comment 14: \'I changed the status for orders in DHC & sent them to plant", "Comment 15: please check.\'", "Comment 16: \'Could you please confirm if we can close this task?Regards\'", \'Comment 17: "Hi Piotr,I checked and it\\\'s correct. Thank you."\', "Comment 18: \'Hi Priscyla", "Comment 19: thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'}
628
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8404\n\n### Instruction:\n W dhc zalega vt-1763/1/2023/G oraz vt-1679\r\nvt-1769 posiada taki komunikat Komunikat” Error of type XLApiException has been thrown (XLNowyDokument:2017).\r\n\r\nAPI Name - XLNowyDokument\r\n\r\nAPI Result - 2017\r\n\r\nFlags - 240\r\n\r\nBŁĘDY:|Błąd konwersji/generowania subelementu: [00001 DT219X02S-W00] Zabrakło ilości (nie udało się pobrać towaru lub wymuszono realizacje całości). (NowyDokument-17)”\r\n\r\nNatomiast vt-1679 posiada : Error of type XLApiException has been thrown (XLNowyDokument:2017).\r\nAPI Name - XLNowyDokument\r\nAPI Result - 2017\r\nFlags - 240\r\nBŁĘDY:|Błąd konwersji/generowania subelementu: [00001 0551] Zabrakło ilości (nie udało się pobrać towaru lub wymuszono realizacje całości). (NowyDokument-17)\r\n\r\nIlosci z ZW w CDN z tym co jest w DHC zgadzaja sie . Nie widac tez zadnych rezerwacji które blokowaly by towar.\r\n\r\nProsba o weryfikacje i rozwiazanie problemu\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'", "Comment 3: \'Ok but please correct this vt today\'", "Comment 4: \'Sure", "Comment 5: working on it. Thank you\'", "Comment 6: \'{code:java}2023-01-25 18:34:51,385 [34] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-1763/1/2023/G [Id: c68225ae-adbf-4cf6-9d94-61690e57546f]2023-01-25 18:34:51,385 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-25 18:34:51,401 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-25 18:34:51,668 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution started2023-01-25 18:34:51,889 [13] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL transaction created", \'Comment 7: token ID - PVY8cX5VHQ;YjVi`^VEN9=5---.hE]--2023-01-25 18:34:51,920 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: 6195b8b8-b779-4b95-8bbe-3dfd92a75d33 (DT219X02S-W00 - 0,125000)2023-01-25 18:34:51,920 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: 6250c1b2-5fd5-4fb4-8120-1387fd7a7a7b (DT219X02S-W00 - 0,925000)2023-01-25 18:34:51,920 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: 7dc34b1f-96ae-467f-b2af-8c8434503610 (DB0B1X00S-V00 - 3,000000)2023-01-25 18:34:51,935 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: a30d4c74-e8a3-41ad-8f77-deba52ed75bb (DB0A1X00S-V00 - 7,000000)2023-01-25 18:34:51,935 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: dfbc4a2e-3e92-4b4b-94ba-02beb1563fb9 (DB0A1X00S-V00 - 3,000000)2023-01-25 18:34:51,935 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: e49b9a60-54d3-4b15-a520-dd0ffa18db3f (DT1D4X00G-W00 - 6,000000)2023-01-25 18:34:51,967 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Found only one WMR- (MMW-127/01/23/M) for order ZW-176/01/23/G2023-01-25 18:34:51,967 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Maping to WMR- MMW-127/01/23/M [ID = Firma:246785 - TYP:1603/NUMER:12707009/LP:0]2023-01-25 18:34:51,967 [13] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.LoginHelper [(null)] - Changing context to 14322023-01-25 18:34:57,795 [13] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.LoginHelper [(null)] - Contex changed to 14322023-01-25 18:34:57,795 [13] DEBUG Evolution.ErpIntegrator.CdnXL.Interfaces.Documents.ExternalOrderTransactions.XLAPIExternalOrderTransaction [(null)] - NB Flag - Class = Net\', "Comment 8: API = N2023-01-25 18:34:59,323 [13] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.ExternalOrderTransactions.CdnXL2021ExternalOrderTransactionRepository [(null)] - Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2021.XLApiException has been thrown (XLNowyDokument:2017).API Name - XLNowyDokumentAPI Result - 2017{code}\'", "Comment 9: \'{code:java}2023-01-25 18:25:35,644 [62] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-1679/1/2023/G [Id: d00f4aff-b4bc-414f-91b1-113abd617e07]2023-01-25 18:25:35,644 [62] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-25 18:25:35,660 [62] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-25 18:25:35,738 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution started2023-01-25 18:25:35,785 [34] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL transaction created", \'Comment 10: token ID - cQYDUi5OVAO_USkcM=_76M5----kE---2023-01-25 18:25:35,832 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: c0ff0ed2-3151-4762-952a-e6fde6281d64 (0551 - 22,020000)2023-01-25 18:25:35,863 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Found only one WMR- (MMW-88/01/23/S) for order ZW-168/01/23/G2023-01-25 18:25:35,863 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Maping to WMR- MMW-88/01/23/S [ID = Firma:246785 - TYP:1603/NUMER:12702815/LP:0]2023-01-25 18:25:35,863 [34] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.LoginHelper [(null)] - Changing context to 14322023-01-25 18:25:41,328 [34] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.LoginHelper [(null)] - Contex changed to 14322023-01-25 18:25:41,328 [34] DEBUG Evolution.ErpIntegrator.CdnXL.Interfaces.Documents.ExternalOrderTransactions.XLAPIExternalOrderTransaction [(null)] - NB Flag - Class = Net\', \'Comment 11: API = N2023-01-25 18:25:42,219 [34] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.ExternalOrderTransactions.CdnXL2021ExternalOrderTransactionRepository [(null)] - Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2021.XLApiException has been thrown (XLNowyDokument:2017).API Name - XLNowyDokumentAPI Result - 2017Flags - 240BĊDY:|Bӹd konwersji/generowania subelementu: [00001 0551] Zabrakԯ iloݣi (nie udaԯ siꡰobra桴owaru lub wymuszono realizacje caԯݣi). (NowyDokument-17) at Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.ExternalOrderTransactions.CdnXL2021ExternalOrderTransactionRepository.CreateHeader(XLExternalOrderTransaction documentHeader) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2021\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2021ExternalOrderTransactionRepository.cs:line 792023-01-25 18:25:42,219 [34] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-01-25 18:25:42,219 [34] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-01-25 18:25:42,219 [34] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2021.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -12023-01-25 18:25:42,219 [34] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL transaction rollbacked\', \'Comment 12: token ID - cQYDUi5OVAO_USkcM=_76M5----kE---2023-01-25 18:25:42,250 [34] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Error of type XLApiException has been thrown (XLNowyDokument:2017).API Name - XLNowyDokumentAPI Result - 2017Flags - 240BĊDY:|Bӹd konwersji/generowania subelementu: [00001 0551] Zabrakԯ iloݣi (nie udaԯ siꡰobra桴owaru lub wymuszono realizacje caԯݣi). (NowyDokument-17)Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2021.XLApiException has been thrown (XLNowyDokument:2017).API Name - XLNowyDokumentAPI Result - 2017Flags - 240BĊDY:|Bӹd konwersji/generowania subelementu: [00001 0551] Zabrakԯ iloݣi (nie udaԯ siꡰobra桴owaru lub wymuszono realizacje caԯݣi). (NowyDokument-17) at Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.ExternalOrderTransactions.CdnXL2021ExternalOrderTransactionRepository.CreateHeader(XLExternalOrderTransaction documentHeader) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2021\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2021ExternalOrderTransactionRepository.cs:line 167 at Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.WarehouseMovements.CdnXL2021WarehouseMovementReceiptRepository.CreateHeader(XLWarehouseMovementReceipt warehouseMovementReceipt) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2021\\\\\\\\Documents\\\\\\\\WarehouseMovements\\\\\\\\CdnXL2021WarehouseMovementReceiptRepository.cs:line 256 at Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.WarehouseMovements.CdnXL2021WarehouseMovementReceiptRepository.CreateDocumentWithElements(XLWarehouseMovementReceipt warehouseMovementReceipt\', \'Comment 13: Boolean confirmDoc\', \'Comment 14: Boolean forceQuantity) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2021\\\\\\\\Documents\\\\\\\\WarehouseMovements\\\\\\\\CdnXL2021WarehouseMovementReceiptRepository.cs:line 0 at Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.WarehouseMovements.CdnXL2021WarehouseMovementReceiptRepository.CreateDocumentWithElements(WarehouseMovementReceipt warehouseMovementReceipt\', \'Comment 15: Boolean confirmDoc\', "Comment 16: Boolean forceQuantity) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2021\\\\\\\\Documents\\\\\\\\WarehouseMovements\\\\\\\\CdnXL2021WarehouseMovementReceiptRepository.cs:line 233 at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.OnExecute(VehicleTicket vehicleTicket)2023-01-25 18:25:42,281 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution finished2023-01-25 18:25:42,281 [62] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Extension started - VT-1679/1/2023/G [Id: d00f4aff-b4bc-414f-91b1-113abd617e07] Evolution.ErpIntegrator.Extensions.PackagesAndShipments.PackagesAndShipmentGenerator2023-01-25 18:25:42,281 [62] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Package generation skipped - no POR/PORI documents found VT-1679/1/2023/G2023-01-25 18:25:42,281 [62] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Extension completed - VT-1679/1/2023/G [Id: d00f{code}\'", "Comment 17: \'VT-1763/1/2023/GNa pozycji zamówienia jest mniejsza ilość niż na mmp!image-2023-01-25-19-07-39-646.png!!image-2023-01-25-19-08-12-949.png!!image-2023-01-25-19-09-00-832.png!\'", "Comment 18: \'vt-1679Na dostawach jest:!image-2023-01-25-19-22-22-916.png!Co daje 22,02. Czyli więcej niż na zamówieniu. Do weryfikacji.!image-2023-01-25-19-12-47-259.png!!image-2023-01-25-19-13-41-237.png!!image-2023-01-25-19-14-29-241.png!\'", "Comment 19: \'W ZW - 168 jest zadeklarowane 25 t czyli wiecej niz na dostawach \'", "Comment 20: \'Skoro jest więcej niż na dostawach / zasobach (w XLu są tylko te dwie dostawy dla tego towaru)", "Comment 21: to skąd ma pobrać?\'", "Comment 22: \'Ok ilosc na ZW została skorygowana - błąd pojawia sie nadal\'", "Comment 23: \'Na ZW ilosc moze byc wieksza niz na vt. Nie moze byc mniejsza.\'", "Comment 24: \'1763 jest już generated!image-2023-01-26-12-25-27-769.png!\'", "Comment 25: \'Jeśli chodzi o vt-1679", "Comment 26: potrzebujemy zrobić ręcznie dokument MMP z poziomu XLa i spiąć go od strony bazy.Proszę o akceptację\'", "Comment 27: \'ok", "Comment 28: działajcie,\'", "Comment 29: \'Jeśli chodzi o vt-1679", \'Comment 30: element jest anulowany\', "Comment 31: przywrócić go i podpiąć MMP? MMP zostało wygenerowane do MMW!image-2023-01-27-12-47-29-448.png!\'", \'Comment 32: "{code:java}SELECT * FROM [Evolution_DHCountry].[dbo].[VehicleTicketElementERPDocuments] where VehicleTicketElementId = \\\'C0FF0ED2-3151-4762-952A-E6FDE6281D64\\\' or VehicleTicketElementId = \\\'0938DB7A-90F8-40C5-A761-533F284ACF74\\\'select Status\', "Comment 33: * from VehicleTickets where DocumentNumber = \'1679/1/2023/g\' or DocumentNumber = \'1153/1/2023/s\'select * from VehicleTicketElements where VehicleTicketId in (\'D00F4AFF-B4BC-414F-91B1-113ABD617E07\'", \'Comment 34: \\\'963560FA-3D77-4814-9FC3-24363F22B980\\\'){code}"\', "Comment 35: \'Jeśli chodzi o vt-1679", \'Comment 36: element jest anulowany\', "Comment 37: przywrócić go i podpiąć MMP? MMP zostało wygenerowane do MMW\'", "Comment 38: \'Jeśli chodzi o vt-1679", \'Comment 39: element jest anulowany\', "Comment 40: przywrócić go i podpiąć MMP? MMP zostało wygenerowane do MMW\'", "Comment 41: \'Any feedback?\'", "Comment 42: \'Tak podepnij prosze\'", "Comment 43: \'Gotowe. Proszę o weryfikację.\'", "Comment 44: \'Task to close\']"]\nRelated Issues:\n[]\n\n### End'}
629
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8403\n\n### Instruction:\nSince recently, we automatically see the SR\'s behind the Onbase link automatically, great! However, I have 2 questions remaining because in the first place, the SR that is showed is quite small: \r\n1. Can the note section, right to the SR, be hidden automatically, because there never is a note?\r\n2. Could the square where the SR is shown be a bit bigger? Together with the hide of the note section, the SR can be bigger from the first moment, without having to zoom in? \r\n\r\nThis modification (if possible) would be for both MAS BE and MAS NL (Mitch\'s demand)\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hi [[email protected]],regarding your question\', "Comment 4: the answers below:1. The note section is part of OneBase functionality. We can\'t set default view for that", "Comment 5: because it is works just as web browser.2. We can\'t change size", \'Comment 6: because in the views on documents we can only use predefinied layouts. Used layout on SR is splited by three identical size area without possible to change width.!image-2023-01-30-13-27-53-660.png!Best regards,Grzegorz"\', "Comment 7: \'Hello Grzegorz", \'Comment 8: pity that this is not possible\', "Comment 9: but understandable reading your explanation. thank you for the update.\'", \'Comment 10: "[[email protected]],thank you. Have a nice day.I\\\'m closing the task.Best regards,Grzegorz"]\']\nRelated Issues:\n[\'DGS-8317\']\n\n### End'}
630
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8402\n\n### Instruction:\nThe VT of this call-off is closed, but it is not received in the ERP: Can you check if it\'s synced to DHC and ERP and check what goes wrong? Thanks\n\n### Response:\n["Comment 1: [\'!afbeelding-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-01-25-15-13-43-401.png!\'", "Comment 4: \'Header:!image-2023-01-25-15-24-42-359.png!!image-2023-01-25-15-22-16-329.png!!image-2023-01-25-15-24-42-359!\'", "Comment 5: \'!image-2023-01-25-15-25-05-946.png!\'", "Comment 6: \'Dear Thomas,I have resent this Shipping Notice", \'Comment 7: but I can see status both in DHP and DHC is accepted. Is that correct?!image-2023-01-25-15-42-29-455.png!!image-2023-01-25-15-42-47-754.png!Please\', "Comment 8: verify if ASN arrived to Milas.Regards\'", "Comment 9: \'VT-436 for this ASN", \'Comment 10: in DHC has staus hold. Probably this stops from arriving. Please\', "Comment 11: check VT!image-2023-01-25-15-48-09-953.png!\'", \'Comment 12: "VT\\\'s are all getting status hold\', \'Comment 13: I guess it\\\'s not related? Resending unfortunately didn\\\'t solve the problem"\', "Comment 14: \'!image-2023-01-25-17-01-24-421.png!\'", "Comment 15: \'Please", "Comment 16: check now and let me know if documents arrived to MilasRegards\'", "Comment 17: \'[[DHC] PONOWNE WYSŁANIE VT DO MILAS|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bDHC%5d%20PONOWNE%20WYS%C5%81ANIE%20VT%20DO%20MILAS&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{4EBEDAA7-0DC4-410F-A617-93B6B59B31B6}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHC%5D%20PONOWNE%20WYS%C5%81ANIE%20VT%20DO%20MILAS%7C4EBEDAA7-0DC4-410F-A617-93B6B59B31B6%2F%29])\'", "Comment 18: \'Hi,Please", "Comment 19: check now and let me know if documents arrived to MilasRegards\'", \'Comment 20: "I think we found the reason now why it\\\'s not arriving. Ticket can be closed"\', "Comment 21: \'Thank you.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
631
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8401\n\n### Instruction:\nHi\r\nUrgent from Aneta\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Dzień dobry,Proszę o wskazanie w ramach jakiego szablonu zestawienia są wyliczane i za jaki okres obrachunkowy (cały 2022 czy częściowy)?Dodatkowo", \'Comment 3: czy zanim pojawił się problem z przeliczaniem zestawień\', "Comment 4: czy były dokonywane jakieś modyfikacje w ramach szablonu lub definicji pozycji w ramach wskazanego zestawienia?Pozdrawiam\'", "Comment 5: \'Please verify if now working faster\'", "Comment 6: \'Otrzymałam właśnie informację", "Comment 7: że zgłoszenie zostało rozwiązane w ramach DGS-8400.Proszę po potwierdzeniePozdrawiam\'", "Comment 8: \'tak", "Comment 9: Aneta dzwoniła że ruszyło\'", "Comment 10: \'To zamykamy?\'", "Comment 11: \'czekam na potwierdzenie od Anety\'", "Comment 12: \'!image-1!\'", "Comment 13: \'Jakie indeksy zostały dodane? \'", "Comment 14: \'tabela[CDNXL_DEHEUS].[CDN].[Stany]missing_index_3609402_3609401 missing_index_3609404_3609403\']"]\nRelated Issues:\n[]\n\n### End'}
632
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8400\n\n### Instruction:\nHi\r\n\r\nTask from Iwona\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'According to call with Emlia Markiewicz she has been informed how to coorrect definitions of reports. Can I close this issue?\'", "Comment 3: \'yep", "Comment 4: to close. Many thanks.\']"]\nRelated Issues:\n[]\n\n### End'}
633
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8399\n\n### Instruction:\nWe would like to send the Financial Statement and Saldo-2-Pay with one click in Outlook. Preferebly directly to the right representative.\r\n\r\nCould we think of a functionality about this?\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Hello\', \'Comment 3: # We could think about some solution maybe like this:From Saldo to pay document it could be possible to execute action (button or from lightning) and printout for S2P and Financial statement will be generated in .pdf files and attached to S2P document in Intense. Then Intense will open preview window like e-mail message and user can preview message and edit all data: Subject\', \'Comment 4: e-mail\', "Comment 5: attachments (e-mail will be filled from customer card where is e-mail address). After editing and confirming in this winow and clicks \'Send\' button", "Comment 6: e-mail with attachments will be sent.This solution requires configuration of e-mail or e-mails (depending from which e-mail adresses should it be sent) in Intense. There could be also some issues when there is politics of changing password in De Heus (when password is changed we need also change password in Intense configuration). # There is also some option to make printout and printout will be attached to e-mail and message will open in Outlook application.In these case when users working on terminal and there is no Outlook application it will be useless becasue it couldn\'t be possible to open Outlook.In each case we should verify details of the solution and how to handle it", \'Comment 7: but we can think about some solution."\', "Comment 8: \'Because of e-mail password changes I prefer the second option.Can we meet for this next Friday?\'", \'Comment 9: "Yes\', "Comment 10: we can meet on next friday. It could be hard to do 2nd option if users don\'t have Outlook on terminal", \'Comment 11: but we can see what could be possible. I\\\'ll try to show possibilites in Intense with e-mail sending."\', \'Comment 12: "After meeting confirmed that should be realized 1st option on test environment.{quote} # We could think about some solution maybe like this:From Saldo to pay document it could be possible to execute action (button or from lightning) and printout for S2P and Financial statement will be generated in .pdf files and attached to S2P document in Intense. Then Intense will open preview window like e-mail message and user can preview message and edit all data: Subject\', \'Comment 13: e-mail\', "Comment 14: attachments (e-mail will be filled from customer card where is e-mail address). After editing and confirming in this winow and clicks \'Send\' button", \'Comment 15: e-mail with attachments will be sent.This solution requires configuration of e-mail or e-mails (depending from which e-mail adresses should it be sent) in Intense. There could be also some issues when there is politics of changing password in De Heus (when password is changed we need also change password in Intense configuration).{quote}We need information about: * e-mail template which should be generated and sent to customer * e-mail accounts for users - should it be sent always from one global mail account like [[email protected]|mailto:[email protected]]or each user should have configured in Intense individual mail account (in case if there will be individual mail accounts for each user and password for this e-mail changes\', \'Comment 16: it will be needed to change password for e-mail account in Intense also)"\', "Comment 17: \'[[email protected]|mailto:[email protected]] (ask for password to Martijn)Email template:Beste klant,Bij deze ontvangt u de afrekening. In de bijlage een technisch overzicht van het koppel en de betalingsspecificatie.Bij vragen of opmerkingen kunt u contact opnemen met de specialist.Met vriendelijke groeten,De dierenadministratiePlease analyse the possibilities for translation.\']"]\nRelated Issues:\n[\'DGS-7649\']\n\n### End'}
634
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8398\n\n### Instruction:\nIs it possible to see the job orders from which an SOR picks its stock quantity from? if yes how?\n\n### Response:\n["Comment 1: [\'Can you be more specific about this request?JO takes resources from delivery documents created from receipts by PLR and VT.SOR documents are generated for VT releases.\'", "Comment 2: \'Yes so basically what i am trying to say is for example", "Comment 3: the job order with number JO 1/23 is for 7700-B50 with quantity 1000kg and an SO has been created to sell 7700-b50 is there a way to find out if the SOR document from the SO can show whether the quantity for 7700-b50 was consumed from JO 1/23\'", "Comment 4: \'please stop working on this and close\']"]\nRelated Issues:\n[]\n\n### End'}
635
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8397\n\n### Instruction:\nShipping Notice 98_L000112306 is in DHC but isn\'t arriving in DHP. Can you please check? \n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'!image-2023-01-25-10-04-26-677.png!\'", "Comment 3: \'!image-2023-01-25-10-07-02-201.png!\'", "Comment 4: \'This SN is in DHP but Executiondateis set to the year 1900 - can it be corrected?!image-2023-01-25-10-12-56-494.png!\'", \'Comment 5: "Hi Piotr\', "Comment 6: thanks for your reply. It\'s strange", \'Comment 7: because nowhere is date 1/1/1900 communicated. I have exported the SN again\', \'Comment 8: let\\\'s see what happens"\', "Comment 9: \'I see the date is now correct in DHC\'", "Comment 10: \'And now it is in DHP as well. Thanks", "Comment 11: you can close this request.\'", "Comment 12: \'Thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'}
636
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8396\n\n### Instruction:\nHello,\r\n\r\nHow can i delete multiple accounts from the charts of accounts?\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hello,Unfortunatelly", \'Comment 3: it is not possible to delete multiple accounts with one click. You need to delete accounts one by one starting from the lowest level for example:!image-2023-01-24-19-03-03-965.png!What is more\', \'Comment 4: if there are some settlements in current period for this account\', "Comment 5: the system will not allow you to delete the account.Regards\'", "Comment 6: \'Thank you please\']"]\nRelated Issues:\n[]\n\n### End'}
637
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8395\n\n### Instruction:\ncannot confirm PLR 0672230123016 and 0672240123001. the error message does not give an indication as to what the issue might be. \r\n\r\nwe have checked the logs around this date no error message related. \r\nno raw materials are archived. \r\nmaintenance shows that the order, recipe, item etc. are in every module they need to be in. \r\nwe restarted services IntegrationPCS and Production nothing. \r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'>> confiremd PLR0672230123016id=41616471-4073-4d43-9413-13290367340d>> LOG Prod{code:java}2023-01-24 18:37:54 (32901eea-9335-4778-84b9-72ca6c750256/Plant.Prod.BusinessLogic/SAKDSRV04/18592/210) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateProductionLotCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateProductionLotCommand) methodSystem.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 313 --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId", \'Comment 4: AggregateId businessUnitId\', \'Comment 5: Quantity productionQuantity\', \'Comment 6: IEnumerable`1 settlementData\', \'Comment 7: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 165 at Castle.Proxies.Invocations.IStockEngineApi_UpdateReservationsAndConfirmProductionLot.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Castle.Proxies.IStockEngineApiProxy.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 8: AggregateId businessUnitId\', \'Comment 9: Quantity productionQuantity\', \'Comment 10: IEnumerable`1 settlementData\', \'Comment 11: IEnumerable`1 dosingSiloItemData) at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 12: ConfirmProductionLotActionData data\', \'Comment 13: IEnumerable`1 reservations\', \'Comment 14: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 88 at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 334 at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateProductionLotCommandHandler.Handle(UpdateProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateProductionLotCommandHandler.cs:line 38 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-01-24 18:37:54 (/Plant.Prod.BusinessLogic/SAKDSRV04/18592/195) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/productionLot/update" responded 500 in 859.0456 ms{code}>> Request Log{code:java}2023-01-24 18:37:54 (32901eea-9335-4778-84b9-72ca6c750256/Plant.Prod.BusinessLogic/SAKDSRV04/18592/210) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 15: "host": { "Value": "sakdsrv04:83"\', \'Comment 16: "HasValue": true\', \'Comment 17: "Host": "sakdsrv04"\', \'Comment 18: "Port": 83 }\', \'Comment 19: "path": "/api/productionLot/update"\', \'Comment 20: "queryString": []\', \'Comment 21: "requestBody": "{\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":1,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"a3e8359c-1434-47af-807b-194b09e15329\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":251}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":2,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"2d5d699e-9140-435c-b557-a904b15d0846\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1.68}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":3,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"9915211b-5428-419f-ace3-500107b293c8\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.4}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":4,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"c790227e-d0d1-4391-84ec-b997d014b365\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":348}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":5,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"b6693bc8-055e-4394-99ed-cd2ac383ab5c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":3}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":6,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"cb9254cd-11f3-45d1-8e9a-2379ea68b108\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1388}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":7,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"523a75e3-f5e9-4ea7-88ef-9ba4fd1b9b1c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":235}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":8,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"ccb356e8-b899-46d6-97aa-7f4af566f8d3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":73}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":9,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"97ae7ce1-ac4a-4852-8f5e-6a62446c1b3c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":450}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":10,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"eacc5086-a76d-45b8-b34b-aadcdf8063de\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":6.26}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":11,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"ed1e952c-87b4-46cd-84a3-5f2c50fffb4a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":15.4}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":13,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"99faf3a0-9376-4ac9-953e-c5d13887c0c6\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":218}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":14,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"31f81b61-b661-4d65-84d4-707133fa2816\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":15,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"9c5d67c9-a8d5-4bee-b4d0-d0b18233ad9a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.6}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":16,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"c7f1f3c2-3267-46dd-a88e-cad65fd117b8\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":3.24}}],\\\\\\\\"executions\\\\\\\\":[{\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"1ffec991-c0ee-4d19-be6e-4d1ab446d7c9\\\\\\\\",\\\\\\\\"recipeElementId\\\\\\\\":12,\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"pcs\\\\\\\\",\\\\\\\\"value\\\\\\\\":60}}],\\\\\\\\"readyProductId\\\\\\\\":\\\\\\\\"8ae3d247-05f9-4268-a5d6-e0ff11cfded8\\\\\\\\",\\\\\\\\"packingRecipeId\\\\\\\\":\\\\\\\\"c535edc8-9d73-41b7-9d30-e7eae9b7c08a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2995.58},\\\\\\\\"requestedQuantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":3000},\\\\\\\\"expiryDate\\\\\\\\":\\\\\\\\"2023-07-22T19:13:06.966Z\\\\\\\\"}],\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"d3fe0c16-69c1-42e6-a085-57b9d7419036\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"b4bdeeae-2472-4738-bd4a-5f0b5f331708\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.251}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"bcf1cff7-f7de-4e12-8666-b55c603a5de5\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"e88d2913-317a-477b-8d8e-147e7d7cbad3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":1.388}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"ef8f9c94-733a-47e1-aff0-5d68c71560f1\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"d262b243-0635-4658-9d75-5882d9362942\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.0004}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"43743169-cb9d-4b48-a313-fd1d38ce7b72\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"89e420a1-c8d9-4721-964a-02f307513427\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.0154}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"932f7272-1f25-411e-a64a-1c8d42bfd98f\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"2d67090b-fada-43fb-b7b4-387680bf3ded\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.45}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"f3af5dbd-4fb0-458c-8200-45f81258592c\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"ddbd03ce-2068-4432-ae7e-a6477f1704f2\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.002}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"67fe0c1f-ae58-4574-a5b5-fae0944b2b73\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"67c7f7f8-651f-49c4-a41e-127c09088fa8\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.073}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"e2151be8-cfdc-44d4-b1b9-520aa36820c8\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"21df176b-34bf-46b3-803d-dd8e5cb02ba7\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.235}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"34cf4324-c829-4286-b7ea-2aa653d6b25c\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"6ee5a5ca-c350-40b6-9368-3bbe79b9c479\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.00168}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"090f8a80-f370-43b4-b268-0304d8b2e108\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"12363980-6291-444c-a76a-2342b1c1c3d7\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.00626}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"882ff3a6-1c35-45ba-ad49-1cbce7aaadac\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"b637f0b5-c5b5-45d6-811a-a8e622b65d1e\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.348}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"a1e07f9f-f4fb-4405-b833-583746841a68\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"e250823d-0c9e-4aa0-9539-5df2ffdd658a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.218}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"90227a2e-0100-4223-83f0-7aea35fd2250\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"dde7ba82-8eb6-4c85-8d5f-160932a2fcd3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.00324}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"845f2076-870a-4c68-8a52-b081666cfe25\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"6aee2c6f-fa5c-451d-9edd-d5e5e1e12150\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.003}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"e118e00e-7ed0-4522-bc80-060fa157ced6\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"849bb14d-53f7-4ef3-ad5c-7ff0af6e734a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.0006}}],\\\\\\\\"productionLotId\\\\\\\\":\\\\\\\\"41616471-4073-4d43-9413-13290367340d\\\\\\\\",\\\\\\\\"recipeId\\\\\\\\":\\\\\\\\"c535edc8-9d73-41b7-9d30-e7eae9b7c08a\\\\\\\\",\\\\\\\\"labelId\\\\\\\\":null,\\\\\\\\"productionOrderId\\\\\\\\":\\\\\\\\"3a12e985-3eb8-4720-84be-33f075efbc09\\\\\\\\",\\\\\\\\"businessPartnerId\\\\\\\\":\\\\\\\\"d8db5ff8-b203-44b0-ab5a-6526b352a2a5\\\\\\\\",\\\\\\\\"shiftNumberId\\\\\\\\":null,\\\\\\\\"statusChange\\\\\\\\":2}"}.System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 313 --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 22: AggregateId businessUnitId\', \'Comment 23: Quantity productionQuantity\', \'Comment 24: IEnumerable`1 settlementData\', \'Comment 25: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 165 at Castle.Proxies.Invocations.IStockEngineApi_UpdateReservationsAndConfirmProductionLot.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Castle.Proxies.IStockEngineApiProxy.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 26: AggregateId businessUnitId\', \'Comment 27: Quantity productionQuantity\', \'Comment 28: IEnumerable`1 settlementData\', \'Comment 29: IEnumerable`1 dosingSiloItemData) at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 30: ConfirmProductionLotActionData data\', \'Comment 31: IEnumerable`1 reservations\', \'Comment 32: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 88 at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 334 at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateProductionLotCommandHandler.Handle(UpdateProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateProductionLotCommandHandler.cs:line 38 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Plant.Prod.BusinessLogic.Infrastructure.Api.Controllers.ProductionLotController.UpdateProductionLot(UpdateProductionLotViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\Controllers\\\\\\\\ProductionLotController.cs:line 110 at lambda_method9698(Closure \', \'Comment 33: Object \', \'Comment 34: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 35: ObjectMethodExecutor executor\', \'Comment 36: Object controller\', \'Comment 37: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 38: Scope& scope\', \'Comment 39: Object& state\', \'Comment 40: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 41: Scope& scope\', \'Comment 42: Object& state\', \'Comment 43: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 44: Task lastTask\', \'Comment 45: State next\', \'Comment 46: Scope scope\', \'Comment 47: Object state\', \'Comment 48: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 49: Task task\', \'Comment 50: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 51: Task task\', \'Comment 52: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 53: Task requestTask\', \'Comment 54: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', "Comment 55: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'", \'Comment 56: \\\'Po restarcie pooli ponowiłam confirm na tym samym PLRze{code:java}2023-01-24 18:56:55 (2e53ede8-9517-4e92-ba70-4a54a27c1a7c/Plant.Prod.BusinessLogic/SAKDSRV04/4496/9) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 57: "host": { "Value": "sakdsrv04:83"\', \'Comment 58: "HasValue": true\', \'Comment 59: "Host": "sakdsrv04"\', \'Comment 60: "Port": 83 }\', \'Comment 61: "path": "/api/productionLot/update"\', \'Comment 62: "queryString": []\', \'Comment 63: "requestBody": "{\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":1,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"a3e8359c-1434-47af-807b-194b09e15329\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":251}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":2,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"2d5d699e-9140-435c-b557-a904b15d0846\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1.68}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":3,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"9915211b-5428-419f-ace3-500107b293c8\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.4}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":4,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"c790227e-d0d1-4391-84ec-b997d014b365\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":348}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":5,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"b6693bc8-055e-4394-99ed-cd2ac383ab5c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":3}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":6,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"cb9254cd-11f3-45d1-8e9a-2379ea68b108\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1388}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":7,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"523a75e3-f5e9-4ea7-88ef-9ba4fd1b9b1c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":235}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":8,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"ccb356e8-b899-46d6-97aa-7f4af566f8d3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":73}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":9,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"97ae7ce1-ac4a-4852-8f5e-6a62446c1b3c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":450}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":10,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"eacc5086-a76d-45b8-b34b-aadcdf8063de\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":6.26}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":11,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"ed1e952c-87b4-46cd-84a3-5f2c50fffb4a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":15.4}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":13,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"99faf3a0-9376-4ac9-953e-c5d13887c0c6\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":218}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":14,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"31f81b61-b661-4d65-84d4-707133fa2816\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":15,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"9c5d67c9-a8d5-4bee-b4d0-d0b18233ad9a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.6}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":16,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"c7f1f3c2-3267-46dd-a88e-cad65fd117b8\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":3.24}}],\\\\\\\\"executions\\\\\\\\":[{\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"1ffec991-c0ee-4d19-be6e-4d1ab446d7c9\\\\\\\\",\\\\\\\\"recipeElementId\\\\\\\\":12,\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"pcs\\\\\\\\",\\\\\\\\"value\\\\\\\\":60}}],\\\\\\\\"readyProductId\\\\\\\\":\\\\\\\\"8ae3d247-05f9-4268-a5d6-e0ff11cfded8\\\\\\\\",\\\\\\\\"packingRecipeId\\\\\\\\":\\\\\\\\"c535edc8-9d73-41b7-9d30-e7eae9b7c08a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2995.58},\\\\\\\\"requestedQuantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":3000},\\\\\\\\"expiryDate\\\\\\\\":\\\\\\\\"2023-07-22T19:13:06.966Z\\\\\\\\"}],\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"d3fe0c16-69c1-42e6-a085-57b9d7419036\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"b4bdeeae-2472-4738-bd4a-5f0b5f331708\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.251}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"bcf1cff7-f7de-4e12-8666-b55c603a5de5\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"e88d2913-317a-477b-8d8e-147e7d7cbad3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":1.388}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"ef8f9c94-733a-47e1-aff0-5d68c71560f1\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"d262b243-0635-4658-9d75-5882d9362942\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.0004}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"43743169-cb9d-4b48-a313-fd1d38ce7b72\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"89e420a1-c8d9-4721-964a-02f307513427\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.0154}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"932f7272-1f25-411e-a64a-1c8d42bfd98f\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"2d67090b-fada-43fb-b7b4-387680bf3ded\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.45}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"f3af5dbd-4fb0-458c-8200-45f81258592c\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"ddbd03ce-2068-4432-ae7e-a6477f1704f2\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.002}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"67fe0c1f-ae58-4574-a5b5-fae0944b2b73\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"67c7f7f8-651f-49c4-a41e-127c09088fa8\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.073}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"e2151be8-cfdc-44d4-b1b9-520aa36820c8\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"21df176b-34bf-46b3-803d-dd8e5cb02ba7\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.235}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"34cf4324-c829-4286-b7ea-2aa653d6b25c\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"6ee5a5ca-c350-40b6-9368-3bbe79b9c479\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.00168}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"090f8a80-f370-43b4-b268-0304d8b2e108\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"12363980-6291-444c-a76a-2342b1c1c3d7\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.00626}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"882ff3a6-1c35-45ba-ad49-1cbce7aaadac\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"b637f0b5-c5b5-45d6-811a-a8e622b65d1e\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.348}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"a1e07f9f-f4fb-4405-b833-583746841a68\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"e250823d-0c9e-4aa0-9539-5df2ffdd658a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.218}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"90227a2e-0100-4223-83f0-7aea35fd2250\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"dde7ba82-8eb6-4c85-8d5f-160932a2fcd3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.00324}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"845f2076-870a-4c68-8a52-b081666cfe25\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"6aee2c6f-fa5c-451d-9edd-d5e5e1e12150\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.003}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"e118e00e-7ed0-4522-bc80-060fa157ced6\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"849bb14d-53f7-4ef3-ad5c-7ff0af6e734a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.0006}}],\\\\\\\\"productionLotId\\\\\\\\":\\\\\\\\"41616471-4073-4d43-9413-13290367340d\\\\\\\\",\\\\\\\\"recipeId\\\\\\\\":\\\\\\\\"c535edc8-9d73-41b7-9d30-e7eae9b7c08a\\\\\\\\",\\\\\\\\"labelId\\\\\\\\":null,\\\\\\\\"productionOrderId\\\\\\\\":\\\\\\\\"3a12e985-3eb8-4720-84be-33f075efbc09\\\\\\\\",\\\\\\\\"businessPartnerId\\\\\\\\":\\\\\\\\"d8db5ff8-b203-44b0-ab5a-6526b352a2a5\\\\\\\\",\\\\\\\\"shiftNumberId\\\\\\\\":null,\\\\\\\\"statusChange\\\\\\\\":2}"}.System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 288 --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at System.Threading.Tasks.Task`1.get_Result() at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 64: AggregateId businessUnitId\', \'Comment 65: Quantity productionQuantity\', \'Comment 66: IEnumerable`1 settlementData\', \'Comment 67: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 165 at Castle.Proxies.Invocations.IStockEngineApi_UpdateReservationsAndConfirmProductionLot.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Castle.Proxies.IStockEngineApiProxy.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 68: AggregateId businessUnitId\', \'Comment 69: Quantity productionQuantity\', \'Comment 70: IEnumerable`1 settlementData\', \'Comment 71: IEnumerable`1 dosingSiloItemData) at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 72: ConfirmProductionLotActionData data\', \'Comment 73: IEnumerable`1 reservations\', \'Comment 74: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 88 at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 334 at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateProductionLotCommandHandler.Handle(UpdateProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateProductionLotCommandHandler.cs:line 38 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.Proxies.Invocations.IRunEnvironment_Run.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Castle.Proxies.ICommandRunEnvironmentProxy.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.StandardGate.Dispatch[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.AsyncGateDecorator.Dispatch[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Plant.Prod.BusinessLogic.Infrastructure.Api.Controllers.ProductionLotController.UpdateProductionLot(UpdateProductionLotViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\Controllers\\\\\\\\ProductionLotController.cs:line 110 at lambda_method6341(Closure \', \'Comment 75: Object \', \'Comment 76: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 77: ObjectMethodExecutor executor\', \'Comment 78: Object controller\', \'Comment 79: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 80: Scope& scope\', \'Comment 81: Object& state\', \'Comment 82: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 83: Scope& scope\', \'Comment 84: Object& state\', \'Comment 85: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 86: Task lastTask\', \'Comment 87: State next\', \'Comment 88: Scope scope\', \'Comment 89: Object state\', \'Comment 90: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 91: Task task\', \'Comment 92: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 93: Task task\', \'Comment 94: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 95: Task requestTask\', \'Comment 96: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', "Comment 97: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'", "Comment 98: \'{code:java}2023-01-24 18:56:55 (2e53ede8-9517-4e92-ba70-4a54a27c1a7c/Plant.Prod.BusinessLogic/SAKDSRV04/4496/9) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateProductionLotCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateProductionLotCommand) methodSystem.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 288 --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at System.Threading.Tasks.Task`1.get_Result() at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId", \'Comment 99: AggregateId businessUnitId\', \'Comment 100: Quantity productionQuantity\', \'Comment 101: IEnumerable`1 settlementData\', \'Comment 102: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 165 at Castle.Proxies.Invocations.IStockEngineApi_UpdateReservationsAndConfirmProductionLot.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Castle.Proxies.IStockEngineApiProxy.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 103: AggregateId businessUnitId\', \'Comment 104: Quantity productionQuantity\', \'Comment 105: IEnumerable`1 settlementData\', \'Comment 106: IEnumerable`1 dosingSiloItemData) at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 107: ConfirmProductionLotActionData data\', \'Comment 108: IEnumerable`1 reservations\', \'Comment 109: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 88 at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 334 at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateProductionLotCommandHandler.Handle(UpdateProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateProductionLotCommandHandler.cs:line 38 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.Proxies.Invocations.IRunEnvironment_Run.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-01-24 18:56:55 (/Plant.Prod.BusinessLogic/SAKDSRV04/4496/8) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/productionLot/update" responded 500 in 3008.1672 ms{code}\\\'\', "Comment 110: \'>> ze Stocka{code:java}2023-01-24 18:56:55 (2e53ede8-9517-4e92-ba70-4a54a27c1a7c/Plant.Stock.BusinessLogic/SAKDSRV04/10032/9) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateReservationsAndConfirmProductionLotCommand](Plant.Stock.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateReservationsAndConfirmProductionLotCommand) methodSystem.ArgumentException: Unit mismatch at Kotrak.Common.SharedKernel.Quantity.ToCommonUnit(Quantity x1", \'Comment 111: Quantity x2) at Kotrak.Common.SharedKernel.Quantity.op_Subtraction(Quantity q\', \'Comment 112: Quantity q2) at Plant.Stock.BusinessLogic.Domain.StockManagement.StockData.DecreaseQuantity(Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\StockManagement\\\\\\\\StockData.cs:line 58 at Plant.Stock.BusinessLogic.Domain.StockReplenishment.Policies.StockUnitBaseReplenishmentPolicy.FetchReplenishment(ReplenishmentData replenishmentData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\StockReplenishment\\\\\\\\Policies\\\\\\\\StockUnitBaseReplenishmentPolicy.cs:line 28 at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchReplenishment(IEnumerable`1 filteredStockData\', \'Comment 113: Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 104 at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchProductionElementReplenishment(IEnumerable`1 stockData\', \'Comment 114: ProductionElementSettlementData settlementData\', \'Comment 115: List`1 response\', \'Comment 116: List`1 missingStock) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 90 at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchProductionSettlement(IEnumerable`1 stockData\', \'Comment 117: IEnumerable`1 productionElementsData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 48 at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.ProductionSettlementDomainService.FetchProductionSettlement(IEnumerable`1 stockForSettlement\', \'Comment 118: IEnumerable`1 stockUnits\', \'Comment 119: IEnumerable`1 deliveries\', \'Comment 120: IEnumerable`1 locations\', \'Comment 121: IProductionSettlementPolicy productionSettlementPolicy) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\ProductionSettlementDomainService.cs:line 220 at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.ProductionSettlementDomainService.ExecuteProductionSettlement(ProductionSettlementData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\ProductionSettlementDomainService.cs:line 61 at Plant.Stock.BusinessLogic.Domain.ProductionLots.Services.ConfirmProductionDomainService.ExecuteProductionSettlement(ConfirmProductionLotDomainData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\Services\\\\\\\\ConfirmProductionDomainService.cs:line 102 at Plant.Stock.BusinessLogic.Domain.ProductionLots.Services.ConfirmProductionDomainService.ConfirmProductionLot(ConfirmProductionLotDomainData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\Services\\\\\\\\ConfirmProductionDomainService.cs:line 52 at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.ConfirmProduction(ProductionLot productionLot\', \'Comment 122: IEnumerable`1 productionElements\', \'Comment 123: IEnumerable`1 ingredientDeliveries\', \'Comment 124: IEnumerable`1 ingredientStockUnits\', \'Comment 125: IEnumerable`1 locations\', \'Comment 126: IEnumerable`1 transcodingDefinitions) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 797 at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateReservationsAndConfirmProductionLot(UpdateReservationsAndConfirmProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 459 at Plant.Stock.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateReservationsAndConfirmProductionLotCommandHandler.Handle(UpdateReservationsAndConfirmProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateReservationsAndConfirmProductionLotCommandHandler.cs:line 32 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.Proxies.Invocations.IRunEnvironment_Run.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-01-24 18:56:55 (/Plant.Stock.BusinessLogic/SAKDSRV04/10032/7) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/productionLot/updateReservationsAndConfirm" responded 500 in 1510.1593 ms2023-01-24 18:59:13 (/Plant.Stock.BusinessLogic/SAKDSRV04/10032/10) [Error] Kotrak.Common.Infrastructure.CleanEventsTask - Problem with data cleaning task executionMicrosoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 127: Boolean breakConnection\', \'Comment 128: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 129: Boolean callerHasConnectionLock\', \'Comment 130: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning(Boolean callerHasConnectionLock\', \'Comment 131: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj\', \'Comment 132: UInt32 error) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket() at Microsoft.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 133: SqlCommand cmdHandler\', \'Comment 134: SqlDataReader dataStream\', \'Comment 135: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 136: TdsParserStateObject stateObj\', \'Comment 137: Boolean& dataReady) at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 138: RunBehavior runBehavior\', \'Comment 139: String resetOptionsString\', \'Comment 140: Boolean isInternal\', \'Comment 141: Boolean forDescribeParameterEncryption\', \'Comment 142: Boolean shouldCacheForAlwaysEncrypted) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 143: RunBehavior runBehavior\', \'Comment 144: Boolean returnStream\', \'Comment 145: Boolean isAsync\', \'Comment 146: Int32 timeout\', \'Comment 147: Task& task\', \'Comment 148: Boolean asyncWrite\', \'Comment 149: Boolean inRetry\', \'Comment 150: SqlDataReader ds\', \'Comment 151: Boolean describeParameterEncryptionRequest) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 152: RunBehavior runBehavior\', \'Comment 153: Boolean returnStream\', \'Comment 154: TaskCompletionSource`1 completion\', \'Comment 155: Int32 timeout\', \'Comment 156: Task& task\', \'Comment 157: Boolean& usedCache\', \'Comment 158: Boolean asyncWrite\', \'Comment 159: Boolean inRetry\', \'Comment 160: String method) at Microsoft.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion\', \'Comment 161: Boolean sendToPipe\', \'Comment 162: Int32 timeout\', \'Comment 163: Boolean& usedCache\', \'Comment 164: Boolean asyncWrite\', \'Comment 165: Boolean inRetry\', \'Comment 166: String methodName) at Microsoft.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteNonQuery(RelationalCommandParameterObject parameterObject) at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.ExecuteSqlRaw(DatabaseFacade databaseFacade\', \'Comment 167: String sql\', \'Comment 168: IEnumerable`1 parameters) at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.ExecuteSqlRaw(DatabaseFacade databaseFacade\', \'Comment 169: String sql\', \'Comment 170: Object[] parameters) at Kotrak.Common.Infrastructure.EF.EventRepository.BaseEventRepositoryEf`1.CleanData(TimeSpan removeOlderThen) at Kotrak.Common.Infrastructure.CleanEventsTask.<ExecuteAsync>b__9_0()ClientConnectionId:c39e892c-3080-4114-991c-0209bbba9894Error Number:-2,State:0,Class:112023-01-24 19:01:00 (db3de036-734d-453f-a742-e6c899409eb1/Plant.Stock.BusinessLogic/SAKDSRV04/10032/18) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[ChangeProductionLotQuantityCommand](Plant.Stock.BusinessLogic.Application.Interfaces.ProductionLots.Commands.ChangeProductionLotQuantityCommand) methodMicrosoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.Operation cancelled by user. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 171: Boolean breakConnection\', \'Comment 172: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 173: Boolean breakConnection\', \'Comment 174: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 175: Boolean callerHasConnectionLock\', \'Comment 176: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 177: SqlCommand cmdHandler\', \'Comment 178: SqlDataReader dataStream\', \'Comment 179: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 180: TdsParserStateObject stateObj\', \'Comment 181: Boolean& dataReady) at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior\', \'Comment 182: SqlCommand cmdHandler\', \'Comment 183: SqlDataReader dataStream\', \'Comment 184: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 185: TdsParserStateObject stateObj) at Microsoft.Data.SqlClient.SqlBulkCopy.RunParser(BulkCopySimpleResultSet bulkCopyHandler) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinuedOnSuccess(BulkCopySimpleResultSet internalResults\', \'Comment 186: String updateBulkCommandText\', \'Comment 187: CancellationToken cts\', \'Comment 188: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinued(BulkCopySimpleResultSet internalResults\', \'Comment 189: String updateBulkCommandText\', \'Comment 190: CancellationToken cts\', \'Comment 191: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsync(BulkCopySimpleResultSet internalResults\', \'Comment 192: String updateBulkCommandText\', \'Comment 193: CancellationToken cts\', \'Comment 194: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestContinuedAsync(BulkCopySimpleResultSet internalResults\', \'Comment 195: CancellationToken cts\', \'Comment 196: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts\', \'Comment 197: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount\', \'Comment 198: CancellationToken ctoken) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table\', \'Comment 199: DataRowState rowState) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table) at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.InsertAsync[T](DbContext context\', \'Comment 200: Type type\', \'Comment 201: IList`1 entities\', \'Comment 202: TableInfo tableInfo\', \'Comment 203: Action`1 progress\', \'Comment 204: Boolean isAsync\', \'Comment 205: CancellationToken cancellationToken) at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.InsertAsync[T](DbContext context\', \'Comment 206: Type type\', \'Comment 207: IList`1 entities\', \'Comment 208: TableInfo tableInfo\', \'Comment 209: Action`1 progress\', \'Comment 210: Boolean isAsync\', \'Comment 211: CancellationToken cancellationToken) at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.Insert[T](DbContext context\', \'Comment 212: Type type\', \'Comment 213: IList`1 entities\', \'Comment 214: TableInfo tableInfo\', \'Comment 215: Action`1 progress) at EFCore.BulkExtensions.SqlBulkOperation.Insert[T](DbContext context\', \'Comment 216: Type type\', \'Comment 217: IList`1 entities\', \'Comment 218: TableInfo tableInfo\', \'Comment 219: Action`1 progress) at EFCore.BulkExtensions.DbContextBulkTransaction.Execute[T](DbContext context\', \'Comment 220: Type type\', \'Comment 221: IList`1 entities\', \'Comment 222: OperationType operationType\', \'Comment 223: BulkConfig bulkConfig\', \'Comment 224: Action`1 progress) at EFCore.BulkExtensions.DbContextBulkExtensions.BulkInsert[T](DbContext context\', \'Comment 225: IList`1 entities\', \'Comment 226: BulkConfig bulkConfig\', \'Comment 227: Action`1 progress\', \'Comment 228: Type type) at Kotrak.Common.Infrastructure.EF.EventRepository.GenericEventRepositoryEf`2.Persist(TAggregateRoot aggregateRoot) at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.PersistEvents(TAggregateRoot root) at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.Persist(TAggregateRoot root) at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.ChangeQuantity(AggregateId productionLotId\', "Comment 229: Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 274 at Plant.Stock.BusinessLogic.Application.ProductionLots.CommandHandlers.ChangeProductionLotQuantityCommandHandler.Handle(ChangeProductionLotQuantityCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\ChangeProductionLotQuantityCommandHandler.cs:line 30 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.Proxies.Invocations.IRunEnvironment_Run.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)ClientConnectionId:8f72d6b0-9bb0-4bd5-9ecf-79d29ffe9cd4Error Number:-2,State:0,Class:11{code}\'", \'Comment 230: \\\'Request ze Stocka:{code:java}2023-01-24 18:56:55 (2e53ede8-9517-4e92-ba70-4a54a27c1a7c/Plant.Stock.BusinessLogic/SAKDSRV04/10032/9) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 231: "host": { "Value": "sakdsrv04:92"\', \'Comment 232: "HasValue": true\', \'Comment 233: "Host": "sakdsrv04"\', \'Comment 234: "Port": 92 }\', \'Comment 235: "path": "/api/productionLot/updateReservationsAndConfirm"\', \'Comment 236: "queryString": []\', \'Comment 237: "requestBody": "{\\\\\\\\"productionLotId\\\\\\\\":\\\\\\\\"41616471-4073-4d43-9413-13290367340d\\\\\\\\",\\\\\\\\"businessUnitId\\\\\\\\":\\\\\\\\"93f3b3c7-eefc-47ed-a18e-8629f8dc1c5e\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2995.580000},\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"a3e8359c-1434-47af-807b-194b09e15329\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":251.0},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"d3fe0c16-69c1-42e6-a085-57b9d7419036\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"b4bdeeae-2472-4738-bd4a-5f0b5f331708\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.251}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"2d5d699e-9140-435c-b557-a904b15d0846\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1.68},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"34cf4324-c829-4286-b7ea-2aa653d6b25c\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"6ee5a5ca-c350-40b6-9368-3bbe79b9c479\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.00168}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"9915211b-5428-419f-ace3-500107b293c8\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.4},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"ef8f9c94-733a-47e1-aff0-5d68c71560f1\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"d262b243-0635-4658-9d75-5882d9362942\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.0004}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"c790227e-d0d1-4391-84ec-b997d014b365\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":348.0},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"882ff3a6-1c35-45ba-ad49-1cbce7aaadac\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"b637f0b5-c5b5-45d6-811a-a8e622b65d1e\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.348}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"b6693bc8-055e-4394-99ed-cd2ac383ab5c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":3.0},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"845f2076-870a-4c68-8a52-b081666cfe25\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"6aee2c6f-fa5c-451d-9edd-d5e5e1e12150\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.003}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"cb9254cd-11f3-45d1-8e9a-2379ea68b108\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1388.0},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"bcf1cff7-f7de-4e12-8666-b55c603a5de5\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"e88d2913-317a-477b-8d8e-147e7d7cbad3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":1.388}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"523a75e3-f5e9-4ea7-88ef-9ba4fd1b9b1c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":235.0},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"e2151be8-cfdc-44d4-b1b9-520aa36820c8\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"21df176b-34bf-46b3-803d-dd8e5cb02ba7\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.235}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"ccb356e8-b899-46d6-97aa-7f4af566f8d3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":73.0},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"67fe0c1f-ae58-4574-a5b5-fae0944b2b73\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"67c7f7f8-651f-49c4-a41e-127c09088fa8\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.073}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"97ae7ce1-ac4a-4852-8f5e-6a62446c1b3c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":450.0},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"932f7272-1f25-411e-a64a-1c8d42bfd98f\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"2d67090b-fada-43fb-b7b4-387680bf3ded\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.45}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"eacc5086-a76d-45b8-b34b-aadcdf8063de\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":6.26},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"090f8a80-f370-43b4-b268-0304d8b2e108\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"12363980-6291-444c-a76a-2342b1c1c3d7\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.00626}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"ed1e952c-87b4-46cd-84a3-5f2c50fffb4a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":15.4},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"43743169-cb9d-4b48-a313-fd1d38ce7b72\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"89e420a1-c8d9-4721-964a-02f307513427\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.0154}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"99faf3a0-9376-4ac9-953e-c5d13887c0c6\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":218.0},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"a1e07f9f-f4fb-4405-b833-583746841a68\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"e250823d-0c9e-4aa0-9539-5df2ffdd658a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.218}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"31f81b61-b661-4d65-84d4-707133fa2816\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2.0},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"f3af5dbd-4fb0-458c-8200-45f81258592c\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"ddbd03ce-2068-4432-ae7e-a6477f1704f2\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.002}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"9c5d67c9-a8d5-4bee-b4d0-d0b18233ad9a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.6},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"e118e00e-7ed0-4522-bc80-060fa157ced6\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"849bb14d-53f7-4ef3-ad5c-7ff0af6e734a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.0006}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"c7f1f3c2-3267-46dd-a88e-cad65fd117b8\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":3.24},\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"90227a2e-0100-4223-83f0-7aea35fd2250\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"dde7ba82-8eb6-4c85-8d5f-160932a2fcd3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"t\\\\\\\\",\\\\\\\\"value\\\\\\\\":0.00324}}]},{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"1ffec991-c0ee-4d19-be6e-4d1ab446d7c9\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"pcs\\\\\\\\",\\\\\\\\"value\\\\\\\\":60.0},\\\\\\\\"reservations\\\\\\\\":[]}],\\\\\\\\"siloItems\\\\\\\\":[]}"}.System.ArgumentException: Unit mismatch at Kotrak.Common.SharedKernel.Quantity.ToCommonUnit(Quantity x1\', \'Comment 238: Quantity x2) at Kotrak.Common.SharedKernel.Quantity.op_Subtraction(Quantity q\', \'Comment 239: Quantity q2) at Plant.Stock.BusinessLogic.Domain.StockManagement.StockData.DecreaseQuantity(Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\StockManagement\\\\\\\\StockData.cs:line 58 at Plant.Stock.BusinessLogic.Domain.StockReplenishment.Policies.StockUnitBaseReplenishmentPolicy.FetchReplenishment(ReplenishmentData replenishmentData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\StockReplenishment\\\\\\\\Policies\\\\\\\\StockUnitBaseReplenishmentPolicy.cs:line 28 at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchReplenishment(IEnumerable`1 filteredStockData\', \'Comment 240: Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 104 at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchProductionElementReplenishment(IEnumerable`1 stockData\', \'Comment 241: ProductionElementSettlementData settlementData\', \'Comment 242: List`1 response\', \'Comment 243: List`1 missingStock) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 90 at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchProductionSettlement(IEnumerable`1 stockData\', \'Comment 244: IEnumerable`1 productionElementsData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 48 at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.ProductionSettlementDomainService.FetchProductionSettlement(IEnumerable`1 stockForSettlement\', \'Comment 245: IEnumerable`1 stockUnits\', \'Comment 246: IEnumerable`1 deliveries\', \'Comment 247: IEnumerable`1 locations\', \'Comment 248: IProductionSettlementPolicy productionSettlementPolicy) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\ProductionSettlementDomainService.cs:line 220 at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.ProductionSettlementDomainService.ExecuteProductionSettlement(ProductionSettlementData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\ProductionSettlementDomainService.cs:line 61 at Plant.Stock.BusinessLogic.Domain.ProductionLots.Services.ConfirmProductionDomainService.ExecuteProductionSettlement(ConfirmProductionLotDomainData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\Services\\\\\\\\ConfirmProductionDomainService.cs:line 102 at Plant.Stock.BusinessLogic.Domain.ProductionLots.Services.ConfirmProductionDomainService.ConfirmProductionLot(ConfirmProductionLotDomainData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\Services\\\\\\\\ConfirmProductionDomainService.cs:line 52 at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.ConfirmProduction(ProductionLot productionLot\', \'Comment 249: IEnumerable`1 productionElements\', \'Comment 250: IEnumerable`1 ingredientDeliveries\', \'Comment 251: IEnumerable`1 ingredientStockUnits\', \'Comment 252: IEnumerable`1 locations\', \'Comment 253: IEnumerable`1 transcodingDefinitions) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 797 at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateReservationsAndConfirmProductionLot(UpdateReservationsAndConfirmProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 459 at Plant.Stock.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateReservationsAndConfirmProductionLotCommandHandler.Handle(UpdateReservationsAndConfirmProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateReservationsAndConfirmProductionLotCommandHandler.cs:line 32 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.Proxies.Invocations.IRunEnvironment_Run.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Castle.Proxies.ICommandRunEnvironmentProxy.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.StandardGate.Dispatch[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.AsyncGateDecorator.Dispatch[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Plant.Stock.BusinessLogic.Infrastructure.Api.Controllers.ProductionLotController.UpdateReservationsAndConfirmProductionLot(UpdateReservationsAndConfirmProductionLotViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\Controllers\\\\\\\\ProductionLotController.cs:line 140 at lambda_method9745(Closure \', \'Comment 254: Object \', \'Comment 255: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 256: ObjectMethodExecutor executor\', \'Comment 257: Object controller\', \'Comment 258: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 259: Scope& scope\', \'Comment 260: Object& state\', \'Comment 261: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 262: Scope& scope\', \'Comment 263: Object& state\', \'Comment 264: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 265: Task lastTask\', \'Comment 266: State next\', \'Comment 267: Scope scope\', \'Comment 268: Object state\', \'Comment 269: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 270: Task task\', \'Comment 271: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 272: Task task\', \'Comment 273: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 274: Task requestTask\', \'Comment 275: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', "Comment 276: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'", "Comment 277: \'Hi,Tere is a unit mismatch on item:!image-2023-01-24-18-20-34-818.png!!image-2023-01-24-18-21-07-649.png!!image-2023-01-24-18-22-41-696.png!Please", "Comment 278: verify item.Regards\'", "Comment 279: \'thank you task can be closed \']"]\nRelated Issues:\n[]\n\n### End'}
638
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8394\n\n### Instruction:\nPlease close the contracts. Customer is not able to the following notification\r\nClose old contract. Closing give errors.\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Contracts were closed after selecting the context from the PO documents.\'", "Comment 4: \'!image-2023-01-25-07-38-53-802.png!\'", "Comment 5: \'!image-2!\'", "Comment 6: \'!image-3!\'", "Comment 7: \'HI", "Comment 8: are these 5/07/2022/INT and 8/07/2022/INT also supposed to be closed?\'", "Comment 9: \'Only the mentioned contracts.!image-4!\'", "Comment 10: \'PO-4/7/2022/INT and PO-6/7/2022/INT are partially completed", \'Comment 11: so they have the status Closed in progress.PO-9/7/2022/INT was only confirmed\', "Comment 12: so it has the Closed status.\'", "Comment 13: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
639
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8393\n\n### Instruction:\nWO(PD)120/1/23 cannot be closed due to WD-212 being in status processable. Please cancel this WD so we can close the WO\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Please check should be correct now.Please use erase option !screenshot-2! \'", "Comment 4: \'Hi Piotr", "Comment 5: thanks Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
640
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8392\n\n### Instruction:\nSales order SO000057337 has to be produced early this afternoon.\r\nIt is in DHC but not in DHP Meppel.\r\n\r\nPlease investigate.\n\n### Response:\n["Comment 1: [\'Hello", "Comment 2: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'The item for the order was missing in DHCService (DHHitem).It was corrected.Please resend order.Fixed in dhc 3.0.60 - about missing items DHH in DHCservice.\'", "Comment 5: \'After resending the order popped up in DHP.Thank you for the support", "Comment 6: the ticket can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
641
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8391\n\n### Instruction:\nProśba o wsparcie, wyrzuca błąd przy rozrachunku\r\nW razie problemów prosze kontaktowac sie z Business Reporterem\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Any news ??\'", "Comment 4: \'Any news ??\'", "Comment 5: \'documents have been settled", "Comment 6: please verify\'", "Comment 7: \'Task to close \']"]\nRelated Issues:\n[]\n\n### End'}
642
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8390\n\n### Instruction:\nFor PI-RTN/2022/0067 ID72972 and SI-RLN/2022/0269 ID72971 I used a wrong description. It should be 196 Rosékalveren 24-11 stal De Kievit. Can this be modified?\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Changed descriptions in both documents.\']"]\nRelated Issues:\n[]\n\n### End'}
643
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8389\n\n### Instruction:\nSystem didin\'t create assemly pallets for WMO\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Please ", "Comment 4: can you exit the document?\'", "Comment 5: \'!image-2023-01-24-10-20-19-083.png!{code:java}select RgM_AssemblyLogisticId", \'Comment 6: RgM_ArtId\', \'Comment 7: RgM_Id,RgM_Quantity,RgM_IsReleased,RgM_IsActivated,RgM_Type,RgM_AssemblyLogisticId--into dbo.rgm_dgs3033from [dbo].[WMSInternalDocumentOrderSubElements] wjoin RegisterMappings r on WiS_RgmId = RgM_idwhere WiS_ElementId in (select WiE_Id from WMSInternalDocumentOrderElements where WiE_HeaderId = 2740)select RgM_AssemblyLogisticId\', \'Comment 8: RgM_ArtId\', "Comment 9: RgM_Id,RgM_Quantity,RgM_IsReleased,RgM_IsActivated,RgM_Type,RgM_AssemblyLogisticId,*from RegisterMappings where rgm_id=1269129 select * from WMSInternalDocumentOrderAssemblies where WiA_HeaderId = 2740{code}\'", \'Comment 10: "{code:java}SELECT Cst_Code,RTRIM(CtA_Name1 + \\\' \\\' + isnull(CtA_Name2,\\\'\\\') + \\\' \\\' + isnull(CtA_Name3,\\\'\\\')) CustomerName,CtA_Street +\\\'\', "Comment 11: \' + CtA_PostCode + \' \'+CtA_City as Address,dbo.GetDocumentNumber(dbo.OrderMapper(odh_ordtype)", \'Comment 12: odh_ordnumber\', \'Comment 13: odh_ordmonth\', \'Comment 14: odh_ordyear\', \'Comment 15: odh_ordseries) DocNumber,RP.RgM_Id,RP.RgM_Code,RP.RgM_Quantity,count(RC.RgM_Id) bagsCount,isnull(A.WiA_CloseUserId,0) CloseUserId,RP.RgM_IsReleased,OE.Ode_id,E.WiE_OdeId FROM dbo.WMSInternalDocumentOrderAssemblies Ajoin dbo.RegisterMappings RP on A.WiA_RgMId = RP.RgM_IdLEFT JOIN dbo.RegisterMappings RC on RP.RgM_Id = RC.RgM_AssemblyLogisticIdLEFT JOIN dbo.WMSInternalDocumentOrderSubElements SE on RC.RgM_Id = SE.WiS_RgmIdLEFT JOIN dbo.WMSInternalDocumentOrderElements E on SE.WiS_ElementId = E.WiE_IdLEFT JOIN dbo.OrderElement OE on E.WiE_OdeId = OE.Ode_Id LEFT JOIN dbo.OrderHeader OH on OE.OdE_OdHId = OH.OdH_IdLEFT JOIN dbo.CustomerCard CC on OH.OdH_Cst2Id = CC.Cst_IdLEFT JOIN dbo.CustomerAdressCard AC on OH.OdH_CtA2Id = AC.CtA_IdWHERE WiA_HeaderId = 2740group by Cst_Code,CtA_Name1,CtA_Name2,CtA_Name3,CtA_Street\', \'Comment 16: CtA_PostCode,CtA_City,RP.RgM_Id,OdH_OrdNumber,OdH_OrdMonth,OdH_OrdYear,OdH_OrdSeries,RP.RgM_Code,RP.RgM_Quantity,WiA_CloseUserId,RP.RgM_IsReleased\', \'Comment 17: dbo.GetDocumentNumber(dbo.OrderMapper(odh_ordtype)\', \'Comment 18: odh_ordnumber\', \'Comment 19: odh_ordmonth\', \'Comment 20: odh_ordyear\', \'Comment 21: odh_ordseries),OE.Ode_id,E.WiE_OdeId{code}!image-2023-01-24-10-39-38-621!----Prawidłowy przykład dla HeaderId = 2732!image-2023-01-24-10-40-36-891!----h2. Aktualny stan na 10:41 24.01.2023!image-2023-01-24-10-42-05-187!----h2. Po poprawie !image-2023-01-24-10-51-38-846!"\', "Comment 22: \'There was no link to the order. It was linked from the database !screenshot-2! \'", "Comment 23: \'where was there no link to the order?\'", "Comment 24: \'Missing WiE_OdeId in dbo.WMSInternalDocumentOrderElements\'", "Comment 25: \'task to be closed\'", "Comment 26: \'[[DHP] [WMS] ZPM(K) utworzony", "Comment 27: brakuje składanki|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHP%20Produkcja.one#%5bDHP%5d%20%5bWMS%5d%20ZPM(K)%20utworzony,%20brakuje%20sk%C5%82adanki&section-id=\\\\\\\\{CC5FB5C6-8E0D-42E5-8319-3DC0E80D8642}&page-id=\\\\\\\\{3E43D2FD-CF4C-4FC7-96D1-308C582AEBD5}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHP%20Produkcja.one%7CCC5FB5C6-8E0D-42E5-8319-3DC0E80D8642%2F%5BDHP%5D%20%5BWMS%5D%20ZPM%28K%5C%29%20utworzony%2C%20brakuje%20sk%C5%82adanki%7C3E43D2FD-CF4C-4FC7-96D1-308C582AEBD5%2F%29])\']"]\nRelated Issues:\n[]\n\n### End'}
644
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8387\n\n### Instruction:\nWe produced production SUR1222-P-MD - 0871200123026 and confirmed, but production is not available in DHC. Could you check why production didn\'t integrated and fix it?\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: \\\'!image-2023-01-23-23-22-51-714.png!2023-01-23 19:21:35 (14755c15-2f75-42e9-9303-b601ac9d9be8/Plant.Prod.BusinessLogic/BR-4-SV-VM0204/16144/8) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type "Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.ProductionBatchReportUpdatedEvent"\', \'Comment 3: retry no 1Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 4: Boolean breakConnection\', \'Comment 5: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 6: Boolean callerHasConnectionLock\', \'Comment 7: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning(Boolean callerHasConnectionLock\', \'Comment 8: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj\', \'Comment 9: UInt32 error) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket() at Microsoft.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 10: SqlCommand cmdHandler\', \'Comment 11: SqlDataReader dataStream\', \'Comment 12: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 13: TdsParserStateObject stateObj\', \'Comment 14: Boolean& dataReady) at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior\', \'Comment 15: SqlCommand cmdHandler\', \'Comment 16: SqlDataReader dataStream\', \'Comment 17: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 18: TdsParserStateObject stateObj) at Microsoft.Data.SqlClient.SqlBulkCopy.RunParser(BulkCopySimpleResultSet bulkCopyHandler) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinuedOnSuccess(BulkCopySimpleResultSet internalResults\', \'Comment 19: String updateBulkCommandText\', \'Comment 20: CancellationToken cts\', \'Comment 21: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinued(BulkCopySimpleResultSet internalResults\', \'Comment 22: String updateBulkCommandText\', \'Comment 23: CancellationToken cts\', \'Comment 24: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsync(BulkCopySimpleResultSet internalResults\', \'Comment 25: String updateBulkCommandText\', \'Comment 26: CancellationToken cts\', \'Comment 27: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestContinuedAsync(BulkCopySimpleResultSet internalResults\', \'Comment 28: CancellationToken cts\', \'Comment 29: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts\', \'Comment 30: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount\', \'Comment 31: CancellationToken ctoken) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table\', \'Comment 32: DataRowState rowState) at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.InsertAsync[T](DbContext context\', \'Comment 33: Type type\', \'Comment 34: IList`1 entities\', \'Comment 35: TableInfo tableInfo\', \'Comment 36: Action`1 progress\', \'Comment 37: Boolean isAsync\', \'Comment 38: CancellationToken cancellationToken) at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.InsertAsync[T](DbContext context\', \'Comment 39: Type type\', \'Comment 40: IList`1 entities\', \'Comment 41: TableInfo tableInfo\', \'Comment 42: Action`1 progress\', \'Comment 43: Boolean isAsync\', \'Comment 44: CancellationToken cancellationToken) at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.Insert[T](DbContext context\', \'Comment 45: Type type\', \'Comment 46: IList`1 entities\', \'Comment 47: TableInfo tableInfo\', \'Comment 48: Action`1 progress) at EFCore.BulkExtensions.DbContextBulkTransaction.Execute[T](DbContext context\', \'Comment 49: Type type\', \'Comment 50: IList`1 entities\', \'Comment 51: OperationType operationType\', \'Comment 52: BulkConfig bulkConfig\', \'Comment 53: Action`1 progress) at EFCore.BulkExtensions.DbContextBulkExtensions.BulkInsert[T](DbContext context\', \'Comment 54: IList`1 entities\', \'Comment 55: BulkConfig bulkConfig\', \'Comment 56: Action`1 progress\', \'Comment 57: Type type) at Kotrak.Common.Infrastructure.EF.EventRepository.GenericEventRepositoryEf`2.Persist(TAggregateRoot aggregateRoot) at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.PersistEvents(TAggregateRoot root) at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.Persist(TAggregateRoot root) at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateBatchReport(UpdateBatchReportActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 527 at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateBatchReportCommandHandler.Handle(UpdateBatchReportCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateBatchReportCommandHandler.cs:line 22 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Castle.Proxies.ICommandRunEnvironmentProxy.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.StandardGate.Dispatch[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.AsyncGateDecorator.Dispatch[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.MessageHandlers.BaseMessageHandler`2.Handle(TMessage message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\MessageHandlers\\\\\\\\BaseMessageHandler.cs:line 27 at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message)ClientConnectionId:8600914b-326c-41d8-b0cf-cc2acc8535c9Error Number:-2,State:0,Class:11Wykonana reindeksacja bazy DHC country i DHC service nie pomogław logach w DHP nie ma żadnego komunikatu!image-2023-01-24-00-30-11-956.png!przy próbie kolejnej wysyłki LOT z DHP nie pojawia sie nowy wis w logachD:\\\\\\\\Kotrak\\\\\\\\dhp30_IIS\\\\\\\\PlantIntegrationDhcService\\\\\\\\LogsD:\\\\\\\\Kotrak\\\\\\\\dhp30_IIS\\\\\\\\PlantProductionBusinessLogic\\\\\\\\Logsmoduły w IISPlantProductionBusinessLogic iPlantIntegrationDhcService były restartowaneDHC service było restartowaneselect lotnumber\', "Comment 58: *--update p set ProductionLotStatus=ProductionLotStatusfrom ProductionLots p where lotnumber like \\\\\'0871200123026%\\\\\'select lotnumber", \'Comment 59: *--update p set ProductionLotStatus=ProductionLotStatusfrom ProductionLots pselect lotnumber\', "Comment 60: * from ProductionLots where ReadyProductId = \\\\\'C1A626A7-E181-4CD8-8E7A-EAC19DDB2B61\\\\\'select lotnumber", "Comment 61: * from ProductionLots where recipeid in (\\\\\'64FCA566-0933-48B1-B569-560CB1737B42\\\\\'", "Comment 62: \\\\\'17D9E9E0-31E7-401E-8DF7-ED5E447C5C04\\\\\')select * from Items where id in ( \\\\\'BAC9E85F-0B80-4371-8459-461D2C0F9184\\\\\'", "Comment 63: \\\\\'A4018A7F-5DDC-468E-90A5-DA5AD769A4D2\\\\\')select * from Recipes where id in (\\\\\'64FCA566-0933-48B1-B569-560CB1737B42\\\\\'", "Comment 64: \\\\\'17D9E9E0-31E7-401E-8DF7-ED5E447C5C04\\\\\')select * from RecipeElements where id in (\\\\\'64FCA566-0933-48B1-B569-560CB1737B42\\\\\'", "Comment 65: \\\\\'17D9E9E0-31E7-401E-8DF7-ED5E447C5C04\\\\\')select * from RecipeElements r1join items i on i.id = r1.ItemIdfull outer join RecipeElements r2 on r1.ItemId =r2.ItemId and r2.id=\\\\\'17D9E9E0-31E7-401E-8DF7-ED5E447C5C04\\\\\'where r1.id in (\\\\\'64FCA566-0933-48B1-B569-560CB1737B42\\\\\') order by r2.Noselectselect * from Items where--itemtype = 1id = \\\\\'BAC9E85F-0B80-4371-8459-461D2C0F9184\\\\\' 118 1select * from cdn.b9a646dd-dc8b-4e3d-933d-d1251013f306\'", "Comment 66: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'", "Comment 67: \'[^ProductionLotConfirmedEvent.txt]\'", "Comment 68: \'PLR is now in DHC!image-2023-01-24-09-17-38-012.png!\'", \'Comment 69: "Hello Piotr,I checked and now it\\\'s correct. Do you know why we had this problem?"\', "Comment 70: \'This problem with PLR should be treated as an incident,the next time an error occurs an RCA will be created.We had to resend the message to DHC.Regards.\'", "Comment 71: \'+[[DHP 3.0] Ponowne przesłanie PLR do DHC - generowanie message jak nie ma(ostatni pkt).|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Ponowne%20przes%C5%82anie%20PLR%20do%20DHC%20&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{7502CC07-E06E-48A2-82DD-39E0D4819C77}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHP%203.0%5D%20Ponowne%20przes%C5%82anie%20PLR%20do%20DHC%20%7C7502CC07-E06E-48A2-82DD-39E0D4819C77%2F%29])+\'", "Comment 72: \'All information was provided in the last comment.This ticket is closed.Regards.\']"]\nRelated Issues:\n[]\n\n### End'}
645
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8386\n\n### Instruction:\nIn DHP tema there a re a few plr from 2020 that we would want to get rid of as it is not making the plrs presentable. can you help\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Could you please provide us with those PLRs\\\' numbers?Regards"\', "Comment 3: \'!image!\'", \'Comment 4: "Could you please clarify? Do you want us to delete them from application? Why don\\\'y you cancel them?Regards"\', "Comment 5: \'cancelling them does not remove them. please delete them form application \'", "Comment 6: \'Tych PLR nie ma w DHC", \'Comment 7: wzięłam zakres dat taki\', "Comment 8: jakie są daty na ich screenie!image-2023-01-24-15-47-13-760.png!!image-2023-01-24-15-47-13-760!\'", "Comment 9: \'!image-2023-01-24-16-26-55-534.png!\'", "Comment 10: \'Requested PLRs have been deleted from all modules in Plant. Please", "Comment 11: verify.Regards\'", "Comment 12: \'thanks it has been cleared. please close\'", "Comment 13: \'Thank you.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
646
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8385\n\n### Instruction:\nProblem z ponowną fiskalizacją fs91/01/22/Łpoz\r\nBłąd w załączniku \r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Could you please clarify why are you trying to fiscalize FV second time?Regards\'", "Comment 4: \'Jednak będzie bez fiskalizacji. Błąd uzytkownika Temat do zamknięcia \'", "Comment 5: \'!image-2023-01-23-16-16-18-289.png!\']"]\nRelated Issues:\n[]\n\n### End'}
647
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8384\n\n### Instruction:\nSame problem again. After creating a VT ticket, no warehouse order is created.\r\n\r\nVT-388 Can you please check this?\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Dear Nemanja,I have restarted application again. Please\', \'Comment 3: lest me know if it helped,Can you check if the problem still occurs now and cancel the problematic VT\\\'s and re-issue?Regards"\', \'Comment 4: "Again the same problem\', \'Comment 5: now we can\\\'t see wo for vt VT-422/1/23"\', "Comment 6: \'VT-422/1/23id=fab8158a-2be8-4ae8-8975-81dace95aa07\'", "Comment 7: \'Log jest po modify date", \'Comment 8: po id czy numerze VT\', "Comment 9: nic!image-2023-01-24-14-14-52-290.png!{code:java}2023-01-24 11:52:29 (0d514f08-657b-46e3-a3fe-8f9b788144a1/Plant.WMS.BusinessLogic/RSIIS01/17904/9) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CreatePerformDispatchWarehouseOrderCommand](Plant.WMS.BusinessLogic.Application.Interfaces.WarehouseOrders.Commands.CreatePerformDispatchWarehouseOrderCommand) methodKotrak.Common.Application.Exceptions.BusinessLogicException: Item 20365-B10 is archived ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: ItemIsArchivedMessage at Plant.WMS.BusinessLogic.Application.WarehouseOrders.WarehouseOrderService.GetItemOrThrow(AggregateId itemId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseOrders\\\\\\\\WarehouseOrderService.cs:line 1078 at Plant.WMS.BusinessLogic.Application.WarehouseOrders.WarehouseOrderService.AssertCreateWarehouseOrderElement(CreateWarehouseOrderElementDataStructure elementDataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseOrders\\\\\\\\WarehouseOrderService.cs:line 909 at Plant.WMS.BusinessLogic.Application.WarehouseOrders.WarehouseOrderService.CreatePerformDispatchWarehouseOrder(CreateWarehouseOrderDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseOrders\\\\\\\\WarehouseOrderService.cs:line 188 at Plant.WMS.BusinessLogic.Application.WarehouseOrders.WarehouseOrderService.CreatePerformDispatchWarehouseOrders(CreateWarehouseOrderDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseOrders\\\\\\\\WarehouseOrderService.cs:line 207 at Plant.WMS.BusinessLogic.Application.Workflows.WorkflowRunner.Run(Workflow workflow) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\Workflows\\\\\\\\WorkflowRunner.cs:line 17 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) --- End of inner exception stack trace ---{code}\'", \'Comment 10: "{code:java}SELECT * FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketPackedDispatchElements] where SourceDocumentNumber = \\\'SO-226/1/23/S\\\' order by No desc SELECT * FROM [DHPlantVCBusinessLogicMain].[dbo].[Items] where id in (\\\'C8F78926-607A-451B-BE62-16BCB2C84395\\\',\\\'EBAE1313-DC15-47AE-B641-AF19C501D61C\\\',\\\'83E9AD90-9DD0-48F8-B156-46AF9506201F\\\',\\\'6006F666-ABE4-488F-9159-D95C6B3D0831\\\',\\\'FEE125C4-63DD-49DD-95ED-49D65F0EF9B1\\\',\\\'87BD8B45-7ACA-4482-9100-15A53B851FBB\\\',\\\'9C020A11-3003-4173-9C47-3939161D4781\\\',\\\'6B183163-82B0-4C40-987B-4BFF53A9B729\\\',\\\'59F2C964-483E-4A51-908C-76AF65996B02\\\',\\\'7A82B2B7-0B5C-497A-9F2E-DBD5F6BC5CAC\\\'){code}"\', "Comment 11: \'!image-2023-01-24-14-16-50-642.png!\'", "Comment 12: \'!image-2023-01-24-14-21-06-569.png!\'", "Comment 13: \'VT-388/1/23id = e4748ffa-6475-42ed-8235-2616e87d6f90!image-2023-01-24-14-24-07-988.png!\'", "Comment 14: \'I am asking for a quick solution", "Comment 15: our loadings are at a standstill due to the non-generation of WO in the warehouse.\'", "Comment 16: \'Dar Nemanja,For VT-422/1/23 item20365-B10 is archaived. The same issue with VT-388", "Comment 17: item 20583-B10 is archaived. Maybe someone has archived them after processing VT? Is there such possibility?Regards\'", "Comment 18: \'Nevertheless", "Comment 19: those two items cause the issue.\'", "Comment 20: \'Ok", "Comment 21: i will check now with our product manager.\'", "Comment 22: \'Thank you. Waiting for your feedback then.Regards\'", "Comment 23: \'Hi,Any feedback?Regards\'", "Comment 24: \'Everything is ok for now. The product manager unarchived the codes that he archived by mistake. There is no problem with creating a WO for now.\'", "Comment 25: \'Great. So I am closing this task. If the issue reoccurs", "Comment 26: please raise another one.Regards\'", "Comment 27: \'Ok", \'Comment 28: tnx\', "Comment 29: you can close the ticket.\']"]\nRelated Issues:\n[\'DGS-8378\']\n\n### End'}
648
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8383\n\n### Instruction:\nDuring the puchase monitor tests, we detected a difference between the contract volumes in DHC and DH CDN.\r\n\r\nThe problem was noticed in two contracts ZZ-572/12/22 and 574/12/22. Where does this difference come from?\r\n\r\nWhen i want synchronize contracts in DHC, it\'s occurs error.\r\n\n\n### Response:\n["Comment 1: [\'!1!!2023-01-23_095833.jpg|thumbnail!!2023-01-23_100109.jpg|thumbnail!!2023-01-23_100139.jpg|thumbnail!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Sorry for the delay in response ZZ-572 - in progress - Quantity executed 24,82T", \'Comment 4: unexecuted 0,18T.ZZ-574 - executed. This first order is still as in the request\', "Comment 5: the second order is already updated(executed).What is the difference for the order ZZ-572?\'", "Comment 6: \'chodzi o ilości niezrealizowane/zrealizowane:Zrobiłem sync w DHC i się zmieniło na poprawne ilości np ZZ-54/02/23!image-2023-02-20-11-57-00-692.png!!image-2023-02-20-11-57-56-800.png!\'", \'Comment 7: "{code:java} select * FROM [Evolution_DHCountry].[dbo].[OrderElements] where OrderId in( select id FROM [Evolution_DHCountry].[dbo].[Orders] where documentnumber like \\\'zz-54/02/23\\\' and status=3) select * FROM [Evolution_DHCountry].[dbo].[ContractElements] where ContractId=\\\'D5EBAC15-3E21-470A-BB27-A9221AABFD00\\\' select * FROM [Evolution_DHCountry].[dbo].[Contracts] where OrderId=\\\'7A144BD5-055F-4E50-AC66-5C2AF367C6E4\\\' select * FROM [Evolution_DHCountry].[dbo].[Orders] where documentnumber like \\\'zz-54/02/23%\\\' and status=3{code}"\', "Comment 8: \'{code:java} select UnexecutedQuantity as ilosc1,QuantityInTransit as ilosc2,rez.rez_ilosc as rezerwacja", \'Comment 9: [CDN].nazwaobiektu ( rez.rez_zrdtyp\', "Comment 10: rez.rez_zrdnumer,1,2) as numer,* FROM [sql03-20\\\\\\\\dhapp].[Evolution_DHCountry].[dbo].[ContractElements] dhccinner join [sql03-20].[DhcErpPlugin].[dbo].[ContractSyncs] erpc on dhcc.contractid=erpc.dhcid inner join [sql03-20].[CDNXL_DEHEUS].[CDN].[Rezerwacje] rez on rez.Rez_ZrdNumer=erpc.xlid and dhcc.ElementNo=rez.Rez_zrdlp where (dhcc.UnexecutedQuantity<>rez.rez_ilosc and dhcc.QuantityInTransit<>rez.rez_ilosc and (dhcc.UnexecutedQuantity+dhcc.QuantityInTransit<>rez.rez_ilosc)){code}\'", "Comment 11: \'po resent zeszło do 122 z prawie 700.\'", "Comment 12: \'{code:java}2023-02-20 20:00:00,003 [DefaultQuartzScheduler_Worker-3] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job Contracts.ContractsSynchronization2023-02-20 20:00:00,003 [DefaultQuartzScheduler_Worker-3] DEBUG Evolution.DHCountry.Logging.DomainCommandHandlerWithLog4NetTracing [(null)] - Handled command [Evolution.DHCountry.Documents.Contracts.Commands.SynchronizeERPContractsCommand] by command handler [Evolution.DHCountry.Domain.DomainCommandHandlerWithPublishingEvents] under domain context [1749f5579d6144c28c2ed916e979d630]2023-02-20 20:00:00,191 [DefaultQuartzScheduler_Worker-3] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction2023-02-20 20:00:01,214 [217] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Documents.Contracts.Events.ContractChangedEvent] to publisher [Evolution.Events.EventPublisher] under domain context [c39bb8b8f3f84c44b71a0df42cd11d7e]2023-02-20 20:00:01,292 [217] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Documents.Contracts.Events.ContractChangedEvent] to publisher [Evolution.Events.EventPublisher] under domain context [a84ee29a598f4a46bb549563c6df46d7]2023-02-20 20:00:01,402 [217] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Documents.Contracts.Events.ContractChangedEvent] to publisher [Evolution.Events.EventPublisher] under domain context [bd1cd41215f3423886f88b83c2d2a9e1]2023-02-20 20:00:01,481 [217] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Documents.Contracts.Events.ContractChangedEvent] to publisher [Evolution.Events.EventPublisher] under domain context [430c707837ac41639695d8c2bc699ffb]{code}!image-2023-02-21-13-43-30-571!\'", "Comment 13: \'{code:java}WHERE ZaN_GIDTyp = 960 AND ZaN_ZamTyp = 1152 AND ZaN_DataWystawienia BETWEEN @DateFrom AND @DateTo AND EXISTS( SELECT ZaE_GIDNumer", "Comment 14: ZaE_GIDLp FROM CDN.ZamElem INNER JOIN CDN.Magazyny M WITH (NOLOCk) ON M.Mag_GidNumer = ZaE_MagNumer WHERE ZaE_GIDNumer = ZaN_GIDNumer AND ZaE_GidTyp=ZaN_GidTyp AND M.Mag_Kod IN @Warehouses){code}\'", "Comment 15: \'The mechanism works so that documents from the last seven days are synchronized at 20:00", \'Comment 16: the date of issue is what counts(ZaN_DataWystawienia).As for the update\', \'Comment 17: should be perform manual synchronization\', \'Comment 18: but by selecting the appropriate factory and the appropriate date range.If there are still inaccuracies after manual synchronization\', \'Comment 19: please provide a specific examples(after successful manual synchronization).If a change in automatic synchronization is required\', "Comment 20: it should be reported to GDC.\'", "Comment 21: \'I think you can close this task.\']"]\nRelated Issues:\n[]\n\n### End'}
649
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8382\n\n### Instruction:\nFeed Sale document posted as Expenses.\r\nCustomer Mensing 006174\r\n\n\n### Response:\n["Comment 1: [\'{color:black}Goodmorning,{color} {color:black}{color} {color:black}In customer Mensing 006174 we missed some feed sale documents. I made a manual posting in Feed Sale for these.{color}{color:black}{color} !image001!{color:black}{color}{color:black}{color} {color:black}Strange thing is that these lines are shown in expenses.{color} {color:black}When opening these lines it switch back to Feed Sale.{color} {color:black}These should be on Feed sale", "Comment 2: cause all lines are related to feed.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image002!{color:blue}{color}{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | |{color:blue}{color} !image003!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | |{color:blue}{color} !image004!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image006!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | \'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 4: "**Everything works as intended. On the subject card\', \'Comment 5: we see an indication of the expenses group. That\\\'s why this feed sale lane is in the expense group.!image-2023-01-23-11-54-24-165.png!"\', "Comment 6: \'Can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
650
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8381\n\n### Instruction:\nHello, good day,\r\n\r\nWe will love to transfer opening balances from 2022 to 2023.\r\n1, Chart of accounts have been moved alread and team members are working in 2023. will it affect the transfer?\r\n\r\n2. Can we select some accounts and leave some for later? \r\n\r\n3. How do we transfer the opening balances. \r\n\r\nMany thanks\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hello # Thereis no problem that you wrking and posting in 2023 before opening balance has been transferred. You must always remember that all acounts from charts of account should be tranferred before you make transfer of charts of accounts. # You can transfer like that in three ways: * transfer all accounts to obening balance as accepted", \'Comment 3: after changes in 2022 change opening balance status to Buffer and then discard opening balance and transfer it once again!image-2023-01-23-07-25-48-430.png! * second way is totransfer all accounts into opening balance as accepted\', "Comment 4: after changes in 2022 transfer once again all accounts (without discarding old opening balance). That will make you will have opening balance (with all accounts) and opening balance (with ony accounts that was changed in 2022) * third option is to transfer opening balance for delected accounts and after changes transfer again for all accounts (that will make abalne account correction as in second case)!image-2023-01-23-07-31-23-952.png! 3. You need to go to period that opening balance should be transffered ( in our case 2023) and next: * Tools-> * transfer of opening balance-> * choose if you want transfer all accounts or selected ones * selected the document status (even if you choose accepted you can change to buffer after balance account will be imported) * If you choose selected account you need to add them using add button (if you choose all accounts you should skip this step) * import opening balance using button with yellow lightning!image-2023-01-23-07-36-56-879.png!\'", "Comment 5: \'Can we close this issue?\'", "Comment 6: \'OK please ", "Comment 7: will raise another ticket if we encounter an issue.\'", "Comment 8: \'I am not able to select the General Ledger+ Bffers!image!\'", "Comment 9: \'You should be able to do it right now. Please verify.\'", \'Comment 10: "I still can\\\'t select it\', \'Comment 11: please."\', "Comment 12: \'Can we connect via team viewer ? could you give me access ?\'", "Comment 13: \'id should look like that now:!image-2023-01-27-11-19-24-241.png!\'", "Comment 14: \'it is not working please", "Comment 15: i am even using the admin user !image-1!\'", "Comment 16: \'Can we connect via team viewer ? could you give me access ?\'", "Comment 17: \'ID : 1 308 392 631PASS: yqiz1um5\'", "Comment 18: \'should be ok right now. Can I close this issue?\'", "Comment 19: \'Yes it is very ok\']"]\nRelated Issues:\n[]\n\n### End'}
651
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8380\n\n### Instruction:\nWe have problem in stock for item SUR7462-P-MD-S25, 0871141222007, produced 8695kg and was used 8695kg, but we still have 1000kg in stock. We checked on stock fisically and we don\'t have item anymore and any stocktaking was done for the item. \r\n\r\nCould you check why we still have stock for this item if was loaded?\r\n\r\nThank you.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \' !screenshot-1! !screenshot-2! \'", "Comment 3: \' !screenshot-3! !screenshot-4! !screenshot-5! 0871141222007 - 9695 kgvt-2494/22 - 8675 kgvt-214/23 - 8650 kg0872311222001 - 20 kg0871200123015 - 8650 kg\'", "Comment 4: \' !screenshot-6! !image-2023-01-23-08-39-17-569!!image-2023-01-23-08-45-11-123!\'", "Comment 5: \'For this PLR should be 0871141222007 -1000kg !screenshot-7! It can be corrected by stocktaking but for further analysis should be created RCA.Please confirm whether we treat it as an incident and after correction we close this ticket or the analysis under RCA should be created.\'", "Comment 6: \'Hello Piotr,the analysis under RCA should be created. Thank you.\'", "Comment 7: \'Hi Priscyla,RCA has been created DGS-8450.\'", "Comment 8: \'RCA has been created DGS-8450.This ticket has been closed.\']"]\nRelated Issues:\n[\'DGS-8450\']\n\n### End'}
652
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8379\n\n### Instruction:\nunder samples the field "tolerance source" has selection "latest product" which no longer functions as it should.\r\nif "latest product" is selected when you open the A/O the values appear for a second then disappear this does not happen when the actual latest version number is selected.\n\n### Response:\n["Comment 1: [\'[^both options exptd values issue.mp4] _(1,24 MB)_[^Exptd Values.mp4] _(381 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'zmieniając tolerancję z wersji receptury na ostatni produkt", "Comment 4: przy otwarciu AO kasowane są expected values dla sładników AO.\'", "Comment 5: \'po stand up. Do testów.\'", "Comment 6: \'Hello,any feedback?\'", "Comment 7: \'hej [[email protected]]", \'Comment 8: [[email protected]]\', "Comment 9: dopytajcie proszę klienta czy problem dalej występuje i czy mają świeże przykłady z wersji 8.5\'", "Comment 10: \'Dear Thabile,Could you please let us know if the issue still exists in version 8.5? If yes", "Comment 11: could you please provide us with fresh examples?Regards\'", "Comment 12: \'Hello", \'Comment 13: it appears that all new samples now default to the latest technology \', \'Comment 14: which solves the problem however if you select "latest product" expected values are still blank (recorded an example on live attached)[^8.5.mp4] _(2,97 MB)_\\\'\', "Comment 15: \'[[email protected]]jednak coś mają", "Comment 16: to było poprawione w wersji 8.5?\']"]\nRelated Issues:\n[]\n\n### End'}
653
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8378\n\n### Instruction:\nIt has been happening since this morning, but after restarting ISS, WOs appeared, but now I tried restarting IIS again, but WOs do not appear. \n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "I restarted the application pool. Can you check if the problem will still occur now and cancel the problematic VT\\\'s and re-issue?"\', "Comment 4: \'For now", \'Comment 5: everything works\', "Comment 6: we will monitor the situation.\'", "Comment 7: \'Thank you for information", "Comment 8: if the problem returns please send a specific VT number.\'", "Comment 9: \'Hello", "Comment 10: have there been any new cases?Or could you please confirm if we can close this task?Regards\'", "Comment 11: \'You can close the ticket.\'", "Comment 12: \'This task/ticket should be treated as an incident,the next time an error occurs an RCA will be created.Regards.\'", "Comment 13: \'Hi Piotr", "Comment 14: same problem again. VT 388 can you check please?\']"]\nRelated Issues:\n[\'DGS-8384\']\n\n### End'}
654
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8377\n\n### Instruction:\nPlease migrate this missing file.\r\nMissing migration 101662 Spijker NAS\n\n### Response:\n["Comment 1: [\'{color:black}Hello,{color} {color:black}{color} {color:black}Please migrate these missing files.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image001!{color:blue}{color}{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | |{color:blue}{color} !image002!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | |{color:blue}{color} !image003!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} | |{color:blue}{color} !image004!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | [^Sales migration_Spijker 101662.xlsx] _(18 kB)_[^Purchase_migration_Spijker 101662.xlsx] _(19 kB)_\'", "Comment 2: \'[[email protected]],all lines have been migrated", "Comment 3: You can feel free to test it.Best regards,Grzegorz\'", "Comment 4: \'Sorry I forgot to reply. You can resolve this as done.\'", \'Comment 5: "No problem. Thank you for a reply. I\\\'m closing the task.Best regards,Grzegorz"]\']\nRelated Issues:\n[]\n\n### End'}
655
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8376\n\n### Instruction:\nWe have again issues with address id\'s in orders. Both cases are for same customer (018896).\r\n\r\nSales order SO000055396 order and trip are sent to DHP and picked up by PCS but data is missing in VC. \r\nError can be found in DHP logging today 12:05 (see screenprints 1 and 2)\r\n\r\nWe resend customer / address and the sales order from Milas. This did not solve the issue. We need the orer and trip in DHP so that dispatch can be registered.\r\n\r\nSales order SO000055359 is in visible in DHP but trip is not visible. Order and trip information is sent to PCS. We need the trip in DHP for registration of dispatch and to load packed items. Only if we have a trip, the printout is made for packed and the warehouse order can be created.\r\nError message: see screenprint 3 and 4.\r\n\r\nWe resend the order and the trip, but this results in same error message.\r\n\r\nPlease support us in solving the issue for this customer.\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!!image-3!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "select ForeignDocumentNumber\', \'Comment 4: MainBusinessPartnerId,MainBusinessPartnerAddressId,b.code --b.CurrentAddressId,a.BusinessPartnerId,* fromorders o join BusinessPartners b on b.id=o.MainBusinessPartnerId--join Addresses a on a.BusinessPartnerId=b.Idwhere o.ForeignDocumentNumber in ( \\\'SO000055396 \\\',\\\'SO000055359\\\')"\', "Comment 5: \'!image-2023-01-20-12-59-48-553.png!\'", "Comment 6: \'ForSO000055396 the cause is the same as in DGS-8369.The order is for Main BP with code 818897but the address is linked to other BP with code018897.Please try to verify and fixed this data on order and resend it again to dhc.\'", \'Comment 7: "select UpdateDate,* from Addresses where id=\\\'39ACFF28-FC22-46F6-AC8B-C85C18DC7F8A\\\' or BusinessPartnerId=\\\'C9F0FDA3-A541-43F7-9A63-21831B7403B2\\\'select UpdateDate,* from BusinessPartners where id=\\\'EF48DAAB-5760-4F19-9E51-18894C7ED2C5\\\'or id =\\\'C9F0FDA3-A541-43F7-9A63-21831B7403B2\\\'"\', "Comment 8: \'drugie zamowienie jest w dhp gdzie trzeba : !image-2023-01-20-13-53-21-129.png!\'", \'Comment 9: \\\'przy wslce shipiing notice nadal errorAn error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ShippingNoticeElementOrders_OrderElements_OrderId_OrderNo". The conflict occurred in database "DHPlantVCBusinessLogicMain"\', \'Comment 10: table "dbo.OrderElements".The statement has been terminated.\\\'\', "Comment 11: \'Customer 818897 and 018897 have same customer name and same address details.How does DHP find the address Id for a customer? Can it be that DHP selects it based on e.g. the name and that it finds multiple results and selects the address linked to 018897 instead of the address linked to 818897? Or is this address id sent with the order from Milas?\'", "Comment 12: \'There is table bussinesspartners", \'Comment 13: everyone has his id. We do not compare names\', "Comment 14: cause will be to time consuming.And there is a table address where very address has his id and realtion to id of bussiness Partners.One address can not be linked to few diffrent BP!image-2023-01-20-14-18-35-213.png!\'", \'Comment 15: "select *from ShippingNotices where id=\\\'D3ACE234-7A5D-4256-B46A-4F4EAF98BED1\\\'select * from ShippingNoticeElements where id=\\\'D3ACE234-7A5D-4256-B46A-4F4EAF98BED1\\\'select* from ShippingNoticeElementOrderElements where id=\\\'D3ACE234-7A5D-4256-B46A-4F4EAF98BED1\\\'jest w pcs te dwa elementy na inen zamowienie psuja chyba cos!image-2023-01-20-14-23-09-740.png!"\', \'Comment 16: "tego ordera brakuje w vt =select * from orders where id=\\\'CFD5F416-0ECD-4990-80C7-A65401259960\\\'"\', "Comment 17: \'too drugie zamówienie z asn to własnie to : !image-2023-01-20-14-31-51-540.png!\'", "Comment 18: \'The second order is correctly synchro to dhp", "Comment 19: but Shipping Notice has elements from both of the orders -SO000055396 andSO000055359 so after fixing address and resending order it all shoud be in DHP.\'", \'Comment 20: "Id\\\'s / names: we checked Milas/Webmethods and indeed the combination of MainBP and address Id is not correct. The Invoice customer is sent as Main BP combined with the addressId of de the delivery customer... that is indeed not correct.We will check why the mapping was done this way. For the order: we updated Main BP id. It is now 018897. Order was updated in DHC. I am waiting to get the update in DHP. We also resent the trip (that indeed is for the two orders). As soon as the order arrives in DHP\', \'Comment 21: I think the trip will also be registered correctly in DHP.About the lookup on name: I was not sure if DHC received the address Id\', \'Comment 22: but now I see that this is the case. Indeed\', \'Comment 23: check on name is not a good idea and in this case no lookup is needed at all - because the Id is received.I will check if the update now arrives correctly."\', "Comment 24: \'Order and trip arrived in DHP and were sent to PCS. This ticket can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
656
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8375\n\n### Instruction:\nUsers were unable to confirm PLR 0662150123005 due to reservations not being assigned\r\n\r\nwe have tried to resend messages but it has not resolved the issue\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Resend messages have been needed - document creation and messages related with PLR processing. !screenshot-1! Looking at the logs in order:-ProductionOrder was missing", \'Comment 3: -SalesOrder and the cause was target Business Partner address for the day of creation was missing.Currently\', "Comment 4: it was enough to transfer the PLR \\\\u200b\\\\u200bitself.\'", "Comment 5: \'Hello", "Comment 6: thank you task can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
657
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8374\n\n### Instruction:\nI cannot make a reverse for a sales invoices. Martijn Beek also not.\r\nIt is working earlier perfect\n\n### Response:\n[\'Comment 1: ["Could you provide number of Sales Invoice which isn\\\'t possible to reverse?There are some conditions when this action is possible to use\', \'Comment 2: so we\\\'ll verify it on example."\', "Comment 3: \'Related to this issue: to this issue: [DHNLC-1157] [GL]All sectors-Credit Invoice actions to be adjusted (availability) - JIRA Kotrak S.A. It is about SR/0083 in MAS NL.\'", \'Comment 4: "Action visibilty has been changed in all sectors.Now it\\\'s possible to use action \\\'Create correction invoice\\\' fo invoices which are not involved in Saldo to pay.Only invoices which are involved in Saldo to pay which is \\\'Archived\\\' are not possible to credit.Invoices involved in Saldo to pay in \\\'Entry\\\' status are possible to credit.It\\\'s done on IBIP_DH and IBIP_DH_TESTPlease verify and confirm that it works properly."\', "Comment 5: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
658
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8373\n\n### Instruction:\nCould you reverse these SR\'s and all invoices (PI\'s and SI\'s) created from them.\r\nSR/2188\r\nSR/2189\r\nSR/2190\r\nSR/2191\r\nSR/2192\r\n\r\nThese are trade SR\'s and we cannot use this button.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Please verify now\', \'Comment 3: it should be possible.Action \\\'Create reverse SR\\\' now is also visible for Slaughtery reports: * when \\\'Full number\\\' is empty and \\\'Farmer code\\\' = 888888 * when it is Trade (full number is Trade) it is possible to reverse the SR"\', "Comment 4: \'This can be closed.\']"]\nRelated Issues:\n[\'DGS-8349\']\n\n### End'}
659
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8372\n\n### Instruction:\nProśba o podpięcie płatności WBR 2048/23 do FAI-65/01/23/WNT, komunikat:\r\n\r\n \r\n\r\nWykonywany skrypt SQL:\r\n\r\nDECLARE @KwotaRozliczenia DECIMAL(15,2);\r\n\r\nSET @KwotaRozliczenia=0;\r\n\r\nEXEC CDN.DodajRozliczenieUwzglWycene @GIDFirma=246785,@GIDTyp1=3344,@GIDNumer1=44600,@GIDLp1=1,@GIDTyp2=784,@GIDNumer2=1822755,@GIDLp2=0,@Kwota=@KwotaRozliczenia OUTPUT,@UserID=543,@DataDzisiejsza=81105,@R2ParID=NULL;\r\n\r\nSELECT @KwotaRozliczenia;\r\n\r\n \n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "The reason are manual changes on this posting (account 204-01-092563). You should unpost this document and post it again without manual changes on 2* account generated by posting scheme. Then error shouldn\\\'t appear anymore!image-2023-01-20-08-12-50-303.png!"\', "Comment 4: \'!image-1!\'", \'Comment 5: \\\'according to conversation I added new posting scheme named "FAI koszty przeł rok" please verify if problem still occurs\\\']\']\nRelated Issues:\n[]\n\n### End'}
660
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8371\n\n### Instruction:\nWe have a problem with duplication of raw materials in DHC. Can you check what the problem is?\n\n### Response:\n["Comment 1: [\'!dupliranje sirovina!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'This item has SSP code added on definition. It should be corrected. !screenshot-1! !screenshot-2! \'", "Comment 4: \'This SSP item doesn`t work. i`m asking you for help. it is urgent.\'", "Comment 5: \'Hello", "Comment 6: please check with new version of the recipe.Item has been corrected but new v. is needed.\'", "Comment 7: \'now we can not see new version\'", "Comment 8: \'New version of the recipe should be sent from DHH and Bestmix.Has another version been created?\'", "Comment 9: \'new version is created", "Comment 10: but not visible in dhp.\'", "Comment 11: \'Hi", \'Comment 12: now are in DHP !screenshot-3! please check and confirm\', "Comment 13: thanks.Regards.\'", "Comment 14: \'hi. now is ok.\'", "Comment 15: \'can you tell me how to slove this problem? if it reapears\'", "Comment 16: \'Hi,when it comes to unlinking the items from the SSP", "Comment 17: such an operation is only possible from the database.In DHC you can only do linking.\'", "Comment 18: \'All information was provided in the last comment.This ticket has been closed.\']"]\nRelated Issues:\n[]\n\n### End'}
661
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8370\n\n### Instruction:\nReports an error on IR+ AND IR-. For some reason there is nothing on those IR documents. They remain in green with the description `does not apply\'.\n\n### Response:\n["Comment 1: [\'!Screenshot_10!!Screenshot_8!!Screenshot_9!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "\\\'does not apply\\\' refers to a document without an element & looks like a problem with the erpintegrator session for XL.IR-- has been generated for this JO correctly. !screenshot-1! These can be removed and we will restart the ERPintregrator services for verification in the following days."\', \'Comment 4: "Still can\\\'t confirm JO? Did you do anything on this?"\', "Comment 5: \'Can I get a example?\'", \'Comment 6: "{color:black}{color} {color:black}{color} *From:* Nemanja Antonic (Jira) <[email protected]> *Sent:* Monday\', \'Comment 7: January 23\', "Comment 8: 2023 1:00 PM *To:* Vukota Barjaktarovic <[email protected]> *Subject:* DGS-8370 Cannot close JO | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | {color:#999999}—-—-—-—{color} {color:#999999}Reply above this line.{color} Nemanja Antonic added you as a participant. [{color:#0052CC}View request{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelpdesk.kotrak.com%2Fservicedesk%2Fcustomer%2Fportal%2F56%2FDGS-8370%3Fsda_source%3Dnotification-email&data=05%7C01%7Cvbarjaktarovic%40deheus.com%7C15b94491c28048f0efde08dafd39649d%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638100720191884788%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=mfnuWMTjhBJBvvWS1qAngW6g8urOuie8X90cEksZ3A0%3D&reserved=0] · [{color:#0052CC}Turn off this request\'s notifications{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelpdesk.kotrak.com%2Fservicedesk%2Fcustomer%2Fportal%2F56%2FDGS-8370%2Funsubscribe%3Fjwt%3DeyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJxc2giOiI3NzZjNmQ5ZWY4YzA0YzQ4MDQ3OWNlZDQ4YjMwNDQ5YWVjOGFlODZkNWU5ZDYyZDQyMGJiOGFlN2Y4YWNhZDMyIiwiaXNzIjoic2VydmljZWRlc2stand0LXRva2VuLWlzc3VlciIsImNvbnRleHQiOnsidXNlciI6IkpJUkFVU0VSMzI5MDUiLCJpc3N1ZSI6IkRHUy04MzcwIn0sImV4cCI6MTY3Njg5NDQwNSwiaWF0IjoxNjc0NDc1MjA1fQ.a2ezT0Jy5uJa3PIVLAjyfULm4FN1IVWBmBk1gxNGlU0&data=05%7C01%7Cvbarjaktarovic%40deheus.com%7C15b94491c28048f0efde08dafd39649d%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638100720192041025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8Pfg3OxBgokc%2FgWenDOf0e0fDoqpyuxC3um0rTf2E7s%3D&reserved=0] {color:#7A869A}This is shared with Nemanja Antonic", \'Comment 9: Barbara Czarnocka\', \'Comment 10: Hardy Huy\', \'Comment 11: and 12 other people.{color} {color:#7A869A}KOTRAK\', \'Comment 12: powered by{color} [{color:#7A869A}{color}{color:#0052CC} Jira Service Desk{color}{color:#7A869A}{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.atlassian.com%2Fsoftware%2Fjira%2Fservice-desk%2Fpowered-by%3Futm_medium%3Demail%26utm_source%3Dservice-desk_email-notification_server%26utm_campaign%3Dservice-desk_email-notification_server&data=05%7C01%7Cvbarjaktarovic%40deheus.com%7C15b94491c28048f0efde08dafd39649d%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638100720192041025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MP%2Fg6yEuGmEHPJ4SzJjE5K8VzYSleMy59TmSrl9mrJU%3D&reserved=0]{color:#7A869A}\', \'Comment 13: sent you this message.{color} !Screenshot_8-1!!Screenshot_9-1!"\', "Comment 14: \'!Screenshot_8-2!!Screenshot_9-2!\'", "Comment 15: \'These are examples from the first half of january and they have already generated documents", "Comment 16: are there other current examples?\'", "Comment 17: \'In Cuprija still have problem to close JO. \'", "Comment 18: \'Hello", "Comment 19: I have one0382240123009 - I will check and let you now.\'", "Comment 20: \'We have missing resources:!image-2023-01-25-09-07-08-398.png!Reservation from DHP:!image-2023-01-25-09-07-25-479.png!Deliveries created in XL:!image-2023-01-25-09-08-05-221.png!IR- document created by operator VUKBAR not by ERPintegrator.Current stock for item:!image-2023-01-25-09-09-09-934.png!Stocks are missing.\'", "Comment 21: \'that is done. but what with others JO?\'", "Comment 22: \'Please give me current example - number. I will check.\'", "Comment 23: \'!Screenshot_11!\'", "Comment 24: \'{code:java}2023-01-19 22:51:03,578 [16] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution started2023-01-19 22:51:03,609 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - GenerateJobOrder execution started2023-01-19 22:51:03,609 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Started PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b6 processing2023-01-19 22:51:03,625 [18] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating documents for PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:03,672 [18] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Job Order for PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:03,672 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generate JO by PLR data.2023-01-19 22:51:03,734 [Thread 18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - JO Created: ID - 118778 [JO-139/01/23/CU]2023-01-19 22:51:03,922 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - JO Element Created: ID - 118628 for new process 1186632023-01-19 22:51:04,000 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - Job order elemnt ID - 118628 process for item 04304 added2023-01-19 22:51:04,078 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - Job order elemnt ID - 118628 ingredient 04301 added2023-01-19 22:51:04,312 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - Job order elemnt ID - 118628 product 04304 added2023-01-19 22:51:04,937 [Thread 18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - JO Closed: ID - 118778 (2816)2023-01-19 22:51:05,015 [18] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generated JO ID - 118778 For PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b6 - BY PLR2023-01-19 22:51:05,219 [18] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Release for PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:05,219 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Adding Element 04301 with quantity 20000.0000 on CU2023-01-19 22:51:05,312 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalRelease created: Firma:1015297 - TYP:1616/NUMER:1635788/LP:0 IR--166/01/23/CU2023-01-19 22:51:05,437 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalRelease Element Created: Firma:1015297 - TYP:1616/NUMER:1635788/LP:12023-01-19 22:51:05,531 [12] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 16357882023-01-19 22:51:05,562 [12] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 16357882023-01-19 22:51:05,578 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalRelease Document Confirmed: Firma:1015297 - TYP:1616/NUMER:1635788/LP:02023-01-19 22:51:05,640 [18] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generated IR- Firma:1015297 - TYP:1616/NUMER:1635788/LP:0 For PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:05,719 [18] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Receipt for PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:05,782 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalReceipt created: Firma:1015297 - TYP:1617/NUMER:1635789/LP:0 IR+-149/01/23/CU2023-01-19 22:51:05,891 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalReceipt Element Created: Firma:1015297 - TYP:1617/NUMER:1635789/LP:12023-01-19 22:51:05,985 [12] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 16357892023-01-19 22:51:06,016 [12] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 16357892023-01-19 22:51:06,031 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalReceipt Document Confirmed: Firma:1015297 - TYP:1617/NUMER:1635789/LP:02023-01-19 22:51:06,063 [18] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generated IR+ Firma:1015297 - TYP:1617/NUMER:1635789/LP:0 For PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:06,157 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - PLR processing finished2023-01-19 22:51:06,157 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - GenerateJobOrder execution finished2023-01-19 22:51:06,157 [16] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution finished{code}\'", "Comment 25: \' !screenshot-2! \'", \'Comment 26: \\\'When closing the job orders problematic one\\\\\\\'s were 106 and 115 - there was a problem with the lack of a fixed cost due to the fact that the documents referred to each other. A manual change had to be made for the delivery - IR+. !screenshot-3! You can check problematic IR+ with graph - "documents with unfixed costs" . You should close the related JO before closing the problematic one. !screenshot-4! If there is a problem with this please choose Fixed delivery value on IR+(which is the delivery).Currently\', "Comment 27: job orders are closed.Can you check if there are any other problems.\'", "Comment 28: \'Could you please confirm if we can close this task?Regards\'", "Comment 29: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 30: please raise another task.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
662
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8369\n\n### Instruction:\nHello, \r\n\r\n this is reported many times, but problem still occurs: In maasbracht I have 2 orders not synced to VC module:\r\nSO000050086\r\nSO000050108\r\n\r\nPlease can you check again the case and mayby perform root cause analysis to get rid of this issue? \n\n### Response:\n["Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\rAgnieszka Januszewska\'", "Comment 2: \'Same applies SO000047783", "Comment 3: SO000052890\'", "Comment 4: \'ciepie sie o adres ponowna wysylka adresu i zamówienia nie pomogłaselect MainBusinessPartnerId,MainBusinessPartnerAddressId,* from orders where ForeignDocumentNumber in ( \\\\\'SO000050086\\\\\',\\\\\'SO000050108\\\\\'", "Comment 5: \\\\\'SO000047783\\\\\'", \'Comment 6: \\\\\\\'SO000052890\\\\\\\')select * from OrderExportInfoes where EntityId=\\\\\\\'1D94C9A0-0F06-45E0-B143-AE315ADB0D40\\\\\\\'select UpdateDate,* from Addresses where id=\\\\\\\'D8294CF0-D490-4E50-9AC2-1972730AAEA8\\\\\\\'select* from AddressExportInfoes where EntityId=\\\\\\\'D8294CF0-D490-4E50-9AC2-1972730AAEA8\\\\\\\' and ClientId=\\\\\\\'F1300CAE-63B3-4F46-AD2E-1023E3748092\\\\\\\'select UpdateDate,* from BusinessPartners where id=\\\\\\\'BB3FECBE-0583-4256-A7E5-982A1521B8AB\\\\\\\'select * from BusinessPartnerExportInfoes where entityid=\\\\\\\'BB3FECBE-0583-4256-A7E5-982A1521B8AB\\\\\\\' and ClientId=\\\\\\\'F1300CAE-63B3-4F46-AD2E-1023E3748092\\\\\\\'An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Orders_ContactDatas_MainBusinessPartnerId_MainBusinessPartnerContactDataId". The conflict occurred in database "DHPlantVCBusinessLogicMain"\', \'Comment 7: table "dbo.ContactDatas".The statement has been terminated.\\\'\', \'Comment 8: "adrs domyslny jest inny =select UpdateDate,* from Addresses where id=\\\'D8294CF0-D490-4E50-9AC2-1972730AAEA8\\\' or id=\\\'0C00D6AE-8BA4-4C7A-8416-4DD0DDCCED20\\\'"\', "Comment 9: \'For ordersSO000052890,SO000050108,SO000047783 is set BusinessPartner with code100064But has set addres that is not linked with the BP100064 but with BP code 000168.!image-2023-01-20-08-16-31-395.png!So please try to send this orders with consistent data this is the current address fo that customer:!image-2023-01-20-08-19-09-035.png! If address is for data from the other BP :!image-2023-01-20-08-21-12-701.png!You may add similar address for BP or use as mainpartner BP000168.\'", "Comment 10: \'For orderSO000050086 the bussiness partner is009907 but the address is the current address from diffrent BP with code00097K\'", "Comment 11: \'mają na orderach adresy przypsane do innych BP - ciekawe co odpiszą,\'", "Comment 12: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
663
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8368\n\n### Instruction:\nChanhe Main and Target adress from 7727 to 0674.\r\n\r\n(Payer has already been changed)\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.RegardsAgnieszka Januszewska\'", "Comment 3: \'Dear Bert,Main", "Comment 4: and Target have been changed!image-2023-01-19-13-23-10-842.png|width=1052,height=195!!image-2023-01-19-13-23-37-125.png|width=1201,height=242!Regards\'", "Comment 5: \'[^DGS-8368.xlsx]\'", \'Comment 6: "{code:java}select TrN_KnPNumer\', \'Comment 7: TrN_AdPNumer\', \'Comment 8: TrN_KnDNumer\', \'Comment 9: TrN_AdWNumer\', \'Comment 10: TrN_KntNumer\', \'Comment 11: TrN_KnANumer\', \'Comment 12: * from cdn.tranag where TrN_GIDTyp=2037 AND TrN_GIDFirma=1015303 AND TrN_GIDNumer=3375490select knt_gidnumer\', \'Comment 13: KnA_GIDTyp\', "Comment 14: a.KnA_GIDNumerfrom cdn.KntKartyjoin cdn.KntAdresy a on KnA_KntNumer=Knt_GIDNumerwhere Knt_Akronim like \'%0674%\' and KnA_DataArc=0 and KnA_GIDTyp=864--UPDATE cdn.tranag set TrN_KnDNumer = 1060", \'Comment 15: TrN_AdWNumer = 3130\', \'Comment 16: TrN_KntNumer = 1060\', \'Comment 17: TrN_KnANumer = 3130 --where TrN_GIDTyp=2037 AND TrN_GIDFirma=1015303 AND TrN_GIDNumer=3375490{code}"\', "Comment 18: \'I asked user if it is oke.\'", "Comment 19: \'Waiting for your feedback then.Regards\'", "Comment 20: \'Again I asked user if it is oke.So far no answer\'", "Comment 21: \'ok\'", "Comment 22: \'Should be correct,.Ticket can be closed!image-3!\']"]\nRelated Issues:\n[]\n\n### End'}
664
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8367\n\n### Instruction:\nHi\r\n\r\nWe are trying to move the UL barcode 87-W007OI to the EMBALAGEM location. However, system displays an error message.\r\n\r\nAlso, when I try to filter EMBALAGEM location in WMS Unitloads screen, an Internal error occurres.\r\n\r\nCould you please help us with this issue?\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.RegardsAgnieszka Januszewska\'", "Comment 3: \'HelloDo we have any news about this?Thnk you\'", "Comment 4: \'We are analyzing the problem.\'", \'Comment 5: \\\'{code:java}2023-01-20 13:56:47 (cbddcadc-d97e-4649-b7eb-31e497a23c64/Plant.WMS.BusinessLogic/BR-4-SV-VM0204/11584/217) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 6: "host": { "Value": "br-4-sv-vm0204:85"\', \'Comment 7: "HasValue": true\', \'Comment 8: "Host": "br-4-sv-vm0204"\', \'Comment 9: "Port": 85 }\', \'Comment 10: "path": "/api/WarehouseMovement/registerMultipleMovements"\', \'Comment 11: "queryString": []\', \'Comment 12: "requestBody": "{\\\\\\\\"movementData\\\\\\\\":[{\\\\\\\\"unitLoadId\\\\\\\\":\\\\\\\\"fb595f60-c10d-49db-8502-1057a7d0710d\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"pcs\\\\\\\\",\\\\\\\\"value\\\\\\\\":5318},\\\\\\\\"destinationLocationId\\\\\\\\":\\\\\\\\"6636b77f-3e39-43ce-9ebe-e168ca0c0180\\\\\\\\"}]}"}.System.ArgumentException: Unit mismatch at Kotrak.Common.SharedKernel.Extensions.QuantityExtensions.<>c__9`1.<Sum>b__9_0(Quantity x\', \'Comment 13: Quantity y) at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source\', \'Comment 14: TAccumulate seed\', \'Comment 15: Func`3 func) at Kotrak.Common.SharedKernel.Extensions.QuantityExtensions.Sum[T](IEnumerable`1 source\', \'Comment 16: Func`2 selector) at Plant.WMS.BusinessLogic.Domain.WarehouseMovements.ExplicitMapping.ToFastMovementValidationData(FastMovementDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Domain\\\\\\\\WarehouseMovements\\\\\\\\ExplicitMapping.cs:line 25 at Plant.WMS.BusinessLogic.Domain.WarehouseMovements.Services.FastMovementDomainService.GenerateFastMovement(FastMovementDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Domain\\\\\\\\WarehouseMovements\\\\\\\\Services\\\\\\\\FastMovementDomainService.cs:line 58 at Plant.WMS.BusinessLogic.Application.WarehouseMovements.FastWarehouseMovementService.RegisterMultipleFastMovements(MultipleFastMovementDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseMovements\\\\\\\\FastWarehouseMovementService.cs:line 74 at Plant.WMS.BusinessLogic.Application.Workflows.WorkflowRunner.Run(Workflow workflow) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\Workflows\\\\\\\\WorkflowRunner.cs:line 17 at Plant.WMS.BusinessLogic.Application.WarehouseMovements.Handlers.RegisterMultipleFastMovementsCommandHandler.Handle(RegisterMultipleFastMovementsCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseMovements\\\\\\\\Handlers\\\\\\\\RegisterMultipleFastMovementsCommandHandler.cs:line 39 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Plant.WMS.BusinessLogic.Infrastructure.Api.Controllers.WarehouseMovementController.RegisterMultipleMovements(RegisterMultipleMovementsViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\WarehouseMovementController.cs:line 114 at lambda_method47002(Closure \', \'Comment 17: Object \', \'Comment 18: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 19: ObjectMethodExecutor executor\', \'Comment 20: Object controller\', \'Comment 21: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 22: Scope& scope\', \'Comment 23: Object& state\', \'Comment 24: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 25: Scope& scope\', \'Comment 26: Object& state\', \'Comment 27: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 28: Task lastTask\', \'Comment 29: State next\', \'Comment 30: Scope scope\', \'Comment 31: Object state\', \'Comment 32: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 33: Task task\', \'Comment 34: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 35: Task task\', \'Comment 36: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 37: Task requestTask\', \'Comment 38: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', "Comment 39: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'", \'Comment 40: "Done\', "Comment 41: one barcode \'87-OB00G4\' has bag size unit= pcs", \'Comment 42: should be kg for destination location. !screenshot-1! "\', "Comment 43: \'Hi PiotrThank you very muchYou can close this task\'", "Comment 44: \'Hi MaiconYou are welcome.Regards.\']"]\nRelated Issues:\n[]\n\n### End'}
665
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8366\n\n### Instruction:\nProduction from the 16th, 17th and 18th are not generation JO documents in ERP. Kindly assist. seems like synchronization is failing. thank you\n\n### Response:\n["Comment 1: [\'please cancelsolved internally\'", "Comment 2: \'Thanks for the information.\']"]\nRelated Issues:\n[]\n\n### End'}
666
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8365\n\n### Instruction:\nGood afternoon,\r\n\r\nPlease, would you create an openings balance for item code: 088127 on plant: Nijkerk. Quantity 5 pcs.\r\n\r\nKind regards,\r\n\r\nGerard\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Opening balance for item has been created.\'", "Comment 3: \'Goodmorning Piotr,Thanks for support on this.Please", "Comment 4: close this ticket.Regards,Gerard\']"]\nRelated Issues:\n[]\n\n### End'}
667
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8364\n\n### Instruction:\nRecipe for 506960 is in DHH and DHC, but does not appear in DHP Sneek.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'I see the recipe has arrived.Ticket can be closed", "Comment 3: thanks.\']"]\nRelated Issues:\n[]\n\n### End'}
668
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8363\n\n### Instruction:\nTwo sales orders are not arriving in DHP Sneek. Can you please check why? The orders are in DHC. \n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "!image-2023-01-18-14-07-53-248.png!{code:java}SELECT DocumentNumber\', "Comment 3: * FROM [DHCountry_NL_AS400_PROD].[dbo].[Orders] where DocumentNumber = \'SO000054520\'SELECT * FROM [DHCountry_NL_AS400_PROD].[dbo].[OrderElements] where OrderId = \'7F273905-B08B-4677-A87E-32D466639425\'SELECT DocumentNumber", \'Comment 4: * FROM [DHCountry_NL_AS400_PROD].[dbo].[Orders] where DocumentNumber = \\\'SO000054522\\\'SELECT * FROM [DHCountry_NL_AS400_PROD].[dbo].[OrderElements] where OrderId = \\\'D02C7757-324B-43C1-8F0E-257D914541A5\\\'{code}"\', "Comment 5: \'Brak orderów w DHC Service:!image-2023-01-18-14-09-07-053.png!\'", "Comment 6: \'{code:java}2023-01-18 09:59:23,723 [31] INFO Evolution.DHCService.Dhc30.Handlers.OrderChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:37] - Receiving message (Evolution.DHCountry.Interfaces.Orders.Messages.OrderChangedMessage) [Id:7f273905-b08b-4677-a87e-32d466639425]2023-01-18 09:59:23,738 [31] INFO Evolution.DHCService.Dhc30.Handlers.OrderChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:49] - Message received successfuly!{code}\'", "Comment 7: \'{code:java}2023-01-18 09:59:57,385 [85] INFO Evolution.DHCService.Dhc30.Handlers.OrderChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:37] - Receiving message (Evolution.DHCountry.Interfaces.Orders.Messages.OrderChangedMessage) [Id:d02c7757-324b-43c1-8f0e-257d914541a5]2023-01-18 09:59:57,401 [85] INFO Evolution.DHCService.Dhc30.Handlers.OrderChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:49] - Message received successfuly!{code}\'", "Comment 8: \'W DHC Service item nie wpadł też!image-2023-01-18-14-15-35-451.png!\'", "Comment 9: \'!image-2023-01-18-14-17-48-701.png!\'", "Comment 10: \'Dear Theo,Please resent Orders from Milas. Then it should be fine.Regards\'", \'Comment 11: "Hi Aleksandra\', "Comment 12: I have exported them again. Don\'t see them in DHP (yet)", \'Comment 13: but perhaps i\\\'m a bit impatient :) What did you do in order to get them through?"\', "Comment 14: \'Yes I see them in DHP\'", \'Comment 15: "Well\', \'Comment 16: the Item from the Orders was not in DHC Service and this caused the issue. I had to resend DHH item\', \'Comment 17: then resynced recipe\', \'Comment 18: production recipe and technology. It may take a while untl Orders will be reprocessed :). Let\\\'s wait a bit.Regards"\', \'Comment 19: "Oh\', \'Comment 20: that\\\'s great. In that case can we close this task? :)"\', "Comment 21: \'Yes please", "Comment 22: close the task. Thank you very much for your help\'", "Comment 23: \'No problem. Thank you\'", "Comment 24: \'zrobiłam resync brakujących towarów:--110122 recipe not accepted--140135", \'Comment 25: wysłałam wszystko w dhc (recipe\', "Comment 26: prod recipe i tehno)--306891 recipe not accepted\']"]\nRelated Issues:\n[]\n\n### End'}
669
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8362\n\n### Instruction:\nDea, \r\nwe don´t see label for 2287 in DHP Bestovice. Pls solve it asap. We need it today afternoon.\r\n\r\nit´s in DHH - info from Holland.\r\nthx, Lucy\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'The item was not linked. I have linked item. Please", "Comment 3: verify if this is fine for you.Regards\'", "Comment 4: \'Hi", "Comment 5: it is okay now. thxHow is it possible taht it wasn´t linked? It was linked because if not I wouldn´t see recipe.Did I do sth wrong?Lucy\'", "Comment 6: \'This is well known issue for DHC version lower than 55. The best way to avoid this situation is to upgrade DHC to the highest version.Please", "Comment 7: let us know if we can close this task.Regards\'", "Comment 8: \'Yes", "Comment 9: you can close it.\']"]\nRelated Issues:\n[]\n\n### End'}
670
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8361\n\n### Instruction:\nWhen partial items are loaded, i.e. partial quantities of items, then loading other items and reloading the first item, the system miscalculates quantities, increases them\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-01-19-11-11-01-049.png!\'", "Comment 4: \'Hi,Is the issue repetitive - did it occure for oter VTs? What about other plants", "Comment 5: does the issue occur for all or only for Spytkowice?Regards\'", "Comment 6: \'!image-2023-01-19-11-50-44-790.png!W logach na godzinę initial i na end!image-2023-01-19-11-52-30-336.png!{code:java}System.NullReferenceException: Object reference not set to an instance of an object. at BinaryData.Browser.barButtonItemSaveAs_ItemClick(Object sender", \'Comment 7: ItemClickEventArgs e) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHP-DHPD957-JOB1\\\\\\\\BinaryData\\\\\\\\Browser.cs:line 107 at DevExpress.XtraBars.BarItem.OnClick(BarItemLink link) at DevExpress.XtraBars.BarButtonItem.OnClick(BarItemLink link) at DevExpress.XtraBars.BarItemLink.OnLinkClick() at DevExpress.XtraBars.BarButtonItemLink.OnLinkClick() at DevExpress.XtraBars.BarItemLink.OnLinkAction(BarLinkAction action\', \'Comment 8: Object actionArgs) at DevExpress.XtraBars.BarButtonItemLink.OnLinkAction(BarLinkAction action\', \'Comment 9: Object actionArgs) at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.ClickLink(BarItemLink link) at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.UnPressLink(BarItemLink link) at DevExpress.XtraBars.Ribbon.Handler.BaseRibbonHandler.OnUnPressItem(DXMouseEventArgs e\', \'Comment 10: RibbonHitInfo hitInfo) at DevExpress.XtraBars.Ribbon.Handler.BaseRibbonHandler.OnUnPress(DXMouseEventArgs e\', \'Comment 11: RibbonHitInfo hitInfo) at DevExpress.XtraBars.Ribbon.Handler.RibbonHandler.OnUnPress(DXMouseEventArgs e\', \'Comment 12: RibbonHitInfo hitInfo) at DevExpress.XtraBars.Ribbon.Handler.BaseRibbonHandler.OnMouseUp(DXMouseEventArgs e) at DevExpress.XtraBars.Ribbon.Handler.RibbonHandler.OnMouseUp(DXMouseEventArgs e) at DevExpress.XtraBars.Ribbon.RibbonControl.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WmMouseUp(Message& m\', \'Comment 13: MouseButtons button\', \'Comment 14: Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at DevExpress.Utils.Controls.ControlBase.WndProc(Message& m) at DevExpress.XtraBars.Ribbon.RibbonControl.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd\', \'Comment 15: Int32 msg\', \'Comment 16: IntPtr wparam\', "Comment 17: IntPtr lparam){code}\'", "Comment 18: \'yes", \'Comment 19: this problem is repetitive\', \'Comment 20: in each such cases\', "Comment 21: please check at this moment Spytkowice\'", "Comment 22: \'Co udało mi się ustalić:>> info od Marcina:Logika systemu działa chyba tak", \'Comment 23: że jak załadują pierwszy element na 3t potem kolejny towar na drugi element 3 Tpo czym wrócą do 1 elementu i doładują 3t żeby niby było 6t na 1 a 3t na 2. To na koniec mają po 6t na każdym lub na 1 jest 3t a na drugim jest 6tLogikę pisał Tomek Nojek\', \'Comment 24: a uzgadniał Paweł Ogieła>> info od Tomka:Tomkowi też się tak wydaje\', \'Comment 25: że system nie jest przygotowany na wielokrotny zasyp do tej samej komory i mogą się pojawić błędy w takim przypadku i\', "Comment 26: żebyłaby potrzebna analiza kodu do rejestracji tych zasypów\'", "Comment 27: \'Hello,We have analised your case. The system does not support partial loading. If there is a need from your side", "Comment 28: please raise a GDC task.Regards\'", "Comment 29: \'Hello,We have analised your case. The system does not support partial loading. If there is a need from your side", "Comment 30: please raise a GDC task.Regards\'", "Comment 31: \'please close this task", "Comment 32: we will do it in DHP 3.0\'", "Comment 33: \'Sure. With pleasure.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
671
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8360\n\n### Instruction:\nHi,\r\nVT number 000647, date issue 17 Jan 2023 cannot sync to DHC \n\n### Response:\n[\'Comment 1: ["odkryłam log w bazie dhc country :2023-01-17 21:39:48,816 [6] ERROR Evolution.DHCountry.Documents.VehicleTickets.Handlers.VehicleTicketChangedHandler [(null)] - System.Data.Entity.Core.EntityException: The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: MSDTC on server \\\'IDSQL02-TEST\\\' is unavailable."\', "Comment 2: \'!image-2023-01-18-12-00-50-597.png!\'", \'Comment 3: "Hello I checked one again dhc country logs and I found log from 9.38 pm logs thatMSDTC on server \\\'IDSQL02-TEST\\\' is unavailable.could you ask your It if there were any problems or maintenance during this time?"\', "Comment 4: \'Hi,I already ask to our IT Infrastructure team", \'Comment 5: the DB server was restarted at that time,and my question is\', \'Comment 6: if the server is on\', "Comment 7: is the data not automated sync again?\'", "Comment 8: \'It looks like the VT was synchronized from the PLant DB to DHC Service DB", "Comment 9: and the do not go from to DB DHCCountry.If there be no commitedate of synchronization betweenPLant DB to DHC Service DB it wil be resend but in that that case there was need to resend it again.If that restart wasscheduled it is better to do that when there are no working on DHP Plant/DHCountry users.May we close the task?\'", "Comment 10: \'ok thank you\']"]\nRelated Issues:\n[\'DGS-8355\']\n\n### End'}
672
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8359\n\n### Instruction:\nHi\r\n\r\nCan\'t generate docs to cdn.\r\n\r\nRafał Boniecki\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'the seventh VT element is different from the seventh order element !screenshot-1!DD5A1S00K-F00 ZS 7 element.DB0B1X00S-V00 VT 7 element.Were changes made to the order?\'", \'Comment 4: "We don\\\'t know but it can be..."\', "Comment 5: \'Item has been corrected.\'", "Comment 6: \'ok", "Comment 7: thanks. Task to close.\']"]\nRelated Issues:\n[]\n\n### End'}
673
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8358\n\n### Instruction:\nHi\r\nLack of vt-1227 in dhc.\r\n\r\nRafał Boniecki\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \' !screenshot-1! the weights are wrong (it looks like they should be the other way) - we can open this VT and you will correct it.\'", "Comment 4: \'We issued doc in cdn manually. Thanks for help. Task to close.\'", "Comment 5: \'Thank you for confirmation. \']"]\nRelated Issues:\n[]\n\n### End'}
674
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8357\n\n### Instruction:\nHi,\r\n\r\nPlease help this issue:\r\nVT Still In Progress, although dispatch prosess already done and VT closed come to DHC and ERP.\r\nPlease give solution and please give us route cause\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'id vtka =138014jest zamkniety w dhc", \'Comment 4: ale wyglada jakby znowu się otwarł w DHP? vth_status =1nie mamy logów\', "Comment 5: czy można zweryfikowac co sie tam podziało oprócz tego!image-2023-01-18-13-26-13-081.png!\'", "Comment 6: \'In DHc VT is in closed status we do not find error logs.From what I can see with you the logs on vehicleticketlog and vehicleticketelementlog tables are not supported. It looks like VT was opened in dhp. were there more cases like this? If this is a one-time case", "Comment 7: do you set a good status or will you do it yourself?\'", "Comment 8: \'Hi", \'Comment 9: - could you explain how it can be?- what do you mean about vehicleticketlog and vehicleticketelementlog tables are not supported ?- this is the first time case- How we can close VT\', "Comment 10: beside VT on DHC and SOR on ERP already close. And actually the truck already out from factory on 16th Jan (when issue was happened).?\'", \'Comment 11: "and one thing\', \'Comment 12: if we closed VT using manual wb on DHP interface\', \'Comment 13: I think the problem is departure date between VT Close DHP and DHC will be different\', \'Comment 14: and I don\\\'t know about the integration impact."\', "Comment 15: \'Hiad 1. we are unable to give verify it cause there is no error log", \'Comment 16: maybe you may ask operator how this Vt was proceed?Did someone change something from database>?Aboutvehicleticketlog and vehicleticketelementlog - in both tables there are no entries.If there was a one time issue and we do not have more information it looks like one-time incident. In other file logs there is no information from that hour or for that VT.By now the VT seems to be generated correctly to erp\', "Comment 17: so we may change the status from database. Do you wish us to do that?\'", "Comment 18: \'How to make table vehicleticketlog and vehicleticketelementlog can save data?please change status correctly for that vt with departure data based on dispatch close date that already recorded.\'", "Comment 19: \'Status has been changed", "Comment 20: we need to ask our developers about the solution for log monitoring.\'", "Comment 21: \'[[email protected]]ustawiłam status na 3 z 1update VehicleTicketHeader set vth_status=3 where vth_id in (138014)Pytaja jeszcze jak mieć ustawioen logowanie na tych tabelach z vt w dhp", "Comment 22: Block powinien być w przyszłym tygodniu to najwyżej zagadaj.\'", "Comment 23: \'!image-2023-01-25-07-10-26-506.png!\'", "Comment 24: \'Hello,change logging has been enabled for VT header and VT elements. Ifthe problem occurs again", "Comment 25: please create a new ticket. This one should be treated as an incident. Can we close this ticket?\'", "Comment 26: \'ok thank you for your support\']"]\nRelated Issues:\n[]\n\n### End'}
675
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8356\n\n### Instruction:\nHi, \r\n\r\n Like DGS-8304, Asia Formulation Team said they are not able to see "Replacement Price" for MTR factory(56) on DHH. On DHC, we do see as upload successfully. We don\'t know why since week 1 2023, that kinds of issue happen. No root cause is found and after some time they are able to see it. Could you please help check. \n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'!image-2023-01-18-10-44-30-958.png!\'", "Comment 3: \'{code:java}2023-01-18 08:41:51,708 [123] INFO Evolution.DHHolding.GatewayPlugin.Handlers.PriceListChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHH593-JOB1\\\\\\\\Evolution.DHHolding.GatewayPlugin\\\\\\\\GatewayPlugin\\\\\\\\BaseMessageHandler.cs:64] - Receiving message (Evolution.DHHolding.Interfaces.Prices.PriceListChangedMessage) [Id:757c4810-0a17-498a-a99b-214fc1ded538]2023-01-18 08:41:51,723 [123] INFO Evolution.DHHolding.GatewayPlugin.Handlers.PriceListChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHH593-JOB1\\\\\\\\Evolution.DHHolding.GatewayPlugin\\\\\\\\GatewayPlugin\\\\\\\\BaseMessageHandler.cs:69] - Message received successfuly!2023-01-18 08:41:52,192 [123] INFO Evolution.DHHolding.GatewayPlugin.Handlers.PriceListChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHH593-JOB1\\\\\\\\Evolution.DHHolding.GatewayPlugin\\\\\\\\GatewayPlugin\\\\\\\\BaseMessageHandler.cs:64] - Receiving message (Evolution.DHHolding.Interfaces.Prices.PriceListChangedMessage) [Id:3e2267cb-3f29-4031-9407-5b5cd5be40d3]2023-01-18 08:41:52,208 [123] INFO Evolution.DHHolding.GatewayPlugin.Handlers.PriceListChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHH593-JOB1\\\\\\\\Evolution.DHHolding.GatewayPlugin\\\\\\\\GatewayPlugin\\\\\\\\BaseMessageHandler.cs:69] - Message received successfuly!{code}\'", \'Comment 4: \\\'Dear Clara,Price list and "Replacement Price" for plant MTR are visible if we consider week 2.!image-2023-01-18-10-50-08-295.png!!image-2023-01-18-10-50-35-330.png!And week 3:!image-2023-01-18-10-52-55-533.png!!image-2023-01-18-10-54-52-556.png!Are they correct?Regards\\\'\', "Comment 5: \'At about what time replacement prices have been sent from DHC?Regards\'", \'Comment 6: "Hi\', \'Comment 7: Yes\', \'Comment 8: that\\\'s send from DHC. I don\\\'t know why Asia Team take some time to see it. Could you please check DHH received time for Week 3?"\', "Comment 9: \'Dear Clara,Replacement Price Analyses ia a report which is calculated from Price List. Someone in DHH needs to click refresh after choosing relevant week. So it does not have arrival date.When was the Price List for week 3 sent?Regards\'", "Comment 10: \'Hi", \'Comment 11: We do send it week3 at 17-Jan around 5:45 pm (MM Time) (GMT+6:30).Regards\', "Comment 12: Clara\'", "Comment 13: \'+5h:30 >> bo zmiana czasu to będzie 22:30 CET!image-2023-01-19-10-03-54-005.png!\'", "Comment 14: \'17 stycznia nic o wskazanej godzinie", \'Comment 15: a te\', \'Comment 16: które są:{code:java}2023-01-17 12:23:44,433 [17] INFO Evolution.DHHolding.GatewayPlugin.Handlers.PriceListChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHH593-JOB1\\\\\\\\Evolution.DHHolding.GatewayPlugin\\\\\\\\GatewayPlugin\\\\\\\\BaseMessageHandler.cs:69] - Message received successfuly!{code}18 stycznia pierwsz zapisy dopiero o 8 coś!image-2023-01-19-10-34-08-854.png!Ale\', "Comment 17: 17go to był Wtorek i były też P1 z opóźnieniem dla Voedershttps://helpdesk.kotrak.com/browse/DGS-8337\'", \'Comment 18: "Dear Clara,I haven\\\'t found anything suspicious in logs. Changed message has been processed successfully for Price List.However\', \'Comment 19: on the 17th there was some delay in processing in DHH\', \'Comment 20: we have received task from Netherlands regarding item delays in processing.Regards"\', "Comment 21: \'Hi", "Comment 22: Thank you for checking. I will let you know if still face same issue on next week. \'", "Comment 23: \'Shall we close ths task or put it on hold until next week?\'", "Comment 24: \'I prefer to hold till next week (26 Jan).\'", "Comment 25: \'Sure\'", "Comment 26: \'Hi", \'Comment 27: We got inform from user that this week is ok. They can see replacement price on DHH without any issue. Please close the ticket. ThanksBest Regards\', "Comment 28: Clara\'", "Comment 29: \'Hi Clara.Thank you for your information.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
676
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8355\n\n### Instruction:\nHi,\r\nVT number 000647, date issue 17 Jan 2023 cannot sync to DHC \n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", "Comment 3: \'!image-2023-01-18-08-57-12-505.png!\'", "Comment 4: \'Should be ok please verify :!image-2023-01-18-09-28-10-658.png!\'", "Comment 5: \'hi", "Comment 6: could you tell us the route cause of this problem?\'", "Comment 7: \'We need route cause to avoid this issue happen again\'", "Comment 8: \'hello?\'", "Comment 9: \'Hello,In this task we have focused on clearingandunblocking the process.I raised RootCause Analysis (RCA)task for you :DGS-8360Cause from now there is no errors in log to indentify reason quickly.May we close this task?\'", "Comment 10: \'ok thank you", "Comment 11: please close this task.\']"]\nRelated Issues:\n[\'DGS-8360\']\n\n### End'}
677
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8354\n\n### Instruction:\nHi\r\n\r\nDaily we are finding errors in DHP when we try to scan a SU barcode in PCS to load the dosing silos.\r\nMost of time we use other SU barcode fo the same delivery or we go to the WebUI and click in the _UL screen > Stocktaking UL > OK_ . Wth this action the WMS engine updates the Stock and PCS engine with correct status and quantity.\r\nHowever Quantity on Hand sometimes is fixed, sometimes not. This became too hard and it\'s becoming critical. Because is happening more and more.\r\n\r\nI could list here all SU barcodes with Stock/PCS diferences, but there is too much for each plant that has integration with PCS.\r\n\r\nYou can run this query in all of three plants with PCS integration: Apucarana, Toledo and Guararapes and you\'ll find SUs with different information about QuantityOnHand or LogisticStatus. I attached an example of Guararapes result, but you can check in all other Toledo and Apucarana plants.\r\n\r\n{noformat}\r\nSELECT\r\n\tssu.Barcode, ssu.QuantityOnHand, psu.QuantityOnHand, ssu.LogisticStatus, psu.LogisticStatus\r\nFROM DHPlantStockBusinessLogicMain.dbo.StockUnits ssu \r\n\tINNER JOIN DHPlantPCSBusinessLogicMain.dbo.StockUnits psu ON psu.Id = ssu.Id \r\nWHERE ssu.LogisticStatus & 470 = ssu.LogisticStatus\r\nAND ssu.Quantity <> 0\r\nAND (ssu.QuantityOnHand <> psu.QuantityOnHand\r\nOR ssu.LogisticStatus <> psu.LogisticStatus\r\n)\r\n{noformat}\r\n\r\nSo, could you please fix these SUs and fix the root cause of this in DHP engines communication?\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'!image!\'", \'Comment 2: "It\\\'s important to highlight that in December we had 8 DGS about communication errors between engines:* DGS-7974* DGS-8087* DGS-8184* DGS-8185* DGS-8186* DGS-8187* DGS-8203* DGS-8209I don\\\'t have *DGS - Monthly Report* of January yet\', \'Comment 3: but I can assure you that this is not the first.I think a RCA should be raised to thisThank you"\', "Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 5: \'There is already one RCA - DGS-8168I will find out if this is one case and let you know.Regards.\'", "Comment 6: \'Nasz select pokazuje to samo aktualnie są tylko te created w listopadzie.2022 !screenshot-1! . Tutaj Guararapes.\'", "Comment 7: \'Hello,the codes that are still on the list for Guararapes differences are from November:!image-2023-01-25-14-14-56-969.png!We will correct them and check if they will be new/next.I just want to confirm if the stock ones are correct.\'", "Comment 8: \'Hi PiotrWe still have some barcodes from Apucarana and some from Guararapes.Thank you!image-2!!image-3!\'", \'Comment 9: "{code:java}update supcsset supcs.Quantity=su.Quantity,supcs.QuantityOnHand=su.QuantityOnHandFROM DHPlantStockBusinessLogicMain.dbo.StockUnits suINNER JOIN DHPlantPCSBusinessLogicMain.dbo.StockUnits supcs ON supcs.id = su.idwhere --supcs.barcode <> su.barcode and supcs.Quantity<>su.Quantity and su.LogisticStatus not in(32,32800)and supcs.Quantity=0{code}{code:java}SELECT * FROM DHPlantPCSBusinessLogicMain.api.StockUnits su WHERE su.Barcode = \\\'88-W0AREG\\\'{code}{code:java}select supcs.Quantity,supcs.QuantityOnHand,supcs.Id,su.Quantity,su.QuantityOnHand,supcs.barcode,supcs.LogisticStatus,su.LogisticStatus,su.id,su.CreatedDateFROM DHPlantStockBusinessLogicMain.dbo.StockUnits suINNER JOIN DHPlantPCSBusinessLogicMain.dbo.StockUnits supcs ON supcs.id = su.idwhere --supcs.barcode <> su.barcode and supcs.Quantity<>su.Quantity and su.LogisticStatus not in(32,32800)or supcs.QuantityOnHand<>su.QuantityOnHand and su.LogisticStatus not in(32,32800){code}"\', \'Comment 10: "I corrected the codes for Guararapes.\\\'85-OB001B\\\',\\\'85-OB001G\\\',\\\'85-OB0016\\\',\\\'85-OB001F\\\',\\\'85-OB001H\\\',\\\'85-OB001L\\\',\\\'85-OB001I\\\',\\\'85-OB001D\\\'these were on the list of differences also in the last verifications with the same differences.The others codes change during production. Task is still under analysis."\', "Comment 11: \'Hello PiotrThere is this new UL:* Apucarana 88-W0AREG* Guararapes 85-W02DZYThank you\'", "Comment 12: \'Hello Maicon. The problem should not occur in version 8.5I would like to know if there will be an upgrade in the near future to fix the problem.Regards.\'", \'Comment 13: "Hi Piotr We\\\'ll plan the upgrade for the next days.You can close this task.Thank you very much"\', "Comment 14: \'Thank you for information.\']"]\nRelated Issues:\n[]\n\n### End'}
678
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8353\n\n### Instruction:\nPlease remove additional technology UT506468 from DHC Compound.\r\n\r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Additional technology UT506468 has been removed.\'", "Comment 3: \'Thanks Piotr,the ticket can be closed", "Comment 4: thank you for the support.\'", "Comment 5: \'Thank you for confirmation,\\\\rRegards.\']"]\nRelated Issues:\n[]\n\n### End'}
679
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8352\n\n### Instruction:\nwe have problem to read some barcodes on PCS, system can not identify barcodes in the integration.\r\n\r\n88-W0FHGI\r\n\r\n88-W0FHGM\r\n\r\n88-W0FHGQ\r\n\r\n88-W0FHGJ\r\n\r\nCould you please check if we have some error and why the barcodes are not available for pcs?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'!image-1!\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \' !screenshot-1! \'", "Comment 5: \'We can see this barcodes in view [api].[StockUnits] !screenshot-2! Can you ask PCS provider if the problem is not on their side?Regards.\'", "Comment 6: \'Hello", "Comment 7: do you have information according to our last comment or feedback from PCS provider?Could you please confirm if we can close this task?Regards\'", "Comment 8: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
680
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8351\n\n### Instruction:\nMissing migration 101529 Huisman NAS\r\n\n\n### Response:\n["Comment 1: [\'{color:black}Goodday,{color} {color:black}{color} {color:black}Please migrate these missing files for customer Huisman 101529.{color} {color:black}Thanks.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image001!{color:blue}{color}{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | |{color:blue}{color} !image002!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | |{color:blue}{color} !image003!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} | |{color:blue}{color} !image004!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | [^Sales migration_Huisman 101529.xlsx] _(17 kB)_[^Feed migration_Huisman 101529.xlsx] _(254 kB)_[^Purchase_migration_Huisman 101529.xlsx] _(21 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "[[email protected]],please fix data in column Del_ItmID for Feed Sale. A few items doesn\\\'t exists in Intense.I\\\'m waiting for correct data.Best regards,Grzegorz"\', "Comment 4: \'[[email protected]],All documents have been migrated into Intense Platform.You can feel free to test it.Best regards,Grzegorz\'", "Comment 5: \'Sorry I forgot to reply. You can resolve this as done.\'", \'Comment 6: "No problem. Thank you for a reply. I\\\'m closing the task.Best regards,Grzegorz"]\']\nRelated Issues:\n[]\n\n### End'}
681
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8350\n\n### Instruction:\nWhat are the conditons off printing different banking account on invoice.\r\nWill the banking account off "accounting" be used or from "adresses".\r\n\r\nIf "adresses" what are the selecting conditions off the bankingaccount?\r\nIs no bankaccount in "adresses" accepted?\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hello", "Comment 4: could please bring the path to printout template. and document number.It could be set in diffrent way for diffrent document type.this is example of path :!image-2023-01-18-14-48-46-340.png!\'", "Comment 5: \'Dear,According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task.Regards\'", "Comment 6: \'You can categorized this task as a service request.\'", "Comment 7: \'Thank you", "Comment 8: could you provide more details according to my previous question ?could please bring the path to printout template. and document number.It could be set in diffrent way for diffrent document type.this is example of path :\'", "Comment 9: \'See also DGS-8553\'", "Comment 10: \'Since a new task has been created in the same topic", "Comment 11: this one will be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
682
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8349\n\n### Instruction:\nWe should be able to reverse these even though we don’t indicate a full number. In these cases the SR’s are linked to Boer BE.\r\n The SR’s and all related invoices should be reversed.\r\nThe SR’s should be reversed as well.\xa0\n\n### Response:\n[\'Comment 1: ["How it is now:Action \\\'Create Reverse SR\\\' should be visible when on Slaughtery Report \\\'Full number\\\' is filled and selected Round in this field is active.How should it be:If \\\'Full number\\\' is empty *and* \\\'Farmer code\\\' = 888888 action should be visible for these SR documents[[email protected]]is it right?What about reversing Slaughtery Reports. As I know for now there is no functionality for creating reverse Slaughtery Report (correction of original one).How we should handle or deleting Slaughtery Reports should be possible in some cases?"\', \'Comment 2: \\\'Indeed when \\\\\\\'Full number\\\\\\\' is empty and \\\\\\\'Farmer code\\\\\\\' = 888888 action should be visible for these SR documents.Also when it is Trade (full number is Trade) it should be possible to reverse the SR. Now this is not possible.I don\\\\\\\'t get your statement "As I know for now there is no functionality for creating reverse Slaughtery Report (correction of original one)". I don\\\\\\\'t have the rights but there is a possibility to reverse SR\\\\\\\'s (see attachment).Deleting SR\\\\\\\'s is needed sometimes now after reversion. Now the reversed SR\\\\\\\'s are still part of the technical results calculation in Intense. But they shouldn\\\\\\\'t. In order to remove them they are deleted right now.I don\\\\\\\'t want users to be able to delete SR\\\\\\\'s.!image!\\\'\', \'Comment 3: \\\'{quote}Indeed when \\\\\\\'Full number\\\\\\\' is empty and \\\\\\\'Farmer code\\\\\\\' = 888888 action should be visible for these SR documents.Also when it is Trade (full number is Trade) it should be possible to reverse the SR. Now this is not possible.{quote}We can implement this change for these conditions and it could be possible.Regarding part of creating Credit Slaughtery Report:{quote}I don\\\\\\\'t get your statement "As I know for now there is no functionality for creating reverse Slaughtery Report (correction of original one)". I don\\\\\\\'t have the rights but there is a possibility to reverse SR\\\\\\\'s (see attachment).Deleting SR\\\\\\\'s is needed sometimes now after reversion. Now the reversed SR\\\\\\\'s are still part of the technical results calculation in Intense. But they shouldn\\\\\\\'t. In order to remove them they are deleted right now.I don\\\\\\\'t want users to be able to delete SR\\\\\\\'s.!image!{quote}Action \\\\\\\'Create reverse SR\\\\\\\' has few steps and there are: # Creating correct SI invoices # Creating correct PI invoices # Creating correct SI guarantees invoices # Creating S2P (if exist) # Updating field \\\\\\\'Reverse SR\\\\\\\' on Salughtery Report documentIn intense we don\\\\\\\'t have functionality of creating corrected Slaughtery Reports. Only creating documents related to Slaughtery Report.I think functionality of reversing SR is based on this task https://helpdesk.kotrak.com/browse/DHNLC-477I got a quick look at Technical results and calculations skip those SR which has marked field \\\\\\\'Reverse SR\\\\\\\'\\\'\', "Comment 4: \'Ok", "Comment 5: please extend the reverse SR functionality.\'", \'Comment 6: "Functionality has been extended.Action \\\'Create reverse SR\\\' now is also visible for Slaughtery reports: * when \\\'Full number\\\' is empty and \\\'Farmer code\\\' = 888888 * when it is Trade (full number is Trade) it is possible to reverse the SRIt\\\'s done in MAS NL sector on IBIP_DH and IBIP_DH_TEST.Please verify and confirm that is correct."\', "Comment 7: \'Zmienione zostały warunki podłączenia akcji oraz warunek wywołania akcji grupującej.\'", "Comment 8: \'My confirmation.\']"]\nRelated Issues:\n[\'DGS-8373\']\n\n### End'}
683
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8348\n\n### Instruction:\nWe have problem to accept recipe in DHC, system shows an error message and the recipe is not accept.\r\n\r\nItem SUR7721-P-MD version 2\r\n\r\nCould you please check why we can\'t accept and fix it?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", "Comment 3: \'pelniutko bledów do recipe !image-2023-01-17-13-29-39-786.png!\'", "Comment 4: \'Please check now\'", \'Comment 5: "Hello\', \'Comment 6: now it\\\'s correct. You can close this task. Thank you."]\']\nRelated Issues:\n[]\n\n### End'}
684
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8347\n\n### Instruction:\nUser M. Erp can not login DH CDN (SDNL-37717)\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'New message from user:Suddenly I can log in. ?????Please close ticket\'", "Comment 4: \'I am able to log on could you profide full operator login and from what rdp he try to log on\'", "Comment 5: \'Please close ticket\']"]\nRelated Issues:\n[]\n\n### End'}
685
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8346\n\n### Instruction:\nThe PO with number 1283/22 cannot be seen in DHP, please help solve and kindly show me how to solve this issue going forward please.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'!image-2023-01-18-07-48-19-101.png!\'", \'Comment 3: \\\'An error occurred while updating the entries. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Orders_ContactDatas_MainBusinessPartnerId_MainBusinessPartnerContactDataId". The conflict occurred in database "DHPlantVCBusinessLogicMain"\', \'Comment 4: table "dbo.ContactDatas".The statement has been terminated.\\\'\', "Comment 5: \'Please verify.\'", "Comment 6: \'please close\']"]\nRelated Issues:\n[]\n\n### End'}
686
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8345\n\n### Instruction:\nSee example\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hello,Why do you want to delete this line?It\\\'s not possible because it is feed sale line which comes from Milas\', \'Comment 4: so it\\\'s functionality related to integration with Milas implemented in Intense.In that cases you can only move feed to different round."\', \'Comment 5: "Hi Damian\', \'Comment 6: we would like to delete the yellow lines.This customer quit with his contract\', \'Comment 7: but the checkbox was still activated. So there were send from Milas while they shouldn\\\'t been send.!image-1!"\', "Comment 8: \'(68677,82796,82797,75547,98017,98016,98015) id usuniętych elementów nie usunięte z mapingów id dokumentu30878\'", "Comment 9: \'Feed Sale lane is deleted.\']"]\nRelated Issues:\n[]\n\n### End'}
687
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8344\n\n### Instruction:\nMissing migration 803319 Engelenhoven NAS\n\n### Response:\n["Comment 1: [\'{color:black}Goodmorning,{color} {color:black}{color} {color:black}Please migrate these missing files for customer Engelenhoven 803319.{color} {color:black}Thanks.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image001!{color:blue}{color}{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | |{color:blue}{color} !image002!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | |{color:blue}{color} !image003!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} | |{color:blue}{color} !image004!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | [^Purchase_migration_Engelenhoven 803319.xlsx] _(22 kB)_[^Sales migration_Engelenhoven 803319.xlsx] _(19 kB)_[^Feed migration_Engelenhoven 803319.xlsx] _(256 kB)_\'", \'Comment 2: "[[email protected]],I can\\\'t map item -505305 in Del_ItmID column forFeed migration. Could you fix it?Best regards,Grzegorz"\', "Comment 3: \'Hi", "Comment 4: you can take the item code DIVO for this. Thanks in advance.\'", "Comment 5: \'| |{color:#666666} Jong", \'Comment 6: Christine de heeft een OneDrive voor Bedrijven-bestand met u gedeeld. Klik op de onderstaande koppeling om het bestand te bekijken.{color} | | !image00001! |{color:#0072c6}{color} [{color:#0072c6}{color}{color:#0072c6}Feed migration_Engelenhoven 803319.xlsx{color}|https://deheusanimalnutrition-my.sharepoint.com/personal/cjong_deheus_com/Documents/Desktop/NAS%20Intense/Feed%20migration_Engelenhoven%20803319.xlsx?web=1]{color:#0072c6}{color}{color:#0072c6}{color} | {color:black}Hi Grzegorz,{color} {color:black}{color} {color:black}For this item I also made a DIVO.{color} {color:black}See enclosed file{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Grzegorz Materla (Jira) <[email protected]> *Verzonden:* woensdag 18 januari 2023 09:59 *Aan:* Jong\', "Comment 7: Christine de <[email protected]> *Onderwerp:* DGS-8344 Missing migration 803319 Engelenhoven NAS | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | \'", "Comment 8: \'Hi [[email protected]],A lot of migration files have mistakes. Next case when item code is wrong -505506. Could you check the data and sendme a correct data file?The user is responsible for correct data in migration files.If you can", "Comment 9: please look into task too - https://helpdesk.kotrak.com/browse/DGS-8343.Best regards,Grzegorz\'", \'Comment 10: "Hi [[email protected]],your enclosed file doesn\\\'t work. Please add the attachement into the Jira task.Best regards,Grzegorz"\', "Comment 11: \'{color:black}Dear Grzegorz,{color} {color:black}{color} {color:black}Some items are not in Intense and should have the code DIVO.{color} {color:black}I didn’t test all the item codes.{color} {color:black}Enclosed the modified file.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Grzegorz Materla (Jira) <[email protected]> *Verzonden:* woensdag 18 januari 2023 11:01 *Aan:* Jong", "Comment 12: Christine de <[email protected]> *Onderwerp:* DGS-8344 Missing migration 803319 Engelenhoven NAS | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | [^Feed migration_Engelenhoven 803319-1.xlsx] _(256 kB)_\'", "Comment 13: \'[[email protected]]", "Comment 14: [[email protected]],Purchase and Sales Invoices have been migrated into Intense Platform.You can feel free to test it.Best regards,Grzegorz\'", "Comment 15: \'[[email protected]],all documents have been migrated. You can feel free to test it.Best regards,Grzegorz\'", "Comment 16: \'Sorry I forgot to reply. You can resolve this as done.\'", \'Comment 17: "No problem. Thank you for a reply. I\\\'m closing the task.Best regards,Grzegorz"]\']\nRelated Issues:\n[]\n\n### End'}
688
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8343\n\n### Instruction:\nMissing migration 102038 Westerink NAS\n\n### Response:\n["Comment 1: [\'{color:black}Goodmorning,{color} {color:black}{color} {color:black}Please migrate these missing files for customer Westerink 102038.{color} {color:black}Thanks.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image001!{color:blue}{color}{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | |{color:blue}{color} !image002!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | |{color:blue}{color} !image003!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} | |{color:blue}{color} !image004!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | [^Feed migration_Westerink 102038.xlsx] _(251 kB)_[^Sales migration_Westerink 102038.xlsx] _(13 kB)_[^Purchase_migration_Westerink 102038.xlsx] _(18 kB)_\'", \'Comment 2: "Hi [[email protected]],item code -505520 - from FS excel file doesn\\\'t exsist in Intesne for NAS sector. Could you fix it?Best regards,Grzegorz"\', \'Comment 3: "[[email protected]],which Contract Farmer is correct for all import lines?Are you sure\', "Comment 4: that contract farmer \'CF-N/0068\' is for all Sales invoice lines? Because", \'Comment 5: for PI and FS I see different contract - \\\'CF-N/0042\\\'.Best regards,Grzegorz"\', "Comment 6: \'{color:black}Hi Grzegorz,{color} {color:black}{color} {color:black}I made it a DIVO item.{color} {color:black}See enclosed file.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Grzegorz Materla (Jira) <[email protected]> *Verzonden:* dinsdag 17 januari 2023 15:03 *Aan:* Jong", "Comment 7: Christine de <[email protected]> *Onderwerp:* DGS-8343 Missing migration 102038 Westerink NAS | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | [^Feed migration_Westerink 102038-1.xlsx] _(251 kB)_\'", "Comment 8: \'{color:black}Sorry Grzegorz", \'Comment 9: the correct contract is number 0042.{color} {color:black}The round for Westerink is 102038/0042/0001{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Grzegorz Materla (Jira) <[email protected]> *Verzonden:* dinsdag 17 januari 2023 15:48 *Aan:* Jong\', "Comment 10: Christine de <[email protected]> *Onderwerp:* DGS-8343 Missing migration 102038 Westerink NAS | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | \'", "Comment 11: \'[[email protected]],all documents have been migrated. You can feel free to test it.Best regards,Grzegorz\'", "Comment 12: \'Sorry I forgot to reply. You can resolve this as done.\'", \'Comment 13: "No problem. Thank you for a reply. I\\\'m closing the task.Best regards,Grzegorz"]\']\nRelated Issues:\n[]\n\n### End'}
689
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8342\n\n### Instruction:\nWe are missing a lot of migration files for a specific customer. Could you please migrate the information from the files?\r\n\r\nMigration files for customers:\r\n * 817005\r\n * 013563\n\n### Response:\n["Comment 1: [\'została zrobiona kolejna migracja do NAS!image-2023-01-19-12-19-47-476.png!\'", "Comment 2: \'kolejna migracja", "Comment 3: dla MAS NL!image-2023-01-19-15-48-58-157.png!\'", \'Comment 4: "All documents have been migrated into Intense Platform.I\\\'m closing the task.Best regards,Grzegorz"]\']\nRelated Issues:\n[]\n\n### End'}
690
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8341\n\n### Instruction:\nDHC keeps throwing this error message for certain VT\'s when we regenerate the VT the error message eventually updates to the correct one. \r\n\r\nwe are also still experiencing issues with PLR\'s appearing as though they have not generated but are just not linked to their applicable Job Orders.\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'[^VT error message.mp4] _(449 kB)_\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'To tak: jeśli chodzi o VT-581", "Comment 5: teraz ma nieco innego errora!image-2023-01-17-14-25-11-639.png!\'", "Comment 6: \'VT-583 jest już generated bez messega!image-2023-01-17-14-26-39-807.png!\'", "Comment 7: \'Dziś już jest generated!image-2023-01-18-11-10-50-214.png!\'", "Comment 8: \'19A93EF2-6069-4084-A4F0-C5EF1F6F43F2\'", "Comment 9: \'Ilości się zgadzają...!image-2023-01-18-11-37-00-130.png!!image-2023-01-18-11-33-41-531.png!!image-2023-01-18-11-35-57-745.png!!image-2023-01-18-11-35-23-004.png!\'", "Comment 10: \'Hello,Yesterday", \'Comment 11: when I have a look at this VT\', \'Comment 12: I had other error. This is also error from ERP XL:!image-2023-01-18-13-15-52-710.png!This error is rooted generally in Deliveries:>>the lack of a resource>> or the related delivery has dispatched,>> the intake may not have been done yet\', \'Comment 13: i.e. PLR not produced\', \'Comment 14: e.gToday VT-581 has generated documents and all is fine.However\', \'Comment 15: error below may mean that two processes / documents have been processed at the same time. To verify this error we need fresh example or exact time when the documents were generated from VT and resulted with this error!image-2023-01-18-13-39-52-995.png!Reagrding not linked JO and IR documents\', \'Comment 16: again we need the freshest example. Probably there may be a tmeout\', "Comment 17: but to be sure we need to verify it with the new exampe.Regards!image-2023-01-18-13-39-52-995!\'", "Comment 18: \'Hello", "Comment 19: new example for VT issue 295!image-2!\'", "Comment 20: \'please can we link the old job order examples... the latest example is for the 19th !image-3!\'", "Comment 21: \'SO-31/23/MOM!image-2023-01-20-09-32-02-297.png!\'", "Comment 22: \'Log z erp ntegratora[^vt-295.txt]\'", "Comment 23: \'[^so-31-23-MOM.txt]^DHCService dla ordera z tego VT^\'", \'Comment 24: "Data błędu:!image-2023-01-20-09-54-15-817.png!O tej godzinie leciały timeouty\', "Comment 25: aż miłoXD{code:java}2023-01-19 20:19:03,272 [27] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-295/1/2023/MM [Id: 3a693e2e-f6ec-4322-bb4b-0a7b762fab81]2023-01-19 20:19:03,272 [27] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-19 20:19:03,272 [27] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-19 20:19:03,569 [68] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - GenerateSalesOrderRelease execution started2023-01-19 20:19:03,850 [68] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Forcing document number - 143/0/2023/MPMM for vt element id - Id: 0672ff6b-f5f1-4bc5-ace9-c136d90a565c2023-01-19 20:19:04,038 [68] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - System.OutOfMemoryException: Exception of type \'System.OutOfMemoryException\' was thrown. at System.Data.SqlClient.TdsParser.TdsExecuteRPC(SqlCommand cmd", \'Comment 26: _SqlRPC[] rpcArray\', \'Comment 27: Int32 timeout\', \'Comment 28: Boolean inSchema\', \'Comment 29: SqlNotificationRequest notificationRequest\', \'Comment 30: TdsParserStateObject stateObj\', \'Comment 31: Boolean isCommandProc\', \'Comment 32: Boolean sync\', \'Comment 33: TaskCompletionSource`1 completion\', \'Comment 34: Int32 startRpc\', \'Comment 35: Int32 startParam) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 36: RunBehavior runBehavior\', \'Comment 37: Boolean returnStream\', \'Comment 38: Boolean async\', \'Comment 39: Int32 timeout\', \'Comment 40: Task& task\', \'Comment 41: Boolean asyncWrite\', \'Comment 42: Boolean inRetry\', \'Comment 43: SqlDataReader ds\', \'Comment 44: Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 45: RunBehavior runBehavior\', \'Comment 46: Boolean returnStream\', \'Comment 47: String method\', \'Comment 48: TaskCompletionSource`1 completion\', \'Comment 49: Int32 timeout\', \'Comment 50: Task& task\', \'Comment 51: Boolean& usedCache\', \'Comment 52: Boolean asyncWrite\', \'Comment 53: Boolean inRetry) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 54: RunBehavior runBehavior\', \'Comment 55: Boolean returnStream\', \'Comment 56: String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior\', \'Comment 57: String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.<>c.<Reader>b__6_0(DbCommand t\', \'Comment 58: DbCommandInterceptionContext`1 c) at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target\', \'Comment 59: Func`3 operation\', \'Comment 60: TInterceptionContext interceptionContext\', \'Comment 61: Action`3 executing\', \'Comment 62: Action`3 executed) at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command\', \'Comment 63: DbCommandInterceptionContext interceptionContext) at System.Data.Entity.Internal.InterceptableDbCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand\', \'Comment 64: CommandBehavior behavior) at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context\', \'Comment 65: ObjectParameterCollection parameterValues) at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass41_0.<GetResults>b__1() at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func\', \'Comment 66: IDbExecutionStrategy executionStrategy\', \'Comment 67: Boolean startLocalTransaction\', \'Comment 68: Boolean releaseConnectionOnSuccess) at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass41_0.<GetResults>b__0() at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation) at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption) at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__31_0() at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext() at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source) at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.<>c__14`1.<GetElementFunction>b__14_3(IEnumerable`1 sequence) at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.ExecuteSingle[TResult](IEnumerable`1 query\', \'Comment 69: Expression queryRoot) at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.System.Linq.IQueryProvider.Execute[TResult](Expression expression) at System.Data.Entity.Internal.Linq.DbQueryProvider.Execute[TResult](Expression expression) at System.Linq.Queryable.Single[TSource](IQueryable`1 source) at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(XLObjectKey xlId\', \'Comment 70: String code) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 241 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(ObjectKey id) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 30 at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.GenerateSalesOrderReleaseData(VehicleTicket vehicleTicket\', "Comment 71: IMatchRule`1 vehicleTicketElementSelector) at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.OnExecute(VehicleTicket vehicleTicket) at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketIntegrationTaskBase.OnExecute(Object data) at Evolution.ErpIntegrator.IntegrationLibrary.IntegrationTaskBase.Execute(Object data)2023-01-19 20:19:04,038 [68] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - Exception of type \'System.OutOfMemoryException\' was thrown.System.OutOfMemoryException: Exception of type \'System.OutOfMemoryException\' was thrown. at System.Data.SqlClient.TdsParser.TdsExecuteRPC(SqlCommand cmd", \'Comment 72: _SqlRPC[] rpcArray\', \'Comment 73: Int32 timeout\', \'Comment 74: Boolean inSchema\', \'Comment 75: SqlNotificationRequest notificationRequest\', \'Comment 76: TdsParserStateObject stateObj\', \'Comment 77: Boolean isCommandProc\', \'Comment 78: Boolean sync\', \'Comment 79: TaskCompletionSource`1 completion\', \'Comment 80: Int32 startRpc\', \'Comment 81: Int32 startParam) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 82: RunBehavior runBehavior\', \'Comment 83: Boolean returnStream\', \'Comment 84: Boolean async\', \'Comment 85: Int32 timeout\', \'Comment 86: Task& task\', \'Comment 87: Boolean asyncWrite\', \'Comment 88: Boolean inRetry\', \'Comment 89: SqlDataReader ds\', \'Comment 90: Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 91: RunBehavior runBehavior\', \'Comment 92: Boolean returnStream\', \'Comment 93: String method\', \'Comment 94: TaskCompletionSource`1 completion\', \'Comment 95: Int32 timeout\', \'Comment 96: Task& task\', \'Comment 97: Boolean& usedCache\', \'Comment 98: Boolean asyncWrite\', \'Comment 99: Boolean inRetry) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 100: RunBehavior runBehavior\', \'Comment 101: Boolean returnStream\', \'Comment 102: String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior\', \'Comment 103: String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.<>c.<Reader>b__6_0(DbCommand t\', \'Comment 104: DbCommandInterceptionContext`1 c) at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target\', \'Comment 105: Func`3 operation\', \'Comment 106: TInterceptionContext interceptionContext\', \'Comment 107: Action`3 executing\', \'Comment 108: Action`3 executed) at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command\', \'Comment 109: DbCommandInterceptionContext interceptionContext) at System.Data.Entity.Internal.InterceptableDbCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand\', \'Comment 110: CommandBehavior behavior) at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context\', \'Comment 111: ObjectParameterCollection parameterValues) at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass41_0.<GetResults>b__1() at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func\', \'Comment 112: IDbExecutionStrategy executionStrategy\', \'Comment 113: Boolean startLocalTransaction\', \'Comment 114: Boolean releaseConnectionOnSuccess) at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass41_0.<GetResults>b__0() at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation) at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption) at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__31_0() at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext() at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source) at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.<>c__14`1.<GetElementFunction>b__14_3(IEnumerable`1 sequence) at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.ExecuteSingle[TResult](IEnumerable`1 query\', \'Comment 115: Expression queryRoot) at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.System.Linq.IQueryProvider.Execute[TResult](Expression expression) at System.Data.Entity.Internal.Linq.DbQueryProvider.Execute[TResult](Expression expression) at System.Linq.Queryable.Single[TSource](IQueryable`1 source) at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(XLObjectKey xlId\', \'Comment 116: String code) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 241 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(ObjectKey id) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 30 at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.GenerateSalesOrderReleaseData(VehicleTicket vehicleTicket\', \'Comment 117: IMatchRule`1 vehicleTicketElementSelector) at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.OnExecute(VehicleTicket vehicleTicket) at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketIntegrationTaskBase.OnExecute(Object data) at Evolution.ErpIntegrator.IntegrationLibrary.IntegrationTaskBase.Execute(Object data) at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor.<>c__DisplayClass6_2.<ProcessSingleVT>b__1(){code}"\', "Comment 118: \'XL:!image-2023-01-20-10-55-54-884.png!!image-2023-01-20-11-10-13-378.png!DHC!image-2023-01-20-10-56-11-789.png!!image-2023-01-20-11-02-45-157.png!!image-2023-01-20-11-10-13-378!\'", "Comment 119: \'These are linked!image-2023-01-20-11-31-02-434.png!\'", "Comment 120: \'Do sprawdzenia:0633160123002 0633160123001 0682190123003!image-2023-01-20-11-34-32-579.png!!image-2023-01-20-11-34-32-579!\'", "Comment 121: \'!image-2023-01-20-11-42-17-641.png!MM-PL05111-S7238-B50-C-0260!image-2023-01-20-11-48-53-670.png!\'", "Comment 122: \'All are linked now:!image-2023-01-20-12-09-43-767.png!Additionally", \'Comment 123: this PLR had message (screenshot below). I have resent technology and generated documents from application and ERP documents generated!image-2023-01-20-12-05-13-689.png!!image-2023-01-20-12-05-33-824.png!Those two:06331601230020633160123001I have generated documents for PLR in DHC\', \'Comment 124: JOs were generated\', "Comment 125: IR+ and IR- have to be linked.\'", "Comment 126: \'Regarding VT-295", "Comment 127: we are investigating.Regards\'", "Comment 128: \'Regarding this error:!image-2023-01-20-12-48-55-844.png!We have found information about timeouts. I have restarted Erp Int. Please", "Comment 129: let me know if this error reoccurs.Regards\'", \'Comment 130: "Dziś generowałam dokumenty m.in dla tego PLRa 0633160123001\', "Comment 131: id = \'83C4067F-FB7C-4E11-BA41-DBD8D06F3BC3\'!image-2023-01-20-13-08-35-850.png!W DHC pojawił sie tylko dokument JO-656/23/KBP{code:java}2023-01-20 13:00:10,473 [79] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution started2023-01-20 13:00:10,520 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - GenerateJobOrder execution started2023-01-20 13:00:10,520 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Started PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc3 processing2023-01-20 13:00:10,567 [8] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating documents for PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc32023-01-20 13:00:10,723 [8] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Job Order for PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc32023-01-20 13:00:10,723 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generate JO by PLR data.2023-01-20 13:00:10,770 [Thread 8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - Changing context to 3892023-01-20 13:00:11,332 [Thread 8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - Contex changed to 3892023-01-20 13:00:13,082 [Thread 8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Created: ID - 495164 [JO-656/23/KBP]2023-01-20 13:00:13,473 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Element Created: ID - 521565 for new process 5036032023-01-20 13:00:13,864 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - Job order elemnt ID - 521565 process for item RB64080-B50-M added2023-01-20 13:00:14,114 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - Job order elemnt ID - 521565 ingredient RB64080-B50-M added2023-01-20 13:00:14,207 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - Job order elemnt ID - 521565 product RB64080-B50-M added2023-01-20 13:00:14,426 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Closed: ID - 495164 (2816)2023-01-20 13:00:14,567 [8] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generated JO ID - 495164 For PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc3 - BY PLR2023-01-20 13:00:14,598 [8] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Release for PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc32023-01-20 13:00:14,598 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - IR- Document generation disabled in configuration - skipped.2023-01-20 13:00:14,598 [8] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Receipt for PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc32023-01-20 13:00:14,598 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - IR+ Document generation disabled in configuration - skipped.2023-01-20 13:00:14,692 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Closed: ID - 495164 (4)2023-01-20 13:00:15,023 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Closed: ID - 495164 (6)2023-01-20 13:00:17,140 [48] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 40929122023-01-20 13:00:18,209 [48] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 40929132023-01-20 13:00:18,974 [9] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 40929132023-01-20 13:00:19,350 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Closed: ID - 495164 (7)2023-01-20 13:00:19,437 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO status invalid - expeced zamkniete", \'Comment 132: was rozliczono w 50.0% (4)2023-01-20 13:00:19,437 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO status not changed properly - try to close again2023-01-20 13:00:19,450 [8] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLZamknijZlecenieProd:6).API Name - XLZamknijZlecenieProdAPI Result - 6ERRORS:|Error while saving data in database (ZamknijZlecenieProd-6) at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository.InternalCloseDocument(JobOrder header\', \'Comment 133: DocumentStatus documentStatus) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\JobOrders\\\\\\\\CdnXL2019JORepository.cs:line 158 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository.CloseDocument(JobOrder header\', \'Comment 134: DocumentStatus documentStatus) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\JobOrders\\\\\\\\CdnXL2019JORepository.cs:line 1132023-01-20 13:00:19,465 [8] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLZamknijZlecenieProd:6).API Name - XLZamknijZlecenieProdAPI Result - 6ERRORS:|Error while saving data in database (ZamknijZlecenieProd-6) at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository.InternalCloseDocument(JobOrder header\', \'Comment 135: DocumentStatus documentStatus) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\JobOrders\\\\\\\\CdnXL2019JORepository.cs:line 158 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository.CloseDocument(JobOrder header\', \'Comment 136: DocumentStatus documentStatus) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\JobOrders\\\\\\\\CdnXL2019JORepository.cs:line 139 at Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder.OnExecute(Object data)2023-01-20 13:00:19,465 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - PLR processing finished2023-01-20 13:00:19,465 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - GenerateJobOrder execution finished2023-01-20 13:00:19,465 [79] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution finished2023-01-20 13:00:25,285 [79] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution started2023-01-20 13:00:25,410 [79] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution finished{code}"\', "Comment 137: \'Hello", "Comment 138: issue is still occurring !image-4!\'", "Comment 139: \'!image-2023-01-23-13-21-57-209.png!\'", "Comment 140: \'Hello,Thank you for your information. Regarding PLRs 0633160123002", \'Comment 141: 0633160123001\', "Comment 142: automatic generating documents is not configured for this production area. Documents need to be genrated manually!image-2023-01-23-13-26-21-002.png!\'", "Comment 143: \'Cześć:)[[email protected]]po wstępnej rozmowie z Pawłem Piechem", \'Comment 144: przepinam na dev z prośbą o akceptację. Wygląda na to\', \'Comment 145: że coś tam dzieje się niedobrego\', \'Comment 146: a każdy kejs ma inny błąd. Tyle\', \'Comment 147: co udało nam się przeanalizować\', "Comment 148: jest w tasku. Z góry Wielkie Dzięki:)\'", "Comment 149: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'", "Comment 150: \'hello", "Comment 151: thank you we have reenabled the auto generate. new examples for the VT error message !image-5!\'", "Comment 152: \'Hello,As I mentioned before", \'Comment 153: errors about missing quantity roots in Deliveries:>>the lack of a resource>> or the related delivery has dispatched,>> the intake may not have been done yet\', \'Comment 154: i.e. PLR not produced\', \'Comment 155: e.gRegarding error about "SystemOutOfMemory Exception">> we have verified and could see that ERP Int was opened 6 times - so they worked at the same time - documents were processed>> we have linked JOs and IR documents to PLRs>> since Monday JOs are processed corectly\', "Comment 156: so in our opinion multiple opeed ERP Int could cause documents did not link..System out of memory should not appear unless erp int is open multiple times.Regards\'", "Comment 157: \'Why was ERP Integrator opened 6 times?\'", "Comment 158: \'VT 186 and 188 (KB) generated into the ERP (they have been invoiced) but they are now appearing as not generated in DHC. VT a432 (UR) has the same problem!image-6!!image-7!!image-8!!image-9!!image-10!\'", "Comment 159: \'!image-2023-02-14-08-12-19-967.png!\'", "Comment 160: \'Dla VT-432 SO!image-2023-02-14-08-26-47-548.png!DlaVT 186!image-2023-02-14-08-28-23-993.png!VT-188!image-2023-02-14-08-29-31-747.png!\'", "Comment 161: \'Regarding VT-188", \'Comment 162: please make sure that there is correct SO clipped. The error comes from XL and means that either Source document - in this case SO-148 is in status buffer or executed. So the SOR% document cannot be generated. In fact\', "Comment 163: to SO-148 there is SOR generated under SOR-167/23/KBP with the same quantity as in SO but is clipped to VT-241/1/202/KB what is visible on the screenshot of SOR document. This situation is to verify on your side.!image-2023-02-14-08-45-28-629.png!!image-2023-02-14-08-56-38-917.png!!image-2023-02-14-08-49-53-243.png!!image-2023-02-14-08-49-01-150.png!!image-2023-02-14-08-48-07-329.png!\'", "Comment 164: \'!image-2023-02-14-09-00-31-515.png!!image-2023-02-14-09-00-58-426.png!!image-2023-02-14-09-01-36-519.png!\'", "Comment 165: \'We have found more cases thanVT-432 and VT-186. It seems that initially documents were generated and clipped in DHC. But SOR documents have been unclipped but we do not now why. Maybe some process goes on database. We can also see that someone ore something pushed those VTs yesterday morning. It does not seem to by sync issue as this refers only to 8 documents. For now", "Comment 166: please let us know if we should clipped VTs to generated SOR document per list below:!image-2023-02-14-13-47-29-837.png!Regards\'", "Comment 167: \'Hello", "Comment 168: yes please clip the documents against the applicable VTS. \'", "Comment 169: \'Dear Thabile,Please", "Comment 170: check and verify now.Regards\'", "Comment 171: \'Hello", \'Comment 172: thank you they are linked\', "Comment 173: we appear to be having different issues everyday. we are unable to cancel VT 456 (placed on hold) as it says SOR 729/23/PUR is linked to it. this document has been cancelled in the ERP. !image-11![^2023-02-16_8-26-16.mp4] _(370 kB)_\'", "Comment 174: \'!image-2023-02-16-10-47-18-434.png!!image-2023-02-16-10-49-49-515.png!\'", "Comment 175: \'Dear Thabile,Where do you see the error message that youare unable to cancel VT 456 {color:#0747a6}_(placed on hold) as it says SOR 729/23/PUR is linked to it._{color}{color:#172b4d}?{color}{color:#172b4d}Regards{color}\'", "Comment 176: \'!image-2023-02-16-11-05-54-920.png!!image-2023-02-16-11-07-22-679.png!\'", "Comment 177: \'[^dgs-8341.xlsx]\'", "Comment 178: \'Dear Thabile,Now you should be able to cancel VT", "Comment 179: please verify.\'", "Comment 180: \'Hello", \'Comment 181: we\\\\\\\'re still experiencing the error for "System out of memory" can you tell us why the integrator would open itself multiple times? \\\'\', "Comment 182: \'Hello", "Comment 183: we are still experiencing the JOs not linked to their corresponding PLR issue as well!image-12!\'", "Comment 184: \'!image-13!\'", "Comment 185: \'!image-2023-03-01-15-31-20-789.png|width=543,height=419!!image-2023-03-01-15-32-04-669.png|width=1166,height=345!\'", "Comment 186: \'Hi,I have linked IR + and IR - and JOs to PLRs. Still investigating why erp int is opening multiple time. We can see it has been shut down several times.Starting on Monday", "Comment 187: has anybody reset the Erp Int? Or was there the power outage?Regards\'", "Comment 188: \'Hello", \'Comment 189: no one has\', "Comment 190: no power failures either. according to IT server has been up for 17days (restart due to windows updates) \'", "Comment 191: \'Standardowe błędy:{code:java}ERRORS:|Missing quantity (failed to retrieve the item or the entire execution was forced). (DodajPozycje-17) - (4501010) at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.InternalDocuments.CdnXL2019InternalDocumentRepository.AddElement(Int32 xlDocumentId", \'Comment 192: XLInternalDocumentElement xlElement) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\InternalDocuments\\\\\\\\CdnXL2019InternalDocumentRepository.cs:line 260 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.InternalReleases.CdnXL2019InternalReleaseRepository.CreateIRWithElements(InternalRelease internalRelease\', \'Comment 193: Boolean confirmDoc) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\InternalReleases\\\\\\\\CdnXL2019InternalReleaseRepository.cs:line 64 at Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder.GenerateRelease(ProductionLotReport productionLotReport\', \'Comment 194: JobOrder jobOrder\', \'Comment 195: JobOrderElement element\', \'Comment 196: PLRDocuments documentMapping)2023-02-12 00:07:11,508 [9] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLDodajPozycje:17).API Name - XLDodajPozycjeAPI Result - 17Flags - 13{code}{code:java}ERRORS:|Cannot find document header. (ZamknijDokument-3) at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository.CloseDocument(XLExternalOrderTransaction document\', \'Comment 197: DocumentStatus status) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2019ExternalOrderTransactionRepository.cs:line 530 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.SalesOrderReleases.CdnXL2019SalesOrderReleaseRepository.CloseDocument(XLSalesOrderRelease header\', \'Comment 198: DocumentStatus status) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\SalesOrderReleases\\\\\\\\CdnXL2019SalesOrderReleaseRepository.cs:line 84 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.SalesOrderReleases.CdnXL2019SalesOrderReleaseRepository.CreateSORWithElements(SalesOrderRelease salesOrderRelease\', "Comment 199: Boolean confirmDoc) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\SalesOrderReleases\\\\\\\\CdnXL2019SalesOrderReleaseRepository.cs:line 312023-02-12 00:07:56,311 [117] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-02-12 00:07:56,311 [117] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-02-12 00:07:56,311 [117] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2019.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -1{code}{code:java}ERRORS:|Transactions with this customer have been stopped. (NowyDokument-18) at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository.CreateHeader(XLExternalOrderTransaction documentHeader) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2019ExternalOrderTransactionRepository.cs:line 792023-02-12 00:13:56,381 [83] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-02-12 00:13:56,381 [83] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-02-12 00:13:56,396 [83] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2019.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -1{code}\'", "Comment 200: \'{code:java}2023-02-13 04:06:30,717 [16] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - Changing context to 272023-02-13 04:06:38,775 [1] DEBUG Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Started configuration of IoC container2023-02-13 04:06:38,993 [1] WARN Evolution.ErpIntegrator.CdnXL.CdnXL2019.ErpVersionConfiguration [(null)] - Implementation for interface Evolution.ErpIntegrator.ERP.Interfaces.Attachments.IAttachmentRepository not found!2023-02-13 04:06:41,212 [1] DEBUG Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Finished configuration of IoC container2023-02-13 04:06:41,212 [1] DEBUG Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Started configuration of Platform Client2023-02-13 04:06:41,884 [1] DEBUG Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Resending exceptions2023-02-13 04:06:41,884 [1] DEBUG Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Finished configuration of Platform Client2023-02-13 04:06:42,181 [1] INFO Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Running startup extension Evolution.ErpIntegrator.Extensions.DBTriggerCheck.DBTriggerCheckExtension2023-02-13 04:06:42,181 [1] INFO Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Extension completed2023-02-13 04:06:42,181 [1] INFO Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Starting in singe process mode.2023-02-13 04:06:42,197 [1] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - XL login attempt on user - ERPINT2023-02-13 04:06:46,280 [1] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - Set api version to - 201932023-02-13 04:06:46,280 [1] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - Set current context - 12023-02-13 04:06:46,280 [1] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - XL login", "Comment 201: session ID - 597550{code}!image-2023-03-02-08-13-35-430.png!\'", "Comment 202: \'Ten fragment pojawia się 3 razy", "Comment 203: jeszcze ok 1:30 i 16:30,14 lutego da razy!image-2023-03-02-08-14-54-332.png!\'", "Comment 204: \'!image-2023-03-02-09-14-30-809.png|width=1154,height=350!\'", "Comment 205: \'[^DGS-8341 uzasadnienie na retro.docx]\'", "Comment 206: \'[^DGS-8341 uzasadnienie na retro.docx]\'", "Comment 207: \'Please close this ticket", "Comment 208: and open the RCA for out of memory.\'", "Comment 209: \'RCA is underDGS-8756Regards\']"]\nRelated Issues:\n[\'DGS-8756\']\n\n### End'}
691
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8340\n\n### Instruction:\nPlease help to check VT-775/23. WO was closed without realization. And \r\nnothing on stock.\r\n\r\n**Note: Issue in Binh Dinh plant(ID 438) but it not in list so that why i booked it ALL.\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Było reopen: !screenshot-1! !screenshot-2! Messages: !screenshot-3! !screenshot-4! !image-2023-01-18-16-15-18-612!!image-2023-01-18-16-16-36-800!\'", \'Comment 4: "Hello\', \'Comment 5: warehouse order has been reopened by User QUOCVUONG and next Closed without realization(also by QUOCVUONG) - last operations for WO.Can you ask why the user chose that?I know that the VT should be cancelled\', \'Comment 6: but in this case it\\\'s best to re-issue the document.We can change the status of this to canceled from database."\', "Comment 7: \'Hello", "Comment 8: any news about this case?Thank you and regards.\'", "Comment 9: \'you can close the ticket\']"]\nRelated Issues:\n[]\n\n### End'}
692
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8339\n\n### Instruction:\nOn the dhvd02ap170 some labels are not being imported.\r\nThe recipe 115283 must be sent to the plant tonight. But in DHC the recipe remains in draft (version 25) because of the missing label.\r\n\r\nPlease check why the label is not being imported in DHH. I tried already by stopping and starting the autoimporter but that didn\'t help.\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Dear Wijnand,On my side I can see item linked correctly in DHC!image-2023-01-16-21-18-38-460.png!Recipe in DHC!image-2023-01-16-21-19-07-626.png!It is accepted and has label:!image-2023-01-16-21-19-36-233.png!Could you please verify? Maybe it had some delay in synchronisation.Regards\'", "Comment 3: \'It is also in plant Maasbracht!image-2023-01-16-21-28-04-885.png!\'", "Comment 4: \'DearWijnand,As taskDGS-8337 has been resolved", \'Comment 5: please\', "Comment 6: confirm if we can close this task.Regards\'", "Comment 7: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. What is more", \'Comment 8: it has been confirmed in task DGS-8337 that all is working fine now. If the issueappearsagain\', "Comment 9: please raise another task.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
693
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8338\n\n### Instruction:\nCould you please add the column "Document Number" in the round category Eggs in the LAS?\r\n\r\nWe need to present the ERP number in here.\n\n### Response:\n["Comment 1: [\'Added Document Number column to view.!image-2023-01-18-12-11-48-308.png!\'", "Comment 2: \'We need the documents numbers in the LAS to be filled in the category expenses as well. Now this whole column is empty.\']"]\nRelated Issues:\n[]\n\n### End'}
694
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8337\n\n### Instruction:\nItem 115283 is in DHC but does not go to DHP.\r\nIt is needed urgently in DHP Maasbracht, but I can\'t find it in any other DHP.\r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Hello,Please check the DHH Holding.Don\\\'t show in DHH items.Look screenshot!image-2023-01-16-17-18-02-445.png!Regards."\', "Comment 3: \'Hi Adrian,somehow it is in DHH now AND in DHP.This ticket can be closed.Thanks for the support.\']"]\nRelated Issues:\n[]\n\n### End'}
695
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8336\n\n### Instruction:\nHi\r\n\r\nWe are experiecing unusual slowdown on _Production lot_ screen in Rio Claro\'s DHP 2.5 server.\r\nWe just restarted both servers: At first the database server, then we restarted application server, but without success.\r\n\r\nCould you please check it?\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'I checked the indexes,and i made rebuild and update stats", "Comment 4: please verify.\'", \'Comment 5: "Hi PiotrNow it\\\'s fine! It\\\'s taking the usual time to load the screen.You can close this taskThank you very much"\', "Comment 6: \'Hello MaiconThank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'}
696
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8335\n\n### Instruction:\nDzień dobry,\r\n\r\nw zeszłym tygodniu był problem z zaksięgowaniem wyciągu - zgłoszenie do zamknięcia - zostało ono zrealizowane zdalnie przez Monikę Biśta. \r\n\r\n\r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Ticket has been closed.\']"]\nRelated Issues:\n[]\n\n### End'}
697
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8334\n\n### Instruction:\nPlease remove the users:\r\n\r\nPerquin en Veldkamp from the automatic responce\r\n\n\n### Response:\n["Comment 1: [\'This is for : Premix\'", "Comment 2: \'!image-1!\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'Hello,Issue is resolved - Users deactivated.Best Regards,Łukasz Stępień\']"]\nRelated Issues:\n[]\n\n### End'}
698
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8333\n\n### Instruction:\nUser can’t see whether the SO’s : SO-396+397/09/2022 are booked out of stock or if they are cancelled in CDN.\r\nThey should have been booked out of stock in order to create invoices for De Heus Poland, but so far, there were no invoices\r\n( material was physically there and has been loaded, seen transport paper)\r\nHow can it be invoiced?\r\n \r\n\r\n\r\n \n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "It\\\'s about restoring these orders in XL and manual execution from the XL level or what are the expectations for the task? The status in the GUI is visible. Canceled as mentioned in the task. !screenshot-1! Regards."\', "Comment 4: \'Hello", "Comment 5: any news about this case?Thank you and regards.\'", "Comment 6: \'According to me is only one correct.I Have asked the user what the meaning exactly is. \'", "Comment 7: \'Comment in wrong ticket\'", "Comment 8: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
699
{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8332\n\n### Instruction:\nOrders and shipping notices for this customer often don\'t arrive in the factory. But after some investigations it seems that the SN isn\'t in DHP, for example L000105355.\r\nSales Order SO000052655 is in DHP though and the Shipping Notice is in DHC also.\r\nCan you please check what is wrong so we can fix this?\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: " !screenshot-1! 2023-01-16 12:56:39.260{code:java} FROM [DHCService_NL_AS400_PROD].[dbo].[ShippingNoticeExportInfoes] where EntityId=\\\'0B43E530-3C45-4BEC-9FBB-E668E14A2889\\\' FROM [DHCService_NL_AS400_PROD].[dbo].[Orders] where ForeignDocumentNumber in(\\\'SO000052660\\\') FROM [DHCService_NL_AS400_PROD].[dbo].[Addresses] where BusinessPartnerId=\\\'C9F0FDA3-A541-43F7-9A63-21831B7403B2\\\'{code}"\', "Comment 3: \'For this order the address is wrongly associated with BP (order SO000052660 for the main BP and payer)Correct this data in DHC?\'", "Comment 4: \'Could you please confirm if we can close this task?Regards\'", \'Comment 5: "Hi Piotr\', \'Comment 6: no please don\\\'t close this task yet. I need as example and I\\\'m not sure if this one is correct in Milas and we need to change it there. But it has low priority for us now."\', \'Comment 7: "Hi Theo\', \'Comment 8: thank you for information - so we\\\'ll wait for an answer.Regards."\', "Comment 9: \'Hello,can I count on an update of this ticket?Thank you and regards.\'", "Comment 10: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time.Regards\']"]\nRelated Issues:\n[]\n\n### End'}