Unnamed: 0
int64 0
999
| 0
stringlengths 258
77k
|
|---|---|
400 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8632\n\n### Instruction:\nI\'ll write an e-mail\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: \'Mail from Christine!image-2023-03-03-10-44-43-831.png!\'", "Comment 3: \'Hi Christine,These 4 lines have been deleted from Feed saleFE-N/0007.!image-2023-03-03-10-57-13-674.png!Please verify that is correct and if we can close the task.Regards\'", "Comment 4: \'{color:black}Thank you Damian{color} {color:black}😊{color}{color:black}{color} {color:black}All is well now.{color} {color:black}{color} {color:black}Have a great weekend!{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* vrijdag 3 maart 2023 10:59 *Aan:* Jong", "Comment 5: Christine de <[email protected]> *Onderwerp:* DGS-8632 Delete wrong feed sale registrations FE-N/0007 !image006!\']"]\nRelated Issues:\n[]\n\n### End'} |
401 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8631\n\n### Instruction:\nFind the below error in DHP Johnson\n\n### Response:\n["Comment 1: [\'!IMG-20230227-WA0000.jpg|thumbnail!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Dear Solomon,I have restarted application pools. Now for me it seems to be working fine. Please", "Comment 4: verify and let me know.Regards\'", "Comment 5: \'It is working now but orders are not showing \'", "Comment 6: \'Let me check\'", "Comment 7: \'Could you please provide me an example of the Order (document number) that does not arrive to DHP?\'", "Comment 8: \'IO 788/23\'", "Comment 9: \'!image-2023-02-27-09-35-18-233.png!\'", "Comment 10: \'The order is in Plant now. The rest of the Orders as well. Could you please", "Comment 11: let me know if you restarted serevers or did you experience temporary lack of internet or electricity?\'", "Comment 12: \'Please close\'", "Comment 13: \'błędy w logach od momentu restartu app serwera tj.2/26/2023", "Comment 14: 2:54:24 AM\']"]\nRelated Issues:\n[]\n\n### End'} |
402 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8630\n\n### Instruction:\nwhen scanning at the final location of the replenishment, we get an error message.\r\n\r\nThey got this message several times\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: \'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: \'Dziwny ten dokument jest :( !RM 3143 - 24.02.2023! ----Ostatnia próba generowania WMO RM z automatu jest 2023-01-27!image-2023-02-27-14-23-14-981!Log z 27-01-2023 dla WMO(RM)- 3941/01/23!image-2023-02-27-14-32-13-718!----Do ABM wpis z tym SN powstał 24.02.2023 10:49 (Id = 4771)!image-2023-02-27-14-24-47-116!Historia ABM dla towaru 00978!image-2023-02-27-14-27-22-380!\'", "Comment 5: \'[[email protected]] prosiłbym o próbę zreprodukowania błędu na naszym środowisku \'", "Comment 6: \'Hi,This issue will be fixed in new version. Please", "Comment 7: let us know if we can close this task.Regards\'", "Comment 8: \'New version off?When wil this new version been installed?\'", "Comment 9: \'[[email protected]] This deployment has been made today at night. I was discussing with Thomas Dankers about the upgrade of DHP Mobile", "Comment 10: which operators should do today in the morning. There is a newer build of the same Release you have had. DHP Desktop 2.7.1911.164 (previous version 2.7.1911.157)Newer Web Service for DHP Mobile based on the same release as DHP Desktop DHP Mobile version 2.7.1911.18 (previous 2.7.1911.16)\'", "Comment 11: \'May we close this task?Regards\']"]\nRelated Issues:\n[\'DGS-8560\']\n\n### End'} |
403 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8629\n\n### Instruction:\nPORs don\'t come into ERP automatically, i have to move them manually from DHC to ERP, can you please help identify the issue and solve. 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: \'!image-2023-02-27-08-39-20-301.png!\'", "Comment 3: \'Dear Solomon,I have done reindexation of DB and updated statistics. Please", \'Comment 4: let me know if it helped.If it did not help\', "Comment 5: please provide me with examples of documents to invesigate further.Regards\'", "Comment 6: \'Okay thanks", "Comment 7: please close\'", "Comment 8: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
404 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8628\n\n### Instruction:\nWZ-1360/02/G został wygenerowany przez automat w CDN, następnie został "cofnięty" do DHC\r\nW tym momencie w CDN WZ jest Anulowany\r\n\r\nVT-3839/2/2023/G zwraca błąd:\r\nBŁĘDY:|Zabrakło ilości (nie udało się pobrać towaru lub wymuszono realizacje całości). (DodajPozycje-17) - (DD0A2R00C-L4B)\r\n\r\nProśba o pomoc z ponownym wygenerowaniem WZ w CDN\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,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-02-27-11-16-42-754.png!!image-2023-02-27-11-16-59-429.png!!image-2023-02-27-11-17-49-394.png!!image-2023-02-27-11-19-13-795.png!\'", "Comment 4: \'Hi,For today I can see only 18 t available (6 is reserved from 24). And you need nearly 20.Please", "Comment 5: verify!image-2023-02-27-11-30-41-075.png!\'", "Comment 6: \'!image-2023-02-27-11-32-44-081.png!\'", \'Comment 7: "But I don\\\'t see this 6t reservation in history !image!"\', "Comment 8: \'How was document SOR / WZ cancelled? In application or under db?\'", "Comment 9: \'from what i know - application\'", "Comment 10: \'you can close this task. WZ was generated\'", "Comment 11: \'We fixed the problem - task to close.\'", "Comment 12: \'ok\']"]\nRelated Issues:\n[]\n\n### End'} |
405 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8627\n\n### Instruction:\nRaw material 9114 is not arriving in DHC after several attempts.\r\nIt;s needed for several recipes that need to be in DHP by tomorrow morning.\r\n\r\n\r\nMessages in the communication log:\r\n\r\nDistributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.\r\n\r\nThe transaction has aborted.\r\n\r\nThe transaction associated with the current connection has completed but has not been disposed. The transaction must be disposed before the connection can be used to execute SQL statements.\r\n\r\nAnd several deadlocks.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'!image-2023-02-24-18-38-52-512.png!\'", \'Comment 3: "Dear Rob,We ahve a deadlock here. Message queues were quite big. I have restarted services and now I\\\'m waiting till the queues will give 0 messages!image-2023-02-24-18-48-27-147.png!"\', "Comment 4: \'I am waiting for that event as well. So we both suffer the same ;)\'", "Comment 5: \'19:04hThe transaction associated with the current connection has completed but has not been disposed. The transaction must be disposed before the connection can be used to execute SQL statements.Transaction Timeout\'", "Comment 6: \'Restart usług", "Comment 7: zmiana kolejności wiadomości dla BP!image-2023-02-24-19-22-07-011.png!\'", "Comment 8: \'Yes", "Comment 9: messages queues are still not empty\'", "Comment 10: \'Queues are empty and I cannot see any errors anymore. But", "Comment 11: please confirm one thing. In Communiction log name looks a bit different than in DHH. Is that ok?!image-2023-02-24-19-50-49-495.png!!image-2023-02-24-19-51-10-692.png!\'", "Comment 12: \'Was this item sent from ERP to DHC? Please resent this item from ERP system.Regards\'", "Comment 13: \'I re-sent the item.Differences in description are not relevant I presume.\'", "Comment 14: \'Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.The transaction associated with the current connection has completed but has not been disposed. The transaction must be disposed before the connection can be used to execute SQL statements.\'", "Comment 15: \'The difference in description is a language thing", "Comment 16: both mean the same.\'", "Comment 17: \'Hi All recipes contains this item as a raw item are made on plant 015 Balgoij and on this plant there is no DHP application. How do you want to produce on tahat plantThe problem was automatic acceptance of recipes on this plant. Can we turn off automatic acceptance of recipes for all plants where DHP application is not supported?Item is aleady in DHC and all recipes are accepted!image-2023-02-24-22-00-32-660!\'", \'Comment 18: "The recipes are exported to the plant itself\', \'Comment 19: they have their own systems to process them. I think automatic acceptance is still needed for them.If the users had exported the item before they created the recipes there wouldn\\\'t be a problem. I will instruct them to follow the right steps."\', "Comment 20: \'Item is aleady in DHC and all recipes are accepted. Can we close this issue?\'", "Comment 21: \'Yes you most certainly can. Thanks for your support", "Comment 22: have a nice weekend.\'", "Comment 23: \'Have a nice weekend for you too.\']"]\nRelated Issues:\n[]\n\n### End'} |
406 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8626\n\n### Instruction:\nId 6318595 start transfer error \r\n\r\nProdukcja w trakcie - prośba o pilną interwencję.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'!image-2023-02-24-15-40-02-094.png!\'", "Comment 3: \'This lot230224021 was in status finished. We have cancelled messages.Please", "Comment 4: verify.Regards\'", "Comment 5: \'Is correct - task to close.\'", "Comment 6: \'[[DHP] Production lot is already closed|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%20Production%20lot%20is%20already%20closed§ion-id=\\\\\\\\{CC5FB5C6-8E0D-42E5-8319-3DC0E80D8642}&page-id=\\\\\\\\{F78DF54D-8192-44F0-96D3-F7FC6B86DC74}&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%20Production%20lot%20is%20already%20closed%7CF78DF54D-8192-44F0-96D3-F7FC6B86DC74%2F%29])\']"]\nRelated Issues:\n[]\n\n### End'} |
407 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8625\n\n### Instruction:\nIn Ivory Coast there is problem with intake from production, in case the WO[IP] quantity is higher than produced one. It is hard to verify that because in the UI in WO[IP] production order quantity is displayed as produced quantity, what is confusing for the user, I would like you: 1.to check which quantity is really considered for the validation, 2. Change the UI display of WO[IP] in the column produced q-ty display q-ty produced, not ordered, 3. inform what is the tolerance of the validation between mentioned quantities on WO[IP] document \n\n### Response:\n["Comment 1: [\'!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: \'Hi [[email protected]],# Produced quantity is validated# I created a GDC-855 for this change# Tolerance quantity is available from the UI from R8.6 and can be configured here: !woipconfig! Regards\'", "Comment 5: \'We agreed with [[email protected]] that since there is not so easy to change it we will change the description\'", "Comment 6: \'Please inform which version will contain the change. And close the ticket\'", "Comment 7: \'[[email protected]]wersja 8.6?\'", "Comment 8: \'[[email protected]] tak\'", "Comment 9: \'[[email protected]]version 8.6.Regards\']"]\nRelated Issues:\n[\'DAP-13373\']\n\n### End'} |
408 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8624\n\n### Instruction:\nPlease set PI-RLB/2023/1084 back to entry\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Already done", "Comment 3: this can be closed.\'", "Comment 4: \'Thank you for information.\']"]\nRelated Issues:\n[]\n\n### End'} |
409 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8623\n\n### Instruction:\nHi, Recipe 111282 isn\'t arriving in DHP for Maasbracht (plant 12). \r\nIn DHC this is the error in the communication log:\r\n\r\nRecipeChangedMessage: Id=98ea2e12-154a-4bb9-8aaf-6a94d172ca0a Version=30 ProductionAreaId=06e2b435-8093-4eeb-a3b5-946c8c94181a DhhItemId=64902f3b-7f1a-40dd-a2bd-fd9e0423e6da StartDate=2/22/2023 12:00:00 AM EndDate=\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Dear Theo,Recipe is in plant now.!image-2023-02-23-19-31-45-688.png!Regards\'", "Comment 3: \'Thanks Aleksandra", "Comment 4: could you tell me what was wrong?\'", \'Comment 5: "Probably yesterday\\\'s issue with queues made that. Item111282 did not appear in DHC Service (it usually happens when too many messages are sent) so I needed to resent item\', \'Comment 6: resynced Recipe\', \'Comment 7: Production Recipe and Technology :)Regards"\', "Comment 8: \'Can I close this task? :)\'", "Comment 9: \'Sure", "Comment 10: please close the task.Many thanks again. \']"]\nRelated Issues:\n[]\n\n### End'} |
410 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8622\n\n### Instruction:\nIt is impossible to link item 088452 to BM item 999999, I constantly get time-out situations when saving the changes.\r\n\r\nThere is a sales order and a calloff that are blocked now because the item is not linked.\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 have linked these two items", "Comment 3: please verify and let me know.Regards\'", "Comment 4: \'Hi Aleksandra,the item was linked", \'Comment 5: and I was able to link the other item variant needed myself.Thanks for the support\', "Comment 6: the ticket can be closed.\']"]\nRelated Issues:\n[]\n\n### End'} |
411 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8621\n\n### Instruction:\nCould you please move all bookings to the respective category?\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,Which documents should be moved from851199 and881199 to customer051199?SI\\\'s and PI\\\'s or othere documents like Feed sale lines (there are some movements as I saw)!image-2023-02-24-12-10-13-203.png!!image-2023-02-24-12-10-33-852.png!"\', \'Comment 3: "It is about the SI\\\'s and PI\\\'s\', \'Comment 4: The feed from the migration is already moved if it is correct."\', \'Comment 5: "Ok\', "Comment 6: so all PI\'s and SI\'s from screens should be updated (and all calculated fields like on screen below)", \'Comment 7: right?These invoices are archived\', \'Comment 8: so maybe there is needed also some changes in Milas.!image-2023-02-24-15-55-04-699.png!"\', "Comment 9: \'Indeed", \'Comment 10: these fields need to be changed except for the ones I made blue.These invoices are mostly registration I ecspect\', "Comment 11: so they have no relation with Milas. !image!\'", "Comment 12: \'All SI and PI documents from 851199 and881199 have been moved to051199.10 documents have been modified. * originally 851199:SI-RTV/2022/0021SI-RTV/2022/0018PI-RLV/2022/0016SI-RTV/2022/0016SI-RTV/2022/0007 * originally 881199:SI-RTV/2022/0022PI-RLV/2022/0018SI-RTV/2022/0020SI-RTV/2022/0015SI-RTV/2022/0006!image-2023-02-27-10-03-39-102.png!Please verify that is correct.Regards\'", "Comment 13: \'It is correct and almost complete. Also PI-RTV/2022/0003 and PI-RTV/2022/0010 should be moved from 851199 to 051199.\'", "Comment 14: \'PI-RTV/2022/0003 and PI-RTV/2022/0010 have been modified and are on round051199/0001/0001 for customer051199.Please verify that is correct.Regards\'", "Comment 15: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'} |
412 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8620\n\n### Instruction:\nIntegrated login has been disabled and saved once.\r\nLater it was switched on again and saved and it is no longer possible to log in integrated via CDNCL.\r\nAfter this, no more via DH CDN. The user BKRE is no longer in the selection menu so that it can no longer be selected.\r\n\r\nIf login different than integrated login is turned off, you can log in after first pressing Change password.\r\nThen the message Clear Password appears and you must answer the question to delete it with "Yes". You cannot enter a new password.\r\n\r\nAfter this you can log in to CDN CL by not using integrated login.\r\nAfter this you can log in again as a user BKRE integrated in DH CDN.\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!!image-4!\'", "Comment 2: \'Hi,I have replied you for this issue in DGS-8616. Please", \'Comment 3: let me know if after any chnage on any user\', "Comment 4: the user or you exited the system?Regards\'", "Comment 5: \'Using exit then the value NWIJ is default entered.Log in without password.Integrated login stil does not work.!image-5!\'", "Comment 6: \'Only those two users are impacted:NWIJ and PWIJ?Regards\'", "Comment 7: \'One more thing. Integrated login means you can login to the system withoud entering credentials only from your computer under your domain. Please", "Comment 8: let me know if usersNWIJ and PWIJ tried to login from their devices.Regards\'", "Comment 9: \'Logging in is done from my own device. I can no longer log in integrated. I tested once to no integrated log in. This did not work due to the password. For this", "Comment 10: clicked on change password where there was no option to change it. Only delete password. I could log in using BKRE. After this it is no longer possible to log in integrated. New users also cannot log in integrated.\'", \'Comment 11: "Niels Wijnen has again trouble logging into CDN.He wants to get into Accounting using the button accounting. Then he geta the gray screen according screen shot. Last Thursday when he was in the office Veghel it went well. He also can\\\'t close the gray screen which keeps him logged in and has to ask someone else to kick kim out."\', "Comment 12: \'!image-3!\'", "Comment 13: \'When I at the office go to accounting there is no problem.!image-6!\'", "Comment 14: \'Niels is now working on the office in Ede. (Kabel)\'", "Comment 15: \'The system sees users assigned to domain (point 1)As we chekced", \'Comment 16: only few users can login with integrated login (point 2). There are no users that you mentioned!image-2023-02-27-10-40-39-027.png!For example\', \'Comment 17: for Bob we can see what local group he is a member:!image-2023-02-27-10-41-50-650.png!Wherease for your user\', "Comment 18: we can see you are not assigned to any group:!image-2023-02-27-10-43-08-251.png!I would advise to check a domain controller what went wrong.Regards\'", "Comment 19: \'The wright NT group and user is selected.!image-7!!image-8!\'", "Comment 20: \'!image-9!\'", "Comment 21: \'But as I send you screenshot from CMD", "Comment 22: they are not in the domain. So they need to be resynced in domain controller.Regards\'", "Comment 23: \'Why can other user who are not in your screen shot log in integrated?For example RGAN.!image-10!!image-11!\'", "Comment 24: \'Dear Bert,Let me be more clear. This is the issue of domain controller", \'Comment 25: not ERP XL itself. When the policy will finally update\', "Comment 26: no one will be able to login to xl with integrated login. You need to verify this issue from Active Directory side.Regards\'", "Comment 27: \'What action is expected of us. Our service desk sees all users in AD\'", "Comment 28: \'We have forwarded your issue to producer. We will let you know about the result as soon as possible. Till then", "Comment 29: I will put this task in On Hold status.Regards\'", "Comment 30: \'I think there is some missunderstand how integrated login works in ERPXL. To allow user to use integrated login there must be some conditions meet. * User have to be member of specified domain group. * This group have to be synchronized with ERPXL to match domain NTSID and NT account login with operator in ERP system. * Domain group synchtonization with ERPXL must be done when XL is run as administrator. * User has to got Use NT authorization for thos user parameter set. * User have to be login through correct domain account to Windows while login to ERPXL.If any of those conditions is not meet then You will not be able to log in using domain account.Operators PWIJ and NWIJ do not have NTSiD or domain account provided in ERPXL. Those account nas not been synchronized to ERPXL.Operator RGAN do have bothNTSiD anddomain account provided in ERPXL. That means it have been in proper domain group when synchronization occurs.In order to synchronize domain group with ERPXL You should run ERPXL as Admninistrator and run Synchronize accounts of ERP XL operators with NT group operation.!image-2023-03-07-19-46-37-786.png!Be aware that any mapped connections for operators that has been removed from provided domain group wil bee removed from ERPXL. Caution is advised.Please check.\'", "Comment 31: \'In the past i did login using AD.A new user could not login ussing AD.When i was testing login with my own name and pasword ( not using AD) i could login.Whwn i activated login usung AD it did not work anymore while in the past there was no problem.. \'", "Comment 32: \'Could you please confirm if all below steps have been done correctly: * User have to be member of specified domain group. * This group have to be synchronized with ERPXL to match domain NTSID and NT account login with operator in ERP system. * Domain group synchtonization with ERPXL must be done when XL is run as administrator. * User has to got Use NT authorization for thos user parameter set. * User have to be login through correct domain account to Windows while login to ERPXL.Regards\'", \'Comment 33: "Hi,I noticed in one of your screenshots you\\\'re looking at the group in the EMEA.corp.deheus.com domain. That\\\'s not where our user accounts reside (at the moment) that is the HEUS domain (de-heus.nl). In that domain there is a group with the same name\', \'Comment 34: but filled with the proper useraccounts.Please let the application refer to the HEUS domain. Thanks!"\', "Comment 35: \'Zalogowałam się userem w domenie heus", "Comment 36: a dalej woła emea!image-2023-03-20-13-49-21-733.png!\'", "Comment 37: \'!image-2023-03-20-14-37-56-982.png!\'", "Comment 38: \'Dear Martijn,Yes", \'Comment 39: because I have run a query with group assigned in XL and it looks this group is in emea\', "Comment 40: not heus. Are you able to check how this group is named in Heus domain?!image-2023-03-21-08-30-12-977.png!Regards\'", "Comment 41: \'The group has the same name in HEUS: NL - Citrix - DH Premix Prod\'", "Comment 42: \'Any update to mention?\'", "Comment 43: \'Did You try update information on domain users in ERPXL according to my previous comment?!image-2023-03-28-12-15-29-605.png!\'", \'Comment 44: "Hi\', "Comment 45: it\'s a bit unclear for me what information to take from that post. The users are member of a certain group. What exactly do you want me to change on that?The synchronization you mention", \'Comment 46: is that a manual action that has to be done every now and then?"\', "Comment 47: \'This action should be done every time when you add new member to specific domain group. This is not an automatic process.\'", "Comment 48: \'Please", "Comment 49: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 50: \'All users are in the list for selecting user.But why do already syngronized user disappear and are only a few users present?\'", "Comment 51: \'only a few users present acording to Kotrak\'", "Comment 52: \'During synchronization", "Comment 53: the list of AD users related to ERP XL is refreshed according to the current content of the selected group.Do you expect any additional actions from us regarding this issue?\'", \'Comment 54: \\\'Do we first have to click on "NT Login" at the bottom left of the screen?How long will it take for this to show a result. The screen does not show anny action for a very long time.Is this oke or is this wrong?If this is oke doe we have to click : Synchronize account of ERP-XL?!image-12!!image-13!!image-14!\\\'\', \'Comment 55: \\\'Use NT-integrated login parameter!image-2023-04-05-12-41-43-710.png!should be choosen when you want to set "Use NT authorization for this operator" paramenter on operator card.!image-2023-04-05-12-43-04-995.png!If You do not choose it then mentioned paramenter on operator card will not bee set during synchronization.Duration of synchronization depends on how many operators will be changed when process occurs. this process can take several minutes. Please run in while ERPXL (administrator module) is running as administrator.\\\'\', "Comment 56: \'Please", "Comment 57: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'", \'Comment 58: "Setting to integrated login is not enough. Users can be selected from the list\', \'Comment 59: but it still doesn\\\'t work. Please perform the necessary actions so that the integrated login works properly again."\', "Comment 60: \'Do users that have an issues with login into ERPXL through integrated login are wokning on theirs accounts in Windows domain. Is it the same domain as provided in ERP. Please an example of incorrect user configuration. Please provide information on witch account has he logon into windows account. Is there any message while user tries to login al integrated user into ERP system.\'", "Comment 61: \'For myself (Kremers) I have always been able to log in integrated (for years). After I removed integrated once and then put it back on integrated", "Comment 62: it suddenly stopped working. What happens at Synchronize Account. Will I only have a very limited amount of users left?!image-15!!image-16!!image-17!\'", \'Comment 63: \\\'It looks like there is an issue with domain controllerIm running*net group /domain "NL - Citrix - DH Premix Prod"* command in *HEUS* domain ant it has been proceed for*EMEA* domain. It gives information on limited number of domain group members.!image-2023-04-12-08-36-25-787.png!\\\'\', \'Comment 64: "The server resides in the EMEA domain\', "Comment 65: but the users in HEUS. So the group that is used should be HEUS\\\\\\\\NL - Citrix - DH Premix Prod.That\'s not an issue with the domain controller", \'Comment 66: it is just a different group"\', \'Comment 67: \\\'Synchronization data in ERPXL contains information on opertor NT account and it\\\\\\\'s NT SID id.!image-2023-04-13-13-07-59-433.png!Unfortunately I do not have access to this information in AD regardless of whether I log in to the HEUS or EMEA domain. It is possible that data in ERPXL is outdated.Please try to resynchronize data in ERP system with"Use NT authorization for this operator" paramenterset on and let me know if that solved this issue.\\\'\', \'Comment 68: \\\'I clicked on "NT-Login" and then the attached screen appeared after a few minutes.Do we now have to click on "Synchronice accounts or ERP XL" for further processing?!image-18!\\\'\', \'Comment 69: \\\'What is the status of this discussion?Bartłomiej Brzęk Yesterday 08:41It looks like there is an issue with domain controllerIm running net group /domain "NL - Citrix - DH Premix Prod" command in HEUS domain ant it has been proceed for EMEA domain. It gives information on limited number of domain group members.Martijn Meier Yesterday 14:36The server resides in the EMEA domain\', "Comment 70: but the users in HEUS. So the group that is used should be HEUS\\\\\\\\NL - Citrix - DH Premix Prod.That\\\\\'s not an issue with the domain controller", "Comment 71: it is just a different group\'", \'Comment 72: \\\'[[email protected]]Yes you shouldclick on "Synchronice accounts or ERP XL" for further processing\', \'Comment 73: byt be aware that all operators for selected domain group will be synchronized.Regarding the domain controller discussion.I do not have access to Heus domain\', \'Comment 74: I can not see any users in domain HEUS\', \'Comment 75: group "NL - Citrix - DH Premix Prod". I can not verify [[email protected]]information. I see that in EMEA domain for"NL - Citrix - DH Premix Prod" group there is limited number of users assign to that group.If "NL - Citrix - DH Premix Prod" group on different domains exchange information between domains and users SID is changing then this could be an source of that issue.I\\\\\\\'m no expert on the AD controller and its configuration\', "Comment 76: but it looks unusual.\'", "Comment 77: \'Hi", \'Comment 78: as you can see in this attachment from a server in the HEUS domain\', \'Comment 79: the group contains almost 90 users. Can we click the "Synchronize accounts..." button in the application without breaking any existing account configuration?!afbeelding!\\\'\', \'Comment 80: "As I wrote before\', \'Comment 81: I do not have access to this domain group. I can not confirm if those account are the same as accounts synchronized with ERPXL. I do not know if all accounts in ERPXL are still in provided domain group\', "Comment 82: with the same NT SID id\'s. You shuld check if provided domain group conatains all users needed.After synchronization if there will be any issues with user that shuld have access to ERP system as integrated login", \'Comment 83: You can always disable this feature for that one operator and let him login with user and password."]\']\nRelated Issues:\n[\'DGS-8616\', \'DGS-8637\', \'DGS-8647\']\n\n### End'} |
413 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8619\n\n### Instruction:\nIntakes are not being sent from DHP to DHC.\r\nAn example we have more intakes that are not synchronized to DHC at all.\r\n\r\nFor example, we have ASN-104/01/2023 and ASN-105/01/2023. Which are identical but one isn’t in DHC and the other one is. \r\n\r\nASN-104/01-23 is done in Vt-381/01/23 and ASN-105/01/2023 is done in VT-380/1/23. Both are closed around the same time. \r\n\r\n\n\n### Response:\n["Comment 1: [\'Hi,we need 8 working hours for analysis. Please accept.Regards.\'", "Comment 2: \'accepted\'", "Comment 3: \'[[email protected]]", "Comment 4: [[email protected]],Tutaj development został zrobiony trzeba podegrac nowy DHC Service\'", "Comment 5: \'Hello,after the developers analysis a new version of DHC Service Client will be prepared and uploaded for the solution.Regards.\'", "Comment 6: \'Buduję nową aplikację i wgram im na produkcję.\'", "Comment 7: \'Is it known when the new version of DHC Service will be installed?\'", "Comment 8: \'Hej", \'Comment 9: możemy przekazać termin klientowi\', "Comment 10: dzięki.\']"]\nRelated Issues:\n[\'DGS-8410\']\n\n### End'} |
414 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8618\n\n### Instruction:\nAfter sales orders created with a transport expense ; The transport detail is not visible when a Vehicle ticket is created from the sales order ; the VT document doesn`t show the transport detail ; \r\nsee attached document SO 1015 showing trans but not VT 1168 ? \r\n\n\n### Response:\n["Comment 1: [\'!image-3!!image-4!\'", "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 for the quick response ;\'", "Comment 4: \'Could You please bring more detailsPlease send a screen-shoot of example oftransport detail visible in VT.I compare VT you mentioned and it is similar.I am not sure if you are asking for some change section for VT similar to SO?\'", "Comment 5: \'Hey dear This problem just started since the day before yesterday . if you see all the VTs created from the SO which have transport ; they all show transport detail on documents ; See this or on the attached documents all VTs ; Because of the reason we print and give Customers the VT detail so when it is not visible couse a problem communicating with our sales workers !image001! *From:* Agnieszka Januszewska (Jira) <[email protected]> *Sent:* Friday", \'Comment 6: February 24\', "Comment 7: 2023 15:30 *To:* Gemechis Terefe <[email protected]> *Subject:* DGS-8618 Sales orders created with Transport ; transport not visible on Vehicle ticket Document !transport gemechis.PNG|thumbnail!\'", "Comment 8: \'Ok so item named trans2 is not visible on VT. I will check it.\'", "Comment 9: \'You can see the deference in SO 1013", \'Comment 10: SO1014 and SO 1015 / !image002! !image001! !image004! *This all VTs doesn`t have trans information when all the SO 1013,1014,1015 were all created with transport (Trans)* *See above VT and this ones which Trans is visible where all the above 3 trans not visible* ** !image003! ** ** *From:* Gemechis Terefe *Sent:* Friday\', \'Comment 11: February 24\', \'Comment 12: 2023 15:51 *To:* [email protected] *Subject:* RE: DGS-8618 Sales orders created with Transport ; transport not visible on Vehicle ticket Document Hey dear This problem just started since the day before yesterday . if you see all the VTs created from the SO which have transport ; they all show transport detail on documents ; See this or on the attached documents all VTs ; Because of the reason we print and give Customers the VT detail so when it is not visible couse a problem communicating with our sales workers !image003! *From:* Agnieszka Januszewska (Jira) <[[email protected]|mailto:[email protected]]> *Sent:* Friday\', \'Comment 13: February 24\', "Comment 14: 2023 15:30 *To:* Gemechis Terefe <[[email protected]|mailto:[email protected]]> *Subject:* DGS-8618 Sales orders created with Transport ; transport not visible on Vehicle ticket Document !image001-1!\'", "Comment 15: \'Yes please thanks !\'", "Comment 16: \'HelloI can see that someone use some procedure but there change on erp xl on article card the type was changed from type product to type cost.It was changed 22.02.2023 about 12.50Why it was changed ?!image-2023-02-27-14-03-49-848.png!\'", "Comment 17: \'Hey dear As I tried to understand the situation happened at moments is ;- # A sales officer mistakengingly created a SO with a trans of 1 kuntal or 100 kg where she was supposed create 101 kunatal not 1 kuntal or 101,000 kg ; # Then they tried create a trans so just for the mistaken 100 kunatl left to include ? so since then the system revoked Showing trans item on VT even if the Trans is visible on SO Since then they are revoked to create a SO with trans Regards!image001-2!\'", "Comment 18: \'They just tried create a SO just for the mistake left 100 kuntal ; just another SO only for this purpose ; Since it stopped allowing Regards *From:* Gemechis Terefe!image001-2!\'", "Comment 19: \'I asked you about changes on item with code TRANS2.Why the type of item was changed via database?\'", \'Comment 20: "SELECT * FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketPackedDispatchElements] where id in (\\\'7627D406-615F-45D7-9673-56FF9AE004B2\\\',\\\'9F4A44A3-C64D-41F9-B86B-9EAF58188D53\\\') --and ItemId=\\\'C6FCFBA4-A394-48BD-A9BE-1B64D8894D95\\\' select * from OrderElements where id=\\\'75DE5DFD-95B7-46A6-BFD8-C08BD723B1E6\\\'select cdn.TSToDate(Twr_LastModC,1),* from cdn.TwrKarty where twr_kod like \\\'trans2\\\'select top 100 * from cdn.HistoriaZmian where HIS_ObiNumer=\\\'7326\\\' or HIS_StaraWartosc=\\\'TRANS2\\\'select * from cdn.TwrGrupyselect cdn.TSToDate(1045918526,1)"\', "Comment 21: \'!image-2023-02-27-17-22-43-744.png!\'", "Comment 22: \'Please check this item in dhp it is set as unhandled", \'Comment 23: so the system is unable to put it to right VT element table. As I wrote before\', "Comment 24: what was the reason that you changed this type few days ago? !image-2023-02-27-17-52-42-109.png!!image-2023-02-27-17-52-42-109!\'", "Comment 25: \'Hello Dear ; I am responsible for system setting changes if it is requested or suggested by the Deheus or the company but I don`t do any changes with out asking or discussing with our professionals like you guys Kotrak . May be This is a mistake done by the other IT person that have access to our server Data base environment . So please let me know who tried to change this ; whether to help the sales officers or mistaken ? Could you please also help us set this right and suggest me how to put control over this kind of mistakes not to happen again ; Thanks !image001-3!!image002-1!\'", "Comment 26: \'Hello Yes I checked this on DHP and it is like you mentioned on email ; it is unhandled for both ; I still want to know who tried change via database ; so from now on ", \'Comment 27: the person must be aware of not doing changes with out discussing with the group ; and responsible for the problem happened dispatching ; Regards !image003! *From:* Gemechis Terefe *Sent:* Tuesday\', \'Comment 28: February 28\', \'Comment 29: 2023 07:58 *To:* [email protected] *Subject:* RE: DGS-8618 Sales orders created with Transport ; transport not visible on Vehicle ticket Document Hello Dear ; I am responsible for system setting changes if it is requested or suggested by the Deheus or the company but I don`t do any changes with out asking or discussing with our professionals like you guys Kotrak . May be This is a mistake done by the other IT person that have access to our server Data base environment . So please let me know who tried to change this ; whether to help the sales officers or mistaken ? Could you please also help us set this right and suggest me how to put control over this kind of mistakes not to happen again ; Thanks *From:* Agnieszka Januszewska (Jira) <[[email protected]|mailto:[email protected]]> *Sent:* Monday\', \'Comment 30: February 27\', "Comment 31: 2023 19:54 *To:* Gemechis Terefe <[[email protected]|mailto:[email protected]]> *Subject:* DGS-8618 Sales orders created with Transport ; transport not visible on Vehicle ticket Document !image001-3!!image002-1!\'", "Comment 32: \'About solution I may set previous setting for items Trans2 and Trans in erpxl ( type product in erpxl)In this task we have focused on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue", \'Comment 33: we may raise RootCause Analysis (RCA)task for you.Please\', "Comment 34: let us knowhow you wish us to proceed.\'", "Comment 35: \'Hey Dear We need the solution bro As soon as possible ; we need you set us to the pervious setting for both items (Tran & Tran2). Thanks The only reason we asked to investigate was just to inform or warn and explain the consequences to the user . so this won`t happen again . Thanks very much again Regards\'", "Comment 36: \'!newsettings.PNG|thumbnail!\'", "Comment 37: \'Hello I set this to codes", "Comment 38: so in new vt it be working fine again.Please remember that for vt module in dhp types service and costs are unhandled.!newsettings.PNG!\'", "Comment 39: \'Hello Dear I really want appreciate the effort and thanks very much ; So now we have no problem of including Trans item in VT list Thanks again!image001-4!\']"]\nRelated Issues:\n[]\n\n### End'} |
415 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8617\n\n### Instruction:\nThe IPOR-00000009/23/YGM - USD Currency Fx-Rate is 2983 MMK. When we check the currencies table for Jan 2023. I could not find that rate. Could you please check?\n\n### Response:\n["Comment 1: [\'[^Exchange Rate_CDN.xlsx] _(11 kB)_!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 TOP (1000) [WaE_Symbol] ,cdn.tstodate([WaE_KursTS],1) ,[WaE_Lp] ,[WaE_KursM] ,[WaE_KursL] ,[WaE_OpisKursu] FROM [CDNXL_Myanmar].[CDN].[WalElem] where WaE_Symbol=\\\'usd\\\' and WaE_KursL=\\\'2983.00\\\' order by 2 desc{code}"\', \'Comment 4: "This currency is from 12/30/2022 !screenshot-2! It was the last of this day in 2022\', \'Comment 5: the next one is from 03/01/2023 and that one should be on document.But it looks like it wasn\\\'t added then. Currently when checking the rate from 03/1/2023 is being added.Regards."\', "Comment 6: \'Hi", \'Comment 7: I have 2 questions:1) Do CDN system take "system date"\', "Comment 8: to get Fx-rate? Not server date to get Fx-Rate.2) I am not clear about 03-Jan-2023? Could you please elaborate more?\'", "Comment 9: \'Hello,the date is taken from XL & as for the date of January 3rd it was the last one before January 5th(looking now).\'", "Comment 10: \'Hi,I got it. Please close the Ticket. \']"]\nRelated Issues:\n[]\n\n### End'} |
416 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8616\n\n### Instruction:\nBatch off payments shows strange signs.\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: \'myślę", "Comment 4: że reset widoku okna powinien pomóc\'", "Comment 5: \'zapytam go", \'Comment 6: za chwilę mam spotkanie z Ghaną\', "Comment 7: to będzie musiał poczekać :Pw sprawie NAV\'", "Comment 8: \'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 9: \'Making the last batch last week the batch was oke.A moment later displaying it again the same strange screen occurred.When making a new batch this week the same strange screen occures.\'", "Comment 10: \'Please restore the default view settings !image-2023-02-23-12-47-32-936.png|width=847,height=389!Regards\'", "Comment 11: \'But this does not have bloking impact on producing product or deliver product. So kindly approve lowering priority to P2.\'", \'Comment 12: "jak to nie pomoze to bedzie trzeba wyczyscic formatowanie list{code:java}---szukamy operatoraselect *from cdn.OpeKartywhere Ope_Ident = \\\'SKO\\\'--szukamy powiazane z nim formaty listselect *from cdn.FormatyListwhere FLS_IDOperatora = 22--zmieniamy powiazanie formatow na dowolnego nieustniejacego operatoraupdate cdn.FormatyListset FLS_IDOperatora = 888888where FLS_IDOperatora = 22--jesli wszystko gra i buczy to usuwamy wpisydelete from cdn.FormatyListwhere FLS_IDOperatora = 888888{code}"\', "Comment 13: \'It is critical because we can not do anny paymentYour advice is restore the default view setting. My question is how to do this?Someting other strange thing appears.I had saved my own login.Afther warts i could not login and had to type in a password.Then the the message off integrated login was shown.Afther unlink : Block different than integrated login can work in the system without typing a password.!image-1!!image-2!!image-3!!image-4!\'", "Comment 14: \'Is there a problem with integrated login afher saving a user?Added new user PWIJ als can not get in the system\'", "Comment 15: \'User is NWIJ\'", "Comment 16: \'When i vieuw the screen there is no problem!image-5!\'", "Comment 17: \'To restore default sysstem settings", "Comment 18: please try!image-2023-02-23-14-17-55-072.png!\'", "Comment 19: \'Have exited system after each modification or just used Change Operator?!image-2023-02-23-14-37-59-087.png!\'", "Comment 20: \'Some onformation for ticket DGS-8620 about integrated login has been typed in this ticket", "Comment 21: Sorry for that. Integrated login is ticket dgs-8616.\'", "Comment 22: \'So what about batch of payments? Is it configured properly now? Have you reset the view?Regards\'", "Comment 23: \'Window Default Setting was the solution of the problem.Verry strange the setting disapeared. What can be the reason.\'", "Comment 24: \'You have very old version of ERP system", \'Comment 25: this may be one of the reasons. For exact reason\', \'Comment 26: we may raise RCA task.Please\', "Comment 27: let us know what would be next step.Regards\'", "Comment 28: \'Is : very old version of ERP system an general reason for lot of problems? Please Close ticketThank you\'", "Comment 29: \'I did not mention that for most / a lot of problems", "Comment 30: but for this particular one - it is highly possible.Thank you.Regards\']"]\nRelated Issues:\n[\'DGS-8620\']\n\n### End'} |
417 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8615\n\n### Instruction:\nSystem niepoprawnie naliczył ekwiwalent za urlop pracownikowi Filiński Karol. Wynagrodzenie zasadnicze nie zostało ujęte w podstawie.\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: "Przy wyliczaniu ekwiwalentu należy zwrócić uwagę na kilka elementów:{color:#394754}Proszęzwrócić uwagę na jakiej liście płac zostaje naliczany ekwiwalent. Ekwiwalent powinien być naliczony na liście płac utworzonej za ostatni miesiąc zatrudnienia pracownika.{color}{color:#394754} Dodatkowo pr{color}oszę zweryfikować czy poprawnie wprowadzono datę zwolnienia pracownika. Data zwolnienia powinna zostać odnotowana w bieżącym zapisie historycznym pracownika\', \'Comment 3: a nie poprzez aktualizację formularza danych kadrowych. Jeżeli zwolnienie pracownika zostało odnotowane poprzez aktualizację zapisu\', \'Comment 4: proszę usunąć zbędny zapis.{color:#494949}W kolejnym kroku\', "Comment 5: w celu poprawnego wyliczenia składnika \'Ekwiwalent za niewykorzystany urlopu\'", \'Comment 6: należy przeliczyć limity nieobecności pracownika. Limit / limity nieobecności na rok zwolnienia pracownika powinny mieć okres zawężony do daty zwolnienia pracownika. Jeżeli na liście limitów byłby limit zawierający niepoprawne dane (okres obowiązywania limitu po dacie zwolnienia pracownika)\', \'Comment 7: proszę usunąć limit / limity na bieżący rok i dodać go ponownie. {color}"\', "Comment 8: \'Please close to task.\']"]\nRelated Issues:\n[]\n\n### End'} |
418 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8614\n\n### Instruction:\nI\'ll write an e-mail\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: \'What is the status of this?\'", \'Comment 3: "Hello,[[email protected]]We didn\\\'t receive any email with details about this task\', \'Comment 4: can you verify is this task actual or send us information what should be done in this topic.Regards"\', "Comment 5: \'{color:black}No actions seen here.{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:* Mitch van Bovene (Jira) <[email protected]> *Verzonden:* dinsdag 21 maart 2023 11:50 *Aan:* Jong", "Comment 6: Christine de <[email protected]> *Onderwerp:* DGS-8614 Registered document not visible on feedsale FE-N/0008 \'", "Comment 7: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Resolve this as done.. I really don’t know what it was anymore.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* dinsdag 21 maart 2023 12:00 *Aan:* Jong", "Comment 8: Christine de <[email protected]> *Onderwerp:* DGS-8614 Registered document not visible on feedsale FE-N/0008 \']"]\nRelated Issues:\n[]\n\n### End'} |
419 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8613\n\n### Instruction:\nSee attached example: I think this is an issue for the dev team: Due to some ERP bug, a delete message for a load is send multiple times (30x in this case). In DHP the load is multitimes created. As the loadnumber should be the key here, how is this possible? \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: "Jest tego więcej ale mają różne numery !screenshot-1! !screenshot-2! {code:java}SELECT count(ForeignNumber),ForeignNumber FROM [DHCountry_NL_AS400_PROD].[dbo].[ShippingNotices] -- where ForeignNumber like \\\'8_L000133584\\\' group by ForeignNumber having count(ForeignNumber)>10{code}"\', "Comment 4: \'The document appears so many times in the list because of the different numbers for the document - as seen in DHC: !screenshot-3! Was it correctly canceled from the ERP?\'", "Comment 5: \'It was incorrectly cancelled in TMS system. But why does DHC create multiple lines? Load number is not the key here?\'", \'Comment 6: "[[email protected]]after canceling order\', \'Comment 7: mapping key is deleted to avoid problem that we had in past with duplicated TransactionIDs on different order elements\', "Comment 8: that\'s why if we canceled previous because of lack of order element", \'Comment 9: and removed mapping and that why new mapping and new order is created"\', "Comment 10: \'Thanks for explanation", "Comment 11: ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'} |
420 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8612\n\n### Instruction:\nHi, \r\n\r\nThe VT-6450/20/23 is "dispatch VT". We have 2 weight-bridge. When the truck of VT-6450/20/23 weight on WB-1 for departure, we have another truck on WB2 for intake. While user close the VT-6450, user didn\'t encounter any issue. After some time user realized that VT-6450 VT header information is gone. I do see VT status change as "Intake Inprogress". Could you please check why that could happen?\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello", \'Comment 3: is this a single case\', "Comment 4: is the problem only with this VT?\'", "Comment 5: \'Hi", "Comment 6: So far we have 2 cases like that. first cases around 6 months ago.\'", "Comment 7: \'Change logging is disabled for VT", "Comment 8: we can run it and check for another case if it occurs.Change logging will be then active all the time.What about the current one can be canceled and reissued?\'", "Comment 9: \'{code:java} FROM [DHP_YAN].[dbo].[VehicleTicketHeader] v where VtH_Id = 390632{code}\'", "Comment 10: \'On this case", \'Comment 11: we will handle alternative solution for current VT. If new case happen\', "Comment 12: are we able to check our own?\'", "Comment 13: \'Hello", "Comment 14: yes change logging for the VT header has been started. We will have data for analysis.\'", "Comment 15: \'Hi", "Comment 16: Please close this ticket and I will raise new ticket if we encounter again.\']"]\nRelated Issues:\n[]\n\n### End'} |
421 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8611\n\n### Instruction:\nIt seems that ERP integration communication is broken.\r\nI see that orders are being delivered succesfully to the ERP integration service, but are not processed in DHC.\r\nAlso no entries in the communication logs. It look like something is not running.\r\nCan you please fix this ASAP. This is blocking our logistical processes\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'!image-2023-02-23-08-12-30-871.png!\'", "Comment 3: \'Hello", \'Comment 4: Process is verified\', "Comment 5: in another request DGS-8608.Regards\'", \'Comment 6: "I don\\\'t see that request. I think the problem is not solved"\', \'Comment 7: "Hello\', \'Comment 8: Message processing is in progress ERP integration.I\\\'m asking you to being patient.Regards"\', "Comment 9: \'Dear Wijnand,The Queues are empty now so DHC should work properly now. Please confirm and let me know if we can close this task and task related under DGS-8608Regards!image-2023-02-23-15-40-11-023.png!\'", "Comment 10: \'This task can be closed\']"]\nRelated Issues:\n[\'DGS-8608\']\n\n### End'} |
422 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8610\n\n### Instruction:\nGoodmorning,\r\n\r\nIn the xml file on DHP Veghel for Salesorder: SO000069460 there is missing some data. The product label information is missing.\r\nIt\'s important information for our customers.\r\n\r\nAs attachment hereby the xmldata that we recieved on DHP and the printscreen of the itemcode 318254 and itemcode 318547 and label that belongs to this itemcodes at DHP and DHC.\r\n\r\nPlease could you have a look at this problem?\r\nThis example is not the only one, at the moment, I got more questions about this type of issue.\r\n\r\nKind regards,\r\n\r\nGerard\n\n### Response:\n["Comment 1: [\'[^Afleverbon_ve_SO000069460_6EE64133-5DB2-2B47-AB1B-3D344B06812F.xml] _(8 kB)_!DHC_Item_318254.PNG|thumbnail!!DHC_Item_318547.PNG|thumbnail!!DHP_Item_318254.PNG|thumbnail!!DHP_Item_318547.PNG|thumbnail!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "tu jest inna sytuacja dla podengo zgłoszenia nie ma rozbieżnosci miedzy recepotura na elemencie a na vteselect i.Code\', \'Comment 4: r.EntityId rc_EntityId\', \'Comment 5: r.Version\', \'Comment 6: r.Subversion ,--,i.ItemBaseWeight\', \'Comment 7: g.Code ,-- la.Value\', \'Comment 8: la.No\', \'Comment 9: la.Type\', \'Comment 10: la.LabelType\', \'Comment 11: la.Sequence,ln.Name\', \'Comment 12: ln.Quantity\', \'Comment 13: ln.QuantityUnit,lnt.Name\', \'Comment 14: lnt.Type\', \'Comment 15: ln.Description,ln.No\', \'Comment 16: ln.IsHeader\', \'Comment 17: ln.Ordinal\', \'Comment 18: lnt.*,lnt.Name,--,--lw.Code\', \'Comment 19: lw.Description,lt.Description,ltf.Translation --\', "Comment 20: ltf.Idfrom [DHPlantPCSBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPCSBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantIdjoin [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrients ln on ln.id = l.Idleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrientTypes lnt on lnt.Id=ln.LabelNutrientTypeId--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelWarnings lw on lw.Id=l.Id and lw.No=ln.Noleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslations lt on lt.LanguageId = g.Idleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslationFields ltf on ltf.Id=lt.Id and ltf.LabelNutrientTypeId=ln.LabelNutrientTypeId--and ltf.No=ln.Nowhere 1=1and ln.No > 0aND ln.IsHeader = 0--and r.Id in (\'8FC6DDFB-D79A-4F03-88F0-65F41AC40743\')--,\'9274CACB-B6D2-4603-BB2B-75BFFF335BAB\',\'DC3E0094-694A-4019-8726-73BFB4505B40\',----\'D16DF237-8B1F-47E0-A33C-422CF89826FA\',\'E9A39A85-600E-45EF-A6F6-396DE48BD141\')and--and l.Id=andi.Code = \'318254\'and g.Code = \'DE\'order by r.Version desc", \'Comment 21: Subversion desc \', \'Comment 22: lnt.Type\', \'Comment 23: ln.Ordinalwyniki są ale plik jest bez zawartosci dla labelki"\', "Comment 24: \'After analisys for orderSO000069460 we have diffrent situations then in linked dgs.Could please provide backup of plant databases with current data ( from yesterday)!image-2023-02-24-12-21-21-913.png!\'", "Comment 25: \'Good morning Agnieszka,Can you tell me which databases are involved?Regards,Gerard\'", "Comment 26: \'Thank you please provide bakcups for databaseDHPlantPCSBusinessLogicMain,DHPlantVCBusinessLogicMain,DHPlantWMSBusinessLogicMain,DHPlantStockBusinessLogicMain,DHPlantProdBusinessLogicMain\'", "Comment 27: \'Goodmorning Agnieszka,Question: are you able to connect to the DHVD01DB47 to access the backup?The backup is 14,1 Gb on: G:\\\\\\\\MSSQL\\\\\\\\Veghel\\\\\\\\Backup\\\\\\\\20230302 at the DHVD01DB47.RegardsGerard \'", "Comment 28: \'The IP serwer is :172.23.1.83?I can not log to these rdp nor with ip address nor with usingDHVD01DB47?Maybe You may add this to location when we have access f.e:172.23.1.67", "Comment 29: or172.23.1.88?\'", "Comment 30: \'Good morning Agnieszka,We added your account to a shared folder.Your colleque: Maciej Dobrzanski has also the possibility and access to this share and the backup who is available in this share-folder.Please could yo try it again?Regards,Gerard \'", "Comment 31: \'Could you bring full path and ip for the server as I asked you beforeIs that172.23.1.67", "Comment 32: or172.23.1.88? Or any other IP?I tried to find in on172.23.1.88 via network!image-2023-03-06-12-14-59-115.png|width=481,height=172!\'", "Comment 33: \'Hi Agnieszka,hereby,\\\\\\\\\\\\\\\\DHVD02DB47\\\\\\\\20230302\\\\\\\\Regards,Gerard\'", "Comment 34: \'!image-2023-03-06-14-55-04-226.png!\'", "Comment 35: \'it works - thank you,\'", "Comment 36: \'!image-2023-03-13-13-29-39-553.png!\'", \'Comment 37: "select * from DHPlantProdBusinessLogicMain.dbo.Labels where ItemId in (\\\'E017E700-8694-4F78-8C3C-64CE79E8F713\\\',\\\'5A4BBFE2-1DE6-4C30-A3D4-0A649BDE7E1C\\\') and LanguageId = \\\'EA2B7C3F-6277-44A2-9143-B99AF97B34D2\\\' select * from DHPlantProdBusinessLogicMain.dbo.Recipes where Id in (\\\'9C545083-6BE6-4B7A-91B4-C7C2215145A4\\\'\', \'Comment 38: \\\'972115A5-07A7-4E90-8681-D93C6BD5F44D\\\')"\', "Comment 39: \'[^SPS_admin_13032023_141759677_40bf50b4-41e4-47f6-8358-5734b171a5e4.xml] [^SPS_admin_13032023_141759918_7b72a90c-9c0c-4a74-a571-c9eca251cb5b.xml] [^SPS_admin_13032023_141931502_f4ec70cf-9047-4c97-9155-87e6a6db8538.xml] [^SPS_admin_13032023_141931574_1e1ae686-d536-4587-bad4-8c3f45837575.xml]\'", "Comment 40: \'Hello,Right know the xml are generate with descriptions. In this case problem was with missing recipe version in VT module", \'Comment 41: for that recipe and order version of labels 3 and 4 were used after resending them from dhc\', "Comment 42: xml seems to be complete.BR\'", "Comment 43: \'May we close the task?\'", "Comment 44: \'Gooda afternoon Agnieszka,Thanks for support. You may close this ticket.Have a nice weekend.Kind regards,Gerard\']"]\nRelated Issues:\n[\'DGS-8609\']\n\n### End'} |
423 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8609\n\n### Instruction:\nGoodmorning,\r\n\r\nIn the xml file on DHP Veghel for Salesorder: SO000068853 there is missing some data. The product label information is missing.\r\nIt\'s important information for our customers.\r\n\r\nAs attachment hereby the xmldata that we recieved on DHP and the printscreen of the itemcode 303436 and label that belongs to this itemcode at DHP and DHC.\r\n\r\nPlease could you have a look at this problem?\r\nThis example is not the only one, at the moment, I got more questions about this type of issue.\r\n\r\nKind regards,\r\n\r\nGerard\n\n### Response:\n["Comment 1: [\'[^Afleverbon_ve_SO000068853_58B7D554-2FAC-4E47-B0B9-364B1D7C7914.xml] _(5 kB)_!DHC_Item_303436.PNG|thumbnail!!DHP_Item_303436.PNG|thumbnail!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Dla podanego przykładu brakuje sekcji dla nl<Field_Label> <Field_LabelProductionDate>15-02-2023</Field_LabelProductionDate> <Field_LabelExpirationDate>15-08-2023</Field_LabelExpirationDate> <Field_LabelReferenceCode>VE150223</Field_LabelReferenceCode> <Field_LabelPackingSize>0 KG</Field_LabelPackingSize> <Field_LabelLanguage>de</Field_LabelLanguage> </Field_Label>\'", \'Comment 4: "[[email protected]]tego co widze dla towaru\\\'303436\\\' dla obu jezyków labalki saw module prod i pcs widzę że jakieś gdc na to będę wdzięczna jak zerknieszFROM [DHPlantMaintBusinessLogicMain].[dbo].[Labels] where id in ( \\\'B1D0A992-B3D3-451B-AB96-1DAAE5091080\\\'\', "Comment 5: \'E4EAFCB0-7491-4B35-A779-35116DD03094\'", "Comment 6: \'9ED4AF5F-F559-4A40-A78C-3B62D6366C0E\'", "Comment 7: \'1A7858A2-530D-4041-B6CE-6CB0D2021B43\'", "Comment 8: \'6A032472-96C7-4CD9-997B-F51E49394236\'", \'Comment 9: \\\'AA36CBD5-323B-4264-B74F-D58CF8AE85DC\\\')W logach nic nie widze."\', \'Comment 10: "select i.Code\', \'Comment 11: I.Name\', \'Comment 12: --\', \'Comment 13: r.Version\', \'Comment 14: r.Subversion,L.ProductDescription1 Label_ProductDescription1\', \'Comment 15: L.ProductDescription2 Label_ProductDescription2\', \'Comment 16: L.ProductDescription3 Label_ProductDescription3\', \'Comment 17: L.ProductType Label_ProductType--,l.Caution,,la.Value--,n.Code\', "Comment 18: n.Name--,r.*--,l.FeedingGuide--,ltf.Translationfrom [DHPlantPCSBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPCSBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantIdjoin [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageId--left outer join [DHPlantProdBusinessLogicMain].[dbo].RecipeElements rn on rn.id=r.Id--left outer join [DHPlantProdBusinessLogicMain].[dbo].Items n on n.id=rn.ItemIdleft left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelAdditionalTexts la on la.id=l.Id--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrients ln on ln.id = l.Id--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrientTypes lnt on lnt.Id=ln.LabelNutrientTypeId--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelWarnings lw on lw.Id=l.Id and lw.No=ln.No--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslations lt on lt.LanguageId = g.Id --left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslationFields ltf on ltf.Id=lt.Id --and ltf.No=ln.No and ltf.LabelNutrientTypeId=ln.LabelNutrientTypeIdwhere 1=1--and r.Id=--and l.Id in (\'B1D0A992-B3D3-451B-AB96-1DAAE5091080\',\'E4EAFCB0-7491-4B35-A779-35116DD03094\',\'9ED4AF5F-F559-4A40-A78C-3B62D6366C0E\',\'1A7858A2-530D-4041-B6CE-6CB0D2021B43\',\'AA36CBD5-323B-4264-B74F-D58CF8AE85DC\',\'6A032472-96C7-4CD9-997B-F51E49394236\')--and i.Code = \'303436\'--and g.Code = \'NL\'order by r.Version desc", \'Comment 19: Subversion desc--\', \'Comment 20: ln.Ordinal\', \'Comment 21: ln.No"\', "Comment 22: \'!image-2023-02-23-15-00-11-800.png!\'", \'Comment 23: "select i.Code\', \'Comment 24: r.EntityId rc_EntityId\', \'Comment 25: r.Version\', \'Comment 26: r.Subversion --\', \'Comment 27: i.ItemBaseWeight--\', \'Comment 28: g.Code \', \'Comment 29: la.Value\', \'Comment 30: la.No\', \'Comment 31: la.Type\', \'Comment 32: la.LabelType\', \'Comment 33: la.Sequence\', \'Comment 34: ln.Name\', \'Comment 35: ln.Quantity\', \'Comment 36: ln.QuantityUnit,lnt.Name\', \'Comment 37: lnt.Type--\', \'Comment 38: ln.Description--,ln.No\', \'Comment 39: ln.IsHeader\', \'Comment 40: ln.Ordinal--\', \'Comment 41: lnt.*--,lnt.Name--,lw.Code\', \'Comment 42: lw.Description,,lt.Description,ltf.Translation --\', "Comment 43: ltf.Idfrom [DHPlantPCSBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPCSBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantIdjoin [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrients ln on ln.id = l.Idleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrientTypes lnt on lnt.Id=ln.LabelNutrientTypeId--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelWarnings lw on lw.Id=l.Id and lw.No=ln.No left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslations lt on lt.LanguageId = g.Id left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslationFields ltf on ltf.Id=lt.Id and ltf.LabelNutrientTypeId=ln.LabelNutrientTypeId--and ltf.No=ln.No where 1=1and ln.No > 0aND ln.IsHeader = 0and r.Id in (\'27772437-0268-4B71-A960-A943934FB1B5\')--,\'9274CACB-B6D2-4603-BB2B-75BFFF335BAB\',\'DC3E0094-694A-4019-8726-73BFB4505B40\',----\'D16DF237-8B1F-47E0-A33C-422CF89826FA\',\'E9A39A85-600E-45EF-A6F6-396DE48BD141\')and--and l.Id=and i.Code = \'303436\'and g.Code = \'DE\'order by r.Version desc", \'Comment 44: Subversion desc \', \'Comment 45: lnt.Type\', \'Comment 46: ln.Ordinal"\', \'Comment 47: "na bazie jestselect i.Code\', \'Comment 48: r.EntityId rc_EntityId\', \'Comment 49: r.Version\', \'Comment 50: r.Subversion ,--\', \'Comment 51: i.ItemBaseWeight\', \'Comment 52: g.Code ,-- la.Value\', \'Comment 53: la.No\', \'Comment 54: la.Type\', \'Comment 55: la.LabelType\', \'Comment 56: la.Sequence\', \'Comment 57: ln.Name\', \'Comment 58: ln.Quantity\', \'Comment 59: ln.QuantityUnit,lnt.Name\', \'Comment 60: lnt.Type--\', \'Comment 61: ln.Description--,ln.No\', \'Comment 62: ln.IsHeader\', \'Comment 63: ln.Ordinal--\', \'Comment 64: lnt.*--,lnt.Name--,lw.Code\', \'Comment 65: lw.Description,,lt.Description,ltf.Translation --\', "Comment 66: ltf.Idfrom [DHPlantPCSBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPCSBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantIdjoin [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrients ln on ln.id = l.Idleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrientTypes lnt on lnt.Id=ln.LabelNutrientTypeId--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelWarnings lw on lw.Id=l.Id and lw.No=ln.No left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslations lt on lt.LanguageId = g.Id left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslationFields ltf on ltf.Id=lt.Id and ltf.LabelNutrientTypeId=ln.LabelNutrientTypeId--and ltf.No=ln.No where 1=1and ln.No > 0aND ln.IsHeader = 0and r.Id in (\'27772437-0268-4B71-A960-A943934FB1B5\')--,\'9274CACB-B6D2-4603-BB2B-75BFFF335BAB\',\'DC3E0094-694A-4019-8726-73BFB4505B40\',----\'D16DF237-8B1F-47E0-A33C-422CF89826FA\',\'E9A39A85-600E-45EF-A6F6-396DE48BD141\')and--and l.Id=and i.Code = \'303436\'and g.Code = \'DE\'order by r.Version desc", \'Comment 67: Subversion desc \', \'Comment 68: lnt.Type\', \'Comment 69: ln.Ordinal"\', "Comment 70: \'!image-2023-02-23-15-28-58-028.png!\'", "Comment 71: \'[[email protected]]od dla podanego przykładu zwraca wyniki ( select drugi)konfig się zgadza!image-2023-02-23-15-38-30-748.png!\'", "Comment 72: \'[[email protected]] poprozmawia z [[email protected]] jak można to zdebugować\'", \'Comment 73: "select ii.Code as itemcode\', \'Comment 74: o.DocumentNumber as salesordernumber\', \'Comment 75: o.ForeignDocument\', \'Comment 76: bp.Code as customercode\', \'Comment 77: e.No as linenumber\', "Comment 78: (select top 1 r.EntityId rc_EntityIdfrom [DHPlantPcsBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPcsBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantIdjoin [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdwhere 1=1and i.id = ii.idand g.Code = \'DE\'order by r.Version desc", \'Comment 79: Subversion desc) as recipeidfrom [DHPlantPcsBusinessLogicMain].dbo.Orders oinner join dbo.OrderElements e on e.id = o.idinner join dbo.items ii on ii.id = e.itemidinner join [DHPlantPcsBusinessLogicMain].dbo.BusinessPartners bp on bp.Id = o.TargetBusinessPartnerIdwhere o.ForeignDocument = \\\'SO000068853\\\'and ii.code = \\\'303436\\\'select * from [DHPlantPcsBusinessLogicMain].[dbo].Recipes where EntityId=55051select * from labels where itemid=\\\'2BA9DE6F-A5D0-41E6-882F-C2ED8D1DE942\\\' and VersionNo=348"\', "Comment 80: \'[^SPS_admin_24022023_093103852_f862e1be-81de-4d99-b748-60822d573275.xml]\'", \'Comment 81: "wywgenerowany wydruk do folderu test \', \'Comment 82: ( vt 695)select * from Orders where ForeignDocumentNumber=\\\'SO000068853\\\'select top 10 * from VehicleTickets where id=\\\'FCA3DDA3-5F45-4B6B-AD1D-EFA42F468815\\\'select * from items where code =\\\'303436\\\'[^SPS_admin_24022023_093103852_f862e1be-81de-4d99-b748-60822d573275.xml]^osttania label i recipe doa tego itemu to aktualnie wersja 348^^recipeid r.Id=\\\'164BD6FE-FB6A-498C-9FCC-F9FFE274F93C^^wynik zwraca elementy^w xml jest tak!image-2023-02-24-09-39-03-794.png!"\', \'Comment 83: "receptura na elemencie vt jest na inny itemselect * from Orders where ForeignDocumentNumber=\\\'SO000068853\\\'select top 10 * from VehicleTickets where id=\\\'FCA3DDA3-5F45-4B6B-AD1D-EFA42F468815\\\'select * from items where code =\\\'303436\\\'select RecipeId,* from VehicleTicketBulkDispatchElements where ItemId=\\\'2BA9DE6F-A5D0-41E6-882F-C2ED8D1DE942\\\' and OrderId=\\\'38B4566B-0765-4704-B733-65B707CB6FB5\\\'!image-2023-02-24-09-49-16-990.png!"\', "Comment 84: \'[[email protected]]ok więc dla podanego VT 695 jest z niewiadomych przyczyn użyta receptura na inny towar ( screeny powyzej) i wtedy nie ma takiej labelki:!image-2023-02-24-09-57-24-242.png!\'", \'Comment 85: "na szybko select na vt bulk elementy gdzie item z recipe id jest inne niż na vte.jest 64 takich receptur z 2023 rokuselect distinct(RecipeId),i2.code as itemforVT\', \'Comment 86: i.code as itemforrecipe from VehicleTicketBulkDispatchElements vte join [DHPlantProdBusinessLogicMain].[dbo].recipes r on vte.RecipeId=r.Id join Items i on i.id= r.ItemId join items i2 on i2.id=vte.ItemIdwhere vte.ItemId<>r.ItemId and r.ImportDate>\\\'2023-01-01 01:02:00.3918811\\\'"\', \'Comment 87: "podmiana receptury na vt 695--update VehicleTicketBulkDispatchElements --set RecipeId=\\\'164BD6FE-FB6A-498C-9FCC-F9FFE274F93C\\\'--where ItemId=\\\'2BA9DE6F-A5D0-41E6-882F-C2ED8D1DE942\\\' --and OrderId=\\\'38B4566B-0765-4704-B733-65B707CB6FB5\\\'-- recipe na inny item-- 8FC6DDFB-D79A-4F03-88F0-65F41AC40743"\', "Comment 88: \'[^SPS_admin_24022023_114702900_ffa731c1-ecfe-4371-bc33-be1e017001cf-1.xml]\'", \'Comment 89: "[^SPS_admin_24022023_114702900_ffa731c1-ecfe-4371-bc33-be1e017001cf.xml]HelloWe analyzed the problem and it appears that for some VT items is assigned from pcs recipe to another item. Therefore\', "Comment 90: the system does not retrieve information to the label in the case of order SO000068853 was assigned a recipe for the item 303641 and SO and VT refer to the item with the code 303436\'", \'Comment 91: we can see that for 303436 such Vt is more. For the order of the item VT 695 we changed the recipe to the last one for the commodity 303436 and on the printout you can see the data about the label( attached xml). In this situation\', \'Comment 92: on the remaining reported in this and related shuffle\', \'Comment 93: do we change it recipe to VT?I also ask for verification on the pcs side\', \'Comment 94: as it is pcs that sends the information in RECIPE!image-2023-02-24-12-00-07-320.png!"\', "Comment 95: \'[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%20XML%20WERYFIKACJA%20WYDRUKU%20SPS%20SalesPackingSlip%7C2057108A-87BD-422C-84FB-79682EEDF1C9%2F%29]\'", \'Comment 96: "In Additional technologies I could not find it\', \'Comment 97: but at the time of the order\', \'Comment 98: there must have been an additional technology for this item:In order SO000068853 (SO-6269/2/23) the item 303436 was ordered (ItemCodeCustomer) but item 303641 was send to produce. See attached json for sales order to PCSTrip 00976953 was assigned. It contains 3 orders\', "Comment 99: all for the same item. I found that PCS message for the dispatch message of this trip contained two different recipeId\'s for those three orders. See attached json from PCS. In case the plant produces and load another code then was ordered", \'Comment 100: in the dispatch we expect the code that was ordered by the customer (303436) and the recipeId of the code that was produced (e.g. recipeId of 303641). This is as designed for derived items because the plant does not have a recipe for the item that was ordered.[^20230313_trip_00976953_from_PCS.json] _(1 kB)_"\', "Comment 101: \'Attachement order sent to PCS[^20230313_order_SO000068853_to_PCS.json] _(4 kB)_\'", "Comment 102: \'Info od Tomka Koźmina:Tu by się przydało napisać takie spore zapytanie parametryzowane np. po numerze SO # co wpadło do DHC # co przeleciało do DHP # co poleciało do PCS # co zostało wyprodukowane # co poleciało spakowane - jeśli było # co poleciało na wydruki (baglabel i SPS) # co było na VTi to wszystko ze wskazaniem ItemCode", \'Comment 103: ItemCodeCustomer\', \'Comment 104: RecipeID\', \'Comment 105: RecipeVersion\', \'Comment 106: etc.napisać raz\', "Comment 107: udostępnić im jako raportin niech sami sobie to śledzą\'", \'Comment 108: \\\'Hello The original content of the task wasIn the xml file on DHP Veghel for Salesorder: SO000068853 there is missing some data. The product label information is missing. It\\\\\\\'s important information for our customers.As attachment hereby the xmldata that we recieved on DHP and the printscreen of the itemcode 303436 and label that belongs to this itemcode at DHP and DHC.And you send as xml and sreenshot where for that SO was a problem in that area of that printout : Field_LabelContents.!image-2023-02-24-09-39-03-794.png!We analyzed the code and procedure that generates these printouts.We see that what I response to you at 24,02.2023 that there are diffrent recipes and item in related objects in dhp,and send you an XML to verifyAnd then in your response at 13.03You are not bringing information about this XML printout if the description is correct:If yes may we close this task ?If not were it isincorrect?Your response to be about different topics more about this 2 "problematic" items.As I can see in Jira Both of this codes have some historyhttps://helpdesk.kotrak.com/browse/DGS-8196here we had situation were "An additional technology VE303436 was created on 12 December for derived item 303436. Code to produce is 303641.\\\\\\\'as solution AT was removed \', \'Comment 109: AT was removed also here and product definition flag has been changed:https://helpdesk.kotrak.com/browse/DGS-8125,https://helpdesk.kotrak.com/browse/DGS-8127 And here where Bartłomiej and Przemek verify that codes and recipes again:https://helpdesk.kotrak.com/browse/DGS-8735So if there is a need to analyze recipes and codes in a given period of time for a specific commodity code\', \'Comment 110: please create a new Task. However\', "Comment 111: if at this point AT has been deleted it may be very difficult due to the lack of key data.Could you please provide another task for that or you prefer to create an RCA in that matter?We could also create you some kind of useful procedure/report from database that will show youwhat was in the DHCwhat was sent to DHPwhat was sent to PCSwhat was producedwhat was bagged - (if any)what was printed (baglabel and SPS)what was on VTif you are interested in this type of report please create a SR ticket.\'", "Comment 112: \'Hello Agnieszka", "Comment 113: this ticket can be closed.\']"]\nRelated Issues:\n[\'DGS-8610\']\n\n### End'} |
424 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8608\n\n### Instruction:\nOrder SO000073172 is in DHC but is not arriving in DHP. In the communication log a deadlock is mentioned. \r\nCan you please help as this customer needs their feed tomorrow morning. \r\n\r\n\r\n\r\nOrderChangedMessage: Id=11c8b8c8-9110-4be2-9112-7d402edf8a8b DocumentNo=\'SO000073172\' DocNumeratorYear=2023 DocNumeratorMonth=2 DocNumeratorNumber=10498 DocNumeratorSeries= OrderType=2\r\nTransaction (Process ID 147) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction\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: \'Thank you Monika. It is quite urgent\'", "Comment 3: \'already some news? our planners have to plan this order and the factory needs to produce it... \'", "Comment 4: \'still under analysis\'", "Comment 5: \'has it something to do with the different recipe subversions?\'", "Comment 6: \'The reason is full queues !screenshot-1! we need to wait until all messages will be overprocessed.\'", "Comment 7: \'we have some queries where we can prioritize the orders and shipping notes over recipes and labels\'", "Comment 8: \'did you make any scripts? couse some of queues are missing !screenshot-2! \'", \'Comment 9: "No\', \'Comment 10: didn\\\'t make any script or something"\', "Comment 11: \'status shouldnt be waiting for customer since i have replied ;)\'", \'Comment 12: \\\'could you send me query that you mentioned here?"we have some queries where we can prioritize the orders and shipping notes over recipes and labels"\\\'\', \'Comment 13: "Yes\', \'Comment 14: we have got this script from Przemek:--READ FIRST BEFORE USE OF THIS SCRIPT --STEP 1: On DHVD01AP174\', \'Comment 15: open the BusinessPlatform Management Console--STEP 2: Stop Evolution.DHCService.PlatformApplication service--STEP 3: After executing the script below\', "Comment 16: start the Evolution.DHCService.PlatformApplication service againUSE Evolution_Messagingbegin trantruncate table dhcservice_tmpinsert into dhcservice_tmpSELECT * FROM DHCService D WITH (NOLOCK)where D.Body like \'%RecipeChangedMessage%\'or D.Body like \'%ProductionRecipeChangedMessage%\'or D.Body like \'%TechnologyChangedMessage%\'or D.Body like \'%LabelChangedMessage%\'delete D FROM DHCService Djoin dhcservice_tmp DS on DS.id= D.IdINSERT INTO [dbo].[DHCService]([Id],[CorrelationId],[ReplyToAddress],[Recoverable],[Expires],[Headers],[Body])select [Id],[CorrelationId],[ReplyToAddress],[Recoverable],[Expires],[Headers],[Body] from dhcservice_tmporder by charindex(\'.RecipeChangedMessage\'", "Comment 17: Headers) desc,charindex(\'.ProductionRecipeChangedMessage\'", "Comment 18: Headers) desc,charindex(\'.TechnologyChangedMessage\'", "Comment 19: Headers) desc,charindex(\'.LabelChangedMessage\'", \'Comment 20: Headers) desccommit -- Now perform STEP 3."\', \'Comment 21: "RecipeChangedMessage\', \'Comment 22: ProductionRecipeChangedMessage\', \'Comment 23: TechnologyChangedMessage and LabelChangedMessage ane exacly wchich are dissapeared from queues. Please make restart of server 172.23.1.67. As I can see queues withiout RecipeChangedMessage\', \'Comment 24: ProductionRecipeChangedMessage\', \'Comment 25: TechnologyChangedMessage and LabelChangedMessage not decreasing anymore. If restart doesn\\\'t helps we need to disquss this issue with our dev team tommorow morning"\', \'Comment 26: "Hi Monika\', \'Comment 27: I cannot restart this server as I don\\\'t have access to it... we have to pick it up tomorrow morning. Thanks for your help anyway"\', "Comment 28: \' !screenshot-3! \'", "Comment 29: \'solved. Wijnand potwierdził ze teraz im działą\'", "Comment 30: \'Queues should decrease now. We need to wait until all messages will be overprocessed.\'", "Comment 31: \'All messages are processed. Please close the ticket. \'", "Comment 32: \'Thank you\']"]\nRelated Issues:\n[\'DGS-8611\']\n\n### End'} |
425 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8607\n\n### Instruction:\nLike to award relevant sector article\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: "Hello,This field on Item Card is filled in when item is sent from Milas and is not editable right now in Intense.Is it wrong value for this item? Why it\\\'s needed to change this value?Generally it\\\'s important for items with ItemGroup = \\\'Raw Material\\\' or \\\'Finish product\\\' which are on Feed sale documents. It\\\'s possible to set this value on Feed sale element manually also in those cases.!image-2023-02-23-09-29-28-915.png!Regards"\', "Comment 4: \'Hi Damian", "Comment 5: Bert would like to add this item to some different sectors. Bert could you give us the item code you refer to and also the sector in which it should be visible?\'", "Comment 6: \'I&RR should be made available to the NAS as wel. Could you do it?\'", \'Comment 7: "I\\\'ve marked NAS in Relevant sectors\', \'Comment 8: is it correct right now?!image-2023-02-23-15-22-03-027.png!"\', "Comment 9: \'No", \'Comment 10: it should be marked in het multisector as well. I don’t think we can do it ourselves. *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* donderdag 23 februari 2023 15:24 *Aan:* Bovene\', "Comment 11: Mitch van <[email protected]> *Onderwerp:* DGS-8607 Artikel toekennen sector !image001!\'", "Comment 12: \'Confirmed that is correct right now.\']"]\nRelated Issues:\n[]\n\n### End'} |
426 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8606\n\n### Instruction:\nProszę o poprawienie na karcie środków trwałych z listy poniżej współczynnika amortyzacji podatkowej, powinno być 1/1.\r\n\r\nJednocześnie prośba o poprawienie na wszystkich wygenerowanych dokumentach amortyzacji prawidłowych wartości miesięcznych.\n\n### Response:\n["Comment 1: [\'!image![^Lista.xlsx] _(11 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Values on fixed assets has been corrected. Documents are already posted. Do you want to correct tax values on posted documents. This change shouldn\\\'t change postings?"\', "Comment 4: \'Odp od usera:Amortyzację księgujemy wg wartości bilansowej.Podatkowa jest do skorygowania. \'", "Comment 5: \'Values has been corrected on documents. PLease verify \'", "Comment 6: \'Changes are correct - task to close - thanks for help.\']"]\nRelated Issues:\n[]\n\n### End'} |
427 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8605\n\n### Instruction:\nHello,\r\n\r\nsee attached screenshot, for IO000000898 and IO000001300 we cannot create VT: We get a unexpected error: Can you please check and solve this?\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: \'{code:java} at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message)2023-02-22 15:14:23 (142612de-f30e-487f-8dd1-3a629d76faf0/Plant.VC.BusinessLogic/DHVD01AP180/28812/219) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CreateVehicleTicketFromShippingNoticeCommand](Plant.VC.BusinessLogic.Application.Interfaces.VehicleTickets.Commands.CreateVehicleTicketFromShippingNoticeCommand) methodAutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:ShippingNoticeEntity -> ShippingNoticePlant.VC.BusinessLogic.Infrastructure.Persistance.ShippingNotices.ShippingNoticeEntity -> Plant.VC.BusinessLogic.Domain.ShippingNotices.ShippingNoticeType Map configuration:ShippingNoticeEntity -> ShippingNoticePlant.VC.BusinessLogic.Infrastructure.Persistance.ShippingNotices.ShippingNoticeEntity -> Plant.VC.BusinessLogic.Domain.ShippingNotices.ShippingNoticeDestination Member:Elements ---> AutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:ShippingNoticeElementEntity -> ShippingNoticeElementPlant.VC.BusinessLogic.Infrastructure.Persistance.ShippingNotices.ShippingNoticeElementEntity -> Plant.VC.BusinessLogic.Domain.ShippingNotices.ShippingNoticeElementType Map configuration:ShippingNoticeElementEntity -> ShippingNoticeElementPlant.VC.BusinessLogic.Infrastructure.Persistance.ShippingNotices.ShippingNoticeElementEntity -> Plant.VC.BusinessLogic.Domain.ShippingNotices.ShippingNoticeElementDestination Member:PackingForm ---> System.ApplicationException: \\\\\'4\\\\\' is not a valid value in Plant.VC.BusinessLogic.Domain.ShippingNotices.Enumerations.ShippingNoticePackingForm at Kotrak.Common.SharedKernel.Enumeration.Parse[T,K](K value", \'Comment 4: String description\', \'Comment 5: Func`2 predicate) at lambda_method7355(Closure \', \'Comment 6: ShippingNoticeEntity \', \'Comment 7: ShippingNotice \', \'Comment 8: ResolutionContext ) --- End of inner exception stack trace --- at lambda_method7355(Closure \', \'Comment 9: ShippingNoticeEntity \', \'Comment 10: ShippingNotice \', \'Comment 11: ResolutionContext ) --- End of inner exception stack trace --- at lambda_method7355(Closure \', \'Comment 12: ShippingNoticeEntity \', \'Comment 13: ShippingNotice \', \'Comment 14: ResolutionContext ) at lambda_method7357(Closure \', \'Comment 15: Object \', \'Comment 16: Object \', \'Comment 17: ResolutionContext ) at Kotrak.Extensions.Mapping.CompositeMapper.Mapper.Execute(Object source\', \'Comment 18: Object destination\', \'Comment 19: ICustomInjection[] customInjections\', \'Comment 20: Type sourceType\', \'Comment 21: Type targetType) at Kotrak.Extensions.Mapping.CompositeMapper.Mapper.Map[TSource,TTarget](TSource source\', \'Comment 22: TTarget destination) at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.GetForEntity(TEntity entity) at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.Get(AggregateId id) at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.CreateVehicleTicketFromShippingNotice(AggregateId vehicleTicketId\', \'Comment 23: AggregateId shippingNoticeId\', \'Comment 24: 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)2023-02-22 15:14:23 (/Plant.VC.BusinessLogic/DHVD01AP180/28812/248) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/VehicleTicket/createVehicleTicketFromShippingNotice" responded 500 in 35.1744 ms{code}\\\'\', "Comment 25: \'!image-2023-02-22-15-30-09-525.png!\'", \'Comment 26: "{code:java}select * FROM [DHPlantVCBusinessLogicMain].[dbo].[ShippingNotices] where Description like \\\'IO000000898\\\' --select * FROM [DHPlantVCBusinessLogicMain].[dbo].[ShippingNoticeElements] where id = \\\'8B88312E-6842-4DBA-81F2-CD20A056C81A\\\' --select * from [DHPlantVCBusinessLogicMain].[dbo].[Items] where code in (\\\'0162\\\',\\\'085618\\\',\\\'088107\\\') select QuantityOnHandUnit,QuantityUnit,* from [DHPlantStockBusinessLogicMain].[dbo].[StockUnits]where ItemId in (\\\'9CFC6B85-5D4D-4CF7-A0AE-F6A35F991D81\\\',\\\'B17CA009-71F1-4BBF-9700-3AFD4F7C30EC\\\',\\\'284304DA-527D-4EBA-A0C9-BDA28D293670\\\'){code}"\', "Comment 27: \'6D805791-EE4B-41C6-A491-C334F19D74DC kgA82B6B8C-7331-4D81-8E19-80DCFDEC0999 pcs1DDADA9D-F221-4BD8-948D-4227CE6ECD4F pcs\'", "Comment 28: \'Zmiana PackingForm na 3 !image-2023-02-23-11-10-47-304.png!\'", "Comment 29: \'Hello Thomas", \'Comment 30: I have made a correction to the documents\', "Comment 31: IO000000898 and IO000001300 Causes in problems correct Description element Please Verify Regards,\'", "Comment 32: \'!image-2023-02-23-11-41-40-583.png!\'", "Comment 33: \'[[DHC 3.0] Item settlement type - related with VT. Destination site.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHC%203.0%5d%20Item%20settlement%20type%20-%20related%20with§ion-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{76E90592-C95A-48F3-888C-4CBC948085DA}&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%5BDHC%203.0%5D%20Item%20settlement%20type%20-%20related%20with%7C76E90592-C95A-48F3-888C-4CBC948085DA%2F%29])\'", "Comment 34: \'ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'} |
428 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8604\n\n### Instruction:\nHello, can you please confirm PLR 0061020123050 in DHP Nijkerk? I get an unexpected error when I try to close it\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: \'Is0061020123050 i correct number I do not see it in Nijerk", "Comment 3: could you also provide dates? !image-2023-02-22-15-22-34-536.png!\'", \'Comment 4: "it\\\'s there; if you search on active lot reports!afbeelding!"\', "Comment 5: \'id=9748873a-889c-4c71-a467-94adaa3bf9b6 plr\'", \'Comment 6: \\\'2023-02-22 15:46:33 (7fcb2146-9348-4fe0-881a-1b0182cbee63/Plant.Prod.BusinessLogic/DHVD01AP181/36416/57) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 7: "host": { "Value": "dhvd01ap181:83"\', \'Comment 8: "HasValue": true\', \'Comment 9: "Host": "dhvd01ap181"\', \'Comment 10: "Port": 83 }\', \'Comment 11: "path": "/api/productionLot/update"\', \'Comment 12: "queryString": []\', \'Comment 13: "requestBody": "\\\\\\\\{\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":1,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"63fdb7ab-555d-419c-a8e4-f01a8e1ad96b\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1448.3}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":2,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"ffe4c116-7723-46b5-a79b-a59a58943c32\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":69.176}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":3,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"871567c3-6a50-41c7-929f-5c23e683bcf7\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":12674.9}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":4,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"4b0c15ce-e19c-4223-b952-088f8c8c219d\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":776}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":5,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"f772c49d-1380-409c-bffe-71dd5df71fcc\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":22.3}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":6,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"3a6641d9-3287-4e54-9ddb-8978755f01e7\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":89.169}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":7,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"a77f17e1-76b7-4d1c-ba81-29d0f37d791d\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":82.549}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":8,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"ff864766-d77e-469a-a8e3-35956c46e9e0\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":376.4}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":9,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"157bddce-f0e1-4098-8718-479970100780\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1107.296}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":10,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"dc713a02-689e-4549-a4d0-d0eb5252168b\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":104.765}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":11,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"d4bcb839-3d48-4346-ac48-391eb118096c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":116.4}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":12,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"b0968ca7-eb58-4a22-911a-3a05d77c140e\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":68.53}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":13,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"449b8b7e-a2bd-48e6-8dd8-10347cf3a7eb\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":44.359}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":14,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"622189a3-8f08-4ad2-b9ad-907dbc641181\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":42.384}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":15,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"dc600dc2-416b-4ee2-85fc-2d9192812beb\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":320.339}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":16,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"25fe5b28-5b2e-4b20-86c4-f83293e2c37b\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":423.5}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":17,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"d162fa0a-5020-4451-ab73-5c7f9974db62\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":4541.801}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":18,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"eda1d707-8c10-475d-a7da-c2696ebf7890\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":4230.4}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":19,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"09be2508-e5cd-45b3-bce5-aa9ade358df2\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1671.7}},\\\\\\\\{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":20,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"dc600dc2-416b-4ee2-85fc-2d9192812beb\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":3805.612}}],\\\\\\\\"executions\\\\\\\\":[\\\\\\\\{\\\\\\\\"elements\\\\\\\\":[],\\\\\\\\"readyProductId\\\\\\\\":\\\\\\\\"406a617a-c70d-41d7-994b-b885a3cd6d9b\\\\\\\\",\\\\\\\\"packingRecipeId\\\\\\\\":null,\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":32015.887},\\\\\\\\"requestedQuantity\\\\\\\\":\\\\\\\\{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":32015.887},\\\\\\\\"expiryDate\\\\\\\\":\\\\\\\\"2023-04-02T20:31:07.660Z\\\\\\\\"}],\\\\\\\\"reservations\\\\\\\\":[],\\\\\\\\"productionLotId\\\\\\\\":\\\\\\\\"9748873a-889c-4c71-a467-94adaa3bf9b6\\\\\\\\",\\\\\\\\"recipeId\\\\\\\\":\\\\\\\\"019e2b35-bf9f-440f-8852-ca6202061b97\\\\\\\\",\\\\\\\\"labelId\\\\\\\\":null,\\\\\\\\"shiftNumberId\\\\\\\\":null,\\\\\\\\"statusChange\\\\\\\\":2}"}.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).\\\'\', "Comment 14: \'2023-02-22 15:46:33 (7fcb2146-9348-4fe0-881a-1b0182cbee63/Plant.Prod.BusinessLogic/DHVD01AP181/36416/57) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateProductionLotCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateProductionLotCommand) methodSystem.AggregateException: One or more errors occurred. (Response status code does not indicate success: 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 /_/Refit/RequestBuilderImplementation.cs:line 313 --- End of inner exception stack trace ---\'", \'Comment 15: \\\'brakuje lota w module stock :2023-02-22 15:46:33 (7fcb2146-9348-4fe0-881a-1b0182cbee63/Plant.Stock.BusinessLogic/DHVD01AP181/37340/307) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 16: "host": { "Value": "dhvd01ap181:92"\', \'Comment 17: "HasValue": true\', \'Comment 18: "Host": "dhvd01ap181"\', \'Comment 19: "Port": 92 }\', \'Comment 20: "path": "/api/productionLot/updateReservationsAndConfirm"\', \'Comment 21: "queryString": [],Kotrak.Common.Application.Exceptions.BusinessLogicException: Production lot with id *9748873a-889c-4c71-a467-94adaa3bf9b6 was not found*\\\'\', "Comment 22: \'!image-2023-02-22-18-16-47-852.png!\'", "Comment 23: \'Przesłałam eventy dotycząceutworzenia/aktualizacji production lota do modułu stock", \'Comment 24: resent successfully\', "Comment 25: ale nie wpada. Trza było popchać rabbitem!image-2023-02-22-18-33-38-681.png! !image-2023-02-22-18-33-38-681!\'", "Comment 26: \'Hi Thomas,Production lot is now confirmed. Please", "Comment 27: verify.!image-2023-02-22-19-20-59-840.png!Regards\'", "Comment 28: \'Thanks! ticket can be closed\']"]\nRelated Issues:\n[\'DGS-8686\']\n\n### End'} |
429 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8603\n\n### Instruction:\nHello,\r\n\r\nthe ASN element view in DHP 3 location Helmond doesn\'t show the correct data. For example, if we select all incoming ASNs for next week, in the header view I get 98 results, see screenshot.\r\n\r\nThen if I select the element view, first I get zero results.. If I select show all, I get also zero results: \r\n\r\nPlease check and fix this: Location uses the element view to make an overview of incoming intakes\n\n### Response:\n["Comment 1: [\'!afbeelding!!afbeelding-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Problem z listą dla ASN", "Comment 4: Trip jest poprawnie i tylko w tej wersji dla Sneek np działa.Przełączając się między widokami jest pusta lista dla elementów.\'", "Comment 5: \'ustalenia stand up do sprawdzenia czy to kwestia DHP 8.5\'", "Comment 6: \'Na liście elementów nie wyświetlają się ANSy/TRIPy", "Comment 7: które nie są zlinkowane z VT.Zgłoszone w DAP-13356 .!SN-no linked VT-2!\'", "Comment 8: \'Any update please?\'", "Comment 9: \'Hello", "Comment 10: we have found the problem - I will let you know how it will be solved and in what form.\'", "Comment 11: \'any update?\'", "Comment 12: \'Hello. So sorry for the lack of answers", "Comment 13: a fix has been prepared some time ago. As for the date of uploading on production for Helmond please contact directly with PM.Thank you and best regards.\'", "Comment 14: \'Hello", "Comment 15: a fix has been prepared some time ago. As for the date of uploading on production for applications please always contact directly with PM.\\\\rThank you and best regards.\\\\r\\\\rThis ticket has been closed.\']"]\nRelated Issues:\n[\'DAP-13356\']\n\n### End'} |
430 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8602\n\n### Instruction:\nSP-B/0554 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 Koen,Now you have rights for starting new process - it means that you should be able to put this document to entry status.Please try to do it and let us know that it\\\'s possible\', \'Comment 3: it should be available from document like on screen.!image-2023-02-22-08-40-31-700.png!Regards,Damian"\', "Comment 4: \'Confirmed.!image-2023-02-22-13-21-07-476.png!\']"]\nRelated Issues:\n[]\n\n### End'} |
431 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8601\n\n### Instruction:\nHi, \r\nin DHC I need to link BMX code 1298 and code from our ERP system Integra 19807. I don´t see 19807 in the list.\r\nPls solve it asap. I need new recipes with this new RM.\r\nthx\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-2023-02-21-17-27-50-357.png!!image-2023-02-21-17-28-40-418.png!\'", "Comment 4: \'Dear Lucie,I can see that item 19807 is linked to 01236. Please", "Comment 5: verify.Regards!image-2023-02-21-17-31-19-140.png!\'", "Comment 6: \'pls change it. I need to make new link.thx!\'", "Comment 7: \'Just to confirm", "Comment 8: should I unlink 19807 from bmx 01236?\'", "Comment 9: \'yes pls. We don´t use 01236 anymore.\'", "Comment 10: \'Please", \'Comment 11: check. Now you should link items.Please\', "Comment 12: verify!image-2023-02-21-17-46-07-970.png!\'", "Comment 13: \'I could select 19807 in teh list but it looks it still is not linked. !image-1!\'", "Comment 14: \'Please", "Comment 15: check!image-2023-02-21-17-59-24-074.png!\'", "Comment 16: \'it is okay nowthx\']"]\nRelated Issues:\n[]\n\n### End'} |
432 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8600\n\n### Instruction:\nHello,\r\n\r\nuser reported that the printout option is not available on VT preview screen: I checked and added different roles but it\'s not there. Can you please solve this?\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: \'U mnie działa!image-2023-02-21-13-43-56-657.png!\'", "Comment 4: \'Dear Thomas,Please", "Comment 5: check now with user and let us know.Regards\'", "Comment 6: \'Edit user:!image-2023-02-21-14-03-38-106.png!Wybrać set business unit", "Comment 7: wybrać (w tym wypadku Helmond) i zapisać na business unicie i na powyższym ekranie\'", \'Comment 8: "Thanks\', \'Comment 9: I\\\'ll let him check"\', "Comment 10: \'When you ave feedback from user", \'Comment 11: please\', "Comment 12: let me know if e can close this task.Regards\'", "Comment 13: \'Hi Thomas,Can we close this task?Regards\'", "Comment 14: \'Yes please\'", "Comment 15: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
433 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8599\n\n### Instruction:\nWhen adjust import duty of Item code: 00828 to 6.5% in CDN, unfortunately, failed. \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: \'Is it possible to complete the required fields from the list of attributes. !screenshot-1! If it is not on the list - please add for required ones and check if there is still a problem. !screenshot-2! \'", "Comment 4: \'Ticket can be closed.!image-1!\']"]\nRelated Issues:\n[]\n\n### End'} |
434 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8598\n\n### Instruction:\n Pallets from another lane are suddenly in a load order where they do not belong to\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: \'In the scan there are still 4 pallets that should still be scanned in the loading order. in the application there are only 3 left and this is also correct.The last pallet in the scanner (187190811000313638) does not belong in this Trip at all.\'", "Comment 4: \'!image-2!\'", "Comment 5: \'Hereby an other recently example.!image-3!\'", "Comment 6: \'{code:java}SELECT * FROM [dbo].[WMSInternalDocumentOrderHeaders] HJoin [dbo].[WMSInternalDocumentOrderElements]E on E.WiE_HeaderId = H.WhI_Idwhere H.WhI_Id = 175795 or WiE_Id between 477547 and 477551{code}!image-2023-03-27-10-11-24-138!\'", "Comment 7: \'Wyjaśnione z Thomasem Dankersem. Po analizie wygląda na błędy kolejności procesowania wydań przez użytkowników na magazynie.\'", "Comment 8: \'Hi", \'Comment 9: according to Marcin Block information\', "Comment 10: this issue was explained with Thomas Dankers. After the analysis it looks like errors in the order of processing releases by users in the warehouse.This issue has been closed.\'", "Comment 11: \'This issue is closed by Kotrak.The problem did occur again.The user reports:he scan still contains 4 pallets that should still be scanned in the loading order. There are only 3 left in the application and this is also correct. The last pallet in the scanner (187190811000313638) does not belong in this Trip at all.!image-4!!image-5!\'", "Comment 12: \'Last remark was an old remark send by the user\'", \'Comment 13: "Hi Bert\', \'Comment 14: your last comment has the same examples that were originally in the issue - wasn\\\'t this already clarified with Marcin?Can we close this task?"]\']\nRelated Issues:\n[\'DGS-8560\']\n\n### End'} |
435 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8597\n\n### Instruction:\nSales Order missing from DHC, and therefore not sync\'ing to DHP. Needed for production.\r\n\n\n### Response:\n["Comment 1: [\'https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8594\'", "Comment 2: \'Widać w logach eprintegratora że adres poszedł wcześniej !screenshot-1! Historia zmian: !screenshot-2! z DHC: !screenshot-3! dla adresu !screenshot-4! \'", "Comment 3: \'dodaliśmy do konfiguracji ERP Integratora wpis który załącza dosyłanie brakujących informacji.\'", "Comment 4: \'We have changed the ERP Integrator configuration that enables the sending of missing information.The problem should no longer occur.\'", "Comment 5: \'Does this resync all connected objects (Customer/Address/Recipe/Article)?\'", "Comment 6: \'Sending of missing information related to ERP XL", \'Comment 7: so items\', "Comment 8: customers and addresses.The recipes are from DHC.\'", "Comment 9: \'Ok", "Comment 10: thank you. The ticket can be closed.\']"]\nRelated Issues:\n[\'DGS-8594\']\n\n### End'} |
436 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8596\n\n### Instruction:\nBack to entry\r\nPI-RLB/2023/0999\r\nSI-RLB/2023/1047\r\nSRBe/2128\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Could you give Koen the rights to set these types of documents back to entry himself? Just like he can reopen rounds. Please move it to PROD.\'", "Comment 3: \'[[email protected]],all documents from list have been reply to your Inbox.[[email protected]],yes", \'Comment 4: we can add rights for these types of documents for all users from role "Start new process for document":!image-2023-02-21-11-11-22-168.png!Best regards,Grzegorz\\\'\', "Comment 5: \'{color:black}Hello{color} {color:black}{color} {color:black}All documents?{color} !image001!{color:black}{color} {color:black}I don’t see them in the inbox{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:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.‑LOCATIEHELMOND*{color}* | | | |{color:#000001} Gerstdijk12 \\\\u200b5704RGHelmond{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}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Grzegorz Materla (Jira) <[email protected]> *Verzonden:* dinsdag 21 februari 2023 11:13 *Aan:* Huibers", "Comment 6: Koen <[email protected]> *Onderwerp:* DGS-8596 Back to entry !image007!\'", "Comment 7: \'{color:black}It’s ok", \'Comment 8: I was in the wrong inbox{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:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.‑LOCATIEHELMOND*{color}* | | | |{color:#000001} Gerstdijk12 \\\\u200b5704RGHelmond{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}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Huibers\', \'Comment 9: Koen *Verzonden:* dinsdag 21 februari 2023 11:19 *Aan:* [email protected] *Onderwerp:* RE: DGS-8596 Back to entry {color:black}Hello{color} {color:black}{color} {color:black}All documents?{color} !image008!{color:black}{color} {color:black}I don’t see them in the inbox{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:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.‑LOCATIEHELMOND*{color}* | | | |{color:#000001} Gerstdijk12 \\\\u200b5704RGHelmond{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}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Grzegorz Materla (Jira) <[[email protected]|mailto:[email protected]]> *Verzonden:* dinsdag 21 februari 2023 11:13 *Aan:* Huibers\', "Comment 10: Koen <[[email protected]|mailto:[email protected]]> *Onderwerp:* DGS-8596 Back to entry !image001!!image007!\'", \'Comment 11: "[[email protected]],thank you for your reply.[[email protected]],I\\\'ve added posibility for all invoices for all sectors in test and prod environment. Only users with suitable rights can do it.Best regards\', \'Comment 12: Grzegorz"]\']\nRelated Issues:\n[]\n\n### End'} |
437 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8595\n\n### Instruction:\nsuddenly too many bags disconnected during replenishment and a negative line\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: \'next order from the same pallet gives the same problem!!image-2!\']"]\nRelated Issues:\n[\'DGS-8560\']\n\n### End'} |
438 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8594\n\n### Instruction:\nSales Order missing from DHC, and therefore not sync\'ing to DHP. Needed for production.\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: \'order is now in DHC!screenshot-1! the order was missing due to the missing address for the customer", "Comment 4: the data has been sent.\'", "Comment 5: \'{code:java} update k\\\\t set kna_nazwa2=KnA_Nazwa2 FROM [CDNXL_DHFU].[CDN].[KntAdresy] k where KnA_GIDNumer=32433\\\\t update z\\\\t set zan_stan=ZaN_Stan FROM [CDNXL_DHFU].[CDN].[ZamNag] z where ZaN_GIDNumer=797908{code}{code:java}2023-02-21 11:26:43,431 [47] DEBUG Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - Order OrderId: bfc4bdf5-52fb-4a5c-962c-130ce462f3af BusinessPartnerAddress: feca58ef-77d1-4e9d-be2b-2de15b5cb120S is not synchronized2023-02-21 11:26:43,431 [47] INFO Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - ResynchronizeDataExtension is off - resynchronization skipped2023-02-21 11:26:43,431 [47] DEBUG Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - Order OrderId: bfc4bdf5-52fb-4a5c-962c-130ce462f3af BusinessPartnerAddress: feca58ef-77d1-4e9d-be2b-2de15b5cb120 is not synchronized2023-02-21 11:26:43,431 [47] INFO Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - ResynchronizeDataExtension is off - resynchronization skipped{code}\'", "Comment 6: \'Thank you.Do we have an existing RCA open for this? \'", "Comment 7: \'Ok. I see one has been opened. You may close this ticket. Thanks.https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8597 \'", \'Comment 8: "No\', \'Comment 9: we don\\\'t have it open. I have created RCA DGS-8597."]\']\nRelated Issues:\n[\'DGS-8597\']\n\n### End'} |
439 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8593\n\n### Instruction:\nitem has just been replenished and a new replenishment immediately comes into the scan while this is not possible\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'What is the reason off immediately a new replenishment?\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \' !WMO 2508! !image-2023-03-07-13-15-53-203!\'", "Comment 5: \'Od 22.12.2022 nie działała synchronizacja eventowa (Exchange - PCS", "Comment 6: Exchange - DHP). Powodem braku działania był brak wczytania konfiguracji. Po wykonaniu procedury reloadconfiguration synchronizacja eventowa zaczęła działać.\'", "Comment 7: \'Hello,after the developers analysis the reload configuration procedure was required to be processed.Synchronization for events has been verified.Please verify and send a feedback.\'", "Comment 8: \'{code:java}System.Data.SqlClient.SqlException (0x80131904): Transaction context in use by another session. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception", \'Comment 9: Boolean breakConnection\', \'Comment 10: Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 11: Boolean callerHasConnectionLock\', \'Comment 12: Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 13: SqlCommand cmdHandler\', \'Comment 14: SqlDataReader dataStream\', \'Comment 15: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 16: TdsParserStateObject stateObj\', \'Comment 17: Boolean& dataReady) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior\', \'Comment 18: SqlCommand cmdHandler\', \'Comment 19: SqlDataReader dataStream\', \'Comment 20: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 21: TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.TdsExecuteTransactionManagerRequest(Byte[] buffer\', \'Comment 22: TransactionManagerRequestType request\', \'Comment 23: String transactionName\', \'Comment 24: TransactionManagerIsolationLevel isoLevel\', \'Comment 25: Int32 timeout\', \'Comment 26: SqlInternalTransaction transaction\', \'Comment 27: TdsParserStateObject stateObj\', \'Comment 28: Boolean isDelegateControlRequest) at System.Data.SqlClient.SqlInternalConnectionTds.PropagateTransactionCookie(Byte[] cookie) at System.Data.SqlClient.SqlInternalConnection.EnlistNonNull(Transaction tx) at System.Data.SqlClient.SqlInternalConnection.Enlist(Transaction tx) at System.Data.ProviderBase.DbConnectionInternal.ActivateConnection(Transaction transaction) at System.Data.ProviderBase.DbConnectionPool.PrepareConnection(DbConnection owningObject\', \'Comment 29: DbConnectionInternal obj\', \'Comment 30: Transaction transaction) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 31: UInt32 waitForMultipleObjectsTimeout\', \'Comment 32: Boolean allowCreate\', \'Comment 33: Boolean onlyOneCheckConnection\', \'Comment 34: DbConnectionOptions userOptions\', \'Comment 35: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 36: TaskCompletionSource`1 retry\', \'Comment 37: DbConnectionOptions userOptions\', \'Comment 38: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 39: TaskCompletionSource`1 retry\', \'Comment 40: DbConnectionOptions userOptions\', \'Comment 41: DbConnectionInternal oldConnection\', \'Comment 42: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 43: DbConnectionFactory connectionFactory\', \'Comment 44: TaskCompletionSource`1 retry\', \'Comment 45: 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() at Exchange.Repository.SQL.AppCenter.OpenConnection() at Exchange.Repository.SQL.Logger.Log(ExchangeLogType type\', \'Comment 46: String message\', \'Comment 47: LogCategory category\', \'Comment 48: Nullable`1 objectId) at Exchange.Repository.SQL.Logger.Log(ExchangeLogType type\', \'Comment 49: String message\', "Comment 50: LogCategory category) at Exchange.EventBasedSynchronization.MainService.LoadConfiguration() at Exchange.EventBasedSynchronization.MainService.LoadConfigurationIfEmpty() at Exchange.EventBasedSynchronization.MainService.SynchronizeReplenishmentRequest()ClientConnectionId:4597b135-70f4-4fb8-b3be-0a92f7b05b6aError Number:3910,State:2,Class:16{code}!Exchange event base synchro stopped 2022-12-22!\'", "Comment 51: \'This issue has been resolved. Ticket has been closed.\']"]\nRelated Issues:\n[\'DGS-8560\']\n\n### End'} |
440 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8592\n\n### Instruction:\nItem and recipe for 515006 are not arriving in DHP Sneek, even after various synch and resend attempts.\r\n\r\nItem needs to be produced tonight for first shipment tomorrow, so it\'s urgent.\r\n\r\nPlease fix.\r\n\r\nRegards,\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: \'Item and recipe should be in DHP now. Please verify.\'", "Comment 3: \'Verified!Both items and the recipe are in DHP Sneek. I informed the production manager.\'", "Comment 4: \'Ok. So I close this issue. Regards\'", "Comment 5: \'Thanks Monika.\']"]\nRelated Issues:\n[]\n\n### End'} |
441 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8591\n\n### Instruction:\nHi,\r\nMay you help check data: i found some SO sending 2 time in log file?\r\nis it still ok or we must fix it?\n\n### Response:\n["Comment 1: [\'!image![^MNS Feed - Check duplicate SO (1).xlsx] _(3,66 MB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'query that from DHC\'", "Comment 4: \'Dear Hardy,I have checked your query. You have made it by order elements", \'Comment 5: that is why you can see duplicated sent date.But if you have a look for marked order numebr you can see that it refers to 4 different elements:!image-2023-02-20-14-52-03-467.png|width=910,height=533!After a little modification\', "Comment 6: you can see there is only one order.!image-2023-02-20-14-54-55-651.png|width=914,height=533!Regards\'", "Comment 7: \'In DHP we can see one document:!image-2023-02-20-14-58-02-779.png!\'", "Comment 8: \'!image-2023-02-20-15-21-33-583.png!\'", \'Comment 9: "{code:java}select A.ID\', \'Comment 10: B.DocumentNumber\', \'Comment 11: B.IssueDate\', \'Comment 12: B.Status\', \'Comment 13: A.CommitDate as datapotw\', \'Comment 14: A.EntityIdfrom OrderExportInfoes ALEft JOIn Orders B On A.EntityId=B.Id--LEFT JOIN OrderElements C ON B.Id=C.OrderId--left join items D On C.ItemId=D.id--left join BusinessPartners E ON B.MainBusinessPartnerId =E.idwhere a.id in(\\\'C8D7E034-7981-4F5D-9C3A-0064FF705D76\\\',\\\'4A56B226-0CCB-402F-A2CD-D491F1CBC820\\\',\\\'C7075B41-A54F-4EE0-BF4D-31F1EAF7BB71\\\',\\\'EFA72E37-8CA0-4A3A-A64E-34EA754C7E53\\\',\\\'D3209B82-D8E6-4066-ADF0-8082081450FE\\\',\\\'E365E3E2-E89D-4381-B2B9-CF39848629A3\\\',\\\'EDDCB12E-8D0B-436A-8605-59C015F63771\\\',\\\'5C9E45F8-2E81-4D95-9AD3-E43ECC024250\\\',\\\'BA370AFF-3789-4C7C-9800-AABE5F36BD22\\\',\\\'515FECF7-394F-4413-81EC-3961301E4994\\\',\\\'C606FE7C-D2D1-49C0-89AF-5517937E5E44\\\',\\\'36BBCE71-29D1-4E3A-9518-8FF8369A6A3E\\\',\\\'9C0AB804-A606-43F9-9620-EBD041E58822\\\',\\\'AD5DD91A-9B47-41B9-8674-719DC171CDC5\\\',\\\'194C8278-90D3-4C33-9E8C-47DDCB051CD5\\\',\\\'239056A1-8A54-4BC7-BA83-EA9A7FA1ADB3\\\',\\\'9EFB4D5C-7633-4219-B5D1-E8AA41BF7DD3\\\',\\\'8A4D0147-73CF-4E17-9AFC-37B1A316BA3A\\\',\\\'78645BD9-E92E-4418-97CF-2ED85C712E91\\\',\\\'ED92A313-3CAE-4173-A4B7-2964E1C9965B\\\',\\\'C0305799-A6CC-4432-ABD3-A7879ACD1A7C\\\',\\\'714D9DD8-B722-42D5-99E4-2AF72707B124\\\',\\\'1233C2E3-0E23-4A75-8F4E-4607ABAD8C3A\\\',\\\'F0BBCF23-E057-4216-ABBA-68FADCA43229\\\',\\\'EB362139-8B64-4A9D-899D-4AD42E63D9FD\\\',\\\'145D54F0-C0CB-4144-8205-D0E0A4763EEF\\\',\\\'25582D46-7D82-4738-A622-5F2AA486A2F0\\\',\\\'89517F67-DDD7-4DD7-B9D5-D9DDAF3447E3\\\',\\\'3998B89A-51F5-4E03-A021-E11153960256\\\',\\\'7092E974-585F-4313-8696-25247B91EE31\\\',\\\'2FCE11D4-BF17-48BC-BBB4-35B63F525A52\\\',\\\'72939D64-B5D3-4BA0-99F5-E3154603D3BB\\\',\\\'FB0AAAD8-9970-4748-A2D3-9BB4F0608E34\\\',\\\'56EA6093-3BD7-4FD5-93F3-9200AD303AC4\\\',\\\'2F54C8B7-8F77-44B2-8214-C80B938278C2\\\',\\\'95EACB3A-8E84-46F3-9D23-43818F2672B8\\\',\\\'1065D408-ED41-421E-B5E3-AF11B92CBA3A\\\',\\\'087AFC78-AC54-4661-8249-54B27EF2F640\\\',\\\'968BE807-58E0-4198-8036-0F9251C60EB5\\\',\\\'ABB6993E-6AD3-456E-B21F-6A8D904CAFE9\\\',\\\'96989CEA-DA6D-40A9-ACF9-FF4402C48792\\\',\\\'E62DF455-F22A-43DB-9A69-E769D166C8FA\\\',\\\'1E67699C-03E3-4328-8EF7-BEADC809FF34\\\',\\\'3638A40D-42DB-4367-9A2C-72677C233AAD\\\',\\\'97E20ACF-4C51-44C3-92F2-63CAE19A9B9D\\\',\\\'94644FE6-8E2C-405D-B340-EA83FD0B73AE\\\',\\\'178F59A0-0700-49D9-9232-3A2935B7DFB0\\\',\\\'64DE7FFA-EC9B-402E-9A27-41F0617498E8\\\',\\\'8128EF5C-C5C3-49DA-9829-A28D4E5F38EE\\\',\\\'4287D615-03B5-44E0-96ED-B6F8428579E0\\\',\\\'57424739-095F-42FD-A18A-F75A44EC9BCD\\\',\\\'A2416ED6-84F6-49C0-B8CB-6F51C98A3E79\\\',\\\'7CFD8AA7-B76B-4312-9A06-989B7BAD1A8E\\\',\\\'BAE3005A-69DF-4F98-881E-ADB394EFF321\\\',\\\'1EDD8647-DECB-442C-AA85-9DD867CF8EFC\\\',\\\'775B06D1-719E-4AED-98DC-561EA5F2C86C\\\',\\\'2D408C91-A1C3-41B9-A752-CD8B9D00A56C\\\',\\\'0B3509C3-4A82-416C-8C6F-3AF36149E023\\\',\\\'04161A2F-1C47-4FC4-A27A-C2ED311035EF\\\',\\\'5111B600-5C56-43E2-AF92-05210D26F358\\\',\\\'62C979D7-8FA9-44A8-85EB-FB0CBEC84292\\\',\\\'743B4485-CD3B-45B2-9839-D55D63F4C9D4\\\',\\\'A40C02AF-4215-448C-ACA4-51F3706D2245\\\',\\\'54DF8DB4-305D-421F-953B-2193A4B9D79C\\\',\\\'F9F635E0-42BA-48E3-B300-E9429361A4A8\\\',\\\'697A611B-C8D3-4716-8AF7-EBCD5B2CE667\\\',\\\'2E33E509-4278-4235-929B-96EC82E76403\\\',\\\'147F959A-5438-4896-8D82-06FEB4E97E53\\\',\\\'29B69124-1388-4BE5-A534-6DDC509F6BB9\\\',\\\'8B5F9739-C7AF-4988-83BB-1197AEF3E285\\\',\\\'5740ACCD-2FE4-4C15-99B8-73C0F789CFB5\\\',\\\'1DECAB2A-CF6A-45AB-829D-1D94920FCBFE\\\',\\\'4029DA86-B40C-46CD-AF01-E78B1878F5A4\\\',\\\'93390ADD-C50B-4BD2-81C6-00E3B3AB5825\\\',\\\'4C9EB1E3-9525-48DB-A610-637ED22B36DC\\\',\\\'D7955DFE-D00B-4582-AAD7-9447E09C9D74\\\',\\\'39964473-0549-4F50-8508-F6E896D1151E\\\',\\\'8F988E7C-7EC1-4C63-81E8-2EC07C514D94\\\',\\\'9C149A4B-5D15-4300-8944-C0DFAB716FB8\\\',\\\'B8B96362-CF2A-4D97-B9D0-CBA1360E96C8\\\',\\\'1A21E196-8A8F-4F1B-837E-C6C63DC3965D\\\',\\\'13A2A582-3741-4696-8960-5E26831A0892\\\',\\\'AB6117BE-1326-40F0-93EC-876717662299\\\',\\\'6BE6E8FE-4C5F-4B5C-9239-8DD83A546EF1\\\',\\\'7CD3A0E1-8688-4B22-A47D-2C6B7FE35EF6\\\',\\\'07604816-7DC0-4A45-84C0-5F3A337A6A12\\\',\\\'E8D49B45-3CA8-4A61-A82A-D98B1F5E4FF4\\\',\\\'58377FBE-56F5-4414-89B5-91F95E205FC1\\\',\\\'6FB82146-8107-4ED1-B403-0328A347F328\\\',\\\'87086D51-5314-44A8-8EF8-C8E6917330F0\\\',\\\'E63B86B2-831A-4CD8-8779-8BB07B5B5BBF\\\',\\\'95239AF8-D9AA-4216-A950-7088FE69AF21\\\',\\\'16EBA4B1-B5FC-4FDD-B0BB-162B73881A27\\\',\\\'914154C0-41C9-4962-BD69-9A64C42665E8\\\'){code}"\', \'Comment 15: "{code:java}select A.ID\', \'Comment 16: B.DocumentNumber\', \'Comment 17: B.IssueDate\', \'Comment 18: B.Status\', \'Comment 19: C.ItemCode\', \'Comment 20: C.Quantity\', \'Comment 21: E.Code\', \'Comment 22: A.CommitDate as datapotw\', \'Comment 23: A.EntityIdfrom OrderExportInfoes ALEft JOIn Orders B On A.EntityId=B.IdLEFT JOIN OrderElements C ON B.Id=C.OrderIdleft join items D On C.ItemId=D.idleft join BusinessPartners E ON B.MainBusinessPartnerId =E.idwhere a.id in(\\\'C8D7E034-7981-4F5D-9C3A-0064FF705D76\\\',\\\'4A56B226-0CCB-402F-A2CD-D491F1CBC820\\\',\\\'C7075B41-A54F-4EE0-BF4D-31F1EAF7BB71\\\',\\\'EFA72E37-8CA0-4A3A-A64E-34EA754C7E53\\\',\\\'D3209B82-D8E6-4066-ADF0-8082081450FE\\\',\\\'E365E3E2-E89D-4381-B2B9-CF39848629A3\\\',\\\'EDDCB12E-8D0B-436A-8605-59C015F63771\\\',\\\'5C9E45F8-2E81-4D95-9AD3-E43ECC024250\\\',\\\'BA370AFF-3789-4C7C-9800-AABE5F36BD22\\\',\\\'515FECF7-394F-4413-81EC-3961301E4994\\\',\\\'C606FE7C-D2D1-49C0-89AF-5517937E5E44\\\',\\\'36BBCE71-29D1-4E3A-9518-8FF8369A6A3E\\\',\\\'9C0AB804-A606-43F9-9620-EBD041E58822\\\',\\\'AD5DD91A-9B47-41B9-8674-719DC171CDC5\\\',\\\'194C8278-90D3-4C33-9E8C-47DDCB051CD5\\\',\\\'239056A1-8A54-4BC7-BA83-EA9A7FA1ADB3\\\',\\\'9EFB4D5C-7633-4219-B5D1-E8AA41BF7DD3\\\',\\\'8A4D0147-73CF-4E17-9AFC-37B1A316BA3A\\\',\\\'78645BD9-E92E-4418-97CF-2ED85C712E91\\\',\\\'ED92A313-3CAE-4173-A4B7-2964E1C9965B\\\',\\\'C0305799-A6CC-4432-ABD3-A7879ACD1A7C\\\',\\\'714D9DD8-B722-42D5-99E4-2AF72707B124\\\',\\\'1233C2E3-0E23-4A75-8F4E-4607ABAD8C3A\\\',\\\'F0BBCF23-E057-4216-ABBA-68FADCA43229\\\',\\\'EB362139-8B64-4A9D-899D-4AD42E63D9FD\\\',\\\'145D54F0-C0CB-4144-8205-D0E0A4763EEF\\\',\\\'25582D46-7D82-4738-A622-5F2AA486A2F0\\\',\\\'89517F67-DDD7-4DD7-B9D5-D9DDAF3447E3\\\',\\\'3998B89A-51F5-4E03-A021-E11153960256\\\',\\\'7092E974-585F-4313-8696-25247B91EE31\\\',\\\'2FCE11D4-BF17-48BC-BBB4-35B63F525A52\\\',\\\'72939D64-B5D3-4BA0-99F5-E3154603D3BB\\\',\\\'FB0AAAD8-9970-4748-A2D3-9BB4F0608E34\\\',\\\'56EA6093-3BD7-4FD5-93F3-9200AD303AC4\\\',\\\'2F54C8B7-8F77-44B2-8214-C80B938278C2\\\',\\\'95EACB3A-8E84-46F3-9D23-43818F2672B8\\\',\\\'1065D408-ED41-421E-B5E3-AF11B92CBA3A\\\',\\\'087AFC78-AC54-4661-8249-54B27EF2F640\\\',\\\'968BE807-58E0-4198-8036-0F9251C60EB5\\\',\\\'ABB6993E-6AD3-456E-B21F-6A8D904CAFE9\\\',\\\'96989CEA-DA6D-40A9-ACF9-FF4402C48792\\\',\\\'E62DF455-F22A-43DB-9A69-E769D166C8FA\\\',\\\'1E67699C-03E3-4328-8EF7-BEADC809FF34\\\',\\\'3638A40D-42DB-4367-9A2C-72677C233AAD\\\',\\\'97E20ACF-4C51-44C3-92F2-63CAE19A9B9D\\\',\\\'94644FE6-8E2C-405D-B340-EA83FD0B73AE\\\',\\\'178F59A0-0700-49D9-9232-3A2935B7DFB0\\\',\\\'64DE7FFA-EC9B-402E-9A27-41F0617498E8\\\',\\\'8128EF5C-C5C3-49DA-9829-A28D4E5F38EE\\\',\\\'4287D615-03B5-44E0-96ED-B6F8428579E0\\\',\\\'57424739-095F-42FD-A18A-F75A44EC9BCD\\\',\\\'A2416ED6-84F6-49C0-B8CB-6F51C98A3E79\\\',\\\'7CFD8AA7-B76B-4312-9A06-989B7BAD1A8E\\\',\\\'BAE3005A-69DF-4F98-881E-ADB394EFF321\\\',\\\'1EDD8647-DECB-442C-AA85-9DD867CF8EFC\\\',\\\'775B06D1-719E-4AED-98DC-561EA5F2C86C\\\',\\\'2D408C91-A1C3-41B9-A752-CD8B9D00A56C\\\',\\\'0B3509C3-4A82-416C-8C6F-3AF36149E023\\\',\\\'04161A2F-1C47-4FC4-A27A-C2ED311035EF\\\',\\\'5111B600-5C56-43E2-AF92-05210D26F358\\\',\\\'62C979D7-8FA9-44A8-85EB-FB0CBEC84292\\\',\\\'743B4485-CD3B-45B2-9839-D55D63F4C9D4\\\',\\\'A40C02AF-4215-448C-ACA4-51F3706D2245\\\',\\\'54DF8DB4-305D-421F-953B-2193A4B9D79C\\\',\\\'F9F635E0-42BA-48E3-B300-E9429361A4A8\\\',\\\'697A611B-C8D3-4716-8AF7-EBCD5B2CE667\\\',\\\'2E33E509-4278-4235-929B-96EC82E76403\\\',\\\'147F959A-5438-4896-8D82-06FEB4E97E53\\\',\\\'29B69124-1388-4BE5-A534-6DDC509F6BB9\\\',\\\'8B5F9739-C7AF-4988-83BB-1197AEF3E285\\\',\\\'5740ACCD-2FE4-4C15-99B8-73C0F789CFB5\\\',\\\'1DECAB2A-CF6A-45AB-829D-1D94920FCBFE\\\',\\\'4029DA86-B40C-46CD-AF01-E78B1878F5A4\\\',\\\'93390ADD-C50B-4BD2-81C6-00E3B3AB5825\\\',\\\'4C9EB1E3-9525-48DB-A610-637ED22B36DC\\\',\\\'D7955DFE-D00B-4582-AAD7-9447E09C9D74\\\',\\\'39964473-0549-4F50-8508-F6E896D1151E\\\',\\\'8F988E7C-7EC1-4C63-81E8-2EC07C514D94\\\',\\\'9C149A4B-5D15-4300-8944-C0DFAB716FB8\\\',\\\'B8B96362-CF2A-4D97-B9D0-CBA1360E96C8\\\',\\\'1A21E196-8A8F-4F1B-837E-C6C63DC3965D\\\',\\\'13A2A582-3741-4696-8960-5E26831A0892\\\',\\\'AB6117BE-1326-40F0-93EC-876717662299\\\',\\\'6BE6E8FE-4C5F-4B5C-9239-8DD83A546EF1\\\',\\\'7CD3A0E1-8688-4B22-A47D-2C6B7FE35EF6\\\',\\\'07604816-7DC0-4A45-84C0-5F3A337A6A12\\\',\\\'E8D49B45-3CA8-4A61-A82A-D98B1F5E4FF4\\\',\\\'58377FBE-56F5-4414-89B5-91F95E205FC1\\\',\\\'6FB82146-8107-4ED1-B403-0328A347F328\\\',\\\'87086D51-5314-44A8-8EF8-C8E6917330F0\\\',\\\'E63B86B2-831A-4CD8-8779-8BB07B5B5BBF\\\',\\\'95239AF8-D9AA-4216-A950-7088FE69AF21\\\',\\\'16EBA4B1-B5FC-4FDD-B0BB-162B73881A27\\\',\\\'914154C0-41C9-4962-BD69-9A64C42665E8\\\'){code}"\', "Comment 24: \'Hi,You can see may query. 2 row for 1 order!image-1!!image-2!\'", "Comment 25: \'!image-2023-02-21-13-07-27-567.png!\'", "Comment 26: \'DHC:!image-2023-02-21-13-16-30-944.png!Service:!image-2023-02-21-13-17-04-415.png!\'", "Comment 27: \'Hi Hardy,We have checked and data from the Orders did not duplicate in DHC or DHP so in our opinion we should treat it as incidental case. Nothing critical.Regards\'", "Comment 28: \'thank you. you can close the ticket\'", "Comment 29: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
442 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8590\n\n### Instruction:\nSystem should displays value \'Trade\' on invoices when there is value \'1\' in field Full number on SI and PI.\r\n\r\nIt can happen when invoices are generated from SR\'s (SR -> SI -> PI)\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n["Comment 1: [\'!image009!\'", \'Comment 2: "[[email protected]]do ogarnięcia\', \'Comment 3: aby to zrobić tak\', "Comment 4: że wyświetlamy w polu \'Full number\' (numer rundy) \'Trade\' jeżeli * jest to dokument SI", "Comment 5: który jest wygenerowany ze Slaughtery Report - pole \'Leading doc\'!image-2023-02-22-14-40-15-576.png! * jest to dokument PI", \'Comment 6: który jest wygenerowany z PI\', \'Comment 7: a PI jest wygenerowane z SR. Ewentualnie można to oprzeć o powiązanie na PI w poli \\\'Go to Slaughtery Report\\\' !image-2023-02-22-14-39-52-979.png!Na SR wtedy w polu \\\'Full number\\\' będzie wartość \\\'Trade\\\'.!image-2023-02-22-14-44-03-798.png!Na SI i na PI w innych przypadkach (poza takimi SI i PI pochodzące z SR jak w przykładzie wyżej) nie powinna być możliwa do wybrania z lookupa wartość \\\'Trade\\\'."\', \'Comment 8: \\\'[[email protected]],the modification has been added in field "Full number" for SI and PI MAS NL (include credit invoices) in test environment.You can feel free to test it.Best regards,Grzegorz\\\'\', "Comment 9: \'Confirmed", "Comment 10: can be closed.\'", "Comment 11: \'[[email protected]],the modification has been moved in prod environment.You can feel free to test it.Best regards,Grzegorz\']"]\nRelated Issues:\n[]\n\n### End'} |
443 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8589\n\n### Instruction:\nwe still regularly see that a warehouse employee completes a replenishment order and a new order immediately comes in for the same number of big bags of the same item. Partly known that this is because an order is completed in DHP, when the stock is not yet known in the factory and the factory in the meantime makes a new request that this goes wrong.\r\n\r\nhowever, there is one thing we do not know for sure and we would like to know. namely: what happens if the assignment in DHP is “in progress” and a new request arrives in the meantime?\r\n\r\nwill this be ignored or will a new RM assignment be created?\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: \'Out internal number : (SDNL-31532)\'", "Comment 4: \'Hi,We need to analize briefly your question.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.Regards\'", "Comment 5: \'After the analysis on Friday", \'Comment 6: it turned out that the event-based integration had not worked since December 22\', \'Comment 7: 2022. Only the service based on timed synchronization calls every 5 minutes worked for over four months. Therefore\', \'Comment 8: this caused problems in transferring replenishment information\', \'Comment 9: pallet labels from production\', \'Comment 10: and many other delayed processes.Currently\', \'Comment 11: the event base synchronization is up and running. ---- Answering the question of Bert:"what happens if the assignment in DHP is “in progress” and a new request arrives in the meantime?"This WMO\', \'Comment 12: which is in progress\', \'Comment 13: will proceed by the operator as it is\', "Comment 14: and a new order will be generated for the excess quantity.\'", "Comment 15: \'[[email protected]] Jak dla mnie task można procesować do zamknięcia.\'", "Comment 16: \'What exactly were the actions performed. Were any services not started or were services stopped and restarted? if yes", "Comment 17: which services were these?\'", "Comment 18: \'Kolega ma pytanie :P\']"]\nRelated Issues:\n[]\n\n### End'} |
444 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8588\n\n### Instruction:\nPlease unlink attached recipes in DHC. 4 for Veghel and 1 for Nijkerk\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: \'We can remove them from DHC and DHP databases.Please confirm.\'", "Comment 4: \'Yes please!\'", "Comment 5: \'VE307499-1this technology has a subversion,!image-2023-02-20-14-22-58-051.png! should it be removed too?\'", "Comment 6: \'Yes", "Comment 7: please remove both versions. Thanks for asking!\'", \'Comment 8: "There are already so many PLRs generated for the technologiesnumber of PLR\\\'s | technology code76 NY303436 334 VE303436 may i know what is the reason for the change? because we will have to use a different solution"\', "Comment 9: \'{color:black}Vivian", \'Comment 10: can you please answer this question?{color} {color:black}{color} {color:black}(hope your answer will be directly available in the ticket){color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Martijn{color} |{color:#000001} {color} |{color:#000001} Meier{color} | {color:#000001}ApplicationEngineer{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}+31621679216{color}{color:#000001} <tel:+31%206%2021%20679%20216>{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}_ | | !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} | *From:* Piotr Gaczorek (Jira) <[email protected]> *Sent:* maandag 20 februari 2023 14:39 *To:* Meier\', "Comment 11: Martijn <[email protected]> *Subject:* DGS-8588 Unlinking of recipes \'", "Comment 12: \'Dear Poitr and Martijn,Thank you for your help!What do you mean with PLR’s? The reason for the questionto remove these additional technologies is to change the link between therecipes.Now recipe A is linked torecipe B", "Comment 13: but in the new situation recipe B must be linked to A. I hope this answers yourquestion. Kind regards,Vivian van der NatFormulator\'", "Comment 14: \'[^plr_list.xlsx]\'", "Comment 15: \'We need to remove the associated PLR documents to remove the technologies themselves - I am sending a list of PLRs.Please confirm that they can be removed from the databases. [^plr_list.xlsx] \'", "Comment 16: \'Confirmed :)\'", "Comment 17: \'Thank you. I just wanted to mention the GDC-799 is for approval (additional technology- option to archive/disable and filter on latest version).\'", \'Comment 18: "In case you haven\\\'t removed the PLR\\\'s yet\', "Comment 19: please don\'t do. I received additional feedback about it. It was strongly suggested not to remove PLR from after October 1st", \'Comment 20: 2022.Is there an alternative way of unlinking the recipes without removeing the PLR\\\'s?"\', "Comment 21: \'There are two technologies to remove:VE303436,NY303436To remove them I must also remove the PLRs.Now recipe A is linked torecipe B", "Comment 22: but in the new situation recipe B must be linked to A.Can i get an example after such a change?\'", "Comment 23: \'Hi Piotr", "Comment 24: please remove thoses technologies. the connected PLRs are only for the recoding to the customer item. Some times customer itemcode is no longer valid and then it should be cleaned to be used as normal De Heus item\'", "Comment 25: \'This is also the reason why a change is asked for to be able to archive such technologies\'", "Comment 26: \'Hello", "Comment 27: additional technologies have been removed.\'", "Comment 28: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'} |
445 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8587\n\n### Instruction:\nwe are trying to produce 7800-b50 but when we create a production order it shows up as bulk therefore unable to confirm production order. please 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: \'Hello", "Comment 3: Please make a new version of the recipe.The linked now have been corrected.Regards.\'", "Comment 4: \'okay\'", "Comment 5: \'Can we close this incident as the issue has been resolved ?Regards\'", "Comment 6: \'yes please\']"]\nRelated Issues:\n[]\n\n### End'} |
446 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8586\n\n### Instruction:\nHello,\r\n\r\nWe cant confirm PLR 0672180223004, the error message does not give an indication as to what the issue might be.\r\n\r\nwe have checked the logs around this date no error message related.\r\nno raw materials are archived.\r\nmaintenance shows that the order, recipe, item etc. are in every module they need to be in.\r\nwe restarted services IntegrationPCS and Production nothing.\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hello", "Comment 4: Please verify connection!image-2023-02-20-10-38-37-621.png!Regards\'", \'Comment 5: \\\'Exception has been thrown by the target of an invocation. -> An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ProductionLots_Recipes_RecipeId". The conflict occurred in database "DHPlantStockBusinessLogicMain"\', \'Comment 6: table "dbo.Recipes"\', "Comment 7: column \\\\\'Id\\\\\'.The statement has been terminated.\'", "Comment 8: \'[[DHP 3.0] Unable to confirm PLR - Production lot with id 25117bcb-0486-4d8c-bf81-dcf8c74581d4 was not found|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%20Unable%20to%20confirm%20PLR%20-%20Production§ion-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{7ADC7B54-2063-46F7-A176-9F22E23993D5}&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%20Unable%20to%20confirm%20PLR%20-%20Production%7C7ADC7B54-2063-46F7-A176-9F22E23993D5%2F%29])\'", "Comment 9: \'!image-2023-02-20-11-26-39-216.png!\'", "Comment 10: \'Please try to confim it again.\'", "Comment 11: \'Resolved", "Comment 12: Thanks\']"]\nRelated Issues:\n[]\n\n### End'} |
447 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8585\n\n### Instruction:\nHello I have a problem with my own access rights in DHP CU. Namely it appears that somehow I inherited existence from the ex colleague with the same name as I. So the DHP CU says that the user already exists even that my colleague from IT erased all the roles. Everything is OK in DHP Sabac just for DHP CU. Can you please create me as new user in DHP CU? Nemanja Antonic will expand my rights but just please create me as a user. 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: \'This user required activation", "Comment 3: he is currently active - you can edit this account now.!image-2023-02-20-10-20-30-309.png!\'", "Comment 4: \'Hi it is now OK and thank you for your help. Best regards.\'", "Comment 5: \'Thank you for confirmation", "Comment 6: regards.\']"]\nRelated Issues:\n[]\n\n### End'} |
448 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8584\n\n### Instruction:\nPlease help to check PLR 4374190223005 in CanTho Plant ( 0437) .\r\n\r\nIn Production module : user created and confirmed lot number 374190223005 with 28 tons . But in WMS has delivery with 30 tons .\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-02-20-15-11-08-325.png!\'", \'Comment 4: "robił ten sam user w WMS nie ma zmiany z 30t na 28t{code:java} FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots] where AggregateId=\\\'be308d6e-cd50-4e89-bc1c-7476911e8990\\\' order by Created FROM [DHPlantWmsBusinessLogicEvents].[dbo].[WarehouseOrders] where AggregateId=\\\'9b573e79-92da-49b7-bfd6-44259f16a5e8\\\' order by Created{code} !image-2023-02-20-15-20-41-349.png! "\', "Comment 5: \' !screenshot-1! \'", "Comment 6: \'{code:java}Validation failed: -- Warehouse order should be in created status -- Warehouse order should be in processable status -- Warehouse order should be in progress -- Warehouse order should be execution pending -> Validation failed: -- WarehouseOrderShouldBeCreatedMessage -- WarehouseOrderShouldBeProcessableMessage -- WarehouseOrderShouldBeInProgressMessage -- WarehouseOrderShouldBeExecutionPendingMessage{code}!image-2023-02-21-11-50-53-383!!image-2023-02-21-11-51-20-475!\'", "Comment 7: \'hi Any news for this issue\'", "Comment 8: \'ustalenia stand up.\'", "Comment 9: \'Hello", "Comment 10: please provide information on how the operator made the change for this PLR and what operations were performed on the WO - we need a scenario for the error.In the log there is information that the change in the amount of PLR will not be processed due to the status of the WO.\'", "Comment 11: \'hi", "Comment 12: we do not have information how they can do that. just guess they align quantity but system get quantity in initial request\'", "Comment 13: \' !screenshot-2! mają ustawione na true dla AutomaticWoIpExecution\'", "Comment 14: \'The error occurred once", \'Comment 15: checking the logs there is no conclusive reason.The update did not pass to the WO due to the status of the document.If the problem recurs we can suggest RCA\', "Comment 16: it should be treated as an incident.\'", "Comment 17: \'so", "Comment 18: what will be next? close and RCA?\'", "Comment 19: \'Hi.We suggest to create RCA if the situation repeats - for a new case. We can create rca now and suspend them if the problem is reproducible (until the next case).\'", "Comment 20: \'no need to create DCA And please close the ticket\']"]\nRelated Issues:\n[]\n\n### End'} |
449 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8583\n\n### Instruction:\nPlease help to check this issue in Dong Nai Plant ( 0461).\r\nVT-67/2/23 : WO(PD)-30/2/23 and WO(PD)-29/2/23 has canceled but stock unit has relaeased and can not pick . \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: \'Everything looks correct. Stock has been moved to Released location. You should move it to desire location Using WMS functionality.On provided WO(PD) documents destination location was set to location FG.Please", "Comment 4: let me know if you expect any additional actions from us regarding this issue?\'", \'Comment 5: "{code:java}select * from [WarehouseOrders] where DocumentPrefix = \\\'wo(pd)\\\' and DocumentNumber in (29,30) and DocumentMonth=2 and DocumentYear=2023select * from WarehouseOrderElements where id in (\\\'AF6579BB-9210-46B2-BB50-37B0A6C0E15A\\\',\\\'FD0AFFE2-46C2-439F-9AFB-E487376AC959\\\')select * from StorageLocations where id =\\\'19C7E203-C6AF-40F9-A928-23D0B721C41E\\\'select * from [dbo].[WarehouseDispatches] where WarehouseOrderDocumentNumber in (\\\'WO(PD)-29/2/23\\\',\\\'WO(PD)-30/2/23\\\') order by documentselect * from [dbo].[WarehouseDispatchElements] where id in (\\\'A147676A-8D79-4AEC-8E3A-0986F05331CB\\\',\\\'58937AE6-01C2-4FCD-80A6-15AEF7EF7042\\\',\\\'DC2A9023-FBCF-4036-93D0-1D76A8F62373\\\',\\\'F58B8972-49B6-47D6-85DD-24A9BB80DCC7\\\',\\\'E007842D-F61E-411B-B5A5-32CE10FD50F2\\\',\\\'E076C276-314E-4096-A00D-590B78140C03\\\',\\\'DB060C7A-2C21-4415-A5B4-81C44E23ACB1\\\',\\\'991988EC-87D7-446E-A384-BCEAAE4845AF\\\',\\\'9B01E892-BE41-47B6-95BD-D5C74151A3BF\\\',\\\'95A44B47-4B41-4F48-BDF8-DC7DBEEA59B4\\\'){code}"\', "Comment 6: \'HiI understand. You can close this ticket. Thank u.\']"]\nRelated Issues:\n[]\n\n### End'} |
450 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8582\n\n### Instruction:\nWe have problem to close some warehouse order (IP), when we try to confirm, system shows an error message.\r\n\r\nWO(IP)-151/5/22\r\nWO(IP)-239/5/22\r\nWO(IP)-255/6/22\r\n\r\nCould you close ?\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: \'Nie ma już z taką datą.!image-2023-02-17-18-50-55-204.png!\'", "Comment 4: \'elementy są executed!image-2023-02-17-18-59-30-565.png!\'", "Comment 5: \'!image-2023-02-20-09-19-26-318.png!\'", "Comment 6: \'wszystko wydane już.\'", \'Comment 7: "{code:java}update w set status=50 FROM [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseOrders] w where Document in (\\\'WO(IP)-151/5/22\\\',\\\'WO(IP)-239/5/22\\\',\\\'WO(IP)-255/6/22\\\'){code}"\', "Comment 8: \'HiPriscyla", \'Comment 9: documents were verified and the status corrected to executed\', "Comment 10: please check.\'", "Comment 11: \'Hello,can I count on an update of this ticket?Thank you and regards.\'", "Comment 12: \'Hello Piotr,I checked and documents now are correct. You can close this task.Thank you\'", "Comment 13: \'Hello", "Comment 14: Priscyla.\\\\rThank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'} |
451 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8581\n\n### Instruction:\nsp-b/0541 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 in Entry again.Regards"]\']\nRelated Issues:\n[]\n\n### End'} |
452 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8580\n\n### Instruction:\nI\'ll write an e-mail\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: "Hi [[email protected]],Is it actual? We didn\\\'t get any details in this topic.Regards"\', "Comment 3: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}How irritating that my tickets are not communicated with you…{color} {color:black}See enclosed my message. Awaiting 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:windowtext}{color} !image001! <[https://www.de-heus.nl/]>{color:black}{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} _DeHeusVoeders_{color}_|https://www.de-heus.nl/privacy-beleid] _{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* dinsdag 21 februari 2023 10:02 *Aan:* Jong", "Comment 4: Christine de <[email protected]> *Onderwerp:* DGS-8580 102038 Several customers visible in Feed Sale Failed to add the following attachment to this issue because the file name is invalid.- 102038_Several_customers_visible_in_Feed_Sale___>_DGS_8580.eml\'", "Comment 5: \'Hi Christine,Unfortunately I still cannot see any attachment. Could you try enclose it by Jira directly from this link [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8580]? maybe name is not valid as I see in your last comment to this task. You can also send it to me by email.!image-2023-02-22-12-23-00-174.png!Regards\'", "Comment 6: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Working well this new process of tickets{color} {color:black}☹{color}{color:black}{color} {color:black}Not up to you", \'Comment 7: I know{color} {color:black}😊{color}{color:black}{color} {color:black}{color} {color:black}See below my mail{color} {color:black}😊{color} *Van:* Jong\', \'Comment 8: Christine de *Verzonden:* vrijdag 17 februari 2023 14:01 *Aan:* NL Servicedesk IT [[email protected]|mailto:[email protected]] *CC:* Geijtenbeek\', \'Comment 9: Bert [[email protected]|mailto:[email protected]] *Onderwerp:* 102038 Several customers visible in Feed Sale --> DGS-8580 {color:black}Hi,{color}{color:black}{color} {color:black}{color} {color:black}This should not happen..{color} {color:black}I am working in FE-N/0005 belonging to customer 102038.{color}{color:black}{color} !image001!{color:black}{color}{color:black}{color} {color:black}Feed movement to next round shows these round numbers?{color} {color:black}Only 102038/0042/0002 should be visible.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* woensdag 22 februari 2023 12:25 *Aan:* Jong\', "Comment 10: Christine de <[email protected]> *Onderwerp:* DGS-8580 102038 Several customers visible in Feed Sale !image001-1!!image007!\'", \'Comment 11: "Hi Christine,It\\\'s quite new requirement modified in task[https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8523] - \\\'Moving feed to different round on Feed sale - showing rounds also from invoice customer\\\'Now it\\\'s possible to choose also rounds for other customers if the same invoice customer is on both customers.For example if customer 102038 has the same Invoice customer = 004265 on Customer card like customer 014814 it\\\'s possible to choose rounds of this customer.!image-2023-02-22-15-17-39-753.png!!image-2023-02-22-15-17-32-219.png!Regards,Damian"\', "Comment 12: \'{color:black}Good morning Damian,{color} {color:black}{color} {color:black}Ah okay{color} {color:black}😊{color}{color:black}{color} {color:black}It was for me the first time I saw this.{color} {color:black}{color} {color:black}No problem then there. Case solved{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) <[email protected]> *Verzonden:* woensdag 22 februari 2023 15:26 *Aan:* Jong", "Comment 13: Christine de <[email protected]> *Onderwerp:* DGS-8580 102038 Several customers visible in Feed Sale !image006!!image007-1!\'", "Comment 14: \'Damian,We reconsidered this. For NAS please only make visible the same customer number", "Comment 15: actual round and next round. No other customer numbers.This is error sensitive.Thanks for your help.Christine\']"]\nRelated Issues:\n[\'DGS-8523\']\n\n### End'} |
453 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8579\n\n### Instruction:\nI\'ll write an e-mail\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 [[email protected]],Is it actual? We didn\\\'t get any details in this topic.Regards"\', "Comment 3: \'[[email protected]] odpowiedź klienta która nie wpadła do portalu (bo była mailem..)*Onderwerp:* FW: DGS-8579 Migration document not on FS 100753/0039/0001Hi Damian,It is indeed actual. Don’t know why this is not communicated with you.We are working on closure of our NAS rounds. ID 35468 is not visible on the financial statement.This should be solved.||Metvriendelijkegroet,\\\\u200b\\\\u200b\\\\u200b\\\\u200b||||Christinede||Jong|||MedewerkerContractadministratie|||\'", \'Comment 4: "Hi [[email protected]]It\\\'s caused by data on this PIThere is no Reference on this document\', "Comment 5: is it correct?Wen reference will be filled in this invoice will appear on Financial statement.Please let us know if we should filled in Reference in this field (I\'m not sure that you can do it", "Comment 6: it\'s Archived and sent to Milas).Otherwise (if this invoice is right) we need to adjust displaying invoices on Financial statement", "Comment 7: it\'s little different than on Round", "Comment 8: then on Round it\'s visible", "Comment 9: but on Financial Statement it\'s not visible.!image-2023-03-06-12-38-48-484.png!Please add remarks and responses directly in tickets in Jira as a comments", \'Comment 10: otherwise mails could stuck somewhere (when you sent information on e-mail adress [email protected]).Regards"\', \'Comment 11: "Hi Damian\', \'Comment 12: I don\\\'t now why reference is not filled. Cause it s a migration post.You can add reference SL008146.I think it should not have been sent to MILAS.Please modify.Thanks!Christine"\', "Comment 13: \'Hi Christine,Reference has been filled in and now PI is visible on Financial statement.Please verify that is correct.!image-2023-03-07-15-25-19-352.png!!image-2023-03-07-15-26-40-547.png!Regards\'", "Comment 14: \'Could we close the task?\'", "Comment 15: \'{color:black}Good morning!{color} {color:black}{color} {color:black}Yes Damian", \'Comment 16: please mark it as done.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* maandag 27 maart 2023 13:47 *Aan:* Jong\', "Comment 17: Christine de <[email protected]> *Onderwerp:* DGS-8579 Migration document not on FS 100753/0039/0001 \']"]\nRelated Issues:\n[]\n\n### End'} |
454 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8578\n\n### Instruction:\nOrder not sync to DHP CIteurup from DHC,, Evolution Service is Running and BUsiness platform is running.\r\n\r\nCTP SO 26329 for example\n\n### Response:\n["Comment 1: [\'!image-2!\'", "Comment 2: \'Hi,As per taskDGS-8575,currently we do not have access to DHP application server. Waiting for your feedback in email communication.Regards\'", "Comment 3: \'Currently", "Comment 4: my user also does not have access to below server to check DHC.Regards!image-2023-02-17-11-22-24-284.png!\'", "Comment 5: \'please wait", "Comment 6: my team will add your credential first\'", "Comment 7: \'Dostęp do servera DHC na credentialach Piotrka:!image-2023-02-17-11-31-07-977.png!\'", "Comment 8: \'Waiting for your feedback then\'", "Comment 9: \'Hi", "Comment 10: please try to connectApplication and Database DHP Welgro (10.62.15.13 and 10.62.15.6)\'", "Comment 11: \'What obout terminal server? Please", "Comment 12: see my reply via email\'", "Comment 13: \'Hi can we have teams call?\'", "Comment 14: \'sure\'", "Comment 15: \'Hi aleksandra,Do you already fix that? Our operational waiting for order.\'", "Comment 16: \'Klient robi restart usługi", "Comment 17: nie mamy uprawnień na restart usługi.była luka!image-2023-02-17-14-23-01-390.png!\'", "Comment 18: \'!image-2023-02-17-14-24-35-843.png!\'", "Comment 19: \'After restarted serviceDHCServiceClient orders have been processed.\'", "Comment 20: \'Actually we have done restart the service 3 times today to solve this problem", "Comment 21: and this is the 4th. How about after restart and then next order still not sync to dhp? Please give us solution.\'", "Comment 22: \'In reference to the conversation please extend the permissions to restart the serviceDHCServiceClient for my account.\'", "Comment 23: \'!image-2023-02-17-14-54-40-451.png!za niski poziom logowania usługi.\'", "Comment 24: \'Required entity was not found. -jest wyników 10260 do synchry.\'", "Comment 25: \'Samples", \'Comment 26: analyzes and analysis results had to be sent from DHP. Configuration changes were required after running the synchronization for this data.Additionally\', "Comment 27: the change affected the factory -Wirifa,Pasuruan.And for the factory Pasuruan and only here you still need to do a service restart.\'", "Comment 28: \'wyjaśnione przez teams - powiązane zDGS-6921.rozwiązaniem była zmiana dla externalID na numer planta (oprócz tego w tasku wcześniejszym)!image-2023-02-17-17-48-47-661.png!\'", "Comment 29: \'Hi piotr,Integration between DHP and DHC already smooth", "Comment 30: with monitoring from 17 midnight until 19 feb. Thank you for your support\'", "Comment 31: \'Hi", "Comment 32: thanks for confirming.As for the reason as I mentioned the problem was related to the export of samples and analysis results. A change was required to set correct the definition for the production areas.I am closing this task.\']"]\nRelated Issues:\n[]\n\n### End'} |
455 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8577\n\n### Instruction:\nCL000020433 is in DHC but not in DHP Andel\r\n\r\nPlease investigate.\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: \'Please verify I can see it in DHP :!image-2023-02-17-11-29-27-170.png!\'", "Comment 3: \'Ah", "Comment 4: it was at ASN and not on the Trip tab (where we were looking at). Thanks!\']"]\nRelated Issues:\n[]\n\n### End'} |
456 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8576\n\n### Instruction:\nlinked production areas are failing to auto generate recipes, again.\r\n\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7271\n\n### Response:\n["Comment 1: [\'Reklamacja do poprzedniego rca i zgłoszenia - opis w zlinkowanym pliku.\'", \'Comment 2: "Hi,We put this ticket on hold per last comment inDGS-8545. Waiting for Thabile when she\\\'s back to office.Regards"\', "Comment 3: \'Dear Thabile,Please", "Comment 4: let us know when you return.Regards\'", "Comment 5: \'Hello", "Comment 6: please take this off of hold i have commented in DGS-8545\'", \'Comment 7: "Hello,Thank you. I\\\'ve passed this issue to our Dev Team.Regards"\', \'Comment 8: "Hello [[email protected]]\', "Comment 9: for production area this won\'t work since non of warehouses are assigned to this production area. Because of performance issue we limited technology generation to only those production area that have orders created. Because non of warehouse is assigned to this production area", \'Comment 10: non of order will be assigned to it and non packed technology will be generated for this particular production area. If you would like to change this process\', \'Comment 11: please contact Product Owner of DH Country (Wijnand) to decide if it\\\'s global or local change and create GDC for you."\', "Comment 12: \'Hi,Any feedback? Can we close this task?Regards\'", \'Comment 13: "Still discussing with the business. I\\\'ll be on leave till Wed next week. Will respond after."\', "Comment 14: \'Sure", "Comment 15: waiting for you then :)Best regards\'", "Comment 16: \'Hi,Can we close this task?Regards\'", \'Comment 17: "Hi AleksandraI\\\'ve escalated it to NL (Theo). I\\\'m waiting for a response. You can place it on hold.Regards"\', "Comment 18: \'Hi Rey,Sure. Thank you for your information then.Regards\'", "Comment 19: \'We can close the ticket. We will be opening a GDC.\'", "Comment 20: \'Thank you", "Comment 21: Rey.Regards\']"]\nRelated Issues:\n[\'DGS-8545\']\n\n### End'} |
457 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8575\n\n### Instruction:\nPLR DHP Not Sync to DHC from 13:27 but service to DHC is running.\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 some examples number for plr’s and the ip addresses and credentials for Citeureup (Welgro) ( application and database?)\'", "Comment 3: \'We already restart dhc on citeurup dhp server 3times", \'Comment 4: after restart plr come to dhc. But I think there is something wrong\', "Comment 5: wo don’t need to restart service as often as that.\'", "Comment 6: \'As I asked you we do no have any information how to log toCiteureup (Welgro) enviroment.So pleaseCould you please provide some examples number for plr’s and the ip addresses and credentials for Citeureup (Welgro) ( application and database?)\'", "Comment 7: \'IP DHP Welgro terminal server : 10.62.15.13IP DHP Database Welgro : 10.62.15.6!image-2!\'", "Comment 8: \'User and password", "Comment 9: please\'", "Comment 10: \'please type your email", "Comment 11: I will ask to infrastructure team to add your credential\'", "Comment 12: \'If the PLr are in dhc may we change the priority to p2 ?In this task we have focused on clearingandunblocking the process. We can look up for the reason but if analisys will be more time consumingwe may raise RootCause Analysis (RCA)task for you.Please", "Comment 13: let us knowhow you wish us to proceed.\'", "Comment 14: \'Tha email for credentials has been already sent to you and Eric\'", "Comment 15: \'PLR not in DHC yet\'", "Comment 16: \'HiPLR already in DHC please closed the ticket.\']"]\nRelated Issues:\n[]\n\n### End'} |
458 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8574\n\n### Instruction:\nHi\r\n\r\nWe need to register this 85-W03A4A UL for PLR 0851150223005 on WO(IP)-147/2/23 document.\r\nWhen we try to register, system shows an message error: *Requested quantity for unit load exceeds available produced quantity. Unit load cannot be registered.*\r\n\r\nHowever, Produced Quantity = 2030kg; we already registered 2010kg and this 85-W03A4A UL is for 20kg\r\nI don\'t understand why system doesn\'t allow to register it.\r\n\r\nThe truck will arraive the factory tomorrow morning to load it. Could you please fix, identify why this i happening or teach us how to solve it?\r\n\r\nThank you very much\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-2023-02-17-07-36-34-592.png!\'", \'Comment 4: \\\'{code:java}2023-02-17 03:39:41 (9c2448e3-ddcc-42f1-87a3-2861b91583e7/Plant.WMS.BusinessLogic/BR-1-SV-VM0604/7432/199) [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/WarehouseIntake/registerMultipleIntakeFromProduction"\', \'Comment 10: "queryString": []\', \'Comment 11: "requestBody": "{\\\\\\\\"warehouseOrderId\\\\\\\\":\\\\\\\\"bccb4cef-3798-41ce-9951-21664aec752b\\\\\\\\",\\\\\\\\"warehouseOrderElementNo\\\\\\\\":1,\\\\\\\\"bagSize\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":30},\\\\\\\\"unitLoads\\\\\\\\":[{\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":20},\\\\\\\\"unitLoadType\\\\\\\\":40,\\\\\\\\"barcode\\\\\\\\":{\\\\\\\\"code\\\\\\\\":\\\\\\\\"85-W03A4A\\\\\\\\"}}]}"}.Kotrak.Common.Application.Exceptions.BusinessLogicException: Requested quantity for unit load exceeds available produced quantity. Unit load cannot be registered. ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: Requested quantity for unit load exceeds available produced quantity. Unit load cannot be registered. at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Plant.WMS.BusinessLogic.Domain.WarehouseIntakes.Services.IntakeFromProductionDomainService.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Domain\\\\\\\\WarehouseIntakes\\\\\\\\Services\\\\\\\\IntakeFromProductionDomainService.cs:line 69 at Plant.WMS.BusinessLogic.Application.WarehouseIntake.WarehouseIntakeFromProductionService.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionDataStructure dataStructure\', \'Comment 12: WarehouseOrder warehouseOrder\', \'Comment 13: WarehouseOrderElement warehouseOrderElement\', \'Comment 14: Owner owner) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseIntake\\\\\\\\WarehouseIntakeFromProductionService.cs:line 410 at Plant.WMS.BusinessLogic.Application.WarehouseIntake.WarehouseIntakeFromProductionService.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseIntake\\\\\\\\WarehouseIntakeFromProductionService.cs:line 111 at Plant.WMS.BusinessLogic.Application.WarehouseIntake.Handlers.RegisterMultipleIntakeFromProductionCommandHandler.Handle(RegisterMultipleIntakeFromProductionCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseIntake\\\\\\\\Handlers\\\\\\\\RegisterMultipleIntakeFromProductionCommandHandler.cs:line 36 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.WarehouseIntakeController.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\WarehouseIntakeController.cs:line 329 at lambda_method46691(Closure \', \'Comment 15: Object \', \'Comment 16: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 17: ObjectMethodExecutor executor\', \'Comment 18: Object controller\', \'Comment 19: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 20: Scope& scope\', \'Comment 21: Object& state\', \'Comment 22: 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 23: Scope& scope\', \'Comment 24: Object& state\', \'Comment 25: 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 26: Task lastTask\', \'Comment 27: State next\', \'Comment 28: Scope scope\', \'Comment 29: Object state\', \'Comment 30: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 31: Task task\', \'Comment 32: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 33: Task task\', \'Comment 34: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 35: Task requestTask\', \'Comment 36: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', "Comment 37: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext) --- End of inner exception stack trace ---{code}\'", "Comment 38: \'Na unitloadzie kody z reworku?!image-2023-02-17-08-49-43-882.png!!image-2023-02-17-08-57-42-838.png!\'", "Comment 39: \'Bulk miał rezerewację do PLR 0851150223021 i jego quantity on hand była 0", "Comment 40: dlatego nie można było zarejestrować palety. Po usunięciu rezerwacji z PLRa paleta została zarejestrowana. !screenshot-1! !screenshot-2! \'", \'Comment 41: "Bulk had its reservation forPLR 0851150223021 and its quantity = 0 that is why you couldn\\\'t register a pallet. After removing the reservation\', \'Comment 42: pallet has been registered.Please verify,Regards!image-2023-02-17-09-08-01-591.png!"\', "Comment 43: \'Hi AleksandraIs it possible to know the source of the request for reservation?I mean", \'Comment 44: who made this reservation? PCS\', \'Comment 45: user (which user?)And also why we have a document on reservation column\', "Comment 46: but no reserved quantity?Thank you very much\'", "Comment 47: \'!image-2023-02-17-13-55-59-558.png!Po finish jest jeszcze 181 eventów:!image-2023-02-17-14-11-18-404.png!\'", "Comment 48: \'Dear Maicon,PCS did not indicate the delivery and per plant configuration", \'Comment 49: delivery had to be indicated by the user.What I can check are the events on PLR. The last event made by PCS was ProductionLotFinishedEvent. Then\', \'Comment 50: there are 180 updating events\', \'Comment 51: done by uservsantanna and today by admin (which is Kotrak user) and uservsantanna again including Confirm event.To reply your question:_And also why we have a document on reservation column\', \'Comment 52: but no reserved quantity_?>> We havecolumn "Quantity" with all stock and "Quantity on hand",that shows available stock - quantity of reservations.!image-2023-02-17-14-37-01-649.png!\\\'\', "Comment 53: \'Hi AleksandraThanks for the information.You can close this task.Thank you very much\'", "Comment 54: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
459 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8573\n\n### Instruction:\nWe need to make consumption in production of item SUR6908-MD-S25 lot number 0891020223037, but this lot number is associated in the sales order/customer with entrusted configuration. (The lot number returned to factory to be reprocessed).\r\nWe need urgent use this production in an PLR as ingredient, but system not allow to use. Could you remove this configuration entrusted and link with SO to be possible use it?\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'We have removed check entrusted,!image-2023-02-16-19-39-57-035.png!please check if any further changes are required.\'", "Comment 3: \'{code:java} update d set del_cstid=null FROM [DHPlant_RC].[dbo].[Delivery] d where Del_Id = 244001{code}\'", "Comment 4: \'We added as ingredient in production 0891140223027", \'Comment 5: but when we try to close production\', \'Comment 6: is showing error message yet\', "Comment 7: missing stock. Could you check it? \'", "Comment 8: \'!MicrosoftTeams-image (49)-1!!MicrosoftTeams-image (47)-1!\'", "Comment 9: \'{{update [DHPlant_RC].[dbo].[WarehouseStocks] set [Wst_CstId]=null where Wst_ArtId = 21817 and Wst_DelId = 244001}}\'", "Comment 10: \'You should be able to close this PLR. Please check.\'", "Comment 11: \'Hi Bartłomiej Now it worked.You can close this task.Thank you very much!\'", "Comment 12: \'[[DHP 2.X] Entrusted customer - stock for item.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHP%202.X%5d%20Entrusted%20customer%20-%20stock%20for%20item§ion-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{6C364C55-E55B-487F-87F7-BED48EA81D86}&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%202.X%5D%20Entrusted%20customer%20-%20stock%20for%20item%7C6C364C55-E55B-487F-87F7-BED48EA81D86%2F%29])\']"]\nRelated Issues:\n[]\n\n### End'} |
460 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8572\n\n### Instruction:\nRealized weights do not arrive in DHP, which means no packing slips are being printed.\r\n\r\nSO example is SO000067871.\r\n\r\nPlease check, thanks!\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "Comment 2: \'Hello", "Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task underDGS-8571We will revert to processing your task as soon as possible.Regards\'", "Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 5: \'spora kolejka dla Proda:!image-2023-02-16-14-44-05-512.png!aktualnie schodzi\'", "Comment 6: \'Can I get information on what VT the realization should be? because for trip there is also no connection as below:!image-2023-02-16-15-23-36-849.png!\'", "Comment 7: \'kolejka z prod zeszła", "Comment 8: co odpiszą na nasz ostatni komentarz - realizacja SO.\'", "Comment 9: \'Could you please confirm if we can close this task?Regards\'", "Comment 10: \'Could you please confirm if we can close this task?Regards\'", "Comment 11: \'Could you please confirm if we can close this task?Regards\'", "Comment 12: \'Oops", "Comment 13: sorry. Yes you can.\']"]\nRelated Issues:\n[]\n\n### End'} |
461 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8571\n\n### Instruction:\nPlease remove the additional technologies for Andel-West: AW967352: This technology is wrong and now blocking the sending of recipe 966715\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: \'Hello", "Comment 4: you may check DGS-8572 first: This one has less priority\'", "Comment 5: \'Just to confirm", "Comment 6: all three subversions?\'", "Comment 7: \'Sure", "Comment 8: will do\'", "Comment 9: \'All three subversions indeed\'", "Comment 10: \'And what about the last one for item code 967352?!image-2023-02-16-14-06-58-989.png!\'", "Comment 11: \'For below items", \'Comment 12: additional technology has been removed. Please\', "Comment 13: let me know what about the fourth item with code 967352!image-2023-02-16-14-28-09-326.png!\'", \'Comment 14: "I think that last one is correct and shouldn\\\'t be removed"\', "Comment 15: \'Sure. So the three have been removed. Please", "Comment 16: let me know if we can close this task.Regards\'", "Comment 17: \'Thanks", "Comment 18: ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'} |
462 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8570\n\n### Instruction:\nProśba o skorygowanie od strony bazy naliczonej amortyzacji podatkowej środków trwałych (lista w załączniku) w module ŚT oraz weryfikacja poniższego środka, aby nie naliczała się amortyzacja podatkowa tylko bilansowa w przyszłości.\n\n### Response:\n["Comment 1: [\'!1_d23311cb039e4c8fb9847b7bf257dbe9![^do skorygowania wartość podatkowa.xlsx] _(12 kB)_\'", "Comment 2: \'Hi", "Comment 3: Fixed assets from xls file has been corrected. Please verify. When you add new fixed asset and you want to make only balance depreciation (without tax depreciation) you should add fixed asset like below !screenshot-1! and on OT document as below !screenshot-2! Please let me know if we can close this issue?\'", "Comment 4: \'Everything looks good", \'Comment 5: thanks for help\', "Comment 6: task to close.\']"]\nRelated Issues:\n[]\n\n### End'} |
463 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8569\n\n### Instruction:\nWhen creating a VT for Shipping Notice (Trip) 7_L000131024, DHP generates an error (see attachment for screenshot). \n\n### Response:\n["Comment 1: [\'!Error on creating VT!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: \\\'{code:java}2023-02-16 11:17:43 (8e91a85d-e516-4d86-8fdb-f2bcf9b5b0b4/Plant.VC.BusinessLogic/DHVD01AP183/1384/190) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 4: "host": { "Value": "dhvd01ap183:82"\', \'Comment 5: "HasValue": true\', \'Comment 6: "Host": "dhvd01ap183"\', \'Comment 7: "Port": 82 }\', \'Comment 8: "path": "/api/VehicleTicket/createVehicleTicketFromShippingNotice"\', \'Comment 9: "queryString": []\', \'Comment 10: "requestBody": "\\\\\\\\"09d81845-4001-4beb-92bb-cc641131eeb6\\\\\\\\""}.System.InvalidOperationException: Sequence contains no matching element at System.Linq.ThrowHelper.ThrowNoMatchException() at Plant.VC.BusinessLogic.Application.VehicleTickets.Extensions.VehicleTicketExplicitMapping.GetShippingNoticeElementsRelations(ShippingNotice shippingNotice\', \'Comment 11: IBusinessPartnerRepository businessPartnerRepository\', \'Comment 12: IOrderRepository orderRepository\', \'Comment 13: IItemRepository itemRepository) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Extensions\\\\\\\\VehicleTicketExplicitMapping.cs:line 332 at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.CreateVehicleTicketFromShippingNotice(AggregateId vehicleTicketId\', \'Comment 14: AggregateId shippingNoticeId\', \'Comment 15: 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_method6625(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: \'!image-2023-02-16-11-43-01-246.png!\'", "Comment 40: \'Could you please check if this packing form is correct?!image-2023-02-16-12-48-04-610.png!\'", "Comment 41: \'Hi Aleksandra", "Comment 42: this looks correct\'", "Comment 43: \'Dear Theo,-Z20 is packed", \'Comment 44: not bulk. Please\', "Comment 45: see attached settlement type:!image-2023-02-16-14-35-39-054.png!\'", "Comment 46: \'Hi Aleksandra", "Comment 47: please close this task\'", "Comment 48: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
464 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8568\n\n### Instruction:\nThere is need to back 2 rounds to Active status, because there should be created invoices and now it\'s not possible to choose this rounds on Purchase Invoices because they are closed.\n\n### Response:\n["Comment 1: [\'Rounds102051/0240/0001 and 102051/0240/0002 have been moved to Active again.\'", \'Comment 2: "These 2 documentsSP-M/0328\', \'Comment 3: SP-M/0330 have been sent to Entry to allow delete invoices from these S2P and update rounds on invoices (it\\\'s not possible to update round number on invoices when invoice is on S2P)."\', "Comment 4: \'More general: could we give Koen", \'Comment 5: Steffen\', "Comment 6: Nancy and Peter Moeiliker the rights to re-open rounds? Also they need to be able to set S2P back to entry status whenever they are archived.\'", "Comment 7: \'[[email protected]]do dodania dla tych userów uprawnienia do rozpoczyniania nowego procesu. Można stworzyć osobną rolę do tego", \'Comment 8: niewykluczone\', "Comment 9: że dojdą w przyszłości kolejni.\'", \'Comment 10: \\\'[[email protected]],the role "Start new process for document" has been added into test and prod Intense for Besse\', \'Comment 11: Koen\', \'Comment 12: Nancy\', \'Comment 13: Peter and Steffen.These users can test it on test environment\', "Comment 14: but they need to re-login to check it.Best regards,Grzegorz\'", "Comment 15: \'For Slaughtery Report documents in MAS NL and MAS BE has been turned on possibility to start new process for users who has rights to start new process for documents.\']"]\nRelated Issues:\n[]\n\n### End'} |
465 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8567\n\n### Instruction:\n21052 on pick location, active batch is correct but does not work.\r\nmanually it works immediately.\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: \'t seems that after the last update something is not going well. 21180 does not appear in the replenishment. Active batch is goodAllocation is empty", "Comment 4: but it is no longer allowed to look at it after the last update of the software.\'", "Comment 5: \'The analysis is in progress under the ticket numberDGS-8560\'", "Comment 6: \'Hello", "Comment 7: information has been provided in issue DGS-8560.Can this be closed?\'", "Comment 8: \'Close ticket\']"]\nRelated Issues:\n[\'DGS-8560\']\n\n### End'} |
466 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8566\n\n### Instruction:\nHelllo,\r\n\r\nthere are two warehouse orders for Sneek hanging, with status execution pending, see screenshot . When I try to open corresponding VT\'s I get an error: Can you please solve this and complete the intake?\n\n### Response:\n["Comment 1: [\'!2023-2-5-8-58-40-644!!2023-2-5-8-59-16-305!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-02-16-10-08-37-853.png!!image-2023-02-16-10-12-09-946.png!!image-2023-02-16-10-13-10-364.png!\'", \'Comment 4: \\\'{code:java}2023-02-16 10:12:48 (24d7e195-dc88-49c8-9396-176f9a9cb707/Plant.VC.BusinessLogic/DHVD01AP180/27856/203) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 5: "host": { "Value": "dhvd01ap180:82"\', \'Comment 6: "HasValue": true\', \'Comment 7: "Host": "dhvd01ap180"\', \'Comment 8: "Port": 82 }\', \'Comment 9: "path": "/api/VehicleTicket/getIntakeValidationInfo"\', \'Comment 10: "queryString": []\', \'Comment 11: "requestBody": "\\\\\\\\"efc5b6c1-7470-4349-aedc-908fb6ff0064\\\\\\\\""}.System.ArgumentException: Unit mismatch at Kotrak.Common.SharedKernel.Quantity.ToCommonUnit(Quantity x1\', \'Comment 12: Quantity x2) at Plant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicketBulkIntakeElement.get_Weight() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketBulkIntakeElement.cs:line 32 at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext() at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source\', \'Comment 13: TAccumulate seed\', \'Comment 14: Func`3 func) at Kotrak.Common.SharedKernel.Extensions.QuantityExtensions.Sum[T](IEnumerable`1 source\', \'Comment 15: Func`2 selector) at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.VehicleTicketIntakeDeviationPolicy.CalculateDeviation(VehicleTicket vehicleTicket) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\VehicleTicketIntakeDeviationPolicy.cs:line 34 at Plant.VC.BusinessLogic.Application.VehicleTickets.QueryHandlers.VehicleTicketIntakeDeviationQueryHandler.Handle(VehicleTicketIntakeDeviationQuery query) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\QueryHandlers\\\\\\\\VehicleTicketIntakeDeviationQueryHandler.cs:line 25 at Plant.VC.BusinessLogic.Infrastructure.Api.Controllers.VehicleTicketController.GetIntakeValidationInfo(String vehicleTicketId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\VehicleTicketController.cs:line 139 at lambda_method41897(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: \'Dear Thomas,I can see both related VT have status in progress. But I can also see a unit mismatch. Is taht correct?Regards!image-2023-02-16-10-16-42-660.png!!image-2023-02-16-10-17-03-250.png!\'", "Comment 40: \'It seems correct", \'Comment 41: because those products should be packed and not bulk. It seems I cannot correct this\', "Comment 42: can you do this? You may also remove these products from the VT so that the rest of the VT can be processed\'", "Comment 43: \'Also can you see what causes this? because the settlement seems to be correct in DHP?\'", "Comment 44: \'I cancelled problematic VTs", \'Comment 45: changed packing form for those items. Please\', \'Comment 46: create new VTs\', "Comment 47: it should work fine then.Regards\'", "Comment 48: \'thanks", "Comment 49: ticket can be closed\'", "Comment 50: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'} |
467 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8565\n\n### Instruction:\nCan you change in Fiancial Statement: Eendagskuikens to Aankoop\r\n\r\nCan you move documentnr. 1200089181/85 from Aankoop to Slachterij?\r\nYou can see what i have arched.\r\nSucces\n\n### Response:\n["Comment 1: [\'!image!\'", \'Comment 2: "Hello,{quote}Can you change in Fiancial Statement: Eendagskuikens to Aankoop{quote}We can change it on printout of Financial Statement in VAS sector - it should be changed only on FS printout in VAS?{quote}Can you move documentnr. 1200089181/85 from Aankoop to Slachterij?{quote}System displays documents on Financial statement based on \\\'Round Category\\\' on invoices.These 2 invoices have \\\'Round Category\\\' = \\\'Pigs\\\'\', "Comment 3: due to this are in section \'Pigs\' on Financial Statement. If it should be on \'Slaughtery\' section on Financial statement it should has \'Round Category\' = \'Slaughtery\'.I see that this Item = \'KORE\' has different \'Possible Round Category\'", \'Comment 4: maybe it\\\'s not well parametrized. Please verify these invoices and this item.!image-2023-02-16-09-28-26-980.png!!image-2023-02-16-09-29-41-998.png!"\', "Comment 5: \'To change label on printout.Item has been adjusted to different Round Category.\'", "Comment 6: \'Do zmiany linkowanie dokumentu SI z PI", \'Comment 7: PI powinien być widoczny na rundzie i być wygenerowany z SI\', "Comment 8: błąd przy migracji. PI31944 powinien być widoczny na rundzie.!image-2023-02-21-15-53-33-206.png!\'", \'Comment 9: "Do zmiany etykieta na wydruku w VAS - \\\'Eendagskuikens\\\' na \\\'Aankoop\\\'!image-2023-02-22-08-49-21-925.png!"\', \'Comment 10: "[[email protected]],we\\\'ve made changes in links\', \'Comment 11: round category in PI (ID: 31944). The document is visible on round now. Also we\\\'ve adjusted the printout for financial statement in VAS sector. You can feel free to test it.Best regards,Grzegorz"\', "Comment 12: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'} |
468 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8564\n\n### Instruction:\nWe are missing Lot reports in Milas (most for Andel, but also for other sites). The draft Lot reports and/or Lot reports are available in DHC but perhaps were not exported?\r\n\r\nCan you resend the draft Lot reports and Lot reports in the attached list to Milas?\r\n\n\n### Response:\n["Comment 1: [\'[^20230215_Missing Lot reports in Milas from 20230101-1.xlsx] _(18 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "{code:java}2023-02-13 13:14:28,046 [160] INFO Evolution.DHCERPService.MilasWebServiceClient.Services.MilasService [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MilasWebServiceClient\\\\\\\\Services\\\\\\\\MilasService.cs:178] - SendProductionLotReport 863060c6-7c19-4081-b78d-b129fd4a8b1b2023-02-13 13:14:28,093 [160] INFO Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:66] - Message with command ProductionLotReportSave and object id 863060c6-7c19-4081-b78d-b129fd4a8b1b was sucessfully processed.{code}Np z Andel wysłali 64 plr\', \'Comment 4: od początku roku{code:java}/****** Script for SelectTopNRows command from SSMS ******/SELECT * FROM [Evolution_DHCERP_NL_AS400_Identities].[dbo].[ProductionLotReportMappings] where dhcid in (select id FROM [DHCountry_NL_AS400_PROD].[dbo].[ProductionLotReports] where LotNumber in(\\\'0052160123003\\\',\\\'0984070223002\\\',\\\'0984060223002\\\',\\\'0984060223001\\\',\\\'0984100223004\\\',\\\'0984090223003\\\',\\\'0984030223002\\\',\\\'0984030223001\\\',\\\'0984060223003\\\',\\\'0984130223001\\\',\\\'0984100223003\\\',\\\'0984080223001\\\',\\\'0984070223001\\\',\\\'0984090223001\\\',\\\'0984070223003\\\',\\\'0984100223002\\\',\\\'0984230123004\\\',\\\'0984300123004\\\',\\\'0984160123002\\\',\\\'0984230123001\\\',\\\'0984190123002\\\',\\\'0984170123001\\\',\\\'0984260123002\\\',\\\'0984200123002\\\',\\\'0051090123009\\\',\\\'0984170123002\\\',\\\'0984170123006\\\',\\\'0051090123001\\\',\\\'0984130123001\\\',\\\'0984190123001\\\',\\\'0984160123003\\\',\\\'0984230123002\\\',\\\'0984270123002\\\',\\\'0984160123004\\\',\\\'0984170123003\\\',\\\'0984010223001\\\',\\\'0984220123001\\\',\\\'0984300123001\\\',\\\'0984270123003\\\',\\\'0984300123002\\\',\\\'0984240123002\\\',\\\'0984250123001\\\',\\\'0984270123001\\\',\\\'0984020223001\\\',\\\'0984160123001\\\',\\\'0984170123005\\\',\\\'0984260123001\\\',\\\'0984240123001\\\',\\\'0984110123002\\\',\\\'0984200123001\\\',\\\'0051110123010\\\',\\\'0984110123001\\\',\\\'0984180123001\\\',\\\'0984230123003\\\',\\\'0984170123004\\\',\\\'0984130123002\\\',\\\'0984180123002\\\',\\\'0984300123003\\\',\\\'0984220123002\\\',\\\'0984240123003\\\',\\\'0984130123003\\\',\\\'0984080223002\\\',\\\'0984090223002\\\',\\\'0051291222033\\\' )){code}Przy ponownej synchrze info że już jest wysłany:{code:java}2023-02-15 18:08:47,719 [13] WARN Evolution.DHCERPService.MilasWebServiceClient.Commands.ProductionLotReportSaveCommand [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MilasWebServiceClient\\\\\\\\Commands\\\\\\\\ProductionLotReportSaveCommand.cs:51] - PLR 863060c6-7c19-4081-b78d-b129fd4a8b1b was already synchronized - skiped2023-02-15 18:08:47,720 [13] INFO Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:66] - Message with command ProductionLotReportSave and object id 863060c6-7c19-4081-b78d-b129fd4a8b1b was sucessfully processed.2023-02-15 18:08:47,999 [24] INFO Evolution.DHCERPService.MessageSender.Handlers.BaseMessageHandler`1 [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:64] - Message received successfuly!{code}"\', "Comment 5: \'Please check if any of the plr list is still missing.\'", "Comment 6: \'Hello", "Comment 7: please reply to our last comment.Thank you and regards.\'", "Comment 8: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
469 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8563\n\n### Instruction:\nI\'ll write a mail after a meeting..\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,I think it\\\'s the same topic as in https://helpdesk.kotrak.com/browse/DHNLC-1233I think that is due to Item card parametrization. Where it should appear on Financial Statement? In \\\'Expenses\\\' section?If in \\\'Expenses\\\' item should have possible round category also \\\'Expenses\\\' (now is only feed).!image-2023-02-17-12-14-26-341.png!Please verify and let us know that it solves an issue.Regards"\', "Comment 3: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}It should be feed.{color} {color:black}{color} {color:black}I made the posting in feed sale", \'Comment 4: so it should be in feed.{color} {color:black}{color} {color:black}But because it can also be posted as an expense system can’t choose?{color} {color:black}Am I correct in my understanding?{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* vrijdag 17 februari 2023 12:27 *Aan:* Jong\', "Comment 5: Christine de <[email protected]> *Onderwerp:* DGS-8563 KOOG item not visible in feedsale \'", \'Comment 6: "In case when it should be feed that item should be also parametrized little differently.System displays lines from Feed sales on Financial statement section \\\'Total Feed\\\' when Item has: * has Item Group = \\\'Raw Materials\\\' or \\\'Finish product\\\' * has Possible Round Category = \\\'Feed\\\' * field \\\'Relevant\\\' on Feed sale line should be markedItem card!image-2023-02-17-13-17-06-217.png!Feed sale line!image-2023-02-17-13-18-51-437.png!!image-2023-02-17-13-09-18-889.png!"\', "Comment 7: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}This is feed it is a raw material.{color} {color:black}Can you change it on the Itemcard?{color} {color:black}I don’t have these rights{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* vrijdag 17 februari 2023 13:21 *Aan:* Jong", "Comment 8: Christine de <[email protected]> *Onderwerp:* DGS-8563 KOOG item not visible in feedsale !image006!!image007!!image008!\'", \'Comment 9: "I could change parametrization of this item\', \'Comment 10: but if this item has been used on other documents\', "Comment 11: then after changing this item on \'raw material\' it could affect settlements on other documents like Round", \'Comment 12: Financial Statement\', \'Comment 13: Saldo 2 Pay.Despite this\', \'Comment 14: should I change this item ?Regards"\', "Comment 15: \'{color:black}It should be change to feed.{color} {color:black}Then it is on the correct category.{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* vrijdag 17 februari 2023 13:56 *Aan:* Jong", "Comment 16: Christine de <[email protected]> *Onderwerp:* DGS-8563 KOOG item not visible in feedsale \'", \'Comment 17: "Item Group has been changed from Expenses to \\\'Raw materials\\\' on KOOG item card.If you tick field \\\'Relevant\\\' on Feed sale lines it should appear on Financial statement.Please verify that is ok."\', "Comment 18: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Okay I will check this.{color} {color:black}Thanks and have a great weekend{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* vrijdag 17 februari 2023 14:14 *Aan:* Jong", "Comment 19: Christine de <[email protected]> *Onderwerp:* DGS-8563 KOOG item not visible in feedsale \'", "Comment 20: \'Could you confirm that is correct?\'", "Comment 21: \'{color:black}Please close ticket. When it is not okay. I will report again.{color} {color:black}Thanks for your action{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* dinsdag 21 februari 2023 15:23 *Aan:* Jong", "Comment 22: Christine de <[email protected]> *Onderwerp:* DGS-8563 KOOG item not visible in feedsale \'", \'Comment 23: "Has been added role \\\'Item Relevant sectors edit\\\' which allows edit field \\\'Relevant sectors\\\' on Item Card. Users added to role:Bert\', \'Comment 24: Chrsitine\', \'Comment 25: Nancy\', \'Comment 26: Peter,Mitch\', \'Comment 27: Richard"\', "Comment 28: \'{color:black}Damian,{color} {color:black}{color} {color:black}Thanks so much!{color} {color:black}{color} {color:black}It works like a charm{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | *Van:* Damian Świstek (Jira) <[email protected]> *Verzonden:* dinsdag 28 februari 2023 12:13 *Aan:* Jong", "Comment 29: Christine de <[email protected]> *Onderwerp:* DGS-8563 KOOG item not visible in feedsale \']"]\nRelated Issues:\n[]\n\n### End'} |
470 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8562\n\n### Instruction:\nHi, can you permit access for Hurk, Elvera van den <[email protected]>; Dam, Nancy van <[email protected]>; Schellekens, Janine <[email protected]> in each others inbox?\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: \'Access for inboxes have been added to these 3 users.\']"]\nRelated Issues:\n[]\n\n### End'} |
471 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8561\n\n### Instruction:\nThis JO-330/23/TEMA has, zero cost on item 6320003, please help resolve this.\r\nI have tried using the method you showed earlier but it did not work on this one.\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: \'PLR = 0722110223003!image-2023-02-16-08-13-42-834.png!!image-2023-02-16-08-12-07-649.png!Nie ma tego itema na wydaniu!image-2023-02-16-08-12-51-160.png!\'", "Comment 4: \'!image-2023-02-16-08-22-02-383.png!!image-2023-02-16-08-28-33-799.png!\'", "Comment 5: \'!image-2023-02-16-08-34-45-472.png!\'", "Comment 6: \'!image-2023-02-16-08-40-42-026.png!\'", "Comment 7: \'Hi,Regarding this Job Order", "Comment 8: you do not have any resource in ERP XL for this item:!image-2023-02-16-09-05-49-463.png!!image-2023-02-16-09-04-51-327.png!?This is error from XL that says you do not have resource for give item:!image-2023-02-16-09-06-44-926.png!You do not have resource registered in XL because the intake was done only based on VT!image-2023-02-16-09-07-38-437.png!that does not have connection to any order!image-2023-02-16-09-08-32-193.png!!image-2023-02-16-09-10-43-782.png!Regards\'", "Comment 9: \'Hi,Is there anything else we can do for you or we can close this task?Regards\'", "Comment 10: \'Ok Please close the ticket", "Comment 11: we will handle it pls.\'", "Comment 12: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
472 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8560\n\n### Instruction:\nGoodmorning,\r\n\r\nthere are a lot of complaints about automatic replenishment not working for premixNL: See attached list, all those are created by hand because automatic replenishment did not work: Please investigate and propose a solution as quick as possible, frustrations are really high at the moment\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "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: \'And this is the list from yesterday", "Comment 5: you can see in colum created by that a lot are created by the user and not PCS_Automatic!afbeelding-1!\'", "Comment 6: \'xml message from pcs this morning[^Replenishments_20230215090412_d1c2b00d-cc79-4203-b99a-6c57a101a152_40577533.xml] _(3 kB)_\'", "Comment 7: \'It seems proces runs into an error !afbeelding-2!\'", "Comment 8: \'You can set it to P2 indeed\'", "Comment 9: \'Thank You\'", "Comment 10: \' !ABM for item 21079! \'", \'Comment 11: "{code:java}Select TOP (50) * FROM [DHapps_log].[dbo].[PcsWebServiceLog] where OperationId in (SELECT OperationId FROM [DHapps_log].[dbo].[PcsWebServiceLog] where OperationType = \\\'[PcsReplenishment]\\\' and LogLevel = \\\'DEBUG\\\')Order by Id Desc{code} !PcsReplenishment Errors TOP 50 ! Problem dotyczy tylko towaru 21079 i zaczął się !image-2023-02-15-14-44-09-079!----h2. Rezerwacje pod SO na kodach !image-2023-02-15-14-58-25-799!!image-2023-02-15-15-00-30-960!"\', \'Comment 12: "{code:java}SELECT TOP (1000) * FROM [DHP_NL_PROD].[dbo].[WarehouseStocks] where wst_artid = 1008 and Wst_SerialNumber = \\\'87014030112022266006\\\' order by 1 desc SELECT TOP (1000) * FROM [DHP_NL_PROD].[dbo].Delivery where Del_ArtId = 1008 and Del_SerialNumber = \\\'87014030112022266006\\\' order by 1 desc SELECT TOP (1000) * FROM [DHP_NL_PROD].[dbo].RegisterMappings where RgM_ArtId = 1008 and RgM_DelId = 266006 Select * from dbo.WMSStorageElements where StE_Code like \\\'%4000%\\\' order by StE_CreateDate desc Select * from dbo.Reservation where Res_ArtId = 1008{code}"\', "Comment 13: \'any update?\'", "Comment 14: \' !Double allocation with archival! \'", "Comment 15: \'Dear Thomas,We are still analyzing.Regards\'", "Comment 16: \'{code:java} DELETE FROM [DHP_NL_PROD].[dbo].[Allocation] where AlN_Id in --(3509) -- nie da się (2289)-- nie da się (2329)-- nie da się (2273)-- (27434)-- (27435)-- (3903)-- nie da się (3602)-- nie da się (3786)-- (3418)-- (3169){code}{code:java}Select * FROM [DHP_NL_PROD].[dbo].[Allocation] where AlN_Id in (2289,2329,2273,3602,3786)Select * FROM [DHP_NL_PROD].[dbo].ArticleCard where Art_Id in (258,993){code}!image-2023-02-27-13-15-31-522!\'", "Comment 17: \'any update?\'", "Comment 18: \'Dear Thomas,Thi issue and all others task related to replenishment have been still investigated by dev team. We are working on it.Regards\'", "Comment 19: \' !Deleted 5 allocations from DHP! \'", "Comment 20: \'Dear Thomas,I have information that Marcin has informed you about the case via Teams.Please", "Comment 21: let me know what would be the next step. Should we close this task?Regards\'", "Comment 22: \'I think the solution for the problem is not yet there on the application so please keep it open\'", \'Comment 23: "So let\\\'s put this task On Hold until solution will be deployed to application. Please\', \'Comment 24: let me know if this is fine for you.Regards"\', "Comment 25: \'Hi,Does the fix implemented underDGS-8630 resolved issue for you?Regards\']"]\nRelated Issues:\n[\'DGS-8593\', \'DGS-8598\', \'DGS-8630\', \'DGS-8595\', \'DGS-8634\', \'DGS-8567\']\n\n### End'} |
473 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8559\n\n### Instruction:\nShipping Notice L000131024 is visible in DHC but not arriving in DHP Utrecht, even after resending. \r\nCan you please check? \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: \'brak commitdate!image-2023-02-15-10-18-11-589.png!\'", "Comment 3: \'ogolnie jest takich 159\'", "Comment 4: \'Hi @Agnieszka", "Comment 5: already some news?\'", "Comment 6: \'@Agnieszka?\'", "Comment 7: \'The truck needs to leave", "Comment 8: please help!\'", "Comment 9: \'[[email protected]]it looks like sth wrong with ASN please look at screen below:!image-2023-02-15-11-56-17-718.png!It looks like this shipping notice is linked to two orders. One is for andel and one is for Utrecht.I think that is the case.\'", \'Comment 10: "[[email protected]] wydłubałem takie zapytanie:{code:java} select distinct pa.Name as shippingnoticeplant\', \'Comment 11: sn.ForeignNumber as ShippingNoticeNumber,bs.Name as OrderPlant\', \'Comment 12: o.ForeignDocumentNumber as OrderNumber --\', \'Comment 13: pa.*\', \'Comment 14: o.*\', \'Comment 15: oei.*\', \'Comment 16: bs.* from dbo.ShippingNoticeElements e inner join dbo.ShippingNoticeElementOrders seo on seo.ShippingNoticeElementId = e.Id inner join dbo.ShippingNotices sn on sn.id = e.ShippingNoticeId inner join dbo.OrderElements oe on oe.id = seo.OrderElementId inner join dbo.orders o on o.id = oe.OrderId inner join dbo.OrderExportInfoes oei on oei.EntityId = o.id inner join dbo.BusinessStructures bs on bs.id = oei.ClientId inner join dbo.ProductionAreas pa on pa.id =sn.ProductionAreaId where ForeignNumber like \\\'%7_L000131024%\\\'{code}"\', "Comment 17: \'[[email protected]],It looks like we have two asnsbut one with two elements with wrong order linked:!image-2023-02-15-12-01-31-230.png!\'", "Comment 18: \'Please check", "Comment 19: should be ok now\'", \'Comment 20: "Yes\', \'Comment 21: I see it now.Thanks!This morning I see lots of different things with SN\\\'s. I will monitor it. For now you can close this task."]\']\nRelated Issues:\n[]\n\n### End'} |
474 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8558\n\n### Instruction:\nOn request of the Formulation department, please remove these 2 links in DHC:\r\n\r\nVE303612 \r\nVE307617 \r\n\r\nPlease do so before 12:00 today. Thanks!\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hi,Could you please provide me some more details? What do those codes refer to? Could you please provide us with a screenshot from application?Regards\'", "Comment 3: \'I passed your question to Vivian", "Comment 4: is this attached screenshot sufficient information?!2023-2-4-10-53-11-859!\'", "Comment 5: \'Please", "Comment 6: confirm. You want us to remove additional technology for those items?\'", "Comment 7: \'Yes please", "Comment 8: only those two.\'", "Comment 9: \'Both additional technologies have been removed. No PLR related.Regards\'", "Comment 10: \'Yes thanks! Formulation is happy now :)Thanks a lot.\'", "Comment 11: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'} |
475 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8557\n\n### Instruction:\nHi\r\n\r\nTask from Wiola.\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: \'[^DGS-8557.docx]\'", "Comment 4: \'Description of the cause of the problem in the attachment[^DGS-8557.docx]\'", "Comment 5: \'!image-1!\']"]\nRelated Issues:\n[]\n\n### End'} |
476 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8556\n\n### Instruction:\nThe report Weighbridge dispatch available in VT is duplicating the element. We have problem in Unit Itaberaí and Apucarana. Could you check and fix it?\r\n\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'DGS-8433\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'In the last task (DGS-8433) was asked more examples", "Comment 4: but all VTs are with error\'", "Comment 5: \'ItaberaíVT-186/23VT-188/23VT-191/23!image!!image-1!!image-2!\'", "Comment 6: \'ApucaranaVT-681/23VT-679/23VT-669/23!image-3!!image-4!!image-5!\'", \'Comment 7: "Hello guysWe need this fixed asap.DGS-8433 was raise and we provided real cases of that. If the error is not present in other DHPlants it doesn\\\'t mean the problem doesn\\\'t exists. That\\\'s why we informed which plants have the issue.Thank you very much"\', \'Comment 8: "exec [dbo].[GetWeighBridgeNewPrintout] \\\'86117720-332a-44fa-87cb-b614b40bfb74\\\' !screenshot-1! {code:java}SELECT D.*\\\\t\\\\tFROM dbo.VehicleTicketPackedDispatchElements E\\\\t\\\\tINNER JOIN dbo.VehicleTicketPackedDispatchElementResources R ON R.Id = E.Id AND R.No = E.No\\\\t\\\\tLEFT JOIN dbo.Deliveries D ON D.SerialNumber = R.SerialNumber\\\\t\\\\tWHERE E.Status = 10 AND R.IsCancelled = 0 and e.Id=\\\'86117720-332a-44fa-87cb-b614b40bfb74\\\'{code}tutaj są dwa wpisy !screenshot-3! !screenshot-2! "\', \'Comment 9: "Problem jak w połacznym zgłoszeniu wydruk wiaze te z po deliveryid a tu mamy duble[[email protected]] Problemem jest wiazanie do tabeli delivery poniewaz dla jednej serialnumber jest kilka deliveryid więc dlatego w tym przypadku wyniki się duplikują.Czy jest to standardowe i normlane działanie ? czy Brazylia cos zmieniła w procesie\', \'Comment 10: czy ta procedura jest zła?bo sama procedura jak patrzyłam i w Apu i w innej fabryce jest taka sama\', \'Comment 11: wtedy taka sytuacja z duplikacją pozycji występowała by częsciej\', \'Comment 12: procedura też nie ejst najnowsza.Pytanie czy tak zawsze robili że jeden serial number był przypisany do kilku deliveryid?Przykład dla tgo zgłoszenia vt 669/23 z apuSELECT E.Id\', \'Comment 13: E.No\', \'Comment 14: NULL AS IssueDate\', \'Comment 15: R.SerialNumber\', \'Comment 16: R.WeightValue AS ResourceQuantity\', \'Comment 17: R.WeightUnit AS ResourceQuantityUnit\', \'Comment 18: R.ExpiryDate\', \'Comment 19: D.InternalSerialNumber\', \'Comment 20: D.CreatedDate\', \'Comment 21: NULL AS ForeignEAN\', \'Comment 22: NULL AS SourceDocumentNumber FROM dbo.VehicleTicketPackedDispatchElements E INNER JOIN dbo.VehicleTicketPackedDispatchElementResources R ON R.Id = E.Id AND R.No = E.No LEFT JOIN dbo.Deliveries D ON D.SerialNumber = R.SerialNumber WHERE E.Status = 10 AND R.IsCancelled = 0 and e.id= \\\'1E6686E6-0C73-4CCF-940A-6DF5DF515A36\\\'daje 32 wynikinp ten serialnumberd.SerialNumber=\\\'0882030223002\\\' pojawia sie 2 razy :!image-2023-02-15-07-36-03-220.png!natomiast wynik zapytania dla samej tabeliselect * from VehicleTicketPackedDispatchElementResources where id=\\\'1E6686E6-0C73-4CCF-940A-6DF5DF515A36\\\' ten serial number jest tylko raz a wszystkich wyników jest 14!image-2023-02-15-07-35-12-620.png!!image-2023-02-15-07-35-12-620! !image-2023-02-15-07-36-03-220!"\', "Comment 23: \'Taskhas been forwarded to the developers.\'", "Comment 24: \'[[email protected]] czy możesz podać z przykłady z jakich dokumentów pochodzą te serial number? \'", \'Comment 25: "Przykład dla tego zgłoszenia sprawdziłam{color:#0747a6}*vt 669/23 z apucarany*{color}SELECT E.Id\', \'Comment 26: E.No\', \'Comment 27: NULL AS IssueDate\', \'Comment 28: R.SerialNumber\', \'Comment 29: R.WeightValue AS ResourceQuantity\', \'Comment 30: R.WeightUnit AS ResourceQuantityUnit\', \'Comment 31: R.ExpiryDate\', \'Comment 32: D.InternalSerialNumber\', \'Comment 33: D.CreatedDate\', \'Comment 34: NULL AS ForeignEAN\', \'Comment 35: NULL AS SourceDocumentNumber FROM dbo.VehicleTicketPackedDispatchElements E INNER JOIN dbo.VehicleTicketPackedDispatchElementResources R ON R.Id = E.Id AND R.No = E.No LEFT JOIN dbo.Deliveries D ON D.SerialNumber = R.SerialNumber WHERE E.Status = 10 AND R.IsCancelled = 0 and e.id= \\\'1E6686E6-0C73-4CCF-940A-6DF5DF515A36\\\' !image-2023-02-15-09-59-01-956.png!!image-2023-02-15-09-59-01-956!"\', "Comment 36: \'[^GetWeighBridgeNewPrintout.sql]\'", "Comment 37: \'The procedure for printing has been updated.Uploaded to the plant Itaberaí.Please check.If it is correct", "Comment 38: we will upload to the other factories.\'", "Comment 39: \'Hello", "Comment 40: please reply to our last comment.Thank you and regards.\'", "Comment 41: \'Hello Piotr,I checked and is correct. Could you add for all units?Thank you\'", "Comment 42: \'[[email protected]] takie zmiany na sql/rdl do wydruków potrzebujemy też wciągnąć na Bitbucket.http://10.10.10.52:82/projects/PLA3/repos/dhp30implementations/browse/BASE/PRINTOUTS/BR\'", "Comment 43: \'Tutaj okazuje się", \'Comment 44: że na Staszku już mamy najnowsze zmiany.Natomiast jak będzie w przyszłości taki temat [[email protected]] to trzeba napisać do Maćka i do mnie\', \'Comment 45: żeby założyć DAPa i wciągnąć zmiany do projektu. Plus zapytać klienta\', \'Comment 46: jeśli tego nie powie\', \'Comment 47: czy wgrywać na innych plantach. [[email protected]] tylko wydaje się\', \'Comment 48: że nie zawsze zmieniony plik będziemy mogli wgrać na inne fabryki\', \'Comment 49: bo mogą mieć niższą wersję\', "Comment 50: w których np nie będzie odpowiednich kolumn.\'", "Comment 51: \'Rio Claro - aktualny.Apucarana - zmiana.Toledo - zmiana.Caruaru - procedura wywala się w tej wersji planta. !screenshot-4! Itaberai - zmiana już wykonana.Guararapes - zmiana.\'", "Comment 52: \'(y)\'", "Comment 53: \'Hello. The printouts have been updated on the factories except the factory in Caruaru - plant update is required", "Comment 54: due to the plant version.\'", "Comment 55: \'Hello Piotr,ok", "Comment 56: you can close this task. Thank you.\']"]\nRelated Issues:\n[\'DGS-8433\']\n\n### End'} |
477 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8555\n\n### Instruction:\nAll Purchase invoices should have always filled in fields\xa0\'Scanned Total invoice amount\' and \'Scanned Total VAT amount\'.\r\n\r\n\r\n!image-2023-02-14-15-21-02-039.png!\r\n\r\nWhen PI documents are sent to Milas and these fields are empty there is needed to filled in these fields in Milas.\r\n\r\nIn Intense these 2 fields should be always filled after saving document.\r\n\r\nWhen \'Kofax ID\' on Purchase Invoice is empty these 2 fields should be updated by Gross value and VAT value from Intense document.\r\n\r\nIt should be done on Purchase Invoices for all sectors.\r\n\r\n!image-2023-02-14-15-22-53-702.png!\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: ["Ready fro tests on UAT environment (IBIP_DH_TEST).If \\\'Kofax ID\\\' on Purchase Invoice is empty fields \\\'Scanned Total invoice amount\\\' and \\\'Scanned Total VAT amount\\\' will be updated after document save. * \\\'Scanned Total invoice amount\\\' = Gross Value for document * \\\'Scanned Total VAT amount\\\' = VAT Value for documentIf \\\'Kofax ID\\\' is not empty document won\\\'t be updated and will be like sent from Kofax.Please verify that everything is correct and after confirmation we can move it on production environment."\', "Comment 2: \'Hi,The new functionality has been tested successful by MvB. Please deploy asap to PROD.Thanks for the quick response! \'", "Comment 3: \'Hi,It has been deployed laso on production environment in all sectors.Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
478 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8554\n\n### Instruction:\nItem 307309 was linked an recipe for Helmond was received and accepted in DHC. Technology seems to be generated correctly. \r\nHowever, item and recipe did not arrive in DHP / PCS Helmond.\r\n\r\nCan you please check why the item and recipe are missing in DHP. Plant needs the recipe for production.\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: \'Recipes are now in DHP !screenshot-1! \'", "Comment 4: \'Ok", "Comment 5: thank you. What was the issue?\'", "Comment 6: \'Missing dhhitem in DHCService", "Comment 7: it has fixed in DHC 3.0.60.\'", "Comment 8: \'Thank you. This ticket can be closed.\'", "Comment 9: \'Thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'} |
479 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8553\n\n### Instruction:\nWhat are the conditons off printing different banking account on invoice.\r\nWill the banking account off "accounting" be used or from "adresses".\r\n\r\nIf "adresses" what are the selecting conditions off the bankingaccount?\r\nIs no bankaccount in "adresses" accepted?\r\n\r\nSee also DGS-8350\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'What are the criteria off selecting the bank account.In witch order.\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'PleaseThank you", "Comment 5: could you provide more details according to my previous question ?could please bring the path to printout template. and document number.It could be set in diffrent way for diffrent document type.To see how to check the path see alsoDGS-8350\'", "Comment 6: \'!image-2!!image-3!\'", "Comment 7: \'the incorrect HSBC bank account number is now also printed on the invoice.This is done using the Customers table under Addresses.How can be prevented the printing off this banking account\'", "Comment 8: \'Thank you for the example but what printout typoe you are using,?!image-2023-02-22-11-45-14-622.png!When I tried to generate an printout I get the empty number.\'", "Comment 9: \'In CDN (DH Premix) customer 7727 (De Heus a.s.) has the old DH Premix HSBC bank account number in the card (under Accounting settings). This ‘HSBC’ bank account number is printed on each invoice Premix sends to De Heus a.s. but needs to be removed in order to have the standard ABN bank account number of DH Premix on the invoice (it’s in the letter head).See customer card of customer 0674 where there is no Bank account number in the customer card", "Comment 10: then the standard will be printed when generating the invoice.Thanks and regards,Reinier!image-4!!image-5!\'", "Comment 11: \'I think this is a bug in CDN as (per below) once I open the Banks I don’t see the number ‘99’ in the list.To my opinion", \'Comment 12: the field should be blank but I cannot delete this.I tried to change it into NL14ABNA (which is the bank account number of Premix) but this doesn’t help.Now I cannot exit the customer card\', "Comment 13: see below.Best regards,Reinier!image-6!\'", "Comment 14: \'Hellothere is a few different cases you are mentioning herefirstthis is not an error it is not error:!image-2023-03-23-15-30-43-129.png!If you see that message and in fact you did not make changes in the document", \'Comment 15: just press save and then close the object.I am not sure what printout you are using but according to your message the problem is that the information in ERP XL for customer7727 are not updated and incorrect\', "Comment 16: do you wish us to set it the same as for 0694? The bank account is taken from address are you not able to add new address for that customer?\'", \'Comment 17: \\\'CASE WHEN "Rejestry"."KAR_IdentKontr"=1 THEN CDN.WirtualnyNumerRachunku("Rejestry"."KAR_RachIdentNrKier","Rejestry"."KAR_RachIdent","TraNag"."TrN_KntNumer",\\\\\\\'PL\\\\\\\') Else "Rejestry"."KAR_NrRachunku" ENDgidnumer dokuemntuTrN_GIDTyp=2037 AND TrN_GIDFirma=1015303 AND TrN_GIDNumer=3375490TrN_GIDNumer=3374351\\\'\', "Comment 18: \'Our employee B. Czarnocka made an comment.You cannot remove a bank account which has been used in the past but you can archive it", "Comment 19: add a new one and choose the new one as default (in the screenshot below I marked the fields to be used for that). When I look at this customer in CDN I see 2 addresses and 2 bank accounts for him. I do notice that there is an error when trying to edit the current one and it is not possible to archive him or to make the other one default (the field is greyed out).Why this appears and how can we change the default address & thus also bank account number?!image-7!!image-8!\'", "Comment 20: \'NL23HSBC0786449802HSBCNL2A\'", "Comment 21: \'!addin.PNG|thumbnail!\'", "Comment 22: \'Good morningthe bank field on the accounting bookmark has been updated", \'Comment 23: which by default of the previous add-on is not editable\', "Comment 24: the add-on is already enabled please verify!image-2023-03-30-13-52-47-402.png!!addin.PNG!!image-2023-03-30-13-53-47-279.png!\'", "Comment 25: \'May we close the task?\'", "Comment 26: \'Not yet.User did not respnde.\'", "Comment 27: \'I don’t see this HSBC bank account number anymore on the customer card so wait for the next invoice", "Comment 28: but should be fixed now.Thanks,Reinier\'", "Comment 29: \'If solved", "Comment 30: ok for me to go ahead & we will see on the next invoice to De Heus a.s. if this HSBC bank account number again appears or not.ThxReinier\'", "Comment 31: \'Ticket kan be closed\']"]\nRelated Issues:\n[]\n\n### End'} |
480 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8552\n\n### Instruction:\nPlease remove additional technology UT704911 (Utrecht) from DHC.\r\n\r\nKind regards,\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: \'Dear Rob,Which subversion? 0 or 1?Regards\'", "Comment 3: \'!image-2023-02-15-07-22-16-388.png!\'", "Comment 4: \'Dear Rob,Which subversion? 0 or 1?Regards\'", "Comment 5: \'Both\'", "Comment 6: \'Both additional technologies have been deleted.Regards\'", "Comment 7: \'Thank you for the support", "Comment 8: the ticket can be closed.\'", "Comment 9: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'} |
481 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8551\n\n### Instruction:\nRecipe 545201 does not go from DHC Compound to DHP Sneek.\r\nProduct needs to be produced.\r\n\r\nPlease investigate/fix.\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 Rob van Veen", \'Comment 3: It should be fine now. Please verify\', \'Comment 4: Recipe 545201 re-synchronize DHH >AS400 >DHP Sneek Please\', "Comment 5: let me know if you expect any additional actions from us regarding this issue? Can we close this ticket?Regards.\'", "Comment 6: \'AS400?The recipe arrived in SNeek. The ticket can be closed.Thanks for the support.\'", "Comment 7: \'fix in new versionRegards\']"]\nRelated Issues:\n[]\n\n### End'} |
482 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8550\n\n### Instruction:\nSP-B/0512 back to entry, S2P isn\'t correct, is it possible to do this myself?\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 Koen,Now it\\\'s in Entry again.Mitch and Richard now are also able to starting new process for Saldo to pay and put it back to Entry status.Regards"]\']\nRelated Issues:\n[]\n\n### End'} |
483 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8549\n\n### Instruction:\nCustomer 051199\r\nMany feed documents are double booked from 10-06-2022 till 24-09-2022\r\nCan you check and delete this?\n\n### Response:\n["Comment 1: [\'Hi,please mark in Excel file", "Comment 2: which lines should be delete from Feed Sale document - FE-V/0002:[^FS_ElementsToDelete_14022023_GM.xlsx]Best regards,Grzegorz\'", "Comment 3: \'To delete the latest duplicates compared by Document number", \'Comment 4: Item\', "Comment 5: Gross value.\'", "Comment 6: \'Elements to delete on red[^FS_ElementsToDelete_22022023_DS.xlsx]\'", "Comment 7: \'[[email protected]],the duplicate elements have been deleted from FE-V/0002 document.You can feel free to look into the Feed sale and give us the feedback.Best regards,Grzegorz\'", "Comment 8: \'THis can be closed.\']"]\nRelated Issues:\n[\'DGS-8537\']\n\n### End'} |
484 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8548\n\n### Instruction:\nHi, \r\n\r\nCould we update all the affected document of DGS-8498 on database level?\r\n\r\nBest Regards, \r\nClara\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 you wish to set checked fixed costs? Could you provide list of documents numbers?\'", "Comment 3: \'Yes", "Comment 4: we wish to set checked fixed costs. I will provide you the list this week since we do update document and then will list the affected cases. \'", \'Comment 5: "Hi\', "Comment 6: Sorry for keep you wait. I\'m waiting end user for month end closed. This month they do manage to close themselves. Please close the ticket. If I need any", \'Comment 7: I will raise new request. Thank you."]\']\nRelated Issues:\n[]\n\n### End'} |
485 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8547\n\n### Instruction:\nWe need to change bank account numbers on these two types of documents.\r\n\r\nIn the red rectangles are the old numbers and in the black are the new bank accounts.\n\n### Response:\n["Comment 1: [\'!ESI_Izmena (2)!!SI_Izmena (2)!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Default printouts have been modified: !screenshot-1! !screenshot-2! Please verify,regards.\'", "Comment 4: \'Everything is fine. You can close the ticket.\'", "Comment 5: \'Thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'} |
486 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8546\n\n### Instruction:\nHi, from Iwona:\r\n \r\n\r\nProśba o rozliczenie rozrachunków na koncie 238-04 od strony bazy:\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: \'Documents have been settled. Please verify.\'", "Comment 4: \'!image-2!\'", "Comment 5: \'Task to close", "Comment 6: thanks.\']"]\nRelated Issues:\n[]\n\n### End'} |
487 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8545\n\n### Instruction:\nlinked production areas are failing to auto generate recipes, again.\r\n\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7271\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!!image-3!!image-4!!image-5!!image-6!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'We create new RCa", "Comment 4: may we close this task and procceed all inDGS-8576?\'", "Comment 5: \'Hello,does the situation constantly repeat itself", "Comment 6: has technlogy not generated or is not generating in specific cases?\'", "Comment 7: \'Thabile is out of office this week. We will respond next week.\'", "Comment 8: \'Hello", "Comment 9: the function appears to not be working at all. users are manually generating production recipes if the PCS gives a warning stating that the recipe in the system is older than 3 months. the highlighted examples are for the lickline 70 these have orders not older than 90 days in DHP but the production recipes have not generated for them. the start date for all was 01/02/2023 import/acceptance 10/02/2023. all of them have only the base recipe in DHP aside from one or two where the recipes were manually generated !image-7!\']"]\nRelated Issues:\n[\'DGS-8576\']\n\n### End'} |
488 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8544\n\n### Instruction:\nAfter mistake of weighbridge operator in processing VT and canceling some items on it, DHC cannot syncrhonize documents, three item on VT-126/02/2023/CU. In red rectagnle is correct IO number, for black ractangle we need to change IO number to IO-14. \r\n\r\nCan you please check 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: "select * from VehicleTicketElementERPDocuments vdjoin VehicleTicketElements ve on ve.id=vd.VehicleTicketElementIdwhere vehicleticketid=\\\'AAA30761-BF08-4687-B1A8-308FE608D710\\\'-- ( pozycja 4 )"\', "Comment 4: \'Order IO 14 is executed by wmr+ that was modified from!image-2023-02-14-12-48-50-339.png!ON WMR +10 there is full quantity thats why it is impossible to choose this order from dhp ( it is on the list)Please verify and let me know to linked that VC with IO 14 and WMR+ 10 and set it as generated in DHC for that item?\'", \'Comment 5: "select * from TradeDocumentSyncs where xlid=\\\'1659655\\\'select * from TradeDocumentElementSyncs where xlid=\\\'1659655\\\'"\', "Comment 6: \'You need to add these two items on the stock also.!vukota dodavanje 21.02.2023!\'", "Comment 7: \'I asked you beforePlease verify and let me know to linked that VC with IO 14 and WMR+ 10 and set it as generated in DHC for that item? it was about a other vtVT-126/02/2023/CU.Do you need any help with this VT and this IO (14)?I do not get anserw.Now you are asking about other VT", "Comment 8: could you please create new task about vt 145/2 and please send more details what need to be done with this other VT.\'", "Comment 9: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 10: please raise another task.Regards\'", \'Comment 11: "Our management did not gave us any instructions regarding this incident so I couldn\\\'t answer you. Thanks for help!"]\']\nRelated Issues:\n[]\n\n### End'} |
489 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8543\n\n### Instruction:\nKB small WB is not showing weights in DHP. \r\n\r\nservices and sites were restarted but DHP still shows 0T \n\n### Response:\n["Comment 1: [\'!3789c1e7-8efc-4cd6-8634-ebe1421ffbf2.jpg|thumbnail!!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Please", "Comment 4: verify now and let me know.Regards\'", "Comment 5: \'Hello still not working. DHP initially showed nothing so we added more weigh0t", "Comment 6: then it showed weights for a second. [^2023-02-14_11-01-01.mp4] _(230 kB)_\'", "Comment 7: \'!image-2023-02-14-10-24-26-417.png!!image-2023-02-14-10-25-22-368.png!\'", "Comment 8: \'Please", "Comment 9: verify once again\'", "Comment 10: \'Hi", \'Comment 11: its still doing the same thing. "HP initially showed nothing so we added more weigh0t\', \'Comment 12: then it showed weights for a second."\\\'\', "Comment 13: \'Please", "Comment 14: verify now\'", "Comment 15: \'Not working !image-1!!image-2!\'", "Comment 16: \'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 17: \'We haveadjusted the parsing of data coming from the scale. Now it should work", "Comment 18: please verify.Regards\'", "Comment 19: \'!image-2023-02-14-14-58-11-956.png!\'", "Comment 20: \'Hi,How is the scale working today? Is it fine? If yes", "Comment 21: can we close this task?Regards\'", "Comment 22: \'Hello", "Comment 23: yes it is thank you task can be closed\']"]\nRelated Issues:\n[]\n\n### End'} |
490 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8542\n\n### Instruction:\nI\'m trying to generate Jan VTs but they are not going through.The Period is open\r\n !image-2023-02-13-16-00-41-177.png|thumbnail! \r\n\r\n !image-2023-02-13-16-01-03-177.png|thumbnail! \n\n### Response:\n[\'Comment 1: ["Probably the period of trade operations was closed by accident and later opened. The ERP integrator has updated information about the period closing and that\\\'s why the VT was not generated.We were restarting the ERPIntegrator\', \'Comment 2: the DHC settings were updated again and VT was generated in ERP."\', "Comment 3: \'Confirmed on Teams by Nosipho !screenshot-1! \']"]\nRelated Issues:\n[]\n\n### End'} |
491 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8541\n\n### Instruction:\nDears,\r\n\r\nthe following PO numbers are in DHC and not in DHP:\r\n\r\n23009497\r\n23009498\r\n23009499\r\n23009500\r\n23009501\r\n23009502\r\n23009503\r\n\r\nplease check as intake stopped.\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: \'Orders are now in DHP", \'Comment 3: !screenshot-2! !screenshot-3! after restarting the server\', "Comment 4: IIS services had to be restarted. !screenshot-1! \'", \'Comment 5: \\\'{code:java}2023-02-13 12:37:59 (/Plant.DHC.Integration/DHP-3/8476/16) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Peer. ReplyText "CONNECTION_FORCED - broker forced connection closure with reason \\\\\\\'shutdown\\\\\\\'"{code}\\\'\', "Comment 6: \'Thanks Piotr.\'", \'Comment 7: "You\\\'re welcome."]\']\nRelated Issues:\n[]\n\n### End'} |
492 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8540\n\n### Instruction:\nWiola zgłasza błędne działanie funkcjonalności do cofania anulowania wynagrodzeń(komunikat na zrzucie ekranu).\r\n\r\nProśba o cofnięcie anulowania wynagrodzenia dla pracownika Pinkas Mariusz:\r\n\r\nE-UM/2022/01/209\r\n\r\nE-UM/2022/02/74\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Proszę o weryfikację połączenia przez VPN", "Comment 3: jest zrywane bez żadnego komunikatu\'", "Comment 4: \'Anulowanie dla wskazanych wypłat zostało wycofane", "Comment 5: przyczyna komunikatu był indywidualny triggerKR_UpdateWPLZamknieta pilnujący poprawności opisów analitycznych. Pracownik na obecnym zatrudnieniu ma inny opis analityczny niż na anulowanej wypłacie stąd komunikat. Sama funkcja działa prawidłowo. Jeśli istnieje taka potrzeba można rozbudować trigger o dodatkowe warunki ale w ramach osobnego zamówienia i wyceny.\'", "Comment 6: \'Dzięki za pomoc", "Comment 7: do zamknięcia :)\']"]\nRelated Issues:\n[]\n\n### End'} |
493 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8539\n\n### Instruction:\nThe following recipes are not sent to the PCS.\r\nThey do exists in DHP.\r\n\r\n966715 \r\n960840\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: \'Dear Wijnand,Under DB I can see recipes are in PCS now. Please", "Comment 3: werify.Regards\'", "Comment 4: \'!image-2023-02-13-14-34-36-107.png!!image-2023-02-13-14-34-55-161.png!!image-2023-02-13-14-35-26-037.png!\'", "Comment 5: \'Hi", "Comment 6: the recipes are in the PCS. Thanks!\']"]\nRelated Issues:\n[]\n\n### End'} |
494 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8538\n\n### Instruction:\nLot reports are not send from DHP to DHC. The status in DHP is \'Finished\'. This holds for the following lot reports: 0092040223001, 0092040223002, 0093100223056, 0092040223003, 0093100223053, 0093100223064, 0092110223011\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: \'!image-2023-02-13-14-14-43-811.png!\'", "Comment 3: \'Could you please press confirm onh5. 0093100223056 and verifyalso0092040223001", \'Comment 4: 0092040223002\', "Comment 5: are cancell now!image-2023-02-13-14-17-52-611.png!\'", \'Comment 6: "I can confirm 0093100223056 needs to be send. The ones with status cancelled\', \'Comment 7: doesn\\\'t need to be send."\', "Comment 8: \'Let me know when you confirm 0093100223056.\'", \'Comment 9: "w logach z produkcji wisza na inboud wiaodmosci\', \'Comment 10: w pliku logów jak sie przywiesi trzeba sprawdzic czy jest log w logach tesktowych modulu prodkolejke zblokowal error typu :2023-02-13 00:00:00 (/Plant.Prod.BusinessLogic/DHVD01AP203/4900/35) [Error] Kotrak.Common.Infrastructure.Integration.Jobs.InboundProcessJob - Error during inbound processingMicrosoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint \\\'PK_Errors\\\'. Cannot insert duplicate key in object \\\'dbo.Errors\\\'. The duplicate key value is (0e883ddf-0f20-46d5-97f9-7fb254896233).The statement has been terminated. * trzeba wywyalic z tabeli intercontst wpis * FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[Errors] where id jak np (0e883ddf-0f20-46d5-97f9-7fb254896233)iloc wiadomosci an inboud :SELECT count (id) FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[InboundMessages]"\', "Comment 11: \'We have verified that there were problems with the queue of messages", \'Comment 12: incoming to the production module\', \'Comment 13: which may interfere with the work\', \'Comment 14: the queue has been started and gradually descend the messages\', "Comment 15: we are monitoring. Please try to confirm the remaining PLR and let us know if it helped.\'", \'Comment 16: "The PLR\\\'s I mentionned are from a couple days ago\', "Comment 17: so I don\'t expect them in the queue. The status of those PLR\'s are already on \'Finished\'", \'Comment 18: so I shouldn\\\'t confirm them again. It should be resended again from DHP."\', "Comment 19: \'pierwsze są z 08.02 które czekają mimo że lista spada zostają . !screenshot-1! \'", "Comment 20: \'The problem with the processing of messages has been since February 8", "Comment 21: so currently after clearing the process( the message must go down).You can try to manually confirm documents to go out of the queue.\'", "Comment 22: \'To confirm these PLRs quantities are needed to be added( by inventory).We can do it and confirm these PLRs - but we need confirmation from you. !screenshot-2! \'", "Comment 23: \'- dodanie ownera do dbo.owners w bazie prod(z bazy stock)- przesunięcie stockunitcreated dla ProcessDate - 6dni- dodanie stockunitcreated z error do kolejki inbound production z datą -10dni\'", "Comment 24: \'tyle zostało: !screenshot-3! {code:java}SELECT count(id)FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[InboundMessages]{code}\'", "Comment 25: \'Message queue is empty. Please check.\'", "Comment 26: \'[[DHP 3.0] kolejki dla modułu planta np. inbound prod|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%20kolejki%20dla%20modu%C5%82u%20planta%20np.%20inbound§ion-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{B86DBAE3-055E-48BC-A0F3-028121592873}&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%20kolejki%20dla%20modu%C5%82u%20planta%20np.%20inbound%7CB86DBAE3-055E-48BC-A0F3-028121592873%2F%29])\'", "Comment 27: \'Hello", "Comment 28: can we close this task?\'", "Comment 29: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 30: please raise another task.Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
495 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8537\n\n### Instruction:\nCan you move the feed delivery date before 01-10-2022 from 100451 > 51199\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 Bert,There are 33 lines on this Feed sale (FE-V/0001) with delivery date before 01-10-2022!image-2023-02-13-14-07-37-508.png!Should we moved all these lines to FE-V/0002 (customer 051199)?\'", "Comment 3: \'Yes indeed\'", "Comment 4: \'All feed sale lines with delivery date before 01-10-2022 have been moved fromFE-V/0001 toFE-V/0002.\']"]\nRelated Issues:\n[\'DGS-8549\']\n\n### End'} |
496 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8536\n\n### Instruction:\nIt should be possible to create credit invoices for SI and PI invoices in all sectors when this invoice is on Saldo to Pay.\r\n\r\nSystem shouldn\'t verify that invoice are on S2P or not.\n\n### Response:\n[\'Comment 1: ["Now it\\\'s possible to use action of crediting invoices for all invoices (SI and PI) in all sectors.It\\\'s not verified right now that invoice is already on Saldo to pay document\', "Comment 2: then it\'s possible to credit all invoices", \'Comment 3: it doesn\\\'t matter that this invoice is on S2P or not.It has been modified on test and production environmnents.Please verify that it\\\'s possible to use this action right now."\', "Comment 4: \'Zmieniona funkcjaKR_ReversebookingButton_Visible", "Comment 5: która odpowiada za podłączenie akcji.\'", "Comment 6: \'Is working properly.\'", "Comment 7: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'} |
497 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8535\n\n### Instruction:\nHello,\r\n\r\nWe see 2 lot reports with status finished not being send to ERP: Can you check why and resend these? Expect the problem is in DHC, but could be also DHP?\r\n\r\nlot report numbers:\r\n0093100223053\r\n0093100223056\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: \'0093100223053 = 55ddba83-a09e-4e84-af6c-6db1ca8f597b0093100223056 =e1a5ab46-bd75-452d-86f2-55515e45fa7c\'", "Comment 3: \'!image-2023-02-13-12-44-04-085.png!!image-2023-02-13-12-44-23-578.png!\'", "Comment 4: \'!image-2023-02-13-12-50-29-851.png!!image-2023-02-13-12-51-07-402.png!\'", "Comment 5: \'Hi Thomas,I can see confirm button is active for both PLRs. PLRs are sent to DHC only when they are in confirmed status. Could you please check if you can confirm both PLRs?Regards\'", \'Comment 6: "Hi Aleksandra\', \'Comment 7: for the DHP\\\'s used by the Netherlands it is configured that lot reports are also send in status finished (Finished product quantity is send) I assume this is also configured for Helmond?"\', "Comment 8: \'Hi Thomas,Please check today per solution in taskDGS-8538.Regards\'", "Comment 9: \'Ticket can be closed\'", "Comment 10: \'ok", "Comment 11: thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
498 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8534\n\n### Instruction:\nconfig for order status from which a PRO can be created is set to "confirmed and in progress" but if you click on \'select all\' (create based on order >> order filter) all statuses reappear.\n\n### Response:\n["Comment 1: [\'[^filter PRO.mp4] _(823 kB)_!image!\'", "Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", "Comment 3: \'Dear Thabile,Select all means select all statuses", \'Comment 4: from created to cancelled. Please\', \'Comment 5: provide me detailed information\', "Comment 6: what should appear after choosing all statuses?Regards\'", \'Comment 7: \\\'Hi AleksandraA change request was submited to restrict what could be seen/used from this screen. We\\\\\\\'ve set the config to only show "in progress" and "confirmed orders". Therefore the "Select All" option should obey the same rules. It makes no sense to be able to configure the system to not show these orders and be easily bypassed by checking "Select All".Regards\\\'\', "Comment 8: \'Hi Rey,Are you able to provide me with the change request number?Regards\'", "Comment 9: \'https://helpdesk.kotrak.com/browse/GDC-550\'", "Comment 10: \'Thank you\'", "Comment 11: \'Hi [[email protected]]", "Comment 12: [[email protected]],I created the GDC task for the fix to be implemented under the GDC-834.Regards\'", "Comment 13: \'Thank you. The ticket may be closed.\'", "Comment 14: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'} |
499 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8533\n\n### Instruction:\nPlease check the screenshot. It appears that i do not have access rights to see all the tickets in this case dgs8522. So please expand my rights so I can see all the tickets created by anyone in RS. Thank you.\n\n### Response:\n["Comment 1: [\'!CannotSee8522ticket.PNG|thumbnail!\'", "Comment 2: \'I have added you as a request participants to task DGS-8522.Please", "Comment 3: verify.Regards\'", "Comment 4: \'Now I can I access. Thank you for your quick help. Best regards.\'", "Comment 5: \'Thank you.\'", "Comment 6: \'Hello again. It appears that still I do not have access rights to se all the incidents in RS created by anyone. Namely Nemanja just created one incident and I could not see it until he added me manualy via SHARE. Can you please give me same rights as Nemanja Antonic for RS incidents? Thank you.\']"]\nRelated Issues:\n[]\n\n### End'} |
Subsets and Splits