Datasets:

pismacx
/

ai_assistant

Dataset card Data Studio Files Files and versions Community

Split (1)

train · 1k rows

Unnamed: 0 int64 0 999	0 stringlengths 258 77k
700	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8331\n\n### Instruction:\nMorning,\r\n\r\nIs it possible to remove the option of Cntrl+Add (Copy) of existing PO’s to create a new one. Users must be forced to create a PO from scratch.\r\n\r\nThis must apply only to the Sundry Purchase Contexts ( HQ Sundry Purchase.\r\n\r\nThanks.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'!image-2023-01-17-12-03-02-378.png!Że tu?!image-2023-01-17-12-13-51-778.png!!image-2023-01-17-12-13-51-778!\'", "Comment 3: \'Dear Nosipho,How do you exactly activatePO Ctrl Copy Feature? Is it used from ERP XL or DHCDN?Regards\'", \'Comment 4: "It\\\'s standard ERP functionality:Ctrl+Ins (or \\\'+\\\' button)"\', "Comment 5: \'No", "Comment 6: unfortunatelly standard functionalities cannot be removed / deactivated. To avoidcreating a PO from scratch I think the best option would be add / create PO from the very beginning.Regards\'", "Comment 7: \'Thanks", "Comment 8: you may close this ticket\'", "Comment 9: \'We will check one more thing but we have to wait until relevant dev will return from his holidays. We will ultimately confirm in about 10 days. Till this time I will put this task on hold. Would that be fine for you?Regards\'", "Comment 10: \'That is fine as well.\'", "Comment 11: \'Thanks\'", "Comment 12: \'Morning AleksandraDo you have an update on this please.Regards\'", "Comment 13: \'Morning Rey,Our colleague came back today to the office", "Comment 14: so we will let you know this week.Regards\'", "Comment 15: \'Hi,Total Costs: 8 working hours.Specification:The mechanism will intercept the Ctrl + Insert key combinations with the call on the list of order documents in the orders module.The mechanism will work on the indicated Comarch ERP XL centers.The operation of the action will consist in intercepting the Ctrl + Insert command", "Comment 16: which will not open a window with a new order.The mechanism will be created under the XL 2019.3\'", "Comment 17: \'Hi,Do You accept costs ?\'", "Comment 18: \'Hello,We discussed the below with the business and they do not accept the cost.You may close this ticket.Thanks\'", "Comment 19: \'Sure. Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}
701	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8330\n\n### Instruction:\nPlease help to check PLR 4322130123075 in Nghe An Plant ( 0432) . \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,Could you please verify the connection for us?Regards!image-2023-01-16-13-56-03-211.png!\'", \'Comment 4: "Hi,i\\\'m not sure where you get that info but correct info as in Attachment!image-2!"\', "Comment 5: \'Hi,These are or rather were IP addresses forNghe An plant valid for the 7th of December:!image-2023-01-17-09-21-12-345.png!We did not know that IPs have changed. Thank you for information\'", "Comment 6: \'It has the same error message:!image-2023-01-17-10-16-08-221.png!For all below users:!image-2023-01-17-10-15-43-333.png!Please", "Comment 7: verify.Regards\'", "Comment 8: \'i do not know who will provide like that. it should be: Apac\\\\\\\\user\'", "Comment 9: \'!image-2023-01-17-13-55-54-442.png!\'", "Comment 10: \'What is more", \'Comment 11: I have received information from our dev team\', \'Comment 12: that it always worked with user like: !image-2023-01-17-13-57-32-553.png!Finally\', \'Comment 13: with this login I can login to other plant servers\', \'Comment 14: for example Can Tho.Please\', "Comment 15: verify.Regards\'", "Comment 16: \'please try!image-3!\'", "Comment 17: \'For both users it is working fine now.Thank you\'", "Comment 18: \'{code:java}2023-01-13 17:34:48 (e6380b58-125d-41c2-a0b4-7a0e694dd1f5/Plant.Prod.BusinessLogic/VNACNA-TS1/21796/5) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[StartProductionCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ProductionLots.Commands.StartProductionCommand) methodKotrak.Common.Application.Exceptions.BusinessLogicException: Production lot report with id 4d4f4c92-8a98-4c09-9443-5f1ce8ef7781 already exists. ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: ProductionLotReportAlreadyExistsMessage at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.StartProduction(StartProductionActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 239 at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.StartProductionCommandHandler.Handle(StartProductionCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\StartProductionCommandHandler.cs:line 37 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 19: \'W Stock i WMS czysto", "Comment 20: tylko w Prod!image-2023-01-18-07-55-28-522.png!\'", "Comment 21: \'!image-2023-01-18-07-59-06-833.png!\'", "Comment 22: \'!image-2023-01-18-08-06-36-677.png!\'", "Comment 23: \'!image-2023-01-18-09-22-38-178.png!\'", \'Comment 24: "{code:java}SELECT LotNumber\', "Comment 25: PcsLotId,* FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where id = \'4D4F4C92-8A98-4C09-9443-5F1CE8EF7781\' SELECT LotNumber", \'Comment 26: PcsLotId\', "Comment 27: * FROM [DHPlantStockBusinessLogicMain].[dbo].[ProductionLots] where id = \'4D4F4C92-8A98-4C09-9443-5F1CE8EF7781\' SELECT PcsLotId", \'Comment 28: * FROM [DHPlantPCSBusinessLogicMain].[dbo].[ProductionLots] where id = \\\'4D4F4C92-8A98-4C09-9443-5F1CE8EF7781\\\' --LotNumber = \\\'4322130123075\\\' or {code}{code:java}SELECT TOP (1000) [Id] ,[Created] ,[AggregateType] ,[AggregateId] ,[Event] ,[EventType] ,[UserId] ,[UserName] ,[CorrelationId] FROM [DHPlantPCSBusinessLogicEvents].[dbo].[ProductionLots] where AggregateId = \\\'4D4F4C92-8A98-4C09-9443-5F1CE8EF7781\\\' SELECT * FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots] where AggregateId = \\\'4D4F4C92-8A98-4C09-9443-5F1CE8EF7781\\\'{code}{code:java} SELECT pp.LotNumber as Production,sp.LotNumber as Stock SELECT pp.LotNumber as Production,sp.LotNumber as Stock FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] pp left join [DHPlantStockBusinessLogicMain].[dbo].[ProductionLots] sp on pp.id=sp.id where pp.LotNumber like \\\'4322130123%\\\'{code}"\', "Comment 29: \'Hi,Was functionPredict Lot Number in Production Line configuration activated for PLR4322130123075? Is this function activated for all PLRs?Regards\'", "Comment 30: \'stand up - do analizy dla Tomka.\'", "Comment 31: \'Currently", \'Comment 32: this issue continues to happen at Nghe An Plant (0432) . Please help to check PLR 4322220323007\', \'Comment 33: 4322220323006\', \'Comment 34: 4322210323039\', \'Comment 35: 4322210323036\', "Comment 36: 4322220323003 . Tks u\'", "Comment 37: \'Exactly", "Comment 38: the PLRs \\\\u200breleased to stock and auto released out of stock after that.\'", "Comment 39: \'Please help to close this ticket. I raised this issue in new ticket.\'", "Comment 40: \'Due toDGS-8801 task", "Comment 41: this task will be closed as requested. Thank you for your comment.Regards\']"]\nRelated Issues:\n[\'DGS-8801\', \'DGS-8422\', \'DGS-8329\']\n\n### End'}
702	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8329\n\n### Instruction:\nhi team, \r\nwe faced with issue of confirmation for PLR. After checking i found that, this lot number can not be created in Stock module due to duplicated. \r\nWe did cancel PLR and create new one and it works. \r\n\r\nbut\r\n\r\ni would ask for fix this issue\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,Does the issue occurs only forCan Tho or for other plants as well. Is this the only example? If there are any new examples", "Comment 4: please provide us with PLR number.Regards\'", "Comment 5: \'{code:java}id=b85005e1-f436-427f-95cf-da74dd5f25f5{code}\'", "Comment 6: \'!image-2023-01-16-14-47-10-555.png!!image-2023-01-16-14-47-10-555!\'", \'Comment 7: \\\'request log dla tego PLRa{code:java}2023-01-14 14:33:56 (1597b71e-f394-4af9-98ca-d37d2d2fe295/Plant.Prod.BusinessLogic/VNPCT-TS01/37416/142) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 8: "host": { "Value": "10.84.165.11:83"\', \'Comment 9: "HasValue": true\', \'Comment 10: "Host": "10.84.165.11"\', \'Comment 11: "Port": 83 }\', \'Comment 12: "path": "/api/productionLot/update"\', \'Comment 13: "queryString": []\', \'Comment 14: "requestBody": "{\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":2,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"b9d59fe1-8d5b-4bf3-a2fc-9ef0f8215a68\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":10975}}],\\\\\\\\"executions\\\\\\\\":[{\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"af7c6cd4-59ac-4a3a-b031-2b7592eb702b\\\\\\\\",\\\\\\\\"recipeElementId\\\\\\\\":1,\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"pcs.\\\\\\\\",\\\\\\\\"value\\\\\\\\":439}}],\\\\\\\\"readyProductId\\\\\\\\":\\\\\\\\"93117a11-8a61-4810-a27d-e609f5a266de\\\\\\\\",\\\\\\\\"packingRecipeId\\\\\\\\":\\\\\\\\"78714528-54d7-4cbb-9922-e6033adc8fd4\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":10975},\\\\\\\\"requestedQuantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":10975},\\\\\\\\"expiryDate\\\\\\\\":\\\\\\\\"2023-07-13T07:29:20.073Z\\\\\\\\"}],\\\\\\\\"reservations\\\\\\\\":[],\\\\\\\\"productionLotId\\\\\\\\":\\\\\\\\"b85005e1-f436-427f-95cf-da74dd5f25f5\\\\\\\\",\\\\\\\\"recipeId\\\\\\\\":\\\\\\\\"78714528-54d7-4cbb-9922-e6033adc8fd4\\\\\\\\",\\\\\\\\"labelId\\\\\\\\":null,\\\\\\\\"productionOrderId\\\\\\\\":\\\\\\\\"31bc80b5-be67-43e0-82e6-e7c621722fd1\\\\\\\\",\\\\\\\\"shiftNumberId\\\\\\\\":\\\\\\\\"4723a183-8aa0-4d63-a309-21beb277ee3b\\\\\\\\",\\\\\\\\"description\\\\\\\\":\\\\\\\\"CA 1\', \'Comment 15: 14/01/2023\\\\\\\\",\\\\\\\\"statusChange\\\\\\\\":3}"}.System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 400 (Bad Request).) ---> Refit.ApiException: Response status code does not indicate success: 400 (Bad Request). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273 --- End of inner exception stack trace --- at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 16: AggregateId businessUnitId\', \'Comment 17: Quantity productionQuantity\', \'Comment 18: IEnumerable`1 settlementData\', \'Comment 19: 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 20: ConfirmProductionLotActionData data\', \'Comment 21: IEnumerable`1 reservations\', \'Comment 22: 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 23: Object \', \'Comment 24: Object[] ) at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target\', \'Comment 25: Object[] parameters) at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 26: ObjectMethodExecutor executor\', \'Comment 27: Object controller\', \'Comment 28: 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 29: Scope& scope\', \'Comment 30: Object& state\', \'Comment 31: 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 32: Scope& scope\', \'Comment 33: Object& state\', "Comment 34: 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: 400 (Bad Request). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273<---{code}\'", \'Comment 35: "{code:java}SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where id=\\\'b85005e1-f436-427f-95cf-da74dd5f25f5\\\' SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLotElements] where RecipeId = \\\'78714528-54D7-4CBB-9922-E6033ADC8FD4\\\' SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[Recipes] where Id = \\\'78714528-54D7-4CBB-9922-E6033ADC8FD4\\\' SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[RecipeElements] where ItemId = \\\'93117A11-8A61-4810-A27D-E609F5A266DE\\\' SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where recipeid = \\\'78714528-54D7-4CBB-9922-E6033ADC8FD4\\\'{code}"\', "Comment 36: \'hi team", "Comment 37: this issue happened in others as well when we activate Predict Lot Number in Production Line configuration. \'", "Comment 38: \'[[email protected]]zgodnie z rozmową na Teams", "Comment 39: dzięki <3\'", "Comment 40: \'Tank you for your information. We are analysing your issue.Regards\'", \'Comment 41: \\\'PLR o numerze "4372140123005" ma w stocku inny idik niż w prodzie. Dlatego przy potwierdzaniu pojawia się błąd "Production lot with id b85005e1-f436-427f-95cf-da74dd5f25f5 was not found".{code:java}2023-01-14 16:03:06 (9c3f58d8-6e3c-436a-aff5-393c412acab5/Plant.Stock.BusinessLogic/VNPCT-TS01/16360/227) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 42: "host": { "Value": "10.84.165.11:92"\', \'Comment 43: "HasValue": true\', \'Comment 44: "Host": "10.84.165.11"\', \'Comment 45: "Port": 92 }\', \'Comment 46: "path": "/api/productionLot/updateReservationsAndConfirm"\', \'Comment 47: "queryString": []\', \'Comment 48: "requestBody": "{\\\\\\\\"ProductionLotId\\\\\\\\":\\\\\\\\"b85005e1-f436-427f-95cf-da74dd5f25f5\\\\\\\\",\\\\\\\\"BusinessUnitId\\\\\\\\":\\\\\\\\"600d0754-5893-4745-9dbf-eb158f613e52\\\\\\\\",\\\\\\\\"Quantity\\\\\\\\":{\\\\\\\\"Unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"Value\\\\\\\\":10975.000000},\\\\\\\\"Elements\\\\\\\\":[{\\\\\\\\"ItemId\\\\\\\\":\\\\\\\\"b9d59fe1-8d5b-4bf3-a2fc-9ef0f8215a68\\\\\\\\",\\\\\\\\"Quantity\\\\\\\\":{\\\\\\\\"Unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"Value\\\\\\\\":10975.0},\\\\\\\\"Reservations\\\\\\\\":[]},{\\\\\\\\"ItemId\\\\\\\\":\\\\\\\\"af7c6cd4-59ac-4a3a-b031-2b7592eb702b\\\\\\\\",\\\\\\\\"Quantity\\\\\\\\":{\\\\\\\\"Unit\\\\\\\\":\\\\\\\\"pcs\\\\\\\\",\\\\\\\\"Value\\\\\\\\":439.0},\\\\\\\\"Reservations\\\\\\\\":[]}],\\\\\\\\"SiloItems\\\\\\\\":[]}"}.Kotrak.Common.Application.Exceptions.BusinessLogicException: Production lot with id b85005e1-f436-427f-95cf-da74dd5f25f5 was not found ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: ProductionLotNotFoundMessage at Kotrak.Common.Infrastructure.Extensions.RepositoryExtensions.GetOrThrow[TAggregate](IRepository`1 repository\', \'Comment 49: AggregateId id\', \'Comment 50: String exceptionMessage) at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.GetProductionLotOrThrow(AggregateId productionLotId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 619 at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateReservationsAndConfirmProductionLot(UpdateReservationsAndConfirmProductionLotActionData data) 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) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Plant.Stock.BusinessLogic.Infrastructure.Api.Controllers.ProductionLotController.UpdateReservationsAndConfirmProductionLot(UpdateReservationsAndConfirmProductionLotViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\Controllers\\\\\\\\ProductionLotController.cs:line 140 at lambda_method(Closure \', \'Comment 51: Object \', \'Comment 52: Object[] ) at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target\', \'Comment 53: Object[] parameters) at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 54: ObjectMethodExecutor executor\', \'Comment 55: Object controller\', \'Comment 56: 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 57: Scope& scope\', \'Comment 58: Object& state\', \'Comment 59: 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 60: Scope& scope\', \'Comment 61: Object& state\', "Comment 62: 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) --- End of inner exception stack trace ---{code} !screenshot-1! \'", "Comment 63: \'Dear Eric,Could you please provide us with other examples? How many PLRs per week are impacted more less?Regards\'", \'Comment 64: "hi Team\', "Comment 65: it\'s not about how many", \'Comment 66: but it is about stuck of our operation at factory. we generate PLR by manually to have stock for dispatch. if we have this issue\', \'Comment 67: then customer will wait too long\', \'Comment 68: sometime we to solve this\', \'Comment 69: they wait up to 2-3 hours. Please analysis this!"\', "Comment 70: \'Hi [[email protected]],We will analyse this issue.\'", "Comment 71: \'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 72: \'Hi [[email protected]],Do you have any integration with a PCS system in this plant?\'", "Comment 73: \'Dear [[email protected]],To resolve this issue permamently", \'Comment 74: we need to raise an RCA task. Please\', "Comment 75: confirm if you agree for raising an RCA task.Regards\'", "Comment 76: \'for this", "Comment 77: we do not integrate with PCS system\'", "Comment 78: \'Do you accept raising RCA task?Regards\']"]\nRelated Issues:\n[\'DGS-8330\', \'DGS-8422\', \'DAP-13495\']\n\n### End'}
703	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8328\n\n### Instruction:\nError message when trying to load historical prices\r\n\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-5775\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hello,Please", "Comment 4: verify if you can upload historical prices now.Regards\'", "Comment 5: \'Zrobiony reindex i update statistics", \'Comment 6: Nosipho Teamsem potwierdziła\', \'Comment 7: że dalej wytępuje ten sam error z Timeoutem\', \'Comment 8: sprawdziłam\', "Comment 9: u nas też!image-2023-01-16-12-39-04-827.png!\'", "Comment 10: \'{code:java}2023-01-16 14:09:06,186 [166] ERROR - An unexpected error occurred in service.2023-01-16 14:09:06,186 [166] ERROR - An unexpected error occurred in service.Exception data: HelpLink.ProdName: Microsoft SQL Server", \'Comment 11: HelpLink.ProdVer: 13.00.7016\', \'Comment 12: HelpLink.EvtSrc: MSSQLServer\', \'Comment 13: HelpLink.EvtID: -2\', \'Comment 14: HelpLink.BaseHelpUrl: http://go.microsoft.com/fwlink\', \'Comment 15: HelpLink.LinkId: 20476System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out at System.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 16: Boolean breakConnection\', \'Comment 17: Action`1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 18: Boolean breakConnection\', \'Comment 19: Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 20: Boolean callerHasConnectionLock\', \'Comment 21: Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 22: SqlCommand cmdHandler\', \'Comment 23: SqlDataReader dataStream\', \'Comment 24: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 25: TdsParserStateObject stateObj\', \'Comment 26: Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 27: RunBehavior runBehavior\', \'Comment 28: String resetOptionsString\', \'Comment 29: Boolean isInternal\', \'Comment 30: Boolean forDescribeParameterEncryption\', \'Comment 31: Boolean shouldCacheForAlwaysEncrypted) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 32: RunBehavior runBehavior\', \'Comment 33: Boolean returnStream\', \'Comment 34: Boolean async\', \'Comment 35: Int32 timeout\', \'Comment 36: Task& task\', \'Comment 37: Boolean asyncWrite\', \'Comment 38: Boolean inRetry\', \'Comment 39: SqlDataReader ds\', \'Comment 40: Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 41: RunBehavior runBehavior\', \'Comment 42: Boolean returnStream\', \'Comment 43: String method\', \'Comment 44: TaskCompletionSource`1 completion\', \'Comment 45: Int32 timeout\', \'Comment 46: Task& task\', \'Comment 47: Boolean& usedCache\', \'Comment 48: Boolean asyncWrite\', \'Comment 49: Boolean inRetry) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 50: RunBehavior runBehavior\', \'Comment 51: Boolean returnStream\', \'Comment 52: String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior\', \'Comment 53: String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior) at Dapper.SqlMapper.ExecuteReaderWithFlagsFallback(IDbCommand cmd\', \'Comment 54: Boolean wasClosed\', \'Comment 55: CommandBehavior behavior) at Dapper.SqlMapper.<QueryImpl>d__136`1.MoveNext() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at Dapper.SqlMapper.Query[T](IDbConnection cnn\', \'Comment 56: String sql\', \'Comment 57: Object param\', \'Comment 58: IDbTransaction transaction\', \'Comment 59: Boolean buffered\', \'Comment 60: Nullable`1 commandTimeout\', \'Comment 61: Nullable`1 commandType) at DHCDNRMPriceService.Data.Repository.ReplacementPriceRepository.GetLastAcceptedPrices(Filter filter) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-RMPRICES102-JOB1\\\\\\\\DHCDNRMPriceService.Data\\\\\\\\Repository\\\\\\\\ReplacementPriceRepository.cs:line 52 at DHCDNRMPriceService.Data.DHCDNRMPriceServiceImpl.GetHistoricPriceDocumentsWithPaging(PageRequest`1 request) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-RMPRICES102-JOB1\\\\\\\\DHCDNRMPriceService.Data\\\\\\\\DHCDNRMPriceServiceImpl.cs:line 318 at SyncInvokeGetHistoricPriceDocumentsWithPaging(Object \', \'Comment 62: Object[] \', \'Comment 63: Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance\', \'Comment 64: Object[] inputs\', "Comment 65: Object[]& outputs) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)ClientConnectionId:d1fc5fa2-5e65-4cc6-b518-5c773d771b41Error Number:-2,State:0,Class:112023-01-16 14:09:15,671 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:09:42,021 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:10:10,904 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:10:35,137 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:11:03,299 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:11:27,022 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:11:50,331 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:12:14,789 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:12:41,163 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:13:08,797 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:13:35,182 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:14:01,599 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:14:28,881 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:14:52,203 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:15:19,548 [16] DEBUG - Batch acquisition of 0 triggers2023-01-16 14:15:42,618 [16] DEBUG - Batch acquisition of 0 triggers{code}\'", \'Comment 66: "{code:java}DECLARE @Database NVARCHAR(255) DECLARE @Table NVARCHAR(255) DECLARE @cmd NVARCHAR(1000) DECLARE DatabaseCursor CURSOR READ_ONLY FOR SELECT name FROM master.sys.databases WHERE name IN (\\\'CDNXL_DHFU\\\') -- use this to select specific databases and comment out line aboveORDER BY 1 OPEN DatabaseCursor FETCH NEXT FROM DatabaseCursor INTO @Database WHILE @@FETCH_STATUS = 0 BEGIN SET @cmd = \\\'DECLARE TableCursor CURSOR READ_ONLY FOR SELECT \\\'\\\'[\\\'\\\' + table_catalog + \\\'\\\'].[\\\'\\\' + table_schema + \\\'\\\'].[\\\'\\\' + table_name + \\\'\\\']\\\'\\\' as tableName FROM [\\\' + @Database + \\\'].INFORMATION_SCHEMA.TABLES WHERE table_type = \\\'\\\'BASE TABLE\\\'\\\'\\\' -- create table cursor EXEC (@cmd) OPEN TableCursor FETCH NEXT FROM TableCursor INTO @Table WHILE @@FETCH_STATUS = 0 BEGIN BEGIN TRY SET @cmd = \\\'ALTER INDEX ALL ON \\\' + @Table + \\\' REBUILD\\\' --PRINT @cmd -- uncomment if you want to see commands EXEC (@cmd) END TRY BEGIN CATCH PRINT \\\'---\\\' PRINT @cmd PRINT ERROR_MESSAGE() PRINT \\\'---\\\' END CATCH FETCH NEXT FROM TableCursor INTO @Table END CLOSE TableCursor DEALLOCATE TableCursor FETCH NEXT FROM DatabaseCursor INTO @Database END CLOSE DatabaseCursor DEALLOCATE DatabaseCursor{code}"\', "Comment 67: \'Hello,As per Teams", "Comment 68: I am still getting error messages.!image-2!!image-3!\'", "Comment 69: \'Dear Nosipho,On my side the list is loading now.Please", "Comment 70: verify on your side.Regards\'", "Comment 71: \'!image-2023-01-16-14-23-30-327.png!\'", \'Comment 72: "Also,As Piotr Farynski mentioned in taskDGS-5775:_{color:#0747a6}Hello everyone\', "Comment 73: below you can find some suggestions on what to include in the maintenance plan. It would be the best to run the rebuild twice a week.{color}__{color:#0747a6}EXECUTE dbo.IndexOptimize{color}__{color:#0747a6}@Databases = \'USER_DATABASES\',{color}__{color:#0747a6}@FragmentationLow = NULL,{color}__{color:#0747a6}@FragmentationMedium = \'INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE\',{color}__{color:#0747a6}@FragmentationHigh = \'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE\',{color}__{color:#0747a6}@FragmentationLevel1 = 5,{color}__{color:#0747a6}@FragmentationLevel2 = 30,{color}__{color:#0747a6}@UpdateStatistics = \'ALL\',{color}__{color:#0747a6}@MinNumberOfPages=1,{color}__{color:#0747a6}@OnlyModifiedStatistics = \'Y\',{color}__{color:#0747a6}@FillFactor = 90{color}__{color:#0747a6}Please also consider proceeding with an SQL servers audit", "Comment 74: as there might be a need to create additional indexes. We\'ve provided the cost estimation in ticketDGS-5806.{color}__{color:#0747a6}Please let us know if we can close this ticket or is there anything else you want us to do here.{color}_Please", \'Comment 75: mind above suggestion.Regards"\', "Comment 76: \'HiBoth servers have the index optimization running daily. Note that server 20 failed today/yesterday. !image-1!!image-4!!image-5!!image-6!\'", "Comment 77: \'All right. Then we should treated this issue as incidental case. Please", "Comment 78: let me know if Historical Prices work fine for you and we could close this task.Regards\'", "Comment 79: \'Przed odbudową:!image-2023-01-16-14-50-19-092.png!\'", "Comment 80: \'We are waiting for Purchasing to confirm.\'", "Comment 81: \'Waiting for your feedback then.Regards\'", "Comment 82: \'Hello", "Comment 83: issue has been resolved thank you \'", "Comment 84: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}
704	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8327\n\n### Instruction:\nAlthough we closed some SC\'s in Intense we can still select them when we are registering a SR.\r\n\r\nThis should not be possible.\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Fixed", "Comment 3: now dropdown should work correctly.\']"]\nRelated Issues:\n[]\n\n### End'}
705	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8326\n\n### Instruction:\nWe have a few improvements for the Saldo 2 Pay document:\r\n* Hide the column "Totaal bedrag" on the printout\r\n* Show the expenses in the order:\r\n 1. Invoices related to category Hatchery\r\n 2. Invoices related to Feed\r\n 3. Invoices related to Expenses \r\n\r\n(Maybe later we would like to implement this in other sectors ass well)\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: \'Nie wprowadzamy zmian na starych wydrukach.Dodajemy nowe wydruki (w pierwszej kolejności dla MAS NL)", "Comment 3: na których dodajemy zmiany z opisu taska.\'", \'Comment 4: "[[email protected]]How should we order documents having more than one line with different field \\\'Round Category\\\'?Invoice is shown in 1 row on S2P printout\', "Comment 5: but on Invoice there are 2 lines \'Hatchery\' and \'Expenses\'Should we check that when exist any line from Hatchery it will be treated like Hatchery and shown on printout at first?Similar in other cases when it will be more than 1 round category on invoice. I mean", \'Comment 6: if there will be even one of line from Feed we should treat it like Feed (although there will be other lines with different categories\', \'Comment 7: but not Hatchery which should be treated like Hatchery)?Can we do it with this assumption?There is example of this one from IBIP_DH !image-2023-01-16-12-26-34-869.png!!image-2023-01-16-12-25-26-265.png!"\', "Comment 8: \'Yes", "Comment 9: when it hold a line for hatchery please present it in this category.For feed it is the same.I think we can have situations with elements for Hatchery or Feed with a line for Expenses.\'", "Comment 10: \'New S2P printout is ready on UAT for MAS NL sector - Saldo 2 pay_2 (MAS).Please verify that printout is correct and after that we can also implemented it in MAS BE sector on UAT.!image-2023-01-16-15-53-52-661.png!\'", "Comment 11: \'plik od klienta z opisanym szablonem wydruku S2P[^S2P_new_printout_comments.xls]\'", "Comment 12: \'Uwagi do wydruku po spotkaniu z klientem[^S2P_2_new.xlsx]\'", "Comment 13: \'The last two invoices are credit notes (PCN******). These should be presented with a minus on the S2P and not as positive values.!image!\'", \'Comment 14: \\\'The number after "Ronde:" is not correct. This is the FS number. It should be the "Round number". !image-1!\\\'\', "Comment 15: \'{quote}The last two invoices are credit notes (PCN******). These should be presented with a minus on the S2P and not as positive values.{quote}Now it should be good", \'Comment 16: all values for Slaughtery categories will be multiplied by (-1)\', "Comment 17: then on printout it will be opposite sign than on S2P document.All changes for S2P printout have been made on IBIP_DH_TEST and also on IBIP_DH environment.\'", \'Comment 18: \\\'The closing sentences on the S2P are wrong. Also in PROD.It seems like it says "totaal door u te betalen EUR" all the time right now.\\\'\', "Comment 19: \'Potwierdzone przez Richarda", "Comment 20: że wydruk zaakceptowany i można przystąpić do tworzenia wydruku S2P dla MAS BE.\'", "Comment 21: \'S2P printout for MAS BE sector is ready to verify on test environment (IBIP_DH_TEST)\'", "Comment 22: \'Do przerzucenia także na prod wydruk S2P dla sektora MAS BE\'", "Comment 23: \'S2P printout for MAS BE sector is ready to verify on production environment (IBIP_DH)!https://attachments.office.net/owa/damian.swistek%40kotrak.com/service.svc/s/GetAttachmentThumbnail?id=AAMkADY2ZTAxMzM3LTE0YjctNGI0Ni1hYjIxLWE3MDFjOTVkNmExNwBGAAAAAAA%2FcPjpt4lNRZFonusrO6C9BwA5bA29TyJrQIX6A6F8SkSqAAAAAAEJAAA5bA29TyJrQIX6A6F8SkSqAAS37XAYAAABEgAQAGsrHCgSVJFKmROqYOppr%2FI%3D&thumbnailType=2&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IkQ4OThGN0RDMjk2ODQ1MDk1RUUwREZGQ0MzODBBOTM5NjUwNDNFNjQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiIySmozM0Nsb1JRbGU0Tl84dzRDcE9XVUVQbVEifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiNzQ1YWJkOWJmNWUxNGJhMWJkNjE5OTZmNzhmMzQzNGYiLCJzaWduaW5fc3RhdGUiOiJbXCJrbXNpXCJdIiwidmVyIjoiRXhjaGFuZ2UuQ2FsbGJhY2suVjEiLCJhcHBjdHhzZW5kZXIiOiJPd2FEb3dubG9hZEA5OGIwMzVmZi1iMTIxLTQ1OGItYTNmMC0zMjM1NGRiMWI3ODEiLCJpc3NyaW5nIjoiU0lQIiwiYXBwY3R4Ijoie1wibXNleGNocHJvdFwiOlwib3dhXCIsXCJwdWlkXCI6XCIxMTUzNzY1OTMyMzQ4MzE1MTQ3XCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIixcIm9pZFwiOlwiYjU1MGNmY2EtYjZhYS00NmFkLWFlYjAtZTllNjIyYTMyOTE2XCIsXCJwcmltYXJ5c2lkXCI6XCJTLTEtNS0yMS0zNjk5NTUyNDA4LTIxNDA2MTAxMy0yMzI0NTA4MTctMTMxMDk3OTRcIn0iLCJuYmYiOjE2NzU5Mzk1MjcsImV4cCI6MTY3NTk0MDEyNywiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImhhcHAiOiJvd2EifQ.dtba9dp33xG_er7jRDburybMA50q_i_jZx-F2Af5ZrK9lV692WczTAGdMtwpYNY9bfc58gzlyBTP198DS3le5kDM_s5HHGDd8Yjwp9p9JNU97IPAzYdIbwHJayT5ph3mwswd6EmoJxbB22n6B1dG-FNHr69n_6nC4SReAnlvIJ0gvE7iHQWYDKmeoIDztevaxgAmifgkflzrzZfXAfIV8wIr3TiCUN1qPKz2P9VeJwxpdcrjIETOmfg0GB890vipgkdmVU8nJEn2jF5z4Hm1tRqRJeGEDfe5wx_cTcgUjjmhSNcK-rxV_jwAlbNdfoOPZdQoRY6pYJzTOWRl5Q1R0A&X-OWA-CANARY=fnSOvPkW0UiUcKfpcNKnteBUxV6LCtsYvCupXfc1ldHUij-gCjpTAlQN0TzqLNx33AukEKgJByo.&owa=outlook.office.com&scriptVer=20230127001.12&animation=true!\'", \'Comment 24: "I haven\\\'t heard any complains so I think it works correct"\', \'Comment 25: \\\'Please sort on Invoice data "Factuurdatum". Now it is only sorted on the day and not the full date it looks like.!image-2!\\\'\', \'Comment 26: "It\\\'s adjusted right now on production and test environment in MAS NL and MAS BE and it\\\'s sorted from oldest dates.You can verify on other documents also.!image-2023-02-15-15-24-04-009.png!"\', "Comment 27: \'Confirmed that can be closed.\'", "Comment 28: \'Please re-open", \'Comment 29: we have a new request.Could we use the field "Name abbreviation" for the S2P printout in the column "Referentie" dor the "Eendagskuikens" (read Hatchery) and "Slachterij" ( Slaughteries)? Just as we do on the prinouts for the Financial Statement 2?!image-3!\\\'\', "Comment 30: \'{quote}Please re-open", \'Comment 31: we have a new request.Could we use the field "Name abbreviation" for the S2P printout in the column "Referentie" dor the "Eendagskuikens" (read Hatchery) and "Slachterij" ( Slaughteries)? Just as we do on the prinouts for the Financial Statement 2?!image-3!{quote}Yes\', "Comment 32: we will add displaying these field from customer card instead of name on new S2P printout for Hatchery and Slaughtery sections.\'", "Comment 33: \'[[email protected]],we made modification in test Intense environment.You can verify it.Best regards,Grzegorz\'", "Comment 34: \'Can be moved to PROD.\'", "Comment 35: \'Excuse me", "Comment 36: I still see it is not working properly. !image-4!\'", \'Comment 37: "[[email protected]],where does this example come from? If it comes from the PROD environment\', \'Comment 38: we haven\\\'t moved the modification yet.Best regards,Grzegorz"\', "Comment 39: \'Test", "Comment 40: it is ID79894. \'", \'Comment 41: \\\'We found a mistake in the S2P regarding loans. Please have a look at SP-B/0679.The amount that we need to settle for the loans is not 10.000,- but should be 2.500,- (the column aflossing). Could you please put in the value in column "aflossing" from the S2P document and put this in the column "Openstaand" on the PDF?Please note that the "Totaal" on the bottom of the PDF should be changed as well. \\\'\', \'Comment 42: \\\'The guarantees should be presented in the category "Diversen"\', \'Comment 43: it is on the category "Slachterij" right now.!image-5!\\\'\', \'Comment 44: \\\'{quote}We found a mistake in the S2P regarding loans. Please have a look at SP-B/0679.The amount that we need to settle for the loans is not 10.000,- but should be 2.500,- (the column aflossing). Could you please put in the value in column "aflossing" from the S2P document and put this in the column "Openstaand" on the PDF?Please note that the "Totaal" on the bottom of the PDF should be changed as well.{quote}Please verify righ now,changes have been madeon test and prod environment as well.{quote}The guarantees should be presented in the category "Diversen"\', \'Comment 45: it is on the category "Slachterij" right now.!image-5!{quote}Now guarantees are in \\\\\\\'Diversen\\\\\\\' category. Please veriify.Changes have been made for this on test and prod environment as well.\\\'\', \'Comment 46: "{quote}Test\', \'Comment 47: it is ID79894.{quote}[[email protected]]do sprawdzenia funkcjonalność \\\'Name abbreviation\\\' z komentarza Mitcha"\', "Comment 48: \'This can be closed.\'", "Comment 49: \'There is one more remark which has been adjusted", \'Comment 50: please verify right now. It has been adjusted on test and prod environment - name abbreviation should be displayed on printout intead of reference full name.{quote}Excuse me\', \'Comment 51: I still see it is not working properly.!image-4!{quote}If it will be confirmed\', "Comment 52: we can close the task.\'", "Comment 53: \'Can be closed.\']"]\nRelated Issues:\n[\'DGS-8067\', \'DGS-8907\', \'DGS-8459\']\n\n### End'}
706	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8325\n\n### Instruction:\nWe would like to be able to indicate with a checkbox on the Financial Statement if a certain element must be printed on the Financial Statement printout.\r\n\r\nBy default this checkbox should be checked on.\r\n\r\nSome more content: it can happen that we make a mistake and make a credit for it. Than the balance of these two elements is zero. One must be able to decide not to show this on the FS.\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\\\'s related only to the new version of FS printouts from DGS-8215\', \'Comment 3: so old versions should be still without these rules."\', \'Comment 4: "On Financial Statement document it\\\'s not possible to add checkbox\', \'Comment 5: because there are only lists which we cannot edit in any way (only add or remove columns and specify conditions what could be displayed on list\', \'Comment 6: but not any additional actions like mark a checkbox).Is it only related to credit and credited invoices and should be possible display or not that kind of invoices?Maybe some solution will be if we add parameter to the printout and if someone select proper printout there will be window only with credit invoices and credited invoices which will be possible to mark (the view will be more clearer if there will be only that kind of invoices instead of all invoices)? If user will mark invoices\', \'Comment 7: these invoices will not show on printout.Steps: # Select type of printout # Provide parameter values # Mark invoices you don\\\'t want to see on printoutSome kind of mockup below. !image-2023-01-18-11-02-08-176.png!"\', "Comment 8: \'It is related to all invoices. In theory all elements on the printout could be hidden by the users.A window is a good idea. However in that case is should be like a table with a checkbox to include or exclude the element on the printout. Your mock-up looks good.\'", \'Comment 9: "Does it means that every element (line of invoice) should be possible to hide from all sections of the printout (not only credit and credited invoices): * Total DOCs * Total Feed * Total Slaughtery * Miscellaneous Slaughtery * Total Expense * Total Loans?What columns should we display to mark documents which shouldn\\\'t be visible. I think too many columns could be inconvinient in this widow\', \'Comment 10: but we could also display all of columns which are visible on Financial statement document.!image-2023-01-19-09-48-14-523.png!"\', "Comment 11: \'Indeed", \'Comment 12: it should be possible to hide very element from the printout in all sections.In the columns I would like to see the amount\', \'Comment 13: the document number\', \'Comment 14: the item code\', \'Comment 15: the weight\', "Comment 16: the quantity and the document date.\'", \'Comment 17: "Additional requirement:All elements that are turned off on the printout shouldn\\\'t be in the technical results calculation as well.Please let me know whether you need more information about this."\', \'Comment 18: "Regarding to this\', "Comment 19: because it\'s more complex:{quote}Additional requirement:All elements that are turned off on the printout shouldn\'t be in the technical results calculation as well.Please let me know whether you need more information about this.{quote}Technical results should be calculated without hide elements (marked by user elements)", "Comment 20: right?In that case we need to add new procedure or call this procedures with other parameters (without hide elements) to recalculate tech results before printout.Then we will calculate on the fly these values for technical results (values won\'t be saved anywhere", \'Comment 21: only calculate and taken on printout).Is it the way how we should do it?"\', "Comment 22: \'Indeed", "Comment 23: technical results should be calculated without hide elements marked by user.The culculations should be stored in the system as well. These are the calculations that are relevant at that moment.In theory when someone hides another element the calculations must be done again and these values must be stored. Is this clear?\'", \'Comment 24: "Does it means that should it worked like that:Example: # Someone selects printout of Financial statement (after caluclation of technical result on FS document by button \\\'Calculate Technical Results\\\') # Someone else selects printout of Financial statement with hiding 2 invoices ## System calculates technical results without these 2 invoices ## Printout shows technical results values without these 2 invoices ## System calculates technical results without these 2 invoices and stored it on FS document (system overwrite data on Tech Results tab on FS) # When someone opens this FS document values on Tech Results tab will be like on the last printout call up (only in case when someone will use button \\\'Calculate Technical Results\\\' values will recalculate again without hided before 2 invoices)Is that solution which is needed?On document in that case we don\\\'t know what elements were hidden when someone made a printout or should we register which documents were hidden by user when printout was called last time. Then maybe we do it in other way and add some table with elements for FS to hide on printout and user should at first select elements to hide and save document and then select printout without any parameters."\', "Comment 25: \'1", "Comment 26: 2 and 3 are indeed correct.What was hided by the users should be visible on the documents as well. When I open the document the next time I should be able to see what I or my collegues needed.\'", \'Comment 27: "It\\\'s done on test and prod environment.It works on new printouts of Financial statements in MAS NL and MAS BE.!image-2023-02-10-11-07-51-460.png!"\', "Comment 28: \'Could you explain to me how it works? Do I need to hide them from technical results? Will it than not appear on the printouts?\'", \'Comment 29: "It works like that: # Select and marked lines from Financial statement in field \\\'Elements to hide for calculations\\\'!image-2023-02-10-14-17-31-114.png! # Calculate results by button \\\'Calcualate Technical Results\\\' - calculations will be without selected lines in step 1!image-2023-02-10-14-22-47-448.png! # Printout (new one) - printout will be without selected lines in step 1!image-2023-02-10-14-23-30-317.png!"\', \'Comment 30: \\\'I have few remarks. We need:* Headers with information* To add a column with "Item description"* To add a column with "Net value". Maybe there is one right now but due to the missing headers I don\\\\\\\'t see it.!image-1!\\\'\', \'Comment 31: "Unfortunately we\\\'re not able to add a headers for column (it\\\'s Intense restriction that in this type of field - multiselect it\\\'s not possible).We can only add some text before each column (or before some columns) and it could look like that:!image-2023-02-14-14-07-31-942.png!Is it ok for you? You can provide us what text should be before each column and we can put this text before value of each column."\', "Comment 32: \'Ok", \'Comment 33: you can do it like this\', "Comment 34: Please use the header columns as texts for now.\'", "Comment 35: \'[[email protected]],the modification ready on test environment", \'Comment 36: you can feel free to test (MAS NL\', "Comment 37: MAS BE).Best regards,Grzegorz\'", "Comment 38: \'Do dodania na grid lookupie kolumna z NetValue.\'", "Comment 39: \'[[email protected]]Column with Net Value has been added to the lookup list.!image-2023-02-24-12-45-43-730.png!\'", "Comment 40: \'I have excluded the invoice line for SLAC for PI-RLM/2022/0704. The net value indeed is deducted from the Feed profit. However the quantity and the weight should be distracted from the numbers in the category First Loaders. However nothing seems to be changed in here. Could you check this? !image!\'", \'Comment 41: "I\\\'ve checked procedure for calculating technical results and indeed some values won\\\'t change when you exclude this PI or other invoices.Some values for calculations are taken from Slaughtery Report documents\', \'Comment 42: not from invoices\', \'Comment 43: for example these fields: * Numbers of first loaders (quantity) * Weight of first loaders (in kg) * Average weight first loaders * Numbers of all loaders (quantity) * Weight of all loaders (in kg) * Average weight all loadersIn this case calculations will be the same if invoices will be excluded."\', \'Comment 44: "Than we should be able to somehow exclude the SR\\\'s as well.Otherwise let\\\'s assume that we have an SR with 1.000 units and 2.500kg. From this SR a SI to the slaughter and a PI to the farmer are created. If on the Financial Statement the PI is excluded than the numbers from the SR should not be in the calculations as well.Could you think about a solution to do so?"\', "Comment 45: \'What is the status of this?\'", \'Comment 46: "{quote}Than we should be able to somehow exclude the SR\\\'s as well.Otherwise let\\\'s assume that we have an SR with 1.000 units and 2.500kg. From this SR a SI to the slaughter and a PI to the farmer are created. If on the Financial Statement the PI is excluded than the numbers from the SR should not be in the calculations as well.Could you think about a solution to do so?{quote}I think the only solution to do it\', \'Comment 47: is to rebuild procedure of calculate Technical Results.It will be needed to take linked from excluded invoices linked to SR.How should we excluding values if from SR is generated PI and SI and if someone will exclude only one of invoices (SI or PI). Should be excluded values from this SR if any of invoices (SI or PI) will be excluded from the list?This is how are documents linked:MAS NL - SR -> SI -> PIMAS BE - SR -> PI -> SIin both sectors PI is always displayed on Rounds\', \'Comment 48: FS and we should base on these invoicesThis changes will have impact on performance of calculating technical results - it could slow down when we need to excluding and looking for excluding values."\', "Comment 49: \'[[email protected]] - Mitch chciał", \'Comment 50: żeby najpierw przenieść tą funkcjonalność do wszystkich sektorów poza MAS NL i MAS BE.W MAS NL i MAS BE musimy przemyśleć i sprawdzić jak to zrobić sensownie z kalkulacją Technical Results\', "Comment 51: więc te sektory dopiero później.!image-2023-03-23-10-27-10-088.png!\'", "Comment 52: \'To move to production environment for all sectors without MAS NL and MAS BE.In this case there is needed to rebuilt technical results calculation", "Comment 53: so we need to discuss it and find solution how to do it safely.Changes in technical results are related also to tasks:[https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8714][https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8675]\'", \'Comment 54: \\\'Please not that this functionality is presented right now on the tab "technical results". We don\\\\\\\'t see this tab in sectors other than MAS. Could you please move this functionality to the general tab? That one is visible in all sectors.\\\'\', "Comment 55: \'[[email protected]]but new FS printouts now are only created in MAS NL and MAS BE and it works only here.How it should works for other sectors? Should it be applied to old versions of printouts?\'", "Comment 56: \'Yes", "Comment 57: it should work like this for the old version of the printouts as well.\'", "Comment 58: \'What is the progress in this?\'", "Comment 59: \'[[email protected]],the modifications have been added into Financial Statement for two sectors NAS and LAS in TEST Intense environment.We are focusing on other sectors right now.Best regards,Grzegorz\'", "Comment 60: \'For NAS and LAS in can be moved to PROD.\'", "Comment 61: \'[[email protected]],next sector PAS with FS print is ready to tests.Best regards,Grzegorz\'", "Comment 62: \'[[email protected]],next sector OPPAS with FS print is ready to tests.Best regards,Grzegorz\'", "Comment 63: \'[[email protected]],next sector VAS with FS print is ready to tests.Best regards,Grzegorz\'", "Comment 64: \'* Do skopiowania wydruki FS dla sektorów opróczMAS NL i MAS BE z test i do podmienienia databasename w parametrach wydruku * Do dodania przy definicji akcji wydruku parametr Dontshowids * Do przeniesienia procedury z test na prod dotyczące lookupów na FS!image-2023-03-31-14-35-31-274.png! * Do przeniesienia procedury z test na prod procedury dotyczące wydruków FS innych niż MAS NL i MAS BE!image-2023-03-31-14-32-23-402.png!\'", "Comment 65: \'Mitch van Bovene6 dagen geleden 11:53For NAS and LAS in can be moved to PROD.Please move it to the PROD for the NAS.\'", "Comment 66: \'New function of printouts in NAS moved to production.\'", "Comment 67: \'[[email protected]]please let us know if we can move to prod environment other sectors.For now only NAS is on production database.\'", \'Comment 68: "To move on Prod environment solution for sector LAS\', \'Comment 69: VAS\', \'Comment 70: OPPAS/PAS.For MAS NL and MAS BE is needed to handle technical results\', \'Comment 71: when it will be done we\\\'ll inform you that is ready for tests."]\']\nRelated Issues:\n[\'DGS-8215\', \'DGS-8732\', \'DGS-8877\', \'DGS-8526\']\n\n### End'}
707	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8324\n\n### Instruction:\nIt should not be possible to send to archive invoice in which "booked on one side" is not marked and there is no invoice linked to.\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'!image-2023-01-13-12-24-34-659!\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'{color:black}This is a good approach{color} {color:black}😊{color}{color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Ewa Mucha (Jira) <[email protected]> Verzonden: vrijdag 13 januari 2023 12:26 Aan: Jong", "Comment 5: Christine de <[email protected]> Onderwerp: DGS-8324 NAS -Regular SI/PI invoice without a linked invoice cannot be archived \| {color:white} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} \| !image006!\'", "Comment 6: \'Done at UAT redy to test\'", "Comment 7: \'dodana nowa funkcja dla nasa [dbo].[KR_InvoicesFlowCondtionNasArchived] dla przepływów archived\'", "Comment 8: \'[[email protected]]do dodania tekst informujący dlaczego nie można wykonać przepływu do archiwum.\'", "Comment 9: \'Dodana walidacja komunikatu wyświetlanego na przepływie do archiwum w NAS\'", "Comment 10: \'This works good. Can be deployed to PROD.\'", "Comment 11: \'[[email protected]]sprawdzisz i poprawisz? Wygląda na to", \'Comment 12: że tylko te dokumenty z pierwszego wiersza są możliwe do zarchiwizowania\', \'Comment 13: powinno dać się także wysłać do archiwum dokumenty z 2 wiersza\', \'Comment 14: czyli te 2 typy ze screenu.Przykładowy dokument z IBIP_DH\', "Comment 15: które nie są teraz w stanie zarchiwizować - ID89679!image-2023-01-26-10-13-59-062.png!\'", "Comment 16: \'Poprawione\'", "Comment 17: \'Can you confirm me", "Comment 18: that its all ok?\'", "Comment 19: \'{color:black}Dear Tomasz,{color} {color:black}{color} {color:black}I can only check this when a “case” appears..{color} {color:black}Not able to test this now", \'Comment 20: so remark this as done.{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Tomasz Zygoń (Jira) <[email protected]> Verzonden: dinsdag 7 februari 2023 11:32 Aan: Jong\', "Comment 21: Christine de <[email protected]> Onderwerp: DGS-8324 Ready for UAT tests - NAS -Regular SI/PI invoice without a linked invoice cannot be archived \| {color:white} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} \| \']"]\nRelated Issues:\n[\'DGS-8081\']\n\n### End'}
708	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8323\n\n### Instruction:\nHi\r\nW tym tygodniu mamy już 2 przypadki, w których mamy rozbieżność na pozycjach vt w dhp i w dhc. Proszę o zbadanie sytuacji, bo my nic nie wyłapaliśmy.\r\n\r\nRafał Boniecki\n\n### Response:\n["Comment 1: [\'[^WZ Z CDN.pdf] _(535 kB)_[^WZ Z DHP.pdf] _(515 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'And the previous issue...!image!\'", "Comment 4: \'[^scan_20230111151021.pdf] _(720 kB)_\'", "Comment 5: \'{code:java} select distinct ve.VtE_No,vter.* from dbo.VehicleTicketHeader v inner join [dbo].[VehicleTicketElement] ve on ve.VtE_VtHId=v.VtH_Id inner join dbo.registermappings r on r.RgM_VtEIdRelease=ve.vte_id inner join dbo.VehicleTicketElementRelease vter on vter.VeW_VtEId=ve.VtE_Id where VtH_Id=224267 and ve.VtE_ArtId=12573{code}!image-2023-01-16-19-49-22-264! !image-2023-01-16-19-50-04-124!\'", "Comment 6: \'I checked 282/1/2023/l and Problematic barcode:27-66GUI !screenshot-1! This barcode should be related with VT element number 21. !screenshot-2! missing element has been imported.\'", \'Comment 7: \\\'what do you mean "Problematic barcode"? What happened and how we can prevent such situations in the future? it is unacceptable that the system does not generate complete documents\\\'\', "Comment 8: \' !screenshot-3! wydanie palet w tym samym momencie.\'", "Comment 9: \'In general", "Comment 10: the topic concerns discrepancies in barcodes linked to the VT element.We check on the plant side:VehicleTicketElementRelease table,The RegisterMappings table after the RgM_ReleaseVtEId column.If discrepancies in codes are found in the tables it is necessary to determine which barcodes were issued within a given VT element and unify the mapping.VT-282:RGM_parrentid 28283747 has releases for elements VTE_id (915414,915377) but should only for Vte_id=915414VT-166:RGM_parrentid 28314514,28314511 have release for one VT element 914924 but should for element vte_id =914915.If an RgM_Id (bag) is indicated that has an RgM_ParrentId then the barcode (pallets) should also be issued under such VTE. \'", "Comment 11: \' select * from dbo.RegisterMappings where RgM_VtEIdRelease in(914924,914915)\\\\t select * from dbo.RegisterMappings where RgM_VtEIdRelease in(915414,915377)\'", "Comment 12: \'Piotr", \'Comment 13: we know it and know how to correct in the system\', "Comment 14: but the question is what happened and why? WMO look properly\'", "Comment 15: \'We can create RCA for analysis. Please confirm.\'", "Comment 16: \'how many hours do you need for analysis?\'", "Comment 17: \'Could you answer?\'", "Comment 18: \'Hi", "Comment 19: we need 4 hours for analysis. Please confirm.\'", "Comment 20: \'Confirm.\'", "Comment 21: \'Hi", "Comment 22: RCA DGS-8435 has been created.\'", "Comment 23: \'This ticket has been closed", "Comment 24: further realization will be in RCA DGS-8435.\']"]\nRelated Issues:\n[\'DGS-8435\']\n\n### End'}
709	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8322\n\n### Instruction:\npls check\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-01-13 11:31:09 (59fb871c-0006-4307-ac22-00b70e539595/Plant.Prod.BusinessLogic/VNPCT-TS01/31076/181) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 4: "host": { "Value": "10.84.165.11:83"\', \'Comment 5: "HasValue": true\', \'Comment 6: "Host": "10.84.165.11"\', \'Comment 7: "Port": 83 }\', \'Comment 8: "path": "/api/productionLot/update"\', \'Comment 9: "queryString": []\', \'Comment 10: "requestBody": "\\\\\\\\{\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"substitutes\\\\\\\\":[],\\\\\\\\"recipeElementId\\\\\\\\":2,\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"35b2793f-d4d7-4f04-8c05-f014d6af8fcc\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":500}}],\\\\\\\\"executions\\\\\\\\":[\\\\\\\\{\\\\\\\\"elements\\\\\\\\":[{\\\\\\\\"itemId\\\\\\\\":\\\\\\\\"9b6e499c-f370-49bc-8a19-a950a4109d04\\\\\\\\",\\\\\\\\"recipeElementId\\\\\\\\":1,\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"pcs\\\\\\\\",\\\\\\\\"value\\\\\\\\":50}}],\\\\\\\\"readyProductId\\\\\\\\":\\\\\\\\"5022b834-8d23-4d2b-9fcf-eb730a0d912f\\\\\\\\",\\\\\\\\"packingRecipeId\\\\\\\\":\\\\\\\\"57d24018-0797-43dd-8287-fcd71b1488c8\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":\\\\\\\\{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":500},\\\\\\\\"requestedQuantity\\\\\\\\":\\\\\\\\{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":500},\\\\\\\\"expiryDate\\\\\\\\":\\\\\\\\"2023-07-11T07:11:37.069Z\\\\\\\\"}],\\\\\\\\"reservations\\\\\\\\":[\\\\\\\\{\\\\\\\\"deliveryId\\\\\\\\":\\\\\\\\"b774eee9-df3d-4d05-889a-9a2e27cbcb6b\\\\\\\\",\\\\\\\\"stockUnitId\\\\\\\\":\\\\\\\\"19ac64dc-7fef-46a3-b24e-57dacfb304cf\\\\\\\\",\\\\\\\\"quantity\\\\\\\\":{\\\\\\\\"unit\\\\\\\\":\\\\\\\\"kg\\\\\\\\",\\\\\\\\"value\\\\\\\\":500}}],\\\\\\\\"productionLotId\\\\\\\\":\\\\\\\\"511f2425-9d8f-4081-bda8-91b8f6f97d07\\\\\\\\",\\\\\\\\"recipeId\\\\\\\\":\\\\\\\\"57d24018-0797-43dd-8287-fcd71b1488c8\\\\\\\\",\\\\\\\\"labelId\\\\\\\\":null,\\\\\\\\"productionOrderId\\\\\\\\":\\\\\\\\"4b2c6089-bc36-4b72-aebd-c64173d1b20c\\\\\\\\",\\\\\\\\"shiftNumberId\\\\\\\\":\\\\\\\\"4723a183-8aa0-4d63-a309-21beb277ee3b\\\\\\\\",\\\\\\\\"description\\\\\\\\":\\\\\\\\"CA 1\', \'Comment 11: 12/01/2023\\\\\\\\",\\\\\\\\"statusChange\\\\\\\\":3}"}.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 ---\\\'\', "Comment 12: \'Please try again\'", "Comment 13: \'not yet\'", "Comment 14: \'not successfull\'", "Comment 15: \'can you check one more time?\'", "Comment 16: \'!image-1!\'", \'Comment 17: "był unit mismatch poprawiłam z pcs. na pcs w tych 2 miejscach--update [DHPlantPCSBusinessLogicMain].[dbo].[Items] --set ItemBaseWeightUnit=\\\'pcs\\\' --where id=\\\'9b6e499c-f370-49bc-8a19-a950a4109d04\\\'--update --StockUnits --set QuantityUnit=\\\'pcs\\\' --where --ItemId=\\\'9b6e499c-f370-49bc-8a19-a950a4109d04\\\'"\', "Comment 18: \'please try now\'", \'Comment 19: "--update UnitLoads --set QuantityUnit=\\\'pcs\\\' --where id=\\\'A96E702D-F44A-413B-A746-DD22EEF5C038\\\'"\', "Comment 20: \'i confirmed succesfully now. I would like to know about resolution. \'", "Comment 21: \'There was a problem with unit mismatch for raw materialBGCA00010 it has stock unit created by ani-330 where some was used wrong unit pcs. instead of pcsI can see that the view of stockunit or this item is not avaible form the app", \'Comment 22: we may look at this if you wish\', \'Comment 23: but could we change the priority for p2?I also find other items with mismatches there are 22 of them\', "Comment 24: please verify it ( the last column is for unit in pcsmodule)\|id\|wmsbaseunit\|code\|stockbu\|ItemBaseWeightUnit\|\|FF58ACDC-DFD4-49E8-A66E-2185CB6CB0A1\|pcs.\|BS595030\|pcs\|pcs.\|\|2A9CFC5B-59AD-431B-8BDF-581E75C1C410\|pcs.\|BN879905\|pcs\|pcs.\|\|0A2B2F09-57FC-40E8-8B70-998A38FC1D74\|pcs.\|BN383025\|pcs\|pcs.\|\|3614113F-6C26-4D01-923D-ABA4AC49F305\|pcs.\|BS511525\|pcs\|pcs.\|\|3D43C0D7-27C2-4A3B-B584-1C0A2EA20188\|pcs.\|BS595030C\|pcs\|pcs.\|\|B21B524E-D5DE-4A53-A112-0BDF8E8A43D8\|T\|TEEST\|T\|kg\|\|FD99F5EC-DE89-4AE6-AC00-3D90BFE1A6C6\|pcs.\|BBAGWASTE10\|pcs\|pcs.\|\|B8CBD972-4EA6-40B4-9A28-9553539FB28E\|pcs.\|BS752825\|pcs\|pcs.\|\|AF7C6CD4-59AC-4A3A-B031-2B7592EB702B\|pcs\|BPEY00002\|pcs\|pcs.\|\|0F6FBDE7-8BAB-44AD-A2E3-7021049E5F22\|pcs.\|BPEY00787\|pcs\|pcs.\|\|DEAF1AED-B465-466F-9057-DD3AE7E773F9\|T\|Fail\|T\|kg\|\|24033C1C-A097-4EF3-A6EA-7723E09ADB58\|pcs.\|BS511325\|pcs\|pcs.\|\|0B23E073-FBC9-49EB-9117-83623F59F7EA\|pcs.\|BSBESTTOM20\|pcs\|pcs.\|\|53DF9394-E306-4A85-B3CF-D0ED169D7F16\|pcs.\|BSBESTTOM10\|pcs\|pcs.\|\|E088E3DB-5835-4165-9B2D-092EFCE82C98\|pcs.\|BBAGWASTE20\|pcs\|pcs.\|\|45E1D250-1F65-41F3-B228-98AF66E44230\|pcs.\|BS9222ML20\|pcs\|pcs.\|\|4EEF3029-EEFC-409A-A0FD-2E0F67C4B476\|pcs.\|BS394025SVT\|pcs\|pcs.\|\|E90E00D3-BA04-4982-B434-107C2D7F9346\|T\|FAIL2222\|T\|kg\|\|6DD95153-209F-4ABC-8E9F-510A384A5081\|T\|FAIL111\|T\|kg\|\|670C7CE8-20C1-40BF-9A1F-55A48F8406E4\|pcs.\|BS762225T\|pcs\|pcs.\|\|9B563B6D-4F9C-485D-A296-8178B5F683E9\|pcs.\|BNSTICKER9801S\|pcs\|pcs.\|\|A30BAC50-A2A7-43A8-876E-B8E33B57E12B\|pcs.\|BS511725\|pcs\|pcs.\|\'", "Comment 25: \'sure", "Comment 26: we need to change back to P2 and thank you very much for explanation below.i think in can understand whole picture. \'", \'Comment 27: "-select QuantityUnit from [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseStocktakingElements]-select QuantityUnit from [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseStocktakingElements]-- where ItemId=\\\'9b6e499c-f370-49bc-8a19-a950a4109d04\\\' --update [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseStocktakingElements] --set QuantityUnit=\\\'pcs\\\' --where ItemId=\\\'9b6e499c-f370-49bc-8a19-a950a4109d04\\\' ----select QuantityUnit from --update [DHPlantStockBusinessLogicMain].[dbo].[Deliveries] --set QuantityUnit=\\\'pcs\\\' --where id=\\\'326BBF3C-C1EB-4064-B2CC-41C290A55876\\\' -- --select QuantityUnit FROM -- update [DHPlantPCSBusinessLogicMain].[dbo].[Deliveries] -- set QuantityUnit=\\\'pcs\\\' -- where id=\\\'326BBF3C-C1EB-4064-B2CC-41C290A55876\\\' -- -- select QuantityUnit FROM --update [DHPlantWmsBusinessLogicMain].[dbo].[StockUnitReleases] --set QuantityUnit=\\\'pcs\\\' --where id=\\\'B01FA663-C8B7-446F-B5FB-5894B9B2E6D4\\\' and no= 1"\', \'Comment 28: "update [DHPlantStockBusinessLogicMain].[dbo].[StockUnitIntakes] set quantityunit=\\\'pcs\\\' where id=\\\'B01FA663-C8B7-446F-B5FB-5894B9B2E6D4\\\'"\', "Comment 29: \'Ok więc plr się dało potwierdzić", \'Comment 30: po kolejnych poprawach jednostke na bazach jak w internalu da się wejsc w stock unit itema w aplikacji i w delivery w aplikacji jednak przy próbie wyświetlenia itema\', "Comment 31: w module stock nadal jest error prośba o podpowiedź co to jeszcze można poprawić :w logu usługi nadal jest ino o mapowaniu jednostek !image-2023-01-13-14-21-00-003.png!\'", \'Comment 32: \\\'Już jest okej :)!image-2023-01-27-08-58-30-250.png!Item ten miał błędny unit - wszędzie zamiast kg miał pcs (takiego nie ma) - dlatego waliło błędem z unit mismatch (poprawiłem w vc,stock,wms).Oprócz tego poprawiłem BaseUnity na reszcie tych itemów gdzie zamiast pcs było "pcs." w modułach wms,stock,vc.Niech sprawdzą\', "Comment 33: powinno być okej.Na przyszłość pamiętać żeby nie zmieniać danych z kolumny Unit bo ta tyczy się tylko tego czy to są kg czy tony.\'", "Comment 34: \'May we close the task?\'", "Comment 35: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 36: please raise another task.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
710	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8321\n\n### Instruction:\nHi\r\n\r\nWe have the following SO/s\r\nSO-113/23/UMR \r\nSO-117/23/UMR <--Priority 1\r\nSO-137/23/UMR\r\n\r\nBagged products give the attached error/ when trying to create/confirm a PrO\r\n\r\nRegards\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: \'Something strange on the recipe execution !image-2!\'", "Comment 4: \'!image-2023-01-12-21-54-35-255.png!\'", "Comment 5: \'I created the unconfirmed PRO 350 for so -117 - cehck if you are able to confirm.!image-2023-01-12-22-15-21-624.png!\'", "Comment 6: \'[^workaround.docx]\'", "Comment 7: \'For other SO please try ma workaround :[^workaround.docx]\'", "Comment 8: \'!image-2023-01-12-22-24-38-465.png!\'", "Comment 9: \'According to teams conversation I set this to p2\'", "Comment 10: \'Mamy obejscie pytanie dlaczego do pro zapisuja sie 2 pozycje jedna na ilosc z zamowienia w bba druga jako bulk,\'", "Comment 11: \'Let us know if you will be able to create next to PRO using workaround.\'", \'Comment 12: "Hello\', "Comment 13: In reference to yesterday\'s task", "Comment 14: I am sending information about the reason for which there was a communication and why the item was implicitly added to the PRO as bulk.The reason is based on configuration theattributeBatch size establishment policy in umlass is set as Default:\'!image-2023-01-13-08-10-38-719.png!and defailt batch size is set for 3000!image-2023-01-13-08-13-08-942.png!So if order element is as for example 2000 from default 2 position are added 1 for quantity from the order and 1 for missing quantity from (3000x7)-2000", \'Comment 15: what is regular functionality.like in the case with order 217In that situation if you wish to hare weight diffrent from default you may also change values in batch size ans batch count fields !image-2023-01-13-08-18-06-677.png!Also If you prefere You may change product configurationBatch size establishment policy to calculated.Are these explanations sufficient and thetask can be closed?"\', \'Comment 16: "You may close the ticket. It\\\'s understood."\', "Comment 17: \'https://helpdesk.kotrak.com/browse/GDC-803\']"]\nRelated Issues:\n[]\n\n### End'}
711	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8320\n\n### Instruction:\nPlease validate data report "DGS-6413 RAPORT DO PIT 11". \n\n### Response:\n["Comment 1: [\'!image-1![^podatek dochodowy 2022-1.xls] _(34 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'From: Monika Biśta Sent: Friday", \'Comment 4: January 13\', \'Comment 5: 2023 11:49 AM To: Kucharska\', \'Comment 6: Adrianna <[email protected]> Subject: RE: Zgłoszenie - prośba o poprawę raportu do weryfikacji podatku dochodowegoPodegrałam nową wersję wydruku. Prośba o weryfikację.Pozdrawiam / Best regards,Monika Biśta mobile: +48538212 162tel.: +48 3235 12721e-mail: [[email protected]\|mailto:[email protected]]Kotrak S.A.Parczewskiego 2540-582 KatowicePolandtel./phone: (+48 32)35 12700[www.kotrak.com\|https://kotrak.com/]Certified ISO 9001:2015++Sąd Rejonowy / District Court Katowice-Wschód w Katowicach Wydział VIII Gospodarczy KRS\', \'Comment 7: nr KRS: 0000704357NIP: 954-24-96-628 Regon: 277683949Kapitał zakładowy / Share capital: 1.052.700,00 zł\', \'Comment 8: opłacony w całości / paid in fullLokalizacje / Locations: Kraków\', \'Comment 9: Łódź\', \'Comment 10: Warszawa\', \'Comment 11: Opole\', \'Comment 12: Bielsko-Biała\', \'Comment 13: Gdańsk\', "Comment 14: London\'", "Comment 15: \'I asked Adrianna to verifie new version.\'", "Comment 16: \'Data looks correct", \'Comment 17: task to close."Bardzo dziękuję za szybką pomoc Pani Monice oraz Pani Ani." :)\\\']\']\nRelated Issues:\n[]\n\n### End'}
712	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8319\n\n### Instruction:\nproblem with production\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Please verify.\'", "Comment 4: \'confirmed", \'Comment 5: it works\', "Comment 6: task to bo closed\']"]\nRelated Issues:\n[]\n\n### End'}
713	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8318\n\n### Instruction:\nImagine we have this situation:\r\n* a customer has a contract and the second round has been created from it\r\n* a user realises that we should register a new contract for this customer\r\n* the round created in the first step is deleted and removed from the system\r\n* A new round is created from the new contract created in step 2.\r\n\r\nWhat we see is that the new round has round number 3, however it should have been 2 because the other round has been deleted and removed from the system. \r\nIf a document is deleted then the number should be available for the next round. Of course only if the next round is an ascending number. So not that when round 2 is removed and round 4 has been active for longer, the next round will get round 2 again.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Do you have example of it? Is the round number refer to \\\'Round number\\\' field not to \\\'Full Round Number\\\'?\\\'Round number\\\' field on Round is counted by number of all round for the Customer.!image-2023-01-18-12-21-53-651.png!In case when 1st round was created\', \'Comment 3: next 2nd round was created and then 2nd round has been deleted\', \'Comment 4: the next round will get number 2 because exists only 1 round for this customer. This scenario should be good and numerating counts properly.In case when: * 1st round was created (id 1) * 2nd round was created (id 2) * 3rd round was created (id 3) * 2nd round was removed (id 2) * next round is created (now there are 2 round for customer)\', \'Comment 5: so this is 3rd round and document will get \\\'Round number\\\' = 3 (id 4)two rounds (id 3 and id 4) get the value 3"\', "Comment 6: \'It is about round number indeed.Steffen mentioned it. Do you have an example?I think you should be able to test it in the test environment as well. It is like this:•\\\\t1st round was created (id 1)•\\\\t2nd round was created (id 2)•\\\\t2rd round is deleted •\\\\tNew round is created (riund number will be 3 but should be 2)\'", \'Comment 7: "https://helpdesk.kotrak.com/browse/DHNLC-1142tubyła obsługa aktualizowania rundy\', \'Comment 8: ale zdaje się\', "Comment 9: że aktualizujemy tylko \'Full round number\' na SR i fakturach", \'Comment 10: a powinno się także aktualizować pole \\\'Round number\\\' !image-2023-01-20-11-52-28-248.png!"\', "Comment 11: \'What is the current status?\'", \'Comment 12: "I think it will be ready today for UAT tests.Our solution is to create action for users which handle renumber Round documents. Action will renumber documents in order of date of creation documents.{quote}In case when:{quote} * {quote}1st round was created (id 1){quote} * {quote}2nd round was created (id 2){quote} * {quote}3rd round was created (id 3){quote} * {quote}2nd round was removed (id 2){quote} * {quote}next round is created (now there are 2 round for customer)\', "Comment 13: so this is 3rd round and document will get \'Round number\' = 3 (id 4){quote}In this case system will renumber documents and update existing round numbers on Round documents for customer (numeration when round is created is counted by customer).1st will be 1 (id 1)2nd will be 2 (id 2)3rd will be 3 (id 4){quote}I think you should be able to test it in the test environment as well. It is like this:• 1st round was created (id 1)• 2nd round was created (id 2)• 2rd round is deleted• New round is created (riund number will be 3 but should be 2){quote}I tested it", \'Comment 14: but in this case it work properly. If there are 2 rounds\', \'Comment 15: and 2nd was deleted the new one will get number 2 (not 3).Issue that we have is this case (also Steffen reported to me). It happens when someone create round to old contract\', \'Comment 16: then create round to new contract and realize that round for old contract should be deleted.Users are able to delete Round and Feed sale documents when documents are in their Inboxes\', "Comment 17: but numeration is like this below.-----additional topic connected to Round numbersDue to this also invoices and slaughtery reports gets a number of round (which takes number from Round). Should we also extend action from task https://helpdesk.kotrak.com/browse/DHNLC-1142?By using this action only field \'Full number\' is updated. Fielrd \'Round number\' on Round is not updated. Als Sales Invoice", \'Comment 18: Purchase Invoice\', \'Comment 19: Slaughtery Reports connected to round these field on screen below are not updated right now.!image-2023-01-24-09-35-36-267.png!"\', "Comment 20: \'Added action updating Round Number of rounds on UAT. !image-2023-01-24-10-52-22-756.png!\'", \'Comment 21: "I could delete the round indeed. the next round\\\'s number was not automatically updated. When I tried to update the round number in the round through the button Tomasz showed here\', \'Comment 22: I got this error below. Did I do something wrong or forgot something?!image!"\', \'Comment 23: \\\'Yes sorry my fault from the database everything was working fine but in the system I accidentally add one more ")" and it was at fault. Now should be ok\\\'\', \'Comment 24: "It seems to work with the button now\', \'Comment 25: great! If we do this before there are any documents (even in entry mode) on this round\', \'Comment 26: the round number will be correct on future documents where this round is selected? And what for SR\\\'s that are already in archive mode?!image-1!!image-2!"\', \'Comment 27: "I tested this button but that doesn\\\'t seem to work for already archived SR\\\'s and linked invoices!image-3!"\', \'Comment 28: "[[email protected]]możesz to sprawdzić odnośnie tej akcji update\\\'owania rund i przygotować to wg tego co w komentarzu wcześniej - czyli aktualizacja pól na Rundzie \\\'Round number\\\' oraz na Sales Ivoice\', \'Comment 29: Purchase Invoice i Slaughtery Report powiązanych z daną rundą. Mitch nie potwierdził\', \'Comment 30: ale logiczne byłoby\', "Comment 31: żeby to tak działało.{quote}By using this action only field \'Full number\' is updated. Fielrd \'Round number\' on Round is not updated. Als Sales Invoice", \'Comment 32: Purchase Invoice\', \'Comment 33: Slaughtery Reports connected to round these field on screen below are not updated right now.{quote}"\', \'Comment 34: "Now on test database the number is updated on the SR and related invoices when using the action \\\'Update SR and linked invoice\\\'."\', "Comment 35: \'@Steffen can you confirm this works?\'", \'Comment 36: "This seems to work in the TEST environment (also for archived SR\\\'s and invoices)\', \'Comment 37: I just tested it."\', "Comment 38: \'Can be moved to PROD.\'", "Comment 39: \'Moved to production\'", "Comment 40: \'Dodano akcjeRecalculateRoundNumberPrzeniesiono procedureexec [dbo].[KR_RecalculateRoundNumber] @CSTID@,@FRM@Przeniesiono procedury i akcjeUpdate SR and linked invoices Round NumberExec dbo.[KR_Update_SR_and_linked_invoices_round_MASBE] @CurrentID@,@ROUND@,@UserID@Exec dbo.[KR_Update_SR_and_linked_invoices_round_MASNL] @CurrentID@,@ROUND@,@UserID@\'", "Comment 41: \'Do sprawdzenia czy akcja do aktualizacji faktur i SR działa poprawnie - zgłoszone przez Mitcha", \'Comment 42: że coś jest nie tak na tych dokumentach.{quote}Hi Damian\', "Comment 43: this is still going strange. Please see these examples:On the PI we see conflicting rounds.!image-2023-03-06-16-01-45-960.png!On the SI the round information is not updated at all:!image-2023-03-06-16-01-55-683.png!On the SR we still see round 2:!image-2023-03-06-16-02-03-925.png!{quote}\']"]\nRelated Issues:\n[]\n\n### End'}
714	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8317\n\n### Instruction:\nOn the right side of the screen in the SR document we would like to see a preview of the scanned slaughter report from Kofax.\r\n\r\nThis was working in the past but later changed in the hyperlink. However the users have difficulties with having Kofax and Intense on two screens. So comparing the values is very hard right now.\r\n\r\nCan we add the preview back on the screen? Or can we make sure that we can have the two systems on two screens at the same time? \n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: \\\'Hi [[email protected]],we can change field URL "OnBasePrintout" into field type "Web browser" on Slaughtery Report (it can be looks like tab "Attachements" on SR).This changed "OnBase Printout" field\', "Comment 4: we can place on the right side of SR document (placed where right now is area for attachements):!image-2023-01-12-15-01-28-307.png!This solution will be good for you?Best regards,Grzegorz\'", "Comment 5: \'{color:black}Hoi Mitch", \'Comment 6: Grzegorz,{color} {color:black}{color} {color:black}It is een good solution.{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Nancyvan{color} \|{color:#000001} {color} \|{color:#000001} Dam{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} M:{color}{color:#000001}{color}{color:#000001}0318675565{color}{color:#000001} <tel:0318%20675%20565>{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Grzegorz Materla (Jira) <[email protected]> Verzonden: donderdag 12 januari 2023 15:05 Aan: Dam\', "Comment 7: Nancy van <[email protected]> Onderwerp: DGS-8317 Preview of SR in Intense \| {color:white} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} \| !image006!\'", "Comment 8: \'When is this fixed?\'", \'Comment 9: "[[email protected]],I have been waiting for your accept to make this change on test environment.We\\\'ll plan it according to the schedule. When we do\', \'Comment 10: I\\\'ll notify you,Best regards,Grzegorz"\', \'Comment 11: "Where can I find a proper example? I ramdomly clicked open some SR\\\'s but I can\\\'t find an example.We cannot send new SR\\\'s from Kofax\', \'Comment 12: we don\\\'t have a test version of Kofax."\', \'Comment 13: "It\\\'s mockup\', "Comment 14: so you can\'t find it in system.It\'s no problem to test it", \'Comment 15: we can prepare this field with link from random OnBase link.Best regards,Grzegorz"\', "Comment 16: \'No problem", "Comment 17: you can directly move this to PROD. This is quite urgent.If you can show the preview of the SR on the place of the website in your mock-up that it is perfect.\'", "Comment 18: \'Added on production and test.\'", "Comment 19: \'It is working properly\'", "Comment 20: \'One thing; the users need to login to OnBase everytime again and again. This should be done on each individual SR.Could you solve this?\'", "Comment 21: \'Omówieone mailowo[^RE_ Preview from Onbase on SR in Intense.eml]\'", \'Comment 22: "Please verify that solution with users settings helped and now it\\\'s ok.\\\\r\\\\r!https://attachments.office.net/owa/damian.swistek%40kotrak.com/service.svc/s/GetAttachmentThumbnail?id=AAMkADY2ZTAxMzM3LTE0YjctNGI0Ni1hYjIxLWE3MDFjOTVkNmExNwBGAAAAAAA%2FcPjpt4lNRZFonusrO6C9BwA5bA29TyJrQIX6A6F8SkSqAAAAAAEJAAA5bA29TyJrQIX6A6F8SkSqAASppNjvAAABEgAQAOBGQbqao15Akkfr0GR1Ps4%3D&thumbnailType=2&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IkQ4OThGN0RDMjk2ODQ1MDk1RUUwREZGQ0MzODBBOTM5NjUwNDNFNjQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiIySmozM0Nsb1JRbGU0Tl84dzRDcE9XVUVQbVEifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiNzQ1YWJkOWJmNWUxNGJhMWJkNjE5OTZmNzhmMzQzNGYiLCJzaWduaW5fc3RhdGUiOiJbXCJrbXNpXCJdIiwidmVyIjoiRXhjaGFuZ2UuQ2FsbGJhY2suVjEiLCJhcHBjdHhzZW5kZXIiOiJPd2FEb3dubG9hZEA5OGIwMzVmZi1iMTIxLTQ1OGItYTNmMC0zMjM1NGRiMWI3ODEiLCJpc3NyaW5nIjoiU0lQIiwiYXBwY3R4Ijoie1wibXNleGNocHJvdFwiOlwib3dhXCIsXCJwdWlkXCI6XCIxMTUzNzY1OTMyMzQ4MzE1MTQ3XCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIixcIm9pZFwiOlwiYjU1MGNmY2EtYjZhYS00NmFkLWFlYjAtZTllNjIyYTMyOTE2XCIsXCJwcmltYXJ5c2lkXCI6XCJTLTEtNS0yMS0zNjk5NTUyNDA4LTIxNDA2MTAxMy0yMzI0NTA4MTctMTMxMDk3OTRcIn0iLCJuYmYiOjE2NzQ1NDc4NzMsImV4cCI6MTY3NDU0ODQ3MywiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImhhcHAiOiJvd2EifQ.uHabLqzmC-Fz6S7eq-8N3Hoa7ahCALJHRlKqnSOuaOlCeEwg9a28aWEZDEg965J9PZv4SYVADPhufCEV5bx_oNZEYcA78TVSB045lhIr59nRtqIcfakatVEvwApzYvpeE8WvFSXHghXTltuQmXhSkKEM1kX2_dmPWeTzlurV6E6_qTgsZEyjgyb23T9ukNGJxDlLSJtaAUm-uPvX7LtOQ8eZl6Q5oFFYZlgAo9we0Eka4lPpm6YGxoShS8qFLYPOPjv76u_gS9LghKU-GRzJxIY7B2PCC2qLHE7EVYxu4T1gqYIILCwBHj0LUTYpVdEwXMWuIzMLLTjxr7ypG_c76Q&X-OWA-CANARY=YE30i8dQrUOf_GMubfiFgHADINri_doYnPD5j01pvrT__dLZozkivKi5BIuSMtMBKB6tNQE8WSk.&owa=outlook.office.com&scriptVer=20230113006.11&animation=true!"\', "Comment 23: \'Its ok now.\'", "Comment 24: \'I close the task\']"]\nRelated Issues:\n[\'DGS-8403\']\n\n### End'}
715	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8316\n\n### Instruction:\nFor item 702562, an additional technology AW702562 was created. This is not correct (anymore). Please disable / remove this additional technology so that \r\n- recipes for 702562 arrive in PCS\r\n- orders for item 702562 are sent to PCS where additional technology is no longer applied (so ItemCode and ItemCodeCustomer is 702562)\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'additional technology AW702562 has been deleted.\'", "Comment 3: \'Thank you. This ticket can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
716	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8315\n\n### Instruction:\nHello,\r\n\r\nSales Order SO000011369 isn\'t arriving in DHP. This order is in DHC though. \r\nCan you please check? Is it again BP which is causing the issue?\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Please check again !screenshot-3! This order has been imported at 2023-01-12 10:06Issue date is from October .!image-2023-01-12-10-52-14-070!\'", \'Comment 3: "Excuse me\', \'Comment 4: you\\\'re right. I had the data filter settings wrong (until 12-01-23)"\', "Comment 5: \'Thank you for confirmation.\'", "Comment 6: \'This ticket has been closed.\']"]\nRelated Issues:\n[]\n\n### End'}
717	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8314\n\n### Instruction:\nVT-793/1/23 released missing serial number 260822-1-L3-P60-71 .\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,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'!image-2023-01-13-15-07-53-260.png!\'", "Comment 5: \'f4270626-7da5-41b6-a9d3-62c6f4d5108d\'", \'Comment 6: "select* from VehicleTicketElements where id=\\\'f4270626-7da5-41b6-a9d3-62c6f4d5108d\\\'!image-2023-01-16-14-59-15-829.png!"\', \'Comment 7: "del id=\\\'be7652ac-0ce9-41cf-96d5-446f6d48ff83!image-2023-01-16-15-03-24-556.png!"\', "Comment 8: \'!image-2023-01-16-15-07-56-831.png!\'", \'Comment 9: "Na tej tabeli brak jednego wpisu SELECT TOP (1000) [Id] ,[No] ,[SubNo] ,[SerialNumber] ,[ExpiryDate] ,[WeightValue] ,[WeightUnit] ,[IsCancelled] ,[IsArchived] ,[ReactionReasonId] ,[ProducerId] ,[ProductionDate] ,[DeliveryId] ,[ReservationId] ,[StockUnitId] FROM [DHPlantVCBusinessLogicMain].[dbo]. [VehicleTicketBulkDispatchElementResources] where id=\\\'f4270626-7da5-41b6-a9d3-62c6f4d5108d\\\' or deliveryid=\\\'be7652ac-0ce9-41cf-96d5-446f6d48ff83\\\'select sum(weightvalue) from dbo. [VehicleTicketBulkDispatchElementResources] where idid=\\\'f4270626-7da5-41b6-a9d3-62c6f4d5108d\\\'"\', "Comment 10: \'We fixed information on delivery but there are missing stock but verify the stock and create a stocktaking for missing quantity\'", \'Comment 11: "i\\\'m not sure what is fixed Delivery? for missing stock we can handle that"\', "Comment 12: \'Please check the information on VT,\'", "Comment 13: \'you can close the ticket\']"]\nRelated Issues:\n[]\n\n### End'}
718	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8313\n\n### Instruction:\nChange main, target and payer customer off SOR239 + SOR240 + SOR257 + SOR258 from CA00000003 to customer CA00000001 \r\n\n\n### Response:\n["Comment 1: [\'!image-3!!image-4!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Customers for documents SOR239/09/2022/VM", \'Comment 4: SOR240/09/2022/VM ,SOR257/09/2022/VM ,SOR258/09/2022/VM have been changed\', "Comment 5: please check.\'", "Comment 6: \'This must be all codes: main", "Comment 7: target en payer!image!\'", "Comment 8: \'This SOR is from a different series - V", "Comment 9: previously was given to VM.\'", "Comment 10: \'!image-1!\'", "Comment 11: \'Yes", "Comment 12: but you sent also !screenshot-1! SOR with V series. :)\'", "Comment 13: \'Wrong typing.Should be the VM\'", "Comment 14: \' !screenshot-2! !screenshot-3! should be correct", "Comment 15: please verify.\'", "Comment 16: \'Could you please confirm if we can close this task?Regards\'", "Comment 17: \'!image-2!!image-5!\'", "Comment 18: \'I have asked the requester if it is Oke.\'", "Comment 19: \'According to me is only one correct.I Have asked the user what the meaning exactly is.Comment is confusing.\'", \'Comment 20: "Hello. Thank you for your information,So I\\\'m still waiting to know what else needs to be changed.Regards."\', "Comment 21: \'Yesterday i have asked for a conformation.Did not recieve it yet\'", "Comment 22: \'I have asked the requester for a responce\'", "Comment 23: \'Ticket kan be closed\']"]\nRelated Issues:\n[]\n\n### End'}
719	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8312\n\n### Instruction:\nSO 135/1/23/UMR has four elements. all of them have synced to dhp, the business partner, recipes etc. appear to be available in all the applicable modules. \r\nwhen we look for the SO under production we can see all the elements but when we try to add element one to a PRO it is not available for selection. (this was attempted on multiple user profiles and sessions, cache was also cleared). \r\nwe attempted to resync the order as well but the element is still not showing. we cannot identify anything in the error queue related to this product. \n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!!image-3!!image-4!!image-5!\'", "Comment 2: \'please ignore task\'", "Comment 3: \'The ticket has been closed\']"]\nRelated Issues:\n[]\n\n### End'}
720	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8311\n\n### Instruction:\nHello, \r\n\r\nthis issue has not been resolved \r\n\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7972\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. This issue has been fixed since version 8.3.2.You have 8.3.1 !screenshot-2! \'", "Comment 4: \'hello", \'Comment 5: thank you\', "Comment 6: is there a newer version ready for deployment other than 8.3.2?\'", "Comment 7: \'Please contact the DHP Product Owner for information about the latest version of the application.Regards.\'", "Comment 8: \'Hello", "Comment 9: you can close this ticket\']"]\nRelated Issues:\n[]\n\n### End'}
721	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8310\n\n### Instruction:\nReceptura DT2B3X00G oraz DT2B3X00G-L00 jest w DHC. JEst zlinkowana i zaakceptowana. Technologie rowniez sa wykonane lecz mimo to receptury brak w DHP\n\n### Response:\n["Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", \'Comment 2: "brak labelki w dhc service select * from Labels where DhhItemId=\\\'975595F0-19A5-4DF6-8769-5D5ADBF9AD8C\\\' and ProductionAreaId=\\\'ED949013-364F-48A8-A501-F9A190907941\\\'"\', "Comment 3: \'There are problem with a lot of messages in queue for dhc service - I restarted it and watching.Slowly the messages are going - when do you need this recipes in DHP?!image-2023-01-11-22-26-10-813.png!\'", "Comment 4: \'After about an hour 1600 messages pass", "Comment 5: It seems that about 2-3 am all messages should be pass and for tommorow early morning recipe should be at the dhp.May we lower the priority to p2 ? If you do no need this tonight ?\'", "Comment 6: \'labelka i receptura i prod receptura juz sa w dhc service czekamy tylko n technologieh!image-2023-01-12-00-04-24-067.png!\'", "Comment 7: \'Recipes for that items should be in dhp.\'", "Comment 8: \'Task to close\']"]\nRelated Issues:\n[]\n\n### End'}
722	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8309\n\n### Instruction:\nCześć,\r\n\r\nw lotach produkcyjnych 2842110123010 oraz 2842110123011 pojawił się surowiec, którego nie powinno tam być: 4612070 CALPRONA GOL – ZAKWASZACZ PŁYNNY. Proszę o usunięcie go z raportów.\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: \'[[DHP] [Produkcja] Błędnie wprowadzone dane przy produkcji - potrzebna zmiana artykułu np. z luzu na worek\|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHP.one#%5bDHP%5d%20%5bProdukcja%5d%20B%C5%82%C4%99dnie%20wprowadzone%20dane%20przy%20produkcji%20&section-id=\\\\\\\\{F3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9}&page-id=\\\\\\\\{2A972AF7-7F0E-47FF-AFE4-71EDDBF2129C}&end] ([Widok sieci Web\|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHP.one%7CF3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9%2F%5BDHP%5D%20%5BProdukcja%5D%20B%C5%82%C4%99dnie%20wprowadzone%20dane%20przy%20produkcji%20%7C2A972AF7-7F0E-47FF-AFE4-71EDDBF2129C%2F%29])\'", \'Comment 3: "select * from ProductionLotReportHeader where PlH_LotNumber in (2842110123010,2842110123011)select * from RecipeElement where RcE_RcHId in (26506,26496) and RcE_ArtId=22326select * from ArticleCard where art_code=\\\'4612070\\\'"\', "Comment 4: \'lotów nie ma w dhc.\'", "Comment 5: \'!image-2023-01-11-20-32-07-733.png!\'", "Comment 6: \'!11plr.PNG\|thumbnail!\'", "Comment 7: \'I can see that this article is not on the prl2842110123011.!11plr.PNG!\'", "Comment 8: \'Tak racja w 2842110123011 nie ma wskazanego artykulu.W 2842110123010 jest!image!\'", "Comment 9: \'Pozycje usunięto proszę o weryfikację,\'", "Comment 10: \'Ok w 2842110123011 nie widze.USer wskazał poprawny LOT 2842110123009 w ktorym wskazany artykuł jeszcze wystepuje\'", "Comment 11: \'!09plr.PNG\|thumbnail!\'", "Comment 12: \'Z lot też usunięto.Jest to możliwe z poziomu aplikacji. Wszystkie wpisane PLR były sa w buforze jeśli na jakimś plr status nadal będzie bufor to proszę by użytwkownik wyszukał kod towaru i wybrał ctrl+del po wejściu na artykuł a następnie potwierdził operacjęPLr w buforze można rozpoznać po zielonym kolorze i zaznaczonym checku :!image-2023-01-11-21-17-53-674.png!!09plr.PNG!\'", "Comment 13: \'Ok. Task to close\']"]\nRelated Issues:\n[]\n\n### End'}
723	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8308\n\n### Instruction:\nWe tried to creat A-T for product 080800-B1000 in DHC. However, system indicates that it already exists. I tried to find it, but it doesn\'t show up/ Can you check how to fix this and create the technology? \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. There is already one from 2019 with a different name BE. DIEYEN W-19. We can rename it and you will add a subversion then. !screenshot-1! \'", "Comment 4: \'Yes please\'", "Comment 5: \'Please check now by Add subversion !screenshot-2! \'", "Comment 6: \'Thanks", "Comment 7: ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
724	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8307\n\n### Instruction:\nHello,\r\n\r\nVT-474/1/23 cannot be closed, when clicking on close, an error message is displayed and the ticket isn\'t opened. \r\n\n\n### Response:\n["Comment 1: [\'Hi,What is the error message? Could you please provide us with yur error?Regards\'", \'Comment 2: "see screenshot\', \'Comment 3: occurs from Vehicle tickets screen\', \'Comment 4: when I select option \\\'close\\\': normally it should open the VT to fill in missing weights!afbeelding!"\', "Comment 5: \'Please transfer the resource from pallet to bulk for the item using inventory and check. Or I can do it", "Comment 6: just need confirmation. !screenshot-1! \'", "Comment 7: \'Item pcs should be on pallet", "Comment 8: not bulk. Can you change this?\'", "Comment 9: \'The correct ASN should be sent and the VT issued again (VT cancelled).\'", "Comment 10: \'Could you please confirm if we can close this task?Regards\'", "Comment 11: \'task can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
725	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8306\n\n### Instruction:\nHi\r\n\r\nWe found new SU Barcodes in WMS engine with wrong information.\r\nThe PLR were already confirmed, but the SUs still with reservation document, and because of it we are not able to fast move this SUs.\r\nThere one in Toledo:\r\nPLR LotNumber\tBarcode\r\n0871040123012\t87-W005CB\r\n\r\nAnd other six in Itaberaí\r\nPLR LotNumber\tBarcode\r\n0831090123009\t83-W09OXG\r\n0833040123006\t83-W09QFA\r\n0833040123006\t83-W09R5T\r\n0833060123001\t83-W09GP5\r\n0833090123009\t83-W09GP5\r\n0833090123010\t83-W09GP5\r\n\r\nCould you please fix that?\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: \'rezerwacji brak dla kodu :87-woo5cb ale jest rzbieznosc!image-2023-01-12-10-46-47-668.png!\'", "Comment 3: \'could you bring more details aboutPLR LotNumber Barcode0871040123012 87-W005CB!image-2023-01-12-11-04-30-440.png!There is no reservations for that item nor for wms nor for SU modulesI only see some diffrence between qunatity on unitload table - could you bring more details maybe screen shoot from application ?\'", "Comment 4: \'I also verified the other barcodes for all of them there were now reservation and no diffrences.Please verfy and bring more details.\'", "Comment 5: \'Hi AgnieszkaHere is the evidence for SU 87-W005CBThank you!image!!image-1!\'", "Comment 6: \'Hi AgnieszkaHere the evidence for SU* 83-W09QFA* 83-W09R5T* 83-W09GP5Thank you!image-2!!image-3!!image-4!!image-5!!image-6!!image-7!!image-9!\'", "Comment 7: \'The data has been corrected", "Comment 8: please verify.\'", \'Comment 9: "Hi PiotrIt\\\'s fixed now.You can close this taskThank you very much"]\']\nRelated Issues:\n[]\n\n### End'}
726	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8305\n\n### Instruction:\nNo dispatches are registered in DHP Utrecht. E.g. for trip 00959448 a dispatch message swas send from PCS at 12.48. No registration seems to be done in DHP. Please check. Plant needs registration/packing slips for dispatches.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'{code:java}2023-01-11 10:03:33 (3db99815-e5e3-4bf4-a27d-06a93dce4553/Plant.PCS.BusinessLogic/DHVD01AP183/28120/7) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CompleteVehicleTicketDispatchCommand](Plant.PCS.BusinessLogic.Application.Interfaces.VehicleTickets.Commands.CompleteVehicleTicketDispatchCommand) methodKotrak.Common.SharedKernel.Exceptions.DomainOperationException: Cannot complete dispatch in current vehicle ticket\\\\\'s status. ---> Kotrak.Common.SharedKernel.Exceptions.DomainOperationException: CannotCompleteDispatchInCurrentStatus at Plant.PCS.BusinessLogic.Domain.VehicleTickets.VehicleTicket.CompleteDispatch(IEnumerable`1 elements) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicket.cs:line 89 at Plant.PCS.BusinessLogic.Application.VehicleTickets.VehicleTicketService.CompleteDispatch(AggregateId vehicleTicketId", \'Comment 3: IEnumerable`1 elements) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Application\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketService.cs:line 77 at Plant.PCS.BusinessLogic.Application.VehicleTickets.CommandHandlers.CompleteVehicleTicketDispatchCommandHandler.Handle(CompleteVehicleTicketDispatchCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\CompleteVehicleTicketDispatchCommandHandler.cs:line 25 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 ---2023-01-11 10:03:33 (3db99815-e5e3-4bf4-a27d-06a93dce4553/Plant.PCS.BusinessLogic/DHVD01AP183/28120/7) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type "Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketDispatchCompletedEvent"\', "Comment 4: retry no 5Kotrak.Common.SharedKernel.Exceptions.DomainOperationException: Cannot complete dispatch in current vehicle ticket\\\\\'s status. ---> Kotrak.Common.SharedKernel.Exceptions.DomainOperationException: CannotCompleteDispatchInCurrentStatus at Plant.PCS.BusinessLogic.Domain.VehicleTickets.VehicleTicket.CompleteDispatch(IEnumerable`1 elements) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicket.cs:line 89 at Plant.PCS.BusinessLogic.Application.VehicleTickets.VehicleTicketService.CompleteDispatch(AggregateId vehicleTicketId", "Comment 5: IEnumerable`1 elements) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Application\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketService.cs:line 77 at Plant.PCS.BusinessLogic.Application.VehicleTickets.CommandHandlers.CompleteVehicleTicketDispatchCommandHandler.Handle(CompleteVehicleTicketDispatchCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\CompleteVehicleTicketDispatchCommandHandler.cs:line 25 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message) --- End of inner exception stack trace ---2023-01-11 10:03:43 (3db99815-e5e3-4bf4-a27d-06a93dce4553/Plant.PCS.BusinessLogic/DHVD01AP183/28120/7) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CompleteVehicleTicketDispatchCommand](Plant.PCS.BusinessLogic.Application.Interfaces.VehicleTickets.Commands.CompleteVehicleTicketDispatchCommand) methodKotrak.Common.SharedKernel.Exceptions.DomainOperationException: Cannot complete dispatch in current vehicle ticket\\\\\'s status. ---> Kotrak.Common.SharedKernel.Exceptions.DomainOperationException: CannotCompleteDispatchInCurrentStatus at Plant.PCS.BusinessLogic.Domain.VehicleTickets.VehicleTicket.CompleteDispatch(IEnumerable`1 elements) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicket.cs:line 89 at Plant.PCS.BusinessLogic.Application.VehicleTickets.VehicleTicketService.CompleteDispatch(AggregateId vehicleTicketId", \'Comment 6: IEnumerable`1 elements) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Application\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketService.cs:line 77 at Plant.PCS.BusinessLogic.Application.VehicleTickets.CommandHandlers.CompleteVehicleTicketDispatchCommandHandler.Handle(CompleteVehicleTicketDispatchCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\CompleteVehicleTicketDispatchCommandHandler.cs:line 25 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 ---2023-01-11 10:03:43 (3db99815-e5e3-4bf4-a27d-06a93dce4553/Plant.PCS.BusinessLogic/DHVD01AP183/28120/7) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type "Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketDispatchCompletedEvent"\', "Comment 7: message will be discardedKotrak.Common.SharedKernel.Exceptions.DomainOperationException: Cannot complete dispatch in current vehicle ticket\\\\\'s status. ---> Kotrak.Common.SharedKernel.Exceptions.DomainOperationException: CannotCompleteDispatchInCurrentStatus at Plant.PCS.BusinessLogic.Domain.VehicleTickets.VehicleTicket.CompleteDispatch(IEnumerable`1 elements) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicket.cs:line 89 at Plant.PCS.BusinessLogic.Application.VehicleTickets.VehicleTicketService.CompleteDispatch(AggregateId vehicleTicketId", "Comment 8: IEnumerable`1 elements) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Application\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketService.cs:line 77 at Plant.PCS.BusinessLogic.Application.VehicleTickets.CommandHandlers.CompleteVehicleTicketDispatchCommandHandler.Handle(CompleteVehicleTicketDispatchCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\CompleteVehicleTicketDispatchCommandHandler.cs:line 25 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message) --- End of inner exception stack trace ---{code}\'", \'Comment 9: \\\'{code:java}2023-01-11 01:16:34 (b4116685-be33-4cda-a7b9-6a63690211d8/Plant.PCS.BusinessLogic/DHVD01AP183/28120/7) [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 INSERT statement conflicted with the FOREIGN KEY constraint \\\\\\\\"FK_StockUnits_Deliveries_DeliveryId\\\\\\\\". The conflict occurred in database \\\\\\\\"DHPlantPCSBusinessLogicMain\\\\\\\\"\', \'Comment 10: table \\\\\\\\"dbo.Deliveries\\\\\\\\"\', "Comment 11: column \\\\\'Id\\\\\'.The statement has been terminated. at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception", \'Comment 12: Boolean breakConnection\', \'Comment 13: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 14: Boolean callerHasConnectionLock\', \'Comment 15: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 16: SqlCommand cmdHandler\', \'Comment 17: SqlDataReader dataStream\', \'Comment 18: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 19: TdsParserStateObject stateObj\', \'Comment 20: Boolean& dataReady) at Microsoft.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at Microsoft.Data.SqlClient.SqlDataReader.get_MetaData() at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 21: RunBehavior runBehavior\', \'Comment 22: String resetOptionsString\', \'Comment 23: Boolean isInternal\', \'Comment 24: Boolean forDescribeParameterEncryption\', \'Comment 25: Boolean shouldCacheForAlwaysEncrypted) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 26: RunBehavior runBehavior\', \'Comment 27: Boolean returnStream\', \'Comment 28: Boolean isAsync\', \'Comment 29: Int32 timeout\', \'Comment 30: Task& task\', \'Comment 31: Boolean asyncWrite\', \'Comment 32: Boolean inRetry\', \'Comment 33: SqlDataReader ds\', \'Comment 34: Boolean describeParameterEncryptionRequest) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 35: RunBehavior runBehavior\', \'Comment 36: Boolean returnStream\', \'Comment 37: TaskCompletionSource`1 completion\', \'Comment 38: Int32 timeout\', \'Comment 39: Task& task\', \'Comment 40: Boolean& usedCache\', \'Comment 41: Boolean asyncWrite\', \'Comment 42: Boolean inRetry\', \'Comment 43: String method) at Microsoft.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject) at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.Execute(IRelationalConnection connection)ClientConnectionId:6bbef45c-2439-46b8-bcc0-604166c81247Error Number:547,State:0,Class:16 --- End of inner exception stack trace --- at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.Execute(IRelationalConnection connection) at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.Execute(IEnumerable`1 commandBatches\', \'Comment 44: IRelationalConnection connection) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(IList`1 entriesToSave) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(StateManager stateManager\', \'Comment 45: Boolean acceptAllChangesOnSuccess) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 46: Func`3 operation\', \'Comment 47: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(Boolean acceptAllChangesOnSuccess) at Microsoft.EntityFrameworkCore.DbContext.SaveChanges(Boolean acceptAllChangesOnSuccess)"Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): The INSERT statement conflicted with the FOREIGN KEY constraint "FK_StockUnits_Deliveries_DeliveryId". The conflict occurred in database "DHPlantPCSBusinessLogicMain"\', \'Comment 48: table "dbo.Deliveries"\', "Comment 49: column \\\\\'Id\\\\\'.The statement has been terminated. at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception", \'Comment 50: Boolean breakConnection\', \'Comment 51: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 52: Boolean callerHasConnectionLock\', \'Comment 53: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 54: SqlCommand cmdHandler\', \'Comment 55: SqlDataReader dataStream\', \'Comment 56: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 57: TdsParserStateObject stateObj\', \'Comment 58: Boolean& dataReady) at Microsoft.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at Microsoft.Data.SqlClient.SqlDataReader.get_MetaData() at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 59: RunBehavior runBehavior\', \'Comment 60: String resetOptionsString\', \'Comment 61: Boolean isInternal\', \'Comment 62: Boolean forDescribeParameterEncryption\', \'Comment 63: Boolean shouldCacheForAlwaysEncrypted) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 64: RunBehavior runBehavior\', \'Comment 65: Boolean returnStream\', \'Comment 66: Boolean isAsync\', \'Comment 67: Int32 timeout\', \'Comment 68: Task& task\', \'Comment 69: Boolean asyncWrite\', \'Comment 70: Boolean inRetry\', \'Comment 71: SqlDataReader ds\', \'Comment 72: Boolean describeParameterEncryptionRequest) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 73: RunBehavior runBehavior\', \'Comment 74: Boolean returnStream\', \'Comment 75: TaskCompletionSource`1 completion\', \'Comment 76: Int32 timeout\', \'Comment 77: Task& task\', \'Comment 78: Boolean& usedCache\', \'Comment 79: Boolean asyncWrite\', \'Comment 80: Boolean inRetry\', \'Comment 81: String method) at Microsoft.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject) at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.Execute(IRelationalConnection connection)ClientConnectionId:6bbef45c-2439-46b8-bcc0-604166c81247Error Number:547,State:0,Class:16 --- End of inner exception stack trace --- at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.Execute(IRelationalConnection connection) at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.Execute(IEnumerable`1 commandBatches\', \'Comment 82: IRelationalConnection connection) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(IList`1 entriesToSave) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(StateManager stateManager\', \'Comment 83: Boolean acceptAllChangesOnSuccess) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 84: Func`3 operation\', "Comment 85: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(Boolean acceptAllChangesOnSuccess) at Microsoft.EntityFrameworkCore.DbContext.SaveChanges(Boolean acceptAllChangesOnSuccess){code}\'", \'Comment 86: "{code:java}2023-01-11 13:19:48 (/Plant.PCS.BusinessLogic/DHVD01AP183/32104/1) [Warning] Microsoft.AspNetCore.DataProtection.Repositories.EphemeralXmlRepository - Using an in-memory repository. Keys will not be persisted to storage.2023-01-11 13:19:48 (/Plant.PCS.BusinessLogic/DHVD01AP183/32104/1) [Warning] Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager - Neither user profile nor HKLM registry available. Using an ephemeral key repository. Protected data will be unavailable when application exits.2023-01-11 13:19:48 (/Plant.PCS.BusinessLogic/DHVD01AP183/32104/1) [Warning] Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager - No XML encryptor configured. Key {95e63fbc-ec04-45db-94db-faa2eb5235e6} may be persisted to storage in unencrypted form.2023-01-11 13:21:45 (/Plant.PCS.BusinessLogic/DHVD01AP183/32104/5) [Warning] Microsoft.EntityFrameworkCore.Query - Compiling a query which loads related collections for more than one collection navigation\', "Comment 87: either via \'Include\' or through projection", "Comment 88: but no \'QuerySplittingBehavior\' has been configured. By default", "Comment 89: Entity Framework will use \'QuerySplittingBehavior.SingleQuery\'", "Comment 90: which can potentially result in slow query performance. See https://go.microsoft.com/fwlink/?linkid=2134277 for more information. To identify the query that\'s triggering this warning call \'ConfigureWarnings(w => w.Throw(RelationalEventId.MultipleCollectionIncludeWarning))\'.2023-01-11 13:21:45 (/Plant.PCS.BusinessLogic/DHVD01AP183/32104/5) [Warning] Microsoft.EntityFrameworkCore.Query - Compiling a query which loads related collections for more than one collection navigation", "Comment 91: either via \'Include\' or through projection", "Comment 92: but no \'QuerySplittingBehavior\' has been configured. By default", "Comment 93: Entity Framework will use \'QuerySplittingBehavior.SingleQuery\'", "Comment 94: which can potentially result in slow query performance. See https://go.microsoft.com/fwlink/?linkid=2134277 for more information. To identify the query that\'s triggering this warning call \'ConfigureWarnings(w => w.Throw(RelationalEventId.MultipleCollectionIncludeWarning))\'.2023-01-11 13:21:45 (/Plant.PCS.BusinessLogic/DHVD01AP183/32104/5) [Warning] Microsoft.EntityFrameworkCore.Query - Compiling a query which loads related collections for more than one collection navigation", "Comment 95: either via \'Include\' or through projection", "Comment 96: but no \'QuerySplittingBehavior\' has been configured. By default", "Comment 97: Entity Framework will use \'QuerySplittingBehavior.SingleQuery\'", "Comment 98: which can potentially result in slow query performance. See https://go.microsoft.com/fwlink/?linkid=2134277 for more information. To identify the query that\'s triggering this warning call \'ConfigureWarnings(w => w.Throw(RelationalEventId.MultipleCollectionIncludeWarning))\'.2023-01-11 13:21:46 (97944319-d592-400e-ab1e-5a7a7eca841e/Plant.PCS.BusinessLogic/DHVD01AP183/32104/9) [Warning] Microsoft.EntityFrameworkCore.Query - Compiling a query which loads related collections for more than one collection navigation", "Comment 99: either via \'Include\' or through projection", "Comment 100: but no \'QuerySplittingBehavior\' has been configured. By default", "Comment 101: Entity Framework will use \'QuerySplittingBehavior.SingleQuery\'", "Comment 102: which can potentially result in slow query performance. See https://go.microsoft.com/fwlink/?linkid=2134277 for more information. To identify the query that\'s triggering this warning call \'ConfigureWarnings(w => w.Throw(RelationalEventId.MultipleCollectionIncludeWarning))\'.2023-01-11 13:21:47 (97944319-d592-400e-ab1e-5a7a7eca841e/Plant.PCS.BusinessLogic/DHVD01AP183/32104/9) [Warning] Microsoft.EntityFrameworkCore.Query - Compiling a query which loads related collections for more than one collection navigation", "Comment 103: either via \'Include\' or through projection", "Comment 104: but no \'QuerySplittingBehavior\' has been configured. By default", "Comment 105: Entity Framework will use \'QuerySplittingBehavior.SingleQuery\'", \'Comment 106: which can potentially result in slow query performance. See https://go.microsoft.com/fwlink/?linkid=2134277 for more information. To identify the query that\\\'s triggering this warning call \\\'ConfigureWarnings(w => w.Throw(RelationalEventId.MultipleCollectionIncludeWarning))\\\'.{code}"\', "Comment 107: \'Dear Bob,I have restarted service for PCS", "Comment 108: please let me know if it helped.Regards\'", "Comment 109: \'Provided trip is in DHP now:!image-2023-01-11-13-27-11-914.png!\'", \'Comment 110: "Dispatch messages now do result in VT\\\'s. SO that seems to work now.I am waiting for confirmation from plant that SPS is generated as well"\', "Comment 111: \'Printing of packing slips is working fine. So all seems to be ok now. This ticket can be closed.\'", "Comment 112: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}
727	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8304\n\n### Instruction:\nWhen we send "Replacement Price" for MTR (56). Our site sees as process complete. However, Asia Formulation Team said they are not able to see price for MTR. Could you please check?\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: \'!dhhpricelist2.PNG\|thumbnail! !dhhpricelist.PNG\|thumbnail! !dhh_replan.PNG\|thumbnail!\'", "Comment 4: \'You are saying due to that code price different? Could you please share in comment?\'", "Comment 5: \'Sorry previous comment was not saved. From what we have verified and as you can see on the scrennach price list for the stated period is in DHH and the prices agree example for Item. Please verify\'", "Comment 6: \'Hi", "Comment 7: Now they are able to see price. Do you do any fix?\'", "Comment 8: \'No I just check logs and log on to both applications to verify.May we close this task?\'", "Comment 9: \'Yes", "Comment 10: please close the ticket\']"]\nRelated Issues:\n[]\n\n### End'}
728	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8303\n\n### Instruction:\nOn Financial Statement printout there is wrong VAT value on section Guarantee.\r\n\r\nRound ID = 70831, FS ID = 85212\r\n\r\n!image-2023-01-11-12-12-51-559.png!\r\n\r\n\xa0\n\n### Response:\n["Comment 1: [\'Fixed at database test and production\']"]\nRelated Issues:\n[]\n\n### End'}
729	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8302\n\n### Instruction:\nHi,\r\n\r\nSales order SO000050717 is in DHC but isn\'t arriving in DHP for Utrecht. \r\nCan you please have a look? We need to ship this order today. \n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'I just see the Sales Order arriving in DHP :)\'", \'Comment 3: "But the Shipping Notice 7_L000103455 hasn\\\'t arrived yet"\', "Comment 4: \'Main and Payer have incorrect addresses!image-2023-01-11-11-54-56-577.png!Regards\'", "Comment 5: \'Hi Aleksandra", "Comment 6: the main address should be P. AMMERLAAN RIJSBERGEN B.V.BREEDSCHOTSESTRAAT 334891 PK RIJSBERGENNetherlandsPayer address should be P. AMMERLAAN ETTEN-LEUR B.V.RIOOLSEWEG 44874 NX ETTEN-LEURNetherlands\'", "Comment 7: \'Dear Theo,Under database I can see:Main>> code:811338>> name:P. AMMERLAAN ETTEN-LEUR B.V.>> address:BREEDSCHOTSESTRAAT 33,4891PK,RIJSBERGENPayer:>> code:811338>> name:P. AMMERLAAN ETTEN-LEUR B.V.>> address:BREEDSCHOTSESTRAAT 33,4891PK,RIJSBERGENTarget:>> code: 006501>> name: P. AMMERLAAN RIJSBERGEN BV>> address:BREEDSCHOTSESTRAAT 33,4891PK,RIJSBERGEN\'", \'Comment 8: \\\'!image-2023-01-11-13-18-27-482.png!{code:java}An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ShippingNoticeElementOrders_OrderElements_OrderId_OrderNo". The conflict occurred in database "DHPlantVCBusinessLogicMain"\', \'Comment 9: table "dbo.OrderElements".The statement has been terminated.{code}\\\'\', "Comment 10: \'The address for code 811338 should be:RIOOLSEWEG 4", \'Comment 11: 4874 NX\', "Comment 12: ETTEN-LEURThe address for 006501 is correct.Can you please change this in the database?\'", "Comment 13: \'Dear Theo,Please", \'Comment 14: ask Milas departament to correct the address and resent order from Milas?Please\', "Comment 15: let me know if this is possible.Regards\'", "Comment 16: \'Data is correct in Milas", "Comment 17: but it is wrongly mapped to DHC. This is not easy to solve today. \'", \'Comment 18: "{code:java}SELECT * FROM [DHCountry_NL_AS400_PROD].[dbo].[Orders] where ForeignDocumentNumber = \\\'SO000050717\\\' SELECT * FROM [DHCountry_NL_AS400_PROD].[dbo].[BusinessPartners] WHERE ID IN (\\\'B0C9EBCE-52E9-4883-8A26-FCA5ECE0CD5C\\\',\\\'D65B0026-CF98-428B-A630-E3C209BCDE46\\\')SELECT * FROM [DHCountry_NL_AS400_PROD].[dbo].[Addresses] WHERE BusinessPartnerId IN (\\\'B0C9EBCE-52E9-4883-8A26-FCA5ECE0CD5C\\\',\\\'D65B0026-CF98-428B-A630-E3C209BCDE46\\\')update [DHCountry_NL_AS400_PROD].[dbo].[Orders] set MainBusinessPartnerAddressId = \\\'2D0F2E93-6BC7-4101-AFA0-1249F6ABDE4F\\\' where MainBusinessPartnerId = \\\'B0C9EBCE-52E9-4883-8A26-FCA5ECE0CD5C\\\'update [DHCountry_NL_AS400_PROD].[dbo].[Orders] set PayerBusinessPartnerAddressId = \\\'2D0F2E93-6BC7-4101-AFA0-1249F6ABDE4F\\\' where PayerBusinessPartnerId = \\\'B0C9EBCE-52E9-4883-8A26-FCA5ECE0CD5C\\\'{code}"\', \'Comment 19: "Status shouldn\\\'t be waiting for customer\', \'Comment 20: should it?"\', \'Comment 21: "Yes\', \'Comment 22: you\\\'re right. My friend made a mistake"\', "Comment 23: \':) No problem\'", "Comment 24: \'I have exported the address for 811338 again from Milas", "Comment 25: but the address really is:P. AMMERLAAN ETTEN-LEUR B.V.RIOOLSEWEG 44874 NX ETTEN-LEURNetherlands \'", "Comment 26: \'Documents are in plant now.Please", "Comment 27: verify.Regards\'", "Comment 28: \'Thank you very much Aleksandra!\'", "Comment 29: \'No issue :)\']"]\nRelated Issues:\n[]\n\n### End'}
730	{'prompt': "Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8301\n\n### Instruction:\nQAM- export of AO to XML file does not work\n\n### Response:\n['Comment 1: []']\nRelated Issues:\n[]\n\n### End"}
731	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8300\n\n### Instruction:\nHi\r\nFrom Paulina\r\n\r\n\r\nRafał Boniecki\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: \'[^hrm.docx]\'", \'Comment 4: "The system producer\\\'s interpretation is attached[^hrm.docx]"\', "Comment 5: \'Task to close", "Comment 6: thanks.!image-1!\']"]\nRelated Issues:\n[]\n\n### End'}
732	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8299\n\n### Instruction:\nHello, \r\n\r\nconfirmed/closed documents stock reservations are not clearing again in DHP.\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!!image-3!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'{code:java}SELECT distinct p.lotnumberFROM DHPlantStockBusinessLogicMain.dbo.ProductionLots PJOIN DHPlantStockBusinessLogicMain.dbo.StockUnitReservations R ON P.Id = R.SourceDocumentIdWHERE P.ProductionLotStatus = 4{code}066218082202006623108220040662100622028066207062201906622308220330662240922007{code:java}SELECT count(),DocumentYear FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTickets] v inner join dbo.StockUnitReservations r on v.Id=r.SourceDocumentId where status>=120 group by documentyear{code} !screenshot-1! \'", "Comment 4: \'Poprawa dla PLR:0662180822020066231082200406621006220280662070622019066223082203306622409220070692240922005068218112201706820206220180672150322015\'", \'Comment 5: "Przykładowy VT z UR:{code:java}SELECT r. FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTickets] v inner join dbo.StockUnitReservations r on v.Id=r.SourceDocumentId where documentyear=2023 and status>=120 and DirectionType=20 order by SourceDocumentId SELECT * FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnitReleases]where SourceDocumentId=\\\'EB9A8A7D-DB07-438A-8383-0812707924Ef\\\'{code} !screenshot-2! !screenshot-3! !screenshot-4! "\', "Comment 6: \'błąd w logu!image-2023-01-26-10-30-58-761.png!po resend zrobił się wpis w[DHPlantStockBusinessLogicMain].[dbo].[StockUnitReleases]!image-2023-01-26-10-30-58-761!\'", "Comment 7: \'{code:java} SELECT distinct r.SourceDocumentNumber FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTickets] v inner join dbo.StockUnitReservations r on v.Id=r.SourceDocumentId where documentyear=2023 and status>=120 and DirectionType=20{code}vehicleticketdispatchclosedUR:VT-1000/1/23 VT-398/1/23 VT-446/1/23 VT-808/1/23 VT-855/1/23 VT-864/1/23vt-538/1/23VT-1073/12/22 VT-1086/12/22 VT-1110/12/22 VT-698/12/22 - 15.12.2022. VT-715/12/22MM:VT-153/12/22 VT-3/1/23 VT-386/1/23 VT-441/12/22 VT-454/12/22 VT-56/12/22 VT-569/11/22 - 30.11.2022 VT-64/12/22KD:VT-118/1/23 VT-136/12/22 VT-188/1/23 VT-188/12/22 VT-191/1/23 VT-233/1/23 VT-254/12/22 VT-261/12/22 VT-275/1/23 VT-3/1/23 VT-339/1/23 VT-35/12/22 VT-36/12/22 VT-397/1/23 VT-449/12/22 VT-505/12/22 VT-507/12/22 VT-53/12/22 VT-539/12/22 VT-54/12/22 VT-57/12/22 VT-63/12/22 VT-65/12/22 VT-677/11/22 VT-96/1/23Do analizy:VT-144/1/23 VT-293/6/22 VT-297/6/22KB:VT-167/1/23VT-185/1/23VT-217/12/22VT-236/1/23VT-341/12/22VT-466/12/22VT-56/1/23VT-6/1/23\'", "Comment 8: \'Hello,data has been corrected for PLR and VT for PLR there is already RCA - DGS-8168,but for VT documents RCA should be created ", "Comment 9: please confirm to create RCA.\'", "Comment 10: \'Hello,in version 8.5 the issue has been resolved - confirmed with developers.\'", "Comment 11: \'thank you", "Comment 12: task can be closed\']"]\nRelated Issues:\n[\'DAP-13254\']\n\n### End'}
733	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8298\n\n### Instruction:\nPrzez pomyłkę zamknąłem ZPM(K)-107/01/23 Agrochurt nie mogę ponownie otworzyć nie aktywna ikona proszę otworzyć je jeszcze raz.\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Temat bardzo pliny kierowca czeka. \'", "Comment 3: \'Close the task \']"]\nRelated Issues:\n[]\n\n### End'}
734	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8297\n\n### Instruction:\nProduction reports missing recipes. In the communication I see 400 errors. These are caused by incomplete product definitions in the messages, for item 960694 and for item 967433::\r\n\r\n\xa0<ProductDefinitions>\xa0\xa0\xa0\xa0\xa0 <ProductDefinition>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <ActionCode>ADD</ActionCode>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <MaterialDefinitionID>960693</MaterialDefinitionID>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <MaterialErpID>2302</MaterialErpID>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <Version>61</Version>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <PDNumber />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <InclusionRate xsi:nil="true" />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <BatchSize>99.999500</BatchSize>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <CreationDate>20221222 101222</CreationDate>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <EffectiveDate>20221222 101222</EffectiveDate>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <ExpirationDate />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <UseByDays xsi:nil="true" />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <Remark />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <RecipeHeaderId>23785</RecipeHeaderId>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <ProductDensity xsi:nil="true" />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <ContaminationCode />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <Materials />\xa0\xa0\xa0\xa0\xa0 </ProductDefinition>\r\n\r\n<ProductDefinition>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <ActionCode>ADD</ActionCode>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <MaterialDefinitionID>967344</MaterialDefinitionID>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <MaterialErpID>4448</MaterialErpID>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <Version>2</Version>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <PDNumber />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <InclusionRate xsi:nil="true" />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <BatchSize>99.999500</BatchSize>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <CreationDate>20230110 074618</CreationDate>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <EffectiveDate>20230110 074618</EffectiveDate>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <ExpirationDate />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <UseByDays xsi:nil="true" />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <Remark />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <RecipeHeaderId>23851</RecipeHeaderId>\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <ProductDensity xsi:nil="true" />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <ContaminationCode />\xa0\xa0\xa0\xa0\xa0\xa0\xa0 <Materials />\xa0\xa0\xa0\xa0\xa0 </ProductDefinition>\r\n\r\nCan you please delete these?\n\n### Response:\n["Comment 1: [\'same problem for 970125-B25", "Comment 2: 970136 and 960893-B25: Please check\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'select h.* --into DH_Exchange_NL_PROD.dbo.RecipeHeader_DGS8297 --delete hfrom DH_Exchange_NL_PROD.dbo.RecipeHeader hleft join DH_Exchange_NL_PROD.dbo.RecipeElement e on rch_id=RcE_RcHIdwhere RcE_RcHId is null and rch_id<>13507\'", "Comment 5: \'Synchronization schould work. Please check.\'", "Comment 6: \'Thans!\'", "Comment 7: \'Hi Thomas,Can we close this task?Regards\'", "Comment 8: \'yes", "Comment 9: thanks\']"]\nRelated Issues:\n[]\n\n### End'}
735	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8296\n\n### Instruction:\nWe have a value after the m2: sign on the technical results. Before this value there is a €-sign. However this is a regular number, there shouldn\'t be an € sign in front of it.\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: \'Printout fixed.\']"]\nRelated Issues:\n[]\n\n### End'}
736	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8295\n\n### Instruction:\nCould you modify the item tax group for this item to G-L please?\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'This must be done in Milas", \'Comment 3: I will handle this.Steffen\', "Comment 4: normally Bessel must be responsible for this.\'", \'Comment 5: "Ok\', \'Comment 6: thank you Mitch\', \'Comment 7: I didn\\\'t know that."\', "Comment 8: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 9: \'Hello,No activity needed for this issue on our side", "Comment 10: soI close the task.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
737	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8294\n\n### Instruction:\nSee attachment\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: "Rounds are counting by customer from field \\\'Customer\\\' and when \\\'Contract type\\\' = \\\'Participation\\\' the field is empty.If value for \\\'Contract type\\\' = \\\'Participation\\\' visible field is \\\'Farmer\\\' and field \\\'Customer\\\' is not visible and empty\', \'Comment 4: but if there is\\\'Contract type\\\' other than \\\'Participation\\\' visible is field \\\'Customer\\\'.Should we in case when \\\'Contract type\\\' = \\\'Participation\\\' counting rounds by field \\\'Farmer\\\'? Or should we fill also field \\\'Customer\\\' with value from field \\\'Farmer\\\' in that case?!image-2023-01-11-12-17-46-959.png!!image-2023-01-11-12-18-48-266.png!"\', "Comment 5: \'I see the full round number is filled in right now on this contract. Is it changed already?In case of participation indeed look at the field customer.\'", \'Comment 6: "{quote}In case of participation indeed look at the field customer.{quote}Did you mean field \\\'Farmer\\\'? Because we don\\\'t have field \\\'Customer\\\' in that case{quote}In case of participation indeed look at the field customer.{quote}Oh\', \'Comment 7: yes\', \'Comment 8: that was changed for this one Contract and field \\\'Customer\\\' was filled (is not visible on document)."\', "Comment 9: \'Yes Farmer in that case.\'", "Comment 10: \'Done,at this point it works fine on both environments the round counter and the round is indicated correctly based on the customer.\']"]\nRelated Issues:\n[]\n\n### End'}
738	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8293\n\n### Instruction:\nWhen SOR-111/09/2022/V using detele marked on screen later not canceled \r\nLater oon it stil appears on the screen.\r\n(Remark : It is not "To Buffer")\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-3!!image-4!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'this document is in the buffer.You may delete it !image-2023-01-10-15-37-31-898.png\|width=528,height=264!If you are trying to delete it do you see get any message?Also In what context user is log on :!image-2023-01-10-15-39-33-081.png!!image-2023-01-10-15-38-33-316.png!\'", "Comment 4: \'While deleting by klicking on OK then it is disapeard from the list. When you later on go back to the list it is back again.!image-1!!image-2!\'", "Comment 5: \'Deleting on screen also gives problems. ( message )!image-5!!image-6!\'", "Comment 6: \'Are you sure that this the same document", \'Comment 7: cause\', \'Comment 8: after deleting this same docuemnt number is using also this document if is generated by erp integrator so it is generated again so at first the VT in dhc shoudl be set as holdthen try to delete it.Error message meant thet someon else is editing document\', "Comment 9: ask this user to close it.Why you want to remove this dosument?\'", "Comment 10: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 11: please raise another task.RegardsAgnieszka Januszewska\']"]\nRelated Issues:\n[]\n\n### End'}
739	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8292\n\n### Instruction:\nASN\'s not sync\'ing to DHP, and not showing in DHC.\r\n13060 and 13061\r\n\r\nThere may be others please confirm for us.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Do zbadania jest", \'Comment 3: dlaczego po zmianie w kartotece kontrahenta\', "Comment 4: zmiana nie synchronizuje się dalej.\'", "Comment 5: \' !screenshot-1! !screenshot-2! \'", "Comment 6: \'Hello", "Comment 7: for the analysis we need a case where no additional operations were performed to synchronize the address.Thank you. Regards.\'", \'Comment 8: "You may close the ticket\', \'Comment 9: we\\\'ve had no further examples."]\']\nRelated Issues:\n[\'DGS-7992\', \'DGS-8171\']\n\n### End'}
740	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8291\n\n### Instruction:\nDHP is goving an error when opened\n\n### Response:\n["Comment 1: [\'!IMG-20230110-WA0002.jpg\|thumbnail!\'", "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-01-10 11:55:21 =CRASH REPORT==== crasher: initial call: rabbit_disk_monitor:init/1 pid: <0.451.0> registered_name: rabbit_disk_monitor exception exit: {could_not_determine_disk_free,[{rabbit_disk_monitor,get_disk_free,2,[{file,"src/rabbit_disk_monitor.erl"},{line,261}]},{rabbit_disk_monitor,internal_update,1,[{file,"src/rabbit_disk_monitor.erl"},{line,217}]},{rabbit_disk_monitor,handle_info,2,[{file,"src/rabbit_disk_monitor.erl"},{line,167}]},{gen_server,try_dispatch,4,[{file,"gen_server.erl"},{line,689}]},{gen_server,handle_msg,6,[{file,"gen_server.erl"},{line,765}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,226}]}]} ancestors: [rabbit_disk_monitor_sup,rabbit_sup,<0.280.0>] message_queue_len: 0 messages: [] links: [<0.450.0>] dictionary: [] trap_exit: false status: running heap_size: 4185 stack_size: 28 reductions: 298049373 neighbours:2023-01-10 11:55:21 =SUPERVISOR REPORT==== Supervisor: {local,rabbit_disk_monitor_sup} Context: child_terminated Reason: could_not_determine_disk_free Offender: [{pid,<0.451.0>},{id,rabbit_disk_monitor},{mfargs,{rabbit_disk_monitor,start_link,[50000000]}},{restart_type,{transient,1}},{shutdown,300000},{child_type,worker}]{code}\\\'\', "Comment 4: \'The rabbit service reported an error", "Comment 5: I had to restart the DHP services.Please check.\'", "Comment 6: \'working please close\']"]\nRelated Issues:\n[]\n\n### End'}
741	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8290\n\n### Instruction:\nCould you please change on invoice number 9/12/2022 payer to De Heus s.r.o. Kendice 146, 082 01 Kendice SK ?\r\n\r\nNumber of customer is 0674\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: \'Payer has been changed - please check.\'", "Comment 3: \'Payer has been changed\'", "Comment 4: \'Thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'}
742	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8289\n\n### Instruction:\nVT-5653/12/2022/VP not accepted and give no message.\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: \'The document for VT has been generated", "Comment 4: it is the last one before the changes in 21/12/2022.(DGS-7827)\'", "Comment 5: \'Ticket can be closed\']"]\nRelated Issues:\n[\'DGS-7827\']\n\n### End'}
743	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8288\n\n### Instruction:\nTo verify rights for Steffen and Koen in MAS NL sector.\r\n\r\nThey should have similar rights to Bessel in MAS NL.\n\n### Response:\n["Comment 1: [\'Roles have been added to Steffen and Koen similar to Bessel for MAS NL.Can you confirm on test database", "Comment 2: that is it all correct?\'", \'Comment 3: "Steffen says: At first sight we seem to have access to everything we can in MAS BE.Only difference: If we want to change the conditions on a contract in MAS BE\', \'Comment 4: we can assign this task to a colleague from Belgium\', "Comment 5: I don\'t think this is already the case in MAS NL for us.Secondly", \'Comment 6: all contracts are also under your name. We can get to this via the shared inbox\', \'Comment 7: but it should remain that way."\', "Comment 8: \'Stefen and Koen have the same rights and roles as Bessel but may not be holders of documents that were created before they were granted these roles.\']"]\nRelated Issues:\n[]\n\n### End'}
744	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8287\n\n### Instruction:\nWe accidently opened round B100014/0208/0003 (ID 83601) + Feed Sale FE-B/0568 (ID 83602) while this customer has a new contract. Therefor we opened round B100014/0237/0001 (ID 83681), round 1 on a new contract. We would now like you to delete B100014/0208/0003 (ID 83601) + Feed Sale FE-B/0568 (ID 83602) (we checked, this round is empty and there won\'t be any documents sent to this round anymore) and modify the total round number of B100014/0237/0001 (ID 83681) from 4 to 3. Thank you\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Round B100014/0208/0003 (ID 83601) and feed saleFE-B/0568 (ID 83602) are deleted. Update round Number onB100014/0237/0001 (ID 83681).\']"]\nRelated Issues:\n[]\n\n### End'}
745	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8286\n\n### Instruction:\nBulk item code = 302551 recipe not sent from DHC to DHP\r\nFG item code = 302551-B50 recipe sent not correct from DHC to DHP\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'The Recipes are using in Wirifa Entity. \'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'!image-2023-01-10-14-15-24-830.png!\'", "Comment 5: \'I have corrected item linking and resynced recipes and technology.Please", "Comment 6: verify if now it is fine for you.Regards\'", "Comment 7: \'i have checked the recipes", \'Comment 8: for 302551 already correct\', \'Comment 9: but for 302551 still have different ingredients with DHC\', "Comment 10: please check again.!image-3!!image-4!\'", "Comment 11: \'i mean 302551-B50 stil not correct\'", "Comment 12: \'For302551-B50 you need to have new version of the Recipe from DHH.Regards\'", "Comment 13: \'OK", "Comment 14: let me make new one\'", "Comment 15: \'i have make a new one on DHC", "Comment 16: still not sync to the DHP for new version\'", "Comment 17: \'item 302551-B50 is Additional Technology that created by ourselfe on DHC", "Comment 18: DHH just provide us for bulk item recipe 302551\'", "Comment 19: \'I still cannot see it in DHH. Please", "Comment 20: let me know when version 3 will be available i DHH. New version of recipe needs to be created and then production recipe and technology.!image-2023-01-10-16-00-08-310.png!\'", \'Comment 21: "it is not recipe from DHH\', \'Comment 22: it\\\'s additional technology from DHC!image-5!"\', "Comment 23: \'before", \'Comment 24: if i add new version for additional technology\', \'Comment 25: it will sync to DHP also\', \'Comment 26: but in this case 302551-B50 version come to DHP but have ingredient like Recipe\', \'Comment 27: it should be same with additional technology that i Inputed\', \'Comment 28: like detail below:Version : 302551-B50\', "Comment 29: item Code 302551-B50 content : - 302551- FC302550- BB302550\'", "Comment 30: \'hello,could you help us? because we need to process this item in production\'", "Comment 31: \'Any update?\'", "Comment 32: \'hello\'", "Comment 33: \'Hi,Please ask formultaion in DHH to sent new version of recipe for item302551. Then you will be able to accept and create technology for302551-B50. I have already checked", "Comment 34: there is no new version of the recipe in DHH.Regards\'", "Comment 35: \'Version 2 for item 302551 already newest version", "Comment 36: how we able to explain to formulation to make new version with same ingredient?could you give explanation why they must input new version again? \'", "Comment 37: \'The question is why the latest version of technology for 302551-B50 not sync to DHP\'", "Comment 38: \'Version 2 is version from the 9th of January. The point is that linking of the item was incorrect. Best mix item was linked to B50", \'Comment 39: not to bulk item as it should be. I have corrected linking\', "Comment 40: but version 2 from the 9th of January with incorrect Technology was sent. Recipes do not resync. New version needs to be created with the correct item linking.\'", "Comment 41: \'linking was used 302551", \'Comment 42: like picture below\', "Comment 43: but why it can be link to 302551-B50?!image-2!\'", "Comment 44: \'Previously in marked field it was302551-B50. As I mentioned twice", "Comment 45: I have corrected it yesterday.!image-2023-01-11-09-37-33-513.png!Regards\'", "Comment 46: \'Ok let me ask to fomulation first\'", "Comment 47: \'Thank you. Waiting for your feedback then.Regard\'", "Comment 48: \'Hi Recipe versio 3 already created and accepted", \'Comment 49: and new technology for 302551-B50 already created also\', "Comment 50: but 302551-B50 in DHP still using wrong ingredient. please kindly check.\'", "Comment 51: \'Please", "Comment 52: check now the newest version in Plant.Regards\'", "Comment 53: \'still wrong ingredient .it should be like thisVersion : 302551-B50content :302551FC302550BB302550!image-6!\'", "Comment 54: \'Additional Technology always has version 0. Under db of DHC I can see that there are subversion 0 and 1. Subversion 1 is the freshest.Please change filter in marked fields and let me know. I have used your screenshot as we do not have access to plant Wirifa", "Comment 55: we have access only to plant Bekasi!image-2023-01-11-11-18-18-328.png!\'", "Comment 56: \'this is correct sample for different product!image-7!\'", "Comment 57: \'!image-2023-01-11-11-22-19-145.png!!image-2023-01-11-11-22-34-520.png!\'", "Comment 58: \'If for product302551-B50 it is still incorrect", "Comment 59: please provide us with:>> application server ip>> sql server ip>> login and password for access.Regards\'", "Comment 60: \'>> application server ip : 10.62.25.9>> sql server ip : 10.62.25.6>> login and password for access.!image-8!\'", "Comment 61: \'Hiplease confirm is that below your name for user to our server?!1!\'", "Comment 62: \'I am new user for you. My user name should be Aleksandra PrzybylekRegards\'", "Comment 63: \'Please provide your email here", "Comment 64: our infrastructure team will send you credential to your email.\'", "Comment 65: \'my email: [[email protected]\|mailto:[email protected]]also please", "Comment 66: if it is possible access for user [email protected]\'", "Comment 67: \'Hi Aleksandra,please check email from me.\'", "Comment 68: \'Here your access to DHP Environment.User : Apac\\\\\\\\ Aleksandra.PrzybyłekPassword : yy7CE6jUH.\'", "Comment 69: \'hi any update today?\'", "Comment 70: \'Dear Esabella,We are still working on this issue but unfortunately", "Comment 71: we do not have official information about supporting the new plant Wirifa on Service Desk. I will contact Eric Quang to confirm all the needed information.We will back with more information as soon as possible.Regards\'", \'Comment 72: "Hi Katarzyna,Please send back confirmation asap\', \'Comment 73: because our production team stuck in PCS\', \'Comment 74: they can\\\'t continue bagging proses."\', \'Comment 75: " !screenshot-1! !screenshot-2! !screenshot-3! we can\\\'t access to servers\', \'Comment 76: please verify."\', "Comment 77: \'Hi,Do you connect using VPN?\'", \'Comment 78: "From server 103.60.180.254:5001and domain @Apac !screenshot-4! I don\\\'t have VPN for this."\', "Comment 79: \'Please try connect again\'", "Comment 80: \'Usinv domain @apac.corp.deheus.com\'", "Comment 81: \'Please confirm if you can connect well to the server\'", "Comment 82: \'Now i have for [email protected] !screenshot-5! \'", "Comment 83: \'Please try again", "Comment 84: we already register your user\'", "Comment 85: \'If additional technology is to be used they have the number 0 of the recipe", "Comment 86: such a filter should be selected in DHP. !screenshot-6! \'", "Comment 87: \'Do you mean that the 1st version is the wrong recipe? Can you disable the 1st version so it will be default to the correct last version \'", "Comment 88: \'There are recipes in DHC that were incorrectly created due to incorrectly linked items(base item). They should not be used - version 1 and 2.When it comes to additional technology these are recipes that always have a number zero and there is a subversion numbering.Please specify what recipe is to be used for production.\'", "Comment 89: \'Second one", "Comment 90: 0 number with no subversion\'", \'Comment 91: "Second one\', \'Comment 92: 0 number with no subversionyou mean the second version of the recipe?why can\\\'t you use the third one?"\', "Comment 93: \'For recipe bulk item we use the third one", \'Comment 94: I mean for additional technology\', "Comment 95: 302551-B50\'", \'Comment 96: "let\\\'s chat via teams"\', "Comment 97: \'Sure", "Comment 98: please call me [email protected]\'", "Comment 99: \'już wiem o co chodzi pcs tak działa u nich że bierze ostatnie receptury", "Comment 100: tutaj jest poprawnie: !screenshot-7! i tak samo ma być dla 302551 !screenshot-8! pakowany ma być jako additional technology nie z receptury.\'", "Comment 101: \'Please check should be correct now. !screenshot-9! \'", \'Comment 102: "Zmiana na szybko dla kolejnych -1,-2,-3.{code:java}\\\\t update r\\\\t set rch_version=\\\'-1\\\' FROM [DHP_Wirifa].[dbo].[RecipeHeader] r where RcH_ArtId=1577 and RcH_Id in(3959,4020,4037){code}"\', "Comment 103: \'Hello", "Comment 104: unfortunately we have to do additionally check the data in exchange.I would like login details to connect to the exchange database.Please wait for our comment.Thanks.\'", "Comment 105: \'ok we waiting for your comment\'", "Comment 106: \'hi already check transaction for this item after production run process. everything looks correct.\'", "Comment 107: \'wpadło dobrze !screenshot-10! \'", "Comment 108: \'Thank you for confirmation", "Comment 109: recipes for item 302551-B50 have been removed only additional ones have been left.Regards.\'", "Comment 110: \'OK thank you\'", "Comment 111: \'Ticket has been closed.\'", "Comment 112: \'hi team", \'Comment 113: our way of working for version 1\', "Comment 114: sub 0 or sub 1 is normal. Please note that. \']"]\nRelated Issues:\n[]\n\n### End'}
746	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8285\n\n### Instruction:\nDzień dobry, \r\n\r\nproszę o realizację poniższego zgłoszenia:\r\n\r\n"Potrzebuję przekodować zbiornik 3020 z 0829 \r\narginina na 1047 Izoleucyna przy próbie zmiany wyświetla się komunikat \r\n„Zmiana zablokowana przez plan produkcji”. Zbiornik ten nie bierze udziału w aktualnej produkcji jest wyczyszczony i wyzerowany."\r\n\r\nW przypadku dodatkowych pytań proszę o kontakt z Business Reporterem\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "{code:java}\\\\tSELECT *FROM Leczyca_Pre_DB.dbo.produkcjeWHERE (pro_id = 210817006){code}this production should be ended !screenshot-1! We don\\\'t have acccess to change. !screenshot-2! "\', "Comment 3: \'[[DHP] [PCS]Zmiana zablokowana przez plan produkcji\|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHP.one#%5bDHP%5d%20%5bPCS%5dZmiana%20zablokowana%20przez%20plan%20produkcji&section-id=\\\\\\\\{F3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9}&page-id=\\\\\\\\{66909BBC-34D1-4B4B-819F-A0512B92551B}&end] ([Widok sieci Web\|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHP.one%7CF3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9%2F%5BDHP%5D%20%5BPCS%5DZmiana%20zablokowana%20przez%20plan%20produkcji%7C66909BBC-34D1-4B4B-819F-A0512B92551B%2F%29])\'", "Comment 4: \'pro_dhp_koniec changed to 1 \'", "Comment 5: \'Confirmed by phone", "Comment 6: can we close?\'", "Comment 7: \'Thank you for your help. Please close task. \']"]\nRelated Issues:\n[]\n\n### End'}
747	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8284\n\n### Instruction:\nHello,\r\n\r\nCL000013342 and CL000013644 are not arriving in DHP Andel, in DHC the CL is accepted, but it\'s not visible in DHP Andel. Queues are not full, so can you check the reason\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'!image-2023-01-10-08-48-52-709.png!Nie ma tej drugiej!image-2023-01-10-08-52-10-559.png!\'", "Comment 3: \'Hi,Please", "Comment 4: confirm if the numberCL000013644 is correct.Regards\'", "Comment 5: \'CL0000133644 is not yet in DHC. We are checking that one in Webmethods now.\'", "Comment 6: \'Please", "Comment 7: let me know about the result then.\'", "Comment 8: \'But we do have CL000013342 in DHC and it is missing in DHP\'", "Comment 9: \'Yes", \'Comment 10: I know. But when investigating I cannot be sure if reason for both is the same. I found out thatCL0000133644 is not in DHC\', "Comment 11: that is why I asked if the number is fine\'", "Comment 12: \'!image-2023-01-10-09-30-20-775.png!\'", \'Comment 13: "But this is clipped with Order from different plant. Shouldn\\\'t the order number be with 5 in the beginning?Regards!image-2023-01-10-09-54-26-075.png!"\', "Comment 14: \'That is indeed not correct. The order was created for Veghel and the call off is for Andel... I will check this.\'", "Comment 15: \'Thank you. Please", "Comment 16: let us know if it helped.Regards\'", "Comment 17: \'Prio can be lowered to 2.We asked purchase to correct the call off and resend it.\'", "Comment 18: \'Sure", \'Comment 19: thank you. Please\', "Comment 20: also ask purchase to check if data onCL000013644 is correct.Regards\'", "Comment 21: \'Andel-Mest!image-2023-01-11-07-33-23-811.png!\'", "Comment 22: \'Hi,I can seeCL000013644 is in plant now. However,CL000013342 is still not corrected. Do you need any help from our side?Regards\'", "Comment 23: \'It still needs correction in Milas from De Heus side.\'", "Comment 24: \'Thank you.Waiting for feedback then.\'", "Comment 25: \'We send a new Load from Milas. However", "Comment 26: in DHC it still links to the old contract (for Veghel) and intake is not send to DHP/PCS.Can you delete the old contract and intake?!image!\'", "Comment 27: \'W Veghel jest to zamówienie z problematycznym CL i ASN!image-2023-01-11-10-50-41-337.png!\'", "Comment 28: \'Dla tego CL mamy dwa ordery i dwa ASNy!image-2023-01-11-11-46-04-211.png\|width=1252,height=575!!image-2023-01-11-11-58-09-962.png!\'", \'Comment 29: "{code:java}SELECT ForeignNumber\', \'Comment 30: Description\', \'Comment 31: DocumentCode\', "Comment 32: * FROM [DHCountry_NL_AS400_PROD].[dbo].[ShippingNotices] where ForeignNumber = \'5-L000097667\' or ForeignNumber = \'8-L000097667\' SELECT * FROM [DHCountry_NL_AS400_PROD].[dbo].[OrderElements] where OrderId = \'EAF7B6B6-05B1-47A7-89CA-A45279A050F2\' or id = \'A34663E7-AE17-418C-A4DE-A281BCFC3AB2\' SELECT DocumentNumber", "Comment 33: * FROM [DHCountry_NL_AS400_PROD].[dbo].[Orders] where id = \'EAF7B6B6-05B1-47A7-89CA-A45279A050F2\' or DocumentNumber = \'5-L000097667\' SELECT TOP (1000) [Id] ,[ShippingNoticeElementId] ,[OrderElementId] ,[Quantity] FROM [DHCountry_NL_AS400_PROD].[dbo].[ShippingNoticeElementOrders] where ShippingNoticeElementId in( \'4E4C470D-92EE-4A95-9C8E-CA6E6D248256\'", \'Comment 34: \\\'E0510CFC-B0BF-4B48-870E-BA1F78228454\\\') SELECT * FROM [DHCountry_NL_AS400_PROD].[dbo].[ShippingNoticeElements] where ShippingNoticeId = \\\'970F431D-CDC2-4A25-BF64-87762A24FBF7\\\' or ShippingNoticeId = \\\'C07AA110-FCD2-48DA-81D1-2FEA77A2169B\\\'-- SELECT --FROM [DHCService_NL_AS400_PROD].[dbo].[ShippingNoticeExportInfoes] where EntityId = \\\'970F431D-CDC2-4A25-BF64-87762A24FBF7\\\'-- SELECT -- FROM [DHCService_NL_AS400_PROD].[dbo].[ShippingNoticeElements] where ShippingNoticeId = \\\'970F431D-CDC2-4A25-BF64-87762A24FBF7\\\'{code}"\', \'Comment 35: "{code:java}SELECT * FROM [Evolution_DHCERP_NL_AS400_Identities].[dbo].[AdvancedShippingNoticeElementMappings] where dhcid = \\\'E0510CFC-B0BF-4B48-870E-BA1F78228454\\\' or dhcid = \\\'4E4C470D-92EE-4A95-9C8E-CA6E6D248256\\\'SELECT * FROM [Evolution_DHCERP_NL_AS400_Identities].[dbo].[AdvancedShippingNoticeMappings] where DhcId = \\\'C07AA110-FCD2-48DA-81D1-2FEA77A2169B\\\' or dhcid = \\\'970F431D-CDC2-4A25-BF64-87762A24FBF7\\\'SELECT * FROM [Evolution_DHCERP_NL_AS400_Identities].[dbo].[OrderElementMappings] where dhcid = \\\'68162A60-03E4-4C32-88A2-EC2A320CCFFF\\\'SELECT * FROM [Evolution_DHCERP_NL_AS400_Identities].[dbo].[OrderMappings] where dhcid = \\\'EAF7B6B6-05B1-47A7-89CA-A45279A050F2\\\' or dhcid =\\\'A34663E7-AE17-418C-A4DE-A281BCFC3AB2\\\'{code}"\', "Comment 36: \'z mapowań wpisy z 5 usunąć- restart erpservice- wysyłka zamówienia z 8.i podmiana.\'", "Comment 37: \'Please resend order 8-L000097667", "Comment 38: thank you.\'", "Comment 39: \'The call off must be send to Andel (location 5). The original order and call-off were created for Veghel (location 8) and the correction I think was not done correctly / not processed correctly. I resend the load for this call off from Milas: Load 5-L000103315This update is not processed due to duplicate key issue...Resending the load 8-L000097667 from Milas (to cancel it)", "Comment 40: does not seem to be possible because it seems to be deleted from Milas...Can you delete all references to CL000013342? Then we will retry.!image-1!\'", "Comment 41: \'We are working on it. We need information on what orders are to be linked to these ASNs:SN-1251/2023SN-4059/2023SN-4175/2023SN-3118/2023\'", "Comment 42: \'Only location where I can check SN numbers and links with (purchase) orders is in DHC Shipping notices (SN number is generated in DHC). Load numbers SN-1251/2023: not foundSN-4059/2023 not foundSN-4175/2023 this is the call off that we need in Andel", \'Comment 43: It is now linked to order 5-L000097667 (seems to be an order for Andel now\', \'Comment 44: at start\', \'Comment 45: this was an order for Veghel (8-....). Call off is not in DHP. I tried to resend call off from DHC. It is exported to DHP (13/1/2023 10:02 \', "Comment 46: but it does not seem to arrive in DHP. PErhaps it is still in the queue?SN-3118/2023: not found\'", "Comment 47: \'Hello", "Comment 48: please verify for Andel !screenshot-1! \'", \'Comment 49: "{code:java}SELECT * FROM [Evolution_DHCERP_NL_AS400_Identities].[dbo].[AdvancedShippingNoticeElementMappings] where dhcid = \\\'E1790C03-95EF-4CC1-B58C-0B3BDE7FE53F\\\' SELECT * FROM [Evolution_DHCERP_NL_AS400_Identities].[dbo].[AdvancedShippingNoticeMappings] where DhcId = \\\'0C2A7168-1D28-49B3-8F2A-7C5F8C494564\\\'SELECT * FROM [Evolution_DHCERP_NL_AS400_Identities].[dbo].[OrderElementMappings] where dhcid = \\\'68162A60-03E4-4C32-88A2-EC2A320CCFFF\\\'SELECT * FROM [Evolution_DHCERP_NL_AS400_Identities].[dbo].[OrderMappings] where dhcid = \\\'EAF7B6B6-05B1-47A7-89CA-A45279A050F2\\\' or dhcid =\\\'A34663E7-AE17-418C-A4DE-A281BCFC3AB2\\\'{code}"\', "Comment 50: \'Ok", "Comment 51: thank you. ASN arrived. Plant will register intake on it. Did you take any action to get intake in DHP? Or did it just take a longer time?\'", "Comment 52: \'We had to changed statuses for ASN elements and left only SN-4175/2023", \'Comment 53: changed the data for the ASN and relation to the order document in DHC databases\', "Comment 54: changed the order element for correct one and resent the ASN to DHP.\'", "Comment 55: \'Ok", "Comment 56: thanks for the explanation. This task can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
748	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8283\n\n### Instruction:\nWarehouse tasks for dispatch cannot be completed. Please check/fix following cases: \r\n\r\nWO(PD)-42/1/23 cannot be closed even after re-selecting the stock from warehouse. VT and WO do seem to have correct status.\r\n\r\n\r\nWO(PD)-43/1/23 cannot be viewed/edited/processed. The detail screen does not open for this WO.\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: \'43/1/23 !screenshot-1! 42/1/23 usunięto wydanie dla elementu i teraz powinno działać.\'", "Comment 4: \'42/1/23 - I canceled the realization. Please process again !screenshot-2! 43/1/23Please check this item has two stock units with different units !screenshot-4! \'", "Comment 5: \'WO(PD)-42: I could now select stock and close WO. So", \'Comment 6: we can use the eraser in cases like this.WO(PD)-43: item seems to be managed in Pcs. To handle the WO\', "Comment 7: must we cancel the quantiy in Kg?\'", "Comment 8: \'I corrected WD-57/1/23 for correct unit ", "Comment 9: please check now.\'", "Comment 10: \'!image-2023-01-10-12-40-21-900.png!\'", "Comment 11: \'Ok", "Comment 12: I could now open the WO and complete it. This task can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
749	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8282\n\n### Instruction:\nIn DHP Utrecht, VT-88/1/23 cannot be closed because of missing stock for e.g. 704961-BB 992Kg\r\nThis BB was produced. Lot report is confirmed. \r\nIn Item history, I see that this production is reserved for the VT.\r\nOn the VT itself there is not reservation done for this item and no stock is available\r\nWhy is the 992Kg not reserved for this VT?\r\nHow can we fix this?\r\nSame for other BB in this order and possible for other VT\'s as well.\r\n\r\nNote on 02-01-2023 (date on which Lot report and VT were created) there were issues with DHP database. Perhaps this is related? \r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!!image-3!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "FROM [DHPlantStockBusinessLogicMain].[dbo].[ReleasedReservations] where SourceDocumentNumber=\\\'0072020123037\\\'"\', \'Comment 4: "select top 10 * from stockunits where Barcode=\\\'7-S00F8I\\\'"\', \'Comment 5: "lot id=\\\'\\\'3A852532-ED3F-4D61-AC76-CF9457879FF2\\\'\\\'"\', "Comment 6: \'Wg eventów na stocku ktos usunal rezerwacje ?!image-2023-01-10-09-31-01-788.png!\'", "Comment 7: \'!image-2023-01-10-09-33-49-537.png!\'", "Comment 8: \'Could you please try to close the VT and check if any error occurs?\'", "Comment 9: \'On closing of VT I still get the same error: missing stock for all three BB items\'", "Comment 10: \'System.ArgumentException: Unit mismatch\'", \'Comment 11: "brak wpisow dla inteków dla itemaselect * from [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketBulkIntakeElements]where itemid=\\\'738E3F89-3CFC-439D-85F8-FDC9B41BB252\\\' select * from [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketPieceIntakeElements]where itemid=\\\'738E3F89-3CFC-439D-85F8-FDC9B41BB252\\\'"\', "Comment 12: \'info od Oli M.mi to wyglada na to", \'Comment 13: ze status vt jest zły\', \'Comment 14: bo juz rozchód poszedł dla tych itemów bulkowych\', \'Comment 15: dla pakowanych nie wiem (pewnie tez)\', \'Comment 16: WO juz są executed. Do pełni szczęścia chyba tylko brakuje zamknięcia tego vt !https://statics.teams.cdn.office.net/evergreen-assets/personal-expressions/v2/assets/emoticons/winktongueout/default/30_f.png?v=v12\|width=20!ale nie sprawdzałam tego dokladnie fest\', "Comment 17: wiec nie weim\'", \'Comment 18: "select * from StockUnits su--join DHPlantstockBusinessLogicMain.dbo.stockunits --ssu on ssu.id=su.Idwhere itemid in ( \\\'68C40430-E321-4F30-97C9-65F45A01D6BC\\\',\\\'738E3F89-3CFC-439D-85F8-FDC9B41BB252 \\\',\\\'F0D753EE-3283-4412-B80B-D919DD51E080 \\\')"\', "Comment 19: \'teraz jest missing quantity : !image-2023-01-11-13-05-07-492.png!\'", "Comment 20: \'Hello,It seems that something unusual situation took place when there were problems with servers.We fixed status via database - please verify.\'", "Comment 21: \'Ok", "Comment 22: VT is now closed. This ticket can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
750	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8281\n\n### Instruction:\nhi,\r\nWe have Vt need to release for Intake but when click release button, it show error.\r\nWe have facing it before so we need why show that error and how to fix it?\r\nNote: this is Plant Can Tho(ID 437) but it not in list so that why i booked it ALL\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: \'ustalenia ze standup. Prośba o sprawdzenie.\'", "Comment 3: \'Now we have 1 more VT can not release: VT 1287!image-1!\'", "Comment 4: \'Wygląda na to", \'Comment 5: że dwóch użytkowników próbuje przeprocesować ten sam dokument.: [^VT 1287.png]\', \'Comment 6: [^VT-808.png]Niestety nie udało mi się odtworzyć tego na środowisku z RF (151).Udało się natomiast doprowadzić do sytuacji\', \'Comment 7: gdzie arrival date nie jest uzupełniona:1. Jako user A tworzę planowane VT na postawie itema ale pozostaje na formie "Add VT elements" (nie klikam save)- VT jest w statusie planned i nie ma elementów2. User B akceptuje to VT- VT jest w statusie created- Arrival date jest wypełniona !arrival!3. User A klika "Save" na widoku "Add Vt element"- arrival date zostaje usunięta !brak arrival! [^arrival_brak.mp4] \\\']\']\nRelated Issues:\n[\'DGS-8275\', \'DGS-8276\', \'DGS-8921\']\n\n### End'}
751	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8280\n\n### Instruction:\nWe cannot close the VT ticket, it says that there are no goods on the stock, we checked in DHP and Comarch, there are goods in stock.\r\n\r\nCan you please check?\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} FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where ItemId=\\\'427E2B7F-90FC-42D0-9C03-44B68C6FC76B\\\' and Quantity>0 and QuantityOnHand>0{code} !screenshot-2! {code:java}FROM [DHPlantVCBusinessLogicMain].[dbo].[Deliveries] where id=\\\'184A1F86-3A49-417F-8CE7-E368977AF685\\\'{code} !screenshot-3! "\', "Comment 4: \'VT-116/1/22 delivery is created for packed item(packing form),for Bulk should be created.\'", "Comment 5: \'How can we solve it", "Comment 6: can you fix it?\'", "Comment 7: \'If the definition of the item is correct and it looks like it is a new delivery has to be made.This delivery should be released for example by inventory.\'", "Comment 8: \'Can you explain to me step by step what needs to be done in order to properly close this VT?\'", "Comment 9: \'It would be best to make the inventory !screenshot-4! !screenshot-5! and increase it to bulk - but there is no such.Will there be new delivery for this product?\'", "Comment 10: \'Hello", "Comment 11: any news about this case?Thank you and regards.\'", "Comment 12: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
752	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8279\n\n### Instruction:\nPlease explain where such serial numbers come from? How the system generates them?\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \' !screenshot-1! do przerobienia trigger logowania zmian na nagłówku jest info o user.!image-2023-01-09-13-14-42-136! !image-2023-01-09-13-14-58-914!Przykład z tego roku na podstawie ZW i Tripa!image-2023-01-09-13-23-46-066! !image-2023-01-09-13-24-07-007!i Golub!image-2023-01-09-13-26-44-303!\'", "Comment 4: \'zgodnie z rozmową.\'", "Comment 5: \'Hello,These entries are ZW based transfers (with mobile scanning).If it goes from A to B then it is 1x 027984384848 and if he goes from B to C later it will be done 1x 1x 02798438484.This issued Serial Number is entered into the text field and mobile adds the number of pallets or bags issued in this element at the beginning.\'", "Comment 6: \'This is not correct. The system cannot change the serial number of the goods. Besides", "Comment 7: such changed serial number is taken on the SOR document!image-2!\'", "Comment 8: \'!image-2023-01-25-07-12-56-134.png!\'", "Comment 9: \'Po stand up\\\\r\\\\rdoszły numery dostaw z cyframi np. 5 x za początku dla SO.\\\\r\\\\rCzy wycenić analizę dalszą? Ewentualnie ile by zajęło aby uprzedzić klienta.\\\\r\\\\rDzięki.\'", "Comment 10: \'any news?\'", "Comment 11: \'Z mojego punktu widzenia klient może składać GDC do tego zgłoszenia a DGS powinien być zamknięty.\'", "Comment 12: \'Hello", "Comment 13: if changes are to be made GDC should be created (changes for registration of the serial numbers when selling from mobile DHP).Or functionality can be removed if that is the case.\'", "Comment 14: \'Klient się upiera że to nie jest kwestia poprawnego działania systemu", \'Comment 15: problem od marca/kwietnia 2022\', "Comment 16: po aktualizacjach DHC - informacja klienta z retro.\'", "Comment 17: \'[[email protected]] I rzeczywiście może mieć rację. Mam przebłyski w pamięci z przed wielu lat", \'Comment 18: że ten temat pojawił się w ramach DHC 2.5. Trzeba by się zagłębić w meandry kodu DHC 2.5 żeby to potwierdzić. Rzeczywiście wydaje mi się\', "Comment 19: że były robione jakieś zmiany na synchronizacji w starym WS i/lub DHC 2.5 żeby to się tak nie przesyłało.\'", "Comment 20: \'https://helpdesk.kotrak.com/browse/GDC-837\'", "Comment 21: \'Thank you for creating GDC", "Comment 22: further implementation of the change in GDC.DGS ticket has been closed.\']"]\nRelated Issues:\n[\'DGS-8208\']\n\n### End'}
753	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8278\n\n### Instruction:\nHello,\r\n\r\nwe have for intake VT\'s on location Andel where the intake quantity is 6 times the quantities send back. The VT\'s have status intake completed, but I\'m not able to correct this to the right quantities. \r\nVT numbers are:\r\nVT-351/12/22, should be 27040 kg\r\nVT-353/12/22, should be 43080 kg\r\nVT-354/12/22, should be 38060 kg\r\nVT-356/12/22, should be 29580 kg\r\nVT-357/12/22, should be 26840 kg\r\n\r\nCan you help to correct and close these VT\'s? Attached you find the messages send by the pcs:\r\n\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: \'!image-2023-01-09-12-38-34-894.png!\'", "Comment 4: \'!image-2023-01-09-12-39-52-907.png!\'", \'Comment 5: "VT-353/12/22 Id = \\\'fa5f4b9c-64e9-4dbd-9727-b57c63f3441b\\\'Wszystkie VT są na ten sam item\', \'Comment 6: item code: 1195!image-2023-01-10-07-47-09-953.png!!image-2023-01-10-07-47-09-953!"\', \'Comment 7: "{code:java}SELECT * FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTickets] where Id = \\\'fa5f4b9c-64e9-4dbd-9727-b57c63f3441b\\\'SELECT * FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketBulkIntakeElements] where OrderId = \\\'5F7FD6D6-FE94-424E-B273-7F842F012F7E\\\' SELECT * FROM [DHPlantVCBusinessLogicMain].[dbo].[Orders] where Document = \\\'PO-2904/10/22\\\'{code}{code:java}SELECT * FROM [DHPlantWmsBusinessLogicMain].[dbo].[VehicleTicketElements] where OrderId = \\\'5F7FD6D6-FE94-424E-B273-7F842F012F7E\\\'{code}{code:java}SELECT * FROM [DHPlantStockBusinessLogicMain].[dbo].[VehicleTicketElements] where orderid = \\\'5F7FD6D6-FE94-424E-B273-7F842F012F7E\\\'SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[VehicleTicketElements] where OrderId = \\\'5F7FD6D6-FE94-424E-B273-7F842F012F7E\\\'SELECT * FROM [DHPlantPCSBusinessLogicMain].[dbo].[VehicleTicketElements] where orderid = \\\'5F7FD6D6-FE94-424E-B273-7F842F012F7E\\\'{code}"\', "Comment 8: \'!image-2023-01-09-14-11-20-933.png!!image-2023-01-09-14-03-00-853.png!!image-2023-01-09-14-03-19-290.png!!image-2023-01-09-14-11-20-933!\'", "Comment 9: \'Dear Thomas,What quantity was taken into the stock? The correct one? Because it is not only the case of changing quantity on VT. What about stock then?Regards\'", "Comment 10: \'The incorrect quantity was taken into stock", "Comment 11: which should also be corrected to the quantities mentioned below\'", "Comment 12: \'!image-2023-01-09-14-36-41-761.png!\'", "Comment 13: \'Dla VT 353/12/22 nie ma elementu dla Andel!image-2023-01-09-15-03-00-363.png!\'", "Comment 14: \'We think that better", \'Comment 15: cheaper and faster option would be to do an inventory for those items. Please\', "Comment 16: let us know how should we perform further.Regards\'", "Comment 17: \'But how can I close the VT;s?\'", \'Comment 18: "Because I cannot change stock units as long status = \\\'in progress\\\'?"\', "Comment 19: \'Hi,It is possible to close VT from the list:!image-2023-01-10-10-16-32-215.png!But", \'Comment 20: when you close the VTs\', \'Comment 21: stock status will change. Then you can perform the inventory. But the quantity on VT will not change then. Only stock will change after the Inventory.Please verify if this is suitable for you. If you have any hesitation\', "Comment 22: please let us know.Regards!image-2023-01-10-10-16-32-215!\'", "Comment 23: \'Hi Aleksandra", \'Comment 24: if I try to close it from the list\', "Comment 25: I get this error message: !afbeelding-1!\'", "Comment 26: \'We need to consult this case", "Comment 27: I will let you know as soon as possible.Regards\'", "Comment 28: \'These are other intakes with same issue: Note that those are all for location 98", \'Comment 29: Andel-Mest. I checked for VT-141/1/23 and this is the JSON message received: {"Intakes":[{"VehicleTicketNumber":"VT-141/1/23","DeliveryId":5539,"ArticleCode":"1195","Quantity":29300,"SupplierDocumentQuantity":29320,"IsPartial":false,"BargeEmpty":null,"IntakeDate":"2023-01-11T01:00:00Z","CountryOfOrigin":"NL"}]}So somehow DHP duplicates this value 6 times!afbeelding-2!\\\'\', "Comment 30: \'Thank you Thomas", "Comment 31: this is crucial information for us. Are you able to estimate how long does the Andel-Mest 98 is working?Regards\'", \'Comment 32: "I\\\'m not sure if I understand your question? We configured it correct since last week of december or someting"\', "Comment 33: \'!image-2023-01-11-07-50-31-117.png!!image-2023-01-11-07-51-40-667.png!!image-2023-01-11-07-52-20-537.png!!image-2023-01-11-07-52-41-815.png!\'", "Comment 34: \'Sprawdzic:BulkIntakeRegisteredEvent\'", "Comment 35: \'Na przykładzie VT-351", "Comment 36: dane przyszły z PCSa!image-2023-01-16-08-36-18-607.png!\'", "Comment 37: \'Tak samo VT-353!image-2023-01-16-08-39-48-420.png!\'", "Comment 38: \'Any update?\'", "Comment 39: \'!image-2023-01-16-14-59-01-954.png!\'", \'Comment 40: \\\'W przedziale czasowym!image-2023-01-17-07-44-56-412.png!Dla VT-351!image-2023-01-17-07-30-55-041.png!!image-2023-01-17-07-35-21-079.png!{code:java}// code placeholderBody{"Intakes":[{"VehicleTicketNumber":"VT-351/12/22","DeliveryId":3964,"ArticleCode":"1195","Quantity":27040,"SupplierDocumentQuantity":27040,"IsPartial":false,"BargeEmpty":null,"IntakeDate":"2022-10-11T02:00:00Z","CountryOfOrigin":""}]}{code}Potem jest już kolejny impacted VT - VT-353!image-2023-01-17-07-44-35-495.png!!image-2023-01-17-07-46-23-633.png!\\\'\', \'Comment 41: \\\'{code:java}--HEADER IMPORT{ "Accept": [ "application/json" ]\', \'Comment 42: "Content-Length": [ "30" ]\', \'Comment 43: "Content-Type": [ "application/json; charset=utf-8" ]\', \'Comment 44: "Expect": [ "100-continue" ]\', \'Comment 45: "Host": [ "172.23.1.91:94" ]}--HEADER REGISTER{ "Accept": [ "application/json" ]\', \'Comment 46: "Content-Length": [ "235" ]\', \'Comment 47: "Content-Type": [ "application/json; charset=utf-8" ]\', \'Comment 48: "Expect": [ "100-continue" ]\', \'Comment 49: "Host": [ "172.23.1.91:94" ]}--BODY REGISTER {"Intakes":[{"VehicleTicketNumber":"VT-353/12/22","DeliveryId":3966,"ArticleCode":"1195","Quantity":43080,"SupplierDocumentQuantity":43080,"IsPartial":false,"BargeEmpty":null,"IntakeDate":"2022-10-13T02:00:00Z","CountryOfOrigin":""}]}{code}ilość jest poprawna - taka\', "Comment 50: jak powinna być. Tyko jeden wpis\'", "Comment 51: \'!image-2023-01-17-08-43-17-161.png!\'", "Comment 52: \'[[email protected]]Maciek", \'Comment 53: sprawdziłam zgodnie z Twoimi wytycznymi\', "Comment 54: ale może coś dojrzysz Twoim mądrzejszym okiem :)\'", "Comment 55: \'[[email protected]] przedstawiam procedurę mojej analizy:1. Sprawdzić eventy wysłane z PCS !events_sent_from_pcs! 2. Sprawdzić ile razy przetwarzany był event w module VC !vc_processing! 3. Sprawdzić logi tekstowe w module VC !vc_logs! W logach pojawia sie bład: PurchaseOrderReceiptForBusinessUnitNotConfiguredMessages4. Wejść do konfiguracji w module VC !por_VC_Config! Wygląda na to że nie ma skonfigurowanego drugiego Business Unita dla Andel. Czyli pokrywa sie to z tym co pisałaś chodzi o ten drugi Andel uruchomiony pod koniec grudnia.Po wprowadzeniu poprawnej konfiguracji problem zostanie rozwiązany.\'", "Comment 56: \'[[email protected]]dzięki Ci wielkie <3\'", "Comment 57: \'Dear Thomas,Andel - Mest is not configured. Please", "Comment 58: let us know if you manage to do that or you need our help.Regards!image-2023-01-17-10-40-57-153.png!\'", "Comment 59: \'To avoid mistakes", "Comment 60: could you configure it correct?\'", "Comment 61: \'Done. Andel Mest has been configured!image-2023-01-17-13-51-55-453.png!\'", \'Comment 62: "we tested in and we\\\'re able to change. New intakes are also OK now. Thanks\', \'Comment 63: ticket can be closed"\', "Comment 64: \'Thank you.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
754	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8277\n\n### Instruction:\nCan you create access to Intense for:\r\n * Henriette van Gorp ([email protected]) - rights like Nancy van Dam\xa0\r\n * Tim van Drie - rights like Mitch van Bovene\n\n### Response:\n["Comment 1: [\'The accounts have been created in Intense Platform.\'", "Comment 2: \'Can we close the task?\'", "Comment 3: \'Yes", "Comment 4: sorry for not informing you earlier.\']"]\nRelated Issues:\n[]\n\n### End'}
755	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8276\n\n### Instruction:\nProConco Can Tho\r\n\r\nPlease check on picture\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-01-09-09-12-23-743.png!\'", "Comment 4: \'Hello,It should be fine now. Please verifyRegards.\'", "Comment 5: \'hi team", "Comment 6: please close this ticket.\'", "Comment 7: \'DGS-8281 RCA has been created.\']"]\nRelated Issues:\n[\'DGS-8281\']\n\n### End'}
756	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8275\n\n### Instruction:\nhi,\r\nWe have Vt need to release for Intake but when click release button, it show error.\r\nWe have facing it before so we need why show that error and how to fix it?\r\nNote: this is Plant Can Tho(ID 437) but it not in list so that why i booked it ALL\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Now we have 1 more VT is 808 with same issue\'", "Comment 4: \'Hello,Yes I can see you have created P1 task for VT 808. We are investigating 606 as well.Regards\'", "Comment 5: \'VT 606 is cancelled. Should we investigate further or just investigate VT 808? But I can see there was no arrival date and this caused the issue!image-2023-01-09-09-13-48-218.png!Regards!image-2023-01-09-09-13-48-218!\'", "Comment 6: \'yes", "Comment 7: please go ahead with VT 808\'", "Comment 8: \'The issue is solved underDGS-8276. Can we close this task?Regards\'", \'Comment 9: "what is problem? we\\\'re facing it day by day"\', "Comment 10: \'In this task we have focused on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue", \'Comment 11: we may raise RootCause Analysis (RCA)task for you.Please\', "Comment 12: let us knowhow you wish us to proceed.Regards\'", "Comment 13: \'yes please process RCA for this issue. Cause we are facing with it\'", "Comment 14: \'The RCA task is under:DGS-8281. Please", "Comment 15: confirm if you have access.Regards\'", "Comment 16: \'yes i can access. you can close this ticket\'", "Comment 17: \'Thank you.Regards\']"]\nRelated Issues:\n[\'DGS-8281\']\n\n### End'}
757	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8274\n\n### Instruction:\n If De Heus Voeders (B005059) is chosen as reference on a regular purchase invoice (the leading doc) than the sales invoice that is created from it is initially created as a registered sales invoice.\r\n\r\nCould this be changed to a regular sales invoice?\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "In this case we have dependence that when on Purchase Invocie there is CustomerB005059 orB805059 then during generation Sales Invoice is set Type of sale = \\\'Registered\\\'. This is scenario from column \\\'R\\\' in Relation Table I think.So after changes on SI should be always the same \\\'type of sale\\\' like chosen on source PI \\\'type of purchase\\\'\', \'Comment 3: right? Is this change should be applied only to MAS BE sector?!image-2023-01-09-15-26-24-027.png!"\', \'Comment 4: "Indeed\', \'Comment 5: only in MAS BE it must be changed. In MAS NL it doesn\\\'t need to be changed. There we still used registered in most cases."\', "Comment 6: \'Done on test database.\'", \'Comment 7: "A manually created regular PI where the reference (and thus the customer on the following SI) is B005059 De Heus Voeders doesn\\\'t lead to a registered sale invoice anymore. This can be implemented in PROD\', \'Comment 8: thank you.!image!"\', "Comment 9: \'Done at production and uat\']"]\nRelated Issues:\n[]\n\n### End'}
758	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8273\n\n### Instruction:\nSometimes it happens that by accident an SR is archived without creating the invoices from it first.\r\n\r\nCan we built in a warning massage in Intense whenever an SR is archived without any invoices has been created from 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: "We can add condition on performing flow to \\\'Archive\\\'.If there will be no invoices generated from SR system will not allow user perform the flow.Is it ok or are there any cases when Slaughtery Report shouldn\\\'t have any invoices?"\', "Comment 3: \'Powinno być dodane ostrzeżenie", "Comment 4: nie powinniśmy blokować możliwości wysłania dokumentu do archiwum.!image-2023-01-10-10-50-40-056.png!\'", "Comment 5: \'MASBEIF not EXISTS (SELECT Doc_ID AS [ID]", \'Comment 6: Doc_FullNumber AS [Number] FROM Documents WHERE Doc_LeadingDocID = @CurrentID@ AND Doc_DdfID = 43) and not EXISTS (SELECT si.Doc_ID\', "Comment 7: si.Doc_FullNumber FROM Documents AS pi JOIN Documents AS si on si.Doc_LeadingDocID = pi.Doc_ID AND pi.Doc_DdfID = 43 AND si.Doc_DdfID = 42 WHERE pi.Doc_LeadingDocID = @CurrentID@) and @DocTypeID@ =46 SELECT @Warning@\'", "Comment 8: \'MASNLIF not EXISTS (SELECT FROM DocumentsWHERE Doc_LeadingDocID = @CurrentID@AND Doc_DdfID = 14)and not EXISTS(SELECT FROM Documents AS piJOIN Documents AS si on si.Doc_ID = pi.Doc_LeadingDocID AND pi.Doc_DdfID = 13 AND si.Doc_DdfID = 14WHERE si.Doc_LeadingDocID = @CurrentID@)and @DocTypeID@=12select @Warning@\'", "Comment 9: \'Solution applied on a test base\'", "Comment 10: \'This seems fine in the test environment", "Comment 11: thank you.!image!\'", "Comment 12: \'Done at production database.\']"]\nRelated Issues:\n[]\n\n### End'}
759	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8272\n\n### Instruction:\nPlease add columns:\r\n* Delivery date\r\n* Reference \r\n\r\nTo the document list in Intense.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Could you specify to which document we should displays these fields?Only to Purchase Invoices and Sales Invoices or any others?\'", "Comment 3: \'Do poprawienia przy okazji wyświetlanie kolumny Type of sale/purchase. Póki co działa tylko dla dokumentów PI/SI z MAS NL.\'", \'Comment 4: "Do dodania kolumny \\\'Delivery date\\\' i \\\'Reference\\\' dla typów dokumentów SI oraz PI na liście dokumentów."\', "Comment 5: \'Added to documents list. * Delivery date * Reference\'", "Comment 6: \'Thank you is done.\']"]\nRelated Issues:\n[]\n\n### End'}
760	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8271\n\n### Instruction:\nAdd column to Inbox BP-tax group\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Hi [[email protected]]\', \'Comment 3: the BP TAX Group have multiple values for invoices. Is it possible that for one invoice we have different values? If yes\', \'Comment 4: we can displayseparate values by for example sign \\\';\\\'."\', \'Comment 5: "I don\\\'t expect on one invoice (mind it is about purchase invoices) to have multiple BP Tax Groups. We are always dealing with one business partner/supplier."\', "Comment 6: \'[[email protected]]", \'Comment 7: according to your answer\', "Comment 8: we will add a column with one value.Best regards,Grzegorz\'", "Comment 9: \'[[email protected]] the new column is on Inbox view. You can feel free to test it.Best regards,Grzegorz\'", "Comment 10: \'This can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
761	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8270\n\n### Instruction:\nIn the rounds and Financial Statement we want to have some more division. Now all eggs are presented in the same category but we would like to separate this into:\r\n\r\nEieropbrengsten (item code EIOP, this can be presented in the current category Eggs)\r\nBroedeieren (item code BROE)\r\nConsumptie eieren (item code CONS)\r\nDubbeldooiers (item code DUBB)\r\nKleine broedeieren (item code KLEB)\r\n\r\nThis means we need to add 4 categories on the rounds. This also means we need to have 4 additional sections in the Financial Statements.\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 should be separate divisions on Details tab only or also on General tab on Financial statement?Are there needed subtotals for each new division on Details tab?!image-2023-01-18-11-23-08-112.png!!image-2023-01-18-11-23-40-718.png!\'", "Comment 3: \'Please make this division on the General tab as well and add subtotals.\'", "Comment 4: \'We added new tabs on test database Can you confirm it and we will process it at production.\'", "Comment 5: \'Move to PROD\'", "Comment 6: \'Moved to production\']"]\nRelated Issues:\n[]\n\n### End'}
762	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8269\n\n### Instruction:\nKINDLY ASSIST TO OPEN THE NEW PERIOD 2023 AND SHOW US HOW TO DO SAME\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: \'Creating new period:1. System-> Comfiguration-> Accounting -> Accounting periodsGreen plus icon - create new periodSave !screenshot-1! 2. System- change period !screenshot-2! \'", "Comment 3: \'HiI would like to add:After creating new period you need to generate a chart of accounts", \'Comment 4: i.e. transfer a chart of accounts from the previous period.Accounting module -> Tools -> Transfer of chart of accounts.You can transfer all accounts at once or do it partially using option "selected"After tranferring chart of account you can post documents in new period. !screenshot-3! \\\'\', "Comment 5: \'thank you we on on it and it is working fine if we meet any unforseen situation will seek for help. Regards\']"]\nRelated Issues:\n[]\n\n### End'}
763	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8268\n\n### Instruction:\nCould you move all bookings from:\r\n00095Q/0283/0001\r\n\r\nTo:\r\n\r\n009449/0228/0001\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: "Should we change only Sales Invoices and Purchase Invoices ?\|32061\|PI-RLM/2022/0085\|\|32062\|PI-RLM/2022/0086\|\|80471\|SI-RLM/2022/3488\|\|80472\|PI-RLM/2022/2152\|\|80473\|SI-RLM/2022/3489\|\|32449\|SI-RLM/2022/0086\|\|32450\|SI-RLM/2022/0087\|\|76538\|PI-FNM/2022/0358\|\|76539\|SI-FNM/2022/0346\|\|80474\|PI-RLM/2022/2153\|Some of these invoices have been sent to Milas\', \'Comment 3: so should we change rounds for these documents?If we should change Round is it means that we also should change Reference/Supplier on SI\\\'s and PI\\\'s to 009449 everytime where on Invoice exists00095Q?"\', \'Comment 4: "SI\\\'s\', \'Comment 5: PI\\\'s and also the Feed sales.Yes we can also change the rounds on documents that are already send to Milas. And indeed if the round is changed you also should change Reference/Supplier on SI\\\'s and PI\\\'s to 009449 everytime where on Invoice exists 00095Q. Very smart idea."\', "Comment 6: \'Sales", "Comment 7: purchase invoice and feed are moved to009449/0228/0001 from00095Q/0283/0001 round.Can you confirm it to us?\'", "Comment 8: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
764	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8267\n\n### Instruction:\nGood afternoon,\r\n\r\nwe have got a problem with Salesorder: SO-0000038550 on DHP.\r\nIt\'s not create in Vehicle Control.\r\n\r\nPlease would you so kind to solve this issue?\r\n\r\nKind regards,\r\n\r\nGerard Geerts\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 Gerard.Order is not in VC module as there is issue with customers and addresses:Target Business Partner has correct address but Main Business Partner and Payer have incorrect addresses. They have Target\\\'s address assigned. When you correct address for MAin and Payer\', \'Comment 4: please resend Sales Order from ERP system once again. When addresses are correct\', \'Comment 5: they will appear in VC module.Regards"\', "Comment 6: \'!image-2023-01-09-07-54-20-866.png!\'", "Comment 7: \'Good morning Aleksandra,Thanks for your reply on this issue.We are going to investigate on our side and waiting for feedback.. Please keep this serviceticket open!Regards,Gerard\'", "Comment 8: \'Good morning.Sure", "Comment 9: waiting for your feedback then.Regards\'", "Comment 10: \'Good afternoon Gerard,Do we have any feedback?Regards\'", "Comment 11: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 12: please raise another task.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
765	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8266\n\n### Instruction:\ndetailed description is in the attached document\n\n### Response:\n["Comment 1: [\'[^I added 2 column to the report.docx] _(1,93 MB)_\'", "Comment 2: \'Dear Kotrak Engineer,Could you help for update this issue? we are need you response. Thank you.\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'Hi Adrian,Thank you for your response", "Comment 5: we waiting for the result.\'", "Comment 6: \'Hello,Could you please provide me with exact path of executing this report? Is it a Test report as in screenshot below?Regards!image-2023-01-09-10-15-15-542.png!\'", "Comment 7: \'!image-2023-01-10-08-41-20-308.png!!image-2023-01-10-08-41-20-308!\'", "Comment 8: \'Hi", \'Comment 9: correct\', "Comment 10: Test report is the path of report that i mean.\'", \'Comment 11: "{code:java}SELECTdistinctdbo.GetDocumentNumber(VtH_DocType\', \'Comment 12: VtH_DocNumber\', \'Comment 13: VtH_DocMonth\', \'Comment 14: VtH_DocYear\', "Comment 15: null) as \'Document Number\'", "Comment 16: CASE WHEN C1.Vhc_Id is null THEN VtH_VhcNotRegister ELSE C1.Vhc_PlateNumber END as \'Plate Number\'", "Comment 17: CASE WHEN C2.Vhc_Id is null THEN VtH_VhcNotRegister2 ELSE C2.Vhc_PlateNumber END as \'Plate Number Trailer\'", "Comment 18: CAST(VtH_DateInitial as datetime) as \'Entry Date\'", "Comment 19: CW1.Csn_Name as \'Entry Location\'", \'Comment 20: FORMAT(ISNULL(W1.Wgt_Value\', \'Comment 21: 0)\', "Comment 22: \'# ###\') as \'Entry Weight\'", "Comment 23: CAST(W1.Wgt_Date as datetime) as \'Entry 1st Weight Date\'", "Comment 24: CW2.Csn_Name as \'Departure Location\'", \'Comment 25: FORMAT(ISNULL(W2.Wgt_Value\', \'Comment 26: 0)\', "Comment 27: \'# ###\') as \'Departure Weight\'", "Comment 28: CAST(VtH_DateFinished as datetime) as \'Departure Date\'", "Comment 29: (CASE WHEN VtH_Status = 0 THEN \'Intake in progress\' WHEN VtH_Status = 1 THEN \'Dispatch in progress\' WHEN VtH_Status = 2 THEN \'Closure in progress\' WHEN VtH_Status = 3 THEN \'Ticket closed\' ELSE \'Others\' END) as Status", "Comment 30: dbo.CustomersListVehicleTicket(VtH_Id) as \'Target Business Partner\'", \'Comment 31: FORMAT(isnull(E.IntakeWeight\', \'Comment 32: 0)\', "Comment 33: \'# ###\') as \'Intake Weight\'", \'Comment 34: FORMAT(isnull(E.DispatchWeight\', \'Comment 35: 0)\', "Comment 36: \'# ###\') as \'Dispatch Weight\',(case when Ohd_OdhType= 3 THEN FORMAT(isnull((W1.Wgt_Value-E.IntakeWeight-W2.Wgt_Value)", \'Comment 37: 0)\', "Comment 38: \'# ###\') when Ohd_OdhType= 1 THEN FORMAT(isnull((W2.Wgt_Value-E.DispatchWeight-W1.Wgt_Value)", \'Comment 39: 0)\', "Comment 40: \'# ###\') end) as Variance ,vth_id,Ohd_OrderDocumentNumber as PO_SO_Number FROM VehicleTicketHeader LEFT JOIN dbo.VehicleCard C1 ON VtH_VhcId = C1.Vhc_Id LEFT JOIN dbo.VehicleCard C2 ON VtH_Vhc2Id = C2.Vhc_Id LEFT JOIN dbo.Weighbridge W1 ON VtH_Wgt1Id = W1.Wgt_Id LEFT JOIN dbo.Weighbridge W2 ON VtH_Wgt2Id = W2.Wgt_Id LEFT JOIN dbo.ConfigurationWeighbridge CW1 on CW1.Csn_Id = W1.Wgt_CsnId LEFT JOIN dbo.ConfigurationWeighbridge CW2 on CW2.Csn_Id = W2.Wgt_CsnId --LEFT JOIN VehicleTicketElement F ON VehicleTicketHeader.VtH_Id = F.VtE_VtHId and F.VtE_Cancel = 0 --LEFT join VehicleTicketElementOrder G on f.VtE_Id = g.Veo_VtEId LEFT join OrderHeaderDHPStatus H on vehicleticketheader.vth_id= h.Odh_vtHId CROSS APPLY ( SELECT sum(CASE WHEN E.VtE_DirectionType = 1 THEN E.VtE_Weight ELSE 0 END) as IntakeWeight", \'Comment 41: sum(CASE WHEN E.VtE_DirectionType = 2 THEN E.VtE_Weight ELSE 0 END) as DispatchWeight FROM VehicleTicketElement E WHERE E.VtE_VtHId = VtH_Id ) E WHERE (CAST(VtH_DateInitial AS date) BETWEEN cast(44927 as datetime) AND cast(44934.5627313889 as datetime) AND VtH_Status IN (3) ) AND ISNULL(VtH_Transfer\', \'Comment 42: 0) = 0 AND VtH_DocType = 6060 order by VtH_Id DESC{code}"\', "Comment 43: \'!image-2023-01-10-08-42-04-893.png!!image-2023-01-10-08-42-04-893!\'", "Comment 44: \'!image-2023-01-10-08-16-27-146.png!\'", \'Comment 45: "{code:java} CAST(VtH_DateInitial as datetime) as \\\'Entry Date\\\'\', "Comment 46: CW1.Csn_Name as \'Entry Location\'", \'Comment 47: FORMAT(ISNULL(W1.Wgt_Value\', \'Comment 48: 0)\', "Comment 49: \'# ###\') as \'Entry Weight\'", "Comment 50: CAST(W1.Wgt_Date as datetime) as \'Entry 1st Weight Date\'", "Comment 51: CW2.Csn_Name as \'Departure Location\'", \'Comment 52: FORMAT(ISNULL(W2.Wgt_Value\', \'Comment 53: 0)\', "Comment 54: \'# ###\') as \'Departure Weight\'", \'Comment 55: CAST(VtH_DateFinished as datetime) as \\\'Departure Date\\\',{code}{code:java}FROM VehicleTicketHeader LEFT JOIN dbo.VehicleCard C1 ON VtH_VhcId = C1.Vhc_Id LEFT JOIN dbo.VehicleCard C2 ON VtH_Vhc2Id = C2.Vhc_Id LEFT JOIN dbo.Weighbridge W1 ON VtH_Wgt1Id = W1.Wgt_Id LEFT JOIN dbo.Weighbridge W2 ON VtH_Wgt2Id = W2.Wgt_Id LEFT JOIN dbo.ConfigurationWeighbridge CW1 on CW1.Csn_Id = W1.Wgt_CsnId LEFT JOIN dbo.ConfigurationWeighbridge CW2 on CW2.Csn_Id = W2.Wgt_CsnId --LEFT JOIN VehicleTicketElement F ON VehicleTicketHeader.VtH_Id = F.VtE_VtHId and F.VtE_Cancel = 0 --LEFT join VehicleTicketElementOrder G on f.VtE_Id = g.Veo_VtEId LEFT join OrderHeaderDHPStatus H on vehicleticketheader.vth_id= h.Odh_vtHId CROSS APPLY{code}"\', "Comment 56: \'!image-2023-01-10-11-14-31-410.png!!image-2023-01-10-11-13-54-588.png!!image-2023-01-10-11-13-31-280.png!\'", "Comment 57: \'hallo any update for this?\'", "Comment 58: \'The issue is under consultation.Regards\'", "Comment 59: \'hi any update today?\'", "Comment 60: \'hello please give us update for this issue.\'", "Comment 61: \'{code:java}SELECT * FROM [DHP_IND].[dbo].[Weighbridge] where Wgt_Id in(891355,893355) select * FROM [DHP_IND].[dbo].[Users] where Usr_Id in(94) SELECT * FROM [DHP_IND].[dbo].[WeighbridgeLog] where WgtL_VthId=133236 select * from [dbo].[ConfigurationWeighbridge] select VtH_Wgt1Id,VtH_Wgt2Id,* FROM [DHP_IND].[dbo].[VehicleTicketHeader] where VtH_DocNumber=76449 select cw1.,cw2. FROM VehicleTicketHeader LEFT JOIN dbo.VehicleCard C1 ON VtH_VhcId = C1.Vhc_Id LEFT JOIN dbo.VehicleCard C2 ON VtH_Vhc2Id = C2.Vhc_Id LEFT JOIN dbo.Weighbridge W1 ON VtH_Wgt1Id = W1.Wgt_Id LEFT JOIN dbo.Weighbridge W2 ON VtH_Wgt2Id = W2.Wgt_Id LEFT JOIN dbo.ConfigurationWeighbridge CW1 on CW1.Csn_Id = W1.Wgt_CsnId LEFT JOIN dbo.ConfigurationWeighbridge CW2 on CW2.Csn_Id = W2.Wgt_CsnId where VtH_id=133236\\\\t select * FROM [DHP_IND].[dbo].[VehicleTicketHeader] where VtH_id=133236{code}\'", "Comment 62: \'Hello", "Comment 63: from what I see it does not always occur.For example:VT-76447last change by the operator apac\\\\\\\\yadi.supriatna at 2022-12-29 22:52:46 !screenshot-1! VT-76446last change by the operator apac\\\\\\\\yadi.supriatna at 2022-12-29 22:30:19.Were there differences in processing VT?!image-2023-01-13-11-26-54-325!\'", \'Comment 64: "yes correct\', "Comment 65: that\'s not always occur", \'Comment 66: and i already check actual process for scaling vt\', \'Comment 67: it done by normally\', \'Comment 68: in actual vt in and out was did from different scale\', \'Comment 69: but after they input vt out (second scale)\', \'Comment 70: data scale in become changed.do you have any suggestion what user interaction on DHP that make it problem?"\', "Comment 71: \'They Just scan VT using WB out ( WB C) and directly change data WB In. Please give advice\'", "Comment 72: \'When we just open VT form with default Scale is C", "Comment 73: everything become C\'", "Comment 74: \'hallo?\'", "Comment 75: \'We are working on it.Please also attach a recording of how the VT is processed and according to the latest comments(about data scale in become changed).\'", "Comment 76: \'Hi", "Comment 77: here are recording for processed that show data scale become changed\'", "Comment 78: \'Hi,here are recording for processed that show data scale become changed", \'Comment 79: the first image is condition before scaling out process\', "Comment 80: and second one is after scaling out and save the VT.!image!!image-1![^IDDE041 (91128190) - UltraViewer Beta 2023-01-19 10-55-10.zip] _(18,75 MB)_\'", "Comment 81: \'{code:java}select VtH_Wgt1Id,VtH_Wgt2Id,VtH_WgtDispatchId,VtH_WgtIntakeId,* from dbo.vehicleticketheader where vth_id=138664select * from [dbo].[Weighbridge] where wgt_id In(920116,920388,920387)SELECT * FROM [DHP_IND].[dbo].[WeighbridgeLog] where WgtL_VthId=138664 select * from [dbo].[ConfigurationWeighbridge]{code} !screenshot-3! \'", "Comment 82: \'Dosłali filmik i selecta przed i po zamknięciu", "Comment 83: wygląda że faktycznie jest zmiana w DHP jak zamykają.\\\\rw [dbo].[WeighbridgeLog] nie loguje się ta kolumna. tj. Wgt_CsnId\\\\r\\\\r\'", "Comment 84: \'hi", "Comment 85: any update for this issue?\'", "Comment 86: \'ustalenia standup. klient dodał wykres,przy realizacji VT zmienia się nazwa wagi (WGT_CSNID). i dla wykresu są inne dane po zakończonej realizacji.\'", "Comment 87: \'hi,any update for this issue?\'", "Comment 88: \'Hello", "Comment 89: any updates relate this one?\'", "Comment 90: \'Hi Everyone..Please help us to close this ticket. We will consult with Eric to get more information.As his information", "Comment 91: so many customization and configuration by himself for Indonesia.Thank you.\'", "Comment 92: \'No problem. We are closing this task.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
766	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8265\n\n### Instruction:\nwe have problem to link base item for SUR7714-MD, the user added wrong item and now we can\'t fix.\r\n\r\nCould you replace wrong base item and add SUR7714-MD? We need to schedule production in DHP but is not possible till fix base item.\r\n\r\nThank you\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", "Comment 3: \'HeyPlease verify and link other items.. I can also see that there is one recipe for that dhhitem", "Comment 4: please resend the recipe from dhh.\'", "Comment 5: \'Hi Agnieszka,I checked and now is correct", \'Comment 6: you can close this task\', "Comment 7: thank you.\']"]\nRelated Issues:\n[]\n\n### End'}
767	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8264\n\n### Instruction:\nWe need to add payment instructions to the new foreign currency account in the field marked in red in PDF document.\r\n\r\nThis only applies to export invoices.\r\n\r\nDE HEUS Doo Šabac\r\nIBAN: RS35285001406539000285\r\nNAŠA AIK BANKA AD BELGRADE, SERBIA\r\nSwift Code : SABRRSBG\n\n### Response:\n["Comment 1: [\'[^10123cue.pdf] _(54 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hello", "Comment 4: please verify.Printout has been modified. !screenshot-1! \'", \'Comment 5: \\\'Hi Piotr,I just received new instructions from the bank. Instead of "NAŠA AIK BANKA AD BELGRADE\', \'Comment 6: SERBIA" it should be written only "AIK BANKA AD"\', "Comment 7: can you correct it?\'", "Comment 8: \'Corrected :)\'", "Comment 9: \'Tnx Piotr,Everything is fine", "Comment 10: you can close the ticket.\']"]\nRelated Issues:\n[]\n\n### End'}
768	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8263\n\n### Instruction:\nHello,\r\n\r\non VT\'s send to Pcs, the deliveryID is missing. Therefore VTs are refused by the pcs system. Can you please check and solve this?\r\n\r\n{"vehicleTickets":[{"vehicleTicketNumber":"VT-235/1/23","asnNumber":"CL000013172","status":5,"realisationDate":"2023-01-05T02:00:00.0000000+01:00","forwarderCode":"HEU","forwarderName":"HEU","plantId":8,"vehiclePlateNumber":"TRUCK","vehicleTicketLines":[{"loadLineNumber":1,"articleCode":"0010","articleName":"GERST","packingForm":"BLK","itemBaseWeight":0.000000,"itemBaseWeightUnit":"kg","supplierCode":"L002365","supplierName":"Cefetra B.V.","estimatedQuantity":25000.000000,"estimatedQuantityUnit":"kg","countryOfOrigin":""}]},{"vehicleTicketNumber":"VT-238/1/23","asnNumber":"CL000013172","status":1,"realisationDate":"2023-01-05T02:00:00.0000000+01:00","forwarderCode":"HEU","forwarderName":"HEU","plantId":8,"vehiclePlateNumber":"TRUCK","vehicleTicketLines":[{"loadLineNumber":1,"articleCode":"0010","articleName":"GERST","packingForm":"BLK","itemBaseWeight":0.000000,"itemBaseWeightUnit":"kg","supplierCode":"L002365","supplierName":"Cefetra B.V.","estimatedQuantity":25000.000000,"estimatedQuantityUnit":"kg","countryOfOrigin":""}]}]}\n\n### Response:\n["Comment 1: [\'Examples: VT-243/1/23 and VT-238/1/23\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \' !screenshot-1! !image-2023-01-05-13-53-31-574!\'", "Comment 4: \'Can I get an update?\'", "Comment 5: \' !screenshot-2! \'", "Comment 6: \'We are checking why messages to the stock module are not processed.\'", "Comment 7: \'kolejka z jakiegoś powodu rośnie", "Comment 8: mimo restartu puli aplikacji.\'", "Comment 9: \'VT jest in progress", "Comment 10: dostawy jeszcze nie ma bo sie nie utworzyła (przez zablokowany stock). - Ola m.\'", \'Comment 11: \\\'It is still not solved?{"vehicleTickets":[{"vehicleTicketNumber":"VT-257/1/23","asnNumber":"CL000012237","status":1,"realisationDate":"2023-01-05T02:00:00.0000000+01:00","forwarderCode":"HEU","forwarderName":"HEU","plantId":8,"vehiclePlateNumber":"TRUCK","vehicleTicketLines":[{"loadLineNumber":1,"articleCode":"0145","articleName":"CHOCOPOWER","packingForm":"BLK","itemBaseWeight":0.000000,"itemBaseWeightUnit":"kg","supplierCode":"L006858","supplierName":"FeedValid B.V.","estimatedQuantity":25000.000000,"estimatedQuantityUnit":"kg","countryOfOrigin":"*"}]}]}\\\'\', "Comment 12: \'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 13: \'[[email protected]],The stock corrections messages are blocking queues. I bypassed all messages. VTs and PLRs should be comming now. Please check them. Meanwhile I will check what is wrong with stock corrections\'", \'Comment 14: "Oke\', \'Comment 15: thanks for solving. I see deliveryID\\\'s are filled in now. "\', "Comment 16: \'Hello,May we close the task? Or change it priority to p2 ?If there is a need from your sideto investigate the reasonof the issue", \'Comment 17: we may raise RootCause Analysis (RCA)task for you.Please\', "Comment 18: let us knowhow you wish us to proceed.\'", \'Comment 19: "[[email protected]],We found the root cause of this issue. It turned out that PCS keeps sending to DHP stock correction for item 0258 \| SPOEL TARWE LASALOCI which slows down the processing of the queue.Currently\', \'Comment 20: in the DHP there is only one stock unit for that item\', "Comment 21: and the number of received stock corrections is over 17000 that\'s why the processing of messages takes so much time. Please look at the messages received from pcs: !stock_Intakes! .As a temporary solution", \'Comment 22: we created another stock unit from the same delivery\', \'Comment 23: but if the PCS system will keep sending us so many messages the situation will occur once again.Can you please check why the PCS sends so much correction for this item? So far we have received a quantity of over 20187858 kgs from the PCS system for one single stock unit that was created during Opening Balance with 44000 kg.Regards"\', "Comment 24: \'I will contact the PCS supplier regarding this issue\'", "Comment 25: \'Could you please confirm if we can close this task?Regards\'", "Comment 26: \'Yes you can close", "Comment 27: thanks for the help\']"]\nRelated Issues:\n[\'DAP-13164\', \'DGS-8961\']\n\n### End'}
769	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8262\n\n### Instruction:\nCalculated price SOR-143/12/2022/V different from total price. \r\n\r\nWhat is the cause off this problem?\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: \'It seems like an ERP XL issue", \'Comment 4: sometimes this application set wrong values ad document header.This docuemnt is in buffer\', "Comment 5: please delete it and verify if when the erp integrator generate it agaian there will be still wrong values.\'", "Comment 6: \'May we close the task ?\'", "Comment 7: \'May we close the task ?\'", "Comment 8: \'i did not get responce of the requester. I am stil waiting \'", "Comment 9: \'zgłoszenia Berta lubia obrastać patyną. Tutaj była zła wartosc na nagłówku Sor", \'Comment 10: prawdopdobnie jakiś bład erp xl\', \'Comment 11: ( czasem się to zdarza w XL) zasugerowałam by usuneli błedy dok w buforze i zoabczyli jak na nowo im wygeneruje jak dobrze to do zamknięcia.Jesli coś będzie źle to niech podadzą nowy numer SOR trzeba namierzyć źrodłowe SO i zprawdzić tabele cdn.zamvat i po gidnumerze kuknąć jakie tam sa wartości\', "Comment 12: czasem z tego coś się psuło.\'", "Comment 13: \'i did not get responce of the requester. I am stil waiting\'", "Comment 14: \'Waiting for customer then.Regards\'", "Comment 15: \'Internal Jira kode : SDNL-37072\'", "Comment 16: \'Ticket can be closed!image-1!\']"]\nRelated Issues:\n[]\n\n### End'}
770	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8261\n\n### Instruction:\nVT 25/1/23 has duplicated the elements in DHP generated SOR 12 and 13 only 13 synced to DHC.\n\n### Response:\n["Comment 1: [\'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 2: \'[[email protected]],Udało sie znaleźć że w sytuacji kiedy użytkownik kliknie dwa razy przycisk close (a będzie jakikowliek lag) to zorbią sie dwa SORy.\'", "Comment 3: \'Hi,We have finally reproduced this case. It happens under two conditions:>> when user double-clicks close button>> when user clicks close button twice (because there is a delay or lag in database", \'Comment 4: and close button was clicked second time).The issue was consulted with dev team\', "Comment 5: relevant functionality lock will be deployed.Regards\'", "Comment 6: \'[[email protected]] po rozmowie z dev podjąłem decyzję że fix bedzie w 8.5\'", "Comment 7: \'[[email protected]]ok\'", "Comment 8: \'Ok. Do we have a work around or script we can run to clean up the issue?\'", "Comment 9: \'Hello Rey,We do not have workaround", \'Comment 10: only to ask users to click once. This issue will be fixed to prevent / block situation after doubleclick in version 8.5.To verify duplicated documents\', \'Comment 11: you can run below script onDHPlantVCBusinessLogicMain database. It will return SO and VT document that has duplicated SORs:{code:java}SELECT OrderDocument\', \'Comment 12: COUNT(OrderDocument)\', \'Comment 13: VehicleTicketDocumentFROM SalesOrderReleasesGROUP BY OrderDocument,VehicleTicketDocumentHAVING COUNT(OrderDocument) > 1{code}I have checked\', \'Comment 14: there are some\', \'Comment 15: but not too many:UR - one VTKD - 4 VTsKB - 2 VTsMM - 3 VTs.Please\', \'Comment 16: verify documents and let us know what should be further steps\', "Comment 17: as some of them are from 2021.Regards\'", "Comment 18: \'UR - one VT!image-2023-01-18-10-02-45-318.png!KD - 4 VTs!image-2023-01-18-10-02-27-351.png!KB - 2 VTs!image-2023-01-18-10-02-09-340.png!MM - 3 VTs.!image-2023-01-18-10-01-38-353.png!\'", \'Comment 19: "Ok thank you. We\\\'ll use the SQL until 8.5.You may close the ticket."\', "Comment 20: \'Sure. Thank you.Regards\']"]\nRelated Issues:\n[\'DGS-8237\', \'DGS-5761\', \'DGS-7973\', \'DAP-13198\']\n\n### End'}
771	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8260\n\n### Instruction:\nThese yellow invoices should be deleted from the round. They have been wrongly migrated from AS/400.\r\n\r\nWe cannot find these invoices ourselves, that is why we ask you. Maybe there are more than these lines on the invoices, than you can delete them as well.\r\n\r\nThese whole invoices need to be deleted.\n\n### Response:\n["Comment 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: "[[email protected]]\', \'Comment 4: could you send me the file with values? If you have ID\\\'s of this documents it will be helpful."\', \'Comment 5: "For most of them I have ID\\\'s but not all:!image!"\', "Comment 6: \'[[email protected]]", "Comment 7: good. Could you send me the original file? Because I can not use picture in SQL query.\'", "Comment 8: \'[[email protected]]thank you for the file. Documents from yellow lines have been deleted.\'", "Comment 9: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
772	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8259\n\n### Instruction:\nWe have a situation in which there are expenses visible on a Feed sale document. This happens for instance with item 088345 Silo Shot.\r\n\r\nThis item should be presented on the round category expenses. However it is invoiced on the same invoices as feed (its origin is Milas) and I think that is the reason why it is presented on the category feed.\r\n\r\nIt should be presented in the category expenses.\r\n\r\nAnother problem is that we cannot move these expenses in the feed sale document to another round. That seems to be only possible for feed items.\n\n### Response:\n["Comment 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: "I see that this line from Feed sale with item \\\'SILO SHOT\\\' is on Round and Financial Statement on \\\'Expenses\\\' section\', "Comment 4: so that is correct?On feed sales now it\'s not possible to \'Move feed to different round\' when on the line is Item with ItemGroup = \'Expenses\'So", \'Comment 5: is this Item parametrized well? ItemGroup and Possible Round categories?Maybe some soulution is to enable moving this lines to different rounds?Steffen reported me similar topic with this Item in MAS BE\', \'Comment 6: and it should be on Feed section\', \'Comment 7: not on Expenses. System verify displaying on Round/Financial Statement for Feed sale lines by Item (Item Group\', \'Comment 8: Possible Round Categories).!image-2023-01-05-10-14-22-799.png!!image-2023-01-05-10-15-35-806.png!"\', "Comment 9: \'!image-2023-01-05-13-18-06-983.png!\'", "Comment 10: \'[[email protected]]", "Comment 11: done for Feed sale elements on test environment. You can feel free to test it.\'", "Comment 12: \'Można przerzucić zmianę na prod. !image-2023-01-18-13-55-47-311.png!\'", "Comment 13: \'[[email protected]],we moved functionality for production environment.You can feel free to test it.Best regards,Grzegorz\']"]\nRelated Issues:\n[]\n\n### End'}
773	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8258\n\n### Instruction:\nCould you please make the table for the feed sales document higher? We need to scroll a long way down at the moment.\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: \'[[email protected]]resize of Feed Sale table - I done it for all sectors. You can feel free to test it.\'", "Comment 4: \'Great", "Comment 5: this can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
774	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8257\n\n### Instruction:\nCannot generate SI from PI.\r\n\r\nSI was created and then was corrected by credit invoice CSI and now the button Create Sales Invoice is not visible on PI.\r\n\r\nIt should be possible to create invoice again when old invoice has been corrected.\r\n\r\n\xa0\r\n\r\nExample - Doc ID 74779\n\n### Response:\n["Comment 1: [\'Do sprawdzenia gdzie powinna być możliwość ponownego generowania faktur. PI z SI i SI z PI.\'", "Comment 2: \'To be checked on UAT", "Comment 3: document number that meets the requirements of 74779.Done on UAT.\'", "Comment 4: \'potwierdzone w podlinkowanym DHNLC-1214", "Comment 5: że może być wgrane na Prod\'", \'Comment 6: "Stara funkcja odwołanie do komentarza z funkcjiALTER FUNCTION [dbo].[KR_ButtonVisibleOnInvoices]( @TypeOfDocumentInvoice int /0 - Sales Invoice\', \'Comment 7: 1 - Purchase Invoice/ \', \'Comment 8: @CurrentProcessStateID int \', \'Comment 9: @Doc_LeadingDocID int \', \'Comment 10: @InvoiceType int \', \'Comment 11: @BookedOnSideCheckbox int \', \'Comment 12: @Doc_ID int)RETURNS intASBEGINdeclare @IsGenFromInvoice int,@Result int,@InvoiceGeneratedFromInvoice int,@CorrectedInvoice int = (select IIF((select isnull(Doc_IntColumn2,0) from Documents where Doc_ID = @Doc_ID) != 0,1,0))IF (@TypeOfDocumentInvoice = 0) /Sales Invoice/BEGIN select @IsGenFromInvoice = (select IIF((select Lead.Doc_DdfID from Documents Lead where Lead.Doc_ID = @Doc_LeadingDocID) in (13,25,28,43,51,57) /All DDF_ID of PI/ OR exists (select PI.Doc_DdfID from Documents SI join Documents PI on SI.Doc_ID = PI.Doc_LeadingDocID where SI.Doc_ID = @Doc_ID and PI.Doc_DdfID in (13,25,28,43,51,57)) /All DDF_ID of PI/ ,1,0)) select @InvoiceGeneratedFromInvoice = (select IIF(isnull((select top 1 Doc_ID from Documents where Doc_DdfID in (13,25,28,43,51,57) and Doc_LeadingDocID = @Doc_ID),0) = 0 ,0,1))--select @IsGenFromInvoice = (select IIF((select Lead.Doc_DdfID -- from Documents Lead -- where Lead.Doc_ID = @Doc_LeadingDocID) in (13,25,28,43,51,57) /All DDF_ID of PI/ -- OR (select PI.Doc_DdfID -- from Documents SI -- join Documents PI on SI.Doc_ID = PI.Doc_LeadingDocID -- where SI.Doc_ID = @Doc_ID) in (13,25,28,43,51,57) /All DDF_ID of PI/ -- ,1,0)) select @Result = IIF(@InvoiceType = 557 /Registered SI type/ OR @ISGenFromInvoice = 1 /old condition: OR @CurrentProcessStateID in (241\', \'Comment 13: 242\', \'Comment 14: 243\', \'Comment 15: 244\', \'Comment 16: 245\', "Comment 17: 246) /All Waiting for approval nodes/ / /old condition: (23,94,97,166,187,194) /All entry\'s node/ / OR @BookedOnSideCheckbox = 1 OR (SELECT Doc_DdfID FROM Documents WHERE Doc_ID = @Doc_LeadingDocID) = 12 OR @InvoiceGeneratedFromInvoice = 1 OR @CorrectedInvoice = 1 ", \'Comment 18: 0\', \'Comment 19: 1)ENDIF (@TypeOfDocumentInvoice = 1) /Purchase Invoice/BEGIN select @IsGenFromInvoice = (select IIF((select Lead.Doc_DdfID from Documents Lead where Lead.Doc_ID = @Doc_LeadingDocID) in (14,24,29,42,52,58) /All DDF_ID of SI/ OR exists (select SI.Doc_DdfID from Documents PI join Documents SI on PI.Doc_ID = SI.Doc_LeadingDocID where PI.Doc_ID = @Doc_ID and SI.Doc_DdfID in (14,24,29,42,52,58)) /All DDF_ID of SI/ ,1,0)) select @InvoiceGeneratedFromInvoice = (select IIF(isnull((select top 1 Doc_ID from Documents where Doc_DdfID in (14,24,29,42,52,58) and Doc_LeadingDocID = @Doc_ID),0) = 0 ,0,1))--select @IsGenFromInvoice = (select IIF((select Lead.Doc_DdfID -- from Documents Lead -- where Lead.Doc_ID = @Doc_LeadingDocID) in (14,24,29,42,52,58) /All DDF_ID of SI/ -- OR (select SI.Doc_DdfID -- from Documents PI -- join Documents SI on PI.Doc_ID = SI.Doc_LeadingDocID -- where PI.Doc_ID = @Doc_ID) in (14,24,29,42,52,58) /All DDF_ID of SI/ -- ,1,0)) select @Result = IIF(@InvoiceType = 554 /Registered PI type/ OR @ISGenFromInvoice = 1 /old condition: OR @CurrentProcessStateID in (241\', \'Comment 20: 242\', \'Comment 21: 243\', \'Comment 22: 244\', \'Comment 23: 245\', "Comment 24: 246) /All Waiting for approval nodes/ / /old condition: (23,94,97,166,187,194) /All entry\'s node/ / OR @BookedOnSideCheckbox = 1 OR @InvoiceGeneratedFromInvoice = 1 OR @CorrectedInvoice = 1 ", \'Comment 25: 0\', \'Comment 26: 1)END RETURN @Result;END"\', "Comment 27: \'Solution moved to production database\'", \'Comment 28: "The functionality works. However users don\\\'t have the rights to push the button. Could you make this available for:Dam\', \'Comment 29: Nancy van <[email protected]>; Geerenstein\', \'Comment 30: Dirco van <[email protected]>; Jong\', \'Comment 31: Christine de <[email protected]>; Meijer\', \'Comment 32: Thelma <[email protected]>; Geijtenbeek\', \'Comment 33: Bert <[email protected]>; Broek\', \'Comment 34: Bessel van den <[email protected]>; Verdam\', \'Comment 35: Anja <[email protected]>; Reimerink\', \'Comment 36: Rick <[email protected]>; Visser\', \'Comment 37: Oscar <[email protected]>; Groot\', \'Comment 38: Erik de <[email protected]>; Driesens\', \'Comment 39: Steffen <[email protected]>; Huibers\', \'Comment 40: Koen <[email protected]>"\', \'Comment 41: "Can you please give one example of a document and a user who can\\\'t use the button,because every user who is in the roleNormal contract administrator and Seniorcontract administrator can generate invoice from every active documents. Only you[[email protected]]and admins have special rights that enable to use everything from archive documents."\', "Comment 42: \'Anja saw the button but it did not work. I pushed it for her so that example no longer holds. I am sure next week we will see a new example", "Comment 43: so I will tell you when I see it.\'", \'Comment 44: "[[email protected]]tu będzie potrzebna zmiana.Jeżeli dokument PI/SI jest już w Archiwum\', "Comment 45: to użytkownicy nie mogą ponownie użyć przycisku \'Create Sales Invoice\' / \'Create Purchase Invoice\'. Widzą przycisk", \'Comment 46: ale jeżeli jest to dokument w Archiwum\', \'Comment 47: to nie mogą i tak go użyć. Trzeba by było tą akcję podpiąć też pod piorun\', \'Comment 48: żeby można było używać to dla dokumentów w Archiwum.Do sprawdzenia czy faktycznie tak jest na teście i czy podpięcie tej samej akcji pod piorun zadziała dla użytkowników\', \'Comment 49: którzy nie mają praw do edycji dokumentów w Archiwum."\', "Comment 50: \'The button is not working when the document is archived (and normally it is archived).This action should be moved under the lightning button.\'", "Comment 51: \'Add action to LIGHTING button to solve problem with archive documents\']"]\nRelated Issues:\n[\'DGS-8158\']\n\n### End'}
775	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8256\n\n### Instruction:\nHi\r\n\r\nWe are creating some internal reports in DHP 3.0, for all plants.\r\nOne of these reports stands for physical quantity of the item on stock.\r\nWe are using the following instruction we copied from ItemStock report you created to get the wanted SUs:\r\n{noformat}\r\nSELECT * FROM DHPlantStockBusinessLogicMain.dbo.StockUnits WHERE LogisticStatus & 86 = LogisticStatus\r\n{noformat}\r\n\r\nHowever we have some SUs that is not being get from this query, like you can see in attached screenshot of item GCM3512-S30.\r\nWhen looking to _WMS -> Warehouse stocks -> Unit loads_ screen, we can see full quantity of item: 5250kg\r\nBut when we look to the result of the query above, the quantity is: 2550kg\r\n\r\nThe query condition is excluding WLFS and WLFP status.\r\n\r\nCould you please send me the right query condition to get the SUs also with WLFS or WLFP status?\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'132 - WLFS388 - WLFS\|WLFP\'", \'Comment 4: "{code:java}SELECT LogisticStatus,count() FROM DHPlantStockBusinessLogicMain.dbo.StockUnits WHERE LogisticStatus & 86 = LogisticStatusgroup by LogisticStatusSELECT LogisticStatus,count() FROM DHPlantStockBusinessLogicMain.dbo.StockUnits WHERE LogisticStatus & 388 = LogisticStatusgroup by LogisticStatusSELECT LogisticStatus,count() FROM DHPlantStockBusinessLogicMain.dbo.StockUnits WHERE LogisticStatus & 390 = LogisticStatusgroup by LogisticStatusSELECT LogisticStatus,QualityStatus, FROM DHPlantStockBusinessLogicMain.dbo.StockUnits WHERE Barcode=\\\'83-W0930Q\\\'select LogisticStatus,QualityStatus,* FROM DHPlantStockBusinessLogicMain.dbo.StockUnits where logisticstatus=132{code}!image-2023-01-11-10-18-50-357!"\', "Comment 5: \'HiDo we have any progress about this?Thank you\'", "Comment 6: \'Hello", "Comment 7: yes please check with this {code:java}SELECT * FROM DHPlantStockBusinessLogicMain.dbo.StockUnits WHERE LogisticStatus & 470 = LogisticStatus{code}\'", \'Comment 8: "Hi PiotrNow it\\\'s OK!You can close this taskThank you very much"\', "Comment 9: \'Thank you for confirmation.\\\\r\']"]\nRelated Issues:\n[]\n\n### End'}
776	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8255\n\n### Instruction:\n 140472 and 148114 don\'t arrive in DHP Meppel.\r\n\r\nI do see them in DHH and DHC however. \r\nI also see them in the DHCService_Errors queue, with the message:\r\n\r\nSystem.Data.SqlClient.SqlException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.The statement has been terminated.\r\n\r\nWhat causes this, and how do we solve it?\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "brak itemó i dhh itemów w dhc serviceselect * from DhhItems where code like \\\'148114%\\\'select * from DhhItems where code like\\\'140472%\\\'select * from Items where code like \\\'148114%\\\'select * from Items where code like\\\'140472%\\\'"\', "Comment 3: \'!472.PNG\|thumbnail! !14.PNG\|thumbnail!\'", \'Comment 4: "Recipes are now in the DHP,this error messagewas confusing because the main reason was that the dhhitem was not synchronised to the dhcservice database. Probably after yesterday\\\'s break down not everything synchronised correctly. !472.PNG!"\', "Comment 5: \'OK", "Comment 6: thanks! Do you think we can expect more of these cases? \'", "Comment 7: \'From what I check there are 6 dhhitems that are in dhc country and not in dhc service\|Code\|BestMixCode\|\|112239\|112239.NL\|\|702247\|702247.NL\|\|116402\|116402.NL\|\|702246\|702246.NL\|\|967341\|967341.NL\|\|506959\|506959.NL\|Do you wish to fixed that for them ?\'", "Comment 8: \'select top 10 s.id as service", \'Comment 9: c.id as country,c.Code,c.BestMixCode\', \'Comment 10: c.BaseItemId\', \'Comment 11: ci.IsArchive\', "Comment 12: ci.Code from [DHCountry_NL_AS400_PROD].[dbo].[dhhitems] cleft join [DHCService_NL_AS400_PROD].[dbo].[dhhitems] s on s.id=c.idjoin [DHCountry_NL_AS400_PROD].[dbo].[items] ci on ci.id=c.BaseItemIdwhere s.id is null\'", "Comment 13: \'Yes please. Afterwards you can close the ticket.\'", "Comment 14: \'HelloI fixed linking and resynchro dhhitems", \'Comment 15: realeted items to them\', \'Comment 16: created recipes\', \'Comment 17: prod reciepes and technologies to dhc service.If there will be something missing in dhp for recipes\', \'Comment 18: prod. reciepes and technologies\', "Comment 19: you may resend them vua DHC application.If there any order or order elements missing please send it again from your erp,br\'", "Comment 20: \'wersja DHC 3.0.60 poprawka jak brakuje dhh items w dhcservice.\'", "Comment 21: \'Hello", "Comment 22: from the version3.0.60 of the application DHC the problem should not occur - this is due to the amount of messages being sent to DHC.Regards.\']"]\nRelated Issues:\n[]\n\n### End'}
777	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8254\n\n### Instruction:\nLocation Sneek frequently reports that dispatch messages are not arriving in DHP. I did a check on some of those today, and we found out those were send by the pcs, but not accepted by DHP due to a 500 error respons from the server. Please find below the orders and the time the dispatch message was send:\r\n Can you please check and hopefully prevent this from happening?\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'I verified the orders in Sneek plant and I can find them in this plant in expected modules f.e.:!image-2023-01-04-17-16-33-585.png!please check if now it is ok.If there is some documents still missing let me know.\'", \'Comment 4: "It\\\'s not about the orders: It\\\'s the Dispatch messages related to the order: Those are send from the PCS and are denied because of a 500 server error\', \'Comment 5: please check"\', \'Comment 6: \\\'2023-01-05 07:05:50 (/Plant.Integration.PCS.NL/DHVD01AP180/3012/148) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/bulk-dispatch/register-bulk-dispatches" responded 500 in 7.2308 ms2023-01-05 13:27:53 (/Plant.Integration.PCS.NL/DHVD01AP180/3012/173) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/bulk-dispatch/register-bulk-dispatches" responded 500\\\'\', \'Comment 7: \\\'2023-01-04 02:11:28 (/Plant.Integration.PCS.NL/DHVD01AP180/3012/56) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "GET" "/api/sales-order/100" responded 500 in 35001.5618 ms2023-01-04 15:49:39 (/Plant.Integration.PCS.NL/DHVD01AP180/3012/111) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/bulk-dispatch/register-bulk-dispatches" responded 500 in 7.8214 ms2023-01-04 23:21:45 (/Plant.Integration.PCS.NL/DHVD01AP180/3012/29) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/bulk-dispatch/register-bulk-dispatches" responded 500 in 8.0117 ms\\\'\', "Comment 8: \'Please verify.\'", \'Comment 9: "Please\', "Comment 10: it\'s not about sending them again: I would like you or development to investigate what goes wrong: The fact that dispatches messages are not processed on time means that the packing slip is not available when they leave. This should not occur", \'Comment 11: so I would like to know what was wrong on that time and how to prevent this from happening"\', "Comment 12: \'Are you still receiving error messages? A few days ago there were problems with the servers - perhaps the problem no longer exists?If so", "Comment 13: does this only apply to these items?Where do you receive - do you see the stated error? Can I ask for a screenshot?\'", \'Comment 14: "I\\\'m now trying to confirm it is better know. Can be related to server errors we had with the DHP database"\', "Comment 15: \'According to your last coment may we close the task?\'", "Comment 16: \'yes please\']"]\nRelated Issues:\n[]\n\n### End'}
778	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8253\n\n### Instruction:\nGood afternoon,\r\n\r\nplease would you so kind to create an openingsbalance for the following items on plant Nijkerk?\r\nitem: 080185-Z10 quantity of 100 kg\r\nitem: 066451-Z20 quantity of 800 kg\r\nitem: 087059-Z20 quantity of 2000 kg\r\n\r\nKinds regards\r\n\r\nGerard\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Dear Gerard,Opening balances for below items have been created.But Item066451-Z20 is not in DHP and DHC. Please", "Comment 3: send it from ERP system.Regards!image-2023-01-05-08-29-23-457.png!!image-2023-01-05-08-36-52-264.png! !image-2023-01-05-08-36-52-264!\'", "Comment 4: \'!image-2023-01-05-08-35-17-310.png!\'", "Comment 5: \'Dear Aleksandra,the itemcode should be: 088451-Z20.Sorry for my mistype / mistakeRegards,Gerard\'", "Comment 6: \'Dear Gerard,Last Opening Balance is created:!image-2023-01-05-09-40-22-865.png\|width=1387,height=262!Regards\'", "Comment 7: \'Hi Aleksandra,thanks for your support.Please", "Comment 8: close this ticket.Kind regards,Gerard\']"]\nRelated Issues:\n[]\n\n### End'}
779	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8252\n\n### Instruction:\nHi\r\n\r\nYesterday we had this DGS-8241. The item + Sales order were integrated, however the recipe/technology of this MTP5266-MD item didn\'t integrated.\r\nCould you please integrate it?\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'Please verify now", "Comment 2: should be ok.\'", "Comment 3: \'Hi AgnieszkaNow is there!Can you please tell me what you did and the reason in raised RCA for this case (DGS-8245)?Thank you\'", "Comment 4: \'I resend the recipes", "Comment 5: production recipes and technologies from the DHC app once again .About RCa we are working on it.!image-2023-01-04-14-13-03-111.png!!image-2023-01-04-14-13-56-066.png\|width=621,height=173!!image-2023-01-04-14-14-37-168.png!May we close this task?\'", "Comment 6: \'Hi AgnieszkaThank you for the informationYou can close this task\']"]\nRelated Issues:\n[\'DGS-8241\']\n\n### End'}
780	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8251\n\n### Instruction:\nHi,\r\n\r\nI will send an e-mail with missing migration files.\r\nPlease let me know when handled.\r\n\r\nChristine\n\n### Response:\n["Comment 1: [\'{color:black}Hi,{color} {color:black}{color} {color:black}Please migrate these missing files.{color} {color:black}Thanks for your support{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image001!{color:blue}{color}{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \|{color:blue}{color} !image002!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \|{color:blue}{color} !image003!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \|{color:blue}{color} !image004!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \|{color:blue}{color} !image005!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| [^Feed migration_Tettero 801200.xlsx] _(250 kB)_[^Purchase_migration_Tettero 801200.xlsx] _(19 kB)_[^Sales migration_Tettero 801200.xlsx] _(14 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'[[email protected]]", \'Comment 4: we have problem with one column. Can you look at "Quantity" of FeedSale file migration?!image-2023-01-04-12-55-59-832.png!\\\'\', "Comment 5: \'{color:black}Excuse me", \'Comment 6: enclosed file with quantity filled.{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Grzegorz Materla (Jira) <[email protected]> Verzonden: woensdag 4 januari 2023 12:57 Aan: Jong\', "Comment 7: Christine de <[email protected]> Onderwerp: DGS-8251 Missing migration 801200 Tettero NAS \| {color:white} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} \| !image006![^Feed migration_Tettero 801200-1.xlsx] _(251 kB)_\'", "Comment 8: \'[[email protected]]one more question about column Contract Farmer Number in FeedSale migration file. Are you sure", "Comment 9: that one FS line is for 68 but others for 69?\'", "Comment 10: \'{color:black}No it should be 68 I forgot to copy the cell{color} {color:black}😊{color}{color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Grzegorz Materla (Jira) <[email protected]> Verzonden: woensdag 4 januari 2023 13:31 Aan: Jong", "Comment 11: Christine de <[email protected]> Onderwerp: DGS-8251 Missing migration 801200 Tettero NAS \| {color:white} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} \| \'", "Comment 12: \'[[email protected]]all data has been migrated into Intense. You can feel free to test it.\'", "Comment 13: \'[[email protected]]", "Comment 14: everything ok with migrated data? Can we close the task?\'", "Comment 15: \'Hi Grzegorz", \'Comment 16: Thanks migration file is in Intense. You can resolve this task as done. Have a good weekend. {color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Grzegorz Materla (Jira) <[email protected]> Verzonden: donderdag 12 januari 2023 14:24 Aan: Jong\', "Comment 17: Christine de <[email protected]> Onderwerp: DGS-8251 Missing migration 801200 Tettero NAS \| {color:white} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} \| \'", \'Comment 18: "Hi [[email protected]],I\\\'m closing the task. Have a nice weekend too.Best regards,Grzegorz"]\']\nRelated Issues:\n[]\n\n### End'}
781	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8250\n\n### Instruction:\nHello, \r\n\r\nwe have received further information from the users that this has not been resolved. not all results are importing.\r\n\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8018\n\n### Response:\n["Comment 1: [\'[^Scans not imported from NIR to DHP .xlsx] _(13 kB)_\'", "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: Umlaas is also experiencing the same issue. \'", \'Comment 5: "{code:java}SELECT a.code as AO,ar.Created_At as \\\'created result\\\' FROM [DHPlantQAMBusinessLogicMain].[dbo].[AnalysisOrders] a left join [DHPlantQAMBusinessLogicMain].[dbo].[AnalysisResults] ar on a.id=ar.AnalysisOrderId where IssueDate>=\\\'2022-12-08\\\' --and IssueDate<=\\\'2022-12-08\\\' and ar.Type=\\\'Imported\\\' order by ar.Created_At desc{code}KB !screenshot-1! UM !screenshot-2! "\', "Comment 6: \'Downloading results for plants:- for KB are up to date !screenshot-3! .UR had the last one in the old year !screenshot-4! Were there connection problems then?Can you re-upload the missing results to the resource and check again?Specify missing as examples (but only after re-sending).\'", "Comment 7: \'Hello", "Comment 8: some are importing others are not. the ones you see had to be rescanned. this one is still failing after multiple attempts (KB). [^20230109100754.CSV] _(0,4 kB)_\'", "Comment 9: \'As it was in the previous task the connection to the KB server is of poor quality during the analysis with such a connection quality there will be problems of this type. !screenshot-5! And now is imported !screenshot-6! \'", \'Comment 10: "Hi PiotrWe\\\'ve aske IT to setup the export to the NIR to explort locally\', "Comment 11: and the lab is now copying the files to the import folder. The one\'s that will just no import we\'ll upload here for you to test", \'Comment 12: but they have already reported that some files need to be copied up to 3 times before they import. The file does not end up in the error/fail folder. It just disapears. Regards "\', "Comment 13: \'Yes", "Comment 14: there can be problems with such an intensity of connection interruptions.The QAM module had 500 errors and a restart of the QAM module was required - here.\'", "Comment 15: \'All these server are on a site. Why would a connection from HQ to KB be an issue for imports that happen locally?\'", \'Comment 16: \\\'{code:java}2023-01-09 13:45:44 (null/Plant.QAM.BusinessLogic/SAKBSRV04/14836/9) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type "Plant.Integration.LabEquipment.Abstractions.Nir.NirResultRegisteredEvent"\', \'Comment 17: message will be discardedKotrak.Extensions.Validation.Abstractions.ValidationException: Validation failed: -- Laboratory result does not contain analysis order number ---> Kotrak.Common.Application.Exceptions.CommandValidationException`1[Plant.QAM.BusinessLogic.Application.Interfaces.Analyses.Results.Commands.RegisterLaboratoryResultCommand]: Validation failed: -- Laboratory result does not contain analysis order number 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.QAM.BusinessLogic.Infrastructure.ContextIntegration.BaseCommandEventHandler`2.Handle(TEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\BaseCommandEventHandler.cs:line 40 at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message) --- End of inner exception stack trace ---2023-01-09 14:39:43 (/Plant.QAM.BusinessLogic/SAKBSRV04/14836/226) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/sampleanalyses/samples" responded 500 in 30036.4366 ms2023-01-09 14:46:34 (/Plant.QAM.BusinessLogic/SAKBSRV04/14836/192) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/sampleanalyses/samples" responded 500 in 30021.5542 ms2023-01-09 14:46:36 (/Plant.QAM.BusinessLogic/SAKBSRV04/14836/12) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP "POST" "/api/sampleanalyses/samples" responded 500 in 30022.2131 ms2023-01-09 15:35:12 (/Plant.QAM.BusinessLogic/SAKBSRV04/14836/213) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Application. ReplyText "Connection close forced"{code}o tej 15:35 poszedł restart.\\\'\', \'Comment 18: "If so\', \'Comment 19: please report if the issue occurs again after yesterday\\\'s service restart."\', "Comment 20: \'Hello", \'Comment 21: after your restart of services certain files still had to be imported more than once before they uploaded. (see highlighted time stamp)we restarted services this morning and attempted an upload for the attached file\', "Comment 22: sample 69230105060 and it still failed (attached csv 20230109164250). !image![^20230109164250.CSV] _(0,5 kB)_\'", \'Comment 23: \\\'mi pobrało. ale wczoraj przed restartem modułu też tak mieliśmy timeouty z dziś:{code:java}2023-01-11 12:04:49 (0e150165-3080-4e71-9f15-71f5daf7b68c/Plant.QAM.BusinessLogic/SAKBSRV04/23340/184) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 24: "host": { "Value": "sakbsrv04:84"\', \'Comment 25: "HasValue": true\', \'Comment 26: "Host": "sakbsrv04"\', \'Comment 27: "Port": 84 }\', \'Comment 28: "path": "/api/sampleanalyses/samples"\', \'Comment 29: "queryString": []\', \'Comment 30: "requestBody": "{\\\\\\\\"sortedColumns\\\\\\\\":[{\\\\\\\\"columnName\\\\\\\\":\\\\\\\\"code\\\\\\\\",\\\\\\\\"order\\\\\\\\":2}],\\\\\\\\"pagingViewModel\\\\\\\\":{\\\\\\\\"pageSize\\\\\\\\":50,\\\\\\\\"pageNumber\\\\\\\\":1},\\\\\\\\"summaryColumns\\\\\\\\":[],\\\\\\\\"types\\\\\\\\":[],\\\\\\\\"issueDate\\\\\\\\":{\\\\\\\\"rangeStart\\\\\\\\":null,\\\\\\\\"rangeEnd\\\\\\\\":null},\\\\\\\\"expirationDate\\\\\\\\":{\\\\\\\\"rangeStart\\\\\\\\":null,\\\\\\\\"rangeEnd\\\\\\\\":null},\\\\\\\\"excludeIds\\\\\\\\":[],\\\\\\\\"laboratoryIds\\\\\\\\":[],\\\\\\\\"laboratoryPlantNumbers\\\\\\\\":[],\\\\\\\\"code\\\\\\\\":\\\\\\\\"692\\\\\\\\"}"}.System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 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.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 40: RunBehavior runBehavior\', \'Comment 41: String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 42: RunBehavior runBehavior\', \'Comment 43: Boolean returnStream\', \'Comment 44: Boolean async\', \'Comment 45: Int32 timeout\', \'Comment 46: Task& task\', \'Comment 47: Boolean asyncWrite\', \'Comment 48: SqlDataReader ds) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Dapper.SqlMapper.ExecuteReaderWithFlagsFallback(IDbCommand cmd\', \'Comment 49: Boolean wasClosed\', \'Comment 50: CommandBehavior behavior) in /_/Dapper/SqlMapper.cs:line 1075 at Dapper.SqlMapper.QueryMultipleImpl(IDbConnection cnn\', \'Comment 51: CommandDefinition& command) in /_/Dapper/SqlMapper.cs:line 1058 at Plant.QAM.BusinessLogic.Infrastructure.Dapper.Samples.SampleReadModel.GetSamplesWithAnalysisOrdersFromDb(Template selector\', \'Comment 52: Int32& totalCount) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Infrastructure.Dapper\\\\\\\\Samples\\\\\\\\SampleReadModel.cs:line 686 at Plant.QAM.BusinessLogic.Infrastructure.Dapper.Samples.SampleReadModel.GetSamplesWithAnalysisOrdersList(ListQuery`1 query) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Infrastructure.Dapper\\\\\\\\Samples\\\\\\\\SampleReadModel.cs:line 623 at Plant.QAM.BusinessLogic.Infrastructure.Api.SampleAnalyses.SampleAnalysesListController.GetSamples(SamplesWithAnalysisOrdersListRequest request) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\SampleAnalyses\\\\\\\\SampleAnalysesListController.cs:line 66 at lambda_method6229(Closure \', \'Comment 53: Object \', \'Comment 54: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 55: ObjectMethodExecutor executor\', \'Comment 56: Object controller\', \'Comment 57: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 58: Scope& scope\', \'Comment 59: Object& state\', \'Comment 60: 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 61: Scope& scope\', \'Comment 62: Object& state\', \'Comment 63: 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 64: Task lastTask\', \'Comment 65: State next\', \'Comment 66: Scope scope\', \'Comment 67: Object state\', \'Comment 68: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited\|17_0(ResourceInvoker invoker\', \'Comment 69: Task task\', \'Comment 70: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited\|17_0(ResourceInvoker invoker\', \'Comment 71: Task task\', \'Comment 72: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask\|6_0(Endpoint endpoint\', \'Comment 73: Task requestTask\', \'Comment 74: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', "Comment 75: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)ClientConnectionId:fb28fa52-0ccb-4046-8f4a-3f0ae3df7447Error Number:-2,State:0,Class:11{code}\'", "Comment 76: \'!image-2023-01-10-12-07-15-580.png!\'", "Comment 77: \'I will consult this issue with the developers and let you know.\'", "Comment 78: \'Na KB mają tak: !screenshot-7! Na MM: !screenshot-8! logi w QAM są timoutywe wcześniejszym komentarzu.\'", "Comment 79: \'Hello", "Comment 80: I can see that the plant KB DB server is using more resources than the other factories. !screenshot-9! Can you restart the server and check?Thank you and regards.\'", "Comment 81: \'po restarcie !screenshot-10! \'", "Comment 82: \'Please check now importing the results after server has been restarted.If there will be still a problem", "Comment 83: please do not restart the application pool.We will then check the QAM operation of the module before restarting to determine the cause.Regards and sorry for the confusing comment.\'", "Comment 84: \'Hello", "Comment 85: we are still experiencing issues 69230109022[^20230109122154.CSV] _(0,5 kB)_\'", "Comment 86: \'backup QAM wysłany na teams - dzięki.\'", "Comment 87: \'MorningWe are still experiencing the issue. I have a teams channel on to support the issue. If you would like to join for further information.!image-1!\'", "Comment 88: \'Hi [[email protected]],We found the root cause of this issue.I created a GDC ticket for this change GDC-843.\'", "Comment 89: \'Hi MaciejDo you know 1. How long it will take to resolve2. will it be fixed in this or 8.53. Is there anything we can do now to work around the issueRegards\'", "Comment 90: \'We need to change the way how results are imported to QAM", "Comment 91: so it can take around one week to develop it. I have a meeting with Theo scheduled for tomorrow so I talk with him about when and to which version it can be delivered. I will let you know about the output of this meeting.So far the only way how we can struggle with that issue is to create a report in DHP and send it to defined recipients about the failed imports.\'", "Comment 92: \'Thank you.\'", "Comment 93: \'And now that we have GDC", "Comment 94: can we close this task?\'", "Comment 95: \'Sure.\']"]\nRelated Issues:\n[]\n\n### End'}
782	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8249\n\n### Instruction:\nLocations are waiting for the intake weight to show up in the ERP for Barges, as they need a closing document from the ERP. We have an example for Utrecht and Maasbracht were the intake weights are not in the ERP, please check.\r\n\r\nFor Utrecht, VT-154/1/23 is in DHC. When checking communication I cannot find anything send to ERP. Please check what is going on in DHC service.\r\n\r\nFor Maasbracht, VT-121/1/23 is in DHC. When checking communication I cannot find anything send to ERP. Please check what is going on in DHC service.\r\n\r\nCan you please check, resend if necessary and perform an analysis of why it is not send?\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: \'There was a deadlock - messages are currently being processed\'", "Comment 3: \'Was it only affecting VT messages", "Comment 4: or also others? Is there some kind of monitoring on this so it is noticed on time before complains are coming in from the business?\'", "Comment 5: \'This is not a case", "Comment 6: my mistake we are checking\'", "Comment 7: \'te dane się nie zapisują w DHC. !screenshot-2! !image-2023-01-04-13-17-31-951!ale są na elementach:!image-2023-01-04-13-25-43-014! !image-2023-01-04-13-25-56-119!\'", "Comment 8: \'Are these the only two cases?To resend the VT to ERP should not be canceled from the ERPsystem before?\'", "Comment 9: \'Could be more", "Comment 10: I hope you can see from DHC logging what is and what is not send.\'", "Comment 11: \'Can you resend", "Comment 12: than I can at least check if they come through\'", "Comment 13: \'Another example: VT-27/1/23 for location Ravenstein: also not arriving in the ERP. please check\'", "Comment 14: \'There is a delay in message processing", "Comment 15: messages need to be processed. !screenshot-3! \'", "Comment 16: \'do nocy może zejdzie ;) w 2h jakies 10 tysiecy message zeszlo !image-2023-01-04-16-39-20-647.png!\'", "Comment 17: \'Still 6000 in the queue? How is this possible? Is it related to DHP DB issues we had yesterday?\'", "Comment 18: \'Yes this is the most possible reason", \'Comment 19: it looks like almost 10 000 messages was proceed in 2 hours,\', "Comment 20: we are monitoring the queue. When i will be ok I will ( hope that will take about 1 hour) to ask you if there are any new examples of missing intake weight.\'", "Comment 21: \'All messages has pass could you please verify now?!image-2023-01-04-18-04-41-279.png!\'", \'Comment 22: "Hi\', "Comment 23: indeed I see the intakes are in ERP now. Let\'s have the ticket open (lower prio) for tomorrow", \'Comment 24: to see if there will be more cases"\', "Comment 25: \'According to Your request priority has been lowered to P2.Regards\'", "Comment 26: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
783	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8248\n\n### Instruction:\nDear, \r\npls update list of SU codes for CZ_SK and SK_HU medicated labels. \r\nthx\n\n### Response:\n["Comment 1: [\'[^SU codes SK_HU_03012023.csv] _(7 kB)_[^SU codes_CZ_SK_03012023.csv] _(12 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Dear Lucie,Codes are updated in Bestovice completely for both CZ_SK and SK_HU.However", \'Comment 4: for data base in Marefy for version CZ_SK in line 73\', "Comment 5: phrase from column E:_{color:#de350b}Prasata: Maso 11 dní / Mäso a vnútornosti: ošípané: 10 dní{color}_ is too long. This field allows only for 42 signs and phrase nas 58 signs (togehter with space signs).Is it possible to shorten it somehow?Regards\'", "Comment 6: \'Hi Lucie,In Marefy", \'Comment 7: we have modified column for highier number of signs. Then I have added label no 73.Please\', "Comment 8: verify.Regareds\'", "Comment 9: \'Hi", "Comment 10: it´s okay. You can close the issue.thx\']"]\nRelated Issues:\n[]\n\n### End'}
784	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8247\n\n### Instruction:\nDzień dobry,\r\n\r\nproszę o pomoc w przesunięciu AWD-97303/12/22 do DHP. W DHC jest widoczne natomiast nie przechodzi do DHP.\r\n\r\nSprawa pilna - auto na wadze. \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: \'ZaN_GIDNumer=3638959\'", "Comment 3: \'Proszę o zwolnienie dokumentu :!image-2023-01-03-19-20-25-690.png!\'", "Comment 4: \'Już wyszedłem z AWD. \'", "Comment 5: \'SN nie wpada do dhc dla niego jak i asn zadnych bledów resendy z dhc i gui nie nie dajawidze ze problem moze być tutaj!image-2023-01-03-19-53-10-012.png!\'", "Comment 6: \'podejrzane pliki logów!image-2023-01-03-19-57-43-987.png!\'", \'Comment 7: \\\'leca bledy dla technlogii2023-01-03 19:37:13,307 [48] ERROR Evolution.DHCService.Dhc30.Handlers.TechnologyChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-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.Technologies_dbo.ProductionRecipes_ProductionRecipeId". The conflict occurred in database "Evolution_DHCService"\', \'Comment 8: table "dbo.ProductionRecipes"\', "Comment 9: column \\\\\'Id\\\\\'.The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception", \'Comment 10: Boolean breakConnection\', \'Comment 11: Action`1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 12: Boolean breakConnection\', \'Comment 13: Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 14: Boolean callerHasConnectionLock\', \'Comment 15: Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 16: SqlCommand cmdHandler\', \'Comment 17: SqlDataReader dataStream\', \'Comment 18: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 19: TdsParserStateObject stateObj\', \'Comment 20: Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 21: RunBehavior runBehavior\', \'Comment 22: String resetOptionsString\', \'Comment 23: Boolean isInternal\', \'Comment 24: Boolean forDescribeParameterEncryption\', \'Comment 25: Boolean shouldCacheForAlwaysEncrypted) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 26: RunBehavior runBehavior\', \'Comment 27: Boolean returnStream\', \'Comment 28: Boolean async\', \'Comment 29: Int32 timeout\', \'Comment 30: Task& task\', \'Comment 31: Boolean asyncWrite\', \'Comment 32: Boolean inRetry\', \'Comment 33: SqlDataReader ds\', \'Comment 34: Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 35: RunBehavior runBehavior\', \'Comment 36: Boolean returnStream\', \'Comment 37: String method\', \'Comment 38: TaskCompletionSource`1 completion\', \'Comment 39: Int32 timeout\', \'Comment 40: Task& task\', \'Comment 41: Boolean& usedCache\', \'Comment 42: Boolean asyncWrite\', \'Comment 43: Boolean inRetry) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 44: RunBehavior runBehavior\', \'Comment 45: Boolean returnStream\', \'Comment 46: String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior\', \'Comment 47: String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.<>c.<Reader>b__6_0(DbCommand t\', \'Comment 48: DbCommandInterceptionContext`1 c) at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target\', \'Comment 49: Func`3 operation\', \'Comment 50: TInterceptionContext interceptionContext\', \'Comment 51: Action`3 executing\', \'Comment 52: Action`3 executed) at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command\', \'Comment 53: DbCommandInterceptionContext interceptionContext) at System.Data.Entity.Internal.InterceptableDbCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Entity.Core.Mapping.Update.Internal.DynamicUpdateCommand.Execute(Dictionary`2 identifierValues\', \'Comment 54: List`1 generatedValues) at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update() --- End of inner exception stack trace --- at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update() at System.Data.Entity.Core.EntityClient.Internal.EntityAdapter.<>c.<Update>b__21_0(UpdateTranslator ut) at System.Data.Entity.Core.EntityClient.Internal.EntityAdapter.Update[T](T noChangesResult\', \'Comment 55: Func`2 updateFunction) at System.Data.Entity.Core.EntityClient.Internal.EntityAdapter.Update() at System.Data.Entity.Core.Objects.ObjectContext.<SaveChangesToStore>b__153_0() at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func\', \'Comment 56: IDbExecutionStrategy executionStrategy\', \'Comment 57: Boolean startLocalTransaction\', \'Comment 58: Boolean releaseConnectionOnSuccess) at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesToStore(SaveOptions options\', \'Comment 59: IDbExecutionStrategy executionStrategy\', \'Comment 60: Boolean startLocalTransaction) at System.Data.Entity.Core.Objects.ObjectContext.<>c__DisplayClass148_0.<SaveChangesInternal>b__0() at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation) at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesInternal(SaveOptions options\', "Comment 61: Boolean executeInExistingTransaction) at System.Data.Entity.Core.Objects.ObjectContext.SaveChanges(SaveOptions options) at System.Data.Entity.Internal.InternalContext.SaveChanges() --- End of inner exception stack trace --- at System.Data.Entity.Internal.InternalContext.SaveChanges() at System.Data.Entity.Internal.LazyInternalContext.SaveChanges() at System.Data.Entity.DbContext.SaveChanges() at Evolution.DHCService.Dhc30.Handlers.BaseMessageHandler`2.Handle(TMessage message) in E:\\\\\\\\BambooHome\'", "Comment 62: \'Proszę o zmianę statusu na P2.\'", "Comment 63: \'AWD widoczne w DHP - proszę o zamknięcie zgłoszenia. \']"]\nRelated Issues:\n[]\n\n### End'}
785	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8246\n\n### Instruction:\nHi\r\n\r\nWe are trying to confirm the Stocktaking Location STK-165/1/23 in Warehouse orders list, however the system shows an error message.\r\nWe tried to cancel it, but there\'s no option to cancel.\r\n\r\nWe opened a STK-LO for the same location hours ago and no problem were found\r\n\r\nSame situation happened in DGS-8233 and you changed the status of STK in WMS engine than it worked.\r\n\r\nWe are under full inventory routine, waiting for it.\r\nCould you please help us?\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'HelloWe have DGS-8220", \'Comment 2: DGS-8233\', "Comment 3: DGS-8234 and DGS-8243 that is related to this issue.Thank you\'", "Comment 4: \'\'", "Comment 5: \'The problem was caused by an erroneous unit load creation after a failed index grouping. A fix for the error is already prepared and such ULs will not be created.\'", \'Comment 6: "Hi AgnieszkaThank you for the information.We\\\'ll wait for the fix"]\']\nRelated Issues:\n[\'DGS-8243\', \'DAP-13153\', \'DAP-13152\', \'DGS-8220\', \'DGS-8233\', \'DGS-8234\', \'DGS-8975\']\n\n### End'}
786	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8245\n\n### Instruction:\nHi\r\n\r\nThe integration of DHC x DHP is not working properly.\r\nThe Sales Order OVE-071875 is in DHC, but not in DHP.\r\nItem: MTP5266-MD-S20 (all units not integrated)\r\n\r\nI think the problem is with this item but I don\'t know why\r\n\r\nCould you please help us?\n\n### Response:\n[\'Comment 1: ["Obydwa kodyMTP5266-MD-S20 iMTP5266-MD ( któy jest base itemem ) nie przechodziły do dhc serviceW bazie dhc service brakowałoselect * from items where id=\\\'74AB78BD-1655-4353-AD93-F1BB844711B3\\\'select * from DhhItems where id=\\\'62E522C1-58AA-4AE0-A378-04D0E041B6C6\\\'select * from items where id=\\\'B8778752-D925-4EDC-957B-8E1377ED8BDA\\\' ( base item)Dodałam dhhitem do bazy dhc service i potem od apki dosłałam itemy.[[email protected]]z tego co widziałąm był błędy dla is medicinal i to wygląda na stary bład\', \'Comment 2: chyba że to coś innego i było popriwane dla 3.0.https://helpdesk.kotrak.com/browse/DAP-6068?jql=text%20~%20%22is%20medicinal%22"\', "Comment 3: \'[[email protected]]najprawdopodobniej jest to błąd który nie występuje w najnowszym DHC na który mają przechodzić przed podniesieniem Rio Claro", "Comment 4: zapytaj się klienta czy jest potrzeba RCA.\'", "Comment 5: \'It has been ascertained that this error does not exist in the latest DHc for which an upgrade is planned", "Comment 6: Can the task be closed in this situation?\'", "Comment 7: \'Hi AgnieszkaWhich version of DHC is this fixed?Yes", "Comment 8: you can close this task.Thank you very much\'", "Comment 9: \'poprawione w wersji DHC 3.0.60\'", "Comment 10: \'Hello Maicon it was fixed in DHC 3.0.60Regards.\']"]\nRelated Issues:\n[\'DGS-8241\']\n\n### End'}
787	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8244\n\n### Instruction:\nHi\r\n\r\nWe have 6 StockUnits with different information between Stock and PCS engine.\r\nThey are missing in PCS and we need it to dose it on the Production Orders in progress.\r\n\r\n* 88-OB00KF\r\n* 88-OB00JQ\r\n* 88-W02781\r\n* 88-W0277Z\r\n* 88-W0F2UV\r\n* 88-W02780\r\n\r\nCould you please help us?\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'Hello", "Comment 2: We kindly inform you that wecurrentlyare processing another Priority1 task. -dgs-8243We will revert to processing your task as soon as possible.Regards\'", "Comment 3: \'GuysI know you are working on another P1", "Comment 4: but this is also urgentIs there only one person in KOTRAK team to give us support?The production line is waiting since we raised this task.Thank you\'", "Comment 5: \'We are investigentigating this issue\'", "Comment 6: \'Please check now.\'", \'Comment 7: "Didn\\\'t work :("\', "Comment 8: \'[[email protected]]I can see quantities please look on the screenshot below:!image-2023-01-03-17-30-36-082.png!\'", \'Comment 9: "Hi MaciejSELECT * FROM DHPlantPCSBusinessLogicMain.api.StockUnits su WHERE su.Barcode = \\\'88-OB00KF\\\'All has the same status"\', "Comment 10: \'[[email protected]]now you should be able to see barcodes\'", \'Comment 11: "Problem polegał na tym ze kody nie byly widoczne w tabeli api.StockUnits. NIe było ich tam ponieważ miały status recrated. I to jest dobre zachowanie. Kiedys był błąd z kodami recrated. Przypadki wyglądają jakby były z września czyli sprzed wersji 8.3. To co zrobiłem to zaktualizowałem wskazanie do dobrego stockUnitId oraz zmieniłem status i ilosci na kodach.Do naprawy użyłem następującego skryptu:{code:java}update suset su.id = \\\'E03C2ADA-0613-471A-98B8-BA32AA94A797\\\'\', \'Comment 12: LogisticStatus = 4--\', \'Comment 13: quantity = 7344.000000\', \'Comment 14: QuantityOnHand = 7344.000000from DHPlantPCSBusinessLogicMain.dbo.StockUnits su WHERE su.Barcode = \\\'88-W02780\\\'SELECT * FROM DHPlantPCSBusinessLogicMain.dbo.StockUnits su WHERE su.Barcode like \\\'%88-OB00KF%\\\'SELECT * FROM DHPlantPCSBusinessLogicMain.dbo.StockUnits su WHERE su.id = \\\'AC876897-84B2-42AE-8CB4-85A3758FCDE1\\\'select * from DHPlantstockBusinessLogicMain.dbo.StockUnits where barcode like \\\'%88-W02780%\\\'SELECT * FROM DHPlantPCSBusinessLogicMain.api.StockUnits su WHERE su.Barcode = \\\'88-W02780\\\'SELECT * FROM DHPlantPCSBusinessLogicMain.dbo.StockUnits su WHERE su.Barcode = \\\'88-W02780\\\'{code}"\', "Comment 15: \'Now it worked!Tahnk you very muchYou can close this task\'", "Comment 16: \'[Weryfikacja ilości i jednostek w DHP miedzy modułami. Brazylia pcs i stock - różnice z pcs.\|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#Weryfikacja%20ilo%C5%9Bci%20i%20jednostek%20w%20DHP%20miedzy%20modu%C5%82ami.%20Brazylia%20pcs&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{1E9D684B-2D7C-425D-AB4F-3D4AF6624A05}&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%2FWeryfikacja%20ilo%C5%9Bci%20i%20jednostek%20w%20DHP%20miedzy%20modu%C5%82ami.%20Brazylia%20pcs%7C1E9D684B-2D7C-425D-AB4F-3D4AF6624A05%2F%29])\']"]\nRelated Issues:\n[]\n\n### End'}
788	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8243\n\n### Instruction:\nHi\r\n\r\nWe are trying to confirm the Stocktaking Location STK-165/1/23 in Warehouse orders list, however the system shows an error message.\r\nWe tried to cancel it, but there\'s no option to cancel.\r\n\r\nWe opened a STK-LO for the same location hours ago and no problem were found\r\n\r\nSame situation happened in DGS-8233 and you changed the status of STK in WMS engine than it worked.\r\n\r\nWe are under full inventory routine, waiting for it.\r\nCould you please help us?\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello", "Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task under DGS-8241We will revert to processing your task as soon as possible.Regards\'", "Comment 4: \'stockagingid79be8322-c841-4815-baa9-0eaf66bd846cwoidid=c3629db4-4852-4917-97e6-4975ed82502e&!image-2023-01-03-14-25-14-125.png!\'", "Comment 5: \'!image-2023-01-03-14-26-39-353.png!\'", "Comment 6: \'Hi,we are not able to get to the serwer10.55.49.12 !image-2023-01-03-14-45-39-221.png!For other ip it is working fine", "Comment 7: could you verify?\'", "Comment 8: \'Hi [[email protected]]Could you please help us with access for Agnieszka as admin on Gua server?Thank you very much\'", "Comment 9: \'Hi! I changed the password: 123ChangeCould you try please?Best Regards", "Comment 10: \'", "Comment 11: \'Plase use the domain: mubbrasil.local\\\\\\\\your user\'", "Comment 12: \'Still do not work", "Comment 13: this previuos password works for other rdp but not here maybe the ip address is wrong ?Maybe my and Aleksandra Przybyłek user are not added to this location?!image-2023-01-03-15-02-00-748.png!\'", "Comment 14: \'Hi Agnieszkain your screenshot you are trying domain DEHEUSBRAZIL", "Comment 15: however for Guararapes there is this other domain that Ludemila informed.Could you please try with this other mubbrasil.local domain?Thank you\'", "Comment 16: \'Ok it works now thank You.\'", "Comment 17: \'HiHow much time will you need to check this?Maybe we can try to open a new STK for this locationThe factory is stoped", \'Comment 18: there are new POs waiting to start production\', "Comment 19: many people calling me.What do you think of this idea?Thank you\'", "Comment 20: \'Please verify\'", "Comment 21: \'Hi AgnieszkaNow we can see the WO in mobile screenThank you very much!You can close this task", \'Comment 22: but please\', "Comment 23: raise a RCA this happened 4 times in last 24 hours in different Business UnitsThank you\'", "Comment 24: \'RCA is underDGS-8246\']"]\nRelated Issues:\n[\'DGS-8246\', \'DGS-8234\']\n\n### End'}
789	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8242\n\n### Instruction:\nCan you please cancel this trip in DHC/DHP? Status in ERP is cancelled, but it is still in DHapps, which is not correct. trip foreign document number =2_L000095781\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,2_L000095781 has been cancelled both in DHP and DHC.Regards!image-2023-01-04-12-59-12-055.png!!image-2023-01-04-12-59-31-690.png!\'", "Comment 4: \'Thanks", "Comment 5: ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
790	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8241\n\n### Instruction:\nHi\r\n\r\nThe integration of DHC x DHP is not working properly.\r\nThe Sales Order OVE-071875 is in DHC, but not in DHP.\r\nItem: MTP5266-MD-S20 (all units not integrated)\r\n\r\nI think the problem is with this item but I don\'t know why\r\n\r\nCould you please help us?\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "brak order elementów\', \'Comment 3: itemu\', \'Comment 4: dhh itemu w bazie dhc serviceselect * from OrderElements where OrderId=\\\'D432178C-B45B-421D-B2D7-35E2B44291D4\\\'select * from items where id=\\\'74AB78BD-1655-4353-AD93-F1BB844711B3\\\'select * from DhhItems where id=\\\'62E522C1-58AA-4AE0-A378-04D0E041B6C6\\\'select * from items where id=\\\'B8778752-D925-4EDC-957B-8E1377ED8BDA\\\'"\', "Comment 5: \'Item i base item sa is medicimal\'", "Comment 6: \'https://helpdesk.kotrak.com/browse/DAP-10894https://helpdesk.kotrak.com/browse/DAP-6068\'", "Comment 7: \'Could you please try to resend orders to dhc once again?\'", \'Comment 8: "to już w dhc service jestselect * from items where id=\\\'74AB78BD-1655-4353-AD93-F1BB844711B3\\\'select * from ItemExportInfoes where EntityId=\\\'74AB78BD-1655-4353-AD93-F1BB844711B3\\\'select * from DhhItems where id=\\\'62E522C1-58AA-4AE0-A378-04D0E041B6C6\\\'select * from items where id=\\\'B8778752-D925-4EDC-957B-8E1377ED8BDA\\\'"\', \'Comment 9: "Hi AgnieszkaJust sent and now it worked!What was the reason the item MTP5266-MD-S20 didn\\\'t integrate?Thank you very much!You can close this task!image!"\', "Comment 10: \'Yes from what I can see both items was set as is medicinal", "Comment 11: that seems blocked it to be set to dhc service.I may raise RCA task for that issue if you wish.!image-2023-01-03-15-32-36-897.png!\'", \'Comment 12: "HiYes\', \'Comment 13: please!Raise a RCA because it\\\'s normal to have medicinal items. DHC service can\\\'t block the integration of the medicinal item or Sales order with medicinal items.The validation of prodution or dispatch is on DHP sideThank you"\', "Comment 14: \'RCA was created asDGS-8245Thank Youbye\']"]\nRelated Issues:\n[\'DGS-8245\', \'DGS-8252\']\n\n### End'}
791	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8240\n\n### Instruction:\nHi\r\nFrom Ada.\r\n\r\nRafał Boniecki\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Realized. Approved with Adrianna by call\'", "Comment 3: \'!image-1!\'", "Comment 4: \'ostatni komentarz chyba miał być do zgłoszenia odnośnie raportu DRA. Dodatek z tego zgłoszenia nie ma nic wspólnego z DRA\'", "Comment 5: \'Zgadza się. Ten temat do zamknięcią. Dziekuję.\']"]\nRelated Issues:\n[]\n\n### End'}
792	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8239\n\n### Instruction:\nGood morning, \r\n\r\nBest wishes to you all for 2023!\r\n\r\nFor an SKV invoice we have to make registered posting to a fictive customer to be able to see these posts on the various rounds. \r\nFor PI-RLN/2023/0005 ID82249. I made this action, see tab Elements to Sales Invoice. I think I have put the sales invoice in the flow, while thinking I was in the purchase invoice.\r\n\r\nCan this be corrected? The registered sales invoices on tab Elements to Sales Invoice should be released.\r\n(SI-RTN/2023/0008 ID82279 is not correct for this reason)\r\n\r\nThanks for your help.\r\n\r\nChristine\r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Hi Christine,Do you mean that fromPI-RLN/2023/0005 should be create many sales invoices by \\\'Create Sales Invoices\\\' button at the bottom of document and now it\\\'s not possible becausePI-RLN/2023/0005 is Archived?SI-RTN/2023/0008 isn\\\'t correct because it\\\'s generated from first tab (Purchase Invoice) instead of button from second tab (Elements to Sales Invoices) and should be deleted?!image-2023-01-03-12-09-39-697.png!"\', "Comment 3: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Yes indeed. I was working from Elements to Sales Invoice", \'Comment 4: but probably I was distracted by a question and started the flow while thinking I was in the PI.{color} {color:black}The PI is correct\', \'Comment 5: but the one sales invoice{color} SI-RTN/2023/0008 should be the several ones. {color:black}Can you open the flow (button) so I can make the registrations as prepared?{color} {color:black}{color} {color:black}Sorry for the inconvenience{color} {color:black}😊{color}{color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| \|{color:black}{color} !image006.jpg\|thumbnail!{color:black}{color} \| Van: Damian Świstek (Jira) <[email protected]> Verzonden: dinsdag 3 januari 2023 12:28 Aan: Jong\', "Comment 6: Christine de <[email protected]> Onderwerp: DGS-8239 Regular Purchase to several registered sales invoices \| {color:white} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} \| !image007!\'", \'Comment 7: "Ok\', \'Comment 8: I deleted the wrong sales invoice SI-RTN/2023/0008.PI-RLN/2023/0005 now is in Entry and you can create many sales invoices from tab \\\'Elements to Sales Invoice\\\'.Please remember that when you Archive thePI-RLN/2023/0005 it will be sent to Milas again."]\']\nRelated Issues:\n[]\n\n### End'}
793	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8238\n\n### Instruction:\nCoud you check the filters on WMS items list, please. It doesn\'t work properly. What is different in the list and what the filter shows is different\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: "Cały select{code:java}SELECT M.RgM_Id AS Id\', \'Comment 4: S.StE_Address AS Address\', \'Comment 5: ISNULL(A.Art_Code\', \'Comment 6: dbo.GetAssemblyItemCodes(M.RgM_Id)) AS ArticleCode\', \'Comment 7: A.Art_Name AS ArticleName,A.Art_Unit AS ItemUnit,M.RgM_Code AS PalletCode,ISNULL(A.Art_Name\', "Comment 8: \'\') AS WMSProductsName", \'Comment 9: M.RgM_Quantity AS Quantity\', \'Comment 10: CASE WHEN (D.Del_Id IS NOT NULL) THEN D.Del_ExpiryDate END AS ExpirationDate\', \'Comment 11: CAST( D.Del_IssueDate AS datetime2) AS IssueDate\', \'Comment 12: S.StE_Id as StorageElementId,CAST((CASE WHEN Del_3PlCstId IS NULL THEN 0 ELSE 1 END) AS BIT) AS IsThirdPartyItem,case when M.RgM_Type = 8 then dbo.Kr_GetAssemblySerialNumber(M.RgM_Id) else D.Del_SerialNumber end as SerialNumbers,S.ste_code StorageElementCode,S.StE_BsUId as BusinessUnitId,D.Del_PkGId AS WarehousePackageId,CAST(M.RgM_Type AS int) as BarcodeType,CASE WHEN H.VtH_Id is not null THEN dbo.GetDocumentNumber(H.VtH_DocType\', \'Comment 13: H.VtH_DocNumber\', \'Comment 14: H.VtH_DocMonth\', \'Comment 15: H.VtH_DocYear\', \'Comment 16: null) WHEN cast(PH.PlH_LotNumber as nvarchar) is not null THEN cast(PH.PlH_LotNumber as nvarchar) WHEN IH.INH_ID is not null THEN dbo.GetDocumentNumber(IH.INH_DocType\', \'Comment 17: IH.INH_DocNumber\', \'Comment 18: IH.INH_DocMonth\', \'Comment 19: IH.INH_DocYear\', \'Comment 20: null) WHEN CPH.CpH_Id is not null THEN dbo.GetDocumentNumber(CPH.CpH_DocType\', \'Comment 21: CPH.CpH_DocNumber\', \'Comment 22: CPH.CpH_DocMonth\', \'Comment 23: CPH.CpH_DocYear\', \'Comment 24: null) ELSE ISNULL(dbo.GetAssemblyOrder(M.RgM_Id)\', "Comment 25: \'-\')END as Document,R.OrderDocumentNumber AS OrderDocumentNumber,D.Del_ForeignSerialNumber as ForeignSerialNumber,S.StE_IsPickingLocation AS IsPickingLocation,S.StE_ProductionArea AS IsProductionAreaFROM dbo.RegisterMappings AS M INNER JOIN dbo.WMSStorageElements AS S ON M.RgM_StEId = S.StE_IdLEFT OUTER JOIN dbo.Delivery AS D ON M.RgM_DelId = D.Del_IdLEFT OUTER JOIN dbo.ArticleCard AS A ON M.RgM_ArtId = A.Art_IdLEFT JOIN dbo.VehicleTicketElement E on E.VtE_Id = D.Del_VtEIdLEFT JOIN dbo.VehicleTicketHeader H ON E.VtE_VtHId = H.VtH_IdLEFT JOIN dbo.ProductionLotReportHeader PH on PH.PlH_Id = D.Del_PlHIdLEFT JOIN dbo.InventoryElement IE on IE.INE_Id = D.Del_INEIdLEFT JOIN dbo.InventoryHeader IH ON IE.INE_InHId = IH.INH_IdLEFT JOIN dbo.ChangePackageElement CPE ON CPE.CpE_Id = D.Del_CpEIdLEFT JOIN dbo.ChangePackageHeader CPH on CPH.CpH_Id = CPE.CpE_CpHIdLEFT JOIN( SELECT DISTINCT Res_RgMId", \'Comment 26: dbo.GetDocumentNumber(dbo.OrderMapper(OH.OdH_OrdType)\', \'Comment 27: OH.OdH_OrdNumber\', \'Comment 28: OH.OdH_OrdMonth\', \'Comment 29: OH.OdH_OrdYear\', \'Comment 30: OH.OdH_OrdSeries) AS OrderDocumentNumber FROM dbo.Reservation R INNER JOIN dbo.OrderElement OE ON OE.OdE_Id = R.Res_ObjectId INNER JOIN dbo.OrderHeader OH ON OH.OdH_Id = OE.OdE_OdHId) R ON R.Res_RgMId = M.RgM_Idwhere M.RgM_IsReleased = 0 and M.RgM_Quantity > 0and S.StE_IsArchival = 0 AND M.RgM_ParrentID IS NULL AND M.RgM_AssemblyLogisticId IS NULL AND M.RgM_IsActivated = 1 AND S.StE_IsVirtual = 0 AND S.StE_BsUId IN (6){code}Różnica po zaznaczeniu !screenshot-1! {code:java}( DATEDIFF(dd,GETDATE()\', \'Comment 31: D.Del_ExpiryDate) > 1.00 and DATEDIFF(dd,GETDATE()\', \'Comment 32: D.Del_ExpiryDate) < 30.00 OR DATEDIFF(dd,GETDATE()\', \'Comment 33: D.Del_ExpiryDate) > 31.00 and DATEDIFF(dd,GETDATE()\', \'Comment 34: D.Del_ExpiryDate) < 90.00 ){code}"\', "Comment 35: \' !screenshot-2! Hello.Checking the box displays a list with the condition where the expiry of deliveries is less than 30 days and greater than 1 day from the current date. Del_ExpiryDate.Regards.\'", "Comment 36: \'[[DHP] WMS - widok produktów\|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHP.one#%5bDHP%5d%20WMS%20-%20widok%20produkt%C3%B3w&section-id=\\\\\\\\{F3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9}&page-id=\\\\\\\\{488531BA-0246-4268-ABFD-79E1C25C3E3A}&end] ([Widok sieci Web\|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHP.one%7CF3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9%2F%5BDHP%5D%20WMS%20-%20widok%20produkt%C3%B3w%7C488531BA-0246-4268-ABFD-79E1C25C3E3A%2F%29])\'", "Comment 37: \'but the list of results should be the same", \'Comment 38: whether using a filter or a list\', "Comment 39: in both cases it should be the same\'", "Comment 40: \'Can you point the differences after the article code?examples?\'", "Comment 41: \'910914-W25 at this moment", "Comment 42: Have you done sth?\'", "Comment 43: \' !screenshot-3! w warunkach są luki dla granicznych dni.\'", "Comment 44: \'We can process the change of this filtering but as a GDC with a 4 hours.Please accept the cost.\'", "Comment 45: \'What does this change entail? A new version of DHP 2.7 will be needed or just some small cosmetic change in the way the current filter works\'", "Comment 46: \'Yes", "Comment 47: only applies to change for filtering.\'", "Comment 48: \'ok clear", "Comment 49: you can do it:)\'", "Comment 50: \'GDC-806 has been created.\'", "Comment 51: \'ok", "Comment 52: thx:)\'", "Comment 53: \'Thanks too", "Comment 54: so we closed this ticket.\']"]\nRelated Issues:\n[]\n\n### End'}
794	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8237\n\n### Instruction:\nVT 25/1/23 has duplicated the elements in DHP generated SOR 12 and 13 only 13 synced to DHC.\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: \'!image-2023-01-03-10-25-48-563.png!Jest luka", "Comment 4: nie ma SOR-12!image-2023-01-03-10-29-47-326.png!\'", "Comment 5: \'Podobnie jak w tasku https://helpdesk.kotrak.com/browse/DGS-7973SOR-12 nie zreleasował stocka!image-2023-01-03-10-48-45-654.png!!image-2023-01-03-10-49-19-465.png!\'", "Comment 6: \'Dear Thabile,Similar as inDGS-7973", \'Comment 7: SOR-12 did not generate in EXP XL as well. What is more\', \'Comment 8: the quantity was not relesaed form the Stock. I suggest that we could just delete SOR-12 from the DHP system. Please\', "Comment 9: let us know if it is fine for you.Regards\'", "Comment 10: \'Hello", "Comment 11: yes you can delete\'", \'Comment 12: "SOR-12 w logach{code:java}2023-01-02 03:04:37,418 [26] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution started2023-01-02 03:04:37,543 [26] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-25/1/2023/UR [Id: 2ab18ebe-adf8-4f90-9fe0-45dc491fd6e8]2023-01-02 03:04:37,543 [26] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-02 03:04:37,559 [26] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-02 03:04:37,669 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - GenerateSalesOrderRelease execution started2023-01-02 03:04:37,778 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Forcing document number - 12/0/2023/PUR for vt element id - Id: 048ded9f-c47a-4e29-b9e6-21ad17f022132023-01-02 03:04:37,825 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Enter SORPriceExtension2023-01-02 03:04:37,825 [80] DEBUG SORPriceSystemSQLLogger [(null)] - declare @price DECIMAL(15,4); EXECUTE [dbo].[spGetSorPriceERPINT] 1227\', "Comment 13: \'2023-01-02 03:04:26.690\'", \'Comment 14: 22463\', \'Comment 15: 9.260000\', \'Comment 16: 960\', \'Comment 17: 790832\', \'Comment 18: 4\', \'Comment 19: 12756\', \'Comment 20: @price OUTPUT2023-01-02 03:04:37,934 [80] DEBUG SORPriceSystemSQLLogger [(null)] - select @price as Calculated\', \'Comment 21: 7768.7800 as Result2023-01-02 03:04:37,934 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Calculated SOR price 7768.78002023-01-02 03:04:37,997 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Enter SORPriceExtension2023-01-02 03:04:37,997 [80] DEBUG SORPriceSystemSQLLogger [(null)] - declare @price DECIMAL(15,4); EXECUTE [dbo].[spGetSorPriceERPINT] 1227\', "Comment 22: \'2023-01-02 03:04:26.690\'", \'Comment 23: 26037\', \'Comment 24: 2.880000\', \'Comment 25: 960\', \'Comment 26: 790832\', \'Comment 27: 2\', \'Comment 28: 12756\', \'Comment 29: @price OUTPUT2023-01-02 03:04:38,075 [80] DEBUG SORPriceSystemSQLLogger [(null)] - select @price as Calculated\', \'Comment 30: 7949.7800 as Result2023-01-02 03:04:38,075 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Calculated SOR price 7949.78002023-01-02 03:04:38,122 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Enter SORPriceExtension2023-01-02 03:04:38,122 [80] DEBUG SORPriceSystemSQLLogger [(null)] - declare @price DECIMAL(15,4); EXECUTE [dbo].[spGetSorPriceERPINT] 1227\', "Comment 31: \'2023-01-02 03:04:26.690\'", \'Comment 32: 22455\', \'Comment 33: 9.100000\', \'Comment 34: 960\', \'Comment 35: 790832\', \'Comment 36: 1\', \'Comment 37: 12756\', \'Comment 38: @price OUTPUT2023-01-02 03:04:38,231 [80] DEBUG SORPriceSystemSQLLogger [(null)] - select @price as Calculated\', \'Comment 39: 8424.7800 as Result2023-01-02 03:04:38,231 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Calculated SOR price 8424.78002023-01-02 03:04:38,309 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Enter SORPriceExtension2023-01-02 03:04:38,309 [80] DEBUG SORPriceSystemSQLLogger [(null)] - declare @price DECIMAL(15,4); EXECUTE [dbo].[spGetSorPriceERPINT] 1227\', "Comment 40: \'2023-01-02 03:04:26.690\'", \'Comment 41: 22459\', \'Comment 42: 8.840000\', \'Comment 43: 960\', \'Comment 44: 790832\', \'Comment 45: 3\', \'Comment 46: 12756\', \'Comment 47: @price OUTPUT2023-01-02 03:04:38,403 [80] DEBUG SORPriceSystemSQLLogger [(null)] - select @price as Calculated\', \'Comment 48: 7949.7800 as Result2023-01-02 03:04:38,403 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Calculated SOR price 7949.78002023-01-02 03:04:38,403 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - VehicleTicketElement Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-02 03:04:38,748 [80] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - VehicleTicketElement Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-02 03:04:38,764 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Transactions.XLTransaction [(null)] - XL transaction created\', \'Comment 49: token ID - <O6;B1Cc=QO:lF0G._904]5---.@?=--2023-01-02 03:04:38,764 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Found reservation 1\', "Comment 50: 81176812023-01-02 03:04:38,780 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - --== Changed reservations ==--2023-01-02 03:04:38,780 [80] INFO Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Reservation of id \'Firma:556290 - TYP:2576/NUMER:8117681/LP:0\' has been changed from quantity 9.0000 to 9.260000 (Q:9.260000 E:0.0000)For order element - Firma:556290 - TYP:960/NUMER:790832/LP:42023-01-02 03:04:38,780 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Found reservation 1", \'Comment 51: 81176792023-01-02 03:04:38,795 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Found reservation 1\', "Comment 52: 81176782023-01-02 03:04:38,795 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - --== Changed reservations ==--2023-01-02 03:04:38,795 [80] INFO Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Reservation of id \'Firma:556290 - TYP:2576/NUMER:8117678/LP:0\' has been changed from quantity 9.0000 to 9.100000 (Q:9.100000 E:0.0000)For order element - Firma:556290 - TYP:960/NUMER:790832/LP:12023-01-02 03:04:38,811 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Found reservation 1", \'Comment 53: 81176802023-01-02 03:04:38,811 [80] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-01-02 03:04:38,811 [80] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-01-02 03:04:38,811 [80] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-01-02 03:04:38,811 [80] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-01-02 03:04:38,811 [80] DEBUG Evolution.ErpIntegrator.CdnXL.Interfaces.Documents.ExternalOrderTransactions.XLAPIExternalOrderTransaction [(null)] - NB Flag - Class = Net\', \'Comment 54: API = N2023-01-02 03:04:38,998 [80] INFO Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - SalesOrderRelease created: Firma:556290 - TYP:2001/NUMER:4054201/LP:0 SOR-12/23/PUR2023-01-02 03:04:38,998 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - Element creating: Code:PA07030-S7238-P Q:9.2600002023-01-02 03:04:38,998 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - No deliveries found.2023-01-02 03:04:38,998 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - Catalog Price from elem: 7768.7800\', \'Comment 55: exRates: 12023-01-02 03:04:38,998 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - Catalog Price after currency recalc: 7768.7800\', \'Comment 56: exRates: 12023-01-02 03:04:39,108 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.SalesOrderReleases.CdnXL2019SalesOrderReleaseRepository [(null)] - Error occurred - document Firma:556290 - TYP:2001/NUMER:4054201/LP:0 will be deleted2023-01-02 03:04:39,108 [80] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - SalesOrderRelease closing: Firma:556290 - TYP:2001/NUMER:4054201/LP:0 (-1)2023-01-02 03:04:39,108 [80] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.SalesOrderReleases.CdnXL2019SalesOrderReleaseRepository [(null)] - Error occurred - document was not deletedError of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLZamknijDokument:3).API Name - XLZamknijDokumentAPI Result - 3ERRORS:\|Cannot find document header. (ZamknijDokument-3) at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository.CloseDocument(XLExternalOrderTransaction document\', \'Comment 57: DocumentStatus status) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2019ExternalOrderTransactionRepository.cs:line 530 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.SalesOrderReleases.CdnXL2019SalesOrderReleaseRepository.CloseDocument(XLSalesOrderRelease header\', \'Comment 58: DocumentStatus status) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\SalesOrderReleases\\\\\\\\CdnXL2019SalesOrderReleaseRepository.cs:line 84 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.SalesOrderReleases.CdnXL2019SalesOrderReleaseRepository.CreateSORWithElements(SalesOrderRelease salesOrderRelease\', \'Comment 59: Boolean confirmDoc) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\SalesOrderReleases\\\\\\\\CdnXL2019SalesOrderReleaseRepository.cs:line 312023-01-02 03:04:39,123 [80] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-01-02 03:04:39,123 [80] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-01-02 03:04:39,123 [80] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2019.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -1{code}SOR-13 w logach{code:java}2023-01-02 04:36:10,857 [16] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-25/1/2023/UR [Id: 2ab18ebe-adf8-4f90-9fe0-45dc491fd6e8]2023-01-02 04:36:10,857 [16] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-02 04:36:10,857 [16] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-02 04:36:10,982 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - GenerateSalesOrderRelease execution started2023-01-02 04:36:11,092 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Forcing document number - 13/0/2023/PUR for vt element id - Id: 048ded9f-c47a-4e29-b9e6-21ad17f022132023-01-02 04:36:11,138 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Enter SORPriceExtension2023-01-02 04:36:11,138 [104] DEBUG SORPriceSystemSQLLogger [(null)] - declare @price DECIMAL(15,4); EXECUTE [dbo].[spGetSorPriceERPINT] 1227\', "Comment 60: \'2023-01-02 03:05:38.393\'", \'Comment 61: 22463\', \'Comment 62: 9.260000\', \'Comment 63: 960\', \'Comment 64: 790832\', \'Comment 65: 4\', \'Comment 66: 12756\', \'Comment 67: @price OUTPUT2023-01-02 04:36:11,248 [104] DEBUG SORPriceSystemSQLLogger [(null)] - select @price as Calculated\', \'Comment 68: 7768.7800 as Result2023-01-02 04:36:11,248 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Calculated SOR price 7768.78002023-01-02 04:36:11,310 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Enter SORPriceExtension2023-01-02 04:36:11,310 [104] DEBUG SORPriceSystemSQLLogger [(null)] - declare @price DECIMAL(15,4); EXECUTE [dbo].[spGetSorPriceERPINT] 1227\', "Comment 69: \'2023-01-02 03:05:38.393\'", \'Comment 70: 26037\', \'Comment 71: 2.880000\', \'Comment 72: 960\', \'Comment 73: 790832\', \'Comment 74: 2\', \'Comment 75: 12756\', \'Comment 76: @price OUTPUT2023-01-02 04:36:11,420 [104] DEBUG SORPriceSystemSQLLogger [(null)] - select @price as Calculated\', \'Comment 77: 7949.7800 as Result2023-01-02 04:36:11,420 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Calculated SOR price 7949.78002023-01-02 04:36:11,482 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Enter SORPriceExtension2023-01-02 04:36:11,482 [104] DEBUG SORPriceSystemSQLLogger [(null)] - declare @price DECIMAL(15,4); EXECUTE [dbo].[spGetSorPriceERPINT] 1227\', "Comment 78: \'2023-01-02 03:05:38.393\'", \'Comment 79: 22455\', \'Comment 80: 9.100000\', \'Comment 81: 960\', \'Comment 82: 790832\', \'Comment 83: 1\', \'Comment 84: 12756\', \'Comment 85: @price OUTPUT2023-01-02 04:36:11,592 [104] DEBUG SORPriceSystemSQLLogger [(null)] - select @price as Calculated\', \'Comment 86: 8424.7800 as Result2023-01-02 04:36:11,607 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Calculated SOR price 8424.78002023-01-02 04:36:11,654 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Enter SORPriceExtension2023-01-02 04:36:11,654 [104] DEBUG SORPriceSystemSQLLogger [(null)] - declare @price DECIMAL(15,4); EXECUTE [dbo].[spGetSorPriceERPINT] 1227\', "Comment 87: \'2023-01-02 03:05:38.393\'", \'Comment 88: 22459\', \'Comment 89: 8.840000\', \'Comment 90: 960\', \'Comment 91: 790832\', \'Comment 92: 3\', \'Comment 93: 12756\', \'Comment 94: @price OUTPUT2023-01-02 04:36:11,748 [104] DEBUG SORPriceSystemSQLLogger [(null)] - select @price as Calculated\', \'Comment 95: 7949.7800 as Result2023-01-02 04:36:11,748 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Calculated SOR price 7949.78002023-01-02 04:36:11,748 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - VehicleTicketElement Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-02 04:36:12,139 [104] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - VehicleTicketElement Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-02 04:36:12,154 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Transactions.XLTransaction [(null)] - XL transaction created\', \'Comment 96: token ID - Z1H<M-cD-akd4Z9^4<9\\\\\\\\L]5----JB]--2023-01-02 04:36:12,154 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Found reservation 1\', "Comment 97: 81176812023-01-02 04:36:12,154 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - --== Changed reservations ==--2023-01-02 04:36:12,154 [104] INFO Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Reservation of id \'Firma:556290 - TYP:2576/NUMER:8117681/LP:0\' has been changed from quantity 9.0000 to 9.260000 (Q:9.260000 E:0.0000)For order element - Firma:556290 - TYP:960/NUMER:790832/LP:42023-01-02 04:36:12,170 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Found reservation 1", \'Comment 98: 81176792023-01-02 04:36:12,170 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Found reservation 1\', "Comment 99: 81176782023-01-02 04:36:12,170 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - --== Changed reservations ==--2023-01-02 04:36:12,170 [104] INFO Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Reservation of id \'Firma:556290 - TYP:2576/NUMER:8117678/LP:0\' has been changed from quantity 9.0000 to 9.100000 (Q:9.100000 E:0.0000)For order element - Firma:556290 - TYP:960/NUMER:790832/LP:12023-01-02 04:36:12,185 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.Ordes.CdnXL2019OrderRepository [(null)] - Found reservation 1", \'Comment 100: 81176802023-01-02 04:36:12,185 [104] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-01-02 04:36:12,185 [104] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-01-02 04:36:12,185 [104] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-01-02 04:36:12,185 [104] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-01-02 04:36:12,185 [104] DEBUG Evolution.ErpIntegrator.CdnXL.Interfaces.Documents.ExternalOrderTransactions.XLAPIExternalOrderTransaction [(null)] - NB Flag - Class = Net\', \'Comment 101: API = N2023-01-02 04:36:12,389 [104] INFO Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - SalesOrderRelease created: Firma:556290 - TYP:2001/NUMER:4054220/LP:0 SOR-13/23/PUR2023-01-02 04:36:12,389 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - Element creating: Code:PA07030-S7238-P Q:9.2600002023-01-02 04:36:12,389 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - No deliveries found.2023-01-02 04:36:12,389 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - Catalog Price from elem: 7768.7800\', \'Comment 102: exRates: 12023-01-02 04:36:12,389 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - Catalog Price after currency recalc: 7768.7800\', \'Comment 103: exRates: 12023-01-02 04:36:12,529 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.SalesOrderReleases.CdnXL2019SalesOrderReleaseRepository [(null)] - Error occurred - document Firma:556290 - TYP:2001/NUMER:4054220/LP:0 will be deleted2023-01-02 04:36:12,545 [104] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - SalesOrderRelease closing: Firma:556290 - TYP:2001/NUMER:4054220/LP:0 (-1)2023-01-02 04:36:12,545 [104] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.SalesOrderReleases.CdnXL2019SalesOrderReleaseRepository [(null)] - Error occurred - document was not deletedError of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLZamknijDokument:3).API Name - XLZamknijDokumentAPI Result - 3ERRORS:\|Cannot find document header. (ZamknijDokument-3) at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository.CloseDocument(XLExternalOrderTransaction document\', \'Comment 104: DocumentStatus status) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2019ExternalOrderTransactionRepository.cs:line 530 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.SalesOrderReleases.CdnXL2019SalesOrderReleaseRepository.CloseDocument(XLSalesOrderRelease header\', \'Comment 105: DocumentStatus status) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\SalesOrderReleases\\\\\\\\CdnXL2019SalesOrderReleaseRepository.cs:line 84 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.SalesOrderReleases.CdnXL2019SalesOrderReleaseRepository.CreateSORWithElements(SalesOrderRelease salesOrderRelease\', \'Comment 106: Boolean confirmDoc) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\SalesOrderReleases\\\\\\\\CdnXL2019SalesOrderReleaseRepository.cs:line 312023-01-02 04:36:12,545 [104] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-01-02 04:36:12,545 [104] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-01-02 04:36:12,560 [104] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2019.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -1{code}"\', "Comment 107: \'!image-2023-01-04-11-26-56-485.png!!image-2023-01-04-11-27-23-339.png!!image-2023-01-04-11-29-02-433.png!\'", "Comment 108: \'Temat był już w zgłoszeniu https://helpdesk.kotrak.com/browse/DGS-5761(tylko tutaj pobrało stock) i tutaj https://helpdesk.kotrak.com/browse/DGS-7973(ze stocka nic nie zeszło)Maciek mówi", "Comment 109: żeby przed usunięciem zrobić RCA i zbadać temat\'", "Comment 110: \'Hello,Before I delete anything", "Comment 111: I have consulted your case with dev. The suggestion is to raise RCA task to find a root cause of this issue as it is reoccuring (ex DGS-7973 and DGS-5761). Do you accept raising RCA task?Regards\'", "Comment 112: \'Hello", "Comment 113: yes you can raise a RCA.\'", "Comment 114: \'Thank you\'", "Comment 115: \'RCA task is underDGS-8261Regards\'", "Comment 116: \'[^dgs-8237.xlsx]\'", "Comment 117: \'[^dgs-8237.xlsx]\'", "Comment 118: \'Hi,SOR-12 has been removed from DHP. Please", "Comment 119: also be informed taht RCA task is under dev investigation.Regards\'", "Comment 120: \'Thank you.\'", "Comment 121: \'Please", \'Comment 122: let me know if we can close this task and investigate in RCA. Please\', "Comment 123: confirm if you have access to RCA task.Regards\'", "Comment 124: \'yes you may. \'", "Comment 125: \'Thank you\']"]\nRelated Issues:\n[\'DGS-8261\', \'DGS-7973\']\n\n### End'}
795	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8236\n\n### Instruction:\nGoodmorning,\r\n\r\nIt looks like that there are problems with communication between DHP and PCS-systems. No data received on DHP.\r\n\r\nMissing displatches.\r\n\r\nPlease could you help me.\r\n\r\nKind regards,\r\n\r\nGerard\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: \\\'Ravenstein{code:java}2023-01-03 04:27:57 (/Plant.Integration.PCS.NL/DHVD01AP179/7848/33) [Error] Microsoft.AspNetCore.Server.IIS.Core.IISHttpServer - Connection ID ""16645304224371972817""\', \'Comment 3: Request ID ""80001ad2-0000-e700-b63f-84710c7967bb"": An unhandled exception was thrown by the application.System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', "Comment 4: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found.{code}\'", "Comment 5: \'Does the problem affect all plants?Is there currently an issue for Ravenstain as well", "Comment 6: in a previous task the application pools were restarted.I would like some examples - what is missing and from what plant.Regards.\'", "Comment 7: \'Yes", "Comment 8: the problem affect all plants.Regards,Gerard\'", "Comment 9: \'Please be informed we have an issue with the databaseserver", "Comment 10: which is under investigation by Valid.\'", "Comment 11: \'thank you for the information because we have information about connection problems to SQL Server in the logs\'", "Comment 12: \'Can we check after restarting the service for pcs on one selected plant", "Comment 13: will the problem persist?\'", "Comment 14: \' !screenshot-1! \'", \'Comment 15: "Databaseserver has been rebooted. In my monitoring of the inbound queues of the DHP instances\', "Comment 16: I see there is a big backlog for most of the factories. This backlog is not being processed very actively at the moment. Sneek and Andel don\'t have a backlog", \'Comment 17: but the others do. For example for Ravenstein there are 16000 messages waiting. Can you please check?"\', "Comment 18: \'DHP Andel keeps giving this error. Even after restarting DHPApiGateway (8080) site.!afbeelding!\'", "Comment 19: \'Please check Andel\'", \'Comment 20: "See below screenshot from location Meppel\', \'Comment 21: VT\\\'s created this morning do not have a deliveryID and are declined by pcs!afbeelding-1!"\', "Comment 22: \'Possible also related to database issues?\'", "Comment 23: \'Andel error message is gone now", "Comment 24: thanks.\'", "Comment 25: \'Please check Ravenstein and messages processing. \'", "Comment 26: \'Message processing is steadily going down. This is the graph of the past 2 hours for Ravenstein:!afbeelding-3!\'", "Comment 27: \' !screenshot-2! \'", "Comment 28: \'It has to be processed.\'", "Comment 29: \'All backlog is processed.If Gerard Geerts agrees I think we can close this ticket.\'", "Comment 30: \'Thank you for confirmation.Regards.\'", \'Comment 31: "Hello Piotr and Martijn,feedback from plants recieved. It\\\'s okay.Thanks for support. Please\', \'Comment 32: close this ticket.Regards,Gerard"]\']\nRelated Issues:\n[\'DGS-8218\', \'DGS-8235\']\n\n### End'}
796	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8235\n\n### Instruction:\nGoodmorning,\r\n\r\nwe got an internal error on DHVD01AP179. (see printscreen)\r\n\r\nPLease, could you help me?\r\n\r\nKind regards,\r\n\r\nGerard\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}Description: The process was terminated due to an unhandled exception.Exception Info: Autofac.Core.DependencyResolutionException: An exception was thrown while activating Plant.VC.BusinessLogic.Application.Configurations.ConfigurationJsonWriter -> λ:Plant.VC.BusinessLogic.Domain.Configuration.ConfigurationInfo. ---> 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. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', \'Comment 4: error: 40 - Could not open a connection to SQL Server){code} !screenshot-1! !screenshot-2! !screenshot-3! "\', "Comment 5: \'Please verify - after restarted application pools dhp should work properly now.\'", "Comment 6: \'Goodmorning Piotr,This problem is solved. Thanks for your support.Please close this ticket.Regards,Gerard\']"]\nRelated Issues:\n[\'DGS-8236\']\n\n### End'}
797	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8234\n\n### Instruction:\nHi\r\n\r\nWe are trying to confirm the Stocktaking Location STK-29/1/23 in Warehouse orders list, however the system shows an error message.\r\nCould you please help us?\r\nWe are under full inventory routine, waiting for it.\r\n\r\nWe opened a STK-LO for the same location hours ago and no problem were found\r\n\r\nSame situation happened in Toledo (DGS-8220) and Guararapes (DGS-8233) and you cancelled it so we opened a new STK and it worked.\r\n\r\nCould you please fix or at least change the status for Processable like you did for Guararapes?\r\n\r\nCould you please fix or cancel this STK-43/1/23?\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Please precise is itSTK-43/1/23 as in issue descroiption orSTK-69/1/23 as in screenshot.Also please let me know if we can proceed this one in the morning at 7:00 GMT time. I understand that there may be more issues like that and we could processe them all at once then.\'", \'Comment 4: "I\\\'m sorry. The right one is STK-29/1/23 for Itaberaí (please change in the title of this DGS)No! We can\\\'t wait. Please\', \'Comment 5: do wat you did for Guararapes.After you action was possible to Settle the STK-LO for Guararapes.I hope it will work for Itaberaí too.Thank you"\', \'Comment 6: "I\\\'m investigating your issue. I\\\'llwill inform you about the solution as soon as possible."\', \'Comment 7: "WO\\\'s for STK-69/1/23 in Itaberai have got Proceseable status. Please check."\', "Comment 8: \'Hi Bartłomiej It is thereThank you very much\'", "Comment 9: \'Grouped bags\']"]\nRelated Issues:\n[\'DGS-8243\', \'DGS-8246\']\n\n### End'}
798	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8233\n\n### Instruction:\nHi\r\n\r\nWe are trying to confirm the Stocktaking Location STK-43/1/23 in Warehouse orders list, however the system shows an error message.\r\nCould you please help us?\r\nWe are under full inventory routine, waiting for it.\r\n\r\nWe opened a STK-LO for the same location hours ago and no problem were found\r\n\r\nSame situation happened in Toledo (DGS-8220) and you cancelled it so we opened a new STK and it worked.\r\n\r\nCould you please fix or cancel this STK-43/1/23?\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "I\\\'m afraid that recreating STK document will not be enough. We need some more time for the analysis.Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible."\', "Comment 4: \'Hi Bartłomiej We are under full inventoryWe need to start counting it asap.All managers and full board of DeHeus Brazil are waiting for itHow much time do you need to check it?Thank you\'", \'Comment 5: "Hello Bartłomiej,Please have a look what Kotrak did in DGC-8220 refering a similiar or same problem reported in this DGS.DGC-8220 = https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8220It´s really urgent once we have all people doing the inventory counting followed by PwC auditors in all our plants.Thanks a lot and we\\\'re waiting a quick answer from your side.Juliano"\', \'Comment 6: "Hi\', \'Comment 7: Juliano this is not that case\', \'Comment 8: and no it is not similar. This issue is related to incorrect warehouse location configuration. We need more time to check that.At the moment we have created workaround for WO\\\'s for STK-43/1/23. They have got Proceseable status.Please check."\', \'Comment 9: "select * --into dbo.StorageLocationsBackfrom dbo.StorageLocationswhere ParentId = \\\'facf0953-0d0c-4a29-8d1d-5c124dd70ef3\\\'update dbo.StorageLocationsset ParentId = nullwhere ParentId = \\\'facf0953-0d0c-4a29-8d1d-5c124dd70ef3\\\'"\', \'Comment 10: "Hi Bartłomiej Thank you! We\\\'ll start processing this WO on mobile"\', "Comment 11: \'Please let me know if / when can I close this task.\'", \'Comment 12: "Maicon\', \'Comment 13: please contact Kotrak urgent (tomorrow) to understand what exactly is the wrong configuration\', "Comment 14: according Bartłomiej\'s information.Is really important mitigate all problems when we\'re performing inventory couting", \'Comment 15: in special the first one of the year\', \'Comment 16: including external auditing.Please let me know if I can help in anything.Thank you Bartłomiej for the support.Juliano"\', "Comment 17: \'[[DHP 3.0] Inwentaryzacja ", "Comment 18: Stocktaking Brazylia.\|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%20Inwentaryzacja%20,%20Stocktaking%20Brazylia.&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{B3F3F0B8-ADEF-4142-8A6F-E63F7E114E16}&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%20Inwentaryzacja%20%2C%20Stocktaking%20Brazylia.%7CB3F3F0B8-ADEF-4142-8A6F-E63F7E114E16%2F%29])\']"]\nRelated Issues:\n[\'DGS-8246\', \'DAP-13152\']\n\n### End'}
799	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8232\n\n### Instruction:\nDzień dobry,\r\n\r\nproszę o pomoc w wygenerowaniu VT z DHC - brak komunikatu błędu\r\nVT-44/1/2023/G\r\nSprawa pilna - klient fiskalny.\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: "2023-01-02 18:49:12,142 [14] WARN Evolution.ErpIntegrator.DHC.DHC30.Documents.VehicleTickets.VehicleTicketRepository [(null)] - Vehicle Ticket with number 44/1/2023/G (3fd0e8d7-c5d1-4581-8370-c73f2326cbbf) was not processed because it doesn\\\'t have all required elements."\', "Comment 3: \'Please check I did generate the sor for that vt,\'", "Comment 4: \'zastosowano poprawę ilości elementów na nagłówku:[[DHC] [VT] Problem z generowaniem dokumentów do VT\|[[DHC] [VT] Problem z generowaniem dokumentów do VT\|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHC.one#%5bDHC%5d%20%5bVT%5d%20Problem%20z%20generowaniem%20dokument%C3%B3w%20do%20VT&section-id=\\\\\\\\{7D50734F-49D8-4579-83B9-E51158168A8F}&page-id=\\\\\\\\{0E5254AC-5C56-4E96-9FC8-5FA601146685}&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%2F%5BDHC%5D%20%5BVT%5D%20Problem%20z%20generowaniem%20dokument%C3%B3w%20do%20VT%7C0E5254AC-5C56-4E96-9FC8-5FA601146685%2F%29])\'", "Comment 5: \'VT generated correctly", "Comment 6: what was the cause of the error?\'", "Comment 7: \'There weremismatch on the base between the quantity on the base on the vt header and the quantity of vt elements.In this task we have focused on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue", \'Comment 8: we may raise RootCause Analysis (RCA)task for you.Please\', "Comment 9: let us knowhow you wish us to proceed.\'", "Comment 10: \'Thanks for help", "Comment 11: please close task. \']"]\nRelated Issues:\n[]\n\n### End'}

Subsets and Splits