Datasets:

pismacx

/

ai_assistant

like 1

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8131\n\n### Instruction:\nGood morning,\r\n\r\nI am unable to book out these sales orders. SO-284/12/2022 and SO-285/12/2022 and SO-286/12/2022\r\nThis is strange because I could just make the orders based on the stock indicated in the allocation list. (so the stock is there)\r\n\r\nWhen I want to create the SORs I get the following message (for all three SOs, see image.\r\n\r\nPlease, could you help me?\r\n\r\nKind regards,\r\n\r\nGerard Geerts\n\n### Response:\n["Comment 1: [\'!Premix_issue!\'", "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: \'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 4: \'Hello Aleksandra,Oké!.Regards,Gerard \'", "Comment 5: \'Thank you\'", "Comment 6: \'This item has no stock in XL for EX warehouse. !screenshot-1! \'", "Comment 7: \'Good morning Piotr,thanks for your support. You may close this ticket.I wish you a Merry Cristmas and a Happy New Year.Enjoy your holidays.Kind regards,Gerard \'", "Comment 8: \'Thank you", "Comment 9: I wish you tooa Merry Christmas and a Happy New Year.Regards,\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8130\n\n### Instruction:\nHi\r\n\r\nThe integration between DHC x DHP in Toledo factory has stoped.\r\nWe have VTs, PLRs and Medicated control not synchronized from DHC.\r\nVT-2538/22 / VT-2542/22 / Others VTs\r\n0871191222035 / 0871191222032 / Others PLRs\r\n4/71917-01 / Others Medicated controls\r\n\r\nCould you check it please?\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: "Hi PiotrLooking to Linked servers in the database\', \'Comment 3: seems that this wasn\\\'t updated by KOTRAK.I don\\\'t know if this has any relation to the connection.!image!"\', \'Comment 4: "For the service there are errors with the connection to the sql server,and as you can see it was restarted a few hours ago !screenshot-1! Can you do a application pool restart for PlantIntegrationDhcService?I don\\\'t have permissions on my account."\', "Comment 5: \'Hi PiotrI have already restarted", "Comment 6: but I did it again right now.Unfortunatelly no success until nowThank you\'", \'Comment 7: "PLR\\\'s are in DHC now !screenshot-2! VT\\\'s !screenshot-3! We have also restarted the application pool for PlantIntegrationDhcService"\', "Comment 8: \'Hi PiotrI can see these documents on DHP/DHC.Did you only restarted PlantIntegrationDhcService in IIS?Thank you\'", "Comment 9: \' !screenshot-4! \'", "Comment 10: \'Did you only restarted PlantIntegrationDhcService in IIS?Yes", \'Comment 11: stopped site and application pool\', "Comment 12: then started app. pool and site.And finally browse website.\'", "Comment 13: \'[~mberbert@deheus.com]I repeat the request for an admin on the toledo DHP server", "Comment 14: as you can see today it is important that we have such permissions.Thank you.\'", "Comment 15: \'This ticket has been closed.\'", "Comment 16: \'[~lalmeida1@deheus.com]\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8129\n\n### Instruction:\nVT printouts is taking a long time to load\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,I would like additional information:- does the preview also take a long time to generate or only the printout?,- the problem only applies to VT\\\'s. I would like some examples - is the problem for every VT?,- is the problem on every server?Thank you and regards."\', "Comment 3: \'Please it is fine now", \'Comment 4: kindly close !image002! *From:* Piotr Gaczorek (Jira) <jira@kotrak.com> *Sent:* Friday\', \'Comment 5: December 23\', \'Comment 6: 2022 8:27 AM *To:* Feyi\', "Comment 7: Solomon <SFeyi@koudijs.com.gh> *Subject:* DGS-8129 Vt printouts taking a very longtime to load | *{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}* | \']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8128\n\n### Instruction:\nHi\r\n\r\nWe uploaded the pricelist to DHC but it\'s not updating in DHH.\r\nIMPORTANT: We changed the local IP in DHC server today. Mr Przemek made some change in communication with DHH to make Recipes integrate, now we have this Price List issue.\r\n\r\nCould you please check it?\r\nThank you very much\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'We need for ready for tomorrow morning.Thank you\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'!image-2022-12-21-10-31-17-765.png!!image-2022-12-21-10-30-12-649.png!!image-2022-12-21-10-30-42-577.png!\'", "Comment 5: \'W DHC mamy processed successfull ale po prod area id w bazie holdingu nie ma tej pricelisty!image-2022-12-21-11-00-24-366.png!!image-2022-12-21-11-00-44-218.png!\'", "Comment 6: \'Wprawdzie Maicon podał tegotygodniową", "Comment 7: ale zeszłotygodniowej też nie ma\'", "Comment 8: \'Dear Maicon,We have analised your case and it looks there is no communication from DHC to DHH. In taht case", "Comment 9: please contact Valid.Regards\'", "Comment 10: \'Dear AleksandraYesterday Przemek needed to make some configuration in DHH about this DHC Recipes communication.Does him need to replicate this configuration in DHH also for Price list?Could you check with him first?Thank you\'", "Comment 11: \'Is the filter fine? I have consulted with Przemek. Price List from last week is in DB", "Comment 12: please verify!image-2022-12-21-14-21-06-171.png!\'", "Comment 13: \'HiThe filter was correct. I myself checked it when we raised this DGS.But OK! Now the information is there. You can close this task.Thank you very much.\'", "Comment 14: \'Thank you.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8127\n\n### Instruction:\nWrong final product in additional technology VE307499.\r\nShould be 307499 instead of 303436\r\n\r\nCan you please fix this asap, there are peol[ple waiting on it.\r\n\r\nThanks in advance,\r\nRob.\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: \'Provided additional technology has been modified. Please check.\'", \'Comment 5: "It\\\'s OK now\', \'Comment 6: the ticket can be closed.Thanks for the support."]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8126\n\n### Instruction:\nDear Sirs,\r\n\r\nin Bestmix we have 2 plants but in DHH we combined it into 1.\r\nI did the customization in DHH.\r\nPlease do your part in DHC - see screenshot I attached\r\nCode 0511\r\nParent production area 051\r\n\r\nPlease treat it as a priority - go live project\r\n\r\nSince I am on holiday since tomorrow, please contact Rob Hughan\r\nrhughan@deheus.com\r\n\r\nKind regards,\r\nDiana Cielecka\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: \'!image-2022-12-21-08-33-07-537.png!\'", "Comment 4: \'!image-2022-12-21-08-42-57-261.png!!image-2022-12-21-08-43-15-554.png!\'", "Comment 5: \'!image-2022-12-21-12-07-18-661.png!\'", "Comment 6: \'Dear DianaPlease", "Comment 7: check if it is fine for you.Regards\'", "Comment 8: \'{color:black}Goodmorning,{color} {color:black}{color} {color:black}My colleague created this ticket", "Comment 9: but I am unable to view it:{color} !image001!{color:black}{color} {color:black}{color} {color:black}Can you add me to see it?{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Rob{color} |{color:#000001} {color} |{color:#000001} Hughan{color} | {color:#000001}ApplicationEngineer{color} | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image002!{color:blue}{color}{color:black} <[https://www.deheus.com/]>{color} | | *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+310621127007{color}{color:#000001} <tel:+31%200621127007>{color} | {color:#000001}CoC16011201{color} _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | |{color:blue}{color} !image003!{color:blue}{color} <[https://www.facebook.com/deheusanimalnutrition]>{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/royal-de-heus/mycompany/]>{color:black}{color} | |{color:blue}{color} !image006!{color:blue}{color} <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} | |{color:black}{color} !image007.jpg|thumbnail!{color:black}{color} | \'", \'Comment 10: "Hi Aleksandra,I can\\\'t check as I do not have access to DHC. If you send me the screens shot from the system\', \'Comment 11: the same I sent you with the changes I requested I will be able to approve it.Please treat is us priority 1. We need to send the recipes asap.Please ass a copy to my friend ROB as I AM ON HOLIDAYS!Kind regrardsDiana"\', "Comment 12: \'Olu", \'Comment 13: chodziło aby spiąć 511 z parentem 51\', "Comment 14: na twoim screenie widać że 511 jest spięty z parentem 442. Przepiąłem na 51 na produkcji w VN. Jak na razie obowiązują ustalenia ze takich zmian dokonuje lokalne IT a my ich wspieramy w tym jak taka konfiguracja powinna wyglądać żeby osiągnęli zamierzony cel.\'", "Comment 15: \'Dzięki Przemku", \'Comment 16: Na razie to lokalne IT się dre\', \'Comment 17: że jest na wakacjach. Co do spinania\', \'Comment 18: bo ja tylko przeedetywałam w Holdingu BP i Production Area (czyli spacja / check żeby save było active)\', \'Comment 19: myślisz\', \'Comment 20: że coś nagmerałam przy okazji? :)w sumie to nawet nie wiem\', "Comment 21: jak tego parenta dodać :Pwięc to raczej nie ja :P\'", "Comment 22: \'Done. Rob is added as a Participant.\'", "Comment 23: \'generalnie to dostałem maila z którego wynika ze nie powinno to zostać ustawione jako parent ale ok", "Comment 24: jak chcieli to tak mają.\'", "Comment 25: \'Wiesz", \'Comment 26: z tym nie dyskutuję\', \'Comment 27: raczej zakładam\', \'Comment 28: że Diana zrobiła to źle\', \'Comment 29: a potem zgłosiła\', "Comment 30: że nie pykło.\'", "Comment 31: \'Mniejsza z tym", "Comment 32: dzięki za pomoc :):*\'", "Comment 33: \'Hi,Can we close this task?Regards\'", "Comment 34: \'pease close the task\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8125\n\n### Instruction:\nOrder SO-8150/12/22 (external ordernumber SO000041513) contains three lines, all with a special. For third orderline, the one time recipe is sent to PCS. For first two lines (both for item 303436 with special 702072), the one time recipe is generated (we see it in DHP) but it does not seem to be exported to PCS. \r\nProduction for this order must start. Please check why the one time recipes for order lines 1 and 2 (for item 303436) are not exported to PCS and - if possible - export the recipes so that the plant can start production.\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: "NIe ma tych receptur w tabeli export\', \'Comment 4: w [DHPlantPCSBusinessLogicMain].[dbo].[Recipes] są :{code:java} select * FROM [DHPlantPCSBusinessLogicMain].[dbo].[Recipes] where OrderId=\\\'89C78DF4-E281-4183-ADD0-F741382EA25C\\\'{code} !screenshot-1! Nie ma ich w eksporcie:{code:java} select * FROM [DHPlantPCSBusinessLogicMain].[dbo].[ExportRecipes]where EntityId in(46936,46940,46939,46935){code} !screenshot-2! tutaj też nic nie pokazuje:{code:java}select * FROM [DHPlantPCSBusinessLogicMain].[dbo].[WebApiRequestLog] where path like \\\'%recipe%\\\' and body like \\\'%46939%\\\' order by 1 desc{code} !screenshot-3! "\', "Comment 5: \'Hello,Correct synchronization of export to PCS is to synchronize the recipe ", \'Comment 6: flag error for these recipes Related to the commodity did not have the associated production definition flag.There is a flag on the recipeProduction will resume if the recipe flag is modified\', "Comment 7: so they will not be sent to PCSPlease correct the recipe.These are the assumptions in your production.Regards\'", \'Comment 8: "{code:java}SELECT TOP 100 R.*FROM dbo.Recipes RINNER JOIN dbo.Items I ON I.Id = R.ItemIdWHERE-- R.EntityId NOT IN (SELECT E.EntityId FROM dbo.ExportRecipes E) AND R.IsProductDefinition = 0 AND I.IsDerived = 0 --AND NOT EXISTS --( -- SELECT * -- FROM dbo.Recipes ZR -- WHERE ZR.IsProductDefinition = 1 -- AND ZR.ItemId = R.ItemId --)\\\\tand r.EntityId = 46934ORDER BY R.EntityIdselect * from dbo.Recipeswhere itemid = \\\'2BA9DE6F-A5D0-41E6-882F-C2ED8D1DE942\\\'{code}"\', "Comment 9: \'Is productionDefinition ma być 0 inne wcześniej receptury.Do weryfikacji klienta receptura !image-2022-12-20-17-28-24-227.png!\'", "Comment 10: \'Hi Adrian", \'Comment 11: Ok\', \'Comment 12: I now see that invalid additional technology VE307499 was created for 303436 for Veghel. We cannot (yet) remove or undo this additional technology in the application. Can you please remove the additional technology VE307499. After this\', "Comment 13: the one time recipes I think should be sent to PCS\'", "Comment 14: \'Or can you update the flag in the two recipes in DHP", "Comment 15: so that it will be exported?\'", "Comment 16: \'Ok removed VE307499. Please verify. The problem has been resolved? Regards\'", "Comment 17: \'Thank you. Recipes were sent to Pcs. This ticket can be closed. {quote}Op 20 dec. 2022 om 18:12 heeft Adrian Kozak (Jira) <jira@kotrak.com> het volgende geschreven: {quote} {quote} \\\\ufeff |{color:#ffffff} 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}{color}{color:#7a869a}{color}{color:#7a869a}{color} {quote}\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8124\n\n### Instruction:\nOn the customer card we have a checkbox to indicate whenever a customer needs to have his technical results created. It looks like this checkbox is marked at all cases and is not editable. \r\n\r\nThis field should be editable by all users.\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: \'MitchIf the checkbox is not marked", "Comment 4: the Technical Results tab should to be hidden in Financial Statement?\'", "Comment 5: \'It should be atleast not be shared with the customer. So creating a PDF should be not possible.For internal purposes it can be helpfull to have this calculations either way.\'", "Comment 6: \'Checkbox Techical Results in Customer Card # Checkbox must be visible only in MAS NL and MAS BE for BP_Category = Farmer (only in these two sectors TR are calculated) # Checkbox must be available for editing for role Customer Edit # If the checkbox = 1 the Technical Result printout can be generated by a user Otherwise", \'Comment 7: the TR can be calculated in Financial Statement\', "Comment 8: but the printout for Technical Results cannot be generated\'", "Comment 9: \'1. Checkbox is now visible only in MAS NL and MAS BE for BP_Category =Farmer2. Checkbox is now editable for all users with Customer edit role.3.If the checkbox is marked the Technical Result printout can be generated by a userOtherwise", \'Comment 10: the TR can be calculated in Financial Statement\', "Comment 11: but the printout for Technical Results cannot be generated.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8123\n\n### Instruction:\nSlaughter report “BN2233402 1480672” of 15 Dec gives an error on the Capacity (stockingDensityPerM2) field. \r\n\r\nIt contains the value 2.5, but according to Intense only integer values are allowed. This should be adjusted. We can have all kinds of numbers in this field.\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: \'Podczas synchronizacji z Kofax do Intense wartość Capacity trafia w złe pole - Doc_IntColumn20", "Comment 3: które w Intense jest flagą (0/1).Docelowo powinno to wyglądać następująco:Jeżeli z Kofax synchronizujemy wartość Capacity -> Ustaw flagę Doc_IntColumn20 = 1 oraz uzupełnij wartość w polu Doc_ShortStringColumn4. Wartość Capacity wg. informacji od klienta jest typu decimal.Pozdrawiam,Grzegorz\'", "Comment 4: \'Czy to będzie poprawione?\'", "Comment 5: \'[~tomasz.koziol@kotrak.com]", "Comment 6: [~michal.kordys@kotrak.com] :)\'", "Comment 7: \'Wrzucone na wewnętrzną listę podsumowującą,\'", "Comment 8: \'DHNLC-1207\'", "Comment 9: \'Ready for UAT tests\'", "Comment 10: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8122\n\n### Instruction:\nSI RLM/2022/2002 should be linked to PI RLM/2022/1110 (this should be the leading doc).\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: \'SI-RLM/2022/2002 is linked to PI-RLM/2022/1110!image-2022-12-21-11-12-50-539.png!\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8121\n\n### Instruction:\nIn some sectors we have a checkbox on the round that is called "Active". The checkbox should be checked whenever the round is active and should be unchecked whenever the round is closed.\r\n\r\nNow this is empty at all rounds.\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: \'-All rounds have been updated.-If round status was set to closed then the active field was set to 0 if round status was set to active then the field was set to 1.-At this point", "Comment 4: each round that changes from active to closed automatically changes the active field.-Every new round get marked field active.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8120\n\n### Instruction:\nIf ERP Document number in Invoice is equal to 1000000305 the user should be able to adjust the ERP document number in Invoice (ligthening icon action ) \r\n\r\nThe same for Feed Sale positions*\n\n### Response:\n["Comment 1: [\'* Na fakturach PI", "Comment 2: SI powinna być możliwa edycja pola Document Number ERP (Doc_ShortStringColumn20) jeżeli pole Doc_SetID IS NOT NULL - akcja spod pioruna\'", "Comment 3: \'* -Na Feed sale powinna być możliwa edycja pola Document No. (ELM_ShortStringColumn2) jeżeli pozycja Feed sale (Del_ID) nie znajduje się w mapowaniach w tabeli w kolumnie ID tabeli AgraSyncIdentityMappingsProd.dbo.FeedSaleMappings-Na tą chwilę jest już blokowana cała zakładka w tym pole Document No. poprzez funkcję", \'Comment 4: która sprawdza czy dana pozycja przyszła z Milasa\', \'Comment 5: więc powinno to wystarczyć i pozostałe pozycje\', "Comment 6: które nie pochodzą z Milas powinny być możliwe do edycji.\'", "Comment 7: \'Na ten moment na produkcyjnym środowisku!image-2022-12-22-14-24-08-546.png!!image-2022-12-22-14-24-00-116.png!\'", "Comment 8: \'[~tomasz.zygon@kotrak.com] # W jakich sektorach zostały wprowadzone zmiany i na jakich dokumentach? W jaki sposób zmienić numer zmigrowanej faktury", "Comment 9: która jest w archiwum? W tasku informacja o akcji spod pioruna. # Czy zmiany są również wprowadzone na TEST?\'", "Comment 10: \'Na IBIP_DH_TEST powinno to działać", "Comment 11: a na produkcyjnym póki co zmiany są wykomentowane i czekało to na implementację zmian z taska z S2P - https://helpdesk.kotrak.com/browse/DHNLC-1206\'", "Comment 12: \'DHNLC-1210Implemented on IBIP_DH_TEST", "Comment 13: to be tested by DH\'", "Comment 14: \'Ready for UAT tests\'", \'Comment 15: "I can\\\'t test this because I cannot find a document with number 1000000305. Which document did you use to test this with?"\', \'Comment 16: "You can try on some invoices from migration\', \'Comment 17: for example on some from this list. It\\\'s possible for migration invoices.32762 SI-RLM/2022/036732753 PI-RLM/2022/036532744 SI-RLM/2022/036532743 SI-RLM/2022/036432742 SI-RLM/2022/036332741 SI-RLM/2022/036232740 SI-RLM/2022/036132739 SI-RLM/2022/036032738 SI-RLM/2022/035932737 SI-RLM/2022/035832736 SI-RLM/2022/035732735 SI-RLM/2022/035632734 SI-RLM/2022/035532733 SI-RLM/2022/035432732 SI-RLM/2022/035332731 SI-RLM/2022/035232730 SI-RLM/2022/035132729 SI-RLM/2022/035032728 SI-RLM/2022/034932727 SI-FNM/2022/0022"\', "Comment 18: \'Sprawdzone przez klienta", "Comment 19: można wrzucać na PROD. !image-2023-01-13-12-27-05-676.png!\'", "Comment 20: \'Done at production database.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8119\n\n### Instruction:\n VT-246/12/22 has status closed, but the related warehouse order has status execution pending. It doesn\'t close and the related stock units stay in progress. Please close this WO so that the stock units have status on stock\r\n\r\n\n\n### Response:\n["Comment 1: [\'!afbeelding!!afbeelding-2!!afbeelding-3!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2022-12-20-14-29-03-028.png!\'", "Comment 4: \'Hi Thomas,It should be fine now. Please", "Comment 5: verifyRegards\'", "Comment 6: \'Yes it is fine", "Comment 7: thanks. Any idea what causes this and how to prevent this from happening?\'", "Comment 8: \'W sumie 11 eventów reopen WO!image-2022-12-21-13-17-01-192.png!!image-2022-12-21-13-21-01-621.png!Tu jest aż 10 minut!image-2022-12-21-13-21-45-401.png!\'", "Comment 9: \'Hi Thomas,I have verified logs and I can see Warehouse Order has been reopened several time. Do you have any knowledge if someone from your Team reopened WO(PI)-5/12/22?Regards\'", "Comment 10: \'Could be me in this case", "Comment 11: I tried reopening and closing a few times\'", "Comment 12: \'Can we close this task?Regards\'", "Comment 13: \'Please close\'", "Comment 14: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8118\n\n### Instruction:\nPlease set ID 76877 back to entry\r\nslaughtery report SRBe/1064\n\n### Response:\n[\'Comment 1: ["It\\\'s in Entry right now."]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8117\n\n### Instruction:\nAttached ASN is not handled as warehouse intake, can you check? settlement is pieces, item is in pcs: so I expect it to be handled in DHP?\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: \\\'Hi,Is the packing form correct then? Shouldn\\\\\\\'t it be "packed" ? You would probably need to cancel this ASN and make a new one.!image-2022-12-21-11-25-09-173.png!\\\'\', "Comment 4: \'Indeed you;re right: I was able to change it to piece. But I cannot delete the VT: Can you do this?\'", "Comment 5: \'Why delete? VT should be cancelled. Please", "Comment 6: let me know if you are able to cancel the VT.Regards\'", "Comment 7: \'Ah sorry", "Comment 8: I mean cancel\'", "Comment 9: \'Please", "Comment 10: try now. You shuld be able to cancel VT now. Let me know about the result.Regards\'", "Comment 11: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8116\n\n### Instruction:\nFSK 31 oraz 66/12/22/PK nie można zaksięgować. Są to korekty danych \r\nDla przykładu 66/11/22/PK, księguje się bez problemu, również jest to korekta danych\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,On invoice 66/11/22/PK payment has been corrected (from casch to transfer) that is why invoice has been posted on accounts related with payment!image-2022-12-20-14-41-47-600.png!!image-2022-12-20-14-44-42-360.png!Correction invoicesFSK 31 and 66/12/22/PK is related only with the customer data. Customer is still the same. There is no amounts to be posted.If you want to post this documents please give us information on accounts and amounts.\'", "Comment 3: \'thank you. You can close this task\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8115\n\n### Instruction:\nUser wants to create a VT for calloff CL000008902 in DHP. VT is not created, an error message shows. Maybe this is related to the fact that the calloff is for location 98 instead of location 5? can you advise how to solve?\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: \'I think we miss destination site for Andel Mest?\'", "Comment 4: \'Also can you check if configuration is correct for dispatches for location 098?\'", \'Comment 5: \\\'2022-12-20 13:50:40 (7ac126a3-e950-4e5f-8f37-9522b2443b61/Plant.VC.BusinessLogic/DHVD01AP184/20836/220) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 6: "host": { "Value": "dhvd01ap184:82"\', \'Comment 7: "HasValue": true\', \'Comment 8: "Host": "dhvd01ap184"\', \'Comment 9: "Port": 82 }\', \'Comment 10: "path": "/api/VehicleTicket/createVehicleTicketFromShippingNotice"\', \'Comment 11: "queryString": []\', \'Comment 12: "requestBody": "\\\\\\\\"7d2730b1-a089-42f9-85a3-14e62543d118\\\\\\\\""}.System.ArgumentException: DefaultDestinationSiteIsNotConfigured\\\'\', "Comment 13: \'This look like the same issue with configuratio like here :in task DGS-8036this is for bulk :!image-2022-12-20-13-57-24-528.png!There is no unit in configuration for feed 098 :Please add it in WMS->configuration-> storage locationsThis plant need to be add and set in vt configuration!image-2022-12-20-14-00-17-271.png!\'", "Comment 14: \'Indeed", \'Comment 15: I added storage location Andel Mest\', "Comment 16: that solved it: Thanks!!afbeelding-2!\']"]\nRelated Issues:\n[\'DGS-8036\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8114\n\n### Instruction:\nThe round in the NAS is already closed. However we can still select this number on documents, in this example in the Elements to sales functionality.\r\nClosed rounds should never be selectable on any other document.\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", \'Comment 2: \\\'I have verified and fixed the "round" fields on the documents. The elements that required fix were loan payments and purchase invoice elements.\\\']\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8113\n\n### Instruction:\nHello,\r\n\r\nI am not able to move invoices to another round.\r\nScreenshot is from Richard. He has this rights.\r\n\r\nThanks for your support\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: \'Now", "Comment 4: you should be able to update round number on this invoice from Action -> Update round number on InvoicePlease verify and confirm that it works.!image-2022-12-20-11-29-51-637.png!\'", "Comment 5: \'Na tą chwilę został zmieniony parametr dla akcji: Update round number on Invoice i rundy są wyświetlane dla warunków w następujący sposób. * jeśli Sales invoice i Customer (Doc_CstID) = Slaughter --> rundy pobierane z pola Reference (Doc_IntColumn8) * jeśli Sales invoice i Customer (Doc_CstID) != Slaughter --> rundy pobierane z pola Customer (Doc_CstID) * jeśli Purchase invoice i Reference(Doc_CstID) != (Farmer", \'Comment 6: Pas Farmer\', \'Comment 7: Oppas Farmer) --> rundy pobierane z pola Supplier (Doc_IntColumn8) * jeśli Purchase invoice i Reference(Doc_CstID) = (Farmer\', \'Comment 8: Pas Farmer\', "Comment 9: Oppas Farmer) --> rundy pobierane z pola Reference (Doc_CstID)\'", "Comment 10: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Indeed for moving documents it works. Only in category Slaughtery we are not able to move.{color} {color:black}We need this action to have the correct posting on our round.{color} {color:black}{color} {color:black}Thanks for your support.{color} {color:black}{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} | |{color:black}{color} !image006.jpg|thumbnail!{color:black}{color} | *Van:* Damian Świstek (Jira) <jira@kotrak.com> *Verzonden:* dinsdag 20 december 2022 11:32 *Aan:* Jong", "Comment 11: Christine de <CJong@deheus.com> *Onderwerp:* DGS-8113 Rights to move invoices to another round | *{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}* | !image007!\'", "Comment 12: \'Hi Christine,So it means you can update round number for invoices or do you have some example where you cannot update round on invoice?\'", "Comment 13: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Yes for invoices it works", \'Comment 14: but not in category Slaughtery.{color} {color:black}I don’t know why this differs from other categories as NAS doesn’t work with SR like in MAS{color} {color:black}{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} | |{color:black}{color} !image006.jpg|thumbnail!{color:black}{color} | *Van:* Damian Świstek (Jira) <jira@kotrak.com> *Verzonden:* dinsdag 20 december 2022 13:52 *Aan:* Jong\', "Comment 15: Christine de <CJong@deheus.com> *Onderwerp:* DGS-8113 Rights to move invoices to another round | *{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 16: \'Christine", "Comment 17: could you please provide the ID of the invoice in which you cannot change the Round Number?Thank you in addvance!\'", "Comment 18: \'Dodane do listy z podsumowaniem wysłanej do klienta.\'", "Comment 19: \'{color:black}Hi Ewa,{color} {color:black}{color} {color:black}We wanted to close the round on 800629/0002/0001. This is why we need to move several invoices from one round to another.{color} {color:black}I was working on this with Richard.{color} {color:black}{color} {color:black}I now think we made the wrong approach. We have to do it from document tab.{color} {color:black}It is not possible from inside the round.{color} {color:black}{color} {color:black}Strange thing is Richard saw possibilities (read: rights to do this) I was not able to.{color} {color:black}But working on too many things I can’t specify what the problem was{color} {color:black}☹{color}{color:black}{color} {color:black}{color} {color:black}Richard is on leave. We will continue after his break.{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} | |{color:black}{color} !image006.jpg|thumbnail!{color:black}{color} | *Van:* Ewa Mucha (Jira) <jira@kotrak.com> *Verzonden:* donderdag 22 december 2022 09:42 *Aan:* Jong", "Comment 20: Christine de <CJong@deheus.com> *Onderwerp:* DGS-8113 Rights to move invoices to another round | *{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 21: \'Waiting for Richard\'", "Comment 22: \'Sorry I forgot to reply. You can resolve this as done.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8112\n\n### Instruction:\nPlease remove additional technology UT508095.\r\n\r\nThank you,\r\nRob.\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: additional technology has been removed.\'", "Comment 4: \'Thank you Piotr", "Comment 5: the ticket can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8111\n\n### Instruction:\nHello,\r\n\r\nitems 505330-z20 and 086426-z20 are on stock in Andel, see example for item 086426-z20. However, when item needs to be picked on warehouse order, system shows no available pallets. Can this be solved, and can you indicate the reason for this?\n\n### Response:\n["Comment 1: [\'!afbeelding!!afbeelding-2!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'You can close this ticket for now: Packed goods are taken in as Bulk", "Comment 4: so thats why it cannot be processed on the WO\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8110\n\n### Instruction:\nHi,\r\n\r\nWe need to get Draft PLR report but the current DHP version does not support this kind of report. I registered a ticket in Jira Servicedesk but this process takes a long time to complete usually and It is so important to us that this upgrade is done asap.\r\nAccording to the above explanation, I will be grateful if the process of starting the update will be done sooner.\r\n\r\nThanks and regards.\r\n\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\\\\r\'", "Comment 2: \'Could you please provide me a ticket number that you have raised for applications upgrade?Regards\'", "Comment 3: \'Yes. it is GDC-762\'", "Comment 4: \'Dear Ramin,I can see GDC task is assigned to Theo Berendsen. The only way to push this upgrade is to contact with Theo directly. Service Desk can do nothing to push the proccess as it is not approved", \'Comment 5: in this case\', \'Comment 6: by Theo.Please\', "Comment 7: confirm if I can close P1 task.Regards\'", "Comment 8: \'Dear Aleksandra,Thanks for your explanation.Before closing this ticket would you please tell me how much is this update cost?\'", \'Comment 9: "All necessary information like costs and date of upgrade is usually delivered within GDC task. I\\\'ll try to get some more information\', \'Comment 10: who you should contact directly as these are not in Service Desk scope and we do not have that information.Regards"\', "Comment 11: \'Hi,For costs estiamtion", \'Comment 12: please contact directly [marcin.kleszcz@kotrak.com|mailto:marcin.kleszcz@kotrak.com]Please\', "Comment 13: confirm if I can close this task.Regards\'", "Comment 14: \'Hi Aleksandra.Many thanks for your reply.Please close this ticket.\'", "Comment 15: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8109\n\n### Instruction:\nUrosły raporty PCS. Błąd rap BGB Already exists last big bag for this production.\r\nProblem jest z lotem 221219003\r\n\r\n998,8 kod 27-663YI\r\nProszę o pilną pomoc.\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: \'W razie pytan prosze kontaktowac sie z pracownikiem Produkcji : 781290728\'", "Comment 3: \'Any news ??\'", "Comment 4: \'Any news ?? Production are stopped .\'", "Comment 5: \'Production is currently running. Messages are being processed.Please let us know if we can close this issue.\'", "Comment 6: \'Thanks. Task to close\'", "Comment 7: \'Temat na retro", "Comment 8: co tu się podziało? dlaczego Bartek dogenerował 13 etykietę i zmienił jej status na ostatni jak i tak jest nieaktywna i została się na rolkach. Dlaczego dogenerowanie fikcyjnej etykiety i zmiana statusu rozwiązała problem?!image!!image-1!\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8108\n\n### Instruction:\nFor this S2P, I moved a part of a feed delivery to the next round, because I want the final stock to be paid on the next round. When I now gather the S2P, the gross value of this line is the total invoice value, but the remaining value is the value that should be paid this round. Finally the value \'paid\' is the value that should be financially transmitted to the next round (basically like moving feed to the next round, but this time just a part of the delivery). How should we solve this?\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: \'Change request will be handled under https://helpdesk.kotrak.com/browse/DHNLC-1206\'", "Comment 4: \'It will be handled on UAT and tested with Theo in January. After tests this can be deployed on PROD.\'", "Comment 5: \'New requirements related to this taks are in https://helpdesk.kotrak.com/browse/DHNLC-1226,requirements fromhttps://helpdesk.kotrak.com/browse/DHNLC-1206are outdated.\'", \'Comment 6: "Changes from task https://helpdesk.kotrak.com/browse/DHNLC-1226have been deployed on test and prod environment and confirmed in this task that works.Please verify that we can close this taks.Below are requirements fromhttps://helpdesk.kotrak.com/browse/DHNLC-1226{quote}*The new view is that even if the feed is partly moved from this round to the next round that the total remaining value of this invoice should be settled within this round. Only when a complete feed delivery is moved it should be part of the next S2P.*Example: # On Round 1 has been sent invoice DocNo123 with Weight 100kg from Milas or line has been added manually by user in Intense # From Round 1 to Round 2 has been moved 30 kg from the DocNo123Values on Round\', \'Comment 7: Financial Statement\', \'Comment 8: Saldo to pay:--------- * Round 1Round 1 (total 70kg) # DocNo 123 \', \'Comment 9: Weight 100kg # DocNo 123 \', \'Comment 10: Weight - 30kgFinancial Statement 1 (total 70kg) # DocNo 123 \', \'Comment 11: Weight 100kg # DocNo 123 \', \'Comment 12: Weight - 30kgSaldo to pay 1 (total 100kg) # DocNo 123 \', \'Comment 13: Weight 100kg----------- * Round 2Round 2 (total 30kg) # DocNo 123 \', \'Comment 14: Weight 30kgFinancial Statement 2 (total 30kg) # DocNo 123 \', "Comment 15: Weight 30kgSaldo to pay 2 (total 0kg)No values for DocNo 123---------------------*One invoice should be shown on one line in the S2P. It cannot happen that one invoice is shown on multiple lines on the S2P. This leads to a lot of problems in calculating the right saldo to pay.*Example in Intense database:SP-M/0274 - multiple line with SI000006301 on S2P was caused by grouping \'Due date\'. Procedure for calculating Saldo to pay is grouping documents also by \'Due dates\' from Feed sale lines.If there is the same number", \'Comment 16: but with different due dates it is grouping separately.It should be changed and on S2P system should displays one invoice numer only once.*Feed sale issues and verifying manualy adding elements.*\\\'Due date\\\' on Feed sale lines sometimes are empty and that causes issues with displaying line for the same document number few times. It can happen when users add manually Feed sale lines on Feed sale document and don\\\'t fill the field \\\'Due date\\\'.Some fields should be mandatory if line on feed sale is adding manually by user in Intense.Automatically calculated fields: * Customer (\\\'Customer code\\\' field from document header)Mandatory if there is no MilasId: * Date of the document * Descirption * Weight * Net Value * Price * VAT * Vat Rate * Gross value * Quantity * Due dateNot editable: * Price per 100 kgThere should be also reorganized order of field on element edit view to facilitate adding fields in good order - to be sent by DH{quote}"\', "Comment 17: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': "Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8107\n\n### Instruction:\n[INTERNAL] Podsumowanie dyżuru\n\n### Response:\n['Comment 1: []']\nRelated Issues:\n[]\n\n### End"}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8106\n\n### Instruction:\nSO-102/12/2022 only 5 ton on SOR Should be 7 ton. ( 5 ton not showing)\r\nWhen display partial sor then 5ton is visible !!!\r\n\r\nWe see also differences in DH-CDN and CDN-XL\n\n### Response:\n["Comment 1: [\'!image-3!!image-4!!image-5!!image-6!!image-7!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Can this issued SOR already for 5 tons be canceled?Were there problems when issuing this SO-49/12?Maybe the operator issued only SOR for one position.\'", "Comment 4: \'{color:black}Piotr,{color} {color:black}{color} {color:black}It is very strange in the beginning the 5000 kg is not shown.{color} {color:black}Afterwards it is shown.{color} {color:black}{color}{color:black}{color} [{color:black}@Thuis", \'Comment 5: Ronnie{color}|mailto:RThuis@deheus.com]{color:black} Can you react on the comment off Piotr{color} {color:black}{color} {color:black}{color} !image007!{color:black}{color} {color:black}{color} !image008!!image009!{color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Bert{color} |{color:#000001} {color} |{color:#000001} Kremers{color} | {color:#000001}SystemAnalist{color} _{color:#000001} _WorkingonMonday,Tuesday,Thursday_{color}_ | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.deheus.com/]>{color} | | *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+31653729893{color}{color:#000001} <tel:+31%206%2053%20729%20893>{color} | |{color:#000001} T:+31886370461{color} | {color:#000001}ChamberofCommerce 16011201{color} _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | | !image003! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image004! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | | !image005! <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} | |{color:black}{color} !image006.jpg|thumbnail!{color:black}{color} | *Van:* Piotr Gaczorek (Jira) <jira@kotrak.com> *Verzonden:* dinsdag 20 december 2022 08:13 *Aan:* Kremers\', "Comment 6: Bert <bkremers@deheus.com> *Onderwerp:* DGS-8106 SO-102/12/2022 only 5 ton on SOR Should be 7 ton. (SDNL-36456) | *{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 7: \'{color:black}Piotr,{color}{color:black}{color} {color:black}{color} {color:black}What is the connection off SO-49/12/ with this problem?{color} {color:black}I suppose you mean SOR-49/12/{color} {color:black}{color} {color:black}{color} !image001!!image002!!image010!{color:black}{color} !image003!{color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Bert{color} |{color:#000001} {color} |{color:#000001} Kremers{color} | {color:#000001}SystemAnalist{color} _{color:#000001} _WorkingonMonday,Tuesday,Thursday_{color}_ | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image011!{color:black} <[https://www.deheus.com/]>{color} | | *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+31653729893{color}{color:#000001} <tel:+31%206%2053%20729%20893>{color} | |{color:#000001} T:+31886370461{color} | {color:#000001}ChamberofCommerce 16011201{color} _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image012! <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | | !image013! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image014! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | | !image015! <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} | |{color:black}{color} !image016.jpg|thumbnail!{color:black}{color} | *Van:* Kremers", \'Comment 8: Bert *Verzonden:* dinsdag 20 december 2022 08:43 *Aan:* dgs@help.kotrak.com; Thuis\', \'Comment 9: Ronnie <RThuis@deheus.com> *Onderwerp:* SDNL-36456 : DGS-8106 SO-102/12/2022 only 5 ton on SOR Should be 7 ton. {color:black}Piotr,{color} {color:black}{color} {color:black}It is very strange in the beginning the 5000 kg is not shown.{color} {color:black}Afterwards it is shown.{color} {color:black}{color}{color:black}{color} [{color:black}@Thuis\', \'Comment 10: Ronnie{color}|mailto:RThuis@deheus.com]{color:black} Can you react on the comment off Piotr{color} {color:black}{color} {color:black}{color} !image017!{color:black}{color} {color:black}{color} !image018!!image019!{color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Bert{color} |{color:#000001} {color} |{color:#000001} Kremers{color} | {color:#000001}SystemAnalist{color} _{color:#000001} _WorkingonMonday,Tuesday,Thursday_{color}_ | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image011!{color:black} <[https://www.deheus.com/]>{color} | | *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+31653729893{color}{color:#000001} <tel:+31%206%2053%20729%20893>{color} | |{color:#000001} T:+31886370461{color} | {color:#000001}ChamberofCommerce 16011201{color} _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image012! <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | | !image013! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image014! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | | !image015! <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} | |{color:black}{color} !image016.jpg|thumbnail!{color:black}{color}{color:black}{color} | *Van:* Piotr Gaczorek (Jira) <[jira@kotrak.com|mailto:jira@kotrak.com]> *Verzonden:* dinsdag 20 december 2022 08:13 *Aan:* Kremers\', "Comment 11: Bert <[bkremers@deheus.com|mailto:bkremers@deheus.com]> *Onderwerp:* DGS-8106 SO-102/12/2022 only 5 ton on SOR Should be 7 ton. (SDNL-36456) | *{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!!image002-1!!image003-1!!image004!!image005!!image006.jpg|thumbnail!!image007!!image008!!image009!\'", "Comment 12: \'Yes it was about SOR-49/12.Was it about these fields - executed 5 tons and there are still 2 tons left? !screenshot-1! \'", "Comment 13: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 14: please raise another task.Regards\'", "Comment 15: \'Do not exist in DHP!!!image!\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8105\n\n### Instruction:\nOrder SO000040537 is not accepted by VC module in DHP. I checked business partner data in DHC, it seems to be correct:\r\n\r\nbut in DHP it is not accepted. And I\'m not sure what;s the reason: Can you check and advice how to solve?\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: \'Target Business Partner has incorrect address or target address is assigned to incorect Business Partner :) Please", \'Comment 4: compare Business Partners Code in DHC:!image-2022-12-19-15-20-02-926.png!!image-2022-12-19-15-14-38-713.png!When you resend the order\', "Comment 5: please wait a bit longer as all need some time to reprocess.Regards!image-2022-12-19-15-20-02-926!\'", "Comment 6: \'!image-2022-12-19-15-19-22-838.png!\'", "Comment 7: \'Hi Aleksandra", \'Comment 8: In this case the target business adress is assigned to the target business partner\', \'Comment 9: exactly as I expect it to be and as it is on the order\', "Comment 10: so no need to resend business partner?\'", "Comment 11: \'another example for location Veghel: SO000038550 is also not in VC module", "Comment 12: seems the same reason!afbeelding-1!\'", \'Comment 13: \\\'Another one for location Andel: Target business partner address is linked to correct business partner and address is the current address. But again in DHP the order is not synced to VC module: 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 14: table "dbo.ContactDatas".The statement has been terminated.!afbeelding-2!\\\'\', \'Comment 15: "Hi Thomas,Yes\', "Comment 16: regarding\'SO000040537\' you are right", \'Comment 17: my mistake. The issue is with main partner and probably payer as they are the same? In red I have marked addresses. As you can see from the first query\', \'Comment 18: Main has address id which is assigned in addresses table to Target.!image-2022-12-20-07-20-25-203.png!"\', \'Comment 19: "Order\\\'SO000038550\\\' - address assigned to MAin and Payer seems to be incorrect!image-2022-12-20-07-40-27-326.png!"\', "Comment 20: \'Can you please provide me with impacted SO for Andel? :)Regards\'", \'Comment 21: "Hi aleksandra\', \'Comment 22: yes adress for payer and main is incorrect: This is the case for every Sales order\', \'Comment 23: as from ERP only one address is send. This address is duplicated to all business partner fields. If you check others\', \'Comment 24: with no problems the situation will be the same. So in my opinion\', \'Comment 25: this couldn\\\'t be the reason the order is not accepted in VC module in DHP?"\', "Comment 26: \'SO for Andel = SO000032891\'", "Comment 27: \'Als for Andel: SO000041124 is an example of a sales order where combination of main business partner and address is not correct: It is accepted by VC module in DHP\'", "Comment 28: \'ForSO000032891 Main and Payer have assigned address from Target!image-2022-12-20-13-13-10-242.png!!image-2022-12-20-13-13-10-242!\'", "Comment 29: \'RegardingSO000041124Generaly", "Comment 30: VC module validates if address is correct for specific Business Partner. That is why Orders do not drop to VC in DHP. Why this specific one dropped? I will have a look and investiagte. Let you know as soon as possible\'", \'Comment 31: "there are plenty of orders with different main and target BP\\\'s: As only the TargetBP address is send with the order\', \'Comment 32: there are always mismatches: So apperently it isn\\\'t a problem: Only a few fail and dont show up in VC module"\', "Comment 33: \'SO000041124!image-2022-12-20-13-34-23-134.png!!image-2022-12-20-13-40-50-630.png!!image-2022-12-20-13-40-50-630!\'", "Comment 34: \'!image-2022-12-20-14-23-35-860.png!\'", "Comment 35: \'[~maciej.dobrzanski@kotrak.com]zwracam honor", "Comment 36: w plancie są poprawne informacje :)\'", "Comment 37: \'Hi Thomas,Sorry for my delay. RegardingSO000041124", "Comment 38: it has correct data in DHP (please see screenshot from DHP and screenshot from db). We think that first data on SO was correct that is why it dropped to DHP and after that data on SO has been changed in ERP system and synced to DHCRegards!image-2022-12-21-13-41-43-807.png!!image-2022-12-21-13-43-48-504.png!\'", "Comment 39: \'Hi Aleksandra", "Comment 40: If you check an order send today you will find the same situation: I can give you several examples. This cannot be the reason in my opinion\'", "Comment 41: \'Generalnie data commita z modify date w DHP jest spójna!image-2022-12-22-07-38-19-301.png!!image-2022-12-22-07-39-27-292.png!\'", "Comment 42: \'Wysłałam to zamówienie z OrderExportInfoes", \'Comment 43: w eventach:{code:java}{"Id":{"Id":"109a4905-97aa-4921-b168-3f659df5a74b"},"MainBusinessPartnerId":{"Id":"fbea6d3f-77a9-43de-a1c9-1efa9c3a6b64"},"MainBusinessPartnerContactDataId":2,"TargetBusinessPartnerId":{"Id":"450129fa-d186-4219-b3aa-290934bc217d"},"TargetBusinessPartnerContactDataId":2,"FinalBusinessPartnerId":null,"FinalBusinessPartnerContactDataId":null,"DocumentNumber":{"Number":7783,"Day":0,"Month":12,"Year":2022,"Series":"","Prefix":"SO"},"ForeignDocumentNumber":"SO000041124","IssueDate":"2022-12-19T00:00:00","ValidityDate":"2022-12-22T01:00:00","RealisationDate":"2022-12-22T01:00:00","OrderType":1,"OrderStatus":30,"Description":"Hygienemaatregelen in acht nem\', \'Comment 44: en\', \'Comment 45: overall aan \', \'Comment 46: Stofzak gebruiken! Ontluchings\', \'Comment 47: buizen zitten om de hoek. do ochtend lossen","OrderElementEvents":[{"ItemId":{"Id":"6ebe0f95-d93e-439c-9523-fa7437bbdfad"},"Quantity":{"Unit":"kg","Value":3000.000000},"RealisedQuantity":{"Unit":"kg","Value":0.000000},"Description":"007025 SPEEN OPTIMAAL KR"},{"ItemId":{"Id":"8561fb24-2ab6-4ebf-b95d-882fe4e8313a"},"Quantity":{"Unit":"kg","Value":6000.000000},"RealisedQuantity":{"Unit":"kg","Value":0.000000},"Description":"008851 BIG VERHAGEN VETHUIZEN"}]}{code}EventType:{code:java}Plant.VC.BusinessLogic.DomainAbstractions.Orders.OrderChangedEvent{code}\\\'\', "Comment 48: \'Errory tylko dla VT:!image-2022-12-23-13-38-32-651.png!!image-2022-12-23-13-38-57-691.png!\'", "Comment 49: \'!image-2022-12-23-13-43-58-091.png!!image-2022-12-23-13-43-23-795.png!\'", "Comment 50: \'Dear Thomas,We have verified logs and we do not have exact information if the address on OrderSO000041124 has been changed in ERP system after it arrived to DHC. What is more", \'Comment 51: in this task we are focused on unblocking the process.Please\', "Comment 52: also let us know if problem ith address wil be solved on your side.Regards\'", "Comment 53: \'Dear Thomas,Is there anything else we can do for you due to this task? Or can we close it?Regards\'", "Comment 54: \'Dear Thomas,Is there anything else we can do for you due to this task? Or can we close it?Regards\'", "Comment 55: \'please close this task\'", "Comment 56: \'Thank you.Regards\']"]\nRelated Issues:\n[\'DGS-8094\', \'DGS-7968\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8104\n\n### Instruction:\nplease can you link these plrs they are generated as job orders but appear as if they have not. \r\n\r\nalso could you please share the steps on how the linking is done.\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: \'!image-2022-12-20-11-11-28-550.png!!image-2022-12-20-11-11-42-165.png!\'", "Comment 4: \'!image-2022-12-20-12-10-29-102.png!\'", "Comment 5: \'Hi,For the list below all PLRs had documnets JO", "Comment 6: IR+ and IR- in ERP so I have mapped them under db in DHC!image-2022-12-20-13-43-38-037.png!Regards\'", "Comment 7: \'Hello", "Comment 8: please assist with these as well!image-1!\'", "Comment 9: \'Hello,Done . Please", "Comment 10: verify\'", "Comment 11: \'Hello", "Comment 12: all documents are linked. thank you \']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8103\n\n### Instruction:\nHi Ewa,\r\n\r\nWe got this problem.\r\n\r\nWe can’t move the feed from round 1 to round 2. Why not?\r\n\r\nMet vriendelijke groeten,\r\n\r\nBessel van den Broek\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", \'Comment 2: "Feed sale document for Round005138/0001/0002 wasn\\\'t created before. We created yesterday feed sale document FE-P/0017 for this round.Now it should be possible to move feed to this round.Plase verify and confirm that is ok."\', "Comment 3: \'Dodane do listy z podsumowaniem wysłanej do klienta.\'", \'Comment 4: "[~bbroek@deheus.com]could you check?I think it\\\'s done but could we close the task?"\', "Comment 5: \'Confirmed that can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8102\n\n### Instruction:\nFor some RM we see that stock is reserved. However, the Lot reports that are shown in Reservation are already confirmed.\r\nExample: Andel, RM 0294, serial 0144 shows > 10 reservations on Lot reports from October. E.g. 0051071022003. These are already confirmed - we do not expect that stock is reserved for these Lot reports anymore.\r\nIn the Lot report I do see that for item 0294 stock was taken from serial 0144. So, perhaps the reservation was not confirmed?\r\n\r\nSame may have happened for other RM / other plants?\r\n\r\nCan you please check why the stock is reserved / how it can be confirmed or released? \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: "{code:java}/****** Script for SelectTopNRows command from SSMS ******/SELECT distinct s.[SourceDocumentNumber],p.ProductionLotStatus FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnitReservations] s inner join [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] su on su.Id=s.Id left join [dbo].[ProductionLots] p on s.SourceDocumentNumber=p.LotNumber where --s.Id in (select id FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] --where Barcode like \\\'OB-%\\\') and --s.SourceDocumentNumber like \\\'005%\\\' and p.ProductionLotStatus=4{code} !screenshot-1! jest takich 23{code:java}declare @barcode nvarchar(max) = \\\'5-S00003\\\'select u.QuantityValue AS \\\'Wms Qty\\\'\', \'Comment 4: s.Quantity\', \'Comment 5: s.QuantityOnHand\', \'Comment 6: sum(sr.QuantityValue),s.Quantity - s.QuantityOnHand as difffrom dbo.StockUnits sleft join DHPlantWmsBusinessLogicMain.dbo.Unitloads u on u.id = s.unitloadidleft join dbo.StockUnitReservations sr on sr.Id = s.Idwhere s.Barcode = @barcodegroup by u.QuantityValue\', \'Comment 7: s.Quantity\', "Comment 8: s.QuantityOnHand--delete sr--from dbo.StockUnits s--inner join dbo.StockUnitReservations sr on sr.Id = s.Id--where s.Barcode = @barcode--update dbo.StockUNITS--SET QuantityOnhand = Quantity--where barcode = @barcodeselect u.QuantityValue AS \'Wms Qty\'", \'Comment 9: s.Quantity\', \'Comment 10: s.QuantityOnHand\', \'Comment 11: sum(sr.QuantityValue),s.Quantity - s.QuantityOnHand as difffrom dbo.StockUnits sleft join DHPlantWmsBusinessLogicMain.dbo.Unitloads u on u.id = s.unitloadidleft join dbo.StockUnitReservations sr on sr.Id = s.Idwhere s.Barcode = @barcodegroup by u.QuantityValue\', \'Comment 12: s.Quantity\', \'Comment 13: s.QuantityOnHand{code}"\', \'Comment 14: "I corrected the data for plrs from the list below:|51071022003||51071022004||51071022005||51071022006||51071022007||51071022008||51071022009||51071022010||51071022011||51071022019||51071022020||51071022021||51071022023||51071022024||51071022025||51071022026||51071022028||51071022030||51071022032||51071022033||51081022002||51081022008||51241022018|Please verify for this plant.We\\\'ll check the other plants after your feedback.As for the analysis of the cause of the RCA will be needed - please let me know whether to do it."\', "Comment 15: \'RCA was created for cause analysis DGS-8168.\'", "Comment 16: \'RCA was created for cause analysis DGS-8168.This issue has been closed.\']"]\nRelated Issues:\n[\'DGS-8087\', \'DGS-8168\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8101\n\n### Instruction:\nVT \'s are not going from DHXC to CDN\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are closing this task as it is duplicate to (DGS-8099).Please,follow above task.Regards\'", "Comment 3: \'What was the reason we had to open an incedent.I did this and now it is closed.!image-1!\'", "Comment 4: \'The type was changed in an earlier SR task dgs8099.There was no need to make a new one.\']"]\nRelated Issues:\n[\'DGS-8099\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8100\n\n### Instruction:\nDzień dobry,\r\n \r\nproszę o sprawdzenie i wyeliminowanie błędu jaki pojawia się podczas dodawania nowej struktury podległościowej w pionie sprzedaży pozostałych Gatunków (komunikat błędu w załączniku).\r\n\r\nProblem taki nie występuje w pionie operacyjnym Biuro Obsługi Klienta. \r\n\n\n### Response:\n["Comment 1: [\'!obraz!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Any news about issue?\'", "Comment 4: \'We are analysis issue\'", "Comment 5: \'Reason are different codes in Optima and XL.You can make full synchronizationa forom XL configuration (please firstly make this operation on test database)orYou can change names in XL in this window in that way they will be the same as they are in Optima and save. This albo should resolve issue. I checked andsubordinate structure is not using on any posting scheme", "Comment 6: all relations in standard database tabels are based on ID not on code.Before you make changes (manually or using synchronisation) you should check if you have any addins baased onsubordinate structure and using Code against ID.!image-2022-12-21-07-36-16-645.png!\'", "Comment 7: \'Po zmianie ręcznej w CDN można podłączać podległe zespoły w Optimie", \'Comment 8: problem jest natomiast gdy zostanie utworzony nowy węzeł podległy\', "Comment 9: nie ma możliwości utworzenia pod nim kolejnego ponieważ w strukturze podległościowej w CDN nie istnieje taki węzeł. Jak ma zostać to rozwiązane? Czy ma zostać taki węzeł utworzony ręcznie CDN? Czy ma zostać przeprowadzona synchronizacja przy każdorazowym utworzeniu węzła nadrzędnego?Na serwerze testowym po utworzeniu węzła głównego pojawia się w CDN testowym natomiast Makroregionu (węzła poniżej) po synchronizacji nie przechodzi do CDN. \'", "Comment 10: \'*XL/943340**problem z synchronizacją między XL a Optimą*.Konsultacje z comarchem. Są zduplikowane dane w bazach. Comarch ma podesłać skrypty do rozwiązania problemu.\'", \'Comment 11: "There are some duplicated data between XL and Optima databases!image-2022-12-23-16-29-26-392.png!I\\\'m consulting solution for that witherp system manufacturer.I\\\'ll let you know as soon as possible on next steps."\', "Comment 12: \'Any news ??\'", "Comment 13: \'Temat był już analizowany w ramach task DGS-7400,Po przekazaniu pojawiających się komunikatów producent sugerował iż problem może wynikać z błędnego hasła dla cdndts", \'Comment 14: co w Państwa opinii zostało wykluczone.Po wykonaniu synchronizacji w ramach baz testowych problem przy edycji atrybutów nie występował. Resynchronizacja była zalecana w ramach środowiska produkcyjnego\', \'Comment 15: lecz do dnia dzisiejszego nie ustalono terminu kiedy można ją wykonać.Na chwilę obecną zalecamy by w pierwszej kolejności ponownie wykonać synchronizację w ramach świeżych baz testowych (zarówno XL jak i Optimy) zweryfikować czy prawidłowo synchronizują się elementy struktury podległościowej\', \'Comment 16: pracowniczej i atrybutów a także czy miedzy systemami prawidłowo przekazywane są listy płac. Dopiero po potwierdzeniu prawidłowości tych procesów w ramach środowiska testowego zalecamy wykonanie resynchronizacji w ramach baz produkcyjnych.-----The topic has already been analyzed as part of task DGS-7400,We have sent error messages to producer\', \'Comment 17: the Comarch suggested that the problem may be due to the wrong password for cdndts\', \'Comment 18: what\', \'Comment 19: in your opinion\', \'Comment 20: should be excluded.After performing the synchronization within the test databases\', \'Comment 21: the problem with editing the attributes did not occur. Resynchronization was recommended in the production environment\', \'Comment 22: but we still did not receive information if and when should it be done on our or your side.At the moment\', \'Comment 23: we recommend that you first should perform the synchronization again within the fresh test databases (both XL and Optima) to verify whether the elements of the subordinate structure\', \'Comment 24: employee structure and attributes are synchronized correctly\', \'Comment 25: and whether payrolls are correctly transferred between the systems. Only after confirming the correctness of these processes within the test environment\', "Comment 26: we recommend performing resynchronization within the production databases.\'", "Comment 27: \'Dzień dobry", \'Comment 28: na obecnych bazach testowych problem z synchronizacją nie występuje\', \'Comment 29: nie były odświeżane bazy\', \'Comment 30: cdndts jest poprawny bez tego nie pobierałyby się listy płac\', "Comment 31: a pobierają się prawidłowo. Proszę o dalszą analizę problemu. \'", "Comment 32: \'Dzień dobryna testach nie było problemu po wykonaniu ponownej synchronizacji. Jeśli wykonują Państwo kopie zarówno optimy jak i XL do zintegrowania tych dwóch testowych środowisk niezbędna jest ponowna synchronizacja. Ze co było już przez nas zalecane kilka miesięcy temu. Środowiska testowe były integrowane już jakiś czas temu więc najlepszym rozwiązaniem w zaistniałej sytuacji będzie utworzenie nowych środowisk testowych i ich ponowna synchronizacja", "Comment 33: jeśli proces synchronizacji przebiegnie bez błędów a opisane problemy w taks {color:#172b4d}DGS-8100 i {color}{color:#172b4d}DGS-7400 nie będą występowały proponujemy wykonanie synchronizacji na środowisku produkcyjnym{color}\'", "Comment 34: \'Po odświeżeniu baz na tescie", \'Comment 35: podczas wykonywania synchronizacji\', "Comment 36: bład aktualizacji struktury atrybutów klas nie występuje:!image!\'", \'Comment 37: \\\'Ponadto po wykonaniu synchronizacji na teście utworzone w Optimie Makroregiony w "Pion Sprzedaży POZ.GAT." nie pojawiły sie w CDNXL (mimo że etap synchronizacji struktury podległościowej nie zgłosił błędów).Raport z synchronizacji w załaczniku.[^Raport z Synchronizacja struktury organizacyjnej.7z] _(121 kB)_\\\'\', "Comment 38: \'Proszę o wskazanie lokalizacji środowisk testowych w celu weryfikacji\'", "Comment 39: \'Środowiska sa te same co dotychczas:BazySQL05-20\\\\\\\\cdnxl_deheus (XL)sqL05-20\\\\\\\\cdn_DEHEUS (Optima)Optima na DEV-TS02-20", "Comment 40: podobnie XL (baza TEST_SQL5_XLDH).\'", "Comment 41: \'Trwa weryfikacja problemu: *XL/944430*\'", "Comment 42: \'Mamy jakieś wieści ?.Struktura musi wejść w życie 1-go stycznia a Kadry na chwilę obecna nie sa w stanie w zasadzie nic zrobić.\'", "Comment 43: \'Na razie temat jest dalej weryfikowany przez producenta. Jako obejście możemy zaproponować wprowadzanie tej struktury od strony XL", "Comment 44: wówczas synchronizacja działa poprawnie.\'", "Comment 45: \'Jesteśmy świadomi obejścia ale czy takie rozwiazanie nie wygeneruje problemów dalej", "Comment 46: gdy synchronizacja zacznie dzialać ?\'", "Comment 47: \'Jak tylko otrzymam informację od producenta niezwłocznie ją Państwu przekażę\'", "Comment 48: \'Dalsza weryfikacja zgłoszenia wykazała iż na Państwa bazie brakuje standardowych procedur", \'Comment 49: zauważono brak procedury: ZnajdzDzialStrPodleglosciowej\', \'Comment 50: mimo uzupełnienia jej w ramach środowiska testowego błąd nadal występował\', "Comment 51: wymagana jest w tym temacie dalsza weryfikacja. Trwają prace związane z dalszą analizą przyczyny problemu i braków na Państwa bazie\'", "Comment 52: \'Od producenta na chwilę obecną nie otrzymaliśmy dalszych wytycznych\'", "Comment 53: \'Czy mamy jakieś nowe wieści ?Temat jest naprawdę pilny.\'", "Comment 54: \'Cały czas jesteśmy na etapie weryfikacji.Proszę jeszcze o informację czy ta struktura jest wykorzystywana w XL?Bo jeśli nie to istnieje możliwość wyłączenia synchronizacji w tym zakresie przez zaznaczenie w XL parametru:!image-2023-01-02-14-08-00-177.png!wówczas od strony optimy będziemy mieć możliwość wprowadzania danych bez komunikatu o braku synchronizacji.\'", "Comment 55: \'Tak jest wykorzystywana.Ponadto przy właczonej blokadzie wyszarzy sie opcja do zapisów z Aplikacji Comarch HRM i zaczna sie problemy z E-Pracownikiem.!image-1!\'", "Comment 56: \'Udało się rozwiązać przyczynę problemu. Dodano do bazy brakująca procedurę i nadano jej odpowiednie uprawnienia.Proszę o weryfikację. Jeśli jakiś gałęzi brakuje w XL proszę je dodać przez edycję tych pozycji w Optimie (np. przez edycję nazwy - dodanie kropki/ zapisanie zmian/ usunięcie kropki)\'", "Comment 57: \'Wstępnie wygląda obiecująco.Do końca dnia będę miał potwierdzenie z kadr.\'", "Comment 58: \'Czy zgłoszenie można uznać za zakończone?\'", "Comment 59: \'Tak", "Comment 60: możemy.\']"]\nRelated Issues:\n[\'DGS-7400\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8099\n\n### Instruction:\nVT \'s are not going from DHXC to CDN \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: \'Hi,This should be an incident. Please", "Comment 4: approve changing task type.Regards\'", "Comment 5: \'incident has be created Close this ticket\'", "Comment 6: \'Further analysis will be here.\'", "Comment 7: \'I was asked to open a incident what i did.Instead off closing this ticket you did close the the opend incident\'", \'Comment 8: "VT doesn\\\'t run through and no message has been shown.!image-1!"\', "Comment 9: \'!image-2!\'", \'Comment 10: "Documents for VT\\\'s have been generated."\', "Comment 11: \'What did course the problem\'", "Comment 12: \'This issue is related with DGS-7827,after realization this task( DGS-7827) the problem should no longer occur.\'", "Comment 13: \'The mentioned problem are solved but a lot new prblems did occur.!image-3!\'", "Comment 14: \'Are LOT report the problem\'", "Comment 15: \'The second line gives problems.It is not know what exacly the problem isOther line have a lack off product\'", "Comment 16: \'Yes the reason is despite generating JO no IR- and IR+ in XL.Should we verify it?\'", "Comment 17: \'Can you correct IR- and IR+ ?So far i know you do this often.\'", \'Comment 18: "{code:java} select * FROM [Evolution_DHCountry].[dbo].[VehicleTickets] where DocumentNumber like \\\'5767/12/2022%\\\' or DocumentNumber like \\\'5774/12/2022%\\\'or DocumentNumber like \\\'5630/12/2022%\\\' select DeliveryId,* FROM [Evolution_DHCountry].[dbo].[VehicleTicketElements] where VehicleTicketId in(\\\'B022E818-CE0E-41ED-8284-6251EE369B6F\\\',\\\'B5581C27-E4BC-4FAB-9E7F-71D30F2AFDC0\\\',\\\'AD02A43A-1F11-4441-832C-E8EA19FE8F8F\\\')SELECT * FROM [DhcErpPlugin].[dbo].[DeliverySyncs] where DhcId in(\\\'DA4DD13D-B138-4857-922A-C26028D64A84\\\',\\\'2F76562D-F12A-4080-99C1-BB8657E931FD\\\',\\\'12F57728-881F-473F-8DCD-81911C8126F5\\\',\\\'388FF789-FF27-470D-A439-7BFE2DD6938E\\\',\\\'EF9CB350-A50F-49A8-85F5-B5EEC2B58D74\\\',\\\'4723C65A-A90E-41D0-937D-53B60039D894\\\' ){code}"\', \'Comment 19: "Hello\', \'Comment 20: for December 2022 there are three VT\\\'s on the list to generate.Out of resources due to invalid IR+ warehouse - should be on DCVE.Items:0113500716-B75000707-B1000IR+: !screenshot-1! !screenshot-2! !screenshot-3! !screenshot-4! "\', \'Comment 21: " !screenshot-5! PORI-31/10/2022/VIMPPORI-37/10/2022/VIMPPORI-5/12/2022/VIMPPORI-65/12/2022/VIMPna styczeń: !screenshot-6! {code:java} select deliveryid,* FROM [Evolution_DHCountry].[dbo].[VehicleTicketElements] t where VehicleTicketId in(\\\'B2A3F2EC-83E3-4A8B-961F-97B8D27B2AA2\\\') SELECT * FROM [DhcErpPlugin].[dbo].[DeliverySyncs] where DhcId in(\\\'3E90283F-4F03-4375-AA8E-962FB8A57BE7\\\',\\\'E53E4B4E-A527-401C-A133-01530CAF381B\\\',\\\'29A47317-9828-4F21-A856-1FED9AEA1343\\\',\\\'D010E1FB-3ED5-4C6A-A2F5-639F808A448C\\\',\\\'A53FCCF1-89DB-4C49-AEBD-E6160D62DF91\\\' )SELECT *select cdn.nazwaobiektu (Dst_TrnTyp\', \'Comment 22: Dst_TrnNumer,1,2) FROM [CDNXL_DHNL_PROD].[CDN].[Dostawy] where Dst_GIDNumer IN(42686\\\\t,45255\\\\t,44566\\\\t,42719){code}"\', "Comment 23: \'Example : 01135R+ and R- are present.What is wrong?!image-4!!image-5!!image-6!!image-7!!image-8!!image-9!!image-10!\'", "Comment 24: \'VT - quantity!image-2023-01-25-08-29-32-430.png!Stocks in XL:!image-2023-01-25-08-29-51-102.png!but IR+ has been created for incorrect warehouse!image-2023-01-25-08-30-24-135.png!\'", "Comment 25: \'Ticket can be closed\']"]\nRelated Issues:\n[\'DGS-7827\', \'DGS-8101\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8098\n\n### Instruction:\nThere seems to be a problem starting today regarding the feed sale document: feed lines move but also stay on the previous round? This withelds us from finishing a round.\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 Steffen", "Comment 4: please provide all IDs of the Feed Sales where you noticed this problem.\'", "Comment 5: \'In this case FE-B/0293 (ID 60043) and FE-B/0484 (ID 78139). Koen had the same problem with FE-B/0476 (ID 77545) and FE-B/0347 (ID 64455). These were the first we did so I think it counts for every feed sale.\'", \'Comment 6: "For Feed Sale FE-B/0153 (ID 31246) I don\\\'t get this problem. I don\\\'t know if it has anything to do with the updates you just did? However for the feed sales below the lines are still on both rounds.!image-1!"\', "Comment 7: \'linked toDGS-8097\'", "Comment 8: \'Hi,I think that do it again after yesterday changes it should be good.Is it right now everything correct and we can close task?\'", "Comment 9: \'Hello Damian,I think it is all right indeed now. Yesterday morning", \'Comment 10: we stopped after the 2 examples\', "Comment 11: and these I could successfully move yesterday evening.\'", "Comment 12: \'Ok", "Comment 13: great.So I close the task. In case of any issues please let us know and report.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8097\n\n### Instruction:\nI set 4 feed linens to another round B004145/0035/0003 to B004145/0035/0003 with move and Tick\r\nThe weight is now on both rounds\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: \'linked toDGS-8098\'", "Comment 4: \'Hi,\\\\r\\\\rI think that do it again after yesterday changes it should be good.\\\\r\\\\rIs it right now everything correct and we can close task?\'", "Comment 5: \'Dodane do listy z podsumowaniem tasków wysłanej do klienta.\'", "Comment 6: \'[~khuibers@deheus.com]could you check and verify?Could we close the task?\'", "Comment 7: \'Yes\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8096\n\n### Instruction:\nI accidently closed the round of the wrong customer. Could you please re-open round B002150/0187/0002 (ID 61574)? Thank 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: "Round is reopened now. It\\\'s in inbox Brigitte Danneel as it was before"]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8095\n\n### Instruction:\nPlease set ID-77165 back to entry\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: \'Duplicated - DGS-8092\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8094\n\n### Instruction:\nThe order SO000040557 is not in the VC module of DHP, but is send to the PCS: The problem is already known, as a solution was advised to resend BP for the order. In this case I resend BP 100064 and BP 000168. But this doesn\'t bring a solution. Please check this example and advice what to do\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: \'Error message dla wskazanego zamówienia:!image-2022-12-19-09-15-00-714.png!\'", "Comment 3: \'Dear Thomas,Please", "Comment 4: verify if address and Customers are correct:!image-2022-12-19-09-55-02-508.png!Under DB:!image-2022-12-19-09-56-50-536.png!Regards\'", "Comment 5: \'Oke", "Comment 6: so to understand: The address send with the order is not the current adress (is current) registered in DHC\'", "Comment 7: \'I think this screenshot would be clearer:Main BusinessPartnerID = PayerBusinessPartnerID =BB3FECBE-0583-4256-A7E5-982A1521B8ABTargetBusinessPartnerID =0FAD898B-A546-4D96-A2F4-B0C6BF1FFDEEbut target has the same address as Main and Payer but if you have a look at 3rd query", "Comment 8: only Target has correct address / address ID!image-2022-12-19-13-09-18-421.png!\'", \'Comment 9: "Oke\', \'Comment 10: I checked and changed so that the address is set to is current: Then I resend the order\', "Comment 11: but in DHP it\'s still not accepted bij VC module", \'Comment 12: please check!afbeelding!"\', "Comment 13: \'Ticket can be closed", "Comment 14: is solved now\'", "Comment 15: \'It is in DHP in VC now:!image-2022-12-19-14-08-40-345.png!\'", "Comment 16: \'Regards :)\'", \'Comment 17: "Sorry\', \'Comment 18: I haven\\\'t noticed your information that task can be closed.Thank you for your information.Regards"\', "Comment 19: \'Can you check another example?\'", "Comment 20: \'Sure,I have received new task. So I will proceed under DGS-8105Regards\']"]\nRelated Issues:\n[\'DGS-8105\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8093\n\n### Instruction:\non Dec 16/2022 We had a problem Verifying( Accept & Confirm) Production lot reports on DHP . and was solved @adrina Kozak . but this particular PLRs couldn`t leave from DHC and reach ERP ; \r\nError says PLR skipped (NULL) \r\n26 PLRs not yet Generated ! our finance Dep can`t do weekly report for this sake ; \r\nThanks in Advance \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: \'Thanks very Much Much Appreciated and I be here to contact and help as needed ;\'", "Comment 4: \'Technology 7700-B25 ver 439 is not generated. Please", \'Comment 5: generate technology.!image-2022-12-19-11-57-08-777.png!For two others technologies\', \'Comment 6: I have resent Technology!image-2022-12-19-12-01-18-810.png!!image-2022-12-19-12-00-33-662.png!PLR should generate documents in a while\', \'Comment 7: if not\', "Comment 8: please generate documents again:!image-2022-12-19-12-09-25-098.png!\'", "Comment 9: \'Please", "Comment 10: let us know if you need any further assistance.Regards\'", "Comment 11: \'Dear I did generated Technology 7700-B25 Ver 439 ; it is generated I will wait a little and try Generate the PLR ; Will tell ya the Updates and results Thanks Again ; !image001! *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com> *Sent:* Monday", \'Comment 12: December 19\', "Comment 13: 2022 14:11 *To:* Gemechis Terefe <gemechis@alemakoudijs.com> *Subject:* DGS-8093 Production lot reports Re-submitted Dec 16/2022 Didn`t leave DHC or Reached to ERP . Not yet Generated . !image002!!image003!!image004!!image005!\'", "Comment 14: \'Waiting for your feedback then.Regards\'", "Comment 15: \'Hey Dear I did generated the Two 7700-B25 Ver 439 And 6630-B50-C And also 8 PLRS are generated already Will tell you the final Result ASAP Thanks Again *From:* Gemechis Terefe !image001!!dhc 1.PNG|thumbnail!!dhc 2.PNG|thumbnail!!image002!!image003!!image004!!image005!\'", "Comment 16: \'Sure. Waiting for your feedback then.Regards\'", "Comment 17: \'Hello Dear From 26 PLR only 9 is Generated and All 7700 layer phase one (17) are not yet generated . I did Generate the Technology for 7700 and they are all generated . But this one still not yet Generated Documents !image001! !image002! !image003! !image004! All this layer Super phase 1 are not yet Generated . I tried to Generate the Documents many times ", \'Comment 18: We also did added like Limestone \', \'Comment 19: FulFat soya and Corn white … But still I couldn`t Generate this documents from DHC Hope to Hear from you . Thanks *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com> *Sent:* Monday\', \'Comment 20: December 19\', "Comment 21: 2022 15:50 *To:* Gemechis Terefe <gemechis@alemakoudijs.com> *Subject:* DGS-8093 Production lot reports Re-submitted Dec 16/2022 Didn`t leave DHC or Reached to ERP . Not yet Generated . !image001-1!!image002-1!!image003-1!!image004-1!\'", "Comment 22: \'Hi,PLRs with error message that technology is inactive have been generated / processed. There are some left but they are PLRs", "Comment 23: where quantity on VT was missing. This is to verify on your side.Reagrds\'", "Comment 24: \'Hello Dear Problem Solved .Now all PLRS are Generated ! I used to check stalk missing from DHC log files with amount of Kg and inform Departments about it . But now since the Error message is only say PLR skipped (NULL) was hard to tell Missing Quantity . but Told Production and Finance Department to enter Row material and confirm for the for PZ seeing ThePLR. Then after putting Limestone ", \'Comment 25: Lime Fine \', \'Comment 26: Corn White\', "Comment 27: FulFAT .. they all Generated ; @Aleksandra Przybyłek Thanks So much for your Time . Thanks Jira service help desk portal. Much Appreciated \'", "Comment 28: \'Thank you for your information :)In taht case", "Comment 29: I am closing this task.Regards\'", "Comment 30: \'Yes Pls ; You can close it ! Thanks very Much\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8092\n\n### Instruction:\nPlease set ID 77165 slaughtery report 1124 back to entry\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 It´s urgent", "Comment 3: we have to pay the customer\'", \'Comment 4: "It\\\'s in Entry now"]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8091\n\n### Instruction:\nProszę o zmianę ilości towaru\xa0 do ZS -1025 ( Prochoń Małgorzata)\xa0\xa0z 3,990 na 5,180 i podłączenie 3 komory. Był doładunek i nie został doliczony.\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-2022-12-17-07-01-15-564.png!!image-2022-12-17-07-00-40-077.png!WZ jest już w XL!image-2022-12-17-07-02-09-137.png!\'", "Comment 3: \'Please try to make another VT for missing quantity\'", "Comment 4: \'He spoke to the manager", "Comment 5: it is to be corrected on existing documents.\'", "Comment 6: \'Data has been corrected. Please verify\'", "Comment 7: \'Still to be improved: VT- 18581 ,załadunek – 39,740i waga wyjazdowa – 39,740 T\'", "Comment 8: \'Done. PLease let me know if I can close this ticket?\'", \'Comment 9: "It\\\'s ok\', \'Comment 10: please close task."]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8090\n\n### Instruction:\nThis is to check access to the Jira service Desk. \r\nTest Ticket \r\nMuch appreciated ! \n\n### Response:\n["Comment 1: [\'Very Helpful !\'", "Comment 2: \'Dear Jira Service Desk This was just a test Ticket created to check the Jira portal Ethiopia . Thanks very much for your concern and Much appreciated . I confirm to close this ticket back now . Thanks Again \'", "Comment 3: \'Hi,Thank you for your ticket.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8089\n\n### Instruction:\nProszę o przypisane\xa0 na zbiornikach symbole surowców (wytłuszczenie), których nie ma a są niezbędne abym mógł zadozować z nich surowce biorące udział w naważaniu.\r\nMy mamy taką możliwość zmiany, ale pod warunkiem 0 ilości na zbiorniku,\xa0a one są większe od 0 kg.\r\nZb 622004\xa0 2004 -\xa0 0818\xa0\xa0\xa0\xa0\xa0 \r\n622006\xa0 2006 – 21482\xa0\xa0\xa0\xa0\xa0 \r\n622008\xa0 2008\xa0 -\xa0 0641\xa0\xa0\xa0\xa0\xa0 \r\n623011\xa0 3011 -\xa0 0645\xa0\xa0\xa0\xa0\xa0 \r\nTemat pilny z powodu realizacji zam.produkcyjnych .\r\nDo uzupełnienia 4 pola zaznaczone na czerwono.\n\n### Response:\n["Comment 1: [\'!silosy.bmp|thumbnail!\'", "Comment 2: \'Hello", "Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'", "Comment 4: \'Hi,Data has been filled :!image-2022-12-16-23-21-58-856.png!PLease verify and let us know if we can close this issue\'", "Comment 5: \'please close task\'", "Comment 6: \'[[DHP 2.X] Wizualizacja PCS - Tank data|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHP.one#%5bDHP%202.X%5d%20Wizualizacja%20PCS%20-%20Tank%20data&section-id=\\\\\\\\{F3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9}&page-id=\\\\\\\\{001B9CF9-BE9E-4404-92B2-E01D738A0F63}&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.one%7CF3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9%2F%5BDHP%202.X%5D%20Wizualizacja%20PCS%20-%20Tank%20data%7C001B9CF9-BE9E-4404-92B2-E01D738A0F63%2F%29])\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8088\n\n### Instruction:\nNie można aktywować etykiety na towar 915914-w25 1t numer kodu kreskowego etykiety to 27-65JQP.Dostawa z vt-24395.Komunikat na skanerze: „Aktywacja kodu kreskowego przekroczy ilość z dostawy 1t. Operacja została przerwana”\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: \'Please try now\'", "Comment 4: \'please close task\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8087\n\n### Instruction:\nWe have problem with some items/Unit load with wrong reservation. The productions are closed but they still are reserving some unit load. \r\n\r\nExample production 0881031122029, 0881031122030 and 0881031122038\r\n\r\nCould you check why reservation was not done when productions were closed, check if we have more productions with the same error and fix it?\r\n\r\nIt\'s urgent because system not allow to move or make inventory for unit load with reservation.\r\n\r\nThank you\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: \\\'"system not allow to move or make inventory for unit load with reservation." Can you attach screenshot with error?\\\'\', "Comment 4: \'Item21808 barcode 88-W0DY0Q!image-1!\'", "Comment 5: \'Please verify if problem still occurs for88-W0DY0Q and let me know. If changes helps then we will make the same on other barcodes\'", \'Comment 6: "we have the same error.It\\\'s not possible move item.!image-2!!image-3!"\', "Comment 7: \'Please verify now if problem still occurs for88-W0DY0Q and let me know if I can make the same changes on other barcodes\'", \'Comment 8: "Hi MonikaFor 88-W0DY0Q the problem is solved\', \'Comment 9: however we still have problem with a couple of reservations.As you can find by yourself there\\\'s a lot of ULs with reservation for PLRs already confirmed and consumed.You can lower the priority of this task for P2 but we need all UL with already confirmed PLR reserved fixed by monday morning because we\\\'ll have many location stocktakings next week.Thank you very much!image-4!"\', "Comment 10: \'All barcodes related with productions0881031122029", "Comment 11: 0881031122030 and 0881031122038 has been corrected. PLease provide us if you have another lot numbers with this kind of issue.\'", \'Comment 12: "HiWe found some barcodes in Stock engine\', \'Comment 13: but I don\\\'t know if this will have some impact on stocktaking routine.We also found new ULs with confirmed PLR. Do we need to raise a new DGS for that?0881031122036088104112200908810411220310881031122026088201112200208810311220400881031122023088103112203508810311220330881011122017088103112203408810311220270881031122037Thank you!image-5!!image-6!!image-7!"\', "Comment 14: \'poprawa dla PLR:881011122017881031122023881031122026881031122027881031122029881031122030881031122033881031122034881031122035881031122036881031122037881031122038881031122040881041122009881041122031882011122002882260122004\'", "Comment 15: \'Reservations have been corrected for PLR from the list:881011122017881031122023881031122026881031122027881031122029881031122030881031122033881031122034881031122035881031122036881031122037881031122038881031122040881041122009881041122031882011122002882260122004Please verify.Please confirm to create an RCA for root cause analysis.\'", "Comment 16: \'{code:java} SELECT distinct s.[SourceDocumentNumber],p.ProductionLotStatus FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnitReservations] s inner join [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] su on su.Id=s.Id inner join [dbo].[ProductionLots] p on s.SourceDocumentNumber=p.LotNumber where p.ProductionLotStatus=4{code}\'", "Comment 17: \'[[DHP 3.0] Stocktaking - Reserved StockUnits", "Comment 18: rezerwacja na stockach|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Stocktaking%20-%20Reserved%20StockUnits,%20rezerwacja%20na&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{F85E69B9-BC0D-4FAA-BDC2-3E89CD2E4917}&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%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHP%203.0%5D%20Stocktaking%20-%20Reserved%20StockUnits%2C%20rezerwacja%20na%7CF85E69B9-BC0D-4FAA-BDC2-3E89CD2E4917%2F%29])\'", \'Comment 19: "Hi PiotrThank you for this correction!It\\\'d be nice to now why is happened\', "Comment 20: however when this happened we had 7.9 version and now we have 8.3Since then we didn\'t experienced this again", \'Comment 21: maybe it was some error of the version.If you think is a good task\', \'Comment 22: we can create a RCA.Thank you"\', "Comment 23: \'If the analysis is to be for RCA the verification would be for new cases ( as you mentioned", "Comment 24: there were version changes for DHP).\'", "Comment 25: \'Po konsultacjach z [~maciej.dobrzanski@kotrak.com]:Wskazane raporty zostały kilkukrotnie potwierdzone (w tym samym czasie)", \'Comment 26: co mogło spowodować powstanie rezerwacji już po potwierdzeniu PLR. Musimy spróbować zreprodukować możliwość kilkukrotnego\', \'Comment 27: równoległego potwierdzenia PLR\', \'Comment 28: żeby dobrać najkorzystniejsze rozwiązanie problemu. - [~maciej.buchacz@kotrak.com]\', \'Comment 29: [~aleksandra.masternak@kotrak.com]prośba o testy i zreprodukowanie błędu.Proponowane sposoby naprawy: - zablokowanie przycisku na UI po pierwszym kliknięciu\', \'Comment 30: - obsługa potwierdzania PLR w ramach transakcji SQL\', \'Comment 31: - obsługa konkurencyjności dla agregatu PLR\', \'Comment 32: - wprowadzenie statusu "ConfirmationPending" dla PLR\', \'Comment 33: - zmiana procesu potwierdzania PLR na zdarzeniowy.Poniżej dodaję zapytania SQL pomocne w analizie problemu.{code:java}SELECT *FROM DHPlantStockBusinessLogicMain.dbo.ProductionLots PJOIN DHPlantStockBusinessLogicMain.dbo.StockUnitReservations R ON P.Id = R.SourceDocumentIdWHERE P.ProductionLotStatus = 4ORDER BY P.StartDate DESC;{code}{code:java}SELECT AggregateId\', \'Comment 34: COUNT(CorrelationId) AS _Count\', "Comment 35: MAX(Created) AS _DateFROM DHPlantProdBusinessLogicEvents.dbo.ProductionLotsWHERE EventType LIKE \\\\\'%ProductionLotConfirmedEvent\\\\\'GROUP BY AggregateIdHAVING COUNT(CorrelationId) > 1ORDER BY MAX(Created) DESC;{code}{code:java}DECLARE @LotNumber NVARCHAR(100) = \\\\\'0881031122029\\\\\'DECLARE @ProductionId UNIQUEIDENTIFIER = (SELECT Id FROM DHPlantProdBusinessLogicMain.dbo.ProductionLots WHERE LotNumber = @LotNumber)DECLARE @StartDate DATETIME = (SELECT CONVERT(DATE", "Comment 36: StartDate) FROM DHPlantProdBusinessLogicMain.dbo.ProductionLots WHERE Id = @ProductionId);WITH Events AS( SELECT * FROM DHPlantProdBusinessLogicEvents.dbo.ProductionLots WHERE AggregateId = @ProductionId UNION ALL SELECT * FROM DHPlantStockBusinessLogicEvents.dbo.StockUnits E WHERE E.Created > @StartDate AND Event LIKE (\\\\\'%\\\\\' + @LotNumber + \\\\\'%\\\\\'))SELECT Created", \'Comment 37: CorrelationId\', \'Comment 38: UserName\', \'Comment 39: REPLACE(REPLACE(AggregateType\', "Comment 40: \\\\\'Plant.Prod.BusinessLogic.Domain.ProductionLots.Model.\\\\\'", "Comment 41: \\\\\'\\\\\')", "Comment 42: \\\\\'Plant.Stock.BusinessLogic.Domain.StockUnits.\\\\\'", "Comment 43: \\\\\'\\\\\') AS AggregateType", \'Comment 44: AggregateId\', \'Comment 45: REPLACE(REPLACE(EventType\', "Comment 46: \\\\\'Plant.Prod.BusinessLogic.DomainAbstractions.ProductionLots.DomainEvents.\\\\\'", "Comment 47: \\\\\'\\\\\')", "Comment 48: \\\\\'Plant.Stock.BusinessLogic.DomainAbstractions.StockUnits.\\\\\'", "Comment 49: \\\\\'\\\\\') AS EventType", "Comment 50: EventFROM Events EORDER BY E.Created;{code}\'", "Comment 51: \'Hello", "Comment 52: finally RCA was created for cause analysis DGS-8168.\'", "Comment 53: \'[~tomasz.nojek@kotrak.com] Nie udało mi się zreprodukować błędu. Gdy próbowałam równolegle potwierdzić ten sam PLR", "Comment 54: to jeden z nich się potwierdzał a na drugim pojawiał błąd o złym statusie PLRa. !confirmation! \'", "Comment 55: \'Hello,you can close this task", "Comment 56: thank you.\'", "Comment 57: \'Hi PiotrAs we have this RCA (DGS-8168).You can close this task.Thank you very much\']"]\nRelated Issues:\n[\'DGS-8168\', \'DGS-8102\', \'DGS-8184\', \'DGS-8185\', \'DAP-13157\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8086\n\n### Instruction:\nDOcuments are not synchroniing into erp, all plrs from yesterday are not showing in erp as job orders\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: \'Wszystkie z czwartku mają taki error:!image-2022-12-19-07-40-07-559.png!\'", "Comment 3: \'Timeout pojawiał się od 15 grudnia{code:java}Application: Evolution.ErpIntegrator.PlatformApplication Date: 12/18/2022 7:38:16 AM Id: 129686 Message: An error occurred while executing the command definition. See the inner exception for details. Source: EntityFramework StackTrace: System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out --- End of inner exception stack trace --- at System.Data.SqlClient.SqlConnection.OnError(SqlException exception", \'Comment 4: Boolean breakConnection\', \'Comment 5: Action`1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 6: Boolean breakConnection\', \'Comment 7: Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 8: Boolean callerHasConnectionLock\', \'Comment 9: Boolean asyncClose) at System.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 System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 15: RunBehavior runBehavior\', \'Comment 16: String resetOptionsString\', \'Comment 17: Boolean isInternal\', \'Comment 18: Boolean forDescribeParameterEncryption\', \'Comment 19: Boolean shouldCacheForAlwaysEncrypted) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 20: RunBehavior runBehavior\', \'Comment 21: Boolean returnStream\', \'Comment 22: Boolean async\', \'Comment 23: Int32 timeout\', \'Comment 24: Task& task\', \'Comment 25: Boolean asyncWrite\', \'Comment 26: Boolean inRetry\', \'Comment 27: SqlDataReader ds\', \'Comment 28: Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 29: RunBehavior runBehavior\', \'Comment 30: Boolean returnStream\', \'Comment 31: String method\', \'Comment 32: TaskCompletionSource`1 completion\', \'Comment 33: Int32 timeout\', \'Comment 34: Task& task\', \'Comment 35: Boolean& usedCache\', \'Comment 36: Boolean asyncWrite\', \'Comment 37: Boolean inRetry) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 38: RunBehavior runBehavior\', \'Comment 39: Boolean returnStream\', \'Comment 40: String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior\', \'Comment 41: 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.<Reader>b__c(DbCommand t\', \'Comment 42: DbCommandInterceptionContext`1 c) at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target\', \'Comment 43: Func`3 operation\', \'Comment 44: TInterceptionContext interceptionContext\', \'Comment 45: Action`3 executing\', \'Comment 46: Action`3 executed) at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command\', \'Comment 47: 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 48: CommandBehavior behavior) --- End of inner exception stack trace --- at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand\', \'Comment 49: CommandBehavior behavior) at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context\', \'Comment 50: ObjectParameterCollection parameterValues) at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__6() at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func\', \'Comment 51: IDbExecutionStrategy executionStrategy\', \'Comment 52: Boolean startLocalTransaction\', \'Comment 53: Boolean releaseConnectionOnSuccess) at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5() 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__0() at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at Evolution.ErpIntegrator.DHC.DHC30.Documents.VehicleTickets.VehicleTicketRepository.GetVehicleTickets(Boolean forProcessing\', "Comment 54: GuidObjectKey id) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\Evolution.ErpIntegrator.DHC.DHC30\\\\\\\\Documents\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketRepository.cs:line 275 at Evolution.ErpIntegrator.DHC.DHC30.Documents.VehicleTickets.VehicleTicketRepository.GetVehicleTicketsToSynchronization() in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\Evolution.ErpIntegrator.DHC.DHC30\\\\\\\\Documents\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketRepository.cs:line 108 at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor.OnExecute(Object data) at Evolution.ErpIntegrator.IntegrationLibrary.IntegrationTaskBase.Execute(Object data) at Evolution.ErpIntegrator.IntegrationLibrary.Integrator.Execute() at Evolution.ErpIntegrator.PlatformApplication.Application.TimerCallback(Object state){code}\'", "Comment 55: \'!image-2022-12-19-08-34-14-112.png!!image-2022-12-19-08-34-48-333.png!\'", "Comment 56: \'!image-2022-12-19-08-35-16-048.png!\'", "Comment 57: \'Hi,It should be fine now. If missing documents did not generate", \'Comment 58: please generate them again from application: first VT\', "Comment 59: then PLRs.!image-2022-12-19-09-08-50-112.png!Regards\'", "Comment 60: \'{color:#212121}Okay please close{color} ----\'", "Comment 61: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8085\n\n### Instruction:\nError id 6111032 start transfer 3\n\n### Response:\n["Comment 1: [\'Zgłoszenie w trakcie realizacji\'", "Comment 2: \'Please check", "Comment 3: for p46034 in database was a different item - id 19905.\'", "Comment 4: \' !screenshot-1! \'", "Comment 5: \'użyta procedura z[[DHP] Problem ze zbiornikiem", \'Comment 6: ciągłe czyszczenie\', "Comment 7: jeżdzą w kółko. Incorrect article.|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%20Problem%20ze%20zbiornikiem,%20ci%C4%85g%C5%82e%20czyszczenie,%20je%C5%BCdz%C4%85%20w%20k%C3%B3%C5%82ko&section-id=\\\\\\\\{CC5FB5C6-8E0D-42E5-8319-3DC0E80D8642}&page-id=\\\\\\\\{5BCB8D63-41B2-417C-B3C8-73B535158C20}&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%20Problem%20ze%20zbiornikiem%2C%20ci%C4%85g%C5%82e%20czyszczenie%2C%20je%C5%BCdz%C4%85%20w%20k%C3%B3%C5%82ko%7C5BCB8D63-41B2-417C-B3C8-73B535158C20%2F%29])\'", "Comment 8: \'Confirmed by teams", "Comment 9: the taskis closed.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8084\n\n### Instruction:\nWe want help in making our 2023 calender year on stock in ERP zero with no roll backs from 2022, so that we can have a true reflection of the stock count from december to be used in january. 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: "HelloIn ERP it is possible to close period of trade operations\', "Comment 3: it really means that you can\'t sell anything but also can not make any warehouse movement.So", \'Comment 4: if you are sure that you want to close 2022 year\', \'Comment 5: you can close December 2022 and make printout Stock on hand dated on ....- but to close December 2022 you must first close every earlier periods- month by month.Closing periods is possible in module Administrator -> Company -> Periods of trade operations !screenshot-1! "\', "Comment 6: \'which means if i close 2022 month by month in 2023 it will be fresh start?\'", \'Comment 7: \\\'This means that the system should not allow you to change documents in the old year or issue new ones. I don\\\\\\\'t know what you exactly mean by "fresh start"?\\\'\', "Comment 8: \'{color:#212121}Okay i understand. Please close{color} ----\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8083\n\n### Instruction:\nCodes 6051020 and 6051901 do not have BulkItemId in the database.\r\n\r\nFor this reason scanning in PCS system does not work properly.\r\n\r\nPlease update BulkItemId for those 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: \'!image-2022-12-19-09-22-55-529.png!\'", "Comment 3: \'Pleasecheck the items have been resent.Regards.\'", "Comment 4: \'The issue has been completed and is closed.Regards.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8082\n\n### Instruction:\nVT for intake was created (VT-379/12/22). VT is for ASN with 4 lines. ASN and VT show correct quantity for all lines in DHP. VT message has no quantity for last item. Because of this, message is not accepted in PCS.\r\nPlease check why the quantity is missing. This particular VT was processed manually by PCS supplier, plant informed us that the had similar cases. \r\n\r\nNote that this VT has multiple lines. \r\nPerhaps that is related to this issue.\r\n\r\nExpected: on loadLineNumber 4: estimatedQuantity: 6000Kg. Message contains: 0Kg\r\n\r\n{\r\n\t\t\t"vehicleTicketNumber": "VT-379/12/22",\r\n\t\t\t"asnNumber": "CL000010522",\r\n\t\t\t"status": 1,\r\n\t\t\t"realisationDate": "2022-12-19T02:00:00.0000000+01:00",\r\n\t\t\t"forwarderCode": "HEU",\r\n\t\t\t"forwarderName": "HEU",\r\n\t\t\t"plantId": 4,\r\n\t\t\t"vehiclePlateNumber": "TRUCK",\r\n\t\t\t"vehicleTicketLines": [\r\n\t\t\t\t{\r\n\t\t\t\t\t"loadLineNumber": 1,\r\n\t\t\t\t\t"articleCode": "0769",\r\n\t\t\t\t\t"articleName": "PX LEG-ZC 0.25%",\r\n\t\t\t\t\t"packingForm": "BLK",\r\n\t\t\t\t\t"itemBaseWeight": 0.0,\r\n\t\t\t\t\t"itemBaseWeightUnit": "kg",\r\n\t\t\t\t\t"supplierCode": "L004239",\r\n\t\t\t\t\t"supplierName": "De Heus Premix BV",\r\n\t\t\t\t\t"estimatedQuantity": 8000.0,\r\n\t\t\t\t\t"estimatedQuantityUnit": "kg",\r\n\t\t\t\t\t"deliveryId": 18429,\r\n\t\t\t\t\t"countryOfOrigin": "*"\r\n\t\t\t\t},\r\n\t\t\t\t{\r\n\t\t\t\t\t"loadLineNumber": 2,\r\n\t\t\t\t\t"articleCode": "0777",\r\n\t\t\t\t\t"articleName": "PX LAYERS 0.1%",\r\n\t\t\t\t\t"packingForm": "BLK",\r\n\t\t\t\t\t"itemBaseWeight": 0.0,\r\n\t\t\t\t\t"itemBaseWeightUnit": "kg",\r\n\t\t\t\t\t"supplierCode": "L004239",\r\n\t\t\t\t\t"supplierName": "De Heus Premix BV",\r\n\t\t\t\t\t"estimatedQuantity": 10000.0,\r\n\t\t\t\t\t"estimatedQuantityUnit": "kg",\r\n\t\t\t\t\t"deliveryId": 18430,\r\n\t\t\t\t\t"countryOfOrigin": "*"\r\n\t\t\t\t},\r\n\t\t\t\t{\r\n\t\t\t\t\t"loadLineNumber": 3,\r\n\t\t\t\t\t"articleCode": "0672",\r\n\t\t\t\t\t"articleName": "PX VIT E 40.000",\r\n\t\t\t\t\t"packingForm": "BLK",\r\n\t\t\t\t\t"itemBaseWeight": 0.0,\r\n\t\t\t\t\t"itemBaseWeightUnit": "kg",\r\n\t\t\t\t\t"supplierCode": "L004239",\r\n\t\t\t\t\t"supplierName": "De Heus Premix BV",\r\n\t\t\t\t\t"estimatedQuantity": 7000.0,\r\n\t\t\t\t\t"estimatedQuantityUnit": "kg",\r\n\t\t\t\t\t"deliveryId": 18431,\r\n\t\t\t\t\t"countryOfOrigin": "*"\r\n\t\t\t\t},\r\n\t\t\t\t{\r\n\t\t\t\t\t"loadLineNumber": 4,\r\n\t\t\t\t\t"articleCode": "0695",\r\n\t\t\t\t\t"articleName": "PX VITEXTRA-CO .5%",\r\n\t\t\t\t\t"packingForm": "BLK",\r\n\t\t\t\t\t"itemBaseWeight": 0.0,\r\n\t\t\t\t\t"itemBaseWeightUnit": "kg",\r\n\t\t\t\t\t"supplierCode": "L004239",\r\n\t\t\t\t\t"supplierName": "De Heus Premix BV",\r\n\t\t\t\t\t"estimatedQuantity": 0.0,\r\n\t\t\t\t\t"estimatedQuantityUnit": "kg",\r\n\t\t\t\t\t"deliveryId": 18432,\r\n\t\t\t\t\t"countryOfOrigin": "*"\r\n\t\t\t\t}\r\n\t\t\t]\r\n\t\t}\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! {code:java} select * FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketBulkIntakeElements] -- where VehicleTickets=\\\'2E1DC5A6-1F17-4D19-84A8-18B47167203D\\\' where InternalSerialNumber like \\\'VT-379/12/22%\\\'{code} !screenshot-2! "\', \'Comment 3: \\\'{code:java}SELECT TOP (1000) [Id] ,[Created] ,[Event] ,[EventType] ,[UserName] FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets] FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets] where AggregateId=\\\\\\\'2E1DC5A6-1F17-4D19-84A8-18B47167203D\\\\\\\' and EventType=\\\\\\\'Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketBulkIntakeFinalWeighingPerformedEvent\\\\\\\' and event like \\\\\\\'%"No":4%\\\\\\\' order by created{code}\\\'\', "Comment 4: \'Final weight information for element 4 came from pcs.What you can see below and in the VC module. !screenshot-4! !image-2022-12-20-14-12-59-154!\'", "Comment 5: \'PCS supplier manually updated the quantity so that intake could be completed. However", \'Comment 6: that is not the solution.On 20-12 again we had a VT with quantity 0: VT-461/12/22Same case: multiple lines\', \'Comment 7: last line has qty 0.\\\\t\\\\t{\\\\t\\\\t\\\\t"vehicleTicketNumber": "VT-461/12/22",\\\\t\\\\t\\\\t"asnNumber": "CL000010495",\\\\t\\\\t\\\\t"status": 1,\\\\t\\\\t\\\\t"realisationDate": "2022-12-21T02:00:00.0000000+01:00",\\\\t\\\\t\\\\t"forwarderCode": "HEU",\\\\t\\\\t\\\\t"forwarderName": "HEU",\\\\t\\\\t\\\\t"plantId": 4,\\\\t\\\\t\\\\t"vehiclePlateNumber": "TRUCK",\\\\t\\\\t\\\\t"vehicleTicketLines": [\\\\t\\\\t\\\\t\\\\t{\\\\t\\\\t\\\\t\\\\t\\\\t"loadLineNumber": 1,\\\\t\\\\t\\\\t\\\\t\\\\t"articleCode": "0791",\\\\t\\\\t\\\\t\\\\t\\\\t"articleName": "PX BREEDR1 0.1%",\\\\t\\\\t\\\\t\\\\t\\\\t"packingForm": "BB",\\\\t\\\\t\\\\t\\\\t\\\\t"itemBaseWeight": 0.0,\\\\t\\\\t\\\\t\\\\t\\\\t"itemBaseWeightUnit": "kg",\\\\t\\\\t\\\\t\\\\t\\\\t"supplierCode": "L004239",\\\\t\\\\t\\\\t\\\\t\\\\t"supplierName": "De Heus Premix BV",\\\\t\\\\t\\\\t\\\\t\\\\t"estimatedQuantity": 8000.0,\\\\t\\\\t\\\\t\\\\t\\\\t"estimatedQuantityUnit": "kg",\\\\t\\\\t\\\\t\\\\t\\\\t"deliveryId": 18541,\\\\t\\\\t\\\\t\\\\t\\\\t"countryOfOrigin": "*"\\\\t\\\\t\\\\t\\\\t},\\\\t\\\\t\\\\t\\\\t{\\\\t\\\\t\\\\t\\\\t\\\\t"loadLineNumber": 2,\\\\t\\\\t\\\\t\\\\t\\\\t"articleCode": "0774",\\\\t\\\\t\\\\t\\\\t\\\\t"articleName": "PX SLF-ORG-MIN 0,25%",\\\\t\\\\t\\\\t\\\\t\\\\t"packingForm": "25 KG",\\\\t\\\\t\\\\t\\\\t\\\\t"itemBaseWeight": 0.0,\\\\t\\\\t\\\\t\\\\t\\\\t"itemBaseWeightUnit": "kg",\\\\t\\\\t\\\\t\\\\t\\\\t"supplierCode": "L004239",\\\\t\\\\t\\\\t\\\\t\\\\t"supplierName": "De Heus Premix BV",\\\\t\\\\t\\\\t\\\\t\\\\t"estimatedQuantity": 2000.0,\\\\t\\\\t\\\\t\\\\t\\\\t"estimatedQuantityUnit": "kg",\\\\t\\\\t\\\\t\\\\t\\\\t"deliveryId": 18542,\\\\t\\\\t\\\\t\\\\t\\\\t"countryOfOrigin": "*"\\\\t\\\\t\\\\t\\\\t},\\\\t\\\\t\\\\t\\\\t{\\\\t\\\\t\\\\t\\\\t\\\\t"loadLineNumber": 3,\\\\t\\\\t\\\\t\\\\t\\\\t"articleCode": "0778",\\\\t\\\\t\\\\t\\\\t\\\\t"articleName": "PX BROSUPP EXP 0.1%",\\\\t\\\\t\\\\t\\\\t\\\\t"packingForm": "BB",\\\\t\\\\t\\\\t\\\\t\\\\t"itemBaseWeight": 0.0,\\\\t\\\\t\\\\t\\\\t\\\\t"itemBaseWeightUnit": "kg",\\\\t\\\\t\\\\t\\\\t\\\\t"supplierCode": "L004239",\\\\t\\\\t\\\\t\\\\t\\\\t"supplierName": "De Heus Premix BV",\\\\t\\\\t\\\\t\\\\t\\\\t"estimatedQuantity": 8000.0,\\\\t\\\\t\\\\t\\\\t\\\\t"estimatedQuantityUnit": "kg",\\\\t\\\\t\\\\t\\\\t\\\\t"deliveryId": 18543,\\\\t\\\\t\\\\t\\\\t\\\\t"countryOfOrigin": "*"\\\\t\\\\t\\\\t\\\\t},\\\\t\\\\t\\\\t\\\\t{\\\\t\\\\t\\\\t\\\\t\\\\t"loadLineNumber": 4,\\\\t\\\\t\\\\t\\\\t\\\\t"articleCode": "0674",\\\\t\\\\t\\\\t\\\\t\\\\t"articleName": "PX VIT HYD-MIX 0,1%",\\\\t\\\\t\\\\t\\\\t\\\\t"packingForm": "BB",\\\\t\\\\t\\\\t\\\\t\\\\t"itemBaseWeight": 0.0,\\\\t\\\\t\\\\t\\\\t\\\\t"itemBaseWeightUnit": "kg",\\\\t\\\\t\\\\t\\\\t\\\\t"supplierCode": "L004239",\\\\t\\\\t\\\\t\\\\t\\\\t"supplierName": "De Heus Premix BV",\\\\t\\\\t\\\\t\\\\t\\\\t"estimatedQuantity": 0.0,\\\\t\\\\t\\\\t\\\\t\\\\t"estimatedQuantityUnit": "kg",\\\\t\\\\t\\\\t\\\\t\\\\t"deliveryId": 18544,\\\\t\\\\t\\\\t\\\\t\\\\t"countryOfOrigin": "*"\\\\t\\\\t\\\\t\\\\t}\\\\t\\\\t\\\\t]\\\\t\\\\t}\\\'\', \'Comment 8: \\\'mam dla dwóch przypadków EventType=\\\\\\\'Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketBulkIntakeFinalWeighingPerformedEvent\\\\\\\' dla pozycji po 0. jak niżej{code:java} select event,eventtype,username FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets] where AggregateId=\\\\\\\'2E1DC5A6-1F17-4D19-84A8-18B47167203D\\\\\\\' and EventType=\\\\\\\'Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketBulkIntakeFinalWeighingPerformedEvent\\\\\\\'-- and event like \\\\\\\'%"No":4%\\\\\\\' order by created select event,eventtype,username FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets] where AggregateId=\\\\\\\'B0728B49-D06D-4223-A511-5396660CF55A\\\\\\\' and EventType=\\\\\\\'Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketBulkIntakeFinalWeighingPerformedEvent\\\\\\\'-- and event like \\\\\\\'%"No":4%\\\\\\\' order by created{code} !screenshot-6! \\\'\', \'Comment 9: "Isn\\\'t this the same issue as in the DHITS-611?"\', \'Comment 10: "{color:#000000}In this case I do not see that VT was sent a second time. And situation only seems to occur for VT\\\'s with multiple lines.{color} {color:#000000}{color} {color:#000000} {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black} Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Piotr Gaczorek (Jira) <jira@kotrak.com> *Sent:* Thursday\', \'Comment 11: December 22\', \'Comment 12: 2022 3:33 PM *To:* Kennedy\', \'Comment 13: Bob <BKennedy@deheus.com> *Subject:* DGS-8082 VT for intake does not contain quantity for one of the lines{color} |{color:#ffffff} 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 14: \'Analogicznie do:https://helpdesk.kotrak.com/browse/DAP-13104?focusedCommentId=1068405&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1068405\'", "Comment 15: \'Hello", "Comment 16: this issue has been fixed in version 8.5.Can we close this ticket?\'", "Comment 17: \'This ticket can be closed.\']"]\nRelated Issues:\n[\'DAP-13104\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8081\n\n### Instruction:\nHello all,\r\n\r\nWe want to improve a process in NAS. When build it can be rolled out our other administrations when needed.\r\n\r\nImprovement NAS – deposits\r\n•\tWe do not want to use Kofax (now we are creating invoices ourselves and scan them with Kofax)\r\n•\tWe want the possibility to copy registration sales invoices that are booked on an specific NAS round now VERG. Creation of a new item code, specific for this type of posting: item code VNAS\r\n\r\nStart of this process must be something like this: \r\no\t1. From out the Round select the Registration Sale document and drill down to this document (double click). \r\no\t2. Copy this document by clicking the <Action> button and choose <copy this document>.\r\no\t3. Automatically I come into the created document where I can adjust the document on header level and also on line level.\r\no\t4. Create Purchase Regular invoice and adjust what is needed on header level and line level. = standard procedure.\r\no\t5. Send the Purchase invoice into the workflow for approval (Archive) = standard procedure.\r\no\t6. Return to the created SI document and send this one into the approval flow (Archive) = standard procedure.\r\no\t7. Return to the source SI registered document and close.\r\no\t8. Return to the Round. Where the proces initially started.\r\no\tEND.\r\n\r\n•\tAdditional requirments below:\r\n•\tThe information on the invoice lines should be copied, but we need to be able to adjust the invoice lines.\r\n•\tThe invoice date of the document should be the day of today, the delivery date can be copied from the original document. The due date should be the invoice date +1. Data like supplier, invoice type, reference and full number should be copied as well.\r\n•\tA regular purchase invoice should be created in the background at the same time the registration sales invoice is copied from the round. All data except the invoice and due date need to be copied as well. The SI and PI need to be linked the same way as whenever they were created manually.\r\n•\tPurchase invoices with the item code VNAS should always be considered as self-billing, although we will select a L-number as Supplier. The L-number that is used in the communication with Milas should be the L-number of the delivery customer (and not the invoice customer)\r\n•\tBert and Christine should be able to move the created invoices to another round (of the same customer)\r\n•\tYou could have a look at SI-RTN/2022/0132 (ID57946) and the linked PI document as a reference of how we do it right now.\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: \'Do wewnętrznego podsumowania.\'", "Comment 3: \'linked toDHNLC-691Waititng for Mitch\'", "Comment 4: \'Hi @MitchHi [~CJong@deheus.com]I have some questions I want to clarify before we start working on that topic.As I understand from above", \'Comment 5: the process for invoicing the VNAS item (in NAS) starts from SI registration\', \'Comment 6: from which PI regular is created. It means that we want to see in Round SI Registration\', "Comment 7: but at the same time we need to have a PI Regular linked to this SI. PI is not to be presented in Round. None of these invoices will be listed in S2P. Could you confirm that is correct?!image-2023-01-09-16-11-07-299.png!\'", "Comment 8: \'We divide this task to 2 steps. 1st step is ready for UAT tests.After confirmation that it\\\\\'s correct", \'Comment 9: we can start adjusting 2nd part of the task\', \'Comment 10: so points1-5 are ready for UAT tests:*1st part of task*{quote}1. Add a new tab in Round document <Vergoeding> (like Expenses) * SI REGULAR with VNAS item code (and corrections)- new relation is added to the Relation Table in NAS (AD column)2. Add new section (lists like Expenses) "Vergoeding" in Financial Statement document form (the same data is to be displayed as described on point 2): * General * Details3. Addnew section "Vergoeding" to the printout Financial Statement printout4. Add the invoicesSI REGULAR with VNAS item code (if not corrected by CSI) to S2P document and saldo calculation5. Add the invoicesSI REGULAR with VNAS item code (if not corrected by CSI) to S2P printout{quote}*2nd part of task:*NAS - new process:to do: # Add the possibility to copy the SI Regular (VNAS) and PI Regular (linked to SI) from a Round. It should be possible to double click in the VNAS item in Round (the system opens the SI) and create copies of the VNAS invoices by lightening action "Create copies of VNAS SI and PI". # The system should open both generated documents SI and below PI. The user can adjust data in these invoices!image-2023-01-16-11-45-12-739.png! Data in the copied invoices: - document date - generation date - delivery date - to be copied from the original invoice -the due date should be the invoice date +1. - it should be possible to change the round number (only for round related to the farmer from SI/PI) !image-2023-01-16-11-45-26-847.png!!image-2023-01-16-11-45-12-739! !image-2023-01-16-11-45-26-847!\\\'\', "Comment 11: \'Part 1 is approved.\'", "Comment 12: \'What is the status of part 2?\'", "Comment 13: \'[~mbovene@deheus.com]we are in progress.\'", \'Comment 14: \\\'[~mbovene@deheus.com],we have done part 2. You can feel free to test new funtionality.Creation copy for SI and PI is attached on SI document with VNAS element:!image-2023-01-27-11-08-29-220.png!I have one more question about view on Round expenses table:!image-2023-01-27-11-23-22-890.png!We need to exclude VNAS invoice positions from "Expenses" on Round?Best regards\', "Comment 15: Grzegorz!image-2023-01-27-11-23-22-890!\'", \'Comment 16: "Hi [~mbovene@deheus.com],Hi[~CJong@deheus.com],Please review redesign of functionality and add some remarks if it\\\'s needed or confirm that this is correct.There is summary of adjustments needed after our today meeting. * Relation tableThere process should looks like that: Purchase Invoice -> Sales InvoiceFirst should be created Purchase Invoice\', "Comment 17: then from PI should be created Sales Invoice.Only Sales invoices should be included on Round and Financial statement. !image-2023-02-01-14-23-29-141.png!We need to add new values \'Vergoeding\' to dictionaries:!image-2023-02-01-14-17-26-832.png! * Item Group * Round Category * Relation Table for Round - there should be added relations for: ** Customer", \'Comment 18: Farmer,Vergoeding,Vergoeding ** Vendor\', "Comment 19: Farmer,Vergoeding,Vergoeding!image-2023-02-01-14-17-13-579.png!Item VNAS should be properly parrametrized (otherwise on invoice line values for \'Default round category\' and \'Round category\' won\'t be set with correct values): * Item Group = \'Vergoeding\' * Possible Round Categories = \'Vergoeding\' !image-2023-02-01-14-10-26-552.png! * Purchase Invoice documents list:There will be new list of documents (defined list) which will contain elements of Purchase Invoices with items = \'VNAS\' - important column for this list is: Description from document elements. These invoices will have only one line with Item = \'VNAS\'!image-2023-02-01-14-29-13-026.png!From the list it will be possible to select multiple invoices on list", "Comment 20: then from the ligtning button execute action - \'Create copies of VNAS PI and SI\' for all selected PI\'s.For each PI will be created: * Copy of PI * Copy of SI (connected to source PI by Leading doc)Documents will be created in background in inbox of user who execute action and it will be possible to change data on documents (for example Description on invoice elements)For exapmle: If there will be 10 selected PI documents from this list", \'Comment 21: action will generate 10 copies of PI and 10 copies of SI documents.Access to this list should have: Christine and Bert (for now)"\', "Comment 22: \'{color:black}Good morning Damian,{color} {color:black}{color} {color:black}Please continue this development.{color} {color:black}It is a correct approach of our meeting yesterday!{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) <[jira@kotrak.com|mailto:jira@kotrak.com]> *Verzonden:* woensdag 1 februari 2023 14:42 *Aan:* Jong", "Comment 23: Christine de <[CJong@deheus.com|mailto:CJong@deheus.com]> *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG) | *{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!!image007!!image008!!image009!!image010!\'", "Comment 24: \'Dodano listę z PI w NAS:!image-2023-02-02-14-56-34-871.png!Pod prawym przyciskiem myszy na danej fakturze - możliwość generacji:!image-2023-02-02-14-57-07-372.png!Generacja kopiuje pierwsze PI i podnosi je do edycji (z możliwością wykonania przepływu)", "Comment 25: kolejno SI.Do przetestowania przez klienta z uwzględnieniem informacji o których rozmawialiśmy.\'", \'Comment 26: "Could we meet to review how we changed it right now and verify wheter it will be ok for your needs and discuss other details of this functionality?Please let me know if you have time tomorrow or any other day and I will show you our changes so far. I can also record some short video if you want to show how it could works.We\\\'ve made some changes\', \'Comment 27: but we had to modified functionality of copying PI and SI due to technical limitations of Intense. We cannot use multiply selecting documents and make copy all of documents (PI and SI) by one clik. It would be possible to do it with 2 steps (1st: multiple select on PI list and create PI copies\', \'Comment 28: 2nd:multiple select on PI list and create SI copies)\', \'Comment 29: but this solution when we discuss about it\', "Comment 30: it\'s not so comfortable.We\'ve made some different solution right now which seems better to handle this process of creating invoices.In summary: * There is a list of PI documents with \'VNAS\' item * Action from lighnitng is executed for 1 document PI (we don\'t select multiple documents) ** copy of PI is generated and it\'s open on screen", "Comment 31: then you can change needed fields and also make a flow for the document ** copy of SI is generated and it\'s open on screen", \'Comment 32: then you can change needed fields and also make a flow for the documentIn this case it will be done for 1 document\', \'Comment 33: but you can handle whole process: copy of invoices\', \'Comment 34: change values\', \'Comment 35: make a flowsThen it\\\'s not needed to go again to all documents and make some changes."\', "Comment 36: \'Do wysłania info jak obecnie jest to skonfigurowane na bazie testowej\'", \'Comment 37: "We\\\'ve discussed internally this solution and made partly changes of this functionality. How it can works right now: # From defined list you are able to select multiple Purchase Invoices # Then you can select action from Lightning button # Copy of all selected documents are created - (PI -> new PI\', \'Comment 38: SI (based on PI Leading doc) -> new SI)There is an attachment with video where you can see how works this part of functionality.[^VNAS.wmv]If it is good way to handle process we can start with further part of solution with extended the process of sending invoices to Archive (we discussed about it last time that it could be 2 processes for invoices which are modified and for this which are a copy 1 to 1 from old document and could be send to Archive without any Approval flow).We can plan a meeting again and discuss about solution which will be best suited to your needs."\', "Comment 39: \'{color:black}Good morning Damian,{color} {color:black}{color} {color:black}{color} {color:black}Thanks for your input and development to this process adjustment.{color} {color:black}Last Thursday we tested and discuss this modification. The tab/button shows the information we need for this action.{color} # {color:black} How does the system recognize that a posting which is not modified can be archived at once.{color} {color:black}Maybe it is a good approach that when a modification/new document should be made we create one as usual{color} {color:black}à{color}{color:black} regular PI.{color} # {color:black} After action", \'Comment 40: these documents should go to the inbox of the action taker à not administrator.{color} {color:black}At first Bert Geijtenbeek and Christine de Jong should be able to create these.{color} # {color:black} Are only the documents visible which were created last month or is this only with a filter?{color}# {color:black} These criteria were not clear in our test The red text we missed:{color} |{color:black} Purchase Invoice Number{color} | = To be generared automatically | |{color:black} Invoice date{color} | = TODAY | |{color:black} Delivery date{color} |{color:red} = TODAY{color} | |{color:black} Due date{color} |{color:red} = TODAY + 1{color} | |{color:black} External Document Number{color} |{color:red} = To be generared automatically\', \'Comment 41: dynamic (source document + 1){color} | |{color:black} {color} |{color:red} {color} | {color:black}Awaiting your feedback\', \'Comment 42: so we can test again.{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) <jira@kotrak.com> *Verzonden:* maandag 13 februari 2023 16:03 *Aan:* Jong\', "Comment 43: Christine de <CJong@deheus.com> *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG) | *{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.gif!\'", \'Comment 44: "Hello Christine,Below my remarks.{quote}{color:#000000}Last Thursday we tested and discuss this modification. The tab/button shows the information we need for this action.{color} # {color:#000000}How does the system recognize that a posting which is not modified can be archived at once.{color}{quote}{color:#000000}We don\\\'t have any good moment or field when we know that document should be modified or not. I think the best solution for now is to decide by user that this document should be modified or not and decide which invoices should go to \\\'Archive\\\' directly without \\\'Waiting for Approval\\\' flow.{color}{color:#000000}After creating many documents we\\\'re not able to know how these documents should be treated.{color}{quote}{color:#000000}Maybe it is a good approach that when a modification/new document should be made we create one as usual{color}{color:#000000}à{color}{color:#000000}regular PI.{color} # {color:#000000}After action\', "Comment 45: these documents should go to the inbox of the action taker à not administrator.{color}{quote}All of Purchase invoices copied in this process should be created as a \'Regular\' type of purchase? Is it something which we should set by default for these invoices (even if the old PI was different than \'Regular\')?Ok", "Comment 46: we will verify these and invoices will be created in inbox of user who launched this action.{quote}{color:#000000}At first Bert Geijtenbeek and Christine de Jong should be able to create these.{color} # {color:#000000}Are only the documents visible which were created last month or is this only with a filter?{color}{quote}{color:#000000}We will add permission to this list also to Bert.{color}{color:#000000}Now on Purchase Invoice (VNAS) list there are all PI invoices with item = \'VNAS\'. You can filter it on tjhe list by document date or other fields from invoices. We can also add some conditions and show only specify invoices if it will be needed.{color}{quote} # {color:#000000}These criteria were not clear in our test The red text we missed:{color}|{color:#000000}Purchase Invoice Number{color}|= To be generared automatically||{color:#000000}Invoice date{color}|= TODAY||{color:#000000}Delivery date{color}|{color:#FF0000}= TODAY{color}||{color:#000000}Due date{color}|{color:#FF0000}= TODAY + 1{color}||{color:#000000}External Document Number{color}|{color:#FF0000}= To be generared automatically", \'Comment 47: dynamic (source document + 1){color}||{color:#000000}{color}|{color:#FF0000}{color}|{color:#000000}Awaiting your feedback\', \'Comment 48: so we can test again.{color}{quote}{color:#000000}Ok\', "Comment 49: we will change \'Delivery date\' and \'Due date\' calculations like above.{color}{color:#000000}For \'External Document Number\' - this field it\'s not only numeric as I saw in database", "Comment 50: so there are also values with text. It couldn\'t be possible to add + 1 number to all fields if there will be some letter? Maybe we should add some letter/sign at the end of old number? It should be unique for Milas", \'Comment 51: right? Milas won\\\'t accept 2 invoices with the same \\\'External Document Number\\\'{color}"\', "Comment 52: \'[~damian.swistek@kotrak.com],dodałem pole na SI i PI w NAS - Doc_IntColumn40 - gdzie wrzucamy 1 przy generowaniu.Daty uzupełnione.Pozdrawiam", "Comment 53: Grzegorz\'", "Comment 54: \'Hi Damian", \'Comment 55: # {color:black} Maybe it is a good approach to only use the copy button when a document should be copied.{color}# {color:black} In case of modification I will make a regular posting à Regular PI / SI. This is a manual action\', \'Comment 56: already in Intense. No copy button used here.{color} {color:black}I think that this we’ll have the least impact for you in developing this new functionality.{color} # {color:black} In our external documentnumber we need to have a month notification.{color} {color:black}That’s why we now use 2023/1-02.. 2023/1-03 etc.{color} {color:black}When we change this to letters it will not be clear for our customers which month is compensated. Also\', \'Comment 57: when we make the closure of the rounds things can be mixed up.{color} {color:black}Mitch came up with the brilliant idea that if we change the letter of the purchase to a number\', \'Comment 58: are you then able to{color} {color:red}= To be generared automatically\', \'Comment 59: dynamic (source document + 1){color}{color:black}{color} {color:black}{color} {color:black}Thanks for your feedback.{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) <jira@kotrak.com> *Verzonden:* maandag 20 februari 2023 12:39 *Aan:* Jong\', "Comment 60: Christine de <CJong@deheus.com> *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG) \'", \'Comment 61: "{quote}{color:#000000}1. Maybe it is a good approach to only use the copy button when a document should be copied.{color}{quote}{color:#4c9aff}Do you mean to use in this case action as it is on IBIP_DH_TEST right now?{color}{color:#000000}!image-2023-02-27-10-50-57-302.png!{color}{quote}{color:#000000}2. In case of modification I will make a regular posting à Regular PI / SI. This is a manual action\', \'Comment 62: already in Intense. No copy button used here.{color}{quote}{color:#4c9aff}Which action do you mean in this case? Manually creating PI and SI\', \'Comment 63: not copying documents by action from point above?{color}{quote}{color:#000000}1. In our external documentnumber we need to have a month notification.{color}{color:#000000}That’s why we now use 2023/1-02.. 2023/1-03 etc.{color}{color:#000000}When we change this to letters it will not be clear for our customers which month is compensated. Also\', \'Comment 64: when we make the closure of the rounds things can be mixed up.{color}{color:#000000}Mitch came up with the brilliant idea that if we change the letter of the purchase to a number\', \'Comment 65: are you then able to{color}{color:#FF0000}= To be generared automatically\', \'Comment 66: dynamic (source document + 1){color}{quote}{color:#4c9aff}I\\\'m not sure that i good understand it.{color}{color:#4c9aff}Do you mean that there will be always a number in field \\\'External Document Number\\\'? And then will be for example 20230102 and we should calculate it when there will be a copy of this PI and put number for new PI number 20230103 (20230102 + 1) ? Or do you refer to other number?{color}{color:#000000}!image-2023-02-27-11-30-15-576.png!{color}{color:#000000}Regards{color}"\', "Comment 67: \'1. Yes you are right.2. Yes", \'Comment 68: also correct. In that case we will only copy documents which 100% identical (in step 1\', \'Comment 69: except the dates and external document number)1. Yes\', \'Comment 70: we can agree with your proposal. For example 20230102 and we should calculate it when there will be a copy of this PI and put number for new PI number 20230103 (20230102 + 1).Next to this we would like to use the field "Description on the header" to indicate the month of compensation. This can be only a number like 1 for January\', "Comment 71: 2 for February etc. Could we do a +1 to this field when we copy the previous document?\'", "Comment 72: \'{quote}2. Yes", \'Comment 73: also correct. In that case we will only copy documents which 100% identical (in step 1\', \'Comment 74: except the dates and external document number){quote}In this case documents will be created manually by already existing functionality\', "Comment 75: right?How \\\\\'External Document Number\\\\\' field should be calculated on new document (when it\\\\\'s copying by functionality \\\\\'Create copied VNAS SI and PI\\\\\' for identical documents)?There are examples from database", \'Comment 76: there are sometimes values like these:01VF009316,101529/9-3-2022 2022/11-00004\', \'Comment 77: then we\\\\\\\'re not able to add +1 to this values when it\\\\\\\'s a text or other characters between numbers.{quote}Next to this we would like to use the field "Description on the header" to indicate the month of compensation. This can be only a number like 1 for January\', "Comment 78: 2 for February etc. Could we do a +1 to this field when we copy the previous document?{quote}Maybe it\\\\\'s better to add new number field (to avoid letters or any other characters) which will be filled only by numbers. We can calculate this number when document will be copying", \'Comment 79: but what should be range of this values (do we need a calculating like month - from 1 to 12\', "Comment 80: or it could be continuous). It\\\\\'s also option to calculate this value from other field (from invoice date - we can take proper month from this date and fill in this field).Where this field should appears? it should be visible on Purchase Invoice list of VNAS document? It will be better when this field will be numeric only", "Comment 81: then we can be sure that we\\\\\'re able to calculate it properly (when it\\\\\'s a text field we don\\\\\'t know what will be in this field).\'", \'Comment 82: "Hi [~CJong@deheus.com],Could you confirm/add some remarks to this summary of meeting below: * External Document Number should be calculated and created from other data and should looks like that *803319/A/2023/02* ** 803319 - Code from Reference ** A - manually added symbol\', "Comment 83: copying when coument is copying by action ** 2023 - year - taken from current date of invoicing (date from creation date of document) ** 02 - month- taken from current date of invoicing (date from creation date of document)Main rules for these calculation for External Document Number will be always unique ** document will be created in month of real creation of it ** document will be created once per month for this type of invoice!image-2023-03-06-12-12-04-129.png! * Should be created new flows for documents which are copying 1:1 - without changes in data on invoices (for PI and SI documents) ** should be possible to perform flow from \'Entry\' to \'Archive\' directly without approval flow ** this flow should only appear for documents which are copied by functionality\'Create copied VNAS SI and PI\'", \'Comment 84: for other documents (not created by this action - \\\'Create copied VNAS SI and PI\\\' - flow from \\\'Entry\\\' to \\\'Archive\\\' shouln\\\'t be available"\', \'Comment 85: "CONFIRMED - External Document Number should be calculated and created from other data and should looks like that 803319/A/2023/02803319 - Code from ReferenceA - manually added symbol\', "Comment 86: copying when coument is copying by action2023 - year - taken from current date of invoicing (date from creation date of document)02 - month - taken from current date of invoicing (date from creation date of document)Main rules for these calculation for External Document Number will be always uniqueCONFIRMEDdocument will be created in month of real creation of itdocument will be created once per month for this type of invoiceCONFIRMEDShould be created new flows for documents which are copying 1:1 - without changes in data on invoices (for PI and SI documents)should be possible to perform flow from \'Entry\' to \'Archive\' directly without approval flowthis flow should only appear for documents which are copied by functionality \'Create copied VNAS SI and PI\'", \'Comment 87: for other documents (not created by this action - \\\'Create copied VNAS SI and PI\\\' - flow from \\\'Entry\\\' to \\\'Archive\\\' shouln\\\'t be available"\', "Comment 88: \'{color:black}Good day,{color} {color:black}{color} {color:black}We have an adaptation in our process requirement.{color} {color:black}It should be regular PI to registered SI.{color} # {color:#172B4D} This is WRONG: Copy of all selected documents are created - (PI -> new PI", \'Comment 89: SI (based on PI Leading doc) -> new SI){color} {color:#172B4D}GOOD: PI -> new PI (regular)\', \'Comment 90: SI (based on PI Leading doc) -> new SI (registered){color} {color:black}Please confirm if this is clear.{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:* Mitch van Bovene (Jira) <jira@kotrak.com> *Verzonden:* dinsdag 7 maart 2023 13:11 *Aan:* Jong\', "Comment 91: Christine de <CJong@deheus.com> *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG) \'", \'Comment 92: "Ok\', \'Comment 93: so for each document which will be copied by action\\\'Create copied VNAS SI and PI\\\' (copy 1:1 - without changes in data on invoices) it should be created PI regular (copy of old PI regular with calculated fields) and then it should be created SI registered."\', "Comment 94: \'Indeed.\'", "Comment 95: \'{color:black}Dear Damian,{color} {color:black}{color} {color:black}What is the status of this project? We would like to make a full test before implementation.{color} {color:black}{color} {color:black}Furthermore", \'Comment 96: our financial management has decided that process of booking should be regular{color} {color:black}à{color}{color:black} regular as per 01-04-2023.{color} {color:black}Relations for this booking change will be set by the project managers. We think that this should not have implications for Intense. As my posting will be from 01-04-2023 regular{color} {color:black}à{color}{color:black} regular. When I make a copy of this in the VNAS\', \'Comment 97: system will pick-up.{color} {color:black}Can you confirm this thought?{color} {color:black}{color} {color:black}Thanks for your feedback.{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) <jira@kotrak.com> *Verzonden:* vrijdag 10 maart 2023 13:26 *Aan:* Jong\', "Comment 98: Christine de <CJong@deheus.com> *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG) \'", \'Comment 99: "Hi Christine,Unfortunately due to other urgent topics we didn\\\'t make much progress in this topic.We\\\'ll try to do this as soon as possible and I\\\'ll let you know when it will be ready for another tests.{quote}{color:#000000}Furthermore\', \'Comment 100: our financial management has decided that process of booking should be regular{color}{color:#000000}à{color}{color:#000000}regular as per 01-04-2023.{color}{color:#000000}Relations for this booking change will be set by the project managers. We think that this should not have implications for Intense. As my posting will be from 01-04-2023 regular{color}{color:#000000}à{color}{color:#000000}regular. When I make a copy of this in the VNAS\', \'Comment 101: system will pick-up.{color}{color:#000000}Can you confirm this thought?{color}{quote}{color:#000000}What do you mean regularàregular? Can it happen that some assumptions from this taks can change?{color}{color:#000000}Should it works like it was described before?{color}{quote}{color:#000000}Ok\', \'Comment 102: so for each document which will be copied by action\\\'Create copied VNAS SI and PI\\\' (copy 1:1 - without changes in data on invoices) it should be created PI regular (copy of old PI regular with calculated fields) and then it should be created SI registered.{color}{quote}{color:#000000}Regards,{color}{color:#000000}Damian{color}"\', "Comment 103: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Thanks for your message.{color} {color:black}Okay if it can be prioritized again it would be of much help to me. Process now is very inefficient.{color} {color:black}{color} {color:black}Indeed in process it is back to first set-up regular{color} {color:black}à{color}{color:black} regular.{color} {color:black}Not regular{color} {color:black}à{color}{color:black} registration.{color} {color:black}{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) <jira@kotrak.com> *Verzonden:* donderdag 30 maart 2023 13:17 *Aan:* Jong", "Comment 104: Christine de <CJong@deheus.com> *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG) \'", \'Comment 105: \\\'Hi [~CJong@deheus.com],we\\\\\\\'ve made changes on VNAS process:1. Added new generation for external document number (for copied PI invoices).2. Added new flow for VNAS documents (entry -> archive).You can verify it from list "Purchas Invoices (VNAS)".Best regards,Grzegorz\\\'\', "Comment 106: \'{color:black}Hi Grzegorz,{color} {color:black}{color} {color:black}It works! Thanks a lot.{color} {color:black}Please make it available for PROD.{color} {color:black}{color} {color:black}Can you prioritize that VNAS item is available next week. So that I can make the deposits for 04-2023 with VNAS item code.{color} {color:black}Than we can use the copy function starting 05-2023.{color} {color:black}{color} {color:black}Thanks a lot", \'Comment 107: to the whole team\', \'Comment 108: this is a great efficiency approvement.{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:* Grzegorz Materla (Jira) <jira@kotrak.com> *Verzonden:* vrijdag 14 april 2023 09:55 *Aan:* Jong\', "Comment 109: Christine de <CJong@deheus.com> *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG) \'", \'Comment 110: "Hi [~CJong@deheus.com],we\\\'ve moved all functionality into PROD Intense environment. We have also prepared special role for VNAS document list and we have already pinned you and Mitch:!image-2023-04-21-09-27-04-212.png!If you want add more users please provide us with names.Best regards,Grzegorz"\', "Comment 111: \'{color:black}Hi Grzegorz,{color} {color:black}{color} {color:black}Thanks for your action.{color} {color:black}NAS functionality should be available for me and Bert Geijtenbeek.{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:* Grzegorz Materla (Jira) <jira@kotrak.com> *Verzonden:* vrijdag 21 april 2023 09:33 *Aan:* Jong", "Comment 112: Christine de <CJong@deheus.com> *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG) !image006-1!\'", \'Comment 113: "Ok,Bert has also access to this list.One more thing is to verify that item in Intense is configured properly\', "Comment 114: we see 2 items in Intense. 1st one with name \'Vergoeding NAS\' we configured as on Test database. We\' re not sure why there are 2 items", \'Comment 115: one looks like created manually and 2nd like sent from Milas.!image-2023-04-21-12-35-27-347.png!!image-2023-04-21-12-36-50-035.png!2nd with other name \\\'Vergoeding NAS_VNAS\\\' is congifured like that: !image-2023-04-21-12-37-05-224.png!Please verify it and maybe make some test on Test database aslo with archiving these documents with VNAS code and see that it will go to Milas properly."]\']\nRelated Issues:\n[\'DGS-8324\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8080\n\n### Instruction:\nHello,\r\n\r\nWe miss 3 catergories on the round of Reimert 101619/0023/0001.\r\nPlease add, Calves/Expenses-Feed/Slaughtery.\r\n\r\nWe need this information to be able to close the round. If it can be made priority it would be of much help.\r\n\r\nKR Christine\r\n\n\n### Response:\n["Comment 1: [\'[^Purchase_migration_Reimert 101619-1.xlsx] _(20 kB)_[^Sales_migration_Reimert 101619-1.xlsx] _(19 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'The files have been checked", "Comment 4: and they were sent to Grzegorz. To be planned based on the current backlog.\'", "Comment 5: \'Grzegorz has migrated the files. Christine", "Comment 6: please verify if everything is OK :)\'", "Comment 7: \'Dodane do listy z podsumowaniem wysłanej do klienta.\'", "Comment 8: \'Everything is okay. Thanks for migration. File is complete\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8079\n\n### Instruction:\nDear Service Desk \r\nWe have experienced a problem in DHPlant on Accepting and Confirming production lot reports on the listed Lot Numbers. \r\nWe never had this kind of problem before so ; if anyone who is able to assist us in solving the problem would be so helpful .\r\nThis are the lot reports denied to accept and confirm with the Error massage. (Attached)\r\n\r\nLot number\r\n0415131222006/ 0415131222005/ 0415131222003/ 0415131222002/ 0415121222006\r\n0415121222005/ 0415121222001/ 0415101222010/ 0415101222008/ 0415101222007\r\n0415101222004/ 0415101222003/ 0415101222002/ 0415091222006\r\n\r\nThanks in Advance \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: \'Thanks very Much We wait for you. \'", "Comment 3: \'Good morning,Please attach the error Message indicates tolerance", "Comment 4: !image-2022-12-16-12-17-25-102.png|width=1495,height=783!Raw production Valid ? Is the user role set ? !image-2022-12-16-12-21-59-368.png!Regards\'", \'Comment 5: \\\'{code:java}022-12-16 14:29:51 (e9ef4f10-b4ae-4048-8a60-41df7735adab/Plant.Prod.BusinessLogic/ETDB04/12476/111) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 6: "host": { "Value": "10.103.3.33:83"\', \'Comment 7: "HasValue": true\', \'Comment 8: "Host": "10.103.3.33"\', \'Comment 9: "Port": 83 }\', \'Comment 10: "path": "/api/productionLot/update"\', \'Comment 11: "queryString": []\', \'Comment 12: "requestBody": "{\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":1,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"04167494-ebf7-46ad-ac04-11e526b26b86\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":8622.887},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":2,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"77c37b5a-8668-425c-870f-00fedc43d6da\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2402.233},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":3,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"8f643e2c-f2af-4f84-9899-bc0d0ca93acc\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":5040.365},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":4,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"c4461a25-a85d-4948-b9ae-83549ce2b6ff\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":120.964},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":5,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"37b8e22a-4e7c-4c8c-a064-cca2179bebfa\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1504.411},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":6,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"c148f2cb-b821-4370-9ea3-ed9f44fc0c0e\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1017.799},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":7,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"0e1d846b-db85-42b4-87e9-99953a68f015\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":4259.599},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":8,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"1ea1388f-851e-41b2-ae58-57e94e9253c0\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":613},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":9,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"11edbf16-5303-42a3-854a-5b44db0b32a4\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":685.084},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":10,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"b760843d-7131-4900-8275-35044f545d45\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1561.572},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":11,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"0d1662a5-43a4-4a31-89ad-42c401424983\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":30281.895},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":12,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"7f225535-0db8-4ea2-9e5a-2ab2a18f60f2\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":120.344},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":13,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"52abdb1b-bb1c-4d2e-8b49-c6d92c2de176\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":180},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":14,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"e5cd69cf-ea6e-4821-ac7e-955bd4abb1a0\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":626.908},\\\\\\\\"description\\\\\\\\":null},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":15,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"627dfb57-370f-4e2a-b83e-f38f60fc1b90\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":3005.108},\\\\\\\\"description\\\\\\\\":null}],\\\\\\\\"executions\\\\\\\\":[{\\\\\\\\"elements\\\\\\\\":[],\\\\\\\\"readyProductId\\\\\\\\":\\\\\\\\"1ef655dc-4d13-469e-a955-e58f7aee615b\\\\\\\\",\\\\\\\\"packingRecipeId\\\\\\\\":\\\\\\\\"c927c795-a570-42e6-b19e-e6fc52dba462\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":60042.169},\\\\\\\\"requestedQuantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":60000},\\\\\\\\"expiryDate\\\\\\\\":\\\\\\\\"2023-06-09T15:51:34.476Z\\\\\\\\"}],\\\\\\\\"reservations\\\\\\\\":[],\\\\\\\\"productionLotId\\\\\\\\":\\\\\\\\"79fdfac7-7f09-48bc-bd8f-50aa29f7f97c\\\\\\\\",\\\\\\\\"recipeId\\\\\\\\":\\\\\\\\"c927c795-a570-42e6-b19e-e6fc52dba462\\\\\\\\",\\\\\\\\"labelId\\\\\\\\":null,\\\\\\\\"productionOrderId\\\\\\\\":\\\\\\\\"3163ad39-d59a-4894-a5d8-2fb3698d692d\\\\\\\\",\\\\\\\\"businessPartnerId\\\\\\\\":null,\\\\\\\\"shiftNumberId\\\\\\\\":null,\\\\\\\\"description\\\\\\\\":null,\\\\\\\\"statusChange\\\\\\\\":3}"}.System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 400 (Bad Request).) ---> Refit.ApiException: Response status code does not indicate success: 400 (Bad Request). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273 --- End of inner exception stack trace --- at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 13: AggregateId businessUnitId\', \'Comment 14: Quantity productionQuantity\', \'Comment 15: IEnumerable`1 settlementData\', \'Comment 16: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 132 at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 17: ConfirmProductionLotActionData data\', \'Comment 18: IEnumerable`1 reservations\', \'Comment 19: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 82 at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 308 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 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.Prod.BusinessLogic.Infrastructure.Api.Controllers.ProductionLotController.UpdateProductionLot(UpdateProductionLotViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\Controllers\\\\\\\\ProductionLotController.cs:line 106 at lambda_method(Closure \', \'Comment 20: Object \', \'Comment 21: Object[] ) at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target\', \'Comment 22: Object[] parameters) at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 23: ObjectMethodExecutor executor\', \'Comment 24: Object controller\', \'Comment 25: Object[] arguments) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next\', \'Comment 26: Scope& scope\', \'Comment 27: Object& state\', \'Comment 28: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next\', \'Comment 29: Scope& scope\', \'Comment 30: Object& state\', "Comment 31: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync() at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)---> (Inner Exception #0) Refit.ApiException: Response status code does not indicate success: 400 (Bad Request). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273<---{code}\'", "Comment 32: \'Hello Dear we tried now to edit salt and accept confirm then this error message still appers raw production is valid and the user role is set fro production yes ; see attached error message!image002!!image003!!buz 2.PNG|thumbnail!\'", "Comment 33: \'Hello", "Comment 34: Please Verify production lot reports “0415131222003”Regards\'", "Comment 35: \'Hi dear yes this lot reports “0415131222003” is verified and accepted this one worked great . Thanks\'", "Comment 36: \'Hello Gemechis", \'Comment 37: I have resubmitted the batch reports.The reason\', "Comment 38: out of stock items.Please check Lot number.0415131222006/ 0415131222005/ 0415131222003/ 0415131222002/ 04151212220060415121222005/ 0415121222001/ 0415101222010/ 0415101222008/ 04151012220070415101222004/ 0415101222003/ 0415101222002/ 0415091222006Regards\'", "Comment 39: \'Dear sorry for the late replay ; but this lot number verified 0415101222007/ 0415101222004/ 0415101222003/ 0415101222002/ 0415091222006/0415131222003 0415121222001/ 0415101222008/0415121222005/ We are also trying verify the rest will tell you the result thanks so much and respect\'", \'Comment 40: "I\\\'m waiting for feedbackYou can close your incident?The problem has been resolved? Regards"\', "Comment 41: \'Dear Ok I will close the ticket But this one is still rejecting not accepting 0415121222003\'", "Comment 42: \'Hello", \'Comment 43: Please verify \', "Comment 44: 0415121222003.You can close your incident?Regards\'", "Comment 45: \'Thanks very much Now we have closed / Verified all the lot Report we had faced problem Accepting ; Thanks very much Again @Adrian Kozak for your time and support . Much appreciated Regards\'", "Comment 46: \'Thanks a lot.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8078\n\n### Instruction:\nKontenery dostają status 999 (czyszczenia), pomimo wyczyszczenia nadal dostają status 999 i tak od nowa. Produkcja zatrzymana.\r\nWcześniej pojawiały się liczne błędy:\r\nId 6109642 -finish transfer\r\n6109533 – register transfer error 5:1\r\nOstatni log z błędem 20:15\r\n\n\n### Response:\n["Comment 1: [\'[^komunikat błędu.txt] _(3 kB)_!obraz!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Please check if problem still occurs\'", "Comment 4: \'Nadal jest komunikat 999", "Comment 5: powinien być do gotowy do zasypu. \'", "Comment 6: \'Please check now\'", "Comment 7: \'pokazał się błąd id 6110188\'", "Comment 8: \'!obraz-1!\'", "Comment 9: \'Please check if problem still occurs\'", "Comment 10: \'Problem dalej występuje.Kontenery jeżdżą w kółko do czyszczenia.Produkcja stoi", "Comment 11: temat ktyryczny !\'", "Comment 12: \'Błąd nie dotyczy silosu tylko transportu\'", \'Comment 13: "Problem still occurs. Production can\\\'t produce. When will problem resolved?"\', "Comment 14: \'We are working on solution with our dev team. I will give you feedback as soon as possible.\'", "Comment 15: \'Hi,Can you please check?!image-2022-12-16-09-40-12-729.png!\'", \'Comment 16: "I\\\'ve verified VPN connection right now and it\\\'s working. Please restart FortiClient and try again."\', "Comment 17: \'Messages for this production has been cancelled yesterday. Please provide us why?!image-2022-12-16-10-14-01-704.png!\'", "Comment 18: \'Messages have been incorrectly removed as requested by the reporter.\'", "Comment 19: \'Please check conatiners now\'", "Comment 20: \'communication should be working right now. Please verify\'", "Comment 21: \'msg_id 6110637 - error:System.Web.Services.Protocols.SoapException: Serwer nie może przetworzyć żądania. ---> StartTransfer error: System.Data.SqlClient.SqlException (0x80131904): StartTransferError 2: Transfer from silo containing different article\'", "Comment 22: \'Please check current queue", "Comment 23: looks like since 12:39 all messages are with status 0 \'", "Comment 24: \'containers are cleaning all the time", "Comment 25: it can be caused by PCS-DHP error reported while ago. \'", "Comment 26: \'Please provide us wchih art_id is right:!image-2022-12-16-14-07-42-650.png!\'", "Comment 27: \'art_id 27579 poprawny915752-W25 był dla lotu 28 transferowany z p46033 do p46063\'", "Comment 28: \'Also there areResidues in destination codep46063. As I understand it should be empty am I right?!image-2022-12-16-14-38-59-823.png!\'", "Comment 29: \'all tanks are emptied and cleaned\'", "Comment 30: \'We cleaned entries in database . please verify\'", "Comment 31: \'is correct", "Comment 32: no error shows\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8077\n\n### Instruction:\nQuestion from my collegue Koen. These invoices are on round B004145/0035/0001, but should be on round B004145/0035/0002. Financially everything is right, so can you move these documents in Intense?\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: \'SteffenCould you and Koen try to do it by yourself?!image-2022-12-16-10-27-22-596.png|width=1108,height=293!!image-2022-12-16-10-28-39-443.png!\'", "Comment 4: \'I was able to change the round so we can now. Thank you!!image-1!\'", "Comment 5: \'Great! This action works only in case of Slaughtery Report invoices. After using this action the system changes Round Number in: SR", \'Comment 6: SI and PI. This is very important to keep the same Round number in these three documents\', "Comment 7: otherwise the Technical Results will no be calculated properly.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8076\n\n### Instruction:\nThe recipe 3921.030 does not appear in DHC even though it is available in DHC and the technology has been generated properly.\n\n### Response:\n["Comment 1: [\'!1.jpg|thumbnail!!2.jpg|thumbnail!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "System.Data.Entity.Infrastructure.DbUpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.Entity.Core.UpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Cannot insert duplicate key row in object \\\'dbo.Items\\\' with unique index \\\'IX_Code\\\'. The duplicate key value is (3204010).The statement has been terminated."\', \'Comment 4: \\\'brak itemu w dhc service przy update z poziumu dhc linkowania2022-12-15 15:26:15,427 [35] INFO Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER497-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:37] - Receiving message (Evolution.DHCountry.Interfaces.Items.ItemChangedMessage) [Id:bd7b72a3-7c5a-11ed-86ea-ccca08f7b613]2022-12-15 15:26:15,427 [35] ERROR Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER497-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:55] - Cannot handle message (Evolution.DHCountry.Interfaces.Items.ItemChangedMessage). Exception occured:2022-12-15 15:26:15,427 [35] ERROR Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER497-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:56] - System.Data.Entity.Infrastructure.DbUpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.Entity.Core.UpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_dbo.Items_dbo.DhhItems_DhhItemId". The conflict occurred in database "DHCService_UA_Test"\', \'Comment 5: table "dbo.DhhItems"\', "Comment 6: column \\\\\'Id\\\\\'.The statement has been terminated.\'", "Comment 7: \'Please verify should be ok now!image-2022-12-15-14-48-49-764.png!\'", "Comment 8: \'Yes", \'Comment 9: we see\', "Comment 10: thank you\'", "Comment 11: \'May we close the task?\'", "Comment 12: \'Yes\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8075\n\n### Instruction:\nFurthermore, we have a question regarding the types of hatchery invoices. In almost every case where we put in a hatchery invoice which should be settled in the saldo (regular or financed, not registration), we use financed. In that case, the customer gets the invoice from the hatchery but we have to finance it for the customer. In that case, we thus do not send the invoice created from Milas (because the customer already has the invoice from the hatchery). Right now, the printouts still use the invoice number from Milas (as it gets posted in Milas, which is also correct), but Koen and I were wondering if we could use the external document number on the invoice from the hatchery instead. So only in the following case: Financed PI and SI on hatchery round category. For regular invoices on hatchery round, the Milas SI number can be showed, as we do sent the invoice to the customer then.\r\nWe would like to hear from you if this is possible.\r\n\n\n### Response:\n[\'Comment 1: [\\\'Financial Statement Printout in MAS BE:In case of Financed SI/PI the system must show the "External Number" instead of the "Document Number ERP" field in the "Document nr" column.Regular/Registration invoices remains as they are (Regular- Document Number ERP\', \'Comment 2: Registartion- Intense PI/SI Document Number)Purchase Invoice- External Document NumberDoc_ShortStringColumn19Sales invoice- no External Document NumberSteffen\', \'Comment 3: there is no External Document Number field in Sales Invoice\', "Comment 4: could you please tell us how we should manage this?\'", "Comment 5: \'We would like the external invoice number from the PI to come through on SI invoices on printouts as well. This invoice+number is sent from the hatchery directly to the customer", \'Comment 6: so they both "know" this external document number. To finalize\', "Comment 7: is this possible only for financed HATCHERY invoices?\'", \'Comment 8: \\\'Yes. I forgot to write this is related to the Hatchery financed invoices.ADJUSTED STATEMENT: Financial Statement Printout in MAS BE:In case of Financed HATCHERY SI/PI the system must show the "External Number" from PI instead of the "Document Number ERP" field in the "Document nr" column.Nothing change for Regular/Registration invoicesPurchase Invoice/ External Document Number: Doc_ShortStringColumn19\\\'\', "Comment 9: \'[~ewa.mucha@kotrak.com]", "Comment 10: done for FS. You can feel free to test it ;)\'", "Comment 11: \'Grzesiu", "Comment 12: UAT?\'", "Comment 13: \'Dodane do wewnętrznego podsumowania tasków.\'", "Comment 14: \'[~ewa.mucha@kotrak.com]UAT :)\'", "Comment 15: \'!image-2022-12-28-15-23-41-098.png|width=841,height=347!!image-2022-12-28-15-24-03-549.png|width=803,height=139!!image-2022-12-28-15-24-36-997.png|width=779,height=351!\'", "Comment 16: \'[~grzegorz.materla@kotrak.com]sprawdziłam na FS ID78688 i system wyświetla numer ERP zamiast External Number z PI\'", "Comment 17: \'[~ewa.mucha@kotrak.com]", \'Comment 18: rzeczywiście kolumna która była wyświetlana to ERP nr.\', \'Comment 19: a nie Document nr. tak jak sugerował wydruk\', "Comment 20: aktualnie zaktualizowałem i działa.Pozdrawiam,Grzegorz\'", "Comment 21: \'Przetestowane i działa na UAT.DHNLC-1209\'", "Comment 22: \'Steffen", \'Comment 23: this was adjusted in the system. Could you please test this on IBIP_DH_TEST? After your confirmation everything is correct\', "Comment 24: the changes will be deployed on PROD>!image-2022-12-28-16-01-52-834.png!\'", "Comment 25: \'{color:black}Hello Ewa,{color} {color:black}{color} {color:black}This seems to be correct for the FS", \'Comment 26: but I don’t see a modification on the S2P in the test environment.{color} {color:black}{color} {color:black}First\', \'Comment 27: on the S2P\', \'Comment 28: the external document number is showed under document nr.{color} {color:black}{color} !image001!{color:black}{color} {color:black}{color} {color:black}Second\', \'Comment 29: on the S2P\', \'Comment 30: I still see the SIB numbers for hatchery invoices (first two lines on the printout){color} {color:black}{color} !image009!{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}SalutationsCordiales{color} | | | |{color:#000001} Steffen{color} |{color:#000001} {color} |{color:#000001} Driesen{color} | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSBELGIEN.V.*{color}* | | |{color:black} {color} | |{color:#000001} LouisPasteurstraat11/201 \\\\u200b3920Lommel{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+32-11-546672{color}{color:#000001} <tel:+32%20-%2011%20-%2054%2066%2072>{color} | {color:#000001}Ondernemingsnummer:0437.737.739{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} | |{color:black}{color} !image007.jpg|thumbnail!{color:black}{color} | *Van:* Ewa Mucha (Jira) <jira@kotrak.com> *Verzonden:* woensdag 28 december 2022 16:03 *Aan:* Driesens\', "Comment 31: Steffen <SDriesen@deheus.com> *Onderwerp:* DGS-8075 Financial Statement printout update for financed hatechery invoice | *{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}* | !image008!\'", "Comment 32: \'[~ewa.mucha@kotrak.com]", "Comment 33: z tego co widzę to klient chce takie zmiany jeszcze na S2P wydruku.\'", "Comment 34: \'Steffen", "Comment 35: could you please specify what has to be adjusted in the S2P printout? Only FS printout was modified.\'", \'Comment 36: "If possible\', \'Comment 37: we would like to see the same external document number on the S2P (under \\\'factuurnummer\\\' for this case (financed hatchery invoices). So the same number as the one used on the FS under document nr.!image!"\', "Comment 38: \'[~grzegorz.materla@kotrak.com] jesteśmy w stanie rozróżnć hatchery invoices od pozostałych na wydruku S2P?\'", "Comment 39: \'[~grzegorz.materla@kotrak.com]sprawdzisz to ?\'", "Comment 40: \'[~ewa.mucha@kotrak.com],[~damian.swistek@kotrak.com]", \'Comment 41: tak\', \'Comment 42: możemy sięgnąć do faktur\', "Comment 43: które istnieją w systemie i są powiązane z S2P aby zweryfikować czy jest to Hatchery.\'", "Comment 44: \'Question", \'Comment 45: could we enlarge this principle for all financed invoices? We do get a few financed invoices other than hatchery invoices (veterinary costs\', "Comment 46: slaughtery reports as well,...)\'", "Comment 47: \'Hello", "Comment 48: do you have the current status for this?\'", "Comment 49: \'Hello Steffen,Could you confirm changes are needed on printouts?Should we change FS printout and also S2P printout", \'Comment 50: right?Changes are related to the old printouts (printous which you use right now\', \'Comment 51: not new layout for Coppens)?Is it requirement correct? It should be applied to all Financed SI/PI invoices instead \\\\\\\'Financed HATCHERY SI/PI\\\\\\\'{quote}In case of Financed HATCHERY SI/PI the system must show the "External Number" from PI instead of the "Document Number ERP" field in the "Document nr" column.Nothing change for Regular/Registration invoicesPurchase Invoice/ External Document Number: Doc_ShortStringColumn19{quote}Now we\\\\\\\'re working on new Financial statement printout and S2P printout (regarding Coppens new layout) and it\\\\\\\'s priority and then we can adjust printouts for MAS BE which you use right now. I think it could be handleat the earliest on next week.\\\'\', \'Comment 52: "Hello Damian\', \'Comment 53: this update is indeed for both the FS and also the S2P. Also this is related to the current printouts\', "Comment 54: I don\'t know how the Coppens layout will look like", \'Comment 55: however I suspect that in the end\', \'Comment 56: there we would like to see the same number. Additionally\', \'Comment 57: if possible we would like to see it for all types of financed invoices indeed\', \'Comment 58: we found out there are a few other cases than hatchery invoices only."\', "Comment 59: \'The document numbers on the new Coppens layouts should indeed be the same numbers as Steffen refers to.\'", \'Comment 60: "Do sprawdzenia wydruki FS i S2P dla MAS BE (zarówno nowe jak i stare) i do zmiany wyświetlanie numeru dokumentu - powinen być \\\'External Document Number\\\' zamiast \\\'Document ERP Number\\\' dla wszystkich faktur PI o typie \\\'Financed\\\'."\', "Comment 61: \'Sprawdzone", "Comment 62: zmienione dla PI o trypie Financed dla MAS BE na test.\'", \'Comment 63: "Now for all \\\'Financed\\\' invoices (SI and PI) on S2P and Financial statement printouts will be displayed \\\'External Document Number\\\'.It\\\'s ready on UAT environment (IBIP_DH_TEST).It has been implemented to all printouts of FS and S2P (new and old versions) in MAS BE sector.Please verify that it works properly on printouts of FS and S2P\', \'Comment 64: then we can move it to producion environment."\', "Comment 65: \'This looks good for the Hatchery section on the FS (it took the external nr. from the PI and showed this where there would be an SI nr. otherwise. For the S2P (and I guess for other sections such as expenses/slaughtery) there is no update yet.!image-1!!image-2!\'", \'Comment 66: "Do you mean this invoice on S2P? SI-FNB/2022/0053?In this case should we displays value from Purchase Invoice linked with this SI?On SI Financed invoices there are no field \\\'External Document Number\\\'.!image-2023-02-17-15-56-38-867.png!!image-2023-02-17-15-56-51-768.png!!image-2023-02-17-15-57-03-433.png!"\', \'Comment 67: "Yes indeed. The SI is the one that will be shown on the S2P\', \'Comment 68: but it is indeed the PI that has de external document number. So if possible\', \'Comment 69: we would like to see the external document number from the PI as the document number on the printouts for both PI\\\'s or SI\\\'s (if financed of course)."\', \'Comment 70: "[~SDriesen@deheus.com],we\\\'ve made changes on S2P printouts in MAS BE test environment. You can feel free to test it.Best regards,Grzegorz"\', "Comment 71: \'Grzegorz", "Comment 72: I took a quick look. For financed hatchery/expenses invoices this looks fine to me on the S2P. For financed slaughtery invoices we don\\\\\'t really seem to have an external document number because we just use the slaughter report", \'Comment 73: no invoice. So that would explain why this field is empty (line of 85.764,22 EUR). For the last line (202.563,77 EUR\', \'Comment 74: also financed document)\', \'Comment 75: I do however see "TEST123" (see screenshot 1). To what is that referring? Secondly\', \'Comment 76: these implementations could be moved to the FS as well. There I see that for hatchery this external doc. nr is already used\', "Comment 77: but not for expenses etc. as it is for the S2P (see last 3 screenshots)!image-3!!image-4!!image-5!!image-6!\'", \'Comment 78: "Grzegorz\', \'Comment 79: I have an additional question. Is it possible\', \'Comment 80: that when we have a registration document on the FS printout\', \'Comment 81: the document nr. column for this line will be empty? The customer doesn\\\'t know this number neither."\', "Comment 82: \'What is the status of this?\'", "Comment 83: \'Hi [~SDriesen@deheus.com]could you please confirm all changes which should be done in this task to adjust all your requirements.I reviewed this task and try to summarize all remaining changes.{quote}For the last line (202.563,77 EUR", \'Comment 84: also financed document)\', \'Comment 85: I do however see "TEST123" (see screenshot 1). To what is that referring?{quote}It\\\\\\\'s a External Document Number from this Financed PI!image-2023-04-18-12-26-36-727.png!{quote}Secondly\', \'Comment 86: these implementations could be moved to the FS as well. There I see that for hatchery this external doc. nr is already used\', "Comment 87: but not for expenses etc. as it is for the S2P (see last 3 screenshots){quote}It means that if there is \\\\\'Financed\\\\\' Purchase Invoice it should be shown on Financial statement printouts (old and new) always \\\\\'External Document Number\\\\\' from Purchase Invoice instead of Intense document number or Erp Document number. It doesn\\\\\'t matter in which section it is (Expense", \'Comment 88: Slaughtery\', "Comment 89: Hatchery) it should be alway \\\\\'External Document Number\\\\\'?In cases when it\\\\\'s \\\\\'Financed\\\\\' Sales Invoice it should be visible alway \\\\\'External Document Number\\\\\' from linked PI (\\\\\'Leading doc\\\\\')?{quote}Grzegorz", \'Comment 90: I have an additional question. Is it possible\', \'Comment 91: that when we have a registration document on the FS printout\', "Comment 92: the document nr. column for this line will be empty? The customer doesn\\\\\'t know this number neither.{quote}Should it be applied to all \\\\\'Registered\\\\\' Purchase Invoices and all \\\\\'Registered\\\\\' Sales Invoices?Everytime when one of these cases (SI or PI registerd) will be shown on FS printouts and S2P printouts it shouldn\\\\\'t be visible any number in column \\\\\'Document nr\\\\\' on printout?!image-2023-04-18-13-01-43-574.png!\'", "Comment 93: \'Hello Damian,To sum up we would like:1. To have all financed invoices (hatchery", \'Comment 94: expenses\', \'Comment 95: slaughtery,..) show their external document number on both the FS and the S2P. So for financed documents not the Intense document number\', "Comment 96: nor the Milas document number.2. We reconsidered and the demand to make the document number for registrated invoices empty should NOT be put through. Our apologies.\'", \'Comment 97: "Hi Steffen,we\\\'ve made changes on FS old (FS new has no document number) and S2P old and new regarding your comments.You can feel free to test it in TEST Intense environment.Best regards,Grzegorz"\', \'Comment 98: "Hello Grzegorz,I tested it for multiple cases\', \'Comment 99: but I still have some comments:1. For financed slaughtery invoices (PI to the customer)\', "Comment 100: I couldn\'t continue because of this error (screenshot 1)2. I do see the external number for the hatchery invoice on the hatchery category (marked in yellow)", \'Comment 101: but I do miss the numbers for the expenses category (stripes in black\', \'Comment 102: external document number was 002079 and 002080) and as I said in point 1\', "Comment 103: I couldn\'t add the external document number", \'Comment 104: so these numbers are also missing (stripes in red\', \'Comment 105: external document nr was 002081).!image-7!!image-9!"\', "Comment 106: \'Hello Steffen,ad1. Every condition from error message did you check?ad2. Could you give me the document numer or id?Best regards,Grzegorz\'", \'Comment 107: "Hello Grzegorz,Ad 1. Yes. The difference with this financed slaughtery invoice and all the other financed invoices is that for this financed slaughtery invoice\', \'Comment 108: the PI is directed to the the customer (a customer number\', \'Comment 109: B006062). The other invoices\', \'Comment 110: there the financed PI is directed to a supplier (a hatchery\', \'Comment 111: veterinary,.. a supplier number\', "Comment 112: LB000054). The error says I can\'t create a financed invoice with an external document number if there is no supplier number (LB-number) as supplier.Ad 2. The round is B006062/0201/0003 (ID 79961)", \'Comment 113: financed hatchery invoice PI-FNB/2023/0002 (ID 79971)\', \'Comment 114: financed veterinary invoice PI-FNB/2023/0003 (ID 79973) and financed slaughtery invoice PI-FNB/2023/0004 (79976)."\', \'Comment 115: "{quote}Ad 1. Yes. The difference with this financed slaughtery invoice and all the other financed invoices is that for this financed slaughtery invoice\', \'Comment 116: the PI is directed to the the customer (a customer number\', \'Comment 117: B006062). The other invoices\', \'Comment 118: there the financed PI is directed to a supplier (a hatchery\', \'Comment 119: veterinary,.. a supplier number\', "Comment 120: LB000054). The error says I can\'t create a financed invoice with an external document number if there is no supplier number (LB-number) as supplier.{quote}Error messages appears during sending to Archive if one of conditions hasn\'t been met. There are some validation to prevent sending unacceptable data for Milas. Probably there were no VendorID on \'Customer Card\' for this supplier. If you will have this message again", \'Comment 121: please send us screen and we\\\'ll see which validation it is."\', \'Comment 122: \\\'Steffen,as I verified these invoices and this document doesn\\\\\\\'t have "Document Number ERP\\\\\\\' for example:!image-2023-04-19-11-13-29-164.png!Do we need to display something else when the "Document Number ERP" is empty?\\\'\', "Comment 123: \'Grzegorz", \'Comment 124: Damian,Yes I deleted this number\', \'Comment 125: because of the error. You can fill in a number yourself\', \'Comment 126: then the error will come back. It has to do with the fact dat the supplier on this invoice is not a supplier card\', \'Comment 127: but a customer card. When it is a customer card\', "Comment 128: external doc nr. should be empty according to the system.\'", \'Comment 129: "In this case condition for Milas validation has been met: Purchase Invoice has a Supplier with BP_Type = Customer and Type of purchase is different than \\\'Registration\\\'\', "Comment 130: then External Document Number must be empty.Maybe it\'s only test case", \'Comment 131: but it won\\\'t be real data?!image-2023-04-24-13-32-00-450.png!!image-2023-04-24-13-32-25-895.png!Is this solution with displaying numbers on printouts works properly or should we adjust it somehow?"\', \'Comment 132: "If \\\'External Document Number\\\' is empty it should be displayed Intense number - for Financed PI."\', "Comment 133: \'do sprawdzania czy External Document Number jest uzupełniony", \'Comment 134: jeśli nie\', \'Comment 135: to pokazujemy nr z Intense.we wszystkich sekcjach powinno to działać tak samo\', \'Comment 136: na żółto jedna faktura\', \'Comment 137: w sekcji Hatchery jest dobry numer\', "Comment 138: w innych nie. Do sprawdzenia i poprawienia.!image-2023-04-24-14-55-54-714.png!\']"]\nRelated Issues:\n[\'DGS-8067\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8074\n\n### Instruction:\nHi Ewa,\r\n\r\nI have 3 migration files to upload in Intense. This round was missing in the migration file.\r\n\r\nPlease see e-mail for details.\n\n### Response:\n["Comment 1: [\'Planned on Tuesday next week.\'", "Comment 2: \'!image-2022-12-19-14-26-44-879!\'", "Comment 3: \'The files have been migrated.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8073\n\n### Instruction:\nPlease have a look at feed sale FE-M/0100 in MAS NL. This document is assigned to customer 003774 but most probably it should be assigned to customer 004334 because the round is 004334/0100/0001 and all invoices belong to customer 004334 (maybe 43571 is an exception).\r\n\r\nAccording to this screen the other active round number is 003774/0060/0002 which is assigned to the first customer. Because of this issue it seems that a few feed sale invoice elements are (partly) moved from customer 004334 to customer 003774.\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n["Comment 1: [\'Theo has confirmed green comments: !image-2022-12-15-09-20-29-566.png|width=1244,height=101! !image-2022-12-15-09-20-26-929! !image-2022-12-15-09-20-29-566!\'", "Comment 2: \'Feed elements (4 lines) fromFE-M/0403 (round003774/0060/0002) have been moved back to the FE-M/0100 (round004334/0100/0001) and Customer onFE-M/0100 has been changed from 003774 to 004334.Feed elements (1 line) from FE-M/0288 (round 005550/0125/0002) have been moved back to the FE-M/0131 (round 005724/0131/0001) and Customer on FE-M/0131 has been changed from 005550 to 005274.Please verify that everything is correct now.\'", "Comment 3: \'MitchTheoCould you please check and confirm we can close the task?Thank you in advance.\'", "Comment 4: \'Dodane do listy podsumowania dla klienta.\'", "Comment 5: \'Mitch", "Comment 6: could you check and confirm status?Can we close the task?\'", "Comment 7: \'Confirmed by Theo that can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8072\n\n### Instruction:\nUmlaas WB\'s are not available for usage on DHP\r\n\r\nissue previously experienced with KD etc...\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8019\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7990\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: \'{code:java}2022-12-15 08:52:12 (/Plant.Weightbridge.Integration/SAURSRV04/7264/28) [Error] Plant.Integration.Weighbridge.Implementation.WcfWeightbridgeService - Cannot get weight data from wcf service.System.ServiceModel.CommunicationException: No connection could be made because the target machine actively refused it. (10.27.2.5:8041) ---> System.Net.Http.HttpRequestException: No connection could be made because the target machine actively refused it. (10.27.2.5:8041) ---> System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it. at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error", \'Comment 4: CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea\', \'Comment 5: ValueTask connectTask\', \'Comment 6: CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host\', \'Comment 7: Int32 port\', \'Comment 8: HttpRequestMessage initialRequest\', \'Comment 9: Boolean async\', \'Comment 10: CancellationToken cancellationToken) --- End of inner exception stack trace --- at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host\', \'Comment 11: Int32 port\', \'Comment 12: HttpRequestMessage initialRequest\', \'Comment 13: Boolean async\', \'Comment 14: CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request\', \'Comment 15: Boolean async\', \'Comment 16: CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request\', \'Comment 17: Boolean async\', \'Comment 18: CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request) at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request\', \'Comment 19: Boolean async\', \'Comment 20: CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request\', \'Comment 21: Boolean async\', \'Comment 22: Boolean doRequestAuth\', \'Comment 23: CancellationToken cancellationToken) at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request\', \'Comment 24: Boolean async\', \'Comment 25: CancellationToken cancellationToken) at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request\', \'Comment 26: Boolean async\', \'Comment 27: CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request\', \'Comment 28: HttpCompletionOption completionOption\', \'Comment 29: CancellationTokenSource cts\', \'Comment 30: Boolean disposeCts\', \'Comment 31: CancellationTokenSource pendingRequestsCts\', \'Comment 32: CancellationToken originalCancellationToken) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpClientRequestChannel.HttpClientChannelAsyncRequest.SendRequestAsync(Message message\', \'Comment 33: TimeoutHelper timeoutHelper) --- End of inner exception stack trace --- at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(HttpRequestException requestException\', \'Comment 34: HttpRequestMessage request\', \'Comment 35: HttpAbortReason abortReason) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpClientRequestChannel.HttpClientChannelAsyncRequest.SendRequestAsync(Message message\', \'Comment 36: TimeoutHelper timeoutHelper) at System.ServiceModel.Channels.RequestChannel.RequestAsync(Message message\', \'Comment 37: TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.RequestAsyncInternal(Message message\', \'Comment 38: TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message\', \'Comment 39: TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message\', \'Comment 40: TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action\', \'Comment 41: Boolean oneway\', \'Comment 42: ProxyOperationRuntime operation\', \'Comment 43: Object[] ins\', \'Comment 44: Object[] outs\', \'Comment 45: TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(MethodCall methodCall\', \'Comment 46: ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(MethodInfo targetMethod\', \'Comment 47: Object[] args) at generatedProxy_1.GetWeightData() at Plant.Integration.Weighbridge.Implementation.Integrations.Wcf.WeightbridgeServiceClient.GetWeight() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\be19d0deb1043a27\\\\\\\\Plant.Integration.Weighbridge\\\\\\\\Plant.Integration.Weighbridge.Implementation\\\\\\\\Integrations\\\\\\\\Wcf\\\\\\\\WeightbridgeServiceClient.cs:line 48 at Plant.Integration.Weighbridge.Implementation.WcfWeightbridgeService._timer_Elapsed(Object sender\', "Comment 48: ElapsedEventArgs e) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\be19d0deb1043a27\\\\\\\\Plant.Integration.Weighbridge\\\\\\\\Plant.Integration.Weighbridge.Implementation\\\\\\\\WcfWeightbridgeService.cs:line 80{code}\'", "Comment 49: \'{code:java}2022-12-15 09:03:34 (/Plant.Weightbridge.Integration/SAURSRV04/8116/21) [Error] Plant.Integration.Weighbridge.Implementation.WcfWeightbridgeService - Scale: ABWeighbridge is not responding. Auto reconnect.2022-12-15 09:03:34 (/Plant.Weightbridge.Integration/SAURSRV04/8116/35) [Error] Plant.Integration.Weighbridge.Implementation.WcfWeightbridgeService - Scale: Gate is not responding. Auto reconnect.{code}\'", "Comment 50: \'Hello Thabile,I restarted the services,I checked in the DHP application currently running!image-2022-12-15-08-24-22-489.png!You can close your incident?The problem has been resolved? Regards\'", "Comment 51: \'Hello", "Comment 52: thank you task can be closed\'", "Comment 53: \'[[DHP 3.0] Weighbridge|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%20Weighbridge&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{44A9CA7C-AB75-48F4-A7D1-65EEAE848D9F}&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%20Weighbridge%7C44A9CA7C-AB75-48F4-A7D1-65EEAE848D9F%2F%29])\']"]\nRelated Issues:\n[\'DGS-7990\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8071\n\n### Instruction:\nCan\'r select/find SO-2987/22//KBG to create a PrO in Kleinberg\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: \'!image!!image-1!!image-2!\'", "Comment 3: \'!image-3!\'", "Comment 4: \'!image-4!\'", "Comment 5: \' !screenshot-2! !image-2022-12-14-20-29-37-132!\'", "Comment 6: \'SO should be avilable to choose. Please verify.!image-2022-12-14-20-30-10-412.png!\'", "Comment 7: \'!image-2022-12-14-20-41-56-703.png!\'", "Comment 8: \'[[DHP 3.0] Brak SO na liście przy dodatnie PrO ProductionOrder|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%20Brak%20SO%20na%20li%C5%9Bcie%20przy%20dodatnie&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{CB917569-631C-4815-87B9-09D10C0E1270}&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%20Brak%20SO%20na%20li%C5%9Bcie%20przy%20dodatnie%7CCB917569-631C-4815-87B9-09D10C0E1270%2F%29])\'", "Comment 9: \'Configuration of the item was not complete.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8070\n\n### Instruction:\nPlease relink code 080587 in DHC for Premix Veghel. It should be linked to bulk code 080587, but it is linked to BB code 080587-B1000\r\nThere is an order for production and delivery this week.\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'It is already done !screenshot-1! \'", \'Comment 3: "thank\\\'s"]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8069\n\n### Instruction:\nDear Kotrak Team,\r\n\r\nWe will be glad if our system could be set to two decimal places only for all parameters on ERP.\r\n\r\nThe difference is causing lot of descripancies for us as shown below. \r\n\r\nIt is happening at other area such as purchases, inventory etc.\r\n\r\ncan we fix it please? and how?\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: \'Currently for document the value is correct.Can I get information on how this value has been generated - as it is in the attachment.Checking the control option should help but it should be tested. !screenshot-1! I understand that the problem is for different documents?Regards.\'", "Comment 4: \'we are looking for value of GHS 14,220.90 but the unit price doe not equate when multiplied.\'", "Comment 5: \'We have used the control option aswell", \'Comment 6: but the best result was that it gave a discount \', "Comment 7: which we dont want.\'", "Comment 8: \'In this case if the item has a quantity of 13500 this 14220.9/13500 gives a price of 1.0534.For two decimal places it is 1.05.I understand that the problem is when the item is copied and for the next item of the document is 1.05*13500=14175.Or is it about something else?\'", "Comment 9: \'Exactly\'", "Comment 10: \'How can we make it uniform,because if the customer recieves the invoice for 2 decimal his com putations would be different and might think we are cheating him or her\'", "Comment 11: \'And on what basis is the position value determined? Because the price then is with four decimal places.The price itself results from rounding in this case to two places.If changing the price to four places is not an option we can change the presentation of only printouts with four places.Only in this case will the price on the printout be different from the one in the system.\'", "Comment 12: \'Will consult with commercial team as well and get back please\'", "Comment 13: \'Hello", "Comment 14: do you have any update for our last comment?Thank you and regards.\'", "Comment 15: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8068\n\n### Instruction:\nWe have an issue with creating sales orders when there are no stocks available.\r\nis it possible to block or stop the confirmation of a sales order when an item in the sales order does not have the requested sale quantity?\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: \'You meant sales order or Sales order release ?Could you rpovide a screenshot from error message?\'", "Comment 3: \'i mean sales order. It is not an errorBasically", \'Comment 4: we want to put a control measure when there are no stocks available for an item so when a sales order is created on the item\', "Comment 5: erp should not allow the order to be confirmed\'", "Comment 6: \'We may trigger on database the cost shouldnt exceed 3 hours.\'", "Comment 7: \'okay but is it possible to put that control in the ERP?\'", "Comment 8: \'Yes that trigger will be verifying when user will be confiming SO if there is enough resources\'", "Comment 9: \'okay please go ahead\'", "Comment 10: \'so we can test\'", "Comment 11: \'the control should indicate what product is missing the quantities\'", "Comment 12: \'you wish an error message for operator?\'", "Comment 13: \'{color:#212121}Yes please there should be an error message indicating what products are missing quantities depending on the requested sale quantity{color} ----\'", "Comment 14: \'I would ask for some more information before preparing the trigger:What about the situation when there are two orders for the same commodity and the total quantity is not sufficient for approval or", \'Comment 15: when several orders are approved in bulk\', \'Comment 16: does the - should only one order be approved\', \'Comment 17: e.g. with a higher gidnumber?- None of them will be approved? How should the message read? Should it show which goods are missing?Changes from erp xl are to be verified?I would also like to point out that we are currently seeing ungenerated documents from you all the time\', \'Comment 18: VT from the dhc level. It would be a good idea for you to sort this out first and to reconcile your inventories.After deeper analisys\', "Comment 19: adding this will be about 5 man -hours,\'", "Comment 20: \'Thank you and to the answer your questions;If there are two orders for the same product", \'Comment 21: only the order that can be fulfilled by the current stock should be allowed to be confirmed.The error messages should be something like "the order SO123/22 cannot be confirmed due 7700-b50 missing the requested quantity\', \'Comment 22: please check your stock levels and try again" something like this.For the ungenerated VT from dhc i will be working on them.\\\'\', "Comment 23: \'Error message : Order SO123/22 cannot be confirmed due to missing quantity for item 7700-b50. Please check your stock levelsandtryagain\'", \'Comment 24: \\\'About"If there are two orders for the same product\', \'Comment 25: only the order that can be fulfilled by the current stock should be allowed to be confirmed."If we got 2 orders for item code item1 with stock 50 kgOlder order ( with lower gidnumber) is for 50 kgandNewer older ( with higher gidnumber) is for 50 kgwhich of them should be confirmed ?\\\'\', "Comment 26: \'the older one", "Comment 27: first come first served\'", "Comment 28: \'Please any update?\'", "Comment 29: \'We are very sorry for the time of implementation of the work is in progress.\'", "Comment 30: \'We prepared solution on internal envirovment. Did you wish to insert in to production or do you have any test database?\'", "Comment 31: \' will it cause any issue when inserted into production environment?\'", "Comment 32: \'Well it is opertion that are blocking confirming SO ", "Comment 33: so if there is possibility please prepare backup to be used as database for tests.\'", "Comment 34: \'okay\'", "Comment 35: \'okay we will push it to production environment next week so i will use this week to prepare the grounds\'", "Comment 36: \'please implement it\'", "Comment 37: \'Hellooo\'", "Comment 38: \'Hello,Please let me know if the change is to be added immediately to the production base?If not whether you have issued bakcup ( if so", "Comment 39: in what location) I do not see at this time any test base plugged into erp xl.\'", "Comment 40: \'{color:#212121}We have a test environment where we can test that. If it is okay by you. I am sure you are aware of the test environment for ERP{color} ----\'", "Comment 41: \'Unfortunately", \'Comment 42: I do not have the given directions for the erp xl test environment\', "Comment 43: can you provide,\'", "Comment 44: \'{color:#212121}I will furnish you with the information soon{color} ----\'", "Comment 45: \'the ip to the test server is 10.233.3.34would you need any other info?\'", "Comment 46: \'Whta is the correct databse to log on", \'Comment 47: the one with extenstion prod is for good version but it wnat work \', \'Comment 48: cause the key menager is not set correctly.Please verify it and let me know\', "Comment 49: where is the wroking test for erpxl\'", "Comment 50: \'okay\'", "Comment 51: \'the database is 10.233.3.30 \'", "Comment 52: \'!image!\'", "Comment 53: \'there are 2 ERPXL databases ton this server", "Comment 54: do you meant this with extension _prod?\'", "Comment 55: \'no the one with test at the end\'", "Comment 56: \'[^kr_zatwierdzanie_zamowienie.sql]trigger we wspolpracy z Bartkiem\'", "Comment 57: \'Please indicate unequivocally where you have a test environment and on which base will ruuchominy erpxl to verify the base.Cause ERPXL_GHA_Test database is for version 2019.1.0 but you are using different versions of ERPXL so noe one will be uble to test it.In both test and prod you are using 2020.1.0 version of ERPXL.We may add this to ERPXL_GHA_Test but do you want us to upgrade this DB if yes we need to increase the pricing for setting up you test envirovemnt.But if you are working on db from this server with extension prod ( but it seems not to be you prod db", \'Comment 58: different server and no sales documents from 2023) just confirm that.We have prepared solution\', "Comment 59: we need only add this to correct test database on correct server.!image-2023-01-20-12-33-04-721.png!\'", "Comment 60: \'if that be the case add it to the production environment for use\'", "Comment 61: \'lets add the solution to the production environment\'", "Comment 62: \'Hi,The trigger has been implemented on Prod db:!image-2023-01-20-14-06-02-081.png!If it causes any issues", "Comment 63: please disable it and let us know. Right click on Trigger and then disable.Trigger name:KR_zatwierdzanieZamowienia!image-2023-01-20-14-05-08-737.png!Regards\'", "Comment 64: \'Thanks please close\'", "Comment 65: \'please close\'", "Comment 66: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8067\n\n### Instruction:\nToday, we received the first vendor invoices from Milas, translated to French. I see now that everything is translated (correct), exept the item codes and names. They are still in Dutch. According to Adifo, the company behind Milas, this is data that should be translated in Intense and only then will be translated on the vendor invoice in Milas. Could you tell me if indeed this is the case? We do have the translations of these item codes. In the annexe an example of such an invoice, with the French header and the Dutch item codes and names.\n\n### Response:\n["Comment 1: [\'[^VendInvoiceDocument-sdriesens-0_14122022_095522_31_30309_P.pdf] _(62 kB)_\'", "Comment 2: \'This has to be discussed with Mitch.\'", "Comment 3: \'[~damian.swistek@kotrak.com] do omówienia z klientem: # Czy chcą tłumaczyć item code oraz item name # Czy chcą do MILASA wysyłać przełtumaczony item code i item name? Co dla mnie jest wątpliwe", \'Comment 4: bo item code musi się zgadzać pomiedzy MILAS i Intense\', \'Comment 5: więc jeśli zmienimy w Intensie Item Code\', \'Comment 6: to Milas go chyba nie rozpozna.Do wewnętrznej analizy # Jesli wydruki faktur sa generowane w MILASIE\', \'Comment 7: to chyba najlepiej tłumaczyć faktury w MILASIE. Co do wydruku FS\', \'Comment 8: to trzeba by się zastanowić jak to obsłużyć w Intensie. Myślałam\', \'Comment 9: że można dodać pola z dodatkowym item name np. po francusku\', \'Comment 10: po niemiecku i jeśli pole jest wypełnione na kartotece Itemu oraz jezyk wybrany na kartotece klienta\', "Comment 11: to system automatycznie wybiera dobre tlumaczenie dla nzwy itemu na wydruk FS.\'", "Comment 12: \'The translations provided by Steffen are enclosed.[^RE_ French translations printouts.msg]\'", "Comment 13: \'What is the status of this?\'", "Comment 14: \'Na tą chwilę mamy plik z tłumaczeniami dla Itemów na język francuski.[^Copy of Copy of Artikelen vertalingen.xlsx]Przyszłościowo powinny być także tłumaczenia na język niemiecki oraz holenderski.\'", "Comment 15: \'W pierwszej kolejności robimy obsługę wielojęzyczności na Itemie i zaciągnięcie francuskich tłumaczeń", "Comment 16: które zostały dostarczone.W drugim etapie będziemy robić obsługę tłumaczeń na wydrukach.\'", "Comment 17: \'zaimportowano dane i stworzono walidacje na odpowiednie tłumaczenia\'", "Comment 18: \'Na IBIP_DH_TEST wyłączona została akcja po zapisie Itemu z procedurą [dbo].[KR_TranslationCount]", \'Comment 19: która powoduje problemy w zakładaniu itemów z Milasa.Do sprawdzenia i zmiany\', "Comment 20: aby nie blokować zapisywania itemów.\'", "Comment 21: \'[~grzegorz.materla@kotrak.com]do zrobienia druga część zmian z taska", "Comment 22: czyli - obsługa tłumaczeń itemów na wydrukach Financial Statement i S2P.\'", "Comment 23: \'Dotyczy wszystkich wydruków FS i S2P", \'Comment 24: zarówno starych\', \'Comment 25: jak i nowych dla sektora MAS BE.Przyszłościowo też będzie to w sektorze MAS NL i być może innych\', "Comment 26: ale na tą chwilę implementujemy w MAS BE.\'", "Comment 27: \'Wydruki", \'Comment 28: na których są już obsłużone tłumaczenia dla itemów na IBIP_DH_TEST: * Financial Statement (MAS BE) Horizontal * Financial Statement (MAS BE) VerticalDo przetłumaczenia nagłówki dla nowego wydruku FS * Financial Statement 2 (new printout) (MAS BE)Do ustalenia czy na wydruku S2P mają też być tłumaczone jakieś inne elementy wydruku czy tylko nagłówek\', "Comment 29: tam nie wyświetlamy nazw itemów. * Saldo 2 pay_2 (new printout) (MAS BE)\'", "Comment 30: \'[^FS_new_printout_translations.xls]\'", \'Comment 31: "On IBIP_DH_TEST there are provided French translations for Items. On Item card there is new tab with table where are translations.!image-2023-02-22-10-59-42-408.png!It\\\'s ready to tests for FS printouts on IBIP_DH_TEST: * Financial Statement (MAS BE) Horizontal * Financial Statement (MAS BE) Vertical-------------Could you provide to us translations for: * Financial Statement 2 (new printout) (MAS BE) - in Excel there are all labels which i found on printout (if we already had a translation I filled it in column \\\'French\\\'). You can add/modify values for translation in this excel.[^FS_new_printout_translations.xls] * Saldo 2 pay_2 (new printout) (MAS BE) - I think only these 2 labels\', \'Comment 32: others we already had for old S2P printouts. Should be other elements of S2P printouts translated on French? On S2P printouts there are no item names\', \'Comment 33: we have only invoices without invoice elements. ** Diversen ** Subtotal!image-2023-02-22-11-39-47-908.png!"\', "Comment 34: \'[~mbovene@deheus.com],the translations have been added on S2P (MAS BE) in test environment.You can feel free to test it.Best regards,Grzegorz\'", \'Comment 35: "Hello,I can\\\'t find the translations in the item card in the test environment.Can you tell me where I should look?!image!"\', "Comment 36: \'Sorry", "Comment 37: wrong screenshot (previously). !image-1!\'", "Comment 38: \'[~SDriesen@deheus.com],the translations have been added in the test environment IBIP_DH_TEST:!image-2023-02-27-10-39-17-906.png!Best regards,Grzegorz\'", "Comment 39: \'Regarding this topic:Could you provide to us translations for:Financial Statement 2 (new printout) (MAS BE) - in Excel there are all labels which i found on printout (if we already had a translation I filled it in column \\\\\'French\\\\\'). You can add/modify values for translation in this excel. FS_new_printout_translations.xls --> This topic is in progress. I asked a colleague to help me with this.Saldo 2 pay_2 (new printout) (MAS BE) - I think only these 2 labels", \'Comment 40: others we already had for old S2P printouts. Should be other elements of S2P printouts translated on French? On S2P printouts there are no item names\', \'Comment 41: we have only invoices without invoice elements.Diversen --> Translation FR: DiversSubtotal --> can the Dutch version be modified to "Subtotaal" (2 A\\\\\\\'s)? Translation FR: Sous-total--> The translations can indeed be copied from the old printouts if available. The two other codes\', "Comment 42: \\\\\'diversen\\\\\' and \\\\\'subtotal\\\\\' may be translated. You can find it above.\'", \'Comment 43: \\\'[~SDriesen@deheus.com],the name "Subtotaal" has been changed on S2P printout in test environment.Best regards,Grzegorz\\\'\', "Comment 44: \'Grzegorz,Regarding the translations", "Comment 45: that was my fault. I was indeed accidently looking in PROD and not in TEST. There I can see the translations and I can modify them.\'", "Comment 46: \'Grzegorz,Do you have any idea when this translation field will be moved from TEST to PROD environment?!image-2!!image-3!\'", \'Comment 47: "Hello Steffen,We should be able to move it to PROD environment to the end of this week - 10.03.2023.We\\\'ll let you know when it will be moved.For now ready to move on PROD are printouts: * Financial Statement (MAS BE) Horizontal * Financial Statement (MAS BE) Vertical * Saldo 2 pay (MAS BE) Horizontal * Saldo 2 pay (MAS BE) Vertical * Saldo 2 pay_2 (new printout) (MAS BE)We\\\'re waiting only for translations for printout: * Financial Statement 2 (new printout) (MAS BE)Regards,Damian"\', "Comment 48: \'Could you tell me if the translation field can be moved to PROD by now?The translation of FS 2 (new) I hope to be able to deliver you this week. Do you need any more translations for S2P_2 (new)? If not", "Comment 49: when do you think the translation will be available?\'", "Comment 50: \'Hi [~SDriesen@deheus.com],we are working with [~mbovene@deheus.com]on FS 2 (new) calculations right now. Could you tell me when is your deadline for the translation of FS 2 (new)?Best regards,Grzegorz\'", \'Comment 51: "Hello Grzegorz,I hope this week\', "Comment 52: but that\'s up to the person helping me (he is a native French speaker and a representative). I will do my best to deliver the translations as soon as possible. My question was regarding the translation field on item cards", \'Comment 53: I don\\\'t know if you were talking about this as well?!image-4!"\', "Comment 54: \'[~SDriesen@deheus.com],yes", \'Comment 55: my mistake. I thought about the printouts. If we are talking about the fields on item cards\', "Comment 56: we can plan import translation data for tommorow. Could you provide me the file with translations?Best regards,Grzegorz\'", "Comment 57: \'Grzegorz,Normally the translations were already provided a while ago and should be on the item cards in TEST. If not", \'Comment 58: let me know\', "Comment 59: I think we have the list somewhere here.\'", "Comment 60: \'[~SDriesen@deheus.com],yes", "Comment 61: we have the translations items in test environment. We can transfer it to prod Intense environment or when you have new file with new translations you can provide it to us.Best regards,Grzegorz\'", "Comment 62: \'Normally these translations are valid. If we notice that there are some things we would like to see translated differently", "Comment 63: we will let you know afterwards.\'", "Comment 64: \'Hello Grzegorz,I translated the whole Financial Statement 2 (new). You can find the translations in blue in the excel provided. When do you expect the translated FS 2 (new) and S2P 2 (new) to be available in French?[^Translations Financial Statement 2 (new).xls] _(57 kB)_\'", "Comment 65: \'Made 1 more small adjustment", "Comment 66: this is the final version:[^Translations Financial Statement 2 (new) 2.0.xls] _(57 kB)_\'", \'Comment 67: "Hi [~SDriesen@deheus.com],we\\\'ve made changes on printout FS 2(new) for translations in test Intense environment. Now we are focusing on migrate translations for items.You can verify it.Best regards,Grzegorz"\', "Comment 68: \'Hello Damian,I looked into both documents. They look good", \'Comment 69: but we have a few more adaptions we would like to have on both documents\', \'Comment 70: everything written in red specifically. If you modified that\', "Comment 71: you may move both to PROD. Thank you!Regards,Steffen Driesen[^Translations Financial Statement 2 (new) MODIFIED.xls] _(57 kB)_[^Translations Saldo 2 Pay 2 (new) MODIFIED.xls] _(50 kB)_\'", "Comment 72: \'One more small modification on FS 2", "Comment 73: please use this version.[^Translations Financial Statement 2 (new) MODIFIED-1.xls] _(57 kB)_\'", \'Comment 74: "[~SDriesen@deheus.com],We\\\'ve made changes with your new version. You can feel free to test it.Best regards,Grzegorz"\', \'Comment 75: "Grzegorz,The changes for FS 2 new are fine. You may move this to PROD. Do you know when this will be? And the translations on the item card\', \'Comment 76: when will those be added in PROD? I see the field is already available.The changes for S2P 2 new however I don\\\'t see yet in TEST? [^Translations Saldo 2 Pay 2 (new) MODIFIED-1.xls] _(50 kB)_"\', "Comment 77: \'[~SDriesen@deheus.com],FS2 (new) and Items translations are avaliable on PROD Intense environment. Other prinouts will be migrate after the weekend.S2P 2 (new) with translations is in TEST Intense environment.Best regards", "Comment 78: Grzegorz\'", \'Comment 79: "Hello Grzegorz\', \'Comment 80: Thank you for the update!Here a few reactions:1. FS 2 (new): Translations seem good\', "Comment 81: only the stock isn\'t translated", "Comment 82: which was in TEST (see screenshot 1)2. I don\'t see the translated item names on the old FS while I do see them on item cards (see screenshot 2)3. Translations ands changes for S2P 2 (new) seem good in TEST", \'Comment 83: so they may be moved to PROD. Can the info be placed a bit more under the titles? (see screenshot 3)!image-5!!image-6!!image-7!"\', \'Comment 84: "Hi[~SDriesen@deheus.com],we\\\'ve moved all printout with translation into Prod Intense environment. We\\\'ve included your reactions\', \'Comment 85: but we don\\\'t understand point 3. Could you explain it with more details?Best regards,Grzegorz"\', \'Comment 86: "Ok\', \'Comment 87: I\\\'ve got the feedback from Damian. We\\\'ve changed alignment at titles on Saldo 2 pay prinouts.Best regards,Grzegorz"\', "Comment 88: \'Hi Grzegorz,I will look into them", \'Comment 89: thank you.My remark on point 3 was regarding the alignment\', "Comment 90: but now in Prod it looks much better already. Below you see the difference.!image-8!!image-9!\'", "Comment 91: \'Hello,1. S2P new seems good in PROD", \'Comment 92: alignment as well2. On FS new\', \'Comment 93: the entry stock and final stock are still in Dutch on French printouts (see screenshots 1&2) and the remark of Mitch regarding the guarantee that needs to be included in the feed profit (positive or negative) is not modified yet.3. The translations of the item codes are visible on the printouts.So if you could get the stock fields translated it seems fine to me.One more question\', \'Comment 94: for feed lines we have "voer\\\\\\\' as description on the S2P and for one sided SI\\\\\\\'s where the customer is both the supplier and the reference\', \'Comment 95: we have "Salmonellafonds" as description on the S2P. Could these fields be translated as well\', "Comment 96: looking to the customer card for the correct translation?!image-10!!image-11!\'", \'Comment 97: \\\'When can point 2 "On FS new\', \'Comment 98: the entry stock and final stock are still in Dutch on French printouts" be moved to PROD? These translations seemed to be allright in TEST.\\\'\', "Comment 99: \'Hi [~SDriesen@deheus.com],point 2 have been moved into Prod Intense environment. You can feel free to test it.Regarding your question about Salmonellafonds", "Comment 100: it is possible to translate it for french customers. Could you send us the particular translation for this word?Best regards,Grzegorz\'", "Comment 101: \'Hello Grzegorz,Translations of stock in French on FS new are fine (and by that the whole document is", \'Comment 102: thank you).On S2P\', \'Comment 103: we would like to see feed and salmonellafonds translated\', "Comment 104: so:* Voer (Dutch version) --> Aliments (French version) (is feed) * Salmonellafonds (Dutch version) --> Fonds de salmonelle (French version)\'", \'Comment 105: "Hi[~SDriesen@deheus.com],we\\\'ve modified the printout S2P in the TEST environment. You can feel free to test it.Best regards,Grzegorz"\', "Comment 106: \'Zmodyfikowana funkcja[dbo].[KR_Printouts_Translation].\'", \'Comment 107: "Hello Grzegorz,I don\\\'t see both changes in test. On a French S2P ( horizontal)\', "Comment 108: I still see \'voer\' for feed and \'salmonellafonds\' for the salmonelle fund", "Comment 109: but not the translations below. For the new S2P \'salmonellafonds\' is correctly translated", "Comment 110: \'voer\' we don\'t see on these printouts so that is good. But if you can move this also to the other available S2P printouts it would be great.Mitch also asked me this morning if I saw the abbreviated slaughtery and hatchery names", \'Comment 111: but as you can see they aren\\\'t yet (all?) on the new S2P.!image-13!!image-14!"\', \'Comment 112: "Update: the abbreviations are probably not visible because they aren\\\'t in test I just realised. Mitch showed me that if he adds the abbreviation manually\', \'Comment 113: it is shown and right now I did the same. This works for the new FS\', \'Comment 114: but not yet for the new S2P as you can see in the screenshots. !image-15!!image-16!!image-17!"\', "Comment 115: \'[~SDriesen@deheus.com],we adjusted only the S2P (new) printout in test environment.In that case", "Comment 116: are you want to add the translation also on the other S2P prinouts?Best regards,Grzegorz\'", "Comment 117: \'Grzegorz", \'Comment 118: Yes\', \'Comment 119: if possible. If that is too much work\', "Comment 120: it will be fine I guess.Best regards,Steffen\'", "Comment 121: \'[~SDriesen@deheus.com],so", "Comment 122: we added it on theremaining S2P prints.You can verify it.Best regards,Grzegorz\'", "Comment 123: \'Grzegorz,This is perfect", \'Comment 124: thank you. You may move this to PROD\', "Comment 125: the only thing open for the new S2P is the abbreviations of the slaughtery/hatchery I guess.\'", \'Comment 126: "The new S2P is good now\', \'Comment 127: only the abbreviations for hatchery and slaughtery are still missing and on the old S2P\', \'Comment 128: the French translations of \\\'voer\\\' and \\\'salmonellafonds should be added in the French version (see down below)."\', \'Comment 129: "Oh\', \'Comment 130: and 1 extra comment now\', \'Comment 131: on the french new S2P\', \'Comment 132: the title \\\'Divers\\\' is missing (on the dutch version it is called \\\'Diversen\\\')!image-12!"\', \'Comment 133: "[~SDriesen@deheus.com],could you test the prints one more time? We\\\'ve made changes.If everithing will be ok\', \'Comment 134: we will move the modifications to PROD.Best regards,Grzegorz"\', "Comment 135: \'Grzegorz,I see all the last asked changes on the different S2P versions", \'Comment 136: so these modifications may be moved to PROD. The abbreviations for slaughtery/hatchery names are in PROD\', \'Comment 137: so if that stands as it is on the new S2P in PROD now\', "Comment 138: everything regarding S2P should be good.Regards,Steffen\'", \'Comment 139: "[~SDriesen@deheus.com],we\\\'ve moved translations for S2P (MAS BE) printouts from TEST to PROD Intense environment.You can feel free to test it.Best regards,Grzegorz"\', "Comment 140: \'Grzegorz,Everthing regarding S2P printouts looks fine to me in PROD now. Thank you.Regards,Steffen\'", \'Comment 141: "I notice now that there are 2 small modifications that we would like to see on the new S2P. 1. Could you make \\\'leverdatum\\\' (delivery date) the leading column for the chronlogy of the printout? 2. Could you switch column 1 \\\'factuurdatum\\\' (invoice date) and column 5 \\\'leverdatum\\\' (delivery date) around? So that \\\'leverdatum\\\' (delivery date) is the first column and the leading column for the chronology?!image-18!"\', \'Comment 142: "[~SDriesen@deheus.com]These 2 changes should be applied only to S2P printout in MAS BE?{quote}I notice now that there are 2 small modifications that we would like to see on the new S2P. 1. Could you make \\\'leverdatum\\\' (delivery date) the leading column for the chronlogy of the printout? 2. Could you switch column 1 \\\'factuurdatum\\\' (invoice date) and column 5 \\\'leverdatum\\\' (delivery date) around? So that \\\'leverdatum\\\' (delivery date) is the first column and the leading column for the chronology?!image-18!{quote}"\', "Comment 143: \'Hello Damian,If possible also for MAS NL please.\'", \'Comment 144: "[~SDriesen@deheus.com],we\\\'ve made changes on S2P new printouts (MAS NL\', \'Comment 145: MAS BE) in the TEST environment.You can verify it.Best regards,Grzegorz"\', "Comment 146: \'Hello Grzegorz,This seems good both in MAS BE and MAS NL test. You may move this to PROD. Thank you!Regards,Steffen\'", \'Comment 147: "Hello Steffen,we\\\'ve made changes also in PROD environment.You can feel free to test it.Best regards,Grzegorz"\', \'Comment 148: "Hello,I think there is still one small error.The columns are switched perfectly\', "Comment 149: but the first column \'leverdatum\' (delivery date) should still be leading for the chronology. I think it is still ordered on \'factuurdatum\' (invoice date). On the example I tested yesterday in TEST", \'Comment 150: I think there was no case like this.!image-20!"\', "Comment 151: \'Hello,yes", "Comment 152: we have order by Facturdatum in SQL procedure. We made changes. Can you look at it one more time in PROD environment?Best regards,Grzegorz\'", \'Comment 153: "Hello,It still seems to be sorted by \\\'factuurdatum\\\'. Do I need to re-login?!image-21!"\', \'Comment 154: "I did by now\', \'Comment 155: but it\\\'s still the same order. (I am talking about the PROD environment)"\', "Comment 156: \'Hi Steffen,could you give me the document number?Best regards,Grzegorz\'", "Comment 157: \'Hello Grzegorz,The screenshot down below for example is SP-B/0652 (ID 106931).\'", "Comment 158: \'Hi,yes", \'Comment 159: you are right with the order\', "Comment 160: because we had the wrong date type. The prints are working fine now.You can verify it.Best regards,Grzegorz\'", "Comment 161: \'Hello,It seems good now indeed", "Comment 162: thank you.\']"]\nRelated Issues:\n[\'DGS-8215\', \'DGS-8326\', \'DGS-8075\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8066\n\n### Instruction:\nIn Andel a printout must be generated when an order for packed arrives in DHP. Manual selection of printout on sales order in DHP does generate a print; the template and printer seem to be fine. \r\n\r\nPlease check/fix config so that the printout is created automatically when sales order for packed arrives.\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: \'Hej", "Comment 3: sposób generowania wydruku można skonfigurować z poziomy pliku konfiguracyjnego pluginu as400 (\\\\\\\\kotrak\\\\\\\\dhp30_IIS\\\\\\\\PlantPrintoutPrintServer\\\\\\\\Plugins):!image-2022-12-20-08-43-44-854.png!\'", "Comment 4: \'aktualny konfig :!image-2022-12-20-09-08-05-212.png!\'", "Comment 5: \'According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task?AlsoThe current configuration is such that for shipping notice on creation and update is enabled I understand that it should be enabled?The automatic printout generation for orders (enabled at the moment) should not be changed?\'", "Comment 6: \'{color:#000000}Goodmorning.{color} {color:#000000}{color} {color:#000000}Ok to change the type of this task and please check/change the setup so that orders are printed.{color} {color:#000000}Plant needs the printout for packed orders.{color} {color:#000000}{color} {color:#000000} {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black} Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Agnieszka Januszewska (Jira) <jira@kotrak.com> *Sent:* Tuesday", \'Comment 7: December 20\', \'Comment 8: 2022 11:32 AM *To:* Kennedy\', "Comment 9: Bob <BKennedy@deheus.com> *Subject:* DGS-8066 Printout packed Andel not generared on receiving sales order{color} |{color:#ffffff} 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 10: \\\'konfig zmieniany 13.12. 2022 " !image-2022-12-22-08-14-28-445.png!drukowanie dla orderow jest ustawione!image-2022-12-22-08-17-24-405.png!\\\'\', "Comment 11: \'Please verify", "Comment 12: after you log on again.Configuration for order is set.\'", "Comment 13: \'May we close the task? Did you verify it?\'", "Comment 14: \'Andel responded that still no printouts are received for packed orders. \'", "Comment 15: \'Hi Bob,Could you please confirm when do Andel want to print printout for packed orders? When Order arrives or when Trip arrives?Regards\'", "Comment 16: \'{color:#000000}Andel wishes to get printout on arrival of order{color} {color:#000000}{color} {color:#000000} {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black} Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com> *Sent:* Monday", \'Comment 17: January 23\', \'Comment 18: 2023 3:28 PM *To:* Kennedy\', "Comment 19: Bob <BKennedy@deheus.com> *Subject:* DGS-8066 Printout packed Andel not generared on receiving sales order{color} |{color:#ffffff} 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 20: \'Dear Bob,Could you please ask Andel to verify again?Regards\'", "Comment 21: \'Dear Bob,Could you please ask Andel to verify again?Regards\'", "Comment 22: \'I have asked Andel to verify.\'", "Comment 23: \'Sure", "Comment 24: waiting for your feedback then.Regards\'", "Comment 25: \'Andel checked and they are not receiving printout for packed sales orders. Is there a way to check where in the process we have an issue? Is a print file generated? Is the printer / paper tray available?\'", "Comment 26: \'[~maciej.dobrzanski@kotrak.com]server aplikacyjny:172.23.1.91server bazodanowy:DHVD01AG01\\\\\\\\ANDEL\'", "Comment 27: \'Order: SOBE000014055 f3ceec11-90bf-4a0b-9115-77e6e166b77dWydruk jest widoczny w preview. Idiki wydruku są poprawne w konfiguracji pluginu. !prevoew! \'", \'Comment 28: \\\'Hi,Could you please set up "Keep Printed Documents" configuration for us?Regards!image-2023-02-16-07-17-37-560.png!\\\'\', "Comment 29: \'I have asked Martijn Meier for this configuration\'", "Comment 30: \'Thank you. Please", "Comment 31: let us know when it is configured.Regards\'", "Comment 32: \'Can you give us the Ip address for this printer? We are not sure which printer it is {quote}Op 17 feb. 2023 om 07:22 heeft Aleksandra Przybyłek (Jira) <jira@kotrak.com> het volgende geschreven: {quote} {quote} \\\\ufeff{color:#999999}{color}{color:#999999}{color}{color:#7a869a}{color}{color:#7a869a}{color} {quote}\'", "Comment 33: \'This is the name of the printer:!image-2023-02-17-10-46-10-103.png!\'", "Comment 34: \'Hi", \'Comment 35: requested checkbox "Keep printed documents" has been set.\\\'\', "Comment 36: \'Thank you\'", "Comment 37: \'Ordery są zapisane na liście wydrukowanych dokumentówPrzykłady:SOBE000014869 - created 2023-02-22 12:40:50 -> Printed 12:40SO000072839 - created 2023-02-22 12:12:48 -> Printed 12:12 !Created_SO! !printed! \'", "Comment 38: \'Dear,Orders are saved on printd documents list", "Comment 39: please see our examplesSOBE000014869 - created 2023-02-22 12:40:50 -> Printed 12:40SO000072839 - created 2023-02-22 12:12:48 -> Printed 12:12!image-2023-02-22-14-12-32-533.png|width=1279,height=755!We advise to check devices if they are connected properly or maybe there was some Windows update that crashed communication with printer.Regards\'", "Comment 40: \'Hi Aleksandra", \'Comment 41: Martijn sent a test page to the printer and it was printed correctly. However\', "Comment 42: the documents generated from DHP are sent to the queue but these are not printed. We will try to find out why. Or do you have an idea what may be the issue here?\'", "Comment 43: \'Dear Bob,All we could verify was done. I will put on hold this task untill we get some feedback from Martijn.Regards\'", "Comment 44: \'Hi,Any feedback? Can we close this task?Regards\'", "Comment 45: \'Plant confirmed that printout is now working fine. This ticket can be closed.\'", "Comment 46: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8065\n\n### Instruction:\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-6795\r\nwhen the daily report is run(execute report then bulk approval) if a different tab is opened then a user goes back to the report the system retains the previous settings but does not allow the user to continue with bulk approval, only the download button shows. It does not allow a refresh, the only solution being to reload the entire site then are we able to use the report again. dhp refresh does not work.\n\n### Response:\n["Comment 1: [\'[^2022-11-28_15-09-58.mp4] _(1,63 MB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Dear Thabile,Does the issue occurs for all users in plant? Do users experience issue ony in MM server? If there are fewer tabs open", \'Comment 4: does the system behave the same way?{color:#0747a6}_It does not allow a refresh\', \'Comment 5: the only solution being to reload the entire site then are we able to use the report again. dhp refresh does not work._{color}{color:#172b4d}Should I understand that you need the same report again like presented\', \'Comment 6: ie. from 28th of October to 28th of November when returning to Daily control reports?{color}{color:#172b4d}Just to confirm\', "Comment 7: on the movie you reload report with Refresh button ... Could you please confirm how report should be refreshed? !image-2022-12-14-11-50-43-941.png!{color}{color:#172b4d}Regards{color}\'", "Comment 8: \'Odtworzyłam sytuację na moim userze", \'Comment 9: przeklikując się przez moduły planta (identycznie jak widac na filmiku) powrót do Daily Control Reports u mnie powoduje zzmianę filtra na datach\', "Comment 10: natomiast knefelki Bulk Approval i Execute Report sa aktywne!image-2022-12-14-15-00-43-271.png!\'", "Comment 11: \'Hello", "Comment 12: the issue was resolved in 8.3.0... (see video from test environment on how it should behave) and yes all plants have this issue.!image![^2022-12-15_8-30-51.mp4] _(1,07 MB)_\'", "Comment 13: \'Dear Thabile,Could you please ask some users to clear Cache and cookies and let me know if it helped?Regards\'", "Comment 14: \'Hello", "Comment 15: I have been using the admin profile to check. I had and have again cleared cache as well as cookies. the issue still exists. \'", "Comment 16: \'Próbowałam przeklikać z widokiem dla dev", \'Comment 17: to za pierwszym razem poszła 400\', "Comment 18: ale po przeklikaniu wszystkiego brak błędów!image-2022-12-16-08-31-36-026.png!Tylko filtr wraca do dzisiejszej daty!image-2022-12-16-08-32-05-447.png!\'", "Comment 19: \'Dear Thabile,We still cannot reproduce this issue.Could you please confirm if browser was restarted after clearing cache?Could you please let me know or confirm if user is logged", \'Comment 20: for example\', "Comment 21: in Umlaas Road server and the issue occurs in DHP Umlaas?Could you please ask one user to recreate situation but first open dev view in browser (please click F12 button to open the console) and record it?!image-2022-12-21-13-07-33-645.png!Regards\'", "Comment 22: \'Hello", "Comment 23: please see attached[^from server.mp4] _(1,63 MB)_[^dev view.mp4] _(1,22 MB)_\'", "Comment 24: \'Hi,Thank you for recordings. But", \'Comment 25: the dev view\', \'Comment 26: as I metioned before\', \'Comment 27: we need console not elements. If it would be possible to make the recordin again\', "Comment 28: I would be very thankful.Regards!image-2022-12-22-10-19-56-144.png!\'", "Comment 29: \'Hello", "Comment 30: as per our discussion!image-1![^2022-12-22_15-20-01.mp4] _(1,53 MB)_\'", "Comment 31: \'Thank you\'", "Comment 32: \'Chodzi o to że po powrocie do Daily control report i wybraniu Bulk aproval nie ma opcji na dole: !screenshot-1! - zostaje Download jak przy execute report - pomaga F5.To co w DAP-12061.\'", "Comment 33: \'[~maciej.dobrzanski@kotrak.com]to by trzeba chyba Oli podesłać czy oddelegować czy coś. Tak", \'Comment 34: jak Piotrek pisał\', \'Comment 35: brakuje tych trzech knefli na dole\', "Comment 36: co ze zgłoszenia niekoniecznie wynikało...\'", "Comment 37: \'Na Firefox też nie działa!image-2023-01-10-13-35-14-485.png!\'", "Comment 38: \'To jest dalej to samohttps://helpdesk.kotrak.com/browse/DAP-12061\'", "Comment 39: \'Udało mi się znaleźć babola :)\'", "Comment 40: \'[~gedeon.kucharski@kotrak.com]!image-2023-01-11-07-43-48-797.png|width=281,height=202!\'", "Comment 41: \'Okay", \'Comment 42: w wersji 8.3.1 najnowszej ten case został poprawiony.[~maciej.dobrzanski@kotrak.com]\', "Comment 43: [~aleksandra.przybylek@kotrak.com]trzeba by dopytać ich kiedy ewentualnie można by im podegrać.\'", "Comment 44: \'This problem has been fixed in the new version of the application.\'", "Comment 45: \'Dear Thabile,As Piotr mentioned", \'Comment 46: problem has been fixed in the newest version. Please\', "Comment 47: contact your Project Manager to set relevant date for upgrade.Regards\'", "Comment 48: \'Hello,you can close this ticket\']"]\nRelated Issues:\n[\'DAP-13180\', \'DGS-6795\', \'DAP-12061\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8064\n\n### Instruction:\nIO....610 was created in Milas with call off for Meppel and sent to DHC/DHP/PCS. ASN is not available in DHP. In Masterdata I see that the ASN is missing is Vehicle Control.\r\n\r\nPlease check why this ASN (and possible others?) are not in Vehicle Control / in DHP.\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: \\\'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 4: table "dbo.ContactDatas".The statement has been terminated.!image-2022-12-14-10-38-38-592.png!\\\'\', \'Comment 5: \\\'Could you please provide here information for Bussines Partner with code 96 ?for that order in dhp after resending I got this error messageAn 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 6: table "dbo.ContactDatas".The statement has been terminated.after you did that you may send as information or tried to use resend on marked row:!image-2022-12-14-10-51-39-599.png!The esend should be done on every module\\\'\', "Comment 7: \'{color:#000000}Hi,{color} {color:#000000}Code 96 is a business partner created for one of our own warehouses (site 96){color} {color:#000000}In this transfer order", \'Comment 8: it is the location from which items are delivered{color} {color:#000000}{color} {color:#000000}What I see from logging\', \'Comment 9: the busines paerner data was nog correct in DHP? Or was data missing?{color} {color:#000000}{color} {color:#000000}We resend order with other BP linked and now the order is visble in DHP and intake can be registered.{color} {color:#000000}{color} {color:#000000}This ticket can be closed.{color} {color:#000000}{color} {color:#000000}{color} {color:#000000} {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black} Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Agnieszka Januszewska (Jira) <jira@kotrak.com> *Sent:* Wednesday\', \'Comment 10: December 14\', \'Comment 11: 2022 10:53 AM *To:* Kennedy\', "Comment 12: Bob <BKennedy@deheus.com> *Subject:* DGS-8064 Internal order is sent to PCS but not available in DHP{color} |{color:#ffffff} 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} |\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8063\n\n### Instruction:\nHi, from Wiola\r\nRaport needs to be correct.\r\n\r\nRafał Boniecki\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: \'Any news?\'", "Comment 4: \'According to call with Wioletta Winkler report will be corrected. Predicted date is first week of January 2023\'", \'Comment 5: "report has been corrected. Wioletta informed by e-mail. I\\\'m waiting for feedback from Wioletta"\', "Comment 6: \'*From:* Winkler", \'Comment 7: Wioletta <wwinkler@deheus.com> *Sent:* Saturday\', \'Comment 8: January 7\', \'Comment 9: 2023 2:25 PM *To:* Monika Biśta <monika.bista@kotrak.com> *Subject:* ODP: uzupełnie raportu nadgodzinDzień dobryBider- jest widoczny poprawnie w grudniu.U Pana Kostrzewy w grudniu już nie są widoczne na raporcie godz. średniotygodniowe (100). Wypłacona odstawa (powyżej normy jest i nie jest zaznaczone w raporcie.|PozdrawiamWiola***Wioletta Winkler**kierownik sekcji administracji płac*||+48600291 312[wwinkler@deheus.com|mailto:wwinkler@deheus.com][*www.deheus.pl*|https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.deheus.pl%2F&data=04%7C01%7Cwwinkler%40deheus.com%7Cd75ad8044e434b7cdc6a08d9150c5b5b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C637563965071751417%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X6qcIpvA%2Bw63vtWwf7ooaJK7gtrJAQHCZ70Yo4vPQs8%3D&reserved=0]**W tytułach wiadomości stosuję regułę *ARDI*: *A* – proszę o akcję\', \'Comment 10: działanie; *R* – proszę o recenzję\', \'Comment 11: reakcję; *D* – proszę o decyzję; *I* – informuję|||| |DeHeusSp.zo.o. ul.Lotnicza21B 99–100Łęczyca tel.:247210400 fax:247210404 REGON:011917655 NIP:526-13-06-893 wysokośćkapitałuzakładowego:22141000.00zł nrKRS:0000060991 SądRejonowydlaŁodzi-ŚródmieściawŁodzi XXWydziałKRS||Treść tej informacji może być poufna\', \'Comment 12: w związku z czym powinna trafić bezpośrednio do rąk adresata. Jakiekolwiek jej ujawnianie\', \'Comment 13: rozpowszechnianie\', "Comment 14: bądź kopiowanie jest zabronione.||\'", "Comment 15: \'!image-2!\'", "Comment 16: \'*From:* Monika Biśta *Sent:* Tuesday", \'Comment 17: January 17\', \'Comment 18: 2023 7:58 AM *To:* Winkler Wioletta <wwinkler@deheus.com> *Subject:* FW: uzupełnie raportu nadgodzinDzień dobry,Proszę o poniższą informację możemy się zdzwonić w tym tygodniu jestem 7-15.*Pozdrawiam / Best regards,**Monika Biśta* mobile: +48538212 162tel.: +48 3235 12721e-mail: +[monika.bista@kotrak.com|mailto:monika.bista@kotrak.com]+*Kotrak S.A.*Parczewskiego 2540-582 KatowicePoland*tel./phone:* (+48 32)35 12700[www.kotrak.com|https://kotrak.com/]*Certified ISO 9001:2015*++*Sąd Rejonowy / District Court* *Katowice-Wschód w Katowicach* *Wydział VIII Gospodarczy KRS\', \'Comment 19: nr KRS*: 0000704357*NIP*: 954-24-96-628 *Regon:* 277683949*Kapitał zakładowy / Share capital:* 1.052.700,00 zł\', \'Comment 20: opłacony w całości / paid in full*Lokalizacje / Locations:* Kraków\', \'Comment 21: Łódź\', \'Comment 22: Warszawa\', \'Comment 23: Opole\', \'Comment 24: Bielsko-Biała\', \'Comment 25: Gdańsk\', \'Comment 26: London*From:* Monika Biśta *Sent:* Monday\', \'Comment 27: January 9\', \'Comment 28: 2023 8:06 AM *To:* Winkler\', \'Comment 29: Wioletta <[wwinkler@deheus.com|mailto:wwinkler@deheus.com]> *Subject:* RE: uzupełnie raportu nadgodzinDzień dobry,U Pana Kostrzewy dodałam godziny średniodobowe 100 \', \'Comment 30: W którym miejscu w raporcie powinna być wykazana informacja powyżej normy?*Pozdrawiam / Best regards,**Monika Biśta* mobile: +48538212 162tel.: +48 3235 12721e-mail: +[monika.bista@kotrak.com|mailto:monika.bista@kotrak.com]+*Kotrak S.A.*Parczewskiego 2540-582 KatowicePoland*tel./phone:* (+48 32)35 12700[www.kotrak.com|https://kotrak.com/]*Certified ISO 9001:2015*++*Sąd Rejonowy / District Court* *Katowice-Wschód w Katowicach* *Wydział VIII Gospodarczy KRS\', \'Comment 31: nr KRS*: 0000704357*NIP*: 954-24-96-628 *Regon:* 277683949*Kapitał zakładowy / Share capital:* 1.052.700,00 zł\', \'Comment 32: opłacony w całości / paid in full*Lokalizacje / Locations:* Kraków\', \'Comment 33: Łódź\', \'Comment 34: Warszawa\', \'Comment 35: Opole\', \'Comment 36: Bielsko-Biała\', \'Comment 37: Gdańsk\', \'Comment 38: London\', "Comment 39: Santa Clara\'", "Comment 40: \'Cześć", \'Comment 41: przesłałem to do Wioli\', \'Comment 42: ale ma cały ten tydzień urlop\', "Comment 43: więc nie wiem czy się odezwie...\'", "Comment 44: \'ok przyszły tydzień pracuję 7-15 wtedy myślę skontaktujemy się\'", "Comment 45: \'przypomnieć w tym temacie. Ten tydzień jestem 12-20", "Comment 46: przyszły 7-15\'", "Comment 47: \'!image-3!\'", "Comment 48: \'any feedback?\'", "Comment 49: \'!image-4!\'", "Comment 50: \'6.10 u tego pracownika oznaczony jako OBM to 4h a nie 1h . Stąd pochodzi 3h różnicy między raportem a wyliczeniami z maila. Pozostałe dni są ok. Proszę o weryfikację po stronie Deheus. !screenshot-1! \'", "Comment 51: \'!image-5!\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8062\n\n### Instruction:\nFrom approx 08.30 DHP does not seem to process dispatch messages for DHP Maasbracht. Messages do arrive from PCS and are accepted in DHP, but VT is not created and no packing slip XML is generated.\r\nThere was another ticket about this issue (did you install a logger on DHP Maasbracht to monitor for delays?). Here you have more examples (see timestamp messages from PCS and overview of VTs\r\nE.g. dispatch message for trip 00946181 (received at 08:52) from PCS is for an active trip (not cancelled), but VT is missing.\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: \'Hi Bob,We can see a lot of messages were to process so we will analise this log. But it looks now message queues are clean right now. Please", "Comment 4: let me know if you can see documents processing.Regards\'", \'Comment 5: "I still do not see any new VT\\\'s created (so no SPS will be generated) in DHP."\', "Comment 6: \'How many VTs are missing? Do we have this information?\'", "Comment 7: \'But how many VTs should be cerated approximately? 10? 20?\'", "Comment 8: \'As far as I can check", "Comment 9: already 10 dispatches are not processed. Please check services / why dispatches messages from PCS are not picked up in DHP. Plant needs the packing slips.First missing dispatch in DHP: see marked line in attached screenprint!image-3!\'", \'Comment 10: \\\'{code:java}2022-12-14 10:04:29 (/Plant.Integration.PCS.NL/DHVD01AP178/31760/162) [Error] Microsoft.AspNetCore.Server.IIS.Core.IISHttpServer - Connection ID ""18230571293206390851""\', \'Comment 11: Request ID ""80002844-0000-fd00-b63f-84710c7967bb"": An unhandled exception was thrown by the application.System.Data.SqlClient.SqlException (0x80131904): 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 System.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 12: Boolean breakConnection\', \'Comment 13: Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 14: Boolean callerHasConnectionLock\', \'Comment 15: Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 16: SqlCommand cmdHandler\', \'Comment 17: SqlDataReader dataStream\', \'Comment 18: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 19: TdsParserStateObject stateObj\', \'Comment 20: Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 21: RunBehavior runBehavior\', \'Comment 22: String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 23: RunBehavior runBehavior\', \'Comment 24: Boolean returnStream\', \'Comment 25: Boolean async\', \'Comment 26: Int32 timeout\', \'Comment 27: Task& task\', \'Comment 28: Boolean asyncWrite\', \'Comment 29: SqlDataReader ds) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Dapper.SqlMapper.ExecuteReaderWithFlagsFallback(IDbCommand cmd\', \'Comment 30: Boolean wasClosed\', \'Comment 31: CommandBehavior behavior) in /_/Dapper/SqlMapper.cs:line 1075 at Dapper.SqlMapper.QueryRowImpl[T](IDbConnection cnn\', \'Comment 32: Row row\', \'Comment 33: CommandDefinition& command\', "Comment 34: Type effectiveType) in /_/Dapper/SqlMapper.cs:line 1187 at Plant.Integration.PCS.NL.Infrastructure.Persistence.Repositories.LogRepository.LogWebApiRequest(WebApiRequestDto request) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\1b53a96170a797c0\\\\\\\\Plant.Integration.PCS.NL\\\\\\\\Plant.Integration.PCS.NL.Infrastructure.Persistence\\\\\\\\Repositories\\\\\\\\LogRepository.cs:line 33 at Plant.Integration.PCS.NL.Middleware.ApiRequestLoggingMiddleware.InvokeAsync(HttpContext context) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\1b53a96170a797c0\\\\\\\\Plant.Integration.PCS.NL\\\\\\\\Plant.Integration.PCS.NL\\\\\\\\Middleware\\\\\\\\ApiRequestLoggingMiddleware.cs:line 58 at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContextOfT`1.ProcessRequestAsync()ClientConnectionId:6e465ec9-bbf3-4675-b756-2a9566512378Error Number:-2,State:0,Class:11{code}\'", \'Comment 35: "{code:java}2022-12-14 08:32:19 (null/Plant.PCS.BusinessLogic/DHVD01AP178/31780/8) [Warning] Microsoft.EntityFrameworkCore.Query - Compiling a query which loads related collections for more than one collection navigation\', "Comment 36: either via \'Include\' or through projection", "Comment 37: but no \'QuerySplittingBehavior\' has been configured. By default", "Comment 38: Entity Framework will use \'QuerySplittingBehavior.SingleQuery\'", \'Comment 39: which can potentially result in slow query performance. See https://go.microsoft.com/fwlink/?linkid=2134277 for more information. To identify the query that\\\'s triggering this warning call \\\'ConfigureWarnings(w => w.Throw(RelationalEventId.MultipleCollectionIncludeWarning))\\\'.{code}"\', "Comment 40: \'VT for trip is in plant now.In my opinion", \'Comment 41: we need to wait for processing documents. As tehy will appear in some time. In the mean time\', "Comment 42: can we lower priority to P2?Regards\'", "Comment 43: \'!image-2022-12-14-10-24-36-518.png!\'", \'Comment 44: "I see that VT\\\'s are now created in DHP and I was informed that VT\\\'s from one hour ago are picked up and SPS are printed.Prio 2: for this ticket it is okBut: I ask you to analyze this further and find a solution to solve these delays. The trucks from last hour left without SPS because they cannot wait for one hour until document is generated. This is an issue because it is not allowed and customers do not accept it anymore.Last weeks we had several moments where we had these delays\', \'Comment 45: also for other plants. I hope you found information in the log why it takes such a long time / what type of data is taking that long to process. If we can avoid sending this data (e.g. recipes)\', \'Comment 46: please let us know. "\', "Comment 47: \'Tripped marked in yellow have VTs now in plant:!image-2022-12-14-10-46-31-337.png!\'", "Comment 48: \'Sure", "Comment 49: thank you. We are now analysing the data. Will let you know as soon as possible.Regards\'", "Comment 50: \'I have checked", "Comment 51: al VTs from above list are in plant now.\'", "Comment 52: \'Dear Bob,We are analysing data within RCA task for this issue underDGS-7949. I know you have access to RCA task", \'Comment 53: so I think we can close this incident as missing VTs are now in Plant.Please\', "Comment 54: let me know if I can close this incident.Regards\'", "Comment 55: \'{color:#000000}Ok", \'Comment 56: you can close this ticket.{color} {color:#000000}Can you add me to DGS-7949 I cannot access it.{color} {color:#000000} {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black} Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com> *Sent:* Wednesday\', \'Comment 57: December 14\', \'Comment 58: 2022 1:17 PM *To:* Kennedy\', "Comment 59: Bob <BKennedy@deheus.com> *Subject:* DGS-8062 Dispatches not processed in DHP{color} |{color:#ffffff} 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 60: \'Please", \'Comment 61: verify\', "Comment 62: you are added as a request participant since the very beginning :)!image-2022-12-14-14-40-04-436.png!\'", "Comment 63: \'{color:#000000}Ok", \'Comment 64: indeed I have access\', \'Comment 65: perhaps the URL I used was not correct.{color} {color:#000000}{color} {color:#000000} {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black} Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com> *Sent:* Wednesday\', \'Comment 66: December 14\', \'Comment 67: 2022 2:42 PM *To:* Kennedy\', "Comment 68: Bob <BKennedy@deheus.com> *Subject:* DGS-8062 Dispatches not processed in DHP{color} |{color:#ffffff} 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 69: \'Good. Thank you.Regards\']"]\nRelated Issues:\n[\'DGS-7949\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8061\n\n### Instruction:\nThere is sample result in DHC MM BU. However, we got informed from Formulation Department that they cannot see result started from 25-Nov-2022.\r\nPlease check. I do attached screenshot of DHC for your reference\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: \'We are unable to log on to your VPN", "Comment 4: !image-2022-12-14-08-12-51-716.png!\'", "Comment 5: \'Hi", \'Comment 6: We are looking into it now. We will update you back about access.Best Regards\', "Comment 7: Clara\'", \'Comment 8: \\\'Please set up the Forticlient VPN as per attached and try for connection with your current VPN user. Configuration of Preshare key is "Deheus@IPsec" !IPsec-2.jpg|thumbnail!!IPsec-3.jpg|thumbnail!!IPsec-1.jpg|thumbnail!\\\'\', "Comment 9: \'!image-2022-12-14-13-45-15-586.png!\'", "Comment 10: \'!image-2022-12-14-13-46-09-343.png!\'", "Comment 11: \'!image-2022-12-14-13-53-13-478.png!\'", "Comment 12: \'!image-2022-12-14-14-21-02-902.png! nie dla dla tego sample analisysFROM [DHP_YAN].[dbo].[SampleAnalysis]-- where SAn_SRgId= 230087\'", "Comment 13: \'You mentioned in task title about DHH", \'Comment 14: but in other task you mentioned DHC\', \'Comment 15: also DHc is visible in screenshoot\', "Comment 16: you missed results in DHC and we should focus on sample registers without results ?\'", \'Comment 17: "There is 2 issues. This Ticket is for DHC to DHH for all sample result. The other ticket is from DHP to DHC for Aqua Factory (57) result only.As I mention\', "Comment 18: Formulation Department say they cannot see the result on DHH. That\'s why I raise it. Last night", \'Comment 19: Formulation Department informed us that they can see it on DHH. So\', \'Comment 20: you can close this ticket. Please investigate for other ticket. Thanks"]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8060\n\n### Instruction:\nThere is all sample result from 57- Aqua Plant result not in DHC. Starting from late November. There is result on DHP been executed. \r\nFor Example: \r\nSample Code - 57221201001.\r\n\r\nI do attached screen shot for more details.\r\n\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: \'We are unable to log on to your vpn!image-2022-12-14-08-08-21-125.png!\'", "Comment 4: \'Hi", \'Comment 5: We are looking into it and will update you back Best Regards\', "Comment 6: Clara\'", \'Comment 7: \\\'Please set up the Forticlient VPN as per attached and try for connection with your current VPN user. Configuration of Preshare key is "Deheus@IPsec" !IPsec-2.jpg|thumbnail!!IPsec-3.jpg|thumbnail!!IPsec-1.jpg|thumbnail!\\\'\', "Comment 8: \'https://helpdesk.kotrak.com/browse/DGS-6936\'", "Comment 9: \'SELECT TOP (1000) [SAR_Id] ,[SAR_SAnId] ,[SAR_Identity] ,[SAR_Date] ,[SAR_Type] ,[SAR_ForeignId] ,[Sar_plantid] FROM [DHP_YAN].[dbo].[SampleAnalysisResult] where sar_sanid=117766SELECT TOP (1000) [SAR_Id] ,[SAR_SAnId] ,[SAR_Identity] ,[SAR_Date] ,[SAR_Type] ,[SAR_ForeignId] ,[Sar_plantid] FROM [DHP_YAN].[dbo].[SampleAnalysisResult] where sar_sanid=117766\'", \'Comment 10: "W odróznieniu do zalinkowanego taska tutaj nie zgasdza się plat it na analisys resultselect a.SAn_Id,r.SRg_PlantId,a.SAn_PlantId,AR.sar_plantid,r.SRg_Codefrom SampleRegister R join SampleAnalysis A on A.SAn_SRgId = srg_id left join SampleAnalysisResult AR on AR.SAR_SAnId = A.SAn_Idwhere (Sar_plantid <>SAn_PlantId)and SAn_CreateDate>\\\'2022-12-01 00:00\\\'!image-2022-12-15-10-34-05-515.png!"\', "Comment 11: \'Co do ostatniego komentarza ten sar_Plantid jest dobrze mają 55 wszystkie - są dwa planty w jednym.!image-2022-12-15-19-03-48-839.png!Zostały przesłane analizy i wyniki około 15 dziś ich czasu !screenshot-1! I błędy się skończyły dla dhcservice o tej godzinie - Required entity was not found !screenshot-2! Teraz dane są w DHC: !screenshot-3! \'", "Comment 12: \'Please verify and send a feedback - thank you. !screenshot-4! \'", "Comment 13: \'All are ok now. May I know the root cause of this issue?\'", "Comment 14: \'We were unable to find a clear reason why the samples did not originally pass", "Comment 15: after restarting the services the results did pass. It is likely that there may have been some problems with the infrsatructure.Can the request be closed?\'", "Comment 16: \'Sure. Please close the request. \']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8059\n\n### Instruction:\nWe have problem to remove one barcode from VT using mobile, system is showing error message when I try to remove.\r\nThese barcode was loaded by mobile picking without use of a bag label but they loadade wrong barcode and was trying to remove.\r\nCould you check why we have this error and fix it?\r\n\r\nThank you\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: " !screenshot-1! {code:java}SELECT * FROM [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseOrderElements] where id=\\\'B982C7F2-63BF-4822-AD3B-AC21E4BEE993\\\'SELECT * FROM [DHPlantWmsBusinessLogicMain].[dbo].[VehicleTicketElements] where id=\\\'39E87E76-2B71-4C0E-82D3-B1B5BD969D8C\\\'{code}"\', \'Comment 4: \\\'{code:java}2022-12-13 13:51:40 (f3d4b686-79d6-47a2-9388-6a9286b60cdc/Plant.WMS.BusinessLogic/BR-1-SV-VM0604/968/218) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 5: "host": { "Value": "br-1-sv-vm0604.mubbrasil.local:85"\', \'Comment 6: "HasValue": true\', \'Comment 7: "Host": "br-1-sv-vm0604.mubbrasil.local"\', \'Comment 8: "Port": 85 }\', \'Comment 9: "path": "/api/WarehouseDispatch/withdrawUnitLoadFromWarehouseDispatchOrder"\', \'Comment 10: "queryString": []\', \'Comment 11: "requestBody": "{\\\\\\\\"warehouseOrderId\\\\\\\\":\\\\\\\\"b982c7f2-63bf-4822-ad3b-ac21e4bee993\\\\\\\\",\\\\\\\\"unitLoadBarcode\\\\\\\\":{\\\\\\\\"code\\\\\\\\":\\\\\\\\"85-W00XQ8\\\\\\\\"}}"}.System.InvalidOperationException: Sequence contains more than one element at System.Linq.ThrowHelper.ThrowMoreThanOneElementException() at System.Linq.Enumerable.TryGetSingle[TSource](IEnumerable`1 source\', \'Comment 12: Boolean& found) at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source) at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.GetByExpression(Expression`1 expression) at Plant.WMS.BusinessLogic.Infrastructure.Persistance.WarehouseDispatches.WarehouseDispatchRepository.GetWarehouseDispatchForWarehouseOrderAndUnitLoadBarcode(AggregateId warehouseOrderId\', \'Comment 13: AggregateId unitLoadId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.Persistance\\\\\\\\WarehouseDispatches\\\\\\\\WarehouseDispatchRepository.cs:line 87 at Plant.WMS.BusinessLogic.Application.WarehouseDispatches.WarehouseDispatchService.GetWarehouseDispatchOrThrow(AggregateId warehouseOrderId\', \'Comment 14: AggregateId unitLoadId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseDispatches\\\\\\\\WarehouseDispatchService.cs:line 1054 at Plant.WMS.BusinessLogic.Application.WarehouseDispatches.WarehouseDispatchService.WithdrawUnitLoadFromWarehouseDispatchOrder(AggregateId warehouseOrderId\', \'Comment 15: Barcode unitLoadBarcode) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseDispatches\\\\\\\\WarehouseDispatchService.cs:line 445 at Plant.WMS.BusinessLogic.Application.WarehouseDispatches.Handlers.WithdrawUnitLoadFromWarehouseDispatchOrderCommandHandler.<>c__DisplayClass5_0.<Handle>b__0() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseDispatches\\\\\\\\Handlers\\\\\\\\WithdrawUnitLoadFromWarehouseDispatchOrderCommandHandler.cs:line 39 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.WarehouseDispatches.Handlers.WithdrawUnitLoadFromWarehouseDispatchOrderCommandHandler.Handle(WithdrawUnitLoadFromWarehouseDispatchOrderCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseDispatches\\\\\\\\Handlers\\\\\\\\WithdrawUnitLoadFromWarehouseDispatchOrderCommandHandler.cs:line 44 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.WarehouseDispatchController.WithdrawUnitLoadFromWarehouseDispatchOrder(WithdrawUnitLoadFromWarehouseDispatchOrderViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\WarehouseDispatchController.cs:line 203 at lambda_method358589(Closure \', \'Comment 16: Object \', \'Comment 17: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 18: ObjectMethodExecutor executor\', \'Comment 19: Object controller\', \'Comment 20: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 21: Scope& scope\', \'Comment 22: Object& state\', \'Comment 23: 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 24: Scope& scope\', \'Comment 25: Object& state\', \'Comment 26: 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 27: Task lastTask\', \'Comment 28: State next\', \'Comment 29: Scope scope\', \'Comment 30: Object state\', \'Comment 31: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 32: Task task\', \'Comment 33: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 34: Task task\', \'Comment 35: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 36: Task requestTask\', \'Comment 37: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', "Comment 38: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'", "Comment 39: \'[~piotr.gaczorek@kotrak.com],Problem istnieje wtedy gdy zeskanowana paleta została więcej niż raz (czyli dwa razy częściowo zeskanowali paletę). Nie wiem dlaczego tak robią. Zawsze mogą częściowo sprzedać raz.Funkcjonalność którą używają została dostarczona w https://helpdesk.kotrak.com/browse/GDC-224. Z racji tego że nie w scope nie było żadnej mowy o wycofaniu a funkcjonalność została dostarczona tylko pod NL jeżeli klient chce to w takiej formie to używać to musi zgłosić GDC.\'", "Comment 40: \'Hello. This problem exists when the scanned pallet has been scanned more than once (i.e. partially scanned the pallet twice).It is always possible to partially sell once.GDC is required for this to work as it is (as reported in this task).This functionality has been provided but for NL - GDC-224.Regards\'", "Comment 41: \'All information was provided in the last comment.The issue is closed.\']"]\nRelated Issues:\n[\'DAP-13096\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8058\n\n### Instruction:\nCommunication not working (trips not arriving in DHP), dispatches not processed in DHP, code 500 errors in DHP UI (same type of issues occurred in Utrecht today)\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 restarted application but i didn\\\'t get error 500.Please check if there are any missing documents (please provide examples).Thank you."\', "Comment 3: \'This ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8057\n\n### Instruction:\nWhen we move feed to the next round this should be maximised by the weight of the original delivery. \r\n\r\nNot we can move 5.000kg for instance while the original delivery was only 2.000kg.\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: \'[~mbovene@deheus.com]this is handled in the newest version of Feed Sale that will be deployed on PROD on Monday. I will close the task when deployment is completed.\'", "Comment 3: \'[~ewa.mucha@kotrak.com]you can close this task. Update is working on PROD right now ;).\'", "Comment 4: \'Great! I close the task.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8056\n\n### Instruction:\nHi\r\n\r\nWe had two DHC x ERP integration erros last week about PLRs:\r\n\r\nPLR LotNumber 0856051222001\r\nPLR LotNumber 0856051222003\r\n\r\nThen we found the reason: There were these two PLRs from Guararapes that had substitutes in PLR, however, DHC and ERP received the original item instead the substitue.\r\n\r\nCould you please fix that?\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.Regards\'", "Comment 3: \'!image-2022-12-14-08-58-33-063.png!A po itemid dla substitute:!image-2022-12-14-09-13-13-620.png! !image-2022-12-14-08-58-33-063!!image-2022-12-14-09-13-13-620!\'", "Comment 4: \'!image-2022-12-14-09-02-28-353.png!\'", "Comment 5: \'Hi Maicon,I have analised your case. To solve this issue in ERP system", \'Comment 6: you need to replace item. Integration with ERP does not integrate substitutes. For this issue\', \'Comment 7: a GDC task needs to be raised.Please\', "Comment 8: let us know if this solution is fine for you.Regards\'", \'Comment 9: "Hi AleksandraI don\\\'t see this as an issue on DHC x ERP integration\', \'Comment 10: but an issue on DHP x DHC integration.Take a look at the screenshot from DHC application\', \'Comment 11: the item in DHC is also wrong.!image-2!"\', "Comment 12: \'!image-2022-12-14-14-35-22-300.png!!image-2022-12-14-14-35-22-300!\'", "Comment 13: \'Having analised for example PLR:!image-2022-12-14-14-22-47-544.png!Substitutes are defined here:!image-2022-12-14-14-23-58-221.png!What I can do is to chnage Item id under db for the PLR preview (which in fact means there will be other item on PLR element) and this will be resent to ERP.As I mentioned before", \'Comment 14: with the view above,Integration with ERP does not integrate substitutes. For this issue\', \'Comment 15: a GDC task needs to be raised.Please\', "Comment 16: let me know what should be done on our side.\'", \'Comment 17: "Hi AleksandraNow I understood. Thank you.However the origin of the issue in DHC x ERP integration is not a case of GDC but a fixing on the functionality.As you can see in the attached screenshot the documentation about DHCxERP integration and it was already covered.We didn\\\'t notice this error before because no one raised their hand to ask for help untill now.But seems that DHC are not sending this information for a long time.Could you please help us?Thank you!image-3!!image-4!"\', \'Comment 18: \\\'{code:java}2022-12-05 17:29:54,686 [142] DEBUG Evolution.DHCERPService.LocalLimsIntegration.Lims.Lims [C:\\\\\\\\Repository\\\\\\\\erpS\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.LocalLimsIntegration.Lims\\\\\\\\Lims.cs:366] - Lims DTO: {"BatchNo":"0856051222003","PlantID":"f7cf4447-16a6-4972-8757-09db240a58a6","ItemID":"3471b5d7-d763-4e9f-a638-2220a235f5b7","ItemVersion":0,"Quantity":"2100.000000","QuantityUnits":"kg","ManufacturingDate":"2022-12-05T17:18:42","CustomerRequirements":[],"XmlType":null}2022-12-05 17:29:55,249 [16] DEBUG Evolution.DHCERPService.LocalLimsIntegration.Lims.Lims [C:\\\\\\\\Repository\\\\\\\\erpS\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.LocalLimsIntegration.Lims\\\\\\\\Lims.cs:374] - Lims result: {"Success":true,"ErrorMessage":"","XmlType":"_WS_In_Common_DTO.serviceCallResponseDTO"}2022-12-05 17:29:55,280 [142] DEBUG Evolution.DHCERPService.LocalLimsIntegration.Commands.ProductionLotReportSavedCommand [C:\\\\\\\\Repository\\\\\\\\erpS\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.LocalLimsIntegration\\\\\\\\Commands\\\\\\\\ProductionLotReportSavedCommand.cs:58] - Import OK!2022-12-05 17:29:55,280 [142] INFO Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [C:\\\\\\\\Repository\\\\\\\\erpS\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:64] - Message with command ProductionLotReportSave and object id e4724e3c-2173-4a37-8435-9174b423fae8 was sucessfully processed.{code}ItemID powinno pokrywać się z ID planta lub dhc?!image-2022-12-15-11-53-54-910.png!!image-2022-12-15-11-54-11-865.png!\\\'\', "Comment 19: \'Dear Maicon,Could you please provide me with correct example of substitute that integrated do ERP correctly?Regards\'", \'Comment 20: "Hi AleksandraI don\\\'t have such example because I was never informed about bugs on it.I\\\'m looking to the documentation from KOTRAK.Thank you"\', "Comment 21: \'Hi Maicon,So should I understood you have never used substitute before?Regards\'", \'Comment 22: "Hi AleksandraIf you query the ProductionLotReportElementSubstitutes table\', \'Comment 23: you\\\'ll find a lot of cases.Thank you very much"\', "Comment 24: \'W opisie powołał się na dwa przykłady", \'Comment 25: zatem miałam prawo założyć\', \'Comment 26: że nie zadziałało dwa razy. Przegadałam z Przemkiem\', \'Comment 27: w Brazylii nie mają takiej integracji substitues to ERP obsłużonej\', \'Comment 28: a dokument\', \'Comment 29: którym macha Maicon opisuje możliwości nie założenia deploymentu. !image-2022-12-16-14-59-16-085.png!Tak w tabeli DHC jest wiele substitutes\', \'Comment 30: ale nie ma powiązania do dokumenty ERP\', \'Comment 31: o którego poprawny przykład pytałam wcześniej.!image-2022-12-16-15-08-41-851.png!Obejrzałam dokument mappingu i nie wiem\', "Comment 32: co Maicon sobie ubzdurał\'", "Comment 33: \'Hej [~marcin.kleszcz@kotrak.com]Jak opisałam wyżej", \'Comment 34: wyjaśnisz proszę Maiconowi\', \'Comment 35: że to\', \'Comment 36: czym macha to możliwości a nie deployment? I że to nigdy nie działało\', "Comment 37: bo tego zwyczajnie nie mają? :)\'", "Comment 38: \'Hej,[~aleksandra.przybylek@kotrak.com] jeśli tak faktycznie jest", \'Comment 39: że jest to opisane w dokumencie technicznym\', \'Comment 40: ale nie ma jeszcze takiej integracji do ERP\', \'Comment 41: to tak też napisz\', "Comment 42: że taka integracja nie była do tej pory realizowana.\'", \'Comment 43: "Hi Maicon,Regarding to:{color:#0747a6}_If you query the ProductionLotReportElementSubstitutes table\', "Comment 44: you\'ll find a lot of cases.{color:#172b4d}-{color}_ {color:#172b4d}yes but I have asked about cases / substitutes that integrated to ERP.{color}{color}{color:#0747a6}{color:#172b4d}I have consulted this case and", \'Comment 45: as I mentioned before\', \'Comment 46: the document you are showing only describes the possibility of such integration. Integration of substitutes has not been released so far.{color}{color}{color:#0747a6}{color:#172b4d}Regards{color}{color}"\', \'Comment 47: "HiThank you for the information. I\\\'ll raise a GDC for KOTRAK to deliver what is in the documentation created by KOTRAK itself.Thank you very much.You can close this task."\', "Comment 48: \'Hi,Thank you.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8055\n\n### Instruction:\nSee also : DGS-8046 and DGS-8048\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.In DGS-8048 I asked you could you anserw!image-2022-12-13-15-16-34-151.png!Regards\'", "Comment 2: \'Ok I can see this is the same situation as dgs-8046\'", "Comment 3: \'Please check both items ", \'Comment 4: should be ok\', "Comment 5: also if there were recipes ( for 080587 were ) please asked dhh holding to send them again.,\'", "Comment 6: \'May we close the task?\'", "Comment 7: \'Link 080587-B1000 and 080583-B1000 are still present in Premix!image!!image-1!\'", "Comment 8: \'Please bring details what do you need. We changed base item.you want to deleted items from DHC? Or unlinked them - if we do that that means that no order ", \'Comment 9: no recipe etc would not be send to DHP.You may do it by yourself from the application.Please go to details by click "link ite"m in dhc and then use buttons to unlink the itemUsually when you have item with code 080587.nl it has baseitem 080587 and linked other items start with 080587.!image-2022-12-15-12-11-09-627.png!\\\'\', "Comment 10: \'According the list somebody has delete the base items 080597-B1000 and 080587-B1000 so it shlould be correct.!image-2!!image-3!\'", "Comment 11: \'Hi,To conclude", "Comment 12: can we close this task?Regards\'", "Comment 13: \'I am waiting off the conformation off the requester\'", "Comment 14: \'Ticket can be closed!image-4!\']"]\nRelated Issues:\n[\'DGS-8048\', \'DGS-8046\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8054\n\n### Instruction:\nIn DHP Utrecht user server error 500 in DHP and sales orders do not seem to arrive. Can you check if DHP is working ok?\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 kindly inform you that wecurrentlyare processing another Priority1 task.DGS-8051We will revert to processing your task as soon as possible.Regards\'", "Comment 4: \'!image-2022-12-13-15-12-56-684.png!\'", "Comment 5: \'Good morning,Services have been restarted in the DPH application.The message is currently not showing.Are you expecting additional action on this request ?Can we close this incident ?Regards\'", "Comment 6: \'[[DHP 3.0] aplikacji i rabbit kolejność uruchomienia.|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#%5bDHP%203.0%5d%20%20aplikacji%20i%20rabbit%20kolejno%C5%9B%C4%87%20uruchomienia.&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{0589CBBE-2349-4B7D-9707-381B3E7C7F9C}&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%5BDHP%203.0%5D%20%20aplikacji%20i%20rabbit%20kolejno%C5%9B%C4%87%20uruchomienia.%7C0589CBBE-2349-4B7D-9707-381B3E7C7F9C%2F%29])\'", "Comment 7: \'We will check if all processes are working ok again\'", "Comment 8: \'We see same kind of issues in Maasbracht. Do you need a separate ticket for this? Or can you check it in this ticket?\'", "Comment 9: \'Please create new one.Thank you.\'", "Comment 10: \'This ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8053\n\n### Instruction:\nThe formula needs to be changed:\r\n\r\nFeed profit = Total net value of SLAC – (Total net value of Item group DOC’s) – (Total net value of all items codes in green) – Total net value of Feed \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: \\\'MitchWhat items codes do you mean "(Total net value of all items codes in green) "?Could you please confirm this is related only to MAS NL?\\\'\', "Comment 3: \'This is for the MAS and MAS BE.Thank you for asking.I have added the attachment", "Comment 4: I forgot to add it.!image![^RE_ Item codes MAS_xlsx.msg] _(236 kB)_\'", \'Comment 5: "[~mbovene@deheus.com]should we mark somehow Item Cards which are green on list?It\\\'s better to keep somewhere this information that we should collect data from that kind of items to some calculations.Maybe we can add checkbox on Item Card \\\'Include in Feed profit\\\' (or something like this) or add new dictionary to allow in the future adding or removing items which should be possible to include in calculations.I\\\'m not sure this values will be changed often or not\', \'Comment 6: but it will be more flexible if we will not hard code these item in procedures to calculations and allow to add/remove items when we need.What do you think?"\', \'Comment 7: "I totally agree. I don\\\'t think it will change very often but it is good to have some flexibility."\', \'Comment 8: "Ok\', \'Comment 9: great\', \'Comment 10: so we\\\'ll add to Item Card checkbox\\\'Include in Feed profit\\\'."\', \'Comment 11: "Zostało dodane pole Itm_IntColumn9 na Item Card o nazwie\\\'Include in Feed profit\\\' i dla wskazanych itemów zostało ono uzupełnione.Na potrzeby wyliczania danych z ww. Itemów zostały dodane funkcje:[dbo].[KR_TechResults_TotalIncludeFeedProfitItems][dbo].[KR_TechResults_TotalIncludeFeedProfitItems_MASBE]Zostały zmodyfikowane procedury:[dbo].[KR_calculatetechresults][dbo].[KR_calculatetechresults_MASBE]Procedury korzystają ze wspomnianych wcześniej funkcji."\', \'Comment 12: "On Item Card has been added field\\\'Include in Feed profit\\\' and was marked for Items indicated on green on the list for sectors MAS NL and MAS BE (35 items in each sector). This field is visible only for user = Administrator.Changes with new formula have been implemented on production database IBIP_DH.Please verify on one or more documents that calculations for Feed profit is correct in sectors MAS NL and MAS BE."\', "Comment 13: \'Damian", "Comment 14: to be verified!image-2022-12-19-14-06-18-633.png|width=1590,height=364!!image-2022-12-19-14-07-02-258.png!\'", "Comment 15: \'Maybe a plus and a minus are mixed up by accident. On the other hand I think the total value from the formula is divided by the number of broilers. While in the formula as provided by me (based on input from Oscar) this isn’t. The provided formula was:Feed profit = Total net value of SLAC – (Total net value of Item group DOC’s) – (Total net value of all items codes in green) – Total net value of FeedOur interpretation of the numbers (maybe that is were it went wrong): Feed profit (can be positive or negative base on the outcome) = Total net value of SLAC (positive value) – Total net value of Item group DOC’s (positive value) – Total net value of all items codes in green (positive value) – Total net value of Feed (positive value).The logic of this formula is that a farmer needs to know what his profit it when his costs (docs", \'Comment 16: feed\', "Comment 17: most of the expenses) are subtracted from his revenues (SLAC).Regards,Mitch\'", "Comment 18: \'In addition", "Comment 19: they would like to see this profit per broiler.\'", \'Comment 20: \\\'The outcome of the formula should be diveded by "Number of first loaders (quantity)+Number of alle loaders (quantity)".\\\'\', \'Comment 21: "Ok\', \'Comment 22: so it means that we should take always absolute value of: * Total net value of SLAC * Total net value of Item group DOC’s * Total net value of all items codes in green * Total net value of FeedIs it correct that in formula expression (Total net value of all items codes in green) contains item = \\\'SLAC\\\' (on list item \\\'SLAC\\\' is marked on green)?It means that we at firs sum all \\\'SLAC\\\' in*Total net value of SLAC*and then in *(Total net value of all items codes in green)* substract sum of \\\'SLAC\\\' and other items marked on green.Feed profit = *Total net value of SLAC* – (Total net value of Item group DOC’s) – *(Total net value of all items codes in green)* – Total net value of FeedFor case of document ID = 78127 there is: * Total net value of SLAC =276893,20 * Total net value of Item group DOC’s =26122,50 * Total net value of all items codes in green =275054,26 * Total net value of Feed =156502,62 * Number of first loaders (quantity) = 0 * Number of alle loaders (quantity) = 63773so result of Feed profit formula will be after rounding for conditions above =-2.83"\', "Comment 23: \'* We should indeed take absolute values of the four SUMS you mention. Note", \'Comment 24: it could be that some of the parts are with a minus when you look at the green item codes.* No\', \'Comment 25: that is a mistake. The SLAC should not be included in the green item codes.* Almost all your SUMS are correct\', "Comment 26: however the Total net value of the items in green will be 1838,94 (you need to exclude SLAC)\'", \'Comment 27: "Calculation have been modified and \\\'SLAC\\\' is now excluded from the \\\'Total net value of all items codes in green\\\'Now value of Feedprofit = 1,45Please verify that is correct righ now."\', "Comment 28: \'Yes indeed\'", "Comment 29: \'Ok", "Comment 30: so I close the task.\']"]\nRelated Issues:\n[\'DGS-8215\', \'DGS-8428\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8052\n\n### Instruction:\nProduct created by mistake as bulk. And so it was produced and confirmed. Subsequently, a colleague noticed the mistake, corrected it instead of buulk in bagged.\r\n\r\nNow we have the produced quantity on stock, which instead of a 20 kg bag is on stock as bulk.\r\n\r\nHow can we fix it, can you put the entire amount of product 30440140-B20 to be bagged?\n\n### Response:\n["Comment 1: [\'!Screenshot_1!!Screenshot_3!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Performing changes by inventory.For bullk stock units change to zero.For bagged stocks adding what\\\'s taken out of the bulk stock units?"\', "Comment 4: \'Hello", "Comment 5: can we get feedback for our last comment?\'", "Comment 6: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8051\n\n### Instruction:\nLot report do not come into DHP\r\nPossible error included\r\n\r\nSee also : DGS-8050\r\n\r\n\n\n### Response:\n["Comment 1: [\'[^Batchperformance_202212090068_BL01_1_d1c2b00d-cc79-4203-b99a-6c57a101a152_35168067.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_2_d1c2b00d-cc79-4203-b99a-6c57a101a152_35170346.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_3_d1c2b00d-cc79-4203-b99a-6c57a101a152_35252533.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_4_d1c2b00d-cc79-4203-b99a-6c57a101a152_35256933.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_5_d1c2b00d-cc79-4203-b99a-6c57a101a152_35264995.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_6_d1c2b00d-cc79-4203-b99a-6c57a101a152_35268376.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_7_d1c2b00d-cc79-4203-b99a-6c57a101a152_35272898.xml] _(13 kB)_[^Batchperformance_202212090068_SL06_1_10_4b3785c2-9349-4c80-92e0-8757133e5ade_34250438.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_11_4b3785c2-9349-4c80-92e0-8757133e5ade_34251532.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_2_4b3785c2-9349-4c80-92e0-8757133e5ade_34221064.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_3_4b3785c2-9349-4c80-92e0-8757133e5ade_34223244.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_4_4b3785c2-9349-4c80-92e0-8757133e5ade_34227212.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_5_4b3785c2-9349-4c80-92e0-8757133e5ade_34230483.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_6_4b3785c2-9349-4c80-92e0-8757133e5ade_34232298.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_7_4b3785c2-9349-4c80-92e0-8757133e5ade_34237321.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_8_4b3785c2-9349-4c80-92e0-8757133e5ade_34237471.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_9_4b3785c2-9349-4c80-92e0-8757133e5ade_34243429.xml] _(2 kB)_!image!\'", "Comment 2: \'Hi,Could you please provide us with Production Lot Report Number?Where does this message come from? Which database? !image-2022-12-13-12-12-23-640.png!Regards !image-2022-12-13-12-12-23-640!\'", "Comment 3: \'These lot reports are coming from PCS (KSE)\'", "Comment 4: \'Okay", "Comment 5: but what are Production Lot Reports numbers?\'", "Comment 6: \'In the XML files are the numbers of the lot reports present.!image-1!\'", "Comment 7: \'This number is a part off the lot report name in DHP\'", "Comment 8: \'We are investigating\'", "Comment 9: \'!image-2022-12-13-14-53-19-686.png!\'", "Comment 10: \'{code:java}System.Net.WebException: The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.GetResponse() at PCS.Repository.Netherlands.Repositories.BaseSaveRepository`6.Save(Package`1 package", "Comment 11: ActionCode action) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPS25-PCSEV139-JOB1\\\\\\\\PCS.Repository.Netherlands\\\\\\\\Repositories\\\\\\\\BaseSaveRepository.cs:line 70{code}\'", \'Comment 12: " !screenshot-4! {code:java} FROM [DH_Exchange_NL_PROD].[dbo].[ProductionLotReportHeader] where PLH_Id in(\\\'87014110122222217\\\',\\\'87014110122222183\\\') select * FROM [DHP_NL_PROD].[dbo].[ProductionLotReportHeader] where PlH_LotNumber in(\\\'87014110122222217\\\',\\\'87014110122222183\\\'){code} !screenshot-5! nie ma w dhp. exchange jest."\', "Comment 13: \'PLRy z 10.12 \\\\r87014110122222183\\\\r87014110122222217\\\\rsą w exchange", \'Comment 14: nie ma dhp\', "Comment 15: prośba o pomoc w ustaleniu przyczyny. \\\\rW logach są błędy ale nie jestem stanie ustalić czy pod te.\\\\rDzięki.\'", "Comment 16: \'I have one question,can it wait until tomorrow morning?We need analysis results from our developers.\'", "Comment 17: \'brak receptury w plancie: !screenshot-6! usunięta z bazy dhp: !screenshot-7! \'", \'Comment 18: "Please resend lot reports to DHP and check.Please send a feedback.Recipe for item was missing in DHP and it\\\'s seems to have been removed from the database."\', "Comment 19: \'Total weight off lot report is visible but used raw material is not present. Zero KG.Track and tracing is not posible without consumption off raw material,!image-2!\'", "Comment 20: \'Please correct the used consumption off raw material.\'", "Comment 21: \'We are working on it\'", \'Comment 22: "Only on PLR \\\'87014110122222183\\\' or on PLR\\\'87014110122222217\\\' as well?"\', \'Comment 23: "Please\', \'Comment 24: verify\\\'87014110122222183\\\' and let me know"\', "Comment 25: \'The real quantity is stil zero\'", "Comment 26: \'We are checking\'", "Comment 27: \'Real quantity is fild in but the dosed quantity is now twice as mutch.!image-3!\'", \'Comment 28: "Please\', \'Comment 29: check\\\'87014110122222183\\\' now"\', \'Comment 30: "Please\', \'Comment 31: check\\\'87014110122222217\\\'"\', "Comment 32: \'{code:java} select * FROM [DHP_NL_PROD].[dbo].[PcsDosing] where DSN_PlEId in(SELECT PlE_Id FROM ProductionLotReportElement WHERE (PlE_PlHId = 254279 ))\\\\t\\\\tselect *\\\\t\\\\t FROM [DHP_NL_PROD].[dbo].[ProductionLotReportRelease] where PlR_PlEId in(SELECT PlE_Id FROM [DHP_NL_PROD].[dbo].[ProductionLotReportElement] where PlE_PlHId=254278) SELECT PlE_Id,* --delete FROM [DHP_NL_PROD].[dbo].[ProductionLotReportElement] where PlE_PlHId=254279 and PlE_RcEId is null\\\\t\\\\t{code}\'", "Comment 33: \' !screenshot-8! \'", "Comment 34: \'Lot report in DHC and not going to CDN.!image-4!\'", \'Comment 35: "PLR or VT? If VT\', "Comment 36: which of them:\'87014110122222183\' ,\'87014110122222217\' ?If none of them", \'Comment 37: please\', \'Comment 38: arise another task.Regards"\', \'Comment 39: "I have checked\', "Comment 40: and For PLR:87014110122222183\'", \'Comment 41: item 970125-B25!image-2022-12-19-10-50-21-745.png!There are documents in CDN:!image-2022-12-19-10-50-47-007.png!!image-2022-12-19-10-51-55-160.png!!image-2022-12-19-10-52-16-744.png!Please\', \'Comment 42: let me know what is the exact case.Regards !image-2022-12-19-10-51-55-160! !image-2022-12-19-10-52-16-744!"\', "Comment 43: \'It is about 87014110122222183.87014110122222217 is an wrong one and kan be deleted.\'", "Comment 44: \'Ok", \'Comment 45: but documents: JO\', \'Comment 46: IR+ and IR - related to PLR:87014110122222183 are generated in ERP XL as you can see on above screenshots.Please\', "Comment 47: let us know what is missing?Regards\'", \'Comment 48: "The problem is VT is not accepted.See ticket : DGS-8099 VT \\\'s are not going from DHC to CDN Please solve ticket DGS-8099 and close thics ticket "\', "Comment 49: \'Ticket DGS-8099 is under investigation.Regards\'", "Comment 50: \'[[DHP/Exchange] Bad Request 400 dla PLR - są w exchange nie wpadają do DHP|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baza%20wiedzy.one#%5bDHP/Exchange%5d%20Bad%20Request%20400%20dla%20PLR%20-%20s%C4%85&section-id=\\\\\\\\{B6BA0A4E-07B0-413E-A582-89B093FD9A36}&page-id=\\\\\\\\{7504D29D-9B42-4A26-81C2-0BE1CF27FE2C}&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%2FBaza%20wiedzy.one%7CB6BA0A4E-07B0-413E-A582-89B093FD9A36%2F%5BDHP%5C%2FExchange%5D%20Bad%20Request%20400%20dla%20PLR%20-%20s%C4%85%7C7504D29D-9B42-4A26-81C2-0BE1CF27FE2C%2F%29])\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8050\n\n### Instruction:\nLot report do not come into DHP \r\nPossible error included\r\n\r\n\r\n\n\n### Response:\n["Comment 1: [\'[^Batchperformance_202212090068_BL01_1_d1c2b00d-cc79-4203-b99a-6c57a101a152_35168067.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_2_d1c2b00d-cc79-4203-b99a-6c57a101a152_35170346.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_3_d1c2b00d-cc79-4203-b99a-6c57a101a152_35252533.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_4_d1c2b00d-cc79-4203-b99a-6c57a101a152_35256933.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_5_d1c2b00d-cc79-4203-b99a-6c57a101a152_35264995.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_6_d1c2b00d-cc79-4203-b99a-6c57a101a152_35268376.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_7_d1c2b00d-cc79-4203-b99a-6c57a101a152_35272898.xml] _(13 kB)_[^Batchperformance_202212090068_SL06_1_10_4b3785c2-9349-4c80-92e0-8757133e5ade_34250438.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_11_4b3785c2-9349-4c80-92e0-8757133e5ade_34251532.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_2_4b3785c2-9349-4c80-92e0-8757133e5ade_34221064.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_3_4b3785c2-9349-4c80-92e0-8757133e5ade_34223244.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_4_4b3785c2-9349-4c80-92e0-8757133e5ade_34227212.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_5_4b3785c2-9349-4c80-92e0-8757133e5ade_34230483.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_6_4b3785c2-9349-4c80-92e0-8757133e5ade_34232298.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_7_4b3785c2-9349-4c80-92e0-8757133e5ade_34237321.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_8_4b3785c2-9349-4c80-92e0-8757133e5ade_34237471.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_9_4b3785c2-9349-4c80-92e0-8757133e5ade_34243429.xml] _(2 kB)_!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hi,If this issue has the highiest priority", "Comment 4: you should raise an incident with priority P1 or P2.Could you please provide us with Production Lot Report Number?Where does this message come from? Which database?!image-2022-12-13-12-02-57-399.png!Regards\'", "Comment 5: \'I am closing this task as it is processing underDGS-8051.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8049\n\n### Instruction:\nDHC does not work. \r\nRestart of Business platform does not work: \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: "2022-12-13 10:05:37,299 [5] FATAL Evolution.BusinessPlatform.BusinessPlatform [(null)] - Some errors occured during platform startupSystem.Data.SqlClient.SqlException (0x80131904): Login failed for user \\\'dhbp\\\'. Reason: The password of the account has expired. at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 4: UInt32 waitForMultipleObjectsTimeout\', \'Comment 5: Boolean allowCreate\', \'Comment 6: Boolean onlyOneCheckConnection\', \'Comment 7: DbConnectionOptions userOptions\', \'Comment 8: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 9: TaskCompletionSource`1 retry\', \'Comment 10: DbConnectionOptions userOptions\', \'Comment 11: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 12: TaskCompletionSource`1 retry\', \'Comment 13: DbConnectionOptions userOptions\', \'Comment 14: DbConnectionInternal oldConnection\', \'Comment 15: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 16: DbConnectionFactory connectionFactory\', \'Comment 17: TaskCompletionSource`1 retry\', \'Comment 18: DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection\', \'Comment 19: DbConnectionFactory connectionFactory\', \'Comment 20: TaskCompletionSource`1 retry\', \'Comment 21: DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.Open()"\', "Comment 22: \'!image-2022-12-13-11-39-03-985.png!\'", "Comment 23: \'[~marta.litkie@kotrak.com]sprawdź z nimi", \'Comment 24: czy dane do bazy nie pozmieniali\', \'Comment 25: albo użytkowników\', "Comment 26: niech przyróca najlepiej stare haslo dla dhbp\'", \'Comment 27: "Hello we check that there are erorrs like :2022-12-13 10:05:37,299[5]FATAL Evolution.BusinessPlatform.BusinessPlatform[(null)]- Some errors occured during platform startupSystem.Data.SqlClient.SqlException (0x80131904): Login failed for user \\\'dhbp\\\'. Reason: The password of the account has expired.at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 28: UInt32 waitForMultipleObjectsTimeout\', \'Comment 29: Boolean allowCreate\', \'Comment 30: Boolean onlyOneCheckConnection\', \'Comment 31: DbConnectionOptions userOptions\', \'Comment 32: DbConnectionInternal& connection)could you bring bag the old password for database for userdhbp?"\', "Comment 33: \'Hello", \'Comment 34: what was the old password? Write please a login |{color:#0070C0} З найкращими побажаннями,{color}{color:#0070C0} Петро Світлик{color}{color:#0070C0} IT відділ{color}{color:#0070C0}{color}{color:#0070C0} {color}{color:#0070C0} Best regards,{color}{color:#0070C0} Petro Svitlyk{color}{color:#0070C0}{color}{color:#0070C0} IT department{color}{color:#0070C0} {color}{color:#0070C0}{color} [{color:#0070C0}{color}{color:#0563C1}servicedesk@koudijs.ua{color}{color:#0070C0}{color}|mailto:servicedesk@koudijs.ua]{color:#0070C0}{color} {color:blue} +{color}[{color:blue}{color}{color:#0563C1} + Teams+{color}{color:blue} {color}|https://teams.microsoft.com/l/chat/0/0?users=servicedesk@koudijs.ua]{color:blue} {color}+ : [{color:#0563C1}Viber{color}|viber://chat/?number=+380952855727] :{color:#0070C0}{color} [{color:#0070C0}{color}{color:#0070C0}WhatsApp{color}{color:#0070C0}{color}|https://wa.me/380952855727]{color:#0070C0}{color} : {color:#0070C0} +{color}[{color:#0070C0}{color}{color:#0563C1} + Telegram+{color}{color:#0070C0} {color}|https://t.me/psvitlyk]{color:#0070C0} {color}+ *{color:#006FB7} **{color}* | |{color:black}{color} !image003!{color:black}{color} | *{color:#006FB7} **{color}* *{color:#006FB7} *Коудайс Україна*{color}*{color:#006FB7} c{color}{color:#006FB7}.{color}{color:#006FB7}Хильчиці\', \'Comment 35: Золочівський р-н\', \'Comment 36: Львівська область{color} *{color:#006FB7} **{color}* *{color:#006FB7} *KoudijsUkraine*{color}*{color:#006FB7}{color}{color:#006FB7} Khylchytsi village\', \'Comment 37: Zolochiv district\', \'Comment 38: Lviv region{color}{color:#006FB7}{color} [{color:#006FB7}{color}{color:#0563C1}www.koudijs.ua{color}{color:#006FB7}{color}|http://www.koudijs.ua/]{color:#006FB7}{color}{color:black}{color}{color:#006FB7}{color} | |{color:black}{color} !image002!{color:black}{color} | *From:* Agnieszka Januszewska (Jira) <jira@kotrak.com> *Sent:* Tuesday\', \'Comment 39: December 13\', "Comment 40: 2022 12:45 PM *To:* Servicedesk <servicedesk@koudijs.ua> *Subject:* DGS-8049 DHC does not work \'", "Comment 41: \'For DHc db we had this password and login|dhbp|ZAQ!2wsx|login is dhbp\'", "Comment 42: \'IP: {color:#242424}10.106.25.32{color}{color:#242424} 10.106.25.33{color} ?\'", "Comment 43: \'!image-2022-12-13-13-02-06-869.png!\'", "Comment 44: \'Przy probie logowanai do bazy danych powpowiedziało mi zmiane hasla !image-2022-12-13-14-11-20-436.png!\'", "Comment 45: \'Did you set password again: I am not able to change it during login!image-2022-12-13-14-11-20-436.png!\'", "Comment 46: \'Please check again", "Comment 47: we have updated the password to the same one!image001!\'", "Comment 48: \'Please check services have been started.\'", "Comment 49: \'Yes", \'Comment 50: running\', "Comment 51: thanks\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8048\n\n### Instruction:\nRemove linked item 080587-B1000 in Premix\r\n\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: \'\'", "Comment 4: \'If I understand correctly", "Comment 5: you want baseitem to be 080587 instead of 080587-b1000?Do you give the shuffle a higher priority p2? p1?!image-2022-12-13-11-52-01-301.png!\'", \'Comment 6: "select *from dhhitems where code like \\\'080587\\\'select * from items where code like \\\'080587\\\'--update DhhItems--set BaseItemId=--\\\'BDCFBF6C-1B0C-423D-8351-AEE2B33608A6\\\'--where code like \\\'080587\\\'"\', "Comment 7: \'Linked DHC items 080587-B1000 and 080583-B1000 must be deleted.This can not be done using a screen.!image-1!!image-2!\'", "Comment 8: \'We are processing this task indgs-8055", "Comment 9: so this task will be closed.\']"]\nRelated Issues:\n[\'DGS-8055\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8047\n\n### Instruction:\nWe need to add a relation to the table on the NAS. \r\n\r\nWe already created an invoice SI-RTN/2022/0503. Can this be linked to the round whenever this relation is added?\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: \'Mitch", \'Comment 4: after the changes this will be visible in the Round etc. but still need to gain some more details before we start with the system update.I see the yellow relation\', \'Comment 5: did you add it to our Excel "Relation tables"? I cannot find it.Second question: in the yellow relation\', \'Comment 6: you wrote that Item Group = Slaughtery\', "Comment 7: while I see AFLE is Expenses. What should be the item code for the items handled in the new relation?Sales invoiceInvoice type: RegisteredCustomer: FarmerReference: NULLItem Group: ExpensesRound Category: Slaughtery\'", "Comment 8: \'I have added it our relationshop table on BOX again and saved it.I have changed the item group of AFLE to SlaughteryExpenses. It is mostly about AFLE. \'", \'Comment 9: "Dodana obsługa relacji w sektorze NAS - dodane na Rundzie\', \'Comment 10: na FS\', \'Comment 11: na zapytaniach do wydruku FS. Na S2P bez zmian\', \'Comment 12: bo to faktura \\\'Registered\\\'."\', "Comment 13: \'New relation in NAS has been added and adjusted on documents Round", "Comment 14: Financial Statement.\\\\r\\\\rNow that type of Sales Inovices will be visible on Round and Financial Statement.\'", "Comment 15: \'Great! Thank you", "Comment 16: Damian!\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8046\n\n### Instruction:\n Item 080583 is linked in DHC to BB item. Please relmove link.\r\n\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: \'Hi,Linking has been removed. You can link items correctly now.Please", "Comment 4: let us know if we can close this task.Regards\'", "Comment 5: \'This change was done in dgs-8055\']"]\nRelated Issues:\n[\'DGS-8055\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8045\n\n### Instruction:\nFor plant Andel multiple XML files are generated for SPS. A fix was done to prevent this (and installed for all plants). However, for Andel we still get these duplicates\r\nIssue does not seem to be related to multiple order lines:\r\n\r\nDe SO-37131 1 orderline\r\nDe SO-37028 2 orderlines\r\nDe SO-36457 1 orderline\r\n\r\nPlease / adjust check config\r\n\r\nSee examples of XML files below (from 12/12/2022)\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: \'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 4: \\\'[~aleksandra.przybylek@kotrak.com]- zmieniłem konfiguracje na AS400PluginConfiguration"GenerateOnVehicleTicketDispatchClosedEvent": false\', \'Comment 5: wygląda mi to że tutaj leżał problem.Niech sprawdzą czy mają jeszcze takie przypadki jeszcze\', "Comment 6: jakieś nowe od momentu zmiany.\'", "Comment 7: \'[~gedeon.kucharski@kotrak.com]Dzięki :)\'", "Comment 8: \'Hi,About 12:30 configuration has been changed. Please", "Comment 9: verify and let us know if new cases occured after 12:30.Regards\'", "Comment 10: \'Issue not found anymore. This ticket can be closed.\'", "Comment 11: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8044\n\n### Instruction:\nRonnie Thuis does have more options on the contract list witch I do not see on my screen. Do I have to reset layout?\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: \'Please uncheck minimize the ribbon in the context menu. !screenshot-1! \'", "Comment 4: \'Minimize the system was not selected. Selecting and deselecting the minimize did not make any difference.The only thing wich was working was : Reset layout.Afther this the fields had to be added munualy .\'", "Comment 5: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8043\n\n### Instruction:\nFor item 302010, recipe version 86 and 87 are sent for location 15 GFM. \r\nAccording to recipe overview, item is not linked. In Bestmix I see that item is linked. \r\n\r\nCan you check/fix linking of this item?\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: \'Please link this item - 9111 !screenshot-1! \'", "Comment 4: \'{color:#000000}Thanks", \'Comment 5: I was not aware of the missing RM. This ticket can be closed.{color} {color:#000000}{color} {color:#000000} {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black} Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Piotr Gaczorek (Jira) <jira@kotrak.com> *Sent:* Monday\', \'Comment 6: December 12\', \'Comment 7: 2022 4:21 PM *To:* Kennedy\', "Comment 8: Bob <BKennedy@deheus.com> *Subject:* DGS-8043 Recipe for item 302010 not accepted because it not linked. Item is linked{color} |{color:#ffffff} 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} |\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8042\n\n### Instruction:\nHow to select a total overvieuw of Service Request - NL (Compound Feed)\r\nNot possible to select \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: \'Sudenly service request is added!image-1!\'", "Comment 4: \'Only my own ticket are visible.!image-2!\'", "Comment 5: \'Hello Bert,We added you to the request participants section and now you are able to select all open tickets. Starting today you will be added automatically to all new tickets from NL.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8041\n\n### Instruction:\nHi,\r\nWe can not receive Recipes from DHH to DHC.\r\nPlease kindly help check: Cần Thơ Factory(ID:437) with Versions:\r\n91C5006-04 V8\r\n91C5006-05 V10\r\n91C5007A-05 V11\r\n90C8004-2C V1\r\n90C8005-2C V4\r\n Note: Put P1 because need for production\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: \'{code:java}2022-12-12 17:18:27,974 [52] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Dictionaries.Recipes.Events.RecipeSaveEvent RecipeId: 228555d8-6206-4399-8e70-c2f6f229fc26", \'Comment 3: HasError: True\', \'Comment 4: Reason:System.InvalidOperationException: The operation failed: The relationship could not be changed because one or more of the foreign-key properties is non-nullable. When a change is made to a relationship\', \'Comment 5: the related foreign-key property is set to a null value. If the foreign-key does not support null values\', \'Comment 6: a new relationship must be defined\', \'Comment 7: the foreign-key property must be assigned another non-null value\', \'Comment 8: or the unrelated object must be deleted. at System.Data.Entity.Core.Objects.ObjectContext.PrepareToSaveChanges(SaveOptions options) at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesInternal(SaveOptions options\', "Comment 9: Boolean executeInExistingTransaction) at System.Data.Entity.Core.Objects.ObjectContext.SaveChanges(SaveOptions options) at System.Data.Entity.Internal.InternalContext.SaveChanges() at System.Data.Entity.Internal.LazyInternalContext.SaveChanges() at System.Data.Entity.DbContext.SaveChanges() at Evolution.DHCountry.Infrastructure.Recipes.RecipeChangedHandler.OnHandle(RecipeChangedMessage recipeMessage) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHC-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry.Infrastructure\\\\\\\\Recipes\\\\\\\\RecipeChangedHandler.cs:line 80] to publisher [Evolution.Events.EventPublisher] under domain context [6ea48361ad5648e99f5397492bf619ba]{code}\'", \'Comment 10: "Hello Hardy,We don\\\'t have access below servers IP 113.161.145.252:3370IP 10.84.1.22!image-2022-12-12-11-27-50-715.png!Regards"\', "Comment 11: \'which user you want to login?\'", "Comment 12: \'Apac\\\\\\\\Piotr.Gaczorek Apac\\\\\\\\aprzybyłekApac\\\\\\\\akozak kotrak11@apac.corp.deheus.com kotrak12@apac.corp.deheus.com kotrak13@apac.corp.deheus.com kotrak14@apac.corp.deheus.com\'", "Comment 13: \'Please try\'", "Comment 14: \'Sorry", "Comment 15: this account no accessPlease refresh this acount Apac\\\\\\\\Piotr.GaczorekApac\\\\\\\\aprzybyłekIP 113.161.145.252:3370IP 10.84.1.22!image-2022-12-12-11-42-58-460.png!\'", "Comment 16: \'!image!\'", "Comment 17: \'Please try\'", "Comment 18: \'I need connect to server 113.161.145.252:3370!image-2022-12-12-11-59-55-214.png!IP 10.84.1.22 OK\'", "Comment 19: \'from Puclic remote you can try with IP: 10.84.1.16\'", "Comment 20: \'!image-1!\'", "Comment 21: \'Thank you for your accesses I sent again from DHH recipesCurrently", "Comment 22: the recipes appear in the DHC applicationRegards\'", "Comment 23: \'what is root cause? issue from DHH? \'", "Comment 24: \'and you can lower it to P2. i will check and feedback later on\'", "Comment 25: \'data have been arrived to DHC\'", "Comment 26: \'Hello,In this task we have focused on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue", \'Comment 27: we may raise RootCause Analysis (RCA)task for you.Please\', "Comment 28: let us knowhow you wish us to proceed.Regards.\'", "Comment 29: \'so", "Comment 30: what is clearing and unblocking? clear from DHH or DHC?\'", "Comment 31: \'Resend from DHH holding Recipe to DHC No errors in synchronization.Create RootCause Analysis ?Will we do a more extensive request analysis next time we report ?Close this Incident ?Regards\'", "Comment 32: \'thank", "Comment 33: you can close the ticket\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8040\n\n### Instruction:\nInvoices PI-RLB/2022/1050 (ID 75798) and SI-RLB/2022/1135 (ID 75799) were sent with wrong prices. Could you please put them back to entry? They aren\'t posted in Milas yet.\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Same counts for SI-RLB/1136 (ID 75801)\'", \'Comment 3: "There are in Entry (in Koen\\\'s Inbox)PI-RLB/2022/1050,SI-RLB/2022/1135,SI-RLB/2022/1136"\', "Comment 4: \'Send to Entry\'", \'Comment 5: "The round wasn\\\'t modified on the original PI (PI-RLB/2022/1051\', \'Comment 6: ID 75800). Could you put this one back to entry as well? Sorry for the work.!image-1!"]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8039\n\n### Instruction:\nHello,\r\n\r\nAttached LOTs are not showing dosed quantity in DHP.\r\n\r\nPlease assist.\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", \'Comment 2: \\\'{code:java}2022-12-09 14:23:07 (/Plant.PCS.BusinessLogic/SAURSRV04/6936/7) [Error] Microsoft.EntityFrameworkCore.Query - An exception occurred while iterating over the results of a query for context type \\\\\\\'"Plant.PCS.BusinessLogic.Infrastructure.EF.IntercontextCommunicationDbContext"\\\\\\\'."""Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', \'Comment 3: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found. at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 4: UInt32 waitForMultipleObjectsTimeout\', \'Comment 5: Boolean allowCreate\', \'Comment 6: Boolean onlyOneCheckConnection\', \'Comment 7: DbConnectionOptions userOptions\', \'Comment 8: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 9: TaskCompletionSource`1 retry\', \'Comment 10: DbConnectionOptions userOptions\', \'Comment 11: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 12: TaskCompletionSource`1 retry\', \'Comment 13: DbConnectionOptions userOptions\', \'Comment 14: DbConnectionInternal oldConnection\', \'Comment 15: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 16: DbConnectionFactory connectionFactory\', \'Comment 17: TaskCompletionSource`1 retry\', \'Comment 18: DbConnectionOptions userOptions) at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 19: SqlConnectionOverrides overrides) at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 20: Func`3 operation\', \'Comment 21: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20"Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', \'Comment 22: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found. at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 23: UInt32 waitForMultipleObjectsTimeout\', \'Comment 24: Boolean allowCreate\', \'Comment 25: Boolean onlyOneCheckConnection\', \'Comment 26: DbConnectionOptions userOptions\', \'Comment 27: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 28: TaskCompletionSource`1 retry\', \'Comment 29: DbConnectionOptions userOptions\', \'Comment 30: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 31: TaskCompletionSource`1 retry\', \'Comment 32: DbConnectionOptions userOptions\', \'Comment 33: DbConnectionInternal oldConnection\', \'Comment 34: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 35: DbConnectionFactory connectionFactory\', \'Comment 36: TaskCompletionSource`1 retry\', \'Comment 37: DbConnectionOptions userOptions) at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 38: SqlConnectionOverrides overrides) at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 39: Func`3 operation\', "Comment 40: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20{code}\'", \'Comment 41: "{code:java}SELECT * FROM [DHPlantPCSBusinessLogicEvents].[dbo].[ProductionLots] where AggregateId=\\\'6445a774-0ad1-4d86-b00d-42722bc8ab19\\\' SELECT * FROM [DHPlantPCSBusinessLogicEvents].[dbo].[ProductionLots] where AggregateId=\\\'716a9be0-d457-4f65-96e7-0e0406164d70\\\' {code}{code:java}SELECT * FROM [10.0.1.40\\\\\\\\PCS].[DHExchange66].[dbo].[SqlApiRequestLog] where parameters like \\\'%66221208002%\\\'GOSELECT * FROM [10.0.1.40\\\\\\\\PCS].[DHExchange66].[dbo].[SqlApiRequestLog] where parameters like \\\'%66221205009%\\\'GO{code} !screenshot-1! !image-2022-12-09-15-08-53-441!"\', "Comment 42: \'There are entries in PCS module(Plant.PCS.BusinessLogic) about missing sql connections,module has been restarted.Missing amounts of doses should be add in the application manually.That PLR from yesterday also has dosed information missing from PCS?", "Comment 43: I have only as below: !screenshot-2! \'", "Comment 44: \'What table is that?\'", "Comment 45: \'[10.0.1.40\\\\\\\\PCS].[DHExchange66].[dbo].[SqlApiRequestLog]\'", "Comment 46: \'Sorry..Same table.Thought you were looking at 009\'", "Comment 47: \'Please drop it to a P2\'", \'Comment 48: "We\\\'ve asked them to create it manually in the mean time. Can you tell us what went wrong with 009?We\\\'ll report 002 to the PCS supplier.Doesn\\\'t the new version of DHP (8.3) accept zero (0) value production lots?"\', "Comment 49: \'PLR 66221208002 has been finished by user not PCS. !screenshot-5! As for PLR 66221205009 there was a DHP upgrade at the time", "Comment 50: and only those from before seven in the morning registered in the plant. !screenshot-4!So I suspect the cause here.\'", "Comment 51: \'Thanks", "Comment 52: you may close this ticket\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8038\n\n### Instruction:\nShipping Notice isn\'t arriving in DHP it is in DHC though. \r\nConcerns 7_L000076575 with ext_nr 00944774\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", "Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task DGS-8030.We will revert to processing your task as soon as possible.Regards\'", "Comment 4: \'Please verify !image-2022-12-09-14-09-52-731.png!\'", "Comment 5: \'Yes", "Comment 6: it is there now. Thank you Adrian!\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8037\n\n### Instruction:\nDzień dobry,\r\n\r\nproszę o dodanie nowego składnika wynagrodzeń jakim jest: odprawa pośmiertna. \r\n\r\nZgłoszenie proszę przekazać dla Monika Biśta.\r\nZgłoszenie już zostało zrealizowane - do zamknięcia. \n\n### Response:\n["Comment 1: [\'Dzień dobry,Zgłoszenie zostało przyjęte do weryfikacji.\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Realized\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8036\n\n### Instruction:\nOn creation of VT for call off for Andel-Mest (location 98, managed in DHP Andel, location 5), an error message is given. See e.g. CL000008902\r\n\r\nPlease check why we get an error message / how it can be solved. We must be able to register intakes for Andel-Mest.\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: \\\'022-12-09 14:40:13 (bf5569e0-a6ee-478b-938f-804b730efead/Plant.VC.BusinessLogic/DHVD01AP184/18856/10) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 4: "host": { "Value": "dhvd01ap184:82"\', \'Comment 5: "HasValue": true\', \'Comment 6: "Host": "dhvd01ap184"\', \'Comment 7: "Port": 82 }\', \'Comment 8: "path": "/api/VehicleTicket/createVehicleTicketFromShippingNotice"\', \'Comment 9: "queryString": []\', \'Comment 10: "requestBody": "\\\\\\\\"7d2730b1-a089-42f9-85a3-14e62543d118\\\\\\\\""}.System.ArgumentException: DefaultDestinationSiteIsNotConfigured at Plant.VC.BusinessLogic.Domain.Configuration.ConfigurationExtensions.GetDestinationSiteIdOrThrow(Dictionary`2 defaultDestinationSitesStructure\', \'Comment 11: AggregateId businessUnitId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\Configuration\\\\\\\\ConfigurationExtensions.cs:line 15 at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.BaseVehicleTicketFromShippingNoticeGenerationPolicy.AddBulkIntakeElementToVehicleTicket(VehicleTicket vehicleTicket\', \'Comment 12: ShippingNoticeElement shippingNoticeElement\', \'Comment 13: AggregateId businessUnitId\', \'Comment 14: ShippingNotice shippingNotice\', \'Comment 15: Item item\', \'Comment 16: BusinessPartner businessPartner\', \'Comment 17: Nullable`1 producerId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\BaseVehicleTicketFromShippingNoticeGenerationPolicy.cs:line 180 at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.ItemSettlementTypeVehicleTicketFromShippingNoticeGenerationPolicy.OnIntakeElementGeneration(AddShippingNoticeToVehicleTicketDomainDataStructure dataStructure\', \'Comment 18: ShippingNoticeElementRelationsDataStructure shippingNoticeRelations\', \'Comment 19: ShippingNoticeElement shippingNoticeElement) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\ItemSettlementTypeVehicleTicketFromShippingNoticeGenerationPolicy.cs:line 26 at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.BaseVehicleTicketFromShippingNoticeGenerationPolicy.AddVehicleTicketElements(AddShippingNoticeToVehicleTicketDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\BaseVehicleTicketFromShippingNoticeGenerationPolicy.cs:line 108 at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.BaseVehicleTicketFromShippingNoticeGenerationPolicy.GenerateVehicleTicket(CreateVehicleTicketFromShippingNoticeDomainDataStructure dataStructure\', \'Comment 20: ContainerCompartment compartments) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\BaseVehicleTicketFromShippingNoticeGenerationPolicy.cs:line 49 at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.CreateVehicleTicketFromShippingNotice(AggregateId vehicleTicketId\', \'Comment 21: AggregateId shippingNoticeId\', \'Comment 22: Boolean isPlanned) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketService.cs:line 485 at Plant.VC.BusinessLogic.Application.VehicleTickets.CommandHandlers.CreateVehicleTicketFromShippingNoticeCommandHandler.Handle(CreateVehicleTicketFromShippingNoticeCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\CreateVehicleTicketFromShippingNoticeCommandHandler.cs:line 21 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.VC.BusinessLogic.Infrastructure.Api.Controllers.VehicleTicketController.CreateVehicleTicketFromShippingNotice(Guid shippingNoticeId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\VehicleTicketController.cs:line 762 at lambda_method33788(Closure \', \'Comment 23: Object \', \'Comment 24: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 25: ObjectMethodExecutor executor\', \'Comment 26: Object controller\', \'Comment 27: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 28: Scope& scope\', \'Comment 29: Object& state\', \'Comment 30: 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 31: Scope& scope\', \'Comment 32: Object& state\', \'Comment 33: 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 34: Task lastTask\', \'Comment 35: State next\', \'Comment 36: Scope scope\', \'Comment 37: Object state\', \'Comment 38: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 39: Task task\', \'Comment 40: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 41: Task task\', \'Comment 42: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 43: Task requestTask\', \'Comment 44: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', "Comment 45: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)\'", "Comment 46: \'!image-2022-12-09-14-58-36-384.png!\'", "Comment 47: \'HelloThere is no unit in configuration for feed 098 :Please add it in WMS->configuration-> storage locations!image-2022-12-09-15-07-22-352.png!Then in VT configuration check if here you have value", "Comment 48: if it will be empty add new line!image-2022-12-09-14-58-36-384.png!Please let me know if that informations are helpfull and we may clos ethe task\'", "Comment 49: \'May we close the task?\'", "Comment 50: \'Vt intake arrived. This task can be closed. {quote}Op 20 dec. 2022 om 08:31 heeft Agnieszka Januszewska (Jira) <jira@kotrak.com> het volgende geschreven: {quote} {quote} \\\\ufeff |{color:#ffffff} 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}{color}{color:#7a869a}{color}{color:#7a869a}{color} {quote}\']"]\nRelated Issues:\n[\'DGS-8115\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8035\n\n### Instruction:\nMove feed from 00651A/0006/0001 to 806514/0004/0001.\r\n\r\nIn Milas this is already done.\n\n### Response:\n["Comment 1: [\'Hi Mitch", \'Comment 2: can I ask what happened that Feed Sale invoices were booked on customer 0651A\', \'Comment 3: so they were sent to Round 0651A/0006/0001\', \'Comment 4: but then the customer was changed\', "Comment 5: so now they should be in Round 806514/0004/0001?\'", "Comment 6: \'A wrong customer number was use in Intense unfortunately. The specific customer has different account and a wrong one was used.\'", "Comment 7: \'[~damian.swistek@kotrak.com]dasz radę to ogarnąć albo pokazać Grzesiowi lub Tomkowi jak to zrobić? Należy przenieść pozycje Feed Sale z00651A/0006/0001 do 806514/0004/0001.\'", "Comment 8: \'22 elements from Feed Sale FE-L/0006 releted to Round00651A/0006/0001 have been moved to the Feed SaleFE-L/0002 related to Round806514/0004/0001. There are 63 elements in total. From No. 42 there are moved elements.!image-2022-12-13-15-21-11-234.png!\'", "Comment 9: \'Elements have been moved to other Feed Sale\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8034\n\n### Instruction:\nRecipe 505582 for Global feed mill (plant 15) was sent from DHH. Import of recipe in DHC failed.\r\nRecipes were sent yesterday and today\r\n\r\nError message: Object reference not set to an instance of an object.\r\n\r\nCan you check why the import failed / how it can be fixed. Plant needs the recipe.\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: \'Dear Bob,Item is not linked.Regards!image-2022-12-09-10-47-20-176.png!\'", \'Comment 4: "{code:java}2022-12-09 11:22:10,600 [176] ERROR Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Error occurred for event [Evolution.DHCountry.Dictionaries.Recipes.Events.RecipeChangedEvent[RecipeId=\\\'b17da454-8b02-43df-91b2-d82ec5b5fc11\\\']] in publisher [Evolution.Events.EventPublisher] under domain context [a5cea9f65ec04d4d85861d54e4850951]Evolution.Events.EventPublishException: Exception occurred while handling event. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Evolution.DHCountry.Production.AS400.ContaminationGroups.Queries.GetMatchedContaminationGroupAS400Query.OnExecute() in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Production\\\\\\\\AS400\\\\\\\\ContaminationGroups\\\\\\\\Queries\\\\\\\\GetMatchedContaminationGroupAS400Query.cs:line 115 at Evolution.DHCountry.Domain.DomainCommand.Execute() in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Domain\\\\\\\\DomainCommand.cs:line 94 at Evolution.DHCountry.Dictionaries.Recipes.Subscribers.GenerateProductionRecipeSubcriber.GetMatchedContaminationGroupId(Recipe recipe\', \'Comment 5: Model context) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Dictionaries\\\\\\\\Recipes\\\\\\\\Subscribers\\\\\\\\GenerateProductionRecipeSubcriber.cs:line 300 at Evolution.DHCountry.Dictionaries.Recipes.Subscribers.GenerateProductionRecipeSubcriber.ValidateMatchedContaminationGroupsForAS400(Recipe recipe\', \'Comment 6: Model context\', \'Comment 7: ValidationResult& result) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Dictionaries\\\\\\\\Recipes\\\\\\\\Subscribers\\\\\\\\GenerateProductionRecipeSubcriber.cs:line 221 at Evolution.DHCountry.Dictionaries.Recipes.Subscribers.GenerateProductionRecipeSubcriber.Validate(Recipe recipe\', \'Comment 8: Model context) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Dictionaries\\\\\\\\Recipes\\\\\\\\Subscribers\\\\\\\\GenerateProductionRecipeSubcriber.cs:line 206 at Evolution.DHCountry.Dictionaries.Recipes.Subscribers.GenerateProductionRecipeSubcriber.GenerateProductionRecipeFromRecipe(Guid recipeId\', \'Comment 9: Boolean generatedAutomatically) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Dictionaries\\\\\\\\Recipes\\\\\\\\Subscribers\\\\\\\\GenerateProductionRecipeSubcriber.cs:line 150 at Evolution.DHCountry.Dictionaries.Recipes.Subscribers.GenerateProductionRecipeSubcriber.OnEventHandle(RecipeChangedEvent event) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Dictionaries\\\\\\\\Recipes\\\\\\\\Subscribers\\\\\\\\GenerateProductionRecipeSubcriber.cs:line 47 --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target\', \'Comment 10: Object[] arguments\', \'Comment 11: Signature sig\', \'Comment 12: Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj\', \'Comment 13: Object[] parameters\', \'Comment 14: Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj\', \'Comment 15: BindingFlags invokeAttr\', \'Comment 16: Binder binder\', \'Comment 17: Object[] parameters\', \'Comment 18: CultureInfo culture) at Evolution.Events.EventPublisher.HandleEvent(Object subscriber\', \'Comment 19: Object event) at Evolution.Events.EventPublisher.PublishToSubscriberTypes(Object event\', \'Comment 20: IEnumerable`1 subscriberTypes) --- End of inner exception stack trace --- at Evolution.Events.EventPublisher.PublishToSubscriberTypes(Object event\', \'Comment 21: IEnumerable`1 subscriberTypes) at Evolution.Events.EventPublisher.Publish(Object event) at Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing.Publish(Object event) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Logging\\\\\\\\EventPublisherWithLog4NetTracing.cs:line 31{code}"\', "Comment 22: \'In error logs we have information that contamination group is not matched to this recipe when we trying to import recipe.Please", "Comment 23: verify\'", "Comment 24: \'Indeed", \'Comment 25: item is not linked\', \'Comment 26: but that should not give issue on import of recipe.Assigning of contamination group normally happens when recipe is accepted\', \'Comment 27: not on import. And even if recipe cannot be accepted\', "Comment 28: it is successfully imported and visible in DHC. In this case I cannot find the recipe in DHC!image-1!\'", \'Comment 29: "Well,As base item is not linked with DHH item\', "Comment 30: the recipe cannot linked to contamination group. So it won\'t appear to accept according to error about containation group matching. The best and the quickest way is t link base item with dhh item.I have consulted your case", \'Comment 31: in version 3.0.61 this issue should not occur. If possible\', \'Comment 32: please\', \'Comment 33: link items.Best regards"\', "Comment 34: \'ERP item was not exported. I exported it. DHC linked the item automatically. Can you reprocess the recipe?!image-2!\'", "Comment 35: \'We have already sent recipe fro Holding", "Comment 36: please verify. On our side we can see version 2.Regards\'", "Comment 37: \'Yes", \'Comment 38: now both versions are in DHC and accepted.So\', \'Comment 39: currently import of recipes fails if item is not linked? This is new for me; I do know that it cannot be accepted before it is linked\', "Comment 40: but then at least the recipe is visible in DHC\'", "Comment 41: \'Yes", \'Comment 42: because contaminaton group requires linked items.If everything is fine now\', "Comment 43: can we close task? :)Regards\'", "Comment 44: \'Yes", "Comment 45: you can close this task.\'", "Comment 46: \'Thank you\'", "Comment 47: \'Ok", "Comment 48: thank you. I will check this with formulation.\'", \'Comment 49: "Hi Bob,Shouldn\\\'t this comment be underDGS-8849? ;)"\', "Comment 50: \'Indeed. My mistake.\'", "Comment 51: \'No issue :)\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8033\n\n### Instruction:\nHello,\r\n\r\nVT-153/12/MM and VT-158/12/MM are stuck in DHC (please see attached error message).\r\nSORs are not showing in ERP, we are not sure whether they were re-opened and deleted.\r\n\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-6448\r\n\r\nPlease assist.\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: \'Morning,Can we please have feedback \'", "Comment 4: \'{code:java}2022-12-12 20:24:33,956 [63] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-158/12/2022/MM [Id: ac544643-16f6-49f0-a183-366af7e8e4d3]2022-12-12 20:24:33,956 [63] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2022-12-12 20:24:33,956 [63] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2022-12-12 20:24:34,050 [89] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - GenerateSalesOrderRelease execution started2022-12-12 20:24:34,112 [89] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Forcing document number - 2783/0/2022/MPMM for vt element id - Id: 9118867a-22e7-4773-8fa0-58576aef75bf2022-12-12 20:24:34,191 [89] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - System.InvalidOperationException: Sequence contains no elements 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 5: 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 6: 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 7: 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)2022-12-12 20:24:34,191 [89] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - Sequence contains no elementsSystem.InvalidOperationException: Sequence contains no elements 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 8: 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 9: 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 10: 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()2022-12-12 20:24:34,191 [63] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - Sequence contains no elementsSystem.InvalidOperationException: Sequence contains no elements at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor.ProcessSingleVT(VehicleTicket vehicleTicket)2022-12-12 20:24:34,191 [63] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution finished2022-12-12 20:24:34,191 [63] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution started2022-12-12 20:24:34,206 [63] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution finished2022-12-12 20:24:37,524 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Order message from trigger - ID - 7868762022-12-12 20:24:37,540 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Order data downloaded - SO-526/22/MMW2022-12-12 20:24:37,540 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Sending Order message - SO-526/22/MMW2022-12-12 20:24:37,540 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapping.... (Firma:556290 - TYP:960/NUMER:786876/LP:0\', \'Comment 11: SO-526/22/MMW)2022-12-12 20:24:37,555 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapped (Firma:556290 - TYP:960/NUMER:786876/LP:0\', \'Comment 12: SO-526/22/MMW)2022-12-12 20:24:37,555 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message send (Firma:556290 - TYP:960/NUMER:786876/LP:0\', "Comment 13: SO-526/22/MMW){code}\'", \'Comment 14: "Sprawdziłem linkowane itemy i order elementy\', \'Comment 15: klientai powiązanie elementów VT do elementów SO.{code:java}SELECT ve.* FROM [DHCountry_RSA_PROD].[dbo].[VehicleTicketElements] ve left join [DHCountry_RSA_PROD].[dbo].[OrderElements] oe on ve.[OrderElementId]=oe.id where ve.VehicleTicketId=\\\'AC544643-16F6-49F0-A183-366AF7E8E4D3\\\'SELECT TOP (1000) [Id] ,[DhcId] ,[XlId] ,[XlTyp] ,[XlFirma] FROM [DHCErpPlugin_RSA_PROD].[dbo].[ItemSyncs] where dhcid=\\\'1095AE07-44C7-4438-A3C8-58407D7928ED\\\' or DhcId=\\\'5F577FD4-7D25-4F7A-9B11-979388197B3D\\\' /****** Script for SelectTopNRows command from SSMS ******/SELECT TOP (1000) [Id] ,[DhcId] ,[XlId] ,[XlTyp] ,[XlFirma] FROM [DHCErpPlugin_RSA_PROD].[dbo].[OrderElementSyncs] where DhcId in(\\\'44335F42-6A97-452A-ACB3-145D777A8122\\\',\\\'50E2E0E8-03C2-47AD-9CAE-536325F07FF0\\\')SELECT TOP (1000) [Id] ,[DhcId] ,[XlId] ,[XlTyp] ,[XlFirma] FROM [DHCErpPlugin_RSA_PROD].[dbo].[OrderSyncs] where xlid in(787981,786876) or DhcId=\\\'A20D0E7A-7E78-49A7-B5F7-8F6DF0200CF1\\\'{code}"\', "Comment 16: \' !screenshot-1! \'", "Comment 17: \'problem się zaczal 5 grudnia!image-2022-12-13-13-04-48-160.png!\'", "Comment 18: \'{code:java} update z set z.zae_twrtyp=16 FROM [CDNXL_DHFU].[CDN].[ZamElem] z left join cdn.twrkarty t on t.twr_gidnumer=z.zae_twrnumer where zae_twrtyp=2 select cdn.tstodate(zan_datawystawienia,0),* from cdn.zamnag where zan_gidnumer in(select ZaE_GIDNumer FROM [CDNXL_DHFU].[CDN].[ZamElem] z where zae_twrtyp=2){code}\'", "Comment 19: \'Corrected for now", "Comment 20: please check.As to the cause - under investigation.\'", "Comment 21: \'VTs generated.\'", \'Comment 22: "Hello,SO-989/22/KDWSO-990/22/KDWSO-991/22/KDWSO-992/22/KDWSO-993/22/KDWSO-597/22/MMWSO-994/22/KDWThe problem still occurs due to incorrect data on the order elements/items. Were they created differently from the others?(it\\\'s not about creating from a copy or from a plus)Above is a list from the last days."\', "Comment 23: \'Hi PiotrYes", "Comment 24: they were created differently. I inserted the line items via SQL.Can you tell me what field was/is wrong?Regards\'", "Comment 25: \'Hello,zae_twrtyp column should be equal to 16 it is a reference to a group of items.\'", "Comment 26: \'Hello", "Comment 27: VT 323/12/2022/MM has the same issue. !image-1!\'", "Comment 28: \'Generated.\'", \'Comment 29: "Thank you. I\\\'ll fix that now. Please keep the ticket open till I can confirm."\', \'Comment 30: "Ok\', "Comment 31: I\'véupdate the query", \'Comment 32: and the orders already create with the incorrect type.Thank you for the assistance."\', "Comment 33: \'Thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8032\n\n### Instruction:\nHi, we\'ve a lots of awd in Active status in gui, but it should be Realized (PZ generated to awd).\r\nThe same status in dhc. Any idea why? It must be corrected....\r\n\r\nRafał Boniecki\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: "Puściłem dwa przykładowe i się statusy zaaktualizowały{code:java}AWD-60201/08/22 EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12119444,1489,2573532AWD-79773/10/22 EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12496634,1490,2593274{code}{code:java}SELECT dhcs.status,dhcs.foreignnumber,sh.DocumentStatus,t.TrN_GIDNumer,t.TrN_GIDTyp,sh.idFROM [CDNXL_DEHEUS].[Kotrak].[ShipmentNotificationsHeaders] shINNER join [CDNXL_DEHEUS].[Kotrak].[ShipmentNotificationsElements] seon sh.id=se.HeaderIdINNER join cdn.TraNag t on t.TrN_GIDNumer=se.DocumentElementGIDNumberINNER join [sql03-20\\\\\\\\dhapp].[Evolution_DHCountry].[dbo].[ShippingNotices] DHCSon dhcs.foreignid=sh.id--where dhcs.foreignnumber=\\\'AWD-76509/10/22\\\'--where dhcs.status=6 and sh.DocumentStatus=9 OR WHERE dhcs.documentyear=2022 and dhcs.status<>6 and dhcs.foreignnumber like \\\'AWD%\\\'and sh.DocumentStatus=5--where--(dhcs.foreignnumber IN(\\\'AWD-79773/10/22\\\'))--)){code}jest takich ponad 50 !screenshot-1! !image-2022-12-13-19-19-25-475!"\', \'Comment 4: "Ostatni przykład: !screenshot-2! !screenshot-3! {code:java}2022-12-12 10:59:21,107 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Shipment Notification processing started for PZ-76/12/22/Y2022-12-12 10:59:21,107 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12567434,1489,26046182022-12-12 10:59:21,154 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Shipment Notification processing finished for PZ-76/12/22/Y2022-12-12 10:59:21,154 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document completed - PZ-76/12/22/Y [Firma:246785 - TYP:1489/NUMER:12567434/LP:0] Evolution.ErpIntegrator.Extensions.MYShipmentNoticeUpdate.MYShipmentNoticeUpdate2022-12-12 10:59:21,154 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document started - PZ-76/12/22/Y [Firma:246785 - TYP:1489/NUMER:12567434/LP:0] Evolution.ErpIntegrator.Extensions.PLAdvanceLogger.PLAdvanceLogerExtension2022-12-12 10:59:21,154 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document completed - PZ-76/12/22/Y [Firma:246785 - TYP:1489/NUMER:12567434/LP:0] Evolution.ErpIntegrator.Extensions.PLAdvanceLogger.PLAdvanceLogerExtension2022-12-12 10:59:21,185 [126] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL transaction commited\', \'Comment 5: token ID - U_Y/2XMWl1O@`LG?SI-RM=5---0>D---2022-12-12 10:59:21,185 [126] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction commit started2022-12-12 10:59:21,185 [126] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction commit finished{code}puszczam procedurę i executed !screenshot-4! !screenshot-5! "\', "Comment 6: \'list of corrected awd below", "Comment 7: [^awd.txt] statuses are updated for the current ones.We will check in the next few days if there are any new cases.\'", \'Comment 8: "There are again SN with status Active. What\\\'s the problem?!image-3!"\', \'Comment 9: "Są nowe w logu:{code:java}2022-12-21 12:35:15,845 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document started - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.MYShipmentNoticeUpdate.MYShipmentNoticeUpdate2022-12-21 12:35:15,880 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Shipment Notification processing started for PZ-457/12/22/D2022-12-21 12:35:15,880 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12600421,1489,26087342022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Shipment Notification processing finished for PZ-457/12/22/D2022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document completed - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.MYShipmentNoticeUpdate.MYShipmentNoticeUpdate2022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document started - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.PLAdvanceLogger.PLAdvanceLogerExtension2022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document completed - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.PLAdvanceLogger.PLAdvanceLogerExtension2022-12-21 12:35:16,005 [73] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL transaction commited\', \'Comment 10: token ID - d:eJj^@U]1GGL<Q.T2klg=5---0EJ]--2022-12-21 12:35:16,005 [73] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction commit started2022-12-21 12:35:16,005 [73] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction commit finished{code}Jak puściłem ten sam ponownie przeszło:EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12600421,1489,2608734"\', "Comment 11: \'Hello", "Comment 12: I confirm new cases for no status change to executed.RCA will be required for analysis - please confirm to create.\'", "Comment 13: \'i confirm", "Comment 14: you can create RCA task.\'", "Comment 15: \'We confirm create RCA.\'", "Comment 16: \'RCA has been created DGS-8153. \'", "Comment 17: \'Thanks", "Comment 18: this task you can close.\']"]\nRelated Issues:\n[\'DGS-8153\']\n\n### End'}