Unnamed: 0
int64 0
999
| 0
stringlengths 258
77k
|
|---|---|
500 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8532\n\n### Instruction:\nHi, \r\n\r\nWe cannot close JO 315/23/AY and show error message as "Missing Quantity" to 9105. However, there is enough stock on 9105. No missing resources.\r\n\n\n### Response:\n["Comment 1: [\'!JO_20230213-1.JPG|thumbnail!!JO_20230213-2.JPG|thumbnail!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'prawdopdoobnie problemem sa rezerwacje na joselect sum(rez_ilosc) from cdn.Rezerwacje join cdn.twrkarty on twr_gidnumer=rez_twrnumer where rez_twrnumer=1084 and Rez_MagNumer=34\'", "Comment 4: \'May I know any update?\'", "Comment 5: \'Hi ClaraSorry for the delay.As I see now ", "Comment 6: the JO -315/23/AY was closed by Melody.Item 9105 was released.\'", \'Comment 7: "I checked that there was released item TC9105 instead of 9105.I think that probable reason of problems with releasing item 9105 was reservation of delivery IR+315/23/AY - 2/9/2023and system configuration that doesn\\\'t allow to you to release item before delivery date.There are resources on 9105 but delivery date is later then 2/9/2023. !screenshot-1! "\', "Comment 8: \'We do fix that JO and now is ok. Please proceed to close the ticket. Thank\']"]\nRelated Issues:\n[]\n\n### End'} |
501 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8531\n\n### Instruction:\nHi\r\n\r\nOrder SO-8534/22/UMR missing from DHP Umlaas.\r\n\r\nI can\'t find it in DHC either, but this may be a filter.\r\n\r\nI\'m busy with something, but will check back soon.\r\n\r\nRegards\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: \'2023-02-12 17:23:25,124 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Order message from trigger - ID - 7904202023-02-12 17:23:25,155 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Order data downloaded - SO-8534/22/UMR2023-02-12 17:23:25,155 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Sending Order message - SO-8534/22/UMR2023-02-12 17:23:25,155 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapping.... (Firma:556290 - TYP:960/NUMER:790420/LP:0", \'Comment 3: SO-8534/22/UMR)2023-02-12 17:23:25,202 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapped (Firma:556290 - TYP:960/NUMER:790420/LP:0\', \'Comment 4: SO-8534/22/UMR)2023-02-12 17:23:25,202 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message send (Firma:556290 - TYP:960/NUMER:790420/LP:0\', \'Comment 5: SO-8534/22/UMR)2023-02-12 17:23:26,870 [66] DEBUG Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - Order OrderId: 0ad206ce-8050-41c7-ba28-36c3140c8e2c BusinessPartnerAddress: c571ba02-6055-4b41-bbfd-01afbee3a32e is not synchronized2023-02-12 17:23:26,870 [66] INFO Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - ResynchronizeDataExtension is off - resynchronization skipped2023-02-12 17:23:39,183 [26] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution started2023-02-12 17:23:39,459 [26] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution finished2023-02-12 17:23:39,459 [26] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution started2023-02-12 17:23:39,475 [26] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution finished2023-02-12 17:23:43,012 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Order message from trigger - ID - 7904202023-02-12 17:23:43,028 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Order data downloaded - SO-8534/22/UMR2023-02-12 17:23:43,028 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Sending Order message - SO-8534/22/UMR2023-02-12 17:23:43,028 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapping.... (Firma:556290 - TYP:960/NUMER:790420/LP:0\', \'Comment 6: SO-8534/22/UMR)2023-02-12 17:23:43,044 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapped (Firma:556290 - TYP:960/NUMER:790420/LP:0\', \'Comment 7: SO-8534/22/UMR)2023-02-12 17:23:43,059 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message send (Firma:556290 - TYP:960/NUMER:790420/LP:0\', "Comment 8: SO-8534/22/UMR)2023-02-12 17:23:44,135 [51] DEBUG Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - Order OrderId: 0ad206ce-8050-41c7-ba28-36c3140c8e2c BusinessPartnerAddress: c571ba02-6055-4b41-bbfd-01afbee3a32e is not synchronized2023-02-12 17:23:44,135 [51] INFO Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - ResynchronizeDataExtension is off - resynchronization skipped2023-02-12 17:23:54,191 [16] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution started\'", "Comment 9: \'Przesynchronizowano ponownie - log w komentarzy wyżej.\'", \'Comment 10: "We tried to re-sync the document but it won\\\'t create. This document is from the time of the inventory.Could you SO be canceled and reissued?If this doesn\\\'t solve the problem\', \'Comment 11: can we change this priority to P2 and verify the problem with the development department first thing tomorrow morning?"\', \'Comment 12: "I\\\'ve asked. If you are unable to solve the issue\', \'Comment 13: then drop to a P2."\', \'Comment 14: "Needs ti be bumped back to a P1. Order SO-691/23/UMR done to replace order is not sync\\\'ing either."\', "Comment 15: \'Can you confirm you are working on this?\'", "Comment 16: \'Yes. We are working on it\'", "Comment 17: \'Please check now it should be ok\'", "Comment 18: \'Asking production to check.\'", "Comment 19: \'There was a problem with address synchronization. I forced sync again and order showed up in the system. Please check if other orders from this contractor are correct.\'", "Comment 20: \'Thank you. You may close the ticket.Have a good evening.\']"]\nRelated Issues:\n[]\n\n### End'} |
502 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8530\n\n### Instruction:\nPlease help to check this case and solving in Hai Phong 2Plant -0436.\r\n\r\nPLR 4361100223101 could not be found in the Production Report module (Maybe, user deleted this PLR) . But release to stock with stock unit status In progress . Please check and clear this stock unit . Thank u\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: \'Yes", \'Comment 4: indeed\', \'Comment 5: PLR was in Stock module\', \'Comment 6: so probably it has been deleted by user from Production module.Stock Unit is cleared. Please\', "Comment 7: verify.Regards\'", "Comment 8: \'Dear AleksandraU can close this ticket. Thank u.\'", "Comment 9: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
503 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8529\n\n### Instruction:\nHi\r\n\r\nWe just received the information that Microsoft is validating the security protocol:\r\nbq. Any non-TLS 1.2 compliant and older cipher suites will no longer be supported.\r\n\r\nIn August/2022 we had a DGS-7365 because the security protocol was changed and our Microsoft partner forgot to communicate us about the change. Then Przemysław Przybyszewski made the fix for us.\r\n\r\nI\'d like to know if *the fix done in August is already with TLS 1.2?*\r\n\r\nYou can check it here: [Link here|https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/get-started/removed-deprecated-features-platform-updates#transport-layer-security-tls-rsa-cipher-suites]\r\n\r\nThank you very much\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 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 3: \'[[email protected]]we made changed according to this article [https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client]so it should be on TLS 1.2\'", "Comment 4: \'Hi PrzemysławThank you very much for this information.You can close this task\']"]\nRelated Issues:\n[]\n\n### End'} |
504 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8528\n\n### Instruction:\nRecipe 110469 did not arrive in Maasbracht.\r\n\r\nI see an error in DHC, see attached screenshot.\n\n### Response:\n["Comment 1: [\'!2023-02-10 19_57_51-Window!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hi Bartlomiej", \'Comment 4: any update to mention? I got a call from the people\', "Comment 5: they are really urgently waiting on it.\'", \'Comment 6: "Please give us a moment. We\\\'re working on it"\', "Comment 7: \'Sure", "Comment 8: thanks!\'", "Comment 9: \'Please check. Now it should be ok.\'", \'Comment 10: "I see\', \'Comment 11: thanks!I\\\'ve asked if the planning dept. can proceed. Will update you soon."\', "Comment 12: \'It is indeed in DHP now", "Comment 13: but not in PCS. Any suggestions?\'", \'Comment 14: "Probably a PCS issue. On a truckplanning list in the PCS they see it\', \'Comment 15: but not in production.They\\\'ll call PCS supplier."\', "Comment 16: \'OK thanks for the information. It should appear in PCS if it is correct in DHP.Please let me know how to contact PCS.\'", "Comment 17: \'The people in the factory will do that. We can close this ticket. Please provide an RCA (can be done next week).Thanks for the support!\'", "Comment 18: \'The issue is fixed in version 3.0.60 of DHC.RCA is DGS-8487\']"]\nRelated Issues:\n[\'DGS-8487\']\n\n### End'} |
505 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8527\n\n### Instruction:\nPomyłka operatora. Proszę o zmianę indeksu na W00.\r\nProszę o dokonanie potrzebnych zmian w DHP, DHC i CDN\r\n\r\nPasza pilna do workowania.\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: \'If I understand correctly issue is related to LOT 0211100223032. This lot is confirmed. That mean it has been send to DHC and documents in ERP system has been generated (ZP-443/02/23/G and PW-442/02/23/G)We are sugesting to create new lot and proceed it for new production. Existing dokuments forLOT 0211100223032 in ERP systems should be cancelled and quantity for resources in DHP have to be corrected trough stocktaking.The work related to correcting this situation from the database will take several hours and we cannot guarantee that as a result of them there will be no problems with this product in the future.\'", "Comment 4: \'Task to close \'", "Comment 5: \'Jakby się powtórzył taki błąd - do poprawy od bazy.Informacja po retro.\']"]\nRelated Issues:\n[]\n\n### End'} |
506 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8526\n\n### Instruction:\nI am not able to calculate technical results.\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: "We\\\'ve fixed this issue with procedure parameter. Now it should be good.Regards"\', "Comment 4: \'It is working again.\'", "Comment 5: \'I close the task - it was related toDGS-8325\']"]\nRelated Issues:\n[\'DGS-8325\']\n\n### End'} |
507 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8525\n\n### Instruction:\nThe PO 1260/12/22 has been intaked with VT 154/2/23 but the resulting POR is not showing up in ERP, i have also checked in DHC yet nothing to indicate it has been processed\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-10-12-17-09-600.png!\'", "Comment 3: \'!image-2023-02-10-12-20-22-825.png!\'", "Comment 4: \'!image-2023-02-10-12-23-22-275.png!\'", "Comment 5: \'w DHC VT jest spięty juz z zrealizowanym IO - 181 ", \'Comment 6: po 1260 jest w ogole na inny item,który został zrealizowanym innym dokumentem ale wg erp xl w opsiei dla io - vt 157 a nie 154select cdn.NazwaObiektu(TrN_GIDTyp,TrN_GIDNumer,1,2),trn_openumerw,tno_opis,cdn.NazwaObiektu(zan_gidtyp,zan_gidnumer,1,2)\', "Comment 7: trn_zannumer,* from cdn.ZamNag left join cdn.tranag on zan_gidnumer=TrN_ZaNNumer join cdn.TrNOpisy on TnO_TrnNumer=TrN_GIDNumer where trn_zannumer in (27466,27461,25355)!image-2023-02-10-13-11-42-852.png! !image-2023-02-10-13-15-48-519.png! !image-2023-02-10-13-11-42-852!!image-2023-02-10-13-15-48-519!\'", "Comment 8: \'wg bazy danych sa dwa vt o numerze 154 na luty :!image-2023-02-10-13-25-11-962.png!\'", "Comment 9: \'Hello could you please provide full VT numberbecuase in data base I can see 2 vt:154/2/2023/AC 154/2/2023/JNI DHC country I can see only this154/2/2023/JN it is on hold status and linked to diffrent order= IO 181 and it is in onhold status.It is for diffrent item then the order po 1260 in ERPXLAlso this item is set as not generated", \'Comment 10: because the IO-481 was executed by VTVT-157/2/2023/AC and it was executed buy next one. Let me know\', \'Comment 11: if the realization for IO 181 is correct\', "Comment 12: if yes andIf forvt -154/2/2023/JN informationare sufficient for you let me now. If you do not want to proceed the vt-154/2/2023/JN - you may hold/cancel it.!image-2023-02-10-13-37-22-784.png!THE second154/2/2023/AC with AC extension was invisible in application cause it has no elements synchronized to DHC.!image-2023-02-10-13-48-33-390.png!But it is in dhp :with connection to order po-1260!image-2023-02-10-13-53-00-021.png! !image-2023-02-10-13-53-00-021!I resend this VT again to DHC!image-2023-02-10-14-23-50-373.png!And POR was generated :!image-2023-02-10-14-25-13-900.png!!image-2023-02-10-14-23-50-373! !image-2023-02-10-14-25-13-900!\'", \'Comment 13: "id vt w dhp\\\'id=2c3cbce0-0cfc-4011-915d-4305f52df6a0\\\'"\', "Comment 14: \'PLEASE CLOSE\']"]\nRelated Issues:\n[]\n\n### End'} |
508 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8524\n\n### Instruction:\nWe would like to have the same "add/change conditions" functionality available on SC\'s as we have on contracts farmer.\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: "[[email protected]]did you mean there is needed flow fro \\\'Contract Slaughtery\\\' document (not Slaughtery Report) as it is in \\\'Contract farmer\\\' document?When document is \\\'Active\\\' and we want to send it to \\\'Add change conditions\\\' to which users it should be processed? (In Contract farmer process it is sent to users from role \\\'Senior contract administrator\\\')"\', "Comment 3: \'Yes indeed\'", \'Comment 4: \\\'[[email protected]],I added new flows "Add/change conditions" from "Active" status for Contract Slaughtery MAS NL and MAS BE on test environment.You can feel free to test it.Best regards,Grzegorz\\\'\', "Comment 5: \'Tested", "Comment 6: can be moved to PROD.\'", "Comment 7: \'[[email protected]],the new flows added to PROD process.You can feel free to test it.Best regards,Grzegorz\'", "Comment 8: \'Confirmed that can be closed.\']"]\nRelated Issues:\n[]\n\n### End'} |
509 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8523\n\n### Instruction:\nOn Feed sale line in \'Move to round number\' should be possible to choose rounds from other customer who has the same invoice customer like this one on Feed sale.\n\n### Response:\n[\'Comment 1: [\\\'Hi,adjustements on "Move to another feed sale" lookup have been done for Feed Sale elements. You can feel free to test it on test environment.Best regards\', "Comment 2: Grzegorz\'", "Comment 3: \'In Production?\'", "Comment 4: \'[[email protected]]", "Comment 5: I forgot to write this in comment. On the test environment.\'", "Comment 6: \'No problem. I have tested this and it works fine. Can be moved to PROD.\'", \'Comment 7: "[[email protected]]\', \'Comment 8: the modification has been adjusted on production environment. I\\\'m waiting for respone to close the task.Best regards,Grzegorz"\', "Comment 9: \'It should be possilbe to choose rounds like on the example below:Customer A ", \'Comment 10: Invoice Customer BCustomer C\', \'Comment 11: Invoice Customer BCustomer D\', "Comment 12: Invoice Customer EFeed sale on Customer A - should be possible to choose round from Customer A and C (because there is connection between invoice customer)\'", "Comment 13: \'HI", \'Comment 14: it can also be like this:Customer A \', \'Comment 15: Invoice Customer BCustomer B\', \'Comment 16: Invoice Customer BCustomer D\', "Comment 17: Invoice Customer DThan as well A and B are able to send feed sales to each other.\'", \'Comment 18: \\\'Hi,we did rollback the settings on the field "Move to round number" on production database.The modifications for field have been added on test environment. You can feel free to test it.I\\\\\\\'m waiting for your reply to add it on prod environment.Best regards,Grzegorz\\\'\', "Comment 19: \'In the test environment I should be able to move feed from and to these three rounds:* 00024J/0276/0001* 808104/0041/0001* 008104/0285/0001All these three customers have the invoice customer 008104. However I am not able to move feed from 00024J/0276/0001 to 008104/0285/0001", "Comment 20: not from 00024J/0276/0001 to 808104/0041/0001.\'", "Comment 21: \'[[email protected]],I made changes in this area and now it looks good.!image-2023-02-13-11-51-50-132.png!\'", "Comment 22: \'OK", "Comment 23: can be moved to PROD.\'", \'Comment 24: \\\'It would be nice if the same procedure (being able to move to different delivery customer but the same invoice customer) is available for the functionality "Update round number on invoice".Is that possible?\\\'\', "Comment 25: \'[[email protected]],done. You can feel free to test it on production environment.\'", \'Comment 26: \\\'I\\\\\\\'m looking into action and I see that right now the customer on "Round" lookup is selected with conditions: * SI: when Customer of Sales invoice has BP_Category -"Slaughter" then we are use Referance but in other cases we are use Customer field. * PI: when Customer of Purchase invoice has BP_Category - "Farmer"\', \'Comment 27: "Pas Farmer"\', \'Comment 28: "Oppas farmer" then we are use Referancebut in other cases we are use Customer field.So\', "Comment 29: for sure are you want to add the funtionality for more Rounds on list for these two cases: Customer and Reference?\'", "Comment 30: \'I am not sure if I get you. I am not sure how the reference is involved in this.It should be like this: if a specific invoice is now on round for customer A and customer A has invoice customer B than it should be possible to move this invoice to other rounds that are related to invoice customer B:Customer A ", \'Comment 31: Invoice Customer BCustomer B\', \'Comment 32: Invoice Customer BCustomer D\', "Comment 33: Invoice Customer DThan as well A and B are able to send invoices to each other.\'", "Comment 34: \'[[email protected]],I made changes on action", "Comment 35: you can feel free to test it on test environment.Best regards,Grzegorz\'", "Comment 36: \'Confirmed that can be closed.\'", "Comment 37: \'In NAS sectore change is needed - it should works like it was before. Should be possible to move feed to different round only for rounds from customer which is selected on header of the document.In other sectors it should be possible to choose rounds also from other customers which has the same invoice customer.\'", "Comment 38: \'[[email protected]]do zmiany w sektorze NAS - powinno być tak jak wcześniej i dać się wybrać rundy powiązane tylko z kontrahentem", "Comment 39: który jest w nagłówku Feed sale.\'", \'Comment 40: "[[email protected]],we\\\'ve made changes in prod on Feed Sale elements in NAS.You can feel free to test it.Best regards,Grzegorz"\', "Comment 41: \'Can be closed.\']"]\nRelated Issues:\n[\'DGS-8580\']\n\n### End'} |
510 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8522\n\n### Instruction:\nA colleague receives this message after entering comarch, when he clicks ok, everything works normally. This is not the case for other users, only for RRUISCH users. Do you know what the problem could be?\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 check now", "Comment 4: how it works for this user.\'", "Comment 5: \'Everything works. Can you tell me what was the problem?\'", "Comment 6: \'The operator did not have the acc. period selected. !screenshot-1! Alternatively select a change for all operators.\'", "Comment 7: \'Ok", "Comment 8: tnx. You can close the ticket.\']"]\nRelated Issues:\n[]\n\n### End'} |
511 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8521\n\n### Instruction:\nGood morning,\r\n\r\nPlease could you take action on the next problem.\r\nIn DHC the item: 318547 is not sending tot DHP.\r\nOur production plant in Veghel is waiting for this and can\'t process while the item / recipe are not available on DHP.\r\n\r\nKind regards,\r\n\r\nGerard\n\n### Response:\n["Comment 1: [\'Hello", "Comment 2: We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-02-10-07-06-09-974.png!\'", "Comment 4: \'@Lukasz", \'Comment 5: it might not been only this item. For today\', "Comment 6: there are also no orders in DHC. I think communication between DHC and DHP is failing completely\'", "Comment 7: \'318254318547\'", "Comment 8: \'@Theo", \'Comment 9: we will check the communication. For now I can see this item is missing in DHC Service\', \'Comment 10: when I solve this issue\', "Comment 11: we will check the communication\'", "Comment 12: \'I think both issues are related\'", "Comment 13: \'Recipe in DHP now!image-2023-02-10-07-19-35-140.png!\'", \'Comment 14: "That\\\'s great. Order SO000067034 still isn\\\'t. Should we export it again from ERP?"\', "Comment 15: \'Let me check the order\'", "Comment 16: \'I see the order now", "Comment 17: thank you very much. What happened?\'", "Comment 18: \'Regarding orderSO000067034", \'Comment 19: Main Business Partner and Payer have incorrect address\', \'Comment 20: they have address of Target Business Partner. Please\', "Comment 21: ask order department to correct and resend prder.Regards\'", "Comment 22: \'And for the recipe?\'", "Comment 23: \'I know what happened. Apart from addresses", \'Comment 24: the order was for requested item:318547. It did not drop to DHC service. I have resynces this item\', "Comment 25: so the recipe appeared and order appeared as well. There was one more item to resync -318254. I have resynced it\'", "Comment 26: \'Ok", "Comment 27: clear. How can we prevent such issues? \'", "Comment 28: \'The issue is fixed in versio 3.0.60 of DHC\'", \'Comment 29: "I\\\'m trying to monitor items\', \'Comment 30: for example in RCADGS-8487 I have pushed 10 items yesterday."\', "Comment 31: \'Theo,Please", "Comment 32: let me know if we can close this task.Regards\'", "Comment 33: \'Thanks! Glad to hear that it is fixed in future version of DHC. I hope", \'Comment 34: untill we have installed that version\', "Comment 35: it doesnt occur too much.Many thanks for your help Aleksandra and Lukasz\'", \'Comment 36: "You\\\'re welcome\', \'Comment 37: Theo. Have a nice day!"]\']\nRelated Issues:\n[]\n\n### End'} |
512 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8520\n\n### Instruction:\n\xa0From Round\xa0808104/0041/0002 to round should be moved feed sale lines (sent in email).\r\n\r\n\xa0\r\n\r\nOn this Purchase invoices and also on linked SI and SR should be updated round number from\xa0808104/0041/0002 to\xa000024J/0276/0001\r\n\r\nPI-RLM/2023/0042\r\n\r\nPI-RLM/2023/0067\r\n\r\nPI-RLM/2023/0066\r\n\r\nPI-RLM/2023/0059\r\n\r\nPI-RLM/2023/0058\r\n\r\nPI-RLM/2023/0081\r\n\r\nPI-RLM/2023/0079\xa0\r\n\r\n\xa0\n\n### Response:\n["Comment 1: [\'These three lines have been moved to this feed saleFE-M/0041 (round808104/0041/0001) - from FE-M/0380 and from FE-M/0447.!image-2023-02-09-15-26-49-816.png|id=x_imageSelected0!\'", \'Comment 2: "We\\\'ve updated data on: * Purchase Invoice -\\\'Supplier\\\'\', "Comment 3: \'Full number\' * Sales Invoice -\'Reference\'", "Comment 4: \'Full number\' * Slaughtery report - \'Farmer\',\'Full number\'for these PI\'s", \'Comment 5: linked SI\\\'s and SR\\\'s:|PI-RLM/2023/0042|SI-RLM/2023/0042|SR/2968||PI-RLM/2023/0059|SI-RLM/2023/0057|SR/2950||PI-RLM/2023/0067|SI-RLM/2023/0065|SR/2967||PI-RLM/2023/0081|SI-RLM/2023/0078|SR/2988||PI-RLM/2023/0058|SI-RLM/2023/0056|SR/2949||PI-RLM/2023/0066|SI-RLM/2023/0064|SR/2966||PI-RLM/2023/0079|SI-RLM/2023/0076|SR/2987|"]\']\nRelated Issues:\n[]\n\n### End'} |
513 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8519\n\n### Instruction:\nno orders are not syncing to DHC \r\n\r\nthe list we have thus far \r\nKB:\r\nSO-388/23/KBW\r\nSO-355/23/KBW\r\nSO-347/23/KBW\r\nSO-410/23/KBW\r\nSO-411/23/KBW\r\nSO-151/23/KBG\r\nSO-148/23/KBG\r\nSO-378/23/KBW\r\nSO-421/23/KBW\r\n\n\n### Response:\n["Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", "Comment 2: \'KD:so-98/23/kdwso--314/23/klrso-315/23/klrso-317/23/klr so-197/23/kdwso-245/23/klrso-316/23/dkdUR: \\\\t76/23/UMR270/23/UMR285/23/UMR363/23/UMR392/23/UMR474/23/UMR475/23/UMR\'", \'Comment 3: "aktualnie ejst tylko 355select top 100 DocumentNumber,*from orders where DocumentNumber in (\\\'SO-388/23/KBW\\\',\\\'SO-355/23/KBW\\\',\\\'SO-347/23/KBW\\\',\\\'SO-410/23/KBW\\\',\\\'SO-411/23/KBW\\\',\\\'SO-151/23/KBG\\\',\\\'SO-148/23/KBG\\\',\\\'SO-378/23/KBW\\\',\\\'SO-421/23/KBW\\\')"\', "Comment 4: \'Order NumberSO-204/23/MOMSO-204/23/MOMSO-205/23/MOMSO-205/23/MOMSO-242/23/MOMSO-242/23/MOMSO-242/23/MOMSO-89/23/MMWSO-89/23/MMWSO-89/23/MMWSO-89/23/MMWSO-89/23/MMWSO-92/23/MMWSO-92/23/MMWSO-92/23/MMWSO-92/23/MMWSO-92/23/MMWSO-92/23/MMWSO-254/23/MOMSO-255/23/MOM\'", "Comment 5: \'Próbowalam przeslac 388 ale bez skutku", "Comment 6: restrty nie pomagaja w logach nic nie widze ...\'", "Comment 7: \'tu wyglada jakby ordery prestaly isc o 10.25 !image-2023-02-09-14-09-50-856.png!\'", "Comment 8: \'Hello", "Comment 9: please note that some of the branches are at a standstill\'", \'Comment 10: "Check I can see that all of this documents are in dhc :\\\'SO-388/23/KBW\\\',\\\'SO-355/23/KBW\\\',\\\'SO-347/23/KBW\\\',\\\'SO-410/23/KBW\\\',\\\'SO-411/23/KBW\\\',\\\'SO-151/23/KBG\\\',\\\'SO-148/23/KBG\\\',\\\'SO-378/23/KBW\\\',\\\'SO-421/23/KBW\\\'"\', \'Comment 11: "po kosnulatacje z Przemkiem puscilam taki update jeszcze ,update cdn.ZamNag set zan_stan=zan_stan where (zan_zamrok=2023 and zan_zamseria in ( \\\'mmw\\\'\', "Comment 12: \'mom\') and zan_zamnumer in (204", \'Comment 13: 242\', \'Comment 14: 89 \', \'Comment 15: 92 \', \'Comment 16: 254\', \'Comment 17: 255)) or ( zan_zamrok=2023 and zan_zamseria in (\\\'kdw\\\',\\\'klr\\\') and (zan_zamnumer =197 or zan_zamnumer in (245,315,317,314,316,245))) or (zan_zamrok=2023 and zan_zamseria in ( \\\'umr\\\') and zan_zamnumer in (76,270,285,363,392,474,475 ))jak napisza ze czegos im barlk trzeba wymusic synchre w erp xl"\', "Comment 18: \'From what I have verified also other mentioned order numbers are in DHC.\'", "Comment 19: \'DH_Sys który blokował tabele", "Comment 20: Przemek poprawił triggery i jakos poszlo\'", "Comment 21: \'May we close the task?\'", "Comment 22: \'Hello", "Comment 23: yes you may thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
514 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8518\n\n### Instruction:\nI have changed the PO link on the VT listed in the attachment. Before that the VTs were NOT sent to ERP, because wrongly linked POs did not have sufficient quantity. I have changed the VT-PO link to correct PO, but I cannot sent the VT\'s to ERP, because there is validation in DHC that once VT was sent, it cannot be resent again, even if ERP rejected it. \r\nThat is why I ask for removing the message, and resending those VT again. If resending is a problem, pls remove the message, then I can resend them from DHC interface. (I hope it will work). PLs call me if you have any questions. \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,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 could you please let us know where do you exactly chnaged this linking? What table / db or under application?!image-2023-02-09-12-40-31-949.png!\'", "Comment 5: \'I changed it using the standard DHC functionality", "Comment 6: in the interface !image-1!\'", "Comment 7: \'nothing from tables \'", "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: \'it is blocking the process since december", \'Comment 10: when I lower the priority\', "Comment 11: when it is resolved then? \'", "Comment 12: \'Mappings has been removed.\'", "Comment 13: \'According to service agreement", \'Comment 14: P1 - are incident having a critical or blocking impact on business process which means De Heus cannot produce or deliver. If the issue exists from December\', \'Comment 15: 2022\', "Comment 16: it is not blocking.\'", "Comment 17: \'Ok", \'Comment 18: removed\', "Comment 19: that means I can resend the tickets again? \'", "Comment 20: \'Yes", \'Comment 21: You can try to resend them.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.According to service agreement\', \'Comment 22: P1 - are incident having a critical or blocking impact on business process which means De Heus cannot produce or deliver. If the issue exists from December\', \'Comment 23: 2022\', "Comment 24: it is not blocking.\'", "Comment 25: \'Hi", \'Comment 26: I have sent the VTs\', \'Comment 27: and some were recived by ERP properly\', \'Comment 28: but some not\', "Comment 29: I am getting the following message in DHC: Evolution.DHCERPService.IdentityMapping.IdentityNotMappedException: Key of entity OrderElementMappingEntity was not mapped. Key value Id: 669944d2-2e07-4551-8c4d-2f178bc037c8 at Evolution.DHCERPService.IdentityMapping.IdentityMappingRepository`1.GetERPKey(GuidKey key) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.IdentityMapping\\\\\\\\IdentityMappingRepository.cs:line 42 at Evolution.DHCERPService.WoWWebServiceClient.Services.IntakeServiceClient.SendIntake(VehicleTicket vehicleTicket) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.WoWWebServiceClient\\\\\\\\Services\\\\\\\\IntakeServiceClient.cs:line 69\'", "Comment 30: \'also VT 419/12/2022 cannot be sent", \'Comment 31: from one reason or another the button "generate ERP document" is inactive \\\'\', "Comment 32: \'List of VTs which have mentioned error message in DHC !image-2!\'", "Comment 33: \'For VT-419/12/2022 was generated POR-419/12/2022/ document in ERP system. Please check if. Error message You have send is related to this document.Please check.\'", "Comment 34: \'Please check document 426/12/2022/. It look like it is use in ERP system.Rest of documents has been synchronised. Please verify.\'", "Comment 35: \'Please", "Comment 36: let me know do you expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 37: \'not yet", "Comment 38: we must verify well what had been done \'", "Comment 39: \'Waiting for your feedback then.Additionally", \'Comment 40: according to service agreement\', \'Comment 41: P1 - are incident having a critical or blocking impact on business process which means De Heus cannot produce or deliver. If the issue exists from December\', \'Comment 42: 2022\', \'Comment 43: it is not blocking and verification is time consuming\', \'Comment 44: I insist on P2 priority.In P1 we are focusing on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue\', \'Comment 45: we may raise RootCause Analysis (RCA)task for you.Please\', "Comment 46: let us knowhow you wish us to proceed.Regards\'", "Comment 47: \'no permission for RCA\'", "Comment 48: \'We will not create RCa then", "Comment 49: did you verify426/12/2022 and rest of the documents?\'", "Comment 50: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 51: please raise another task.Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
515 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8517\n\n### Instruction:\nOn contract farmer and contracy slaughtery (linked to contract farmer) method in table \'Market indices prices\' (\'Pricing meat\' tab) should be updated on value = \'week\' for customers from list below.\r\n\r\n!image-2023-02-09-12-26-31-160.png!\r\n |200264|\r\n|200257|\r\n|200237|\r\n|200243|\r\n|200239|\r\n|200248|\r\n|200236|\r\n|200268|\r\n|200262|\r\n|200222|\r\n|200223|\r\n|200245|\r\n|200212|\r\n|200254|\r\n|200226|\r\n|200220|\r\n|200302|\r\n|200303|\r\n|200259|\r\n|200244|\r\n|200209|\r\n|200266|\r\n|200211|\r\n|200260|\r\n|200210|\r\n|102086|\r\n|200253|\r\n|2220|\r\n|200364|\r\n|200246|\r\n|200247|\r\n|200238|\r\n|122041|\r\n|200214|\r\n|200215|\r\n|200249|\r\n|200206|\r\n|200233|\r\n|200205|\r\n|101942|\r\n|187|\r\n|200305|\r\n|200256|\r\n|200258|\r\n|200228|\r\n|201|\r\n|200232|\r\n|200229|\r\n|200263|\r\n|200251|\r\n|200207|\r\n|200219|\r\n|101898|\r\n|200203|\r\n|200217|\r\n|200304|\r\n|200235|\r\n|101519|\r\n|101936|\r\n|200240|\r\n|200265|\r\n|200261|\r\n|200267|\r\n|200301|\r\n|200218|\r\n|200213|\r\n|200250|\r\n|200221|\r\n|5844|\r\n|200208|\r\n|125798|\r\n|B100061|\r\n|B100078|\r\n|B100056|\r\n|B100057|\r\n|B100049|\r\n|B100054|\r\n|B100059|\r\n|B100052|\r\n|B100079|\r\n|B100053|\r\n|B100058|\r\n|B005580|\r\n|B100075|\r\n|B100055|\r\n|B100051|\r\n|B100077|\r\n|B100080|\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: ["Lista Contract Slaughtery\', \'Comment 2: które też powinny być zaktualizowane o week w kolumnie \\\'Method\\\'[^Map2.xlsx]"\', "Comment 3: \'[[email protected]] wszystkie rekordy wraz z tymi w excel zostały zaktualizowane na bazie produkcyjnej :).\'", \'Comment 4: "Hi [[email protected]],all lines have been updated on production environment. You can feel free to test it.I\\\'m waiting for your response to close the task.Best regards,Grzegorz Materla"\', "Comment 5: \'[[email protected]]could you confim?\'", \'Comment 6: "{color:black}Hello{color} {color:black}{color} {color:black}All contracts are ok{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}!image001!{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}_ | | !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:32 *Aan:* Huibers\', \'Comment 7: Koen <[email protected]> *Onderwerp:* DGS-8517 Update indices prices method = \\\'week\\\' for Contract Farmer and Contract Slaughtery for many customers "]\']\nRelated Issues:\n[]\n\n### End'} |
516 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8516\n\n### Instruction:\nCześć,\r\n\r\nProszę o jak najszybsze zweryfikowanie problemu przeniesienia LP z Optimy do CDN-a; migracja pierwszy raz po zmianie struktury.\r\n\r\n \r\n\r\nProszę o przekierowanie zadania do Pani Monik Biśty\r\n\n\n### Response:\n["Comment 1: [\'!image![^Przechwytywanie komunikatów.log] _(603 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'[^DGS-8516.docx]\'", "Comment 4: \'Odpowiedź w załączniku[^DGS-8516.docx]\'", "Comment 5: \'Została dodana na próbe lista E-UM3/2023/06/*/E Niestety Iwona Sadowska nie może jej pobrać z Optimy \'", "Comment 6: \'Lista główna za styczeń została przeniesiona.Ze względu na zmiany wydziałów z dniem 01.02.2023 system wymagał ustawienia daty importu na 31.01.2023", \'Comment 7: dodatkowo prze-edytowano poprzednie wydziały pracowników (obowiązujące w ramach listy za styczeń) Na przyszłość proszę zwrócić uwagę na nazwy działów\', \'Comment 8: nie jestem w stanie sprawdzić jak to będzie wpływać na dalsze działanie systemu ale na zapisach historycznych osób dla których wydział był zmieniany brakuje informacji co zmieniano i wynika to właśnie z faktu iż nazwa wydziału jest taka sama ale w innej gałęzi. Może to powodować nieprawidłowości.Jeśli chodzi o testową listę płac na późniejszy okres proszę o weryfikację czy lista została zamknięta na czas przeniesienia\', \'Comment 9: ponieważ XL jej nie widzi (lista w buforze nie może być przeniesiona dl XL)\', "Comment 10: po zamknięciu listy proszę o przekazanie informacji do księgowości w celu weryfikacji importu.\'", "Comment 11: \'Odp od Iwony Sadowskiej : Jeśli chodzi o listę testową za okres luty została poprawnie zaksięgowana.Problem jest tylko z listą styczniową – nie została zaksięgowana jak również wszystkie koszty weszły wg „starej” struktury", "Comment 12: przed zmianą.\'", "Comment 13: \'Proszę o wskazanie lokalizacji gdzie zapisywane są logi i errory z działania automatu do księgowania lub o ich przesłanie z piątku", "Comment 14: godziny wieczorne\'", "Comment 15: \'[^AutoAccounting v.2.0.7z] _(25 kB)_\'", "Comment 16: \'Będę wdzięczna za weryfikację czy w log i error z soboty i niedzieli jest jakiś zapis dot. listy płac:E-UM/2023/01/* GIDTyp => 2976 GIDFirma => 246785 GIDNumer =>3226lub o przesłanie tych log/error!image-2023-02-13-14-12-48-134.png!\'", "Comment 17: \'2023-02-12 00:34:21.9799|ERROR|AutoAccounting.Posting| [6536] Nie udało sie zaksięgować dokumentu E-UM/2023/01/* BŁAD XLKsiegujDokument() => 120 | Wystąpił wewnętrzny błąd modyfikacji danych.|Zaistniała sytuacja nieprzewidziana przez program.||Przyczyna:|Szczegóły operacji:Operacja zmiany obiektu o identyfikatorze .Identyfikator operacji: .Błąd: ", \'Comment 18: .||Remedium:|Spróbuj wykonać operację ponownie\', \'Comment 19: jeżeli problem nie będzie ustępował\', \'Comment 20: skontaktuj się z Administratorem systemu.2023-02-12 22:37:19.6975|TRACE|AutoAccounting.Posting| [4104] START AutoAcounting - Posting2023-02-12 22:37:19.6975|TRACE|AutoAccounting.Log| [4104] Pobieranie dodatkowych procedur do wykonania2023-02-12 22:37:19.7131|TRACE|AutoAccounting.Log| [4104] Ilość dodatkowych procedur do wykonania => 02023-02-12 22:37:19.7131|TRACE|AutoAccounting.Posting| [4104] Rozpoczęcie pobierania dokumentów do zaksięgowania2023-02-12 22:37:19.7131|TRACE|AutoAccounting.Posting| [4104] Pobrano dokumenty do zaksięgowania w ilości => 12023-02-12 22:37:19.7131|TRACE|AutoAccounting.Posting| [4104] Księgowanie dokumentu Identyfikator => E-UM/2023/01/* GIDTyp => 2976 GIDFirma => 246785 GIDNumer =>3226 GIDLp =>02023-02-12 22:37:19.7131|TRACE|AutoAccounting.Log| [4104] Pobieranie dodatkowych procedur do wykonania2023-02-12 22:37:19.7288|TRACE|AutoAccounting.Log| [4104] Ilość dodatkowych procedur do wykonania => 22023-02-12 22:37:19.7288|TRACE|AutoAccounting.Log| [4104] InputString przed zamianą => exec [CDN].[KR_PoprawOpisListyPlacKosztyNEW] ^DNGIDTyp^\', \'Comment 21: ^DNGIDNumer^2023-02-12 22:37:19.7288|TRACE|AutoAccounting.Log| [4104] InputString po zmianie => exec [CDN].[KR_PoprawOpisListyPlacKosztyNEW] 2976\', \'Comment 22: 32262023-02-12 22:37:19.7443|TRACE|AutoAccounting.Log| [4104] Pomyślnie wykonano procedurę SQL => exec [CDN].[KR_PoprawOpisListyPlacKosztyNEW] ^DNGIDTyp^\', \'Comment 23: ^DNGIDNumer^2023-02-12 22:37:19.7443|TRACE|AutoAccounting.Log| [4104] InputString przed zamianą => exec [CDN].[KR_PoprawOpisListyPlacNEW] ^DNGIDTyp^\', \'Comment 24: ^DNGIDNumer^2023-02-12 22:37:19.7443|TRACE|AutoAccounting.Log| [4104] InputString po zmianie => exec [CDN].[KR_PoprawOpisListyPlacNEW] 2976\', \'Comment 25: 32262023-02-12 22:37:19.7443|TRACE|AutoAccounting.Log| [4104] Pomyślnie wykonano procedurę SQL => exec [CDN].[KR_PoprawOpisListyPlacNEW] ^DNGIDTyp^\', "Comment 26: ^DNGIDNumer^\'", "Comment 27: \'Lista została zaksięgowana", "Comment 28: proszę o weryfikację.\'", \'Comment 29: "It\\\'s Ok. Task to close"]\']\nRelated Issues:\n[]\n\n### End'} |
517 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8515\n\n### Instruction:\n I am trying to look for December 2022 closing balance for 2022, but I cant find the Balances in 2023 for January as a beginning, I should add those balances as a beginning in 2023 or the system should take it as a balance what is the option to do this? looking your responses. the year is not closed still some thing to correct and waiting until it will be Audited or any changes.\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,To add opening balance in new period (2023)", \'Comment 3: please open Accounting module\', \'Comment 4: then choose period:!image-2023-02-10-13-08-13-424.png!!image-2023-02-10-13-08-41-565.png!Then you need to go to Accounting >> Tools tab >> Transfer Opening Balance!image-2023-02-10-13-05-40-981.png!Then decide whether you want to transfer all accounts the All\', \'Comment 5: if Selected\', \'Comment 6: please choose Selected and then + button to select desired account!image-2023-02-10-13-07-27-235.png!Please\', "Comment 7: let us know if this is fine for you.Regards\'", "Comment 8: \'Hi,Is there anything else we can do for you?Regards\'", "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: \'I tried to Move for 2022 Ending Balance for 2023 Beginning Balance but not working properly it will take 2022 Beginning Balance for 2023 Beginning Balance. can you help me on this\'", "Comment 12: \'Dear Sir", \'Comment 13: not yet resolved for this Issue\', \'Comment 14: I tried to Move opening Balance for 2023 from 2022 Ending and closing balance\', \'Comment 15: but not working properly it will take 2022 Opening Balance as 2023 Opening balance. Can you look it again for you assist. Thanks. {color:#1F3864}With best Regards,{color} {color:#1F3864}{color} {color:#1F3864}Getish Lemma\', \'Comment 16: Finance Manager{color} {color:#1F3864}{color} {color:#1F3864}Alema Koudijs Feed PLC{color} {color:#1F3864}(+251) 912 144 728{color}{color:#2E74B5}{color} !image001!{color:#2E74B5}{color} *From:* Aleksandra Przybyłek (Jira) <[email protected]> *Sent:* Friday\', \'Comment 17: February 10\', "Comment 18: 2023 3:11 PM *To:* Getish Lemma <[email protected]> *Subject:* DGS-8515 2022 closing balance !image002!!image003!!image004!!image005!\'", "Comment 19: \'Hi,The issue is not resolved for you", "Comment 20: however you did not inform us since the 10th of February.Please raise a new task for this issue as this task has been already closed and settled.Best Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
518 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8514\n\n### Instruction:\nHello,\r\n\r\nPlease assist cancel SORC-6/23/UMR.\r\n\r\nStock was collected from a customer and user had to credit them for it, user mistakenly included another product on the credit note, user created a new SORC-7/23/UMR (which is correct).\r\nStock from SORC-6/23/UMR was used.\r\n\r\nCan you please assist in cancelling SORC-6/23/UMR.\r\n\r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'document 6 /sorcTrN_GIDTyp=2009 AND TrN_GIDFirma=556290 AND TrN_GIDNumer=40775877TrN_GIDNumer=4077709select * from cdn.traelem where tre_gidnumer in (4077587,4077709)\'", "Comment 3: \'!image-2023-02-10-15-34-25-678.png!\'", "Comment 4: \'!image-2023-02-10-15-35-28-389.png!\'", "Comment 5: \'zasobyselect * from cdn.dostawy where Dst_GIDTyp=160 AND Dst_GIDNumer=825391select * from cdn.twrzasoby where twz_twrnumer=13371 and twz_magnumer=4\'", "Comment 6: \'--select * from cdn.traselem where Trs_GIDNumer=4077709select * from cdn.traelem where Tre_GIDNumer=4077709select TrS_Ilosc,* from cdn.traselem where Trs_DstNumer=825391--select * from cdn.traselem where Trs_GIDNumer=4077587--select TrS_Ilosc,* from cdn.traselem where Trs_DstNumer=798475--select TrS_Ilosc,* from cdn.traselem where Trs_DstNumer=799863select TwZ_IlSpr,* from cdn.twrzasoby where twz_dstnumer in (825391)--),798475)--,799863)select * from cdn.twrzasoby where twz_twrnumer=13371 and TwZ_IlSpr >= 0.3750 and TwZ_MagNumer=4select Dst_KsiegowaNetto/Dst_Ilosc,* from cdn.dostawy where Dst_GIDNumer in (825391,835319,839194)select Trs_DstNumer,839194,* from cdn.traselem t where Trs_DstNumer=825391 and TrS_GIDNumer in (4077651,4091295)update t set Trs_DstNumer=839194 from cdn.traselem t where Trs_DstNumer=825391 and TrS_GIDNumer in (4077651,4091295)select * from cdn.traelem where Tre_GIDNumer=4077587select TrS_Ilosc,* from cdn.traselem where Trs_DstNumer=798475 and TrS_GIDNumer>= 4077587--select TrS_Ilosc,* from cdn.traselem where Trs_DstNumer=799863 and TrS_GIDNumer>= 4077587select Dst_KsiegowaNetto/Dst_Ilosc,* from cdn.dostawy where Dst_GIDNumer in (798475,834103)select * from cdn.twrzasoby where twz_twrnumer=13371 and TwZ_IlSpr >= 0.1500 and TwZ_MagNumer=4select Trs_DstNumer,834103,* from cdn.traselem t where Trs_DstNumer=798475 and TrS_GIDNumer in (4077651)--update t set Trs_DstNumer=834103 from cdn.traselem t where Trs_DstNumer=798475 and TrS_GIDNumer in (4077651)\'", "Comment 7: \'[^sorc6.docx]\'", "Comment 8: \'Heelo", "Comment 9: we made operations on db nightly please verify.Deatils in attachment.If what we did is ok please notce that realistion this on production db will be cost more then 3 man-hours.[^sorc6.docx]\'", "Comment 10: \'Hello,Purchasing Department Approved.Please make the same changes on LIVE.\'", \'Comment 11: \\\'Good morning One of the supplies that was available for "swap" was consumed\', \'Comment 12: we need additional time for analysis - the main logic itself to cancel documents will not change.So the task may take more than 3 rbh\', "Comment 13: = additional analysis and changes on the production environment is about 2 rbh.\'", "Comment 14: \'!hand.PNG|thumbnail! !period_prod.PNG|thumbnail!\'", "Comment 15: \'In the course of retesting on a nightly DB we encountered another problem", \'Comment 16: a trading period has been closed and it is not possible to cancel documents.Is it possible to open this period\', \'Comment 17: the same situatuon would be on the prod version.Please also bear in mind that the later we have feedback\', \'Comment 18: the more analysis is necessary\', \'Comment 19: it may turn out that\', \'Comment 20: for example\', \'Comment 21: in a given warehouse completely run out of resources and in order to replace supplies and cancel SORc it will be necessary to generate transfers\', "Comment 22: etc.!hand.PNG!!image-2023-02-21-14-24-14-331.png!\'", "Comment 23: \'Hello,Period is now open.\'", "Comment 24: \'Thank you so I testes it on nightly again and then did the same on productionall 3 documentssic 191sorc 7sorc 6are cancelled now operator can make new sorc for sor-105/23/umr and then create clip docuemnt,if there will be problem the number of new sic clipped invoice", \'Comment 25: let us know\', "Comment 26: before it will be confirmed.!image-2023-02-22-15-01-07-346.png!\'", "Comment 27: \'Thank you so much.You may close this ticket\']"]\nRelated Issues:\n[]\n\n### End'} |
519 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8513\n\n### Instruction:\nDear, \r\nI don´t see label in DHP for 5445. Recipe is okay.\r\npls check 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: "brak labelek w dhc service!image-2023-02-09-10-01-26-375.png!select * from labels where DhhItemId=\\\'9608C72D-1656-4F66-A392-C39BE6558FC8\\\' and ProductionAreaId=\\\'53D059F7-7B99-4CEF-A24C-6706B2F6F6C7\\\'recipe jest"\', \'Comment 3: "023-02-09 10:00:49,439 [70] ERROR Evolution.DHCountry.Infrastructure.Commands.CommandHandlerWithLog4Net`1 [(null)] - Exception occurred when handling command Evolution.DHCountry.Dictionaries.Labels.Commands.SendLabelChangedMessageCommand of ID=\\\'da3ca5c0-f7f0-4c1b-b7c8-04a3df270154\\\'. Command data: \\\'Evolution.DHCountry.Dictionaries.Labels.Commands.SendLabelChangedMessageCommand[CommandId=\\\'da3ca5c0-f7f0-4c1b-b7c8-04a3df270154\\\'\', "Comment 4: LabelId=\'f10e986d-0394-4867-b87e-4c53ee769566\']\'.AutoMapper.AutoMapperMappingException:Mapping types:Label_58409578ECBEFFA14BC24C43BE145B28A08E64E550FF16DA798E9978C252CC51 -> List`1System.Data.Entity.DynamicProxies.Label_58409578ECBEFFA14BC24C43BE145B28A08E64E550FF16DA798E9978C252CC51 -> System.Collections.Generic.List`1[[Evolution.DHCountry.Interfaces.Labels.LabelElement", \'Comment 5: Evolution.DHCountry.Interfaces\', \'Comment 6: Version=3.0.61.0\', \'Comment 7: Culture=neutral\', \'Comment 8: PublicKeyToken=null]]Destination path:LabelChangedMessage.Elements.ElementsSource value:System.Data.Entity.DynamicProxies.Label_58409578ECBEFFA14BC24C43BE145B28A08E64E550FF16DA798E9978C252CC51 ---> System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out --- End of inner exception stack trace --- at System.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 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.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()"\', \'Comment 18: "nie wpada do tabeli export inforesselect top 10 * from LabelExportInfoes --order by senddate descwhere entityid in (\\\'F10E986D-0394-4867-B87E-4C53EE769566\\\',\\\'010A84D5-6B88-4CCE-8C78-2AB8B153D0FD\\\')"\', "Comment 19: \'labelka nie wpada do labale export infoes", \'Comment 20: nie ma erororw już recipe jest\', \'Comment 21: item jest w dhp\', "Comment 22: elementy lableki są takie same w obu bazach - country service\'", "Comment 23: \'brakowało baseitemid w dhc service na dhh itemie\'", "Comment 24: \'teraz brak commitdatelogi z dhcint=egration2023-02-09 12:11:27 (/Plant.DHC.Integration/CZDHPIISBE01/9444/13) [Error] Plant.Integration.DhcService.Infrastructure.FetchDataFromDhcTask - LabelPipelineExecutor execution errorSystem.Exception: Cannot connect to server ---> System.ServiceModel.FaultException: Internal server error\'", "Comment 25: \'Please verify it shoul be ok now :!image-2023-02-09-12-24-17-903.png!\'", "Comment 26: \'It´s okay. thx\']"]\nRelated Issues:\n[]\n\n### End'} |
520 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8512\n\n### Instruction:\nPlease set round + feed sale B001070/0161/0001 active \n\n### Response:\n["Comment 1: [\'Hello,\\\\r\\\\rRound and Feed sale are Active now.\\\\r\\\\rRegards\']"]\nRelated Issues:\n[]\n\n### End'} |
521 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8511\n\n### Instruction:\nProszę o pomoc przy zamknięciu vt\r\nWaga konicowa do vt 1909 -17,340\r\n\r\nKomunikat czynności sąwykonywane prawidłowo. \n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'The weight of unloading is 21,440 t now and there is no actual weight registered now. Please", "Comment 4: advise!image-2023-02-09-07-28-14-364.png|width=1469,height=286!\'", "Comment 5: \'plz close the task \'", "Comment 6: \'dla wyjaśnienia bo temat nie został rozwiązany: problemem nie jest brak wagi", \'Comment 7: wagi nie ma bo nie mogli zważyć samochodu\', \'Comment 8: podczas zapisywania VT waga była\', "Comment 9: widać to na screenie zgłoszeniowym. Problemem jest ilość zrealizowana na WMO i tu pytanie co system zrobił!image-2!!image-3!!image-4!!image-5!\'", "Comment 10: \'została kwestia anulowania ZPM !screenshot-1! \'", "Comment 11: \'Marcin Block wyjaśni na sesji z DH.\']"]\nRelated Issues:\n[]\n\n### End'} |
522 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8510\n\n### Instruction:\nProduction recipes are not appearing in DHP Helmond.\r\n\r\nEg. order SO000066143 item 303315.\r\n\r\nRecipes in DHC are created but don\'t appear in DHP.\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: "Can you specify what is lacking. Both order SO000066143 and recipe for303315 are available in Helmond\\\'s DHP!image-2023-02-08-17-05-27-839.png!!image-2023-02-08-17-05-41-960.png!"\', "Comment 3: \'In DHC subversions of the recipe are created (without checking 11 and 12).Those are not found in DHP.... so the plant is missing the added special or medicine.\'", "Comment 4: \'Any news?\'", "Comment 5: \'Should be fixed", "Comment 6: please check.\'", "Comment 7: \'Hi Gedeon,it seems to be working fine now. Thanks.What was the problem/solution?Regards,Rob.\'", "Comment 8: \'Hi Rob,Integration between DHC and DHP suspended. Can we close this task?Regards\'", "Comment 9: \'Hi Aleksandra,what caused this? Can this be avoided to happen? Can we fix it ourselves next time maybe?Regards\'", "Comment 10: \'I think we should treat it as incidental case. We will observe if the issue re-occurs.Regards\'", "Comment 11: \'This ticket can be closed.\']"]\nRelated Issues:\n[]\n\n### End'} |
523 | {'prompt': "Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8509\n\n### Instruction:\nMove of DHP and DHC databases and applications to the prod server\n\n### Response:\n['Comment 1: []']\nRelated Issues:\n[]\n\n### End"} |
524 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8508\n\n### Instruction:\nHi,\r\nIn our plant in Andel, we have received 952 bags of product 087059 (bags a 25 kg), but we cannot finalize this intake due to a missing barcode prefix.\r\nCan you please check? \r\n\n\n### Response:\n["Comment 1: [\'!20230208_145716.jpg|thumbnail!\'", "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-09-11-36-39-917.png!\'", "Comment 4: \'!image-2023-02-09-11-37-14-682.png!\'", "Comment 5: \'Hi,Configuration has been set up:!image-2023-02-09-11-44-08-098.png!Regards\'", "Comment 6: \'Na barcode prefix kliknąć edit i dodać prefix!image-2023-02-09-11-45-01-613.png!\'", "Comment 7: \'Hi Aleksandra,Dziekuje bardzo. A question? Does dit count for only this product? \'", "Comment 8: \'It works for all products of Andel Mest now :)\'", "Comment 9: \'Thanks Aleksandra! You can close the task\'", "Comment 10: \'Thank you :)\']"]\nRelated Issues:\n[]\n\n### End'} |
525 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8507\n\n### Instruction:\nWe need to have notification service configurated so that we will be able to use the email address feature in DHC\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Dzięki Przemku :)\'", "Comment 3: \'Dear [[email protected]]", \'Comment 4: to configure notification service we will need some email account to send notification\', \'Comment 5: please provide us information about email address that we can use\', \'Comment 6: password\', \'Comment 7: smtp server address\', "Comment 8: port to communicate with smtp and other necessary information like type of security protocol.\'", "Comment 9: \'Okay I will get back to you with those details soon Kind regards | !image001!!image004! | *{color:#2E74B5} *Feyi Seyram Solomon*{color}*{color:#2E74B5} ServiceDesk Engineer{color} *{color:#2E74B5} *Koudijs Ghana Limited*{color}*{color:#2E74B5} Phone: +233 30 7000 580 : Mobile: +233 59 6914 778{color}{color:#2E74B5}{color} *{color:#2E74B5} *GK-0173-1282", \'Comment 10: Tema Free Zone Enclave*{color}* *{color:#2E74B5} *Tema\', \'Comment 11: Greater Accra\', \'Comment 12: COD TD 200 Ghana*{color}* *{color:#2E74B5} **{color}*{color:#2E74B5} This e-mail message and its attachments are subject to the disclaimer published at the website of{color} [{color:#0563C1}Koudijs Animal Nutrition{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.koudijs.com%2Fdisclaimer&data=05%7C01%7CSFeyi%40koudijs.com.gh%7C1cdd4c26b4484d6270e708daf877ef8b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638095491246060747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Sda%2Fs8RH6LVyAD6b9dCkcyZFILd6rVJqdsWh%2B65H9QE%3D&reserved=0]{color:#2E74B5}{color} | *From:* Przemysław Przybyszewski (Jira) <[email protected]> *Sent:* Friday\', \'Comment 13: March 17\', \'Comment 14: 2023 10:35 AM *To:* Feyi\', "Comment 15: Solomon <[email protected]> *Subject:* DGS-8507 notification service configuration !image002!\'", "Comment 16: \'Email : [[email protected]|mailto:[email protected]] Password: St@RL1m5 Smtp : smtp.office365.com Port : 587 Security protocol : starts Will this help? | !image001!!image004! | *{color:#2E74B5} *Feyi Seyram Solomon*{color}*{color:#2E74B5} ServiceDesk Engineer{color} *{color:#2E74B5} *Koudijs Ghana Limited*{color}*{color:#2E74B5} Phone: +233 30 7000 580 : Mobile: +233 59 6914 778{color}{color:#2E74B5}{color} *{color:#2E74B5} *GK-0173-1282", \'Comment 17: Tema Free Zone Enclave*{color}* *{color:#2E74B5} *Tema\', \'Comment 18: Greater Accra\', \'Comment 19: COD TD 200 Ghana*{color}* *{color:#2E74B5} **{color}*{color:#2E74B5} This e-mail message and its attachments are subject to the disclaimer published at the website of{color} [{color:#0563C1}Koudijs Animal Nutrition{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.koudijs.com%2Fdisclaimer&data=05%7C01%7CSFeyi%40koudijs.com.gh%7C1cdd4c26b4484d6270e708daf877ef8b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638095491246060747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Sda%2Fs8RH6LVyAD6b9dCkcyZFILd6rVJqdsWh%2B65H9QE%3D&reserved=0]{color:#2E74B5}{color} | *From:* Przemysław Przybyszewski (Jira) <[email protected]> *Sent:* Friday\', \'Comment 20: March 17\', \'Comment 21: 2023 10:35 AM *To:* Feyi\', "Comment 22: Solomon <[email protected]> *Subject:* DGS-8507 notification service configuration !image002!\'", "Comment 23: \'Hi [[email protected]]", \'Comment 24: yes\', "Comment 25: it should enough.\']"]\nRelated Issues:\n[\'DGS-8504\']\n\n### End'} |
526 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8506\n\n### Instruction:\nHello, \r\n\r\nVT-1188/1 is closed, but the stock unit status has status in progress. What is going on? please solve this and let us know the cause so we can prevent this from happening\n\n### Response:\n["Comment 1: [\'!afbeelding-4!!afbeelding-6!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: " !screenshot-1! {code:java}SELECT * FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits] where AggregateId=\\\'FA380786-43F2-4804-91A1-322DB3E12B0E\\\' and EventType like \\\'%status%\\\' order by Created SELECT * FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits] where AggregateId=\\\'78387d81-af37-4c6f-8329-b73c1b23e557\\\' and EventType like \\\'%status%\\\' order by Created{code} !screenshot-2! {code:java}SELECT * FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets] where AggregateId=\\\'28C232A5-FD90-4D8A-87ED-E7008D8B6B20\\\' order by Created SELECT * FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets] where AggregateId=\\\'c3fb8632-3d2a-4ad1-b699-2f3b90e8fcfb\\\' order by Created{code} !screenshot-3! {code:java}SELECT status,* FROM [DHPlantStockBusinessLogicMain].[dbo].[VehicleTickets] where id=\\\'28c232a5-fd90-4d8a-87ed-e7008d8b6b20\\\'--or id=\\\'c3fb8632-3d2a-4ad1-b699-2f3b90e8fcfb\\\' SELECT status,*from DHPlantVCBusinessLogicMain.[dbo].[VehicleTickets] where id=\\\'28c232a5-fd90-4d8a-87ed-e7008d8b6b20\\\'--or id=\\\'c3fb8632-3d2a-4ad1-b699-2f3b90e8fcfb\\\' select top 10 * from DHPlantStockBusinessLogicMain.[dbo].[Deliveries]where [SourceDocumentId] in(\\\'28c232a5-fd90-4d8a-87ed-e7008d8b6b20\\\')--,\\\'c3fb8632-3d2a-4ad1-b699-2f3b90e8fcfb\\\') select top 10 * from DHPlantStockBusinessLogicMain.[dbo].[StockUnits]where DeliveryId in(--\\\'DF8495E1-F842-42A3-B343-4684B99CAC4C\\\',\\\'D68C07B7-029C-45B6-8F7E-F69EA6A477C7\\\'){code} !screenshot-4! "\', \'Comment 4: "{code:java}SELECT v.status,s.LogisticStatus,d.Status,v.Document,s.ItemId,i.Code,s.Id,s.QuantityOnHand,s.InitialQuantity FROM [DHPlantStockBusinessLogicMain].[dbo].[VehicleTickets] v inner join DHPlantStockBusinessLogicMain.[dbo].[Deliveries] d on v.id=d.SourceDocumentId inner join DHPlantStockBusinessLogicMain.[dbo].[StockUnits] s on s.DeliveryId=d.Id inner join DHPlantStockBusinessLogicMain.[dbo].Items i on i.id=s.ItemId --where v.Id=\\\'28c232a5-fd90-4d8a-87ed-e7008d8b6b20\\\' where v.Status=120 and LogisticStatus=2{code} !screenshot-5! "\', "Comment 5: \'Attempted to divide by zero.{code:java} at System.Decimal.DecCalc.VarDecDiv(DecCalc& d1", \'Comment 6: DecCalc& d2) at Plant.Stock.BusinessLogic.Domain.Services.CloseStockUnitsIntakeDomainService.<>c__DisplayClass3_0.<CalculateStockUnitsQuantityDifference>b__2(StockUnitQuantityDifferenceCalculationData stockUnit) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Services\\\\\\\\CloseStockUnitsIntakeDomainService.cs:line 103 at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source\', \'Comment 7: Func`2 keySelector\', \'Comment 8: Func`2 elementSelector\', \'Comment 9: IEqualityComparer`1 comparer) at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source\', \'Comment 10: Func`2 keySelector\', \'Comment 11: Func`2 elementSelector) at Plant.Stock.BusinessLogic.Domain.Services.CloseStockUnitsIntakeDomainService.CalculateStockUnitsQuantityDifference(IEnumerable`1 stockUnitsData\', \'Comment 12: Quantity absoluteDifference) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Services\\\\\\\\CloseStockUnitsIntakeDomainService.cs:line 99 at Plant.Stock.BusinessLogic.Domain.Services.CloseStockUnitsIntakeDomainService.CalculateQuantityDifference(IEnumerable`1 stockUnitsData\', \'Comment 13: Quantity finalQuantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Services\\\\\\\\CloseStockUnitsIntakeDomainService.cs:line 0 at Plant.Stock.BusinessLogic.Domain.Services.CloseStockUnitsIntakeDomainService.CalculateQuantityDifference(IEnumerable`1 stockUnits\', \'Comment 14: Quantity finalQuantity\', \'Comment 15: SourceDocument intakeSourceDocument) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Services\\\\\\\\CloseStockUnitsIntakeDomainService.cs:line 37 at Plant.Stock.BusinessLogic.Domain.Services.RegisterIntakeDomainService.CloseBulkIntake(Delivery delivery\', \'Comment 16: IEnumerable`1 stockUnits\', "Comment 17: Quantity finalQuantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Services\\\\\\\\RegisterIntakeDomainService.cs:line 235 at Plant.Stock.BusinessLogic.Application.Services.RegisterIntakeService.CloseBulkIntake(CloseBulkIntakeElementData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Services\\\\\\\\RegisterIntakeService.cs:line 277 at Plant.Stock.BusinessLogic.Application.CommandHandlers.BulkIntake.CloseBulkIntakeCommandHandler.Handle(CloseBulkIntakeCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\CommandHandlers\\\\\\\\BulkIntake\\\\\\\\CloseBulkIntakeCommandHandler.cs:line 30 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.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.Stock.BusinessLogic.Infrastructure.ContextIntegration.IntercontextCommunication.VC.VehicleTicketIntakeClosedEventHandler.Handle(VehicleTicketIntakeClosedEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\IntercontextCommunication\\\\\\\\VC\\\\\\\\VehicleTicketIntakeClosedEventHandler.cs:line 34 at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message){code}\'", \'Comment 18: "Hello\', \'Comment 19: statuses were updated by checking error messages in the stock module for VT\\\'s.And resent for events VehicleTicketIntakeClosed. !screenshot-7! "\', \'Comment 20: "Oke\', \'Comment 21: and this should\\\'t occur anymore?"\', "Comment 22: \'Hello Thomas,as for recurrence there were no new cases.\'", "Comment 23: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'} |
527 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8505\n\n### Instruction:\nVT-1627/2/2023/P nie przechodzi do CDNa\r\n\r\nByła zmiana na ZS-32/02/23/P kod GT267X00X-W00 na ZS-332/02/23/P \r\nPozostałe elementy przeszły jeden został z błędem \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-08-14-23-26-693.png!!image-2023-02-08-14-25-13-074.png!\'", "Comment 4: \'!image-2023-02-08-14-37-19-632.png!!image-2023-02-08-14-40-13-638.png!\'", "Comment 5: \'Czy jest możliwość usunięcia elementu z VT i dodania go ponownie w plancie?\'", "Comment 6: \'Niestety nie bo pozostale elementy z tego vt przeszly z dhc \'", "Comment 7: \'I have verified this issue. When you modified order element released on VT you should delete this element from VT and add new one from correct order. Right now we sugest to add this element manualy to WZ document and correct quantity in DHP through stocktaking.Please", \'Comment 8: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?Zweryfikowałem ten problem. Kiedy zmodyfikowałeś element zamówienia wydany na VT\', "Comment 9: powinieneś usunąć ten element z VT i dodać nowy z właściwego zamówienia. W tej chwili sugerujemy ręcznie dodać brakujący element do dokumentu WZ i skorygować ilość w DHP poprzez inwentaryzację.Proszę o informację czy przekazana odpowiedź jest dla Państwa wystarczająca? Czy oczekują Państwo od nas jakiś dodatkowych działań w zakresie tego zgłoszenia? Czy możemy zamknąć zgłoszenie?\'", "Comment 10: \'Na VT był usunięty ZS-32/02/23/P kod GT267X00X-W00 i dodany za niego ZS-332/02/23/.Na pierwszym screenie widać błąd przed zmianą na drugim jest juz po tej zmianie. Elementy przeszły", "Comment 11: była całą lista jak widać. ale jeden pozostał. \'", "Comment 12: \'According to previous sugestion please add this element manualy to WZ document and correct quantity in DHP through stocktaking.Zgodnie z wcześniejszą sugestią zalecamyręcznie dodać brakujący element do dokumentu WZ i skorygować ilość w DHP poprzez inwentaryzację.\'", "Comment 13: \'Close\'", "Comment 14: \'przy ponownym tego typu błędzie - poprawiamy od bazy - prośba klienta po retro. \']"]\nRelated Issues:\n[]\n\n### End'} |
528 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8504\n\n### Instruction:\nThe email address function in DHC is not working, kindly help solve.\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: \'I think it has never worked for you as you do not have notification service configured. If there is a need", "Comment 4: please raise a GDC task.Regards\'", "Comment 5: \'!image-2023-02-08-14-09-17-901.png!\'", "Comment 6: \'please close\'", "Comment 7: \'Thank you\']"]\nRelated Issues:\n[\'DGS-8507\']\n\n### End'} |
529 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8503\n\n### Instruction:\nShipping Notice L000126539 is in DHC but is not arriving in DHP Andel (factory 98). Can you please check, we have to load this truck. \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: \'I see it is in DHP now. Mihgt have been some delay \'", "Comment 3: \'!image-2023-02-08-11-51-57-742.png!\'", "Comment 4: \'Dear Theo,It is in plant now.Regards!image-2023-02-08-12-04-49-977.png!\'", "Comment 5: \'Sorry", \'Comment 6: I missed your previous comment. Yes\', \'Comment 7: possible there was a delay\', \'Comment 8: I have restarted application pools. Please\', "Comment 9: confirm if we can close this task.Regards\'", "Comment 10: \'Yes", "Comment 11: please close the task. \']"]\nRelated Issues:\n[]\n\n### End'} |
530 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8502\n\n### Instruction:\nVT 2666/2/2023/G nie chce wygenerować się z DHC do CDN.\r\nBrak komunikatu błędu, prośba o rozwiązanie problemu.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Ale ten VT ma już wygenerowane dokumenty!image-2023-02-08-13-48-13-669.png!!image-2023-02-08-13-48-13-669!\'", "Comment 3: \'Ok", \'Comment 4: dzięki do zamknięcia\', "Comment 5: wyjątkowo długo się generowały.\'", "Comment 6: \'luzik :)\']"]\nRelated Issues:\n[]\n\n### End'} |
531 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8501\n\n### Instruction:\nI would like to schedule a meeting with you to help me with an issue on NAV reporting.\r\nWhat I would like is to be able to relate a Job Order to sales made per product,\r\nCan you help with this?\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: \'Would you mind sending us more details? It would be very helpful to receive some examples of documents and information which exactly data are important for reporting (with screenshots).How do you calculate NAV? Do you have any formula or example of a report?\'", "Comment 3: \'please close\']"]\nRelated Issues:\n[]\n\n### End'} |
532 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8500\n\n### Instruction:\nSee below, VT-465 is multiplied multiple times in WO module, these elements contain no data: Please check, and fix this \n\n### Response:\n["Comment 1: [\'!afbeelding-4!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'id=91710f26-6c92-4dbc-8f4e-26ac842c39b0\'", \'Comment 4: \\\'{code:java}2023-02-08 10:01:41 (c3d5f865-3134-4017-b09b-8648dce97529/Plant.VC.BusinessLogic/DHVD01AP183/11148/237) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 5: "host": { "Value": "dhvd01ap183:82"\', \'Comment 6: "HasValue": true\', \'Comment 7: "Host": "dhvd01ap183"\', \'Comment 8: "Port": 82 }\', \'Comment 9: "path": "/api/VehicleTicket/completeDispatch"\', \'Comment 10: "queryString": []\', \'Comment 11: "requestBody": "{\\\\\\\\"id\\\\\\\\":\\\\\\\\"ae59ae71-510c-4f57-952e-3d33ef5b2d83\\\\\\\\",\\\\\\\\"date\\\\\\\\":\\\\\\\\"2023-02-08T09:01:43.915Z\\\\\\\\"}"}.Kotrak.Extensions.Validation.Abstractions.ValidationException: Validation failed: -- Missing weight on packed elements. Warehouse order has to be finished ---> Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.VehicleTicketInvalidDispatchOperationException: Validation failed: -- MissingWeightOnPackedElementsMessage at Plant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicket.SetDispatchCompleted() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicket.cs:line 744 at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.CompleteVehicleTicketDispatch(AggregateId vehicleTicketId\', \'Comment 12: DateTime date) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketService.cs:line 418 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.CompleteDispatch(CompleteVehicleTicketDispatchViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\VehicleTicketController.cs:line 618 at lambda_method240975(Closure \', \'Comment 13: Object \', \'Comment 14: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 15: ObjectMethodExecutor executor\', \'Comment 16: Object controller\', \'Comment 17: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 18: Scope& scope\', \'Comment 19: Object& state\', \'Comment 20: 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 21: Scope& scope\', \'Comment 22: Object& state\', \'Comment 23: 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 24: Task lastTask\', \'Comment 25: State next\', \'Comment 26: Scope scope\', \'Comment 27: Object state\', \'Comment 28: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 29: Task task\', \'Comment 30: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 31: Task task\', \'Comment 32: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 33: Task requestTask\', \'Comment 34: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', "Comment 35: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext) --- End of inner exception stack trace ---{code}\'", "Comment 36: \'!image-2023-02-08-10-57-52-799.png!\'", "Comment 37: \'!image-2023-02-08-11-13-20-751.png!\'", "Comment 38: \'!image-2023-02-08-11-14-37-091.png!\'", "Comment 39: \'!image-2023-02-08-11-31-59-758.png!\'", "Comment 40: \'What order number should be linked to this VT?\'", "Comment 41: \'here you see all order number that should be related to the VT. But somehow system only generates a few", "Comment 42: when one is fullfilled others are created with empty data!afbeelding-6!\'", "Comment 43: \'Dear Thomas,We have resend missing order that caused the issue and closed all empty WO (PD)Please", "Comment 44: let us know if this is fine for you.Regards\'", "Comment 45: \'Thanks! ticket can be closed\'", "Comment 46: \'Thank you\'", "Comment 47: \'[[DHP] VT is duplicated multiple time after fulfilling first order|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%5d%20VT%20is%20duplicated%20multiple%20time%20after%20fulfilling%20first§ion-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{42941D5F-5106-42D9-A367-A9B57DA0EFB6}&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%5D%20VT%20is%20duplicated%20multiple%20time%20after%20fulfilling%20first%7C42941D5F-5106-42D9-A367-A9B57DA0EFB6%2F%29])\']"]\nRelated Issues:\n[]\n\n### End'} |
533 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8499\n\n### Instruction:\nWhen there is a SILO SHOT on a round, this is under expenses and you can see it on the feed sale (this is good). However, when you generate the FS printout, for this line (SILO SHOT, under \'diverse kosten\') the document nr. is empty, and the real document nr. (SIB...) is shown under description. We would like to see \'DE HEUS VOEDERS B.V\' as \'referentie\' (= reference) just like the feed lines, the invoice nr. under \'document nr.\', and the description \'SILO SHOT\' under \'omschrijving\' (description) if possible (it\'s in line with the rest then). This example is on FS-B/0486 (ID 95412).\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 [[email protected]]", "Comment 4: we changed the data shown on the printout at MasBE now everything should match the information you provided.!image-2023-02-08-13-08-06-104.png!\'", \'Comment 5: "Hello Tomasz,Everything seems fine now\', \'Comment 6: just that the customer\\\'s name is shown under reference. Can that be DE HEUS VOEDERS B.V just as on the feed segment?"\', \'Comment 7: "My apologies\', "Comment 8: I misread. It\'s fine now", \'Comment 9: thank you!"]\']\nRelated Issues:\n[]\n\n### End'} |
534 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8498\n\n### Instruction:\nHi, \r\n\r\nEven in same customer some of Sale Invoice able to post. Some are not. And we didn\'t get any error message for unposted Sale Invoice. Kindly reference attached for more details.\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: \\\'You can not post this becouse there is no "Fixed delivery value" parameter set on document that create delivery/resource used on that SI dokument.!image-2023-02-07-18-05-11-375.png!If this not set then delivery do not have set "Cost has been fixed" parameter.!image-2023-02-07-18-06-11-343.png!And accounting tab is disable on WZ / (C)FS document\', \'Comment 4: as well as "Cost of goods sold has been fixed" parameter is turned off.!image-2023-02-07-18-08-57-958.png!!image-2023-02-07-18-09-13-145.png!To turn this parameter On on all documents You will have to finddocument that create this delivery and check "Fixed delivery value" parameter!image-2023-02-07-18-11-44-591.png!!image-2023-02-07-18-11-56-821.png!That will check this parameter on all documents that use this delivery/resource unless there will be other deliveries that do not have this parameter checked.Please\', "Comment 5: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 6: \'Please", "Comment 7: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 8: \'Hi", "Comment 9: we are clear. Thank you. You can proceed to close ticket. Sorry for late response.\']"]\nRelated Issues:\n[]\n\n### End'} |
535 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8497\n\n### Instruction:\nVT-402/1/2023/vp with error message (SDNL-38749)\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: \'!image-2023-02-08-09-11-54-654.png!\'", "Comment 4: \'!image-2023-02-08-09-25-57-896.png!!image-2023-02-08-09-24-51-092.png!A w bazie:!image-2023-02-08-09-27-37-641.png!\'", "Comment 5: \'Itemy w DHC", "Comment 6: żaden z nich nie jest archive!image-2023-02-08-09-38-41-888.png!\'", "Comment 7: \'Hi,Indeed", \'Comment 8: under the database I can see on order element item with code 00921 and name that is now assigned to code 00922. Probably the code was mistakenly assigned in ERP\', \'Comment 9: SO has been made and sent do DHC\', \'Comment 10: and then Item was corrected in ERP. But it does not correct in DHC. To sollve this issue\', "Comment 11: you should create new Sales Order and clip it with VT.Regards!image-2023-02-08-10-11-00-145.png!\'", \'Comment 12: "{code:java}SELECT * FROM [Evolution_DHCountry].[dbo].[Orders] where DocumentNumber = \\\'SO-188/01/2023/V\\\' SELECT * FROM [Evolution_DHCountry].[dbo].[OrderElements] where orderid = \\\'7B1AB58E-A2AC-4114-ABED-BAB516D175C9\\\' --SELECT * --FROM [Evolution_DHCountry].[dbo].[VehicleTickets] where DocumentNumber = \\\'402/1/2023/VP\\\' -- SELECT ItemId\', "Comment 13: * --FROM [Evolution_DHCountry].[dbo].[VehicleTicketElements] where VehicleTicketId = \'67233B7F-975A-4C15-9D8F-42E6FD6C1C33\' SELECT * FROM [Evolution_DHCountry].[dbo].[Items] where id in ( \'0986B80F-9F36-4ACD-ADA9-4745BC717D18\',\'0986B80F-9F36-4ACD-ADA9-4745BC717D18\') or code in (\'00921\'", \'Comment 14: \\\'00922\\\'){code}"\', "Comment 15: \'Hello,Is there anything else we can do for you due to requested VT?Regards\'", "Comment 16: \'Hello,Is there anything else we can do for you due to requested VT?Regards\'", "Comment 17: \'Hi,It has been resolved under*DGS-8645.*Please", "Comment 18: let us know if we can close both tasks.Regards\'", "Comment 19: \'Ticket can be closed.!image-1!\'", "Comment 20: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
536 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8496\n\n### Instruction:\nHello,\r\n\r\nA scanner incident is reported by the premix factory, I attached a video of the incident. \r\n\r\nWhen a warehouse employee scans a pallet\r\nlabel, for which no WMO is available, it can happen the employee scans the\r\nlabel a second time because he gets no response. When doing so, the DHP mobile application runs in an error and only solution is to restart. \r\n\r\nCan you please try to reproduce this and supply a fix?\r\n\r\n\r\n\n\n### Response:\n["Comment 1: [\'[^ED81CB6B.mp4] _(28,05 MB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hi,I need few more inforamtion. Does the inciden occur only for one device or multiple devices. Are the scanners restarted often? Did user / users tried to logout and login? Clear cache?Regards\'", "Comment 4: \'[[email protected]]prośba o przygotowanie środowiska do testów dla Oli Masternak", \'Comment 5: Maciej na Stand Up powiedział\', "Comment 6: żeby tak zrobić :)\'", "Comment 7: \'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 8: \'Thanks", "Comment 9: incident occurs for all devices. \'", "Comment 10: \'any update?\'", "Comment 11: \'Dear Thomas,The issue has been still investigated by dev team. We are working on it.Regards\'", "Comment 12: \'Mobilny: ^2.7.1911.16.mp4Baza: DHP_NL_PROD1. Otwieram task listę2. Skanuję kod niepowiązany z WMO(/) Pojawia się komunikat o braku WMO", \'Comment 13: który jest powiązany z tym barcodem3. Skanuję kod jeszcze raz (nie zamykam poprzedniego komunikatu)(x) Pojawia się błąd [^2.7.1911.16.mp4] {code:java}DHPlantMobile.exe ArgumentException Value does not fall within the expected range. at Microsoft.AGL.Common.MISC.HandleAr(PAL_ERROR ar) at System.Windows.Forms.Form.ShowDialog() at BeeMobile.MessageBox.MessageBoxModal.ShowDialog() at BeeMobile.MessageBox.MessageBoxModal.#=qeLqESOQJcNxgfwzrjtbA8Q==(Control #=qrm2DquzWZy2V02erddaodw==\', \'Comment 14: String #=q4ortAnrWpqoWcdr829dRTQ==\', \'Comment 15: String #=q5RS4Y1QmV1KgTSpv6$W9RQ==\', \'Comment 16: String[] #=qwa7E2DVbQ5LCzB$bnML2cQ==) at BeeMobile.MessageBox.MessageBox.ShowDialog(Control Parent) at DHPlantMobile.Controls.KotrakMessageBox.ShowDialog(String title\', \'Comment 17: String message\', \'Comment 18: KotrakMessageBoxButtons buttonsType) at DHPlantMobile.Controls.KotrakMessageBox.ShowDialog(String message\', \'Comment 19: KotrakMessageBoxButtons buttonsType\', \'Comment 20: KotrakMessageBoxType type) at DHPlantMobile.Task.TaskListForm.backgroundWorkerSelectTask_RunWorkerCompleted(Object sender\', \'Comment 21: RunWorkerCompletedEventArgs e) at System.ComponentModel.BackgroundWorker.TellThemOnGuiCompleted(Object sender\', \'Comment 22: EventArgs e) at System.Windows.Forms.Control.TASK.Invoke() at System.Windows.Forms.Control._InvokeAll() at System.Windows.Forms.Control.WnProc(WM wm\', \'Comment 23: Int32 wParam\', \'Comment 24: Int32 lParam) at System.Windows.Forms.Control._InternalWnProc(WM wm\', \'Comment 25: Int32 wParam\', \'Comment 26: Int32 lParam) at Microsoft.AGL.Forms.EVL.EnterModalDialog(IntPtr hwnModal) at System.Windows.Forms.Form.ShowDialog() at BeeMobile.MessageBox.MessageBoxModal.ShowDialog() at BeeMobile.MessageBox.MessageBoxModal.#=qeLqESOQJcNxgfwzrjtbA8Q==(Control #=qrm2DquzWZy2V02erddaodw==\', \'Comment 27: String #=q4ortAnrWpqoWcdr829dRTQ==\', \'Comment 28: String #=q5RS4Y1QmV1KgTSpv6$W9RQ==\', \'Comment 29: String[] #=qwa7E2DVbQ5LCzB$bnML2cQ==) at BeeMobile.MessageBox.MessageBox.ShowDialog(Control Parent) at DHPlantMobile.Controls.KotrakMessageBox.ShowDialog(String title\', \'Comment 30: String message\', \'Comment 31: KotrakMessageBoxButtons buttonsType) at DHPlantMobile.Controls.KotrakMessageBox.ShowDialog(String message\', \'Comment 32: KotrakMessageBoxButtons buttonsType\', \'Comment 33: KotrakMessageBoxType type) at DHPlantMobile.Task.TaskListForm.backgroundWorkerSelectTask_RunWorkerCompleted(Object sender\', \'Comment 34: RunWorkerCompletedEventArgs e) at System.ComponentModel.BackgroundWorker.TellThemOnGuiCompleted(Object sender\', \'Comment 35: EventArgs e) at System.Windows.Forms.Control.TASK.Invoke() at System.Windows.Forms.Control._InvokeAll() at System.Windows.Forms.Control.WnProc(WM wm\', \'Comment 36: Int32 wParam\', \'Comment 37: Int32 lParam) at System.Windows.Forms.Control._InternalWnProc(WM wm\', \'Comment 38: Int32 wParam\', \'Comment 39: Int32 lParam) at Microsoft.AGL.Forms.EVL.EnterModalDialog(IntPtr hwnModal) at System.Windows.Forms.Form.ShowDialog() at DHPlantMobile.Main.MenuForm.InvokeTaskList() at DHPlantMobile.Main.MenuForm.myButtonTaskList_Click(Object sender\', \'Comment 40: EventArgs e) at System.Windows.Forms.Control.TASK.Invoke() at System.Windows.Forms.Control._InvokeAll() at System.Windows.Forms.Control.InvokeHelper(Delegate method\', \'Comment 41: Boolean fSynchronous\', \'Comment 42: Object[] rgobjArgs) at DHPlantMobile.Main.MenuForm.MenuUserSelect_Click(MyIcon icon) at MyControls.MyIcon.OnClick() at MyControls.MyMenuIcon.HandleMouseUp(Object sender\', \'Comment 43: MouseEventArgs e) at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WnProc(WM wm\', \'Comment 44: Int32 wParam\', \'Comment 45: Int32 lParam) at System.Windows.Forms.ContainerControl.WnProc(WM wm\', \'Comment 46: Int32 wParam\', \'Comment 47: Int32 lParam) at System.Windows.Forms.Control._InternalWnProc(WM wm\', \'Comment 48: Int32 wParam\', \'Comment 49: Int32 lParam) at Microsoft.AGL.Forms.EVL.EnterModalDialog(IntPtr hwnModal) at System.Windows.Forms.Form.ShowDialog() at DHPlantMobile.Main.LoginUserForm.LogIn() at DHPlantMobile.Main.LoginUserForm.LoginProcess() at DHPlantMobile.Main.LoginUserForm.menuItemConfig_Click(Object sender\', \'Comment 50: EventArgs e) at System.Windows.Forms.MenuItem.OnClick(EventArgs e) at System.Windows.Forms.Menu.ProcessMnuProc(Control ctlThis\', \'Comment 51: WM wm\', \'Comment 52: Int32 wParam\', \'Comment 53: Int32 lParam) at System.Windows.Forms.Form.WnProc(WM wm\', \'Comment 54: Int32 wParam\', \'Comment 55: Int32 lParam) at System.Windows.Forms.Control._InternalWnProc(WM wm\', \'Comment 56: Int32 wParam\', "Comment 57: Int32 lParam) at Microsoft.AGL.Forms.EVL.EnterMainLoop(IntPtr hwnMain) at System.Windows.Forms.Application.Run(Form fm) at DHPlantMobile.Program.Main(){code}\'", "Comment 58: \'Hi Thomas,The information from dev is that this will be fixed in new version.Please", "Comment 59: let me know if we can close this task.Regards\'", "Comment 60: \'Hi,Did the fix inderDGS-8630 solve issue for you?Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
537 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8495\n\n### Instruction:\nDear, \r\npls update SU code list for medicated labels according to the languages.\r\nthx\r\n\n\n### Response:\n["Comment 1: [\'[^SU codes SK_HU_07022023.csv] _(8 kB)_[^SU codes_CZ_SK_07022023.csv] _(12 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hi,SU codes have been updated. Please", "Comment 4: verify.Regards\'", "Comment 5: \'Hi", "Comment 6: it is ok.thx\']"]\nRelated Issues:\n[]\n\n### End'} |
538 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8494\n\n### Instruction:\nDears,\r\n\r\nI have made an account for my colleague GGeerts for DHP for the new plant in Helmond. Unfortunately I have made a mistake in typing the password. Can you please adjust GGeert\'s current password for DHP 3.0 in Helmond to:\r\n\r\nHeus22!\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 sent a new password in private message.\'", "Comment 3: \'Hi Theo,Did you receive new password for Gerard? Does it work properly? Can we close this task?Regarsd\'", "Comment 4: \'Hi,Can we close this task?Regards\'", "Comment 5: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 6: please raise another task.Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
539 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8493\n\n### Instruction:\nFor some reason, the heavy pallet location group no longer works.\r\n\r\nThis currently results in the warehouse filling up all locations and when heavy pallets arrive, they have to empty racks again to put the pallets in the right place.\r\n\r\nThis does not seem to go well with the locations that are linked to this location group. The fact that all locations are 3 double in it also indicates that something is going wrong here.\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: \'[[email protected]] I removed this group and recreated it again. Please check if it will work. !ZP Location group! \'", "Comment 5: \'Hi,Can we close this task?Regards\'", "Comment 6: \'I still did not recieve any responce from the userI again asked for responce\'", "Comment 7: \'Waiting for ypur feedback then.Regards\'", "Comment 8: \'Any feedback?\']"]\nRelated Issues:\n[]\n\n### End'} |
540 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8492\n\n### Instruction:\nPlease create a new user for Agra-Matic. \r\n\r\nName: Willeke van Dijk.\r\n\r\nSame permissions as Nicole van Stigt Thans\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: \'Account created.\']"]\nRelated Issues:\n[]\n\n### End'} |
541 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8491\n\n### Instruction:\nOld production orders are still in DHP.\r\nIn CDN are the orders canceled.\r\nHow can this list be corrected?\r\n\r\nIt seems to go wrong:\r\nWhen cancelled confirmed \r\n\r\nWhen Closed confirmed it seem to be alwright.\r\n\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "{code:java}select distinct cdn.nazwaobiektu (zan_gidtyp\', \'Comment 4: ZaN_GIDNumer,1,2) from cdn.ZamNag zleft join cdn.ZamElem e on z.ZaN_GIDNumer=e.ZaE_GIDNumerwhere --ZaN_GIDTyp=960 AND ZaN_GIDFirma=1015303 AND ZaN_GIDNumer=18035 and ZaE_GIDNumer is null and ZaN_Stan=35{code}{code:java}select status,DocumentNumber,* FROM [Evolution_DHCountry].[dbo].[Orders] where DocumentNumber in({code}{code:java}select *from [dbo].[OrderExportInfoes] oewhere entityid in(select id FROM [dbo].[Orders] o where DocumentNumber in(\\\'SO-201/05/2022/V\\\',\\\'SO-202/05/2022/V\\\',\\\'SO-203/05/2022/V\\\',\\\'SO-204/05/2022/V\\\',\\\'SO-205/05/2022/V\\\',\\\'SO-206/05/2022/V\\\',\\\'SO-207/05/2022/V\\\')){code}"\', \'Comment 5: "Hello.When canceling an order from XL\', \'Comment 6: do not select options \\\'All items of order will be deleted\\\' and \\\'Customer\\\'s data will be deleted\\\'.When you choose option all reservation will be deleted already canceling orders is available. !screenshot-1! I have resent these orders to DHP - now the status will be correct.I will check the others and send a list."\', "Comment 7: \'Hello. I am sending a full list of corrected statuses for orders", "Comment 8: [^orders.txt] Please check and send a feedback.Regards.\'", "Comment 9: \'[[DHC] błędny status zamówień dhc/dhp|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baza%20wiedzy.one#%5bDHC%5d%20b%C5%82%C4%99dny%20status%20zam%C3%B3wie%C5%84%20dhc/dhp§ion-id=\\\\\\\\{B6BA0A4E-07B0-413E-A582-89B093FD9A36}&page-id=\\\\\\\\{8DE7307B-E53A-430D-B6AF-596D8DCB3070}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaza%20wiedzy.one%7CB6BA0A4E-07B0-413E-A582-89B093FD9A36%2F%5BDHC%5D%20b%C5%82%C4%99dny%20status%20zam%C3%B3wie%C5%84%20dhc%5C%2Fdhp%7C8DE7307B-E53A-430D-B6AF-596D8DCB3070%2F%29])\'", "Comment 10: \'Waiting for feedback off requester\'", "Comment 11: \'Hello,can I count on an update of this ticket?Thank you and regards.\'", "Comment 12: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'} |
542 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8490\n\n### Instruction:\nPlease check the screenshot for error message. JO\'s can not be processed due to an error. Thank you.\n\n### Response:\n["Comment 1: [\'!JO!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hi Aleksandra. The issuer confirmed me that this problem also dissapeared and that JO\\\'s are being processed normaly. As of 10-15 mins ago. As I said and for previous ticket if you find anything suspicious or misuse please fell fre to share with me. Thank you."\', \'Comment 4: \\\'Let me know if you still have this problem.The indicated message is displayed when the document creating the used resource does not have the "Fixed delivery value" parameter selected.!image-2023-02-07-16-50-53-588.png!For a given JO document there are 2 RM documents. One of them\', \'Comment 5: IR--100/02/23/S\', \'Comment 6: has taken resources from 3 deliveries:IR+-73/02/23/S\', \'Comment 7: IR+-76/02/23/S\', \'Comment 8: IR+-87/02/23/SAccording to the message all of those documents did not have set "Fixed delivery value" parameter.For example JO-73/02/23/S that created document IR+-73/02/23/S was closed today.!image-2023-02-07-16-53-32-093.png!That means "Fixed delivery value" parameter on IR+ document related to this JO were set today\', "Comment 9: after closing this JO.At the moment this parameter is set on all related IR+ documents and JO document has got to close status.Please try to close JO-20/02/23/S or let me know if I may try to close it.\'", \'Comment 10: "Well this is one highly detailed report! Now it is quite clear for all of us what causes this kind of JO\\\'s processing conflict. Thank you very much. Best regards."\', "Comment 11: \'You may now close this ticket. Thank you", "Comment 12: best regards.\']"]\nRelated Issues:\n[]\n\n### End'} |
543 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8489\n\n### Instruction:\nHello again, we have the same problem with receipes in Cuprija. Receipes in Sabac are OK so it is again like DGS-8470. Please check what is the problem. Thank you.\n\n### Response:\n["Comment 1: [\'!recipes!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hi,In Cuprija you have exactly the same configuration as in Sabac", \'Comment 4: recipes are available. Please\', \'Comment 5: provide me a screenshot from DHP\', "Comment 6: where is the issue.Regards!image-2023-02-07-12-23-04-287.png!\'", "Comment 7: \'I just called the issuer on which behalf I created the ticket and he told me that the problem was solved 10-15 mins ago so the screenshot does not exist anymore. Did you find any irregularities in using the app? Maybe some users are not doing something properly? Maybe...\'", "Comment 8: \'It is difficult to judge as we do not know what user did", \'Comment 9: maybe user opened wrong tab or sth or some connection issue.If the issue reoccurs\', \'Comment 10: please raise a new task. Forn now\', "Comment 11: I am closing this task.Regards\'", "Comment 12: \'I understand. Thank you for quick answer. Ragards\']"]\nRelated Issues:\n[]\n\n### End'} |
544 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8488\n\n### Instruction:\nPlease help to check VT-3471/23 and quickly solve for Bien Hoa plant .\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 check. Now it should be OK.\'", "Comment 4: \'Hi Łukasz LasokTks for ur support. \'", "Comment 5: \'brak błędów.\']"]\nRelated Issues:\n[]\n\n### End'} |
545 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8487\n\n### Instruction:\n2 recipes 147296 and 116000 don\'t show up in DHP.\r\n\r\nThey exist in DHC however. Resending them from DHH did not help.\r\n\r\nPlease assist. Needs to be produced before tomorrow morning. You can call me on +31621679216\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: \'Dear Martijn,This issue was investigated in other RCA task under:[https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7809]I have granted you access", "Comment 4: please check.The DHC 3.0.60 version should solve the problem.Regards\'", "Comment 5: \'!image-2023-02-09-09-16-16-098.png!\'", "Comment 6: \'DearMartijn,Below is the list of items which I pushed / resynced to DHC Service as they were missing in DHC Service.306250116002116003132160148296148294306814132330132310140373306808Regards\'", "Comment 7: \'Please", "Comment 8: let us know if we can close this task.Regards\'", "Comment 9: \'{color:black}Yes", \'Comment 10: thanks{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:* Aleksandra Przybyłek (Jira) <[email protected]> *Sent:* vrijdag 10 februari 2023 13:16 *To:* Meier\', "Comment 11: Martijn <[email protected]> *Subject:* DGS-8487 [RCA] - 2 receipes not coming to DHP Maasbracht | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | \']"]\nRelated Issues:\n[\'DGS-8486\', \'DGS-8528\']\n\n### End'} |
546 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8486\n\n### Instruction:\n2 recipes 147296 and 116000 don\'t show up in DHP.\r\n\r\nThey exist in DHC however. Resending them from DHH did not help.\r\n\r\nPlease assist. Needs to be produced before tomorrow morning. You can call me on +31621679216\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: \'Recipes for 147296 and 116000 are avaible in DHP. Please check.!image-2023-02-06-19-46-37-025.png!!image-2023-02-06-19-47-04-386.png!\'", "Comment 3: \'[[DHP 3.0] Brak itemu w DHCService|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/S%C5%82owacja/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Brak%20itemu%20w%20DHCService§ion-id=\\\\\\\\{DF42641F-8CC9-4202-8956-D8DA3EB978DE}&page-id=\\\\\\\\{1F3C6D0F-FACF-46BE-9BE3-93975830A455}&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%2FS%C5%82owacja%2FBaza%20wiedzy.one%7CDF42641F-8CC9-4202-8956-D8DA3EB978DE%2F%5BDHP%203.0%5D%20Brak%20itemu%20w%20DHCService%7C1F3C6D0F-FACF-46BE-9BE3-93975830A455%2F%29])\'", "Comment 4: \'I see", \'Comment 5: thanks! What was the cause\', "Comment 6: and how did you solve it?\'", "Comment 7: \'In this task we have focused on clearingandunblocking the process. Provided items did not synchronized correctly. I had to correct data in database and resynchronize items in DHH", \'Comment 8: I also had to resynchnize recipes\', \'Comment 9: production recipes and technology on DHC.If there is a need from your sideto investigate the reasonof the issue\', \'Comment 10: we may raise RootCause Analysis (RCA)task for you.Please\', "Comment 11: let us knowhow you wish us to proceed.\'", "Comment 12: \'Thanks Bartłomiej. I thought there was an agreement dat an RCA is created for every P1 incident.So please proceed on that. Thanks!\'", "Comment 13: \'Hi", "Comment 14: RCA DGS-8487 has been created.\'", "Comment 15: \'May we close this P1 task ?\'", "Comment 16: \'Yes", "Comment 17: this one can be closed. Can you please grant me access to DGS-8487? :)\'", "Comment 18: \'You should already have access\'", "Comment 19: \'Dear Martijn,Could you please check task with number DGS-8487 via portal?Regards\']"]\nRelated Issues:\n[\'DGS-8487\']\n\n### End'} |
547 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8485\n\n### Instruction:\nWhen I check the missing RM report for Utrecht, I see some items displayed that have plenty of stock: Can you check what\'s going on? Are the lot reports still closed automatic when there is stock?\r\n\r\nSee RM report attached.\r\nItem 0002, 0041, 0048 have plenty of stock on hand, but are still dispayed \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 wsparciu Macieja zaczęłam od 0002", "Comment 4: ale nie wyświetla takich PLRów!image-2023-02-08-08-54-15-777.png!!image-2023-02-08-08-54-37-584.png!\'", "Comment 5: \'Dlatowaru 0041!image-2023-02-08-08-55-29-232.png!Potwierdziłam PLRa!image-2023-02-08-08-55-56-715.png!Zniknął z raportu!image-2023-02-08-08-56-24-501.png!\'", "Comment 6: \'[[email protected]],Raport pokazuje missing stock na moment potwierdzania konkretnego raportu.Owszem mają stan magazynowy ale jest on w całości zarezerwowany pod inne loty produkcyjne.Sprawdziłem sporą ilość raportów i w każdym przypadku okazywało sie że brakuje tego stanu do potwierdzenia raportu (min. z powodu tego że jest on zarezerwowany pod inny raport)Te przypadki które udalo Ci się potwierdzić to są takie które i tak byłyby w koncu potwierdzone przez automat. Automat podczas potwierdzania bierze raporty z najmniejsza ilością prób potwierdzeń. Więc to to determinuje kiedy taki raport zostałby potwierdzony.Aby rozwiązać ich problemy należałoby niestety ręcznie pousuwać te rezerwacje i albo wtedy te raporty potwierdzić albo zostawić tą pracę dla automatu.\'", "Comment 7: \'Dear Thomas,The report shows missing stock at the moment of confirming a specific report.You do have stock", \'Comment 8: but it is fully reserved for other production lots.We checked a large number of reports and in each case it turned out that this state is missing to confirm the report (at least because it is reserved for another report)Automatic confirmation closes reports with the least number of confirmation attempts. This is what determines when such a report would be confirmed.To solve the issue\', \'Comment 9: unfortunately\', "Comment 10: these reservations would have to be removed manually and either confirmed also manually or we would leave this work for the automatic closing.Regards\'", \'Comment 11: "Hi Aleksandra: I\\\'m missing your pont. Check article 0002: The report displays a Missing quantity of 273451kg. But the quantity on hand (so not reserved!) is said to be 165 860 kg. So that quantity can be consumed/reserved\', \'Comment 12: but quantity is not lowered"\', "Comment 13: \'And check article 0041: Missing quantity is reported as 58267kg: But DHP displays 0041 with quantity on hand 376 430kg: So more than enough. Sorry to say", \'Comment 14: but as far I can see this is not reserved for anything\', "Comment 15: otherwise it wasn;t on hand: So please check again!afbeelding-4!!afbeelding-6!\'", "Comment 16: \'Hi [[email protected]],Please", \'Comment 17: let me explain to you how the mechanism of auto-confirmation lot reports works. The picture below presents the configuration of the auto-confirmation mechanism:!image-2023-02-08-16-46-18-029.png! * *CronSchedules* means how often the mechanism will check for production lots to be confirmed - in this case every single 1 hour. * *MaxCount* means how many ProductionLots will be taken by autoconfirm mechanism to be confirmed - Currently\', \'Comment 18: it is set to 200. * *MaxAgeInDays* means how "old" production lots will be taken into consideration in autoconfirming Production Lot mechanism - Currently\', \'Comment 19: it is set to 60 days.What is more\', \'Comment 20: in the production lots table there is a column that stores information about how many confirmation trials were performed in order to auto-confirm production lot (Please look at the picture below)!image-2023-02-08-16-50-39-647.png!The mechanism for auto-confirmation of production lots selects only those lot reports that are not older than 60 days and are sorted by the least amount of confirmation attempts.I analyzed 3 production lots with missing item 0002. Those lots are 0071190123076\', \'Comment 21: 0071190123082\', \'Comment 22: 0071190123089.In order to determine if/when those lots will be taken by the auto-confirmation mechanism we can use the query presented below:{code:java};WITH ProductionLotsConfirmationTraials AS( SELECT ROW_NUMBER() OVER(ORDER BY ConfirmationAttempts ASC) AS NumberInQueue\', \'Comment 23: LotNumber\', \'Comment 24: ConfirmationAttempts FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] PL WHERE PL.ProductionLotStatus = 3 and CAST(PL.StartDate AS DATE) >= DATEADD(DAY\', \'Comment 25: -60\', "Comment 26: CAST(GETDATE() AS DATE)))SELECT * FROM ProductionLotsConfirmationTraialsWHERE LotNumber IN (\\\\\'0071190123076\\\\\'", "Comment 27: \\\\\'0071190123082\\\\\'", "Comment 28: \\\\\'0071190123089\\\\\'){code}And here are the results of the query execution:!image-2023-02-08-17-07-10-874.png!It looks like that even though there is a stock available in order to confirm those lots the number in the queue is saying that there are 654 lot reports that have a lower number of confirmation trials. So that is probably the issue of why those lots are not confirmed automatically.I hope that I helped. If you have more questions please feel free to ask me. I will do my best to respond to your questions on Friday since tomorrow I will be not present at work.Regards\'", "Comment 29: \'Hi Maciej", \'Comment 30: Appreciated the explanation\', "Comment 31: that helps a lot! Clear how the mechanism works and why it stays in the report even so stock is available\'", "Comment 32: \'Hi Thomas,Do you need any further help or should we close this task?Regards\'", "Comment 33: \'You can close this task\'", "Comment 34: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
548 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8484\n\n### Instruction:\nRecipe 515205 exists in DHC, but not in DHP Sneek\r\n\r\nIn DHCService_Error queue, I see this error message regarding this recipe:\r\n\r\nThe conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value. \r\n\r\nWhat causes this error, and how do we solve 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: \'Hi,Recipe in Sneek now.Please", "Comment 3: verify.Regards!image-2023-02-07-15-10-32-661.png!\'", "Comment 4: \'{color:black}Yes", \'Comment 5: I see it\', \'Comment 6: thanks!{color} {color:black}{color} {color:black}As always\', \'Comment 7: I’d like to know what was wrong here and whether I could have solved this myself. Can you briefly explain please?{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:* Aleksandra Przybyłek (Jira) <[email protected]> *Sent:* dinsdag 7 februari 2023 15:12 *To:* Meier\', "Comment 8: Martijn <[email protected]> *Subject:* DGS-8484 SDNL-38558 | Recipe 515205 in DHC but not in DHP Sneek | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | !image006!\'", "Comment 9: \'Hi,The item was missing in DHC Service. I have resynced item", "Comment 10: resynced recipe and technology. Can I close this task?Regards\'", "Comment 11: \'Yes", "Comment 12: you can. Thanks for the explanation!\'", "Comment 13: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'} |
549 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8483\n\n### Instruction:\nIn order to accurately track stock can we have the lot numbers appear on their respective JOs? \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,This functionality is already working. Please see example for PLR:0722090223002 and respectiveJO-313/23/TEMA!image-2023-02-10-10-49-05-852.png!!image-2023-02-10-10-52-35-193.png!Regards\'", "Comment 3: \'please close\'", "Comment 4: \'Thank you\'", "Comment 5: \'Alright kindly close | !image001!!image006! | *{color:#2E74B5} *Feyi Seyram Solomon*{color}*{color:#2E74B5} ServiceDesk Engineer{color} *{color:#2E74B5} *Koudijs Ghana Limited*{color}*{color:#2E74B5} Phone: +233 30 7000 580 : Mobile: +233 59 6914 778{color}{color:#2E74B5}{color} *{color:#2E74B5} *GK-0173-1282", \'Comment 6: Tema Free Zone Enclave*{color}* *{color:#2E74B5} *Tema\', \'Comment 7: Greater Accra\', \'Comment 8: COD TD 200 Ghana*{color}* *{color:#2E74B5} **{color}*{color:#2E74B5} This e-mail message and its attachments are subject to the disclaimer published at the website of{color} [{color:#0563C1}Koudijs Animal Nutrition{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.koudijs.com%2Fdisclaimer&data=05%7C01%7CSFeyi%40koudijs.com.gh%7C1cdd4c26b4484d6270e708daf877ef8b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638095491246060747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Sda%2Fs8RH6LVyAD6b9dCkcyZFILd6rVJqdsWh%2B65H9QE%3D&reserved=0]{color:#2E74B5}{color} | *From:* Aleksandra Przybyłek (Jira) <[email protected]> *Sent:* Friday\', \'Comment 9: February 10\', \'Comment 10: 2023 9:55 AM *To:* Feyi\', "Comment 11: Solomon <[email protected]> *Subject:* DGS-8483 Lot numbers on JOs | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | !image002!!image004!!image005!\']"]\nRelated Issues:\n[]\n\n### End'} |
550 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8482\n\n### Instruction:\nHello,\r\n\r\nWe have again an issue with inventorisation.\r\n\r\nComparing the figures downloaded at the end of 31 December 2022 for (stock on hand dated 31st December 2022) and\r\nthe report pulled today for (stock on hand dated 31st December 2022)\r\n\r\nThere seem to be variances in the figures.\r\n\r\nKindly help us get to the cause\n\n### Response:\n["Comment 1: [\'[^recheck dec 31 2022.xls] _(67 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: \\\'Hi SamuelAs I see now the quantities on stocks are different then in your report. The differences between quantity on stock and "for sales" are very small.The small differences result from documents such as warehouse documents without an internal document (generated from inventory) or purchase document (PORC-120/21) without a warehouse document (WR-)WR--126/22WR--118/22WR--127/22WR+1553/22This is because you generated inventory in different way - inventory configuration: stocktaken quantity: warehouseThere should be IR-\', \'Comment 4: IR+ documents generated from these documents. !screenshot-1! There is also IR--247/21/TEMA without WR-so you should generate WR- - by right mouse button on IR--247/21/TEMA and choose option WR- "Release from warehouse"There are also some differences which probably results from some system errors and which has to be analysed .\\\'\', "Comment 5: \'Is it possible to generate all document released or closed on 31st December 2022; but has initiating date prior to 31st December 2022 ( we believe lots of documents from prior month and year were released to disrupt the inventory process)\'", \'Comment 6: "Hi SamuelYes \', "Comment 7: it\'s possible to create documents with date on 31st December and before.Regarding to Inventory process:If at the time of creating the inventory in the system there was a difference between the quantity for sale and the quantity in stock", \'Comment 8: it certainly caused the inventory to be incorrect to some extent.Stocks should always be leveled before starting an inventory and there must be no documents in the buffer.At the moment\', \'Comment 9: even in the system there are still documents in the buffer in old years\', \'Comment 10: e.g. IR-3416/22/TEMA"\', "Comment 11: \'How do we bring this document to excel with quantity and value to explain differences in inventory to our Bosses?\'", \'Comment 12: \\\'Every document in the system can be transfer to excel file.You need to open document and use !screenshot-2! [Export to speadsheet] icon - this option will transfer item with quantityor by [Printing icon] - but you need to print document as "View on the screen" and then use export icon (first icon on the left)The system will open Export window and you can choose options like:Export to excel\', \'Comment 13: PDF\', "Comment 14: others !screenshot-3! \'", "Comment 15: \'What documents should I be looking for and how do I navigate to get all these documents causing these differences at a go?\'", "Comment 16: \'I think we need help resolving all warehouse discrepancies as soon as possible", "Comment 17: how do we do that IR-3416/22.\'", "Comment 18: \'[^Warehouse_discrepancies.xlsx]\'", \'Comment 19: "HiI generated Internal Receipt and Internal Release documents from WR-\', \'Comment 20: WR+also I generated WR-\', \'Comment 21: WR+ from SORs documents from this list: !screenshot-4! I fixed document PORC-206/21\', \'Comment 22: the stock of 1101011 i s ok now (technically ok).I\\\'m attaching the list of documents that are left to fix [^Warehouse_discrepancies.xlsx] "\', \'Comment 23: \\\'HiI generated all warehouse documents.Now all differences between sales and warehouse quantity results from documents with status "BUFFER"This is actually ok.But you need to remember that before inventory all documents should be confirmed.If you will try to add new inventory now the system will show warning:For warehouse ...... there are documents in buffer. It contains items which trade quantity is different than quantity in stock. It may not be possible to fully correct shortage quantity. Documents in buffer will not be confirmed until inventory is completed. !screenshot-5! \\\'\', "Comment 24: \'Could you please confirm if we can close this task?Regards\'", "Comment 25: \'This ticket was created by Samuel so I cannot authorize that please. | !image001!!image004! | *{color:#2E74B5} *Feyi Seyram Solomon*{color}*{color:#2E74B5} ServiceDesk Engineer{color} *{color:#2E74B5} *Koudijs Ghana Limited*{color}*{color:#2E74B5} Phone: +233 30 7000 580 : Mobile: +233 59 6914 778{color}{color:#2E74B5}{color} *{color:#2E74B5} *GK-0173-1282", \'Comment 26: Tema Free Zone Enclave*{color}* *{color:#2E74B5} *Tema\', \'Comment 27: Greater Accra\', \'Comment 28: COD TD 200 Ghana*{color}* *{color:#2E74B5} **{color}*{color:#2E74B5} This e-mail message and its attachments are subject to the disclaimer published at the website of{color} [{color:#0563C1}Koudijs Animal Nutrition{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.koudijs.com%2Fdisclaimer&data=05%7C01%7CSFeyi%40koudijs.com.gh%7C1cdd4c26b4484d6270e708daf877ef8b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638095491246060747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Sda%2Fs8RH6LVyAD6b9dCkcyZFILd6rVJqdsWh%2B65H9QE%3D&reserved=0]{color:#2E74B5}{color} | *From:* Beata Kapturska (Jira) <[email protected]> *Sent:* Friday\', \'Comment 29: March 17\', \'Comment 30: 2023 11:15 AM *To:* Feyi\', "Comment 31: Solomon <[email protected]> *Subject:* DGS-8482 INVENTORY ON HAND !image002!\'", "Comment 32: \'[[email protected]]Could you please confirm if we can close this task?Best Regards\'", "Comment 33: \'yes please\']"]\nRelated Issues:\n[]\n\n### End'} |
551 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8481\n\n### Instruction:\nCan you re-open round ID 30372? I thought this was already done, but I can not book a correction report on 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: "Hello,Round is in Active status now.We sent it back to \\\'Active\\\' status to Anja\\\'s inbox (as it was before).!image-2023-02-06-11-52-45-590.png!Regards"\', \'Comment 3: "Who is able to re-open rounds at the moment? It should be Koen\', \'Comment 4: Steffen\', \'Comment 5: Nancy\', \'Comment 6: Peter and Bessel.I see lot\\\'s of tasks about this and I would like some users to be able to re-open rounds themselves."\', "Comment 7: \'It has been added in taskhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8568\']"]\nRelated Issues:\n[]\n\n### End'} |
552 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8480\n\n### Instruction:\nPrzy podziale pozycji na różne magazyny w kontrakcie system (GUI) przypisuję cenę z magazynu źródłowego pomimo wprowadzenia przez kupca innej ceny na pozycji, której ilość dokładamy już w momencie przepisywania ilości. Zapisanie formatu nie wnosi nic do poprawności danych.\r\n\r\n\r\nPrzykład kontrakt ZZ-298/01/23 testowany przeze mnie.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \' !screenshot-1! \'", \'Comment 3: "Hi\', \'Comment 4: the application has an active configuration for copying the price and VAT from the source element to the target in split position.I understand it\\\'s a different case and is it always?Does it look like this on the test too?"\', "Comment 5: \'Hello", "Comment 6: please reply to our last comment.Thank you and regards.\'", \'Comment 7: \\\'Function "split position" should work as described in task https://helpdesk.kotrak.com/browse/GDC-589\\\'\', "Comment 8: \'DEV-TS01-20 can I get access to this server for tests ? pgaczorek account because this GDC is from the middle of last year.\'", "Comment 9: \'done\'", "Comment 10: \'Access granted\'", "Comment 11: \'I made a scenario with GDC on the test for the order and the price is rewritten from the split position.Is it reproducible", "Comment 12: e.g. can it be repeated on the test - this case from the current dgs?Maybe a step-by-step video.\'", "Comment 13: \'you can close this task\']"]\nRelated Issues:\n[]\n\n### End'} |
553 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8479\n\n### Instruction:\nWe can update rounds for archived SI+PI, but not for SR. Can you make this possible too? \r\n\r\nThis is okay by Mitch. \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 Dirco,There is functionality for SR to updating round and invoices connected to SR.Could you verify that you are able to do it by this action from lightning - action \\\'Update SR and linked invoices Round Number\\\'?!image-2023-02-06-10-47-34-260.png!Regards"\', \'Comment 3: "Yes I see now\', \'Comment 4: please close it. Thanks! Could not do this in another SR\', \'Comment 5: but don\\\'t know which this was"\', "Comment 6: \'I close the task", "Comment 7: if there will appear some other issues with action please report it to us.Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
554 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8478\n\n### Instruction:\nWhen deleted records appears again.\r\n\r\nAdvice was : VT on hold and then delete.\r\n\r\nQuestion : Witch VT?\n\n### Response:\n["Comment 1: [\'See also ticket DGS-8293\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'This VT should be set on hold before delting SOR?The VT is closed. How can it then reopen the sor?!image!!image-1!!image-2!!image-3!\'", \'Comment 4: \\\'Hi,SOR-111/09/2022/V will return because in DHP there is an information about dispatch so ERP Int "copies" the situation in documents in ERP.Why do you want to delete documents with items dispatched?Regards\\\'\', "Comment 5: \'Hi,Any feedback?Regards\'", "Comment 6: \'This SOR111/09 has been incorrectly (double) createdSo this one has to be cancelled\'", "Comment 7: \'Can you please provide me:>> SOR number that was incorrectly (double) created by SOR-111?>> SO that is the source for duplicated SOR (the other one", \'Comment 8: not 111)From ERP all seems to be good:we have one VT\', \'Comment 9: one SO and one SOR\', "Comment 10: quantities are correct:!image-2023-03-01-12-49-20-309.png!!image-2023-03-01-12-50-33-501.png!!image-2023-03-01-12-51-28-996.png!\'", "Comment 11: \'!image-4!\'", "Comment 12: \'!image-5!\'", "Comment 13: \'Hi,I do not see where it is a duplicate. SOR-138 is clipped with different VT document and different SO document!image-2023-03-23-14-56-00-207.png!!image-2023-03-23-14-56-30-434.png!Please", \'Comment 14: compare my screenshots from today and the previous one.If we want to cancel SOR-111 for ever\', \'Comment 15: we also need to cancel clipped VT-3865. Please\', "Comment 16: accept or deny. What about SO-92 then?Regards\'", "Comment 17: \'Any feedback?Regards\'", "Comment 18: \'!image-6!\'", "Comment 19: \'I am waiting off responce from the user\'", "Comment 20: \'Waiting for your feedback then\'", "Comment 21: \'The user can not cancel this SOR.hen he tries to cancel the acceptbutton is still grey.The user is asking if Kotrak will cancel this SOR!image-7!\'", "Comment 22: \'I still do not have an answer for marked question that I have asked on the 23rd of March:If we want to cancel SOR-111 for ever", \'Comment 23: we also need to cancel clipped VT-3865. Please\', "Comment 24: accept or deny. What about SO-92 then?It is impossible to cancel SOR just like that.!image-2023-04-18-14-16-08-716.png!\'", "Comment 25: \'!image-8!\'", "Comment 26: \'VT-3865 has been cancelled in DHC", \'Comment 27: SOR-111 has been deleted as it was in buffer\', \'Comment 28: SO-92 has been cancelled in ERP XL. Please\', \'Comment 29: verify.In DHP\', \'Comment 30: please perform inventory. Please\', "Comment 31: let us know if we can close this task.Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
555 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8477\n\n### Instruction:\nPlease help to check VT-289/2/23 in Hai Phong 2 Plant (0436).\r\nThis VT can\'t be closed .\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: "NA VT są 2x close VT w zależności co się wybierze -Final weighing is required in workflow-Unsupported VT close direction{code:java}SELECT * FROM [DHPlantVCBusinessLogicMain].[dbo].[RF_VehicleTicketWorkflowTransitions] where id=\\\'3a68bd66-6d06-4fb9-af98-4c5a8ccf3ed0\\\' insert into [DHPlantVCBusinessLogicMain].[dbo].[RF_VehicleTicketWorkflowTransitions] values (\\\'3A68BD66-6D06-4FB9-AF98-4C5A8CCF3ED0\\\',2,\\\'2023-02-04 10:40\\\',3,\\\'XB3\\\',null) select top 10 * from dbo.RF_WorkflowNodes where id=\\\'0C2FEEE4-64B4-4D16-87FF-99BCEEBF0693\\\' select top 10 * from RF_VehicleTicketWorkflows where id=\\\'3a68bd66-6d06-4fb9-af98-4c5a8ccf3ed0\\\' {code}"\', "Comment 4: \'Please check", "Comment 5: VT-289 is now closed.\'", "Comment 6: \'[[DHP 3.0] Close VT", "Comment 7: problem z zamknięciem VT|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Wietnam/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Close%20VT,%20problem%20z%20zamkni%C4%99ciem%20VT§ion-id=\\\\\\\\{2B12CDB9-0ACA-4E3F-B40E-E88F97AD3C58}&page-id=\\\\\\\\{B5A9B8B1-38A8-4E61-AFB4-6DCA80B4A046}&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%2FWietnam%2FBaza%20wiedzy.one%7C2B12CDB9-0ACA-4E3F-B40E-E88F97AD3C58%2F%5BDHP%203.0%5D%20Close%20VT%2C%20problem%20z%20zamkni%C4%99ciem%20VT%7CB5A9B8B1-38A8-4E61-AFB4-6DCA80B4A046%2F%29])\'", "Comment 8: \'Hi Piotr Gaczorek .You can close the ticket .\']"]\nRelated Issues:\n[]\n\n### End'} |
556 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8476\n\n### Instruction:\nAction \'Export S2P to Milas\' for S2P document should be executed only when document is sent \'To Archive\' to avoid situations when someone export S2P to Milas and then will change data on S2P. After sending S2P it shouldn\'t be possible to modify document again.\r\n\r\nAction \'Export S2P to Milas\' shouldn\'t be available from lightning button from ribbon - should be removed for all users.\r\n\r\nOnly few users should be able to send Archived S2P document to Entry state (Starting new process for document) - for now Mitch and Richard if there will be need to send again S2P to Milas.\r\n\r\nIt should be applied to all sectors.\r\n\r\n\xa0\n\n### Response:\n["Comment 1: [\'Do zmiany ta akcja:!image-2023-02-03-12-53-46-122.png!!image-2023-02-03-12-53-53-556.png!\'", "Comment 2: \'Wszystkie akcje powinny wyglądać tak:!image-2023-02-03-13-53-57-914.png!\'", "Comment 3: \'We blocked the possibility of sending saldo2pay to milas from the button under the lightning", "Comment 4: saldo is send to milas automatically when the flow to the archive is performed!image-2023-02-03-14-47-28-069.png!\'", \'Comment 5: "Zmienione zostało ustawienie \\\'New process can be started\\\' na wszystkich dokumentach \\\'Saldo to Pay\\\' we wszyskich sektorach:!image-2023-02-06-10-24-26-533.png!Rola \\\'ALL\\\' ma uprawnienia do rozpoczynania nowego procesu. Na tą chwilę możliwość tą powinni mieć Mitch i Richard i są oni w tej roli.Usunięte zostało to uprawnienie dla roli \\\'All users\\\'\', \'Comment 6: tylko rola \\\'ALL\\\' ma możliwość rozpoczynania nowego procesu.!image-2023-02-06-10-31-12-337.png!"\', \'Comment 7: "Exporting Saldo to pay to Milas now is moved to flow\', \'Comment 8: when document is sending \\\'To archive\\\' system sends S2P to Milas.!image-2023-02-06-11-12-21-523.png!Rights for starting new process has been added for Mitch and Richard. It will be possible to start new process in case when it\\\'s needed resend document Saldo to pay to Milas.!image-2023-02-06-11-11-12-104.png!"]\']\nRelated Issues:\n[]\n\n### End'} |
557 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8475\n\n### Instruction:\nwe have problem in production SUR7579-P-MD, 0871010223005, system not allow to add or change reservation.\r\nThe last time that we had similar problem (DGS-8210) was changed to settlement basing on "Mixed" , but this is not correct, we need to make consumption of correct delivery.\r\nWe need to load urgent, could you check why we have this error?\r\nThank you\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hi,Is error message the same as in DGS-8210?\'", "Comment 4: \'To unblock this process we can change configuration as in DGS-8210 for a while", \'Comment 5: you could add reservation and confirm and then we will return to previous configuration. The error is because for example this item is taken from two different deliveries\', \'Comment 6: please see attach:!image-2023-02-03-13-19-23-898.png!As Łukasz mentioned in previous task\', \'Comment 7: it comes from system assumption. If you want change assumption\', "Comment 8: please raise a GDC task. In P1 task we are focusing on unblocking process.Regards\'", \'Comment 9: "Hello Aleksandra,we don\\\'t know if have the same error message\', \'Comment 10: because system not allow to add reservation and when we try to close\', \'Comment 11: shows that is missing reservation.But the tab reservation is with the same error\', \'Comment 12: gray lines without option to edit\', \'Comment 13: and white lines with option to add but when we select lot number\', \'Comment 14: changes to red but is not exceeded quantitty. So it\\\'s not possible to confirm."\', "Comment 15: \'Aleksandra,we can use 2 different deliveries", "Comment 16: and if PCS send a delivery with not available stock we can change the delivery on tab reservation. This happened other times and was possible to edit. Why is not possible edit this one?\'", "Comment 17: \'Is it possible tochange configuration to mixed and check if reservation is possible?\'", "Comment 18: \'We can see that there was some timeout that is why PLR did not change status to confirmed in Prod module. In Stock module it is confirmed and there are dispatches already that is why reservations are not editable. Please", "Comment 19: let us know if you can process PLR in ERP manually. Regards\'", \'Comment 20: \\\'I changed the configuration for "mixed"\', "Comment 21: but it\\\\\'s not possible add the lot number", "Comment 22: system shows the line red even if I didn\\\\\'t add all quantity !image-2!\'", "Comment 23: \'Please", \'Comment 24: return configuration.We can see that there was some timeout that is why PLR did not change status to confirmed in Prod module. In Stock module it is confirmed and there are dispatches already that is why reservations are not editable. Please\', "Comment 25: let us know if you can process PLR in ERP manually. Regards\'", "Comment 26: \'We pushed the event. Please", "Comment 27: verify\'", "Comment 28: \'Aleksandra I returned configuration. And in ERP we created inventory to have stock to invoice. But I need to close this production because this process is temporary and they need to reverse the inventory.You can change to P2. But I still need your help to close this production and open RCA to investigate what happened.Thank You\'", "Comment 29: \'We pushed event", "Comment 30: please verify now\'", "Comment 31: \'Dear [[email protected]],as Aleksandra wrote earlier", \'Comment 32: the lack of possibility to indicate the deliveries from which PLR should to be settled was due to the fact that all raw materials have already been settled.Settlement of raw materials occurred as a result of executing the report confirmation procedure. The procedure settled the raw materials but did not confirm the report due to a timeout in communication between the Stock and Production modules. The timeout\', \'Comment 33: in turn\', \'Comment 34: occurred due to an incorrect way of registerin the production. The procedure used to register the batch report was executed separately for each dosing of raw materials\', \'Comment 35: while it should have been executed once per batch.As of today\', \'Comment 36: we have confirmed the report in the production module and triggered its synchronization to DHC.In order to avoid similar problems in the future\', "Comment 37: we propose to return to discussions about adding a separate procedure to allow each dosing to be registered with a separate message.\'", "Comment 38: \'Dear Priscyla,Can we close this task?Regards\'", "Comment 39: \'Dear Priscyla,Can we close this task?Regards\'", "Comment 40: \'Hi Aleksandra,yes", "Comment 41: you can close this task.Thank you.\']"]\nRelated Issues:\n[\'DGS-8210\', \'DAP-12601\', \'DAP-13280\']\n\n### End'} |
558 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8474\n\n### Instruction:\nDears,\r\n\r\nOne of our customers in Denmark gets audited next Monday and they need the labels. \r\nCan you generate Danish labels for the following three products:\r\n508609, 505312 and 508689? \r\nWe need these a.s.a.p. I hope you can help us. \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: \'Ostatnie wersje z DHH505312 - ver 154 508609 - ver 69508689 - ver 25\'", "Comment 3: \'Dear Theo,Could you please clarify? The newest version from DHH are the newest versions in Plant for requested items. Is that correct? Or freshest labels are required?!image-2023-02-03-12-15-37-286.png!!image-2023-02-03-12-16-27-421.png!!image-2023-02-03-12-16-58-944.png!\'", "Comment 4: \'Hi Aleksandra,Actually I need the labels for these orders (see image). Is that possible?!image-2!\'", "Comment 5: \'These orders have order only the three products i mentioned earlier. But it is important that we get the labels with the correct versions. If I can do something to assit you", "Comment 6: please let me know\'", "Comment 7: \'Theo,The first Order is in Plant. But please", \'Comment 8: mind this order is from October. Could you please provide me the screenshot where the information is missing? And\', "Comment 9: please send us Order numbers in excelRegards!image-2023-02-03-13-31-16-056.png!\'", "Comment 10: \'Otherwise the most recent versions of the labels might be sufficient for now as well. \'", "Comment 11: \'Theo,The first Order is in Plant. But please", \'Comment 12: mind this order is from October. Could you please provide me the screenshot where the information is missing? And\', "Comment 13: please send us Order numbers in excelRegards\'", "Comment 14: \'See attached Excel file (first column) for the Sales Orders. I miss all the label information because in the beginning there were not any labels printed. So all I need are the labels. At leaset for the three products I have mentioned earlier[^Copy of Pakbonnen van klant_638109503540026658.xlsx] _(14 kB)_\'", "Comment 15: \'Thank you\'", "Comment 16: \'[^TRADER_BagLabel_03022023_155931486_fa3dc2ee-cb59-4a6d-9855-93c1ebac33a7.xml]\'", "Comment 17: \'Please", "Comment 18: try to print and let us know if it works\'", \'Comment 19: "{code:java}select ii.Code as itemcode\', \'Comment 20: o.DocumentNumber as salesordernumber\', \'Comment 21: bp.Code as customercode\', \'Comment 22: e.No as linenumber\', "Comment 23: (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.PlantId join [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdwhere 1=1and i.id = ii.idand g.Code = \'DA\'order by r.Version desc", "Comment 24: 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 = \'SO000011036\'and ii.code in(\'508609\'", \'Comment 25: \\\'505312\\\',\\\'508689\\\'){code}"\', "Comment 26: \'In reference to the internal conversations via teams can we change the status of the request to p2?You respond to Maciej Dobrzański that this one label that we created was ok", \'Comment 27: but unfortunately\', "Comment 28: there is problem with missing this orders in other ( not supported by Kotrak) so do you want us to create other xmls files for the rest ?\'", "Comment 29: \'Sytuacja wygląda tak że jakby się zdecydowali robić te xml jednak to :na swagerze post big label request :uzupełniamy wg danych z select", \'Comment 30: nazwy column pokrywają się z polami w polach do uzupełnienia\', \'Comment 31: język bez zmian\', "Comment 32: i jak sprawdziłąm selectem cały czas ten sam costumer code,!image-2023-02-03-17-16-23-044.png!i klikamy na dole executei weryfikujemy czy plik xml się utworzył tutaj :!image-2023-02-03-17-18-35-225.png!wygenrowane pliki wycinamy i wysyłamy w tasku ( nie zostawiamy w tym folderze)\'", \'Comment 33: "tu wersja select juz na te wszystkie ordery z excela z foreignnumerami zeby moze było szybciej z tym poleciecselect ii.Code as itemcode\', \'Comment 34: o.DocumentNumber as salesordernumber\', \'Comment 35: o.ForeignDocument\', \'Comment 36: bp.Code as customercode\', \'Comment 37: e.No as linenumber\', "Comment 38: (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.PlantId join [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdwhere 1=1and i.id = ii.idand g.Code = \'DA\'order by r.Version desc", "Comment 39: 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 in (\'SO000011036\',\'SO000007243\',\'SO000014250\',\'SO000017312\',\'SO000011036\',\'SO000011036\',\'SO000007243\',\'SO000014250\',\'SO000007243\',\'SO000014250\',\'SO000017312\',\'SO000017312\',\'SO000019255\',\'SO000020555\',\'SO000020544\',\'SO000022840\',\'SO000023891\',\'SO000025114\',\'SO000019255\',\'SO000025116\',\'SO000030186\',\'SO000033625\',\'SO000035730\',\'SO000023891\',\'SO000023891\',\'SO000036852\',\'SO000038307\',\'SO000038307\',\'SO000040369\',\'SO000044219\',\'SO000044882\',\'SO000046836\',\'SO000049821\',\'SO000054521\',\'SO000053590\',\'SO000056862\',\'SO000060692\')and ii.code in(\'508609\'", \'Comment 40: \\\'505312\\\',\\\'508689\\\')"\', \'Comment 41: "Hi Agnieszka\', \'Comment 42: you can close this task. Many thanks for your and Maciej\\\'s help in this. "\', "Comment 43: \'No issue :)Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
559 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8473\n\n### Instruction:\nHi, form Wiola\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!\'", "Comment 2: \'Przy dodawaniu jakiego atrybutu (nazwa) jest taki błąd?\'", "Comment 3: \'!image-3!\'", \'Comment 4: "|Współpraca z XL - komunikat z błędem przy zapisie grupy atrybutów\', "Comment 5: do której został dodany atrybut bez zaznaczonego parametru Synchronizowany z Comarch ERP XL.Z poziomu konfiguracji firmy / Płace / Atrybuty-grupy dodając grupę atrybutów w której zostanie przypisany atrybut bez zaznaczonego parametru Synchronizowany z Comarch ERP XL - podczas zapisu pojawia się komunikat:Cannot insert the value NULL into column \'AKl_AtKId\'", \'Comment 6: table \\\'ERPXL_FIRMA_XL.CDN.AtrKompletyLinki\\\'; column does not allow nulls. INSERT fails.|2022.5.1|Oczekujące||||||Zgłaszający||||Data zgłoszenia||||Wersja realizacji|||||2022-06-24 08:51:43|2023.5.1|||"\', \'Comment 7: "Dzień dobry,Na ten moment nie powinno być błędu przy otwieraniu atrybutów na pracownikach. Po naprawie nie powtórzyłam też błędu przy dodawaniu grupy atrybutów. Nie mniej jednak na stronie producenta znalazłam informację że jest to znany błąd o poniższej treści i planowana wersja naprawy to2023.5.1. Proszę o weryfikację czy przy dodawaniu tego pakietu dla innych pracowników problem się powtórzy.Współpraca z XL - komunikat z błędem przy zapisie grupy atrybutów\', "Comment 8: do której został dodany atrybut bez zaznaczonego parametru Synchronizowany z Comarch ERP XL.Z poziomu konfiguracji firmy / Płace / Atrybuty-grupy dodając grupę atrybutów w której zostanie przypisany atrybut bez zaznaczonego parametru Synchronizowany z Comarch ERP XL - podczas zapisu pojawia się komunikat:Cannot insert the value NULL into column \'AKl_AtKId\'", \'Comment 9: table \\\'ERPXL_FIRMA_XL.CDN.AtrKompletyLinki\\\'; column does not allow nulls. INSERT fails."\', "Comment 10: \'Jest ok", \'Comment 11: temat do zamknięcia\', "Comment 12: dzięki.\']"]\nRelated Issues:\n[]\n\n### End'} |
560 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8472\n\n### Instruction:\nHi, \r\n\r\nAt CDN XL 2020 ( x.x.x.41), \r\n We got error as attached when we try these steps -\r\nOption-1 \r\n 1) SO 289 => Item - 883486200068 - 22 kg\r\n 2) SOR => Change Quantity to 22 kg to 22.1 kg and save\r\n ... Got resource issue as attached. \r\n\r\nOption-2\r\n 1) SO 289 => Item - 883486200068 - 22 kg\r\n 2) SOR => Generate as Item - 883486200068 - 22 kg\r\n 3) SORC => Quantity change to 22.1 kg and save.\r\n ... Got resource issue as attached. \r\n\r\nOption-3 \r\nWe can release it if we try as below\r\n 1) SO 289 => Item - 883486200068 - 22.1 kg\r\n 2) SOR => can generate successfully.\r\n\r\nQuestion : \r\n1) since option 3 is works, stock must be available in system. Why we cannot do as Option 1 and Option 2. Any limitation?\r\n\r\n\n\n### Response:\n["Comment 1: [\'!DHF-1.JPG|thumbnail!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hi ", "Comment 4: Any update on below case. \'", \'Comment 5: "I\\\'ve changed configuration for SORC documents. From now on ERP system will allow you to use another delivery for release corrections. Second option should be avaible for You from now on.For purpose of analysis of first option we will need more information such as message with expanded Details section and document with such issue for analysis."\', "Comment 6: \'select * --update k set Kon_Wartosc=1from cdn.konfig k where kon_numer=-123\'", "Comment 7: \'Please", "Comment 8: let me know do you expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 9: \'Hi", "Comment 10: Sorry for late response. I am a bit confuse about 1st option. May I know what is it? I assume 2nd option be resource release from SOR correction able to use it? If we have extra resources. For Example: SOR with 20 kg and SORC with 20.56 kg. Is it worked?\'", "Comment 11: \'System ERP XL works based on quantities from deliveries. When You try to increase quantity on release document in Yours configuration it tries to release quantity from the exact same delivery.Ive changed that configuration option Please try to relog (log off and log on) into ERP sstem and check if system let You to increase quantity without any error message.\'", "Comment 12: \'So", "Comment 13: we will ask user to try and will update here. Please take on hold till end of next week? Is it ok?\'", "Comment 14: \'Please", "Comment 15: let me know do you expect any additional actions from us regarding this issue? Can we close this ticket?\'", \'Comment 16: "Hi\', "Comment 17: users are testing this week. Could you please hold till end of this week (25-Feb). If we don\'t have any further issue", \'Comment 18: please close the ticket. Thank you in advance."\', "Comment 19: \'Please", "Comment 20: let me know do you expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 21: \'Hi,Please close the ticket. \']"]\nRelated Issues:\n[]\n\n### End'} |
561 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8471\n\n### Instruction:\nHello, This is needed for planned Go-Live of Helmond: I set Priority to P2, but prio is high: We have an recipe 114206 which is blocked by contamination: Strange thing is that it is blocked for location Helmond, but same item/recipe exist also for location Maasbracht and is not blocked there: Can you check this and see what is wrong?\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-03-09-53-54-818.png!\'", "Comment 3: \'Hi Thomas,For this issue", "Comment 4: please create a story in task under DHITS-695 and let us know if we can close DGS task.Best regards\'", "Comment 5: \'Ticket created\'", "Comment 6: \'Thank you. Can I close DGS?\'", "Comment 7: \'Will it be picked there? I see it is not handled currently\'", "Comment 8: \'No", "Comment 9: this issue will be processed in DHITS as the factory is not on Service Desk.Regards\'", "Comment 10: \'Oke", "Comment 11: please close this ticket\'", "Comment 12: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'} |
562 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8470\n\n### Instruction:\nThere are only 5 recipes available in dropdown menu for rework in Cuprija plant. It is necessary that all of the recipes are available in that menu, not just last 5. Thank you.\n\n### Response:\n["Comment 1: [\'!HowItShouldBe!!NowOnly5available!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Please check should be working now.\'", "Comment 4: \'It is OK now. Thank you for your help. Best regards!\']"]\nRelated Issues:\n[]\n\n### End'} |
563 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8469\n\n### Instruction:\nHi\r\n\r\nWe created and wrongly registered a UL in WO(IP) process. However, when we try to remove the registered UL, system shows an error message.\r\nWO(IP)-24/2/23\r\n85-W02OS5\r\n\r\nCould you please remove this UL from registered?\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \' !screenshot-1! !screenshot-3! !screenshot-2! !screenshot-4! !screenshot-5! \'", "Comment 4: \'Hello", "Comment 5: this STK is correct one?Because this code has one !screenshot-6! !image-2023-02-03-13-58-25-071!\'", \'Comment 6: "Hi PiotrWe tried to clear the UL from WO(IP) screen\', \'Comment 7: without success.So we tried to release the UL in WMS module by stk also. So after we restored this UL. But we\\\'ll not use it. Physically this palletlabel doesn\\\'t exists anymore.What is your instructions? Confirm this WO(IP) with this UL and release it later with UL STK?Thank you"\', "Comment 8: \'Yes please process it further and then release it by stocktaking.If there are errors please let me know.\'", \'Comment 9: "Hi PiotrI\\\'m trying to COMPLETE it\', \'Comment 10: however the button is disabled.Could you please complete it?Thank you!image-1!"\', "Comment 11: \'Hi Maicon", \'Comment 12: I chose the completed option\', "Comment 13: please check.\'", \'Comment 14: "Hi PiotrNow it\\\'s OKYou can close this taskThank you very much"\', "Comment 15: \'You are welcome\']"]\nRelated Issues:\n[]\n\n### End'} |
564 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8468\n\n### Instruction:\nthe following IOs are not showing up in DHP for VT to be created\r\nIO 404/23, 405/2 and 406/23 please help\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: \'!4062.PNG|thumbnail! !406.PNG|thumbnail! !405.PNG|thumbnail!\'", "Comment 3: \'Please verify again it seems like all of them are all in dhp please verify. !4062.PNG!\'", "Comment 4: \'please close\']"]\nRelated Issues:\n[]\n\n### End'} |
565 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8467\n\n### Instruction:\nHi\r\n\r\nWe had a case of PLR whitout PCS report on screen last week.\r\nYesterday it happened again.\r\nThe PLR lot number *0882300123013* had the Start, Batches and Finish production on PCS however DHP didn\'t received information abou dosed quantity and it\'s reservations.\r\n\r\nHowever I checked in database and the information is there.\r\n\r\nCould you please check why this is happeneing?\r\nI\'m afraid of having more and more cases like this.\r\n\r\nThank you\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: \'HiAny news?Thank you\'", "Comment 4: \'id=d80b877a-e353-4871-9fd2-4c8495888097\'", "Comment 5: \'!image-2023-02-06-14-00-31-759.png!\'", \'Comment 6: \\\'!image-2023-02-06-14-37-30-990.png!{code:java}An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Dosings_StockUnits_StockUnitId". The conflict occurred in database "DHPlantProdBusinessLogicMain"\', \'Comment 7: table "dbo.StockUnits"\', "Comment 8: column \\\\\'Id\\\\\'.The statement has been terminated.{code}\'", "Comment 9: \'!image-2023-02-06-14-48-11-133.png!Ale w stocku jest już inne id!image-2023-02-06-14-48-28-792.png!\'", "Comment 10: \'!image-2023-02-06-14-49-45-803.png!\'", \'Comment 11: "{code:java}FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\' FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%D80B877A-E353-4871-9FD2-4C8495888097%\\\' SELECT * FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%D80B877A-E353-4871-9FD2-4C8495888097%\\\'{code}{code:java}FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where LotNumber = \\\'0882300123013\\\'select * FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLotElements] where id = \\\'D80B877A-E353-4871-9FD2-4C8495888097\\\'SELECT TOP (1000) [Id] ,[Barcode] ,[CreatedDate] ,[ItemId] ,[DeliveryId] ,[Type] FROM [DHPlantProdBusinessLogicMain].[dbo].[StockUnits] where Barcode = \\\'88-W02781\\\' and ItemId = \\\'EB087234-9A43-47BD-8E59-2EE33AB790DA\\\'{code}"\', "Comment 12: \'Hi,The issue is with stock unit with barcode88-W02781. How was the intake done? Or how was it registered? By two users? Or were there some corrections made?Regards\'", "Comment 13: \'W błędach woła", \'Comment 14: że StockUnit z "żółtym" id jest not found. I stock unit z tym id jest nie we wszystkich modułach. Wygląda troche tak\', "Comment 15: jakby było usunięte i na nowo dodane!image-2023-02-07-11-29-15-178.png!!image-2023-02-07-11-29-15-178!\'", \'Comment 16: "{code:java}{code}{code:java}SELECT * FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate desc--SELECT * FROM [DHPlantStockBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate desc--SELECT * FROM [DHPlantWmsBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate descSELECT * FROM [DHPlantVCBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate desc--SELECT * FROM [DHPlantQAMBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate descSELECT * FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate desc{code}"\', \'Comment 17: "{code:java}SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'SELECT * FROM [DHPlantVCBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'SELECT * FROM [DHPlantPCSBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'SELECT * FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'SELECT * FROM [DHPlantWmsBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'SELECT * FROM [DHPlantQAMBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'{code}"\', \'Comment 18: "Hi AleksandraTracking the documents for this UL\', \'Comment 19: it wasn\\\'t done by two users (attached screen)I didn\\\'t find any DGS raised to fix this UL.What is the problem? Can you fix it? Will it happen again? What should we do to prevent it?Thank you!image-3!"\', "Comment 20: \'HiAny news?How long will it take to fix that? Do we need to wait for it happened again?Thank you\'", "Comment 21: \'Hi,The issue relates to recreated barcodes. Problematic barcodes are quite old", \'Comment 22: befor the version 8.3 has been upgraded.!image-2023-02-15-12-59-26-544.png|width=1540,height=110!Please\', "Comment 23: let me know if we should fix the information on the printout.Regards\'", "Comment 24: \'Hi,Do you need any further action from our side or shall we close this task?Regards\'", "Comment 25: \'Hi AleksandraThank you for this information.Is there anything you can do to not allow this happen again? Probably fix this this information?Thank you very much\'", "Comment 26: \'Hi![[email protected]]jesteśmy w stanie to jakoś globalnie fixnąć? :)\'", "Comment 27: \'[[email protected]] badamy możliwości\'", "Comment 28: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis how to prevent such situation.We are waiting for more details and will be back with further information as soon as possible.\'", "Comment 29: \'Podobna sytuacja dla 2 lotów z tego taska oba dotyczą tych dóch barcode :https://helpdesk.kotrak.com/browse/DGS-8728?filter=-1!image-2023-03-10-12-12-20-395.png!\'", "Comment 30: \'[[email protected]] czy te rozjechane stany pochodzą sprzed wersji 8.3?\'", "Comment 31: \'[[email protected]] Tak. Stock unit jest stworzony w styczniu 2022", "Comment 32: a oni mieli upgrade do wersji 7.9 w marcu 2022!image-2023-03-27-14-25-17-529.png!\'", "Comment 33: \'After the changes in version 8.3 the problem should no longer occurs. The barcode provided is from mid-September 2022!image-2023-04-19-12-53-10-450.png!and updates were done in November 2022.\']"]\nRelated Issues:\n[\'DGS-7646\', \'DGS-8728\']\n\n### End'} |
566 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8466\n\n### Instruction:\nChainge main, target and payer customer off SO-76/10/2022/V and ESI-3/11/2022/vexp from 7727 to 0674\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'SDNL-35552\'", "Comment 3: \'See also DGS-8431\'", "Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 5: \'Hello,Customer data changed as requested. Please", "Comment 6: verify and let us know if we can close this task.Regards!image-2023-02-07-10-21-27-262.png!!image-2023-02-07-10-21-44-034.png!\'", "Comment 7: \'Ticket can be closed\'", "Comment 8: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'} |
567 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8465\n\n### Instruction:\nMentioned recipe does not arrive in DHC. \r\n\r\nImport in DHC fails:\r\nObject reference not set to an instance of an object\r\n\r\nPlease verify why this happens. 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: \'In DHC this bestmix has no base item and no linked items also", "Comment 3: could you fixed the linking and resend recipe? !image-2023-02-02-15-19-05-263.png!\'", \'Comment 4: "I\\\'m not familiar with this\', \'Comment 5: I have asked the user if she is. I\\\'ll come back to you later."\', "Comment 6: \'The item is linked to another BestMix item.!afbeelding!\'", "Comment 7: \'!967242.PNG|thumbnail!\'", "Comment 8: \'Are you sure that this is correct ? !967242.PNG!\'", \'Comment 9: "select distinct (i.Code) from RecipeIngredients rijoin Items i on ri.ItemId=i.id where ri.RecipeId in (\\\'EBEA41EC-A0ED-40D4-B305-2025806C4EB9\\\',\\\'953BD597-2953-4D36-A5C6-25B4FD73989D\\\'\', \'Comment 10: \\\'1CF05321-0ACC-4AA1-9688-8D567D5D7D9E\\\')"\', "Comment 11: \'nutrietinty tez wszystkie sa\'", "Comment 12: \'This ticket can be closed", "Comment 13: it is solved.\']"]\nRelated Issues:\n[]\n\n### End'} |
568 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8464\n\n### Instruction:\nHello, \r\n\r\nthis seems to be simular issue as DGS-8443: A lot report in DHP has status in progress but should be closed: If I check the request log I see 7 messages send, including islastbatch message. If I check DHP then the Lot only has 4 batches registered: When I try to resend batchreports the system indicates the batch is finished: Please Check this, we miss finished product stock in our systems due to this bug\n\n### Response:\n["Comment 1: [\'!afbeelding!!afbeelding-1!!afbeelding-2!\'", "Comment 2: \'Same problem applies to PCS Lotnr: 305447", "Comment 3: 305384\'", "Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 5: \'Impacted lots:!image-2023-02-06-07-45-08-260.png!\'", "Comment 6: \'!image-2023-02-06-08-14-57-618.png!\'", "Comment 7: \'{code:java}Exception has been thrown by the target of an invocation. -> A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider", \'Comment 8: error: 40 - Could not open a connection to SQL Server) -> The network path was not found.An exception was thrown while activating Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.RegisterBatchReportCommandHandler -> Plant.Prod.BusinessLogic.Application.ProductionLots.TransactionalProductionLotService -> Plant.Prod.BusinessLogic.Application.OrderProduction.TransactionalOrderProductionSynchronizationService -> Plant.Prod.BusinessLogic.Infrastructure.Persistance.ProductionOrders.ProductionOrderRepository -> Plant.Prod.BusinessLogic.Domain.ProductionOrders.ProductionOrderFactory -> Kotrak.Common.Infrastructure.BarcodeGenerator.BarcodeGenerator -> λ:Kotrak.Common.Infrastructure.BarcodeGenerator.NumberToAlphaBarcodeGeneratorPolicy. -> A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', "Comment 9: error: 40 - Could not open a connection to SQL Server) -> The network path was not found.{code}\'", "Comment 10: \'!image-2023-02-06-08-26-15-292.png!!image-2023-02-06-08-33-57-988.png!\'", "Comment 11: \'!image-2023-02-06-08-54-48-536.png!*Production**!image-2023-02-06-08-56-41-333.png!**PCS**!image-2023-02-06-08-57-09-202.png!*\'", "Comment 12: \'!image-2023-02-06-09-00-20-054.png!!image-2023-02-06-09-01-02-612.png!!image-2023-02-06-09-01-20-182.png!\'", "Comment 13: \'Any update?\'", "Comment 14: \'Yes. For now we know the reason for all three PLR. As you can see below", \'Comment 15: there was network related issue with connection to SQL. We are working on a solutionAn exception was thrown while activating Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.RegisterBatchReportCommandHandler -> Plant.Prod.BusinessLogic.Application.ProductionLots.TransactionalProductionLotService -> Plant.Prod.BusinessLogic.Application.OrderProduction.TransactionalOrderProductionSynchronizationService -> Plant.Prod.BusinessLogic.Infrastructure.Persistance.ProductionOrders.ProductionOrderRepository -> Plant.Prod.BusinessLogic.Domain.ProductionOrders.ProductionOrderFactory -> Kotrak.Common.Infrastructure.BarcodeGenerator.BarcodeGenerator -> λ:Kotrak.Common.Infrastructure.BarcodeGenerator.NumberToAlphaBarcodeGeneratorPolicy. -> A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', "Comment 16: error: 40 - Could not open a connection to SQL Server) -> The network path was not found.\'", "Comment 17: \'I have resent messages. It looks good now.Please", "Comment 18: verify\'", "Comment 19: \'Oke", "Comment 20: thanks: Can you also check https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8443? same issue but then for location Nijkerk\'", "Comment 21: \'Yes", \'Comment 22: we are are working on it. But\', \'Comment 23: unfortunatelly\', "Comment 24: for Nijkerk the cause is different and now it is under dev verification.Can we close this task?Regards\'", "Comment 25: \'Yes you can close this task", "Comment 26: please make sure that ticket/fix will be visible in release notes of next version: otherwise we miss indication that it is fixed\'", "Comment 27: \'Dear Thomas,As I mentioned before", \'Comment 28: here it was caused by network / connection issue. Regarding task DGS-8443 we are working on it to diagnose what happened and let you know inDGS-8443.In that case\', "Comment 29: regarding Maasbracht I am closing this task.Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
569 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8463\n\n### Instruction:\nGood afternoon,\r\nplease, would you create an openings balance for item 0694 on plant Veghel with a quantity of 200 kg.\r\n\r\nThanks for support.\r\n\r\nRegards,\r\n\r\nGerard\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hello Gerard,The opening balance has been created. Please", "Comment 3: verify.Regards!image-2023-02-03-08-07-17-172.png!\'", "Comment 4: \'Hello Gerard,Can we close this task?Regards\'", "Comment 5: \'Hello Aleksandra,My apology", "Comment 6: that i forgot to send you an answer about this. But is correct.Please close this ticket.Have a nice weekend,Kind regards,Gerard\'", "Comment 7: \'Hello Gerard,Thank you for your information.Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
570 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8462\n\n### Instruction:\nHello,\r\n\r\nVehicle ticket for dispatch are not created: Application is receiving bulkdispatch messages from PCS: Please check what is going on. For location Utrecht is happens more often, service restart or something is usually the solution\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: \'Please try now\'", "Comment 3: \'wg logów tutaj był jakis problem o 5.17 wskazuje na jakies problemy z siecią ?!image-2023-02-02-13-35-22-850.png!\'", "Comment 4: \'Thanks\'", "Comment 5: \'May we close the task?\'", "Comment 6: \'Task can be closed\']"]\nRelated Issues:\n[]\n\n### End'} |
571 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8461\n\n### Instruction:\nIn the attachment we see an overview of S2P\'s that are archived. The rounds that are linked to it should be closed as well.\r\n\r\nCreating and archiving the S2P is te last step in the round process. Could you close all these rounds?\r\n\r\nNext to that we need to think about a structural approach for this. Can we automate it like this:\r\n* S2P for a specific round is archived manually by a user\r\n* The related round is automatically closed in the system\n\n### Response:\n["Comment 1: [\'[^Rounds to be closed.xlsx] _(60 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Do sprawdzenia excel i które z tych rund są do zamknięcia i można je zamknąć (przepływ do archiwum).Druga część to do obsłużenia to globalnie w systemie", "Comment 4: ale to też powiązane z podlinkowanymi taskami - do analizy.\'", "Comment 5: \'All of the indicated rounds are already closed\'", \'Comment 6: "It\\\'s related to other 2 tasks\', \'Comment 7: which should be considered with this one and we need to find best solution how to handle it globally.[https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7956]https://helpdesk.kotrak.com/browse/DHNLC-1147"\', "Comment 8: \'[^Closed runds.xlsx]\'", "Comment 9: \'Should we plan a discussion with some users to have this solved?\'", "Comment 10: \'Can be closed\']"]\nRelated Issues:\n[\'DGS-7956\']\n\n### End'} |
572 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8460\n\n### Instruction:\nGood morning,\r\n\r\nOur specials we book with the item code DIVO in the feed sale document.\r\nBecause we want to know what kind of feed the posting is, we give it a description.\r\nProblem is that this is not visible on the feedsale nor the financial statement.\r\n\r\nI will write an e-mail with printscreens.\r\n\n\n### Response:\n["Comment 1: [\'{color:black}Good morning,{color} {color:black}{color} {color:black}Our specials we book with the item code DIVO in the feed sale document.{color} {color:black}Because we want to know what kind of feed the posting is", "Comment 2: we give it a description.{color}{color:black}{color} !image001!{color:black}{color}{color:black}{color} {color:black}Problem is that this is not visible on the feedsale nor the financial statement.{color}{color:black}{color} !image002!{color:black}{color}{color:black}{color} {color:black}Can this be modified?{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} | {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image003!{color:blue}{color}{color:black} <[https://www.de-heus.nl/]>{color} | | *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} | {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | |{color:blue}{color} !image004!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} | |{color:blue}{color} !image006!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image007!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | \'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'Do sprawdzenia i ewentualnego poprawienia także procedury dotyczące wyciągania tych danych na wydruki FSKR_Printout_FS_TotalFeed_NAS\'", "Comment 5: \'Poprawiona procedura i select na dokumencie financial statement\'", \'Comment 6: "The feed table now shows the description and name of the item in the \\\'NAS\\\' sector as it works in other sectors"\', "Comment 7: \'{color:black}Dear Tomasz,{color} {color:black}{color} {color:black}This is not yet functional?{color} {color:black}See enclosed feed sale extract from Intense NAS just a moment ago.{color} {color:black}{color} {color:black}For the migration post it can be that this field wasn’t filled.{color} {color:black}I checked it for SI000037572", \'Comment 8: cause this is a posting made in Intense. Description is filled.{color}{color:black}{color} !image006!{color:black}{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:* Tomasz Zygoń (Jira) <[email protected]> *Verzonden:* dinsdag 7 februari 2023 10:42 *Aan:* Jong\', "Comment 9: Christine de <[email protected]> *Onderwerp:* DGS-8460 Description DIVO not visible in Feed Sale document | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | !image006-1![^Feed VD Berg koppel slacht.xlsx] _(13 kB)_!image007!\'", \'Comment 10: "What is a problem because i can\\\'t redo situation where description is not copied from feed to financial statementView from feed sale!image-2023-02-07-15-08-54-541.png!View from financial statement!image-2023-02-07-15-13-22-107.png!"\', "Comment 11: \'{color:black}Good morning Tomasz,{color} {color:black}{color} {color:black}We prefer a setting where our description is copied onto our FS.{color} {color:black}Is this not possible?{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:* Tomasz Zygoń (Jira) <[email protected]> *Verzonden:* dinsdag 7 februari 2023 15:17 *Aan:* Jong", "Comment 12: Christine de <[email protected]> *Onderwerp:* DGS-8460 Description DIVO not visible in Feed Sale document | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | !image006-2!!image007-1!!image006!!image007!\'", \'Comment 13: "Hello Christine,On Financial statement are presented values from Feed sale lines from field \\\'Description\\\'\', "Comment 14: it means that if you change field \'Description\' on Feed sale document", \'Comment 15: you will see it on Financial statement document also like on the screen below. Values are copied to FS\', \'Comment 16: so it looks good\', \'Comment 17: right?!image-2023-02-08-08-45-32-669.png!Regards"\', "Comment 18: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}When we modify description and it is visible on feed sale extract and financial statement all is good{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 8 februari 2023 08:49 *Aan:* Jong", "Comment 19: Christine de <[email protected]> *Onderwerp:* DGS-8460 Description DIVO not visible in Feed Sale document | *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* | !image006-3!!image006!!image007!\']"]\nRelated Issues:\n[]\n\n### End'} |
573 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8459\n\n### Instruction:\n!image-2023-02-02-11-10-51-390.png!\n\n### Response:\n[\'Comment 1: ["This value \\\'Totaal door u te betalen EUR\\\' should be always positive like a \\\'Totaal\\\' above?"\', "Comment 2: \'Indeed\'", "Comment 3: \'Is it relevant to all sectors for S2P printouts?\'", \'Comment 4: "Do zmiany na wydrukach Saldo to Pay (także nowych\', \'Comment 5: które są stworzone i w trakcie akceptacji)\', \'Comment 6: aby wartość \\\'Totaal door u te betalen EUR\\\' była zawsze wyświetlana jako dodatnia.!https://attachments.office.net/owa/damian.swistek%40kotrak.com/service.svc/s/GetAttachmentThumbnail?id=AAMkADY2ZTAxMzM3LTE0YjctNGI0Ni1hYjIxLWE3MDFjOTVkNmExNwBGAAAAAAA%2FcPjpt4lNRZFonusrO6C9BwA5bA29TyJrQIX6A6F8SkSqAAAAAAEJAAA5bA29TyJrQIX6A6F8SkSqAAS37XAJAAABEgAQADpxOtUHE69HhCtCVdopo1c%3D&thumbnailType=2&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IkQ4OThGN0RDMjk2ODQ1MDk1RUUwREZGQ0MzODBBOTM5NjUwNDNFNjQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiIySmozM0Nsb1JRbGU0Tl84dzRDcE9XVUVQbVEifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiNzQ1YWJkOWJmNWUxNGJhMWJkNjE5OTZmNzhmMzQzNGYiLCJzaWduaW5fc3RhdGUiOiJbXCJrbXNpXCJdIiwidmVyIjoiRXhjaGFuZ2UuQ2FsbGJhY2suVjEiLCJhcHBjdHhzZW5kZXIiOiJPd2FEb3dubG9hZEA5OGIwMzVmZi1iMTIxLTQ1OGItYTNmMC0zMjM1NGRiMWI3ODEiLCJpc3NyaW5nIjoiU0lQIiwiYXBwY3R4Ijoie1wibXNleGNocHJvdFwiOlwib3dhXCIsXCJwdWlkXCI6XCIxMTUzNzY1OTMyMzQ4MzE1MTQ3XCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIixcIm9pZFwiOlwiYjU1MGNmY2EtYjZhYS00NmFkLWFlYjAtZTllNjIyYTMyOTE2XCIsXCJwcmltYXJ5c2lkXCI6XCJTLTEtNS0yMS0zNjk5NTUyNDA4LTIxNDA2MTAxMy0yMzI0NTA4MTctMTMxMDk3OTRcIn0iLCJuYmYiOjE2NzUzMzY0ODQsImV4cCI6MTY3NTMzNzA4NCwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImhhcHAiOiJvd2EifQ.vi3s1cwR0sp_nHT4VSl7JBkFmYFEkdHjs7qh4RR6jtmY3jACh_PZcqdjzjOaw08wBcBzvZyPk62y8OZTDCn5GWtaOWEpbQgRsS49LzVEATJ-XqUpDABaS6vQb-3jfpo9L2AKzdZ_P8aTvhgihtoijrBwqE-FaZTaXnOGft2-qcrS7ISDUqTnTMfJRBuIoFqv5eLwMXC-OAFBqZbsCAYcYEZ6VFdu-GD8f4oaK90Pwr4bMT_yGjdtTp0bVM7I9Sl-zLm8-7rYDE_sXRklLZPkMvtQtChZ1LC4hrVQIyXeFF9fyiyeu2E4PAzaQzNc9jMkvS2AlhY7TbpRGpE5Az1iYg&X-OWA-CANARY=bF9w9Ol8Nkmp9r29KcE7SrCyhVAPBdsYVieOrdUWt0bGur9Y-jGXtOaeLqKdFyZZeIjFVZ4E8_I.&owa=outlook.office.com&scriptVer=20230120008.13&animation=true!"\', "Comment 7: \'Yes\'", "Comment 8: \'At this point. We have such a case that if the total value is greater than 0", \'Comment 9: we display inscription Total door u te betalen EUR + total value multipliedby (-1),in the second case\', \'Comment 10: if the value is lower\', "Comment 11: we display the inscription Total aan u overgemaakt EUR + total valueDo we need to remove this functionality and just showTotal door u te betalen EUR +total value\'", "Comment 12: \'Yes indeed", "Comment 13: we would like to see a positive number in both cases.\'", "Comment 14: \'We have made changes on test database after confirm that its ok", "Comment 15: we gonna upload it on production.\'", "Comment 16: \'It looks OK", "Comment 17: please move it to Production.\'", "Comment 18: \'Moved to production database.\'", "Comment 19: \'Tekst na podsumowaniu wydruku saldo to pay powinien być tekst taki jak był wcześniej w zależności od tego czy była to wartość większa czy mniejsza niż 0", "Comment 20: a sama wartość liczbowa powinna być zawsze ze znakiem plus.\']"]\nRelated Issues:\n[\'DGS-8326\']\n\n### End'} |
574 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8458\n\n### Instruction:\nCan you re-open round from customer 00129 Bartels Wintelre (round 1)? It is already archived, but I have a correction SR to be booked. \r\n\r\nS2P state is Entry. \r\n\r\nRound ID is 30372. \n\n### Response:\n["Comment 1: [\'Round is open again in Anja Verdam inbox.\']"]\nRelated Issues:\n[]\n\n### End'} |
575 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8457\n\n### Instruction:\nNew user account: Daan Aalbers\r\n\r\nBusiness Office / Administrator. Access to Nicole Inbox.\n\n### Response:\n["Comment 1: [\'Account created.\']"]\nRelated Issues:\n[]\n\n### End'} |
576 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8456\n\n### Instruction:\nWhen the full number on a PI created from a SR is changed somehow it changes the full number but not the round number. \r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'We fixed this issue in a test environment. In the DGS-8318 Round number of removed round - JIRA Kotrak S.A.you will find a description of the situation", "Comment 3: we are still waiting for confirmation. We have added an action that calculates round numbers on a round and updates all rounds related to a given customer.\'", "Comment 4: \'I am not sure what you need from us...\'", \'Comment 5: "In task [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8318]it\\\'s fixed and it\\\'s on test database. After tests and confirmation that it works properly in DGS-8318 we can close this task also."\', "Comment 6: \'DGS-8318 is approved.\']"]\nRelated Issues:\n[]\n\n### End'} |
577 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8455\n\n### Instruction:\nHello,\r\n\r\nI got a question from the business about wrong business partner data in DH CDN: I checked and didn\'t see a problem, but as you can see in both screenshots: There is a difference in the data presented between two users: How can this be solved? I suspect it being some caching issue or something but don\'t know how to solve\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: \'There is an difference in customer data between English and Dutch languages!image-2023-02-02-10-35-11-039.png!!image-2023-02-02-10-36-51-514.png!Data shown by DH CDN depends on Language you choose when log into application!image-2023-02-02-10-38-17-496.png!Please", "Comment 4: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?\'", \'Comment 5: "How it that possible? The display of data shouldn\\\'t depend on language setting?? Sorry but this isn;t a solution to the problem"\', "Comment 6: \'Adress data for customers (business parners) can be translated in DH CDN depending on choosen language. If data for selected language is gray then it came from ERPXL. If this data for choosen language is black then translation was created in DH CDN and can be modified by user.This is standard functionality provided by DH CDN.There is no tranlation data for customer (business parner) information in ERP XL.Please", "Comment 7: let me know if the answer is sufficient for you.\'", "Comment 8: \'Oke", \'Comment 9: so to solve this\', "Comment 10: I need to add translation? How to do this?\'", "Comment 11: \'Hello: How to fix this?\'", "Comment 12: \'After You log into DH CDN application and open selected business card information card!image-2023-02-03-08-05-09-856.png!You will have an opton to change language for translation!image-2023-02-03-08-06-06-719.png!As You can see in this case all data in usiness partner card are black... when there was english chosen tgose data were gray!image-2023-02-03-08-07-30-259.png!You can remove this translation using remove option!image-2023-02-03-08-08-06-043.png!or change it and save the changes using save option!image-2023-02-03-08-08-42-471.png!Please", "Comment 13: let me know if the answer is sufficient for you.\'", \'Comment 14: "I try to remove it\', \'Comment 15: but after save and re-opening the business partner\', \'Comment 16: it\\\'s still there"\', "Comment 17: \'can you trry?\'", "Comment 18: \'Data for Dutch translation should be ok right now please verify.!image-2023-02-03-10-42-18-829.png!\'", "Comment 19: \'Yes it is oke now", "Comment 20: I figured out how to adjust. Thanks\']"]\nRelated Issues:\n[]\n\n### End'} |
578 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8454\n\n### Instruction:\nHello,\r\n\r\nShipping Notice L000122318 isn\'t arriving at DHP Utrecht. It is in DHC, but somehow it is not coming through to the plant. This trip needs to departure today, so it is urgent. \r\nHope you can find the reason. \n\n### Response:\n["Comment 1: [\'Hello,We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'", "Comment 2: \'Hi Piotr", "Comment 3: the truck needs to leave within one hour. Please assist\'", "Comment 4: \'i am checking i will let you know.\'", "Comment 5: \' !screenshot-1! \'", "Comment 6: \'Related order is blocked in DHC SO000062704", "Comment 7: please resent this order.\'", "Comment 8: \'I have exported this order again. Please check? \'", "Comment 9: \'Yes", "Comment 10: !screenshot-2! I can see SN now in DHP.\'", "Comment 11: \'Great! Thanks a lot!\'", "Comment 12: \'You are welcome.\']"]\nRelated Issues:\n[]\n\n### End'} |
579 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8453\n\n### Instruction:\nWhen i put in description in the description this doesn\'t come on the invoice. Only the code name comes on the invoice. See appendix.\n\n### Response:\n["Comment 1: [\'!3v bv 1.PNG|thumbnail!!3v bv.PNG|thumbnail!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hello,Invoice printout doesn\\\'t come from Intense\', \'Comment 4: then we can\\\'t do this antyhing with invoice printout.Is this invoice printed from Milas or other system? I think there should be some changes in system where the invoice is printing.Regards"\', \'Comment 5: "It\\\'s a topic related to Milas\', \'Comment 6: so I close the task.!image-2023-02-15-13-26-47-563.png!"]\']\nRelated Issues:\n[]\n\n### End'} |
580 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8452\n\n### Instruction:\nHi, \r\n\r\nWhen I close JO 67/23/AY, costing for bulk code is wrong. While I check the raw material usage, raw material cost distribution is not equally. The things is not one or two raw materials. There is a lot. I do raise as P1 due to this JO in Jan 2023 and now we are closing month end. \n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'I have a problem with logging in", "Comment 4: can you release license for XL?Module Workstation license is not accessible. Program session will be blocked.\'", "Comment 5: \'We are doing now. Please try again\'", "Comment 6: \'it works thanks\'", "Comment 7: \'please exit the documents related to this job order !screenshot-1! ", "Comment 8: thank you.\'", "Comment 9: \'Already exit\'", "Comment 10: \'The solution is to unpost the related documents for the problematic codes in relation to the delivery. !screenshot-2! And the execution of the cost repair procedure for the delivery.The problem is due to the incorrect value of the cost which e.g. for 1113050 should be 709697,43 with price 1340 and the cost itself comes out that much.\'", "Comment 11: \'klient wybrał opcję KK i poprawy dokumentu IR-{code:java}select TrE_KsiegowaNetto,TrE_Pozycja,* from cdn.TraElem where Tre_GIDTyp=1616 AND Tre_GIDNumer=2574917 and TrE_Pozycja in(2,6,7,8,9,10,11,18,19,20,21,22,23,24)select TrS_KosztKsiegowy,TrS_GIDLp,* from cdn.traselem where Trs_GIDTyp=1616 AND Trs_GIDNumer=2574917 and TrS_GIDLp in(2,6,7,8,9,10,11,18,19,20,21,22,23,24){code}Poprawa wartości dla dokumentu jak wyżej i wygenerowanie dokumentów KK dla pozycji.\'", \'Comment 12: "Please verify\', \'Comment 13: CC\\\'s documents have been generated: !screenshot-3! Correction for RW+ also after closed JO. !screenshot-4! "\', "Comment 14: \'We have been fixed all the related documents. You can close this ticket. \'", "Comment 15: \'Thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'} |
581 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8451\n\n### Instruction:\nIn he financial statement van Odink stand none document nr. under feed.\r\nCan you add this?\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", \'Comment 3: "In addition. There are Document numbers for all these postings in the system\', \'Comment 4: however they don\\\'t appear on the printout."\', "Comment 5: \'We fixed it.!image-2023-02-02-10-24-14-529.png!\']"]\nRelated Issues:\n[]\n\n### End'} |
582 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8450\n\n### Instruction:\nWe have problem in stock for item SUR7462-P-MD-S25, 0871141222007, produced 8695kg and was used 8695kg, but we still have 1000kg in stock. We checked on stock fisically and we don\'t have item anymore and any stocktaking was done for the item. \r\n\r\nCould you check why we still have stock for this item if was loaded?\r\n\r\nThank you.\n\n### Response:\n[\'Comment 1: [" !screenshot-1! {code:java}SELECT created,event,EventType,Username FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots] where AggregateId=\\\'8F626584-F9D7-4354-9239-FEC19B8D0FE7\\\' order by created SELECT TOP (1000) [Id] ,[Created] ,[AggregateType] ,[AggregateId] ,[Event] ,[EventType] ,[UserId] ,[UserName] ,[CorrelationId] FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits] where AggregateId=\\\'8B7C9DA6-A0D6-4856-8109-7D94C9CDC3D5\\\' order by Created desc select * FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where DeliveryId=\\\'E78D4B86-E871-4EF0-AED7-B4838D90A531\\\' select * FROM [DHPlantStockBusinessLogicMain].[dbo].[Deliveries] where SourceDocumentId=\\\'8F626584-F9D7-4354-9239-FEC19B8D0FE7\\\' select * FROM [DHPlantStockBusinessLogicMain].[dbo].[ProductionLots] where LotNumber=\\\'0871141222007\\\'{code}!image-2023-02-03-09-29-57-998! !image-2023-02-03-09-30-14-753!"\', "Comment 2: \'Stand up - ustalenia.\\\\r\'", "Comment 3: \'!ByCorrelationId! [^DGS-8450_queries.sql] !ProductionLotQuantityChangedEvent! !StockUnitQuantityChangedEvent! !StockUnitReleases!\'", \'Comment 4: "Przyczyną problemu jest równoległa obsługa w serwisie StockEngine dwóch zdarzeń dotyczących tego samego StockUnit\\\'a:1. rejestracja przyjęcia pakowanego z produkcji przez użytkownika (obsługa żądania API z aplikacji Web) - CorrelationId =7BAED985-27A5-4A0A-89FF-3D64BE0046F12. rejestracja kolejnego dozowania do produkcji przez PCS (obsługa zdarzenia z serwisu PCS) - CorrelationId = B0029C71-D2F0-492C-860D-F3307801CFB7Oba procesy pobrały StockUnita z ilością3037.598 kg.Przyjęcie palety powinno zmniejszyć stan o 1000 kg.Dozowanie powinno zwiększyć stan produkcji o 36,5 kg.Po wykonaniu obu operacji stan powinien wynosić 2074.098 kg.Ponieważ procesy wykonywały się równolegle\', \'Comment 5: drugi proces nadpisał zmiany wykonane przez pierwszy proces i stan wynosił3074.098 kg.W taki sposób powstało nadmiarowe 1000 kg stanu.Rozwiązaniem problemu mogłoby być zaimplementowanie obsługi konkurencyjności przy zapisie agregatu StockUnit\\\'a.!image-2023-02-21-15-15-08-692.png!"\', "Comment 6: \'[[email protected]] dzięki!\'", "Comment 7: \'[[email protected]]The reason for this error in quantity was parallel processing both of WO(IP) and registration of dosing by the PCS system. Those two activities were performed in the same second.The best way to solve this problem is to introduce concurrency in DHP both during the registration of information from PCS and performing intake from production on WO(IP).I raised the GDC-849 to implement this change in order to avoid such issues in the future", "Comment 8: I will discuss it with Theo. Please follow the GDC ticket in order to by updated on the current status of the solution.\'", "Comment 9: \'Hello", "Comment 10: as it was written in the last comment GDC has been created GDC-849.This issue has been closed.\']"]\nRelated Issues:\n[\'DGS-8380\', \'DGS-8715\']\n\n### End'} |
583 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8449\n\n### Instruction:\nPlease re-open round B002601/0010/0001\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 Active right now.Regards"]\']\nRelated Issues:\n[]\n\n### End'} |
584 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8448\n\n### Instruction:\nI notice that I can\'t see Matteo Minnen\'s inbox and he can\'t see mine. For Koen Huibers\' inbox this is already (and he can already see Matteo\'s). Can you add this for me?\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: "I added Matteo\\\'s inbox to Koen and steffen"]\']\nRelated Issues:\n[]\n\n### End'} |
585 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8447\n\n### Instruction:\nPlease help to check this case and solving in Hau Giang Plant -0434.\r\n\r\nPLR 4341180123042 could not be found in the Production Report module . But release to stock with stock unit status In progress . Please check and clear this stock unit . Thank u.\r\n\n\n### Response:\n["Comment 1: [\'!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-02-01-10-00-41-438.png!!image-2023-02-01-10-00-55-483.png!\'", \'Comment 4: "Hello,How is it possible that stock unit has been created from source document that do not exist? Wasn\\\'t this PLR deleted?Please\', \'Comment 5: try to do inventory on this stock unit and let us know.Regards"\', \'Comment 6: "Hi Aleksandra Przybyłek .That\\\'s right. Maybe the user deleted this PLR . Please help clear this stock unit . Thank u."\', \'Comment 7: "{code:java}UPDATE DSET Status = 2\', \'Comment 8: Quantity = 0\', \'Comment 9: ExpiryDate = GETDATE()FROM DHPlantStockBusinessLogicMain.dbo.Deliveries DLEFT JOIN DHPlantStockBusinessLogicMain.dbo.StockUnits S ON S.DeliveryId = D.IdWHERE D.SourceDocumentId IN (\\\'8F261A64-6EE4-4823-AEA3-0426C01090A8\\\')UPDATE SSET Quantity=0,Quantityonhand = 0,logisticstatus=8FROM DHPlantStockBusinessLogicMain.dbo.Deliveries DLEFT JOIN DHPlantStockBusinessLogicMain.dbo.StockUnits S ON S.DeliveryId = D.IdWHERE D.SourceDocumentId IN (\\\'8F261A64-6EE4-4823-AEA3-0426C01090A8\\\'){code}"\', "Comment 10: \'Hi,Stock and deliveries have been updated.Please", "Comment 11: verify.Regards\'", "Comment 12: \'Thanks you . You can do close this ticket.\']"]\nRelated Issues:\n[]\n\n### End'} |
586 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8446\n\n### Instruction:\nplease set ID 92117 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: \'This is the wrong number; please set Srbe/1757 back to entry\'", "Comment 3: \'Hello,SRBe/1757 is now in Entry again.Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
587 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8445\n\n### Instruction:\nGoodmorning,\r\n\r\nplease, would you create an openings balance for item: 303921-Z20 with a quantity of 10 kg and an openings balance for item: 087240-Z20 with also a quantity of 10 kg. Both items on plant Andel.\r\n\r\nThanks for support,\r\n\r\nKind regards,\r\n\r\nGerard Geerts\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 Gerard,Opening balance for item087240-Z20 has been created. However", "Comment 3: there is no item like303921-Z20 in database. Please create item and let me know to process further.Regards!image-2023-02-01-12-19-53-594.png!\'", "Comment 4: \'Dear Aleksandra,sorry about my late reaction on this serviceticket.About the missing item", "Comment 5: I asked the person whose responsible for this.After that I asked you to create an openings balance.Regards,Gerard\'", "Comment 6: \'Dear Aleksandra,it should be an openings balance for item: 303921-Z20 Geurts on plant Andel.Regards,Gerard \'", "Comment 7: \'Dear Gerard,But there is still not such item in DB. You need to create it in ERP and send do DHP", "Comment 8: then I could create opening balance for this itemRegards!image-2023-02-03-07-32-39-369.png!\'", "Comment 9: \'The same in DHC:!image-2023-02-03-07-41-30-462.png!\'", "Comment 10: \'Hello Gerard,Any feedback? I can see this item has been sent to DHC. Should we create an opening balance for item303921-Z20?Regards\'", "Comment 11: \'Good morning Aleksandra,the item is also available in DHP.One moment", "Comment 12: i will aksed my collegue.Kind regards,Gerard\'", "Comment 13: \'Hello Alexandra,Please", "Comment 14: create an opningsbalance with 10 kg for itemcode: 303921-Z20-Geurts on plant Andel? Regards,Gerard!image!\'", "Comment 15: \'Dear Gerard,Should it be pallet or bulk? As in Stock Units there are both with ending:-Z20-Geurts!image-2023-02-22-17-20-49-445.png!Regards\'", "Comment 16: \'Goodmorning Aleksandra,The printscreen shows not the right item?It should be the item: 303921-Z20-Geurts.Regards,Gerard\'", "Comment 17: \'Good afternoon Gerard,My question was what settlement type shoud be defined to303921-Z20-Geurts.: bulk or pallet?Regards,Aleksandra\'", \'Comment 18: \\\'Hello Aleksandra,"pallet" please.Regards,Gerard\\\'\', "Comment 19: \'Dear Gerard,The second Opening Balance is ready.!image-2023-02-23-14-58-08-263.png!Please", "Comment 20: verify.Regards,Aleksandra\'", \'Comment 21: "Dear Aleksandra,Thanks for support.Verify is done. It\\\'s oké!Please close this service ticket?Have a nice evening.Kind regards,Gerard"\', "Comment 22: \'Thank you. The same to you", \'Comment 23: Gerard\', "Comment 24: have a nice eveningKind Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
588 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8444\n\n### Instruction:\nPlease check VT-619/1/23: Quantities are consumed on item history, but still I cannot close VT due to missing stock. \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: \'{code:java}Cannot complete bulk when requested quantity greater than reserved quantity event automatic stocktaking is generated. -> CannotCompleteBulkWhenRequestedQuantityGraterThanReservedQuantityEvenAutomaticStocktakingIsGeneratedMessage{code}!image-2023-02-01-14-40-57-943!\'", "Comment 4: \'I forced a status change for VT please check.Are there other cases like this or is it an incident?\'", "Comment 5: \'It seems like an incident. thanks for solving. You can close the issue\']"]\nRelated Issues:\n[]\n\n### End'} |
589 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8443\n\n### Instruction:\nHello, \r\n\r\nlot report 0061270123041 is in status \'in progress\'. But there are two batches missing. I found those in the APIrequest log, but when I try to reprocess those, I got the message that the lot is already finished. The 2 missing batchreport xmls are added to the ticket. Can you investigate and make sure these are registered correctly? because produced quantity is not send to ERP and is leading to problems.\n\n### Response:\n["Comment 1: [\'[^batch 923265.xml] _(10 kB)_[^last batch 923265.xml] _(0,7 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'*STOCK - 24 ELEMENTY*!image-2023-02-01-13-59-43-276.png!!image-2023-02-01-14-00-01-688.png!\'", "Comment 4: \'*PROD - 24 ELELENTY**!image-2023-02-01-14-01-07-721.png!*!image-2023-02-01-14-03-11-960.png!\'", "Comment 5: \'*PCS - 24 ELEMENTY**!image-2023-02-01-14-04-45-160.png!**!image-2023-02-01-14-05-40-804.png!*\'", "Comment 6: \'PCS QUANTITIES!image-2023-02-01-14-12-06-295.png!\'", "Comment 7: \'W PCS ma status finished a w Prod in progress\'", \'Comment 8: \\\'Log z modułu Stock:{code:java}2023-01-27 16:04:48 (6a6f60a6-8463-4cfc-8fe3-fc95f785728d/Plant.Stock.BusinessLogic/DHVD01AP181/13608/12) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type "Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.ProductionBatchReportRegisteredEvent"\', "Comment 9: retry no 1Kotrak.Common.Application.Exceptions.BusinessLogicException: Production lot with id 2c1d1b84-8cc8-4c2d-9f44-c436d8c9c73a was not found ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: ProductionLotNotFoundMessage at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.RegisterRawMaterialsUsage(RegisterRawMaterialsUsageActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 0 at Plant.Stock.BusinessLogic.Application.ProductionLots.CommandHandlers.RegisterBatchReportCommandHandler.Handle(RegisterBatchReportCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\RegisterBatchReportCommandHandler.cs:line 26 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 Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message) --- End of inner exception stack trace ---{code}\'", "Comment 10: \'Logi z Proda z mniej więcej tej godziny{code:java}2023-01-27 16:00:24 (/Plant.Prod.BusinessLogic/DHVD01AP181/6224/8) [Error] Plant.Prod.BusinessLogic.Infrastructure.Tasks.TryConfirmProductionLotTask - An error occurred while trying to confirm automatically production lot with id [38bcbd76-a671-4926-b7cb-facbaa6f55ec].Plant.Prod.BusinessLogic.DomainAbstractions.ProductionLots.DomainExceptions.ProductionLotConfirmException: Validation failed: -- ProductionLotQuantityIsNegativeOrZeroMessage at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.ValidateConfirmation(ProductionLot productionLot", \'Comment 11: ConfirmProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 111 at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.ConfirmProductionLotWithStockEngineApiCall(ProductionLot productionLot\', \'Comment 12: ConfirmProductionLotActionData data\', \'Comment 13: Func`3 stockEngineApiCall) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 123 at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.ConfirmProductionLotAutomatically(ConfirmProductionLotDto dto) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 371 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Plant.Prod.BusinessLogic.Infrastructure.Tasks.TryConfirmProductionLotTask.TryConfirmProductionLot(Guid productionLotId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Tasks\\\\\\\\TryConfirmProductionLotTask.cs:line 1122023-01-27 16:14:48 (null/Plant.Prod.BusinessLogic/DHVD01AP181/6224/7) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[SynchronizeShippingNoticeCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ShippingNotices.Commands.SynchronizeShippingNoticeCommand) methodKotrak.Common.Application.Exceptions.BusinessLogicException: Some order elements with keys (69a9e395-84b3-4d69-a814-a6e757445584\', \'Comment 14: 3)\', \'Comment 15: (69a9e395-84b3-4d69-a814-a6e757445584\', "Comment 16: 1) were not found. ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: ProductionOrderSomeOrderElementsWereNotFoundMessage at Plant.Prod.BusinessLogic.Application.ShippingNotices.ShippingNoticeService.ThrowIfAnyOrderElementWasNotFound(IEnumerable`1 keys) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ShippingNotices\\\\\\\\ShippingNoticeService.cs:line 117 at Plant.Prod.BusinessLogic.Application.ShippingNotices.ShippingNoticeService.AssertReferences(ShippingNoticeData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ShippingNotices\\\\\\\\ShippingNoticeService.cs:line 88 at Plant.Prod.BusinessLogic.Application.ShippingNotices.ShippingNoticeService.Create(ShippingNoticeData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ShippingNotices\\\\\\\\ShippingNoticeService.cs:line 44 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) --- End of inner exception stack trace ---{code}\'", "Comment 17: \'W intercontext nie ma śladu:!image-2023-02-06-11-45-38-264.png!!image-2023-02-06-11-45-54-305.png!\'", \'Comment 18: \\\'h2. Przeanalizowałem dogłębnie temat i mam parę wniosków:{code:java}SELECT * FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[Errors] where CreateDate between \\\\\\\'2023-01-27 16:00:48.8833333\\\\\\\' and \\\\\\\'2023-01-27 17:30:48.8833333\\\\\\\' and Message like \\\\\\\'%prod%\\\\\\\'SELECT * FROM [DHPlantStockBusinessLogicIntercontext].[dbo].[Errors] where CreateDate between \\\\\\\'2023-01-27 16:00:48.8833333\\\\\\\' and \\\\\\\'2023-01-27 17:30:48.8833333\\\\\\\' and Message like \\\\\\\'%prod%\\\\\\\'SELECT * FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[Errors] where CreateDate between \\\\\\\'2023-01-27 16:00:48.8833333\\\\\\\' and \\\\\\\'2023-01-27 17:30:48.8833333\\\\\\\' and Message like \\\\\\\'%prod%\\\\\\\'SELECT Created,EventType FROM [DHPlantPCSBusinessLogicEvents].[dbo].[ProductionLots] p where AggregateId = \\\\\\\'2C1D1B84-8CC8-4C2D-9F44-C436D8C9C73A\\\\\\\' ORDER BY Created DESC SELECT Created,EventType FROM [DHPlantStockBusinessLogicEvents].[dbo].[ProductionLots] p where AggregateId = \\\\\\\'2C1D1B84-8CC8-4C2D-9F44-C436D8C9C73A\\\\\\\' ORDER BY Created DESCSELECT Created,EventType FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots] p where AggregateId = \\\\\\\'2C1D1B84-8CC8-4C2D-9F44-C436D8C9C73A\\\\\\\' ORDER BY Created DESC{code}Po eventach widać że Event:Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.ProductionBatchReportRegisteredEventDla tego missing batcha (3 i 4) pojawił się *{color:#de350b}dopiero po około 1h19m opóźnienia.{color}**Batch numer dwa czas:2023-01-27 16:11:47.7615228**Batch numer trzy czas:2023-01-27 17:30:08.4554092**Batch numer cztery czas:2023-01-27 17:30:09.3331415**Finish production odrazu po bo 4 batch ma w message: "Last batch =1": 2023-01-27 17:30:10.0259866*W prodzie ostatni event to event z godziny:2023-01-27 16:11:48.0798563 Plant.Prod.BusinessLogic.DomainAbstractions.ProductionLots.DomainEvents.ProductionLotElementsChangedEventCzyli poleciał update na elementach zgodnie z tym co zostało wysłane w batchu numer dwa.!image-2023-02-24-11-15-14-278.png!To screen potwierdzający ową sytuację. *Te 3 wyniki to wyniki z 3 ostatnich selectów*.Co ciekawe w żadnej tabeli intercontextu (stock\', \'Comment 19: prod\', \'Comment 20: pcs) *nie mam żadnych errorów z tegowego czasu (tak samo jak szukam po pcslot albo po productionlotid)*.---------------------------------------------------------Przejdźmy zatem do dbo.WebApiRequestLog:!image-2023-02-24-11-17-21-409.png!Wszystkie batche które dostaliśmy z PCS-a zostały zaakceptowane - oprócz tych które próbował wysłać Thomas - te nie przeszły\', \'Comment 21: *gdyż ten Lot już jest finished z odpowiednią ilością w PCS*.Problem jest taki że ta ilość nie zgadza się z tym co mamy w Stocku i w Prod.Różnica jest jedynie o właśnie tego Batcha numer trzy:{code:java}<ProductionReportToERP xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchReports> <BatchReport> <ProductionLineId>1</ProductionLineId> <PcsLotId>923265</PcsLotId> <PcsBatchId>2631381</PcsBatchId> <RecipeId>30313</RecipeId> <QuantityKg>6002.337</QuantityKg> <StartBatchMixing>2023-01-27T15:40:24</StartBatchMixing> <FinishBatchMixing>2023-01-27T16:12:22</FinishBatchMixing> <IsBrokenBatch>false</IsBrokenBatch> <IsLastBatch>false</IsLastBatch> <LOTReportType>1</LOTReportType> <ItemCode>163420</ItemCode> <Ingredients> <Ingredient> <ItemCode>0112</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>17.926</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>29.694</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0233</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>90.09</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0153</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>119.2</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0307</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>546</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0010</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>179.1</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0362</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>18.752</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>132.057</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>52.091</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0356</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>6.594</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>203.906</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0378</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>16.312</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>529.188</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0041</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>360.104</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>981.996</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0001</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>1451.2</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0001</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>588.2</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0642</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>6.176</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>13.621</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>26.672</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>55.289</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>109.843</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>211.28</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0831</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>0.076</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>0.95</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>7.982</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0631</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>6.002</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0851</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>1.227</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0684</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>0.088</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>0.376</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>2.895</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>9.259</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0839</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>14.462</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0672</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>6.009</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0640</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>38.99</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0718</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>0.025</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>0.124</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>0.534</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>4.869</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0773</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>14.981</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0845</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>0.19</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>3.81</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0989</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>24</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0195</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>3.54</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>12.916</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>30.643</QuantityKg> </Intake> </Intakes> </Ingredient> <Ingredient> <ItemCode>0204</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>3.689</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>69.411</QuantityKg> </Intake> </Intakes> </Ingredient> </Ingredients> </BatchReport> </BatchReports></ProductionReportToERP>{code}*Który to w żaden sposób nie różni sie od pozostałych.*No i oczywiście o batcha numer cztery:{code:java}<ProductionReportToERP xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchReports> <BatchReport> <ProductionLineId>1</ProductionLineId> <PcsLotId>923265</PcsLotId> <PcsBatchId>1</PcsBatchId> <RecipeId>30313</RecipeId> <QuantityKg>0.01</QuantityKg> <StartBatchMixing>2023-01-27T16:13:33</StartBatchMixing> <FinishBatchMixing>2023-01-27T16:13:33</FinishBatchMixing> <IsBrokenBatch>false</IsBrokenBatch> <IsLastBatch>true</IsLastBatch> <LOTReportType>1</LOTReportType> <ItemCode>163420</ItemCode> <Ingredients /> </BatchReport> </BatchReports></ProductionReportToERP>{code}Mam z tym tematem problem\', \'Comment 22: gdyż na początku myślałem że po prostu zmienie status w PCS i ponownie dośle te batche\', \'Comment 23: ale wtedy ta ilość quantity także podniesie się w PCS i będzie rozjazd pomiędzy tym co jest w PCS\', \'Comment 24: a tym co Prod/Stock (prawdopodobnie wgl messege nie doleci\', \'Comment 25: gdyż to quantity będzie mu się nie zgadzać i walidacja tego nie puści).*Obstawiam że po prostu że moduł PCS musiał być w tym momencie mega obciążony\', \'Comment 26: gdyż nie jest to normalne że event batcha wskakuje dopiero po 1h19m.*Tylko nie mam zielonego pojęcia dlaczego te dwa missing batche w żaden sposób nie poleciały do Prod/Stocka i to quantity sie nie zmieniło(?).Analizowałem też Event Viewera i nie widzę żadnych blockerów w tamtym okresie\', \'Comment 27: tylko informacje ale w zupełnie innym temacie.Request o pomoc(flag): [[email protected]]\', \'Comment 28: [[email protected]]*UPDATE:*{color:#4c9aff}*Wpadłem na pomysł żeby po prostu wysłać ten event z trzecim batchem na kolejki Prod i SE.*{color}{color:#4c9aff}*Powinno zupdejtować ilość w tych dwóch modułach\', "Comment 29: no i jeszcze wysłać ten event Finishproduction i powinnien być w prodzie jako finished.*{color}\'", "Comment 30: \'ta dam!image-2023-02-24-13-28-58-935.png|width=1035,height=361!!image-2023-02-24-13-30-34-988.png!\'", "Comment 31: \'No i mówiłam już Gedeonowi", "Comment 32: że w Nijkerk to zaczyna być repetitive issuehttps://helpdesk.kotrak.com/browse/DGS-8604\'", "Comment 33: \'Hello any update? I have a new example: batch report is accepted according to pcsbusinesslogic table", \'Comment 34: but not visible in DHP. if I try to resend xml\', \'Comment 35: there is a message that the lot report is finished\', \'Comment 36: MEssage:<ProductionReportToERP xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchReports> <BatchReport> <ProductionLineId>1</ProductionLineId> <PcsLotId>928417</PcsLotId> <PcsBatchId>2650039</PcsBatchId> <RecipeId>17894</RecipeId> <QuantityKg>9980</QuantityKg> <StartBatchMixing>2023-02-23T07:35:37</StartBatchMixing> <FinishBatchMixing>2023-02-23T10:48:49</FinishBatchMixing> <IsBrokenBatch>false</IsBrokenBatch> <IsLastBatch>false</IsLastBatch> <LOTReportType>1</LOTReportType> <ItemCode>169123-Z20</ItemCode> <Ingredients> <Ingredient> <ItemCode>169123</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>5000.659</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil="true" /> <QuantityKg>4979.341</QuantityKg> </Intake> </Intakes> </Ingredient> </Ingredients> </BatchReport> </BatchReports></ProductionReportToERP>\\\'\', "Comment 37: \'Hi Thomas,0061270123041 is confirmed now", "Comment 38: however we are investigating why this happened.Regards\'", "Comment 39: \'Dear Thomas,To confirm0061270123041 we needed to resend event to Prod and Stock module. We tried also to diagnose what caused the issue.For now", \'Comment 40: we have spent 6,5 h in this task. In the mean time\', \'Comment 41: the same issue in the same plant - Nijkerk reoccured under:DGS-8604. As it seemed to be repetitive\', \'Comment 42: I suggest raising RCA task for this issue.Please\', "Comment 43: let me know if you agree for RCA task or shall we investigate in current DGS-8443 task.Regards\'", "Comment 44: \'Agreed with RCA task\'", "Comment 45: \'Thank you. RCA task is underDGS-8686. Please", "Comment 46: confirm if you have access.\'", "Comment 47: \'I have\'", "Comment 48: \'Great. In that case I am closing this task.Regards\']"]\nRelated Issues:\n[\'DGS-8686\']\n\n### End'} |
590 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8442\n\n### Instruction:\nI cannot sort by delivery date on a financial statement\r\n\r\nI would like to be able to sort all the feed from old to nwe\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: "Hello,We can do it globally for Financial statement printout. It means that always lines will be sorted from old to new by \\\'Delivery date\\\'.Should it be applied only in NAS sector and for section Feed or for all sections (Calves\', \'Comment 4: Feed\', \'Comment 5: Slaughtery\', \'Comment 6: Expenses)?!image-2023-02-02-10-38-04-884.png!"\', "Comment 7: \'Yes please", "Comment 8: do it for all sectors in all categories.\'", "Comment 9: \'Done for all sectors for both database and all categories.\'", "Comment 10: \'Can be closed.\'", "Comment 11: \'We just created an FS and the delivery dates are all intertwined.It should be sorted on date", "Comment 12: now it is sorted only on the first number of the date.!image-1!\'", \'Comment 13: "FS printouts in all sectors have been changed\', \'Comment 14: now all lines in all categories are sorted by \\\'Delivery date\\\' asceding like on screen below.!image-2023-02-06-15-05-05-767.png!Done on test and production database.Regards"]\']\nRelated Issues:\n[]\n\n### End'} |
591 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8441\n\n### Instruction:\nWe need to migrate some missing AS/400 date for two LAS customers\n\n### Response:\n["Comment 1: [\'[^AA - LAS_Migration_PURCHASEINVOICE_workfile_003651+006514.xlsx] _(140 kB)_[^AA - LAS_Migration_SALESINVOICE_workfile_003651+006514.xlsx] _(621 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "[[email protected]],all lines have been migrated to Intense. You can feel free to check the data. I\\\'m waiting for your feedback.Best regards,Grzegorz"\', "Comment 4: \'Done.\'", \'Comment 5: "Ok thank you for respone. I\\\'m closing the task."]\']\nRelated Issues:\n[]\n\n### End'} |
592 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8440\n\n### Instruction:\nHi\r\nUrgent task 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: \'Proszę o wskazanie osoby dla której występuje problem", "Comment 4: oraz przykładowej listy płac\'", "Comment 5: \'!image-1!\'", "Comment 6: \'[^KUP.docx]\'", "Comment 7: \'W załączniku wyjaśnienia[^KUP.docx]\'", "Comment 8: \'Czy temat można uznać za zakończony?\'", "Comment 9: \'Myślę", "Comment 10: że możemy zamknąć.\']"]\nRelated Issues:\n[]\n\n### End'} |
593 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8439\n\n### Instruction:\nplease remove the documents attached becasue they have zero quantity and stopping us from progressing in certain processes\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: \'!image-2023-01-31-16-34-42-373.png!\'", "Comment 4: \'TrN_GIDNumer=437604,TrN_GIDNumer=412473-- spinacz elementów por\'", "Comment 5: \'select cdn.NazwaObiektu(trn_gidtyp,trn_gidnumer,1,2),* from cdn.tranag where trn_gidtyp=1497 and trn_trnrok=2022 and trn_stan in (0,1,2)\'", "Comment 6: \'select cdn.NazwaObiektu(trn_gidtyp,trn_gidnumer,1,2),trn_gidnumer,TrN_SpiNumer,TrN_ZwrNumer,trs_gidnumer,trs_spinumer,trs_spityp,trs_zwrnumer,trs_zwrtyp,* from cdn.tranag join cdn.traselem on trs_gidnumer=trn_gidnumerwhere (trn_gidtyp in (1497) and trn_trnrok=2022 and trn_stan in (0,1,2)) or trs_spinumer in (412217,412232,412241,367362,367361,367360,462425)\'", "Comment 7: \'Document was removed", \'Comment 8: it looked like some strange ERP XL error\', "Comment 9: I verified before if the dociment are not related to any other clip.Please verify and let me know if we may close the task.\'", "Comment 10: \'please close\']"]\nRelated Issues:\n[]\n\n### End'} |
594 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8438\n\n### Instruction:\nOrderChangedMessage: Id=1c42acd1-d8ea-428f-8f5a-606b79537f88 DocumentNo=\'SO000060938\' DocNumeratorYear=2023 DocNumeratorMonth=1 DocNumeratorNumber=12026 DocNumeratorSeries= OrderType=2\r\nValidation failed for one or more entities. See \'EntityValidationErrors\' property for more details.The validation error are: [Code - Value is required]\r\n\r\nThese are the details from the communication log. Can you please investigate and explain what is wrong?\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: \' !screenshot-1! !screenshot-2! Inny bez tego błedu nie pustą sekcję Silos !screenshot-3! \'", "Comment 3: \'Those orders with errors have the silos section filled in: !screenshot-4! Can you check if these orders have the correct data sent from the erp?\'", "Comment 4: \'Hi Piotr", \'Comment 5: thanks! I deleted the silo info in ERP for the order and the order is now in DHC. Not yet in DHP by the way. Can you check this as well\', "Comment 6: or do I need to be more patient for this?\'", \'Comment 7: "In my opinion import of order shouldn\\\'t fail in DHC when there is no silo information. But this I will discuss with Thomas Dankers and ask him to raise a GDC for it. For now my concern is that this order goes correctly to the plant"\', \'Comment 8: "Ah\', \'Comment 9: the order is in DHP as well. I was not being impatient but didn\\\'t change my filter.You can close this request."\', "Comment 10: \'Thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'} |
595 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8437\n\n### Instruction:\nThis revenue does not come in financial statement\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: "Hello,I see that is an issue because we\\\'re showing documents PI when Reference is filled. On this document field is empty.!image-2023-01-31-15-43-10-676.png!Why this field is empty? Is there any reason why this field is empty?For this case filling field \\\'Reference\\\' will resolve issue\', \'Comment 4: however there are some inaccuracies here between Round and Financial statement which we can also adjust.Please inform us about \\\'Reference\\\' on PI invoices."\', "Comment 5: \'Is there needed any work in this task or could we close the task?\'", "Comment 6: \'[[email protected]]could you confirm?\'", "Comment 7: \'L999999 has been filled in as a Reference.Confirmed that can be closed.\']"]\nRelated Issues:\n[\'DGS-8425\']\n\n### End'} |
596 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8436\n\n### Instruction:\nI get an error when archiving\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,Did you get any error message from Intense when you try to send document to \\\'Archive\\\'? If yes\', \'Comment 4: please attach a screen of message.Regards"\', "Comment 5: \'Document is in archive state so you handled it", "Comment 6: can i close this task or you have any question?\'", "Comment 7: \'Could we close the task?\'", "Comment 8: \'Yes\']"]\nRelated Issues:\n[]\n\n### End'} |
597 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8435\n\n### Instruction:\nHi\r\nW tym tygodniu mamy już 2 przypadki, w których mamy rozbieżność na pozycjach vt w dhp i w dhc. Proszę o zbadanie sytuacji, bo my nic nie wyłapaliśmy.\r\n\r\nRafał Boniecki\n\n### Response:\n["Comment 1: [\'analiza z dgsa:VT-282: RGM_parrentid 28283747 wydany dla dwóch VTE_id (915414,915377)VT-166: RGM_parrentid 28314514,28314511 wydany dla VT elementu 914924 ale powinien dla vte_id =914915 - różne między parrentid a paletą.Brakuje wtedy elementów w dhc .\'", "Comment 2: \'mamy akceptację na 4h analizy.\'", "Comment 3: \'zgodnie z rozmową.\'", "Comment 4: \'Zapytanie po retro o status zgłoszenia - o komentarz do taska.\'", "Comment 5: \'Hi", "Comment 6: any news?\'", "Comment 7: \'W Łomży jest tego kilka elementów najnowszy jest z 12.2022 vt-25452/12/2022Brakuje elementu 12!image-2023-03-24-15-11-14-991.png!Tutaj widać nieścisłość!image-2023-03-24-15-11-38-839.png!{code:java}SELECT rgm_id,RgM_VtEIdRelease,RgM_ParrentId,RgM_Quantity FROM [DHP_Lomza].[dbo].[RegisterMappings] where RgM_Id in(28175975,28175971) or RgM_VtEIdRelease=911506or RgM_ParrentId in(28175975,28175971)-----SELECT sum(RgM_Quantity) FROM [DHP_Lomza].[dbo].[RegisterMappings] where RgM_VtEIdRelease=911506and RgM_ParrentId in(28175975)-----SELECT sum(RgM_Quantity) FROM [DHP_Lomza].[dbo].[RegisterMappings] where RgM_ParrentId in(28175971){code}\'", "Comment 8: \'Łęczyca - SQL01-20vt:6179/3/20236631/4/2023elementy id: ilość542573 1,2543924 0,45\'", "Comment 9: \'Hello", "Comment 10: can we get a copy of the database Łęczyca - SQL01-20 from the ssms level for verification the problem described in the task?\'", "Comment 11: \'Hi", "Comment 12: we decided to close that task. We consider it again when problem will return...\'", "Comment 13: \'According to information ticket has been closed.\']"]\nRelated Issues:\n[\'DGS-8323\']\n\n### End'} |
598 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8434\n\n### Instruction:\nWe have some productions not produced but we don\'t have option to cancel. \r\n\r\nSUR7546-P-MD 0871230123004\r\nSUR7546-P-MD 0871200123031\r\nSUR7546-P-MD 0871200123032\r\nSUR7546-P-MD 0871200123033\r\nSUR7546-P-MD 0871200123034\r\n\r\nCould you please cancel the productions?\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: "{code:java} FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where LotNumber in(\\\'0871291222002\\\',\\\'0871230123004\\\',\\\'0871200123031\\\',\\\'0871200123032\\\',\\\'0871200123033\\\',\\\'0871200123034\\\'){code}status 3."\', "Comment 3: \'Documents have been cancelled.\'", "Comment 4: \'Could you please confirm if we can close this task?Regards\'", "Comment 5: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. Regards\']"]\nRelated Issues:\n[]\n\n### End'} |
599 | {'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8433\n\n### Instruction:\nThe report Weighbridge dispatch available in VT is duplicating the element. Could you check and fix it?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'The problem is for the all elements", "Comment 4: items and vt or it happend always?\'", \'Comment 5: "Hi Agnieszka,it\\\'s happening for all elements and all vts dispatch."\', "Comment 6: \'!image-2023-02-01-13-28-46-495.png!\'", "Comment 7: \'GetWeighBridgeNewPrintout-- tu sa elementy vt.GetWeighBridgePrintout\'", "Comment 8: \'!image-2023-02-01-14-17-49-857.png!\'", \'Comment 9: "SELECT E.Id\', \'Comment 10: E.No\', \'Comment 11: NULL AS IssueDate\', \'Comment 12: R.SerialNumber\', \'Comment 13: R.WeightValue AS ResourceQuantity\', \'Comment 14: R.WeightUnit AS ResourceQuantityUnit\', \'Comment 15: R.ExpiryDate\', \'Comment 16: D.InternalSerialNumber\', \'Comment 17: D.CreatedDate\', \'Comment 18: NULL AS ForeignEAN\', \'Comment 19: 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=\\\'cb88b35b-f52c-4781-a9f1-2c1f3424e92b\\\'"\', \'Comment 20: "[[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 21: czy ta procedura jest zła?bo sama procedura jak patrzyłam i w Apu i w innej fabryce jest taka sama\', \'Comment 22: wtedy taka sytuacja z duplikacją pozycji występowała by częsciej\', \'Comment 23: 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 24: E.No\', \'Comment 25: NULL AS IssueDate\', \'Comment 26: R.SerialNumber\', \'Comment 27: R.WeightValue AS ResourceQuantity\', \'Comment 28: R.WeightUnit AS ResourceQuantityUnit,R.ExpiryDate\', \'Comment 29: D.InternalSerialNumber\', \'Comment 30: D.CreatedDate\', \'Comment 31: NULL AS ForeignEAN\', "Comment 32: 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.SerialNumberWHERE 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-30-17-836.png!naromiast wynik zapytania dla samej tabeliselect * from VehicleTicketPackedDispatchElementResources where id=\'1E6686E6-0C73-4CCF-940A-6DF5DF515A36\'!image-2023-02-15-07-31-38-280.png!select SerialNumber,* from dbo.Deliveries D where SerialNumber in (\'0881230123002\'", "Comment 33: \'0881250123013\'", "Comment 34: \'0881250123012\'", "Comment 35: \'0881191222020\'", "Comment 36: \'0881270123010\') order by 1select top 100 * from dbo.StockUnits where DeliveryId in (\'5204C239-1C6F-4760-8F92-8D44E95AF8CA\'", "Comment 37: \'B32C320E-E095-484D-9FB9-821C655C9D56\'", \'Comment 38: \\\'B68AC030-7F37-48F3-9947-5EEB81B6A35D\\\')Pytanie czy takie rzeczy powinny się dziać!image-2023-02-02-13-16-27-474.png!!image-2023-02-15-07-30-17-836! !image-2023-02-15-07-31-38-280!"\', "Comment 39: \'Hello,Could you please provide other vt with similar situation?\'", "Comment 40: \'[[email protected]]czy udało sie zweryfikowac czy działanie jest prawidlowe\'", "Comment 41: \'Good morning", \'Comment 42: after our analysis\', \'Comment 43: it appears that the situation was due to the fact that to one serial number in this case was assigned several different deliveries. Neither the printout nor the procedure has been modified recently\', \'Comment 44: and the same procedure is used in other plants\', \'Comment 45: as you have not indicated more cases\', \'Comment 46: I close the notification\', \'Comment 47: if there is a new case\', \'Comment 48: or the need to continue work\', "Comment 49: please create a new ticket and refer to this number.\']"]\nRelated Issues:\n[\'DGS-8556\']\n\n### End'} |
Subsets and Splits