Datasets:

pismacx

/

ai_assistant

like 1

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8932\n\n### Instruction:\nOrder SOBE000019659 is planned for today but doesn\'t arrive from DHP into PCS. Could you see what is wrong with 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: \'!image-2023-04-07-12-22-50-720.png!\'", "Comment 3: \'Could you please verify with you pcs provider", "Comment 4: we may see that order was exported today about11:13:18.\'", "Comment 5: \'The problems for this particular order seems to be at the pcs provider indeed. Thanks for your assistance", "Comment 6: ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8931\n\n### Instruction:\nHi.\r\nPleas help to check VT-12571/23 was closed without releasing stock .\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!\'", \'Comment 2: "Hi 1. Checking at the database level\', \'Comment 3: we found that the system allowed VT-12571/23 to pick lot 43710060423004 even though this lot had just been created ,not confirmed. 2. PLR 43710060423004 has been completed after VT-12571/23 execution and the quantity after completion is less than during creation. That\\\'s why the system is reserving a quantity in excess of the on-hand quantity?3. So. How to fix this case ?!image-3!"\', "Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 5: \'vt. zamkniety o 17-21 !image-2023-04-07-14-32-37-501.png!\'", \'Comment 6: "select * FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets] where AggregateId=\\\'ef4b4acd-ec15-45f0-8d01-c6f9e16e2900\\\' and eventtype like \\\'%close%\\\'!image-2023-04-07-14-36-34-408.png!"\', "Comment 7: \'blad z czasu !image-2023-04-07-14-46-02-234.png!\'", \'Comment 8: "select* FROM [DHPlantStockBusinessLogicEvents].[dbo].[Deliveries] where AggregateId=\\\'5BCEDD86-2FFA-44A2-8E11-8284316F3219\\\'jest 2 razy event change id na deliwery raz na 10000 raz na 9921 ta róznica to 79.user który confirmowal mniejsza ilosc teżTAJINYKO- to on mogl to zrobić!image-2023-04-07-15-00-43-553.png!"\', "Comment 9: \'If the PLR was created manually and by PCS then the system allows its use before approval. This is not an error. As for the resource for the given code you can try to make an inventory. Please let me know if these infirmations are sufficient?\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8930\n\n### Instruction:\nDear All,\r\n\r\nWe have issues on both the interfaces recipe and ingredients.\r\n\r\n1. Recipe interface\r\nThe recipe was originally sent and an error occurred - see attachment imagine\r\nI corrected the data in DHH but xml does not want to integrate and repeats the error. In the meantime, the new versions of recipes (6 and 7) were sent see Imagine 1.\r\n\r\n2. ingredient interface\r\nWe also had a whole-day issue with the ingredient interface. We cleaned the Kotrak tables a few times but the error repeated. I think it might be related to the recipe interface issue - see image 5\r\n\r\nCan you please help? For is it is PRIO 1\r\n\r\nKind regards,\r\nDiana Cielecka\r\nmobile +31 615 280 243\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \' !screenshot-1! \'", "Comment 4: \'Integration with Spain and Portugal sent the Pricelist to DHH in a loop", "Comment 5: which resulted in a large queue.As a result all messages except recipes and labels were delayed.We have stopped communication with Spain and Portugal. Clearing messages allowed others messages to be processed.Will provide information when all will be processed.\'", "Comment 6: \'Sprawdzanie kolejki.{code:java}select count(1) from DHHolding with (nolock){code}\'", "Comment 7: \'Spain and Portugal jeśli chodzi o te kraje Przemek zgłosił aby ze ogarnęli.\'", "Comment 8: \'!image-2023-04-06-20-15-38-793.png!\'", "Comment 9: \'Hi,Message queues are empty now. Please", "Comment 10: verify.Regards\'", "Comment 11: \'Everything works fine. Thank you very much. Great job!\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8929\n\n### Instruction:\nCould you please fix this ASAP?\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: "Roles forArthur van der Linde has been added to his user in task [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8915]Please verify right now if he gets items to Inbox and should be also able to open list of New Items.!image-2023-04-06-16-40-04-940.png!If he need access to others inbox for old items\', \'Comment 3: we can share someone\\\'s inbox to allow him accept New Item Cards."]\']\nRelated Issues:\n[\'DGS-8915\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8928\n\n### Instruction:\nVT-89 is filled in from pcs intake, but not closed (that\'s the 1e problem)\r\nNow in this case there was also a wrong quantity send, so an opportunity to adjust, but after adjustment ticket cannot be close, see attached error message: Please close ticket with adjusted weight \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: \'!afbeelding-1!\'", "Comment 4: \'Hi Thomas,I tried to recreate your error but in fact I managed to close VT without any issues. I will verify errors what happened yesterday and let you know.Regards!image-2023-04-07-08-02-50-647.png!\'", \'Comment 5: \\\'W maintanance{code:java}2023-04-07 08:21:45 (dfa8eb10-811d-4057-81c5-3ae37cc3362b/Plant.Maint.BusinessLogic/DHVD01AP181/5512/94) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 6: "host": { "Value": "dhvd01ap181:89"\', \'Comment 7: "HasValue": true\', \'Comment 8: "Host": "dhvd01ap181"\', \'Comment 9: "Port": 89 }\', \'Comment 10: "path": "/api/intercontext/vc/errors"\', \'Comment 11: "queryString": []\', \'Comment 12: "requestBody": "{\\\\\\\\"sortedColumns\\\\\\\\":[{\\\\\\\\"columnName\\\\\\\\":\\\\\\\\"createDate\\\\\\\\",\\\\\\\\"order\\\\\\\\":2}],\\\\\\\\"pagingViewModel\\\\\\\\":{\\\\\\\\"pageSize\\\\\\\\":25,\\\\\\\\"pageNumber\\\\\\\\":1},\\\\\\\\"summaryColumns\\\\\\\\":[],\\\\\\\\"createDate\\\\\\\\":{\\\\\\\\"rangeStart\\\\\\\\":null,\\\\\\\\"rangeEnd\\\\\\\\":null}}"}.AutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:PaginatedResultDto`1 -> ErrorPaginatedListViewModelKotrak.Common.Application.Dtos.PaginatedResultDto`1[[Plant.Maint.BusinessLogic.Application.Interfaces.Intercontext.ErrorListDto\', \'Comment 13: Plant.Maint.BusinessLogic.Application.Interfaces\', \'Comment 14: Version=8.5.0.0\', \'Comment 15: Culture=neutral\', \'Comment 16: PublicKeyToken=null]] -> Plant.Maint.BusinessLogic.Infrastructure.Api.ViewModels.Intercontext.ErrorPaginatedListViewModelType Map configuration:PaginatedResultDto`1 -> ErrorPaginatedListViewModelKotrak.Common.Application.Dtos.PaginatedResultDto`1[[Plant.Maint.BusinessLogic.Application.Interfaces.Intercontext.ErrorListDto\', \'Comment 17: Plant.Maint.BusinessLogic.Application.Interfaces\', \'Comment 18: Version=8.5.0.0\', \'Comment 19: Culture=neutral\', "Comment 20: PublicKeyToken=null]] -> Plant.Maint.BusinessLogic.Infrastructure.Api.ViewModels.Intercontext.ErrorPaginatedListViewModelDestination Member:ItemViewModels ---> AutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:ErrorListDto -> ErrorListViewModelPlant.Maint.BusinessLogic.Application.Interfaces.Intercontext.ErrorListDto -> Plant.Maint.BusinessLogic.Infrastructure.Api.ViewModels.Intercontext.ErrorListViewModelType Map configuration:ErrorListDto -> ErrorListViewModelPlant.Maint.BusinessLogic.Application.Interfaces.Intercontext.ErrorListDto -> Plant.Maint.BusinessLogic.Infrastructure.Api.ViewModels.Intercontext.ErrorListViewModelDestination Member:MessageType ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter \\\\\'startIndex\\\\\') at System.String.LastIndexOf(Char value", \'Comment 21: Int32 startIndex\', \'Comment 22: Int32 count) at Plant.Maint.BusinessLogic.Infrastructure.Api.MappingProfiles.ErrorMessageTypeResolver.Resolve(ErrorListDto source\', \'Comment 23: ErrorListViewModel destination\', \'Comment 24: String member\', \'Comment 25: ResolutionContext context) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\778bbb0f253eec26\\\\\\\\Plant.Maint.BusinessLogic\\\\\\\\Plant.Maint.BusinessLogic.Infrastructure.Api\\\\\\\\MappingProfiles\\\\\\\\ErrorMappingProfile.cs:line 42 at lambda_method99551(Closure \', \'Comment 26: PaginatedResultDto`1 \', \'Comment 27: ErrorPaginatedListViewModel \', \'Comment 28: ResolutionContext ) --- End of inner exception stack trace --- at lambda_method99551(Closure \', \'Comment 29: PaginatedResultDto`1 \', \'Comment 30: ErrorPaginatedListViewModel \', \'Comment 31: ResolutionContext ) --- End of inner exception stack trace --- at lambda_method99551(Closure \', \'Comment 32: PaginatedResultDto`1 \', \'Comment 33: ErrorPaginatedListViewModel \', \'Comment 34: ResolutionContext ) at Plant.Maint.BusinessLogic.Infrastructure.Api.Controllers.Intercontext.VcIntercontextController.GetErrorsPaginatedList(ErrorPaginatedListFilterViewModel filterViewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\778bbb0f253eec26\\\\\\\\Plant.Maint.BusinessLogic\\\\\\\\Plant.Maint.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\Intercontext\\\\\\\\VcIntercontextController.cs:line 71 at lambda_method99565(Closure \', \'Comment 35: Object \', \'Comment 36: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 37: ObjectMethodExecutor executor\', \'Comment 38: Object controller\', \'Comment 39: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 40: Scope& scope\', \'Comment 41: Object& state\', \'Comment 42: 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 43: Scope& scope\', \'Comment 44: Object& state\', \'Comment 45: 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 46: Task lastTask\', \'Comment 47: State next\', \'Comment 48: Scope scope\', \'Comment 49: Object state\', \'Comment 50: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 51: Task task\', \'Comment 52: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 53: Task task\', \'Comment 54: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 55: Task requestTask\', \'Comment 56: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', "Comment 57: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code} !image-2023-04-07-08-54-15-338.png!\'", "Comment 58: \'!image-2023-04-07-09-26-53-534.png!\'", "Comment 59: \'Ostatni error z wczoraj!image-2023-04-07-09-28-03-212.png!\'", "Comment 60: \'!image-2023-04-07-09-30-28-631.png!\'", "Comment 61: \'W inbound messages czysto", "Comment 62: restart servisu i restart pooli nie pomógł\'", "Comment 63: \'But it should be corrected to 18000..\'", \'Comment 64: "My fault and my mistake I haven\\\'t asked what quantity should be in VT\', \'Comment 65: what quantity is correct. Now the most sensible solution would be correct the stock by stock correction from PCS or opening balance in plant... Would that be possible for you?Regards"\', "Comment 66: \'Hi,May we close this task?Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8927\n\n### Instruction:\nAs follow up on DGS-8904:\r\n\r\nI asked the dba of Valid to investigate this. He came back with the following:\r\n\r\n================================================\r\nI’ve checked the DHVD01AG09 instance and found that\r\nthe process in the screenshot is the weekly index maintenance.\r\n\r\nIt seems it was blocked (which is also visible from\r\nthe screenshot) from process with ID 126 which was killed yesterday afternoon:\r\n\r\n\xa0\r\nDate\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\r\n4-4-2023 15:14:34\r\n\r\nLog\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\r\nSQL Server (Current - 5-4-2023 09:45:00)\r\n\r\nSource\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\r\nspid53\r\n\r\nMessage\r\n\r\nProcess ID 126 was killed by hostname DHVD01DB45, host\r\nprocess ID 7696.\r\n\r\n\xa0\r\nThe index maintenance was blocked during execution of\r\nthe following:\r\n\r\nALTER INDEX [PK_Deliveries] ON [dbo].[Deliveries]\r\nREBUILD WITH (SORT_IN_TEMPDB = OFF, ONLINE = ON, RESUMABLE = OFF)\r\n\xa0\r\n\r\nThe table DHPlantPCSBusinessLogicEvents is 20MB with 4\r\nMB indexes and for some reason this operation was blocked for more than 2 days,\r\nmeaning something else was holding lock on this table.\r\n\r\nIn order to prevent such long running Index maintenance operations\r\ncaused by table locks my proposal is to limit the time for the operation to\r\nwait for a lock to be released to let’s say 5 minutes. And if the lock is still\r\nactive to continue with the next index. \r\n\r\n===================================================\r\n\r\nI think this proposal makes sense. Do you agree? If so, I\'ll ask him to implement this.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'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: \'[~maciej.dobrzanski@kotrak.com]spojrzysz okiem swym? :)\'", \'Comment 4: "Hi [~mmeier@deheus.com],We are aware of issues related to the growing Events databases along with their indexes. That is why in agreement with Theo we decided to change the way of maintenance of those databases. We can expect this mechanism to be implemented in the Release 8.7 of the DHP. Since then\', \'Comment 5: both the size of databases and indexes should stop growing so much.Limiting operation time to 5 min is for sure a good idea. We don\\\'t recommend doing any activities related to rebuilding indexes or any other jobs that may affect the performance of the DB server during work time (when a factory is running)."]\']\nRelated Issues:\n[\'DGS-8904\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8926\n\n### Instruction:\n6_L000175708 has an item in pcs packing, but it should be KG. On the order the packing form is correct, but on trip its false: Can you check reason and inform how to solve?\r\n\r\n\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hi Thomas,Have you resynced anything? The data on a Trip is correct - it\\\'s bulk and kg!image-2023-04-07-07-52-59-978.png!"\', "Comment 4: \'Oke", "Comment 5: I did a resync yes. Ticket can be closed\'", "Comment 6: \'Thank you.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8925\n\n### Instruction:\nHello,\r\n\r\nPlease assist.\r\n\r\nIO-113/23/KLR is not showing in DHP.\r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'", "Comment 3: \'https://helpdesk.kotrak.com/browse/DGS-8924?focusedCommentId=1122121&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1122121\'", "Comment 4: \'Wczoraj był problem z tymi IO:O-56/23/DKDIO-36/23/DKDIO-54/23/DKDIO-58/23/DKDIO-57/23/DKDIO-28/23/DKDIO-59/23/DKDIO-26/23/DKDIO-45/23/DKDIO-55/23/DKDIO-60/23/DKDIO-37/23/DKD list of orders - please check.\'", "Comment 5: \'Po upgrade DHC w RPA", \'Comment 6: dla IO ustawia się flaga isInnerBU\', \'Comment 7: mimo że w DHC nie ma w konfiguracji wpisu odpowiadającego za ustawianie tej flagi. Config ten był robiony pod BR RC task GDC-500.Aktualnie flaga jest zmieniana na bazie DHC. Natomiast jeśli zrobią w ERP update IO\', "Comment 8: to znów się ustawi flaga na true.\'", "Comment 9: \'Please assist IO-133/23/KLR \'", "Comment 10: \'done!image-2023-04-06-15-08-44-843.png!\'", "Comment 11: \'IO-134/23/KLR\'", "Comment 12: \'Hi", "Comment 13: done.\'", "Comment 14: \'Thanks\'", "Comment 15: \'Hello,Please assist IO-28/23/DKD and IO-29/23/DKD are not showing in DHP\'", "Comment 16: \'Hi,orders should be in DHP (visible).\'", \'Comment 17: "DHC ustawia flagę IsInnerBusinessUnit gdy DestinationWarehouseId i SourceWarehouseId mają wartość i zapytanie:!screenshot-1! zwróci wpisy z jednym BusinessStructuresIddla magazynu \\\'KLD Depot - Klerksdorp\\\' brak wpisu w dbo.ProductionAreaWarehouses i zapytanie zamiast zwrócić dwa rezultaty zwraca jeden.jest 46 magazynów bez przypisanej production area: !screenshot-2! Przypisanie production area rozwiązało by problem.Można również zmienić zapytanie\', \'Comment 18: by uwzględniało magazyny bez przypiętego production area "\', "Comment 19: \'trzeba podegrać nową wersję. DHCountry-release-Release-3.0.63-4-202304111336-FTP No configuration.zip na ftp\'", "Comment 20: \'hej [~piotr.gaczorek@kotrak.com]przekażesz proszę klientowi rezultat analizy? Michał dodatkowo zmienił zapytanie więc trzeba by ustalić z nimi kiedy możemy podegrać DHC z zmianą tego zapytania (zakładany downtime - 30min(\'", "Comment 21: \'[~marek.mamcarz@kotrak.com] między godziną 7-15 ustalić tą lukę na podegranie? i będzie wyłączony DHC wtedy tak?\'", "Comment 22: \'Hello", \'Comment 23: we need to upload a change for DHC.The DHC downtime will then be around 30 minutes.Please let me know when we can make the change between 9 a.m. and 4 p.m.If not today\', "Comment 24: possibly tomorrow.As to the change will be required due to the fact that most warehouses do not have an assigned production area.Only the ones below: !screenshot-3! \'", \'Comment 25: "As per our teams discussion. Noon is the best time but\', "Comment 26: I\'m happy with any time", \'Comment 27: as long as we have at least 1 hour notification. "\', "Comment 28: \'Hi", "Comment 29: the change for DHC has been uploaded.\'", "Comment 30: \'Ostatnia poprawa:IO-57/23/KBDIO-56/23/KBDIO-18/23/KBSIO-8/23/KBGIO-53/23/KBDIO-59/23/KBDIO-58/23/KBDIO-54/23/KBDIO-51/23/KBDIO-29/23/DKDIO-28/23/DKDIO-19/23/KBSIO-17/23/MOMIO-6/23/KBGIO-20/23/KBSIO-55/23/KBDIO-52/23/KBD\'", "Comment 31: \'Hello.According to the changes for DHC please let me know if the problems still exist for IO?If not", "Comment 32: can we close this RCA?\'", "Comment 33: \'Hello,Can we keep the ticket open till Friday (21.04.2023)\'", "Comment 34: \'Yes", \'Comment 35: please send me information on Friday\', "Comment 36: thanks.\'", "Comment 37: \'Hello,You may close this ticket\'", "Comment 38: \'Hello", "Comment 39: thank you.\']"]\nRelated Issues:\n[\'DGS-8924\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8924\n\n### Instruction:\nHello,\r\n\r\nPlease assist.\r\n\r\nIO-113/23/KLR is not showing in DHP.\r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'[~marek.mamcarz@kotrak.com] [~piotr.chmielarski@kotrak.com]tak jak wspominałem po upgrade DHC w RPA mamy problemy z IO. Aktualizacje na bieżąco robi [~piotr.gaczorek@kotrak.com]Natomiast temat trzeba sprawdzić. Rozumiem że RCA dla [~przemyslaw.przybyszewski@kotrak.com]\'", "Comment 3: \'Na razie Wasza procka działa :)\'", "Comment 4: \'IO in plant now. Please", "Comment 5: verify!image-2023-04-06-11-54-08-385.png!\'", "Comment 6: \'RCA task underDGS-8925\'", "Comment 7: \'Hello,Please assist IO-28/23/DKD and IO-29/23/DKD are not showing in DHP\'", "Comment 8: \'Hi", "Comment 9: orders should be in DHP (visible).\'", "Comment 10: \'Can you give new cases only to RCA?Can p1 issue be closed?\'", "Comment 11: \'DGS-8925 - RCA related was closed. This ticket also has been closed.\']"]\nRelated Issues:\n[\'DGS-8925\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8923\n\n### Instruction:\nHi\r\n\r\nCan we change the way the ERP calcualtes a customers SO block when over the limit? \r\n\r\nWe would like it to take into account existing confirmed SO\'s + outstanding SI.\r\n\r\nHow & were do we change this?\r\n\r\nRegards\n\n### Response:\n["Comment 1: [\'https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7197\'", "Comment 2: \'I see from the other ticket how this is done. Can you place this ticket on hold till we test please.\'", \'Comment 3: "HiPlease can we put this request back in progress. The configuration doesn\\\'t seem to be working as intended.Regards "\', "Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 5: "Thank you...We will need to put the ticket back on hold. I\\\'m getting new stories from the accounts team. I want to do some manual confirmations first to test."]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8922\n\n### Instruction:\nASN-870/04/2023 does not arrive in DHP\r\n\r\nAlready tried it 3 times to send, even created a whole new contract, in which everything is just right. (supplier is already known to us, has delivered more often and there was no problem)\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: \'Hello", "Comment 4: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'", "Comment 5: \'we rae back working on Your issue\'", "Comment 6: \'!image-2023-04-06-11-46-13-432.png!\'", \'Comment 7: \\\'The UPDATE statement conflicted with the FOREIGN KEY constraint "FK_dbo.Orders_dbo.Addresses_MainBusinessPartnerAddressId". The conflict occurred in database "Evolution_DHCountry"\', \'Comment 8: table "dbo.Addresses"\', "Comment 9: column \\\\\'Id\\\\\'.The statement has been terminated.\'", \'Comment 10: "select * from AddressSyncs where dhcid in (\\\'3190D73A-D136-4D77-8C0D-A3635E32E7D5\\\',\\\'E3FAFAA8-3C17-4848-AEB1-8CF13C496DF4\\\') or xlid=3296!image-2023-04-06-12-28-28-199.png!"\', \'Comment 11: "The problem was the changed address on the order on the order used an archived address\', \'Comment 12: which in erpxl had almost identical data to the current one ( screen from the database). On the order I changed the gidnumber of the address to the non-archived one.!image-2023-04-06-12-58-25-920.png!When trying to synchronize the address and the PO itself\', \'Comment 13: it turned out that the person editing the new address\', "Comment 14: set the wrong country - the prefix PO instead of \'pl\'", \'Comment 15: which was also corrected. The order went through and the new address went through\', \'Comment 16: but there is still an error about the address on the shipping notice\', \'Comment 17: which does not pass the items.!image-2023-04-06-12-58-47-553.png!I think that in this situation the fastest way is to cancel the order and create a new one on the basis of the already corrected order - please verify whether such an order will synchronize correctly."\', "Comment 18: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8921\n\n### Instruction:\n VT-12423/23 can not release for intake\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'{code:java}2023-04-06 15:29:52 (028004eb-4560-44bb-af97-1685aa9f7d11/Plant.VC.BusinessLogic/VNPCT-TS01/32500/211) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[ReleaseVehicleTicketIntakeCommand](Plant.VC.BusinessLogic.Application.Interfaces.VehicleTickets.Commands.ReleaseVehicleTicketIntakeCommand) methodSystem.InvalidOperationException: Nullable object must have a value. at Plant.VC.BusinessLogic.Domain.VehicleTickets.Factories.VehicleTicketDomainEventFactory.CreateVehicleTicketReleasedForIntakeEvent(VehicleTicket vehicleTicket) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Factories\\\\\\\\VehicleTicketDomainEventFactory.cs:line 538 at Plant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicket.ReleaseForIntake(DateTime date) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicket.cs:line 521 at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.ReleaseVehicleTicketIntake(AggregateId vehicleTicketId", \'Comment 4: DateTime date) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketService.cs:line 194 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-04-06 15:29:52 (null/Plant.VC.BusinessLogic/VNPCT-TS01/32500/207) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/VehicleTicket/releaseIntake" responded 500 in 17.8458 ms{code}a ze stocka{code:java}2023-04-06 14:30:05 (null/Plant.Stock.BusinessLogic/VNPCT-TS01/19396/5) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[SynchronizeBusinessPartnerCommand](Plant.Stock.BusinessLogic.Application.Interfaces.BusinessPartners.SynchronizeBusinessPartnerCommand) methodKotrak.Extensions.Validation.Abstractions.ValidationException: Validation failed: -- Business partner name is missing ---> Kotrak.Common.Application.Exceptions.CommandValidationException`1[Plant.Stock.BusinessLogic.Application.Interfaces.BusinessPartners.SynchronizeBusinessPartnerCommand]: Validation failed: -- MissingBusinessPartnerNameMessage 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 ---2023-04-06 14:30:05 (null/Plant.Stock.BusinessLogic/VNPCT-TS01/19396/5) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type "Plant.Integration.Common.PublishedLanguage.BusinessPartnerChangedMessage"\', "Comment 5: retry no 0Kotrak.Extensions.Validation.Abstractions.ValidationException: Validation failed: -- Business partner name is missing ---> Kotrak.Common.Application.Exceptions.CommandValidationException`1[Plant.Stock.BusinessLogic.Application.Interfaces.BusinessPartners.SynchronizeBusinessPartnerCommand]: Validation failed: -- MissingBusinessPartnerNameMessage 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 6: \'!image-2023-04-06-10-52-20-663.png!\'", "Comment 7: \'Please", "Comment 8: check now.Regards\'", \'Comment 9: "HiWhat\\\'s issue with VT? We have faced this issue a few times before. So how to fix it ?"\', "Comment 10: \'There was no arrival date here:!image-2023-04-06-11-11-12-056.png|width=1171,height=257!I have updated it with arrival weight date.Can we close this task?Regards\'", "Comment 11: \'Yes . Please close this VT.\'", "Comment 12: \'Thank you\'", "Comment 13: \'more question : Why is arrival date missing here ?\'", "Comment 14: \'Hi,We still have RCA task open for this issue underDGS-8281 and will be fixed in 8.6 version of DHPAs soon as we get so information", "Comment 15: we will let you know.Regards\']"]\nRelated Issues:\n[\'DGS-8281\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8920\n\n### Instruction:\nProszę o aktualizację i cofnięcie anulowania wynagrodzeni Dobrzenieckiej Karoliny z listy E-UM/2023/02/*\r\n\r\nProsba tez o weryfikacje czemu w obecnej wersjii user nie moze tego dokonac od strony aplikacji\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: \'Wypłata została przywrócona", "Comment 3: proszę o weryfikację.Wgrano też aktualną funkcję do cofania anulowania.\'", \'Comment 4: "Now it\\\'s OkTask to close"]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8919\n\n### Instruction:\nthe attached recipes are not in DHC.\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: \'Recipe is in DHC now", "Comment 4: please vervfied!image-2023-04-05-16-01-47-862.png!\'", "Comment 5: \'could you please also check the issue with attached list of recipes as all of them are also not in DHC.!image-1!\'", "Comment 6: \'We resnd it from the DHH", "Comment 7: please check.\'", "Comment 8: \'yes", "Comment 9: all is in DHC\'", "Comment 10: \'Could you please confirm if we can close this task?Regards\'", "Comment 11: \'yes", "Comment 12: please close this ticket.thank you!\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8918\n\n### Instruction:\nRecipe 967268 is present in DHC and is accepted, however, it doesn\'t arrive 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: \'Recipe is in plant now!image-2023-04-05-15-42-00-150.png!\'", "Comment 3: \'thank you! Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8917\n\n### Instruction:\nPrzy naliczaniu wynagrodzeń za mc marzec pracownikowi Leszek Daraż, pokazuje się poniższy komunikat.\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: \'Pracownik posiada Zajęcie wynagrodzenia ale nie został dla niego przypisany komornik:. !image-2023-04-05-16-58-10-531.png!\'", "Comment 4: \'Could you please confirm if we can close this task?Regards\'", "Comment 5: \'Yes\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8916\n\n### Instruction:\nPotrzebny pilnie (na dzisiaj) wykaz zmian zapisów historycznych ze szczegółami na kontach pracowników.\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: \'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 that is production or transport. This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'", "Comment 4: \'[^DGS-8916.docx]\'", \'Comment 5: "In the attachment description of Optima\\\'s functionality and topics to be detailed[^DGS-8916.docx]"\', "Comment 6: \'We can lower priority to P2. I shared the doc with the user.\'", \'Comment 7: "Thank you\', \'Comment 8: I\\\'m waiting for an answer"\', \'Comment 9: \\\'User answer "Na potrzeby audytu potrzebuje zestawienia zmian ,dokładnie :Dziennik zmian dokonywanych w zbiorze danych podstawowych pracownika (historia zmian „nowy vs stary”)."\\\'\', "Comment 10: \'Please provide more information as described in the uploaded document\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8915\n\n### Instruction:\nCould you give Arthur the same rights in the MAS as Rick Reimerink.\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: \'Now he has all roles which has user:Rick ReimerinkRick Reimerink AAPlease verify if he can do all needed operations.\'", "Comment 3: \'His inbox is still empty. He should have the same things as Rick Reimerink AA (but then only for MAS", "Comment 4: not PAS/OPPAS).\'", \'Comment 5: "Last New Item Card has been createt in MAS NL which can be accepted and then created Item card is from 2.02.2023 and then he hasn\\\'t been in process of New Item Cards.I gave him right now access to Rick Reimerink AA access. Arthur should be able to see in inbox all New Item Cards which also have Rick Reimeink.Only what he need to do is to use option \\\'All shared inboxes\\\' to see other users document (in this case only of Rick\\\'s) or direcly choose to which inbox in option \\\'Inboxe owned by user\\\'!image-2023-04-07-13-34-14-887.png!"\', \'Comment 6: "I wasn\\\'t just talking about New Item Cards. He doesn\\\'t receive any tasks in his Inbox. So no SR\\\'s etc."\', \'Comment 7: "Oh\', \'Comment 8: so I deleted this shared inbox of Rick.For SR he should be added to role for this (Rick is not in this role -Slaughtery Report from Kofax users)Now there are users like below. I\\\'ve added Arthur also to this role. He should gets new SR to inbox.Does he need any other documents? He should be able to manually create documents,I see now in his inbox some Financial statement and Purchase Invoice and also Round and Feed sale (last 2 automatically generated to users inboxes).!image-2023-04-07-14-26-13-342.png!"]\']\nRelated Issues:\n[\'DGS-8929\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8914\n\n### Instruction:\nBardzo proszę o zweryfikowanie poprawności działania środowiska produkcyjnego, pod kątem poprawności działania synchronizacji pomiędzy aplikacjami ERP-DHC-DHP i Integratorów.\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: \'1. Statusy tras się nie aktualizują w DHC", \'Comment 3: T-2605/23/D tylko pierwsza zmiana spowodowała zmianę statusu na Anulowany\', \'Comment 4: a pozostałe pozostają już w statusie Potwierdzony2. T-2605/23/D jest nie kompletna w DHP. Brakuje elementów z fabryki pasz ZW-52/03/23/I\', \'Comment 5: zamówienie jest w DHP 3. ZW 52/03/23/I - są dwa kompletnie różne zamówienia z różnymi elementami\', \'Comment 6: ale z tym samym numerem 4. Jeżeli brakuje Trasy w DHP i na VT są podpięte zamówienia zamiast tras\', "Comment 7: to w DHC VT nie ma połączenia z ZS np.VT-6185/Ł!image!!image-1!!image-2!!image-3!!image-4!\'", "Comment 8: \'Order for unlinked VT /ZW-163/03/23/g and order ZW-52/03/23/I are from 2023-03-27", \'Comment 9: do we have current examples\', "Comment 10: e.g. from the last two or three days?\']"]\nRelated Issues:\n[\'DGS-8881\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8913\n\n### Instruction:\nIf the original document is visible on the round than the credit document should also be visible on the round. \r\n\r\n\xa0\r\n\r\n\xa0\r\n\r\nCPI-M/2023/0200 isn\'t visible on Round\xa0015236/0187/0004\r\n\r\n!image-2023-04-05-10-09-33-789.png!\r\n\r\n\xa0\r\n\r\nIn relation table for this case leading doc is filled in and on the round only invoices without leading doc are displayed.\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: ["It\\\'s ready to test on Test environment.Changes are described in task [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8764]{quote}Changes have been made on TEST environment. You can verify them.In some sectors and sections displaying Credit invoices worked correctly before\', \'Comment 2: we\\\'ve made changes in Expenses sections.Changes that have been made in sectors on documents: * RoundMAS NL expenses sectionLAS expenses sectionNAS expenses sectionVAS expenses section * Financial StatementMAS NL expenses sectionLAS expenses sectionNAS expenses sectionVAS expenses section * Financial Statement printoutsMAS NLLASNASVAS * Saldo to PayMAS NLLASNASVAS{quote}"]\']\nRelated Issues:\n[\'DGS-8764\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8912\n\n### Instruction:\nPlease cancel the following VT\'s:\r\nVT-36/4/23\r\nVT-38/4/23\r\nVT-185/4/23\r\n\r\nDue to wrong packaging type (pcs) for ASN the VT\'s cannot be cancelled by us. Should be more flexible in my opinion, I corrected the packaging type but VT is not updated and I cannot cancel 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 Thomas,All three VTs are cancelled. Please", "Comment 3: verify,Regards\'", "Comment 4: \'Thanks", "Comment 5: ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8911\n\n### Instruction:\nProblem with open and creating VT 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: \'resolved by Mateusz Banaszczyk .\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8910\n\n### Instruction:\nDear, \r\nI need to link BMX code 0982 with Integra code 10892. I did it in the same way but now it looks different. After selection of "Base item", item isn´t seen at left side in "unliked items"\r\npls look at it.\r\nthx\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'There are two steps of linking - first the base item", "Comment 4: then the rest when reopening the linking window.Were there any errors when linking the item for the first time?I had to correct it from the database.Now should be fine.\'", "Comment 5: \'It´s okay now.No", "Comment 6: it is firt time for longer period when I had problem with linking.\'", "Comment 7: \'The question is whether this is an incident", "Comment 8: please check in the following days if the problem will repeat for other items linking and send a example.\'", "Comment 9: \'Hi", "Comment 10: today I have linked item. it was ok.\'", "Comment 11: \'Can we close it as an incident?\'", "Comment 12: \'Hi", "Comment 13: today. another link was created. Everything is okay. you can close the issue.thx\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8909\n\n### Instruction:\nHi\r\n\r\nWe have this GDC-805 to select Packing Form for ShippingNotice item when creating VT based on Shipping Notice.\r\n\r\nHowever, we are facing an issue, because now the Packing Form for ShippingNotice item is Packed, but DHP is getting the Packing form from Item when creating the VT based on Shipping Notice.\r\n\r\nI integrated a Shipping Notice Trip from ERP to DHP test server, so you can check by yourself this case: CG040192\r\n\r\nCould you please fix that?\r\n\r\nThank you very much!\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: \'Dear Maicon,The DGS project is to raise the incident/issue tickets related to the production environment. In case of introducing new features or modifying existing ones please rise a GDC ticket", "Comment 4: for questions or issues on the test environment you can rise a DHITS.Regards\'", "Comment 5: \'!image-2023-04-05-14-32-25-042.png!!image-2023-04-05-14-33-41-853.png! !image-2023-04-05-14-32-25-042!!image-2023-04-05-14-33-41-853!\'", "Comment 6: \'Plus this is how item is configured in DHC", "Comment 7: it is a bulk!image-2023-04-05-14-36-39-044.png!\'", \'Comment 8: "Hi [~Aleksandra.Przybylek@kotrak.com]I understand the differences betweem GDC and DGS. I\\\'m sorry if I wasn\\\'t too clear in the description of issue. I thought that mentining the GDC would help the understanding of this issue\', "Comment 9: but I screwed up. I\'m sorry!*Let me try again:*h4. SCENARIOWe have the ShippingNotice document in DHP!As far as I was informed", \'Comment 10: when creating the VT\', \'Comment 11: the +Packing form+ in VT will get this information from the ShippingNotice Element.h4. ISSUEWhen creating the VT document based on Shipping Notice\', \'Comment 12: instead of getting the +Packing form+ from Shipping Notice\', \'Comment 13: it is getting the +Packing form+ from the Article card.Could you please help with that?"\', \'Comment 14: "Hi [~mberbert@deheus.com]That\\\'s not the point. Your scenario and description says about test environment. And on service desk we can only verify issue on Production environment. I understand your scenario. But still\', \'Comment 15: I need example from porduction\', \'Comment 16: otherwise you need to create DHITS to check on test.Best regards :)"\', "Comment 17: \'HiYou can check *CG041697* in the Production environmentThank you!image-3!\'", "Comment 18: \'!image-2023-04-06-09-29-46-904.png! Dla wszystkich itemów packing form = bulk!image-2023-04-06-09-37-04-998.png!!image-2023-04-06-10-15-56-866.png!!image-2023-04-06-10-16-31-716.png!!image-2023-04-06-10-15-56-866! !image-2023-04-06-10-16-31-716!\'", "Comment 19: \'21518!image-2023-04-06-09-39-06-364.png!21500!image-2023-04-06-09-38-44-044.png!21533!image-2023-04-06-09-39-31-842.png!21509-MP!image-2023-04-06-09-40-02-948.png!\'", "Comment 20: \'HejOlcia [~aleksandra.masternak@kotrak.com]MAciek [~maciej.dobrzanski@kotrak.com]pytanko mam:Berbeć powiada", \'Comment 21: że jak na SN jest packed\', \'Comment 22: to na VT też powinien być packed\', \'Comment 23: ale:>> item w DHC i DHP jest bulk (wszystkie 4)\', \'Comment 24: czyli zakładam\', \'Comment 25: że w erp też tak jest>> zakładam również\', \'Comment 26: że packing form został na SN zmieniony ręcznie\', \'Comment 27: być może na poziomie erpa>> pytanie: czy przy tworzeniu VT bierze packing form z SN czy jednak z konfiguracji itema?Berbeć podpiera się tym stwierdzeniem:!image-2023-04-06-10-13-28-377.png|width=737,height=177!Ale chyba nie doczytał reszty\', \'Comment 28: i znadinterpretował...Niestety\', \'Comment 29: do tego tripa nie ma VT w systemie\', "Comment 30: ale z chęcią stworzę if you agree!image-2023-04-06-10-15-11-479.png!\'", \'Comment 31: \\\'[~aleksandra.przybylek@kotrak.com]Co mają ustawione w konfigu w VC "Vehicle ticket from shipping notice generation policy"? Może jest tam wybrane itemsettlement zamiast default?Bo generalnie powinno to działać tak:DefaultVehicleTicketFromShippingNoticeGenerationPolicy - patrzy na packing form elementu ASNA\', \'Comment 32: wiec powinien utworzyć pakowane elementy.ItemSettlementTypeVehicleTicketFromShippingNoticeGenerationPolicy - patrzy na settlement type itema\', \'Comment 33: więc jeśli te elementy mają settlement type bulky\', "Comment 34: to powinien utworzyć bulkowe elementy\'", "Comment 35: \'[~aleksandra.masternak@kotrak.com]Mają niby poprawnie:!image-2023-04-06-11-18-51-756.png!Tylko w tym przypadku chyba jedyna metoda weryfikacji", \'Comment 36: to create VT. Bo ten ASN nie ma jeszcze VT. Więc ewentualnie trzeba wierzyć mu na słowo :PWybacz\', \'Comment 37: że troszku zeszło\', "Comment 38: P1 z Vietnamu miałam :)\'", "Comment 39: \'Hi [~Aleksandra.Przybylek@kotrak.com]Any news from this task?We need to start using the functionality this asap.Thank you\'", "Comment 40: \'Aktualnie dla dispatcha działa to w oparciu o settlement type na kartotece towarowej", "Comment 41: jesli chca zmiany to musza zrobić GDC.\'", "Comment 42: \'Hi Maicon,We have investigated your case. Currently", \'Comment 43: for dispatch VT\', \'Comment 44: it takes settlement type from item card.If you need a change\', "Comment 45: please raise a GDC task.Regards\'", \'Comment 46: "Hi [~Aleksandra.Przybylek@kotrak.com]I won\\\'t raise a new GDC for that we already have one: GDC-805I received the information in the GDC-805 that this Packing form needs to come in Shipping notices from ERP\', \'Comment 47: now I have new information.Could you please talk with Maciej Dobrzański and Theo Berendsen and check what information is right?Thank you"\', "Comment 48: \'Hi [~mberbert@deheus.com],As I understand this DGS correctly it refers to the TRIP (ASN for dispatch).The rules for creating vehicle tickets based on ASN differ on whether it is for dispatch or intake. What is more", \'Comment 49: we have more than one policy for generating Vehicle tickets from shipping notices eg. In the case of ASN intake (packing form and settlement type) are considered and for dispatch only (item settlement type)The request from GDC-805 is in my opinion different. First of all\', \'Comment 50: you mentioned raw materials so that is why we understood it as an ASN for intake\', \'Comment 51: not dispatch. It was described so the user will be able to choose the packing form on the Vehicle Ticket\', "Comment 52: not on the Shipping notice during the generation of the Vehicle Ticket.I suggest scheduling a meeting with Theo in order to discuss all of the details.\'", \'Comment 53: "Hi [~mberbert@deheus.com]Is Maciej\\\'s explanation sufficient for you? Can we close this task?Regards"]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8908\n\n### Instruction:\nwe have problem in recipe scale when element is added by additional techologies, DHC is not adding the scale.\r\n* example: item SUE1605-S25 version 114/1, we added the element ROPBCO12A scale type bag, but in the recipe the field is empty, when integrate to DHP was added automatically the scale macro, and the element is sent for wrong production area when integrate to PCS.\r\n\r\nCould you check why recipe is without scale and fix it the functionality (not only this recipe)?\r\n\r\nThank you\r\n\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: " !screenshot-1! {code:java}2023-04-04 09:42:11,487 [311] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Production.ProductionRecipes.Events.ProductionRecipeChangedEvent[ProductionRecipeId=\\\'81ccab2b-0573-44da-827b-cbe2d1baee20\\\']] to publisher [Evolution.Events.EventPublisher] under domain context [d22dcd7d00654c0b96f1d79170665cad]2023-04-04 09:42:12,722 [DefaultQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Core.QuartzSchedulerThread [(null)] - Batch acquisition of 0 triggers2023-04-04 09:42:16,648 [330] DEBUG Evolution.DHCountry.Logging.DomainCommandHandlerWithLog4NetTracing [(null)] - Handled command [Evolution.DHCountry.Production.ProductionRecipes.Commands.AcceptProductionRecipeCommand] by command handler [Evolution.DHCountry.Domain.DomainCommandHandlerWithPublishingEvents] under domain context [32a19184cb3c48929b8a3babde1b2592]2023-04-04 09:42:16,723 [330] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Production.ProductionRecipes.Events.ProductionRecipeAcceptedEvent[ProductionRecipeId=\\\'81ccab2b-0573-44da-827b-cbe2d1baee20\\\']] to publisher [Evolution.Events.EventPublisher] under domain context [2c2168f4537d4cf6a854dae6c6987f08]{code}{code:java}/****** Script for SelectTopNRows command from SSMS ******/SELECT * FROM [Evolution_DHCountry].[dbo].[TechnologyIngredients] where TechnologyId=\\\'833ED31F-5249-48B0-9A45-20BCF32BAF0D\\\' SELECT ScaleType,* FROM [Evolution_DHCountry].[dbo].[Items] where id=\\\'B45C5C4A-49B3-41E7-AD40-AE65FED4A8EF\\\'------------------------------2023-04-04 09:42:25,642 [183] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Production.Technologies.Events.TechnologyGeneratedEvent[TechnologyId=\\\'833ed31f-5249-48b0-9a45-20bcf32baf0d\\\']] to publisher [Evolution.Events.EventPublisher] under domain context [90b7c4d930174e85b8ada49eda5ccf4b]{code}!image-2023-04-11-08-56-20-136!"\', "Comment 4: \'DHC nie przenosi się Scale type do pozycji technologi jak klient dodaje element z poziomu add.technology. Jak to można zreprodukować? Jest jeszcze coś takiego ale tutaj wygląda że chodzi o planta? DGS-8807\'", "Comment 5: \'Na widoku related items ScaleType brane jest z składnika technologii połączonej do production recipe.Jeżeli nie ma technologii", \'Comment 6: jest generowana.Widzę\', "Comment 7: że przy dodawaniu packing technologii w AddPackagingTechnologyActivity nie jest przepisywane scaleType !screenshot-2! Wymagana jest zmiana \'", "Comment 8: \'Prosił bym aby konsultować wpisywanie DGS reason w przypadku Application Bug", "Comment 9: to że user oczekiwał ze aplikacja działa inaczej nie oznacza zaraz że jest to błąd aplikacji.\'", "Comment 10: \'[~psilva@deheus.com]this is how the Additional Technology Form was designed. If you would like to change this please contact PO Wijnand van Geerenstein but I also this that change https://helpdesk.kotrak.com/browse/GDC-895will solve this issue.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8907\n\n### Instruction:\nOn printout there is verification on document which Round category exist on Invoice, but in this case there is no \'Doc No. Intense\'.\r\n When there is no Intense document on S2P like on screen it\'s treated as a invoice from Slaughtery section.\r\n\r\n\r\n I think in those cases we should always go for “Voer”, because feed deliveries can be missing in Intense (but existing in Milas). Slaughter revenues can never not exist in Intense.\r\n\r\n!https://attachments.office.net/owa/damian.swistek%40kotrak.com/service.svc/s/GetAttachmentThumbnail?id=AAMkADY2ZTAxMzM3LTE0YjctNGI0Ni1hYjIxLWE3MDFjOTVkNmExNwBGAAAAAAA%2FcPjpt4lNRZFonusrO6C9BwA5bA29TyJrQIX6A6F8SkSqAAAAAAEJAAA5bA29TyJrQIX6A6F8SkSqAATcM30IAAABEgAQAI9G%2Bh4R%2FQROh0ZHcQ%2B8g%2Fs%3D&thumbnailType=2&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IkQ4OThGN0RDMjk2ODQ1MDk1RUUwREZGQ0MzODBBOTM5NjUwNDNFNjQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiIySmozM0Nsb1JRbGU0Tl84dzRDcE9XVUVQbVEifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiNzQ1YWJkOWJmNWUxNGJhMWJkNjE5OTZmNzhmMzQzNGYiLCJzaWduaW5fc3RhdGUiOiJbXCJrbXNpXCJdIiwidmVyIjoiRXhjaGFuZ2UuQ2FsbGJhY2suVjEiLCJhcHBjdHhzZW5kZXIiOiJPd2FEb3dubG9hZEA5OGIwMzVmZi1iMTIxLTQ1OGItYTNmMC0zMjM1NGRiMWI3ODEiLCJpc3NyaW5nIjoiU0lQIiwiYXBwY3R4Ijoie1wibXNleGNocHJvdFwiOlwib3dhXCIsXCJwdWlkXCI6XCIxMTUzNzY1OTMyMzQ4MzE1MTQ3XCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIixcIm9pZFwiOlwiYjU1MGNmY2EtYjZhYS00NmFkLWFlYjAtZTllNjIyYTMyOTE2XCIsXCJwcmltYXJ5c2lkXCI6XCJTLTEtNS0yMS0zNjk5NTUyNDA4LTIxNDA2MTAxMy0yMzI0NTA4MTctMTMxMDk3OTRcIn0iLCJuYmYiOjE2ODA2MTY3ODEsImV4cCI6MTY4MDYxNzM4MSwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImhhcHAiOiJvd2EifQ.RxgLnlWD94h6yCeFLSc0ElebIk2_fYnT0n7Gjm-5oLh8oHzyGA2cAoSGutoOBWYRnM2DhaoniNCNVPoX099BZOB9HRjUjxPDjorUqV6Kh626Om9RcPHMJiYX66yVZLglQukCUY6aNlKSDM9dGAOkJTHcfhBGPiEDnEhbmyy1ssOjfZZO0gCc0FsDSvcsfoifpQ-ilVV5vVK-JPfvLM8D933lpkpL1N5BDFIxox3W7uZk1VVuzXx1ytIpRt8rqOqiKw2xT6uDxP1eDBavZq48bYJNgQ6Li8uYRnVPju-HNLlYMdddEQykRdfQZ3TDbkKEf5O0mMyWnMfJxRPNA4tP-Q&X-OWA-CANARY=GLSHExmL6Eu7znDmDGZ5nxB-2n0VNdsYJ-jRsGybjBBV9mGxDMviQ4OL_y0B6YPZHiU-go2WSF4.&owa=outlook.office.com&scriptVer=20230324008.13&animation=true!\r\n\r\n!https://attachments.office.net/owa/damian.swistek%40kotrak.com/service.svc/s/GetAttachmentThumbnail?id=AAMkADY2ZTAxMzM3LTE0YjctNGI0Ni1hYjIxLWE3MDFjOTVkNmExNwBGAAAAAAA%2FcPjpt4lNRZFonusrO6C9BwA5bA29TyJrQIX6A6F8SkSqAAAAAAEJAAA5bA29TyJrQIX6A6F8SkSqAATcM30IAAABEgAQAHIKh4tjHrZCoo2dB%2FrRHHk%3D&thumbnailType=2&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IkQ4OThGN0RDMjk2ODQ1MDk1RUUwREZGQ0MzODBBOTM5NjUwNDNFNjQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiIySmozM0Nsb1JRbGU0Tl84dzRDcE9XVUVQbVEifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiNzQ1YWJkOWJmNWUxNGJhMWJkNjE5OTZmNzhmMzQzNGYiLCJzaWduaW5fc3RhdGUiOiJbXCJrbXNpXCJdIiwidmVyIjoiRXhjaGFuZ2UuQ2FsbGJhY2suVjEiLCJhcHBjdHhzZW5kZXIiOiJPd2FEb3dubG9hZEA5OGIwMzVmZi1iMTIxLTQ1OGItYTNmMC0zMjM1NGRiMWI3ODEiLCJpc3NyaW5nIjoiU0lQIiwiYXBwY3R4Ijoie1wibXNleGNocHJvdFwiOlwib3dhXCIsXCJwdWlkXCI6XCIxMTUzNzY1OTMyMzQ4MzE1MTQ3XCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIixcIm9pZFwiOlwiYjU1MGNmY2EtYjZhYS00NmFkLWFlYjAtZTllNjIyYTMyOTE2XCIsXCJwcmltYXJ5c2lkXCI6XCJTLTEtNS0yMS0zNjk5NTUyNDA4LTIxNDA2MTAxMy0yMzI0NTA4MTctMTMxMDk3OTRcIn0iLCJuYmYiOjE2ODA2MTY3ODEsImV4cCI6MTY4MDYxNzM4MSwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImhhcHAiOiJvd2EifQ.RxgLnlWD94h6yCeFLSc0ElebIk2_fYnT0n7Gjm-5oLh8oHzyGA2cAoSGutoOBWYRnM2DhaoniNCNVPoX099BZOB9HRjUjxPDjorUqV6Kh626Om9RcPHMJiYX66yVZLglQukCUY6aNlKSDM9dGAOkJTHcfhBGPiEDnEhbmyy1ssOjfZZO0gCc0FsDSvcsfoifpQ-ilVV5vVK-JPfvLM8D933lpkpL1N5BDFIxox3W7uZk1VVuzXx1ytIpRt8rqOqiKw2xT6uDxP1eDBavZq48bYJNgQ6Li8uYRnVPju-HNLlYMdddEQykRdfQZ3TDbkKEf5O0mMyWnMfJxRPNA4tP-Q&X-OWA-CANARY=1mI5yJ-jBEuBYBZ0G7hUesA1F1cVNdsYKjzn0au9aJcB07w9uuqnY6Elc3kjLAOeLl8vEy_44pU.&owa=outlook.office.com&scriptVer=20230324008.13&animation=true!\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: [\\\'[~mbovene@deheus.com],we\\\\\\\'ve made changes for empty "Doc No. Intense" in S2P new printouts (MAS NL\', "Comment 2: MAS BE).You can verify it.Best regards,Grzegorz\'", "Comment 3: \'Do przeniesienia na Prod!image-2023-04-21-13-30-38-807.png!\'", \'Comment 4: "Hi [~mbovene@deheus.com],we\\\'ve moved it to the PROD Intense environment.Best regards,Grzegorz"\', "Comment 5: \'Can be closed\']"]\nRelated Issues:\n[\'DGS-8326\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8906\n\n### Instruction:\nOn Round is displayed and in this column for SI Regular and Financed there is displayed Delivery date from Leading doc - Purchasae Invoice where Delivery date is 6.12.2022\r\n\r\n!https://attachments.office.net/owa/damian.swistek%40kotrak.com/service.svc/s/GetAttachmentThumbnail?id=AAMkADY2ZTAxMzM3LTE0YjctNGI0Ni1hYjIxLWE3MDFjOTVkNmExNwBGAAAAAAA%2FcPjpt4lNRZFonusrO6C9BwA5bA29TyJrQIX6A6F8SkSqAAAAAAEMAAA5bA29TyJrQIX6A6F8SkSqAATeOusYAAABEgAQAIpBwolwUt5Kp9labJwZCpM%3D&thumbnailType=2&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IkQ4OThGN0RDMjk2ODQ1MDk1RUUwREZGQ0MzODBBOTM5NjUwNDNFNjQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiIySmozM0Nsb1JRbGU0Tl84dzRDcE9XVUVQbVEifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiNzQ1YWJkOWJmNWUxNGJhMWJkNjE5OTZmNzhmMzQzNGYiLCJzaWduaW5fc3RhdGUiOiJbXCJrbXNpXCJdIiwidmVyIjoiRXhjaGFuZ2UuQ2FsbGJhY2suVjEiLCJhcHBjdHhzZW5kZXIiOiJPd2FEb3dubG9hZEA5OGIwMzVmZi1iMTIxLTQ1OGItYTNmMC0zMjM1NGRiMWI3ODEiLCJpc3NyaW5nIjoiU0lQIiwiYXBwY3R4Ijoie1wibXNleGNocHJvdFwiOlwib3dhXCIsXCJwdWlkXCI6XCIxMTUzNzY1OTMyMzQ4MzE1MTQ3XCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIixcIm9pZFwiOlwiYjU1MGNmY2EtYjZhYS00NmFkLWFlYjAtZTllNjIyYTMyOTE2XCIsXCJwcmltYXJ5c2lkXCI6XCJTLTEtNS0yMS0zNjk5NTUyNDA4LTIxNDA2MTAxMy0yMzI0NTA4MTctMTMxMDk3OTRcIn0iLCJuYmYiOjE2ODA2MTY3ODEsImV4cCI6MTY4MDYxNzM4MSwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImhhcHAiOiJvd2EifQ.RxgLnlWD94h6yCeFLSc0ElebIk2_fYnT0n7Gjm-5oLh8oHzyGA2cAoSGutoOBWYRnM2DhaoniNCNVPoX099BZOB9HRjUjxPDjorUqV6Kh626Om9RcPHMJiYX66yVZLglQukCUY6aNlKSDM9dGAOkJTHcfhBGPiEDnEhbmyy1ssOjfZZO0gCc0FsDSvcsfoifpQ-ilVV5vVK-JPfvLM8D933lpkpL1N5BDFIxox3W7uZk1VVuzXx1ytIpRt8rqOqiKw2xT6uDxP1eDBavZq48bYJNgQ6Li8uYRnVPju-HNLlYMdddEQykRdfQZ3TDbkKEf5O0mMyWnMfJxRPNA4tP-Q&X-OWA-CANARY=y6c3QNbRokWcBtjbMC8OwkCPftcUNdsYXm6OfBQhJ-droiov8sMRjvX3fVB2LsdtmZ3VP1Y1aCU.&owa=outlook.office.com&scriptVer=20230324008.13&animation=true!\r\n\r\n\xa0\r\n\r\n\xa0\r\n\r\n!image-2023-04-04-15-59-22-635.png!\n\n### Response:\n[\'Comment 1: ["Do zmiany wyświetlanie \\\'Delivery date\\\' dla SI Regular i SI Financed. Powinna być wyświetlana Delivery date z dokumentu SI\', \'Comment 2: a nie z PI\', \'Comment 3: który jest Leading doc."\', "Comment 4: \'Changed on production and test database.\'", "Comment 5: \'Can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8905\n\n### Instruction:\nSee attached screenshot, the \'unsupported VT close direction\' error is new for me: Can you please check and solve, and advice how to prevent this next time?\r\n\r\nVT-1916/3/23\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hi", \'Comment 4: I have now information about missing stock\', "Comment 5: can you please check again? !screenshot-1! \'", "Comment 6: \'After adding stock", "Comment 7: I get the same message: !afbeelding-1!\'", \'Comment 8: \\\'{code:java}2023-04-17 08:53:36 (a4569f8e-3213-4200-832c-88063fcc7253/Plant.VC.BusinessLogic/DHVD01AP183/23516/12) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 9: "host": { "Value": "dhvd01ap183:82"\', \'Comment 10: "HasValue": true\', \'Comment 11: "Host": "dhvd01ap183"\', \'Comment 12: "Port": 82 }\', \'Comment 13: "path": "/api/VehicleTicket/registerBulkDispatchElementWeightsToVehicleTicket"\', \'Comment 14: "queryString": []\', \'Comment 15: "requestBody": "{\\\\\\\\"vehicleTicketId\\\\\\\\":\\\\\\\\"714f3e93-1639-450f-ac66-09ccd9b367b6\\\\\\\\",\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"vehicleTicketNo\\\\\\\\":12,\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1360}},{\\\\\\\\"vehicleTicketNo\\\\\\\\":14,\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2012}}]}"}.Kotrak.Extensions.Validation.Abstractions.ValidationException: Validation failed: -- Vehicle ticket should be in dispatch in progress -- Vehicle ticket should be in dispatch completed -- Vehicle ticket should be released for dispatch ---> Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.VehicleTicketInvalidDispatchOperationException: Validation failed: -- VehicleTicketShouldBeInDispatchInProgressMessage -- VehicleTicketShouldBeInDispatchCompletedMessage -- VehicleTicketShouldBeReleasedForDispatchMessage at Plant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicket.PerformBulkDispatchInitialWeighing(Int32 vehicleTicketElementId\', \'Comment 16: Weighing weighing) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicket.cs:line 947 at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.DefaultFeedRecalculationPolicy.RecalculateFeed(VehicleTicket vehicleTicket\', \'Comment 17: ICurrentUserPolicy currentUserPolicy\', \'Comment 18: String weighbridgeId\', \'Comment 19: IEnumerable`1 changedElements) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\DefaultFeedRecalculationPolicy.cs:line 33 at Plant.VC.BusinessLogic.Domain.VehicleTickets.Services.Implementations.RegisterBulkDispatchDomainService.RegisterBulkDispatchWeights(RegisterMultipleBulkDispatchWeightsDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\Implementations\\\\\\\\RegisterBulkDispatchDomainService.cs:line 66 at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketBulkDispatchService.RegisterBulkDispatchWeights(RegisterMultipleBulkDispatchWeightsDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketBulkDispatchService.cs:line 327 at Plant.VC.BusinessLogic.Application.VehicleTickets.CommandHandlers.RegisterBulkDispatchElementWeightsToVehicleTicketCommandHandler.Handle(RegisterBulkDispatchElementWeightsToVehicleTicketCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\RegisterBulkDispatchElementWeightsToVehicleTicketCommandHandler.cs:line 29 at Kotrak.Common.Infrastructure.Gate.CommandEnvironment.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.Gate.Filters.CommandProcessFilter`1.Execute(CommandPipelineContext`1 input) at Kotrak.Extensions.Pipeline.PredefinedFilters.FilterDecorator`1.Execute(TContext input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command) at Plant.VC.BusinessLogic.Infrastructure.Api.Controllers.VehicleTicketController.RegisterBulkDispatchElementWeightsToVehicleTicket(RegisterBulkDispatchElementWeightsToVehicleTicketViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\VehicleTicketController.cs:line 558 at lambda_method20037(Closure \', \'Comment 20: Object \', \'Comment 21: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 22: ObjectMethodExecutor executor\', \'Comment 23: Object controller\', \'Comment 24: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 25: Scope& scope\', \'Comment 26: Object& state\', \'Comment 27: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.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 28: Scope& scope\', \'Comment 29: Object& state\', \'Comment 30: 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 31: Task lastTask\', \'Comment 32: State next\', \'Comment 33: Scope scope\', \'Comment 34: Object state\', \'Comment 35: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 36: Task task\', \'Comment 37: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 38: Task task\', \'Comment 39: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 40: Task requestTask\', \'Comment 41: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', "Comment 42: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext) --- End of inner exception stack trace ---{code}!image-2023-04-17-15-48-11-121! !image-2023-04-17-15-48-49-471!!image-2023-04-17-15-49-42-126!!image-2023-04-17-15-58-39-468!\'", "Comment 43: \'Hello,The VT status has been corrected from the database and a message about closing the VT has been sent again to WMS. After the changes in version 8.6 the problem should not occur. The theme of the changes is manageable response time between modules.Regards.\'", "Comment 44: \'Oke thanks. same problem also applies to \'", "Comment 45: \'VT-452/4/23\'", \'Comment 46: "{code:java}SELECT v.Status,s.status FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTickets] v join DHPlantStockBusinessLogicMain.[dbo].[VehicleTickets] son v.id=s.id where v.DocumentNumber=452 and v.DocumentMonth=4 and v.DocumentYear=2023 select * FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnitReleases] where SourceDocumentId=\\\'abbebe20-b427-4417-b157-5460b44633cd\\\'{code} !image-2023-04-18-15-02-53-873.png!"\', "Comment 47: \'VT-1916 został poprawiony ", \'Comment 48: zgłosili kolejny gdzie status VT-452/4/23 jest 110 w bazach stock\', \'Comment 49: vc.nie ma już rezerwacji\', "Comment 50: WO są executed.Jakby co jestem do dyspozycji :).\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8904\n\n### Instruction:\nVT\'s are send to pcs, without the deliveryID: This is needed for processing in the pcs system: please solve this, intakes cannot be done automatically at this moment.\r\n\r\n2 example VTs:\r\nVT-128/4/23\r\nVT-12/4/23\r\n\r\n\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "Comment 2: \'VT-127/4/23\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'!image-2023-04-04-13-23-58-332.png!\'", \'Comment 5: "select * from VehicleTicketElements where id in (\\\'7C1AAAAD-D0C1-4E3A-9B8E-3D64115FD064\\\',\\\'1714F1F6-47A0-4638-B8C6-5A359D5BDF3F\\\')"\', "Comment 6: \'w dhc service też brak deliveryid!image-2023-04-04-13-33-26-434.png!\'", "Comment 7: \'!image-2023-04-04-13-45-08-274.png!\'", "Comment 8: \'wydaje się być powiązane z tymhttps://helpdesk.kotrak.com/browse/DGS-8263\'", "Comment 9: \'select * FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[InboundMessages] where Retries>1jeden problem!image-2023-04-04-13-55-03-837.png!\'", "Comment 10: \'!image-2023-04-04-13-57-22-784.png!\'", \'Comment 11: \\\'uusnieto event wiszacy z 900 retry messageselect * FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[InboundMessages]{"DeliveryId":\\\\\\\\{"Id":"68c0b827-b28f-41c9-aaeb-029e79548330"},"InitialOwnerId":\\\\\\\\{"Id":"423c58b5-f3a8-4e9d-817d-63710a86c93e"},"BusinessUnitId":\\\\\\\\{"Id":"423c58b5-f3a8-4e9d-817d-63710a86c93e"},"ItemId":\\\\\\\\{"Id":"b81ceec3-4ed3-42ba-86f0-4ff700074a3b"},"CreatedDate":"2023-04-03T06:11:44.2540018+02:00","InitialSourceDocument":\\\\\\\\{"DocumentId":{"Id":"3d6bdfad-4d53-47ba-a6d4-a5fa9742de3e"},"DocumentNo":1,"DocumentNumber":"VT-17/4/23","DocumentTypeValue":100},"SourceDocument":\\\\\\\\{"DocumentId":{"Id":"3d6bdfad-4d53-47ba-a6d4-a5fa9742de3e"},"DocumentNo":1,"DocumentNumber":"VT-17/4/23","DocumentTypeValue":100},"SerialNumber":null,"ForeignSerialNumber":null,"InternalSerialNumber":"VT-17/4/23-1","Quantity":\\\\\\\\{"Unit":"kg","Value":0.0},"ProducerId":null,"ExpiryDate":null,"IsMedicated":false,"IsBrokenBatch":false,"UnitLoadId":null,"BusinessPartners":[],"OrderElements":[]}\\\'\', \'Comment 12: "eventid=id=\\\'303F8B94-E88A-4E01-AC19-97A92FE2754F\\\'"\', "Comment 13: \'deliveries were not created because the database was locked the following session", "Comment 14: looks like a query to create/modify indexes!image-2023-04-04-15-18-42-679.png|width=926,height=196!\'", \'Comment 15: "trzeba pilnowac te dostawe :select * FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[InboundMessages] where Id =\\\'303F8B94-E88A-4E01-AC19-97A92FE2754F\\\'"\', "Comment 16: \'insert into DHPlantPCSBusinessLogicIntercontext.dbo.InboundMessages(Id", \'Comment 17: ReceivedAt\', \'Comment 18: Retries\', \'Comment 19: MessageType\', \'Comment 20: Message\', \'Comment 21: ProcessDate\', \'Comment 22: Queue\', \'Comment 23: Metadata\', \'Comment 24: CreatedAt\', \'Comment 25: MetadataType\', \'Comment 26: Priority\', \'Comment 27: PriorityText\', \'Comment 28: Sender\', \'Comment 29: SentAt\', \'Comment 30: Status\', \'Comment 31: StatusText)select d.Id\', \'Comment 32: GETDATE()\', \'Comment 33: 0\', \'Comment 34: d.EventType\', \'Comment 35: d.Event\', \'Comment 36: GETDATE()\', "Comment 37: \\\\\'Plant.Stock.BusinessLogic.DomainAbstractions\\\\\'", \'Comment 38: \\\\\\\'\\\\\\\\{"CorrelationId":{"Id":"\\\\\\\'+CAST(NEWID() AS NVARCHAR(MAX))+\\\\\\\'"}}\\\\\\\'\', \'Comment 39: GETDATE()\', "Comment 40: \\\\\'Kotrak.Common.Infrastructure.Integration.IntercontextMessageMetadata", \'Comment 41: Kotrak.Common.Infrastructure.Integration\', \'Comment 42: Version=6.5.0.0\', \'Comment 43: Culture=neutral\', "Comment 44: PublicKeyToken=null\\\\\'", \'Comment 45: 3\', "Comment 46: \\\\\'Medium\\\\\'", "Comment 47: \\\\\'Stock\\\\\'", \'Comment 48: GETDATE()\', \'Comment 49: 0\', "Comment 50: \\\\\'Created\\\\\'from DHPlantStockBusinessLogicEvents.dbo.Deliveries d where d.Id = \\\\\'303F8B94-E88A-4E01-AC19-97A92FE2754F\\\\\'\'", "Comment 51: \'Any update?\'", "Comment 52: \'So it is fixed now?\'", "Comment 53: \'Yes", "Comment 54: the messages queue has been unlocked and messages have been processed.\'", "Comment 55: \'Hi", \'Comment 56: the problem was caused by unconsulted actions on the datbase (creation of indexes on the previous screenshot) not implemented by us\', "Comment 57: they caused time-outs that blocked the queue and prevented the generation of stock which caused deliveryid=0 on VT. The name of the login of the db user is visible on the screen shoot.!image-2023-04-05-08-05-48-141.png!\'", "Comment 58: \'do you still have problem with deliveryid on this vt", "Comment 59: or may we close this task?\'", \'Comment 60: "Hi,I asked the dba of Valid to investigate this. He came back with the following:================================================I’ve checked the DHVD01AG09 instance and found thatthe process in the screenshot is the weekly index maintenance.It seems it was blocked (which is also visible fromthe screenshot) from process with ID 126 which was killed yesterday afternoon:Date4-4-2023 15:14:34LogSQL Server (Current - 5-4-2023 09:45:00)Sourcespid53MessageProcess ID 126 was killed by hostname DHVD01DB45\', \'Comment 61: hostprocess ID 7696.The index maintenance was blocked during execution ofthe following:ALTER INDEX [PK_Deliveries] ON [dbo].[Deliveries]REBUILD WITH (SORT_IN_TEMPDB = OFF\', \'Comment 62: ONLINE = ON\', \'Comment 63: RESUMABLE = OFF)The table DHPlantPCSBusinessLogicEvents is 20MB with 4MB indexes and for some reason this operation was blocked for more than 2 days,meaning something else was holding lock on this table.In order to prevent such long running Index maintenance operationscaused by table locks my proposal is to limit the time for the operation towait for a lock to be released to let’s say 5 minutes. And if the lock is stillactive to continue with the next index. ===================================================I think this proposal makes sense. Do you agree? If so\', \'Comment 64: I\\\'ll ask him to implement this."\', "Comment 65: \'Hello,In this task we have focused on clearingandunblocking the process.[~mmeier@deheus.com] about the last comment", \'Comment 66: thank you for all information\', "Comment 67: please raise another task for this (SR) I will pass this to our developers to verify it.About themain subject of the task can we close it?\'", "Comment 68: \'DGS-8927 is created.@Thomas Dankers", "Comment 69: do you agree to close this one?\'", "Comment 70: \'Yes I agree\'", "Comment 71: \'Thank you\']"]\nRelated Issues:\n[\'DGS-8927\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8903\n\n### Instruction:\nWhen Anja makes a credit invoice from a PI to reverse the SI she must be able to create a SI again.\r\n\r\nShe sees the button but it is not active, so she cannot create a new SI.\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: \'Do sprawdzenia czy w tym przypadku była dostępna akcja spod pioruna do generowania SI.\'", "Comment 4: \'Due to the fact that the document was in the archive", \'Comment 5: the button was inactive\', \'Comment 6: but we got the functionality on the document that when the button is visible\', "Comment 7: at the same time the action create sales invoice from lightning is active.\'", "Comment 8: \'To verify by Anja\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8902\n\n### Instruction:\nHi, from Wiola\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'[^DGS-8902.docx]\'", "Comment 4: \'Description in the attachment[^DGS-8902.docx]^^\'", "Comment 5: \'!image-1!\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8901\n\n### Instruction:\nVT-1214/2/23 contains intake of 0303 from a barge. During intake, a correction was made on this VT. The intake was closed and has status On stock. The correction still has status In Progress and many Lot reports have made a reservation on this line. Due to this, many production reports cannot automatically be confirmed.\r\nCan you \r\n- change the status of this correction to On stock, or \r\n- remove this correction and the reservations that were made on this line?\r\n\r\nso that Lot reports that consume 0303 can be automatically confirmed\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-04-11-15-31-09-412.png!!image-2023-04-11-15-30-54-012.png!\'", \'Comment 4: \\\'Dla tego "correction" barcode:!image-2023-04-11-15-32-35-607.png!!image-2023-04-11-15-34-14-813.png!\\\'\', "Comment 5: \'Obecnie jest 67 PLRów w statusie Finished!image-2023-04-11-15-34-49-055.png!\'", "Comment 6: \'We updated the status of this stock unit. The stock can now automatically be consumed in the lot reports. This ticket can be closd.\'", "Comment 7: \'Thank you for your informationRegards\'", "Comment 8: \'Dear Bob,If you have another case like that", "Comment 9: please let us know via new task. We would like to check why this happened.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8900\n\n### Instruction:\nWe are dealing with the following situation. When Farach sends an PI to Nancy and the round number is not correct (see the example in the attachment) than Nancy is not able to select the correct round number.\r\n\r\nWhen she sends it back to entry however Farach is also not able to change the full round number. Both users should be able to do so.\r\n\r\nNote: for SI\'s this is possible at the moment. Could you make it possible for PI\'s as well?\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: \'Do sprawdzenia dla przesłanego przykładu dlaczego nie da się wybrać rundy - sprawdzenie co jest na lookupie w liście wartości i jakie są tam warunki.\'", \'Comment 4: "* For Sales invoice documents\', "Comment 5: we check whether the customer indicated in the \'customer\' field has BP_Category set as Slaughter", "Comment 6: we are looking for rounds for the customer indicated in the \'reference\' field. * For Sales invoice", \'Comment 7: which have customers in other BP_Category as likeSlaughter wejust check active rounds for this customer. * For Purchase invoice documents\', \'Comment 8: we just check active rounds for customers from \\\'Refence\\\' field"\', \'Comment 9: "[~mbovene@deheus.com]When PI is generated from SI Full round number is copied to PI. Probably you expect that it will be possible to choose rounds from \\\'Supplier\\\'\', "Comment 10: but it\'s possible right now to choose only rounds from \'Reference\'", \'Comment 11: not from Supplier.Should we adjust it somehow?"\', "Comment 12: \'Yes", \'Comment 13: please make the rounds for the user who is selected as "Supplier" available as well.\\\'\', "Comment 14: \'It has been done in task [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-9012]Please verify that is possible.\']"]\nRelated Issues:\n[\'DGS-9012\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8899\n\n### Instruction:\nFor some labels the feeding program section in the XML to MILAS is not populated with feeding programs.\r\n\r\nE.g. item 705900 and item 704922 .\r\nIf you check the most recent label messages that are sent from DHC there should be a feeding program in it. \r\n705900 should contain BE\r\nand the other one a whole list: \r\nBE\r\nQS\r\nVP\r\nVB\r\nVG\r\nCV\r\nVC\r\nDU\r\nDV\r\nBE\r\nQS\r\nVP\r\nVB\r\nVG\r\nCV\r\nVC\r\nDU\r\nDV\r\n\r\nCan you please check why it is not send. Probably this is the case for more labels. Is there a way to find out for which ones it goes wrong and since when?\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: \'Wchodząc w Label config np. nie ma BE dla Feeding program - !screenshot-1! Ale inne już są.!image-2023-04-11-09-53-33-863!\'", "Comment 3: \'synchro z MILAS było GDC-719", \'Comment 4: czy to jest ten zakres zmian? Wchodząc w Label config np. nie ma BE dla Feeding program\', "Comment 5: ale inne już są.\'", "Comment 6: \'label configuration nie ma nic do tego\'", "Comment 7: \'niech podadzą dla których fabryk", "Comment 8: widzę ze dla jednych fabryk te informacje otrzymujemy z bestmixa a dla innych nie więc pewnie muszą się pokornie udać do działu nutrition.\'", "Comment 9: \'Hello", "Comment 10: we need an additional information. For which factories is the problem?because for some this information is provided from Bestmix.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8898\n\n### Instruction:\nPlant Maasbracht sometimes has big delays in printing of SPS. In those cases plant is using PCS printouts, but that is not desired, because e.g. label information is missing\r\nI tried to analyze the following case:\r\n\r\nSO-12553/3/23\r\ntrip 00999257\r\n2 sales orders: SOBE000018544 (SO-13410/3/23) en SOBE000018362 (SO-12553/3/23)\r\n\r\nVT-2136/3/23 \r\ncreationdate: 29/03/2023 6:34 AM (corresponds to dispatch message received from PCS for order SO-12553/3/23)\r\nclosed: 29/03/2023 6:54 AM (corresponds to dispatch message received from PCS for order SO-13410/3/23)\r\n\r\nGeneration of XML for SPS for both sales orders: 07.25\r\n\r\nSo, the dispatch message from PCS is processed immediately in the VT.\r\nHowever, the XML for Transform is genertated 50 (for first order) -30 (for second order) minutes later!\r\n\r\nWhat can cause these delays? Is the process to close Lot reports/VT\'s (I remember this was the issue in Utrecht)? \r\nHow can we solve this issue? Plant mus be able to deliver correct SPS to the driver directly after dispatch is registered.\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: \'[~maciej.dobrzanski@kotrak.com]czy mamy jakiś sposób", "Comment 3: żeby zbadać przyczynę opóźnień? :)\'", "Comment 4: \'Hello,Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'", "Comment 5: \'[~aleksandra.przybylek@kotrak.com] możemy zrobić RCA i zaplanować to analizy\'", "Comment 6: \'Hi Bob,We have discussed your task. As you have asked for analysis of the rootcause", \'Comment 7: due to service process\', \'Comment 8: we need to close this incident and raise RCA task. Please\', "Comment 9: let us know if you accept RCA task.Regards\'", "Comment 10: \'[~aleksandra.przybylek@kotrak.com] to może być też przczyną tych opóźnień:https://helpdesk.kotrak.com/browse/DGS-8904?focusedCommentId=1120975&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1120975\'", "Comment 11: \'Hi Bob,Are you able to tell me if there is anydelay in printing of SPS today? If any delay occurs today", "Comment 12: could you please let me know?Regards\'", "Comment 13: \'Tak na szybko", \'Comment 14: inbound czysto:!image-2023-04-05-11-29-55-423.png!Tu też czysto:!image-2023-04-05-11-30-55-006.png!!image-2023-04-05-11-31-40-043.png!Musieliby rzeczywiście dać znać\', \'Comment 15: że tu i teraz jest opóźnienie\', "Comment 16: a nie tydzień temu ...\'", "Comment 17: \'Plant is not reporting every delay directly. I am not able to provide this information. I did not get any further information about delays. This task can be closed.\'", "Comment 18: \'Sure. Waiting for new examples and new task then.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8897\n\n### Instruction:\nUsers who close S2P documents should have access to inboxes of other users who has linked documents Financial Statement, Round, Feed sale in their inboxes.\r\n\r\nIt\'s related to recent changes in S2P closing: If the user sends S2P to Archive via flow, others documents such as FS, Round and Feed sale will also be in Archived status.\xa0\r\n\r\n\xa0\r\n\r\nExample\xa0SP-M/0706\r\n\r\nS2P has been sent to Archive\r\n\r\nFS has been sent to Archive\r\n\r\nRound hasn\'t been sent to Archive\r\n\r\nFeed sale hasn\'t been sent to Archive.\r\n\r\n\xa0\r\n\r\nRound\r\n!image-2023-04-03-15-17-47-365.png!\r\n\r\nUsers shared inboxes\r\n\r\n!image-2023-04-03-15-18-04-171.png!\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: ["The solution will be to extend shared inboxes for users who can close S2P\\\'s and give them access to all users who can create Round\', \'Comment 2: Financial Statement\', \'Comment 3: S2P.[~mbovene@deheus.com]do you know which users are closing S2P documents?We can also verify who can process S2Ps and give them access to inboxes ofusers who can create Rounds\', \'Comment 4: Feed sales\', \'Comment 5: Financial statement. If we should do it in that way\', \'Comment 6: please let us know and we can also prepare some analysis to be sure that we don\\\'t want to give access for too many users."\', "Comment 7: \'do you know which users are closing S2P documents? -->MAS: Nancy van Dam", \'Comment 8: Peter Moeiliker\', \'Comment 9: Steffen Driessens\', \'Comment 10: Koen Huiberts,NAS: Bert Geijtenbeek and Christine de JongVAS: Bert GeijtenbeekLAS: Bert GeijtenbeekOPPAS/PAS: Rick Reimerink\', "Comment 11: Thelma Meijer \'", "Comment 12: \'Poniżej wymienieni userzy powinni mieć prawo do udostępnionych inboxów wszystkuich userów", \'Comment 13: którzy mogą tworzyć Rundy\', \'Comment 14: Feed sale\', \'Comment 15: Financial statement (do sprawdzenia na węzłach dla tych dokumentów\', \'Comment 16: kto może je tworzyć). Bez tego wymienieni userzy nie są w stanie przesłać dokumentów do Archiwum. Przy zamykaniu S2P zamykane są automatycznie powiązane dokument FS\', \'Comment 17: Runda\', \'Comment 18: Feed sale.MAS: Nancy van Dam\', \'Comment 19: Peter Moeiliker\', \'Comment 20: Steffen Driessens\', \'Comment 21: Koen Huiberts,NAS: Bert Geijtenbeek and Christine de JongVAS: Bert GeijtenbeekLAS: Bert GeijtenbeekOPPAS/PAS: Rick Reimerink\', "Comment 22: Thelma Meijer\'", "Comment 23: \'Dwie role obejmują całość-Normal contract administrator-Senior contract administrator\'", "Comment 24: \'Dodano na każdym przepływie do archiwum w dokumentach saldo2pay przed wykonaniem flow na innych dokumentach insert na tabele userrelation a po wykonaniu flow jest wykonywany delete na danym użytkowniku.\'", \'Comment 25: "Finally to avoid giving rights of many shared inboxes to users we found another solution.When user will perform flow to \\\'Archive\\\' for Saldo 2 Pay document we add for a while permission for shared inboxes users who can perform flows for archiving FS\', \'Comment 26: Round\', \'Comment 27: Feed sale. This rights will be added only when user perform this flow to Archive for S2P document and will be removed at the end of performing flow.In this case flows should be always performed properly and FS\', \'Comment 28: Round\', \'Comment 29: Feed sale should be perform to Archive even if these documents are in other users inboxes.You can verify it on test environment.For this case it should be tested on some user who has rights for performing S2P flow and for example linked FS or Round is in inbox of other users. User who want to archived S2P shouldn\\\'t has rights to inbox of user who has in inbox FS or Round document."\', "Comment 30: \'It will be tested internally by Kotrak on IBIP_DH_TEST and after then will be moved to Prod environment.When it will be good and will be no issues in logs in Intense on prod after deployment on Prod we will close the task.\'", "Comment 31: \'[~damian.swistek@kotrak.com]do sprawdzenia na IBIP_DH_TEST\'", "Comment 32: \'[~tomasz.zygon@kotrak.com]", \'Comment 33: sprawdziłem na IBIP_DH_TEST i wygląda ok\', "Comment 34: do przerzucenia na Prod.Po przerzuceniu daj znać w komentarzu i zobaczymy przez jakiś czas czy w logach nie ma już błędów związanych z brakiem uprawnień do przesyłanych tasków.\'", "Comment 35: \'Przerzucono na proda jednak tylko w mas be i mas nl wykonują się przepływy dla powiązanych dokumentów w reszcie dodałem to w oczekiwaniu na przeniesienie całościowe rozwiązania z testa\'", "Comment 36: \'Moved to prod\']"]\nRelated Issues:\n[\'DGS-8705\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8896\n\n### Instruction:\nGood morning,\r\n\r\nplease we have got a problem with communication between PCS and DHP on plant Helmond.\r\n\r\nFor example SO-14644/3/23\r\n\r\nIt\'s not processed on DHP.\r\n\r\nCould you have a look at it.\r\n\r\nKind regards,\r\n\r\nGerard Geerts\r\n\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: \\\'01.04 dla modułu pcs były timeouty i 03.04 też.W logach host dla pcs jest info o braku z order w module pcs.2023-04-03 12:11:55 (40516f78-4f32-487a-9659-9efe1467fe6e/Plant.PCS.BusinessLogic/DHVD01AP203/13480/15) [Error] Microsoft.EntityFrameworkCore.Update - An exception occurred in the database while saving changes for context type \\\\\\\'"Plant.PCS.BusinessLogic.Infrastructure.EF.PcsDbContext"\\\\\\\'."""Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): The MERGE statement conflicted with the FOREIGN KEY constraint \\\\\\\\"FK_VehicleTicketElements_Orders_OrderId\\\\\\\\". The conflict occurred in database \\\\\\\\"DHPlantPCSBusinessLogicMain\\\\\\\\"\', \'Comment 3: table \\\\\\\\"dbo.Orders\\\\\\\\"\', "Comment 4: column \\\\\'Id\\\\\'\'", "Comment 5: \'!image-2023-04-04-12-09-21-312.png!\'", "Comment 6: \'W module dhc były problemy z deadlockami2023-04-03 07:18:45 (/Plant.DHC.Integration/DHVD01AP203/12848/3) [Error] Kotrak.Common.Infrastructure.Integration.Jobs.InboundProcessJob - Error during inbound processingMicrosoft.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 158) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception", \'Comment 7: Boolean breakConnection\', \'Comment 8: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 9: Boolean callerHasConnectionLock\', \'Comment 10: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 11: SqlCommand cmdHandler\', \'Comment 12: SqlDataReader dataStream\', \'Comment 13: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 14: TdsParserStateObject stateObj\', \'Comment 15: Boolean& dataReady) at Microsoft.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows) at Microsoft.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout\', "Comment 16: Boolean& more) at Microsoft.Data.SqlClient.SqlDataReader.Read() at Microsoft.EntityFrameworkCore.Query.Internal.SplitQueryingEnumerable`1.Enumerator.MoveNext() at System.Collections.Generic.LargeArrayBuilder`1.AddRange(IEnumerable`1 items) at System.Collections.Generic.EnumerableHelpers.ToArray[T](IEnumerable`1 source) at Kotrak.Extensions.Communication.InternalStorage.Fetch.InternalStorageInboundFetchService`1.FetchEntities(Int32 packageSize) at Kotrak.Extensions.Communication.Database.Fetch.DbFetchService`2.Fetch() at Kotrak.Common.Infrastructure.Integration.Filters.InternalStorageFetchFilter`1.Execute(InternalStorageContext`1 input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Extensions.Pipeline.ContinuousPipeline`1.Execute(TContext input) at Kotrak.Common.Infrastructure.Integration.Jobs.InboundProcessJob.<>c__DisplayClass3_0.<Execute>b__3()ClientConnectionId:733ba743-ff1e-4b55-901c-825655c09f3f\'", "Comment 17: \'023-03-31 15:37:50 (c780c84f-ec61-4491-8a54-cf8403b82ab5/Plant.DHC.Integration/DHVD01AP203/12848/56) [Error] Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler - VehicleTicketDispatchPipelineExecutor execution errorKotrak.Extensions.Communication.Exceptions.ConnectionBrokenException: A connection attempt failed because the connected party did not properly respond after a period of time", \'Comment 18: or established connection failed because connected host has failed to respond. (dhvd01ap174:8087) ---> System.ServiceModel.CommunicationException: A connection attempt failed because the connected party did not properly respond after a period of time\', \'Comment 19: or established connection failed because connected host has failed to respond. *{color:#de350b}(dhvd01ap174:8087){color}* ---> System.Net.Http.HttpRequestException: A connection attempt failed because the connected party did not properly respond after a period of time\', \'Comment 20: or established connection failed because connected host has failed to respond. (dhvd01ap174:8087) ---> System.Net.Sockets.SocketException (10060): A connection attempt failed because the connected party did not properly respond after a period of time\', \'Comment 21: or established connection failed because connected host has failed to respond. at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error\', "Comment 22: CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)\'", "Comment 23: \'server dhc !image-2023-04-04-12-17-39-887.png!\'", "Comment 24: \'!image-2023-04-04-12-19-22-720.png!\'", "Comment 25: \'Hello", \'Comment 26: after yesterday situation on Helmond\', \'Comment 27: raised in task https://helpdesk.kotrak.com/browse/DGS-8904we found someunautorized actions on the database that practically blocked pcs module\', \'Comment 28: causing a lot of timeouts and deadlocks\', \'Comment 29: it seems\', "Comment 30: that this could be ( with high possibility) reason for also situation raised in dgs-8090.log analysis earlier also showed only timeout You can see that values in milliseconds is close to over 56 hour!image-2023-04-05-08-17-24-523.png!Is that information sufficient for you and may we close the task?\'", "Comment 31: \'May we close the task?\'", "Comment 32: \'May we close the task?\']"]\nRelated Issues:\n[\'DGS-8890\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8895\n\n### Instruction:\nHi\r\n\r\nPlease could you find the entry that is breaking the cross posting rule for me.\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: \\\'This entry (screenshot-1) is breaking the cross posting rule "Deny company cross posting" !screenshot-1! !screenshot-2! \\\'\', "Comment 4: \'HiYes", "Comment 5: but how is that a cross entry?\'", "Comment 6: \'The finance team found the issue. Wrong accountTicket may be closed. Thank you for the help!!image-3!\'", "Comment 7: \'Thank you for information :)\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8894\n\n### Instruction:\nIn the category "Eggs" we have multiple sections (in the round and one the FS). We miss one important one called "Tweede soort". Could you add this?\r\n\r\nIn this section we should present the bookings with item code "TWEE". \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: \'Section Tweede soort are added in FS document and Round document for sector PAS.\'", "Comment 4: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8893\n\n### Instruction:\nHi, from Iwona.\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 definition of the category for this pay component has been changed.The changes will be visible when the system recreates the analytic description for this payroll.Please verify.\'", "Comment 4: \'Task to close. Thanks.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8892\n\n### Instruction:\nMorning\r\nPlease could you assist with the following issue:\r\n\r\nDHM BANK 31/03/2023 23/MFNBC/73/39 is not closing\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-2!\'", "Comment 4: \'Please place this ticket on hold as per screenshot. User is going to make a work around.\'", "Comment 5: \'Apologies", "Comment 6: the work around failed. We need to continue with this ticket.\'", "Comment 7: \'HiCould we unpost this bank report and try to do this again?\'", "Comment 8: \'Asking finance to do it now.\'", "Comment 9: \'Still getting an error!image-3!\'", "Comment 10: \'I changed the posting scheme 020IN.Please", "Comment 11: check\'", "Comment 12: \'DHM is closed now. What was wrong with 020IN?\'", \'Comment 13: "I changed the formula in 4th position to:\\\'020-\\\'&KontoWymiaru(\\\'category\\\')it was before:\\\'020-\\\'&KontoWymiaru(\\\'kategoria\\\')"\', "Comment 14: \'Oh", "Comment 15: ok. So a small translation issue. Thanks You can close the ticket.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8891\n\n### Instruction:\nHi,\r\n\r\nPlease help to check this issue. User can not confirm PLR . \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: \\\'{code:java}2023-04-03 14:04:31 (96389402-eba3-4a08-9cb4-623c54f63b91/Plant.Prod.BusinessLogic/VNTN-TS01/5984/161) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 4: "host": { "Value": "10.84.50.199:83"\', \'Comment 5: "HasValue": true\', \'Comment 6: "Host": "10.84.50.199"\', \'Comment 7: "Port": 83 }\', \'Comment 8: "path": "/api/productionLot/update"\', \'Comment 9: "queryString": []\', \'Comment 10: "requestBody": "{\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":1,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"da8b4cf8-b081-43f0-bfa6-9a651ea7f8ee\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1100}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":2,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"c3c1752d-4b4a-48b4-9cb6-8387d15fd902\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1980}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":3,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"9812dcb6-1f33-4b8d-b785-2cc7f7641e86\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":19}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":4,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"7d031926-b504-410c-a97c-d10aac1b79b2\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":5,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"8bf5c2dc-2412-4c4f-af09-9d5e6b34d26f\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":900}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":6,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"4d72d853-c912-4754-8e83-b36fa1d8808b\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":400}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":7,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"bb42bf8f-e30c-4fbf-aec2-925ad555eb80\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":600}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":8,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"616e78e9-b902-4b56-894c-7fb0592ece24\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1000}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":9,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"aa6a64e6-5a7e-4d95-9e4e-620dc018273d\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":980}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":10,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"e471178c-187e-4803-a94c-df14d19f56c0\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":4.4}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":11,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"dd7d749a-1f3d-4c0a-b38e-53a9cc21b24f\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1000}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":12,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"556a242e-5178-44fa-b5d0-6b6a3b4acc3c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":13,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"3f4ae0f3-1122-4e8d-9f30-1a53b8e4dd93\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":14,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"2ceee972-9822-49f3-b10f-e15fabacb0f7\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":10}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":15,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"e2eb8227-7f3f-47fd-83e9-9091b3a13b31\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":200}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":16,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"47266428-01df-42af-818c-6a326688e5cb\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":6005.2}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":17,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"8ad69d7a-59be-44ab-90b6-dfabcabb0711\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2500}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":18,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"94c5d2b6-32b4-497a-ad16-984cfc18201b\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":40}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":19,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"422f7a50-31ca-4ade-89c7-a8c0f9eb2e1c\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":762}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":20,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"956a30a8-4b2c-4027-9795-39a512a9fc2f\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":10}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":21,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"e12d47bc-5607-41d1-81a1-1d1d05dcf7d0\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":34.2}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":22,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"197f87e5-888a-4616-8d9c-00c9e9668848\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":50}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":23,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"a5435af9-9474-459f-8877-d8cbf8b55dde\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":600}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":24,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"80dacfdf-b704-47e2-a76d-0ebea48cccb3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":10}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":25,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"7e761c59-9674-4716-9cd3-0f0c75a8c35a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":620}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":26,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"06d3c0ce-46a0-417e-88fa-7b74a1915a5b\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":69.2}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":27,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"91269b01-7f68-4512-8d53-9a71454454da\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":280}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":28,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"9c3faeff-33a8-455b-b481-3cc2f11b8a91\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":800}},{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":29,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"6320244d-2132-472e-a519-ae1a57138a66\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":20}}],\\\\\\\\"executions\\\\\\\\":[{\\\\\\\\"elements\\\\\\\\":[],\\\\\\\\"readyProductId\\\\\\\\":\\\\\\\\"da56e314-e09c-49a8-b53a-30ccaadd5add\\\\\\\\",\\\\\\\\"packingRecipeId\\\\\\\\":null,\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":20000},\\\\\\\\"requestedQuantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":20000},\\\\\\\\"expiryDate\\\\\\\\":\\\\\\\\"2023-07-02T06:15:24.936Z\\\\\\\\"}],\\\\\\\\"reservations\\\\\\\\":[{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"7555b496-59c0-4305-89c1-3e87e3d9d332\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"b53c2fd7-3e48-4c8e-82ca-71576d084a92\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":19}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"cccb707c-6597-48a4-9e79-5ddf98ac80e4\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"7cac85ea-d639-40d2-b9dc-d8708843e6f3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":10}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"2f8a1e44-af6a-4dca-b1b4-d3b95af4d6c2\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"3902d8f0-7f0e-4aa3-b1c0-22902a21e51b\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":800}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"255961c9-c8f7-48ed-9faf-5ecb6c479a0f\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"121fb072-f4f3-49ce-a43f-454389090f90\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1000}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"2ecc2f02-40b7-45c0-b74c-bdd459b15773\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"66dbc653-3b16-49e2-96a2-818051459add\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":980}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"8338f0c3-071a-40aa-88ae-4b8b000a5436\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"4525fe5f-802a-4761-adf2-86b793bb9f99\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":6005.2}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"ff78bd19-dccf-41bf-837c-1b8ce6e63e36\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"05f47cf4-2a76-4959-9c13-8b7eff10d1a6\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"dbc3e51d-2582-42f3-b489-c64d1048253f\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"3bec8ccd-b20b-4f4f-8903-bcc135005cb0\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":69.2}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"ef542311-1979-482c-b72f-f48e1804ec58\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"0d1db1d4-d583-4e5f-87c1-7c6d1d8d465f\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1000}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"a6eb4819-1d61-4e27-a61b-5bc264ccb4d8\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"96ae00bc-c3c5-464d-a8d2-cfcb5995daab\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1980}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"562ddace-e33f-4e38-9f12-153885f197f2\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"59cf136f-cd20-435f-ab7f-bf82ada010e1\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":200}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"842a0974-2899-49ae-bea3-54a3a397e2e4\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"fefae1df-b013-4dbf-874b-103f2661129b\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":600}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"f50d0faf-c691-4e9b-bc56-d00e6d995de1\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"0f31c250-2103-4c89-b3af-692c55f38b1f\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":40}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"ab669de7-86d5-43e0-a97d-df736159bbff\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"c4827d6c-3d59-4221-a41e-d25cdeb591d7\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":1100}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"63e2941f-ace6-45a6-bd28-c0d4931bdf78\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"6f48c4af-282b-4b00-8bdd-a7b8d6f80a02\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":280}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"4cb2b135-5539-4546-bf6d-f4380adef53d\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"f41f3f99-9951-4542-ad41-77b55c643ff2\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":900}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"51d8f758-98e7-48d3-af53-f5cb4fb26da8\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"3701ff2d-7eb1-45fc-99ad-35d2d7f01545\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":762}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"4ed334e5-5e68-4467-b51d-b84d45ff5a85\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"bf33b145-3f89-4e99-9f2f-b3c32cecef3a\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":20}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"7b31a984-5f4f-461c-9c39-3a29af08faa6\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"9886856f-aad6-40ef-9e3f-07c70b5c799d\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":400}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"e0b295ef-1c8f-4aa8-a847-0796184dc331\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"366a9db9-08fb-45f8-939a-a23a7def5dbb\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"1466480b-2a33-435c-9777-14570905551b\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"4ff95f11-622b-47a9-b401-d60783e5a3f9\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":600}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"7b10e6e1-4497-4565-a9d4-2254d9a6b61e\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"c8357944-3e3b-4449-a1d4-ac939d3cd7e3\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":4.4}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"9a92cbe8-a60a-4ca4-a0ba-ec1dbb037f92\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"3965e4c2-24e9-46a4-a966-798d2f96a5a8\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":2500}},{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"d8881bfc-5f33-4097-8d62-05d72011c791\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"8ce4e88e-28d8-4a8f-ac81-4d5dbae50c3b\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":10}}],\\\\\\\\"productionLotId\\\\\\\\":\\\\\\\\"a12a4bde-930d-4539-803a-980a11af4113\\\\\\\\",\\\\\\\\"recipeId\\\\\\\\":\\\\\\\\"e0c008ad-28bd-4005-b671-509d0a471d26\\\\\\\\",\\\\\\\\"labelId\\\\\\\\":null,\\\\\\\\"productionOrderId\\\\\\\\":\\\\\\\\"a02545ce-a9b2-420f-b033-4272e08c6583\\\\\\\\",\\\\\\\\"shiftNumberId\\\\\\\\":\\\\\\\\"0f4af611-a440-462b-b369-769f1457b817\\\\\\\\",\\\\\\\\"statusChange\\\\\\\\":2}"}.System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273 --- End of inner exception stack trace --- at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 11: AggregateId businessUnitId\', \'Comment 12: Quantity productionQuantity\', \'Comment 13: IEnumerable`1 settlementData\', \'Comment 14: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 135 at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 15: ConfirmProductionLotActionData data\', \'Comment 16: IEnumerable`1 reservations\', \'Comment 17: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 82 at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 325 at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateProductionLotCommandHandler.Handle(UpdateProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateProductionLotCommandHandler.cs:line 39 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Plant.Prod.BusinessLogic.Infrastructure.Api.Controllers.ProductionLotController.UpdateProductionLot(UpdateProductionLotViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\Controllers\\\\\\\\ProductionLotController.cs:line 110 at lambda_method(Closure \', \'Comment 18: Object \', \'Comment 19: Object[] ) at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target\', \'Comment 20: Object[] parameters) at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 21: ObjectMethodExecutor executor\', \'Comment 22: Object controller\', \'Comment 23: Object[] arguments) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next\', \'Comment 24: Scope& scope\', \'Comment 25: Object& state\', \'Comment 26: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next\', \'Comment 27: Scope& scope\', \'Comment 28: Object& state\', "Comment 29: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync() at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIIndexMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)---> (Inner Exception #0) Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273<---{code}\'", "Comment 30: \'{code:java}2023-04-03 14:04:31 (96389402-eba3-4a08-9cb4-623c54f63b91/Plant.Prod.BusinessLogic/VNTN-TS01/5984/161) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateProductionLotCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateProductionLotCommand) methodSystem.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273 --- End of inner exception stack trace --- at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId", \'Comment 31: AggregateId businessUnitId\', \'Comment 32: Quantity productionQuantity\', \'Comment 33: IEnumerable`1 settlementData\', \'Comment 34: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 135 at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 35: ConfirmProductionLotActionData data\', \'Comment 36: IEnumerable`1 reservations\', \'Comment 37: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 82 at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 325 at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateProductionLotCommandHandler.Handle(UpdateProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateProductionLotCommandHandler.cs:line 39 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)---> (Inner Exception #0) Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273<---2023-04-03 14:04:31 (null/Plant.Prod.BusinessLogic/VNTN-TS01/5984/161) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/productionLot/update" responded 500 in 4844.1201 ms{code}\\\'\', "Comment 38: \'{code:java}2023-04-03 14:04:31 (96389402-eba3-4a08-9cb4-623c54f63b91/Plant.Stock.BusinessLogic/VNTN-TS01/9384/250) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateReservationsAndConfirmProductionLotCommand](Plant.Stock.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateReservationsAndConfirmProductionLotCommand) methodSystem.Data.SqlClient.SqlException (0x80131904): Could not allocate a new page for database \\\\\'DHPlantStockBusinessLogicEvents\\\\\' because of insufficient disk space in filegroup \\\\\'PRIMARY\\\\\'. Create the necessary space by dropping objects in the filegroup", \'Comment 39: adding additional files to the filegroup\', \'Comment 40: or setting autogrowth on for existing files in the filegroup. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 41: Boolean breakConnection\', \'Comment 42: Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 43: Boolean callerHasConnectionLock\', \'Comment 44: Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 45: SqlCommand cmdHandler\', \'Comment 46: SqlDataReader dataStream\', \'Comment 47: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 48: TdsParserStateObject stateObj\', \'Comment 49: Boolean& dataReady) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior\', \'Comment 50: SqlCommand cmdHandler\', \'Comment 51: SqlDataReader dataStream\', \'Comment 52: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 53: TdsParserStateObject stateObj) at System.Data.SqlClient.SqlBulkCopy.RunParser(BulkCopySimpleResultSet bulkCopyHandler) at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinuedOnSuccess(BulkCopySimpleResultSet internalResults\', \'Comment 54: String updateBulkCommandText\', \'Comment 55: CancellationToken cts\', \'Comment 56: TaskCompletionSource`1 source) at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinued(BulkCopySimpleResultSet internalResults\', \'Comment 57: String updateBulkCommandText\', \'Comment 58: CancellationToken cts\', \'Comment 59: TaskCompletionSource`1 source) at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsync(BulkCopySimpleResultSet internalResults\', \'Comment 60: String updateBulkCommandText\', \'Comment 61: CancellationToken cts\', \'Comment 62: TaskCompletionSource`1 source) at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestContinuedAsync(BulkCopySimpleResultSet internalResults\', \'Comment 63: CancellationToken cts\', \'Comment 64: TaskCompletionSource`1 source) at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts\', \'Comment 65: TaskCompletionSource`1 source) at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken) at System.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount\', \'Comment 66: CancellationToken ctoken) at System.Data.SqlClient.SqlBulkCopy.WriteToServer(DbDataReader reader) at EFCore.BulkExtensions.SqlBulkOperation.Insert[T](DbContext context\', \'Comment 67: IList`1 entities\', \'Comment 68: TableInfo tableInfo\', \'Comment 69: Action`1 progress) at EFCore.BulkExtensions.DbContextBulkExtensions.BulkInsert[T](DbContext context\', \'Comment 70: IList`1 entities\', \'Comment 71: BulkConfig bulkConfig\', \'Comment 72: Action`1 progress) at Kotrak.Common.Infrastructure.EF.EventRepository.GenericEventRepositoryEf`2.Persist(TAggregateRoot aggregateRoot) at Plant.Stock.BusinessLogic.Infrastructure.Persistance.StockUnits.Repositories.StockUnitRepository.PersistRangeAfterProductionConfirmation(IEnumerable`1 modifiedStockUnits\', \'Comment 73: IEnumerable`1 newStockUnits) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.Persistance\\\\\\\\StockUnits\\\\\\\\Repositories\\\\\\\\StockUnitRepository.cs:line 316 at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.PersistConfirmProductionLotResult(ProductionLot productionLot\', \'Comment 74: ICollection`1 semiProductProductionLots\', \'Comment 75: ConfirmProductionLotResult result) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 756 at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateReservationsAndConfirmProductionLot(UpdateReservationsAndConfirmProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 450 at Plant.Stock.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateReservationsAndConfirmProductionLotCommandHandler.Handle(UpdateReservationsAndConfirmProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateReservationsAndConfirmProductionLotCommandHandler.cs:line 33 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)ClientConnectionId:2bcc4c1b-68ec-4dbf-9bb7-c952c05bf408Error Number:1101,State:12,Class:172023-04-03 14:04:31 (null/Plant.Stock.BusinessLogic/VNTN-TS01/9384/250) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/productionLot/updateReservationsAndConfirm" responded 500 in 4693.3152 ms{code}\\\'\', \'Comment 76: "I have recreated your error. In logs we have information:{code:java}2023-04-03 14:04:31 (96389402-eba3-4a08-9cb4-623c54f63b91/Plant.Stock.BusinessLogic/VNTN-TS01/9384/250) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateReservationsAndConfirmProductionLotCommand](Plant.Stock.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateReservationsAndConfirmProductionLotCommand) methodSystem.Data.SqlClient.SqlException (0x80131904): Could not allocate a new page for database \\\'DHPlantStockBusinessLogicEvents\\\' because of insufficient disk space in filegroup \\\'PRIMARY\\\'. Create the necessary space by dropping objects in the filegroup\', \'Comment 77: adding additional files to the filegroup\', \'Comment 78: or setting autogrowth on for existing files in the filegroup.{code}Please\', \'Comment 79: see db server below: !image-2023-04-03-09-17-49-468.png!Regards"\', "Comment 80: \'i have been clean our backup for space but may we have clean data in event DBs?!image-1!\'", "Comment 81: \'Hi,You can clean this data but please", "Comment 82: clean the oldest ones. But please try to shrink them first.Regards\'", "Comment 83: \'i try to shrink database but it still have it\'", "Comment 84: \'Can we lower the priority?If you cannot shrink", "Comment 85: please delete the oldest data.Regards\'", "Comment 86: \'yes", "Comment 87: please set it to P3\'", "Comment 88: \'Did you delete oldest data?Regards\'", \'Comment 89: "hi\', \'Comment 90: i\\\'m not delete data. just shrink database but after sometime still back to old"\', "Comment 91: \'[~maciej.dobrzanski@kotrak.com] Maciek", \'Comment 92: Marcin Block mówił\', \'Comment 93: żew czwratek w tej fabryce jest upgrade plus zmiana serwerów\', "Comment 94: drążyć temat? Albo po prostu wrzucam FYI :)\'", "Comment 95: \'ja bym poczekał na przypadek po upgrade. Nie mam wersji 8.3 (a taka chyba mają) więc cięzko będzie nam cokolwiek zreprodukować.\'", "Comment 96: \'Hi,I have some information that on Thursday afternoon CET time you have upgrade inHai Phong 2 factory. After short discussion with dev", "Comment 97: it is advise to wait to upgrade and check if the issue wll occur for 8.5 version.Regards\'", "Comment 98: \'so mean that this ticket will be hold to after upgrade?\'", "Comment 99: \'Yes", "Comment 100: if you agree\'", "Comment 101: \'agree", "Comment 102: please keep in HOLD\'", "Comment 103: \'Sure\'", "Comment 104: \'Hi,Does the issue occur in version 8.5?Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8890\n\n### Instruction:\nGood morning,\r\n\r\nplease we have got a problem with communication between PCS and DHP on plant Helmond.\r\n\r\nFor example SO-14644/3/23\r\n\r\nIt\'s not processed on DHP.\r\n\r\nCould you have a look at it.\r\n\r\nKind regards,\r\n\r\nGerard Geerts\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: \'!image-2023-04-03-09-00-49-160.png!\'", "Comment 3: \'!image-2023-04-03-09-04-14-125.png!\'", "Comment 4: \'Culd please verify again ", \'Comment 5: I do not see any errors\', "Comment 6: and we had informaction that order was exported 31.03 at 16:28.\'", "Comment 7: \'Hello Agnieszka,Problem still on. Could it be a problem with the Webservices?Gerard\'", "Comment 8: \'Hello Agnieska,There is no data communicating tot DHP.Maybe first to have a look at the communication between DHC and DHP. Because the salesorder SO000092646 with trip: 9_L000275519 is not communicating to DHP.Regards,Gerard \'", "Comment 9: \'Helloso-14644 is in dhp: its forieng number isSO000091362 ? did you still have problem with that order?!image-2023-04-03-11-18-04-800.png|width=1062,height=171!\'", "Comment 10: \'Hallo Agnieska", \'Comment 11: with so-14644 the problem is that there no VT created\', \'Comment 12: while the dispatch message is accepted in the webservice: Please check thatBesides\', \'Comment 13: Gerard also reports that orders and trips are not coming into DHP\', \'Comment 14: with the example SO000092646 and trip 9_L000275519: please check that also,this as a higher priority\', "Comment 15: because orders and trips do not arrive in the pcs and are blocking the production\'", "Comment 16: \'For your other example it was send to DHP. Please check others.\'", "Comment 17: \'SO000092646 is indeed now in DHP but not send to pcs. please check\'", "Comment 18: \'!afbeelding!\'", "Comment 19: \'!afbeelding-1!\'", \'Comment 20: "Ok so by now there are 2 cases : # that from 1 so no VT was created.- Are you able to create a VT from DHP as workaround? # that other SO\\\'s need resynchro to PCS"\', "Comment 21: \'For 2 Please trigger resync", \'Comment 22: I expect you can do thisFor 1: No we cannot\', "Comment 23: because we need a correct packing slip therefore info from the dispatch message is required\'", "Comment 24: \'ad 2. it looks like integration looks fine", "Comment 25: please verify If there is still something missing.\'", "Comment 26: \'ad 1. VT was created please verify!image-2023-04-03-12-15-50-874.png!\'", "Comment 27: \'Oke", "Comment 28: can we determine root cause because complete communication seems to be down during this mornng: Was the problem mainly in DHC>DHP communication?\'", "Comment 29: \'RCA is underDGS-8896 may we close this one?\'", "Comment 30: \'yes can be closed\']"]\nRelated Issues:\n[\'DGS-8896\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8889\n\n### Instruction:\nMorning\r\nMy support team is not in today, and we are deploying a DHApps update. I\'m not able to investigate this issue. Please can you take a look for me. This is word for word from the internal ticket supplied by the user.\r\n\r\n"Please see below, the accounting note does not reflect on the payment plan for the customer 010-15-10-06070"\r\n\r\nThe finance team needs this resolved today to close the period.\r\n\r\nRegards\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hi This accounting note is not visible in Payment plan because there is no customer (Payer) on this Note.There is only amount.As I see this type of Accounting note - ACC19 is configured in a way it doesn\\\'t allow to add the Payer on it.I can change configuration for this document or you could use simplified note to enter this payment.Best Regards"\', "Comment 4: \'Will ask the finance team what they would like\'", "Comment 5: \'HiThis ticket can be closed. Thank you for the help. Finance team used a simplified note.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8888\n\n### Instruction:\nHi\r\n\r\nPlease help to check 2PLRs 4322010423007 and 4322010423006 .\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!.Please help to close this ticket . t has been resolved . Thanks u.\'", "Comment 4: \'Issue has been closed as requested.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8887\n\n### Instruction:\nCould you please cancel PRO-1032/3/23?\r\n\r\nItem SUR6912-MD-B500\r\nOrder SO-638076283/23/PED\r\n\r\nWe need to produce urgent and system not allow to create new PRO.\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: \'PrO has been canceled.\'", "Comment 3: \'Hi Piotr,ok", "Comment 4: you can close this task. Thank you.\'", "Comment 5: \'Thank you for confirmation.\']"]\nRelated Issues:\n[\'DGS-8869\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8886\n\n### Instruction:\nerror id 6428793 - Intake for this barcode is already closed\r\n\r\nProduction stopped please take care about the problem fast.\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: \'It seems that the message was incorrect. We have cancelled this message. Please", "Comment 3: verify.Regards\'", "Comment 4: \'Production started - task to close.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8885\n\n### Instruction:\nWe got informed the Belgian Intense users experience a very slow performance of Intense in the past weeks. Today is really slow. \r\n\r\nThis is opposed by the Dutch users, who don\'t have such complaints.\r\n\r\nBoth working via Citrix.\r\n\r\nCan you please investigate why the performance is so poor for the Belgian users?\n\n### Response:\n["Comment 1: [\'Hi Martijn,Do you have any details about examples of slow operations in Intense? Regards,Tomasz\'", "Comment 2: \'{color:black}Hi Koen,{color} {color:black}{color} {color:black}I created a ticket at Kotrak for the slowness you experience. As the Dutch users don’t experience this slowness", \'Comment 3: I don’t think Citrix is the issue.{color} {color:black}{color} {color:black}Can you give Tomasz some examples as he requests below? 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:* Tomasz Kozioł (Jira) <jira@kotrak.com> *Sent:* vrijdag 31 maart 2023 13:54 *To:* Meier\', "Comment 4: Martijn <mmeier@deheus.com> *Subject:* DGS-8885 Intense slow for Belgian users \'", "Comment 5: \'To verify possibilty of adding RAM memory on SQL Server\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8884\n\n### Instruction:\nNote: ticket is applicable for all DHP\'s\r\n\r\nVehicle tickets for dispatches are missing in DHC/Milas. We checked and found that Vehicle tickets with status Dispatch completed do not seem to be sent anymore from DHP to DHC. \r\nFor Dutch Feed plants this was the case and it is still needed. \r\n\r\nCan you check if configuration is missing and correct this? \r\nWe need VT\'s with status Dispatch completed in DHC/Milas.\r\n\r\nExamples e.g,1314/3/23 and 1315/3/23 for Sneek: dispatch completed in DHP, no data in DHC\r\n\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: \'Hi Bob,Are you able to confirm if missing VTs are only from March?Regards\'", \'Comment 4: "Indeed only VT\\\'s from March seem to be missing in DHC.I checked for Sneek in February and March and I found only issues in March (from March 9 - date of the deploy of new DHP version for Sneek). First plant for which new DHP was deployed was Ravenstein (28-feb). Also for that plan I only found missing VT in DHC in March"\', "Comment 5: \'Cześć.[~maciej.dobrzanski@kotrak.com],W tym statusie jest ogólnie 145 VT", \'Comment 6: ale zakładam\', \'Comment 7: że nie tylko o status Dispatch Completed chodzi.Rozumiem\', \'Comment 8: że to ten sam kejs\', \'Comment 9: co tu https://helpdesk.kotrak.com/browse/DGS-8694 # Czy jest szansa na skrypt + czy chodzi tylko o VT dispatch completed? # Czy ktoś mógłby spawdzić konfigurację\', \'Comment 10: ewentualnie podac screena\', \'Comment 11: co sprawdzić\', "Comment 12: to sprawdzę?Thanks from the mountain :)[~marek.mamcarz@kotrak.com]ktoś juz pisał z NL z tym do Ciebie?\'", "Comment 13: \'Thank you Bob for your information.Regards\'", "Comment 14: \'[~aleksandra.przybylek@kotrak.com] a nie przesyłaliście ostatnio we współpracy z [~maciej.buchacz@kotrak.com]?\'", "Comment 15: \'[~maciej.dobrzanski@kotrak.com] ale to były PLR", "Comment 16: a tu chcą VT :)to ten scrypt wymagałby małej modyfkacji czy dużego przemeblowania? :)\'", "Comment 17: \'[~aleksandra.przybylek@kotrak.com] tak trzeba troche pozmieniać.[~marcin.kleszcz@kotrak.com] może [~maciej.buchacz@kotrak.com] mógłby pomóc? Już podobne skrypty przerabiał.Jeśli nie trzeba resendować ręcznie\'", "Comment 18: \'[~aleksandra.przybylek@kotrak.com] Czy mogłabyś podać listę dokumentów VT", "Comment 19: którą należy przesłać? (albo skąd wzięłaś ilość 145 vt :) ).\'", "Comment 20: \'[~maciej.buchacz@kotrak.com] Z bazy danych wyszukałam po statusie Dispatch complete we wszystkich plantach. Ale nauczona doświadczeniem z akcji z PLR", \'Comment 21: to nie jestem pewna\', "Comment 22: czy to jedyny właściwy status... [~marek.mamcarz@kotrak.com]??\'", "Comment 23: \'no i zawęziłam do marca ofkors :P\'", "Comment 24: \'Do you have an update on this ticket?\'", "Comment 25: \'[^dgs8884.xlsx]\'", \'Comment 26: \\\'Dear Bob,I have doubts if status "dispatch completed" and month = march is accurate filter for Vehicle Tickets.I have filtered documents list two days ago and today and they differ. In attach\', \'Comment 27: please see al VT documents with status dispatch completed. In some plants we do not have VTs with this status on the VT list. If someone could verified this list and confirm or provide us with the list of VT documents that should be sent\', "Comment 28: I would be very thankful.Regards[^dgs8884.xlsx]\'", "Comment 29: \'[^DGS-8884.xlsx]\'", "Comment 30: \'lista z id i cała resztą informacji[^DGS-8884.xlsx]\'", "Comment 31: \'Hi Aleksandra", \'Comment 32: The list will indeed change every day: - as soon as VT is closed (by operator or automatic closing process by the system)\', \'Comment 33: the VT gets status Closed and is automatically synced -> no action needed- as long as the bug is not fixed\', \'Comment 34: new VT in April will be on the list that still need to be send (e.g. VT-160/4/23\', \'Comment 35: 167/4/23\', \'Comment 36: 173/4/23 for Nijkerk). So\', "Comment 37: I think correct filter is: all VT with status Dispatch Completed from March 1 until todaySecond part of this ticket is solving the bug/change config so that VT with status Dispatch completed are automatically synced to DHC.\'", "Comment 38: \'I have resent those four for Utrecht. Please", "Comment 39: verify and let me know if this is fine for you so that I could send from other plants!image-2023-04-06-11-29-01-363.png!\'", "Comment 40: \'This list for Utrecht is correct\'", "Comment 41: \' !before after! konfigi dla fabryk przed i po upgrade\'", \'Comment 42: \\\'I have resent all VTs with status "Dispatch complete" from March.Now I will check April and will provide you with the list of resent documents\\\'\', "Comment 43: \'Below is the list of VTs from April sent to MilasVeghel:VT-227/4/23Maasbracht:VT-361/4/23VT-179/4/23VT-243/4/23VT-84/4/23VT-170/4/23VT-384/4/23VT-211/4/23VT-344/4/23VT-152/4/23VT-318/4/23VT-150/4/23Ravenstein:VT-118/4/23VT-92/4/23VT-56/4/23VT-55/4/23VT-24/4/23VT-123/4/23VT-36/4/23VT-33/4/23VT-119/4/23VT-89/4/23VT-117/4/23VT-70/4/23VT-98/4/23Helmond:VT-81/4/23VT-242/4/23Nijkekr:VT-111/4/23VT-64/4/23VT-1/4/23VT-122/4/23VT-13/4/23VT-160/4/23VT-173/4/23VT-167/4/23VT-123/4/23VT-41/4/23VT-98/4/23Sneek:VT-9/4/23VT-117/4/23VT-133/4/23VT-257/4/23VT-160/4/23VT-189/4/23VT-24/4/23VT-192/4/23VT-287/4/23\'", "Comment 44: \'To skoro konfiguracja dla tego procesu się nie zmieniła", \'Comment 45: to już nie wiem co... Na razie przesłałam marzec i na bieżąco\', \'Comment 46: ale jest coś\', "Comment 47: że nie działa...\'", "Comment 48: \'[^Resend draft vehicle ticket to DHC 8.5.sql]\'", "Comment 49: \'[^Resend draft vehicle ticket to DHC 8.5.sql]\'", \'Comment 50: "Hi [~BKennedy@deheus.com],We found some cases that may not be sent to DHC. We have fix for that. Do you agree if we deploy the fix? You don\\\'t need to stop production.Best regards"\', \'Comment 51: "Hi Aleksandra,Thank you for sending the VT\\\'s. Will the fix solve the issue that next VT\\\'s with status Dispatch completed will be sent to DHC automatically?Can it be that some of the VT\\\'s listed below are not yet in DHC? (e.g. 118/4/2023/004 - for Ravenstein). Or will this be solved with the fix as well?On Tuesday\', \'Comment 52: I will check with Thomas for the deploy of the fix."\', \'Comment 53: "Hi Bob,Yes\', \'Comment 54: there may be taht some VTs from the list still did not arrive.The fix will solve the issue ofnext VT\\\'s with status Dispatch complete to be sent.Waitng for your feedback then after Thomas\\\'s acceptance.Regards"\', "Comment 55: \'Update w Utrecht done.\'", "Comment 56: \'pięknie <3\'", "Comment 57: \'Hi [~BKennedy@deheus.com],The fix has been implemented to Utrecht. Please", "Comment 58: test if it is woring fine for you now and provide us with the feedback so that we could implement in other factories.Regards\'", \'Comment 59: "Hi @Aleksandra\', \'Comment 60: after the update I did not find any VT with status Dispatch Completed\', "Comment 61: so I could not check if the fix is working correctly. I did check if all other VT\'s (with status Closed) are in DHC", \'Comment 62: and that is still ok. I think you can continue with update for other plants "\', "Comment 63: \'Thank you. I am transferring this task to Dev Team.Regards\'", "Comment 64: \'Hi,The fix has been implemented in all plants.Please", "Comment 65: let us know if we can close this taskRegards\'", \'Comment 66: "New VT\\\'s with status Dispatch Completed are indeed in DHC now. This ticket can be closed."\', "Comment 67: \'Thank you.Regards\']"]\nRelated Issues:\n[\'DGS-8694\', \'DAP-13538\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8883\n\n### Instruction:\nWe still see a lot of old S2P’s in Intense that are still on the status Entry. We are for 99% sure that all these S2P’s are already settled in Milas. However the users forgot to put the status on archive.\r\n\r\nAfter some modifications in the system now it won’t be possible to settle a S2P in Milas if it is not archived so this problem will not exist in the future.\r\n\r\nAre you able to change the status of these S2P to archive without sending them again to Milas? Just to make sure: we don’t want these to be send to Milas again.\n\n### Response:\n["Comment 1: [\'[^S2P Entry.xlsx]\'", "Comment 2: \'There are list of documents from Excel which have been sent to Archive in Intense without sending to Milas.There are some documents with no mapping in mapping table of sent to Milas S2Ps.Please verify that all these documents are in Milas.|*ID*|*Number*|*Mapping*||55460|SP-M/0005|No mapping||63362|SP-M/0020|||68583|SP-M/0029|||71689|SP-M/0043|No mapping||72091|SP-M/0051|No mapping||72619|SP-M/0068|No mapping||72644|SP-M/0070|No mapping||73007|SP-M/0080|||73563|SP-M/0090|||73816|SP-M/0094|||74088|SP-M/0100|No mapping||74462|SP-M/0105|||75705|SP-M/0124|||75921|SP-M/0127|No mapping||76001|SP-M/0128|||77272|SP-M/0152|||77426|SP-M/0156|||77447|SP-M/0157|No mapping||77457|SP-M/0158|No mapping||77987|SP-M/0172|No mapping||78695|SP-M/0185|No mapping||78790|SP-M/0187|||78813|SP-M/0189|||78871|SP-M/0190|||80239|SP-M/0202|||80275|SP-M/0203|No mapping||80646|SP-M/0214|||81796|SP-M/0222|||82056|SP-M/0231|||82721|SP-M/0234|||83141|SP-M/0244|||83220|SP-M/0246|No mapping||83730|SP-M/0262|||83732|SP-M/0263|||83909|SP-M/0269|||84748|SP-M/0296|No mapping||85623|SP-M/0307|No mapping||86661|SP-M/0327|No mapping||86712|SP-M/0328|||86762|SP-M/0330|||86968|SP-M/0331|No mapping||87636|SP-M/0337|||88179|SP-M/0347|||88189|SP-M/0349|||88630|SP-M/0357|||88935|SP-M/0362|||89349|SP-M/0370|||89519|SP-M/0378|||89612|SP-M/0379|No mapping||90107|SP-M/0388|||90344|SP-M/0389|||90379|SP-M/0392|||90449|SP-M/0396|||90540|SP-M/0398|||90650|SP-M/0400|||90817|SP-M/0403|No mapping||90869|SP-M/0404|No mapping||90872|SP-M/0405|No mapping||90965|SP-M/0406|No mapping||91016|SP-M/0407|No mapping||91020|SP-M/0408|No mapping||91046|SP-M/0410|No mapping||91051|SP-M/0411|No mapping||91052|SP-M/0412|||91149|SP-M/0416|||91395|SP-M/0425|||91497|SP-M/0427|||91628|SP-M/0432|||91636|SP-M/0433|||91670|SP-M/0434|No mapping||91751|SP-M/0435|||92041|SP-M/0437|||92112|SP-M/0438|||92135|SP-M/0439|||92197|SP-M/0440|||92199|SP-M/0441|||92277|SP-M/0442|||92293|SP-M/0443|||92321|SP-M/0444|||92375|SP-M/0445|||92382|SP-M/0446|||92402|SP-M/0447|||92406|SP-M/0448|||92416|SP-M/0449|||92449|SP-M/0450|||92482|SP-M/0451|||92485|SP-M/0452|||92491|SP-M/0453|||92669|SP-M/0454|||92673|SP-M/0455|||92681|SP-M/0456|||92688|SP-M/0457|||92701|SP-M/0458|||92705|SP-M/0459|||92710|SP-M/0460|||92843|SP-M/0461|||92909|SP-M/0464|No mapping||93167|SP-M/0466|No mapping||93206|SP-M/0467|||93357|SP-M/0469|||93442|SP-M/0473|No mapping||93686|SP-M/0479|||93859|SP-M/0483|||93877|SP-M/0484|||93886|SP-M/0485|||94327|SP-M/0487|No mapping||95350|SP-M/0504|No mapping||96840|SP-M/0518|No mapping||97187|SP-M/0523||\'", "Comment 3: \'We are verifying this. The task can be closed. \']"]\nRelated Issues:\n[\'DGS-8877\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8882\n\n### Instruction:\nFor sales order SO000091430 with special for Helmond, the one time recipe 303436 version 136 subversion 1 is generated and in DHP, but it is not sent to PCS.\r\n\r\nYesterday an additional technology for this code was archived (see: https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8852)\r\n\r\nIn DHC the one time recipe is generated on the correct (303436) code. However, plant did not receive the one time recipe in PCS.\r\n\r\nPlease check if archiving of additional technology was done correctly (in DHC and DHP).\r\nPlant needs the one time recipe for production.\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: "select * from items where code=\\\'303436\\\'select * from Recipes where id=\\\'5718735F-47FA-4453-81F3-C690A2A60F0C\\\'select * from ExportRecipes where entityid=15317!image-2023-03-31-09-47-42-220.png!"\', "Comment 4: \'!image-2023-03-31-09-49-30-691.png!\'", \'Comment 5: "obu nie ma tabeli export recipes dla tego itema jest tylkoselect * from ExportRecipes where entityid in(select entityid from Recipes where id=\\\'5718735F-47FA-4453-81F3-C690A2A60F0C\\\' or (ItemId=\\\'08B78E4E-277B-4282-8154-FB338C827580\\\'))!image-2023-03-31-09-59-10-730.png!"\', \'Comment 6: "-- DECLARE @RecipeId UNIQUEIDENTIFIER = \\\'FEF262AC-67B2-4F07-A79E-0A299ED68592\\\'; -- id receptury version 0-- DECLARE @RecipeId UNIQUEIDENTIFIER = \\\'FEF262AC-67B2-4F07-A79E-0A299ED68592\\\'; -- id receptury version 0-- DECLARE @RecipeEntityId INT= (SELECT r.EntityId FROM dbo.Recipes r WHERE r.Id = @RecipeId);-- UPDATE dbo.Recipes-- SET IsProductDefinition = 0-- WHERE Id = @RecipeId;-- DELETE FROM dbo.ExportRecipes-- WHERE EntityId = @RecipeEntityId;-- INSERT INTO dbo.ExportRecipes (PackageId\', \'Comment 7: SendDate\', \'Comment 8: ConfirmDate\', \'Comment 9: ExternalSystemId\', \'Comment 10: EntityId)-- SELECT NEWID()\', \'Comment 11: GETDATE()\', \'Comment 12: GETDATE()\', \'Comment 13: er.Id\', \'Comment 14: r.EntityId-- FROM dbo.Recipes r-- JOIN dbo.ExternalSystems er ON 1 = 1--WHERE r.Id = @RecipeId;update [DHPlantProdBusinessLogicMain].dbo.Recipes set IsProductDefinition = 0where Id = \\\'FEF262AC-67B2-4F07-A79E-0A299ED68592\\\'"\', "Comment 15: \'Please check should be ok now.\'", "Comment 16: \'Thank you", "Comment 17: I asked plant to verify if they received the one time recipe correctly.\'", "Comment 18: \'This ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8881\n\n### Instruction:\nPo wczorajszej aktualizacji ERP integratora nasili się problem z synchronizacją tras z DHC do DHP, np:\r\n5041/23/L\r\n\r\n5059/23/G\r\n\r\n2040/23/P\r\n\r\n2224/23/I\r\n\r\n2225/23I\r\n\r\n1039/23/J\r\n\r\nPo wygenerowaniu VT poprzez podpięcie ZS w DHC generują sie elementy bez powiązania z ZS, np. \r\n\r\nVT 4237/P, 4279/P, 4280/P, 6124/M, 6289/G\n\n### Response:\n["Comment 1: [\'ERP Integratora", \'Comment 2: są dwa rodzaje błędów\', \'Comment 3: dla change message:[^error_1.txt]-- dla calego ordera i dla elementówSystem.NullReferenceException: Object reference not set to an instance of an object. at Evolution.DHCService.Dhc30.Handlers.ShippingNoticeElementChangedMessageHandler.FillEntity(ShippingNoticeElementChangedMessage message\', \'Comment 4: ShippingNoticeElementEntity entity) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\ShippingNoticeElementChangedMessageHandler.cs:line 43 at Evolution.DHCService.Dhc30.Handlers.BaseMessageHandler`2.Handle(TMessage message) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:line 56 at lambda_method(Closure \', \'Comment 5: Object \', \'Comment 6: Object ) at NServiceBus.Unicast.MessageHandlerRegistry.Invoke(Object handler\', \'Comment 7: Object message\', \'Comment 8: Dictionary`2 dictionary) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 126 at NServiceBus.Unicast.MessageHandlerRegistry.InvokeHandle(Object handler\', \'Comment 9: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 84 at NServiceBus.LoadHandlersBehavior.<Invoke>b__1(Object handlerInstance\', \'Comment 10: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\LoadHandlersBehavior.cs:line 40 at NServiceBus.InvokeHandlersBehavior.Invoke(IncomingContext context\', \'Comment 11: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\InvokeHandlersBehavior.cs:line 24 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.SetCurrentMessageBeingHandledBehavior.Invoke(IncomingContext context\', "Comment 12: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\SetCurrentMessageBeingHandledBehavior.cs:line 17\'", "Comment 13: \'Moja mała uwaga odnosnie twierdzenia że nic nie zmieniali na zamówieniach", "Comment 14: z tego co widze to na tabeli w ERP xl nie loguje sie info o zmianach na zamówieniach ( kwestiach ich konfigu ale np dla zamówienia 130 na tabeli cdn.zamvat ( nie ma tej zakładki widocznej w erp xl) ale widzimy dla zamówieniaZW-130/03/23/D na tabeli cdn.zamvat mamy zav_gidlp tylko 5 - wiec oznacza to ze pozycje jakies były usuwane bo nie ma pozycji miedzy 1-5 wiec zdecydowanie cos z tymi zamówienia się działo,!image-2023-03-31-07-42-46-952.png|width=950,height=347!\'", "Comment 15: \'Trasę \\\\\'T-5041/23/L\\\\\' nawet nie wiem jak miałbym sprawdzać", \'Comment 16: powstały trzy awizacje o takim numerze jedna wyjazdowa z jednej fabryki i dwie identyczne wjazdowe na drugą fabrykę co już samo w sobie jest absurdalne. Do trasy "T-5059/23/G" sprawdziłem jak wyglądała historia zmian zamówienia (można sprawdzić wpisy w tabeli communicationLogs) otóż na przestrzeni 3 dni dostaliśmy 69 aktualizacji tego zamówienia. Generalnie analiza w tym przypadku mija się już z celem bo i tak nigdy nie dojdziemy czemu brakowało elementów zamówienia spiętych z tymi trasami.Generalnie mają ERP integratora ustawionego tak zeby synchronizował niepotwierdzone zamówienia w których grzebią jak tylko mogą i takie są tego efekty.\\\'\', "Comment 17: \'Hello", "Comment 18: is there any progress with this RCA? Similar cases pop up everyday and engage local IT resources. \'", "Comment 19: \'Good morning,Short analysis results below in two languages to avoid misunderstandingTrasa \\\\\'T-5041/23/L\\\\\' - powstały trzy awizacje o takim numerze - jedna wyjazdowa z jednej fabryki i dwie identyczne wjazdowe na drugą fabrykę", \'Comment 20: co nie jest dobre dla systemu\', \'Comment 21: a przede wszystkim procesu biznesowego i powoduje zamieszanie. Do trasy "T-5059/23/G" sprawdziliśmy jak wyglądała historia zmian zamówienia. W ciągu 3 dni dostaliśmy 69 aktualizacji tego zamówienia. Generalnie analiza w tym przypadku mija się już z celem\', \'Comment 22: bo nie jesteśmy w stanie ustalić\', \'Comment 23: dlaczego brakowało elementów zamówienia spiętych z tymi trasami.ERP integratora macie ustawionego tak żeby synchronizował niepotwierdzone zamówienia\', \'Comment 24: w których są dokonywane pewne zmiany\', "Comment 25: co również powoduje wskazane problemy.Route \\\\\'T-5041/23/L\\\\\' - three Shipping Notices with this number were created", \'Comment 26: one dispatch SN from one factory and two identical intake Shipping Notices to the other factory\', \'Comment 27: which is not good for the system\', \'Comment 28: and above all for the business process\', \'Comment 29: and it also causes confusion. For the "T-5059/23/G" route\', \'Comment 30: we checked the history of the order changes. We have got 69 updates related to this order within 3 days. In general\', \'Comment 31: the analysis in this case misses the point because we are unable to determine why the order elements associated with these routes were missing.Your ERP integrator is set up to synchronize unconfirmed orders where some changes are made\', "Comment 32: which also causes the indicated problems.Best regards\'", "Comment 33: \'Informacyjnie", \'Comment 34: config ErpIntegrator_MSG oraz ErpIntegrator_DOC nie zmienił się podczas zeszłotygodniowej aktualizacji. Jedynie na końcu configu została zmieniona wersja biblioteki log4net.dll z 2.0.8.0 na 2.0.12.0\', \'Comment 35: co wyszło na środowisku testowym podczas pierwszych testów bo nie otrzymaliśmy informacji o tej zmianie.Zaznaczę też że podczas poprzednich aktualizacji wykonywanych przez DH PL IT\', \'Comment 36: nie były zmieniane configi od PlatformApplication\', \'Comment 37: chyba że w kooperacji z Wami\', "Comment 38: przy zgłoszonych DGSach że nagle coś przestało działać po podniesieniu integratora.\'", "Comment 39: \'[~przemyslaw.przybyszewski@kotrak.com] Przemek", "Comment 40: a ERP Int wcześniej też był tak skonfigurowany? Pamiętasz może?\'", "Comment 41: \'W tej chwili pojawił się przykład trasy 5096/23/G która zaczyna się w Mieścisku jedzie przez Janowiec ", "Comment 42: Buk i kończy się w Grodzisku. Powodem braku trasy w DHP Mieścisko były zamówienia 168 i 169 /03/23/G które z jakiegoś powodu nie przeszły do DHP. Wymuszony update na zamówieniu ( poprzez zmianę daty realizacji w CDN ) przepchnął zamówienia do DHP co po ponownym potwierdzeniu trasy skutkowało jej pojawieniem się w systemie Jak widać takie trasy nie powodują wielkiego zamieszania lecz z jakiś powodów Integrator nie przesyła wszystkich danych miedzy systemami . !image!\'", "Comment 43: \'T-1099/23/J jest w DHC nie ma w DHCService\'", "Comment 44: \'Hello", "Comment 45: due to the number of operations on the orders( as it was mentioned earlier) can I get the current case/example (without synchronization attempts)?Thanks.\'", "Comment 46: \'T-5494/L brak trasy w DHPZamówienie dla tej trasy jest w DHP !image-1!\'", "Comment 47: \'Any news ?? \'", "Comment 48: \'Kolejny przykład T-5467 / L \'", "Comment 49: \'It can be process now this second one. Thank you.\'", "Comment 50: \'{code:java} SELECT o.* FROM [dbo].[Orders] o left join [dbo].[OrderElements] e on o.id=e.orderid where DocumentNumerator_Year=2023 and\\\\tDocumentNumerator_Month in(2,3,4) and e.id is null and status <>6 {code}\'", "Comment 51: \'Two examples from today:T-5467/23/L ZS-2431/03/23/LT-5494/23/L ZS-2445/03/23/LOrders elements were missing in DHCService.After sending again orders and trips are in DHC Service and DHP.All orders have a common creation date on 27.3.2023.Was there an upgrade day?All problematic orders have the same date- apart from one ZW(ZW-38/03/23/M)", "Comment 52: there are currently 79 of them.ZS-959/03/23/PZS-953/03/23/DZS-952/03/23/DZS-851/03/23/IZS-1028/03/23/DZS-1001/03/23/DZW-38/03/23/MZS-1445/03/23/ŁZS-2455/03/23/LZS-2433/03/23/LZS-958/03/23/PZS-963/03/23/PZS-859/03/23/IZS-1656/03/23/SZS-858/03/23/IZS-870/03/23/IZS-871/03/23/IZZ-976/03/23ZS-1026/03/23/DZS-874/03/23/IZS-951/03/23/DZS-1627/03/23/SZS-862/03/23/IZS-1043/03/23/DZS-865/03/23/IZS-2439/03/23/LZS-1003/03/23/DZW-154/03/23/MZS-1449/03/23/ŁZS-978/03/23/DZS-967/03/23/DZS-842/03/23/IZS-2450/03/23/LZS-1450/03/23/ŁZS-958/03/23/DZS-943/03/23/DZS-861/03/23/IZS-959/03/23/DZS-2454/03/23/LZS-1443/03/23/ŁZS-841/03/23/IZS-864/03/23/IZS-2451/03/23/LZS-849/03/23/IZS-954/03/23/DZS-857/03/23/IZS-1655/03/23/SZS-872/03/23/IZS-964/03/23/DZS-2453/03/23/LZS-844/03/23/IZS-845/03/23/IZS-840/03/23/IZS-873/03/23/IZS-1444/03/23/ŁZS-850/03/23/IZS-866/03/23/IZS-1007/03/23/DZS-876/03/23/IZS-1439/03/23/ŁZS-863/03/23/IZS-980/03/23/DZS-70/03/23/YZS-843/03/23/IZS-999/03/23/DZS-2452/03/23/LZS-1441/03/23/ŁZS-960/03/23/DZS-1438/03/23/ŁZZ-997/03/23ZS-2438/03/23/LZS-875/03/23/IZS-846/03/23/IZS-965/03/23/PZS-2446/03/23/LZS-2434/03/23/LZS-1442/03/23/ŁZS-960/03/23/PZS-1448/03/23/Ł,we can correct (send again) them and check if there are new cases. \'", "Comment 53: \'I have found that re-syncing the order helps in my cases. The idea of \\\\u200b\\\\u200bre-syncing orders may solve the problem.\'", "Comment 54: \'Orders have been sent again", "Comment 55: please check after current date and time.\'", "Comment 56: \'Problem nadal występuje . Zamówienia potwierdzane wczoraj - przeszły do DHPTrasa potwierdzana godzinę temu - nie przeszła do DHP Przykład trasa 2248/P \'", \'Comment 57: "I\\\'m waiting for another one\', \'Comment 58: this one has already gone to DHP."\', "Comment 59: \'Brak trasy w DHP T-5527/23/G\'", "Comment 60: \'When it comes to this route T-5527/23/G", \'Comment 61: the problem was when changing the Vehicles/Platenumbers to PZ1H806\', \'Comment 62: PZ2K201from PZ 1H806\', "Comment 63: PZ 2K201. The user made several changes to these Vehicles looking at the logs. I sent the registrations again in the order and route.\'", "Comment 64: \'Kolejna trasa : T-2455 /23/ I\'", "Comment 65: \'For DHcService messages need to be process !screenshot-2! \'", "Comment 66: \'Why does the queue raised up to almost 700 orders changed?\'", "Comment 67: \'Were any changes made to the documents", "Comment 68: as indicated by the message?\'", \'Comment 69: "I think some orders have been modified\', \'Comment 70: but many of them were synchronizing all the time so queue shouldn\\\'t raise that much. I think queue should be clear or have only few documents to sync - not 700 orders"\', "Comment 71: \'Kolejna trasa : 131/23/MS \'", "Comment 72: \'Messages need time to process", \'Comment 73: some are more time consuming\', "Comment 74: e.g. technologies.Each order operation is logged as a change - so there can be several of them for each order.\'", "Comment 75: \'Kolejne trasy: 3527/23/S", \'Comment 76: 465/23/P\', "Comment 77: 5624/23/L\'", "Comment 78: \'ZS-742/4/23/L (nie było w dhp", \'Comment 79: przeszło po odświeżeniu\', \'Comment 80: ale jako niepotwierdzone\', \'Comment 81: pomimo\', "Comment 82: ,że w cdn było potwierdzone)\'", "Comment 83: \'Kolejne nie przeszły: 3517/23/S", "Comment 84: 5621/23/G\'", "Comment 85: \'brak ZS-438/04/23/S oraz trasy 3531/23/S\'", "Comment 86: \'brak ZS-53/4/23/G (towar niezlinkowany) oraz T-5757/23/G\'", "Comment 87: \'brak T-5641/23/G\'", "Comment 88: \'brak T-5653/23/G\'", "Comment 89: \'brak T-3491/04/23/S", "Comment 90: T-3504/04/23/S\'", "Comment 91: \'brak T-2310/04/23/P\'", "Comment 92: \'T-2310/04/23/P finalnie w ogóle nie przeszła nawet do serwisu\'", "Comment 93: \'Hello", \'Comment 94: referring to yesterday\', \'Comment 95: after 1:30 pm there was still a large number of messages for the dhcservice queue to be processed (several thousand). Were there any changes made to the DHCService message queue\', \'Comment 96: as it was already 0 on the processing list before 2pm?Also function activity monitor was permanently paused for login dhbp. Can we get access to activity monitor for DHC databases? Or for my domain account\', "Comment 97: thank you.\'", "Comment 98: \'Whether additional processes were running that could have caused mass changes to the data?I see that after 9 am messages began to be processed in very large quantities and are still growing for DHCService !screenshot-3! \'", \'Comment 99: "Other users from Kotrak could run activity monitor\', "Comment 100: you were not listed there because it\'s the first time you need it. Access granted", \'Comment 101: verify.User dhbp is an application user\', "Comment 102: so it should not have additional privileges like for example activity monitor - its not good practice. On other servers you probably also won\'t run any activity monitor using application user like masterplant", \'Comment 103: dhbp and similar."\', "Comment 104: \'I have asked and nobody told me about any other source of problems that could cause this amount of changed data. Long time ago we had same problem", "Comment 105: just look back in requests. Analysis was done and you fixed something.\'", "Comment 106: \'Brak tras w DHP (wszystkie zamówienia są w DHP)T-2808/23/DT-4450/23/MT-4120/23/ŁT-5647/23/L\'", "Comment 107: \'Przykład do analizy ( załadunek na 16:00) T-5767/23/G\'", "Comment 108: \'Brak: ZS-983/04/23/L i T-5708/23/L\'", "Comment 109: \'Kolejka komunikatów niby pusta a synchro leży....\'", "Comment 110: \'We vt-kach brakuje spięcia z zamówieniami !image-2!\'", "Comment 111: \'!image-3!\'", "Comment 112: \'Brak : T-3519/23/S\'", "Comment 113: \'Brak w DHPT-2512/23/IPotwierdzona o 9:12!image-4!\'", "Comment 114: \'Brak: T-4435/23/M\'", "Comment 115: \'We are collecting data for analysis.It is not currently necessary to send a new examples.In order for the trips to be process you need to resent the order earlier.I will try to provide more information tomorrow - the results of the analysis.\'", "Comment 116: \'hello", \'Comment 117: as for the amount of changes\', "Comment 118: this was already a issue:DGS-6103operator TSSROBO These operators currently perform the most changes. !screenshot-4! !screenshot-5! \'", "Comment 119: \'ilość zamówień jakie były modyfikowane.{code:java}SELECT count(*) as ilosc_zmian,ZaN_OpeNumerMod,o.Ope_Nazwisko --[ZaN_OpeNumerMod] --,cdn.tstodate([ZaN_LastMod],2) FROM [CDNXL_DEHEUS].[CDN].[ZamNag] z join cdn.OpeKarty o on o.Ope_GIDNumer=z.ZaN_OpeNumerMod where [ZaN_LastMod]>=1050120000 group by ZaN_OpeNumerMod ,o.Ope_Nazwisko order by count(*) desc{code} !screenshot-6! \'", "Comment 120: \'In DGS-6103 issue has been resolved. It seems to be something similar", "Comment 121: but we had no details what caused this problem with sync before.Could you explain what fixed problem reported in DGS-6103? I think you have some notes because it has been resolved temporarily last time.\'", "Comment 122: \'There are two issues - one problem with orders in dhcservice - this is being analyzedand the second message queue on DHCServiceAs for the number of messages for order changes and operators described above. If there are so many changes for orders the messages must be processed.Currently", "Comment 123: there are no such problems as in the task mentioned earlier - I only indicated why there are so many messages on the DHCService queue.\'", "Comment 124: \'PiotrCh będzie rozmawiał z Łukaszem Grodzkim\'", "Comment 125: \'[Przesyłanie Order/zamówień i tras /ShippingNotice - brak elementów zamówień w DHCService|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHC.one#Przesy%C5%82anie%20Order/zam%C3%B3wie%C5%84%20i%20tras%20/ShippingNotice%20-%20brak%20element%C3%B3w&section-id=\\\\\\\\{7D50734F-49D8-4579-83B9-E51158168A8F}&page-id=\\\\\\\\{F79626AC-B068-431D-BAC5-C6AAFA54C428}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHC.one%7C7D50734F-49D8-4579-83B9-E51158168A8F%2FPrzesy%C5%82anie%20Order%5C%2Fzam%C3%B3wie%C5%84%20i%20tras%20%5C%2FShippingNotice%20-%20brak%20element%C3%B3w%7CF79626AC-B068-431D-BAC5-C6AAFA54C428%2F%29]) naprawa przypadków.\'", "Comment 126: \'Naprawiłam 9 przypadków\'", "Comment 127: \'Kolejki puste", "Comment 128: zamówień 24 - przesłano!image-2023-04-14-19-05-22-715.png!!image-2023-04-14-19-04-58-252.png!\'", "Comment 129: \'!image-2023-04-15-11-14-54-457.png|width=512,height=436!dzisiaj pusto\'", \'Comment 130: "HI\', \'Comment 131: please check after today\\\'s ugrade how the synchronization working and send a feedback.Thank you."\', "Comment 132: \'Please let me know if there are currently any problems described in the issue?Thank you.\'", "Comment 133: \'We need a little more time until orders made after last update will be processed - there are still some cases with orders made before the update.\'", "Comment 134: \'We will wait for final confirmation.\']"]\nRelated Issues:\n[\'DGS-8879\', \'DGS-8965\', \'DGS-8914\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8880\n\n### Instruction:\nWe tried to weight one truck in unit 2 but for VT from unit 1 but the weight is not available.\r\nCould you check why is not working?\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Dispatch weight : 88860kg!MicrosoftTeams-image (61)!\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'Hi,I can see bothe scales are running and VT-1906 is already closed. Do you have any similar example?Regards\'", "Comment 5: \'!image-2023-04-03-11-06-39-563.png!\'", "Comment 6: \'!image-2023-04-03-11-07-01-561.png!\'", \'Comment 7: "Hi [~Aleksandra.Przybylek@kotrak.com]Unfortunately we don\\\'t have any other example.You can close this task.Thank you very much!"\', "Comment 8: \'Thank you.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8879\n\n### Instruction:\nPo wczorajszej aktualizacji ERP integratora nasili się problem z synchronizacją tras z DHC do DHP, np:\r\n5041/23/L\r\n\r\n5059/23/G\r\n\r\n2040/23/P\r\n\r\n2224/23/I\r\n\r\n2225/23I\r\n\r\n1039/23/J\r\n\r\nPo wygenerowaniu VT poprzez podpięcie ZS w DHC generują sie elementy bez powiązania z ZS, np. \r\n\r\nVT 4237/P, 4279/P, 4280/P, 6124/M, 6289/G\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: \'Ewelina jeszcze dzwoniła", \'Comment 3: że ze swojej strony przeanalizowali wszystko. Na zamówieniach nie było nic ruszane\', \'Comment 4: żadne dane.Odnośnie tej części:{color:#0747a6}_Po wygenerowaniu VT poprzez podpięcie ZS w DHC generują sie elementy bez powiązania z ZS\', \'Comment 5: np._{color}{color:#0747a6}_VT 4237/P\', \'Comment 6: 4279/P\', \'Comment 7: 4280/P\', \'Comment 8: 6124/M\', \'Comment 9: 6289/G_{color}Ewelina mówi\', \'Comment 10: że w ten sposób sobie radzili\', "Comment 11: ale ilość dokumentów wzrasta bardzo szybko\'", "Comment 12: \'Z ERP Integratora", \'Comment 13: są dwa rodzaje błędów\', \'Comment 14: dla change message:{code:java}System.InvalidOperationException: Cannot find Order element for specific OrderElementId = 029de345-296b-449b-a0a9-b84a34015907 at Evolution.DHCService.Dhc30.Handlers.ShippingNoticeChangedMessageHandler.MapOrders(ShippingNoticeElementEntity shippingNoticeElementEntity\', \'Comment 15: List`1 orderMessageElemenets) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\ShippingNoticeChangedMessageHandler.cs:line 95 at Evolution.DHCService.Dhc30.Handlers.ShippingNoticeChangedMessageHandler.FillEntity(ShippingNoticeChangedMessage message\', \'Comment 16: ShippingNoticeEntity entity) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\ShippingNoticeChangedMessageHandler.cs:line 74 at Evolution.DHCService.Dhc30.Handlers.BaseMessageHandler`2.Handle(TMessage message) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:line 56 at lambda_method(Closure \', \'Comment 17: Object \', \'Comment 18: Object ) at NServiceBus.Unicast.MessageHandlerRegistry.Invoke(Object handler\', \'Comment 19: Object message\', \'Comment 20: Dictionary`2 dictionary) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 126 at NServiceBus.Unicast.MessageHandlerRegistry.InvokeHandle(Object handler\', \'Comment 21: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 84 at NServiceBus.LoadHandlersBehavior.<Invoke>b__1(Object handlerInstance\', \'Comment 22: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\LoadHandlersBehavior.cs:line 40 at NServiceBus.InvokeHandlersBehavior.Invoke(IncomingContext context\', \'Comment 23: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\InvokeHandlersBehavior.cs:line 24 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.SetCurrentMessageBeingHandledBehavior.Invoke(IncomingContext context\', \'Comment 24: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\SetCurrentMessageBeingHandledBehavior.cs:line 17 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.LoadHandlersBehavior.Invoke(IncomingContext context\', \'Comment 25: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\LoadHandlersBehavior.cs:line 45 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.Transports.SQLServer.ReadIncomingCallbackAddressBehavior.Invoke(IncomingContext context\', \'Comment 26: Action next) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\888dd942b44bad5a\\\\\\\\src\\\\\\\\NServiceBus.SqlServer\\\\\\\\ReadIncomingCallbackAddressBehavior.cs:line 17 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.ApplyIncomingMessageMutatorsBehavior.Invoke(IncomingContext context\', \'Comment 27: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\MessageMutator\\\\\\\\ApplyIncomingMessageMutatorsBehavior.cs:line 23 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.ExecuteLogicalMessagesBehavior.Invoke(IncomingContext context\', \'Comment 28: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Messages\\\\\\\\ExecuteLogicalMessagesBehavior.cs:line 24 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.CallbackInvocationBehavior.Invoke(IncomingContext context\', \'Comment 29: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\CallbackInvocationBehavior.cs:line 22 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.DeserializeLogicalMessagesBehavior.Invoke(IncomingContext context\', \'Comment 30: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Messages\\\\\\\\DeserializeLogicalMessagesBehavior.cs:line 47 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.ApplyIncomingTransportMessageMutatorsBehavior.Invoke(IncomingContext context\', \'Comment 31: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\MessageMutator\\\\\\\\ApplyIncomingTransportMessageMutatorsBehavior.cs:line 20 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.SubscriptionReceiverBehavior.Invoke(IncomingContext context\', \'Comment 32: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Subscriptions\\\\\\\\MessageDrivenSubscriptions\\\\\\\\SubscriptionReceiverBehavior.cs:line 31 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.UnitOfWorkBehavior.Invoke(IncomingContext context\', \'Comment 33: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\UnitOfWork\\\\\\\\UnitOfWorkBehavior.cs:line 42 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.ChildContainerBehavior.Invoke(IncomingContext context\', \'Comment 34: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\ChildContainerBehavior.cs:line 17 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.ProcessingStatisticsBehavior.Invoke(IncomingContext context\', \'Comment 35: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Monitoring\\\\\\\\ProcessingStatisticsBehavior.cs:line 23 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.Invoke() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 52 at NServiceBus.Pipeline.PipelineExecutor.Execute[T](BehaviorChain`1 pipelineAction\', \'Comment 36: T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 129 at NServiceBus.Pipeline.PipelineExecutor.InvokePipeline[TContext](IEnumerable`1 behaviors\', \'Comment 37: TContext context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 85 at NServiceBus.Pipeline.PipelineExecutor.InvokeReceivePhysicalMessagePipeline() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 102 at NServiceBus.Unicast.UnicastBus.TransportMessageReceived(Object sender\', "Comment 38: TransportMessageReceivedEventArgs e) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\UnicastBus.cs:line 826 at NServiceBus.Unicast.Transport.TransportReceiver.OnTransportMessageReceived(TransportMessage msg) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 411 at NServiceBus.Unicast.Transport.TransportReceiver.ProcessMessage(TransportMessage message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 344 at NServiceBus.Unicast.Transport.TransportReceiver.TryProcess(TransportMessage message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 228 at NServiceBus.Transports.SQLServer.AmbientTransactionReceiveStrategy.TryReceiveFrom(TableBasedQueue queue) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\888dd942b44bad5a\\\\\\\\src\\\\\\\\NServiceBus.SqlServer\\\\\\\\AmbientTransactionReceiveStrategy.cs:line 57{code}\'", "Comment 39: \'I dla change element message :{code:java}System.NullReferenceException: Object reference not set to an instance of an object. at Evolution.DHCService.Dhc30.Handlers.ShippingNoticeElementChangedMessageHandler.FillEntity(ShippingNoticeElementChangedMessage message", \'Comment 40: ShippingNoticeElementEntity entity) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\ShippingNoticeElementChangedMessageHandler.cs:line 43 at Evolution.DHCService.Dhc30.Handlers.BaseMessageHandler`2.Handle(TMessage message) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:line 56 at lambda_method(Closure \', \'Comment 41: Object \', \'Comment 42: Object ) at NServiceBus.Unicast.MessageHandlerRegistry.Invoke(Object handler\', \'Comment 43: Object message\', \'Comment 44: Dictionary`2 dictionary) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 126 at NServiceBus.Unicast.MessageHandlerRegistry.InvokeHandle(Object handler\', \'Comment 45: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 84 at NServiceBus.LoadHandlersBehavior.<Invoke>b__1(Object handlerInstance\', \'Comment 46: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\LoadHandlersBehavior.cs:line 40 at NServiceBus.InvokeHandlersBehavior.Invoke(IncomingContext context\', \'Comment 47: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\InvokeHandlersBehavior.cs:line 24 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.SetCurrentMessageBeingHandledBehavior.Invoke(IncomingContext context\', \'Comment 48: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\SetCurrentMessageBeingHandledBehavior.cs:line 17 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.LoadHandlersBehavior.Invoke(IncomingContext context\', \'Comment 49: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\LoadHandlersBehavior.cs:line 45 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.Transports.SQLServer.ReadIncomingCallbackAddressBehavior.Invoke(IncomingContext context\', \'Comment 50: Action next) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\888dd942b44bad5a\\\\\\\\src\\\\\\\\NServiceBus.SqlServer\\\\\\\\ReadIncomingCallbackAddressBehavior.cs:line 17 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.ApplyIncomingMessageMutatorsBehavior.Invoke(IncomingContext context\', \'Comment 51: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\MessageMutator\\\\\\\\ApplyIncomingMessageMutatorsBehavior.cs:line 23 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.ExecuteLogicalMessagesBehavior.Invoke(IncomingContext context\', \'Comment 52: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Messages\\\\\\\\ExecuteLogicalMessagesBehavior.cs:line 24 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.CallbackInvocationBehavior.Invoke(IncomingContext context\', \'Comment 53: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\CallbackInvocationBehavior.cs:line 22 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.DeserializeLogicalMessagesBehavior.Invoke(IncomingContext context\', \'Comment 54: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Messages\\\\\\\\DeserializeLogicalMessagesBehavior.cs:line 47 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.ApplyIncomingTransportMessageMutatorsBehavior.Invoke(IncomingContext context\', \'Comment 55: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\MessageMutator\\\\\\\\ApplyIncomingTransportMessageMutatorsBehavior.cs:line 20 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.SubscriptionReceiverBehavior.Invoke(IncomingContext context\', \'Comment 56: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Subscriptions\\\\\\\\MessageDrivenSubscriptions\\\\\\\\SubscriptionReceiverBehavior.cs:line 31 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.UnitOfWorkBehavior.Invoke(IncomingContext context\', \'Comment 57: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\UnitOfWork\\\\\\\\UnitOfWorkBehavior.cs:line 42 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.ChildContainerBehavior.Invoke(IncomingContext context\', \'Comment 58: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\ChildContainerBehavior.cs:line 17 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94 at NServiceBus.ProcessingStatisticsBehavior.Invoke(IncomingContext context\', \'Comment 59: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Monitoring\\\\\\\\ProcessingStatisticsBehavior.cs:line 23 at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107 at NServiceBus.BehaviorChain`1.Invoke() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 52 at NServiceBus.Pipeline.PipelineExecutor.Execute[T](BehaviorChain`1 pipelineAction\', \'Comment 60: T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 129 at NServiceBus.Pipeline.PipelineExecutor.InvokePipeline[TContext](IEnumerable`1 behaviors\', \'Comment 61: TContext context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 85 at NServiceBus.Pipeline.PipelineExecutor.InvokeReceivePhysicalMessagePipeline() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 102 at NServiceBus.Unicast.UnicastBus.TransportMessageReceived(Object sender\', "Comment 62: TransportMessageReceivedEventArgs e) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\UnicastBus.cs:line 826 at NServiceBus.Unicast.Transport.TransportReceiver.OnTransportMessageReceived(TransportMessage msg) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 411 at NServiceBus.Unicast.Transport.TransportReceiver.ProcessMessage(TransportMessage message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 344 at NServiceBus.Unicast.Transport.TransportReceiver.TryProcess(TransportMessage message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 228 at NServiceBus.Transports.SQLServer.AmbientTransactionReceiveStrategy.TryReceiveFrom(TableBasedQueue queue) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\888dd942b44bad5a\\\\\\\\src\\\\\\\\NServiceBus.SqlServer\\\\\\\\AmbientTransactionReceiveStrategy.cs:line 57{code}\'", "Comment 63: \'Te błedy lecą praktycznie od wczoraj!image-2023-03-30-18-45-37-204.png!\'", "Comment 64: \'Hi Ewelina,Are mentioned ASNs the only ones that requires immediate repairing? Today", \'Comment 65: we will unblock the process but it needs to be investigated in RCA tas tomorrow morning.Please\', "Comment 66: let us know if there are more examples to correct.Regards\'", \'Comment 67: "*Dla\\\'T-5041/23/L\\\'* ZW-130/03/23/D ZW-137/03/23/D*Dla T-5059/23/G*ZS-1640/03/23/G*Dla T-2040/23/P*ZS-953/03/23/P ZS-950/03/23/P ZS-951/03/23/P*Dla\\\'T-2224/23/I\\\'* ZS-1076/03/23/I ZS-1077/03/23/I*Dla\\\'T-2225/23/I\\\'*ZS-1076/03/23/IZS-1077/03/23/I"\', "Comment 68: \'SN-1202900/2023\'", "Comment 69: \'Can you explain which process has been unlocked to drain synchro ? \'", "Comment 70: \'Some of the orders have been resent and so the trips. An entries in the DHC Service database were missing for orders", "Comment 71: trips.list:T-2034/23/PT-2992/23/ST-120/23/JST-2994/23/ST-3775/23/MT-4997/23/LT-3567/23/ŁT-2039/23/PT-4992/23/LT-2040/23/PT-5026/23/GT-2226/23/IT-2041/23/PT-2176/23/IT-2453/23/DT-2453/23/DT-5059/23/GT-2201/23/ICan you verified again and send cases for current missing data.\'", \'Comment 72: "{code:java} SELECT * FROM [Evolution_DHCountry].[dbo].[ShippingNotices] sh left join [Evolution_DHCService].[dbo].[ShippingNotices] shc on sh.id=shc.Id where shc.id is null and sh.IssueDate>=\\\'2023-03-29 00:00\\\' and sh.Status=3{code}{code:java}SELECT * FROM [Evolution_DHCountry].[dbo].[Orders] c left join [Evolution_DHCService].[dbo].[Orders] e on c.id=e.id where c.CreateDate>=\\\'2023-03-25 00:00:00.000\\\' and e.id is null and c.DocumentNumerator_Year=2023 and c.DocumentNumerator_Month=3 and c.Status in(5,6) and c.OrderType=2{code}"\', "Comment 73: \'What these shipping notices have in common and what caused problem with them? \'", "Comment 74: \'They were missing in DHCService", "Comment 75: and as for the reason RCA should be created for analysis.\'", "Comment 76: \'RCa is created under :DGS-8881\']"]\nRelated Issues:\n[\'DGS-8881\', \'DGS-8965\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8878\n\n### Instruction:\nMigration files for customer 008093\n\n### Response:\n["Comment 1: [\'[^AA - PAS_Migration_PURCHASEINVOICE_workfile_Faber.xlsx] _(126 kB)_[^AA - PAS_Migration_SALESINVOICE_workfile_Faber.xlsx] _(603 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'[~mbovene@deheus.com],the invoices have been migrated into PROD Intense environment.You can verify it.Best regards,Grzegorz\'", "Comment 4: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8877\n\n### Instruction:\nThere is analysis of procedure for calculating technical results in MAS NL (in MAS BE it\'s similar, but sequence of generating PI and SI from SR is different)\r\n \xa0[^Technical Results.xlsx]\r\n\r\n\xa0\r\n|\xa0|\xa0|Documents involved in calculations|\xa0Documents involved in calculations|\xa0Documents involved in calculations|\r\n|Name|Value selected from documents|SR|PI|SI|\r\n|Deliver date DOC\'s|PI, SI|\xa0|x|x|\r\n|Deliver day broilers first loaders|PI|x|x|x|\r\n|Delivery date all loaders|PI|x|x|x|\r\n|Average weight first loaders|SR, PI|x|x|x|\r\n|Weight of all loaders (in kg)|SR|x|\xa0|\xa0|\r\n|Disapproves all loaders (in kg)|SR|x|\xa0|\xa0|\r\n|Average weight all loaders|SR, PI|x|x|x|\r\n|Total value of all loaders|PI|x|x|x|\r\n|Numbers of all loaders (quantity)|SR|x|\xa0|\xa0|\r\n|m2|Customer card|\xa0|\xa0|\xa0|\r\n|Average weight in gram|SR, PI|x|x|x|\r\n|Number of DOC\'s|PI, SI|\xa0|x|x|\r\n|Total value of DOC\'s|PI, SI|\xa0|x|x|\r\n|Total weight Feed (in kg)|PI, SI, Feed sale|\xa0|x|x|\r\n|Total value Feed\xa0|PI, SI, Feed sale|\xa0|x|x|\r\n|Numbers of first loaders (quantity)|SR|x|\xa0|\xa0|\r\n|Weight of first loaders (in kg)|SR|x|\xa0|\xa0|\r\n|Disapproves first loaders (in kg)|SR|x|\xa0|\xa0|\r\n|Total value of first loaders|PI|x|x|x|\r\n|Delivery date previous round|PI|x|x|x|\r\n|Dropout percentage|SR, PI, SI|x|x|x|\r\n|Feed conversion netto|SR, PI, SI, Feed sale|x|x|x|\r\n|Feed conversion 1.500 gram|SR, PI, SI, Feed sale|x|x|x|\r\n|Maximum days of living|PI, SI|x|x|x|\r\n|Average days of living|SR, PI, SI|x|x|x|\r\n|Growth per day (in grams):|SR, PI, SI|x|x|x|\r\n|Production number|SR, PI, SI|x|x|x|\r\n|Feed profit per broiler|SR, PI, SI, Feed sale|x|x|x|\r\n|First Load percentage|SR|x|\xa0|\xa0|\r\n|Average price delivered DOC\'s|PI, SI|\xa0|x|x|\r\n|Average price delivered broilers|PI, SR|x|x|x|\r\n|Average price feed per 100 kg|PI, SI, Feed sale|\xa0|x|x|\r\n|Feedcost / kg. broilers bruto 1500 gr|SR, PI, SI, Feed sale|x|x|x|\r\n|Feedcost / kg. broilers netto|SR, PI, SI, Feed sale|x|x|x|\r\n|Feedcost / kg. broilers netto|SR, PI, SI, Feed sale|x|x|x|\r\n|Feed use per delivered broiler per gram per day|SR, PI, SI, Feed sale|x|x|x|\r\n|Startfeed per delivered DOC\'s per gram|PI, SI, Feed sale|\xa0|x|x|\r\n|Fase 2 feed per delivered DOC\'s per gram|PI, SI, Feed sale|\xa0|x|x|\r\n|Fase 3 feed per delivered DOC\'s per gram|PI, SI, Feed sale|\xa0|x|x|\r\n|Fase 4 feed per delivered DOC\'s per gram|PI, SI, Feed sale|\xa0|x|x|\r\n|Percentage Wheat|PI, SI, Feed sale|\xa0|x|x|\r\n|Amount of DOC\'s per m2|PI, SI, Customer card|\xa0|x|x|\r\n|Net Weight per delivered broilers per m2|SR, Customer card|x|\xa0|\xa0|\r\n|Saldo per m2|PI, SI, Feed sale, Loan payment, Customer card|\xa0|x|x|\r\n|Saldo /\xa0 m2 / day|SR, PI, SI, Feed sale, Loan payment, Customer card|x|x|x|\r\n|Feed Profit / m2 / day|PI, SI, Feed sale|\xa0|x|x|\r\n|Percentage Corn|PI, SI, Feed sale|\xa0|x|x|\r\n|Average price delivered broilers per kg|PI, SR|x|x|x|\r\n|Net weight per delivered broilers m2 AL|SR, Customer card|x|\xa0|\xa0|\r\n|Age first loaders|SR|x|\xa0|\xa0|\r\n|Age all loaders|SR|x|\xa0|\xa0|\r\n|Hakdermatitus|SR|x|\xa0|\xa0|\r\n|Voerprogramma|Round|\xa0|\xa0|\xa0|\r\n|Feed profit|PI, SI, Feed sale|x|x|x|\n\n### Response:\n["Comment 1: [\'[^Technical Results.xlsx]\']"]\nRelated Issues:\n[\'DGS-8732\', \'DGS-8883\', \'DGS-8215\', \'DGS-8325\', \'DGS-8641\', \'DGS-8675\', \'DGS-8714\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8876\n\n### Instruction:\nProśba o usunięcie dokumentu AM 00004/2023/03 – za duża liczba rekordów.\r\n\r\nCzy mamy jakieś rozwiązanie z poziomu usera na tego typu błędy na przyszłość?\n\n### Response:\n["Comment 1: [\'Documenthas been discarded\'", "Comment 2: \'What about 2nd question?\'", "Comment 3: \'we will back with answer. Can I lower the priority ?\'", "Comment 4: \'Ofcourse \'", "Comment 5: \'Unfortunatelly there is no solution from user side. Only from database.\'", "Comment 6: \'Could you please confirm if we can close this task?Regards\'", "Comment 7: \'Sure\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8875\n\n### Instruction:\nPlease remove/disable additional technology SN506159 from DHC Compound.\r\n\r\nPlease do the same for SN506247, as requested in ticket DGS-8867, this is getting urgent.\r\n\r\nRegards,\r\nRob.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hi Rob,I have increased Priority for DGS-8867,so working on both.Regards\'", "Comment 3: \'SN506159 has been deactivated", "Comment 4: please verify.Regards\'", "Comment 5: \'Thank you for your support", "Comment 6: the ticket can be closed.Regards,Rob.\'", "Comment 7: \'This additional tech is in hindsight still active.Could you please have another look at it?Regards,Rob.\'", "Comment 8: \'Please", "Comment 9: check now.Regards\'", "Comment 10: \'Great", "Comment 11: is inactive now.Thanks again for the support.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8874\n\n### Instruction:\nGood morning, since middle of March the integration of the data between ERP and DHC is not working properly, we cannot sent the data from ERP to DH Apps: orders and master data, please check and fix the communication. We are getting the following message from the interface AIS:\r\nPlugin return message: ERROR sending datacontract to webmethods.io. Details : Http status 500 (Internal Server Error): failed parsing retrieved response object. -\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: "Calling: DhpWEBUI...System.NotSupportedException: The response content cannot be parsed because the Internet Explorer engine is not available\', \'Comment 4: or Internet Explorer\\\'s first-launch configuration is not complete. Specify the UseBasicParsing parameter and try again. at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.VerifyInternetExplorerAvailable(Boolean checkComObject) at Microsoft.PowerShell.Commands.InvokeWebRequestCommand.ProcessResponse(WebResponse response) at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()PS D:\\\\\\\\kotrak>"\', "Comment 5: \'Dear Katarzyna,Please", "Comment 6: verify if it is working now.Regards\'", "Comment 7: \'Hello", "Comment 8: can you inform what was not working? In meantime we will push data to synchronise. \'", "Comment 9: \'Report server was stopped again and not connected to db.Please", "Comment 10: let me know if synchronisation is working now\'", "Comment 11: \'Hi", \'Comment 12: we have verified if the data/documents are sent to DHC\', \'Comment 13: and unfortunately they are not. We still have SO/PO documents stuck in the integration\', "Comment 14: and the message is: Plugin return message: ERROR sending datacontract to webmethods.io. Details : Http status 500 (Internal Server Error): failed parsing retrieved response object. - As example: SO000417/SO000455/SO000432/SO000420/SO259. PO000423/PO000421/PO000413/PO000427... !image-1!\'", "Comment 15: \'it is not working \'", \'Comment 16: "DlaPO000423 i PO000421{code:java}<PurchOrder>PO000423</PurchOrder> <PurchOrder>PO000423</PurchOrder> Line 8074: <SourceInfo>Intake_20235228105223000_PO000423</SourceInfo> Line 8078: ObjectType: OrderObject\', \'Comment 17: Id: Id: PO000423\', \'Comment 18: FieldName: OrderType\', "Comment 19: Message: Realization date can\'t be earlier than issue date Line 8081: ObjectType: OrderObject", \'Comment 20: Id: Id: PO000423\', \'Comment 21: FieldName: OrderType\', "Comment 22: Message: Realization date can\'t be earlier than issue date Line 8084: ObjectType: OrderObject", \'Comment 23: Id: Id: PO000423\', \'Comment 24: FieldName: OrderType\', "Comment 25: Message: Realization date can\'t be earlier than issue date Line 16217: <PurchOrder>PO000423</PurchOrder>{code}{code:java}2023-03-30 13:11:49,649 [28] DEBUG Evolution.DHCERPService.ImplementationRestWoW.Savers.DataContractSaver`2 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.ImplementationRestWoW\\\\\\\\Savers\\\\\\\\DataContractSaver.cs:39] - Saving IntakeDataContractDeHeusWoW2023-03-30 13:11:49,664 [28] ERROR Evolution.DHCERPService.Service.BaseSaveService`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseSaveService.cs:66] - Validation Exception:Exception of type \'Evolution.DHCERPService.Service.Interface.ExceptionHandling.DataValidationException\' was thrown.ObjectType: OrderObject", \'Comment 26: Id: Id: PO000423\', \'Comment 27: FieldName: OrderType\', "Comment 28: Message: Realization date can\'t be earlier than issue date2023-03-30 13:11:49,664 [28] ERROR Evolution.DHCERPService.Service.BaseSaveService`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseSaveService.cs:75] - Validation Exception:Exception of type \'Evolution.DHCERPService.Service.Interface.ExceptionHandling.DataValidationException\' was thrown.ObjectType: OrderObject", \'Comment 29: Id: Id: PO000423\', \'Comment 30: FieldName: OrderType\', "Comment 31: Message: Realization date can\'t be earlier than issue date2023-03-30 13:11:49,664 [28] ERROR Evolution.DHCERPService.ImplementationRestWoW.Savers.DataContractSaver`2 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.ImplementationRestWoW\\\\\\\\Savers\\\\\\\\DataContractSaver.cs:49] - Validation Exception:Exception of type \'Evolution.DHCERPService.Service.Interface.ExceptionHandling.DataValidationException\' was thrown.ObjectType: OrderObject", \'Comment 32: Id: Id: PO000423\', \'Comment 33: FieldName: OrderType\', \'Comment 34: Message: Realization date can\\\'t be earlier than issue date{code}"\', \'Comment 35: "These are in DHC and DHP now after restart of Business Platform: PO000423/PO000421/PO000413However\', "Comment 36: there are dozens Ordres that do not arrive to Pant with error message:Realization date can\'t be earlier than issue datefor example: PO000438", \'Comment 37: 446\', \'Comment 38: 442\', \'Comment 39: 448\', \'Comment 40: 447\', \'Comment 41: 449\', \'Comment 42: 443\', \'Comment 43: 441\', \'Comment 44: 439\', \'Comment 45: etcNo wonder if we have examples like that!image-2023-03-30-17-29-43-216.png!That is why validation failed for Purchase Orders [^image-2023-03-30-17-29-43-216.png]As I already mentioned\', \'Comment 46: I have restarted business platform. Found nothing unusual in logs so far. Could you please\', \'Comment 47: resend Sales Order from ERP to DHC once again?Regards"\', "Comment 48: \'Tylko to jest dziwne", "Comment 49: bo Sales Ordery z tak zrobionymi datami puszcza:!image-2023-03-30-17-58-46-571.png!!image-2023-03-30-17-58-23-953.png!\'", "Comment 50: \'We are fixing the issue on ERP side \'", "Comment 51: \'Shall we close this task?\'", "Comment 52: \'Actually you can close this ticket", \'Comment 53: but currently I have problem with only one PO-368 - error 500 occurs still. If you can help to resolve that PO-368 within\', "Comment 54: then we can close the task. \'", "Comment 55: \'Hi,Are you sure that it isPO-368? I cannot see this document in both appsRegards!image-2023-04-20-08-16-26-353.png!!image-2023-04-20-08-17-03-161.png!\'", "Comment 56: \'!image-2023-04-20-08-21-27-821.png!\'", "Comment 57: \'indeed the PO-368 is not in DH Apps", \'Comment 58: and we do not know why\', \'Comment 59: the message Error-500 does not explain too much\', \'Comment 60: can you investigate deeper\', \'Comment 61: please\', "Comment 62: or shall we look inside ERP? \'", \'Comment 63: "Hi,Could you please resendPO-368 and provide me with it\\\'s created date and issue date?Regards"]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8873\n\n### Instruction:\nFor order SOBE000018737 the one-time recipes are not created in DHC: As far we can see orders are send with additions from Webmethods. Please check\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Please resent an order from ERP.\'", "Comment 3: \'Just resend 702260\'", "Comment 4: \'Sorry", "Comment 5: just resend \'", "Comment 6: \'SOBE000018737 \'", "Comment 7: \'!afbeelding!\'", "Comment 8: \' !screenshot-1! \'", "Comment 9: \'Please resent an order from ERP.In dhc were two the same additional technology with product definition=1one of them has been archived. !screenshot-2! \'", \'Comment 10: "Oke\', \'Comment 11: I understand; Order was now cancelled and a new order will be created. i\\\'ll check that one if it is processed correct"\', "Comment 12: \'Thank you.\'", "Comment 13: \'[[DHC 3.0] missing one-time/onetime recipe for SO", "Comment 14: brak onetime receptury dla zamówienia. |onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bDHC%203.0%5d%20missing%20one-time/onetime%20recipe%20for&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{DEE5C2FD-8FB2-4F3E-88D7-1E04278DDE76}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHC%203.0%5D%20missing%20one-time%5C%2Fonetime%20recipe%20for%7CDEE5C2FD-8FB2-4F3E-88D7-1E04278DDE76%2F%29])\'", "Comment 15: \'ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': "Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8872\n\n### Instruction:\nDear ,\r\n\r\nPlease help to check this issue in Hai Phong 2 plant (0436) . PLR 4361240323076 receipt both bulk and batch.\r\n\n\n### Response:\n['Comment 1: []']\nRelated Issues:\n['DGS-8829']\n\n### End"}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8871\n\n### Instruction:\nGood morning, since middle of March the integration of the data between ERP and DHC is not working properly, we cannot sent the data from ERP to DH Apps: orders and master data, please check and fix the communication. We are getting the following message from the interface AIS: \r\nPlugin return message: ERROR sending datacontract to webmethods.io. Details : Http status 500 (Internal Server Error): failed parsing retrieved response object. - \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", \'Comment 4: any news? this is urgent\', \'Comment 5: people are waiting for the Sales Orders\', "Comment 6: adn Purchase Orders to register daily operations. \'", \'Comment 7: "Hi,Issue has been reported as a service request with Priority P3. If this is really urgent as commented below\', "Comment 8: why didn\'t you raise an Incident with highier Priority from the very beginning?AsDGS-8874 has been raised right now", \'Comment 9: I am closing SR.Regards"\', "Comment 10: \'Thank you", "Comment 11: please close this ticket. \']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8870\n\n### Instruction:\nHi,\r\nPlease help to check this issue in Can Tho Plant ( 0437) .\r\nCan not release this lot ( 140123L00123-271022CHN-MEN ).\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: \\\'2023-03-30 08:16:45 (00d6e63e-fc48-49bf-8425-e725e9a0a83d/Plant.WMS.BusinessLogic/VNPCT-TS01/35264/224) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 4: "host": { "Value": "10.84.165.11:85"\', \'Comment 5: "HasValue": true\', \'Comment 6: "Host": "10.84.165.11"\', \'Comment 7: "Port": 85 }\', \'Comment 8: "path": "/api/WarehouseStocktaking/registerUnitLoadStocktaking"\', \'Comment 9: "queryString": []\', \'Comment 10: "requestBody": "\\\\\\\\{\\\\\\\\"unitLoadStocktakingData\\\\\\\\":[{\\\\\\\\"unitLoadId\\\\\\\\":\\\\\\\\"6566df10-c81f-4057-aa0d-0c1071ac8d1f\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":0}}]}"}.Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).\\\'\', "Comment 11: \'could you please verify it that problem still occurs?\'", "Comment 12: \'Hello,Yes", "Comment 13: this problem still occurs. User can not stocktaking this lot .\'", "Comment 14: \'Hi,tomorrow will stock count", "Comment 15: so please solve this error today. Thank u.\'", "Comment 16: \'!image-2023-03-31-15-25-33-690.png!\'", "Comment 17: \'{code:java}2023-03-31 20:31:38 (bff12ead-5bd7-4ba7-a19b-65fb990f62e5/Plant.Stock.BusinessLogic/VNPCT-TS01/37472/254) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CompensateRegisterStockUnitStocktakingCommand](Plant.Stock.BusinessLogic.Application.Interfaces.Stocktaking.Commands.CompensateRegisterStockUnitStocktakingCommand) methodSystem.ArgumentNullException: Value cannot be null.Parameter name: value at Newtonsoft.Json.JsonConvert.DeserializeObject(String value", \'Comment 18: Type type\', \'Comment 19: JsonSerializerSettings settings) at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value\', \'Comment 20: JsonSerializerSettings settings) at Plant.Stock.BusinessLogic.Application.Stocktaking.StocktakingService.CompensateRegisterStockUnitStocktaking(Guid correlationId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\StocktakingService.cs:line 274 at Plant.Stock.BusinessLogic.Application.Stocktaking.CommandHandlers.CompensateRegisterStockUnitStocktakingCommandHandler.Handle(CompensateRegisterStockUnitStocktakingCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\CommandHandlers\\\\\\\\CompensateRegisterStockUnitStocktakingCommandHandler.cs:line 38 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-03-31 20:31:38 (null/Plant.Stock.BusinessLogic/VNPCT-TS01/37472/237) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/stocktaking/compensateRegisterStockUnitStocktaking" responded 500 in 20.4732 ms{code}\\\'\', \'Comment 21: \\\'Request WMSA{code:java}2023-03-31 20:31:38 (bff12ead-5bd7-4ba7-a19b-65fb990f62e5/Plant.WMS.BusinessLogic/VNPCT-TS01/39200/247) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 22: "host": { "Value": "10.84.165.11:85"\', \'Comment 23: "HasValue": true\', \'Comment 24: "Host": "10.84.165.11"\', \'Comment 25: "Port": 85 }\', \'Comment 26: "path": "/api/WarehouseStocktaking/registerUnitLoadStocktaking"\', \'Comment 27: "queryString": []\', \'Comment 28: "requestBody": "{\\\\\\\\"unitLoadStocktakingData\\\\\\\\":[{\\\\\\\\"unitLoadId\\\\\\\\":\\\\\\\\"6566df10-c81f-4057-aa0d-0c1071ac8d1f\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":0}}]}"}.Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error). at Refit.RequestBuilderImplementation.<>c__DisplayClass20_0.<<BuildVoidTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 773--- End of stack trace from previous location where exception was thrown --- at Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineExternalApi.CompensateRegisterStockUnitStocktaking(Guid correlationId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineExternalApi.cs:line 91 at Castle.Proxies.Invocations.IStockEngineExternalApi_CompensateRegisterStockUnitStocktaking.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Plant.WMS.BusinessLogic.Application.WarehouseStocktaking.Handlers.RegisterUnitLoadStocktakingCommandHandler.<>c__DisplayClass6_0.<Handle>b__2() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseStocktaking\\\\\\\\Handlers\\\\\\\\RegisterUnitLoadStocktakingCommandHandler.cs:line 52 at Plant.WMS.BusinessLogic.Application.Workflows.WorkflowRunner.Run(Workflow workflow) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\Workflows\\\\\\\\WorkflowRunner.cs:line 21 at Plant.WMS.BusinessLogic.Application.WarehouseStocktaking.Handlers.RegisterUnitLoadStocktakingCommandHandler.Handle(RegisterUnitLoadStocktakingCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseStocktaking\\\\\\\\Handlers\\\\\\\\RegisterUnitLoadStocktakingCommandHandler.cs:line 60 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Plant.WMS.BusinessLogic.Infrastructure.Api.Controllers.WarehouseStocktakingController.RegisterUnitLoadStocktaking(RegisterUnitLoadStocktakingViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\WarehouseStocktakingController.cs:line 151 at lambda_method(Closure \', \'Comment 29: Object \', \'Comment 30: Object[] ) at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target\', \'Comment 31: Object[] parameters) at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 32: ObjectMethodExecutor executor\', \'Comment 33: Object controller\', \'Comment 34: Object[] arguments) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next\', \'Comment 35: Scope& scope\', \'Comment 36: Object& state\', \'Comment 37: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next\', \'Comment 38: Scope& scope\', \'Comment 39: Object& state\', "Comment 40: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync() at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIIndexMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'", \'Comment 41: \\\'LOG LOG WMSa{code:java}2023-03-31 20:31:38 (bff12ead-5bd7-4ba7-a19b-65fb990f62e5/Plant.WMS.BusinessLogic/VNPCT-TS01/39200/247) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[RegisterUnitLoadStocktakingCommand](Plant.WMS.BusinessLogic.Application.Interfaces.WarehouseStocktaking.RegisterUnitLoadStocktakingCommand) methodRefit.ApiException: Response status code does not indicate success: 500 (Internal Server Error). at Refit.RequestBuilderImplementation.<>c__DisplayClass20_0.<<BuildVoidTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 773--- End of stack trace from previous location where exception was thrown --- at Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineExternalApi.CompensateRegisterStockUnitStocktaking(Guid correlationId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineExternalApi.cs:line 91 at Castle.Proxies.Invocations.IStockEngineExternalApi_CompensateRegisterStockUnitStocktaking.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Plant.WMS.BusinessLogic.Application.WarehouseStocktaking.Handlers.RegisterUnitLoadStocktakingCommandHandler.<>c__DisplayClass6_0.<Handle>b__2() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseStocktaking\\\\\\\\Handlers\\\\\\\\RegisterUnitLoadStocktakingCommandHandler.cs:line 52 at Plant.WMS.BusinessLogic.Application.Workflows.WorkflowRunner.Run(Workflow workflow) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\Workflows\\\\\\\\WorkflowRunner.cs:line 21 at Plant.WMS.BusinessLogic.Application.WarehouseStocktaking.Handlers.RegisterUnitLoadStocktakingCommandHandler.Handle(RegisterUnitLoadStocktakingCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseStocktaking\\\\\\\\Handlers\\\\\\\\RegisterUnitLoadStocktakingCommandHandler.cs:line 60 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-03-31 20:31:38 (null/Plant.WMS.BusinessLogic/VNPCT-TS01/39200/178) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/WarehouseStocktaking/registerUnitLoadStocktaking" responded 500 in 58.6384 ms{code}\\\'\', "Comment 42: \'!image-2023-03-31-16-31-26-661.png!!image-2023-03-31-16-32-16-068.png!!image-2023-03-31-16-32-34-850.png!\'", "Comment 43: \'[[DHP 3.0] Brak unit loadu", "Comment 44: na stocku jest|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Brak%20unit%20loadu,%20na%20stocku%20jest&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{961E2282-2E7C-47A8-B946-33764D357518}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHP%203.0%5D%20Brak%20unit%20loadu%2C%20na%20stocku%20jest%7C961E2282-2E7C-47A8-B946-33764D357518%2F%29])\'", "Comment 45: \'Please", "Comment 46: try to release now.Regards\'", "Comment 47: \'Hi,Today", "Comment 48: we are still facing this problem with the two lots below. So how to fix it?Lot number : 030223L00323-311223CHN-EPP and 070323L00523-230123CHN-EPP!image-1!\'", "Comment 49: \'437-W0023G!image-2023-04-03-07-36-20-333.png!437-W0020V!image-2023-04-03-07-37-52-645.png!\'", "Comment 50: \'!image-2023-04-03-07-48-37-070.png!!image-2023-04-03-07-49-09-330.png!\'", "Comment 51: \'8CD999E9-1565-4AC3-A772-93936E9F3B9A\'", "Comment 52: \'For barcode437-W0023G please try to release", "Comment 53: it should be fine now.\'", "Comment 54: \'Regarding production070323L00523-230123CHN-EPP", \'Comment 55: barcode 437-W0020V\', \'Comment 56: I cannot recreate error\', "Comment 57: could you please send a screenshot?Regards\'", "Comment 58: \'Hi.I tried to increase /or decrease this lot", "Comment 59: but the system gave an error!image-2!!image-3!\'", "Comment 60: \'!image-2023-04-03-10-08-21-755.png!\'", \'Comment 61: \\\'2023-04-03 14:16:46 (null/Plant.WMS.BusinessLogic/VNPCT-TS01/24492/201) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/WarehouseStocktaking/registerUnitLoadStocktaking" responded 500 in 37.4843 ms\\\'\', "Comment 62: \'!image-2023-04-03-10-22-43-091.png!\'", "Comment 63: \'!image-2023-04-03-10-48-00-280.png!\'", "Comment 64: \'na stocku barcode jest do itema widocznego na delivery!image-2023-04-03-10-50-50-396.png!\'", \'Comment 65: "w wmsselect itemid,* from UnitLoads where barcode like \\\'437-W0020v\\\' and ItemId=\\\'DA4A7DD7-BE1A-4E66-AB93-4DAF680C29EC\\\'ten barcode jest przypisany do innegoitema niz jest na deliveryi inny niz dla barcode na stocku"\', "Comment 66: \'Could you please provide more details barcode 437-w0020v on WMS module is linked to 91C5006-05/8-B40not for item3201050. ( in stock it is correct)Could you bring back infoamtion how it was proceed", \'Comment 67: did you changed something from database\', "Comment 68: if this barcode should be realeted to3201050 so what about this item91C5006-05/8-B40?\'", "Comment 69: \'prośba o pomoc w analizie", "Comment 70: po stand up - prośba też Macieja.Nie da się wydać stocka na zero - barcode 437-W0020v\'", \'Comment 71: "To był barcode \\\'437-W002{color:#de350b}O{color}V\\\' a nie \\\'437-W002{color:#de350b}0{color}V\\\'. I tak jak w przypadku poprzednich UL\', \'Comment 72: nie ma go w WMSie.!screenshot-1!{code:java}SELECT * FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where barcode = \\\'437-W002OV\\\' SELECT * FROM [DHPlantWMSBusinessLogicMain].[dbo].[UnitLoads] where barcode = \\\'437-W002OV\\\' SELECT * FROM [DHPlantWMSBusinessLogicMain].[dbo].[Items] where id = \\\'DA4A7DD7-BE1A-4E66-AB93-4DAF680C29EC\\\'{code}"\', \'Comment 73: "Good day\', "Comment 74: regarding the code 437-W002OV\' I unintentionally misled you", \'Comment 75: the data has been corrected please check."\', \'Comment 76: "HiIt\\\'s working.Please close the ticket . Thank you."]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8869\n\n### Instruction:\nwe need to create production order for medicated feed but system is showing exceeded quantity. I checked the system and we already created one PRO and PLR, we cancelled PLR but was not possible cancel PRO, and we need to create new PRO because they changed the recipe version.\r\n\r\nPRO-1046 - please cancel\r\nItem SUC6687-MD-S20\r\nOrder SO-638075442/23/PED\r\n\r\nCould you cancel PRO-1046 to be possible create new one?\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'!MicrosoftTeams-image (60)!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: " !screenshot-1! Medicated production order\\\'s and production lots quantity cannot exceed the sum of all attached order element remaining quantities"\', "Comment 4: \'Changing this options in the configuration it should be possible to generate a document despite the confirmed PrO. !screenshot-2! Another option is a new medicated production set up in DHC.As for PrO cancellation developers analysis is required - unfortunately analyzed in the morning.Please let me know whether to change the configuration or whether this ticket can be processed in the morning.\'", "Comment 5: \'klient nie odpisał na wczorajszy komentarz.\'", "Comment 6: \'PRO zostało usunięte. Sum of production requests na medicated production controls = 0.Mimo", \'Comment 7: że użytkownik posiadał uprawnienie do usuwania potwierdzonych PRO\', \'Comment 8: to opcja była nieaktywna w przypadku\', "Comment 9: gdy PLR został już utworzony i anulowany. DAP-13495 - zostanie to poprawione w werji 8.6.Żeby usunąć PRO należy:1. Tymczasowo usunąć ProductionOrderId z usuniętego PLRa w [dbo].[ProductionLots]2. W DHP usunąć PRO (po odpięciu PLRa z PRO opcja stanie się dostępna)3. Uzupełnić ProductionOrderId usuniętego PLRa w [dbo].[ProductionLots]!PRO_cancelled! !Medicated!\'", "Comment 10: \'Hello. PrO has been removed. In case a PLR has been created and canceled there will be a change in the application to make canceling the PrO available as well. For version 8.6.\'", "Comment 11: \'Hello Piotr,we checked and now we can create new PrO. Thank you.\'", "Comment 12: \'[[DHP 3.0] Usunięcie PrO", "Comment 13: productionorder.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Usuni%C4%99cie%20PrO,%20productionorder.&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{0A3DBF1B-FFDB-47DD-B672-6C10C1152EE7}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHP%203.0%5D%20Usuni%C4%99cie%20PrO%2C%20productionorder.%7C0A3DBF1B-FFDB-47DD-B672-6C10C1152EE7%2F%29])\']"]\nRelated Issues:\n[\'DGS-8887\', \'DAP-13495\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8868\n\n### Instruction:\nDear !\r\n\r\nPlease help to check this issue. Can not create sample from PLRs with reason that recipes could not be found.\r\nPLR 4371290323005 item 91C5006-03 Ver 24\r\nPLR 4373290323005 item 91C5007A-05 Ver 32\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-03-29-18-48-15-493.png!!image-2023-03-29-18-48-48-361.png!\'", "Comment 4: \'Pomimo resenda", "Comment 5: technologia w module QAM dalej niedostępna!image-2023-03-29-18-53-04-851.png!\'", "Comment 6: \'!image-2023-03-29-19-08-32-089.png!\'", "Comment 7: \'!image-2023-03-29-19-23-27-592.png!!image-2023-03-29-19-24-07-544.png!\'", "Comment 8: \'!image-2023-03-29-19-34-46-628.png!\'", \'Comment 9: "{code:java}023-03-29 23:14:34 (489a5719-653f-4eca-9f66-578f2b95a81e/Plant.QAM.BusinessLogic/VNPCT-TS01/32984/198) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CreateInternalSampleForProductionLotReportPromiseCommand](Plant.QAM.BusinessLogic.Application.Interfaces.Samples.Internal.Commands.CreateInternalSampleForProductionLotReportPromiseCommand) methodKotrak.Common.Application.Exceptions.BusinessLogicException: Technology of ID \\\'5c0c7b1d-b9ae-48fe-b145-8be48f0d60da\\\' was not found ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: TechnologyByIdNotFoundMessageTemplate at Plant.QAM.BusinessLogic.Application.Technologies.TechnologyRepositoryExtensions.GetOrThrow(ITechnologyRepository repository\', \'Comment 10: AggregateId id) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application\\\\\\\\Technologies\\\\\\\\TechnologyRespositoryExtensions.cs:line 10 at Plant.QAM.BusinessLogic.Application.Samples.InternalSampleService.<>c__DisplayClass19_0.<UpdateInternalSample>b__3(AggregateId technologyId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application\\\\\\\\Samples\\\\\\\\InternalSampleService.cs:line 169 at Plant.QAM.BusinessLogic.PublishedLanguage.ActionExtensions.<>c__DisplayClass3_0`1.<ToVoidFunc>b__0(T arg) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\ActionExtensions.cs:line 29 at Plant.QAM.BusinessLogic.PublishedLanguage.Monads.EitherExtensions.<>c__DisplayClass5_0`4.<Match>b__0(Either`2 e) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\Monads\\\\\\\\EitherExtensions.cs:line 50 at Plant.QAM.BusinessLogic.PublishedLanguage.Monads.Either`2.Match[T](Func`2 left\', \'Comment 11: Func`2 right) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\Monads\\\\\\\\Either.cs:line 31 at Plant.QAM.BusinessLogic.PublishedLanguage.Monads.EitherExtensions.Match[TLeft,TMiddle,TRight,TResult](Either`2 either\', \'Comment 12: Func`2 left\', \'Comment 13: Func`2 middle\', \'Comment 14: Func`2 right) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\Monads\\\\\\\\EitherExtensions.cs:line 49 at Plant.QAM.BusinessLogic.Application.Interfaces.Tolerances.ToleranceSource.<>c__DisplayClass2_0`1.<Match>b__1(Either`2 e) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application.Interfaces\\\\\\\\Tolerances\\\\\\\\ToleranceSource.cs:line 31 at Plant.QAM.BusinessLogic.PublishedLanguage.Monads.Either`2.Match[T](Func`2 left\', \'Comment 15: Func`2 right) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\Monads\\\\\\\\Either.cs:line 31 at Plant.QAM.BusinessLogic.Application.Interfaces.Tolerances.ToleranceSource.Match[TResult](Func`2 itemQualityNorm\', \'Comment 16: Func`2 rawMaterialVersion\', \'Comment 17: Func`1 latestRawMaterial\', \'Comment 18: Func`2 technology\', \'Comment 19: Func`3 productVersion\', \'Comment 20: Func`1 latestProduct) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application.Interfaces\\\\\\\\Tolerances\\\\\\\\ToleranceSource.cs:line 26 at Plant.QAM.BusinessLogic.Application.Interfaces.Tolerances.ToleranceSource.Act(Action`1 itemQualityNorm\', \'Comment 21: Action`1 rawMaterialVersion\', \'Comment 22: Action latestRawMaterial\', \'Comment 23: Action`1 technology\', \'Comment 24: Action`2 productVersion\', \'Comment 25: Action latestProduct) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application.Interfaces\\\\\\\\Tolerances\\\\\\\\ToleranceSource.cs:line 43 at Plant.QAM.BusinessLogic.Application.Samples.InternalSampleService.<>c__DisplayClass19_0.<UpdateInternalSample>b__0(ToleranceSource toleranceSource) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application\\\\\\\\Samples\\\\\\\\InternalSampleService.cs:line 156 at Plant.QAM.BusinessLogic.PublishedLanguage.ActionExtensions.<>c__DisplayClass3_0`1.<ToVoidFunc>b__0(T arg) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\ActionExtensions.cs:line 29 at Plant.QAM.BusinessLogic.PublishedLanguage.DataStructures.EditableValue`1.Match[TResult](Func`2 update\', \'Comment 26: Func`1 noAction) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\DataStructures\\\\\\\\EditableValue.cs:line 24 at Plant.QAM.BusinessLogic.Application.Samples.InternalSampleService.UpdateInternalSample(AggregateId id\', \'Comment 27: UpdateInternalSampleDataStructure updateData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application\\\\\\\\Samples\\\\\\\\InternalSampleService.cs:line 155 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 28: "wiszą messages dla QAM: tj wolno schodzą. !screenshot-1! {code:java}SELECT *update iset createdate=\\\'2023-03-29 21:00\\\',processdate=\\\'2023-03-29 21:00\\\' FROM [DHPlantQAMBusinessLogicIntercontext].[dbo].[InboundMessages] iwhere messagetype like \\\'%item%\\\'SELECT *update iset createdate=\\\'2023-03-29 21:00\\\',processdate=\\\'2023-03-29 21:00\\\' FROM [DHPlantQAMBusinessLogicIntercontext].[dbo].[InboundMessages] iwhere messagetype like \\\'%recipe%\\\'{code}!image-2023-03-29-20-39-39-468!"\', "Comment 29: \'Please check again: !screenshot-2! there are still messages to be processed for the QAM module \\\\\'LecoResultRegisteredEvent\\\\\' so there may be delays - I will let you know when all messages will be processed.If there is still a lack of technology", \'Comment 30: please let me know. !screenshot-3! {code:java}Deadlock dla modułu QAM.2023-03-29 14:08:33 (20cb75fc-c751-4230-8f3e-34957e4a670e/Plant.QAM.BusinessLogic/VNPCT-TS01/13904/12) [Error] Microsoft.EntityFrameworkCore.Query - An exception occurred in the database while iterating the results of a query for context type \\\\\\\'"Plant.QAM.BusinessLogic.Infrastructure.EF.QamContext"\\\\\\\'."""System.InvalidOperationException: An exception has been raised that is likely due to a transient failure. Consider enabling transient error resiliency by adding \\\\\\\'EnableRetryOnFailure()\\\\\\\' to the \\\\\\\'UseSqlServer\\\\\\\' call. ---> System.Data.SqlClient.SqlException: Transaction (Process ID 121) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 31: Boolean breakConnection\', \'Comment 32: Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 33: Boolean callerHasConnectionLock\', \'Comment 34: Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 35: SqlCommand cmdHandler\', \'Comment 36: SqlDataReader dataStream\', \'Comment 37: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 38: TdsParserStateObject stateObj\', \'Comment 39: Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows) at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout\', \'Comment 40: Boolean& more) at System.Data.SqlClient.SqlDataReader.Read() at Microsoft.EntityFrameworkCore.Storage.RelationalDataReader.Read() at Microsoft.EntityFrameworkCore.Query.Internal.QueryingEnumerable`1.Enumerator.BufferlessMoveNext(DbContext _\', \'Comment 41: Boolean buffer) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 42: Func`3 operation\', \'Comment 43: Func`3 verifySucceeded) --- End of inner exception stack trace --- at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 44: Func`3 operation\', \'Comment 45: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.Query.Internal.QueryingEnumerable`1.Enumerator.MoveNext() at Microsoft.EntityFrameworkCore.Query.Internal.QueryBuffer.IncludeCollection[TEntity,TRelated,TElement](Int32 includeId\', \'Comment 46: INavigation navigation\', \'Comment 47: INavigation inverseNavigation\', \'Comment 48: IEntityType targetEntityType\', \'Comment 49: IClrCollectionAccessor clrCollectionAccessor\', \'Comment 50: IClrPropertySetter inverseClrPropertySetter\', \'Comment 51: Boolean tracking\', \'Comment 52: TEntity entity\', \'Comment 53: Func`1 relatedEntitiesFactory\', \'Comment 54: Func`3 joinPredicate) at lambda_method(Closure \', \'Comment 55: QueryContext \', \'Comment 56: ProductionLotReportEntity \', \'Comment 57: Object[] ) at Microsoft.EntityFrameworkCore.Query.Internal.IncludeCompiler._Include[TEntity](QueryContext queryContext\', \'Comment 58: TEntity entity\', \'Comment 59: Object[] included\', \'Comment 60: Action`3 fixup) at lambda_method(Closure \', \'Comment 61: TransparentIdentifier`2 ) at System.Linq.Enumerable.SelectEnumerableIterator`2.MoveNext() at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source) at Microsoft.EntityFrameworkCore.Query.Internal.LinqOperatorProvider.ResultEnumerable`1.GetEnumerator() at Microsoft.EntityFrameworkCore.Query.Internal.LinqOperatorProvider.ExceptionInterceptor`1.EnumeratorExceptionInterceptor.MoveNext()"{code}\\\'\', \'Comment 62: "it\\\'s working.please close the ticket"]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8867\n\n### Instruction:\nPlease remove/deactivate additional technology SN506247 from DHC Compound.\r\n\r\nKind regards,\r\nRob.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: " Can this ticket\\\'s priority be set to P1.They would like to send the recipe now because the feed needs to be produced today.Regards,Rob."\', "Comment 3: \'Hi Rob,Changing priority now.Regards\'", "Comment 4: \'Thank you", "Comment 5: on behalf of the Formulation team :)\'", "Comment 6: \'SN506247 has been deactivated. Please", "Comment 7: verify.Regards\'", "Comment 8: \'Thank you for the support", "Comment 9: the ticket can be closed.\'", "Comment 10: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8866\n\n### Instruction:\nSystem not allow to change expiry date of item ENWINC52A, internal serial number WI-203/1/23-1, correct expiry date 30/01/2024. We can change expiry date but when we click to save, system shows an error message.\r\nCould you check why we have this error?\r\n\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: "{code:java}2023-03-30 09:39:54 (8f1cebc5-9b69-46bc-a770-4dadb2025698/Plant.Stock.BusinessLogic/BR-8-SV-VM0102/2372/302) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateDeliveryDetailsCommand](Plant.Stock.BusinessLogic.Application.Interfaces.Deliveries.Commands.UpdateDeliveryDetailsCommand) methodMicrosoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): Cannot insert duplicate key row in object \\\'dbo.Deliveries\\\' with unique index \\\'IX_Deliveries_SourceDocumentId_SourceDocumentNo_ItemId_SerialNumber_ExpiryDate_BagSize\\\'. The duplicate key value is (389626ef-2700-4539-9c70-235451c6a247\', \'Comment 4: <NULL>\', \'Comment 5: 603e3d81-5af9-45a9-b308-a7c7ec0695a2\', \'Comment 6: 118/23\', \'Comment 7: 2024-01-30 00:00:00.0000000\', \'Comment 8: 1.000000).The statement has been terminated.{code}"\', "Comment 9: \'The error results from the limitation on the dbo.Deliveries table.There cannot be two entries with the same data for:SourceDocumentId,SourceDocumentNo,ItemId,SerialNumber,ExpiryDate,BagSizeI set it one day later and the change was saved.!image-2023-03-30-14-48-51-304.png!\'", "Comment 10: \'Hi Piotr,so do you mean that is not possible create 2 different internal serial number for the same VT intake with the same lot number and expiry date?What are the fields key to control the intake?\'", "Comment 11: \'For deliveries tabel is unigue index for columns:SourceDocumentId", \'Comment 12: SourceDocumentNo\', \'Comment 13: ItemId\', \'Comment 14: SerialNumber\', \'Comment 15: ExpiryDate\', \'Comment 16: BagSize -if the second one is the same\', "Comment 17: there will be a error in the application.\'", \'Comment 18: "Hi Piotr,it\\\'s clear\', \'Comment 19: you can close this task. Thank you."\', "Comment 20: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8865\n\n### Instruction:\nHi,\r\nPlease help check DHC. We can not open menu Recipes to accept recipes, event thought try with some filter\r\nNote: we already rebuild index system \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-03-29-16-30-02-551.png!\'", "Comment 4: \'_{color:#0747a6}Note: we already rebuild index system{color}_Aj dont tink soł:!image-2023-03-29-16-37-19-532.png!\'", "Comment 5: \'21 minut :D!image-2023-03-29-17-14-54-293.png!\'", "Comment 6: \'It works now:!image-2023-03-29-17-18-27-083.png!Please", "Comment 7: verify\'", "Comment 8: \'still error!image-2!\'", "Comment 9: \'I think this can be performance issue of the databse server that I cannot check:!image-2023-03-30-16-47-20-176.png|width=421,height=240!What I can advise for now is to filter Recipes", \'Comment 10: for example\', "Comment 11: you may filter by date or by Production area!image-2023-03-30-16-48-24-755.png|width=795,height=375!Regards\'", "Comment 12: \'!image-2023-03-30-16-49-02-328.png!\'", "Comment 13: \'please try\'", \'Comment 14: "Hi,Why don\\\'t you try to filter Recipes by Production area?!image-2023-04-03-12-33-50-803.png!"\', \'Comment 15: "we have try with that: sometimes\\\'s ok sometime is not. i thinks it should be improve performnace by first defautl when login"\', "Comment 16: \'hej [~przemyslaw.przybyszewski@kotrak.com] Przemku :)czy my coś jesteśmy w stanie z tym zrobić? tam co ok 3-4 dni fragmentacja sięga do 90 %. Wczoraj znowu na 70 paru rowach było 90% i więcej", \'Comment 17: w sumie ok 170 rows było powyżej 30 % (wybacz\', "Comment 18: nie śmieciłam screenem) plus używanie filtra podobno też nie zawsze jest rozwiązaniem dogodnym dla usera :P\'", "Comment 19: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'", "Comment 20: \'Hi,When the Recipes are synchronized in the background", \'Comment 21: the filter may not work. However\', "Comment 22: we have also noticed that fragmentation of DHC indexes becomes very high every 4 days. You need to solve it on your side.Regards\'", "Comment 23: \'hi,we have schedule for rebuild index but not daily because performance and database volume. but Fragment have still like that after rebuild", "Comment 24: so it not related to fragment but related to data for recipes to high\'", "Comment 25: \'Hi,Yes", \'Comment 26: but data for recipes does not depend on Kotrak. The issue with Recipes list occurs also in other countries whe synchronization of recipes goes in the background.In that case\', "Comment 27: can we close this task?Regards\'", "Comment 28: \'DHC is place to store data. if as you mentioned: how can we login and accept recipes if error orrcurs like that\'", \'Comment 29: \\\'The best way is to filter by date for example start date: today and filter by production area. And check "show the lates version" This should help.!image-2023-04-05-08-00-06-970.png!\\\'\', "Comment 30: \'Hi,Is there anything else we can do for you?Regards\'", "Comment 31: \'it not working well. still have isssue now\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8864\n\n### Instruction:\nHi\r\n\r\nWe are facing some delay on light scan on motorola scanners (MC93 model).\r\nWhen we open the own motorola application and test the light scan, we pull the trigger and instantly the scanner light turns on.\r\nHowever, inside the DHP app, no matter the screen, it takes more than 10 seconds to turn on the scanner light.\r\n\r\nThis is happening since go live in Itaberaí (sep/2021), however the time of delay is increasing every new version. I was 3s, then 5s, now is more than 10s.\r\n\r\nCould you please check this?\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: \'Maicon,Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'", \'Comment 3: "[~mberbert@deheus.com] we have checked on our server and we didn\\\'t have the issue with delay as you have described. But we are using: https://www.zebra.com/us/en/products/spec-sheets/mobile-computers/handheld/tc52-tc57.html"\', \'Comment 4: "Hi [~marcin.kleszcz@kotrak.comI\\\'ll make a video for you next time I visit the factory.Maybe it can help you to identify what happens.Thank you very much"]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8863\n\n### Instruction:\nWe would like to have two daily lists (one with PI’s and one with SI’s) that contain:\r\n * All regular and financed invoices that were archived the day before\r\n * With the following colunms:\r\n * Customer Full-name\r\n * Archive date\r\n * Number\r\n * ERP number\r\n * Sector\r\n * Creator\r\n * State\r\n\r\n\xa0\r\n\r\nAre you able to automate the creation of such a list?\n\n### Response:\n["Comment 1: [\'!email_list_of_invoices!\'", "Comment 2: \'Due to issues with emails described in taskhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7649 temporary it will be 2 actions available from Lightning button in Inbox for these 2 reports.\'", "Comment 3: \'A report of archival invoices has been prepared", "Comment 4: available in inbox for Peter Moeliker\'", "Comment 5: \'[~tomasz.zygon@kotrak.com]Dodałem uprawnienia dla Petera Moelikera", "Comment 6: bo nie były jednak dodane.Na Test nie mamy tych akcji?\']"]\nRelated Issues:\n[\'DGS-7649\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8862\n\n### Instruction:\nHi\r\n\r\nI\'d like to have the translation files for R8.6.\r\nThe untranslated and also *system_messages* files because it is being displayed in english, no matter the user\'s choice of language.\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: \'Maicon,Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'", "Comment 3: \'* Web* Mobile* SystemMessages (Web + Mobile)\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8861\n\n### Instruction:\nHi\r\n\r\nWe need to fix translations for R8.5. Could you please send me the fixed merged translation file and untranslated file for this release?\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: \'Maicon,Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8860\n\n### Instruction:\nAfter restarting the virtual machine RSAPP06 (10.100.3.73) I could not access DHP 3.0 Test through the browser. After that, I restarted ISS on RSAPP06, after that I can access the login page via a web browser, but it tells me that my username and password are incorrect. I am sure that my password is correct because I saved it and it worked until before the restart. Can you check what the problem is?\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! \'", "Comment 4: \'Hello,what was done when you used the test environment and when you used this environment before? We need the address data for the database server.Regards\'", \'Comment 5: "I used it a month ago\', \'Comment 6: I can\\\'t remember exactly what I needed. Colleagues use it occasionally when they need to test something.rsdb09.emea.corp.deheus.com [10.100.3.75]"\', "Comment 7: \'Rabbit po uruchomieniu od razu sie stopujewpisy z eventa!image-2023-03-30-14-21-19-687.png!RabbitMQ: Erlang machine stopped instantly (distribution name conflict?). The service is not restarted", \'Comment 8: ignoring OnFail option.A corruption was discovered in the file system structure on volume D:.A corruption was found in a file system index structure. The file reference number is 0xc000000098f22. The name of the file is "\\\\\\\\Kotrak\\\\\\\\dhp30_IIS\\\\\\\\rabbitmq\\\\\\\\data\\\\\\\\db\\\\\\\\rabbit@RSAPP06-plugins-expand\\\\\\\\rabbitmq_web_stomp-3.8.5\\\\\\\\ebin". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".!image-2023-03-30-14-20-55-025.png!\\\'\', "Comment 9: \'Good morning", \'Comment 10: As part of the DGs project we do not handle requests related to the test environment\', \'Comment 11: here exceptionally we wanted to verify \', \'Comment 12: the operation of the application after restarting the pool. Actually\', \'Comment 13: the problem is not your login credentials. Please set up task DHITs\', "Comment 14: the problem is related to the operation of IIs services and mainly rabbit problem.May we close the task.\'", "Comment 15: \'Hello,regarding to our last comment we are closing this issue.Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8859\n\n### Instruction:\nwe have problem in report TT, it\'s showing wrong customer name in the release field. Production SUC1230-MD-S25, lot number 0891280223014, VT dispatch VT-1178, correct customer Marcelo Valles Bento, but is showing Marina Nogueira\r\n\r\nCould you fix the report for all units?\r\n\r\nThank you\r\n\n\n### Response:\n["Comment 1: [\'[^TrackAndTraceReadyProductReport (4).pdf] _(258 kB)_!tt error!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Nie wiem", \'Comment 4: co zmienili\', "Comment 5: ale chyba nie wyszłohttps://helpdesk.kotrak.com/browse/DHITS-745\'", "Comment 6: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'", "Comment 7: \'[~marcin.kleszcz@kotrak.com]widziałam kilka DHITSów dla Rio Claro na wydruki TT", \'Comment 8: tam zdaje się mieli coś sami zmieniać\', "Comment 9: ale nie wyszło... dacie rade spojrzeć na to? :)z góry dzięks\'", \'Comment 10: "Dear Priscyla,Could ypu please clarify few things:>>{color:#0747a6}_in report TT\', "Comment 11: it\'s showing wrong customer name in the release field -_ {color:#172b4d}does the issue occur for all Productions or only to thelot number 0891280223014?{color}{color}{color:#0747a6}{color:#172b4d}>>{color} _Could you fix the report for all units?_{color} - Do you mean all plants? If for all plants printout does not work correctly now", \'Comment 12: and it worked few days ago\', \'Comment 13: could you please let us know if anything was changed on your side\', \'Comment 14: and\', \'Comment 15: if yes\', \'Comment 16: could you please let us know what was changed?Best regards"\', \'Comment 17: "Aleksandra,we found this error till now only for this lot number. Do you know where is the error? If is in this production\', \'Comment 18: you need to fix only in this document\', "Comment 19: but if it\'s in report", \'Comment 20: you need to fix for this unit and how we have the same in all plants\', \'Comment 21: we need to have the correct report in all units."\', "Comment 22: \'!image-2023-03-31-18-55-12-022.png!\'", "Comment 23: \'!image-2023-03-31-18-55-41-202.png!\'", "Comment 24: \'!image-2023-03-31-18-56-18-932.png!\'", \'Comment 25: "{code:java}SELECT *SELECT * FROM [DHPlantStockBusinessLogicMain].[dbo].[Deliveries] where SourceDocumentNumber = \\\'0891280223014\\\' SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where LotNumber = \\\'0891280223014\\\' SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionOrders] where id = \\\'B477A8EA-3012-4651-A754-BF1DC6049527\\\' SELECT BP.Code\', "Comment 26: BP.Name FROM [DHPlantProdBusinessLogicMain].dbo.ProductionLots PL INNER JOIN [DHPlantProdBusinessLogicMain].dbo.ProductionOrders PO ON PO.Id = PL.ProductionOrderId INNER JOIN [DHPlantProdBusinessLogicMain].dbo.BusinessPartners BP ON BP.Id = PO.BusinessPartnerId WHERE PL.ID = \'BEAE28C4-0E16-4970-AAF2-24D2901C519F\' SELECT R.ReleaseDate", \'Comment 27: COALESCE(WOPD_Data.SourceDocumentNumber\', \'Comment 28: WD_Data.SourceDocumentNumber\', \'Comment 29: VC_Data.Document\', \'Comment 30: R.SourceDocumentNumber) AS Document\', \'Comment 31: COALESCE(WOPD_Data.Code\', \'Comment 32: WD_Data.Code\', \'Comment 33: VC_Data.Code\', \'Comment 34: PROD_Data.Code\', "Comment 35: \'\') AS CustomerCode", \'Comment 36: COALESCE(WOPD_Data.Name\', \'Comment 37: WD_Data.Name\', \'Comment 38: VC_Data.Name\', \'Comment 39: PROD_Data.Name\', "Comment 40: \'\') AS CustomerName", \'Comment 41: SUM(R.Quantity) AS ReleasedQuantity\', \'Comment 42: R.QuantityUnit AS ReleasedQuantityUnit\', \'Comment 43: COALESCE(WOPD_Data.ForeignDocumentInfo\', \'Comment 44: WD_Data.ForeignDocumentInfo\', \'Comment 45: VC_Data.ForeignDocumentInfo\', \'Comment 46: \\\'\\\') AS ForeignDocumentInfo FROM [DHPlantStockBusinessLogicMain].dbo.Deliveries D INNER JOIN [DHPlantStockBusinessLogicMain].dbo.StockUnits S ON S.DeliveryId = D.Id INNER JOIN [DHPlantStockBusinessLogicMain].dbo.StockUnitReleases R ON R.Id = S.Id where DeliveryId = \\\'6AF47AFF-6CB9-4DFC-9ED6-C23242245641\\\'{code}"\', "Comment 47: \'!image-2023-03-31-19-00-57-691.png!\'", \'Comment 48: "{code:java}SELECT R.SourceDocumentId,WDE.Id\', \'Comment 49: BP.Code\', \'Comment 50: BP.Name\', \'Comment 51: WOE.SourceDocumentId\', \'Comment 52: WOE.SourceDocumentNo\', \'Comment 53: WOE.SourceDocumentNumber\', \'Comment 54: r.SourceDocumentId AS ReleaseSourceDocumentId\', \'Comment 55: VE.ForeignDocumentInfoSELECT R.SourceDocumentId,WDE.Id\', \'Comment 56: BP.Code\', \'Comment 57: BP.Name\', \'Comment 58: WOE.SourceDocumentId\', \'Comment 59: WOE.SourceDocumentNo\', \'Comment 60: WOE.SourceDocumentNumber\', \'Comment 61: r.SourceDocumentId AS ReleaseSourceDocumentId\', \'Comment 62: VE.ForeignDocumentInfo ,ve.Id,*,WOE.No,WDE.WarehouseOrderElementNo,VE.No,WOE.No FROM [DHPlantStockBusinessLogicMain].dbo.StockUnitReleases R left JOIN [DHPlantStockBusinessLogicMain].dbo.StockUnits S ON S.id =R.Id left JOIN [DHPlantWmsBusinessLogicMain].dbo.WarehouseDispatches WDE ON WDE.Id = R.SourceDocumentId left JOIN [DHPlantWmsBusinessLogicMain].dbo.WarehouseOrderElements WOE ON WOE.Id = WDE.WarehouseOrderId AND ISNULL(WOE.No\', \'Comment 63: 0) = ISNULL(WDE.WarehouseOrderElementNo\', \'Comment 64: 0) left JOIN [DHPlantVCBusinessLogicMain].dbo.VehicleTicketElements VE ON VE.Id = WOE.SourceDocumentId AND VE.No = WOE.No left JOIN [DHPlantProdBusinessLogicMain].dbo.BusinessPartners BP ON BP.Id = VE.MainBusinessPartnerId where R.SourceDocumentId = \\\'BD862CEE-A1AC-4E1E-AA3A-ADF502DC4C76\\\'{code}{code:java} --select MainBusinessPartnerId,* from [DHPlantVCBusinessLogicMain].dbo.VehicleTicketElements where id = \\\'17F0C1D5-559F-4F91-9E16-7B544CBCF205\\\' --select MainBusinessPartnerId,* from [DHPlantVCBusinessLogicMain].dbo.VehicleTicketElements where id = \\\'17F0C1D5-559F-4F91-9E16-7B544CBCF205\\\' --select * from [DHPlantVCBusinessLogicMain].dbo.VehicleTickets where id = \\\'17F0C1D5-559F-4F91-9E16-7B544CBCF205\\\'-- select * from Orders where id in (\\\'F611D5DF-C513-4FCE-AD95-12A84135925A\\\',\\\'33EFC4F0-A8CC-45B1-B22C-822C33308805\\\',\\\'B6290E56-A903-4BDF-AB77-578D9814D081\\\',--\\\'4F730F71-EDB3-4021-A62C-58CF4516593D\\\',\\\'5AB9A750-B44F-4DC7-8257-B5A1E19365DB\\\'){code}Zbiera dane z 16 elementu*!image-2023-04-03-15-04-24-858.png!*"\', "Comment 65: \'Hej[~maciej.dobrzanski@kotrak.com]albo tu cos źle zbiera", \'Comment 66: albo w danych jest coś nakopane. Dlaczego zbiera dane z 16 elementu? Kurde\', \'Comment 67: nie wiemy\', \'Comment 68: co dalej z tym fantem\', \'Comment 69: masz kogoś od wydruków? Ewentualnie podpowiedz\', "Comment 70: co można jeszcze sprawdzić\'", \'Comment 71: "{code:java}select * from OrderElements where id in (\\\'F611D5DF-C513-4FCE-AD95-12A84135925A\\\',\\\'33EFC4F0-A8CC-45B1-B22C-822C33308805\\\',\\\'B6290E56-A903-4BDF-AB77-578D9814D081\\\',\\\'4F730F71-EDB3-4021-A62C-58CF4516593D\\\',\\\'5AB9A750-B44F-4DC7-8257-B5A1E19365DB\\\')--select * from BusinessPartners where id in (\\\'6094DA81-3573-4405-99FA-6239DD858C61\\\',\\\'8939635B-B045-434F-A248-B4F483F93EE0\\\',\\\'A7822B57-9072-4D49-BA83-0BE92C4C622A\\\')--select * from [DHPlantWmsBusinessLogicMain].dbo.WarehouseDispatches where id = \\\'BD862CEE-A1AC-4E1E-AA3A-ADF502DC4C76\\\'--select * from [DHPlantWmsBusinessLogicMain].dbo.WarehouseOrders where id = \\\'B35974F5-5F7C-48FB-B7F9-E299FEDA2F34\\\'{code}"\', "Comment 72: \'[^KtrTrackAndTraceReadyProductReportReleases.sql]\'", "Comment 73: \'[~aleksandra.przybylek@kotrak.com] zmieniłem procedurę i podegrałem ją pod RC.Podegrajcie proszę nową wersję na wszystkie fabryki w BR.[~marcin.kleszcz@kotrak.com] wrzućcie sobie gdzieś do repozytorium tą procedurę. [^KtrTrackAndTraceReadyProductReportReleases.sql] \'", "Comment 74: \'[^TTReadyProductRelease_old.sql]\'", "Comment 75: \'[^TTReadyProductRelease_old.sql]\'", "Comment 76: \'Dear Priscyla,We have corrected the printout and deployed in all plants. But I can see", \'Comment 77: inCaruaru it is not used.Please\', "Comment 78: verify the printout and let me me know aboutCaruaru.Regards\'", \'Comment 79: "Dear Aleksandra,the report is correct. Could you add in Caruaru only for RM? Because we don\\\'t have production in this unit.Thank you"\', "Comment 80: \'Dear Priscyla,For adding printout of raw material in Caruaru", "Comment 81: please raise a service request as this task concerns tt ready product release.Regards\'", "Comment 82: \'Hi Aleksandra,ok", "Comment 83: you can close this task. Thank you.\'", "Comment 84: \'Thank you\']"]\nRelated Issues:\n[\'DAP-13515\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8858\n\n### Instruction:\nCan you add user Manon Straatman in Intense? She works for Mineral and manures and needs the same rights as Freddy Westrik. She will get her own projects and will add hours to this projects.\n\n### Response:\n["Comment 1: [\'In progress.\'", "Comment 2: \'Done.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8857\n\n### Instruction:\nCould you give permission to all sectors for:\r\nHattum, Pascal van <PHattum@deheus.com>\r\nLinde, Arthur van der <ALinde@deheus.com>\r\nDat, Darwin <DDat@deheus.com> (he has access to LAS, MAS NL & MAS BE)\n\n### Response:\n["Comment 1: [\'Hello,\\\\rI will grant access.\'", "Comment 2: \'Hi [~mbovene@deheus.com],The accounts have been set up.Regards,Tomasz\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8856\n\n### Instruction:\nProduction operator by manual mistake confirmed PLR but the food is not produced and raw materials are not consumed, they actually confirmed in DHP production but the sole JO-3480-03-23-S is not confirmed. So please cancel JO. Thank you.\n\n### Response:\n["Comment 1: [\'!JO-3480-03-23-S!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hi,JO-348-03-23-S has been deleted with related IR- and IR+ documents.\'", "Comment 4: \'Thank you for your help. You can close the ticket now.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8855\n\n### Instruction:\nHi,\r\nPlease help check DHP Hai Phong 2 can not login and show error as screenshot\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: \'hi,it working now. you no need to check now.thank you\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8854\n\n### Instruction:\nWe made inventory per location and when we tried to close, system shows an error message. We closed to continue the process, but we need to know why shows error message.\r\n\r\ncould you check it?\r\n\r\nThank you\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: "Hello\', "Comment 4: can I get the error time?I don\'t see any errors for this inventory in the logs.Currently", \'Comment 5: the inventory is executed.Have any other changes been made in the meantime?Thank you and best regards."\', "Comment 6: \'Hello Piotr,the user tried to settle 30min after create the document", \'Comment 7: but how was not working and they needed to use\', \'Comment 8: they executed. But we need to do inventory again\', "Comment 9: and I need to know what heppened to avoid the error again.\'", "Comment 10: \'{code:java}2023-03-21 21:36:12 (2fc1dcfe-2f4a-4299-b4be-f675eb22ffa0/Plant.Stock.BusinessLogic/BR-3-SV-VM0202/1472/308) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[SettleStocktakingCommand](Plant.Stock.BusinessLogic.Application.Interfaces.Stocktaking.Commands.SettleStocktakingCommand) methodSystem.ArgumentException: Unit mismatch at Kotrak.Common.SharedKernel.Quantity.ToCommonUnit(Quantity x1", \'Comment 11: Quantity x2) at Plant.Stock.BusinessLogic.Application.Stocktaking.StocktakingService.Settle(Stocktaking stocktaking\', "Comment 12: IEnumerable`1 stockUnits) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\StocktakingService.cs:line 443 at Plant.Stock.BusinessLogic.Application.Stocktaking.StocktakingService.SettleStocktaking(AggregateId stocktakingId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\StocktakingService.cs:line 171 at Plant.Stock.BusinessLogic.Application.Stocktaking.CommandHandlers.SettleStocktakingCommandHandler.Handle(SettleStocktakingCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\CommandHandlers\\\\\\\\SettleStocktakingCommandHandler.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(){code}\'", "Comment 13: \'There was a unit mismatch for these items0000816SCAAZE03USCCAZD05USCCVED04USCDEST26VSCDVER26U. I corrected them in the database - currently there should be no error for the inventory.\'", "Comment 14: \'Hi Piotr,what was the unit mismatch? It was in pcs and should be Pcs? Or kg and should be Pcs?\'", \'Comment 15: "For StockUnitsthe given barcodes had different units from the others,that\\\'s exactly what the differences in units between pcs and kg were about."\', \'Comment 16: "Hello Piotr,ok\', \'Comment 17: it\\\'s clear. You can close this task. Thank you."\', "Comment 18: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8853\n\n### Instruction:\nThe system display wrong information about deviation, the calculation is done based on item, but display deviation considering truck weight.\r\nWe added configuration with 2%, and system show deviation lower than this but lock to close VT. \r\n\r\nExample on test database VT-83 , deviation is -1.73% and not allow to close. Deviation in weight -225kg, correct deviation 7,44%. The calculation is correct, but information displayed as deviation is wrong.\r\n\r\nCould you show the same and correct deviation that lock to close VT?\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: \'Dear Priscyla,Could you please confirm if this issue relates only to test environment or Prod is impacted as well??Regards\'", "Comment 4: \'Hello,we have problem in both", \'Comment 5: I used example from test because we can simulate some scenarios\', "Comment 6: but users asked help everyday because they have problem on production.\'", "Comment 7: \'Hi,Could you please provide us with specific example from Production environment?Regards\'", "Comment 8: \'Yes,VT-1906 plant RC1 - dispatch weight 88900kg", \'Comment 9: system shows 0,552% of deviation\', \'Comment 10: but not allow to close (and is correct because we have high deviation).The problem is the deviation that system display is based on truck weight\', \'Comment 11: and the deviation that lock close vt is based on the item weight\', "Comment 12: we need to see correct deviation.!vt19062.JPG|thumbnail!!vt1906.JPG|thumbnail!\'", "Comment 13: \'VT-1906 Total weight loaded (item+carrier unit) 12972kg Difference 488kgDeviation correct 3,76%\'", "Comment 14: \'Hej,[~maciej.dobrzanski@kotrak.com]czy jest szansa", "Comment 15: żeby to sprawdzić? :)!image-2023-04-03-12-45-09-649.png|width=228,height=152!\'", \'Comment 16: "Hi [~Aleksandra.Przybylek@kotrak.com]Could you please check Priscyla\\\'s last comment? Do you need anything else?Thank you"\', "Comment 17: \'Hi [~mberbert@deheus.com],This task has been forwarded to Dev team. We will let you know about the result as soon as possible.Best regards\'", "Comment 18: \'Hi [~mberbert@deheus.com],We plan for this task to be analyzed tomorrow.\'", \'Comment 19: "[~psilva@deheus.com]Hello,which configuration with 2% do you mean? Percentage packed dispatch deviation field? Because that one is used to calculate the total weight deviation.In VT-1906 entered departure weight is above the upper limit but in VT-83 the weight is below the lower limit and that\\\'s why the weight control modal appears.Lower and upper limits are calculated as follows (for dispatch):lower = arrival weight + packed weight - total weight deviationupper = arrival weight + packed weight + total weight deviationtotal weight deviation = bulkWeightDeviation + packedWeightDeviation + pieceWeightDeviation + weighbridgeAccuracypacked weight deviation = Percentage packed dispatch deviation * packed weightThe deviation field on VT document displays only the deviation between the predicted weight and entered departure weight. [^weight control.xlsx] !VT_deviations_2-1!"\', "Comment 20: \'Hi,Any feedback?\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8852\n\n### Instruction:\nThe following additional technologies for plant Helmond are not correct and must be removed/disabled:\r\nHE303300\r\nHE303306\r\nHE303436\r\n\r\nTo avoid issues with production, we wish to send new recipes directly after the additional technology is removed/disabled. This is planned on Thursday 30-03-2023 at 12:45\r\n(if additional technology is removed/disabled earlier, incorrect recipes will be send to PCS).\r\n\r\nCan you confirm that the additional technologies will be removed from DHC at 30-03-2023 12:45?\r\n\n\n### Response:\n[\'Comment 1: ["Hello Bob,I confirm. I will hand in this task to Piotr Gaczorek\', \'Comment 2: as he\\\'s working tomorrow morning shift.Regards"\', "Comment 3: \'Hi Aleksandra", \'Comment 4: ok\', \'Comment 5: thank you. Just to be sure: request is for Thursday\', "Comment 6: not tomorrow\'", "Comment 7: \'Yes", "Comment 8: right. But Piotr is working all week morning shift. :)I have already asked him to plan this task for 12:45 on Thursday.Regards\'", "Comment 9: \'Hello", "Comment 10: changes for three additional technologies have been made.\'", "Comment 11: \'We still these additional technologies in DHC. Can you check again if they were removed?!image!\'", "Comment 12: \'Yes", \'Comment 13: setProductDefinition = 0 for these should be enought\', "Comment 14: but I changed their status to blocked and renamed them with arch.\'", "Comment 15: \'Ok", "Comment 16: thank you. At 14.00 we will send new recipes for these codes and recipes should then be sent to PCS (because ProductDefinition = 0). Is that correct?\'", \'Comment 17: "Yes\', \'Comment 18: that\\\'s right.So I am waiting for final confirmation.Thank you."\', "Comment 19: \'Goodmorning,Yesterday at 16:22 a sales order for 303436 with special was sent. 303436 is a code for which you archived the additional technology.The one time recipe is generated on the correct code (303436", \'Comment 20: version 136 subversion 1\', "Comment 21: This recipe is sent to DHP but it is not sent to PCS.Did you also archive the three additional technologies in DHP? Otherwise recipe sending is still blocked.Plant needs the recipe for productionCan you please check /fix these recipes.\'", "Comment 22: \'Hellofor when you need that recipe - today ? If yes what hour?\'", "Comment 23: \'Plant needs the recipe now for production. I have created a new ticket for this: https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8882\'", "Comment 24: \'It was procced at new task ", "Comment 25: may we close this 1?\'", "Comment 26: \'Please perform same action for the other two codes as well (so that new recipes will be sent to PCS: 303300303306\'", "Comment 27: \'Sorry for the late reply", "Comment 28: I confirm that the changes have also been made for the others two.\'", "Comment 29: \'Thank you. This ticket can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8851\n\n### Instruction:\nError closing PO - CDN : PO-4/08/2018/RMP \r\nCould this PO be closed.\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: \'Close:!image-2023-03-28-17-50-40-388.png!Yes:!image-2023-03-28-17-51-42-936.png!{code:java}Server stack trace: at Kotrak.XLInterface.Orders.NewServices.ContractsService.TerminateContract(Int32 gidNumer", \'Comment 4: OrderCloseMode orderCloseMode) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHGUI-DHCDN982-JOB1\\\\\\\\DH CDN\\\\\\\\Kotrak.XLInterface.Orders\\\\\\\\NewServices\\\\\\\\ContractsService.cs:line 3144Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg\', \'Comment 5: IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData\', \'Comment 6: Int32 type) at Kotrak.XLInterface.Orders.Contracts.IContractsService.TerminateContract(Int32 gidNumer\', "Comment 7: OrderCloseMode orderCloseMode) at Kotrak.XLInterface.Orders.Presentation.Forms.ContractsList.TerminateContract(OrderCloseMode orderCloseMode) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHGUI-DHCDN982-JOB1\\\\\\\\DH CDN\\\\\\\\Kotrak.XLInterface.Orders.Presentation\\\\\\\\Contracts\\\\\\\\Forms\\\\\\\\ContractsList.cs:line 1669{code}!image-2023-03-28-17-51-42-936!\'", "Comment 8: \'Hi,PO is closed now.!image-2023-03-29-12-59-11-105.png!Regards\'", "Comment 9: \'I have asked if it is oke.\'", "Comment 10: \'Waiting for your feedback then.Regards\'", "Comment 11: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8850\n\n### Instruction:\nProśba o uwzględnienie wznowienia naliczania amortyzacji dokumentu RN.\r\nŚrodek trwały do sprawdzenia MT/9126.\r\n\r\n(uzgodnione telefonicznie z Panią Moniką)\n\n### Response:\n[\'Comment 1: [\\\'Please verify after changes in two filters:"Bez dotacji" and "Bez dotacji grupa"\\\'\', "Comment 2: \'Looks good - task to close :)\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8849\n\n### Instruction:\nFor item 140475, a new recipeversion was sent on 28-03-2023. Recipe is not arriving in PCS. Recipe is not available in recipe overview in DHP. It is available in masterdata overview. In DHC I found that item is linked, but on linking screen it does not show a base item (and DHC stops responding...). Can you check what is the issue with this item / relink it?\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-3!\'", "Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", "Comment 3: \'!image-2023-03-28-14-55-16-648.png!{code:java}2023-03-28 14:53:51 (/Plant.Prod.BusinessLogic/DHVD01AP175/3736/78) [Error] Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter - Error during process inbound messageKotrak.Common.Application.Exceptions.CommandValidationException`1[Plant.Prod.BusinessLogic.Application.Interfaces.Recipes.Commands.SynchronizeRecipeCommand]: Validation failed: -- RecipeNegativeElementQuantityMessage at Kotrak.Common.Infrastructure.Gate.Filters.ValidateCommandFilter`1.Execute(CommandPipelineContext`1 input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageHandlerFilter.Execute(InternalStorageProcessContext`1 input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter.Execute(InternalStorageContext`1 input)2023-03-28 14:54:02 (/Plant.Prod.BusinessLogic/DHVD01AP175/3736/26) [Error] Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter - Error during process inbound messageKotrak.Common.Application.Exceptions.CommandValidationException`1[Plant.Prod.BusinessLogic.Application.Interfaces.Recipes.Commands.SynchronizeRecipeCommand]: Validation failed: -- RecipeNegativeElementQuantityMessage at Kotrak.Common.Infrastructure.Gate.Filters.ValidateCommandFilter`1.Execute(CommandPipelineContext`1 input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageHandlerFilter.Execute(InternalStorageProcessContext`1 input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter.Execute(InternalStorageContext`1 input){code}\'", "Comment 4: \'Hi,Recipe with invalid quantity arrived from DHH!image-2023-03-28-15-01-23-372.png!!image-2023-03-28-15-02-08-484.png!You need to ask Holding to create correct one.Best regards\'", "Comment 5: \'Ok", "Comment 6: Thank you. I will check this with formulation.\'", "Comment 7: \'Thank you. Waiting for your feedback thenRegards\'", "Comment 8: \'Recipe was not correctly created in Allix. Correct version was sent and is now in DHP and sent to PCS. Would be better if the recipe with invalid composition is not accepted at all in DHC. I will propose this for the change list.This ticket can be closed.\'", "Comment 9: \'Thank you.Best regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8848\n\n### Instruction:\nHi, form Wiola.\r\n\r\n\r\n\r\nRafał Boniecki\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Czy chodzi o weryfikację przesłania do systemy XL i zaksięgowania wskazanych dodatków?jeśli tak", \'Comment 3: to najlepszym sposobem jest utworzenie testowej listy plac na której zostanie naliczony tego typu składnik i przesłanie jej do systemu XL a następnie wykonanie weryfikacji dekretacji po stronie księgowej.Czy są już jakieś wytyczne co do dekretu\', "Comment 4: na jakie kona powinien być on wykonany? Jeśli tak to proszę o informację.\'", \'Comment 5: "It\\\'s ok\', \'Comment 6: task to close\', \'Comment 7: thanks."]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8847\n\n### Instruction:\nThe image below is a print screen (CDN > Accounting > Documents > Documents) with an IPOR that needs to be posted. As shaded yellow you see that there is an amount on the line. \r\nWhen opening the line with double click and choose: Scheme: POR Internal, an amount should normally be entered here (this may differ from the amount in the line above) and I can adjust the ledger account and make the entry (bottom image) . But now nothing appears and I tried with multiple lines.\r\nThe problem is with both the PORC and SOR. When Richard Gans selects one for both POR and SOR, he will see the amounts.\r\nWijnen sees the amount zero.\r\n\r\nThe authorization for both users is the same\r\n\r\n\n\n### Response:\n["Comment 1: [\'[^Gans.docx] _(137 kB)_!image!!image-1!!image-2!!image-3![^Wijnen.docx] _(136 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'I do not repeat this kind of error on document even on exact permissions like user Wijnen . Document IPOR-28/01/2023/VIMP is already posted. Do you have any fresh unposted document with the same problem on user Wijnen where i can test?\'", "Comment 4: \'I do not repeat this kind of error on document even on exact permissions like user Wijnen . Document IPOR-28/01/2023/VIMP is already posted. Do you have any fresh unposted document with the same problem on user Wijnen where i can test?\'", "Comment 5: \'This is what user Wijnen does see.!image-4!\'", "Comment 6: \'User Wijnen has it with all IPOR files. User sees no values \\\\u200b\\\\u200bbut Richard Gans sees everything.For example number 4/04/2023/VIMP", "Comment 7: 71/03/2023/VIMP et cetera\'", "Comment 8: \'The first is Niels Wijnen and the second is Richard GansNiels see zero and Richard see !image-5!!image-6!\'", "Comment 9: \'Both user have the same parameters set in configuration", \'Comment 10: Both are able to work in De Heus Premix B.V. and Headquaters.Bookkeeping permission center.!image-2023-04-06-15-54-12-359.png!There are some differences beetween those two contexts\', \'Comment 11: for example there are different add-ins running for those twopermission centers. !image-2023-04-06-15-56-40-388.png!Please check if when both operators are working in context of the same permission center\', "Comment 12: results differs for IPOR-2/04/2023/VIMP document.IPOR-2/04/2023/VIMP document looks correct. There should be no difference when both operators work in context of the samepermission center.\'", "Comment 13: \'Both operators are working in context of the same permission center.!image-7!!image-8!\'", "Comment 14: \'Please check if both operators are working on the same database. Please ask operator Wijnen to log off and log on into the system and check if he can see values for IPOR documents.\'", "Comment 15: \'Please", "Comment 16: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 17: \'Both users are not working with the same record at the same time. Niels calls up a record and sees the amount zero", \'Comment 18: which he cannot use. If Richard calls it up\', \'Comment 19: he will see a number and can book it in. If Niels then calls up the record again\', "Comment 20: he will see the numbers.IThey ara not working in the same time on the same record.\'", "Comment 21: \'We can not repeat this issue in any IPOR document. We need more informations.Please provide screenshot for full ERPXL module window for Accounting > Posting", \'Comment 22: General and Header tab when this situations occurs.We need precise informations when (date and time) this happens for wich document.For test purpose plese check if\', \'Comment 23: when Ritchard Gans see ammount on IPOR document\', "Comment 24: Niels Winjen can post it. Please ask Richard to witraw from posting such document and let Niels do this.\'", "Comment 25: \'When Richard consults the record he sees the ammount.When Niels consults the record he sees zeroes.\'", "Comment 26: \'Print screens of the differences have already been made and reported. This happens with all documents that Niels consults.!image-9!!image-10!\'", \'Comment 27: "If it\\\'s not clear yet\', \'Comment 28: maybe we should start a teams session so Richard and Niels can show the differences."\', "Comment 29: \'Provided print screen is cut that I cannot see all the details I need to check.Teams session would be a good idea.\'", "Comment 30: \'Here is a description of the authorization of the users\'", "Comment 31: \'[^Niels Wijnen.docx] _(192 kB)_[^Richard Gans.docx] _(183 kB)_\'", \'Comment 32: "Yes I\\\'ve seen that. Both users have the same configuration for theirs accounts in ERPXL."\', "Comment 33: \'Please try to connect to Richard Gans account on Niels Wijnen computer and toNiels Wijnen account onRichard Gans computer", "Comment 34: and verify if you are repeting this issue.\'", \'Comment 35: "According to information gathered from Niels Winjen\', \'Comment 36: this problem also occurs in his account on other computers.We would like to test one more thing. We will create an exact copy of Niels Winjen\\\'s ERPXL account with a modified ID. Then we will check if this problem still occurs. Please let me know if you accept this solution."]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8846\n\n### Instruction:\nWe are receiving the same labels (product, plant, version, language)\r\n3 or 4 times in MILAS from DHC.\r\nPlease check why this is happening. \r\n\r\nE.g today (28/3) we received a label for plant 9 recipes 111249 version 334 language nl 3 times withing the same minute.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: \\\'W logu są trzy wpisy jeden po drugim DHERPServiceSendRequest.log.1{code:java}2023-03-28 08:17:17,689 [112] INFO WcfSendRequestLogger [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\Logging\\\\\\\\LoggingInspectorBehavior.cs:53] - Request:<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Header> <Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertLabel</Action> </s:Header> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <insertLabel xmlns="http://deheus.com/unit01/DHC"> <input xmlns=""> <header> <ReceivingSystem>Milas</ReceivingSystem> <SendingSystem>DHC</SendingSystem> <CreateDate xsi:nil="true" /> <CreateUser xsi:nil="true" /> <MessageID>29fabb38-ccfd-4427-ad77-f19fbf15fffe</MessageID> </header> <label> <itemCode>111249</itemCode> <creationDate>3/24/2023 9:12:54 PM</creationDate> <plant>9</plant> <recipeVersion>334</recipeVersion> \\\\t\\\\t...\\\\t\\\\t\\\\t\\\\t2023-03-28 08:17:18,298 [112] INFO WcfSendRequestLogger [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\Logging\\\\\\\\LoggingInspectorBehavior.cs:53] - Request:<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Header> <Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertLabel</Action> </s:Header> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <insertLabel xmlns="http://deheus.com/unit01/DHC"> <input xmlns=""> <header> <ReceivingSystem>Milas</ReceivingSystem> <SendingSystem>DHC</SendingSystem> <CreateDate xsi:nil="true" /> <CreateUser xsi:nil="true" /> <MessageID>29fabb38-ccfd-4427-ad77-f19fbf15fffe</MessageID> </header> <label> <itemCode>111249</itemCode> <creationDate>3/24/2023 9:12:54 PM</creationDate> <plant>9</plant> <recipeVersion>334</recipeVersion> <quantity>\\\\t\\\\t ...\\\\t\\\\t \\\\t\\\\t 2023-03-28 08:17:18,548 [81] INFO WcfSendRequestLogger [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\Logging\\\\\\\\LoggingInspectorBehavior.cs:53] - Request:<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Header> <Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertLabel</Action> </s:Header> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <insertLabel xmlns="http://deheus.com/unit01/DHC"> <input xmlns=""> <header> <ReceivingSystem>Milas</ReceivingSystem> <SendingSystem>DHC</SendingSystem> <CreateDate xsi:nil="true" /> <CreateUser xsi:nil="true" /> <MessageID>29fabb38-ccfd-4427-ad77-f19fbf15fffe</MessageID> </header> <label> <itemCode>111249</itemCode> <creationDate>3/24/2023 9:12:54 PM</creationDate> <plant>9</plant> <recipeVersion>334</recipeVersion>\\\\t\\\\t ...{code}Cały fragment loga - jest różnica w godzinie i kończą się sukcesem. [^DHERPServiceSendRequest.log.1 fragment.txt] W logu DHERPService też jest trzy razy informacja o wysyłce:!image-2023-03-28-12-13-10-547!\\\'\', "Comment 3: \'W ostatnim komentarzu jest info jak klient przekazał - przykładowa labelka jest trzy krotnie wysyłana", "Comment 4: prośba o pomoc w analizie z czego to może wynikać - dzięki.\'", "Comment 5: \'Hi", "Comment 6: DHCErpService has been changed to block multiple data sending described in the task.It will be required to be DHCErpService upgraded(upgrade date should be set with the PM).\'", "Comment 7: \'DHCErpService has been changed to block multiple data sending described in the task.\\\\rIt will be required to be DHCErpService upgraded(upgrade date should be set with the PM).\\\\rThis issue has been closed.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8845\n\n### Instruction:\nHi\r\n\r\nWe are facing issues with Orders sync from DHC to DHP in Rio Claro.\r\nSeveral orders are integrated to DHC, no erros are reported and we can\'t find these orders in DHP.\r\nFor example, we have these examples:\r\n\r\n||Order||DocumentId||DHC integration||DHP integration\r\n|OVE-080259|5638073942|2023-03-08 14:17:53.120|2023-03-24 16:48:06.634|\r\n|OVE-080263|5638071657|2023-03-08 14:17:53.339|2023-03-24 16:48:06.767|\r\n|OVE-080271|5638073182|2023-03-08 14:37:54.235|2023-03-24 16:48:06.271|\r\n\r\nAs you can check in the log register, DHC had no error during ERP integration request.\r\n\r\nThis turned very critical because we are running out of time to buy raw materials and produce these items. We had the same situation with DGS-8776 and now we have these.\r\n\r\nNo other plants reported this issue. It is probably a version issue.\r\n\r\nCould you please check why is this happening?\r\n\r\nThank you very much!\n\n### Response:\n["Comment 1: [\'logi erp service z 8mego :Line 1926: 2023-03-08 14:17:53,120[117]INFO Evolution.DHCERPService.Service.BaseSaveService`1[E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER401-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseSaveService.cs:79]- Saved: OrderObject with Id Company: 1 DocType:2 Id: 5638073942 Suffix PEDUnmapDeletedElements deletedElements.Count = 0!image-2023-03-27-19-21-14-094.png!!image-2023-03-27-19-21-14-094!ale wygląda to ok chyba ?Pytałam sie klienta czy poda namiar co nam było wysyłane 8mego ale nie ejst chetny. sprawdziłam że dhhitemy i itemy nie były ostatnio w ogóle edytowane.\'", "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: "We are very sorry [~mberbert@deheus.com]that you are facing a problem with synchronization. However this isn\\\'t our job to monitor the status of your disks\', \'Comment 4: this is something that yous infrastructure team should do.!image-2023-03-31-13-37-16-800.png|width=1775,height=893!"\', \'Comment 5: "HI [~Thank you for the analysis\', \'Comment 6: and you are right! It\\\'s our job to monitor the status of our disks. I\\\'ll request such monitoring to our IT team.I\\\'d like to understand why the transaction log of Evolution_DHCountry database is increasing so fast?Look the free space in disk server. Did you shrinked the files?Thank you!image!"\', "Comment 7: \'Aktualnie jest tyle samo !screenshot-1! \']"]\nRelated Issues:\n[\'DGS-8842\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8844\n\n### Instruction:\nHi\r\n\r\nWe want all plants with R8.5 (+GDC_2-3weeks) for:\r\n* Itaberaí\r\n* Apucarana\r\n* Toledo\r\n* Guararapes\r\n\r\nCould you please schedule the update untill 10am CEST for each plant?\r\nWhen is the next available date for you?\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: \'HiDid you have the opportunity to check this request?Thank you\'", "Comment 3: \'Hi [~mberbert@deheus.com]Estimation for upgrade from *8.3* to *8.5* per plant: * *18h* - the most likely case * +20% - the worst case * Working hours: Monday-Friday 7:00-15:00 CEST * Hyper care recommended but not included in the estimation. To be discussed.Draft plan: * 12.04.2023: Apucarana / 7:00-11:00 CEST / * 13.04.2023: Toledo / 7:00-11:00 CEST / * 16.04.2023: Itaberai/ 7:00-11:00 CEST / * 17.04.2023: Guararapes/ 7:00-11:00 CEST /\'", \'Comment 4: "Hi [~marcin.kleszcz@kotrak.com]We had an internal request to do scheduled maintenance on the DHApps applications over the weekend.We have the following window of no activies in the factories:||Plant||Stops at||Starts at|||GUA|Saturday 11am CEST|Monday 11am CEST||ITA|Saturday 11am CEST|Monday 11am CEST||APU|Saturday 11am CEST|Monday 5am CEST||TOL|Sunday 4am CEST|Monday 10am CEST|We know about additional costs on Saturdays and Sundays. So I\\\'d like to propose:||Plant||Date||Time|||GUA|10.04.2023|07am-11am CEST||ITA|10.04.2023|07am-11am CEST||TOL|10.04.2023|07am-10am CEST||APU|15.04.2023|11am-03pm CEST|As default\', \'Comment 5: we need to test access in the Friday so IT team can assure that you have right access before.Is it possible to do it in this time?Thank you"\', \'Comment 6: "[~mberbert@deheus.com]On Sunday and Monday in Poland we have Easter holidays. So\', \'Comment 7: on Monday we can\\\'t upgrade."\', \'Comment 8: "Hi [~Marcin.Kleszcz@kotrak.com]New proposal:||Plant||Date||Time|||*APU*|15.04.2023|11am-03pm CEST||*GUA*|17.04.2023|07am-11am CEST||*ITA*|17.04.2023|07am-11am CEST||*TOL*|17.04.2023|07am-10am CEST|We can\\\'t make these updates during the week because factories are running 24hs.Thank you very much!"\', "Comment 9: \'[~mberbert@deheus.com]I discussed this planning internally.We can do upgrades of DHP from Mon to Fri", "Comment 10: working hours 7:00-16:00.17.04.2023 :* ITA* GUA22.04.2023:* APU* TO\'", "Comment 11: \'Hi [~mberbert@deheus.com]as we have discussed last evening", "Comment 12: I will let you next week. We will be back work on Tuesday and I will try to manage it. \'", "Comment 13: \'[~mberbert@deheus.com]New proposal:||Plant||Date||Time|||*ITA*|17.04.2023|07am-11am CEST||*TOL*|17.04.2023|06am-10am CEST||*APU*|21.04.2023|07am-11am CEST||*GUA*|21.04.2023|12pm-16pm CEST|Before upgrade we need to check Evenet DB (DGS-8827)We will start on Friday - we need to prepare the version before upgrade", "Comment 14: and we will check servers and queues.Do you need hyper care?Do you approve the estimation?\'", \'Comment 15: "Hi [~marcin.kleszcz@kotrak.com]Final dates/times:||Plant||Date||Time|||ITA|17.04.2023|07am-11am CEST||TOL|17.04.2023|06am-10am CEST||APU|21.04.2023|12pm-16pm CEST||GUA|21.04.2023|12pm-16pm CEST|About checking servers\', \'Comment 16: will you need admin access to these servers?To whom we need to grant access?We don\\\'t need hyper care.Estimation approved!Thank you"\', "Comment 17: \'[~mberbert@deheus.com]admin access for:* Marcin Kleszcz* Maciej Buchacz* Wojciech Pyrlik* Maciej Dobrzanski\'", "Comment 18: \'[~piotr.gaczorek@kotrak.com] wszystkie fabryki (oczywiście oprócz Caruaru) podniesione z 8.3 do 8.5. Można zamknąć task.\'", "Comment 19: \'Plants:\\\\r * Itaberaí\\\\r * Apucarana\\\\r * Toledo\\\\r * Guararapes\\\\r\\\\rhave been updated to 8.5.\']"]\nRelated Issues:\n[\'DGS-8727\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8843\n\n### Instruction:\nIt has been found out that the recipe 23VOL030 is incorrectly linked in DHP. It is linked with the recipe 23GVL0125 (see print screen) and now the 6th version of the recipe 23VOL030 is shown as the 6th version of the recipe 23GVL0125 in Production Module\r\n\r\nAll our efforts to unlink these two recipes are in vain, so it would be highly appreciated if you could help us with this issue.\r\n\n\n### Response:\n["Comment 1: [\'!1.jpg|thumbnail!!2.jpg|thumbnail!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: \\\'good morning As far as I can see in DHc there is only base item with code similar to 23VOL030 is 23VOL030.25 do you wish set this as base item or you need to have code "23VOL030"?\\\'\', "Comment 4: \'We would like to have 23VOL030 as a base item and 23VOL030.25 as a sub-item\'", "Comment 5: \'there is no item23VOL030 in DHC could you please sent it ?\'", "Comment 6: \'do need to send the new version of the recipe from Bestmix or what do you mean?\'", "Comment 7: \'The new version for that recipe will be needed also", "Comment 8: but there is no item with code23VOL030 ( just that without no suffix) in your DHC. So I am unable to set it as base item. Could you send it from you ERP.\'", "Comment 9: \'code sent from ERP\'", "Comment 10: \'Ok please verify ", "Comment 11: please resend new reciepes from dhh and send create new recipes and etc for that item.!image-2023-03-29-14-19-31-561.png!\'", "Comment 12: \'We checked", "Comment 13: everything is fine now\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8842\n\n### Instruction:\nHi\r\n\r\nWe are facing issues with Orders sync from DHC to DHP in Rio Claro.\r\nSeveral orders are integrated to DHC, no erros are reported and we can\'t find these orders in DHP.\r\nFor example, we have these examples:\r\n\r\n||Order||DocumentId||DHC integration||DHP integration\r\n|OVE-080259|5638073942|2023-03-08 14:17:53.120|2023-03-24 16:48:06.634|\r\n|OVE-080263|5638071657|2023-03-08 14:17:53.339|2023-03-24 16:48:06.767|\r\n|OVE-080271|5638073182|2023-03-08 14:37:54.235|2023-03-24 16:48:06.271|\r\n\r\nAs you can check in the log register, DHC had no error during ERP integration request.\r\n\r\nThis turned very critical because we are running out of time to buy raw materials and produce these items. We had the same situation with DGS-8776 and now we have these.\r\n\r\nNo other plants reported this issue. It is probably a version issue.\r\n\r\nCould you please check why is this happening?\r\n\r\nThank you very much!\n\n### Response:\n["Comment 1: [\'[^DHERPService.log20230308] _(7,12 MB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Are there any missing orders right now?If not 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.\'", \'Comment 4: "Hi AgnieszkaYou can lower the priority to P2\', \'Comment 5: but I need that this issue will be analysed tomorrow morining in the first time. We manually synchronized all Orders needed for today and tomorrow.However we are talking about a loss of R$ 100k per day. This is huge. That\\\'s why we need a quick solution.Thank you very much"\', \'Comment 6: "create date na dhc service jest 16.47select i.UpdateDate,i.CreateDate,o.CreateDate\', \'Comment 7: o.UpdateDate,i.DhhItemId,* from OrderElements oejoin orders o on oe.orderid=o.id join items i on i.id=oe.ItemId where o.ForeignDocumentNumber in (\\\'OVE-080259\\\',\\\'OVE-080263\\\',\\\'OVE-080271\\\')!image-2023-03-27-19-08-50-500.png!"\', "Comment 8: \'logi erp service z 8mego :Line 1926: 2023-03-08 14:17:53,120 [117] INFO Evolution.DHCERPService.Service.BaseSaveService`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER401-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseSaveService.cs:79] - Saved: OrderObject with Id Company: 1 DocType:2 Id: 5638073942 Suffix PEDUnmapDeletedElements deletedElements.Count = 0!image-2023-03-27-19-21-14-094.png! !image-2023-03-27-19-21-14-094!ale wygląda to ok chyba ?\'", "Comment 9: \'Hello,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.Also If you want us to verify what happens please provide us information: * what was send to us from YOUR ERP or Dynamics system - we do not have access how that orders look at that moment. * how it was proceed?\'", \'Comment 12: "HiYes\', \'Comment 13: please\', \'Comment 14: raise a RCA.I\\\'m attaching the Service received request log file from DHC with information about data sent to you. And you have the Service log file attached when opening this issue.It proceeded with normal flow as all other orders:# We send from ERP# It integrates to DHC# DHC returns a success (or error) message# Minutes later the order is present on DHP systemThank you very much[^DHERPServiceReceivedRequest.log20230308] _(4,60 MB)_"\', "Comment 15: \'HiPlease", "Comment 16: also check DGS-8177Thank you\'", "Comment 17: \'RCa was created under dgs-8845", "Comment 18: may we close this task?\'", \'Comment 19: "HiYes! You can close this task.We\\\'ll follow on DGS-8845Thank you very much"]\']\nRelated Issues:\n[\'DGS-8845\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8841\n\n### Instruction:\nwe just discovered that since the update of DHP to version 8.5, the webservice is rejecting batch reports for the reason: \'Production lot element quantity should be greater than 0\': This is a change compared to the previous versions, which wasn\'t expecting. For this reason now many batch reports are rejected and we running into issues with our finished product stock in the ERP: Can you please check this? I think we need a fix for this, we\'re missing quite some batch reports for all locations\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 [~TDankers@deheus.com],This validation in fact was added during the hyper care in Guararapes in Brasil.We will introduce the configuration for that.Since it is a SQL procedure we will remove this validation on production.\'", "Comment 3: \'Zmiana była zrealizowana w DAP-13108 i dotyczy 3 procedur. Wrzucam skrypty do aktualizacji tych procedur na bazie modułu PCS Main w wersji 8.5. Jeżeli zostaną podane wartości ujemne", \'Comment 4: to wciąż poleci błąd. Dotyczy to ilości na elementach PLR i ELR oraz ilości na dostawach powiązanych z elementami PLR i ELR. Skrypty wrzucam w osobnych komentarzach\', \'Comment 5: bo Jira narzeka\', "Comment 6: że jest za dużo tekstu.\'", \'Comment 7: "*api.RegisterBatchReport*:{code:sql}CREATE OR ALTER PROCEDURE api.RegisterBatchReport(\\\\t@PcsLotId BIGINT,\\\\t@PcsBatchId BIGINT,\\\\t@QuantityKg DECIMAL(18,6),\\\\t@IsBrokenBatch BIT = 0,\\\\t@ReworkItemId INT = NULL,\\\\t@StartBatchMixing DATETIME2 = NULL,\\\\t@FinishBatchMixing DATETIME2 = NULL)ASBEGIN\\\\tSET NOCOUNT ON;\\\\tBEGIN TRY\\\\t\\\\tBEGIN -- Logger\\\\t\\\\t\\\\tDECLARE @Parameters NVARCHAR(MAX) = (\\\\t\\\\t\\\\t\\\\tSELECT\\\\t\\\\t\\\\t\\\\t\\\\t@PcsLotId AS PcsLotId,\\\\t\\\\t\\\\t\\\\t\\\\t@PcsBatchId AS PcsBatchId,\\\\t\\\\t\\\\t\\\\t\\\\t@QuantityKg AS QuantityKg,\\\\t\\\\t\\\\t\\\\t\\\\t@IsBrokenBatch AS IsBrokenBatch,\\\\t\\\\t\\\\t\\\\t\\\\t@ReworkItemId AS ReworkItemId,\\\\t\\\\t\\\\t\\\\t\\\\t@StartBatchMixing AS StartBatchMixing,\\\\t\\\\t\\\\t\\\\t\\\\t@FinishBatchMixing AS FinishBatchMixing,\\\\t\\\\t\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tSELECT Id\', \'Comment 8: PcsLotId\', \'Comment 9: PcsBatchId\', \'Comment 10: ItemId\', \'Comment 11: RecipeElementId\', \'Comment 12: QuantityKg,\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tSELECT Id\', \'Comment 13: ElementId\', \'Comment 14: DeliveryId\', \'Comment 15: Barcode\', \'Comment 16: SiloCode\', \'Comment 17: QuantityKg\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tWHERE APLED.ElementId = APLE.Id\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFOR JSON AUTO\', \'Comment 18: INCLUDE_NULL_VALUES\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t) As Deliveries\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tWHERE PcsLotId = @PcsLotId AND PcsBatchId = @PcsBatchId\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFOR JSON AUTO\', \'Comment 19: INCLUDE_NULL_VALUES\\\\t\\\\t\\\\t\\\\t\\\\t) AS Elements\\\\t\\\\t\\\\t\\\\tFOR JSON PATH\', \'Comment 20: INCLUDE_NULL_VALUES\', "Comment 21: WITHOUT_ARRAY_WRAPPER)\\\\t\\\\t\\\\tDECLARE @RequestLogId BIGINT\\\\t\\\\t\\\\tEXEC dbo.SaveSqlApiRequest \'RegisterBatchReport\'", \'Comment 22: @Parameters\', "Comment 23: @RequestLogId OUTPUT\\\\t\\\\tEND -- Logger\\\\t\\\\t\\\\t\\\\tDECLARE @ConstFactoryObjectTypeDosingSilo INT = 1\\\\t\\\\tDECLARE @ConstBatchReportType INT = 1\\\\t\\\\tDECLARE @ConstBatchStatusFinished INT = 3\\\\t\\\\tDECLARE @ConstAllowStockRegisteringOnSilosKey INT = 3\\\\t\\\\tDECLARE @ConstAllowStockRegisteringOnSilosTrueValue NVARCHAR(4) = \'True\'\\\\t\\\\tDECLARE @ProductionLotAggregateId UNIQUEIDENTIFIER\\\\t\\\\tDECLARE @RecipeAggregateId UNIQUEIDENTIFIER\\\\t\\\\tDECLARE @ReworkItemAggregateId UNIQUEIDENTIFIER\\\\t\\\\tDECLARE @AllowStockRegisteringOnSilos BIT\\\\t\\\\tDECLARE @ConstUndefinedBrokenBatchStatus INT = 0\\\\t\\\\tDECLARE @ConstCreatedBrokenBatchStatus INT = 1\\\\t\\\\tDECLARE @ConstConfirmedBrokenBatchStatus INT = 2\\\\t\\\\tDECLARE @SetRequestedQuantityBasedOnQuantity BIT\\\\t\\\\tBEGIN -- Validation\\\\t\\\\t\\\\tIF (@PcsLotId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000", "Comment 24: \'Parameter @PcsLotId cannot be null.\'", \'Comment 25: 1;\\\\t\\\\t\\\\tIF (@PcsBatchId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 26: \'Parameter @PcsBatchId cannot be null.\'", \'Comment 27: 1;\\\\t\\\\t\\\\tIF (ISNULL(@QuantityKg,0) <= 0)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 28: \'Parameter @QuantityKg cannot be null and should be greater than 0.\'", \'Comment 29: 1;\\\\t\\\\t\\\\tSET @ProductionLotAggregateId = (SELECT Id FROM dbo.ProductionLots WHERE PcsLotId = @PcsLotId)\\\\t\\\\t\\\\tIF (@ProductionLotAggregateId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 30: \'Production lot does not exist.\'", \'Comment 31: 1;\\\\t\\\\t\\\\tIF (SELECT BrokenBatchStatus FROM dbo.Batches WHERE Id = @ProductionLotAggregateId AND PcsBatchId = @PcsBatchId) = @ConstConfirmedBrokenBatchStatus\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 32: \'Cannot update batch report for confirmed broken batch\'", \'Comment 33: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND APLE.QuantityKg < 0\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 34: \'Production lot element quantity cannot be negative.\'", \'Comment 35: 1;\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tSET @RecipeAggregateId = (SELECT RecipeId FROM dbo.ProductionLots WHERE Id = @ProductionLotAggregateId)\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements RE ON APLE.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND APLE.RecipeElementId IS NOT NULL AND (RE.Id IS NULL OR RE.Id != @RecipeAggregateId)\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 36: \'Recipe element in report does not belong to recipe related to current production.\'", \'Comment 37: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND APLED.QuantityKg < 0\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 38: \'Production lot element delivery quantity cannot be negative.\'", \'Comment 39: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND APLED.Barcode IS NOT NULL AND SU.Id IS NULL\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 40: \'Some stock unit barcodes do not exist.\'", \'Comment 41: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\tJOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\t\\\\tJOIN dbo.Deliveries D ON APLED.DeliveryId = D.EntityId\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND D.Id != SU.DeliveryId\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 42: \'Barcode delivery in report does not match stock unit delivery.\'", \'Comment 43: 1;\\\\t\\\\t\\\\tIF (@IsBrokenBatch = 1 AND @ReworkItemId IS NOT NULL)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tSET @ReworkItemAggregateId = (SELECT Id FROM dbo.Items WHERE EntityId = @ReworkItemId)\\\\t\\\\t\\\\t\\\\tIF (@ReworkItemAggregateId IS NULL)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 44: \'Rework item does not exist.\'", \'Comment 45: 1;\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tSET @AllowStockRegisteringOnSilos = IIF((\\\\t\\\\t\\\\t\\\\tSELECT [Value]\\\\t\\\\t\\\\t\\\\tFROM dbo.Configuration\\\\t\\\\t\\\\t\\\\tWHERE [Key] = @ConstAllowStockRegisteringOnSilosKey) = @ConstAllowStockRegisteringOnSilosTrueValue,\\\\t\\\\t\\\\t\\\\t1,\\\\t\\\\t\\\\t\\\\t0)\\\\t\\\\t\\\\tIF (@AllowStockRegisteringOnSilos = 1)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND (APLED.DeliveryId IS NOT NULL OR APLED.Barcode IS NOT NULL) AND APLED.SiloCode IS NOT NULL\\\\t\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 46: \'Element delivery cannot specify both delivery and silo.\'", \'Comment 47: 1;\\\\t\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\t\\\\tJOIN dbo.FactoryObjects FO ON APLED.SiloCode = FO.PcsCode\\\\t\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND FO.ObjectType != @ConstFactoryObjectTypeDosingSilo\\\\t\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 48: \'Not all silos are of dosing silo type.\'", \'Comment 49: 1;\\\\t\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tJOIN dbo.FactoryObjects FO ON APLED.SiloCode = FO.PcsCode\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tJOIN dbo.Items I ON I.EntityId = APLE.ItemId\\\\t\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND (FO.ItemId IS NULL OR i.Id != FO.ItemId)\\\\t\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 50: \'Raw material on silo does not match to raw material on element.\'", \'Comment 51: 1;\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tIF (@StartBatchMixing IS NULL)\\\\t\\\\t\\\\t\\\\tSET @StartBatchMixing = GETDATE()\\\\t\\\\t\\\\tIF (@FinishBatchMixing IS NULL)\\\\t\\\\t\\\\t\\\\tSET @FinishBatchMixing = GETDATE()\\\\t\\\\t\\\\tIF (@StartBatchMixing > @FinishBatchMixing)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 52: \'Batch start date cannot be later than finish date.\'", \'Comment 53: 1;\\\\t\\\\tEND -- Validation\\\\t\\\\t\\\\t\\\\tDECLARE @EmptyGuid UNIQUEIDENTIFIER = (SELECT CAST(0x0 AS UNIQUEIDENTIFIER))\\\\t\\\\tDECLARE @ElementsMappings TABLE (ApiElementId BIGINT NOT NULL\', \'Comment 54: ExecutionNo INT\', \'Comment 55: ElementNo INT\', \'Comment 56: Ratio DECIMAL(16,6) NOT NULL)\\\\t\\\\tDECLARE @ElementDeliveries TABLE (Id INT NOT NULL\', \'Comment 57: DeliveryAggregateId UNIQUEIDENTIFIER NOT NULL\', \'Comment 58: StockUnitAggregateId UNIQUEIDENTIFIER\', \'Comment 59: QuantityKg DECIMAL(18,6) NOT NULL\', \'Comment 60: ElementNo INT NOT NULL\', \'Comment 61: TotalStockUnitConsumption BIT NOT NULL)\\\\t\\\\tDECLARE @ExecutionElementDeliveries TABLE (Id INT NOT NULL\', \'Comment 62: DeliveryAggregateId UNIQUEIDENTIFIER NOT NULL\', \'Comment 63: StockUnitAggregateId UNIQUEIDENTIFIER\', \'Comment 64: QuantityKg DECIMAL(18,6) NOT NULL\', \'Comment 65: ExecutionNo INT NOT NULL\', \'Comment 66: ElementNo INT NOT NULL)\\\\t\\\\tDECLARE @TmpDosings TABLE (ElementId INT NOT NULL\', \'Comment 67: DeliveryAggregateId UNIQUEIDENTIFIER\', \'Comment 68: StockUnitAggregateId UNIQUEIDENTIFIER\', \'Comment 69: SiloAggregateId UNIQUEIDENTIFIER\', \'Comment 70: QuantityKg DECIMAL(18,6))\\\\t\\\\tBEGIN TRANSACTION\\\\t\\\\tBEGIN -- Validation\\\\t\\\\t\\\\tDECLARE @ConstProductionStatusInProgress INT = 2\\\\t\\\\t\\\\tIF (SELECT Status FROM dbo.ProductionLots WHERE Id = @ProductionLotAggregateId) != @ConstProductionStatusInProgress\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 71: \'Production lot is finished.\'", \'Comment 72: 1;\\\\t\\\\t\\\\tIF (SELECT Type FROM dbo.Batches WHERE Id = @ProductionLotAggregateId AND PcsBatchId = @PcsBatchId) != @ConstBatchReportType\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 73: \'Invalid batch type.\'", \'Comment 74: 1;\\\\t\\\\tEND -- Validation\\\\t\\\\tBEGIN -- Production lot quantity update\\\\t\\\\t\\\\tUPDATE dbo.ProductionLots\\\\t\\\\t\\\\tSET Quantity += @QuantityKg\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId;\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\tSET Quantity += @QuantityKg\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = 1;\\\\t\\\\t\\\\tSELECT @SetRequestedQuantityBasedOnQuantity = IIF(EXISTS(\\\\t\\\\t\\\\t\\\\tSELECT 1\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLots\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\t\\\\tAND ProductionOrderId IS NULL\\\\t\\\\t\\\\t\\\\t\\\\tAND BatchSize IS NUll),\\\\t\\\\t\\\\t\\\\t1,\\\\t\\\\t\\\\t\\\\t0);\\\\t\\\\t\\\\tIF (@SetRequestedQuantityBasedOnQuantity = 1)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLots\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = Quantity\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId;\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = Quantity\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = 1;\\\\t\\\\t\\\\tEND\\\\t\\\\tEND -- Production lot quantity update\\\\t\\\\tDECLARE @BatchNo INT\\\\t\\\\tDECLARE @BatchElementNo INT\\\\t\\\\tDECLARE @EventName NVARCHAR(50)\\\\t\\\\tDECLARE @BrokenBatchStatus INT = IIF(ISNULL(@IsBrokenBatch\', \'Comment 75: @ConstUndefinedBrokenBatchStatus) = @ConstUndefinedBrokenBatchStatus,\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t @ConstUndefinedBrokenBatchStatus\', "Comment 76: @ConstCreatedBrokenBatchStatus)\\\\t\\\\tBEGIN -- Batch upsert\\\\t\\\\t\\\\tSET @BatchNo = (SELECT No FROM dbo.Batches WHERE Id = @ProductionLotAggregateId AND PcsBatchId = @PcsBatchId)\\\\t\\\\t\\\\tIF (@BatchNo IS NULL)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tSET @EventName = \'ProductionBatchReportRegisteredEvent\'\\\\t\\\\t\\\\t\\\\tSET @BatchNo = ISNULL((SELECT MAX(No) FROM dbo.Batches WHERE Id = @ProductionLotAggregateId)", \'Comment 77: 0) + 1\\\\t\\\\t\\\\t\\\\tINSERT INTO dbo.Batches (Id\', \'Comment 78: No\', \'Comment 79: PcsBatchId\', \'Comment 80: CreateDate\', \'Comment 81: StartDate\', \'Comment 82: FinishDate\', \'Comment 83: Quantity\', \'Comment 84: QuantityUnit\', \'Comment 85: Status,\\\\t\\\\t\\\\t\\\\t\\\\tBrokenBatchStatus\', \'Comment 86: ReworkItemId\', \'Comment 87: Type)\\\\t\\\\t\\\\t\\\\tVALUES (@ProductionLotAggregateId\', \'Comment 88: @BatchNo\', \'Comment 89: @PcsBatchId\', \'Comment 90: GETDATE()\', \'Comment 91: @StartBatchMixing\', \'Comment 92: @FinishBatchMixing\', \'Comment 93: @QuantityKg\', "Comment 94: \'kg\'", \'Comment 95: @ConstBatchStatusFinished,\\\\t\\\\t\\\\t\\\\t\\\\t@BrokenBatchStatus\', \'Comment 96: @ReworkItemAggregateId\', "Comment 97: @ConstBatchReportType)\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tELSE\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tSET @EventName = \'ProductionBatchReportUpdatedEvent\'\\\\t\\\\t\\\\t\\\\tUPDATE dbo.Batches\\\\t\\\\t\\\\t\\\\tSET Quantity += @QuantityKg,\\\\t\\\\t\\\\t\\\\t\\\\tStartDate = @StartBatchMixing,\\\\t\\\\t\\\\t\\\\t\\\\tFinishDate = @FinishBatchMixing,\\\\t\\\\t\\\\t\\\\t\\\\tReworkItemId = IIF(BrokenBatchStatus = @ConstCreatedBrokenBatchStatus", \'Comment 98: ReworkItemId\', \'Comment 99: @ReworkItemAggregateId),\\\\t\\\\t\\\\t\\\\t\\\\tBrokenBatchStatus = IIF(BrokenBatchStatus = @ConstUndefinedBrokenBatchStatus\', \'Comment 100: @BrokenBatchStatus\', \'Comment 101: BrokenBatchStatus)\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = @BatchNo\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tSET @BatchElementNo = ISNULL((SELECT MAX(No) FROM dbo.BatchElements WHERE Id = @ProductionLotAggregateId AND BatchNo = @BatchNo)\', \'Comment 102: 0) + 1\\\\t\\\\t\\\\tINSERT INTO dbo.BatchElements (Id\', \'Comment 103: BatchNo\', \'Comment 104: No\', \'Comment 105: CreateDate\', \'Comment 106: Quantity\', \'Comment 107: QuantityUnit)\\\\t\\\\t\\\\tVALUES (@ProductionLotAggregateId\', \'Comment 108: @BatchNo\', \'Comment 109: @BatchElementNo\', \'Comment 110: GETDATE()\', \'Comment 111: @QuantityKg\', "Comment 112: \'kg\')\\\\t\\\\tEND -- Batch upsert\\\\t\\\\tINSERT INTO @ElementsMappings (ApiElementId", \'Comment 113: ExecutionNo\', \'Comment 114: ElementNo\', \'Comment 115: Ratio)\\\\t\\\\tSELECT ApiElementId\', \'Comment 116: ExecutionNo\', \'Comment 117: ElementNo\', \'Comment 118: Ratio\\\\t\\\\tFROM dbo.GetProductionElementsMappings(@ProductionLotAggregateId\', \'Comment 119: @PcsLotId\', \'Comment 120: @PcsBatchId)\\\\t\\\\tBEGIN -- Production lot elements upsert\\\\t\\\\t\\\\t;WITH AggregatedElementsCTE (ElementNo\', \'Comment 121: QuantityKg) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT M.ElementNo\', \'Comment 122: SUM(APLE.QuantityKg * M.Ratio)\\\\t\\\\t\\\\t\\\\tFROM @ElementsMappings M\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElements APLE ON M.ApiElementId = APLE.Id\\\\t\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL\\\\t\\\\t\\\\t\\\\tGROUP BY M.ElementNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tUPDATE PLE\\\\t\\\\t\\\\tSET Quantity += C.QuantityKg\\\\t\\\\t\\\\tFROM AggregatedElementsCTE C\\\\t\\\\t\\\\tJOIN dbo.ProductionLotElements PLE ON PLE.Id = @ProductionLotAggregateId AND C.ElementNo = PLE.No\\\\t\\\\t\\\\tDECLARE @ElementMaxNo INT = (SELECT MAX(No) FROM dbo.ProductionLotElements WHERE Id = @ProductionLotAggregateId)\\\\t\\\\t\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotElements (Id\', \'Comment 123: No\', \'Comment 124: ItemId\', \'Comment 125: Quantity\', \'Comment 126: QuantityUnit\', \'Comment 127: RequestedQuantity\', \'Comment 128: RequestedQuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 129: @ElementMaxNo + ROW_NUMBER() OVER (ORDER BY MIN(APLE.Id))\', \'Comment 130: I.Id\', \'Comment 131: SUM(APLE.QuantityKg * M.Ratio)\', "Comment 132: \'kg\'", \'Comment 133: 0\', "Comment 134: \'kg\'\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLE.Id = M.ApiElementId\\\\t\\\\t\\\\tJOIN dbo.Items I ON APLE.ItemId = I.EntityId\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND M.ElementNo IS NULL\\\\t\\\\t\\\\tGROUP BY I.Id\\\\t\\\\t\\\\tUPDATE M\\\\t\\\\t\\\\tSET ElementNo = PLE.No\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN dbo.Items I ON APLE.ItemId = I.EntityId\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLE.Id = M.ApiElementId\\\\t\\\\t\\\\tJOIN dbo.ProductionLotElements PLE ON PLE.Id = @ProductionLotAggregateId AND I.Id = PLE.ItemId\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND M.ElementNo IS NULL\\\\t\\\\tEND -- Production lot elements upsert\\\\t\\\\tBEGIN -- Production lot element deliveries upsert\\\\t\\\\t\\\\tINSERT INTO @ElementDeliveries (Id", \'Comment 135: DeliveryAggregateId\', \'Comment 136: StockUnitAggregateId\', \'Comment 137: QuantityKg\', \'Comment 138: ElementNo\', \'Comment 139: TotalStockUnitConsumption)\\\\t\\\\t\\\\tSELECT MIN(APLED.Id)\', \'Comment 140: ISNULL(SU.DeliveryId\', \'Comment 141: D.Id)\', \'Comment 142: SU.Id\', \'Comment 143: SUM(APLED.QuantityKg * M.Ratio)\', \'Comment 144: M.ElementNo\', \'Comment 145: IIF(SU.Id IS NULL,0,APLED.TotalBarcodeConsumption)\\\\t\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\t\\\\tLEFT JOIN dbo.Deliveries D ON APLED.DeliveryId = D.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND ISNULL(SU.DeliveryId\', \'Comment 146: D.Id) IS NOT NULL\\\\t\\\\t\\\\tGROUP BY SU.DeliveryId\', \'Comment 147: D.Id\', \'Comment 148: SU.Id\', \'Comment 149: M.ElementNo\', \'Comment 150: APLED.TotalBarcodeConsumption\\\\t\\\\t\\\\tUPDATE PLED\\\\t\\\\t\\\\tSET PLED.Quantity += ED.QuantityKg,\\\\t\\\\t\\\\t\\\\tPLED.TotalStockUnitConsumption |= ED.TotalStockUnitConsumption\\\\t\\\\t\\\\tFROM @ElementDeliveries ED\\\\t\\\\t\\\\tJOIN dbo.ProductionLotElementDeliveries PLED ON PLED.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tAND PLED.ElementNo = ED.ElementNo\\\\t\\\\t\\\\t\\\\tAND PLED.DeliveryId = ED.DeliveryAggregateId\\\\t\\\\t\\\\t\\\\tAND ISNULL(PLED.StockUnitId,@EmptyGuid) = ISNULL(ED.StockUnitAggregateId,@EmptyGuid)\\\\t\\\\t\\\\t;WITH DeliveryMaxNoCTE (ElementNo\', \'Comment 151: DeliveryMaxNo) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT ElementNo\', \'Comment 152: MAX(No)\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotElementDeliveries\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tGROUP BY ElementNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotElementDeliveries (Id\', \'Comment 153: ElementNo\', \'Comment 154: No\', \'Comment 155: DeliveryId\', \'Comment 156: StockUnitId\', \'Comment 157: Quantity\', \'Comment 158: QuantityUnit\', \'Comment 159: TotalStockUnitConsumption)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 160: ED.ElementNo\', \'Comment 161: ISNULL(C.DeliveryMaxNo,0) + ROW_NUMBER() OVER (PARTITION BY ED.ElementNo ORDER BY ED.Id),\\\\t\\\\t\\\\t\\\\tED.DeliveryAggregateId\', \'Comment 162: ED.StockUnitAggregateId\', \'Comment 163: ED.QuantityKg\', "Comment 164: \'kg\'", \'Comment 165: ED.TotalStockUnitConsumption\\\\t\\\\t\\\\tFROM @ElementDeliveries ED\\\\t\\\\t\\\\tLEFT JOIN DeliveryMaxNoCTE C ON C.ElementNo = ED.ElementNo\\\\t\\\\t\\\\tWHERE NOT EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT * FROM dbo.ProductionLotElementDeliveries PLED\\\\t\\\\t\\\\t\\\\tWHERE PLED.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\t\\\\tAND PLED.ElementNo = ED.ElementNo\\\\t\\\\t\\\\t\\\\t\\\\tAND PLED.DeliveryId = ED.DeliveryAggregateId\\\\t\\\\t\\\\t\\\\t\\\\tAND ISNULL(PLED.StockUnitId,@EmptyGuid) = ISNULL(ED.StockUnitAggregateId,@EmptyGuid))\\\\t\\\\tEND -- Production lot element deliveries upsert\\\\t\\\\tBEGIN -- Dosings insert\\\\t\\\\t\\\\tINSERT INTO @TmpDosings (ElementId\', \'Comment 166: DeliveryAggregateId\', \'Comment 167: StockUnitAggregateId\', \'Comment 168: SiloAggregateId\', \'Comment 169: QuantityKg)\\\\t\\\\t\\\\tSELECT M.ElementNo\', \'Comment 170: ISNULL(SU.DeliveryId\', \'Comment 171: D.Id)\', \'Comment 172: SU.Id\', \'Comment 173: IIF(@AllowStockRegisteringOnSilos = 1,FO.Id,NULL)\', \'Comment 174: APLED.QuantityKg * M.Ratio\\\\t\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\t\\\\tLEFT JOIN dbo.Deliveries D ON APLED.DeliveryId = D.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\tLEFT JOIN dbo.FactoryObjects FO ON APLED.SiloCode = FO.PcsCode\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND COALESCE(SU.DeliveryId\', \'Comment 175: D.Id\', \'Comment 176: IIF(@AllowStockRegisteringOnSilos = 1,FO.Id,NULL)) IS NOT NULL\\\\t\\\\t\\\\t;WITH ElementDeliveryQuantitySumCTE (ElementId\', \'Comment 177: QuantityKg) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT ElementId\', \'Comment 178: SUM(QuantityKg)\\\\t\\\\t\\\\t\\\\tFROM @TmpDosings\\\\t\\\\t\\\\t\\\\tGROUP BY ElementId\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tINSERT INTO @TmpDosings (ElementId\', \'Comment 179: DeliveryAggregateId\', \'Comment 180: StockUnitAggregateId\', \'Comment 181: SiloAggregateId\', \'Comment 182: QuantityKg)\\\\t\\\\t\\\\tSELECT M.ElementNo\', \'Comment 183: NULL\', \'Comment 184: NULL\', \'Comment 185: NULL\', \'Comment 186: APLE.QuantityKg * M.Ratio - ISNULL(C.QuantityKg\', \'Comment 187: 0)\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLE.Id = M.ApiElementId\\\\t\\\\t\\\\tLEFT JOIN ElementDeliveryQuantitySumCTE C ON C.ElementId = M.ElementNo\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND APLE.QuantityKg * M.Ratio > ISNULL(C.QuantityKg\', \'Comment 188: 0)\\\\t\\\\t\\\\tDECLARE @DosingMaxNo INT = ISNULL((SELECT MAX(No) FROM dbo.Dosings WHERE Id = @ProductionLotAggregateId),0)\\\\t\\\\t\\\\t\\\\t\\\\tINSERT INTO dbo.Dosings (Id\', \'Comment 189: No\', \'Comment 190: BatchNo\', \'Comment 191: BatchElementNo\', \'Comment 192: ElementNo\', \'Comment 193: Quantity\', \'Comment 194: QuantityUnit\', \'Comment 195: Date\', \'Comment 196: DeliveryId\', \'Comment 197: StockUnitId\', \'Comment 198: SiloId)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId,\\\\t\\\\t\\\\t\\\\t@DosingMaxNo + ROW_NUMBER() OVER (ORDER BY TD.ElementId\', \'Comment 199: TD.DeliveryAggregateId\', \'Comment 200: TD.StockUnitAggregateId\', \'Comment 201: TD.SiloAggregateId),\\\\t\\\\t\\\\t\\\\t@BatchNo\', \'Comment 202: @BatchElementNo\', \'Comment 203: TD.ElementId\', \'Comment 204: TD.QuantityKg\', "Comment 205: \'kg\'", \'Comment 206: GETDATE()\', \'Comment 207: TD.DeliveryAggregateId\', \'Comment 208: TD.StockUnitAggregateId\', \'Comment 209: TD.SiloAggregateId\\\\t\\\\t\\\\tFROM @TmpDosings TD\\\\t\\\\tEND -- Dosings insert\\\\t\\\\tBEGIN -- Production lot execution elements upsert\\\\t\\\\t\\\\t;WITH AggregatedExecutionElementsCTE (ExecutionNo\', \'Comment 210: ElementNo\', \'Comment 211: QuantityKg) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT M.ExecutionNo\', \'Comment 212: M.ElementNo\', \'Comment 213: SUM(APLE.QuantityKg * M.Ratio)\\\\t\\\\t\\\\t\\\\tFROM @ElementsMappings M\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElements APLE ON M.ApiElementId = APLE.Id\\\\t\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL\\\\t\\\\t\\\\t\\\\tGROUP BY M.ExecutionNo\', \'Comment 214: M.ElementNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tUPDATE EE\\\\t\\\\t\\\\tSET Quantity += C.QuantityKg\\\\t\\\\t\\\\tFROM AggregatedExecutionElementsCTE C\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements EE ON EE.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tAND EE.ExecutionNo = C.ExecutionNo AND EE.No = C.ElementNo\\\\t\\\\t\\\\t;WITH ExecutionElementMaxNoCTE (ExecutionNo\', \'Comment 215: ElementMaxNo) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT ExecutionNo\', \'Comment 216: MAX(No)\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElements\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tGROUP BY ExecutionNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElements (Id\', \'Comment 217: ExecutionNo\', \'Comment 218: No,\\\\t\\\\t\\\\t\\\\tItemId\', \'Comment 219: Quantity\', \'Comment 220: QuantityUnit\', \'Comment 221: RequestedQuantity\', \'Comment 222: RequestedQuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 223: M.ExecutionNo\', \'Comment 224: ISNULL(C.ElementMaxNo,0) + ROW_NUMBER() OVER (PARTITION BY M.ExecutionNo ORDER BY MIN(APLE.Id)),\\\\t\\\\t\\\\t\\\\tI.Id\', \'Comment 225: SUM(APLE.QuantityKg * M.Ratio)\', \'Comment 226: I.ItemBaseWeightUnit\', \'Comment 227: 0\', \'Comment 228: I.ItemBaseWeightUnit\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLE.Id = M.ApiElementId\\\\t\\\\t\\\\tJOIN dbo.Items I ON APLE.ItemId = I.EntityId\\\\t\\\\t\\\\tLEFT JOIN ExecutionElementMaxNoCTE C ON M.ExecutionNo = C.ExecutionNo\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND M.ElementNo IS NULL\\\\t\\\\t\\\\tGROUP BY M.ExecutionNo\', \'Comment 229: C.ElementMaxNo\', \'Comment 230: I.Id\', \'Comment 231: I.ItemBaseWeightUnit\\\\t\\\\t\\\\tUPDATE M\\\\t\\\\t\\\\tSET ElementNo = EE.No\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN dbo.Items I ON APLE.ItemId = I.EntityId\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLE.Id = M.ApiElementId\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements EE ON EE.Id = @ProductionLotAggregateId AND EE.ExecutionNo = M.ExecutionNo AND EE.ItemId = I.Id\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND M.ElementNo IS NULL\\\\t\\\\tEND -- Production lot execution elements upsert\\\\t\\\\tBEGIN -- Production lot execution element deliveries upsert\\\\t\\\\t\\\\tINSERT INTO @ExecutionElementDeliveries(Id\', \'Comment 232: DeliveryAggregateId\', \'Comment 233: StockUnitAggregateId\', \'Comment 234: QuantityKg\', \'Comment 235: ExecutionNo\', \'Comment 236: ElementNo)\\\\t\\\\t\\\\tSELECT MIN(APLED.Id)\', \'Comment 237: ISNULL(SU.DeliveryId\', \'Comment 238: D.Id)\', \'Comment 239: SU.Id\', \'Comment 240: SUM(APLED.QuantityKg * M.Ratio)\', \'Comment 241: M.ExecutionNo\', \'Comment 242: M.ElementNo\\\\t\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\t\\\\tLEFT JOIN dbo.Deliveries D ON APLED.DeliveryId = D.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND ISNULL(SU.DeliveryId\', \'Comment 243: D.Id) IS NOT NULL\\\\t\\\\t\\\\tGROUP BY SU.DeliveryId\', \'Comment 244: D.Id\', \'Comment 245: SU.Id\', \'Comment 246: M.ExecutionNo\', \'Comment 247: M.ElementNo\\\\t\\\\t\\\\tUPDATE PLEED\\\\t\\\\t\\\\tSET Quantity += EED.QuantityKg\\\\t\\\\t\\\\tFROM @ExecutionElementDeliveries EED\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElementDeliveries PLEED ON PLEED.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tAND PLEED.ExecutionNo = EED.ExecutionNo AND PLEED.ElementNo = EED.ElementNo AND PLEED.DeliveryId = EED.DeliveryAggregateId\\\\t\\\\t\\\\t\\\\tAND ISNULL(PLEED.StockUnitId,@EmptyGuid) = ISNULL(EED.StockUnitAggregateId,@EmptyGuid)\\\\t\\\\t\\\\t;WITH DeliveryMaxNoCTE (ExecutionNo\', \'Comment 248: ElementNo\', \'Comment 249: DeliveryMaxNo) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT ExecutionNo\', \'Comment 250: ElementNo\', \'Comment 251: MAX(No)\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElementDeliveries\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tGROUP BY ExecutionNo\', \'Comment 252: ElementNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElementDeliveries (Id\', \'Comment 253: ExecutionNo\', \'Comment 254: ElementNo\', \'Comment 255: No\', \'Comment 256: DeliveryId\', \'Comment 257: StockUnitId\', \'Comment 258: Quantity\', \'Comment 259: QuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 260: EED.ExecutionNo\', \'Comment 261: EED.ElementNo,\\\\t\\\\t\\\\t\\\\tISNULL(C.DeliveryMaxNo,0) + ROW_NUMBER() OVER (PARTITION BY EED.ExecutionNo\', \'Comment 262: EED.ElementNo ORDER BY EED.Id),\\\\t\\\\t\\\\t\\\\tEED.DeliveryAggregateId\', \'Comment 263: EED.StockUnitAggregateId\', \'Comment 264: EED.QuantityKg\', "Comment 265: \'kg\'\\\\t\\\\t\\\\tFROM @ExecutionElementDeliveries EED\\\\t\\\\t\\\\tLEFT JOIN DeliveryMaxNoCTE C ON EED.ExecutionNo = C.ExecutionNo AND EED.ElementNo = C.ElementNo\\\\t\\\\t\\\\tWHERE NOT EXISTS (SELECT * FROM dbo.ProductionLotExecutionElementDeliveries PLEED\\\\t\\\\t\\\\t\\\\tWHERE PLEED.Id = @ProductionLotAggregateId AND PLEED.ExecutionNo = EED.ExecutionNo AND PLEED.ElementNo = EED.ElementNo\\\\t\\\\t\\\\t\\\\t\\\\tAND PLEED.DeliveryId = EED.DeliveryAggregateId AND ISNULL(PLEED.StockUnitId,@EmptyGuid) = ISNULL(EED.StockUnitAggregateId,@EmptyGuid))\\\\t\\\\tEND -- Production lot execution element deliveries upsert\\\\t\\\\tBEGIN -- Clean up\\\\t\\\\t\\\\tDELETE APLED\\\\t\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\t\\\\tJOIN api.ProductionLotElements APLE ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId\\\\t\\\\t\\\\tDELETE FROM api.ProductionLotElements\\\\t\\\\t\\\\tWHERE PcsLotId = @PcsLotId AND PcsBatchId = @PcsBatchId\\\\t\\\\tEND -- Clean up\\\\t\\\\tINSERT INTO dbo.PcsIntegrationEvents (EventType", \'Comment 266: AggregateId\', "Comment 267: ElementNo)\\\\t\\\\tVALUES (\'Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.\' + @EventName", \'Comment 268: @ProductionLotAggregateId\', \'Comment 269: @BatchNo)\\\\t\\\\t\\\\t\\\\tCOMMIT\\\\t\\\\tEXEC dbo.AcceptSqlApiRequest @RequestLogId\\\\tEND TRY\\\\tBEGIN CATCH\\\\t\\\\tIF (@@TRANCOUNT > 0)\\\\t\\\\t\\\\tROLLBACK;\\\\t\\\\tDECLARE @ErrorMessage NVARCHAR(4000) = ERROR_MESSAGE()\\\\t\\\\tEXEC dbo.RejectSqlApiRequest @RequestLogId\', \'Comment 270: @ErrorMessage;\\\\t\\\\tDELETE APLED\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\tJOIN api.ProductionLotElements APLE ON APLE.Id = APLED.ElementId\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId\\\\t\\\\tDELETE FROM api.ProductionLotElements\\\\t\\\\tWHERE PcsLotId = @PcsLotId AND PcsBatchId = @PcsBatchId;\\\\t\\\\t\\\\t\\\\tTHROW\\\\tEND CATCHENDGO{code}"\', \'Comment 271: "*api.RegisterExecutionReport*:{code:sql}CREATE OR ALTER PROCEDURE api.RegisterExecutionReport(\\\\t@PcsLotId BIGINT,\\\\t@ItemId INT,\\\\t@PackingRecipeId INT,\\\\t@QuantityKg DECIMAL(18,6))ASBEGIN\\\\tSET NOCOUNT ON;\\\\tBEGIN TRY\\\\t\\\\tBEGIN -- Logger\\\\t\\\\t\\\\tDECLARE @Parameters NVARCHAR(MAX) = (\\\\t\\\\t\\\\t\\\\tSELECT\\\\t\\\\t\\\\t\\\\t\\\\t@PcsLotId AS PcsLotId,\\\\t\\\\t\\\\t\\\\t\\\\t@ItemId AS ItemId,\\\\t\\\\t\\\\t\\\\t\\\\t@PackingRecipeId AS PackingRecipeId,\\\\t\\\\t\\\\t\\\\t\\\\t@QuantityKg AS QuantityKg,\\\\t\\\\t\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tSELECT E.Id\', \'Comment 272: E.PcsLotId\', \'Comment 273: E.ReadyProductId\', \'Comment 274: E.PackingItemId\', \'Comment 275: E.RecipeElementId\', \'Comment 276: E.Quantity,\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tSELECT D.Id\', \'Comment 277: D.ElementId\', \'Comment 278: D.DeliveryId\', \'Comment 279: D.Quantity\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElementDeliveries D\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tWHERE D.ElementId = E.Id\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFOR JSON AUTO\', \'Comment 280: INCLUDE_NULL_VALUES\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t) As Deliveries\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFOR JSON AUTO\', \'Comment 281: INCLUDE_NULL_VALUES\\\\t\\\\t\\\\t\\\\t\\\\t) AS Elements\\\\t\\\\t\\\\t\\\\tFOR JSON PATH\', \'Comment 282: INCLUDE_NULL_VALUES\', "Comment 283: WITHOUT_ARRAY_WRAPPER)\\\\t\\\\t\\\\tDECLARE @RequestLogId BIGINT\\\\t\\\\t\\\\tEXEC dbo.SaveSqlApiRequest \'RegisterExecutionReport\'", \'Comment 284: @Parameters\', \'Comment 285: @RequestLogId OUTPUT\\\\t\\\\tEND\\\\t\\\\t\\\\t\\\\tBEGIN -- Validation\\\\t\\\\t\\\\tIF (@PcsLotId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 286: \'Parameter @PcsLotId cannot be null.\'", \'Comment 287: 1;\\\\t\\\\t\\\\tIF (@ItemId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 288: \'Parameter @ItemId cannot be null.\'", \'Comment 289: 1;\\\\t\\\\t\\\\tIF (ISNULL(@QuantityKg\', \'Comment 290: 0) <= 0)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 291: \'Parameter @QuantityKg cannot be null and must be greater than zero.\'", \'Comment 292: 1;\\\\t\\\\t\\\\tDECLARE @ProductionLotAggregateId UNIQUEIDENTIFIER = (SELECT Id FROM dbo.ProductionLots WHERE PcsLotId = @PcsLotId)\\\\t\\\\t\\\\tIF (@ProductionLotAggregateId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 293: \'Production lot does not exist.\'", \'Comment 294: 1;\\\\t\\\\t\\\\tDECLARE @ItemAggregateId UNIQUEIDENTIFIER = (SELECT Id FROM dbo.Items WHERE EntityId = @ItemId)\\\\t\\\\t\\\\tIF (@ItemAggregateId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 295: \'Item does not exist.\'", \'Comment 296: 1;\\\\t\\\\t\\\\tDECLARE @PackingRecipeAggregateId UNIQUEIDENTIFIER =\\\\t\\\\t\\\\t\\\\tCASE WHEN @PackingRecipeId IS NOT NULL THEN\\\\t\\\\t\\\\t\\\\t\\\\t(SELECT Id FROM dbo.Recipes WHERE EntityId = @PackingRecipeId)\\\\t\\\\t\\\\t\\\\tELSE\\\\t\\\\t\\\\t\\\\t\\\\t(SELECT TOP 1 Id FROM dbo.Recipes WHERE ItemId = @ItemAggregateId AND Version = 0 ORDER BY Subversion DESC\', \'Comment 297: CreateDate DESC)\\\\t\\\\t\\\\t\\\\tEND;\\\\t\\\\t\\\\tIF (@PackingRecipeAggregateId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 298: \'Packing recipe does not exist.\'", \'Comment 299: 1;\\\\t\\\\t\\\\tIF (@PackingRecipeId IS NOT NULL)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tIF ((SELECT ItemId FROM dbo.Recipes WHERE Id = @PackingRecipeAggregateId) != @ItemAggregateId)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 300: \'Selected recipe is incompatible with execution\'\'s ready product.\'", \'Comment 301: 1;\\\\t\\\\t\\\\t\\\\tIF ((SELECT Version FROM dbo.Recipes WHERE Id = @PackingRecipeAggregateId) != 0)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 302: \'Selected recipe is not packing recipe.\'", \'Comment 303: 1;\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tDECLARE @ReadyProductAggregateId UNIQUEIDENTIFIER\\\\t\\\\t\\\\tDECLARE @ProductionLotStatus INT\\\\t\\\\t\\\\tSELECT\\\\t\\\\t\\\\t\\\\t@ReadyProductAggregateId = ReadyProductId,\\\\t\\\\t\\\\t\\\\t@ProductionLotStatus = Status\\\\t\\\\t\\\\tFROM dbo.ProductionLots\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\tIF (@ReadyProductAggregateId = @ItemAggregateId)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 304: \'Cannot register execution report for production lot\'\'s ready product.\'", \'Comment 305: 1;\\\\t\\\\t\\\\tDECLARE @ConstInProgressLotStatus INT = 2\\\\t\\\\t\\\\tDECLARE @ConstFinishedLotStatus INT = 3\\\\t\\\\t\\\\tIF (@ProductionLotStatus NOT IN (@ConstInProgressLotStatus\', \'Comment 306: @ConstFinishedLotStatus))\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 307: \'Cannot register execution report because production lot is not in progress or finished.\'", \'Comment 308: 1;\\\\t\\\\t\\\\tDECLARE @IsItemBulkProductValid BIT = (\\\\t\\\\t\\\\t\\\\tSELECT IIF(ISNULL(I1.BulkProductId\', \'Comment 309: I1.Id) = ISNULL(I2.BulkProductId\', \'Comment 310: I2.Id)\', \'Comment 311: 1\', \'Comment 312: 0)\\\\t\\\\t\\\\t\\\\tFROM dbo.Items I1\\\\t\\\\t\\\\t\\\\tJOIN dbo.Items I2 ON I1.Id = @ReadyProductAggregateId AND I2.Id = @ItemAggregateId)\\\\t\\\\t\\\\t\\\\t\\\\tIF (@IsItemBulkProductValid = 0)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 313: \'Item\'\'s bulk product is incompatible with production lot\'\'s ready product.\'", \'Comment 314: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.Quantity < 0\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 315: \'Production lot execution element quantity cannot be negative.\'", \'Comment 316: 1;\\\\t\\\\t\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements RE ON E.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId AND E.RecipeElementId IS NOT NULL\\\\t\\\\t\\\\t\\\\t\\\\tAND (RE.Id IS NULL OR RE.Id != @PackingRecipeAggregateId)\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 317: \'Recipe element in report does not belong to recipe related to current execution.\'", \'Comment 318: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\t\\\\tJOIN dbo.Items I ON E.PackingItemId = I.EntityId\\\\t\\\\t\\\\t\\\\tJOIN dbo.RecipeElements RE ON E.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId AND I.Id != RE.ItemId\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 319: \'Recipe element in report does not match article in report.\'", \'Comment 320: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotExecutionElementDeliveries AD ON E.Id = AD.ElementId\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND AD.Quantity < 0\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 321: \'Production lot execution element delivery quantity cannot be negative.\'", \'Comment 322: 1;\\\\t\\\\t\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElementDeliveries AD\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotExecutionElements E ON AD.ElementId = E.Id\\\\t\\\\t\\\\t\\\\tJOIN dbo.Items I ON E.PackingItemId = I.EntityId\\\\t\\\\t\\\\t\\\\tJOIN dbo.Deliveries D ON AD.DeliveryId = D.EntityId\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId AND D.ItemId != I.Id\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', "Comment 323: \'ItemId of selected delivery does not match packing item.\'", \'Comment 324: 1;\\\\t\\\\tEND\\\\t\\\\tDECLARE @ConstExecutionRegisteredPcsEventSyncStateFlag INT = 1\\\\t\\\\tDECLARE @ConstItemTypePackage INT = 3\\\\t\\\\tDECLARE @ChangesOccurred BIT = 0\\\\t\\\\tBEGIN TRANSACTION\\\\t\\\\tDECLARE @ExecutionLotReportNo INT = (SELECT No FROM dbo.ProductionLotExecutions WHERE Id = @ProductionLotAggregateId AND ReadyProductId = @ItemAggregateId)\\\\t\\\\tDECLARE @DefaultExecutionRequestedQuantityKg DECIMAL(18,6) = (SELECT RequestedQuantity FROM dbo.ProductionLotExecutions WHERE Id = @ProductionLotAggregateId AND No = 1)\\\\t\\\\tDECLARE @NewDefaultExecutionRequestedQuantityKg DECIMAL(18,6) = @DefaultExecutionRequestedQuantityKg\\\\t\\\\t\\\\t\\\\tIF (@ExecutionLotReportNo IS NULL) -- Execution\\\\t\\\\tBEGIN\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\t\\\\tSET @ExecutionLotReportNo = ISNULL((SELECT MAX(No) FROM dbo.ProductionLotExecutions WHERE Id = @ProductionLotAggregateId)\', \'Comment 325: 0) + 1\\\\t\\\\t\\\\tSET @NewDefaultExecutionRequestedQuantityKg = @DefaultExecutionRequestedQuantityKg - @QuantityKg\\\\t\\\\t\\\\tDECLARE @BagPackingForm TINYINT = 2\\\\t\\\\t\\\\tDECLARE @BigBagPackingForm TINYINT = 3\\\\t\\\\t\\\\tDECLARE @IsBaggingFinished BIT = CASE \\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t WHEN ((SELECT PackingForm FROM dbo.Items I WHERE @ItemAggregateId = I.Id) IN (@BagPackingForm\', \'Comment 326: @BigBagPackingForm))\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t THEN 0\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t ELSE null\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t END;\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutions (Id\', \'Comment 327: No\', \'Comment 328: ReadyProductId\', \'Comment 329: Quantity\', \'Comment 330: QuantityUnit\', \'Comment 331: RequestedQuantity\', \'Comment 332: RequestedQuantityUnit,\\\\t\\\\t\\\\t\\\\tPcsEventSyncState\', \'Comment 333: PackingRecipeId\', \'Comment 334: IsBaggingFinished)\\\\t\\\\t\\\\tVALUES (@ProductionLotAggregateId\', \'Comment 335: @ExecutionLotReportNo\', \'Comment 336: @ItemAggregateId\', \'Comment 337: 0\', "Comment 338: \'kg\'", \'Comment 339: @QuantityKg\', "Comment 340: \'kg\',\\\\t\\\\t\\\\t\\\\t@ConstExecutionRegisteredPcsEventSyncStateFlag", \'Comment 341: @PackingRecipeAggregateId\', \'Comment 342: @IsBaggingFinished)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElements (Id\', \'Comment 343: ExecutionNo\', \'Comment 344: No\', \'Comment 345: ItemId,\\\\t\\\\t\\\\t\\\\tRecipeId\', \'Comment 346: RecipeElementId\', \'Comment 347: Quantity\', \'Comment 348: QuantityUnit\', \'Comment 349: RequestedQuantity\', \'Comment 350: RequestedQuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 351: @ExecutionLotReportNo\', \'Comment 352: ROW_NUMBER() OVER (ORDER BY RE.No)\', \'Comment 353: RE.ItemId,\\\\t\\\\t\\\\t\\\\tRE.Id\', \'Comment 354: RE.No\', \'Comment 355: 0\', \'Comment 356: RE.QuantityUnit\', \'Comment 357: 0\', \'Comment 358: RE.QuantityUnit\\\\t\\\\t\\\\tFROM dbo.RecipeElements RE\\\\t\\\\t\\\\tJOIN dbo.Items I ON RE.ItemId = I.Id\\\\t\\\\t\\\\tWHERE RE.Id = @PackingRecipeAggregateId AND I.ItemType = @ConstItemTypePackage\\\\t\\\\tEND\\\\t\\\\tELSE\\\\t\\\\tBEGIN\\\\t\\\\t\\\\tDECLARE @CurrentExecutionLotReportRequestedQuantityKg DECIMAL(18,6) = (\\\\t\\\\t\\\\t\\\\tSELECT RequestedQuantity FROM dbo.ProductionLotExecutions WHERE Id = @ProductionLotAggregateId AND No = @ExecutionLotReportNo)\\\\t\\\\t\\\\tIF (@CurrentExecutionLotReportRequestedQuantityKg <> @QuantityKg)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\t\\\\t\\\\tSET @NewDefaultExecutionRequestedQuantityKg = @DefaultExecutionRequestedQuantityKg - (@QuantityKg - @CurrentExecutionLotReportRequestedQuantityKg)\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = @QuantityKg\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = @ExecutionLotReportNo\\\\t\\\\t\\\\tEND\\\\t\\\\tEND\\\\t\\\\tIF (@DefaultExecutionRequestedQuantityKg <> @NewDefaultExecutionRequestedQuantityKg)\\\\t\\\\tBEGIN\\\\t\\\\t\\\\tIF (@NewDefaultExecutionRequestedQuantityKg >= 0)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = @NewDefaultExecutionRequestedQuantityKg\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = 1\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tELSE\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLots\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = RequestedQuantity - @NewDefaultExecutionRequestedQuantityKg\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = 0\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = 1\\\\t\\\\t\\\\tEND\\\\t\\\\tEND\\\\t\\\\tBEGIN -- Execution elements\\\\t\\\\t\\\\tUPDATE T\\\\t\\\\t\\\\tSET T.Quantity = E.Quantity\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\tJOIN dbo.Items I ON E.PackingItemId = I.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements RE ON E.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements T ON T.Id = @ProductionLotAggregateId AND T.ExecutionNo = @ExecutionLotReportNo\\\\t\\\\t\\\\t\\\\tAND T.ItemId = I.Id AND ISNULL(T.RecipeElementId,0) = ISNULL(RE.No,0)\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId AND T.Quantity != E.Quantity\\\\t\\\\t\\\\tIF (@@ROWCOUNT > 0)\\\\t\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\t\\\\tDECLARE @CurrentMaxElementNo INT = ISNULL((SELECT MAX(No) FROM dbo.ProductionLotExecutionElements\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND ExecutionNo = @ExecutionLotReportNo)\', \'Comment 359: 0)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElements (Id\', \'Comment 360: ExecutionNo\', \'Comment 361: No,\\\\t\\\\t\\\\t\\\\tItemId\', \'Comment 362: RecipeId\', \'Comment 363: RecipeElementId\', \'Comment 364: Quantity\', \'Comment 365: QuantityUnit\', \'Comment 366: RequestedQuantity\', \'Comment 367: RequestedQuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 368: @ExecutionLotReportNo\', \'Comment 369: @CurrentMaxElementNo + ROW_NUMBER() OVER (ORDER BY E.Id),\\\\t\\\\t\\\\t\\\\tI.Id\', \'Comment 370: RE.Id\', \'Comment 371: RE.No\', \'Comment 372: E.Quantity\', \'Comment 373: I.ItemBaseWeightUnit\', \'Comment 374: 0\', \'Comment 375: I.ItemBaseWeightUnit\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\tJOIN dbo.Items I ON E.PackingItemId = I.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements RE ON E.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId AND I.ItemType = @ConstItemTypePackage AND NOT EXISTS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElements T\\\\t\\\\t\\\\t\\\\tWHERE T.Id = @ProductionLotAggregateId AND T.ExecutionNo = @ExecutionLotReportNo\\\\t\\\\t\\\\t\\\\t\\\\tAND T.ItemId = I.Id AND ISNULL(T.RecipeElementId,0) = ISNULL(RE.No,0)\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tIF (@@ROWCOUNT > 0)\\\\t\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\tEND\\\\t\\\\tBEGIN -- Execution element deliveries\\\\t\\\\t\\\\tDECLARE @TmpDeliveries TABLE (Id BIGINT NOT NULL\', \'Comment 376: ElementNo INT NOT NULL\', \'Comment 377: DeliveryId UNIQUEIDENTIFIER NOT NULL,\\\\t\\\\t\\\\t\\\\tQuantity DECIMAL(18,6) NOT NULL\', \'Comment 378: Unit NVARCHAR(10) NOT NULL)\\\\t\\\\t\\\\tINSERT INTO @TmpDeliveries (Id\', \'Comment 379: ElementNo\', \'Comment 380: DeliveryId\', \'Comment 381: Quantity\', \'Comment 382: Unit)\\\\t\\\\t\\\\tSELECT MIN(APLEED.Id)\', \'Comment 383: PLEE.No\', \'Comment 384: D.Id\', \'Comment 385: SUM(APLEED.Quantity)\', \'Comment 386: I.ItemBaseWeightUnit\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElementDeliveries APLEED\\\\t\\\\t\\\\tJOIN api.ProductionLotExecutionElements APLEE ON APLEED.ElementId = APLEE.Id\\\\t\\\\t\\\\tJOIN dbo.Items I ON APLEE.PackingItemId = I.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements RE ON APLEE.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements PLEE ON PLEE.Id = @ProductionLotAggregateId AND PLEE.ExecutionNo = @ExecutionLotReportNo\\\\t\\\\t\\\\t\\\\tAND PLEE.ItemId = I.Id AND ISNULL(PLEE.RecipeElementId,0) = ISNULL(RE.No,0)\\\\t\\\\t\\\\tJOIN dbo.Deliveries D ON APLEED.DeliveryId = D.EntityId\\\\t\\\\t\\\\tGROUP BY PLEE.No\', \'Comment 387: D.Id\', \'Comment 388: I.ItemBaseWeightUnit\\\\t\\\\t\\\\tUPDATE PLEED\\\\t\\\\t\\\\tSET PLEED.Quantity = TD.Quantity\\\\t\\\\t\\\\tFROM @TmpDeliveries TD\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElementDeliveries PLEED ON PLEED.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tAND PLEED.ExecutionNo = @ExecutionLotReportNo AND PLEED.ElementNo = TD.ElementNo AND PLEED.DeliveryId = TD.DeliveryId\\\\t\\\\t\\\\tIF (@@ROWCOUNT > 0)\\\\t\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\t\\\\t;WITH DeliveryMaxNoCTE (ElementNo\', \'Comment 389: MaxNo) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT ElementNo\', \'Comment 390: MAX(No)\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElementDeliveries\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND ExecutionNo = @ExecutionLotReportNo\\\\t\\\\t\\\\t\\\\tGROUP BY ElementNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElementDeliveries (Id\', \'Comment 391: ExecutionNo\', \'Comment 392: ElementNo\', \'Comment 393: No\', \'Comment 394: DeliveryId\', \'Comment 395: Quantity\', \'Comment 396: QuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 397: @ExecutionLotReportNo\', \'Comment 398: TD.ElementNo,\\\\t\\\\t\\\\t\\\\tISNULL(C.MaxNo,0) + ROW_NUMBER() OVER (PARTITION BY TD.ElementNo ORDER BY TD.Id)\', \'Comment 399: TD.DeliveryId\', \'Comment 400: TD.Quantity\', \'Comment 401: TD.Unit\\\\t\\\\t\\\\tFROM @TmpDeliveries TD\\\\t\\\\t\\\\tLEFT JOIN DeliveryMaxNoCTE C ON TD.ElementNo = C.ElementNo\\\\t\\\\t\\\\tWHERE NOT EXISTS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElementDeliveries PLEED\\\\t\\\\t\\\\t\\\\tWHERE PLEED.Id = @ProductionLotAggregateId AND PLEED.ExecutionNo = @ExecutionLotReportNo\\\\t\\\\t\\\\t\\\\t\\\\tAND PLEED.ElementNo = TD.ElementNo AND PLEED.DeliveryId = TD.DeliveryId\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tIF (@@ROWCOUNT > 0)\\\\t\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\tEND\\\\t\\\\tIF (@ChangesOccurred = 1) -- Event\\\\t\\\\tBEGIN\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\tSET PcsEventSyncState |= @ConstExecutionRegisteredPcsEventSyncStateFlag\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = @ExecutionLotReportNo\\\\t\\\\t\\\\tINSERT INTO dbo.PcsIntegrationEvents (EventType\', \'Comment 402: AggregateId\', "Comment 403: ElementNo)\\\\t\\\\t\\\\tVALUES (\'Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.ExecutionReportRegisteredEvent\'", \'Comment 404: @ProductionLotAggregateId\', \'Comment 405: @ExecutionLotReportNo)\\\\t\\\\tEND\\\\t\\\\tCOMMIT\\\\t\\\\tEXEC dbo.AcceptSqlApiRequest @RequestLogId\\\\tEND TRY\\\\tBEGIN CATCH\\\\t\\\\tIF (@@TRANCOUNT > 0)\\\\t\\\\t\\\\tROLLBACK;\\\\t\\\\tDECLARE @ErrorMessage NVARCHAR(4000) = ERROR_MESSAGE()\\\\t\\\\tEXEC dbo.RejectSqlApiRequest @RequestLogId\', \'Comment 406: @ErrorMessage;\\\\t\\\\tTHROW\\\\tEND CATCHENDGO{code}"\', \'Comment 407: "*dbo.SaveProductionReport*:{code:sql}CREATE OR ALTER PROCEDURE dbo.SaveProductionReport(\\\\t@ProductionLotAggregateId UNIQUEIDENTIFIER,\\\\t@QuantityKg DECIMAL(18,6))ASBEGIN\\\\tDECLARE @ConstProductionStatusInProgress INT = 2\\\\tDECLARE @ConstProductionStatusFinished INT = 3\\\\tDECLARE @ConstProductionReportRegisteredPcsEventSyncStateFlag INT = 4\\\\tDECLARE @RecipeAggregateId UNIQUEIDENTIFIER\', \'Comment 408: @ReadyProductAggregateId UNIQUEIDENTIFIER\', \'Comment 409: @ProductionOrderAggregateId UNIQUEIDENTIFIER\', \'Comment 410: @PcsLotId BIGINT\\\\tDECLARE @ElementsMappings TABLE (ApiElementId BIGINT NOT NULL\', \'Comment 411: ExecutionNo INT\', \'Comment 412: ElementNo INT\', \'Comment 413: Ratio DECIMAL(16,6) NOT NULL)\\\\tSELECT\\\\t\\\\t@RecipeAggregateId = RecipeId,\\\\t\\\\t@PcsLotId = PcsLotId,\\\\t\\\\t@ReadyProductAggregateId = ReadyProductId,\\\\t\\\\t@ProductionOrderAggregateId = ProductionOrderId\\\\tFROM dbo.ProductionLots\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\tBEGIN -- Validation\\\\t\\\\tIF ((SELECT Status FROM dbo.ProductionLots WHERE Id = @ProductionLotAggregateId) != @ConstProductionStatusInProgress)\\\\t\\\\t\\\\tTHROW 50000\', "Comment 414: \'Cannot register report in current production status.\'", \'Comment 415: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\t\\\\tWHERE A.PcsLotId = @PcsLotId AND A.QuantityKg < 0\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', "Comment 416: \'Production lot element quantity cannot be negative.\'", \'Comment 417: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements E ON A.RecipeElementId = E.EntityId\\\\t\\\\t\\\\tWHERE A.PcsLotId = @PcsLotId AND A.RecipeElementId IS NOT NULL AND (E.Id IS NULL OR E.Id != @RecipeAggregateId)\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', "Comment 418: \'Recipe element in report does not belong to recipe related to current production.\'", \'Comment 419: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\t\\\\tJOIN dbo.Items I ON A.ItemId = I.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements E ON A.RecipeElementId = E.EntityId\\\\t\\\\t\\\\tWHERE A.PcsLotId = @PcsLotId AND I.Id != E.ItemId\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', "Comment 420: \'Recipe element in report does not match article in report.\'", \'Comment 421: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLED.QuantityKg < 0\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', "Comment 422: \'Production lot element delivery quantity cannot be negative.\'", \'Comment 423: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLED.Barcode IS NOT NULL AND SU.Id IS NULL\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', "Comment 424: \'Some stock unit barcodes do not exist.\'", \'Comment 425: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements AE\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries AD ON AE.Id = AD.ElementId\\\\t\\\\t\\\\tJOIN dbo.Deliveries D ON AD.DeliveryId = D.EntityId\\\\t\\\\t\\\\tJOIN dbo.StockUnits SU ON AD.Barcode = SU.Barcode\\\\t\\\\t\\\\tWHERE AE.PcsLotId = @PcsLotId AND D.Id != SU.DeliveryId\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', "Comment 426: \'Barcode delivery in report does not match delivery id.\'", \'Comment 427: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\tJOIN dbo.FactoryObjects FO ON APLED.SiloCode = FO.PcsCode\\\\t\\\\t\\\\t\\\\tJOIN dbo.Items I ON I.EntityId = APLE.ItemId\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND (FO.ItemId IS NULL OR i.Id != FO.ItemId)\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', "Comment 428: \'Raw material on silo does not match to raw material on element.\'", \'Comment 429: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND (APLED.DeliveryId IS NOT NULL OR APLED.Barcode IS NOT NULL) AND APLED.SiloCode IS NOT NULL\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', "Comment 430: \'Element delivery cannot specify both delivery and silo.\'", \'Comment 431: 1;\\\\tEND\\\\tUPDATE dbo.ProductionLots\\\\tSET Quantity = @QuantityKg,\\\\t\\\\tStatus = @ConstProductionStatusFinished,\\\\t\\\\tEndDate = GETDATE(),\\\\t\\\\tPcsEventSyncState |= @ConstProductionReportRegisteredPcsEventSyncStateFlag\\\\tWHERE Id = @ProductionLotAggregateId;\\\\tINSERT INTO @ElementsMappings (ApiElementId\', \'Comment 432: ExecutionNo\', \'Comment 433: ElementNo\', \'Comment 434: Ratio)\\\\tSELECT ApiElementId\', \'Comment 435: ExecutionNo\', \'Comment 436: ElementNo\', \'Comment 437: Ratio\\\\tFROM dbo.GetProductionElementsMappings(@ProductionLotAggregateId\', \'Comment 438: @PcsLotId\', "Comment 439: NULL)\\\\t\\\\tBEGIN -- Elements\\\\t\\\\tDECLARE @ConstAllowStockRegisteringOnSilosKey INT = 3\\\\t\\\\tDECLARE @ConstAllowStockRegisteringOnSilosTrueValue NVARCHAR(4) = \'True\'\\\\t\\\\tDECLARE @AllowStockRegisteringOnSilos BIT = IIF((\\\\t\\\\t\\\\tSELECT [Value]\\\\t\\\\t\\\\tFROM dbo.Configuration\\\\t\\\\t\\\\tWHERE [Key] = @ConstAllowStockRegisteringOnSilosKey) = @ConstAllowStockRegisteringOnSilosTrueValue,\\\\t\\\\t\\\\t1,\\\\t\\\\t\\\\t0)\\\\t\\\\t;WITH AggregatedElementsCTE (ElementNo", \'Comment 440: QuantityKg) AS\\\\t\\\\t(\\\\t\\\\t\\\\tSELECT M.ElementNo\', \'Comment 441: SUM(A.QuantityKg * M.Ratio)\\\\t\\\\t\\\\tFROM @ElementsMappings M\\\\t\\\\t\\\\tJOIN api.ProductionLotElements A ON M.ApiElementId = A.Id\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL\\\\t\\\\t\\\\tGROUP BY M.ElementNo\\\\t\\\\t)\\\\t\\\\tUPDATE E\\\\t\\\\tSET Quantity = C.QuantityKg\\\\t\\\\tFROM AggregatedElementsCTE C\\\\t\\\\tJOIN dbo.ProductionLotElements E ON E.Id = @ProductionLotAggregateId AND C.ElementNo = E.No\\\\t\\\\tDECLARE @MaxNo INT = (SELECT MAX(No) FROM dbo.ProductionLotElements WHERE Id = @ProductionLotAggregateId);\\\\t\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotElements (Id\', \'Comment 442: No\', \'Comment 443: ItemId\', \'Comment 444: Quantity\', \'Comment 445: QuantityUnit\', \'Comment 446: RequestedQuantity\', \'Comment 447: RequestedQuantityUnit)\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 448: @MaxNo + ROW_NUMBER() OVER (ORDER BY MIN(A.Id))\', \'Comment 449: I.Id\', \'Comment 450: SUM(A.QuantityKg * M.Ratio)\', "Comment 451: \'kg\'", \'Comment 452: 0\', "Comment 453: \'kg\'\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\tJOIN @ElementsMappings M ON A.Id = M.ApiElementId\\\\t\\\\tJOIN dbo.Items I ON A.ItemId = I.EntityId\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND M.ElementNo IS NULL\\\\t\\\\tGROUP BY I.Id\\\\t\\\\tUPDATE M\\\\t\\\\tSET ElementNo = E.No\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\tJOIN dbo.Items I ON A.ItemId = I.EntityId\\\\t\\\\tJOIN @ElementsMappings M ON A.Id = M.ApiElementId\\\\t\\\\tJOIN dbo.ProductionLotElements E ON E.Id = @ProductionLotAggregateId AND I.Id = E.ItemId\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND M.ElementNo IS NULL\\\\t\\\\tINSERT INTO dbo.ProductionLotElementDeliveries (Id", \'Comment 454: ElementNo\', \'Comment 455: No\', \'Comment 456: DeliveryId\', \'Comment 457: StockUnitId\', \'Comment 458: Quantity\', \'Comment 459: QuantityUnit\', \'Comment 460: TotalStockUnitConsumption)\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 461: M.ElementNo\', \'Comment 462: ROW_NUMBER() OVER (PARTITION BY M.ElementNo ORDER BY MIN(APLED.Id)),\\\\t\\\\t\\\\tISNULL(SU.DeliveryId\', \'Comment 463: DD.Id)\', \'Comment 464: SU.Id\', \'Comment 465: SUM(APLED.QuantityKg) * M.Ratio\', "Comment 466: \'kg\'", \'Comment 467: IIF(SU.Id IS NULL,0,APLED.TotalBarcodeConsumption)\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\tLEFT JOIN dbo.Deliveries DD ON APLED.DeliveryId = DD.EntityId\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND ISNULL(SU.DeliveryId\', \'Comment 468: DD.Id) IS NOT NULL\\\\t\\\\tGROUP BY M.ElementNo\', \'Comment 469: SU.DeliveryId\', \'Comment 470: DD.Id\', \'Comment 471: SU.Id\', \'Comment 472: M.Ratio\', \'Comment 473: APLED.TotalBarcodeConsumption\\\\t\\\\tDECLARE @DosingMaxNo INT = ISNULL((SELECT MAX(No) FROM dbo.Dosings WHERE Id = @ProductionLotAggregateId),0)\\\\t\\\\tDECLARE @TmpDosings TABLE (ElementNo INT NOT NULL\', \'Comment 474: DeliveryAggregateId UNIQUEIDENTIFIER\', \'Comment 475: StockUnitAggregateId UNIQUEIDENTIFIER\', \'Comment 476: SiloAggregateId UNIQUEIDENTIFIER\', \'Comment 477: QuantityKg DECIMAL(18,6))\\\\t\\\\t\\\\t\\\\tINSERT INTO @TmpDosings (ElementNo\', \'Comment 478: DeliveryAggregateId\', \'Comment 479: StockUnitAggregateId\', \'Comment 480: SiloAggregateId\', \'Comment 481: QuantityKg)\\\\t\\\\tSELECT M.ElementNo\', \'Comment 482: ISNULL(SU.DeliveryId\', \'Comment 483: D.Id)\', \'Comment 484: SU.Id\', \'Comment 485: IIF(@AllowStockRegisteringOnSilos = 1,FO.Id,NULL)\', \'Comment 486: APLED.QuantityKg * M.Ratio\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\tLEFT JOIN dbo.Deliveries D ON APLED.DeliveryId = D.EntityId\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\tLEFT JOIN dbo.FactoryObjects FO ON APLED.SiloCode = FO.PcsCode\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND COALESCE(SU.DeliveryId\', \'Comment 487: D.Id\', \'Comment 488: IIF(@AllowStockRegisteringOnSilos = 1,FO.Id,NULL)) IS NOT NULL\\\\t\\\\t\\\\t\\\\tINSERT INTO dbo.Dosings (Id\', \'Comment 489: No\', \'Comment 490: BatchNo\', \'Comment 491: BatchElementNo\', \'Comment 492: ElementNo\', \'Comment 493: Quantity\', \'Comment 494: QuantityUnit\', \'Comment 495: Date\', \'Comment 496: DeliveryId\', \'Comment 497: StockUnitId\', \'Comment 498: SiloId)\\\\t\\\\tSELECT \\\\t\\\\t\\\\t@ProductionLotAggregateId,\\\\t\\\\t\\\\t@DosingMaxNo + ROW_NUMBER() OVER (ORDER BY TD.ElementNo\', \'Comment 499: TD.DeliveryAggregateId\', \'Comment 500: TD.StockUnitAggregateId\', \'Comment 501: TD.SiloAggregateId),\\\\t\\\\t\\\\tNULL\', \'Comment 502: \\\\t\\\\t\\\\tNULL\', \'Comment 503: \\\\t\\\\t\\\\tTD.ElementNo,\\\\t\\\\t\\\\tTD.QuantityKg\', "Comment 504: \\\\t\\\\t\\\\t\'kg\'", \'Comment 505: \\\\t\\\\t\\\\tGETDATE()\', \'Comment 506: \\\\t\\\\t\\\\tTD.DeliveryAggregateId\', \'Comment 507: \\\\t\\\\t\\\\tTD.StockUnitAggregateId\', \'Comment 508: \\\\t\\\\t\\\\tTD.SiloAggregateId\\\\t\\\\tFROM @TmpDosings TD\\\\tEND\\\\tBEGIN -- Executions\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\tSET Quantity = @QuantityKg,\\\\t\\\\t\\\\tRequestedQuantity = IIF(@ProductionOrderAggregateId IS NULL\', \'Comment 509: @QuantityKg\', \'Comment 510: RequestedQuantity)\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND ReadyProductId = @ReadyProductAggregateId\\\\t\\\\tUPDATE dbo.ProductionLots\\\\t\\\\tSET RequestedQuantity = (SELECT SUM(RequestedQuantity) FROM dbo.ProductionLotExecutions WHERE Id = @ProductionLotAggregateId)\\\\t\\\\tWHERE Id = @ProductionLotAggregateId;\\\\tEND\\\\tBEGIN -- Execution elements\\\\t\\\\t;WITH AggregatedExecutionElementsCTE (ExecutionNo\', \'Comment 511: ElementNo\', \'Comment 512: QuantityKg) AS\\\\t\\\\t(\\\\t\\\\t\\\\tSELECT M.ExecutionNo\', \'Comment 513: M.ElementNo\', \'Comment 514: SUM(A.QuantityKg * M.Ratio)\\\\t\\\\t\\\\tFROM @ElementsMappings M\\\\t\\\\t\\\\tJOIN api.ProductionLotElements A ON M.ApiElementId = A.Id\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL\\\\t\\\\t\\\\tGROUP BY M.ExecutionNo\', \'Comment 515: M.ElementNo\\\\t\\\\t)\\\\t\\\\tUPDATE EE\\\\t\\\\tSET Quantity = C.QuantityKg\\\\t\\\\tFROM AggregatedExecutionElementsCTE C\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements EE ON EE.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\tAND EE.ExecutionNo = C.ExecutionNo AND EE.No = C.ElementNo\\\\t\\\\t;WITH ExecutionElementMaxNoCTE (ExecutionNo\', \'Comment 516: ElementMaxNo) AS\\\\t\\\\t(\\\\t\\\\t\\\\tSELECT ExecutionNo\', \'Comment 517: MAX(No)\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElements\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\tGROUP BY ExecutionNo\\\\t\\\\t)\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElements (Id\', \'Comment 518: ExecutionNo\', \'Comment 519: No,\\\\t\\\\t\\\\tItemId\', \'Comment 520: Quantity\', \'Comment 521: QuantityUnit\', \'Comment 522: RequestedQuantity\', \'Comment 523: RequestedQuantityUnit)\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 524: M.ExecutionNo\', \'Comment 525: ISNULL(C.ElementMaxNo,0) + ROW_NUMBER() OVER (PARTITION BY M.ExecutionNo ORDER BY MIN(A.Id)),\\\\t\\\\t\\\\tI.Id\', \'Comment 526: SUM(A.QuantityKg * M.Ratio)\', \'Comment 527: I.ItemBaseWeightUnit\', \'Comment 528: 0\', \'Comment 529: I.ItemBaseWeightUnit\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\tJOIN @ElementsMappings M ON A.Id = M.ApiElementId\\\\t\\\\tJOIN dbo.Items I ON A.ItemId = I.EntityId\\\\t\\\\tLEFT JOIN ExecutionElementMaxNoCTE C ON M.ExecutionNo = C.ExecutionNo\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND M.ElementNo IS NULL\\\\t\\\\tGROUP BY M.ExecutionNo\', \'Comment 530: C.ElementMaxNo\', \'Comment 531: I.Id\', \'Comment 532: I.ItemBaseWeightUnit\\\\t\\\\tUPDATE M\\\\t\\\\tSET ElementNo = EE.No\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\tJOIN dbo.Items I ON A.ItemId = I.EntityId\\\\t\\\\tJOIN @ElementsMappings M ON A.Id = M.ApiElementId\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements EE ON EE.Id = @ProductionLotAggregateId AND EE.ExecutionNo = M.ExecutionNo AND EE.ItemId = I.Id\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND M.ElementNo IS NULL\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElementDeliveries (Id\', \'Comment 533: ExecutionNo\', \'Comment 534: ElementNo\', \'Comment 535: No\', \'Comment 536: DeliveryId\', \'Comment 537: StockUnitId\', \'Comment 538: Quantity\', \'Comment 539: QuantityUnit)\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 540: M.ExecutionNo\', \'Comment 541: M.ElementNo\', \'Comment 542: ROW_NUMBER() OVER (PARTITION BY M.ExecutionNo\', \'Comment 543: M.ElementNo ORDER BY MIN(APLED.Id)),\\\\t\\\\t\\\\tISNULL(SU.DeliveryId\', \'Comment 544: DD.Id)\', \'Comment 545: SU.Id\', \'Comment 546: SUM(APLED.QuantityKg * M.Ratio)\', "Comment 547: \'kg\'\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\tLEFT JOIN dbo.Deliveries DD ON APLED.DeliveryId = DD.EntityId\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND ISNULL(SU.DeliveryId", \'Comment 548: DD.Id) IS NOT NULL\\\\t\\\\tGROUP BY M.ExecutionNo\', \'Comment 549: M.ElementNo\', \'Comment 550: SU.DeliveryId\', \'Comment 551: DD.Id\', \'Comment 552: SU.Id\\\\tEND\\\\tDELETE APLED\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\tJOIN api.ProductionLotElements APLE ON APLE.Id = APLED.ElementId\\\\tWHERE APLE.PcsLotId = @PcsLotId\\\\tDELETE FROM api.ProductionLotElements\\\\tWHERE PcsLotId = @PcsLotId\\\\tINSERT INTO dbo.PcsIntegrationEvents (EventType\', "Comment 553: AggregateId)\\\\tVALUES (\'Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.ProductionReportRegisteredEvent\'", \'Comment 554: @ProductionLotAggregateId)ENDGO{code}"\', "Comment 555: \'On all plants have been removed the mentioned validations from the database level", "Comment 556: the problem should no longer occur.\'", "Comment 557: \'Oke", "Comment 558: thanks for now: ticket can be closed\'", "Comment 559: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8840\n\n### Instruction:\nPlease, change the status of the Production Report from Canceled to Finished. Production Report number: 0742150323001\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Dear,According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task.Regards\'", "Comment 4: \'please change the category of the task\'", \'Comment 5: "id=2806eca0-57b6-4100-a5c2-8fdfc07cfe5d — id plrPLR nie ma w DHC.nie ma w bazie pcdlogicmainjest w bazie stock i prod\', \'Comment 6: wms!image-2023-04-04-10-53-44-477.png|width=826,height=123!na wydarzeniach user pcs edytował to ale użytwkonik Admin anulował to 17.03select * from ProductionLots where AggregateId=\\\'2806eca0-57b6-4100-a5c2-8fdfc07cfe5d\\\' !image-2023-04-04-10-53-44-477!"\', "Comment 7: \'Good morning I see that currently there is no this PLR in the PCs database", \'Comment 8: it has not been sent to DHC. Do you expect it to go to DHC and ERP? Why should its status be changed\', \'Comment 9: has this shipment been created and what about the stocks in this situation?Should they be created as for a normal PLR\', "Comment 10: or have they already been consumed,Regarding the creation of stock have you considered stocktaking?\'", "Comment 11: \'We have analyzed the situation and in the given situation we ask you to create a new plr", "Comment 12: recommended.May we close the task?\'", "Comment 13: \'May we close the task?\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8839\n\n### Instruction:\nItemcode 257551 not sync to DHP\r\n\r\nError Log :\r\n2023-03-27 11:06:56,177 [14] ERROR Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\BambooHome\\xml-data\\build-dir\\4292609\\DHAPPSV3-DHCSER411-JOB1\\Evolution.DHCService\\Evolution.DHCService.Dhc30\\Handlers\\BaseMessageHandler.cs:56] - System.Data.Entity.Infrastructure.DbUpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.Entity.Core.UpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_dbo.Items_dbo.DhhItems_DhhItemId". The conflict occurred in database "Evolution_DHCService_IND", table "dbo.DhhItems", column \'Id\'.\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: \'Data has been corrected", "Comment 3: please verify and send a feedback.\'", "Comment 4: \'OK data has been sync", "Comment 5: thank you\'", "Comment 6: \'hi", "Comment 7: could you tell us the route cause of this issue? Did it come from user input or what?\'", "Comment 8: \'Yes", "Comment 9: the reason was missing DHHItem in DhcService database which was fixed in DHC version 3.0.60.\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8838\n\n### Instruction:\nPlease import additional technologies for plant Helmond (9) in DHC test and DHC prod as listed in attached excel, tab Import sheet.\r\n\r\nSee tab README in the excel for more details.\n\n### Response:\n["Comment 1: [\'[^20230327_DHC_Helmond_additional_technology.xlsx] _(1,19 MB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Dear,According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task.Regards\'", "Comment 4: \'You are correct. Please update the type to service request.\'", "Comment 5: \'Hej Przemku zadanie chyba dla Ciebie.\'", "Comment 6: \'Import:!image-2023-03-30-11-37-01-524.png!!image-2023-03-30-11-37-01-524!\'", "Comment 7: \'Import has be done", "Comment 8: please verify.\'", "Comment 9: \'Thank you. Import was done correctly. This ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8837\n\n### Instruction:\nHello,\r\n\r\ncan you please investigate trip 00996605: There are two VT\'s connected: one for bulk and one for the packed goods: It should\'t be possible to create 2 VT\'s connected to one trip in our configuration: Can you please investigate how this can happen and how to prevent?\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: \'!image-2023-03-28-15-52-23-230.png!Tego jednego nie ma w DHC!image-2023-03-28-16-25-37-875.png!\'", "Comment 4: \'!image-2023-03-28-16-29-14-320.png!\'", "Comment 5: \'Wygląda na to", "Comment 6: że VT były zakładane jednocześnie:!image-2023-03-28-16-59-25-952.png!Ten PCSowy jest closed i ma mapowanie:!image-2023-03-28-17-00-06-590.png!\'", "Comment 7: \'!image-2023-03-28-17-03-48-015.png!\'", "Comment 8: \'Na każdym VT są i packed i bulk", \'Comment 9: nie ża na jednym VT jedno\', "Comment 10: a na drugim drugie!image-2023-03-28-17-14-38-680.png!\'", "Comment 11: \'I zastanawiam się czy to nie jest ten element configu!image-2023-03-28-17-15-29-030.png!\'", "Comment 12: \'No i stety lub nie", "Comment 13: oba VT mają elementy released:!image-2023-03-28-17-17-17-757.png!!image-2023-03-28-17-17-36-985.png!\'", "Comment 14: \'!image-2023-03-28-17-24-37-558.png!\'", "Comment 15: \'Zgodnie z rozmową Teams\'", "Comment 16: \'Hi Thomas,We need to consult your configuration issue with dev team. We will let you know about the result as soon as possible.Regards\'", \'Comment 17: "1. PCS wysyła loading report(/) Tworzy się VT\', "Comment 18: ilości dla bulków są rejestrowane2. Prawie w tym samym czasie użytkownik \'produtrecht\' klika na opcję tworzenia VT. Ponieważ lista tripów nie została odświeżona", "Comment 19: to dalej miał dostępną opcję \'create VT\'. Gdyby lista została odświeżona", \'Comment 20: to opcja \\\'create VT\\\' byłaby nieaktywna.: [^2 vt_trip.mp4]Utworzony DAP: DAP-13496 (realizacja w 8.6) !image-2023-03-29-13-24-35-050!"\', "Comment 21: \'Dear Thomas,We can confirm that PCS sent loading report", \'Comment 22: then VT has been created and quantities for bulk are registered. 3 seconds later\', \'Comment 23: userprodutrecht has clicked "create vt". As Trip list has not been refreshed\', \'Comment 24: produtrech had opition "cretae vt" available. As a resultprodutrech created VT-1459. All quantities forpacked bulkare registered on VT-1458 so we think VT-1459 could be cancelled (now it is in progress).Regards\\\'\', "Comment 25: \'Yes it is indeed: But I think a change is needed to prevent this situation from happening?\'", "Comment 26: \'We have raised a task to prevent such situation. It will be fixed in 8.6 version.Please", "Comment 27: let me know if we should cancelVT-1459.Regards\'", "Comment 28: \'Yes you can cancel 1459\'", "Comment 29: \'Done.Can we close this task then?Regards\'", "Comment 30: \'!image-2023-04-03-11-27-46-854.png!\'", "Comment 31: \'can be closed\'", "Comment 32: \'Thank you\']"]\nRelated Issues:\n[\'DAP-13496\']\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8836\n\n### Instruction:\nHello, \n\n\xa0 \n\nI’m resending this email to you, because I got automatic answer from Marta that she isn’t in office today. \n\nCould you please look at our DHC client why is it not working? \n\n\xa0 \n\nMore details bellow. \n\n\xa0 \n\nThank you. \n\n\xa0 \n| \n| \n| \n| \n|{color:blue}{color} !http://www.energyshobby.cz/_email/ENG/body_it.jpg!{color:blue}{color} <[http://www.energyshobby.cz/_email/ENG/body_url_it.htm]> | \n\n{color:black}Best regards\n \n *Michal Polacek*\n IT administrator\n Mobile nr.:\xa0+420 775 862 755{color}\n [{color:blue}mpolacek@deheus.com{color}|mailto:mpolacek@deheus.com]{color:black}{color} \n| \n| \n| !http://www.energyshobby.cz/_email/ENG/line.jpg! | \n| \n| \n| !http://www.energyshobby.cz/_email/ENG/royal_eng.png! | \n| \n| \n|{color:blue}{color} !http://www.energyshobby.cz/_email/ENG/logo.png!{color:blue}{color} <[http://www.deheus.com/]> | \n\n *{color:#2181C0} *De Heus a.s.*{color}*{color:#2181C0}\n Marefy 144, 685 01 Bucovice, Czech Republic\n REG nr.: 25321498, VAT nr.: CZ25321498\n Tel.: +420 517 307 701, Fax: +420 517 307 702{color}\n [{color:blue}info@deheus.cz{color}|mailto:info@deheus.cz%20%20]{color:#2181C0}\xa0/\xa0{color}[{color:blue}www.deheus.cz{color}|http://www.deheus.cz]{color:#2181C0}{color} \n \n\n\xa0 \n \n\n *From:* Poláček, Michal \n *Sent:* Monday, March 27, 2023 12:40 PM\n *To:* Marta Litkie <marta.litkie@kotrak.com>\n *Cc:* Svoboda, Petr <PSvoboda@deheus.com>; Adamcik, Michal <madamcik@deheus.com>; Horáková, Lucie <lhorakova@deheus.com>; Blazek, Oldrich <OBlazek@deheus.com>\n *Subject:* DHC not working \n\n\xa0 \n\nHello Marta, \n\n\xa0 \n\nOn Saturaday night I restarted DHC server 10.42.0.198 because there was windows update waiting for restart and today I needed restart PRODSQL server 10.42.0.195 where I think is database for DHC. \n\nHowever right now DHC is not working. I checked services and Business platform service is running. \n\n\xa0 \n\nCould you please look at that? \n\n\xa0 \n| \n| \n| \n| \n|{color:blue}{color} !http://www.energyshobby.cz/_email/ENG/body_it.jpg!{color:blue}{color} <[http://www.energyshobby.cz/_email/ENG/body_url_it.htm]> | \n\n{color:black}Best regards\n \n *Michal Polacek*\n IT administrator\n Mobile nr.:\xa0+420 775 862 755{color}\n [{color:blue}mpolacek@deheus.com{color}|mailto:mpolacek@deheus.com]{color:black}{color} \n| \n| \n| !http://www.energyshobby.cz/_email/ENG/line.jpg! | \n| \n| \n| !http://www.energyshobby.cz/_email/ENG/royal_eng.png! | \n| \n| \n|{color:blue}{color} !http://www.energyshobby.cz/_email/ENG/logo.png!{color:blue}{color} <[http://www.deheus.com/]> | \n\n *{color:#2181C0} *De Heus a.s.*{color}*{color:#2181C0}\n Marefy 144, 685 01 Bucovice, Czech Republic\n REG nr.: 25321498, VAT nr.: CZ25321498\n Tel.: +420 517 307 701, Fax: +420 517 307 702{color}\n [{color:blue}info@deheus.cz{color}|mailto:info@deheus.cz%20%20]{color:#2181C0}\xa0/\xa0{color}[{color:blue}www.deheus.cz{color}|http://www.deheus.cz]{color:#2181C0}{color} \n \n\n\xa0\n\n### Response:\n["Comment 1: [\'Hi Michal,This should be reported as an incident via portal [https://helpdesk.kotrak.com/servicedesk/customer/portal/56]", "Comment 2: not directly via email to Marta.Regards\'", "Comment 3: \'Hello", \'Comment 4: Ok\', \'Comment 5: sorry. I will create an ticket on kotrak helpdesk righ now. | | | | | !http://www.energyshobby.cz/_email/ENG/body_it.jpg! <[http://www.energyshobby.cz/_email/ENG/body_url_it.htm]> | {color:black}Best regards *Michal Polacek* IT administrator Mobile nr.:+420 775 862 755{color} [{color:black}mpolacek@deheus.com{color}|mailto:mpolacek@deheus.com]{color:black}{color} | | | !http://www.energyshobby.cz/_email/ENG/line.jpg! | | | | !http://www.energyshobby.cz/_email/ENG/royal_eng.png! | | | | !http://www.energyshobby.cz/_email/ENG/logo.png! <[http://www.deheus.com/]> | *{color:#2181C0} *De Heus a.s.*{color}*{color:#2181C0} Marefy 144\', \'Comment 6: 685 01 Bucovice\', \'Comment 7: Czech Republic REG nr.: 25321498\', \'Comment 8: VAT nr.: CZ25321498 Tel.: +420 517 307 701\', \'Comment 9: Fax: +420 517 307 702{color} [{color:#2181C0}info@deheus.cz{color}|mailto:info@deheus.cz%20%20]{color:#2181C0}/{color}[{color:#2181C0}www.deheus.cz{color}|http://www.deheus.cz]{color:#2181C0}{color} *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com> *Sent:* Monday\', \'Comment 10: March 27\', \'Comment 11: 2023 1:14 PM *To:* Poláček\', "Comment 12: Michal <mpolacek@deheus.com> *Subject:* EAS-17271 FW: DHC not working \'", "Comment 13: \'Task to close. Issue realized under ticket DGS-8835\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8835\n\n### Instruction:\nHello,\r\nOn Saturaday night I restarted DHC server 10.42.0.198 because there was windows update waiting for restart and today I needed restart PRODSQL server 10.42.0.195 where I think is database for DHC.\r\nHowever right now DHC is not working. I checked services and Business platform service is running.\r\n\r\nCould you please look at that?\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: \'Michal,DHC should work now. Please", "Comment 3: verify on your side.Regards\'", "Comment 4: \'Wszystkie trzy były stopped after crash!image-2023-03-27-13-22-33-115.png!\'", "Comment 5: \'!image-2023-03-27-13-23-15-407.png!\'", "Comment 6: \'Hi", "Comment 7: Yes it is working now.Thank you.\'", "Comment 8: \'No problem:)Regards\']"]\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8834\n\n### Instruction:\nHello,\r\n\r\nSOBE000018358 contains orderelements for item 111409: this is a composition and there is an additional technology for it. This AT was incorrect, with 0044 set to 20%, this is adjusted with a subversion and now it is set to 35%. However, order is still send with blendpercentage 20%: Can you please check and advise how to solve it? This is P1 because order needs to be procuced ASAP\r\n\r\n<ItemCodeBase>111409</ItemCodeBase><BlendItemCodeMain>111443</BlendItemCodeMain><BlendItemCodeAddition>0044</BlendItemCodeAddition><BlendPercentage>20</BlendPercentage>\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hello\', \'Comment 4: I can confirm it\\\'s now synced correct. Ticket can be closed"]\']\nRelated Issues:\n[]\n\n### End'}

{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8833\n\n### Instruction:\nWe cannot start the app from RSTS01 server, documents are not syncronized. Can you please check asap?\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-03-27-12-18-31-745.png!!image-2023-03-27-12-26-35-129.png!!image-2023-03-27-12-26-35-129!\'", "Comment 4: \'Please", "Comment 5: check now. It should be running now. Reason: Business Platform was not running.Regards\'", "Comment 6: \'Tnx its working now. Can you tell me the exact name of the service", \'Comment 7: because I looked for it in the list and could not find it? That is\', "Comment 8: there is no bussines platform service in the list of Windows services. What is the path to that services? \'", "Comment 9: \'Business Platform. On DHC serverRSAPP08 – 10.100.3.54\'", "Comment 10: \'Ok", "Comment 11: thanks. You can close the ticket.\'", "Comment 12: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}